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.
Related
Problem: Was trying to install AOKP 4.0 onto my fully updated TF201.
Wiped data/cache/davlik
installed ROM
installed Google Apps
Device stuck on splash screen.
Figured out the problem was an older version on CWM. I believe it was 5.5.0.4.
Tried to go install latest version of CWM: 5.8.3.4 by using the Fastboot method.
Accidentally selected Wipe Data Option instead of USB.
Lost CWM, all data on internal memory and my entire OS.
Device cannot boot (stays on splash screen). I also try to get back into CWM and it fails. I get bounced back to the Fastboot screen.
What can I do to get this thing back up and running? I will even take stock at this moment just to get the ball rolling again.
Thanks!
kevinb77 said:
Problem: Was trying to install AOKP 4.0 onto my fully updated TF201.
Wiped data/cache/davlik
installed ROM
installed Google Apps
Device stuck on splash screen.
Figured out the problem was an older version on CWM. I believe it was 5.5.0.4.
Tried to go install latest version of CWM: 5.8.3.4 by using the Fastboot method.
Accidentally selected Wipe Data Option instead of USB.
Lost CWM, all data on internal memory and my entire OS.
Device cannot boot (stays on splash screen). I also try to get back into CWM and it fails. I get bounced back to the Fastboot screen.
What can I do to get this thing back up and running? I will even take stock at this moment just to get the ball rolling again.
Thanks!
Click to expand...
Click to collapse
Go here, http://forum.xda-developers.com/showthread.php?t=1615990 read the OP, then go here to download http://teamw.in/project/twrp2/93
Follow the instructions under
Download - Recovery Image / Fastboot Method:
You will back up and running in no time, unfortunately you will need to reinstall the rom....
PS you will need to adb push the rom after you reboot to recovery....
Gage_Hero said:
Go here, http://forum.xda-developers.com/showthread.php?t=1615990 read the OP, then go here to download http://teamw.in/project/twrp2/93
Follow the instructions under
Download - Recovery Image / Fastboot Method:
You will back up and running in no time, unfortunately you will need to reinstall the rom....
PS you will need to adb push the rom after you reboot to recovery....
Click to expand...
Click to collapse
Thanks for the quick response!
OK, I was able to get the stock TF201 drivers onto my Windows 7 PC (since an alternate method had me change them) I am following every step explained in the directions from TeamW.in and am getting this error: "The program can't start because AdbWinAPI.dll is missing from your computer. Try reinstalling the program to fix this problem"
(UPDATE) I was able to find a ADBWinAPI.dll file and I dropped it into the same folder as the twrp.blob and fastboot.exe files. I am not able to access the cmd line, but it does not start the flash, it only lists a bunch of optional cmds to pick from. None of which look useful.
kevinb77 said:
Thanks for the quick response!
OK, I was able to get the stock TF201 drivers onto my Windows 7 PC (since an alternate method had me change them) I am following every step explained in the directions from TeamW.in and am getting this error: "The program can't start because AdbWinAPI.dll is missing from your computer. Try reinstalling the program to fix this problem"
(UPDATE) I was able to find a ADBWinAPI.dll file and I dropped it into the same folder as the twrp.blob and fastboot.exe files. I am not able to access the cmd line, but it does not start the flash, it only lists a bunch of optional cmds to pick from. None of which look useful.
Click to expand...
Click to collapse
Did you ever have any luck with this? I had a JB ROM soft brick my 201 about a year ago. I lost TWRP recovery, OS, pretty much everything. It stays on the splash screen and allows me to get to the fastboot option. I can't get my computer(windows 8) to recognize it at all. Just states it can not recognize USB device. I installed the universal naked driver package along with trying the stock ASUS driver package with no luck.
I put the tablet down and purchased a 701 but now would like to fix the 201 and sell it. If you have any advice I would be very thankful
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!
Hi All,
Long time lurker and I appreciate all the work everyone does here. It makes owning an android device a great amount of fun...but as you can see by the title of the thread, a great amount of stress as well :laugh:
My device is unlocked and I've used CWM and recenlty noticed that along one of my flashes TWRP 2.4 installed over CWM. All is well because I was meaning to switch over and try this recovery out. Smooth, fast, I like. But I recently installed CM 10.1 using the october version with the JB bootloader because I did not have it. Everything was nice, but I wanted to update CM 10.1 to a more recent UNOFFICIAL build so I flased the 3/20 version on my device. Everything was smooth but the WiFi dropped all the time so I decided to wait out a more stable "official" version of CM 10.1. Take note that I have(had) TWRP 2.4. Now I wanted to stick with JB 4.2.X so I decided to flash Energy's 3/21 build but this hung up on the ASUS screen... So I decided to reflash the rom but first installing the JB bootloader and partitions zip. Still no luck and while exiting TWRP, I noticed that it stated that my device isn't rooted and would I like to root? So I swiped and did it but it seems that the JB bootloader and partitions zip file erased everything on my device, Roms, GAPPS, SU, backups...gone.
The next thing I did was execute Urkels fresh root and fresh start and that seemed to go through all the steps with no issue. When I went back into recovery I noticed that I now have TWRP 2.2.2.1 with a JB bootloader... so what ever I did downgraded TWRP? Ok... Now I wanted to play it safe and stick to the October version of CM 10.1 with the JB bootloader but while flashing the rom (ext SDCARD) i receive an error. I decided to re-execute Urkels fresh root and fresh start and now all my device does is boot into TWRP 2.2.2.1. I can't use fastboot even with holding the power button and vol down.
At this point I feel lost and defeated, I can't use external SD anymore and I can only mount the system. So I decided to see if ADB works. ADB works great in recovery and am able to send files to the device. I sent a ROM to see if I can install but it fails because it can't mount the cache and this is where I am now. Lost... confused and desperate for help :crying: I'll make sure XDA gets a nice donation if anyone can help me out!
What works -
boot to TWRP 2.2.2.1 (thats all)
ADB in recovery
What doesn't-
No rom installed
No backup
No fastboot
My troubleshooting
Again ANY help is appreciated!
Mike
Would I be able to update TWRP within TWRP using a 2.4.4.0 zip file?
TheYoz said:
Would I be able to update TWRP within TWRP using a 2.4.4.0 zip file?
Click to expand...
Click to collapse
This is happening because you are now on 4.2.1 bootloader with an old TWRP which is not compatible with the new bootloader.
When you say you cannot access fast boot do you mean the usb icon is missing? If you do that is part of the new bootloader. As soon as you get to where the icons are you are automatically in fast boot unless you select one of the icons.
I'm out at the moment but if you reply letting me know that you can get to the icons I will post a file when I get back and some instructions to downgrade you to old bootloader and compatible TWRP.
flumpster said:
This is happening because you are now on 4.2.1 bootloader with an old TWRP which is not compatible with the new bootloader.
When you say you cannot access fast boot do you mean the usb icon is missing? If you do that is part of the new bootloader. As soon as you get to where the icons are you are automatically in fast boot unless you select one of the icons.
I'm out at the moment but if you reply letting me know that you can get to the icons I will post a file when I get back and some instructions to downgrade you to old bootloader and compatible TWRP.
Click to expand...
Click to collapse
I figured my TWRP version might have been the culprit...
When I restart and hold the vol down button it normally would activate fastboot, now it goes directly to TWRP, no icons whatso ever. Before I would get the recovery icon, a usb (I think) and an option to wipe data. I can't get to that screen anymore. Is there a command in adb that will allow me to restart to fastboot from recovery? I myself am at work too so I will test anything I can in 3 - 4 hours. Thanks for taking the time to respond! :good:
So basically I won't be able to put TWRP 2.4.4.0 within my current version of TWRP?
TheYoz said:
I figured my TWRP version might have been the culprit...
When I restart and hold the vol down button it normally would activate fastboot, now it goes directly to TWRP, no icons whatso ever. Before I would get the recovery icon, a usb (I think) and an option to wipe data. I can't get to that screen anymore. Is there a command in adb that will allow me to restart to fastboot from recovery? I myself am at work too so I will test anything I can in 3 - 4 hours. Thanks for taking the time to respond! :good:
So basically I won't be able to put TWRP 2.4.4.0 within my current version of TWRP?
Click to expand...
Click to collapse
The version of TWRP you have will not mount the partitions you need to flash anything. You either need to downgrade the bootloader so that version of TWRP will work or get the version of TWRP back on there that was edited to work with the new 4.2.1 bootloader.
When you installed that partition.zip from energy rom it installed the new bootloader and the compatible twrp the same time. To go back he also has a zip that will restore old bootloader and old twrp. This is what you should have done.
What I am worried about now is the fact that you cannot even get to fastboot from the buttons.
Try adb reboot bootloader.
If that lets you in then download this .. http://flumpster.lolcakes.com/android/blob and place it in your fastboot directory.
Now type.
fastboot -i 0x0B05 flash staging blob
wait for it to fully flash and then type
fastboot -i 0x0B05 reboot
Give it about 20 seconds, if it doesn't restart then you will have to hold the power button down for 10 seconds to force a restart.
When it restarts it should now start to fill the blue line on the Asus screen which will flash the old bootloader and compatible TWRP. If it does this then great, just wait until it has finished and it should put you back into twrp where you will be able to install a rom off your external SD.
If it does not do the blue line then we have bigger probs and I hope you have nvflash backup files.
flumpster said:
The version of TWRP you have will not mount the partitions you need to flash anything. You either need to downgrade the bootloader so that version of TWRP will work or get the version of TWRP back on there that was edited to work with the new 4.2.1 bootloader.
When you installed that partition.zip from energy rom it installed the new bootloader and the compatible twrp the same time. To go back he also has a zip that will restore old bootloader and old twrp. This is what you should have done.
What I am worried about now is the fact that you cannot even get to fastboot from the buttons.
Try adb reboot bootloader.
If that lets you in then download this .. http://flumpster.lolcakes.com/android/blob and place it in your fastboot directory.
Now type.
fastboot -i 0x0B05 flash staging blob
wait for it to fully flash and then type
fastboot -i 0x0B05 reboot
Give it about 20 seconds, if it doesn't restart then you will have to hold the power button down for 10 seconds to force a restart.
When it restarts it should now start to fill the blue line on the Asus screen which will flash the old bootloader and compatible TWRP. If it does this then great, just wait until it has finished and it should put you back into twrp where you will be able to install a rom off your external SD.
If it does not do the blue line then we have bigger probs and I hope you have nvflash backup files.
Click to expand...
Click to collapse
Crossing my fingers... I will try what you mentioned and no, I don't have NVFLASH. Something that I have been meaning to do for a few weeks now too. Thanks for the help I will update when I get a chance to try.
Mikw
TheYoz said:
Crossing my fingers... I will try what you mentioned and no, I don't have NVFLASH. Something that I have been meaning to do for a few weeks now too. Thanks for the help I will update when I get a chance to try.
Mikw
Click to expand...
Click to collapse
You cannot do the nvflash process now. You could only do it while on ICS and there is no way back to ICS without having nvflash backups.
flumpster said:
You cannot do the nvflash process now. You could only do it while on ICS and there is no way back to ICS without having nvflash backups.
Click to expand...
Click to collapse
I am able to adb reboot bootloader, and it brings me to fastboot!
I successfully executed the steps you gave me but I didn't get the android screen with the blue line... it went back to TWRP 2.2.2.1. Can I fastboot the new version of TWRP?
TheYoz said:
I am able to adb reboot bootloader, and it brings me to fastboot!
I successfully executed the steps you gave me but I didn't get the android screen with the blue line... it went back to TWRP 2.2.2.1. Can I fastboot the new version of TWRP?
Click to expand...
Click to collapse
Tried one more time with no success... Please let me know if I have any other options since I can get to fastboot via ADB.
I think the reason I am running into this mess is because I didn't download the JB update from ASUS and move the system.blob file according to Urkel fresh start
TheYoz said:
Tried one more time with no success... Please let me know if I have any other options since I can get to fastboot via ADB.
I think the reason I am running into this mess is because I didn't download the JB update from ASUS and move the system.blob file according to Urkel fresh start
Click to expand...
Click to collapse
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
TheYoz said:
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
Click to expand...
Click to collapse
I was worried about this. I have seen loads of people with the same problem you have over on the tf300 forums.
They can access fastboot thru adb reboot fastboot and it appears to send the file over ok but then it doesn't work.
When you mentioned you couldn't get to fastboot by holding button combo it looked like the same prob as them.
Have a look at this thread. http://forum.xda-developers.com/showthread.php?t=2179874
flumpster said:
I was worried about this. I have seen loads of people with the same problem you have over on the tf300 forums.
They can access fastboot thru adb reboot fastboot and it appears to send the file over ok but then it doesn't work.
When you mentioned you couldn't get to fastboot by holding button combo it looked like the same prob as them.
Have a look at this thread. http://forum.xda-developers.com/showthread.php?t=2179874
Click to expand...
Click to collapse
So I probably need to send it to ASUS or wait for a solution? That is for the TF300 would I be able to use any steps for that device with mine?
Also,
I purchased this in January 2012 from best buy, any possibility I can go through them to have this issue fixed?
TheYoz said:
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
Click to expand...
Click to collapse
Flash the .img not the blob that should fix your issue.
Loco0729 said:
Flash the .img not the blob that should fix your issue.
Click to expand...
Click to collapse
I doubt it will but he can try.
No luck flashing the .img file instead. This is the worst
Flumpster thanks a bunch for all of your help. I ended up sending in the tablet, as expected they had to replace the motherboard.:
They quoted me this origionally:
Parts: $165
Labor: $65
Shipping $10
TOTAL $240!!!
I called and complained until my eyes popped out of my head and they ended up replacing the motherboad and shipped it back to me for $150. Now I think I'm going to sell this thing with the dock and buy a Nexus 10. Again, thanks for your help.
Another note... It will probably be a pain to unlock and root this thing again after the RMA im assuming. No more ASUS.
Hi, I did the update here - http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
And removed twrp. Obviously with my lack of knowledge I
made a mistake. Now I have stock recovery and the nabi freezes on the boot logo.
Any chance someone could help with getting it booting again or getting twrp back on.
gavjbrown said:
Hi, I did the update here -http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
And removed twrp. Obviously with my lack of knowledge I
made a mistake. Now I have stock recovery and the nabi freezes on the boot logo.
Any chance someone could help with getting it booting again or getting twrp back on.
Click to expand...
Click to collapse
If Jellybean is installed, then I think this is what you need to install TWRP for JB onto the Nabi:
http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
Once TWRP is on, your options for recovery are much wider.
gavjbrown said:
Hi, I did the update here -http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
And removed twrp. Obviously with my lack of knowledge I
made a mistake. Now I have stock recovery and the nabi freezes on the boot logo.
Any chance someone could help with getting it booting again or getting twrp back on.
Click to expand...
Click to collapse
Did you do everything else in thread or just that post? i.e. Did you update the bootloader too? http://forum.xda-developers.com/showpost.php?p=50356162&postcount=91
You will need TWRP one way or another. Use the ICS version if you didn't update the bootloader, and JB if you did.
Thanks for the help guys. I didn't realises until after that I needed to update the bootloader too, I'm guessing that's where my troubles start.
Just going to have a look at your links now, I know I could get twrp back on when it doest boot.
Thanks again.
Tried nabilab for ics and jb and both are no longer detecting my nabi.
When the nabi tries to boot the circle around the logo isnt even moving.
Still stuck with the Nabi, if anyone could help I'd really appreciate it. All I can do with it at the moment is boot to stock recovery.
gavjbrown said:
Still stuck with the Nabi, if anyone could help I'd really appreciate it. All I can do with it at the moment is boot to stock recovery.
Click to expand...
Click to collapse
So you installed the 2.2 ROM, but didn't update the bootloader. You have the stock recovery on it right now.
Can you get TWRP back on it?
Can you get into fastboot mode by pressing power and vol down?
aicjofs said:
So you installed the 2.2 ROM, but didn't update the bootloader. You have the stock recovery on it right now.
Can you get TWRP back on it?
Can you get into fastboot mode by pressing power and vol down?
Click to expand...
Click to collapse
Edited -
Yes put 2.2 on it but didn't update the boot loader. Tried to get twrp back on using nabilab buts the tablets no longer being detected .
Yes, I only have stock recovery. When I select fastboot protocol, I then get bootloader, continue, reboot-bootloader, reboot and power off.
gavjbrown said:
Edited -
Yes put 2.2 on it but didn't update the boot loader. Tried to get twrp back on using nabilab buts the tablets no longer being detected .
Yes, I only have stock recovery. When I select fastboot protocol, I then get bootloader, continue, reboot-bootloader, reboot and power off.
Click to expand...
Click to collapse
OK now you need to put TWRP back on it with fastboot when it's in that state.
Look in the TWRP thread, I'm mobile right now, but basically you need to open a command prompt where fastboot is located and then
fastboot flash recovery recovery.img
Thanks so much for getting me out of this mess. Twrp is back on so I should be ok now with a bit of trial and error.
Hi everyone,
I have a Wileyfox Swift 2 which came up with and update available. So I went ahead and installed the new update.
I hated it.
So I tried to install a ROM of the previous update using TWRP Recovery. Problem was I accidentally wiped the original OS the phone was running one without having the ROM I wanted to install on the phone (It was my first time doing something like this). I had no access to the phone apart from the fastboot and TWRP Recovery Screens. I emailed Wileyfox Tech Support and told them what happened. They sent me several versions of the stock OS (the new one I wanted to get rid of, but I would be glad to get it working at all at this point).
I ended up having to use ADB Sideload to get the ROM on the phone and I'm pretty sure it is installed properly. Problem is: when I boot it up these messages come up:'your device software can't be checked for corruption, please lock your bootloader' and then 'dm verity not started in enforcing mode' for 5 seconds, and then it just gets stuck on the white booting up screen until I turn it off or go into Recovery. I know how to fix the bootloader lock error but that erases all user data on the phone. I really need to sort this out so what should I do?
Would appreciate any help,
Thanks!
By the way I don't really care about any data on the device, everything is backed up elsewhere.
After flashing the rom you can use adb in twrp recovery with the following command: adb reboot "dm-verity enforcing"
This should remove the dm verity message and allow your phone to boot.
Thank You
But do you mean have TWRP Recovery open on the phone and have ADB command window open on the computer and type the command because I've done that and it comes up with 'error: device null not found'.
I'm completely new to this sort of thing so as much detail as possible would be appreciated.
Yes, you have to have twrp open and on your pc the adb windows. First type adb devices to see if windows recognizes your phone. Mine says 50580003 recovery, when I type the command. If you get an error, you'll probably need to install the driver in device manager.
Ok thanks for confirming that for me. The problem is that my phone doesn't even show up as being connected to my computer and I can't access the phone's OS to turn on USB Debugging, so when I type the command 'fastboot devices' nothing comes up. Is there a way to do this from TWRP Recovery?
Hmm.... You could try installing the old cyanogen of and use that to enable usb debugging. Alternatively you could try flashing Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 . I never tried it but it should work also.
BlueSheep274 said:
Ok thanks for confirming that for me. The problem is that my phone doesn't even show up as being connected to my computer and I can't access the phone's OS to turn on USB Debugging, so when I type the command 'fastboot devices' nothing comes up. Is there a way to do this from TWRP Recovery?
Click to expand...
Click to collapse
Reboot your phone to fastboot mode from TWRP (reboot>bootloader) or the wileyfox boot menu then flash this file
(https://drive.google.com/open?id=0B34ZucLt1HQ9YjFRQ0otbmFRc28)
from your computer with fastboot.
It will also overwrite your recovery, system, data and internal storage partitions.
Facing same/similar problem
boa05 said:
Reboot your phone to fastboot mode from TWRP (reboot>bootloader) or the wileyfox boot menu then flash this file...
(link removed to allow first-time post)
from your computer with fastboot.
It will also overwrite your recovery, system, data and internal storage partitions.
Click to expand...
Click to collapse
Unfortunately the download link you provided is no longer available, would you mind reposting please?
I got the link working. Thanks for sharing. Unfortunately, flashing them failed with the following:
"Updater process ended with ERROR: 7"
Googling the error code, I found this: //.lineageosdownloads(dot)com/fix-error-7-lineage-os/ but I'm still just going round in circles trying to get OTA updates, re-flashing, rebooting into dastboot, losing adb connections and on and on....
markusmunch said:
Unfortunately the download link you provided is no longer available, would you mind reposting please?
Click to expand...
Click to collapse
Sorry about it, here is a reuploaded version.
Exact same problem
Having made exactly the same mistake as the OP, I've managed to re-install the old version of CyanogenOS but I can't get updates OTA or get rid of this dm-verity enforcing error on boot up. Any help would be massively appreciated.
markusmunch said:
Having made exactly the same mistake as the OP, I've managed to re-install the old version of CyanogenOS but I can't get updates OTA or get rid of this dm-verity enforcing error on boot up. Any help would be massively appreciated.
Click to expand...
Click to collapse
Just download the nougat ROM from Wileyfox, they will send you a link if you ask them. Then you can flash boot and system (and if you like all other partitions and radios) and it will then be on nougat and working correctly.
Scott
Worked
RedNas74 said:
After flashing the rom you can use adb in twrp recovery with the following command: adb reboot "dm-verity enforcing"
This should remove the dm verity message and allow your phone to boot.
Click to expand...
Click to collapse
I have been living in dm-verity hell for the past 4 hours trying to fix my phone after a bad firmware flash (4.1.3 replacing a bad SuperSU uninstall), even trying various 4.0.2 firmwares and full packages, as well as a full-phone restore to a previous TWRP backup I had from a few days ago.
I have absolutely no idea why none of the other methods at all worked (such as the simple fastboot oem disable_dm_verity then re-enable command), but this one finally did it on 4.1.3 *fingers crossed it stays that way*