yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] zerofighter1:
Alright, did some reading. From what I can tell, the Sprint GS3 will have limited connectivity at best. The reason being that the radios do not in fact support the same bandwidths.

Verizon's S3 supports:

LTE 750

CDMA 850 / 1900

GSM 850 / 900 / 1800 / 1900

Sprint's S3 supports:

LTE 1900

CDMA 800 / 850 / 1900

US Cellular version adds CDMA 1700, LTE 700/850/1700

Verizon operates on LTE at 750 (mhz?) only, so that's a definite no-go on the LTE. As far as the CMDA 850 matching up - you might get some connectivity, such as voice, maybe 1x data/3g data, but I don't really know enough about the topic to speak with any certainty.

Hope this helps.
[Verizon Samsung Galaxy S III] HypostaticOnion:
You can't anyway because Sprint and Verizon phones are locked because of cdma regulations or something like that.
[Verizon Samsung Galaxy S III] zerofighter1:
My Verizon Note 2 is unlocked factory. T mobile sim cards work fine, I've tested it, just no data because the bandwidths aren't supported by the radio.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
That's different. Note 2 is hardware unlocked so that you can switch to any carrier or use any rom worldwide thanks to your root method. Not the same for the GSIII. In Adam Outler's first Casual method for Note 2, he has a video explaining just how far unlocked the phone is and what you can flash since the hardware (as in the insides) is unchanged worldwide.
[Verizon Samsung Galaxy S III] zerofighter1:
Obviously. Not disputing that - in fact I was more or less observing it. He said that CDMA phones are locked or "something like that" . That statement could be misleading to some, indicating that ALL CDMA phones are locked due to "regulations", when I know for a fact they are not.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Ahh, I see now. Yea, I do agree with you there.
[Verizon Samsung Galaxy S III] HypostaticOnion:
They're locked in a way that makes it to where you cannot switch to Sprint if you're using a Verizon phone and voice versa. So they are in fact locked. Not gsm locked though. Cdma phones are locked. Our phones are gsm capable.
[Verizon Samsung Galaxy S III] zerofighter1:
Can you cite this information?
[Xperia Arc Q&A, Help & Troubleshooting] Artemicion:
Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".

Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks
[Xperia Arc Q&A, Help & Troubleshooting] popthosegaskets:
Yes, if you wipe the system partition there will be no more CWM. For CM10, you need to flash a custom kernel for it to work. This custom kernel will usually come with a CWM recovery so it will not be wiped when you flash a new ROM.

僕のLT18iから送られてきた
[Xperia Arc Q&A, Help & Troubleshooting] Artemicion:
Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?
[Xperia Arc Q&A, Help & Troubleshooting] Sahaab:
Is your bootloader unlocked?

And yes you will have to flash GB ftf using flashtool

Sent from my LT18i
[Xperia Arc Q&A, Help & Troubleshooting] Artemicion:
Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.

So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks
[Xperia Arc Q&A, Help & Troubleshooting] popthosegaskets:
If I am not mistaken the kernel boot img should be inside the ROM zip. Check the ROM zip. Just flash the boot img using fastboot, boot into CWM recovery and flash ROM & gapps.

僕のLT18iから送られてきた
[Xperia Arc Q&A, Help & Troubleshooting] Artemicion:
Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:

fastboot -i 0xfce flash boot boot.img

doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks
[Xperia Arc Q&A, Help & Troubleshooting] tangosierra_:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
[Xperia Arc Q&A, Help & Troubleshooting] popthosegaskets:
You don't need to add -i 0xfce to the command. Just type fastboot flash boot <name of boot image>.img

僕のLT18iから送られてきた
[Xperia Arc Q&A, Help & Troubleshooting] Artemicion:
Thanks, I'll give that a go, not going to be able to try for a few days now, but will. FYI, I took the line of code I was trying directly from the Cyanogenmod wiki for Anzu
[Xperia Arc Q&A, Help & Troubleshooting] Artemicion:
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"

I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks
[Xperia Arc Q&A, Help & Troubleshooting] popthosegaskets:
What is the name of the .img file? It can't have any spaces inside.

僕のLT18iから送られてきた
[Xperia Arc Q&A, Help & Troubleshooting] Artemicion:
Looks to just be "boot.img" to me, no spaces or anything.
[Xperia Arc Q&A, Help & Troubleshooting] tangosierra_:
Have you tried flashtool?
[Xperia Arc Q&A, Help & Troubleshooting] Artemicion:
No, guess I'll try that next. As I remember, that's what I used to flash in order to root it ages ago. Thanks
[T-Mobile Samsung Galaxy Note II] oslek:
hi.. guys... i need a new lcd for the note 2 t-mobile version.... you think if i buy a lcd n7105 version, it will work in my note?

