Develop Bugs

Samsung Galaxy Gio GT-S5660M Discussion - Rooted Stock ROM, Partition Mapping

(Avis aux intéressés, j'ai traduit mon message en français, et reparti une discussion sur Frandroid.)
Hello,
I managed to map the partitions on the Gio 5660M (Bell Canada, 2.3.4, MUGK3) in order to extract an ODIN flashable complete stock backup.
I have also made a stock, rooted ROM backup by working in a hex editor. Other tools that helped the mapping were Winmerge, to do file comparisons with an Euro 5660 ROM, and Notepad++ for string searches.
Those with a 5660M that are experiencing issues after flashing Euro 5660 ROMs that have been posted here now have the possibility of flashing back their original radio and kernel.
ROM development and deployment is going to be safer going forward.
I copied the blocks with the dd command as follows:
dd if=/dev/block/bml1 of=/sdcard/bml1 bs=4096
WARNING!!! DO NOT dd /dev/block/stl5 as there have been multiple reports of bricking following reading it. We already know that this block contains the EFS partition, including the SIM-lock code. You can however dd bml5 without issue from a "live" phone. If you absolutely want stl5, you may get it by using a rooted custom recovery.
From what I've gathered bml is essentially a lower level interface to the same blocks accessed by stl, but the results differ somewhat in resulting file size.
Here are the results:
Code:
/dev/block/bml1 MIBIB
/dev/block/bml2 QCSBL
/dev/block/bml3 OEMSBL
/dev/block/bml4 AMSS
/dev/block/bml6 Essentially empty, with a FSR_STL string at the beginning.
/dev/block/bml7 arm11boot
/dev/block/bml8 boot.img. My initial assumption was based on the .ops file supplied with the Euro ROM I've done my comparisons with. This has since been confirmed with actual flashing.
/dev/block/bml9 recovery.img for the same reasons as above.
/dev/block/bml10 Essentially empty. Mine has a BMC string at the beginning which matches the CSC code on this phone, followed by an ON and an OFF.
/dev/block/bml11 Empty. \xFF all around.
/dev/block/bml12 Seems to contain the same RFS data as stl12, but with an additional 8 megs of data/padding, not readable by MagicISO.
/dev/block/bml13 Like 12 above, but user data
/dev/block/bml14 As above, but the almost empty partition
/dev/block/stl1 cannot open for read
/dev/block/stl2 cannot open for read
/dev/block/stl3 cannot open for read
/dev/block/stl4 cannot open for read
/dev/block/stl6 Empty: contains only \xFF
/dev/block/stl7 cannot open for read
/dev/block/stl8 cannot open for read
/dev/block/stl9 cannot open for read
/dev/block/stl10 cannot open for read
/dev/block/stl11 cannot open for read
/dev/block/stl12 system.rfs - is flashable as-is once tarballed. Also contains the CSC files as we're taking this from a "live" installation, contrary to an OEM provided image. (My image is also rooted for the same reason.)
/dev/block/stl13 data.rfs - User data partition
/dev/block/stl14 cache.rfs - Odin hangs when I try to flash it. Use CWM and dd back into place from the SD card.
From what I see we can't repartition our phones like the GT-I9000 guys do, so there are no PIT files to worry about. Only the OPS files which ODIN uses. We're not able to flash with Heimdall in its current configuration as it requires a PIT file.
GT-S5660M_MUGKG3_stock_rooted_ROM_v2.7z (101.46 MB)
Un7-Zip, flash tarball with Odin using the "One Package" option. Tested working on my phone. I think it goes without saying that flashing this is at your own risk.
(PDA: S5660MUGKG3 PHONE: S5660MUGKG3 CSC: S5660MBMCKG3)
Tutorial on flashing with Odin, with link for the appropriate version for our phone.
I've released my custom 5660M ROM, ArpegGioMod.
Goodbye,
Darkshado

Wow,
Thank you very much. The screen brightness issues and problems connecting to the mobile 3G network were very troublesome.
I will be flashing this ROM back to my s5660m.
THANK YOU!
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!

Cool! Please, pretty please let me know as soon as possible how it turns out. When do you plan on trying this? This afternoon or later tonight?
Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Good luck,
Darkshado

Coolty said:
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!
Click to expand...
Click to collapse
Great! You just made my day!
About the missing CSC file: CSC is an acronym for Carrier/Country Specific Code. The csc.rfs file is a partition image file that, as far as I can tell, is merged with the contents of the system.rfs partition. In our case, the CSC file would contain the APN settings, as well as the Bell proprietary apps like self-serve and remote PVR.
Instead, since I took the system partition from a live phone, the CSC content is already in the system.rfs partition. I think the idea behind this is that Samsung can release new CSC packages without having to update the whole firmware when "new" carriers add the phone to their lineup.
I'll see if I can edit the RFS partitions, (maybe by mounting them on the phone directly?) if so, I would be able to unroot, and make that separate CSC partition as well. That would make the backup completely stock, as if it came right from Samsung.
Another, simpler solution would be to modify the OPS file to skip the CSC partition.
One question: did you re-tar each file individually for ODIN to take them?
CM7 port: I'd love to have one on that phone as well, but I'm not in a position to tackle that project, yet. The good news is that since we now have a way to bring the phone back to stock, we can experiment safely.
Goodbye,
Darkshado

Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Click to expand...
Click to collapse
I will try this as well, will let you know the status of that as soon as I get to that. I am pretty confident with flashing phones by now
One question: did you re-tar each file individually for ODIN to take them?
Click to expand...
Click to collapse
No, I use linux so it was an easy process of copying the factory.rfs to my HDD, renaming it to system.rfs, deleting factory.rfs from TAR, and then adding system.rfs to the TAR file.
Let me know if you want me to try anything else, as I have access to linux and am pretty knowledgeable when it comes to things of that nature.

I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.

Step by Step guide for Noobs?
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.

red02 said:
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.
Click to expand...
Click to collapse
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?

Coolty said:
I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.
Click to expand...
Click to collapse
if you could post it, that would be much appreciated!!

steez003 said:
if you could post it, that would be much appreciated!!
Click to expand...
Click to collapse
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty

Coolty said:
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?
Click to expand...
Click to collapse
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.

red02 said:
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
Click to expand...
Click to collapse
Hi,
I'm not one for explaining things in great detail, but the basic breakdown of the things you need (google is your friend) are:
1) Odin_Multi_Downloader_v4.42
2) The USB drivers for your phone (Hint: Samsung Kies)
3) OPS File (for this phone, I recommend GIO_v1.0.OPS)
4) Either a single TAR file or multiple files (eg, appboot, PDA, etc) For the file I am uploading it will be a single TAR file which is a package that includes all the things needed.
Then, you just remove the battery in your phone, unplug it from USB or wall charger, put battery back in, hold vol down + HOME + power until you see a screen (you may have to press a vol key after that, read the screen to see if you need to) Your screen on the phone should say DOWNLOADING... This is when you:
1) connect phone to computer via USB after installing drivers (kies, usb driver)
2) make sure kies is closed
3) run ODIN
4) choose the proper OPS file
5) click single package
6) choose the TAR file you want to flash to your phone
That's it!
EDIT:
I am providing some forum links that may better explain how to do what you need done:
How to unbrick (for samsung ACE, but applies to the 5660m) http://forum.xda-developers.com/showthread.php?t=1071970
How to use ODIN to flash your phone: http://forum.xda-developers.com/showpost.php?p=16979859&postcount=549
And of course, the great bible of GIO 5660 links and information: http://forum.xda-developers.com/showthread.php?t=1209425

