im in bootloader menu on my htc. i lost superuser access, and all root apps wont work either. im tryin to update superuser but cant get anything to work. please help
It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM
If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?
For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.
Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?
If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.
Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en
ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu
Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053
projektorboy said:
It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM
If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?
For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.
Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?
If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.
Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en
ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu
Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053
Click to expand...
Click to collapse
i ran rummer a month or so ago. i had s-off and on bootloader menu it says unlocked. when i click on recovery it just reboots. when i first did this i never flashed twrp. i did a root check when i did rumrunner it said root access granted. now when i check it it says no root access, and my superuser is gone. i tried dl all sdk again, but i cant get comp to find phone in cmp. i also tried to launch rumrunner again ,, it rebooted phone few times then ended with stupid problems with phone press enter to exit. im about to throw in towel after hours of trying different things..
projektorboy said:
It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM
If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?
For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.
Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?
If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.
Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en
ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu
Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053
Click to expand...
Click to collapse
this also all started after verizon came out with update and phone automatically updated but unsuccusfully
Thank you for re-affirming my suspicion that an OTA put you in this position.
Rumrunner wasn't ever going to help you in your situation. Rumrunner is purely for achieving S-OFF. Since you're still S-OFF, it didn't have anything to do with your phone. Your root access is gone because the OTA wiped it out. It's important to always be careful about OTA updates because OTA updates assume that you NEVER modified your phone and will write whatever they want to wherever they want.
Since you can at least get to the bootloader, your phone can be saved. You said that you tried to update your SDK so that you could have the fastboot files available. When you run the SDK updater (I assume you're on Windows) you have to right-click and run as Administrator to make it work.
The files you want for fastboot are hiding in c:\program files (x86)\Android\android-sdk\platform-tools\
Take adb.exe, fastboot.exe, adbwinapi.dll, and adbwinusbapi.dll and copy them to a separate folder. (Such as C:\adb\) Navigate to that folder and do shift+right-click in a blank area of the folder so you can run a command prompt. You will want to put a ROM and a recovery file in this same folder too. (You sound like you want the stock ROM)
Use the command 'fastboot devices' to see if the phone shows up. If the phone doesn't show up, then you need to go to the HTC Website so you can install HTC Sync, then remove Sync (while leaving the drivers behind) so that your phone has the correct drivers to make it show up in fastboot.
If 'fastboot devices' ends up revealing a device, then you can grab a custom recovery image file and do "fastboot flash recovery filename.img" to put a custom recovery in your phone. Then within the custom recovery you can do adb sideload romname.zip to install a ROM and that should put your phone back into a usable state.
projektorboy said:
Thank you for re-affirming my suspicion that an OTA put you in this position.
Rumrunner wasn't ever going to help you in your situation. Rumrunner is purely for achieving S-OFF. Since you're still S-OFF, it didn't have anything to do with your phone. Your root access is gone because the OTA wiped it out. It's important to always be careful about OTA updates because OTA updates assume that you NEVER modified your phone and will write whatever they want to wherever they want.
Since you can at least get to the bootloader, your phone can be saved. You said that you tried to update your SDK so that you could have the fastboot files available. When you run the SDK updater (I assume you're on Windows) you have to right-click and run as Administrator to make it work.
The files you want for fastboot are hiding in c:\program files (x86)\Android\android-sdk\platform-tools\
Take adb.exe, fastboot.exe, adbwinapi.dll, and adbwinusbapi.dll and copy them to a separate folder. (Such as C:\adb\) Navigate to that folder and do shift+right-click in a blank area of the folder so you can run a command prompt. You will want to put a ROM and a recovery file in this same folder too. (You sound like you want the stock ROM)
Use the command 'fastboot devices' to see if the phone shows up. If the phone doesn't show up, then you need to go to the HTC Website so you can install HTC Sync, then remove Sync (while leaving the drivers behind) so that your phone has the correct drivers to make it show up in fastboot.
If 'fastboot devices' ends up revealing a device, then you can grab a custom recovery image file and do "fastboot flash recovery filename.img" to put a custom recovery in your phone. Then within the custom recovery you can do adb sideload romname.zip to install a ROM and that should put your phone back into a usable state.
Click to expand...
Click to collapse
Ty for walk through! Will try tomorrow! I wanna get kit kat on here. I think some problems were from files on comp in wrong folders. Hope this works
Related
'hey guys/girls.
Im new at installing custom ROMS and all that.
I got my desire rooted with unrevoked 3.0 and it worked fine.
I installed a custom ROM and it worked fine,but i didnt like it so I tried a new one.
I can´t remember the name of it but I didnt like that either. Again i found a new ROM i´d like to try but when I turn off my phone and turn it on again trying to get to Hboot/recovery mode or what its called nothing happens i just stay turn off until i remove my finger from volume down buttom, then it just start then phone normally.
Do any one know what to do?
There are a couple of ways.
Way 1
1) Turn off your phone
2) Hold vol down + power until it loads the bootloader
3) When it's finished checking SD card, move to recovery using volume keys and press power to select recovery
4) It should load into recovery
Way 2
1) Have the Android SDK installed with the platform-tools downloaded and working
2) Make sure you plug your phone cable in your phone and PC
3) Open up command prompt or terminal (depending on your OS)
4) Type "adb reboot recovery" (no quotes) and it will reboot to recovery.
i have similar problem, cant access recovery anymore. that happened after installing a custom rom (leedroid). when i try to access recovery phone just hangs up on that red triangle. to turn it on again i have to pull of the battery. btw, phone works normaly itself only problem is that i cant access recovery to install some other rom :/
Drunk Moose said:
i have similar problem, cant access recovery anymore. that happened after installing a custom rom (leedroid). when i try to access recovery phone just hangs up on that red triangle. to turn it on again i have to pull of the battery. btw, phone works normaly itself only problem is that i cant access recovery to install some other rom :/
Click to expand...
Click to collapse
The red triangle is the stock recovery, so you're actually in recovery there.
Download a recovery and read this. Should get recovery back on your phone again.
but i had normal recovery i installed dozens of custom roms :/ and now phone just stucks in that screen with phone and triangle :/
How the hell can you install custom roms with the stock recovery.
thats the point, i had normal recovery and now i cant access it im using custom roms from the times desire was released and now almost after a year this **** happened :/
Ok... 2 posts ago I linked you to an article that can get the a custom recovery back onto your phone.
can u explain me info in that link a little? what .zip file do i need and where to get it? and WTF is terminal?
1) Download Clockwork Recovery or if you have PVT4 download Amon_RA (GSM)
2) Put it on your SD card
3) Download terminal emulator from the market
4) Type "su" (without quotes) and press allow when it comes up
5) Type "flash_image recovery /sdcard/recovery.img" (without quotes) and it will write the file to your phone.
To check which PVT you have, boot into bootloader. Turn off phone and hold vol down + power.
installed better terminal emulator pro. downloaded img, renamed it to recovery, inserted it to sdcard in terminal typed:
su (enter)
flash_image recovery /sdcard/recovery.img (enter)
and terminal says:
flash_image: not found
Did you put the img into a folder?
no, in the root of sd card
Weird. I don't know. Just tinker around with it. I tried it once and it worked for me. Check spelling, check in a file manager to see if the file is there.
i think i get this. thing is my rom does not have flash_image. now looking how to get it.
yep, there is no flash_image in system.
Are you using the new Sense ROMS/Gingerbread? If so 'Fast Boot' mode will screw with getting into recovery. I have to hold down volume while replacing the battery or turn off fast boot from within settings....
OFC if you have no recovery image anymore this won't help one little bit
KYI
yes im using new leedroid gb. i turned off that fast boot, its not that :/ now trying to push flash_image through adb, but it says "failed to copy....bla bla bla...: out of memmory" getting little desperate
If I was you I would back everything up. Contacts, SMS all that good stuff. I would then use an RUU and get the stock rom back on and just root that. Could of done it by now really.
Ok 2 problems:
1. to the topic starter. The reason you can't access recovery is that your rom uses fast boot up(sleep mode). When this is activated the phone doesn't really shut down when you tell it to, so it also cannot actually enter recovery or fastboot. Just turn it off in the settings menu and you'll be fine.
2. to Drunk Moose.
You have the original htc-recovery installed. I bet that you rooted back before unrevoked, and you probably have been using fakeflash since then. Try making rom manager dl cwm and choose reboot to recovery from rom manager. It should enter clockwork mod. If that is the case, this means that your phone have a modified version of the stock recovery, which allows test-keys. if that is not the case, and you still get the triangle, you somehow overwrote your recovery with a stock one.
Either way to fix this, you need to replace the recovery image with a cwm one. This can only be done in 2 ways for the desire:
1. Use unrevoked even though your phone is rooted and it'll flash it using a known exploit.
2. run alpharev to gain s-off. When you have s-off you will be able to flash the recovery through fastboot or from the system like described by meaple.
The reason it doesn't work for you when you do like meaple descriped, is that the commands tell the phone to use a custom binary called flash_img and passes it the parameters "recovery" and the "recovery.img" file. Then the binary will tell the android system how to write the img file to the recovery partition(it cannot do this entirely by itself). However this bynary is very unlikely to be included on your rom(like you figured out yourself ), so you need to place it somewhere you can access it from the terminal. And even if you had had the file, you wouldn't have been able to do so, as the recovery partition is write-protected doing runtime, when you are s-on.
So I'll recommend that you do one of the 2 mentioned solutions(I'll be glad to provide further help)
edit: and for god sake don't just flash a ruu every time you are in doubt... There are almost certainly an easier solution, and by doing s-off, you can avoid ever having to run a ruu again, as you can restore the system 1 partition at a time if you feel like it.(sorry this was not directed at you but people in general, as meaple just suggested doing so)
in fact i was just trying to use unrevoked bu it stucks on bootloader, tells to check for drivers, despite the drives is installed. :/
p.s. and yes i have rooted my desire almost a year ago there was no unrevoked
any other suggestions? or just try to install ruu?
and about the rom manager, it gets me to the same red triangle. btw the recovery was fine till i installed leedroids rom about a month, and i noticed it only few days ago, when i tryed to update my rom.
hi...
can any1 tell me how to install custom roms using pc...........
i have searched the forum....but couldnt find any answer.................
sorry for starting a new thread........
thanks in advance
General Method:
- find, download and copy a flashable rom called "fullwipe 1.3" to the sd
- copy the zip with the rom you want to load in it to your sd card
- reboot into cwm recovery
- install zip from sd card
- choose the fullwipe 1.3 zip
- install
- then choose the rom's zip
- install
- reboot
wait for it to load. there you go.
For more advanced rom's, you must make directory's on your sd card for them to work properly. Follow instructions posted by the Rom's developer for proper installation.
thanks bro..........4 all ur help..............
1 more question........
what about using it through the fone......
i mean .....after downloading through the rom manager..........should i follow the same procedure ????
question
I rooted today, s-off & eng-off, installed rom manager
what do i have to do to get clockwork to work
I try booting into recovery but, display goes blank & has a red triangle symbol & after many minutes nothing happens..... can some inform me of the step I may have missed or something i can do to verify that i have the device set up properly.
Hopefully Thanks in advance.
gixer131 said:
question
I rooted today, s-off & eng-off, installed rom manager
what do i have to do to get clockwork to work
I try booting into recovery but, display goes blank & has a red triangle symbol & after many minutes nothing happens..... can some inform me of the step I may have missed or something i can do to verify that i have the device set up properly.
Hopefully Thanks in advance.
Click to expand...
Click to collapse
Flash CWM recovery from rom manager again.
Hawks556 said:
Flash CWM recovery from rom manager again.
Click to expand...
Click to collapse
I can appreciate that, but I need to know what to do. I try to do that & i get an error while attempting to run privileged commands. Flashing sounds all great but I cant seem to get it to do anything in recovery... error issues trying to do that, or anything else, I also have super user update issues that say they put a recovery image on the sd card & to go boot that from within recovery.
Just hoping to find out why i cant do the simple things everyone speaks of.
gixer131 said:
I can appreciate that, but I need to know what to do. I try to do that & i get an error while attempting to run privileged commands. Flashing sounds all great but I cant seem to get it to do anything in recovery... error issues trying to do that, or anything else, I also have super user update issues that say they put a recovery image on the sd card & to go boot that from within recovery.
Just hoping to find out why i cant do the simple things everyone speaks of.
Click to expand...
Click to collapse
Well if you can't flash recovery from Rom Manager then there's something wrong with your root privileges or s-offs... Just to make things clear, how did you try to flash the recovery?
AT THE TOP OF THE BOOTLOADER IT MUST SAY "... ENG S-OFF RL" FOR THIS TO WORK
With the device connected, boot into bootloader and select FASTBOOT and press power once.
It will now show FASTBOOT USB, and give you 4 options.
Download the newest 4.x.x.x version of the cwm recovery from the dev section.
Download My Toolkit and Extract to C:\
In the recovery zip that you downloaded from the dev thread, find the "recovery.img" and extract it to the RESOURCE folder of my toolkit. (make sure its only the recovery.img and not the folders it sits in)
open up a command prompt (windows key + R, type "cmd" and hit enter)
type in: cd "C:\HTC ACE TOOLKIT\RESOURCE" and hit enter.
the prompt should now be in that directory.
now type in the following EXACTLY and press enter afterwards:
fastboot flash recovery recovery.img
Let it flash, and badaboom, you have just flash cwm recovery.
JSLEnterprises said:
AT THE TOP OF THE BOOTLOADER IT MUST SAY "... ENG S-OFF RL" FOR THIS TO WORK
With the device connected, boot into bootloader and select FASTBOOT and press power once.
It will now show FASTBOOT USB, and give you 4 options.
Download the newest 4.x.x.x version of the cwm recovery from the dev section.
Download My Toolkit and Extract to C:\
In the recovery zip that you downloaded from the dev thread, find the "recovery.img" and extract it to the RESOURCE folder of my toolkit. (make sure its only the recovery.img and not the folders it sits in)
open up a command prompt (windows key + R, type "cmd" and hit enter)
type in: cd "C:\HTC ACE TOOLKIT\RESOURCE" and hit enter.
the prompt should now be in that directory.
now type in the following EXACTLY and press enter afterwards:
fastboot flash recovery recovery.img
Let it flash, and badaboom, you have just flash cwm recovery.
Click to expand...
Click to collapse
The BOOTLOADER SAYs "... ENG S-OFF but no RL @ the end
Can someone instruct me to what I may have done wrong? I know if I try to s-off or ENG-off I now get a connection problem but the first time I tried it seemed to work properly.
Thanks
Thanks for the help, I have successfuly flached clockwork now & a new rom.... What should I do to update a radio for my device on telus? Thanks
gixer131 said:
Thanks for the help, I have successfuly flached clockwork now & a new rom.... What should I do to update a radio for my device on telus? Thanks
Click to expand...
Click to collapse
well, in that toolkit i told you to download is a command script that does pretty much what I told you do to for the recovery.
Since you and I have the exact same phone I recommend grabbing the radio from the 2.52 korean build (Radio_12.59.60.26U_26.11.04.21_M), and the rill's as well.
Here is the radio and ril (first 2 links, download via the dropbox links): http://forum.xda-developers.com/showthread.php?t=996630
make sure you're in bootloader > fastboot and it says FASTBOOT USB on the screen
take a radio.img from within the zip and drop it into the resource folder and then run the shorcut in the toolkit.
It will now flash the radio to your phone and reboot.
Now with the rill's you flash via cwm recovery, from the RIL zip you downloaded, off your sd card in the same way you would flash a rom.
JSLEnterprises said:
well, in that toolkit i told you to download is a command script that does pretty much what I told you do to for the recovery.
Since you and I have the exact same phone I recommend grabbing the radio from the 2.52 korean build (Radio_12.59.60.26U_26.11.04.21_M), and the rill's as well.
Here is the radio and ril (first 2 links, download via the dropbox links): http://forum.xda-developers.com/showthread.php?t=996630
make sure you're in bootloader > fastboot and it says FASTBOOT USB on the screen
take a radio.img from within the zip and drop it into the resource folder and then run the shorcut in the toolkit.
It will now flash the radio to your phone and reboot.
Now with the rill's you flash via cwm recovery, from the RIL zip you downloaded, off your sd card in the same way you would flash a rom.
Click to expand...
Click to collapse
I would Like to thank you for your help & support, I was a the step of having fastboot usb And on my pc I unziped the radio And droped the image in the resource folder, a window pops up (disk burner) only option to choose is DVD R Drive.... do I have to have the SD card unmouted as a disk drive to the computer?
leave disk burner outta this. lol
The phone should be in bootloader under "fastboot" so the highlighted area will say FASTBOOT USB (since your phone is connected to your pc).
If radio.img is in the RESOURCE folder of my toolkit, go back to the main folder (HTC ACE TOOLKIT) and just double click the "Flash Radio" shorcut.
JSLEnterprises said:
leave disk burner outta this. lol
The phone should be in bootloader under "fastboot" so the highlighted area will say FASTBOOT USB (since your phone is connected to your pc).
If radio.img is in the RESOURCE folder of my toolkit, go back to the main folder (HTC ACE TOOLKIT) and just double click the "Flash Radio" shorcut.
Click to expand...
Click to collapse
Most excellent! Thanks & Thank you, your help has been most usefull & is quite appreciated!
Changed Rom
Changed rom last night & wanted to know weather I should flash the "rill's" & "radio" each time I change roms. I just did the radio now so hope that cures the tinny sound, also it sounded kinda tinny just playing music, is there a patch or something else to do or is all that fixed in the radio?
Any suggestion on roms to try? using Revolution HD right now.
First things first. Im a NOOB, got it. I really want to update to 4.0.4 but haven't been able to acomplish via the posts in the developer forums. I so far have downloaded and installed the GN toolkit, and been able to unlock the bootloader. I have tried to boot to CWM Recovery w/o perm flashing it, to install the update, but I can't get it to work, it just hangs. I don't want to root but I tried that as well via the GN toolkit, it fails out as well. I just want to install the Stock 4.0.4. and relock my bootloader, being back to totally stock, w/the most upto date firmware. PLEASE HELP
1. Go to settings -> about phone -> update (I think, my rom has this feature removed) to get the official OTA from Verizon.
2. If you want to use CWM, you will have to permanently flash it over.
3. If an OTA image is available, you could use fastboot to write it to the system, just make sure you backup everything to a second location as it will often wipe your SD.
flashing CWM is very easy.
download the image for the TORO (galaxy nexus CDMA) version of the nexus from http://www.clockworkmod.com/rommanager
once its downloaded, make sure you are able to use fastboot (should be in the folder for the tool kit)
open a command promt, navigate to the toolkit folder which should have fastboot.exe then type:
fastboot flash recovery cwm-recovery-image-name
let it finish then boot into recovery. this will allow you to flash the 4.0.4 rom.
there is no reason to relock the bootloader and as soon as you boot up, stock recovery will place it self back on the phone since you're not going to root.
Tubes6al4v said:
1. Go to settings -> about phone -> update (I think, my rom has this feature removed) to get the official OTA from Verizon.
2. If you want to use CWM, you will have to permanently flash it over.
3. If an OTA image is available, you could use fastboot to write it to the system, just make sure you backup everything to a second location as it will often wipe your SD.
Click to expand...
Click to collapse
Sadly it isn't truely available OTA. These fourms seem to be the only way it is availble. GN toolkit says it can "boot to CWM Revoery withou Permanently flashing it" but like I said it hangs up on me everytime no matter if I try the standard or the touch version.
Zepius said:
flashing CWM is very easy.
download the image for the TORO (galaxy nexus CDMA) version of the nexus from .....(EDIT)
once its downloaded, make sure you are able to use fastboot (should be in the folder for the tool kit)
open a command promt, navigate to the toolkit folder which should have fastboot.exe then type:
fastboot flash recovery cwm-recovery-image-name
let it finish then boot into recovery. this will allow you to flash the 4.0.4 rom.
there is no reason to relock the bootloader and as soon as you boot up, stock recovery will place it self back on the phone since you're not going to root.
Click to expand...
Click to collapse
the GN toolkit has the disc image file "recovery-cwm-5.5.0.4-toro-lte"
what do you mean when you say make sure I can use fast boot. in the folder I found a application that is named "fastboot-toolkit", but when I click it it opens then closes before I can do anything with it.
also typing in the run box, I'm also not having anyluck, can you be more specific as to what you mean, I tried typing in "fastboot flash recovery cwm-recovery-image-name", and "fastboot flash recovery-cwm-5.5.0.4-toro-lte" because I thought that is the name of the file Im tring to flash, correct?
Is there no way to apply this via the stock recovery?
langman21 said:
the GN toolkit has the disc image file "recovery-cwm-5.5.0.4-toro-lte"
what do you mean when you say make sure I can use fast boot. in the folder I found a application that is named "fastboot-toolkit", but when I click it it opens then closes before I can do anything with it.
also typing in the run box, I'm also not having anyluck, can you be more specific as to what you mean, I tried typing in "fastboot flash recovery cwm-recovery-image-name", and "fastboot flash recovery-cwm-5.5.0.4-toro-lte" because I thought that is the name of the file Im tring to flash, correct?
Is there no way to apply this via the stock recovery?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20632492&postcount=3'
read this post. it should help you get fastboot setup correctly.
and no, there is no way to apply 4.0.4 via stock recovery that i know of.
Status Update....Phone is unlocked, and connected to Computer via USB Debugging is activatied. It is in Fastboot mode, and I have rebooted and went through the initial setup.
I just installed Java Development Kit because it was "required" for the Android SDK tools install which i am setting up now. This is taking a while....
I have copied the fastboot-windows file into the Android platform-tools folder...
in command prompt I get 'fastboot-windows.exe' is not a recognized as an internal or external command, operable program or batch file
looks like I dont need the .exe, it brought up the a bunch of command options...now what?
okay looks like I got fastboot working, and went back into GN Toolkit and flashed CMW recovery. I was able to boot CWM recovery....now where do I save the update so I can find it? I now have the option to choose zip from SDcard.
langman21 said:
okay looks like I got fastboot working, and went back into GN Toolkit and flashed CMW recovery. I was able to boot CWM recovery....now where do I save the update so I can find it? I now have the option to choose zip from SDcard.
Click to expand...
Click to collapse
you'll want to move the .zip file of the 4.0.4 update to anywhere on the SDcard. basically anywhere you'd download something to from your browser on the phone.
once its there, you'll want to make a backup just in case.
once the backup is complete, you should be able to then install from that zip file and be ok.
I have a nexus 7 2013 LTE build KOT49H
I initially managed to unlock and root using nrt 1.8...everything was perfect...there was some confusion getting adb setup though..
(for WugFresh...your instructions are fantastic but you should add a line to "check your device for the message to accept a connection for adb and select ok"...I found myself waiting and waiting, staring at my computer screen thinking that the nrt was hanging when all I needed to do was press "ok" on my device.)
Like I said...everything was perfect but I had to go one step further...
I then installed cyanogenmod 10.2 using twrp...tihs also went fine but I hated it and wanted to get back to my original google os. I had a really hard time getting adb set up once cyanogen was installed but once I finally did I was able to get back to stock again using nrt 1.8.
So now I'm back to stock image KOT49H. Everything runs fine and I see the unlocked logo when I boot so I assume I'm still unlocked.
Here's the problem..
When I try to root now, (I always run the NRT driver test until I get "success" message first) my device hangs on the "Booting modified boot.img to enable..." message.
And I mean hangs...can't even power it down without popping the cover and disconnecting the battery! Thankfully this gets me back to a running device but I still want to root this thing.
Any idea what might be wrong or where I should go to from here?
Thanks for any help you can suggest!
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
mdamaged said:
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Click to expand...
Click to collapse
Thanks for the response...
All these check...I do have to switch to PTP to get adb functional and I do get success on the full driver test before I try rooting...device still hangs at "Booting modified boot.img to enable running privileged commands" message and then wont power down without disconnecting battery...
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
datallboy said:
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestions...
I lost twrp when I went back to stock build.
Sorry...I'm real green at all of this...
You think I should:
power up to fastboot mode...select boot loader mode...then select recovery to see if it boots?
You need to be real clear for me, I'm a total newb
I would need a link to thorough instructions for wiping to factory reset and flashing the supersu.zip...I do have adt installed and have my path modified so that I can run instructions like "adb devices" in a command window but I'm unclear as to where to place files so they will be seen if I try to flash them via adt. (like I say...this is all new to me and I'm not even sure if that last sentence makes sense)
mdamaged said:
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
Click to expand...
Click to collapse
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
SMELZBAD said:
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
Click to expand...
Click to collapse
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest zip, save it to your device (in the root of the sdcard).
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run busybox and see what happens.
Click to expand...
Click to collapse
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
SMELZBAD said:
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
Click to expand...
Click to collapse
Wug's toolkit is doing exactly that, the main difference in doing it manually is we get to see where the problem is.
If this fails then I would probably say you should backup anything on your device you don't want wiped, and try one click restore and try rooting again.
Good luck.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
Click to expand...
Click to collapse
Followed your instructions...everything went as it should until I got to:
fastboot boot openrecovery-twrp-2.6.3.1-deb.img
instead of rebooting the device I only got waiting for device message in command window...
is device supposed to be put in bootloader mode before entering this instruction maybe???
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
SMELZBAD said:
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
Click to expand...
Click to collapse
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
mdamaged said:
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
Click to expand...
Click to collapse
Ya...something likely still abit wacky...I'll be sure to post if anything weird starts happening but for now all is good...I'm definitely rooted though...I was just able to mount a flash drive via Stick Mount and run a video off of it!
info:
Tampered
Unlocked
S-ON
Hboot-3.16.0.0000
Radio-1.16.21331931
CID:T-MOB010 V.1.12.531.19
I wiped everything trying to go back to stock. I can only manage to get to TWRP recovery and tried to use the images but doesn't show up. Tried to install the recovery as a .zip but still no luck. Downloaded android sdk, but don't know how to use it. I just wanted to go back to stock. And my guess was if I could manage to S-Off y could install stock recovery.img, I'm desperate.
Easy.
Boot into TWRP, hit the advanced tab, hit adb sideload.
Open terminal in directory of any rom and type
Code:
adb sideload nameof.zip
nameof.zip is obviously gonna be replaced by the actual name of the zip
Let it do its thing
mikeyinid said:
Easy.
Boot into TWRP, hit the advanced tab, hit adb sideload.
Open terminal in directory of any rom and type
Code:
adb sideload nameof.zip
nameof.zip is obviously gonna be replaced by the actual name of the zip
Let it do its thing
Click to expand...
Click to collapse
Thanks for taking the time to answer me, it didn't work but managed to fix it by putting the back up in TWRP/BACKUPS/[folder with your unique device id/Folder with my actual recovery all I know is I had it un zipped and zipped just in case. But really Thank you I'm so glad I fixed it.