Related
so I have the latest software, used the HTC unlock method, was rooted and had the TWRP recovery working just fine, I'm an idiot and flashed the CM recovery through RM and of course it didn't work, so I've tried every which way I can find to re-flash the TWRP and even tried flashing AMON but it will not go into recovery with any of them after it says it successfully wrote the recovery.
TWRP and CM just wait for a minute then reboot normal, AMON reboots then sits at the HTC screen... forever and i have to pull the battery.
I tried uninstalling RM to see if it was F'ing with it, didn't matter.
not sure what to try next to get a working recovery back onto the phone, I'm still rooted just running the stock ROM, I had loaded an alternate ROM successfully last week, just didn't like it. So I know all is 'working' as expected I just F'd up the recovery part now
any help??
afaik if you used the HTC unlock you need to fastboot flash it, or maybe hboot zip it? What have you tried so far?
I've tried using fastboot to flash amon and TWRP, same result
tried doing TWRP as a zip as well
what's weird is each method seems to "work" i get that it's pushing, writing, completed, no errors with any of them but then it just won't go into recovery and if i change to different recoveries I get different reboot behaviors just none of them work.
that's where I'm stuck, I feel like I've tried all the methods it just refuses to actually go into recovery when it's loaded.
another thing I thought was weird though, when I reflashed TWRP, and then go into RM it would say at the top that I had the latest version of CM installed like it didn't take? I uninstalled RM and tried it all again, same result.
morellox said:
I've tried using fastboot to flash amon and TWRP, same result
tried doing TWRP as a zip as well
what's weird is each method seems to "work" i get that it's pushing, writing, completed, no errors with any of them but then it just won't go into recovery and if i change to different recoveries I get different reboot behaviors just none of them work.
that's where I'm stuck, I feel like I've tried all the methods it just refuses to actually go into recovery when it's loaded.
another thing I thought was weird though, when I reflashed TWRP, and then go into RM it would say at the top that I had the latest version of CM installed like it didn't take? I uninstalled RM and tried it all again, same result.
Click to expand...
Click to collapse
*my opinion*
delete rom manager
boot into recovery using adb
"adb reboot recovery"
or terminal emulator
"reboot recovery"
or the app "quickboot"
does that work?
I've tried all those except Quickboot... *trying now......*
annnnnd
same thing with the app...
I'm thinking at this point I almost need to just write everything over again? use a flashable zip in the bootloader and just have it write everything over again, I was going to do a new rom anyways bored with the stock again.
so I need to find that I guess? re-write everything go back to fresh and start over
1. Make sure u r not flashing CDMA recovery over a GSM device, or vice versa.
2. How did u get ur device rooted in the first place?
3. Last resort, relock ur device and apply the correct RUU, then unlock and root again.
Sent from my HTC EVO 3D X515m using XDA App
1) good there
2) I followed a tutuorial where I pushed the recovery and the SU file after doing the HTC official unlock method, worked great at first, I'm the idiot that pushed the CM recovery over top of it and now I can't get a working recovery back on.
3) do I really have to relock first, I've seen the simple tutorial on doing so, I was hoping maybe I could find an all in one flashable ROM that would at least get me back to operational on all partitions and then re-work that one with a new ROM later or something, not possible?
This is of no help to you but - I had the same error. TWRP v1.0.3. I tried everything in the book to get it to work... but got stuck at the HTC splash screen like you. And I tried installing the 1.13 PG86IMG and then my device turned off while installing the PG86IMG (it was fully charged during flashing, I checked). Be careful with what you do.
I was unlocked with AlphaRev's tool, running my own ROM.
mine hung like that if i flashed AMON, but i could still pull the battery and go back into the bootloader to flash at least TRWP using FastBoot so I could get back into the phone
ugh
morellox said:
mine hung like that if i flashed AMON, but i could still pull the battery and go back into the bootloader to flash at least TRWP using FastBoot so I could get back into the phone
ugh
Click to expand...
Click to collapse
htc unlock method has proven to be a bit shady for the community in that it doesnt allow all the features/functions the revolutionary (and prior unrevoked) unlock method does.
most developers unlocked with revolutionary and haven't performed the htc unlock method so it has been hard to gather technical details on the htc unlock method.
one item we can eliminate in the effort to narrow down your issue: there is no working Amon RA recovery for the EVO 3D. not sure where you obtained Amon RA recovery. TWRP was created to pick up the torch from the Amon RA recovery as he retired from developing his recovery to support emmc devices.
stick to either flashing the twrp or cwm recovery images. there are only a handful of ways to load a custom recovery and only a handful of ways to boot the device into recovery mode.
i'd follow a logical pattern and work your way through the avaiable options. by following the available options one step at a time you should be able to narrow down which methods work and don't work. sorry it has been difficult as this htc unlock method is newer to the community we aren't as familiar with it as we are the revolutionary method.
ways to flash a custom recovery:
1) fastboot - fastboot flash recovery c:\downloads\recovery.img
2) bootloader - PG86IMG.zip file containing recovery.img and android-info.txt
3) flash_image - while in normal android mode (my app Flash Image GUI works well for this)
ways to boot into recovery mode:
1) turn device completely off and unplug USB. vol down + pwr loads bootloader. select recovery from the menu
2) from android mode: adb shell reboot recovery
3) from android mode: use a 3rd party app like quick boot.
this is all off the top of my head so it might not be an *exhaustive* list but it should cover all the common approaches. hope that helps and keep us updated! good luck!
damn...
I really appreciate everyone's help here I've been a part of various forums for a REALLY REALLY long time... from the days of Nextel, then I was a Palm Lover for a few years and now Android.
this obviously isn't urgent as my phone is working just fine, I just can't flash a new ROM since I can't get any recoveries working.
unfortunately I'm pretty sure I've tried all the methods listed above, I'm going to probably sit down sometime this weekend and systematically go through each method one more time just to be sure. TWRP worked for me just fine in the beginning, I flashed a ROM more than once, reverted back to my old ROM, made back ups, cleared cache's all the stuff I'd need to do.
thanks everyone, I'll keep trying
and no one knows of a flashable 'rom' that would have all the different partitions included in a zip or something like that? like.... what is in place of recovery in a stock phone? I can always unroot and start over but I did use the HTC unlock method so I hope that even works
got one to work! followed this method
http://forum.xda-developers.com/showthread.php?t=1239455
Hi all.
I've rooted many an Android device in my days, but this one has me stumped. I flashed the CWM recovery via Odin, it rebooted, I shut it down and did the Power + DownVolume to get to the "Recovery" and "Download" mode scheen, but my screen doesn't have a recovery icon, it has a USB one instead. So it seems like I have no way to get into Recovery? No idea why. Any ideas why this is, and how I can get into recovery to finish the rooting/flashing process?
Much appreciated, and screenshot attached
Thanks!
Chris
Have you tried installing something like rom manager in play store and using the option for boot into recovery?
nest75068 said:
Have you tried installing something like rom manager in play store and using the option for boot into recovery?
Click to expand...
Click to collapse
Oooh. Good thought. I'll give that a whirl.
What I was able to figure out was that the USB symbol is the FastBoot icon. Apparently something was flashed to this device at some point that put it on there. Probably by me, not realizing what exactly I was flashing, when I was trying to fix the boot-loop issue that this device had at one point.
Anyway, I was able to get CWM installed by firing up the adb server, then:
fastboot-mac -p 0x0700 -i 0x0955 boot cwm_recovery.img
Then I could install the root app and CM10. Weird though. Further reboots still give me just the fastboot and download mode options. I would have thought that by doing what I did with fastboot, I would be able to get into recovery now, but nope. Maybe I just booted into the cwm_recovery.img and didn't actually *install* it? I need to read up on the fastboot options I think.
Anyway, thanks for the input. I'll give the rom manager a shot as well. That would be more simple
Chris
I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
JM1084 said:
I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
Click to expand...
Click to collapse
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
santod040 said:
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
Click to expand...
Click to collapse
Yeah, there is no PG05IMG.zip in the sd card root. Also I have tried reinstalling the recovery from the 4EXT recovery control app.
Current verson of recovery installed is 4EXT Recovery Touch v1.0.0.5 RC8.
Tried reflashing that, and also the RC9 test build that is out right now.
Still no go on getting into the recovery.
Thanks.
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
santod040 said:
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
Click to expand...
Click to collapse
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
santod040 said:
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
Click to expand...
Click to collapse
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Edit: I confirmed his hboot is 6.04.1002. same as mine
JM1084 said:
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Click to expand...
Click to collapse
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
Alrighty, I will give that a shot. I am at work right now and am about to head out of town so I will be unable to try it until sunday. I'll post the results here asap. Thanks again!
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
zomgalama said:
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
What is your h boot version?
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
No Go, my tbolt will not mount in Win7, it just says the device has malfunctioned. Rebooting into the bootloader with USB in will not show anything in Windows, even in fastboot. It makes the device connection sound but no devices show up. Running the CMD file in the zip you linked does nothing, I'm at 10 minutes now where it just says "Waiting for device". Is my device just done for?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
coltspackers said:
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
Click to expand...
Click to collapse
Thanks for the info, but this didn't work either. I'm also on 6.04.1002 and rooted mine a week after the T-Bolt shipped manually via adb.
This happened about a month ago also, and I thought it was ext4 but managed to get an older TWRP recovery to work after working on it for about a day and a half without a working phone. At least I have a working phone at this point.
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
allo_87 said:
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
Click to expand...
Click to collapse
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
Excellent advice, thanks man.
Sent from my ADR6400L using Tapatalk 2
My thunderbolt's recovery spin mysteriously started working again yesterday, not sure why.
Doesn't matter though since I switched carriers now:/
Sent from my Sprint LG Optimus G
Still nothing for me. Worse yet is the fact that I can't adb because my usb has not worked properly since "the soup incident"
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
After going over the issue with Max and trying several fixes he suggested (he even made me an app that would format my cache), it seems I either need to obtain an RUU and flash the stock software/recovery back on and re-root or try flashing an updated hboot that already has s-off. The thinking is that it is my hboot that is causing the issue. Does anyone know what files I need? I have a couple of things to try at home to see if I can get my usb working again, if not, anything I do will have to be a flashable zip from the bootloader. Thanks!
I wanted to upgrade my Nabi with the latest OTA. I had TWRP 2.2.2.1. I used it to revert to an old backup. After the restore, I tried to apply the OTA updates. After it rebooted and started the install I got an "!" Android logo.
I power cycled and I was able to boot back in. I noticed I still had the Play Store app (which will not work, error about connecting to services) and suspect the "stockunrooted" restore I used may not have been completely "stock". I did lose root and TWRP though.
I tried to reinstall TWRP again, but it appears that Fastboot no longer works since the restore. The tablet just hangs on the Nabi logo indefinitely. When I press Vol - & + with PWR, and select Recovery Mode, I just get another "!" Android logo (is this stock recovery?).
ADB works, it sees the tablet and I'm able to push, access shell etc.
I used motochopper to root the Nabi again. I tried installing flash_image to manually flash a new TWRP recovery.img, but running the command I get an error about "error scanning partitions".
I'm not sure what else I can do to get Fastboot working or a recovery system installed again. OTA upgrade will not apply, and I'm stuck on 1.9.37 at this point.
Does anyone have a suggestion how I can get Fastboot fixed and the Nabi back to "normal" / upgradeable.
Thanks for your help
kaijan said:
I wanted to upgrade my Nabi with the latest OTA. I had TWRP 2.2.2.1. I used it to revert to an old backup. After the restore, I tried to apply the OTA updates. After it rebooted and started the install I got an "!" Android logo.
Click to expand...
Click to collapse
What software rev did you get to when doing the OTA's?
I power cycled and I was able to boot back in. I noticed I still had the Play Store app (which will not work, error about connecting to services) and suspect the "stockunrooted" restore I used may not have been completely "stock". I did lose root and TWRP though.
Click to expand...
Click to collapse
That is usually a sign that various Google services are removed from the system partition. So in that case it is returned to stock, but there is still information of the Play install on the data partition.
I tried to reinstall TWRP again, but it appears that Fastboot no longer works since the restore. The tablet just hangs on the Nabi logo indefinitely. When I press Vol - & + with PWR, and select Recovery Mode, I just get another "!" Android logo (is this stock recovery?).
ADB works, it sees the tablet and I'm able to push, access shell etc.
I used motochopper to root the Nabi again. I tried installing flash_image to manually flash a new TWRP recovery.img, but running the command I get an error about "error scanning partitions".
I'm not sure what else I can do to get Fastboot working or a recovery system installed again. OTA upgrade will not apply, and I'm stuck on 1.9.37 at this point.
Click to expand...
Click to collapse
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
aicjofs said:
What software rev did you get to when doing the OTA's?
That is usually a sign that various Google services are removed from the system partition. So in that case it is returned to stock, but there is still information of the Play install on the data partition.
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Click to expand...
Click to collapse
OTA is trying to install 2.1.27
You were correct about the fastboot driver issue. I was using Windows 8.1 and it it wasn't working properly. I switched to Ubuntu and now have no problems.
I was able to flash TWRP 2.3.3 and tried another restore to stock. Did OTA again, but still get the "!" Android shortly after it reboots and starts installing. I can't seem to get rid of gapps either. Play Store is still installed. I've tried wiping /data/media, cache's etc and it still remains.
I'm not sure why the OTA upgrade keeps failing. Do you think it's due to the gapps still being on the device?
Any other ideas on how I can get the OTAs to work?
Update:
I booted up stock recovery and tried the update from cache
Verifying current system...
assert failed: apply_patch_check("/system/app/Gallery2.apk", "4cadedee1defcdc28afc99ea968ebb1e631e7b9", "ee310bfc0d0ad2fe11356b97f8cb6e754aa43f2b")
E: Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
kaijan said:
OTA is trying to install 2.1.27
You were correct about the fastboot driver issue. I was using Windows 8.1 and it it wasn't working properly. I switched to Ubuntu and now have no problems.
I was able to flash TWRP 2.3.3 and tried another restore to stock. Did OTA again, but still get the "!" Android shortly after it reboots and starts installing. I can't seem to get rid of gapps either. Play Store is still installed. I've tried wiping /data/media, cache's etc and it still remains.
I'm not sure why the OTA upgrade keeps failing. Do you think it's due to the gapps still being on the device?
Any other ideas on how I can get the OTAs to work?
Update:
I booted up stock recovery and tried the update from cache
Click to expand...
Click to collapse
Hmm that is it weird. It does look like gapps is still installed .As gapps removes gallery2.apk and why it's failing, I don't understand if it's stock how that is happening. Use these updates yet? http://forum.xda-developers.com/wiki/Fuhu_nabi_2
This thread died out....I hate to bump it back to the top...But I have a NABI2-NV7A that I rooted along time ago....and i booted it up and was gonna do some upgrades and everything went kaboom!!
I have TWRP 2.2.2.1 installed.
I can get into TWRP but not fast-boot mode
I'm on a laptop with windows 10 installed...I don't think it's driver related....as i can send commands via adb while TWRP is up....and the NABI responds to those commands
But i never get past the logo screen....and I'm not sure what to to do with NVflash.
I'm experienced...but rooted this thing and installed GAPPS like 2 years ago and the kids dug this thing up and the play store wouldn't work any longer....i read about the OTA....so i was trying to go back to stock and get those OTA's.
Any suggestions or advice?? Anyone...hello....bueller....bueller
hotspace said:
This thread died out....I hate to bump it back to the top...But I have a NABI2-NV7A that I rooted along time ago....and i booted it up and was gonna do some upgrades and everything went kaboom!!
I have TWRP 2.2.2.1 installed.
I can get into TWRP but not fast-boot mode
I'm on a laptop with windows 10 installed...I don't think it's driver related....as i can send commands via adb while TWRP is up....and the NABI responds to those commands
But i never get past the logo screen....and I'm not sure what to to do with NVflash.
I'm experienced...but rooted this thing and installed GAPPS like 2 years ago and the kids dug this thing up and the play store wouldn't work any longer....i read about the OTA....so i was trying to go back to stock and get those OTA's.
Any suggestions or advice?? Anyone...hello....bueller....bueller
Click to expand...
Click to collapse
Have you tried using "adb reboot-bootloader"
There are some things to try before breaking out nvflash. The easiest would be to flash the boot loader and a new TWRP in one recovery session.
Boot twrp2.2.21, Install KK boot loader zip and then install TWRP KK287 zip
Then restore the 3.0.13 ROM
Files and directions here
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
aicjofs said:
Have you tried using "adb reboot-bootloader"
There are some things to try before breaking out nvflash. The easiest would be to flash the boot loader and a new TWRP in one recovery session.
Boot twrp2.2.21, Install KK boot loader zip and then install TWRP KK287 zip
Then restore the 3.0.13 ROM
Files and directions here
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Click to expand...
Click to collapse
I did try ADB REBOOT-BOOTLOADER all that happens is the NABI2 restarts and sits at the logo screen.
I'm able to push via ADB, so I will download the suggested files and take your advice. I'll report back. And, thanks for the reply.
Update...
I was able to push all of the needed files and I verified I pushed them completely by using "adb push -p xxxxxx /sdcard"
I then rebooted back into TWRP
I flashed KK3013bootloader.zip, then flashed twrp-recovery-NV7AUS-287.zip
Rebooted and I can't get back into TWRP. And, now I can't establish a connection for adb commands.
Any advice? tips...pointers? Could this truly be my first bricked device??
hotspace said:
Update...
I was able to push all of the needed files and I verified I pushed them completely by using "adb push -p xxxxxx /sdcard"
I then rebooted back into TWRP
I flashed KK3013bootloader.zip, then flashed twrp-recovery-NV7AUS-287.zip
Rebooted and I can't get back into TWRP. And, now I can't establish a connection for adb commands.
Any advice? tips...pointers? Could this truly be my first bricked device??
Click to expand...
Click to collapse
Nah Nabi2 is practically impossible to brick.
So do you get the command list in the top left when you press the vol and power buttons? i.e the selection continue, fastboot, recovery kernel, forced recovery? or when you select recovery kernel it just doesn't boot TWRP?
I wont type a lot of stuff until I get you answer but if we need to go the nvflash route this is some good reading. You will need to get in to APX mode, install the driver and issue some commands.
Read this post and next few pages after it
http://forum.xda-developers.com/showpost.php?p=46579190&postcount=1687
General idea of commands
http://forum.xda-developers.com/showpost.php?p=48683262&postcount=124
Might be some work, but we should be able to get the device back, I'll let you know which is the best way after I see your reply.
Yup, no boot options. And, I can't get back into TWRP. I hold power button to shut it down. Then vol+ power and typically I'd get the boot options, but nothing, just the logo. Then hold power button to shut down. Continue...repeat...
I appreciate you sticking in for the long haul on this.
Sent from my SM-N920P using Tapatalk
hotspace said:
Yup, no boot options. And, I can't get back into TWRP. I hold power button to shut it down. Then vol+ power and typically I'd get the boot options, but nothing, just the logo. Then hold power button to shut down. Continue...repeat...
I appreciate you sticking in for the long haul on this.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Damn. It IS going to be a long haul, but you will know the tablet well when its done. I don't have the tablet to test anymore, so I have to work from memory(and that's been a long time)
Well the bad news is this is going to require opening the tablet. See this post http://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701
You are going to have to short those pins to get it in to APX mode and use nvflash
-You will need the APX driver as well.
-The nvflash package
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
I will type more later.
aicjofs said:
Damn. It IS going to be a long haul, but you will know the tablet well when its done. I don't have the tablet to test anymore, so I have to work from memory(and that's been a long time)
Well the bad news is this is going to require opening the tablet. See this post http://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701
You are going to have to short those pins to get it in to APX mode and use nvflash
-You will need the APX driver as well.
-The nvflash package
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
I will type more later.
Click to expand...
Click to collapse
Sweet! Looking forward to this.
Sent from my SM-N920P using Tapatalk
hotspace said:
Sweet! Looking forward to this.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Get the nvflash package from the Nabi General Info thread I linked above
Unzip in to a directory of your choosing and open a command prompt in that folder
The Nabi will be broken open and connected by USB to computer
So once you get those pins shorted and press the power button the screen should come on and be completely black(you can tell the backlight is on though)
Check in device manager for a new device(it will be auto detected or you will have to manually install APX driver)
Once the driver is installed you can issue nvflash commands
nvflash --bl bootloader.bin --download 4 bootloader.bin
Before pressing enter for the below command get ready to press and hold the vol+ key.
nvflash --resume --go
Right on. I'll dig into this in the morning
Sent from my SM-N920P using Tapatalk
@aicjofs, I still haven't begun breaking the Nabi down. I'm working from home today and should be able to squeeze the disassemble in sometime today.
I scanned through the comments you've left since finding out I wasn't able to get to the boot menu...I'll post back once I get it torn apart.
Hi, I oem unlocked my Nexus 9, installed TWRP and SuperSU, but I think I missed a step before I can go to custom ROMs and all. I've looked for instructions but I'm just getting confused. I firstly cannot reboot into TWRP unless I fastboot boot recovery from my PC every time. If I don't do that, it just boots into the Flounder PVT Ship white screen with Fastboot USB in red and below that HBOOT, REBOOT, REBOOT FASTBOOT, and POWER DOWN.
What step am I missing in this process? Do I need some sort of custom image or what am I doing wrong?
Thanks,
Chris
Hello,
It can get a bit confusing sometimes and people generally expect you to just know lol.
You've not missed a step. Getting into recovery is irritating lol. For as long as I've had it if booted into recovery from the power menu lol xD.
Reboot the Google Nexus 9 by holding the Power and the Volume Down buttons at the same time and wait until the tablet display shows a Google splash screen before releasing the buttons.
If you get a android with an exclamation mark then you've made a boo boo. Dw, even us pros muck up ;]
Go back to your fastboot. Flash twrp like you do. But this time once you've flashed it type
Code:
fastboot boot recovery twrp.img
That should boot your device into recovery after flashing it.
There it should be stuck on there nicely of it takes a while Dw. That's just the fun of owning a N9 lol. That should Do it .
Happy Flashing.
Give us a Thanka if I helped
ChrispyChris said:
Hi, I oem unlocked my Nexus 9, installed TWRP and SuperSU, but I think I missed a step before I can go to custom ROMs and all. I've looked for instructions but I'm just getting confused. I firstly cannot reboot into TWRP unless I fastboot boot recovery from my PC every time. If I don't do that, it just boots into the Flounder PVT Ship white screen with Fastboot USB in red and below that HBOOT, REBOOT, REBOOT FASTBOOT, and POWER DOWN.
What step am I missing in this process? Do I need some sort of custom image or what am I doing wrong?
Thanks,
Chris
Click to expand...
Click to collapse
If you installed TWRP using
Code:
fastboot flash recovery twrp.img
The only ways I know to get into recovery are to reboot to recovery from the Power menu of your ROM
OR
Boot to fastboot, select HBOOT, then select Recovery. If TWRP is installed as your recovery this will boot TWRP. If it goes to the dead droid screen then you need to install TWRP properly, using the fastboot flash command above.
I can't get my nexus 9 to run twrp as well.
I go to fastboo, select Hboot, then I get the android with exclamation, volume up and power brings up the original android recovery menu, not twrp. I've unlocked the bootloader, wiped everything and tried again, no luck. Always the same result
Mephisto_POA said:
I can't get my nexus 9 to run twrp as well.
I go to fastboo, select Hboot, then I get the android with exclamation, volume up and power brings up the original android recovery menu, not twrp. I've unlocked the bootloader, wiped everything and tried again, no luck. Always the same result
Click to expand...
Click to collapse
Are you using the newest TWRP? 3.1.0.0? It's not working for me either, can't boot to recovery. Use 3.0.2.2 or whatever the last version was
I used the 3.1.0.0
the trick was, after installing it, reboot straight back into recovery, so it doesn't get overwritten