Man I hope somebody can help me! I was trying to flash the latest CM7 nightly when in the process my phone just froze (while the ROM was flashing in recovery). I left it and the phone finally rebooted. I have the latest CWM with ext4 recovery and the Trinity kernel installed on my phone. When I boot up and try to get back into recovery the phone just hangs on the Trinity splash screen and won't let me into recovery.
I tried to reboot recovery through adb, and the phone reboots but it just takes me back to the battery charging screen (since the phone was plugged in). When I use adb the phone does show up when I do adb devices but gives an error when I do adb shell.
Is there anything I can do to do a nandroid restore or flash a new ROM or basically anything to get my phone back?
dude the same thing happened to me take the battery out then press vol up n power this will reboot ur phone now when its rebooting n u get the blank screen for a split second QUICKLY hold vol down n power (recov) n u should get back in recovery good luck bro
after u take batt out make sure to put it back in n do steps forgot to clarify
I had something like this happen a few weeks ago. I re-preformed the NVFlash of CWM and everything worked after that. I don't pretend to know why, but maybe it'll help you. I was still using the test CWM and no extra kernels at the time. Good luck.
Whew! Man that was a close one! Ok It is doing a NANDROID restore now. Here's what I did:
I installed an older CWM thru NVFlash and then I pulled the batter, placed it back in and then did the power+vol up and then quickly power +vol down and it got me to recovery.
Thanks guys for your help!
mightykc said:
Man I hope somebody can help me! I was trying to flash the latest CM7 nightly when in the process my phone just froze (while the ROM was flashing in recovery). I left it and the phone finally rebooted. I have the latest CWM with ext4 recovery and the Trinity kernel installed on my phone. When I boot up and try to get back into recovery the phone just hangs on the Trinity splash screen and won't let me into recovery.
I tried to reboot recovery through adb, and the phone reboots but it just takes me back to the battery charging screen (since the phone was plugged in). When I use adb the phone does show up when I do adb devices but gives an error when I do adb shell.
Is there anything I can do to do a nandroid restore or flash a new ROM or basically anything to get my phone back?
Click to expand...
Click to collapse
Dont stress too hard, ya its a pain and you may have to funble around for a while but you'll get it. I started periodically copying a 'latest backup' along with a 'cwm recovery' file and saving it on my PC Hard Drive. I actually have it setup now where both ROM Manager and TI Backup save the file to my SD card and it then sync's nightly at like 3am to my DropBox fileshare... that way if I'm ever away from my pc I can just find a pc to use and quickly grab it with all the materials I need in one spot (TIB backs-up all your apps by the way which is nice).
If worst comes to worst I grabbed the stock ROM off a thread here and I can link you to it if you need it. I'm sure you'll be able to reflash your backup but if not your phone isnt necessarily toast... its just a headache.
I have a gtablet with CM7.03 on it. It's been working for a while. I hadn't booted it in a while and just tonight I tried to boot it. The cyanogenmod logo comes up and animates for a few minutes, then the screen goes black, the process repeats.
I'm hoping someone can give me some steps to follow to figure out what's wrong. I booted in recovery mode, but wasn't sure what to do first. Should I clear caches? Any expert advice would be appreciated. I'm a programmer, but I'm new to all this Android mod stuff.
I know this is going to sound like a really dumb question, but is it charged? The reason I ask is because you mentioned not turning it on for a while and the battery can drain even then.
If it does have a charge, the only thing I could think of would be (after wiping cache and dalvik and seeing if that works) to wipe data completely IF you have a backup/don't care about starting over.
It does have a charge. I even tried booting it with it plugged in. I just constantly sits on the animated CM7 logo, then goes black, then sits on the logo again.
When I boot to ClockWorkMod recovery, I see:
wipe cache partition
wipe Dalvik cache.
Can I do both of those without losing stuff? If someone can explain what those caches are actually used for, I would really appreciate it.
Well, I couldn't wait and cleared both. Still same problem.
The odd part is that I hadn't changed anything. I'm 99.9% sure it was working. I shut it down, left it plugged in, and then days later tried to boot it.
I can only imagine that an app is starting up on boot that's having issues. Is there a "safe" mode like windows has where I can boot with the minimum OS so I can somehow remove some apps from starting?
Thanks,
Mark
markdemich said:
I have a gtablet with CM7.03 on it. It's been working for a while. I hadn't booted it in a while and just tonight I tried to boot it. The cyanogenmod logo comes up and animates for a few minutes, then the screen goes black, the process repeats.
I'm hoping someone can give me some steps to follow to figure out what's wrong. I booted in recovery mode, but wasn't sure what to do first. Should I clear caches? Any expert advice would be appreciated. I'm a programmer, but I'm new to all this Android mod stuff.
Click to expand...
Click to collapse
What I find odd is the fact that it was running fine before you shut it down for the last time.. The only thing I can think of is there was some sort of low level data corruption before the last time you shut down..
Do you remember installing any new apps or flashing anything like a different kernel, modifying the Build.Prop or anything that may have an adverse effect to normal booting? If so, that may be the cause of your trouble. Since you have at the very least a boot sequence (with Bootloop) it doesn't appear to be a soft brick so that's some good news for you.
I can only suggest if you have a backup use it via recovery mode.
If not you could try and start over from scratch by installing a fresh copy of 7.0.3 (Be sure to Wipe Data and Cache AFTER Flashing) via recovery mode if you can get the zip file copied to your internal SDCard, I say if because with some versions of ClockworkMOD for the GTAB, it will only read from the internal SDCard and not the External SDCard.
The version of CWM I use is v.2.5.1.8 which I believe is also a play on Bekits v.8 but I'm not sure at the moment.
v.2.5.1.8 will mount the USB Storage (External SDCard)via recovery (Mounts & Storage> mount USB Storage) so you can copy the fresh zip file onto it and CWM will read from that card and not the internal SDCard.
If all else fails, you may need to try and NVFlash, which is used to restore the GTAB to its original Out of the Box Condition.. Which should only be used in the event of a Soft Brick...
Good Luck!
markdemich said:
I can only imagine that an app is starting up on boot that's having issues.
Click to expand...
Click to collapse
That and filesystem problems on /data are what I suspect.
Since you are a programmer, do this to find out what's wrong:
1. Switch off gTab.
2. Attach the USB cable to the gTab.
3. Run "adb logcat > logcat.txt" (or "adb logcat | tee logcat.txt" on Unix) on the host PC.
4. Power on gTab.
This will collect logs almost right from the beginning which might hold a clue as to what's wrong.
You might also want to read through these 2 posts:
gTab partitions
gTab SD cards
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
I have absolutly no power on my phone. I was messing around with daemon tools and set it to ondemand. Then about an hour later I updated all apps from market place. I then rebooted the phone and problems started.
It would boot up to lock screen the freeze. Tried removing battery several times and same results. Then booted to recovery and was trying to unmount sdcard from there so I could just wipe and reload Mikes1987 latest rom. (Rev.HD.4.0)
but I couldnt. Then removed sd card and installed to pc to load rom then try to boot back into recovery and wipe phone. Well when done transforing super wipe and ROM I can't. There is no power up. Pluged into wall and also no charge light.
WTF did I do I have had this phone rooted for about 6 months and always changing things. Please Help
xGr4ndx2 said:
I have absolutly no power on my phone. I was messing around with daemon tools and set it to ondemand. Then about an hour later I updated all apps from market place. I then rebooted the phone and problems started.
It would boot up to lock screen the freeze. Tried removing battery several times and same results. Then booted to recovery and was trying to unmount sdcard from there so I could just wipe and reload Mikes1987 latest rom. (Rev.HD.4.0)
but I couldnt. Then removed sd card and installed to pc to load rom then try to boot back into recovery and wipe phone. Well when done transforing super wipe and ROM I can't. There is no power up. Pluged into wall and also no charge light.
WTF did I do I have had this phone rooted for about 6 months and always changing things. Please Help
Click to expand...
Click to collapse
Were u also playing with the voltages when ur phone started goin crazy? The first part sounds like u U/V'd too much & made it very unstable. And u said u were u trying to unmount ur sd from recovery & it wouldn't unmount so u pulled it out anyway?
Btw, didn't mean to "thank" u so there's a freebie :')
I have never really messed with overclocking but ther was an option to download something and I did, but really didnt change anything that I can recall but not saying I didn't.
I was trying to load the fresh ROM from clockwork recovery. but I couldn't get my pc to see it as storage device so I could transfer it over. I then removed sd card and installed into pc and loaded it. When I was done I put back together and that's It. Still searching but no results.
xGr4ndx2 said:
I have never really messed with overclocking but ther was an option to download something and I did, but really didnt change anything that I can recall but not saying I didn't.
I was trying to load the fresh ROM from clockwork recovery. but I couldn't get my pc to see it as storage device so I could transfer it over. I then removed sd card and installed into pc and loaded it. When I was done I put back together and that's It. Still searching but no results.
Click to expand...
Click to collapse
I'm confused... you saying you can't mount your SD? If thats it, there is some bad data somewhere on it back up the pictures and whatever files, format the SD.
.... with the overclock and downloading something and not sure if you ran it. Good rule of thumb if you don't know wtf it is, don't touch it.,..... just sayin.
I was running CM10 on a rooted TFT101. I was having some WiFI connectivity issues so I decided I would try out a new rom. I used Titamium Backup and backed up all my needed files to my Mico SD card. Once backed up, I rebooted into CWM v6.0.1.3. I went to do a factory reset prior to flashing the new rom. The tablet just froze. I rebooted the tablet back into CWM. I tried to again do a factory reset and again the tablet just froze. I tried to boot back into CM10 and I just sits and spins and never actually boots into the OS. I decided that I would just go ahead and just flash the new rom and do a factory reset after the fact. I placed the new rom on the micro sd card and booted back into CWM. I attempted to install zip from SD card and now I get e:can't mount /sdcard/. I have tried 3 different micro sd cards and nothing. I have formatted each to fat32 and not one of them is recognized. All 3 are recognized by windows.
Since I can't boot into the OS...and I can't load a new rom....I am dead in the water. Any help would be greatly appreciated.
Thank you in advance.
If you can get it to that endless boot logo and connect it through USB, ADB (info - download) should be able to access whatever's left on your device assuming it gets far enough in the boot process. If it does, you can adb pull the backups to your computer to save them.
That being said, Easy Flasher will help you get back to 100% unrooted stock and "unbrick" your device with a few clicks. Then you can start over with a new recovery and rom. But it will wipe your entire device clean, hence why I suggest you first check if you still have backups and if you do, pull them on your computer using adb.
I can't help with the CWM problem, I haven't used it in a long time.
Lethe6 said:
If you can get it to that endless boot logo and connect it through USB, ADB (info - download) should be able to access whatever's left on your device assuming it gets far enough in the boot process. If it does, you can adb pull the backups to your computer to save them.
That being said, Easy Flasher will help you get back to 100% unrooted stock and "unbrick" your device with a few clicks. Then you can start over with a new recovery and rom. But it will wipe your entire device clean, hence why I suggest you first check if you still have backups and if you do, pull them on your computer using adb.
I can't help with the CWM problem, I haven't used it in a long time.
Click to expand...
Click to collapse
Thank you Lethe6. I saw that option and wondered if that might help me. I will try it out today.
One quick question. If I flash back to stock I am guessing I will just need to reroot once I am able to boot it back up?
Thank you again for your assistance.
Yes exactly. Easy Flasher has a root option as well so it's fairly easy to get going with customizations after restoring to stock!
Lethe6 said:
Yes exactly. Easy Flasher has a root option as well so it's fairly easy to get going with customizations after restoring to stock!
Click to expand...
Click to collapse
Go figure. I went to fix the issue last night per your instructions and I was sitting at the Google login screen for the the new rom I loaded. What ever issue I was having corrected itself. That never happens. I guess I shouldn't complain =)
Thank you again for your assistance Lethe6!