I have updated my previous post to include the download link to the fixed rom for use with the s5660m.
(search for "s5660m by coolty" on the forums to find it)

Coolty said:
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty
Click to expand...
Click to collapse
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks

Will this help at at all with a blank IMEI? I assume this would only help for people flashing back to stock firmware or recovering from a non-bootable or reboot loop phone?

steez003 said:
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Click to expand...
Click to collapse
I'm also running into the same issue
Sent from my Nexus S using XDA App

Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....

Waqasshazad: Maybe wiping the caches will help, but the issues might be due to running a 5660 on a 5660M as well. We know the kernels and modems aren't compatible, it may go a bit further. By the way, it's spelled factory.
MacrossFX: I've seen mentions of people dd'ing their stl5 partition into a file and then back on the phone, but I'm unsure this worked in the end. I'm afraid your only solution might involve a shipment to the service center...

ClockworkMod Recovery for the Samsung Galaxy Gio GT-S5660
http://forum.xda-developers.com/showpost.php?p=16980117&postcount=559
May be this can backup for you , too with s5660m , i have tested on Gt s5660 and it worked perfectly fine..

waqasshahzad1986 said:
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Click to expand...
Click to collapse
I followed your instructional video and did do a factory reset before and after. Maybe i'll try reflashing it again tonight and see what happens.

Would it be possible to root my sg2 USCC version of Epic4gtouch.

I was looking at the auto root for FB15 and was wanting to know if it would work for my phone, Android version: 2.3.6, Baseband: S:R760.01 K.FB14. Any help is greatly appreciated.
Sent from my SCH-R760 using Tapatalk

^^ Second this. Just got SCH-R760 (SGS II) from USCC, there is currently ZERO support. Thanks!

I've tried the ek02 autoroot three times and it's not able to push the files. SuperOneClick didn't work either.
Sent from my SCH-R760 using xda premium

themac79 said:
I was looking at the auto root for FB15 and was wanting to know if it would work for my phone, Android version: 2.3.6, Baseband: S:R760.01 K.FB14. Any help is greatly appreciated.
Sent from my SCH-R760 using Tapatalk
Click to expand...
Click to collapse
The fb15 on this phone is ics so not going to work on your GB ROM .....maybe steady Hawkin can make you a kernel to root it with Odin ....all you have to do is ask him he may do it
He may port cwm for you too don't hurt to ask
Sent from my SPH-D710 using xda premium

Epix4G said:
The fb15 on this phone is ics so not going to work on your GB ROM .....maybe steady Hawkin can make you a kernel to root it with Odin ....all you have to do is ask him he may do it
He may port cwm for you too don't hurt to ask
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
That would be great! Thanks for the advice, really appreciate it.

not working
from what I hear zergrush no longer works in 2.3.6. I tried manually installing but it fails on the USCC GS2 (SCH-R760)
[+] Found a GingerBread ! 0x00000118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !

mostly working
So I tried it with my SCH-R760 SGS2 I was able to get root boot recovery. Having the FB14 kernel would make this a snap however the Epic 4g Touch is so close it mostly worked. I seem to have intermittent wifi problems but everything else appears to work without issue.
I got the kernel from step two WISHLINK:wiki.rootzwiki.com/index.php/Samsung_Epic_4G_Touch or directly WISHLINK:goo-inside.me/epic4gtouch/kernel/acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar
I tried sweet talking USCC, evidently I'm not as charming as I think I am they told me I'm screwed and don't yet have the re-image. However, the above has the phone working and rooted minus a few problems with wifi.
Good luck.

Margey said:
So I tried it with my SCH-R760 SGS2 I was able to get root boot recovery. Having the FB14 kernel would make this a snap however the Epic 4g Touch is so close it mostly worked. I seem to have intermittent wifi problems but everything else appears to work without issue.
I got the kernel from step two WISHLINK:wiki.rootzwiki.com/index.php/Samsung_Epic_4G_Touch or directly WISHLINK:goo-inside.me/epic4gtouch/kernel/acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar
I tried sweet talking USCC, evidently I'm not as charming as I think I am they told me I'm screwed and don't yet have the re-image. However, the above has the phone working and rooted minus a few problems with wifi.
Good luck.
Click to expand...
Click to collapse
If you can get the E4GT kernel to boot on your phone then just use it to install su onto your ROM (/system), then put back your original USCC kernel and you'll be rooted with everything working.
So basically if your adb shell has a "#" prompt, you can just use Auto Root Option A on your phone and install root onto your phone's ROM. Just ignore the zergrush status, even though it fails, the script is still smart enough to install root onto your rom in your situation.
Then to get your original kernel back, figure out which partition has the recovery.bin, which is an unused mirror of your original kernel/zImage.
In the case of E4GT, this is partition /dev/block/mmcblk0p6
To get the mirror of your zImage type the following in adb shell
Code:
cd /sdcard
dd if=/dev/block/mmcblk0p6 of=zImage bs=256 count=32765
Now it is very important that the partition you chose above is really the recovery.bin partition, otherwise the file you just created will essentially be junk and won't allow you to boot your phone (ie *IF* you installed it, your phone *would not boot*)
Assuming you had the correct partition, to install it as your running kernel, you can do
Code:
cd /sdcard
dd if=zImage of=/dev/block/mmcblk0p5 bs=256 count=32765
Please don't go jumping into this unless you fully understand what I suggested.
YOU CAN MAKE YOUR PHONE UNBOOTABLE IF YOU DO THINGS WRONG.
I don't have your phone and the partitions could be different, so I'm depending on you to figure out if things don't make sense.
If you are unsure, ask questions before doing anything.

While I'm just understanding partitions and the like I'm able to follow your instructions but the *IF* parts I'd like to question.
I have:
/dev/block/mmcblk0p6
and
/dev/block/mmcblk0p5
I'm not sure how this correlates to the recovery.bin unless it is apart of one of those files. So for the SCH-R760 with FB14 I'd be looking for how to verify this. I can easily run the suggested lines and looks like everything is there. However to get this far it's been several hours and I'm a bit gun shy as I have to work tomorrow and actually need my phone. Again thank you for the suggestions and help. I'm very close. Everything but wifi is working and very well.

