Related
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?
Hello everyone!
I need some help rooting my tf300t, because what I've read here and there was somewhat useless, since everyone sais different stuff. For first I'd like to ask for your help in clarifying which one is first. I have read guides in which rooting was first than pushing the recovery, and I have read ones in which fasbooting recovery was the first thing to do, and than flashing su. I have tried both methods, with no luck. When I try to fastboot twrp onto my device, it sais 'waiting for device'. I read that this means fastboot is not properly configured, but I am an administrator on my PC and I have the proper drivers, since adb reboot-bootloader works. So thats for flashing twrp first. Then rooting first. I tried with motochopper, but that does no work on 10.6.1.27.5. So I tried pushing root files manually, but when adb shell /data/local/temp, it sais failure. So if you could help me, of what did I do wrong, I'd greatly appreciate it.
Shad0w32 said:
Hello everyone!
I need some help rooting my tf300t, because what I've read here and there was somewhat useless, since everyone sais different stuff. For first I'd like to ask for your help in clarifying which one is first. I have read guides in which rooting was first than pushing the recovery, and I have read ones in which fasbooting recovery was the first thing to do, and than flashing su. I have tried both methods, with no luck. When I try to fastboot twrp onto my device, it sais 'waiting for device'. I read that this means fastboot is not properly configured, but I am an administrator on my PC and I have the proper drivers, since adb reboot-bootloader works. So thats for flashing twrp first. Then rooting first. I tried with motochopper, but that does no work on 10.6.1.27.5. So I tried pushing root files manually, but when adb shell /data/local/temp, it sais failure. So if you could help me, of what did I do wrong, I'd greatly appreciate it.
Click to expand...
Click to collapse
First make sure that you have unlocked your bootloader (text in the upper right corner of boot screen). What I did first was flash TWRP from ADB. In your case, you would flash the stock ROM, and then flash SU.
cmendonc2 said:
First make sure that you have unlocked your bootloader (text in the upper right corner of boot screen). What I did first was flash TWRP from ADB. In your case, you would flash the stock ROM, and then flash SU.
Click to expand...
Click to collapse
I know I'm unlocked sorry for not mentioning that, though even that was strange, because the unlock device app should have wiped the memory, but it didn't, and still unlocked. But I don't exactly understand what you mean by flashing the stock ROM, then SU. And if you mean that do that with twrp, I can't because fastboot flash recovery twrp.blob just waits for device. Is there another method which I can flash it with? Thanks in advance
Shad0w32 said:
I know I'm unlocked sorry for not mentioning that, though even that was strange, because the unlock device app should have wiped the memory, but it didn't, and still unlocked. But I don't exactly understand what you mean by flashing the stock ROM, then SU. And if you mean that do that with twrp, I can't because fastboot flash recovery twrp.blob just waits for device. Is there another method which I can flash it with? Thanks in advance
Click to expand...
Click to collapse
If it says "waiting for device," your PC is not communicating with the tab. What Windows version do you use? Does "fastboot device" command from fastboot mode on tab return any serial number? It should show a serial number before you can flash TWRP onto the tab. And where did you read that unlocking the device would wipe the memory?
Get fastboot to work first, then you can flash whatever. Otherwise, if you're on stock recovery, try loading the rom zip file onto your sd card and flash it using RCK option. If you have no idea what I'm talking about, read first, so you don't brick your tab just because you have no idea what the heck you're doing.
graphdarnell said:
If it says "waiting for device," your PC is not communicating with the tab. What Windows version do you use? Does "fastboot device" command from fastboot mode on tab return any serial number? It should show a serial number before you can flash TWRP onto the tab. And where did you read that unlocking the device would wipe the memory?
Get fastboot to work first, then you can flash whatever. Otherwise, if you're on stock recovery, try loading the rom zip file onto your sd card and flash it using RCK option. If you have no idea what I'm talking about, read first, so you don't brick your tab just because you have no idea what the heck you're doing.
Click to expand...
Click to collapse
For first, I downgraded my device, so I could root it with motochopper. Then I flashed recovery with the way explained here:http://forum.xda-developers.com/showthread.php?t=1845377
Now twrp seems to be working, i can start it, but it cant mount anything, so i cant flash anything from the device. Both 2.5 and 2.4.4 does this. Goo manager cant find a recovery for this device, so i cant use that either. Fastboot still cant see my tab. Im on windows 7, with proper drivers
Nevermind my stupidity, I installed the wrong recovery, not the one for the 4.2 bootloader. By now I'm a proud owner of a tf300t with cyanogenmod on it Thank you both though, for trying to help
So I rooted my nexus 5 but when I check to see if it is rooted, I get this message. When I go to the bootloader and try to go to the recovery mode, I get the opened android with red sign saying "no command".
I read that I have to flash the latest SuperSU......any ideas how I am supposed to do that?
am3606 said:
So I rooted my nexus 5 but when I check to see if it is rooted, I get this message. When I go to the bootloader and try to go to the recovery mode, I get the opened android with red sign saying "no command".
I read that I have to flash the latest SuperSU......any ideas how I am supposed to do that?
Click to expand...
Click to collapse
are you sure that you "rooted" it, or did you just unlock the bootloader? thgat open android with the red sign is the stock recovery btw. what you need to do is flash a custom recovery via fastboot, either twrp or cwm, then flash the latest supersu via your new custom recovery. thats all that you need to do.
latest supersu http://download.chainfire.eu/supersu
Well I rooted it but due to some problems had to reset the whole thing. Before I reseted it, I had SuperSU installed and it said that the device was rooted.
I can't access the bootloader is the problem, when I go to recovery mode I go to the "stock recovery" with the android with the red sign saying no command. So am I suppose to place the zip file using android file transfer?
am3606 said:
Well I rooted it but due to some problems had to reset the whole thing. Before I reseted it, I had SuperSU installed and it said that the device was rooted.
I can't access the bootloader is the problem, when I go to recovery mode I go to the "stock recovery" with the android with the red sign saying no command. So am I suppose to place the zip file using android file transfer?
Click to expand...
Click to collapse
to access the bootloader, power off first. then power on holding the volume down button and the power button. that is the bootloader. thats what gives you the options to go into recovery, reboot bootloader, boot up, or power off. in order for you to be able to flash the latest supersu, you need to flash a custom recovery first.
simms22 said:
to access the bootloader, power off first. then power on holding the volume down button and the power button. that is the bootloader. thats what gives you the options to go into recovery, reboot bootloader, boot up, or power off. in order for you to be able to flash the latest supersu, you need to flash a custom recovery first.
Click to expand...
Click to collapse
Oh I know about the bootloader I did it before its just that I can't access the recover, when I go to it in the bootloader I go to the android with the red sign.
How do I flash a custom recovery?
am3606 said:
Oh I know about the bootloader I did it before its just that I can't access the recover, when I go to it in the bootloader I go to the android with the red sign.
How do I flash a custom recovery?
Click to expand...
Click to collapse
you need to flash it via fastboot while your phone is in the bootloader(there are instruction here). follow the "installing a custom recovery" part http://forum.xda-developers.com/showthread.php?t=2507905
am3606 said:
Oh I know about the bootloader I did it before its just that I can't access the recover, when I go to it in the bootloader I go to the android with the red sign.
How do I flash a custom recovery?
Click to expand...
Click to collapse
You must have flashed a custom recovery before to flash root.
If you're confused at this moment , its a good idea to put your phone down and get a cup of tea.
Then, read the how to unlock your bootloader / root thread stuck at the top of general.
Read through it. To have been rooted, you must have done all that stuff before. It has instructions for each step. But importantly, read don't do until you're familiar with it all
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
If you're confused at this moment , its a good idea to put your phone down and get a cup of tea.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
thats one of the best pieces of advice ive read!
sometimes, just taking a step back, a breather, a time out, opens your eyes to things right in front of you that you dont see. plus gives you a chance to read up and make yourself better prepared.
rootSU said:
...its a good idea to put your phone down and get a cup of tea...
Click to expand...
Click to collapse
You're so damn civilized across the pond. It's enviable.
You can also download the app "Goo Manager", in the settings menu there is an option to install the latest TWRP recovery. ☺
Sent from my Nexus 5
you can use nexus root toolkit to unlock bootloader and flash supersu:
am3606 said:
So I rooted my nexus 5 but when I check to see if it is rooted, I get this message. When I go to the bootloader and try to go to the recovery mode, I get the opened android with red sign saying "no command".
I read that I have to flash the latest SuperSU......any ideas how I am supposed to do that?
Click to expand...
Click to collapse
We have to know all the setps you´ve done to get root.
1. download SuperSU.zip to your sdcard
2. Unlock bootloader - reboot afterwards done?
3. download a recovery.img, CWM or TWRP
4. Back to bootloader and flash recovery: fastboot flash recovery nameofrecovery.img
5. in bootloader boot now to recovery and select install/SuperSU.zip
6. Reboot and and you are ready to go
All-in-One-Thread here is a link which should help you to get started :good:
Pls report back if you get it sorted :highfive:
---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------
iburtondroid said:
you can use nexus root toolkit to unlock bootloader and flash supersu:
Click to expand...
Click to collapse
Sure, roottoolkit works, but you dont learn something with using toolkits. You dont know what they are doing.
There are easy fastboot commands
fastboot oem unlock
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
........
so nothing special, no toolkits needed
lichti1901 said:
We have to know all the setps you´ve done to get root.
1. download SuperSU.zip to your sdcard
2. Unlock bootloader - reboot afterwards done?
3. download a recovery.img, CWM or TWRP
4. Back to bootloader and flash recovery: fastboot flash recovery nameofrecovery.img
5. in bootloader boot now to recovery and select install/SuperSU.zip
6. Reboot and and you are ready to go
All-in-One-Thread here is a link which should help you to get started :good:
Pls report back if you get it sorted :highfive:
---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------
Sure, roottoolkit works, but you dont learn something with using toolkits. You dont know what they are doing.
There are easy fastboot commands
fastboot oem unlock
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
........
so nothing special, no toolkits needed
Click to expand...
Click to collapse
agree, I have just proposed him, if he is not sure what he was doing wrong, also, correct me if I am wrong, but maybe he didn't enable developer options (not sure if this is a must for other steps he needs to take)
Developer Options are only applicable when Android is booted, has no bearing on things when in fastboot. They also have no bearing on root.
If the OP doesn't know what they're doing then they should read up on everything and LEARN the adb/fastoot commands. It takes all of 10 minutes reading to know the basics and will hold you in good stead for future Android handsets
PhilipTD said:
You're so damn civilized across the pond.
Click to expand...
Click to collapse
Well I couldn't say shoot up and rob a granny now could I?
</poor taste>
rootSU said:
Well I couldn't say shoot up and rob a granny now could I?
</poor taste>
Click to expand...
Click to collapse
LMAO
lichti1901 said:
We have to know all the setps you´ve done to get root.
1. download SuperSU.zip to your sdcard
2. Unlock bootloader - reboot afterwards done?
3. download a recovery.img, CWM or TWRP
4. Back to bootloader and flash recovery: fastboot flash recovery nameofrecovery.img
5. in bootloader boot now to recovery and select install/SuperSU.zip
6. Reboot and and you are ready to go
All-in-One-Thread here is a link which should help you to get started :good:
Pls report back if you get it sorted :highfive:
---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------
Sure, roottoolkit works, but you dont learn something with using toolkits. You dont know what they are doing.
There are easy fastboot commands
fastboot oem unlock
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
........
so nothing special, no toolkits needed
Click to expand...
Click to collapse
mysd card? I thought all I needed is the usb...
I was in class much of yesterday and of today so forgive me for the update.
Downloading the SDK and just downloaded the twrp recovery.img.
TCWadey said:
You can also download the app "Goo Manager", in the settings menu there is an option to install the latest TWRP recovery. ☺
Sent from my Nexus 5
Click to expand...
Click to collapse
you can, but you need root for it to work. the name of this thread is.. "Nexus 5 "No SU binary installed and SuperSU? cannot Install it".
@PhilipTD @rootSU, Sorry to bump this thread, but I had to lol :laugh::laugh::laugh:
So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader
Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"
danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.
Okay will try that. Thanks man.
Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.
Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?
Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader
Hi guys, i need help.
My tablet has only temporary recovery installed after flashing 3.1.1. I can boot to OS just fine, but there's no permanent recovery even the stock one. I can install twrp but only temporarily. everytime i reboot to recovery, it only shows a dead android with exclamation point above it.
I have to flash again every time i want to use recovery.
I came from stock rooted 1.2.1 image with twrp 2.8.7.1 without any problem.
I hope anyone is kind enough to point out where am i doing it wrong.
I just flashed 3.1.1 stock image using this thru fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
and then twrp using:
fastboot flash twrp-2.8.7.1.img
Try copying SuperSU zip to your tablet. Then flash TWRP again, but do not reboot. Go immediately into recovery (which should be TWRP) and flash the zip, then reboot.
koop1955 said:
Try copying SuperSU zip to your tablet. Then flash TWRP again, but do not reboot. Go immediately into recovery (which should be TWRP) and flash the zip, then reboot.
Click to expand...
Click to collapse
Wow thanks a lot. That actually did the trick
bonkeng said:
Wow thanks a lot. That actually did the trick
Click to expand...
Click to collapse
I say this with a smile on my face, but why does everyone seem so surprised whenever I a right about something?
In the folder where I keep my ROM/OTA updates, I always have:
1) SuperSU.zip - to give me and maintain root. And also...
2) Nomoreota.zip (from here: http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489) which will eliminate the kill-switch file.
When I flash an update, I then flash the other two zips. Not necessary if you are flashing a ROM, of course, but important if you are flashing an OTA. It only adds seconds to the process and prevents a brick.
koop1955 said:
I say this with a smile on my face, but why does everyone seem so surprised whenever I a right about something?
In the folder where I keep my ROM/OTA updates, I always have:
1) SuperSU.zip - to give me and maintain root. And also...
2) Nomoreota.zip (from here: http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489) which will eliminate the kill-switch file.
When I flash an update, I then flash the other two zips. Not necessary if you are flashing a ROM, of course, but important if you are flashing an OTA. It only adds seconds to the process and prevents a brick.
Click to expand...
Click to collapse
I'm sorry if i may have offended you. This was my first time trying this method.
Thanks to you, now I know exactly what to do
bonkeng said:
I'm sorry if i may have offended you. This was my first time trying this method.
Thanks to you, now I know exactly what to do
Click to expand...
Click to collapse
No offense at all, I was saying that in jest. Really. (I have an odd sense of humor.)
Just to complete your understanding (and I am glad that I could help) installing SuperSu roots the tablet. Without root, it was not accepting the custom recovery.