Hey, I'm having a problem with my recovery after I installed the latest android version(also installed custom rom and elementalx kernel, but I don't think it has anything to do with it), when I try to flash recovery, it works basically, but whenever I start the phone it automatically goes into recovery, and the only way to fix it is to flash another boot.img file, it reboots fine when I do it, but then I don't have recovery only the dead red triangle thing(please don't give me the power+vol fix, that's not the solution I'm looking for, as its not a very useful recovery), I tried to flash few recoveries/other boot.img files, but none of them boot regulary + recovery is working..
I doubt its a problem with the boot.img I try to flash, because I tried so many and it didn't worked, anyway, I need someone to help me with that, thanks a lot.
Using android 5.1.1 btw.
Be specific in detailing what you've done and the results. The way you're describing things leads me to think that you're not really clear on what you're doing.
Wakamatsu said:
Be specific in detailing what you've done and the results. The way you're describing things leads me to think that you're not really clear on what you're doing.
Click to expand...
Click to collapse
To shorten it, I have 2 booting options, the first one is regular booting with the bad recovery(red triangle), the second one is working recovery, but when I boot it automatically goes to the recovery after the google logo screen, and I can't get past that, tried many recoveries versions, but nothing worked. And yeah its been more than a year since I last touched it, so I don't remember everything as I used to.
Again, your description is extremely vague and is telling re: your knowledge. Provide file names, versions, commands used, logs, error messages, etc.
Wakamatsu said:
Again, your description is extremely vague and is telling re: your knowledge. Provide file names, versions, commands used, logs, error messages, etc.
Click to expand...
Click to collapse
File names of what? boot.img? I'm using flashtool if that's what you mean by commands used, logs of what? there are no error messages, only the red triangle, which I assume you know what I'm talking about, if you mean Android version, as I wrote before, 5.1.1, if you mean recovery version, tried many versions, so I don't think it has anything to do with it.
Are you unrooted and stock rom but just trying to install a custom recovery?
Sent from my Nexus 5 using Tapatalk
Sounds to me like the recovery is being flashed to the boot partition instead of the recovery partition, so when you try to boot normally it boots the recovery and when you try to boot to recovery there isn't anything there.
msacco4 said:
File names of what? boot.img? I'm using flashtool if that's what you mean by commands used, logs of what? there are no error messages, only the red triangle, which I assume you know what I'm talking about, if you mean Android version, as I wrote before, 5.1.1, if you mean recovery version, tried many versions, so I don't think it has anything to do with it.
Click to expand...
Click to collapse
You should not be flashing your phone because you have absolutely no idea what you're doing or trying to do.
Wakamatsu said:
You should not be flashing your phone because you have absolutely no idea what you're doing or trying to do.
Click to expand...
Click to collapse
+1 to this
Uninstall the toolkit and go read a fastboot guide
Sent from my Nexus 5 using Tapatalk
Installed the old and beautiful 4.4 android again, flashed recovery and everything else with no problems, and everything works great, thanks for the fastboot guide tips.
Related
Hi all,
I recently unlocked my VZW Xoom using the OEM unlock instructions found here: http://forum.xda-developers.com/showthread.php?t=967065
I then downloaded the most recent CWM (3.025) and followed the instructions found in this thread: http://forum.xda-developers.com/showthread.php?t=1038870
I was able to write CWM to the recovery partition with no errors showing in either ADB or on the device itself. I verified the checksum of recovery.img.
What happens now is that when I reboot to recovery from ADB, the red Moto logo shows up, and at first everything looks good. At the top it says "Reading ODM fuse 1".
Then, a green Android logo with a yellow exclamation mark on it appears over a black screen. It looks like some sort of error message. I have CWM on my phone so I know this isn't what it's supposed to look like
In any case, has anyone else seen this issue (or better yet, know how to fix it)? I should point out that after a few minutes, the Xoom automatically boots into HC and works just fine.
it kind of sounds like the recovery didn't flash. Have you tried to flash it again?
Jthom203 said:
it kind of sounds like the recovery didn't flash. Have you tried to flash it again?
Click to expand...
Click to collapse
Hi - thanks for the response.
Yes, I've tried that, rebooted the device, rebooted the PC, tried it again, etc. Still no dice
does it still boot? if so try installing rom manager and using it to flash CWR
Sic123 said:
does it still boot? if so try installing rom manager and using it to flash CWR
Click to expand...
Click to collapse
Yep, it still boots. I've never used ROM manager, but I did happen to just download it. I'll give that a shot.
Two other things I didn't mention in the OP:
- I do not have an SD Card in the slot.
- I also didn't 'root' the phone yet with the SuperUser APK, only unlocked the bootloader. Would either of those cause the issue?
I believe you have to root to flash recovery. Here is an easy way to do it http://forum.xda-developers.com/showthread.php?t=1011196 its the one click method just make sure your not doing anything else while running
Jthom203 said:
I believe you have to root to flash recovery. Here is an easy way to do it http://forum.xda-developers.com/showthread.php?t=1011196 its the one click method just make sure your not doing anything else while running
Click to expand...
Click to collapse
Already in the works I'll let you know how it turns out.
Initially, it seems odd that ADB/fastboot wouldn't return an error if root is needed for flashing recovery. Time will tell...
volta said:
Already in the works I'll let you know how it turns out.
Initially, it seems odd that ADB/fastboot wouldn't return an error if root is needed for flashing recovery. Time will tell...
Click to expand...
Click to collapse
Root was the answer. Duh. I feel dumb now.
Either way, once I get to 10 posts, I can post in the dev forum thread to make it clear that root, not just OEM unlock, is required to flash CWM so that dummies like me can get things working quickly
nice, glad that you got it working.
Be sure to install Tiamat 1.31 so you can use your SD card and get full access to CWM
Rom Manager question
Has anyone found a way to allow Rom Manager to "Manage Backups"? It appears that it isn't pointing to the correct directory/ folder.
Had the same issues after installing CWM from ROM Manager - used the adb method instead and this fixed the issue. (Xoom was already rooted and OEM unlocked)
Hello, I seem to have soft bricked my tf700.
I flashed a newish pacman nightly in CWM (after wiping data/cache/dalvik cache), which completed with no errors, then I flashed the corresponding GAPPS. But my device became stuck in the pacman boot intro.
So I tried flashing slimkat which led to my device not getting past the first bootup screen (where you can enter recovery if pressing the corresponding buttons).
After this screw-up I stupidly hit the wipe data button on the bootloader. I then tried doing the method of using fastboot to erase system, cache, and all that so I could flash system blob of the newest asus US SKU (that is correct for a US bought tf700 right?). Either this or wiping the data caused me to have a different bootloader as pictured below as I no longer have the android button and it does not ask me to press volume up to access recovery (the only way to access recovery is by hitting the wipe data button in bootloader).
I can still fastboot flash CWM, but trying to flash TWRP does not work as it finishes but going into recovery causes the tablet to just restart. Trying to flash asus stock as above would always give me an error like the one pictured below. Similar errors occur if trying to flash any rom inside CWM via an external sd card.
I do not have access to adb as i believe i dont have usb debugging enabled since the pacman rom or any other rom did not ever start. It just gives me the device not found error even after manually installing the drivers on two different computers.
Cant seem to get these pics to load, but copying the url and pasting it works.
http://imgur.com/AaU0GMt
http://imgur.com/vDTVa4B
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
tylerleo said:
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
Click to expand...
Click to collapse
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
gio3505 said:
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
Click to expand...
Click to collapse
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
tylerleo said:
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
Click to expand...
Click to collapse
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
gio3505 said:
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
Click to expand...
Click to collapse
Hmm, I'd Download a stock Rom for the device offline, take on the sd card and put it on there real quick and try to flash that, if not, you probably bricked your device. I wouldn't know how to fix it beyond that. Ask the dev that made the Rom were everything that went south and an email to cwm wouldn't hurt either
I am also not sure if I need to have my external sd card formatted a certain way or download a specific CWM to allow flashing the stock rom. Ive spent over 10 hours trying to figure this out, very frustrating.
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
gio3505 said:
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
Click to expand...
Click to collapse
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
berndblb said:
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
Click to expand...
Click to collapse
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
gio3505 said:
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
Click to expand...
Click to collapse
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
berndblb said:
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
Click to expand...
Click to collapse
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
gio3505 said:
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
Click to expand...
Click to collapse
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
berndblb said:
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
Click to expand...
Click to collapse
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
gio3505 said:
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
Click to expand...
Click to collapse
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
berndblb said:
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
Click to expand...
Click to collapse
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
gio3505 said:
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
Click to expand...
Click to collapse
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
berndblb said:
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
Click to expand...
Click to collapse
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Right stop flashing random stuff - you have combinations of JB4.2.1, JB4.1.1 and ICS 4.0.3 just listed there.
Let me put a call out to @lj50036 who may be able to save you but if you have messed the bootloader up with no nvflash backups you are not going to be happy with the result. If you can still get to the bootloader screen then he can perform miraculous superhero acts and *maybe* save your device.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Shoot me an email at [email protected]
We can use hangouts see if there is a solution to your issue ...
Thx Josh
Hi
Earlier I installed TWRP via Philz and that worked fine.
I then reset my phone and flashed Bigxie's Android L, again this worked fine.
I flashed the new radio for the same thread and that worked fine.
I then downloaded CF-Root from here:
http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Ran the Windows Batch file all seemed to go well. Bootloader was unlocked and the big red android appears on screen.
Phone booted back to TWRP, a script ran and then my phone started constantly booting the the TWRP screen.
All I'm getting is teamwin flashing up.
If I power off it goes back to this loop.
Any way I can get this working again ?
Not worried about any data.. I've got all I need backed up.
Thanks
albert_htc said:
Hi
Earlier I installed TWRP via Philz and that worked fine.
I then reset my phone and flashed Bigxie's Android L, again this worked fine.
I flashed the new radio for the same thread and that worked fine.
I then downloaded CF-Root from here:
http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Ran the Windows Batch file all seemed to go well. Bootloader was unlocked and the big red android appears on screen.
Phone booted back to TWRP, a script ran and then my phone started constantly booting the the TWRP screen.
All I'm getting is teamwin flashing up.
If I power off it goes back to this loop.
Any way I can get this working again ?
Not worried about any data.. I've got all I need backed up.
Thanks
Click to expand...
Click to collapse
dont use root toolkits.
flash the factory img via fastboot. then flash twrp again, flash a kernel that allows root, then flash the latest supersu.
Thanks for the reply.
Just want to claify to make sure I don't make it worse..
I've got the L image from Googles site, do I extract the factory.img from that ?
Then flash it using :
fastboot flash factory factory.img
Thanks
Think I may have made things worse..
I extracted the tgz file and while browsing double clicked the flash all batch file.
:silly: Not sure how the hell I clicked it twice.. but it's doing something.. .hopefully not killing my phone.
Any suggestions how I did myself out of this hole..
albert_htc said:
Think I may have made things worse..
I extracted the tgz file and while browsing double clicked the flash all batch file.
:silly: Not sure how the hell I clicked it twice.. but it's doing something.. .hopefully not killing my phone.
Any suggestions how I did myself out of this hole..
Click to expand...
Click to collapse
i dont think hitting it twice will do anything. but you might have to flash the img files separate, as in the flash-all is giving some ppl issues.
simms22 said:
i dont think hitting it twice will do anything. but you might have to flash the img files separate, as in the flash-all is giving some ppl issues.
Click to expand...
Click to collapse
Found out how I've managed to double click.. The trackpad on my laptop is playing up.
I'll have to remember to use a USB mouse with it.
The phone has just rebooted and is coming back up.
Thanks for the advise.. looks like it's working.
I'll start a new thread with a couple of follow up questions.
Thanks
simms22 said:
i dont think hitting it twice will do anything. but you might have to flash the img files separate, as in the flash-all is giving some ppl issues.
Click to expand...
Click to collapse
When doing this, is there any specific order to follow when flashing all the .img files separately? I am also getting errors stating recovery.sig and boot.sig are missing. Does installing separate also take care of this?
Jmurf said:
When doing this, is there any specific order to follow when flashing all the .img files separately? I am also getting errors stating recovery.sig and boot.sig are missing. Does installing separate also take care of this?
Click to expand...
Click to collapse
it appears that the flash-all is having issues and skipping. so by flashing them all individually, you will make sure to flash them all.
It's possible this is also somewhere else, but I am having trouble finding it....so I gave up and figured I'd ask.
Okei. I started with TWRP 2.8.6.1. So from my understanding flashing a modem does not work in versions of TWRP newer than 2.8.6.0. I get that, and so I decided to downgrade. However, that seems to be the version that I am unable to get working. I've attempted to flash the 2.8.6.0 recovery via fastboot. Everything says it's good in my terminal. So I go ahead and boot into recovery, but my phone goes to a black screen for a moment and then reboots into OS. I tried a different method, via the app from the google play store. It tells me that there is an error of some sort, or that I already have it installed. So I used the google play app to install 2.8.6.1, which worked flawlessly. So now I am back where I started.
Is there some trick to getting specifically TWRP 2.8.6.0 working so that I am able to use it to flash a different modem? Will using an even earlier version yield the same results? Or am I better off doing it via fastboot?
Thank you for your time <3
Use philz recovery
Myrskyta said:
It's possible this is also somewhere else, but I am having trouble finding it....so I gave up and figured I'd ask.
Okei. I started with TWRP 2.8.6.1. So from my understanding flashing a modem does not work in versions of TWRP newer than 2.8.6.0. I get that, and so I decided to downgrade. However, that seems to be the version that I am unable to get working. I've attempted to flash the 2.8.6.0 recovery via fastboot. Everything says it's good in my terminal. So I go ahead and boot into recovery, but my phone goes to a black screen for a moment and then reboots into OS. I tried a different method, via the app from the google play store. It tells me that there is an error of some sort, or that I already have it installed. So I used the google play app to install 2.8.6.1, which worked flawlessly. So now I am back where I started.
Is there some trick to getting specifically TWRP 2.8.6.0 working so that I am able to use it to flash a different modem? Will using an even earlier version yield the same results? Or am I better off doing it via fastboot?
Thank you for your time <3
Click to expand...
Click to collapse
I too have experienced exactly what you describe and have yet to find a solution. I own 2 OPO's, plus I administer one for a friend who purchased one based on my recommendation. The oldest one I own which was purchased 4 months prior to the others has worked perfectly with any recovery or ROM I've installed on it. It has TWRP-2.8.6.0 installed and has no problems flashing any partition from recovery. My newer handset and my friend's both refuse to boot into recovery with that version installed. It doesn't matter if I flash from fastboot or from TWRP itself. I have no idea why this phenomena occurs on some of these devices, but it makes administering them a more time consuming pain in the ass. I'm going to try Phil's recovery, as was suggested, as a workaround, but I'm dumbfounded as to why the inconsistencies exhibit themselves on particular devices.
Odysseus1962 said:
I too have experienced exactly what you describe and have yet to find a solution. I own 2 OPO's, plus I administer one for a friend who purchased one based on my recommendation. The oldest one I own which was purchased 4 months prior to the others has worked perfectly with any recovery or ROM I've installed on it. It has TWRP-2.8.6.0 installed and has no problems flashing any partition from recovery. My newer handset and my friend's both refuse to boot into recovery with that version installed. It doesn't matter if I flash from fastboot or from TWRP itself. I have no idea why this phenomena occurs on some of these devices, but it makes administering them a more time consuming pain in the ass. I'm going to try Phil's recovery, as was suggested, as a workaround, but I'm dumbfounded as to why the inconsistencies exhibit themselves on particular devices.
Click to expand...
Click to collapse
Well....at least now I know I'm not totally crazy. Thank you~
=)
Ejvyas said:
Use philz recovery
Click to expand...
Click to collapse
Is there any particular reason for Philz recovery over standard CWM?
Also, while this might be a viable option my understanding is that, that would render my old backups useless since I was previously using TWRP? That's kind of unfortunate. =(
Myrskyta said:
Is there any particular reason for Philz recovery over standard CWM?
Also, while this might be a viable option my understanding is that, that would render my old backups useless since I was previously using TWRP? That's kind of unfortunate. =(
Click to expand...
Click to collapse
uploaded the file for you (Take out .apk extension), hope you know how to flash thru fastboot. Else google.
KSKHH said:
uploaded the file for you (Take out .apk extension), hope you know how to flash thru fastboot. Else google.
Click to expand...
Click to collapse
Unfortunately, if that is the same one from twrp's website it isn't going to do me any good. I already attempted that through fastboot. 2.8.6.1 works flawlessly. 2.8.6.0 seems to bootloop once and then toss me back into the OS. Thank you though, I appreciate it.
Had the same problem tried to flash back to 2.8.6.0 via TWRP and didn't work and seemed like recovery had disapeared so used TWRP App to install 2.8.6.1 booted into recovery then rebooted and tried to downgrade to 2.8.6.0 but got a message about same recovery, rebooted phone tried again and it installed no problem.
stylez said:
Had the same problem tried to flash back to 2.8.6.0 via TWRP and didn't work and seemed like recovery had disapeared so used TWRP App to install 2.8.6.1 booted into recovery then rebooted and tried to downgrade to 2.8.6.0 but got a message about same recovery, rebooted phone tried again and it installed no problem.
Click to expand...
Click to collapse
Hmm...maybe I'll give it another shot then. I had opted to just flash them via fastboot because I couldn't get it to work. It's not the worst thing ever. Thank you =)
Myrskyta said:
Is there any particular reason for Philz recovery over standard CWM?
Also, while this might be a viable option my understanding is that, that would render my old backups useless since I was previously using TWRP? That's kind of unfortunate. =(
Click to expand...
Click to collapse
just FYI, philz recovery does support TWRP backups. you just have to enable that feature in the settings
Oh! Thank you for letting me know. I'll keep that in mind. =)
Save yourself all that trouble, just flash modems with fastboot....fastboot flash modem modem.bin
Hey folks; I'm hoping I can get some advice or pointers, or maybe just a slap upside the head with something I've missed.
I have one of the original Shield tablets, and played around with it quite a lot, installing various custom ROMs from the marvelous directions I've found here. When the battery thing happened, I submitted the required info and happily received my new tablet. The original was rooted and customised still, kill-switch averted, and I had two working tablets. I gave the new stock one to my wife.
But then, about three months ago, I was playing with mine again installing a newer ROM than the one I was using (I *think* I was going from an older Bliss rom to one of the Cyanogen), and ... Something Happened (tm). The tablet rebooted in the middle of everything, and now won't boot to an image.
I'm on Windows 10 now, and had some fun getting the drivers working, but they seem to. I can communicate with the tablet through Fastboot, but ADB doesn't see it. I've flashed several versions of TWRP to the tablet, and can boot into that recovery - both through Fastboot and the tablet's power+vol-dn buttons. I've used TWRP to flash several different ROMs, and it *appears* to work (there are no errors), but when I reboot the tablet .... nada. Nothing but the Nvidia boot screen for days.
So now... what have I missed? I'm a little reluctant to flash a stock ROM, but I'm at a loss. I used to have more time to fiddle and figure, and I'm afraid that my impatience is going to kill the thing.
Format system and data see if that works
You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk
skooter32 said:
Format system and data see if that works
Click to expand...
Click to collapse
Have done, but I'll try it again. Thanks
lafester said:
You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I've tried the latest and the not-so-latest, all with similar results.
Hnefatafl said:
I've tried the latest and the not-so-latest, all with similar results.
Click to expand...
Click to collapse
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida
Hnefatafl said:
Have done, but I'll try it again. Thanks
Click to expand...
Click to collapse
Also format data system to something other than ext4 then re format it back
skooter32 said:
Also format data system to something other than ext4 then re format it back
Click to expand...
Click to collapse
can I ask what that should bring?
wiQbold said:
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida
Click to expand...
Click to collapse
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.
Right, well it looks like I've got this thing going. I could flash TWRP 3.1.0-0, but not any 3.1.1. Cyanogenmod 12 worked. Reading up a little more (it got slow at work for a couple of days...) I flashed the firmware to 5.0, and could now install TWRP 3.1.1-1! Then I could install (in this case) Lineage 14.1, which *almost* worked. It booted, but there's no wifi.
Then I found a suggestion - I think it was on these forums somewhere - and restarted. Wiped all data again, flashed Cyanogenmod 12, no gapps. Restarted, checked everything including wifi, and is good. Rebooted back into recovery, performed a factory reset, then installed Lineage 14.1 and gapps. When it rebooted, everything is working!
So. Firmware. Huh.
Thanks all.
Hnefatafl said:
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.
Click to expand...
Click to collapse
do not know if you need the bootloader(blob) from nougat to boot up, that lafester told you. but that sounds plausible. skooter says something from re-formating. so if you tried that all and nothing changes? cache and data partition you wiped also, so it has to be work for my understanding.
went always stock, so can t help you..
but you can use recovery images > twrp > bliss/linage. no need to boot up stock?
wiQbold said:
can I ask what that should bring?
Click to expand...
Click to collapse
I have had similar issues and I tried everything even this plus what harm is it going to be and as the fellow below said if ur in fastboot and recovery with no issues then surely u should be flashing stick to fix Ur problem ?