ebay link where im gonna buy the lcd....

http://www.ebay.com/itm/Brand-New-N...e_Replacement_Parts_Tools&hash=item4ac6ab1211

apparently the lcd doesnt has a frame installed...
[Galaxy S 4 Q&A, Help & Troubleshooting] bscotth:
**Update**

ivanoterra and myself have both used CF-Auto Root on our GE S4's and we both can confirm that it has worked.

this is the file we used: http://download.chainfire.eu/316/CF-Root/CF-Auto-Root/CF-Auto-Root-jflte-jfltexx-gti9505.zip

**update 2**

More good news, I flashed TWRP using Odin and it worked! TWRP found here: http://www.teamw.in/project/twrp2/182

**OP below **

Hi folks,

Just got my GE S4 this morning. So far it's awesome. The only problem is that I'm so eager to root this phone and I cannot find any information on how to do it. Any ideas? I'm doubting it's as simple as just using the same method as the regular S4's, but I could easily be wrong.

Also, any information on whether there will be a sub-forum for the GE phones?

Thanks!
[Galaxy S 4 Q&A, Help & Troubleshooting] ivanoterra:
Same here

Im on the same road...
[Galaxy S 4 Q&A, Help & Troubleshooting] tublah:
What happens when you put the device in download mode? (Volume Down + Home + Power buttons on start up)
[Galaxy S 4 Q&A, Help & Troubleshooting] bscotth:
Attached is a picture of the download mode screen.

The text in the top left corner says:

ODIN MODE

PRODUCT NAME: GT-I9505G

CURRENT BINARY: Samsung Official

CSB-CONFIG-LSB: 0x30

WRITE PROTECTION: Enable
[Galaxy S 4 Q&A, Help & Troubleshooting] ivanoterra:
Did you try Auto Root ? Im getting close to trying it....

Just did a Auto Root... IT WORKED...

:D

I used this one http://xdaforums.com/showthread.php?t=2219803

The app asked for root and i was able to allow it... :D
[Galaxy S 4 Q&A, Help & Troubleshooting] tublah:
I think we'll have to wait for a custom recovery before we can root, methinks.

If you're feeling saucy, you can try 'fastboot oem unlock' and see what that does? (Warning: it may wipe your device, it does for my nexus 10)

EDIT: Looks like auto-root does fastboot oem unlock if you're not unlocked.
[Galaxy S 4 Q&A, Help & Troubleshooting] bscotth:
which version did you use? The T-Mobile one or the international one?
[Galaxy S 4 Q&A, Help & Troubleshooting] ivanoterra:
This

http://download.chainfire.eu/316/CF-Root/CF-Auto-Root/CF-Auto-Root-jflte-jfltexx-gti9505.zip

This one....
[Galaxy S 4 Q&A, Help & Troubleshooting] tublah:
Sweet! What happens when you go into download mode now? Does it show custom binary counter, or does it still show official?
[Galaxy S 4 Q&A, Help & Troubleshooting] bscotth:
Thanks! Here goes nothing...:D
[Galaxy S 4 Q&A, Help & Troubleshooting] ivanoterra:
Ill try that in a moment... Its recovering my apps... Its like 250 apps.. Its on 32%...

But i guess it wont show as custom, GE edition has a Unlocked Bootloader. It was made to be custom rom friendly....

Even if it counts... It wont matter... Probably a counter reseter will solve it...
[Galaxy S 4 Q&A, Help & Troubleshooting] bscotth:
Didn't work.

"Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
[Galaxy S 4 Q&A, Help & Troubleshooting] tublah:
That was going to be my next question - whether Triangle Away works - again, it should, since this is supposed to be identical to GT-i9505...

Sorry for all the Q's. I'm waiting on my device to ship.
[Galaxy S 4 Q&A, Help & Troubleshooting] ivanoterra:
Nooooo... You dont know how to flash ?

read the instructions there:

- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)

- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one

- (USB) Disconnect your phone from your computer

- Start Odin3-vX.X.exe

- Click the PDA button, and select CF-Auto-Root-....tar.md5

- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)

- (USB) Connect the phone to your computer

- Make sure Repartition is NOT checked

- Click the Start button

- Wait for Android to boot

- Done (if it took you more than 30 seconds, you need practise!)

(KILL ALL KIES PROCESSES... Before proceding...)

---------- Post added at 09:16 PM ---------- Previous post was at 09:15 PM ----------

