Related
Early today, I was working on a G2 trying to get it rooted with a custom ROM installed. I managed to root the phone and disable the bootloader security. From here, I attempted to install clockwork recovery via rom manager... here's where the disaster starts.
Everything seemed to be going well (no errors), so I tried to load a custom ROM. The Rom installation started but failed partway through. This is when I noticed that the clockwork recovery wasn't working properly. It was flickering and none of the options worked (screen just flashed or turned black if you selected anything). So at this point, the phone would not boot since the ROM installation didn't complete, and I had a buggy recovery image installed.
Unfortunately, the fun doesn't stop here. I figured that I should load the PC10IMG.zip and start from scratch... bad idea. This flashed the bootloader (relocking it) then failed-- leaving me with a bad ROM, bad recovery image, and a locked bootloader. Luckily for me, I was able to use adb via the buggy recovery to unlock the bootloader again.
At this point, I got a bit antsy and jumped the gun. I decided to use fastboot to erase and load a new recovery image. Unfortunately, I realized that I didn't have a recovery.img file to flash... just after I used the fastboot erase recovery command.
I'm hoping that someone here has a recovery.img file compatible with the T-Mobile G2 so I can flash the recovery partition with fastboot. If anyone has any better ideas I'm open to suggestions.
Thanks in advance for any help.
Install amon recovery. It's much better then clockword. Do it using adb
Sent from my HTC Hero using XDA App
Just an update. I couldn't get into adb but I was able to flash clockwork via fastboot. For whatever reason, the amon recovery would go through. Nevertheless, I installed cyanogen using clockwork and everything is gravy!
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.
OK so I was on "HairyBean v2.31" and decided to try "CROMBi-kk". So I first flashed "TWRP-TF300T-2_7_0_1.zip" as instructed in the "CROMBi-kk" instructions. Then I flashed "CROMBi-kk" everything seemed to go fine but after reboot I was stuck at the "CROMBi-kk" boot animation. So I wanted to go back to "HairyBean v2.31" so flashed "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". When I got back to HairyBean TWRP I first tryed to Format DATA, well this got stuck and had no choice but to hard reboot. Now when I go back into TWRP I get a screen that asks for a password. I can hit cancel and get passed it, but I can't mount any of the partitions. So this is where in stuck. I do have an NVflash backup. Can someone please help me get out of this mess.
shatterstar78 said:
OK so I was on "HairyBean v2.31" and decided to try "CROMBi-kk". So I first flashed "TWRP-TF300T-2_7_0_1.zip" as instructed in the "CROMBi-kk" instructions. Then I flashed "CROMBi-kk" everything seemed to go fine but after reboot I was stuck at the "CROMBi-kk" boot animation. So I wanted to go back to "HairyBean v2.31" so flashed "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". When I got back to HairyBean TWRP I first tryed to Format DATA, well this got stuck and had no choice but to hard reboot. Now when I go back into TWRP I get a screen that asks for a password. I can hit cancel and get passed it, but I can't mount any of the partitions. So this is where in stuck. I do have an NVflash backup. Can someone please help me get out of this mess.
Click to expand...
Click to collapse
Try this:
Possible Unbrick Solution for Unrecoverable Bootloader & Wrong TWRP Flashes
If that doesn't work you'll have to recover through NVFlash backups.
Restorer said:
Try this:
Possible Unbrick Solution for Unrecoverable Bootloader & Wrong TWRP Flashes
If that doesn't work you'll have to recover through NVFlash backups.
Click to expand...
Click to collapse
Thanks i'll give that a try, but if that fails is their a guide on how to use NVflash to restore my backup? All I can find is how to backup using NVflash but nothing on restoring it.
shatterstar78 said:
Thanks i'll give that a try, but if that fails is their a guide on how to use NVflash to restore my backup? All I can find is how to backup using NVflash but nothing on restoring it.
Click to expand...
Click to collapse
There's plenty in these threads but read them right through carefully first. I've never bricked mine so I have no idea what problems you might encounter. The last two are older guides written before Flatline for JB but info is still relevant. Ignore any stuff about CWM or ROM Manager.
http://forum.xda-developers.com/showthread.php?t=2538028
http://rootzwiki.com/topic/35086-gu...s-guide-unbrickrecoverdowngradeupgrade-tf201/
Same guide but with XDA experiences:
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Restorer said:
There's plenty in these threads but read them right through carefully first. I've never bricked mine so I have no idea what problems you might encounter. The last two are older guides written before Flatline for JB but info is still relevant. Ignore any stuff about CWM or ROM Manager.
http://forum.xda-developers.com/showthread.php?t=2538028
http://rootzwiki.com/topic/35086-gu...s-guide-unbrickrecoverdowngradeupgrade-tf201/
Same guide but with XDA experiences:
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Click to expand...
Click to collapse
I can't tank you enough for your help in pointing me in the right direction. I'm now back up and running:good: The first guide got me close, but did not fully unbrick, so I got creative. I will list the steps I took to maybe help others out.
1. First you need Fastboot get it here(http://matthill.eu/content/downloads/transformerprime-unlock/fastboot.zip)
1b. You will need the Universal_Naked_Driver found here (http://matthill.eu/content/downloads/transformerprime-unlock/Universal_Naked_Driver_0.72.zip)
1c. Unzip the drivers somewhere, if at any point during this guide Windows detects your tablet as an unknown device, point it to this location for the drivers.
2. Unzip fastboot.zip somewhere preferably in C:\ (I found that folder names with spaces can cause problems)
3. Download the official update for your device from Asus. Make sure you get the right one, US, EU, WW, etc.
4. Unzip the update twice so that way you have a blob file.
5. Place the blob file into your fastboot folder.
6. Open a command prompt and navigate to your fastboot folder and enter the fallowing commands.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
This next command will take the longest. Also you will notice the green RCK icon will stop flashing and you will have a blue progress bar, This is normal. Do not run the last command(reboot) until the green RCK logo starts flashing again and the blue progress bar is full.
fastboot -i 0x0B05 flash system c:\fastboot\blob (your path may vary depending where you placed the fastboot folder)
Now that all is done run the last command.
fastboot -i 0x0B05 reboot
If you are back up and running congratulations you are unbricked, but if you are stuck at the white Asus logo follow the next additional steps. Only do this if you are not fully booting up after the first part of this guide.
1. You will need a microsd card(32G max) and has to be formatted to Fat32.
2. Next you are going to take the Asus update you downloaded above, and unzip it ONLY ONCE and rename it to EP201_SDUPDATE.zip
3. Place the newly renamed EP201_SDUPDATE.zip on your sdcard, make sure its on the root directory and not in a folder.
4. Now reboot to fastboot (Hold Power and Volume Down) Press Volume Up when the white text at the top appears.
5. When the fastboot menu comes up with RCK icon selected press Volume up.
6. Go have a beer, this will take some time. Do not touch anything, when it is done the Asus configuration wizard will be displayed.
7. Congratulations you are now hopefully fully unbricked.
Some Tips:
1. Make sure you have "Show File Extensions" enabled in Windows, if not then when you rename the update to "EP201_SDUPDATE.zip" it will actually be "EP201_SDUPDATE.zip.zip".
2. Use Windows 7 if possible, Windows 8 just causes problems.
3. Disable Windows UAC or run fastboot as administrator.
4. Use a stock OEM data cable.
5. Make sure you have a fully charged tablet, cant stress this enough if your battery dies during this process, then you are in some serious trouble.
Credit goes to Buster99 for discovering the first part of this guide.
Bricked my prime
Hello, I have a big problem. I am in the possession of a TF201 and wanted to install the slimkat-rom for the Tf201. I had the topical Bootloader with Harybean V2.31 installed.
Then I have the Recoery (form the Startpost of the rom) in my present Rocovery installed (Custom TWRP v2.7.1.0 JB/KK for TF300T [with device checking] | STABLE)
Afterwards I have restarted the device. Everything functioned perfectly... on it I have booted up in the Recovery. In it I made a Factory-Reset. This became not explained... the device approx. 1 hour got stuck.
On it there I have restarted the device by hand... now I have the problem that I do not come any more to the Recovery. The device hangs with the picture "Teamwin"... I can do nothing more....also i can not go into the fastboot mode!??? (with the volume down button)
I already tried the solution about abd...but in cmd (Windows) always comes the statement "waiting for device"
What have I wrong made... what I can make? Can somebody help me? Please....
sorry for my bad english, thanks
maze44 said:
Hello, I have a big problem. I am in the possession of a TF201 and wanted to install the slimkat-rom for the Tf201. I had the topical Bootloader with Harybean V2.31 installed.
Then I have the Recoery (form the Startpost of the rom) in my present Rocovery installed (Custom TWRP v2.7.1.0 JB/KK for TF300T [with device checking] | STABLE)
Afterwards I have restarted the device. Everything functioned perfectly... on it I have booted up in the Recovery. In it I made a Factory-Reset. This became not explained... the device approx. 1 hour got stuck.
On it there I have restarted the device by hand... now I have the problem that I do not come any more to the Recovery. The device hangs with the picture "Teamwin"... I can do nothing more....also i can not go into the fastboot mode!??? (with the volume down button)
I already tried the solution about abd...but in cmd (Windows) always comes the statement "waiting for device"
What have I wrong made... what I can make? Can somebody help me? Please....
sorry for my bad english, thanks
Click to expand...
Click to collapse
Did you do a NVflash backup before all of this happened? If you did you can follow this guide to unbrick http://forum.xda-developers.com/showthread.php?t=2538028
I think the problem is "TWRP v2.7.1.0". I'm going to look more into it to see if I can figure what the problem is.
Thank you so much for the instructions post above. If you figure out what went wrong with flashing that rom, I would like to know too.
dangoon said:
Thank you so much for the instructions post above. If you figure out what went wrong with flashing that rom, I would like to know too.
Click to expand...
Click to collapse
Well I made some progress, I figured out why I could not mount partitions. Turns out that when I hit "Format Data" and thought that it froze, well it did not freeze it just takes really long to finish(~30min). Now I can install it, but no matter what I try it all ways gets stuck at the 4 penguins on the latest version or the bootanimation on the older version. I have tried every combination of twrp recovery's, kernals and varies versions of the rom, but still no luck. I have tried probably every rom available for this tablet and this is the only rom that just refuses to install. From the sounds of some of the problems this rom has I really don't want to use it, but now im so pissed off that I have to figure out why the hell this thing is not working I just cant quit.
[UPDATE]
Ok got it all squared away. Everything all up and running. The second part of my problem (getting stuck at bootanimation) was caused by doing a factory reset before flashing. So the correct way to flash it is...
1. Make sure you are on the Hairy Bean Bootloader.
2. Make sure you are using a 2.7 TWRP.
3. First Format Data. (It will take long, about 30mins)
4. The go into Advanced Wipe and check everything except SDCard.
5. When it's finished reboot, If all went well you should only be at the bootanimation for about 5mins.
Also if you get the four penguins after reboot, then you did something wrong.
Perfect
Legthy, but OMG thank you very much,
thought I was screwed..
I had to do the second part as well, now I get the Asus Setup , to finalize .
Great work, Thanks again.
Madd Macc
Okay so in an effort to move to 4.4.2 (CM11) on my TF201 I tried to load the Hairybean bootloader. It worked. BUT, the problem is, it removes the USB option in recovery and because of that, I cannot fastboot push a newer recovery - like TWRP - because Fastboot is looking to connect via the USB selection in recovery.
The recovery I have now is an old, old TWRP that was needed to install Hairybean bootloader and then you are suppose to push the newer TWRP - which I had first and which I used to make a nandroid backup - but now I cannot connect to my computer and have it be seen and fastboot the newer TWRP to the tablet. This is because, for some crazy reason, Hairybean removes the USB connection method when you boot into recovery and you only get: RCK, Android, Wipe.
So my thought was to just install the original TF201 bootloader (but I have no idea where to get such a thing), then push the newer TWRP, then restore my system with my TWRP nandroid backup and get on with life as it was before I bad this bad choice.
Any ideas on where I can get a TF201 bootloder that will give me back USB connection when I boot into recovery so I can then fastboot the newer TWRP and restore?
Lock-N-Load said:
Okay so in an effort to move to 4.4.2 (CM11) on my TF201 I tried to load the Hairybean bootloader. It worked. BUT, the problem is, it removes the USB option in recovery and because of that, I cannot fastboot push a newer recovery - like TWRP - because Fastboot is looking to connect via the USB selection in recovery.
The recovery I have now is an old, old TWRP that was needed to install Hairybean bootloader and then you are suppose to push the newer TWRP - which I had first and which I used to make a nandroid backup - but now I cannot connect to my computer and have it be seen and fastboot the newer TWRP to the tablet. This is because, for some crazy reason, Hairybean removes the USB connection method when you boot into recovery and you only get: RCK, Android, Wipe.
So my thought was to just install the original TF201 bootloader (but I have no idea where to get such a thing), then push the newer TWRP, then restore my system with my TWRP nandroid backup and get on with life as it was before I bad this bad choice.
Any ideas on where I can get a TF201 bootloder that will give me back USB connection when I boot into recovery so I can then fastboot the newer TWRP and restore?
Click to expand...
Click to collapse
When you go to the HairyBean bootloader it is normal for the USB icon to disappear ... This has nothing to do with HaiyBean, it is how Asus started doing it.....
The tablet will now boot directly into fastboot ...
Take a look, boot into your bootloader screen and in the upper left, it will say ......
"Starting fastboot USB download protocol"
Thx Josh
lj50036 said:
When you go to the HairyBean bootloader it is normal for the USB icon to disappear ... This has nothing to do with HaiyBean, it is how Asus started doing it.....
The tablet will now boot directly into fastboot ...
Take a look, boot into your bootloader screen and in the upper left, it will say ......
"Starting fastboot USB download protocol"
Thx Josh
Click to expand...
Click to collapse
It is certainly HairyBean related, not Asus related.
My Asus TF201 always, always, always had the USB icon when I went into recovery (RCK, Android, Wipe, USB). Not only that, it was there for the 10 times the same day I used it to use fastboot to push and try 3-4 different recoveries.
Then, when loaded up the HairyBean, the very next boot, USB was gone as a selection. That change had nothing to do with Asus. So not sure what you mean "it is how Asus started doing it" as that is not how my tablet was and no changes I made were Asus related - they were installing a recovery and HairyBean.
Anyway.. You are correct that it does say in white text that it is booting to fastboot BUT the issue is, fastboot stopped allowing me to push recoveries to the tablet from that moment on. So, the 10 times the same day I tested and tried different recoveries (CWM, TWRP, FlatLine, etc.), I could connect my PC to my tablet, select USB at recovery, and use fastboot to push a recovery. Now, when I try to do the same, fastboot does not push the recovery as it says no device found or connected (some error like that).
So in my mind, the loss of the USB icon and the sudden inability to push recoveries via fastboot is no coincidence. So, that is why I asked if there was a way for me to roll back.
So I am not sure what to do now? The old TWRP that came with the HairyBean install does not see my TWRP backup so I cannot roll back. So, my thought was if I could push the newest TWRp - the one I had and made my backup with prior to HairyBean - I could flash my backup and be back to 4.1.1.
Thoughts? The goal is to just get back to a booting TF201.
ps - at the same time, I have lost the ablity to even boot into Android.
Lock-N-Load said:
It is certainly HairyBean related, not Asus related.
My Asus TF201 always, always, always had the USB icon when I went into recovery (RCK, Android, Wipe, USB). Not only that, it was there for the 10 times the same day I used it to use fastboot to push and try 3-4 different recoveries.
Then, when loaded up the HairyBean, the very next boot, USB was gone as a selection. That change had nothing to do with Asus. So not sure what you mean "it is how Asus started doing it" as that is not how my tablet was and no changes I made were Asus related - they were installing a recovery and HairyBean.
Anyway.. You are correct that it does say in white text that it is booting to fastboot BUT the issue is, fastboot stopped allowing me to push recoveries to the tablet from that moment on. So, the 10 times the same day I tested and tried different recoveries (CWM, TWRP, FlatLine, etc.), I could connect my PC to my tablet, select USB at recovery, and use fastboot to push a recovery. Now, when I try to do the same, fastboot does not push the recovery as it says no device found or connected (some error like that).
So in my mind, the loss of the USB icon and the sudden inability to push recoveries via fastboot is no coincidence. So, that is why I asked if there was a way for me to roll back.
So I am not sure what to do now? The old TWRP that came with the HairyBean install does not see my TWRP backup so I cannot roll back. So, my thought was if I could push the newest TWRp - the one I had and made my backup with prior to HairyBean - I could flash my backup and be back to 4.1.1.
Thoughts? The goal is to just get back to a booting TF201.
ps - at the same time, I have lost the ablity to even boot into Android.
Click to expand...
Click to collapse
Well it sure looks like to me that the tablet is in fastboot for sure without the icon as that is how ASUS does it for the TF300T bootloader ending in 27.1
And you are on a TF300T bootloader now so yes it has everything to do with Asus ...
It sounds like to me that your PC has the driver for a 201 not a 300 for fastboot
Check device manager on your PC make sure it see your device in fastboot mode....
Thx Josh
Okay the 201 driver versus a 300 driver makes some sense. But it still does not explain while it will now not boot into Android.
Device manager shows my Asus attached BUT fastboot, since the Hairybean, stopped accepting my ability to push recoveries.
I only went to Hairybean as it offered a path to get to 4.4.2 (others with Tf201's reported doing so) and now I kind of don't care I would just like to get the tablet back to a state I can use it. So if I can install a Hairybean bootloader, why cannot I not just install a TF201 official bootloader? Is that possible? If so, where do you find such?
My goal is to just get a bootable usable tablet back - any thoughts on what I should do now?
Lock-N-Load said:
Okay the 201 driver versus a 300 driver makes some sense. But it still does not explain while it will now not boot into Android.
Device manager shows my Asus attached BUT fastboot, since the Hairybean, stopped accepting my ability to push recoveries.
I only went to Hairybean as it offered a path to get to 4.4.2 (others with Tf201's reported doing so) and now I kind of don't care I would just like to get the tablet back to a state I can use it. So if I can install a Hairybean bootloader, why cannot I not just install a TF201 official bootloader? Is that possible? If so, where do you find such?
My goal is to just get a bootable usable tablet back - any thoughts on what I should do now?
Click to expand...
Click to collapse
Yes we got him all fixed up
it took some doing but we got it with my nvflash steps starting at the fastboot commands ..
We did back up his nvflash blobs also
@Lock-N-Load can you plz add SOLVED to the thread title
Thx Josh :laugh:
Fixed up is an understatement... Josh knocked it out of the park in helping me get back the tablet I was sure was toast. Not only is it not toast, it is now like a new tablet. When you come from 4.1.1 to this.... stunning. Thanks Josh!
Hi all, in general I tried to put EliteRom, the phone went into a fastboot loop, I even tried through miflash, still can not get out of the fastboot. I don't know what to do.
It seems to me that this happened because I immediately after unlocking bootloader through MiFlashUnlock went to fastboot and tried to put elitrom through fastboot respectively. There it seemed to go successfully, but stopped at some process (setting to A, I don't remember exactly), it went very long, about 10 minutes nothing happened, I thought that the process had already finished and tried to boot into the system, but got back into the fastboot. Then I tried to install TWRP via adb, everything seemed to work, but I could not boot into the recovery via volume+on/off or the adb command.
Despaired, decided to return everything as it was through miflash, chose the item that the bootloader is not locked, and the installation failed. Then i chose to lock the bootloader and it seems to say it worked.
Yay, but no, the phone is still hanging in the fastboot and won't start up. Please help the fool, I don't want to go to the service, but I really don't know what to do anymore.
And when I try to put EliteRom again, the console at some point just kicks out
Well dunno what will say others but I have been through this shiet too and ended up in Xiaomi service .. but yeah, you'll wait like week or two...btw no worries about warranty problems cause unlocked bootloader,they don't give a crap..
Hi, try to flash a12 twrp(link is in the xda k50gt) throught fastboot (fastboot flash recovery bla-bla.img), then wipe everything in the wipe section. Install recovery miui.zip then flash. I couldn't understand that you flashed twrp via adb command in bootloader mode?