Database Info

ROM Randomly Died? (stuck in bootloader)

Yesterday my phone's battery died from not charging it and I didn't think too much of it. I plugged it back in to charge however and it automatically booted up...into the boot loader with a message saying "No Image File!" (figured out this was because its checking the microsd card for a rom - I usually flash over usb). Tried to flash another ROM and it appeared to be working but after the reboot (before you get to the stylus configuration screen) just went back to the bootloader and gave the same message.
So, has anyone encountered this before? Looks like the ROM isn't storing anything (and my phone is essentially dead) but perhaps I need to do something simple to fix it.
Thanks in advance!

It's been posted a few times, but it's rare. Try flashing a stock rom over usb.

Hey, appreciate the help!
Tried it and no dice however. Looks like the message I was recieving (No Imaging File!) was from it looking for an Image off the SD card (I always flash off of USB so I had never seen this). Tried to initiate a hard reset from the boot loader as well but it just gets stuck on the "This operation will delete all your..." screen and pressing Volume Up does nothing.
So I tried to flash the ROM found at http://forum.xda-developers.com/showthread.php?t=429843 and am still stuck where it reboots back to the boot loader after the flash.

Maybe try flashing with the sd card removed; you could also try task 29. Sorry, I have no other ideas.
Edit: And I know I've posted this in similar threads (lol), but maybe your vol down button is stuck. If that's the case, any time you reset the device, it will go into bootloader. I can't think of any other reasons you phone isn't booting up properly (other than, like, the phone is toast).

Hey, yea last night attempted to flash without it in as well as from the SD card. Neither worked.
So I kept searching and was reading all about mtty (and task 29) and that looks like the way to go. Couldn't get things to work properly on my Windows Server 2008 R2 box so I'm going to try it from an XP box here in a bit and can hopefully get everything connected.
If anyone is curious, I found this thread describing the use of mtty: http://forum.xda-developers.com/showthread.php?t=540290

