Database Info

Q/A for someone who has some time...

Heres the dealio- I have a Charge I want to root and put a custom rom on. I have done this before, with my Inc and my Archos tablet so I'm not a complete idiot.
I did use Odin and thought everything went fine, followed directions to install a zip from the card but the recovery menu never gave me that option. I am unable to get to the sdcard from the recovery menu. I got the option to install the update.zip but thats all. (I followed one of the many thousand "how to root your charge" threads)
Can someone tell me what happened?
Also, the first time I tried to do it, I realized I didn't have the right file, so I pulled the plug on my Charge while in Odin, also because it kept looping. Now Windows XP on that machine won't recognize the phone anymore.
Anyone have any ideas on that?
One more, I read that you need to downgrade the EE4 in order to root? Is that why recovery didn't work the first time, because I have the EE4? (I did see that info AFTER I installed the recovery)
I've been over these threads hundreds of times but I just don't have alot of time and there is alot of redundant information that makes it hard to get anywhere so I'd appreciate if someone could help me out.

willowave said:
Heres the dealio- I have a Charge I want to root and put a custom rom on. I have done this before, with my Inc and my Archos tablet so I'm not a complete idiot.
I did use Odin and thought everything went fine, followed directions to install a zip from the card but the recovery menu never gave me that option. I am unable to get to the sdcard from the recovery menu. I got the option to install the update.zip but thats all. (I followed one of the many thousand "how to root your charge" threads)
Can someone tell me what happened?
Also, the first time I tried to do it, I realized I didn't have the right file, so I pulled the plug on my Charge while in Odin, also because it kept looping. Now Windows XP on that machine won't recognize the phone anymore.
Anyone have any ideas on that?
One more, I read that you need to downgrade the EE4 in order to root? Is that why recovery didn't work the first time, because I have the EE4? (I did see that info AFTER I installed the recovery)
I've been over these threads hundreds of times but I just don't have alot of time and there is alot of redundant information that makes it hard to get anywhere so I'd appreciate if someone could help me out.
Click to expand...
Click to collapse
1) don't choose the option to select 'update.zip', that option doesn't work on the Charge... also it sounds like you were in the stock recover, you do flashing/wiping in ClockWorkMod recovery (CWM)
2) NEVER pull the cord out during an Odin flash unless its been like 30+ minutes and it looks like it froze or nothings happening, this is probably why your phone can't be recognized now (that is a good way to brick your phone and it sounds like you've got one)... now you will need to get the phone into download mode (if it still will) and flash the stock EE4 rom with the Charge PIT file (can't link from phone but these are in the How To Fix Your Phone sticky in Development) and start over
3) I don't quite understand your last question but no you don't need to be on EE4 to root and you can put CWM on any rom with Odin, EE4 at this point is mostly a 'return to stock' rom
blazing through on my 4G Droid Charge

The phone seems to be working fine, but maybe that is why I was in stock recovery mode, because it looks fine, but won't download now. Because I just tried to install a rom and I get an error. I had tried to install CWM, and thought thats what I was going to when I ended up in the stock recovery. I will try the Charge PIT file that you mentioned and see if that fixes anything, and then start over from there. If not I may be returning the phone since it's fairly new.
Thanks for your time

willowave said:
The phone seems to be working fine, but maybe that is why I was in stock recovery mode, because it looks fine, but won't download now. Because I just tried to install a rom and I get an error. I had tried to install CWM, and thought thats what I was going to when I ended up in the stock recovery. I will try the Charge PIT file that you mentioned and see if that fixes anything, and then start over from there. If not I may be returning the phone since it's fairly new.
Thanks for your time
Click to expand...
Click to collapse
when using the pit file be sure to have the repartition box checked in Odin
blazing through on my 4G Droid Charge

I don't have a PIT option on my Odin, or a repartition. It's version 4.13...is there a better version of Odin to work with and stick with? I'm working with 3 different computers here, so I know I have an Odin at home that was working but this one doesn't seem to connect. It's easier to troubleshoot whats going wrong if the proggies I'm using are at least a consistent version number. I DO know I had PIT on the Odin at home but version I'm using (at work) doesn't have it.

willowave said:
I don't have a PIT option on my Odin, or a repartition. It's version 4.13...is there a better version of Odin to work with and stick with? I'm working with 3 different computers here, so I know I have an Odin at home that was working but this one doesn't seem to connect. It's easier to troubleshoot whats going wrong if the proggies I'm using are at least a consistent version number. I DO know I had PIT on the Odin at home but version I'm using (at work) doesn't have it.
Click to expand...
Click to collapse
You need Odin3 1.82 (not just plain Odin). You can get it from http://forum.xda-developers.com/showthread.php?t=1160580

