[SC-04E] Japan NTT DoCoMo Galaxy S 4 Users

cezeff

Senior Member
Sep 21, 2009
591
147
0
Okinawa, Japan
Thank you.
30K-40K is quite a discount but I think I will exhaust that discount with the basic fee for the data access.
Currently I rarely use cellular data. I'm mostly within a WiFi and have a WiMax modem I take when I go out. So having to pay for the basic data will offset most of the discount I get. Currently I pay only about 2500 Yen monthly (inclusive of White plan charges and small call charges. Most of my regular numbers are on Softbank so call charges arent that much). But if I move to Docomo I I guess I will paying in excess of 4500 Yen monthly (without any call or data charges).
I think its a matter of shelling out 75K at once for the phone vs. paying it monthly.
Plus all the bloatware in Docomo handsets are a dealbreaker too.
Thank you for the info guys.
cool....just know bloatware shouldnt be a deal breaker...there isnt that much on the sc-04e and once that root is fully working, you can say bye bye to bloat....in the long run the 75k up front would save you more money...thats the biggest upside to buying unsubsidized phones...hope you pick up one soon....
 

TonyC40

Member
Jan 19, 2013
34
1
0
I picked up mine today! I have been trying to extract the recovery.img, but for the life of me i cannot get it to work... any suggestions? I am using ADB shell but it keeps saying my device is offline...
 

cezeff

Senior Member
Sep 21, 2009
591
147
0
Okinawa, Japan
I picked up mine today! I have been trying to extract the recovery.img, but for the life of me i cannot get it to work... any suggestions? I am using ADB shell but it keeps saying my device is offline...
ok...cool....lets see if we can get this to work.....what version of windows are you using and do you have the proper drivers installed?
 

TonyC40

Member
Jan 19, 2013
34
1
0
ok...cool....lets see if we can get this to work.....what version of windows are you using and do you have the proper drivers installed?
Using windows 7 - just re-downloaded drivers - I can get it to read from the comp. but adb is showing "218fe911 - Offline"
 

cezeff

Senior Member
Sep 21, 2009
591
147
0
Okinawa, Japan
tried it all and still nothing... it picks up my s3 fine... just not the s4
i'm scouring the net now for some answers....

UPDATE: i think i did it....i followed a trick where you start a firmware update using Kies....once it finishes downloading and decompressing, right before it tries to install you pull the usb cord...at the same time you have your eyes on AppData\Temp and a folder will appear with the firmware update inside....copy it real quick once it finishes decompressing and bout to install... because once its done itll delete the temp file.....im not explaining it the best way but here is the guide i use to do it.....

http://forum.xda-developers.com/showthread.php?t=1170416

i look inside and sure enough its the boot.img and the recovery.img along with other stuff...im going to send it to Chain Fire to see what he says...cross your fingers this root works...

can you guys try the same method, in case i missed something or did something too soon....like an science experiment try to recreate the process to be sure its legit....
 
Last edited:

Chainfire

Moderator Emeritus / Senior Recognized Developer -
Oct 2, 2007
11,428
87,629
263
www.chainfire.eu
It's odd that using the I9505 CFAR would result in a partial root ... really odd. This might mean there's something different in your firmware from the I9505, because really that should mostly just work. You shouldn't need to update the binary after CFAR, is it reporting SuperSU v1.30 ? Also, can somebody confirm this device is running BML like someone suggested in an earlier post ?

Anyways, on a fresh device (without custom recovery or CFAR applied), you'd need to root using an exploit like Motochopper or whatever, then open an ADB shell session, execute "su" to gain root privileges (prompt will change from $ to # ), then execute this command (copy/paste the command, you'll probably mess up trying to enter it manually):

Code:
ls -l /dev/block/platform/*/by-name/recovery
It'll output something like:

Code:
lrwxrwxrwx root     root              1970-01-24 23:27 recovery -> /dev/block/mmcblk0pXX
The /dev/block/mmcblk0pXX part is the important bit! Now execute this command in the adb shell session:

Code:
dd if =/dev/block/mmcblk0pXX of=/data/local/tmp/recovery.img bs=512
Obviously replacing the XX part with whatever the command above returned. It should output something like this:

Code:
20480+0 records in
20480+0 records out
10485760 bytes transferred in 1.080 secs (9709037 bytes/sec)
Now you can exit adb shell and return to the command prompt, and do:

Code:
adb pull /data/local/tmp/recovery.img
And you should end up with the recovery image in your current folder.
 

Chainfire

Moderator Emeritus / Senior Recognized Developer -
Oct 2, 2007
11,428
87,629
263
www.chainfire.eu
Or... whatever cezeff just did is also good. Send me the recovery.img file and I'll look at it. I can confirm on my end if it's (likely to be) the right file.
 

cezeff

Senior Member
Sep 21, 2009
591
147
0
Okinawa, Japan
Or... whatever cezeff just did is also good. Send me the recovery.img file and I'll look at it. I can confirm on my end if it's (likely to be) the right file.
i'm uploading it now through my google drive because its over the 8mb limit for .img on xda....

https://docs.google.com/file/d/0B06L494jdQAlRWhJVkRZdXRHdU0/edit?usp=sharing

theres more in the firmware like hidden.img and what not...im no where near a developer so dont know if anything extra is there too....im uploading the whole pulled firmware to my Drive to and will post the link in case you need anything else from it....itll just take a sec to finish uploading...

---------- Post added at 01:49 PM ---------- Previous post was at 01:45 PM ----------


It's odd that using the I9505 CFAR would result in a partial root ... really odd. This might mean there's something different in your firmware from the I9505, because really that should mostly just work. You shouldn't need to update the binary after CFAR, is it reporting SuperSU v1.30 ? Also, can somebody confirm this device is running BML like someone suggested in an earlier post ?

Anyways, on a fresh device (without custom recovery or CFAR applied), you'd need to root using an exploit like Motochopper or whatever, then open an ADB shell session, execute "su" to gain root privileges (prompt will change from $ to # ), then execute this command (copy/paste the command, you'll probably mess up trying to enter it manually):

Code:
ls -l /dev/block/platform/*/by-name/recovery
It'll output something like:

Code:
lrwxrwxrwx root     root              1970-01-24 23:27 recovery -> /dev/block/mmcblk0pXX
The /dev/block/mmcblk0pXX part is the important bit! Now execute this command in the adb shell session:

Code:
dd if =/dev/block/mmcblk0pXX of=/data/local/tmp/recovery.img bs=512
Obviously replacing the XX part with whatever the command above returned. It should output something like this:

Code:
20480+0 records in
20480+0 records out
10485760 bytes transferred in 1.080 secs (9709037 bytes/sec)
Now you can exit adb shell and return to the command prompt, and do:

Code:
adb pull /data/local/tmp/recovery.img
And you should end up with the recovery image in your current folder.
can some of you guys do it this way just in case I pulled something wrong?...

@Chainfire the Auto-Root flashed just fine, no glitches or anything....once phone booted you even had SU installed...but SU couldnt update binary and gain root permissions...tried several apps that require root ( i.e. LMT launcher, various file explores, CWM, etc) and all failed to gain root permissions..
@Chainfire ....here is everything else that I pulled besides the 2.5 gb system.img.ext4...i'll have to upload that one over night here....let me know if you need anything else..

https://drive.google.com/folderview?id=0B06L494jdQAlbWpfU2Z2Y2xtZVE&usp=sharing
 
Last edited:

cezeff

Senior Member
Sep 21, 2009
591
147
0
Okinawa, Japan
@Chainfire ...No dice...didn't install with the flash...went to market and tried to install SU and got this....also when the phone rebooted is it suppose to have "Recovery Rebooting" flash quickly on my boot screen?


@TonyC40 ...have you tried Chainfire's listed instructions to pull the recovery.img off your device, just in case?


Sent from my SC-04E using xda app-developers app
 

Attachments

Last edited:

Chainfire

Moderator Emeritus / Senior Recognized Developer -
Oct 2, 2007
11,428
87,629
263
www.chainfire.eu
@Chainfire ...No dice...didn't install with the flash...went to market and tried to install SU and got this....also when the phone rebooted is it suppose to have "Recovery Rebooting" flash quickly on my boot screen?


@TonyC40 ...have you tried Chainfire's listed instructions to pull the recovery.img off your device, just in case?


Sent from my SC-04E using xda app-developers app
Did you get the red Android and text on your screen when applying CFAR like usual, though ?

It almost seems like your firmware disables the su binaries at boot or something.
 

cezeff

Senior Member
Sep 21, 2009
591
147
0
Okinawa, Japan
Did you get the red Android and text on your screen when applying CFAR like usual, though ?

It almost seems like your firmware disables the su binaries at boot or something.
@Chainfire ...no red text or Andriod like it was the first time i used the i9505 version...unzipped the file you uploaded...popped in PDA on Odin...flashed fine, like 5 seconds, said "Successful"...phone rebooted...at the first part of the boot screen, tiny little blue words in the upper left saying :Recovery Booting"..then disappeared on the second part ( Docomo XI logo) and then phone just booted up fine, no problems or anything....just no SU....let me give it another try....
@Chainfire I follow the flash process....the phone reboots...at the NTT Docomo screen, upper left same words "Recovery Booting"...then the phone will reboot itself again...NTT Docomo splash screen pops up, no blue words, and a normal boot up follows....so after flashing the CFAR , the phone reboots with the blue words, then reboots itself again and boots into android with no problems
 
Last edited:

Chainfire

Moderator Emeritus / Senior Recognized Developer -
Oct 2, 2007
11,428
87,629
263
www.chainfire.eu
@Chainfire ...no red text or Andriod like it was the first time i used the i9505 version...unzipped the file you uploaded...popped in PDA on Odin...flashed fine, like 5 seconds, said "Successful"...phone rebooted...at the first part of the boot screen, tiny little blue words in the upper left saying :Recovery Rebooting"..then disappeared on the second part ( Docomo XI logo) and then phone just booted up fine, no problems or anything....just no SU....let me give it another try....
Right, something went wrong in that case. You need to see a big ass red Android icon and some text scrolling over the screen for +-15 seconds after flash ...

EDIT: Second and/or third tries any better ?
 
Last edited:

cezeff

Senior Member
Sep 21, 2009
591
147
0
Okinawa, Japan
Right, something went wrong in that case. You need to see a big ass red Android icon and some text scrolling over the screen for +-15 seconds after flash ...

EDIT: Second and/or third tries any better ?
no...same result....i seen the red Android with the patch and stuff when I used the i9505 version...but dont see it at all using this test version.....