did anyone try flashing the cwm from the touch. it should work because the mount points line up the same. if so i can finish the ics rom and give it to who ever is willing to try
---------- Post added at 09:13 PM ---------- Previous post was at 08:56 PM ----------
sfhub said:
If you can get the E4GT kernel to boot on your phone then just use it to install su onto your ROM (/system), then put back your original USCC kernel and you'll be rooted with everything working.
So basically if your adb shell has a "#" prompt, you can just use Auto Root Option A on your phone and install root onto your phone's ROM. Just ignore the zergrush status, even though it fails, the script is still smart enough to install root onto your rom in your situation.
Then to get your original kernel back, figure out which partition has the recovery.bin, which is an unused mirror of your original kernel/zImage.
In the case of E4GT, this is partition /dev/block/mmcblk0p6
To get the mirror of your zImage type the following in adb shell
Code:
cd /sdcard
dd if=/dev/block/mmcblk0p6 of=zImage bs=256 count=32765
Now it is very important that the partition you chose above is really the recovery.bin partition, otherwise the file you just created will essentially be junk and won't allow you to boot your phone (ie *IF* you installed it, your phone *would not boot*)
Assuming you had the correct partition, to install it as your running kernel, you can do
Code:
cd /sdcard
dd if=zImage of=/dev/block/mmcblk0p5 bs=256 count=32765
Please don't go jumping into this unless you fully understand what I suggested.
YOU CAN MAKE YOUR PHONE UNBOOTABLE IF YOU DO THINGS WRONG.
I don't have your phone and the partitions could be different, so I'm depending on you to figure out if things don't make sense.
If you are unsure, ask questions before doing anything.
Click to expand...
Click to collapse
Here is a mount print out of the sgs2 from uscc that i had someone give me.
http://pastebin.com/k0nXEcKt
---------- Post added at 09:19 PM ---------- Previous post was at 09:13 PM ----------
Can't they just odin flash or heimdall flash the kernel/recovery in, that would be easier, then they truly don't have to root the rom first.

ironfisted said:
Can't they just odin flash or heimdall flash the kernel/recovery in, that would be easier, then they truly don't have to root the rom first.
Click to expand...
Click to collapse
They already did that. That is why they have rooted adb through the kernel. The issue is they are using an Epic 4G Touch kernel which causes some things to not work on their phone. I am suggesting they install their root functionality in the ROM and restore their original USCC kernel/zImage.
Since (according to them) they don't have a package to return to stock, basically they don't have a kernel/zImage to flash in ODIN because it was never provided to them.
Their original kernel/zImage is gone because they flashed over it (presumably before backing it up). That is why I gave them instructions to pull the backup kernel/zImage. Once they do that, whether they install that zImage within Android or through ODIN is not really important. The important part is they get the correct partition to use to pull the backup from so that they have a valid kernel/zImage to flash.
---------- Post added at 09:55 PM ---------- Previous post was at 09:42 PM ----------
Margey said:
While I'm just understanding partitions and the like I'm able to follow your instructions but the *IF* parts I'd like to question.
I have:
/dev/block/mmcblk0p6
and
/dev/block/mmcblk0p5
I'm not sure how this correlates to the recovery.bin unless it is apart of one of those files. So for the SCH-R760 with FB14 I'd be looking for how to verify this. I can easily run the suggested lines and looks like everything is there. However to get this far it's been several hours and I'm a bit gun shy as I have to work tomorrow and actually need my phone. Again thank you for the suggestions and help. I'm very close. Everything but wifi is working and very well.
Click to expand...
Click to collapse
Based on the previous pastebin that was posted it looks like the partitions on the USCC GS2 line up with the Sprint E4GT so it should be safe to run what I suggested.
Both /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6 are linux device files that map to partitions in your phone's EMMC memory.
mmcblk0p5 is labeled zImage (on Sprint) and mmcblk0p6 is labeled recovery.bin (on Sprint). They have the exact same contents. zImage is the kernel and recovery for your phone.
recovery.bin is not being used (on Sprint) so it basically ends up being a backup of your zImage/kernel. Since you overwrote your USCC zImage with the Sprint E4GT zImage (presumably before backing it up) you cannot recover the original from your phone using the partition assigned to zImage.
I am suggesting you retrieve your original zImage from what is essentially a backup in the partition labeled recovery.bin (mmcblk0p6). This can then be installed in your zImage partition (mmcblk0p5) either directly through Android or through ODIN.
Once you create the zImage file as above, keep a copy off your phone on your PC just in case.
The whole purpose of putting back your original USCC zImage/kernel is so all the features work again, but since your root was achieved through the kernel, putting back the original zImage/kernel would cause you to lose root. That is why I suggested, prior to putting back the original USCC kernel, you install persistent root inside your ROM (ie /system)
You can do that by running Auto Root - Option A and ignoring the Blue Hellions error. If your adb is rooted as you described above, Auto Root will still install persistent root in your ROM despite the failure of the zergrush exploit. Once you install the persistent root in your ROM, you can restore the original USCC kernel/zImage and still have root for your applications. You can confirm that Auto Root - Option A did its job by typing:
Code:
ls -l /system/xbin/su
and verifying su is there and it has the proper permissions. If you are unsure, post the output and I can confirm.

What didn't work? maybe its a matter of the rom difference that makes stuff not work. Just an idea. I was thinking of porting the ics rom over to the sgs2 for them.

ironfisted said:
What didn't work? maybe its a matter of the rom difference that makes stuff not work. Just an idea. I was thinking of porting the ics rom over to the sgs2 for them.
Click to expand...
Click to collapse
As mentioned by Margey's post, the wifi wasn't working well. wifi drivers are in the kernel. Margey installed just the kernel/recovery, not the ROM.

sfhub said:
As mentioned by Margey's post, the wifi wasn't working well. wifi drivers are in the kernel.
Click to expand...
Click to collapse
hmmm, so ics is still doable then. hmmmmmm

I just wanted to thank everyone for their help it is very much appreciated. I'm going to try what sfhub posted. I still have my stock kernel since I've been working and haven't had time to do anything. I will try and make a copy of my stock kernel. Can I push superuser into my rom using adb or do I need to flash the Epic 4G's kernel then push superuser and then flash my stock kernel back.
Sent from my SCH-R760 using xda premium

eureka
sfhub said:
They already did that. That is why they have rooted adb through the kernel. The issue is they are using an Epic 4G Touch kernel which causes some things to not work on their phone. I am suggesting they install their root functionality in the ROM and restore their original USCC kernel/zImage.
Since (according to them) they don't have a package to return to stock, basically they don't have a kernel/zImage to flash in ODIN because it was never provided to them.
Their original kernel/zImage is gone because they flashed over it (presumably before backing it up). That is why I gave them instructions to pull the backup kernel/zImage. Once they do that, whether they install that zImage within Android or through ODIN is not really important. The important part is they get the correct partition to use to pull the backup from so that they have a valid kernel/zImage to flash.
---------- Post added at 09:55 PM ---------- Previous post was at 09:42 PM ----------
Based on the previous pastebin that was posted it looks like the partitions on the USCC GS2 line up with the Sprint E4GT so it should be safe to run what I suggested.
Both /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6 are linux device files that map to partitions in your phone's EMMC memory.
mmcblk0p5 is labeled zImage (on Sprint) and mmcblk0p6 is labeled recovery.bin (on Sprint). They have the exact same contents. zImage is the kernel and recovery for your phone.
recovery.bin is not being used (on Sprint) so it basically ends up being a backup of your zImage/kernel. Since you overwrote your USCC zImage with the Sprint E4GT zImage (presumably before backing it up) you cannot recover the original from your phone using the partition assigned to zImage.
I am suggesting you retrieve your original zImage from what is essentially a backup in the partition labeled recovery.bin (mmcblk0p6). This can then be installed in your zImage partition (mmcblk0p5) either directly through Android or through ODIN.
Once you create the zImage file as above, keep a copy off your phone on your PC just in case.
The whole purpose of putting back your original USCC zImage/kernel is so all the features work again, but since your root was achieved through the kernel, putting back the original zImage/kernel would cause you to lose root. That is why I suggested, prior to putting back the original USCC kernel, you install persistent root inside your ROM (ie /system)
You can do that by running Auto Root - Option A and ignoring the Blue Hellions error. If your adb is rooted as you described above, Auto Root will still install persistent root in your ROM despite the failure of the zergrush exploit. Once you install the persistent root in your ROM, you can restore the original USCC kernel/zImage and still have root for your applications. You can confirm that Auto Root - Option A did its job by typing:
Code:
ls -l /system/xbin/su
and verifying su is there and it has the proper permissions. If you are unsure, post the output and I can confirm.
Click to expand...
Click to collapse
I doubled checked su, good. Re-ran the image per your suggestion, all good. I have wifi, I have 3G, I have phone and I have root and CWM.
Thank you.