Thanks for the help guys. I got everything back to normal. Drivers and sdcard working properly now. Rooted. Now I just need to get Clockwork back on, and a different rom. Anyone have any fav roms so far? Would love some input on what everyone sees with the different radio builds.
If anyone can answer this, can we get mobile hotspot working on this? Thats a big part of why I need to root and rom this thing.

willowave said:
Thanks for the help guys. I got everything back to normal. Drivers and sdcard working properly now. Rooted. Now I just need to get Clockwork back on, and a different rom. Anyone have any fav roms so far? Would love some input on what everyone sees with the different radio builds.
If anyone can answer this, can we get mobile hotspot working on this? Thats a big part of why I need to root and rom this thing.
Click to expand...
Click to collapse
Everyone will have an opinion on ROM's and radios. My setup is in my sig. As for hotspot, android-wifi-tether works fine on all rooted roms. I've found 3.0pre12 to work the best. 3.1beta6 requires a reboot to get wifi working normally after tethering, but I don't have that issue on 3.0pre12. Be sure to immediately reboot after you install it, and then go in and set your phone type to Samsung Fascinate, and you should be good to go.

[Q] PLEASE HELP. Soft Bricked My Verizon Galaxy S4.

Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.

muazra said:
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
Click to expand...
Click to collapse
Hi there,
it seems an easy problem but do it at your own risk I don't take responsibility of bricked device,etc
so lets go with what you need:
A- Odin [I believe you already have it]
B- stock rom go to this site:
androidayos.com/samsung-galaxy-s4-odin-stock-firmware/
and choose the suitable stock rom based on your Baseband version
C- Drivers installed for your device [if your mac/laptop recognizes your device then skip this step if not google it,download the drivers and install them]
IMPORTANT:Make sure you have 80% or more on battery
after you get these stuff install the device drivers as mentions in C then turn your device off and power it while holding volume up it should take you to download.now open odin and navigate it to the rom which you downloaded from B and flash it .wait for green color to appear and your back to your stock now it should open normally hope that I helped

[Q] Tab 2 WILL NOT ROOT!!

Please, for the love of god, someone help me!!
I have spent the past 2 days trying to root my brand new Tab 2 (verizon) p3100 (android 4.1.2). I've tried every tutorial that I can find. I've tried various versions of Odin, various versions of heimdall, various versions of CWM and other rooting files. I get error after error. The device still works fine but it WILL NOT ROOT!!
I am currently trying to use Odin3 and CF Auto Root (my 100th attempt probably). Every time I use Odin, any version, any tar file, it fails with a "Fail! (Auth)" error. The message in download mode says "SECURE CHECK FAIL: recovery".
I've done a factory reset of the Tab. I've cleared cache. I've tried running Odin is an admin. I've tried different usb ports on my PC (Windows 7, 64bit).
It doesn't matter what I try, it always results in an error. This thing just WILL NOT ROOT!
Can anybody tell me what the problem is? Or another way to root? Please. This is driving me crazy!!
Thank you!!

Try this.

Huge problem
I found these instructions:
droidviews.com/how-to-root-and-install-cwm-twrp-recovery-verizon-galaxy-tab-2-sch-i705-on-ics-jelly-bean/
And finally got it to root. Then I got to the part where I installed the terminal emulator, granted it root access, and followed the instructions to install aboot.img. Then the Tab shut down, I thought it was going to reboot but it never started back up. Now I can't get it to turn on or go into recovery or download mode. Nothing. Everything was fine up to that point. Now nothing at all. How do I fix this??

