Hello all,
Short story, wife had the 4.3 OTA nag popup, accidentally hit 'ok' and pulled battery before unit booted.
I thought maybe I could avoid the 4.3 OTA by flashing CWM via heimdall. I followed the CM directions for d2vzw at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw, basically I did the following:
heimdall flash --ABOOT aboot.mbn --no-reboot
heimdall flash --BOOT boot.img --no-reboot
heimdall flash --RECOVERY recovery-clockwork-6.0.4.5-d2vzw.img
However when I try to boot into recovery mode, I get the android character with spinning globe. I only saw the picture long enough to pull the battery.
Any suggestions on this on? It looks like the confirmation for OTA sets something, and it appears that whatever I did above either was wrong, didn't happen properly, or is ignored at this point. If I boot back into download mode I still see custom binary no, and current/system binary official.
I would like to get this to CWM and CM 10.2, but suspect it is too late ... can anyone tell me how to work around this, or should I just bite the bullet and reboot to see if the OTA updates at this point?
Thanks for any help you can advise on ....
vax1170 said:
Hello all,
Short story, wife had the 4.3 OTA nag popup, accidentally hit 'ok' and pulled battery before unit booted.
I thought maybe I could avoid the 4.3 OTA by flashing CWM via heimdall. I followed the CM directions for d2vzw at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw, basically I did the following:
heimdall flash --ABOOT aboot.mbn --no-reboot
heimdall flash --BOOT boot.img --no-reboot
heimdall flash --RECOVERY recovery-clockwork-6.0.4.5-d2vzw.img
However when I try to boot into recovery mode, I get the android character with spinning globe. I only saw the picture long enough to pull the battery.
Any suggestions on this on? It looks like the confirmation for OTA sets something, and it appears that whatever I did above either was wrong, didn't happen properly, or is ignored at this point. If I boot back into download mode I still see custom binary no, and current/system binary official.
I would like to get this to CWM and CM 10.2, but suspect it is too late ... can anyone tell me how to work around this, or should I just bite the bullet and reboot to see if the OTA updates at this point?
Thanks for any help you can advise on ....
Click to expand...
Click to collapse
Boot into download mode (vol down + Home + power button). Do you see this? If you see the last 2 lines you are on 4.3
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
buhohitr said:
Boot into download mode (vol down + Home + power button). Do you see this? If you see the last 2 lines you are on 4.3
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
Click to expand...
Click to collapse
No not quite. I don't see the last few lines. My eyes are a bit old but what I see is only:
ODIN MODE
product name: SCH-I535
custom binary download: no
current binary: Samsung official
System status: Official
QUALCOMM secureboot ENABLE
And nothing else after that (just the green antroid graphic and 'downlaoding....')
Thank you for the fast response
vax1170 said:
No not quite. I don't see the last few lines. My eyes are a bit old but what I see is only:
ODIN MODE
product name: SCH-I535
custom binary download: no
current binary: Samsung official
System status: Official
QUALCOMM secureboot ENABLE
And nothing else after that (just the green antroid graphic and 'downlaoding....')
Thank you for the fast response
Click to expand...
Click to collapse
Seems like the 4.3 didn't make it. You can boot up the phone and re check..Once phone is up just turn off wifi and 4g to prevent the OTA.
buhohitr said:
Seems like the 4.3 didn't make it. You can boot up the phone and re check..Once phone is up just turn off wifi and 4g to prevent the OTA.
Click to expand...
Click to collapse
Sorry I wasn't clear ....
I believe the phone already had the OTA software downloaded and staged for install. It was popping up that nag screen that asks to run the update. My wife pressed 'OK' on that and as the phone shutdown and brought up the 'samsung' splash screen, the battery was pulled.
It was after this that I attempted to follow the CM directions to flash the older bootloader and CWM. However I don't think it was successful.
After running the procedure, I attempt to boot into recovery. I am expecting to see the usual CWM menu, however I don't. I get the android with the spinning globe in the belly. I am thinking, the flash with CWM didn't take, and the OTA is now attempting to install.
If possible I would like to flash CWM and then load up CM 10.2 from an internal SD card I've prepared.
Let me know what you think .... thanks!
vax1170 said:
Sorry I wasn't clear ....
I believe the phone already had the OTA software downloaded and staged for install. It was popping up that nag screen that asks to run the update. My wife pressed 'OK' on that and as the phone shutdown and brought up the 'samsung' splash screen, the battery was pulled.
It was after this that I attempted to follow the CM directions to flash the older bootloader and CWM. However I don't think it was successful.
After running the procedure, I attempt to boot into recovery. I am expecting to see the usual CWM menu, however I don't. I get the android with the spinning globe in the belly. I am thinking, the flash with CWM didn't take, and the OTA is now attempting to install.
If possible I would like to flash CWM and then load up CM 10.2 from an internal SD card I've prepared.
Let me know what you think .... thanks!
Click to expand...
Click to collapse
It's possible that the 4.3 bootloader already flashed and it's in the process of flashing the rom when you pulled the battery. In any case, if the software is half done you phone won't boot, and if you attempt to flash the old rom, you will brick your phone if the bootloader already locked. So you need to turn it on to see where you at or you can take a chance and try to Odin old stock rom, again if the bootloader already locked you will brick your phone and if not then you will be back to the older version. I would turn it on and see.
Thanks.
Is there anyway to tell for sure if the bootloader is the new one?
Fortunately I have 2 other S3's I can compare against. One is a 32g S3 with OTA 4.3. The other is a 32g S3 I picked up preinstalled with CWM/CM10. The hosed up phone is a 16g S3.
Can I pull something down from these phones with heimdall to check/compare if the 4.3 bootloader is there? I already did a print-pit on all 3 phones, but from what little I know it seems like the only differences are likely due to the memory sizes. 32 vs 16.
If there is no way to tell, then perhaps I'll reboot it and see..... thanks for the help,
vax1170 said:
Thanks.
Is there anyway to tell for sure if the bootloader is the new one?
Fortunately I have 2 other S3's I can compare against. One is a 32g S3 with OTA 4.3. The other is a 32g S3 I picked up preinstalled with CWM/CM10. The hosed up phone is a 16g S3.
Can I pull something down from these phones with heimdall to check/compare if the 4.3 bootloader is there?
If there is no way to tell, then perhaps I'll reboot it and see..... thanks for the help,
Click to expand...
Click to collapse
If you don't see the last 2 lines like I mentioned above, it should be the old bootloader...since the timing you pull the battery, no one really know what state it's in unless you boot it up.
Am I correct in assuming that the 3 heimdall statements I executed above should have resulted in CWM coming up when I do the up-home-power?
The CM instructions for d2vzw are not clear if you really need to let heimdall reboot the phone between each step. I was trying to avoid a full reboot as I expected the OTA to take over if I did.
Perhaps I should reboot it; if it boots up into anything, at least I can sell it ....
vax1170 said:
Am I correct in assuming that the 3 heimdall statements I executed above should have resulted in CWM coming up when I do the up-home-power?
The CM instructions for d2vzw are not clear if you really need to let heimdall reboot the phone between each step. I was trying to avoid a full reboot as I expected the OTA to take over if I did.
Perhaps I should reboot it; if it boots up into anything, at least I can sell it ....
Click to expand...
Click to collapse
Yes, you can boot up now and see what's going on...
So it looks like it is bricked to some degree. What might you advise to undo this?
When I power the phone up I see the usual Samsung galaxy logo, then the screen goes black with pulsing blue LED.
If I boot into recovery, I see the android with spinning globe for about 60sec, then the dead android with red triangle, and phone resets.
If I boot into download mode, it still comes up with the same messages I indicated above. It looks like the boot loader is not new. I can connect with heimdall and print-pit, so something is still alive here.
What is your best advice here? At this point, I don't think I care if it is put back to stock 4.1.2 or upgraded; booting and working with anything is fine.
Thanks
vax1170 said:
So it looks like it is bricked to some degree. What might you advise to undo this?
When I power the phone up I see the usual Samsung galaxy logo, then the screen goes black with pulsing blue LED.
If I boot into recovery, I see the android with spinning globe for about 60sec, then the dead android with red triangle, and phone resets.
If I boot into download mode, it still comes up with the same messages I indicated above. It looks like the boot loader is not new. I can connect with heimdall and print-pit, so something is still alive here.
What is your best advice here? At this point, I don't think I care if it is put back to stock 4.1.2 or upgraded; booting and working with anything is fine.
Thanks
Click to expand...
Click to collapse
I would try to use Odin and flash MF1 full firmware here http://www.androidfilehost.com/?fid=23134718111254196
Thanks for confirming ... I was poking around the forums and figured I should probably try the procedure to completely reflash my device back to stock. I'll try that later tonight. Thanks again ... crossing my fingers
[RESOLVED]
Looks like flashing the 4.1.2 stock image worked, device boots now!
There was somewhat unexpected behavior however, I don’t know if this is interesting or not. I followed the usual directions to use Odin to flash the full MF1 stock rom; this took about 8-10 min to complete.
On reboot, I saw the tiny blue message at top, and the phone appeared to start in recovery mode, at which point the android graphic with spinning belly globe came up. The progress bar went the full length (no error) and phone rebooted. Phone seemed to reboot fine with typical Samsung and LTE logos. When the phone came up, I was surprised. After unlocking the screen, I got a pop-up indicating that the phone update failed. I then found that all my old data was still available; wi-fi passwords, apps, account syncing, etc. everything. I was expecting the device to be wiped clean with the flash - but maybe I misunderstood. Download mode still seems to report the same messages as before (so it looks like it hasn’t been locked). Needless to say, I hit airplane mode and disabled WiFi, and the phone is not activated, so there is no ability for it to pull the OTA again. If it makes any difference, when I flashed this phone it had no SIM card, and it also had a new 1gb SD card I left in there which was populated with CWM and CM images.
Some summary details to anyone who is interested:
- Phone was running stock 4.1.2 MF1, it received the 4.3 OTA package and was popping up the request to update. Accidentally hit ‘ok’ and phone started reboot sequence to apply update. On phone startup, battery was pulled to prevent update.
- Attempted to run the CM 10.2 d2vzw procedure to flash older bootloader and CWM using heimdall. Transferred just fine, but this didn’t appear to work. Upon entering recovery mode, the android graphic comes up and attempts to do something, but fails.
- On reboot, the phone has pulsing blue LED; bricked
- ODIN’ed the stock 4.1.2 image back, and phone is un-bricked, pops up message on failed update, and all previous data is retained.
If there is any other information from this that could be useful to developers let me know. The phone will not be put back into service for some time, and I can transfer off or adb anything someone might find interesting. Just let me know and I'll try to retried and post here.
Thanks for the help!
vax1170 said:
Looks like flashing the 4.1.2 stock image worked, device boots now!
There was somewhat unexpected behavior however, I don’t know if this is interesting or not. I followed the usual directions to use Odin to flash the full MF1 stock rom; this took about 8-10 min to complete.
On reboot, I saw the tiny blue message at top, and the phone appeared to start in recovery mode, at which point the android graphic with spinning belly globe came up. The progress bar went the full length (no error) and phone rebooted. Phone seemed to reboot fine with typical Samsung and LTE logos. When the phone came up, I was surprised. After unlocking the screen, I got a pop-up indicating that the phone update failed. I then found that all my old data was still available; wi-fi passwords, apps, account syncing, etc. everything. I was expecting the device to be wiped clean with the flash - but maybe I misunderstood. Download mode still seems to report the same messages as before (so it looks like it hasn’t been locked). Needless to say, I hit airplane mode and disabled WiFi, and the phone is not activated, so there is no ability for it to pull the OTA again. If it makes any difference, when I flashed this phone it had no SIM card, and it also had a new 1gb SD card I left in there which was populated with CWM and CM images.
Some summary details to anyone who is interested:
- Phone was running stock 4.1.2 MF1, it received the 4.3 OTA package and was popping up the request to update. Accidentally hit ‘ok’ and phone started reboot sequence to apply update. On phone startup, battery was pulled to prevent update.
- Attempted to run the CM 10.2 d2vzw procedure to flash older bootloader and CWM using heimdall. Transferred just fine, but this didn’t appear to work. Upon entering recovery mode, the android graphic comes up and attempts to do something, but fails.
- On reboot, the phone has pulsing blue LED; bricked
- ODIN’ed the stock 4.1.2 image back, and phone is un-bricked, pops up message on failed update, and all previous data is retained.
If there is any other information from this that could be useful to developers let me know. The phone will not be put back into service for some time, and I can transfer off or adb anything someone might find interesting. Just let me know and I'll try to retried and post here.
Thanks for the help!
Click to expand...
Click to collapse
You're a lucky son of .....lol.
Related
Yesterday I got the update on my S3. I am rooted and bootloader unlocked with EZ apps. when I got the update it went into EZ recovery and thinking maybe I could get the update I tried to install it. It looked like alot of it installed but it did kick me out in the end, or gave me an error or something. Anyway when I went to see if the update had gone through under info I saw I was on G1 still not G7 and it said I had an error 401. So I didn't think it had gone through. I tried to change my phone to CM-10 nightlies by invisiblek just now and followed all the steps in the tutorial and when I did my final reboot I get a exclamation point in a sign and a quote, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. I know there is a way to load to easy recovery and I will find that and go back to where I was but I thought I should post this as I have been researching quite a bit and hadn't seen this happen to anyone else. Maybe I missed it but just in case maybe this will help someone else. If someone could respond on how to boot into ez recovery I will do that or if someone has a different idea on what I should do I'm open to suggestions. Thanks in advance...
OK, read something about download mode so tried that. Power-Volume down-Home at same time. Screen came up asking if I wanted to install a custom OS and warning that a custom OS could be dangerous. Same exclamation point thing as not authorized so maybe another Verizon message? Anyway I said yes and it went to Downloading... screen and says do not turn off target. In the upper left hand corner it says Odin mode, product name: SCH-I535, Custom binaryDownload: no, Current Binary: Samsung official, System status: Official, Qualcomm secureboot: enable...
I'm guessing this is how you get into ODIN but as I have never done that and don't have the phone connected to my computer now I'm guessing it's safe to shut off my phone even though it says Do not turn off target!!!
Anyone know how I get to the bootloader? I'm guessing I can load my saved boot from there...UGH!
Tried shutting down phone but it won't. Do I have to remove battery?
Got Odin open but since my backup is a nandroid backup don't see how I can get to it through ODIN. I'm really stuck. Haven't pulled the battery yet as I was hoping someone would chime in here but guess I will have to soon. THere must be a way to get to the bootloader screen as why else would you do a nandroid backup? I also did a full backup on Titanium Backup bt again how do I get there?
OK loaded root66 through odin...phone restored...now what do i need to do to get cm10 on here....
Went and looked at phone under settings and that build was different now and the 401 error was gone so I installed CM10 and it's loading now! Yeah for me
Odin would be your best bet, if you can do that you should be golden, as to recovery ,I believe it's hold volume down, home then power button hold till you feel the vibration then release that should take you to either recovery or download mode.to Odin you need download mode.hope this helps a little
Sent from my SCH-I535 using xda premium
Hey guys,
I am totally freaking out because I was trying to flash my phone back to a somewhat stock position to erase it and just sort of get back to a stock place and then start flashing again. I tried keeping all the different instructions straight and I think I got turned around someplace.
This is where I am at for what is going on:
Flashed the VRALEC bootchain after I flashed the Stock rooted rom root66_VZW_I535VRBMB1.tar.md5.
The phone currently is accessible for the Odin download mode and when it boots I show the Samsung logo with the lock logo that is unlocked. I am totally not sure where to go from here and need some serious help with what to do next. The phone seems to be simply stock at booting on the 4Glte screen with the Verizon logo.
Any help would be very much appreciated as I am so mixed up as to what to do I don't know where to go and I don't want to make matters worse.
:crying:
NeCr0mStR said:
Hey guys,
I am totally freaking out because I was trying to flash my phone back to a somewhat stock position to erase it and just sort of get back to a stock place and then start flashing again. I tried keeping all the different instructions straight and I think I got turned around someplace.
This is where I am at for what is going on:
Flashed the VRALEC bootchain after I flashed the Stock rooted rom root66_VZW_I535VRBMB1.tar.md5.
The phone currently is accessible for the Odin download mode and when it boots I show the Samsung logo with the lock logo that is unlocked. I am totally not sure where to go from here and need some serious help with what to do next. The phone seems to be simply stock at booting on the 4Glte screen with the Verizon logo.
Any help would be very much appreciated as I am so mixed up as to what to do I don't know where to go and I don't want to make matters worse.
:crying:
Click to expand...
Click to collapse
Pull the battery, boot into recovery (hold volume Up, power, and home), then do a Factory reset.
SlimSnoopOS said:
Pull the battery, boot into recovery (hold volume Up, power, and home), then do a Factory reset.
Click to expand...
Click to collapse
Booting into recovery gives me some message about unauthorized software as I had tried that. I was trying this method but the VRALF bootchain was showing as invalid. I just found a copy of it on invisiblek's site and flashed that and was going to continue with that method trying to get this working. I will update once that has gone through as the stock.vzw_root66.tar image is flashing now. Wish me luck!
Ok, so this time when it finished flashing it rebooted, then it showed the android with the spinning hexagon type thing that you would see when doing a rom backup or something of the sort. I pulled the battery rebooted and did a factory reset along with wiping cache directory and now I am waiting at the 4Glte screen again... Keeping fingers crossed and hoping this works.
AND OMG AWESOME!!!!!
Man, now it is time to get back to flashing. Thank you so much SlimSnoopOS for that last thing I was missing, I really appreciate it.
Hey guys,
I managed to f*** up my phone and don't know exactly what went wrong. I'm worried it's a hard brick, but don't know for sure. It won't turn on though, which is freaking me out. I hope one of y'all can help.
So I was running CM10.1 for a long time and everything was great. I eventually installed an update through the built-in CM updater app, decided I didn't like it, and attempted to re-install through the .zip I still had on my sdcard. I'm still not sure why, but doing so put me in a boot-loop. I was pretty busy at the time so just flashed back to stock. Wasn't ideal, but worked fine.
So now I have some free time and decided I'd try to re-install CM. Prior to the install attempt, I was running 4.1.2 stock, rooted and with an unlocked bootloader. Here's what I did:
1: Flashed the VRALEC bootloader, as recommended by the CM wiki, through Odin.
-At this point, everything still worked OK. I think this next step is where I went wrong.
2: Flashed the VRALF2 kernel through Odin.
-This is what I think I did wrong. After I flashed it, instead of booting up the phone got past the Galaxy S3 graphic then the LED just slowly changed from blue to light blue and back. Either way, I still was able to do the following steps.
3: Flashed CWM 6.0.1.2 through Odin.
4: Installed CM10.2 and gapps from recovery.
5: Rebooted, stuck in a boot-loop showing the CM logo.
So hindsight being 20/20, this is where I should have stopped and asked for help. Instead, I decided that I'd try to fix it myself and tried to flash back to stock. When I tried to do so, Odin said it failed. I then reflashed the VRALEC bootloader, again through Odin. This was successful, but after it rebooted, it showed the Galaxy S3 graphic for a bit and then went blank. Since then, I can't get the phone to turn on or enter download or recovery modes.
Can anyone help? I'm really worried I hard-bricked my phone. What do I need to do / where can I go from here?
Update - Maybe not hard-bricked!
berichardson13 said:
Since then, I can't get the phone to turn on or enter download or recovery modes.
Click to expand...
Click to collapse
So I've managed to get the phone into recovery mode, which is the factory recovery (not CWM). And I can also get into download mode. But when I start up the phone, it stops at the "Samsung Galaxy S III" graphic and just stays there. From that screen, I can only get it to turn off by taking out the battery.
Hopefully this means I'm not hard-bricked. Does anyone know what I can do from here to get it functional again?
berichardson13 said:
So I've managed to get the phone into recovery mode, which is the factory recovery (not CWM). And I can also get into download mode. But when I start up the phone, it stops at the "Samsung Galaxy S III" graphic and just stays there. From that screen, I can only get it to turn off by taking out the battery.
Hopefully this means I'm not hard-bricked. Does anyone know what I can do from here to get it functional again?
Click to expand...
Click to collapse
If you can get into recovery/download, you are definitely not hardbricked. Try to do a factory reset in recovery. If that doesn't work try to ODIN a full stock image.
*your internal storage will be wiped with a factory reset (obviously).
I'm pretty sure they recommend flashing the newer CM's from the MF1 base. I might be making that up though.
Sounds like you forgot to flash something, check the thread you used again
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
If you have a blue led light after the Samsung galaxy s3 screen when it goes black then you don't have the proper drivers for your screen which would be in the file you didn't flash
Sent from my SCH-I535 using XDA Premium 4 mobile app
BattsNotIncld said:
If you can get into recovery/download, you are definitely not hardbricked. Try to do a factory reset in recovery. If that doesn't work try to ODIN a full stock image.
Click to expand...
Click to collapse
Tried the factory reset, ended up in the same spot. So, next I'll try flashing back to stock.
I've done this before, but after the scare earlier I'm being overly paranoid - am I going to need to flash a different kernel? Or is it gonna be enough to just flash something like the VRBMF1 image?
Flash back to stock 4.1.2, use Casual to root and unlock, and get a recovery.
http://forum.xda-developers.com/showthread.php?p=42791826
Sent from my Last Ever Samsung Device.
0331 said:
use Casual to root and unlock, and get a recovery.
Click to expand...
Click to collapse
So this is another dumb question. But having just downloaded the newest version of Java to my Windows 7 computer, I still can't get Casual to open. Instead, this command prompt dialogue box pops up for a little bit then disappears. Nothing else happens after that. I'm opening it with JRE 1.7 - should I be doing something differently?
Edit - I just opened it in terminal, got it going fine, but can't get Casual to recognize my phone. I'm about to update the drivers, see if that does the trick.
berichardson13 said:
So this is another dumb question. But having just downloaded the newest version of Java to my Windows 7 computer, I still can't get Casual to open. Instead, this command prompt dialogue box pops up for a little bit then disappears. Nothing else happens after that. I'm opening it with JRE 1.7 - should I be doing something differently?
Edit - I just opened it in terminal, got it going fine, but can't get Casual to recognize my phone. I'm about to update the drivers, see if that does the trick
Click to expand...
Click to collapse
If it still doesn't work, try the slightly older version of Casual: http://rootzwiki.com/topic/44201-★-casualroot-unlock-recovery-1-click-all-otas★/
Sent from my SCH-I535 using Tapatalk 4
There are a couple other guides on here but they are mostly just links to videos or ad infested download links and none of them worked for me so this is how I ended up getting it to work. Everything I used is attached
For the more experienced readers it's simple, flash TWRP using Odin, boot into recovery and TWRP will prompt you to root.
For the only slightly experienced:
Boot into Download Mode (Hold Vol Down +Power to turn on the Device)
Unzip the TWRP Recovery Image after downloading it below.
Connect your tablet to your PC, unzip and run Odin, click the PDA button and select the TWRP md5 file you just unzipped.
Begin holding the Volume Up button on your Tablet and hit the start button in Odin (this will ensure you reboot into the new recovery)
Once in TWRP if you select the reboot option under advanced you should be prompted to root your device if it's not already rooted. If that doesn't happen for some reason you can use adb to sideload the SuperSU zip I've attached, or put it on an sd card and find the flash zip from sdcard option in TWRP to flash it.
Thanks Justin! Works great. Someone should sticky this.
Luckily I had a Windows computer I could use for this, but my main machine is a MacBook Pro. I wish someone would do a nice clear walkthrough like this one for using Heimdall on a Mac.
To start I have rooted many phones but am stumped on this tablet. After getting it to start with holding the volume down and power key it stops on the downloading screen. Once I can get it to reboot I held the volume up and power key and got into system recovery. If I am not mistaken I can boot from here also. Right??
Thanks it was very useful!
Will this trigger the Knox 0x1 problem? I just got this tablet and I want to be able to take it in to Sprint for repairs if I need to.
Thanks!!!
Justin Buser said:
There are a couple other guides on here but they are mostly just links to videos or ad infested download links and none of them worked for me so this is how I ended up getting it to work. Everything I used is attached
For the more experienced readers it's simple, flash TWRP using Odin, boot into recovery and TWRP will prompt you to root.
For the only slightly experienced:
Boot into Download Mode (Hold Vol Down +Power to turn on the Device)
Unzip the TWRP Recovery Image after downloading it below.
Connect your tablet to your PC, unzip and run Odin, click the PDA button and select the TWRP md5 file you just unzipped.
Begin holding the Volume Up button on your Tablet and hit the start button in Odin (this will ensure you reboot into the new recovery)
Once in TWRP if you select the reboot option under advanced you should be prompted to root your device if it's not already rooted. If that doesn't happen for some reason you can use adb to sideload the SuperSU zip I've attached, or put it on an sd card and find the flash zip from sdcard option in TWRP to flash it.
Click to expand...
Click to collapse
Thanks for the help! This is my first root I've done myself and it works like a charm. Now my next step is to flash it to any carrier. Does anyone know how to flash the sprint device to a different carrier? If anyone could help me out, that would be greatly appreciated.
Thanks for this. I finally got a couple Galaxy Tab 3's (One 210 and one 217) to upgrade my girls from their Kindle Fires.
Really needed this root to remove all the factory loaded crap.
Thanks.
colt223 said:
Thanks for this. I finally got a couple Galaxy Tab 3's (One 210 and one 217) to upgrade my girls from their Kindle Fires.
Really needed this root to remove all the factory loaded crap.
Thanks.
Click to expand...
Click to collapse
I just recently got this tablet from a deal sprint had. What version was your tablet on before rooting? Right now mine is on 4.2.2, but there is an update out. I dont want to update if it wont work with this root.
slickdealers said:
I just recently got this tablet from a deal sprint had. What version was your tablet on before rooting? Right now mine is on 4.2.2, but there is an update out. I dont want to update if it wont work with this root.
Click to expand...
Click to collapse
I believe it was on 4.2.2 when I rooted. I will have to double-check that when I get home tonight.
What model number do you have? I had to use a different TWRP download for each one of mine, meaning I had to find a different one for the 210.
colt223 said:
I believe it was on 4.2.2 when I rooted. I will have to double-check that when I get home tonight.
What model number do you have? I had to use a different TWRP download for each one of mine, meaning I had to find a different one for the 210.
Click to expand...
Click to collapse
My model number is T217S. I tried to do some extra googling and came up with a post saying that the update after 4.2.2 installed KNOX on their tablet, which made their tablet come up with errors when trying to root. Based on your answer and what I found, I'm assuming I'm alright to give it a try. I do have one other question though. After rooting do you know if it would be possible to unroot incase I have to go back to Sprint with a problem?
slickdealers said:
My model number is T217S. I tried to do some extra googling and came up with a post saying that the update after 4.2.2 installed KNOX on their tablet, which made their tablet come up with errors when trying to root. Based on your answer and what I found, I'm assuming I'm alright to give it a try. I do have one other question though. After rooting do you know if it would be possible to unroot incase I have to go back to Sprint with a problem?
Click to expand...
Click to collapse
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.
colt223 said:
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.
Click to expand...
Click to collapse
Just tried it and successfully rooted! I got the same message that you described about Knox. It appears when you go to update SuperSu. Thank you for the help!
For anyone else wondering about going back to stock, I found a thread to the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2512172
I found the answer in another thread. Flashing TWRP will trip Knox.
Didn't work for me
I did the TWRP stuff and all it did was trigger that warranty bit. Still no root.
colt223 said:
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.
Click to expand...
Click to collapse
Yeah, same story here. After flashing TWRP then installing SuperSU first via the TWRP option by booting directly to recovery before OS after flashing TWRP through odin.....then once I clicked the SuperSU app after the OS loaded I chose first the "play" option to update SuperSU then the TWRP option to install the binary update. When it next booted it informed me that Knox was installed and asked whether to disable or not..I said yes and haven't had any problems at all...just trying to find a good ROM now^^
awesome thanxs for the info..... now if we could only get cm11 on this puppy
Root Failure, odd case
I have twins - they are both, identically:
Software Version: T217VPUAMH9
Hardware Version: T217S.04
Model Number: SM-T217S
Android Version: 4.2.2
Baseband Version: T217SVPUAMH9
Kernel Version: 3.4.0-1458241
Build Number: JDQ39.T217SVPUAMH9
Jim Trotter III-style, I-DENTICAL!
I successfully rooted one with:
1: Enable debugging
2: Boot into Download Mode (from poweroff, hold Vol Down+Power)
3: terminal: sudo heimdall flash --RECOVERY ./T217S.TWRP2.7.0.0.flashable/recovery.img
4: poweroff ; boot to TWRP. From TWRP, wipe [factory reset], then install: ./root/SuperSU-v1.93.zip
With the second (apparently evil) twin, at the heimdall command, I get:
...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%
ERROR: Failed to send file part packet!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Re-attaching kernel driver...
On the device, the blue progress bar grows to about 2% and stops.
I even tried using a different cable in case one had gone wonky, to no avail.
I am at a total loss here.
... and SUCCEED, but via strangeways
...
So, mounting frustration.
I tried instead a slightly different version of TWRP:
$ sudo heimdall flash --RECOVERY recovery/T217S.TWRP.2.7.0.0.recovery/recovery.tar.md5
This time the result is different, but still no success:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
... but it stuck at 100% and did not continue. Device also stuck.
^C, hard reboot of device.
Tried again to double check, same result - sticks at 100%, progress bar on device sticks at somewhere around 5%.
Aware of the possible futility, but bored, I tried first one again:
$ sudo heimdall flash --RECOVERY ./T217S.TWRP2.7.0.0.flashable/recovery.img
SUCCEED.
So, apparently it has to be "knocked loose"?
Dunno. I'm in. Hope this helps someone else.
Root NB8
This won't work with NB8 EDIT: I was wrong this does work on NB8
Apparently had to reinstall the drivers a few times to get it to take on Windows. Still no clue what the issue was with Heimdall.
I have a razr hd. I can boot into ap fastboot but thats it. Anything else it sits on red m logo. Cant boot into recovery or anything. I can flash xml using one of matts utility without any fails but rebooting just sits on red m.Please help.
meat-rack said:
I have a razr hd. I can boot into ap fastboot but thats it. Anything else it sits on red m logo. Cant boot into recovery or anything. I can flash xml using one of matts utility without any fails but rebooting just sits on red m.Please help.
Click to expand...
Click to collapse
we are going to need a bit more information to possibly help you.
what did you do to get into this predicament?
are you locked or unlocked?
if locked, what was your system version prior to the issue?
bweN diorD said:
we are going to need a bit more information to possibly help you.
what did you do to get into this predicament?
are you locked or unlocked?
if locked, what was your system version prior to the issue?
Click to expand...
Click to collapse
Same issue for me after OTA. Just processed the OTA as normal and phone will not climb out of the Red M loop. Non rooted, locked device. Attempted to utilize RSD with a few flash files and no luck. Very inexperienced with this. Sorry to be so dense, just looking for any direction possible.
Slickville said:
Same issue for me after OTA. Just processed the OTA as normal and phone will not climb out of the Red M loop. Non rooted, locked device. Attempted to utilize RSD with a few flash files and no luck. Very inexperienced with this. Sorry to be so dense, just looking for any direction possible.
Click to expand...
Click to collapse
i wish i could help you but without knowing exactly what the ota flashed before failing, any advice i give has the real possibility of making your phone worse or possibly perma bricked. the problem is you are locked and we dont yet have a fxz for kk.
that being said, if you still want to try and fix it against my advice i will tell you what to try but I AM NOT RESPONSIBLE IF THIS BRICKS YOUR PHONE OR MAKES IT WORSE IN ANY WAY.
download this xml file http://www.mediafire.com/view/p217akcxwmijcr7/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC_DOWN.xml
download the 9.30.1 ota from sbf droid devs
extract it to a folder and DELETE the xml file, then copy the one above into the folder
make sure you have the latest rsd, i think its 6.1.5 (not positive)
load the xml file into rsd and flash as usual
if this does not work, there is no way to fix your phone until the kk fxz is leaked, assuming this doesnt make it worse.
6.1.6 is the newest RSDLite I've seen.
Go here if you haven't applied the OTA yet and your bootloader is locked.
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
If you have applied the OTA and you're locked, don't do it. You'll have to wait for the FXZ to come out. Otherwise, it will brick even further.
If you have applied the OTA AND your bootloader is UNLOCKED, then you can use the tool to flash back to stock 9.30.1.
I too am bricked. unrooted and locked. Ran the ota and when it reset, it now hangs at the red M. Can get into fast boot and recovery. Tried factory restore and wipe cache. Once I did that my phone now randomly boots to andy all opened up, waiting for me to press the buttons to go into recovery. If I leave it like that, it just reboots after a time and does it all over again . I'm going to assume the only way forward is the xfz file? Any body have an idea of when that might become available and where about I can pick it up? I.E. which forum might have it and will it be a new thread?
Grimaldus3320 said:
I too am bricked. unrooted and locked. Ran the ota and when it reset, it now hangs at the red M. Can get into fast boot and recovery. Tried factory restore and wipe cache. Once I did that my phone now randomly boots to andy all opened up, waiting for me to press the buttons to go into recovery. If I leave it like that, it just reboots after a time and does it all over again . I'm going to assume the only way forward is the xfz file? Any body have an idea of when that might become available and where about I can pick it up? I.E. which forum might have it and will it be a new thread?
Click to expand...
Click to collapse
This has been posted many times. When installing the OTA manually via recovery, a few things happen:
The first time you apply the OTA in recovery, it replaces the recovery with a new recovery and reboots the phone. This new recovery requires a new key combo to get into it. The new key combo is vol-up + power.
So, after you attempt to apply the OTA the first time, you need to be around so when it reboots into the Andy screen, you can use the new key combo. Otherwise, if you leave it alone, it will reboot and then you'll see the red Moto logo which means you'll have to reboot the phone and then hold vol-up + power to get the boot menu and select "Recovery" and then go to the next step.
After getting back into the new recovery, you must apply the OTA again so it can continue to upgrade your phone. After this, you'll be upgraded to Kit Kit.
iBolski said:
This has been posted many times. When installing the OTA manually via recovery, a few things happen:
The first time you apply the OTA in recovery, it replaces the recovery with a new recovery and reboots the phone. This new recovery requires a new key combo to get into it. The new key combo is vol-up + power.
So, after you attempt to apply the OTA the first time, you need to be around so when it reboots into the Andy screen, you can use the new key combo. Otherwise, if you leave it alone, it will reboot and then you'll see the red Moto logo which means you'll have to reboot the phone and then hold vol-up + power to get the boot menu and select "Recovery" and then go to the next step.
After getting back into the new recovery, you must apply the OTA again so it can continue to upgrade your phone. After this, you'll be upgraded to Kit Kit.
Click to expand...
Click to collapse
Right. By reading your earlier posts instructions I got into recovery. That is how I was able to factory reset and wipe cache. I'm talking about AFTER I did all that, instead of just being hung at red m screen, it hangs for a few seconds, then flickers, hangs a few more seconds, and then goes into andy screen. If I don't touch it for a few minutes, it reboots, and that same process starts over, ending with the andy screen again...Its like it WANTS me to be in recovery to fix it .
I noticed you also said to others that us lot are pretty much screwed until the fxz file is out, which I assume is this OTA as a zip so we can flash with recovery? Any idea when that will be coming out? and where should I look for it once its out?
Heck, because I was unrooted and locked and it was the official OTA from verizon, maybe I should go in to them and demand they replace my phone with the moto x. Though, I rather liked my razr hd and don't quite wanna give up on it...
Grimaldus3320 said:
Right. By reading your earlier posts instructions I got into recovery. That is how I was able to factory reset and wipe cache. I'm talking about AFTER I did all that, instead of just being hung at red m screen, it hangs for a few seconds, then flickers, hangs a few more seconds, and then goes into andy screen. If I don't touch it for a few minutes, it reboots, and that same process starts over, ending with the andy screen again...Its like it WANTS me to be in recovery to fix it .
I noticed you also said to others that us lot are pretty much screwed until the fxz file is out, which I assume is this OTA as a zip so we can flash with recovery? Any idea when that will be coming out? and where should I look for it once its out?
Heck, because I was unrooted and locked and it was the official OTA from verizon, maybe I should go in to them and demand they replace my phone with the moto x. Though, I rather liked my razr hd and don't quite wanna give up on it...
Click to expand...
Click to collapse
No, the FXZ is the full kit-kat image, not an update like the OTA. The FXZ can be used to flash your phone back to full stock, whether you are locked or not. If you are locked, then you can only flash the version that is currently on your phone or newer. You cannot flash back to a previous version unless your bootloader is unlocked.
The ota is used to only update a previous version to the current version, in this case from JB to KK, but once it's applied, you cannot apply it again since you are already upgraded to that version. It's only an upgrade, not a full image like an FXZ.
iBolski said:
No, the FXZ is the full kit-kat image, not an update like the OTA. The FXZ can be used to flash your phone back to full stock, whether you are locked or not. If you are locked, then you can only flash the version that is currently on your phone or newer. You cannot flash back to a previous version unless your bootloader is unlocked.
The ota is used to only update a previous version to the current version, in this case from JB to KK, but once it's applied, you cannot apply it again since you are already upgraded to that version. It's only an upgrade, not a full image like an FXZ.
Click to expand...
Click to collapse
I see, makes sense. Every days a school day I suppose. Thanks for the info. Guess I have to decide to either wait for the FXZ or go to verizon and see if they can get me a new phone.
Same thing happened to my wife, completely stock now stuck at red m. After calling verizon they suggested the factory reset which just gives you a boot to dead android guy to get into recovery on every boot. Then after a couple minutes just reboots and does the same thing, stuck in a loop. They then said it's not their software, rather Motorola's, so Verizon's only recourse is to sell me an overpriced refurb or upgrade to the edge plan. Screw them. I said unacceptable and they gave me a number for Motorola. Moto said that they put in a request to extend my factory warranty because it was the software update that caused the issue and they will let me know tomorrow. I understand stuff happens, but this is not acceptable when their harassing update causes thee issue. I knew I should've unlocked the boot loader on it when I had the chance.
al2fast said:
Same thing happened to my wife, completely stock now stuck at red m. After calling verizon they suggested the factory reset which just gives you a boot to dead android guy to get into recovery on every boot. Then after a couple minutes just reboots and does the same thing, stuck in a loop. They then said it's not their software, rather Motorola's, so Verizon's only recourse is to sell me an overpriced refurb or upgrade to the edge plan. Screw them. I said unacceptable and they gave me a number for Motorola. Moto said that they put in a request to extend my factory warranty because it was the software update that caused the issue and they will let me know tomorrow. I understand stuff happens, but this is not acceptable when their harassing update causes thee issue. I knew I should've unlocked the boot loader on it when I had the chance.
Click to expand...
Click to collapse
Then you're almost there. At the "dead android" screen, press and hold vol up and then press power and then release both buttons. This gets you into recovery.
At this point, reinstall the OTA via the recovery so it can start into the 2nd stage and then you'll be done.
iBolski said:
Then you're almost there. At the "dead android" screen, press and hold vol up and then press power and then release both buttons. This gets you into recovery.
At this point, reinstall the OTA via the recovery so it can start into the 2nd stage and then you'll be done.
Click to expand...
Click to collapse
I don't know how to reinstall the OTA via stock recovery. I tried it do the install update.zip option and nothing happened. Any pointers would be appreciated.
al2fast said:
I don't know how to reinstall the OTA via stock recovery. I tried it do the install update.zip option and nothing happened. Any pointers would be appreciated.
Click to expand...
Click to collapse
Did you download it to your phone? If so, it needs to be on your external SD card and you choose the option to install from there. You'll have to navigate to where you stored it on the external SD card.
If you didn't download it, then you should be able to push it via ADB PUSH when in the recovery. Just hook up your phone to your PC and do it that way. Just obtain the OTA from this thread. Somewhere, someone provided a link to it. Download it to your PC and then do an adb push to the external SD card of the OTA and then install it that way.
iBolski said:
Did you download it to your phone? If so, it needs to be on your external SD card and you choose the option to install from there. You'll have to navigate to where you stored it on the external SD card.
If you didn't download it, then you should be able to push it via ADB PUSH when in the recovery. Just hook up your phone to your PC and do it that way. Just obtain the OTA from this thread. Somewhere, someone provided a link to it. Download it to your PC and then do an adb push to the external SD card of the OTA and then install it that way.
Click to expand...
Click to collapse
Thanks for the tips. I must have done something wrong when I installed adb, I could not see the phone with the adb devices command, yet I could see the phone in the Matt utility as well as in RSD Lite. I'll give it a shot again, can't hurt. Called Moto and they escalated it and are sending me a replacement device.