I have been trying to use the auto-root method after installing the recovery kernel and it keeps saying waiting for device to connect? How can I get it to see my device?

themac79 said:
I have been trying to use the auto-root method after installing the recovery kernel and it keeps saying waiting for device to connect? How can I get it to see my device?
Click to expand...
Click to collapse
You can actually just copy the files to your sdcard and run the script by hand, but the specific reason it is waiting for your phone is because ADB cannot see your phone.
That might be because you haven't enabled USB debugging. It might be because of driver problem. It could be because your ##8778# setting is incorrect.
Have you ever been able to use "adb" with your phone?

sfhub said:
You can actually just copy the files to your sdcard and run the script by hand, but the specific reason it is waiting for your phone is because ADB cannot see your phone.
That might be because you haven't enabled USB debugging. It might be because of driver problem. It could be because your ##8778# setting is incorrect.
Have you ever been able to use "adb" with your phone?
Click to expand...
Click to collapse
I finally got it, the problem was I was missing a driver for my phone. Now I'm trying to make a copy of my stock kernel using your instructions but for some reason when I type cd /sdcard it says it can't find the path specified. It shows my device listed, I don't know what I'm doing wrong? Wait..do you mean to use my phone to make a copy?

themac79 said:
I finally got it, the problem was I was missing a driver for my phone. Now I'm trying to make a copy of my stock kernel using your instructions but for some reason when I type cd /sdcard it says it can't find the path specified. It shows my device listed, I don't know what I'm doing wrong?
Click to expand...
Click to collapse
Are you doing that from an "adb shell"?
You can replace with "cd /data/local/tmp", it can really be any directory where you have write permissions.
If you want to be more bold, you can skip the step of creating a zImage file and write directly from the recovery.bin partition into the zImage partition. The zImage file is nice because if you screw things up and your phone won't boot, you can still use ODIN to flash the zImage (assuming you moved it to your PC)
Code:
dd if=/dev/block/mmcblk0p6 of=/dev/block/mmcblk0p5 bs=256 count=32765

[Q] Rooting with Linux (No ODIN/Windows is Not an Option)

I'm looking to root my Sprint SGS3 using a Linux machine.
Note: I do not own nor do have access to a Windows machine so don't even suggest I use ODIN in a Windows virtual machine or otherwise.
I've done plenty of searching on this and other forums over the last month but most of what I find suggest using ODIN, however, this is not an option for the above started reason. In addition, the shear number of search results is making it difficult to find the needle in the haystack.
Also, I read the posts in the Sprint SGS3 XDA forums that mention Heimdall but they don't actually explain how to root the Sprint SGS3. All the Heimdall threads I've found only describe what it is capable of. Even Glass Echidna's site only describes what it is capable of but not the steps required to root a phone.
I've also found the post with links to the Heimdall Flasher or other toolkits that either mention basic steps but don't explain what each step does or the toolkit is a Windows executable.
I tried to flash twrp recovery with Heimdall and it appeared to work, however, it tripped the flash counter and either didn't actually flash or it was overwritten because I booted into recovery and still had the stock recovery.
The "[HOWTO][ROOT] Forget about Odin and Heimdall also does not increase counter" post doesn't work anymore. Any attempt to perform an operation on "/data/local/" now fails with "permission denied" thereby thwarting any attempt to root the devices with this method.
Why can't I just root my Sprint SGS3 with adb and fastboot. I was able to root my Motorola XOOM with adb and fastboot so why can't I on a SGS3?
So, with all that said, what I'm looking for is written instructions on flashing in Linux without using a toolkit that does everything for me. I want to actually understand what is going on. Also, I'd prefer not to sit through watching several youtube videos.

Have you seen this thread? I haven't tried it, so I can't vouch for it in any way, but it is stock, rooted lj7 using heimdall. I used heimdall a lot on my captivate and it was a rock solid program, much better than odin in my opinion.
Anyway, It's an old thread, not sure how much support you'll get. Good luck!
http://forum.xda-developers.com/showthread.php?p=34631785
Sent from my SPH-L710 using xda app-developers app

laihafloyd said:
Have you seen this thread? ...
Click to expand...
Click to collapse
Yup, saw it and tried it. Doesn't work running as a normal user.
The package from the post is able to detect when my phone is placed in download mode, however, after clicking the "flash" button, it hangs at 'Detecting device...' I can't remember if I tried running the package as root but it shouldn't be required. When I tried flashing twrp with heimdall before finding the thread you mention, I didn't have to run as root.
Besides, the download in the thread falls into the category of a toolkit and hides everything behind the curtain, which means I'll never understand what is going on.
Thanks anyway.
Edit:
OK, there is a button in the toolkit to show details of the flashing process and, when viewing it, I saw 'Detecting device...ERROR: Failed to access device. libusb error: -3'. So in my case it does need to be run as root because I do not have the udev rules that set the permissions properly for the device file.
Alas, it still fails as root with:
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Re-attaching kernel driver...ERROR: Failed to initialise protocol!
Click to expand...
Click to collapse
Edit Again:
OK, I let the toolkit download and install heimdall (version 1.3.1) with the previous run.
However, I ran the toolkit again but instead of letting it download and install heimdall I had it run heimdall 1.4 RC1 that I downloaded and compiled from source prior to this post.
With this run, the toolkit is actually uploading to my phone now.
Looks like I might be able to root my phone with this toolkit but it still doesn't help me understand how to root a SGS3 step-by-step.
Update:
It worked.
For those who are worried about what they should see inside the main toolkit window while flashing, here is the output of my run:
Operating System: Debian Based x86_64
Found Heimdall Version: Heimdall version is out of date.
Connect your device in Download Mode to procede.
Device Connected. Awaiting package preparation.
Stock Rooted+recovery! L710VPBLJ7 is ready for your device.
Repartition was requested but bootloaders are not to be flashed.
MODEM SBL1 SBL2 SBL3 ABOOT RPM BOOT TZ SYSTEM PERSIST CACHE RECOVERY
Heimdall v1.4 RC1
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
[SNIP - cannot post links]
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
[SNIP - cannot post links]
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Session begun.
In certain situations this device may take up to 2 minutes to respond.
Please be patient!
Downloading device's PIT file...
PIT file download successful.
Uploading MODEM
MODEM upload successful
Uploading SYSTEM
SYSTEM upload successful
Uploading PERSIST
PERSIST upload successful
Uploading CACHE
CACHE upload successful
Uploading RECOVERY
RECOVERY upload successful
Uploading SBL1
SBL1 upload successful
Uploading SBL2
SBL2 upload successful
Uploading SBL3
SBL3 upload successful
Uploading ABOOT
ABOOT upload successful
Uploading RPM
RPM upload successful
Uploading BOOT
BOOT upload successful
Uploading TZ
TZ upload successful
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Click to expand...
Click to collapse