ninasmith said:
I found these instructions:
droidviews.com/how-to-root-and-install-cwm-twrp-recovery-verizon-galaxy-tab-2-sch-i705-on-ics-jelly-bean/
And finally got it to root. Then I got to the part where I installed the terminal emulator, granted it root access, and followed the instructions to install aboot.img. Then the Tab shut down, I thought it was going to reboot but it never started back up. Now I can't get it to turn on or go into recovery or download mode. Nothing. Everything was fine up to that point. Now nothing at all. How do I fix this??
Click to expand...
Click to collapse
<facepalm>
Oh boy... WHY the heck did you flash a bootloader (totally unnecessary step to begin with) from a completely different device?!?! There is so much info on rooting P31xx here on XDA, describing several different methods in details, and yet you managed not only to find a way that is not even intended for your device, but to proceed with no understanding of the process whatsoever...
I would suggest to take a deep breath, and try again (and again) to get your tab started in download mode (hold Volume DOWN + Power until you see a warning screen). If you can do that, flash the proper ROM with Odin -- whatever version you can find, but the one for your device. Then promise yourself to NEVER do anything without at least a basic understanding of what you are doing.
If you can't get the download mode working, then look up the service centre. You have an option to play dumb and just say it suddenly died on you -- maybe, you get lucky and could claim the warranty.
EDIT: OK, I am really confused now... You specifically said you have a P3100, but you also mentioned Verizon. So, which one is it that you have -- GT-P3100, or SGH-i705??? These are very different devices! If you indeed have an i705, disregard what I said above (it's relevant to P3110), and start with this thread. It may not be as bad after all...

kt-Froggy said:
<facepalm>
Oh boy... WHY the heck did you flash a bootloader (totally unnecessary step to begin with) from a completely different device?!?! There is so much info on rooting P31xx here on XDA, describing several different methods in details, and yet you managed not only to find a way that is not even intended for your device, but to proceed with no understanding of the process whatsoever...
I would suggest to take a deep breath, and try again (and again) to get your tab started in download mode (hold Volume DOWN + Power until you see a warning screen. If you can do that, flash the proper ROM -- whatever version you can find, but the one for your device. Then promise yourself to NEVER do anything without at least a basic understanding of what you are doing.
If you can't get the download mode working, then look up the service centre. You have an option to play dumb and just say it suddenly died on you -- maybe, you get lucky and could claim the warranty.
Click to expand...
Click to collapse
It's not a different device. I have the Tab 2 from Verizon, which is the i705. I thought it was the same as a p3100 but I guess it's not because verizon locks it down more. The model number, listed in settings, is the i705. So I found these instructions and actually rooted it just fine using odin (finally). When it rebooted, I had super user and all was good. Until the part where it told me to do the aboot.img with the terminal emulator.
I have been trying for the past half hour and cannot get it to do ANYTHING. I've held down every combination of buttons and nothing at all. It will not turn on. It will not go into recovery. It will not go into download mode. Nothing. I plug it into the computer and it's not recognized by the PC (because it's not on). I've plugged it into the wall. Nothing. It will not do anything! I don't know what will happen if I try to take this back to Verizon.

ninasmith said:
It's not a different device. I have the Tab 2 from Verizon, which is the i705. I thought it was the same as a p3100 but I guess it's not because verizon locks it down more.
Click to expand...
Click to collapse
It's more clear now, thanks! I updated my post above, before I read your reply. i705 and P3100 are very different, not just because of customizations by VZW, but technically -- different CPU, chipset, radio module, everything.
One thing I can think of is to just leave it plugged in to the wall charger overnight, and try again. You might also want to ask your question in the respective thread that I linked above. But if you really can't get your tab to show any signs of life, you are out of luck, I guess...
BTW, here is another thread for you, related to unlocking the bootloader on i705.

kt-Froggy said:
It's more clear now, thanks! I updated my post above, before I read your reply. i705 and P3100 are very different, not just because of customizations by VZW, but technically -- different CPU, chipset, radio module, everything.
One thing I can think of is to just leave it plugged in to the wall charger overnight, and try again. You might also want to ask your question in the respective thread that I linked above. But if you really can't get your tab to show any signs of life, you are out of luck, I guess...
BTW, here is another thread for you, related to unlocking the bootloader on i705.
Click to expand...
Click to collapse
Thanks. Yeah I tried for about an hour. I had it plugged into the wall. It would not do ANYTHING at all. I took it back to Verizon and exchanged it. Now I just cross my fingers and hope they don't figure it out.

ninasmith said:
Thanks. Yeah I tried for about an hour. I had it plugged into the wall. It would not do ANYTHING at all. I took it back to Verizon and exchanged it. Now I just cross my fingers and hope they don't figure it out.
Click to expand...
Click to collapse
Good that they exchanged it for you. Better luck next time! Read those two threads I linked, it should give you enough info.
BTW, my apologies if I sounded like an a$$. To be fair, you said you had a P3100, and I didn't realize it was actually a different device until I noticed that you also mentioned Verizon. Looks like you tried to do the right thing, but somehow it went sideways. Well, sh!t happens...

[Q] NAND Write Start Fail in Odin

Hi all,
for the last three days I've been carrying around a paper weight that looks remarkably like my Galaxy S3...
Anyway, I'm at a point where I don't know what else I could (or should) try. Today I thought I had a winner when I came across this thread: http://forum.xda-developers.com/showthread.php?t=1840030
I thought wrong. Flashing the bootchains works but then when I try flashing the root66.tar in Odin it always fails during NAND Write Start. I have seen people in the above thread with the same problem and then "never mind, I fixed it"-posts without explanations what they actually did... So, if you managed to fix it or know how to fix it, how does it work?
(I can't post in the same thread because I have less than 10 posts..)
Any input would be highly appreciated!
Thanks a lot and happy new year!
Cheers

In detail what did you do before this problem.

ThePagel said:
In detail what did you do before this problem.
Click to expand...
Click to collapse
Hm... a lot of (probably not very wise) things... Let's see...
It all started when I updated CM10.2 to a nightly release. Something went wrong, not sure what. I was talking to someone and when I checked my phone again it was just sitting there in TWPR and wouldn't boot up anymore (stuck in Cyanogen splash screen). I was still able to boot back into recovery and then tried flashing the stable CM10.2, which it didn't do. I factory reset the phone, tried flashing again, to no avail. The error message was that E: data something was missing or not accessible. From then on it's kind of a blur what I actually did, the list includes:
- trying to flash back to stock in Odin
- trying to flash new recovery in Odin
- trying to flash a pit file
- trying to install new firmware in Kies (after downloading the firmware Kies would just quit (PC), or not even download it and tell me that it's not posfible with my phone (Mac))
- trying the method described in the linked thread
At some point I wasn't even able anymore to boot into recovery (I think that was when I tried to flash a new recovery).
Thanks

I had a similar problem a while back: ODIN wouldn't flash anything and I could no longer get to recovery, etc.
I had been running Odin on Windows XP within a Virtual Machine, something that had never been a problem for me in the past. I ran it on native Windows and it flashed fine (root66.tar). If you're running ODIN inside a VM, try that.
http://forum.xda-developers.com/showthread.php?p=47886084#post47886084
-Joe

joeinternet said:
I had a similar problem a while back: ODIN wouldn't flash anything and I could no longer get to recovery, etc.
I had been running Odin on Windows XP within a Virtual Machine, something that had never been a problem for me in the past. I ran it on native Windows and it flashed fine (root66.tar). If you're running ODIN inside a VM, try that.
http://forum.xda-developers.com/showthread.php?p=47886084#post47886084
-Joe
Click to expand...
Click to collapse
Interesting. I am indeed running Windows in a VM... Need to try that later today. I'll report back later in the pm. Thanks!

IT'S BACK ALIVE! Thanks, Joe! Using a native Windows machine did the trick. I didn't use Odin, though, but did a firmware reset in Kies (was easier to do at work). Anyway, phone is up and running again. Next steps are getting CM back...
Thanks again!

Mungo Park said:
IT'S BACK ALIVE! Thanks, Joe! Using a native Windows machine did the trick. I didn't use Odin, though, but did a firmware reset in Kies (was easier to do at work). Anyway, phone is up and running again. Next steps are getting CM back...
Thanks again!
Click to expand...
Click to collapse
Be careful using kies in the future. If they start pushing 4.3 you will be screwed.

Haven't thought about that. It was still 4.1.2 and I'm back on CM10.2.
Thanks!

[Completed] Samsung Galaxy S4 Google Edition GT-i9505G stuck in recovery mode boot loop

Hello. I need some help ASAP. My phone has been rooted (and running CyanogenMod 11) for a LONG while and lately I've been getting into network penetration. Long story short, I unlocked the bootloader of my GT-i9505G, but when it automatically rebooted, it was stuck in a recovery mood boot loop. I've tried reflashing stock Android (got failures), then CyanogenMod (some more failures), and then GApps (want some fail with that failure?). I've also tried to re-flash my firmware again using Odin 1.85, but it failed (surprise, surprise!) as well! It spit out the attached image in the end.
I'm very skilled with computers but lacking in the mobile phone department. I do know my way around them, but getting into THIS level (firmware flashing) on them is beyond me. I honestly don't know how my phone ended up like this, as I read through the guide to get an idea of what would happen and then went through the guide actually doing the work, and I followed it step by step. I REALLY need to fix this ASAP as I'm a high-school student and I take online classes. I'm sorry if this is on a really noob level, but that's exactly what I am and I'm panicking. I don't have a job and my life is on this device.

Hi, thank you for using XDA Assist. In odin DO NOT have re-partition checked. It'll probably work then. If not try different USB ports, the ones in back of the PC, and cables. Odin can be finicky. You might also try Odin 3.09, but 1.85 has always worked for me.
Good luck and don't panic!

jd1639 said:
Hi, thank you for using XDA Assist. In odin DO NOT have re-partition checked. It'll probably work then. If not try different USB ports, the ones in back of the PC, and cables. Odin can be finicky. You might also try Odin 3.09, but 1.85 has always worked for me.
Good luck and don't panic!
Click to expand...
Click to collapse
I got farther in the process this time, but it still failed. This time at the write operation. What should I do? I also tried it in Odin 3.09 but got the same results as in 1.85.

Hi, sorry for the late response. Are you still having problems? There is a forum for your device where others with your specific device may be able to help. It's located here, http://forum.xda-developers.com/galaxy-s4