Database Info

[Q] Part-Bootloop

Hello guys, I've got a weird problem. I messed around with my Transformer a bit, rooted etc on 8.4.4.11. CWM isn't working, and I can't even boot into recovery. It just sits at the "Loading recovery kernel...". Anyway, its freezing at the eeePad screen on bootup and doesn't do anything (this has stopped me from reflashing a blob, or Asus OTA updating). I've tried reflashing stock and rooted images quite a few times, but it always does the same thing. Now, I can get around the freeze by going to the hard reset screen and declining, and it boots into Android.
Whats wrong? Bootloader? Has to be something in startup, but I cant figure it out.

Re-flash using NVFlash method, in dev section (and don't forget to put the NVFlash ROM version in the folder)

bud77 said:
Re-flash using NVFlash method, in dev section (and don't forget to put the NVFlash ROM version in the folder)
Click to expand...
Click to collapse
Nope, that actually made it worse. Anyway, each root that I tried to go through did the exact same thing. Now it doesnt show anything on boot.
Is there some way to completely return it to stock? Just flash an official firmware pack with nvflash and have everything back to the day it was shipped?
EDIT: Fixed it, I had the wrong type of ROM unpacked. Thanks Bud.

padd3r said:
Nope, that actually made it worse. Anyway, each root that I tried to go through did the exact same thing. Now it doesnt show anything on boot.
Is there some way to completely return it to stock? Just flash an official firmware pack with nvflash and have everything back to the day it was shipped?
Click to expand...
Click to collapse
How could it make it worse .... ?
What's the error you're getting while NVFlashing ?
For the stock, if you can't NVFlash a rom, you won't be able to flash stock too, as the process is identical

(HELP!) Is my transformer bricked?!

I recently purchased a Asus Transformer, and being the android nerd I am I immediately began my rooting. After I rooted it, I began to look up roms and such. I decided to put the revolution HD Tom on it. I booted into recovery, wiped data, wiped cache, wiped dalvic, and than processed to flash the rom it flashed and said rom installed successfully. I rebooted and now nothing. I understand the wait time for boot but its been over 30 mins. I almost possitive its off and bricked. I need help as I only know how to unbrick a moto device. :/
sent from a DROIDX using S.S. 2.2... the best rom for it...

after a little searching I found a program called nvflash, I'm guessing that this is sort of like rsd lite. Ill try it later.
sent from a DROIDX using S.S. 2.2... the best rom for it...

NVFlash is only going to work if you have SBK v1.
Did you check the MD5Sum of the ROM file before flashing?

Sbk v1, what's that? And sorry I'm a noob with this transformer.
sent from a DROIDX using S.S. 2.2... the best rom for it...

It is the Secure Boot Kit of the device.
Look at your TF serial number: if you have B7O, B8O, B9O it should have the new version of SBK (v2). If it's the case, you CAN'T use NVFlash method to unbrick at the moment.
Look at this link to be able to check the SBK version of your TF:
http://forum.xda-developers.com/showthread.php?t=1290503

atothis said:
It is the Secure Boot Kit of the device.
Look at your TF serial number: if you have B7O, B8O, B9O it should have the new version of SBK (v2). If it's the case, you CAN'T use NVFlash method to unbrick at the moment.
Look at this link to be able to check the SBK version of your TF:
http://forum.xda-developers.com/showthread.php?t=1290503
Click to expand...
Click to collapse
Well if I can't turn on the device and I cant tell if its off than how can I get it into the mode asked? If that makes sence.
sent from a DROIDX using S.S. 2.2... the best rom for it...

Have you tried to force turn-off?
If not so, press and hold the power button for 10-20 seconds.
Then try to enter CWM recovery (or to boot normally).
Have you also tried to put it to charge? (Just to see if something happens).
EDIT: Did you eventually checked the serial # (On the box or on the back bottom part of the TF) ? If you have a B6O or lower, you can quite surely use NVFlash.

Tf101 is on the bottom as soon as I leave bdubs ill check to see if I can force it off and than enter recovery.
sent from a DROIDX using S.S. 2.2... the best rom for it...

atothis said:
Have you tried to force turn-off?
If not so, press and hold the power button for 10-20 seconds.
Then try to enter CWM recovery (or to boot normally).
Have you also tried to put it to charge? (Just to see if something happens).
EDIT: Did you eventually checked the serial # (On the box or on the back bottom part of the TF) ? If you have a B6O or lower, you can quite surely use NVFlash.
Click to expand...
Click to collapse
I'm guessing it will say B6O at the end of the serial. O and also what must I do in order to use nvflash, what preparation needs to be done?
sent from a DROIDX using S.S. 2.2... the best rom for it...

At the bottom of your transformer is a sticker if it says b60 you can use nvflash
If you have checked that then just look in the dev thread and you will find all you need about nvflash
Sent from my tf101 using xda premium 1.54Ghz

I tryed to hard reset it, didn't work. :/ I also checked and I have a tf101, B6O. How do I use the nvflash tool?
sent from a DROIDX using S.S. 2.2... the best rom for it...

HaXERxPaYLaY said:
I'm guessing it will say B6O at the end of the serial. O and also what must I do in order to use nvflash, what preparation needs to be done?
sent from a DROIDX using S.S. 2.2... the best rom for it...
Click to expand...
Click to collapse
Actually you need to read the FIRST three letters of the serial.
If it is a B6O, you're lucky
I have a B7O SBKv2, so I didn't used NVFlash, but you can find clear instructions here:
http://forum.xda-developers.com/showthread.php?t=1123429
Here's the general REF thread (MANY useful info, it's a sticky thread in dev section): http://forum.xda-developers.com/showthread.php?t=1044424

Ill try this all tonight and ill let you know what happens. I'm kinda nervous cause I really don't want to have high dollar brick.
sent from a DROIDX using S.S. 2.2... the best rom for it...

I got it to work im posting from it now! Thank you guys!

I have this problem and resolved with super wipe full script ( find in first post of revolution hd rom )
For use it, just download, put in sd card, run it on recovry ( install zip ... )
After wipe, I install revolver rom
Sent from my Transformer TF101

HaXERxPaYLaY said:
I got it to work im posting from it now! Thank you guys!
Click to expand...
Click to collapse
how did you get it working?

Hi everyone,
I have tried to read most of the 92 pages and still have not solved my problem.
The situation is as follows:
- I had a perfectly fine Asus Transformer B40 running Revolver 3.11 ROM with CPU OCed @ 1.6 Panda.test. While I was browsing the web the TF shut off and since then I cannot turn it on properly (boot into the OS).
- after failed attempts to reflash I wanted to get back to stock + unroot.
- I followed the steps from the first post here, I have a US version B40. I downloaded the US latest firmware from the first post and then ran the .bat file. Everything went fine and it restarted.
- then I did just this: hold vol- and power until you get the option to erase your data.... Select the option to wipe data.
Now the problem is more or less the same: I boot up the device, it shows the ASUS logo with the spinning wheel and then it turns off or reboots continuously. Sometimes it gets after the logo to the Select Language or Country screen. Touchscreen works. But then it reboots again. Every time it does that there is also a small hardware click sound.
I have also tried to manually reflash with firmware from Asus website but I still get the Android robot with an exclamation mark inside.
I just got this for Christmas, hope you can help me somehow as I don't know what to do...
Thanks a lot!

Just walked a friend through the downgrade on his B70 over the phone, he is rooted and running PRIME 2.1.1 in less than an hour.
First, get the WW_epad-user(blah blah) 8.6.6.19.zip update (downgrade/update, available in the dev section stickies), be sure it is the 8.6.6.19, not 8.6.5.19. Place the file on your SD card in the root, also make a copy and rename it
EP101_SDUPDATE.zip
(make sure your SD card is FAT32 formatted too, this has caused problems for some I have read). If these files are placed in the root of your external SD card then when booting into recovery mode it *should* find one of these two files and ask to install the 'update'. Once updated, install razorclaw and recoveryinstaller, grab the updated CWM installer with the 8.6.6.21 patch on it, available in the dev section, and then flash your new ROM over this patch (apparently you can't flash the patch over anything but a stock ROM, so if you already have a flashed ROM you need to flash back to stock ROM, search around instructions and files are available on xda).
If when you boot into recovery (vol - and pwr, vol+ on prompt) it doesn't tell you it is installing, give it some time, others have reported that the android/yellow triangle screen is actually good to see and will install updates on this screen even though it isn't notifying you (can't confirm from first hand, but what I have read on this site from other users), if it doesn't though, try rebooting normally, other users have said the update installs from notification bar in stock android OS (this confuses me too..). If recovery mode nor rebooting installs the downgrade, double check that you have the correct files, named correctly..try on another SD card, reformat to FAT32, etc. from what I understand even though it's different for some users there is some good success flashing back to the 8.6.6.19 build from the .21. Good luck, tell us if you fix it and how!

superwipe..
Before you flash revolution, you were supposed to flash superwipe then the rom, if you havent already go do so.

[Q] Have there been any real B70+ bricks, what was done?

Hi,
Firstly, I sincerely apologise for another thread like this. I have searched, and done all that stuff, and I have a good idea of the situation in my head, but so often I get these things wrong, I just wanna get confirmation.
I bought a TF101 for Christmas after the UK price drop and it's a B90 device. I understand that as it currently stands, this means it can be rooted and CWM installed, and ROMs such as Prime and Revolver can be installed, but if anything goes wrong, there is no fallback because NVflash doesn't work.
I was just wondering, firstly is this indeed the case? And secondly, have there actually been any reports of B70+ devices being completely bricked with no fix?
I really wanna get a custom ROM, but I'm very aware that while CWM is better than no recovery at all, if anything were to corrupt it, I'd be stuck with no fallback at all, and a useless £300 spent.
What situations may lead to it becoming bricked? I'm guessing it would take the complete destruction of CWM to totally brick?
Sorry for all the questions! I just really want confirmation that I'm right, advice, and a good starting place so I can try and get involved in this community

Also, just a daft thought, but if anything does go wrong and the device bricks, is there no way to use the downloadable files from ASUS and flash them to get back to stock system and recovery?

I'm not quite sure, but I think it would be fairly hard to completely brick it. If your ROM somehow gets corrupted you should be able to restore/factory reset it from either CWM or the stock recovery, and if the recovery partition gets corrupted you should be able to reflash it from within the ROM, like one does when rooting with Razorclaw.
You can use CWM to reflash the stock ROM and recovery:
http://forum.xda-developers.com/showthread.php?t=1093403
http://forum.xda-developers.com/showthread.php?t=1154947
If your CWM/Recovery and ROM are completely corrupted and/or unbootable, then AFAIK the only way to restore it is by using NVFlash, which isn't possible in your case, or RMA'ing it to Asus.
Someone with more experience could probably give you a better answer.

Hellrespawn said:
I'm not quite sure, but I think it would be fairly hard to completely brick it. If your ROM somehow gets corrupted you should be able to restore/factory reset it from either CWM or the stock recovery, and if the recovery partition gets corrupted you should be able to reflash it from within the ROM, like one does when rooting with Razorclaw.
You can use CWM to reflash the stock ROM and recovery:
http://forum.xda-developers.com/showthread.php?t=1093403
http://forum.xda-developers.com/showthread.php?t=1154947
If your CWM/Recovery and ROM are completely corrupted and/or unbootable, then AFAIK the only way to restore it is by using NVFlash, which isn't possible in your case, or RMA'ing it to Asus.
Someone with more experience could probably give you a better answer.
Click to expand...
Click to collapse
Hey thanks for the reply! Basically I'm thinking if I install CWM and a ROM, and just install updates for that ROM and avoid doing much more messing about than that, I shouldn't run into problems.

I rooted using Razorclaw, installed CWM with http://forum.xda-developers.com/showthread.php?t=1346180 and then flashed Revolver and haven't had any trouble.

Hellrespawn said:
I rooted using Razorclaw, installed CWM with http://forum.xda-developers.com/showthread.php?t=1346180 and then flashed Revolver and haven't had any trouble.
Click to expand...
Click to collapse
Is yours a B90 too?

Where do you see the B90 or B70 on the tablet...just got mine and want to check since I see a lot of people using these codes to describe their model number.

SiNJiN76 said:
Where do you see the B90 or B70 on the tablet...just got mine and want to check since I see a lot of people using these codes to describe their model number.
Click to expand...
Click to collapse
Your serial number will be of the form BXY-xxxxxx with XY being 40, 70, 90 etc. It's on the box and should be on the sticker on the back of your TF

jtc42 said:
Is yours a B90 too?
Click to expand...
Click to collapse
I have one of the later B70's, so no NVFlash support.

jtc42 said:
Your serial number will be of the form BXY-xxxxxx with XY being 40, 70, 90 etc. It's on the box and should be on the sticker on the back of your TF
Click to expand...
Click to collapse
Ah. Thanks. I was looking in the tablet at the about tablet screen. Guess I've got the B90.
Guess B90 is the latest release...too bad they never bothered fixing the left speaker.
By the way...What will brick the TABLET? I know in phones...messing up the flash of a Radio will brick the phone...but other than that...as long as you can get into recovery...everything else is repairable...more or less.

It's if you somehow mess up recovery AND system at the same time. Normally not a problem with an external flash app, but with B70+ if that happens, that's it, end of the line.
Wouldn't be worried except in my head, ICS updates, via CWM, are big enough to somehow increase the bricking risk. I might wait until official ICS OTA, and then hope we get root on that :/ I really don't know.
REALLY don't wanna brick it, and while its a very small risk, i'm all nervous still
Sent from my LT15i using XDA App

[Q] CWM and boot problems

So I might very well get crap for this since I know this has been brought up in numerous locations, however none of the answers seem to quite fit my direct problem and the information is so entirely scattered around the forums that it's a wee bit hard piecing it all together. I do apologize in advance if there is some post that details this already, it's rather late and I'm at my wits end.
So I decided to root the old Transformer today and toss on CWM to flash Revolver (yeah you guys see where this problem is headed). Upon loading up CWM and flashing the rom, I promptly rebooted, at which point it just hung on the title screen. After figiting with it a bit I got it to the point that it simply boot loops into CWM directly now (not sure if that would be what we call an improvement). Now, most solutions to this problem involve cold booting linux (this seems to work for most people) however for me it just hangs. NVflash (is that it?) doesn't seem to be an option since I'm one of the unlucky ones that it wont work for (b80 serial) and I'm not sure where to go from here.
Windows won't recognize it at any stage (CWM/hung at linux boot) however I can load it into APX mode and can successfully run Root Toolkit (though I'm not sure that will help me much).
Now I promise I have at least a wee bit of intelligence, I'm not asking for a complete walkthrough or anything but at the very least if there is an answer buried on the forums somewhere, could someone point me in the right direction?

First of all nvflash now work almost all model of TF101 even above B60. You check in general thread..
Sent from my awesome rooted Defy: 2.3.6 XDA premium

Thank you thank you!
Ysed wheelie and a stock rom file to get back to safety, used peri to get root and recovery back, tried to reflash revolver and BAM same problem lol. Guess I'll be giving another ROM a shot.
farsight73 said:
First of all nvflash now work almost all model of TF101 even above B60. You check in general thread..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse

dotpkmdot said:
Thank you thank you!
Ysed wheelie and a stock rom file to get back to safety, used peri to get root and recovery back, tried to reflash revolver and BAM same problem lol. Guess I'll be giving another ROM a shot.
Click to expand...
Click to collapse
What version of CWM are you using?

The rogue touch recovery that the PERI installs.

Are you completely wiping your TF before installing the ROM? You MUST wipe before installing anything in CWM generally.

dotpkmdot said:
The rogue touch recovery that the PERI installs.
Click to expand...
Click to collapse
Huh. Did you factory reset and wipe data/cache?

Without looking at the options, wiping data/factory reset option, wipe cache, wipe dalvic cache.
Afterwards installing Revolver and next the update.
Tried the whole process again without doing the update, results the same.

Try installing a different ROM and see if you get the same result, if you do I'd reflash everything except the SOS partition stock.

Will do, downloading Revolution now to try and give it a shot.

Thing O Doom said:
Try installing a different ROM and see if you get the same result, if you do I'd reflash everything except the SOS partition stock.
Click to expand...
Click to collapse
So, different rom, same results. After flashing and rebooting, I simply get stuck at the Eee Pad screen. Is there any where you can point me to so I can read up on what I would need to do to reflash everything? I'd rather not turn the tablet into a nifty paperweight.

Search for
'wheelie NvFlash'
You can use that to reflash everything, or if you can Cold-Boot into Android (Hold volume-down then press power and wait 30 seconds, still holding volume-down)
You can use dd if=/sdcard/blob of=/dev/block/mmcblk0p4 (Staging partition) to reflash a blob.
See blob tools for extracting partitions from stock blobs to reflash, it's probably EBT (bootloader) that is messed up.

[Q] Numa 3.0 Install on Moto Atrix 2. Stuck on Loading Moto Logo

I installed Numa 3.0 as per this forum thread:
http://forum.xda-developers.com/showthread.php?p=38977610&highlight=stuck#post38977610
However it gets stuck on the "Dual Core Technology" screen at boot up.
I try go in to AP Fastboot mode, and can get there but the down button doesn't work so the only option i have is to boot normally.
Totally stuck. Any suggestions what i can do?
It's Non-AT&T purchased in Central America.
Installed using Bootstrap Recovery.
Followed all instructions at above link except cleared the caches before installing.
No errors showed during install.
Firmware is 2.3.6
Really hoping somebody can help, I'd hate to lose a phone i just spent 2 days searching for and shelled out my hard-earned travel money for
Thanks heaps
Greg

gregoriusness said:
I installed Numa 3.0 as per this forum thread:
http://forum.xda-developers.com/showthread.php?p=38977610&highlight=stuck#post38977610
However it gets stuck on the "Dual Core Technology" screen at boot up.
I try go in to AP Fastboot mode, and can get there but the down button doesn't work so the only option i have is to boot normally.
Totally stuck. Any suggestions what i can do?
It's Non-AT&T purchased in Central America.
Installed using Bootstrap Recovery.
Followed all instructions at above link except cleared the caches before installing.
No errors showed during install.
Firmware is 2.3.6
Really hoping somebody can help, I'd hate to lose a phone i just spent 2 days searching for and shelled out my hard-earned travel money for
Thanks heaps
Greg
Click to expand...
Click to collapse
Quoted from the op in the NUMA thread:
"!-!-FOR ICS 3.0.8 KERNEL ONLY-!-!
BASED ON OFFICIAL AT&T 4.0.4 ICS (but will also work on non-at&t)"
If your firmware is 2.3.6, then you didn't follow the instructions in the op. You can't flash NUMA on gingerbread. You have to be on ICS. That is why you are having problems.
Does the volume down button not work at all? If it doesn't, then I don't know what you can do. If normally it does, turn off the phone completely then press power and volume down at the same time to boot straight into fastboot mode.(what you're describing is not fastboot mode, that's the boot mode selection menu) Then flash your FXZ, update to ICS and try again. NUMA is well worth the effort IMO.:thumbup:
Brought to you by time and relative dimensions in space.

1BadWolf said:
Quoted from the op in the NUMA thread:
"!-!-FOR ICS 3.0.8 KERNEL ONLY-!-!
BASED ON OFFICIAL AT&T 4.0.4 ICS (but will also work on non-at&t)"
If your firmware is 2.3.6, then you didn't follow the instructions in the op. You can't flash NUMA on gingerbread. You have to be on ICS. That is why you are having problems.
Does the volume down button not work at all? If it doesn't, then I don't know what you can do. If normally it does, turn off the phone completely then press power and volume down at the same time to boot straight into fastboot mode.(what you're describing is not fastboot mode, that's the boot mode selection menu) Then flash your FXZ, update to ICS and try again. NUMA is well worth the effort IMO.:thumbup:
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
Yeah, you flashed over GB, which could have even hard bricked you, but I doubt it. your gonna need to get the down button working so you can at least get into fastboot and reflash.

1BadWolf said:
Quoted from the op in the NUMA thread:
"!-!-FOR ICS 3.0.8 KERNEL ONLY-!-!
BASED ON OFFICIAL AT&T 4.0.4 ICS (but will also work on non-at&t)"
If your firmware is 2.3.6, then you didn't follow the instructions in the op. You can't flash NUMA on gingerbread. You have to be on ICS. That is why you are having problems.
Does the volume down button not work at all? If it doesn't, then I don't know what you can do. If normally it does, turn off the phone completely then press power and volume down at the same time to boot straight into fastboot mode.(what you're describing is not fastboot mode, that's the boot mode selection menu) Then flash your FXZ, update to ICS and try again. NUMA is well worth the effort IMO.:thumbup:
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
Damn, seems i messed that up. Itd be nice if it said something like "DO NOT USE ON YOUR PHONE IF IT CAME INSTALLED WITH 2.3.6" or something along those lines for those of us less familiar with the Kernel versions etc.
I have used a computer in an internet cafe to flash it to the leaked ICS ROM. Seems to be working okay now (phew)...
Thanks heaps for the help, you're lifesavers!
edit: how do i get the recovery console working again.. now if i try to boot into recovery i get a sick looking android with an exclamation mark in his stomach. there{s some of the menu items but i cant restore from a file on the sd card.

Hmm... so having some issues. ICS (leak) is working (with the odd bit of chinese here and there??)... but i cant get into a working recovery.
I've tried searching the forum for a bootstrap or recovery i can install, but only find the 2.3.6 version (which is what i had on there before). i tried to run it but it fails.. tried to unroot using that and it failed too.
can soembody show me a recovery i can install so i can boot into recovery and mod to Numa please?

motorola atrix2 boots up but only doesn't on
Im not sure if this is in the wrong section, I recently installed ROM Toolbox and changed the font on my phone and it asked for reboot, but now when I tried it is stuck in boot. it only boots up and motorola screen comes and does not show homescreen ... pls help me

gregoriusness said:
Hmm... so having some issues. ICS (leak) is working (with the odd bit of chinese here and there??)... but i cant get into a working recovery.
I've tried searching the forum for a bootstrap or recovery i can install, but only find the 2.3.6 version (which is what i had on there before). i tried to run it but it fails.. tried to unroot using that and it failed too.
can soembody show me a recovery i can install so i can boot into recovery and mod to Numa please?
Click to expand...
Click to collapse
Search for Boot Menu Manager in the playstore.
antonyvictor said:
Im not sure if this is in the wrong section, I recently installed ROM Toolbox and changed the font on my phone and it asked for reboot, but now when I tried it is stuck in boot. it only boots up and motorola screen comes and does not show homescreen ... pls help me
Click to expand...
Click to collapse
Do you have a custom recovery installed? If you do, try to get into that and restore the backup you hopefully made before you started tinkering. If not, you'll have to flash the FXZ that is for your phone's model.
Brought to you by time and relative dimensions in space.

1BadWolf said:
Search for Boot Menu Manager in the playstore.
Click to expand...
Click to collapse
Got it, but the phone is no longer rooted. I can't find a guide to root a phone that has been flashed with ICS. Any suggestions?