[Q] Stock ROM TF101 will not boot. - Eee Pad Transformer Q&A, Help & Troubleshooting

So yesterday, while writing a review of a movie on my Asus Transformer, it suddenly rebooted and got stuck in a boot cycle. No big deal, this has happened a lot since the ICS update(s). So I tried a warm boot, following that failure with a cold boot. Nothing worked. As a matter of fact, the whole screen went dark and wouldn't even try to boot. I'm pretty average in my Android knowledge, so off I go to the interwebs to find a solution. After an hour of reading or so, I determine that perhaps a reinstall of ICS would be my best bet. After all, there isn't much on the tablet that wasn't backed up.
I attempt the NVFlash process via my laptop. It seemed to start to work but suddenly closes before writing to the partitions (or so I'm led to believe). My screen is now alive with:
"Entering NvFlash recovery mode / NvSp server
Chip Uid: 0370014841601257"
Suddenly, I am out of my league and frustrated that this unit won't respond to anything I do.
Anyone have any advice or a stickythread that they can recommend?
I greatly appreciate any help you can give.
Thanks,
Gary

Android is vulnerable in virus/trojan or such attacked.. So be vigilant about it and have android antivirus installed.
And your issue should start from booting into stock recovery and perform factory wipe before attempting the nvflash.
Now Nvflash work only for TF101 with serial B60 and below. Check yours for the nvflash compatibility.
Sent from my Transformer TF101 using XDA Premium HD app

farsight73 said:
Android is vulnerable in virus/trojan or such attacked.. So be vigilant about it and have android antivirus installed.
And your issue should start from booting into stock recovery and perform factory wipe before attempting the nvflash.
Now Nvflash work only for TF101 with serial B60 and below. Check yours for the nvflash compatibility.
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
Mine is a B60, so I thought it would work. Also, I cannot get into the stock recovery to wipe it, it's refusing to respond to anything except APX. Even then it doesn't do much but fail at NVFlash.
And I did have Avast installed for antivirus.

Additionally, I was able to see that when running NvFlash, it stops right after "creating partition: GPT" and closes itself out. What, if anything, might I be doing wrong here?

also try using NVFLASH from another PC/laptop.
I had some problems making backup with nvflash on 1 pc. Using the other pc solved my problem.
Don't know if it works for you

Related

Unbricking with nvflash(lesson learned)

I ended up soft bricking(if you can get into apx mode or recovery, its not really bricking) by TF today and couldnt get into recovery mode. Although, I was able to get into apx mode. Using the unverisal rootkit, I was unable to restore or install new roms onto the device. But using the vanilla nvflash for the tf, and by extracting the files inside of the prime 2.1 download to the root of the nvflash folder, I was able to get prime installed
Just wanted to post my experience in case this could help someone.
thanks?!
this helped me recover from a soft brick on my b70. i spent all day trying to find a way to fix my transformer(universal rootkit thingy didnt help..) and in the end i saw this post thingy. thank you!!!!
Your welcome
It took me an entire day to figure this out.
Sent from my SAMSUNG-SGH-I777 using xda premium
I had a similar affair while rooting and ended up installing Prime v1.4 I think it was at the time. As long as you have nvflash and APX mode working, there is still some hope lol.
Sent from my Transformer TF101 using Tapatalk

Transformer going insane

So, Recently a family member of mine told me something was wrong with their transformer. I take a look at it and it's not turning on so i assume it's not charged. I plug in the charger and it does not boot up. The transformer only goes to the eeepad screen with the asus logo and shuts off again. Basically it's in a bootloop but problem is, the tf101 is not rooted or tampered with and on stock fw (Tf101 is a b90 model) Anything i can do to fix??? Couldn't have been any sort of virus either as this transformer was only used for video streaming/ listening to music...
http://www.youtube.com/watch?v=DgCRfgGpwBw&feature=youtu.be
It might need to be reflashed. You could try using the wheelie tool, but the internal storage will be wiped. Sounds like a softbrick.
Sent from my Transformer TF101 using xda premium
I had exactly the same problem this week . . . this solved it:
http://forum.xda-developers.com/showthread.php?t=1620758
Reflash with NvFlash. Best idea as of now
Hey there,
I have nearly the same problem but my transformer just gets the first screen and then it tries to reboot.
I tried to reflash it with EasyFlasher but it didnt work. Is there a chance that your way will work?
If you can get ADB peri Might work, but just manually do it with NvFlash.
thanks, i'll try that when I hit back home in three days...
It is possible to get it in APX mode, so just put it on and flash?
Do you know why such a big problem occurs? It was on stock firmware and rooted for the last 5 months...
I'm starting to think my issue is related to condensation.
I started leaving the transformer in my bedroom, since my wife gave her tablet to her mother and is now using my transformer to read.
I was happy on HC, stock, non-rooted. My tablet was working with no issues for 3 months, give or take.
But then I started having random reboots and boot loops. Tried almost all roms for the transformer, same issue. Worked fine on the day I installed, got me bootloops the next day.
Today I thought about condensation after getting another round of boot loops and noticing my tablet screen with a bit of humidity. The temperature difference from my bedroom with A/C to my living room with no A/C can get to 15 or 20 celsius.
So I got the bootloop again today and instead of nvflashing the hell out of it as I have been doing, I put it in APX mode (since I have no recovery ATM, so I couldn't power it off) and leave it resting for 3 hours in room temperature. After that I rebooted it and it is now stable again. I will try to confirm those suspicious, but right now it sounds a lot like it for me. It never slept in the bedroom during the 3 months I was in HC.
theares2014 said:
thanks, i'll try that when I hit back home in three days...
It is possible to get it in APX mode, so just put it on and flash?
Do you know why such a big problem occurs? It was on stock firmware and rooted for the last 5 months...
Click to expand...
Click to collapse
I'm really not sure, but yes just download a stock nvflashable fw (xdafileserver.nl has some good ones) and put in nvflash mode and run reflash_sbkv#.bat (be sure to import wheelie into the stock fw folder and overwrite)
--
Regarding condensation, that's odd, but mabye. ..
Thanks, i'll try this when I am at home.
It is in APX mode but the computer doesnt recognise it... it says unknown device...
What shall i do?
That means the drivers are wrong/bad. Did you install any? You need the Universal Naked Drivers. (Search the tf themes and apps forum)
I installed the Asus PC Suite which means that drivers are inclueded, but I am going to search here if you say they are here.
Anyways, I can not find them there...
No, asus drivers is not what you need, you want the universal naked drivers: http://forum.xda-developers.com/showthread.php?t=1514942&highlight=universal+naked
well, that sounds quite nooby but how to install this drivers... i see several different files but absolutley no exe...
it is so embarrassing...
pnputil -a android_apxdriver.inf (or whatever the inf is called)
then plug in the tf
I opened it but nothing changes... the transformer in apx mode is still an unknown device
Have you tried 'update driver' in device manager, then point to the folder with the apx driver?
sure...
same problem with rebooting
I have exactly same problem...! My TF101 is B70 model and NVFlash not work with this model and higher... How I can fix it? is Megatron 1.1.6 installed on tablet and I have rom on sdcard, but reinstall rom not helped me, also wipe + reinsatll...
any ideas?
---------- Post added at 11:53 PM ---------- Previous post was at 11:06 PM ----------
http://forum.xda-developers.com/showthread.php?t=1688012
this is helped me...!!!

Not sure if its bricked...

Hello everybody. Bought slider101 us... 8.6.5.18 Successfully rooted with Razorclaw. Superuser installed.
Didnt have a chance to flash CWR.
Tried to update through asus notification that i got on my tablet. At the end of update it said something like "failure to update",but it changed to 8.6.5.21 on my tablet. After that tried to install recovery through" recovery installer", couldnt do it. I guess I lost my root on my tablet because of that update and Razorclaw doesnt work with .21 I did try to fix it through ADB commands which led my tablet to non stop rebooting. Cant load a screen after ASUS logo. It keeps rebooting.
The last try was this Nvflash "Unbricking and forever root" but when I hit download batch file it disconnects me from computer and looks like APX is disapearing on Device Manager place.
Cant load to recovery cause didnt install it. Tried to find sollution ,no luck so far. im not sure if its bricked. Thanks for any help in advance.
Update: problem fixed-- somehow could get into the screen where i could wipe data, I think it was system kind of recovery. And then installed nachoroot, cwm recovery, android revolution super wipe and ROM. Works perfect!
I belive you're not supposed to update when rooted.
Sent from my PG86100 using xda app-developers app
There are a few NVflash methods to unbrick devices here. You should read them all in general thread and development thread and see which one suit your slider101. And when you find one, please try different PC to do it. Some PC just act strange but some would give you profit..
farsight73 said:
There are a few NVflash methods to unbrick devices here. You should read them all in general thread and development thread and see which one suit your slider101. And when you find one, please try different PC to do it. Some PC just act strange but some would give you profit..
Click to expand...
Click to collapse
Thank u! Problem fixed. Somehow could get into wipe.data screen and that fixed the problem. Could load to normal screen.
root0660 said:
Thank u! Problem fixed. Somehow could get into wipe.data screen and that fixed the problem. Could load to normal screen.
Click to expand...
Click to collapse
Just for future reference, what steps did you take to fix it? It was my understanding that nvflash does not work for the Slider at all.
Solar.Plexus said:
Just for future reference, what steps did you take to fix it? It was my understanding that nvflash does not work for the Slider at all.
Click to expand...
Click to collapse
I think it wasnt really bricked, it just couldnt load main desktop screen. Its stucked on ASUS logo.I managed to get into system recovery screen where u can see "wipe data" and i think an image of droid man. So by pushing volume down and turning it on u can see that screen, and u need to point onto "wipe data" little green square by pushing volume up right after Ive read something like "cold boot" written with small white letters. And then it started to wipe all data. After that it could boot to the main desktop screen. From there I rooted with nachoroot since I have 8.65.21. Razorclaw can root up to I think .19.

[Q] No longer able to get into recovery mode.

Hi,
I have the Asus Eeepad transformer TF101, I've had it less then a year now, and when I got it, it had been refurbished. Today I had tried to root it, and that's where it all went wrong. The root managed to go through fine, but once I rebooted it, it would not get past the first screen "the eeepad" screen. So I managed to get into recovery mode and undo the root and get it back to factory settings. I once again rebooted and it worked fine...until I went to install the most recent firmware update... the installation fails, again booted it and its stuck at the first screen again. Did another system restore, and tried to upgrade it once more, just in case it hit a glitch or something. Same thing happens, error in the middle of installation and freezes at the screen. Again tried to restore... and this time I wasn't even able to get into the mode to restore... I get the android guy with the loading bar, then the next second I get the android guy with the warning sign with an "!" in the middle of it.... It won't even let me clear the data, it just sits there with the speaker popping every 5 seconds or so. I could really use some help.
constancebwn said:
Hi,
I have the Asus Eeepad transformer TF101, I've had it less then a year now, and when I got it, it had been refurbished. Today I had tried to root it, and that's where it all went wrong. The root managed to go through fine, but once I rebooted it, it would not get past the first screen "the eeepad" screen. So I managed to get into recovery mode and undo the root and get it back to factory settings. I once again rebooted and it worked fine...until I went to install the most recent firmware update... the installation fails, again booted it and its stuck at the first screen again. Did another system restore, and tried to upgrade it once more, just in case it hit a glitch or something. Same thing happens, error in the middle of installation and freezes at the screen. Again tried to restore... and this time I wasn't even able to get into the mode to restore... I get the android guy with the loading bar, then the next second I get the android guy with the warning sign with an "!" in the middle of it.... It won't even let me clear the data, it just sits there with the speaker popping every 5 seconds or so. I could really use some help.
Click to expand...
Click to collapse
Use easy flash and restore your tablet to stock... then if you want try rooting it using the same tool... while using easy flash, read the instruction carefully...go to android development and go to easy flash forum n download the latest software n use it... good luck, if u have nay doubt then ask after reading....
Sent from my Transformer using xda app-developers app
Thank you
udupa82 said:
Use easy flash and restore your tablet to stock... then if you want try rooting it using the same tool... while using easy flash, read the instruction carefully...go to android development and go to easy flash forum n download the latest software n use it... good luck, if u have nay doubt then ask after reading....
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
ok thanks for the help, i'm sure i will have questions after reading.
udupa82 said:
Use easy flash and restore your tablet to stock... then if you want try rooting it using the same tool... while using easy flash, read the instruction carefully...go to android development and go to easy flash forum n download the latest software n use it... good luck, if u have nay doubt then ask after reading....
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
I've tried running the flash but it keps telling me that its unable to find the device.
constancebwn said:
I've tried running the flash but it keps telling me that its unable to find the device.
Click to expand...
Click to collapse
Remove all installed drivers(including Asus sync and any other Asus software) and then download and install naked driver(link is available in easy flash thread).. now plug your tablet and when it asks for driver install naked driver... if it doesn't then go to device manager on your laptop and install from there... once this is done, press power button and volume up buttons together for 5 secs and that will take your tablet into APX mode... plug the tablet back, your laptop will install APX drivers then go back to device manager and right click on the unknown device and update/install driver( same naked driver).. once you have installed required drivers its just a matter of running easy flasher...
Sent from my Transformer using xda app-developers app

[Q] Total device failure: URGENT ASSISTANCE REQUIRED!

I'm quite well up with my Android devices and have enjoyed countless ROMs, modsm, hacks and such for a while now but I have come to a big massive wall and really need help.
I installed RomToolBox on my TF300T which turned out to be the biggest mistake ever. I changed a few settings and had a look around the app when I got a Toast message telling my the system had crashed and was closing. It only gave me the option to click "OK" which upon doing just brought the same message up again and again. I then rebooted by using a pin in the side of the tablet and the device got stuck in a boot loop.
I eventually figured something out and replaced the SystemUI.apk and the Framework-Res.apk in /System/App via ADB and my device booted.
Once booted I noticed my system bar wasn't there and I had no access to the notifications, time etc. I then decided to factory reset so I ran TiBkp and backed up all my Apps + Data and transferred it to my thumbstick.
I proceeded to the settings and ran through the options to wipe and restore to factory settings. After the device rebooted I got the Android on the screen with the Blue loading bar etc. 20 minutes had passed and nothing happened. I decided to Google a few things and ran though the process of trying to sort out the factory restore.
I have tried EVERYTHING and my tablet is now completely screwed.
I have tried everything I can come across, from rebooting into recovery, fastboot and all the rest but noting happens. I've tried the WSG_UnBricker_V1.0.3 and can never get passed "waiting for device". I cant get it to recognise ADB or FASTBOOT and it just sticks on the same factory restore screen.
As I knew it was going to go nowhere, I tried to restart it with a pin and it just gives me the Asus boot screen and then goes straight onto the factory restore screen with no ability to do anything. I cant even turn my device off.
My device was rooted, unlocked, running stock 4.1.1 with all the usual app installed (clockwork etc).
All I can do for now is let the tablet run out of battery and go from there and hope one of you can help.
I will gladly pay for services within the UK if it can be repaired. I obviously can't take it back to the shop. Anyway, enough of that. If you can help, please get in contact.
Thanks,
Dale.
It's a known issue unfortunately if you do a factory reset from the boot loader on a custom recovery.
There should be warnings all over xda about it but I don't think there are. If you can't get the device recognised in fast boot from a PC or you didn't do the nvflash process after unlocking then I'm afraid you probably have a brick.
Not that its much help but if you are bricked like I was, it was quite easy to replace the main board with a used one from Ebay.
No chance you had NV Flash snapshots?
Good luck with it,
Feend
In all honesty it simply sounded at first to be a permissions issue for SystemUI.apk.
But if you can get to fastboot I would try Reformatting your system partition and flashing another ROM. Then factory reset your data partition.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
sbdags said:
It's a known issue unfortunately if you do a factory reset from the boot loader on a custom recovery.
There should be warnings all over xda about it but I don't think there are. If you can't get the device recognised in fast boot from a PC or you didn't do the nvflash process after unlocking then I'm afraid you probably have a brick.
Click to expand...
Click to collapse
Sorry if I've misinterpreted you, but are you saying that doing a factory reset in CWM can brick your device?
Sent from my R800i using xda app-developers app
UndisputedGuy said:
Sorry if I've misinterpreted you, but are you saying that doing a factory reset in CWM can brick your device?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Wow. Thanks a lot for posting this information. I had no idea. Would using the factory reset within CWM or in the settings be dangerous?
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
So doing this completely hard bricks the device? meaning NO bootloader? It almost seems like the bootloader factory reset is touching the block that holds the recovery. Isnt there source code for this bootloader? Couldnt this be solved?
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Wow i am very glad i stumbled across this.. there should be a sticky about this or something!! Thanks for the very helpful post
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I have to agree, I'm REALLY glad I came across this. I'd noted that in a few of the "My tablet is bricked" threads that people had bricked after accidentally clicking something in the bootloader screen and had vowed not to touch anything in the original bootloader.
Thanks for the heads up on this.
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Just a quick question cuz I'm curious... these 3 (or 2 other?) people you know who bricked this way.. were they able to recover? Or was it game over for them?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
markymark567 said:
Just a quick question cuz I'm curious... these 3 (or 2 other?) people you know who bricked this way.. were they able to recover? Or was it game over for them?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Game over
sbdags said:
Game over
Click to expand...
Click to collapse
Did they not have nvflash files? Can nvflash not recover this brick?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
markymark567 said:
Did they not have nvflash files? Can nvflash not recover this brick?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Yes nvflash would have been able to recover. Unfortunately they either didn't know about nvflash before upgrading to jelly bean or they were already on a higher version than nvflash works on when it was released. In all 3 cases they could only get into apx mode. No fast boot and no recovery.
Only fix in this case is to send it back to Asus are able to recover it so we are missing something that Asus have.
sbdags said:
Yes nvflash would have been able to recover. Unfortunately they either didn't know about nvflash before upgrading to jelly bean or they were already on a higher version than nvflash works on when it was released. In all 3 cases they could only get into apx mode. No fast boot and no recovery.
Only fix in this case is to send it back to Asus are able to recover it so we are missing something that Asus have.
Click to expand...
Click to collapse
That's a bummer for them but good to know nvflash can fix it. and f*** Asus for locking the jb boot loader to prevent nvflash... Maybe this is a stupid comment but I think they would sell more devices if they didn't do stuff like this... I know when I look into purchasing a device I come here first to make sure there is android development and unbricking procedures. ( I saw nvflash for tf300t and that's pretty much the reason I picked that tablet). Its a bummer that companies like Asus are much more concerned with making money by repairing bricked devices. (Although I do love Asus hardware. I own a tf300t and a nexus 7...its a love hate thing... Damn you Asus)
Sent from my Nexus 7 using xda app-developers app
D.MADROX said:
I'm quite well up with my Android devices and have enjoyed countless ROMs, modsm, hacks and such for a while now but I have come to a big massive wall and really need help.
I installed RomToolBox on my TF300T which turned out to be the biggest mistake ever. I changed a few settings and had a look around the app when I got a Toast message telling my the system had crashed and was closing. It only gave me the option to click "OK" which upon doing just brought the same message up again and again. I then rebooted by using a pin in the side of the tablet and the device got stuck in a boot loop.
I eventually figured something out and replaced the SystemUI.apk and the Framework-Res.apk in /System/App via ADB and my device booted.
Once booted I noticed my system bar wasn't there and I had no access to the notifications, time etc. I then decided to factory reset so I ran TiBkp and backed up all my Apps + Data and transferred it to my thumbstick.
I proceeded to the settings and ran through the options to wipe and restore to factory settings. After the device rebooted I got the Android on the screen with the Blue loading bar etc. 20 minutes had passed and nothing happened. I decided to Google a few things and ran though the process of trying to sort out the factory restore.
I have tried EVERYTHING and my tablet is now completely screwed.
I have tried everything I can come across, from rebooting into recovery, fastboot and all the rest but noting happens. I've tried the WSG_UnBricker_V1.0.3 and can never get passed "waiting for device". I cant get it to recognise ADB or FASTBOOT and it just sticks on the same factory restore screen.
As I knew it was going to go nowhere, I tried to restart it with a pin and it just gives me the Asus boot screen and then goes straight onto the factory restore screen with no ability to do anything. I cant even turn my device off.
My device was rooted, unlocked, running stock 4.1.1 with all the usual app installed (clockwork etc).
All I can do for now is let the tablet run out of battery and go from there and hope one of you can help.
I will gladly pay for services within the UK if it can be repaired. I obviously can't take it back to the shop. Anyway, enough of that. If you can help, please get in contact.
Thanks,
Dale.
Click to expand...
Click to collapse
I have worked with six or seven who used the wipe data on the bootloader; two recovered.
If you have any chance to recover you have to work at it. First apx mode is useless unless you previously flashed Nvflash.
We need adb, fastboot, or recovery working. Here is a thread for your use to get control of your tablet.
You mention rebooting into recovery. Stock, cwm, or twrp?
As you progress through this list the tablets have a way of evolving. This can happen even if you haven't gotten anything to function as you wish. That means you have to do them again; three times may be the charm.
I would like very much to know about your mention of recovery. Can you still get into recovery and which?
How about a current update before you begin using that link.

Categories

Resources