I recently acquired an asus tf101 that was rooted running katkiss and twrp. I changed it to cm10 and now it wont boot on its own or load twrp it just hangs on "Booting recovery kernal image" i have tried everything i could find online such as EasyFlasher and the twrp app but the app wont let me flash the image for some reason (it does havce rooting permitions btw). If anyone could help find out whats going on it would be helpful. I atached some images if that helps.
Thanks in advance.
William
HI SuperUserWilliam
I have the exact same problem you are having and also my tf101 was rooted with katkiss and since I changed it to cm, I cannot boot into recovery or bootloader. Please let me know if you find a way out of this because I am going to have to trash my tf101 otherwise. Thanks.
VA3JLF
I wish I could help you guys but I can't even get my TF101 rooted since the batteries won't hold a charge.
Related
I think I semi-bricked my xoom.
I installed the new VTL-Launcher posted here http://www.xda-developers.com/android/tablet-oriented-launcher-vtl-launcher-now-in-beta/
and upon reboot, the xoom just stays looping the honeycomb boot animation.
My xoom was not rooted, and completely stock before this.
I tried to recover doing a hard reset as detailed here: https://motorola-global-portal.cust...rola-xoom---master-reset-/-factory-data-reset
but this also does not work. The option of recovery never presents itself.
I can still access the device with fastboot, but thats it really... I do not know what to do with it.
Please help, as I do not really know what to do beyond this.
If you can still access the fastboot you should be able to reflash the stock image.
3G/4G - http://forum.xda-developers.com/showthread.php?t=980803
WiFi - http://forum.xda-developers.com/showthread.php?t=1017398
Wow, really?
I've just downloaded this, and debating if I should or should not install... I guess I wont.
I hope you can get your issues resolve.
Have a look here
http://forum.xda-developers.com/showthread.php?t=973355
happened to me too with vtlauncher... i reflashed all my partitions and relocked my boot loader, then used the one click gui to root with the latest tiamat kernel
And now I can't boot into recovery, it simply freezes at the "Asus" screen.
A quick flip through the forums reveals that it wasn't the smartest thing I have ever done. I can cold boot into Linux and the transformer works fine but I'd like to get everything up and operational.
I tried using the RecoveryInstaller.apk from gnufabio to no avail. Could someone perhaps provide some assistance on what I should do next? It should be noted that I don't have the faintest clue on how to do the 'adb push' operations I've read about.
TIA
PERI
Use my tool, just ignore the rooting stuff since I'm assuming you're already rooted.
Everytime the tab reboots during the tool, make sure to be hold down Volume-Down and cold boot into Android, then continue the script. Once it has flashed recovery you can close it, it doesn't need the root stuff.
Don't use ROM manager
ToD
Hi and thanks for the help and quick response.
I downloaded PERI and followed the instructions except for the part regarding SU as I already have it installed. For each reboot I ended up having to cold boot into linux.
Unfortunately, the final step where the .bat reboots while I hold the vol -, then hit vol +, gets stuck at the "Booting recovery kernel image" part and will not progress.
I'm not currently running ICS but gingerbread. I probably should have mentioned that earlier, sorry.
What should I try next?
Peri only works on ICS.
Now why on Earth are you running GB on the transformer??? Where did you even get a GB rom?
Do you mean Honeycomb?
Ooops (again)! Yes, you are correct. It was a Honeycomb ROM. An old version of Revolver.
gotreef said:
Ooops (again)! Yes, you are correct. It was a Honeycomb ROM. An old version of Revolver.
Click to expand...
Click to collapse
whats your tf's serial number?
Hi,
The Model is TF101 and the serial starts with B60. Does that help? I know that there are several variants of the transformer out there and I'm not sure what the differentiating markings are.
Nvflash for Sbkv1 is now your best bet, since you have a b60 you can use it on windows fine, good luck :]
Search 'Nvflash unbricking released' and you'll find it.
NV Flash worked like a charm. I really appreciate it, I don't think I would have found that program on my own.
Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!
xxboarderxx said:
Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!
Click to expand...
Click to collapse
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.
OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.
I think you could mean a kind of recovery loop: There is a file called "command" on the cache partition which causes the recovery image to boot. But if the recovery is broken then it will not empty cache. The recovery will boot but does not update screen (showing just boot splash). On the next time it will boot again ...
Please be just carefully: "wipe data" in the fastboot menu will create the "command" file.
ScottBroker said:
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.
Click to expand...
Click to collapse
Sorry...if I could have made this attempt last week, I may have been able to help you then. :sly:
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
opethfan89 said:
OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.
Click to expand...
Click to collapse
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
xxboarderxx said:
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.
I was smiling as I read the first post, but this is going to come in real handy if I nuke my bootloader. Thanks. I wish I had gotten to this first, heh, I could have told you don't flash a Jellybean ROM over an ICS bootloader, it won't boot.
Good information to have though. Thank you!
opethfan89 said:
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.
Click to expand...
Click to collapse
:good:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
You can do it if you have a custom recovery already flashed like TWRP or CWM. But I agree with you - after you start having a basic understanding of Android customization, there's no reason why you would want to use 'wipe data' from the volume down+power.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?
opethfan89 said:
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?
Click to expand...
Click to collapse
Automatically gets flashed when you flash stock.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
If you are in recovery loop you cannot go into the fastboot menu. The only way to get the stock recovery back is to use nvflash.
Ok, so here's my situation.
I bought a used Transformer Pad TF300T off Craigslist and it was already unlocked and rooted with ClockworkMod and CyanogenMod. Well, I have no use for all that, so I wanted to reflash to the most current stock firmware. Well, I downloaded the absolutely wrong firmware with the wrong SKU (JP and I live in US) and now I have a Japanese tablet. :/
After much work, I finally got it re-rooted with ClockworkMod v6.0.1.0 so I can install zip from sd card. However, any US or WW SKU firmware I try to install, after the install is complete and I reboot, right underneath the "The device is unlocked" text is "Signature mismatch" in red text.
I tried to install CM 9 & 10 to see if that would help, and it appears to install but it goes from loading 1% to 100% in about a second, and then gets stuck at the ASUS screen.
So, is there anyway someone can guide me? I'm sure I've done some stuff bass ackwards, but I'm only intermediate at hacking and modding, so help is appreciated. I've been scouring forums for weeks, so I give. Help please?
Oh man, this is the best forum. I no longer need assistance because I found the answer
HTML:
http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
here!!! Yay!!!!!
Im not sure how to mark this solved or delete or anything.I'm sorry!
I made the same mistake
TheLovelyFox said:
Ok, so here's my situation.
I bought a used Transformer Pad TF300T off Craigslist and it was already unlocked and rooted with ClockworkMod and CyanogenMod. Well, I have no use for all that, so I wanted to reflash to the most current stock firmware. Well, I downloaded the absolutely wrong firmware with the wrong SKU (JP and I live in US) and now I have a Japanese tablet. :/
After much work, I finally got it re-rooted with ClockworkMod v6.0.1.0 so I can install zip from sd card. However, any US or WW SKU firmware I try to install, after the install is complete and I reboot, right underneath the "The device is unlocked" text is "Signature mismatch" in red text.
I tried to install CM 9 & 10 to see if that would help, and it appears to install but it goes from loading 1% to 100% in about a second, and then gets stuck at the ASUS screen.
So, is there anyway someone can guide me? I'm sure I've done some stuff bass ackwards, but I'm only intermediate at hacking and modding, so help is appreciated. I've been scouring forums for weeks, so I give. Help please?
Click to expand...
Click to collapse
I accidentally flashed the JP firmware on my tf300t, I was trying to update from 4.1.1. Now my recovery (was CWM 6.0.x.x) shows a dead droid when I go into RCK. I am searching around and can not find a way to reinstall CMW without using the fastboot method. How were you able to get it installed? I feel like such a moron for flashing the wrong SKU.Any help here would be SUPER appreciated.
Hello guys need help my tab got stuck on Asus logo and then i used the Easyfalsher and US Firmware but now my phone got stuck only Boot recovery i used the SBK2 methode to be honest i didnt know how to check the version of SBK but with the first one i tried it didnt work checked secound one it worked also installed ROM but tab just wont start up only in recovery mode
Can someone please help me about this issue its kinda urgent
ReMuSeR said:
Hello guys need help my tab got stuck on Asus logo and then i used the Easyfalsher and US Firmware but now my phone got stuck only Boot recovery i used the SBK2 methode to be honest i didnt know how to check the version of SBK but with the first one i tried it didnt work checked secound one it worked also installed ROM but tab just wont start up only in recovery mode
Can someone please help me about this issue its kinda urgent
Click to expand...
Click to collapse
I don't know if the DEV thread is the right place for your question.. However this this: use the Tubuntu flasher and flash back a old ROM (see the tubuntu thread for a guide).. At least it should get it going again.. However you will loose your data.. You maybe better posting in the help and troubleshooting thread.. not DEV.
Also I am sure there is a better way of fixing it.. But I live in the world of Linux on the TF101