[Q] Is it possible to root Tab 3 10.1 P5220? [SOLVED]

I just picked this up and it's build number P5220XXUAMI2 out of the box.
I'm a little confused regarding firmware versions and I've found a few threads for the P5200 and P5210 builds, but nothing for the P5220. Is it possible to root and flash a custom recovery on the model/build I have?
Sorry of this is a super n00b question. Tablets are not my strong point.
EDIT:
I was able to root using the method here
http://forum.xda-developers.com/showthread.php?t=2432467
I wasn't sure it would work as the files are for the P5210 but it was fine.

thank you!

@ebue
I am trying to help ebue to find out exactly what this OLDDDD tread is about:
What is the safe way to root a GT-P5220 Tab3 10 4G .
I decided to move here to stop hijacking ( not really) or taking to much attention for P5220 on the original question of ebue at => http://forum.xda-developers.com/showpost.php?p=55315126&postcount=157
So in this tread we have the ONLY testimony in this forum, where our friend parker_dhd claims he got it
parker_dhd;48219938...[COLOR="Red" said:
I was able to root using the method[/COLOR] here
http://forum.xda-developers.com/showthread.php?t=2432467
....
Click to expand...
Click to collapse
Now it is true that http://forum.xda-developers.com/showpost.php?p=55315126&postcount=157 is an old and abandon thread. But we can guess that in fact as expected P5220 share same partition arrangement for recovery.img with P5210/P5200. Be careful with what I said. I am talking only about recovery.img. There are in fact some other partition that are specifically different like for example the modem one.
Still many had ask the same. In particular I saw moonbutt74 in another thread asking the same compatibility question I have:
moonbutt74 said:
S,
could you tell me jf the following is correct on the 5220 ?
/system = /dev/block/mmcblk0p8
/data = /dev/block/mmcblk0p9
/boot = /dev/block/mmcblk0p10
/recovery = /dev/block/mmcblk0p11
thanks, m
Click to expand...
Click to collapse
The answer is easy to find if we get a Champion owner to help us. I am hoping @ebue can help us help him.
Well at the moment I do not have a good internet connection I am really limited in bandwith.
So we need a champion that can download a Stock Samsung 4.2.2 Firmaware. In particular I need the recovery.img.
So @ebue
1)You should had downloaded a Stock Rom yourself just in case you need to go Back to Stock.? Don't you?
2)Clearly in your case your Stock Official Samsung Rom will not start with
5210xxxxxxx_P5210Xxxxxxx_xxx.zip instead will be with "5220" or something 5220xxxxxxx_P5220Xxxxxxx_xxx.zip
Listen still the name may be in another format. That is the usual name for sammobile files.
3)In my case I downloaded: 5210UEUAMH1_P5210XARAMH1_XAR.zip long time ago.
4)In my case if I can unzip this file I will see inside 2 files:
P5210UEUAMH1_P5210XARAMH1_HOME.tar.md5
SS_DL.dll
Ignore "SS_DL.dll"
5) Now extract "P5210UEUAMH1_P5210XARAMH1_HOME.tar.md5"
6) Now Rename the extracted "P5210UEUAMH1_P5210XARAMH1_HOME.tar.md5" to "P5210UEUAMH1_P5210XARAMH1_HOME.tar". Yes no ".md5"
7) Now open "P5210UEUAMH1_P5210XARAMH1_HOME.tar" with winzip or any other zip app. You will see it contains
"boot.img, cache.img, hidden.img, recovery.img and system.img". ".
8) Now Extract just/only "recovery.img. And using winzip/winrar Zip ONLY "recovery.img" to "recovery.zip".
We zip it back because this forum will not allow to upload files that are not in zip form.
It should be a file of less than 20Megs. Usually around 10megs. Uploads files are done tru "Manage Attachments" link at the bottom on the advance Replay window.
Listen If you have trouble uploading it to this forum you can try to upload in
Code:
http://d-h.st/
9) Post that file in here, so that i can look at it.
Please see that you may have to use Code to not show your Hot Link like this
Code:
http://d-h.st/

Ok,
I spent my time overnight to download a P5220 Stock rom. I did
P5220XXUAMJ8_P5220VFGAMK1_VOD.zip
I think is a Vodaphone from Germany. But as I said the Recovery Info that we need should be the same in all roms.
1) Warning
Now before I say anything more, I want to make clear that there are many people with Tab3 7", 8" and even 10" that claims that had no trouble installing recovery and rooting. But when they decided to go back to Samsung Stock they lost Wifi or Cell capabilities. I know sound serious, and I have no Idea why so many claims. Lets say more, Most of those claims you can find them here in QA and are 7" and 8" that has nothing to do with the TWRP used in 10". I just have to say this because I seen it and have no understanding on the facts.
I will strongly suggest to backup modems and efs partitions as soon as you install a recovery. This can be done using dd command under Recovery. We could even make a update.zip to do that if any is interested.
You need to be sure that you have downloaded your exact Stock Rom. Even more If I was in your case with a Tab3 with cellphone capabilities I will take my Stock Rom and eliminate the modem.img from the package. There is no reason as to have that in the Stock Rom, unless you have in fact a bad modem. This is only my personal opinion. This is personal suggestion from some one that have no Idea of what he is saying. It is opt to you to research in the area.
Click to expand...
Click to collapse
I have compare "fstab.recovery" from both P5210 and P5220 and show exact information.
/recovery emmc /dev/block/mmcblk0p11
I guess we can conclude that all P5200, P5210 and P5220 have "recovery.img" in "/dev/block/mmcblk0p11"
Code:
# Copyright (c) 2011, Code Aurora Forum. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of Code Aurora Forum, Inc. nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
# mount point fstype device [device2]
/efs ext4 /dev/block/mmcblk0p2
/config ext4 /dev/block/mmcblk0p3
/cache ext4 /dev/block/mmcblk0p6
/system ext4 /dev/block/mmcblk0p8
/data ext4 /dev/block/mmcblk0p9 length=-16384
[COLOR="Red"]/recovery emmc /dev/block/mmcblk0p11[/COLOR]
/modem emmc /dev/block/mmcblk0p12
/preload ext4 /dev/block/mmcblk0p13
/boot emmc /dev/block/mmcblk0p10
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
2) So the first question: Can I install and used a TWRP Recovery made for P5200 or P5210 in P5220? Its seems yes, you can install and used it.
3) BUTTTTT
There is no TWRP or any other Recovery that had been made specifically for P5220. So once install your Recovery will think it is a P5200 or P5210 depending in the file you use.!!! This may result in that some "update.zip" type of installation will fail due to mismatch of Model. This should not be a big problem. You can always install back your Stock Recovery. And we can ask moonbutt74 to build a TWRP recovery using the P5220 particular files in ramdisk of recovery.img.
4) If you want to root I sugest you fallow the only sucefull claim in this forrum, see first post of this thread. I will the install Recovery from
http://forum.xda-developers.com/showpost.php?p=45552913&postcount=1
Then I suggest you backup your sensitive partitions using dd if TWRP do not have that capability.
and I guess you can then root using
http://forum.xda-developers.com/showthread.php?t=2642796
Please stick around, I am very interested in getting a copy of you pit file. I had made a WIN7 batch file that will copy that file from your tablet. A soon as you are rooted notify us and I will post the batch file.
I am attaching the recovery.img of P5220 in Odin tar.md5 in the hope that @moonbutt74 can help us, As soon as moonbutt74 has a P5220 you could upgrade as a TESTER! and report your findings.