Its ok... but im not sure about all of that... 70%... just 30% more :D
[Galaxy S 4 Q&A, Help & Troubleshooting] bscotth:
I know how. I've done it many times before this. While flashing, odin crashed. :crying:
[Galaxy S 4 Q&A, Help & Troubleshooting] Piero88:
Is it possible to flash the GE firmware on the international version? If yes does anyone have a guide?
[Galaxy S 4 Q&A, Help & Troubleshooting] bscotth:
Okay, it worked. Thought my phone was bricked. I used a different version of Odin and it stopped crashing and worked.

I can now confirm that Auto Root works on the GE S4!
[Galaxy S 4 Q&A, Help & Troubleshooting] bscotth:
Download mode shows that I'm on a custom binary now. It still says "Write Protection: Enable"

I'm curious to find out what that means. The bootloader is already unlocked. I wonder if a certain partition is locked.

I guess the next question to answer is: Can we use the same recoveries as the i9505? I hope so..
[Galaxy S 4 Q&A, Help & Troubleshooting] tublah:
Would you be willing to try out Triangle Away to see if it'll reset the custom binary counter? I also wonder if you do fastboot oem unlock if it'll turn off write protection?
[Galaxy S 4 Q&A, Help & Troubleshooting] bscotth:
I might be wrong but I don't think download mode supports fastboot. Either that, or I'm doing something wrong. With my phone in download mode and my S4 connected, the command "fastboot devices" doesn't show any devices, but when I plug my N4 in, it shows up. Is there a special fastboot mode that is different from download mode?
[Galaxy S 4 Q&A, Help & Troubleshooting] tublah:
maybe from root in adb try adb reboot bootloader? I'm not sure! :)
[Galaxy S 4 Q&A, Help & Troubleshooting] ivanoterra:
Same here... It show Custom and write protection enabled
[Galaxy S 4 Q&A, Help & Troubleshooting] pinoy929:
How easy is this? I mean, is there an initial set up? I just got the phone, but I've rooted my Nexus S and SGS2 before and it required Odin setup first.

How does this method work? Just go into Bootloader?
[Galaxy S 4 Q&A, Help & Troubleshooting] ivanoterra:
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)

- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one

- (USB) Disconnect your phone from your computer

- Start Odin3-vX.X.exe

- Click the PDA button, and select CF-Auto-Root-....tar.md5

- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)

- (USB) Connect the phone to your computer

- Make sure Repartition is NOT checked

- Click the Start button

- Wait for Android to boot

- Done (if it took you more than 30 seconds, you need practise!)

(KILL ALL KIES PROCESSES... Before proceding...)

Get the CF-Auto-Root link on old posts...
[Galaxy S 4 Q&A, Help & Troubleshooting] bscotth:
Recoveries are good! I just flashed TWRP and it worked. making a backup now!

TWRP here http://www.teamw.in/project/twrp2/182
[Galaxy S 4 Q&A, Help & Troubleshooting] ivanoterra:
Its the same as doing backup with Titanium Backup ? For exemple...
[Galaxy S 4 Q&A, Help & Troubleshooting] tublah:
Did you use the tar in odin method?
[Galaxy S 4 Q&A, Help & Troubleshooting] bscotth:
Yes, I put the .tar inside the PDA slot inside Odin 3
[Galaxy S 4 Q&A, Help & Troubleshooting] ack154:
Anyone know of an ODIN flashable dump of the stock I9505G available yet?

Long story very short, Auto-Root also worked for me, soft-bricked trying to get CWM Recovery. Flashed 4.3 ROM in ODIN to get back to a working state. Would really rather just go back to the stock 4.2.
[Galaxy S 4 Q&A, Help & Troubleshooting] beaver2233:
may I ask what firmware (build number) came with your I9505G? the leaked system dump was MFD.
[Galaxy S 4 Q&A, Help & Troubleshooting] donovanbrock:
Yah.. looking for a ODIN flashable system dump as well. Got jumpy and softbricked assuming it was = i9505 system layout. I think the partitions are a little different. CWM and TWRP both flash, but internal sd doesn't mount in either and any ROM softbricks (wont boot).
[Galaxy S 4 Q&A, Help & Troubleshooting] tublah:
Maybe try putting it in download mode and try the latest build of Kies?
[Galaxy S 4 Q&A, Help & Troubleshooting] beaver2233:
well that sucks! I thought they would've updated it since then, haha thanks.
[Galaxy S 4 Q&A, Help & Troubleshooting] donovanbrock:
No dice... Kies doesn't recognize model number GT-I9505G (it does GT-I9505 though)
[Galaxy S 4 Q&A, Help & Troubleshooting] tublah:
Might try slumming it for a while and run it as GT-I9505 - just flash the system (no modem, no bootloader) partition? *shrug* I'm kinda hoping that I can go between a touchwiz ROM and the pure google ROM.
[Galaxy S 4 Q&A, Help & Troubleshooting] ivanoterra:
How do you take printscreens ?
[Galaxy S 4 Q&A, Help & Troubleshooting] pinoy929:
Is the method for carrier specific models the same for the Google Edition? I have the GE version.