Well, took it to work where I have an XP machine and plugged it into the USB port. It didn't turn on automatically (which it has been when supplied with power) which was kind of weird. So I hit power and voila, it loads the ATT ROM I flashed last night.
Not sure what fixed it (I don't think it was a stuck key, but who knows) but its working now. Thanks for your help Ted.

[Q] Power wont Stay on cannot get into APX mode

I have been following similar threads, but there seems to be just enough that is different with my Gtab I thought I would try a new one in my last ditch effort.
I have most been runnung Tnt lite and everything worked fine. Then curisoity got to me and I installed the Cyrogen 7. I was having issues with gapps and followed instructions until it wouldn't boot past the BitTrix presents....
I was able to get into CM but after all the formarts and such from the intructions on gapps I no longer had any backs or recovery files.
Then I tried the NVflash. First problem is that I could never confirm I was in APX mode. My Linux CentOS machine could see the gtab but the NVFlash would not run. So a pal of mine who is really good with Linux grabbed tnt lite and was able to directly transfer it to the SD card.
Everything looked hopefull until just before the home screen should appear it powers down. then I when into CM and re-installed tnt. Same problem so I go back to CM and try to mount data. I get an error that it doesn't exisit. then it powers down in CM. Each time I go into CM it shuts down sooner and sooner.
I opend the device up and completed a manual reset to no sucess. I hear people say its really heard to brick these things. PLEASE someone help show me that I am not that talented!

no help?
17 views and no replies? Someone has to have something for me right?

Hi
OK, i am no expert here but have you tried just putting a new ROM zip file onto your SD card and rebooting into recovery mode Power & Volume + and choosing the zip file you just copied over?
Works for me everytime but then mine has never died.
Ian

Ianmrr said:
Hi
OK, i am no expert here but have you tried just putting a new ROM zip file onto your SD card and rebooting into recovery mode Power & Volume + and choosing the zip file you just copied over?
Works for me everytime but then mine has never died.
Ian
Click to expand...
Click to collapse
My main issue now is that the power wont even stay on long enough to get to that point.

Instructions if you have a brick.
http://forum.xda-developers.com/showpost.php?p=11230514&postcount=1

mkuzminov said:
Instructions if you have a brick.
http://forum.xda-developers.com/showpost.php?p=11230514&postcount=1
Click to expand...
Click to collapse
These are the instructions I followed when I opened it up. This did not work for me. You can see I posted in that thread as well.

Through all the message boards I read, not one single person including myself thought of the most basic answer.......The battery was dead
I work on computers for a living and this is yet just another example of starting with the basics, no matter what you think your skill level is.
Once charged, I was able to read the zip off of the card. Flashed and everything was great. Until I dropped it, literally minutes afte I got it working.
I am starting to think I wasn't meant to use this tablet.

I guess we all ASSUMED that you had charged it, or at least were trying w the adaper plugged in... I know that was what I assumed ...
Jim

Relock US Xoom Tiamat 1.4.4 resulted in hanging at Motorola logo

Hey guys I was having some problems with my xoom's wifi on Tiamat's 1.4.4 so i decided to relock the device and use stock.
It's a US model and had build HMJ37 but i decided to follow this thread
http://www.xoomforums.com/forum/mot...4600-thinking-about-unrooting-read-first.html
I downloaded img build HRI66 and followed all the steps and it was ok. Then, i rebooted and now my device is at the motorola logo's dual core screen. Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo. It just keeps rebooting and getting stuck at the motorola logo. I then unlocked again, and performed the same process with the HRI39 img and still got the same problem
So im stuck. Please help me out guys, i'm in serious ****.

So you have gone as far as the "fastboot erase cache" and "fastboot oem lock" right? This is kind of funny because I tried to install Tiamat 1.1 ROM tonight and ended up going through this HUGE loop of problems.
Here's the problem I had: some time ago I installed ROMManager from the market. I thought it would be easier. It SHOULD be easier. I let it update my recovery to its own version 4.something. It allowed me to SORT OF install the ROM, but I wound up with some persistent system files that weren't getting wiped and a bcm4329.ko version mismatch.
This stumped me for a long time because all I could see was an "Error" message where I was supposed to be able to toggle the wifi on and off. I tried rolling back to my previous ROM. No go. And the culprit the whole time was ROMManager's CWM.
I tried rolling back my recovery.img file to the Tiamat version recommended in this forum. I kept getting all of these crazy "could not mount" errors for pretty much EVERYTHING. I thought my recovery partition was effed. So I rolled back to stock. Followed pretty much the same instructions you linked to.
From there I was able to boot into the stock OS. WiFi worked. I breathed deeply for a minute or two then dove right back in.
If I was in your position I would (and I did, though not from a boot loop) boot into fastboot and unlock the bootloader again. You can do it by holding the Vol down key as the device boots. When fastboot loads type "fastboot oem unlock". Press the Vol down key then the Vol up key. Do that again. Your device is unlocked now! Hooray!
Now you need to install a recovery.img. (I just did this too.) Get the .img file here: http://forum.xda-developers.com/showthread.php?t=1074979
Boot into fastboot again. Put the recovery img file you downloaded into the same directory as your adb and fastboot executables (if you haven't already linked to them in your PATH). Type "fastboot flash recovery recovery-lotsofstuffhere.img". Type "fastboot reboot". 2 seconds after the Motorola logo pops up press the Vol Down key. Then press the Vol Up key to enter recovery.
Ok, here's where I found out what a dumbass I was. I got all of the stupid "can't mount anything" errors again. I thought, HOLY ****. I just did all of that work, spent hours troubleshooting and reformatting and bringing it back to stock and flashing the custom recovery all over again just to run into the SAME error. I really thought I was screwed. Then I found some forum where a guy was complaining about the same error. He realized he was getting it because his sd card was half-way out. I thought - "SD CARD?!?" Some guys told me I needed one earlier too, but the ROMManager CWM didn't require it. It just screwed up my system files. So I popped one in and rebooted. Voila. Everything's kosher. If YOU have the same problem, make sure you've got an SD card in.
Ok, so now you're in recovery. You'll need to flash an OS of course. If you haven't already got it, get Tiamat 1.1 rom. Put it on the sd card. Wipe data/factory reset. Install zip from sd card. You're golden. At least I was. 5 hours later.
-Mike

Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.

DUDE YOU'RE MY ****ING HERO!!!! I got it running can't say if everything is 100% just yet but the fac tthat im back in is enough to thank you so very much Mike!!! What a guy!

It worked? Great that's excellent news. Just out of curiosity - did you get there because you had ROMManager's ClockWorkMod? Or maybe you didn't do a full wipe before flashing a new rom? Or maybe you restored some WiFi settings with Titanium Backup after a new flash? How did you wind up with tthe problem in the first place - you know, for posterity.

well to be honest i am not 100% sure. I think the source of the problem msut have come from my previous installation of tiamat's 1.4.4 rom, it was always actin up on me and i don't believe i wiped the mod before i updated it and that may have done it. I wish i could give you more than just a pseudo answer.

DeeJayCruiser said:
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
Click to expand...
Click to collapse
This is why they say to make sure you're plugged in when doing this important stuff, lol.

okantomi said:
This is why they say to make sure you're plugged in when doing this important stuff, lol.
Click to expand...
Click to collapse
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
DeeJayCruiser said:
Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo.
Click to expand...
Click to collapse

farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You are right...I had forgotten that from the OP. Very strange indeed.

Yeah I dunno why, my xoom was just acting up. It's fantastic now, albeit the wifi still has a couple kinks but android market issues have been resolved, i get much better streams and with tiamat 1.1 everything is already built in and with a quickboot option =)
Xda...where would i be without you!

farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You should be able to reboot the device using vol up + power, then holding vol down and vol up until it says "Cold booting Linux.....".
This should do the same as letting the battery drain, plugging it in and turning it on.

DeeJay - dunno if you've done this already, but if you haven't you should go back to the Tiamat 1.1 thread and find the Modpack. It fixes the Market update issue and gives you built-in screenshot capabilities and an option to reboot into recovery from the power off menu. It's in there - you just have to scroll down a bit before you find it.
Also - what issues are you having with WiFi?

Thanks for that important tidbit, solarnz. I'm going to file it away for future use.

OMG!!!! Dude you just saved my life! I thought my baby was out the window. I had the exact same problem as you did. I was trying everything from every thread that had anything to do with this problem. I just finished installing and it booted. WHEWWW!!!
Thank u thank u thank u!!

Glad it helped. I'm seeing all kinds of posts in here about the ROMManager CWM. Not good.
Sent from my Xoom using Tapatalk

[Q] Help needed, bootloader error frequently

Hi everyone, i am using milestone A853 model, i follow exactly the guide to root the phone and everything goes perfect, i can boot up and use all the custom rom as usual. BUT the problem now i having is, it happened randomly sometimes i reboot my phone it just got into this bootloader err 1A,23,35,23,00 and i have to flash the GOT 2.2.1.sbf again and do a nandroid restore, i have to flash my phone around 4 times a week.
FYI, i tried the 3 button combination to get into open recovery but still it leads me to the bootloader err page.. is there anyway i can get rid of this?? i need to constantly be with a pc to get my phone working

[d]amour said:
Hi everyone, i am using milestone A853 model, i follow exactly the guide to root the phone and everything goes perfect, i can boot up and use all the custom rom as usual. BUT the problem now i having is, it happened randomly sometimes i reboot my phone it just got into this bootloader err 1A,23,35,23,00 and i have to flash the GOT 2.2.1.sbf again and do a nandroid backup, i have to flash my phone around 4 times a week.
FYI, i tried the 3 button combination to get into open recovery but still it leads me to the bootloader err page.. is there anyway i can get rid of this?? i need to constantly be with a pc to get my phone working
Click to expand...
Click to collapse
According to this thread, it might be an issue with a bad SD card.
http://www.android-hilfe.de/motorola-milestone/12635-milestone-startet-nicht-mehr.html
Can you try with another SD card?
Is it possibly that you have the older version of the Milestone bootloader? (90.73), you can try to flash the VR from kabaldan's website( http://android.doshaska.net/rootable) instead of G.O.T., you just need to put OR on your SD card yourself.

i am using the bootloader 90.78 and androidiani 3.3 open recovery...i try to format my sd card first see if it helps....i flashed my phone yesterday and using a fresh new iceandfire rom 3.0, i tried a couple of times rebooting and turn off my phone and it just boot up without any problem, however this morning i tried to reboot once more and i got this bootloader error again...frustrating =/

[d]amour said:
i am using the bootloader 90.78 and androidiani 3.3 open recovery...i try to format my sd card first see if it helps....i flashed my phone yesterday and using a fresh new iceandfire rom 3.0, i tried a couple of times rebooting and turn off my phone and it just boot up without any problem, however this morning i tried to reboot once more and i got this bootloader error again...frustrating =/
Click to expand...
Click to collapse
AOR dont updated recently, try FuFu openrecovery. it is based on AOR but have many new features and fix, like mmc fix, ext4 module, etc...
if your problem is beacuse the sdcard then you have the mmc error, what is fixed be kabaldan, and he provided a module for the fix, or you have a broken sdcard.

Changing the a different OR will help? i already apply the dsifix.ko 2.6 by kabaldan in my /system/lib/modules directory, just only did a nandroid restore to my phone now, will monitor how long it will last till the next bootloader err...sigh, btw is it ok if i keep trying to reboot like 5 times in an hour time?

[d]amour said:
Changing the a different OR will help? i already apply the dsifix.ko 2.6 by kabaldan in my /system/lib/modules directory, just only did a nandroid restore to my phone now, will monitor how long it will last till the next bootloader err...sigh, btw is it ok if i keep trying to reboot like 5 times in an hour time?
Click to expand...
Click to collapse
5 times seems a bit excessive to me. If all you are trying to do is see if you will boot into the bootloader when you really wanted the recovery, 2 times every hour or so should suffice.

wait a sec, you can enter the recovery console? try to not use the autoboot to or script. if the phone booted to the bootloader mode you can see a triangle, then push the camera and the volume up button to entering the basic recovery mode.
at this point the sdcard not used. then you can try to the update menu, now the phone trying to load the OR update.zip from the sdcard. if you have problem only with the last step, then your sdcard maybe broken, if you have the error at the first step, it is possible that your phone nand memory is failing. in that case you need to call the motorola customer service for the repair.

vadonka said:
wait a sec, you can enter the recovery console? try to not use the autoboot to or script. if the phone booted to the bootloader mode you can see a triangle, then push the camera and the volume up button to entering the basic recovery mode.
at this point the sdcard not used. then you can try to the update menu, now the phone trying to load the OR update.zip from the sdcard. if you have problem only with the last step, then your sdcard maybe broken, if you have the error at the first step, it is possible that your phone nand memory is failing. in that case you need to call the motorola customer service for the repair.
Click to expand...
Click to collapse
Recovery console? you mean the console mode after enter the androidiani menu?i can go straight into AOR with the camera + power button after turning it off.
whenever i got the bootloader error, i cant do anything though, the camera button with volume up is not working.All i can do is flash the .sbf file again.
But for now my phone is still working since the last nandroid restore i did this morning, reboot a few times normally and also reboot to recovery both are working as usual.

[d]amour said:
Recovery console? you mean the console mode after enter the androidiani menu?i can go straight into AOR with the camera + power button after turning it off.
whenever i got the bootloader error, i cant do anything though, the camera button with volume up is not working.All i can do is flash the .sbf file again.
But for now my phone is still working since the last nandroid restore i did this morning, reboot a few times normally and also reboot to recovery both are working as usual.
Click to expand...
Click to collapse
it is sadly, but it is possible that your phone nand memory unstable or have some crc error. do you often reflash before?

vadonka said:
it is sadly, but it is possible that your phone nand memory unstable or have some crc error. do you often reflash before?
Click to expand...
Click to collapse
i only started flashing few weeks ago but the bootloader error occur too frequently that i have to flash at least once every 2 days...for now i see that it lasted longer than usual,if it is really nand memory unstable means that there is nothing i can do to fix it?

[d]amour said:
i only started flashing few weeks ago but the bootloader error occur too frequently that i have to flash at least once every 2 days...for now i see that it lasted longer than usual,if it is really nand memory unstable means that there is nothing i can do to fix it?
Click to expand...
Click to collapse
you cant fix that, only the motorola service, but i suggest to try it some benchmark software like antutu benchmark. with that you can test the memory and see what happened.

well i guess the only solution will be not turning off my phone/reboot for as long as i could, don't wan to take risk later it gets into bootloader error again

My phone always stuck at bootloader when it's hot while booting up.
Wait few minutes or use a fan to cool it down will solve it.
When this happen, recovery mode won't start
and flashing new ROM won't help or even make problem worse because of extra heat produced.
Avoid rebooting after gaming/heavy use is my workaround.

imTigger said:
My phone always stuck at bootloader when it's hot while booting up.
Wait few minutes or use a fan to cool it down will solve it.
When this happen, recovery mode won't start
and flashing new ROM won't help or even make problem worse because of extra heat produced.
Avoid rebooting after gaming/heavy use is my workaround.
Click to expand...
Click to collapse
when u stuck in the bootloader it shows the error code like mine? or just the usual bootloader screen? i tried leaving the phone for few hours without doing anything but it still stuck at the bootloader screen with error code =/

I doubt this will help, but can you try flashing an official 2.2 sbf and try it for a few days? or maybe get an official 2.2 sbf, then root it, then install a rom.

hey there just to informed you guys here that my phone currently had no bootloader error so far for a week, i am using Froyo Mod 2.9.3 and everything just work well. Wonder what happen actually to my phone previously when i flash other rom.
Just wanna ask will the following step i did causes a bootloader error?
-Flash 2.2.1 got sbf files.
-Reboot to recovery (using the latest minimod), Click on root phone (i not sure will this cause the problem as this is suppose to be for stock rom?? plz correct me if am wrong)
-Wipe Dalvik,cache and data
-Apply update of custom rom and gapps.
-Reboot

Stucked on rebooting loop using Prime v 1.9.1

Hello everyone,
First i know this is the general Q&A but since i do not post often [ever] i can't post directly to the development forum for the Prime [ROM]
My Transformer is a B6 model
So here is my issue, I installed Prime about 4 days ago was working fine no problems, and just today (silly of me) i realized that the time zone for the table was at default (don't remember what it was) i think UTC - 0, in any case i went ahead and changed that to Eastern didn't install anything new other the amazon market app.
In any case the table was working fine but as soon as it went to sleep it got locked into a rebooting mode it will perform the mem check and POST, it completes initialization but when it reaches "Activating root access..." it reboots and the cycle repeats.
I can obviously re-flash it and get back to working order but is a rather a unusual error, by the way i do have APX access.
Any ideas?
Thank you very much

Cheers for posting in the correct section dude. You have a problem, you are asking a question.
Thanks for not cluttering up the DEV threads with this.
Have you tried a cold boot?
Also, boot into CWM and clear the caches
Still havin probs? then reinstall the rom and see what happens
Cheers
CaNsA

XRACER said:
Hello everyone,
First i know this is the general Q&A but since i do not post often [ever] i can't post directly to the development forum for the Prime [ROM]
My Transformer is a B6 model
So here is my issue, I installed Prime about 4 days ago was working fine no problems, and just today (silly of me) i realized that the time zone for the table was at default (don't remember what it was) i think UTC - 0, in any case i went ahead and changed that to Eastern didn't install anything new other the amazon market app.
In any case the table was working fine but as soon as it went to sleep it got locked into a rebooting mode it will perform the mem check and POST, it completes initialization but when it reaches "Activating root access..." it reboots and the cycle repeats.
I can obviously re-flash it and get back to working order but is a rather a unusual error, by the way i do have APX access.
Any ideas?
Thank you very much
Click to expand...
Click to collapse
Hi, I doubt that changing the timezone would have a negative effect on your transformer so I'm wondering if maybe something else causes this. Maybe some app that doesn't like the TZ to be changed or maybe even something completely unrelated. Can you get a logcat of the problem and it might help to shed some light on this problem you are experiencing?

you probably have a bad download. Redownload the Tom and try again.
Redownloading the Rom would be better though...oopps

Hello everyone,
thanks for the quick reply, although i am familiar with computers in general i am not very familiar with the android platform.
How do i get it if the system keeps rebooting every 5-7 seconds? or is by default created when the system reboots?
I have been reading through the android dev tools and it needs to be access via adb, i am not very familiar with this environment. Any guidance will be appreciated.

power on with power / vol - and when it says to hit vol up. Yhis will boot you into CWM. Clear dalvik and cache and reboot. If that doesnt work then just flash the rom again. If that doesnt work then wipe data.

thebadfrog said:
power on with power / vol - and when it says to hit vol up. Yhis will boot you into CWM. Clear dalvik and cache and reboot. If that doesnt work then just flash the rom again. If that doesnt work then wipe data.
Click to expand...
Click to collapse
Hello,
Thanks for the reply, i have already try, all of the above mentioned steps, except for the last one i am not really sure what you mean (If that doesnt work then wipe data)
Also i attempted to install another rom (revolver) in this case since it hides the POST procedures it just shows the eee Pad and Asus logo for about 7-10 secs and then reboots

There is an option in CWM that wipes data/factory reset. It wont wipe your personal folders or your external sdcards but it will reset the system back to the beginning and remove all your apps which you have to reinstall

thanks i also did that as a last ditch effort, yet nothing.
hmmm... i refuse to believe my tablet is bricked.
What i will try to do is restore to stock 3.1 and see if that works.
it just seems weird that it was working with no issues until i modified the TZ.
But thanks, and i will give the reset one more try.
----Update----
On a side note.
when in recovery mode i have tried the restore option, but it keeps giving me
E:Can't mount /sdcard
i do presume that is the internal memory where the recovery image is located am i right?
--------------------------Update 2--------------
So i went ahead and nvflash with stock 3.1 that got me back in to working mode, however when attempting to go into the recovery meny it seems something got messed up.
First the prime animation shows up (although i have flashed, revolver and stock on top of that)
then the android logo shows up with a warning triangle on his chest, i guess that is the typical something is wrong here logo.
and then nothing no access to recovery.
So i am trying to flash this one more time, let see if that fixes the issues.
---------------Update 3----------------
well that got me no where :S
i flashed the system with revolver 3.2 via nvflash and i am back to the rebooting loop.
I will wait to see if any of you guys have some ideas, in order to further proceed

Sorry to keep asking.
Does any one have any idea how to resolve this?
Also Roach you mention a log dump, could you please let me know how i can get this log.
thank you.

I know this doesn't help all of your problems, but people have reported having trouble with the nvflash version of Revolver. (myself included) I would recommend, because this is always what works for me when I soft-brick my tablet, nvflashing the latest version of Prime again. Assuming it boots successfully, you can always put the normal version of Revolver on your sdcard, reboot into Recovery, wipe data, and then install Revolver from there.
I hope something works for you soon
Sent from my DROIDX using Tapatalk

Well it seems that did the job.
Although weird why the issue happened in the first place, well i would like to thank everyone who replied. Next time i will keep a rom on my sdcard all the time :-D.
Also thanks XDA And all the community in here.
Sent from my transformer using XDA Premium. (Revolver ROM)