Related
Let's start with the beginning.
I rooted my phone, installed a custom rom and then installed again the official rom. I updated to official ICS and the phone tells me that it's still rooted. I have the Superuser app that didn't work. In the app lists it doesn't show any apps. When I am using a root needing app it doesn't ask me to gain root access. I tried to root it again but when I am using the "fastboot oem unlock" command it is telling me "waiting for device" (the phone is in bootloader. The bootloader says that it is Unlocked).
Because that didn't worked i tried to enter into the recovery menu from bootloader but this didn't worked either. It shows me a very short animation (something like a warning) and then it goes black and the touchsensitive buttons remain bright.
I tried to flash the recovery with cmd but the same problem.. waiting for device.
I factory reseted the phone but still the same trouble.
I've seen a lot of people with this problems.. but only one of them..if superuser doens't work you need recovery to fix and if recovery doesn't work you need cmd to solve. the bootloader doesn't respond to the commands sent from cmd and I can't solve any of these problems. (the adb drivers for usb are installed)
Can anyone help me to solve this please?
you want to be using: fastboot flash recovery recovery.img
Download the latest 5.0.2.0 CWM and flash it through terminal. You want to do this on the bootloader menu (where it says bootloader unlocked) while the usb is connected. Now straight away go into recovery and flash the latest superuser.zip. Now reboot, su should work fine and make sure the superuser app is updated. Rename /system/etc/install-recovery.sh and reflash CWM (Rom Manager or through fastboot again).
Now you're rooted and will have a permanent recovery.
Thx. very helpful! If anyone else have the same problem just use this http://forum.xda-developers.com/showthread.php?t=1407192
I'm posting this in a single thread to minimize clutter.
I recently ran Easy Ace Root tool as instructed on my inspire. The bootloader unlocked, CWM flashed, but there was an error during superuser flash.
After a reflash of superuser things looked okay, but superuser began not responding. I re-flashed superuser twice in attempt to fix it using the Easy Ace Root Tool.
EDIT: I have discovered that superuser will only function with "USB debug mode" enabled. I've tried it on and off several times, and each time it malfunctions but function returns without a problem.
The backup I have been restoring seems to work because it was created with the debug mode enabled. Took a while to see it.
Second, CWM started to exhibit the "power off, charge" recovery bug where CWM opens.
Last, I attempted to install/flash 4ext Recovery Touch twice to address the CWM bug. Both times it hung at "flashing recovery" (approx 20 mins. both times). Eventually, it indicated that 4ext was installed. However, booting into recovery shows that I still have CWM. I used two different versions (RC8 & RC 7) in the attempt.
I'm now using the restored and working ROM. Solutions to the superuser debug issue I haven't seen posted
The failure to flash 4ext is troubling.
Questions
1. Could these issues be related? Or, what should I be looking for?
2. The recovery issue seems to be the most important. What might be the cause of 4ext to fail in this manner?
3. Can the Easy Ace Root Tool be rerun on the unlocked bootloader, and would that fix anything?
4. Is there reason to worry about flashing with CWM?
I see a number of possible solutions, the main one is to flash a new ROM, which I have already downloaded a couple, but doesn't adress the recovery problems.
The issue with CWM and 4ext leave me less than confident in using it to flash with, although CWM seems okay. The other item is that some ROMs indicate that S-off in required, but many of the threads are a couple years old.
5. Is it correct that S-off is not required to flash ROMs (I read it somewhere)?
I found an answer: NO, YOU DON'T NEED S-OFF TO FLASH ROMS....
Solving the issues are good lessons
Stock AT&T ROM
Android 2.3.5, Sense 3.0
Bootloader screen indicates-
UNLOCKED
S_ON
I know that's a lot for one thread but I'm just looking for a direction and I'll do the search.
If anyone has suggestions, directions, or ideas fire away.
Thanks
I think the fact that you are still S-ON is causing problems with the recovery flashing, since S-ON basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-ON still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)
Evil_ryan said:
I think the fact that you are still S-OFF is causing problems with the recovery flashing, since S-OFF basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-OFF still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)
Click to expand...
Click to collapse
Thanks, I think you meant to say the fact that I am still S-ON? The S_ON part shouldn't be an issue from all that I've gathered. In fact, that's how I have CWM. The Easy Ace Root Tool does CWM, with an unlocked bootloader S_ON. Nothing I have come across states that S_OFF is required to flash 4ext recovery.
Other noobs might find this other thread useful as there is some info and links to recovery images. http://forum.xda-developers.com/showthread.php?p=22489317#post22489317
No I haven't tried the fastboot yet. That is an option, I've got it and adb setup on my computer already. I have looked at AAHK, but as it says its no longer supported, and I don't think I need of S_OFF. Taking it slow to sort out the problems so I don't do sumthin stooopid.
How are you flashing 4ext? From fastboot?
Right, S-ON, that's what I get for writing this at 12 AM.
Don't bother with AAHK, it's discontinued, and even if you still had a copy it couldn't download the necessary files.
bananagranola said:
How are you flashing 4ext? From fastboot?
Click to expand...
Click to collapse
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.
Cremnomaniac said:
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.
Click to expand...
Click to collapse
Try doing it from fastboot.
bananagranola said:
Try doing it from fastboot.
Click to expand...
Click to collapse
I thought that would be next.
Can you confirm for me that the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1848846 are correct for the Inspire 4G?
It's the EVO 3D forum. And I have some other links to using fastboot I'll check before doing it.
Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.
Evil_ryan said:
Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.
Click to expand...
Click to collapse
Okay, great. This is the only recovery .img that I have found 4EXT-recovery-2.2.7_RC5.img - 3.33 MB
If I install the 4ext recovery Updater after flashing it should work okay?
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?
Cremnomaniac said:
If I install the 4ext recovery Updater after flashing it should work okay?
Click to expand...
Click to collapse
Probably. But I don't think it really matters, since if you can flash a recovery using fastboot, you can do everything that 4ext updater otherwise would.
Cremnomaniac said:
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?
Click to expand...
Click to collapse
See above.
If 4ext doesn't work, you can also try CWM and TWRP (TeamWin Recovery Project). I use the latter with my Inspire 4g.
I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.
bananagranola said:
I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.
Click to expand...
Click to collapse
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?
Cremnomaniac said:
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?
Click to expand...
Click to collapse
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.
bananagranola said:
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.
Click to expand...
Click to collapse
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?
Cremnomaniac said:
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?
Click to expand...
Click to collapse
No.
bananagranola said:
No.
Click to expand...
Click to collapse
Solved the 4EXT flashing issue. Looks like 4ext flashed okay with fastboot, and the 4EXT Recovery Control works. Rebooted into recovery a couple times just to be sure. That kills 2 birds the CWM bug and the recovery flash.
Thanks for the help and suggestions all.
Some notes from a noobs experience -
Setting up ADB and Fastboot is very easy.
If your cautious as I am run some basic commands in ADB and Fastboot that won't do damage [devices, reboot, reboot-bootloader, etc.]
If you get "error: cannot load 'recovery.img" make sure you navigate to folder that recovery.img is located. Then run "Fastboot flash recovery [Filename]." Even though I set system variables on my desktop to point to adb and fastboot, it won't find the recovery image if you start from the wrong directory in terminal (i.e., C:\)
If you're in ADB and you use the command "adb reboot-bootloader" it will boot the device straight to "Fastboot USB".
Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.
bananagranola said:
Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.
Click to expand...
Click to collapse
Thanks for the reminder. I just spent an hour looking at 4EXT "smartflash no available". I hav some links for doing fastboot flash of the boot.img. I think I'm good there.
One question from my OP remains. Superuser only works (i.e., grants root access) when I have USB debug mode selected. When it's off superuser says the app (e.g., Titanium BU) is granted permission but just hangs until I force close it and re-enable USB debug. i can't find anything on this problem.
Is it an issue to run my phone in USB debug mode all the time? Or, any clue to the problem?
I have unlocked my boot loader which doesn't allow you to use recovery mode. Is there a way to completely wipe the phone and undo the bootloader thing? What program can you use. Also, how can you hide the bootloader unlocked start up screen? Thanks
I want to be sure you have all your ideas straight. How comfortable are you with working from the bootloader or from recovery? What tools do you use? Can you access recovery by this method?: Hold "Power" and "Volume Down" for ten seconds and release. This takes you to the bootloader. Then press "Volume Down" once to select the recovery, then press "Volume Up" to activate that option. This should then boot into the recovery. If that is not what happens, let us know what happens instead.
I have unlocked my boot loader which doesn't allow you to use recovery mode.
Click to expand...
Click to collapse
There should be no problem using any of the various recovery modes with an unlocked bootloader. Stock, TWRP, and CWM should all work fine. Can you describe what you did, what happened, and what you expected to happen?
Is there a way to completely wipe the phone and undo the bootloader thing?
Click to expand...
Click to collapse
There are several things here. You can wipe the phone and return it to factory defaults by using "fastboot -w". This does not change your bootloader or recovery. You can re-lock you bootloader, but it will always register that the bootloader was once unlocked. There is no real benefit to relocking the bootloader so I won't put instructions here, but let me know if that's what you want to do. Finally, you can flash a new recovery image onto your device, which will wipe out whatever recovery image you had on there. The command looks like "fastboot flash recovery recovery.img".
Also, how can you hide the bootloader unlocked start up screen?
Click to expand...
Click to collapse
This is simple as flashing a new logo. The command is "fastboot flash logo logo.bin". This will overwrite the stock logo (which checks if the phone is unlocked) with a modified one which looks the same whether it is unlocked or not.
See here for details and downloads: http://forum.xda-developers.com/showthread.php?t=2548530
FaultyFirmware said:
There should be no problem using any of the various recovery modes with an unlocked bootloader. Stock, TWRP, and CWM should all work fine.
You can wipe the phone and return it to factory defaults by using "fastboot -w". Finally, you can flash a new recovery image onto your device, which will wipe out whatever recovery image you had on there. The command looks like "fastboot flash recovery recovery.img".
The command is "fastboot flash logo logo.bin". http://forum.xda-developers.com/showthread.php?t=2548530
Click to expand...
Click to collapse
I mean fastboot recovery thing if that's what you didnt think.
I can get into the recovery screen fine. Selecting recovery puts me into a no command screen and then just boots up as normally. I was expecting to get another menu with factory reset and cache reset, and factory just boots up normally. Is factory reset from the fastboot screen just the same as the reset in the settings menu? Is it that you cant use those settings with a unlocked bootloader.
Are TWRP and CWN both apps you get for/through rooting in which you can restore back up etc? I have heard about CWN but havent really used it.
Would doing "fastboot -w" just do the same as reset from settings menu? Also I'm not sure what you mean by flash a new recovery image?
Also, I dont understand how to remove the boot loader unlocked screen. You have to start a command prompt and type in that with your phone in fastboot mode?
Is recovery
Sorry for being such stupid noob pleb :good:
I think I understand the problem. The first screen you come to says "Fastboot flash mode" or something like that and has a boot mode selection menu with "Recovery" as one option. This screen is the bootloader. When you are in the bootloader, you use the fastboot command on the computer to do things to the phone.
When you select and activate the "Recovery" option, you get a screen that says "No Command". This is actually the stock recovery. TWRP is TeamWin Recovery Project and CWM is Clockwork Mod. They're both roughly the same in terms to capabilities. Both have far more features than the stock recovery. You can use adb to communicate with your phone in recovery mode.
Here is a program that will help you install the recovery. USB debugging should be turned on on your phone, and you should be booted into the system. Also be sure that the proper USB drivers are installed on your computer.
http://forum.xda-developers.com/showthread.php?t=2635706
Here is the latest version of TWRP. You should download this image and use the above application to flash it.
http://forum.xda-developers.com/showthread.php?t=2561757
As always, ready everything carefully.
Could you explain the remove bootloader screen or how to relock bootloader?
Which one would you recommend: TWRP or CWN? Thanks! :good:
Banana4Life said:
Could you explain the remove bootloader screen or how to relock bootloader?
Which one would you recommend: TWRP or CWN? Thanks! :good:
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2548530
Why you need relock bootloader ?
Use philz recovery based on last cwm. It's amazing.
Could you explain the remove bootloader screen or how to relock bootloader?
Click to expand...
Click to collapse
Here is a thread about removing the warning screen: http://forum.xda-developers.com/showthread.php?t=2548530
In summary, you can either download "logo.zip" and install it from recovery, or you can download "original_logo.zip", extract "logo.bin" and use "fastboot flash logo logo.bin" when you are booted into the bootloader. I am assuming you do not have a "Google Play Edition" or "GPE". If you do, there is a different logo for you in that thread.
The bootloader can be relocked, but it will not change the warning screen. Locking the bootloader will only make it so you cannot flash custom recoveries and such. Can you explain what you hope to achieve by relocking the phone? Again, it can be done, but I want to make sure it is really what you want.
Which one would you recommend: TWRP or CWN? Thanks!
Click to expand...
Click to collapse
You can't go wrong with either TWRP or PhilZ. PhilZ is based on CWM. It has added features and touch capabilities. Because a recovery is so easy to switch, if you make your best guess for which you will like more, and if you are not happy with it, you can switch. I like both, and most users will find all the features they need in either one.
TWRP looks like this: https://www.xda-developers.com/wp-content/uploads/2013/11/AgsV.png
It can be downloaded here: http://forum.xda-developers.com/showthread.php?t=2561757
PhilZ can be downloaded here: http://forum.xda-developers.com/showthread.php?t=2639583
Its features and screenshots are here: http://forum.xda-developers.com/showthread.php?t=2201860
I am not responsible if anything goes wrong.
Post any questions here: [Q&A][ROOT] Root for SHIELD Tablet 2.0 (Lollipop)
Pre-requisites:
Already flashed OTA 2.0 (Unless bootloader is locked in which case read instructions for locked bootloader.)
Unlocked bootloader and flashed CWM from here
SuperSu zip file from here
PC with working adb and fastboot
Instructions (Unlocked bootloader):
Reboot tablet into recovery mode
Code:
adb reboot recovery
Flash SuperSu zip file with CWM
Reboot tablet
If CWM asks to fix root, say yes.
Profit.
Optional Reinstall CWM (The OTA removes it)
Flash via fastboot
Code:
fastboot flash recovery recovery.img
May need to flash a couple of times to get it to stick.
Reboot tablet
Instructions (Locked bootloader):
Download update but DO NOT UPDATE YET
Gain root on previous build via towel root.
Flash CWM from link in prereqs via Flashify
In CWM choose update from zip and choose the zip file in the bottom of your 'nvidia' folder on your internal storage (/sdcard/). DO NOT REBOOT
Flash SuperSu zip file with CWM
Reboot tablet
Don't reboot if you want to reinstall CWM below
Profit.
Optional Reinstall CWM
Copy CWM to root of internal storage
Code:
adb push recovery.img /sdcard/
Flash via adb shell
Code:
adb shell
mount /data
dd if=/data/media/0/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
If the mount commands errors with device or resource busy just skip it and move on.
Reboot tablet
that was quick, thanks!
worked perfectly on Shield Tablet WiFi (LRX21M) with unlocked bootloader.
Thanks for the guide. Hopefully this is just me being stupid, but I ran into some issues following the guide. I rooted via TowelRoot, and then downloaded the OTA without flashing it. After using Flashify to install the CWM image, and installing the OTA via CWM, I'm unable to boot into the recovery image anymore. I can't boot into it through the hardware key combo, and I can't boot into it through ADB.
I'm following the locked bootloader steps, if it helps.
Edit: Nevermind, unlocked the Bootloader is by far the easiest option.
Horvaticus said:
Thanks for the guide. Hopefully this is just me being stupid, but I ran into some issues following the guide. I rooted via TowelRoot, and then downloaded the OTA without flashing it. After using Flashify to install the CWM image, and installing the OTA via CWM, I'm unable to boot into the recovery image anymore. I can't boot into it through the hardware key combo, and I can't boot into it through ADB.
I'm following the locked bootloader steps, if it helps.
Click to expand...
Click to collapse
What is happening instead of it booting?
SuperPichu said:
What is happening instead of it booting?
Click to expand...
Click to collapse
it boots to the old "android on it's back with the red triangle icon" screen. It appears that installing the OTA overwrites the recovery image.
garyd9 said:
it boots to the old "android on it's back with the red triangle icon" screen. It appears that installing the OTA overwrites the recovery image.
Click to expand...
Click to collapse
Fantastic. Working on it
Pretty much this.
Ok I think I fixed the locked instructions
What about if we had already updated to L, but had never unlocked the bootloader? I was rooted before with towel root, but never actually unlocked boot. Does the unlocking method still work? Or am I SOL for now?
PuffinNugz said:
What about if we had already updated to L, but had never unlocked the bootloader? I was rooted before with towel root, but never actually unlocked boot. Does the unlocking method still work? Or am I SOL for now?
Click to expand...
Click to collapse
Yes the unlocking method still works. It is not an exploit it is officially "supported" by Nvidia. See here
As mentioned below unlocking will wipe all data.
PuffinNugz said:
What about if we had already updated to L, but had never unlocked the bootloader? I was rooted before with towel root, but never actually unlocked boot. Does the unlocking method still work? Or am I SOL for now?
Click to expand...
Click to collapse
I don't think it should be any different. They didn't encrypt it or anything. Unlocking should be possible with just doing an oem unlock. Of course this will wipe your data, so be sure to do a backup.
For the "locked" method, you might want to suggest re-flashing CWM recovery (if desired) afterwards. The partition name is SOS.
garyd9 said:
For the "locked" method, you might want to suggest re-flashing CWM recovery (if desired) afterwards. The partition name is SOS.
Click to expand...
Click to collapse
Not a bad idea. Adding it.
SuperPichu said:
Fantastic. Working on it
Click to expand...
Click to collapse
I'm having the same problem just flashing the recovery. Fastboot says it flashed ok, but when I reboot into recovery I get the android on his back with the red triangle.
touretts69 said:
I'm having the same problem just flashing the recovery. Fastboot says it flashed ok, but when I reboot into recovery I get the android on his back with the red triangle.
Click to expand...
Click to collapse
I assume you are using the unlocked instructions? Try flashing it a couple of times. Mine was doing the same thing at first. You can also try the CWM flashing instructions for locked as that may "stick" better.
Thanks for the method, worked fine - WIFI version.
SuperPichu said:
I assume you are using the unlocked instructions? Try flashing it a couple of times. Mine was doing the same thing at first. You can also try the CWM flashing instructions for locked as that may "stick" better.
Click to expand...
Click to collapse
A few more flashes fixed the issue. Thanks!
flakz0r said:
Thanks for the method, worked fine - WIFI version.
Click to expand...
Click to collapse
Was your bootloader locked or unlocked?
SuperPichu said:
Was your bootloader locked or unlocked?
Click to expand...
Click to collapse
Unlocked.
Just flashed boot.img for EU LTE. Root is working! Thanks!
i have purchased yuphoria and it comes with updated rom yng1tbs2p2 . i have unlocked it and when i've tried to flash custom recoveries , i have no success for any of recoveries available for yuphoria. there is no official twrp that works with new update and i have requirement of custom recovery. can anyone port any custom recovery for new update???
dharmang1910 said:
i have purchased yuphoria and it comes with updated rom yng1tbs2p2 . i have unlocked it and when i've tried to flash custom recoveries , i have no success for any of recoveries available for yuphoria. there is no official twrp that works with new update and i have requirement of custom recovery. can anyone port any custom recovery for new update???
Click to expand...
Click to collapse
Here you go ....
http://forums.yuplaygod.com/threads/recovery-twrp-2-8-7-0-for-yu-yuphoria-01-08-15.13974/
I have tried this recovery but my phone is rebooted in stock recovery everytime, i also used flashboot -i 0x2a96 boot recover.img method but this also not worked becaused my phone remain in fastboot mode instead of rebooting in recovery mode and also my phone is remain in fastboot mode even after dettach the data cable.
dharmang1910 said:
I have tried this recovery but my phone is rebooted in stock recovery everytime, i also used flashboot -i 0x2a96 boot recover.img method but this also not worked becaused my phone remain in fastboot mode instead of rebooting in recovery mode and also my phone is remain in fastboot mode even after dettach the data cable.
Click to expand...
Click to collapse
Maybe your bootloader is not unlocked.
I have also that doubt so i have run oem unlock command again but that said unlocked and dont ask confirmation of press volume up button to start unlock. And if you tried flas recovery command while your bootloader is locked then you got error said that you have to unlock bootloader to do this. You can not complete the flashing process. I have rooted all of my phones and never face such problem.
dharmang1910 said:
I have also that doubt so i have run oem unlock command again but that said unlocked and dont ask confirmation of press volume up button to start unlock. And if you tried flas recovery command while your bootloader is locked then you got error said that you have to unlock bootloader to do this. You can not complete the flashing process. I have rooted all of my phones and never face such problem.
Click to expand...
Click to collapse
K man actually i don't hav yuphoria for now! I m buying it in this weekend. But i think you can download slimlp rom for yuphoria and extract the boot.img from zip and can flash. I really hav no idea of how to flash .img file on yu devices. I use slimlp on my xperia z and use flashtool and twrp is its default recovery.i think you will also get twrp recovery after flashing boot.img of slimlp for yuphoria.
porblem solved. Here is link
http://forum.xda-developers.com/yu-yuphoria/general/yuphoria-rooting-guide-method-t3172536