This is great news because I was having problems trying to copy the requested files from my phone. So I can just go ahead and install the 'Odin_SGT3_recovery' from the thread you linked. Then use Rest3ssroot.zip to root, right? Or should I just wait until moonbutt74 looks at the file?

Lets talk about us first.
ebue
Your record shows" Posts: 138 and Join Date: Feb 2010". So you should have some experience. But you are sounding so afraid that I wonder.
Most of us here take risk, you know thinks can go wrong. The important is to try to be prepare, Read, read and read. Then make sure you have the appropriate tools and files to recover in case of trouble. Understand that if something goes wrong you and only you is responsible. Do not blame anyone else. At this point you should had check what firmware is your device, and had downloaded you OWN particular 4.2.2 Stock Recovery from Samsung. Do you have?
Please tell us the the firmware version of you device. Just to at least force you to look at it. jijij
Most important, Are you in original 4.2.2? For me this is important. I personally do not trust 4.4.2.
Please tell us that you have ODIN 3.07 and that you have downloaded your correct stock rom from samsung.
Please tell me that at this point you had backup all essential information from your P5220.
Please tell me you have an External Sdcard with at least 4g for ease zip installations.
r2d23cpo
I am an unemployed user. I have some technical background. I have a GT-P5210 -Tab3 10 wifi.
I like to help people but please understand I am no expert. I do know that I learn a lot while helping others.
moonbutt74
There a bunch of good I mean good developers here that I bet you are double as smart as moonbutt74. jijiji I am kidding I do not know.
But what I know is that moonbutt74 will take a problem by himself and spent hours, days,weeks.. until hi find the solution. I admire him.
I do not know why any of the developers had comment yet, I can assume that the lack of FEEDBACK from P5220 owners reporting the result make us be in safe mode. But believe they are out there watching us. jijiji
You know moonbutt74 had read this, look at the thanks. He has been around. But please understand that he has not commit to create for you a new recovery!! I have faith that he will help P5220 in the near future. But when I do not know. So if you what to wait, that is smart. I just do not know when it will happen.
Listen this is what I am going to do. I am going to test the P5220 4G Stock Recovery I downloaded in my P5210 wifi. I see how it behaves. This is not a fill probe that it can work, but at least we can see if the TAB bootloop failing!
As for procedures.
Remember I am no expert!!! If you want to follow me is at you own risk.
Please understand the difference in installing a Custom recovery.img (TWRP) vs root process.
*Just installing Custom recovery.img (TWRP).
First booting in recovery do not affect normal boot process(Android). Is like a X-ray, you can inspect and take x-rays ( backups) without injury Android OS. You cam always replace the original recovery.img and no harm done.
** rooting - Is like an organ replacement operation at the table, you are installing new software that Android could reject and bootloop!!
A) So first step:
Download and have ready all tools and files. No harm done to the TAB3.
B)Watch this video: it is for TAB3 7" but give you an Idea of the procedure you need to follow:
Code:
http://youtu.be/BDShwBHRjUE
C)installing
[RECOVERY][TWRP_2.7] SGT3 Recovery[FINAL]=>http://forum.xda-developers.com/showthread.php?t=2442915
1) Once you download file you received:
Code:
recovery.tar.zip
2) Unzip you will see:
Code:
recovery.tar.md5.tar
this is the file will be using with Odin.
If you let the TAB to reboot automatically after you install recovery with Odin, chances are that su or recovery will fail. So I suggest you deselect "Auto Reboot" only let "F.Reset Time" This is not a tutorial in ODIN I suggest anyone read more about it. In particular DO NOT mark "RE-Partition" it is very dangerous. That is there for very Special occasions.
Odin
1) Turn Off your TAB.
2) Run Odin 3.07
3) Hook the cable to the TAB3
4) Press Just [Power]+[Volume Down] this is enogth in my tab. But if you Prefer [Power]+[Volume Down]+[Menu] Your Tab should Show the Warning! Screen and the Yellow Triangle. Nothing should be shown in Odin yet.
5) As the test read [Volume Up] to Continue. Your Tab3 shows now the Android and read Downloading. Your PC did a "Beep" acknowledging the Driver is ready. Odin now shows in First Slot of "ID:COM" a Blue data that Reads "0:[COMx]" where x is a number for comport. Number does not mater. This tell you ODIN as recognized your Device.
6) Options: Now make sure check-mark ONLY for "F.Reset Time" is selected. Nothing more. Please read my warning before.
7) Files [Download] select check mark of PDA
8) Press PDA and Navigate to where you have your recovery in you case "recovery.tar.md5.tar"
9) "Message" window . Odin tell you the status in this window. you should see
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
So be smart wait!!
10) Then is file is validated you will see
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS.
11) Now after you see Successful Odin is ready. If you do not see there is something wrong.
12) Now we can press "START"
13) You should see ID:COM with progress bar. TAB3 shows a progress bar too. On top it reads "Recovery". With time you should read in Message
Code:
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.img
<ID:0/011> NAND Write Start!!
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
14)You need to wait until Blue "Recovery" change to "Reset". Remember TAB3 will not boot automatically since we deselect. So Once we see reset we know it is ready.
15) Now we go to the TAB3 and press [Power]+[Volume UP] to get into recovery. This is important since some time recovery fails if we let the TAB3 reboot in to OS.
16) navigate if you like to see your new recovery
Now do not install root yet. Just use TWRP to backup to External SDCARD. yes external so that if something fails you still have recovery files in your External SDCARD.
So once you have done this report to us.
Good luck.

ebue
Keep an eye on moonbutt74. He have not make any comment but, he just edited his thread today around 03:52 PM around 4 hours ago.
And I see a link that reads
Code:
dev-host link - http://d-h.st/4bN TO RECOVERIES - GT-P5220 ODIN -extract then flash.
Usually I do not post other user work "Breaking News", but if I am you I will wait to see if he in fact is helping you!.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
I feel like I am talking by myself.
But I have to say that I did test the STOCK P5220 Recovery and it seems to work nicely. Clearly I have a "Custom" Rom and Recovery shows the Triangle over Android!! Tha we know it happens.
I did also test new h__p://d-h.st/4bN TO RECOVERIES - GT-P5220 ODIN in my P5210 for test purposed and Philz seems to work correctly too.
I did extracted "recovery.img" from "TO RECOVERIES - GT-P5220 ODIN" and seems to shows correct data for P5220 device.code="santos10lte".
At this point I still like TWRP because moonbutt74 TWRP has the ability to accept adb shell commands on the PC! A nice addition while testing.