I have anxieties now about doing this because I bricked my sgs2 using the international method for my carrier specific model.
[Galaxy S 4 Q&A, Help & Troubleshooting] TakuyaZ:
Vol down + power
[Galaxy S 4 Q&A, Help & Troubleshooting] pinoy929:
Sounds like this i the method for TWRP, but I have the GE edition. Is it basically the same thing? Even with the same CF Auto Root zip files?
[Galaxy S 4 Q&A, Help & Troubleshooting] ivanoterra:
This is a i9505g Google Edition topic :P

All we are talking here, is about the GE edition :D

lol ;D
[Galaxy S 4 Q&A, Help & Troubleshooting] pinoy929:
Sorry! Anxiety.

UPDATE:

Can't believe how easy that was, lol. Thanks for not setting me on fire :).
[Galaxy S 4 Q&A, Help & Troubleshooting] ivanoterra:
Yeah, me neither... I thought it would take so much more...
[Galaxy S 4 Q&A, Help & Troubleshooting] Mohammad_Adib:
Crap, so my GE s4 doesnt boot.

I rooted it using CF Auto Root

I then downloaded a bunch of recoveries (CWM, TWRP, Philz Touch)

The recoveries didnt work (can't find /data), since the GE has different partitions.

So right now, Im downloading a i9505 stock image and flashing that to see how it goes.

Anyone have other recomendations or can get me a Odin flashable stock image of the i9505G?
[Galaxy S 4 Q&A, Help & Troubleshooting] donovanbrock:
A position quite a few of us are in. A ODIN image of the i9505G would be great. or else someone else thats at least been able to ODIN down to a I9505 install.
[Galaxy S 4 Q&A, Help & Troubleshooting] NPS_CA:
Rooted mine quickly

My quick steps to root an ACTUAL I9505G (real Google Edition Device).... sorry I don't use the Windows tools for this - on a mac or Linux system

NOTE: since recoveries can't read current partition FOLLOW EXACT STEPS TO GET TO WHERE I AM!! NOT RESPONSIBLE FOR NOT FOLLOWING STEPS BELOW!

1. Bootup device, skip setup or do minimal setup - NOTE: step 8 will wipe phone ; so don't go nuts yet on config/installing apps

2. Go to Settings, About Phone

3. Tap Build Number 7 times, go back to Main Settings Menu and under now shown Developer Options enable USB debugging

4. Plug into Mac or PC with pre-existing ADB and FASTBOOT (using same setup I had on N4 with the binaries from last Android SDK)

5. Accept footprint signature popup - if it DOESN'T appear unplug/replug USB cable

6. Under Command Prompt or Terminal on PC/Mac enter adb devices <enter>. Ensure it shows the device and doesn't show "Offline" - if it does repeat step 5

7. under Command Prompt or Terminal enter :adb reboot bootloader <enter>

8. Once in bootloader, do on your PC/Mac Command Prompt or Terminal: fastboot oem unlock <enter>

9. Accept unlock using Volume key then confirm with power button - device will reboot possibly a few times, once rebooted and in device you can sign into accounts - REPEAT step 2-3 also!!

10. Download and keep handy on your PC/Mac SuperSU .ZIP file from this thread: http://xdaforums.com/showthread.php?t=1538053

11. Download i9505 recovery from: http://www.clockworkmod.com/rommanager {I used Touch one}

12. Repeat Steps 6-7 while plugged into USB on the PC/Mac

13. Once in bootloader enter on your PC/Mac Command Prompt or Terminal: fastboot boot recovery-clockwork-touch-6.0.3.3-jfltexx.img <enter> (change recovery filename to whatever may be newer/updated/different - ensure fastboot is in path and you are in the directory the .IMG file is on or .IMG file is in same directory as fastboot)

NOTE: I don't replace the bootloader I just always do a fastboot boot into a temp recovery - suggest the same until a FULLY tested known recovery is available

14. Once in bootloader take note... touch wasn't working for me, had to use vol +/- and power button to select as needed - that recovery ALSO doesn't mount /sdcard or external SD (don't know if kernel diff / hw layout diff or what)...

15. Select with Vol keys Install ZIP (use pwr to confirm)

16. Select Install ZIP from Sideload

17. On plugged in PC/Mac Command Prompt or Terminal ensure the SuperSU zip downloaded in step 10 is in the path or same directory as adb and enter: adb sideload UPDATE-SuperSU-v1.41.zip <enter> (change filename to reflect a different/newer version)

18. Will do the install, select ++++ GO Back ++++ on the menus when done and then select Reboot System Now

On reboot you will be unlocked on bootloader + rooted.
[Galaxy S 4 Q&A, Help & Troubleshooting] tublah:
Interesting. So now when you go into download mode, does it show write protect disabled?
[Galaxy S 4 Q&A, Help & Troubleshooting] theclueless:
i used ODIN to flash the TWRP recovery then flash "[10.07][ROM]4.2.2 - S4 Google Edition v13 - Feel the Experience of Nexus" and "[Kernel][3.4.52][Google-Edition][V6][Stock][ExFat][Mtp]".

everything seems to be working so far
[Galaxy S 4 Q&A, Help & Troubleshooting] NPS_CA:
Shows it Enabled still; Though on my other S4 this showed up and i was using custom ROMs no issues was just using CWM recovery and not ODIN
[Galaxy S 4 Q&A, Help & Troubleshooting] jaredfaulkner:
WIth my GE edition: I used Odin 3.07 to flash openrecovery-twrp-2.6.0.0-jfltexx.tar from earlier in this thread, and proceeded to install SuperSU (UPDATE-SuperSU-v1.41.zip, also from above). The SuperSU ZIP had to be on an actual SD card; the recovery could not see the internal storage. Root was achieved and everything appears to be working as expected.
[Galaxy S 4 Q&A, Help & Troubleshooting] donovanbrock:
If you have an external SD card you can pop in, and you are in fact rooted if you connect to "adb shell" and you get root access.

Run these commands:

dd if=/dev/block/mmcblk0p16 of=/mnt/extSdCard/backup/mmcblk0p16_system.img bs=4096
dd if=/dev/block/mmcblk0p22 of=/mnt/extSdCard/backup/mmcblk0p22_recovery.img bs=4096
dd if=/dev/block/mmcblk0p21 of=/mnt/extSdCard/backup/mmcblk0p21_boot.img bs=4096

If you can successfully get those 3 files let me know. :good:
[Galaxy S 4 Q&A, Help & Troubleshooting] jaredfaulkner:
I was able to shell and achieved root, but the commands resulted in "cannot open for write: No such file or directory." I created the backup folder on the external SD card, and the errors no longer occured, but no files were created.
[Galaxy S 4 Q&A, Help & Troubleshooting] donovanbrock:
Can you post what the exact output is when you run the command? it should look something like:

shell@android:/ # dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/mmcblk0p14_system.img bs=4096
=/mnt/sdcard/mmcblk0p16_system.img bs=4096 <
512+0 records in
512+0 records out
2097152 bytes transferred in 0.156 secs (13443282 bytes/sec)
[Galaxy S 4 Q&A, Help & Troubleshooting] MichelN:
With the full dump we are able to convert the i9505 to i9505G right ?
[Galaxy S 4 Q&A, Help & Troubleshooting] ack154:
That's the theory...
[Galaxy S 4 Q&A, Help & Troubleshooting] donovanbrock:
I'm not 100% sure. The PIT files are different. There is one partition difference. ***IN THEORY*** you should be able to repartition to the I9505G partition table and flash. I don't have the balls to try. I'm just trying to get a system/boot/recovery dump to get a group of us back to stock after failed attempts to flash I9505 recovery and ROMs.
[Galaxy S 4 Q&A, Help & Troubleshooting] MichelN:
I am pretty sure Aerys will try it :cool:
[Galaxy S 4 Q&A, Help & Troubleshooting] jaredfaulkner:
I'm green, so I'll list the whole exchange:

C:\android-sdk-windows\platform-tools>adb shell
shell@android:/ $ su
su
root@android:/ # dd if=/dev/block/mmcblk0p16 of=/mnt/extSdCard/backup/mmcblk0p16_system.img bs=4096
/mnt/extSdCard/backup/mmcblk0p16_system.img bs=4096 <
[Galaxy S 4 Q&A, Help & Troubleshooting] donovanbrock:
Try giving this a shot... Changed the destination to go to internal sd storage. something i know works from a different rooted device.

dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/mmcblk0p16_system.img bs=4096
dd if=/dev/block/mmcblk0p21 of=/mnt/sdcard/mmcblk0p21_boot.img bs=4096
dd if=/dev/block/mmcblk0p22 of=/mnt/sdcard/mmcblk0p22_recovery.img bs=4096