r2d23cpo said:
Lets talk about us first.
ebue
Your record shows" Posts: 138 and Join Date: Feb 2010". So you should have some experience. But you are sounding so afraid that I wonder.
Most of us here take risk, you know thinks can go wrong. The important is to try to be prepare, Read, read and read. Then make sure you have the appropriate tools and files to recover in case of trouble. Understand that if something goes wrong you and only you is responsible. Do not blame anyone else. At this point you should had check what firmware is your device, and had downloaded you OWN particular 4.2.2 Stock Recovery from Samsung. Do you have?
Please tell us the the firmware version of you device. Just to at least force you to look at it. jijij
Most important, Are you in original 4.2.2? For me this is important. I personally do not trust 4.4.2.
Please tell us that you have ODIN 3.07 and that you have downloaded your correct stock rom from samsung.
Please tell me that at this point you had backup all essential information from your P5220.
Please tell me you have an External Sdcard with at least 4g for ease zip installations.
r2d23cpo
I am an unemployed user. I have some technical background. I have a GT-P5210 -Tab3 10 wifi.
I like to help people but please understand I am no expert. I do know that I learn a lot while helping others.
Click to expand...
Click to collapse
Although I have been a registrant since the said date, I am still a novice. I have no technical ability what so ever. I am kinda busy with my family and work constantly. My kids do not give me a lot of time to do trails and errors and I do not have so much time on my hands. That is why I thought a root would have been available for download so I can just root and get on with my life. I do not have time to experiment lie you guys do. All I want to do is root to remove apps that I do not use or want. That's all. I used to try out different different ROMs a long time ago. But that is when I had time. I do not want to be bother with trying out different ROMS if I am not forced to. That is why I leave these things up to people who have the time and resources and who are dedicated to these things. So, if I have to wait to get a proper root so I do not have to risk anything, than I will. So, I can give you the little info that I have for my pad. Here they are:
1. I have downloaded Odin already and in the process of downloading my Stock Firmware.
2. I do not have an external car yet for my pad. Only for my Note 3, which I am using. I will buy one soon.
2. My Android -Version is 4.2.2 ; Basbandversion is P5220XXUANE1 ; Kompileringsnr is JDQ39.P5220XXUANB4
Anything else you request?

I understand you, not enoght free time. Do not feel presure from me. Wait for others to report a valid solution is no bad, in many cases is the smart thing todo.
As I said moonbutt74 build Philz Advance CWM for P5220. But some one with a P5220 need to test it and report. I see in his last page some interested, but if no one reports we will never know. Reporting Feeback is the most value tool after a developer has done his work.
Sent from my GT-P5210 using XDA Premium 4 mobile app

I just tried Moonbutt's Philz and TWRP recoveries. I was trying to flash the stock roms for p5220)LTE as posted by Restl3ss. In both cases I got errors and am now waiting for a TWRP version that works on the p5220.
Samsung Galaxy Note 2
Dr. Ketan v12.1 4.4.2 NI1
Kernel: Stock
Apex Launcher
---------- Post added at 04:32 PM ---------- Previous post was at 04:04 PM ----------
quijote1 said:
OK, I installed PhilZ and it seems to work fine. First I tried to flash your deodexed rom. Part way through the flash I got the message:
set_metadata_recursive: some changes failed
E;Error in /sdcard/download/P5200-4.4-stock-deodexed-rooted.zip
(Status 7)
E: Installation aborted
So now I'm going to try the totally stock one.....
Same error again. Bummer because I forgot to make a PhilZ backup of my 4.2.2. I have a TWRP backup, but that's all.
Click to expand...
Click to collapse
The above is a message that I sent to Restl3ss, but repeat it here since it shows the error messages that I got with Philz by Moonbutt.
Just to provide feedback, the version of Philz recovery worked very well for the most part. I like it better than TWRP. If I could get it to install roms, I would stick with it.
Off topic, I am in Spain and Orange is my carrier but my tablet is not linked to Orange. There is a stock rom on Sammobile that is for Orange in Spain. Would that work on a tablet that is unlocked?
Samsung Galaxy Note 2
Dr. Ketan v12.1 4.4.2 NI1
Kernel: Stock
Apex Launcher

To add more detail, it turns out that Restl3ss left out a few lines of code for the p5220. Since he didn't have one he never noticed. Now he has added that code and now his rom loads with TWRP.
Samsung Galaxy Note 2
Dr. Ketan v12.1 4.4.2 NI1
Kernel: Stock
Apex Launcher

Need Help with development issue for sgh-i467 (ATT galaxy note 8)

First, I'm not a developer... but I have compiled a few roms from scratch in the past following tutorials. I would consider myself an avid android user, not a developer.
I recently got root access for my device with a locked bootloader... thanks to @K1979C20 pointing out that kingroot v4.1 finally works on our kitkat 4.4.2 device. I then removed kingroot and installed supersu using an app called "supersu me". I now have full root access, but no custom recovery due to the locked bootloader.
I was able to use @Chainfire flashfire beta app to do a backup of all my device partitions (I did not do data or cache, but can if needed).
I'm wondering if the backup can be used to create an Odin flash able package for others to use to gain root access on their device, because the kingroot process apparently works for some, but not for others...
If not Odin flashable, what other options could my files be used for to create a rooted rom that can be installed on others sgh-i467 devices.
Would it be helpful to do a full dump of all partitions? If so, any help figuring out the partition structure and process of dumping it would be appreciated.
I'm willing to do the work on this as time permits... just looking for someone with experience to point me in the right direction.

These are the files I saved in my flashfire backup

Ok now I'm not a developer at all but I'll try to help you out! Ok below is the partitions layout for our device. Now we don't need a copy of the bootloader because in the ota-update they gave us the sboot.bin and the tz.img which is the bootloader! But what we do need is the kernel (the boot.img), the recovery.img, the modem.bin, the param.bin and the system.img. But I'm not sure that even if you manage to pull these from the system that we will be able to flash them using odin cause with us having a locked bootloader if the images aren't signed by AT&T it won't allow the device to boot. But you can do it anyways and anyone willing to try can give it a shot! I would but my wife has taken over my Note 8 to use to play her games and she won't let me risk it cuz she will loose all her data! But to do the system pulls the way I know is to download Terminal Emulator for Android from the play store and make sure you have the latest Stericson Busybox installed and open the Terminal Emulator and type su the hit enter and grant it root access. Now use the following commands to pull the files but don't use the ( ) marks ok!
(busybox dd if=/dev/block/mmcblk0p8 of=/sdcard/param.bin)
(busybox dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img)
(busybox dd if=/dev/block/mmcblk0p10 of=/sdcard/recovery.img)
(busybox dd if=/dev/block/mmcblk0p13 of=/sdcard/modem.bin
(busybox dd if=/dev/block/mmcblk0p20 of=/sdcard/system.img)
If you wanna pull the cache.img, hidden.img, and tombstones.img you can but that's up to you. When you finish if you will put the into a zip file and upload them to like drive or dropbox or whatever you use and send me a link I'll try to talk my wife into letting me test it. I'll put the sboot.bin and tz.img from the ota-update with it.
mmcblk0p1: bota0
mmcblk0p2: bota1
mmcblk0p3: efs
mmcblk0p4: m9kefs1
mmcblk0p5: m9kefs2
mmcblk0p6: m9kefs3
mmcblk0p7: carrier
mmcblk0p8: param
mmcblk0p9: boot
mmcblk0p10: recovery
mmcblk0p11: ota
mmcblk0p12: cdma
mmcblk0p13: modem
mmcblk0p14: tombstones
mmcblk0p15: tdata
mmcblk0p16: hidden
mmcblk0p17: reserved1
mmcblk0p18: reserved2
mmcblk0p19: cache
mmcblk0p20: system
mmcblk0p21: userdata

@RootSuperSU I am working on this now... THANKS will post a link in a while and pm you
EDIT: I have extracted all of the files, but it's gonna be a bit before it is all uploaded. I have 100mbps download speed, but the upload speed is a whole different issue...
EDIT #2: try this link for the files you requested https://onedrive.live.com/redir?resid=7FBDBF9B2D3ACDA5!4928&authkey=!AAiZqsqu3y_s5dk&ithint=file,zip
OR try this one if that doesn't work: https://drive.google.com/file/d/0B3w-dFE5Q3FOUlp3bVhMS2lFYjA/view?usp=sharing

@RootSuperSU
Just so I learn the process... how would I extract the sboot.bin and tz.img? Even if you don't need these from me, I'd like to do it so I can learn the process... it's the old "teach a man to fish" addage. Based on what I have read elsewhere, I taking a guess and wondering if:
Would bota0 be where to extract the sboot.bin?
Would bota1 be where to extract the tz.img?
If these are the correct locations, presumably the same type of code is used to extract them as the other files I did above?

dandroid7 said:
@RootSuperSU
Just so I learn the process... how would I extract the sboot.bin and tz.img? Even if you don't need these from me, I'd like to do it so I can learn the process... it's the old "teach a man to fish" addage. Based on what I have read elsewhere, I taking a guess and wondering if:
Would bota0 be where to extract the sboot.bin?
Would bota1 be where to extract the tz.img?
If these are the correct locations, presumably the same type of code is used to extract them as the other files I did above?
Click to expand...
Click to collapse
I'm not sure about those 2 files! I don't know which files are what that is why I didn't say to pull those mainly! I wish I knew.

Ok developer gurus... i tried using romdump via terminal emulator... i'm getting the following message... I have edited permissions on the romdump file, but cant get it to dump the files... it looks like it is opening the script, but its giving me this error...
Any advice?
I'm trying to do a full romdump vs the partial stuff i have already harvested... wanting to make sure i get everything in the right format.

@dandroid7 I'm not sure if you noticed but boot.img and recovery.img are the exact same size. From what I can tell is that we can't get a real dump of either because of the locked bootloader.

@TMartin
hmmmm, I didn't notice that. but now I see what you are saying. Could be operator error on my part in how I extracted the stuff (see post #3) - or it could be as you say because of the locked bootloader. either way - I don't have the knowledge to say which it is (if either).
I'd really like to learn more about how to properly do this stuff... I have been googling and reading a lot - but not making much progress. It would be awesome to pick the brain of a developer or two who could give me some pointers. I don't mind doing the work - I just need some direction.
I guess we will see if anyone else posts more ideas... meanwhile - I'll keep reading and experimenting.

dandroid7 said:
@TMartin
hmmmm, I didn't notice that. but now I see what you are saying. Could be operator error on my part in how I extracted the stuff (see post #3) - or it could be as you say because of the locked bootloader. either way - I don't have the knowledge to say which it is (if either).
I'd really like to learn more about how to properly do this stuff... I have been googling and reading a lot - but not making much progress. It would be awesome to pick the brain of a developer or two who could give me some pointers. I don't mind doing the work - I just need some direction.
I guess we will see if anyone else posts more ideas... meanwhile - I'll keep reading and experimenting.
Click to expand...
Click to collapse
Hey I don't know what they are talking talking about we can't do rom dumps with locked bootloader because I have unpacked the modem.bin, param.bin, boot.img and recovery.img you sent me successfully with no problems using only my Note 8! I haven't been able to find away to unpack the system.img tho cause I don't have a computer but I am working on trying to find away!

Just trying to learn here... what do you use to unpack the .bin and .img files on the tablet? Not that I know what I'm doing, but I'd like to see what's in the files for the sake of learning.
Additionally... I have a decent computer... so if given a bit of direction, I could unpack the system.img file, put it in a zip file, and post a link to whatever you need for it.
Let me know if you want me to do so.

RootSuperSU said:
Hey I don't know what they are talking talking about we can't do rom dumps with locked bootloader because I have unpacked the modem.bin, param.bin, boot.img and recovery.img you sent me successfully with no problems using only my Note 8! I haven't been able to find away to unpack the system.img tho cause I don't have a computer but I am working on trying to find away!
Click to expand...
Click to collapse
I've tried multiple ways and can't get anything to mount and extract. I'd love to know how you pulled them. Do you have them uploaded anywhere?

TMartin said:
I've tried multiple ways and can't get anything to mount and extract. I'd love to know how you pulled them. Do you have them uploaded anywhere?
Click to expand...
Click to collapse
dandroid7 managed to follow my directions in post #3 on this thread and he managed to do all the pulls. He has them on his ondrive uploaded. Check and read the posts man!

dandroid7 said:
Just trying to learn here... what do you use to unpack the .bin and .img files on the tablet? Not that I know what I'm doing, but I'd like to see what's in the files for the sake of learning.
Additionally... I have a decent computer... so if given a bit of direction, I could unpack the system.img file, put it in a zip file, and post a link to whatever you need for it.
Let me know if you want me to do so.
Click to expand...
Click to collapse
I used the ZArchiver Pro app I bought on the PlayStore to unpack the modem.bin and the param.bin. It's a file manager and has features kinda like 7zip for Windows. Jus open the app and go to the .bin files long press on them and open as archive. Here is a link to the app on my Drive storage.
https://drive.google.com/file/d/0B-Zg_yh4ytvLYkNINVBpZThQQlE/view?usp=docslist_api
For the boot.img and recovery.img I used a app called Unpack Repack Img. You have to make a folder called unpack on the root of your sdcard and place your boot.img on the root of your sdcard also then use the app to unpack. For the recovery.img same app and same way but you will have to rename it to boot.img for the app to do it. But it doesnt work on repacking the images. Here is that app. https://drive.google.com/file/d/0B-Zg_yh4ytvLQ3RLa2I1bWl2OFU/view?usp=docslist_api
Now if you wanna use Android Image Kitchen for Windows/Linux/Mobile to unpack and repack the boot.img and recovery.img then just go check out this thread below for the downloads and information on how to install and use.
http://forum.xda-developers.com/showthread.php?t=2073775&page=1
Now for the system.img since you have a computer I would check out this thread for what seems to be an easy way to unpack it.
http://forum.xda-developers.com/showthread.php?t=2294909&page=1
or
You can look here at this thread for another way to unpack the system.img. Apparently this has Chainfire's Tools he uses to:
* Extract/repacking zip/.tar.md5 ROM files
* Unpacking/mounting/repacking ext4 sparse partition image files
* Unpacking/repacking boot image files
in LINUX OS
http://forum.xda-developers.com/showthread.php?t=2600364&page=1
For a better and more complete guide with step by step and pics on how to get the list of partitions and how to get the dumps using a computer with adb commands or using a Terminal Emulator app on your device go check out this thread!
http://forum.xda-developers.com/showthread.php?t=2450045&page=1
Be sure to go to the OP of each thread. That's the short term for Original Post if you didn't know. I hope this all helps yall out on how to do this stuff! Really all you had to do was Google Search this and just look for the XDA links section. Normally they are some of the 1st links given. But I'm glad to help anybody cause I know how difficult it can be trying to figure out all this stuff. I've only been into this for the past 2 or 3 years. I wish I knew alot more. I hope to be able to get a good computer and maybe compile my own custom roms and kernels and recoveries for my devices!