I was working an issue on my Bionic with dock modes not working, so I did an FDR on the stock ROM and now it won't boot and neither will a SS restore of the stock ROM in the stock ROM slot. I have two separate backups of the stock ROM, and neither one will boot in the stock ROM slot; they both hang right after the Droid boot sound effect. If I leave it alone for a few minutes the hardware keys give a haptic feedback, but the screen stays blank.
On a whim, I tried restoring my most recent stock backup to ROM slot 2, and it works just fine. Question is, what happened and how much should I worry about the stock ROM slot proper not working correctly? I'd rather not go through the entire exercise of RSD/Fastboot/Root/SafeStrap/rebuild etc. if I don't have to, but something is clearly amiss.
TIA for any advice...
Related
I'm new to this whole flashing custom ROMS business. I have a CDMA HTC Hero 2000 and I downgraded to the original 2.1 before the update just fine, rooted my phone just fine. Then I tried to flash Aloysius to it using instructions I found here: [Complete Guide] How To Flash A Custom ROM To Your Android Phone With ROM Manager + Full Backup & Restore | Android News, Reviews, Applications, Games, Phones, Devices, Tips, Mods, Videos, Podcasts - Android Police
After all was said and done, my phone starts to boot with the "HTC quitely brilliant" logo, following by "SPRINT the Now network" logo and after it shows "Now" for many seconds (as it normally does before pulling up the home screen), it reverts back to the HTC logo and repeats this process until I remove the battery.
I removed the microSD and attempted to boot, same thing. Then I held down HOME+BACK+POWER to do a manual hard reset, this took a little longer but again had the same result.
I may just cry now. Please help!!
Run the official sprint ruu, and see what that does for u. Then read the rooting guide here on xda and try it. I personally recommend amon ra recovery to flash roms, rom manger never seemed to work right. Feel free to pm for more help, dont worry u prob arent bricked unless u flashed a gsm rom (which aloysius isn't)
Sent from my HERO200 using XDA App
That's a bootloop not a brick You could try downloading a different rom and flashing it in recovery, nandroid restoring - if you made one, or flashing the same rom again. just wipe your phone before (data/cache/dalvik)
Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.
chrisdegraw said:
Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.
Click to expand...
Click to collapse
Four key words to remember when trying out any new rom
Nandroid is your friend!
additionally, you should always remember to wipe before loading a new rom!
Enjoy!
Yeah, don't ever panic, that was, as everyone said, a bootloop by textbook definition. I've never seen a brick before, but I'm damn sure it won't get as far as the Sprint logo. The only way to brick a CDMA Hero is to flash a GSM Radio/Bootloader to it.
I tried to flash the boot image for my first custom rom using easy kernel flasher, and my Vivid is now stuck at the white HTC screen. I then realized that I had used rom manager to flash CWM, even though I had already flashed the custom CWM from the superguide. Is this what caused my phone to hang at the HTC screen?
Is it safe to pull my battery? What is the next step, repeat step 2 from the superguide and then reflash the new kernel and rom?
I apologize if this has already been answered, I just haven't seen this exact question elsewhere and I don't want to pull my battery without being sure that I won't brick my phone or make my problem worse.
Rom manager does not work for our phones. That is why your phone is stuck. I remember another post like this. The guy pulled the battery and flashed the new cwm image without rom manager and it worked. I believe you would start at step two to correct your issue. Let us know how it goes for you.
Ok I pulled the battery and put it back in and now it won't boot at all. The power light flashes orange and then nothing happens. I'm getting a bit more worried about this now.
androuglas said:
Ok I pulled the battery and put it back in and now it won't boot at all. The power light flashes orange and then nothing happens. I'm getting a bit more worried about this now.
Click to expand...
Click to collapse
Alright, so I just did the same exact thing you did... updated CWM from ROM manager and tried to backup the ROM, hung at HTC screen. I haven't gone through the steps to reverting my CWM yet but I did get it to boot. Pull the battery, put it back, boot into HBOOT and let it do its thing, go to fastboot and then reboot. Give it a minute. Mine came back, set for a while at the boot image but it came back.
I just did the whole thing again but with out the HBOOT process and it worked too. Didn't take nearly as long as before at the boot image. Try both or see if you can't get to recovery from HBOOT. I'm pretty new to the Vivid since this is my wifes phone and its a lot different from my Inspire, the process of everything that is
Now reading your 1st post again, I didn't do the exact thing you did but close...
I tried again and it went in to h-boot, and i was able to reinstall the custom vivid CWM. But now I'm not sure if the kernel flash which started all this worked. Is there a way to find out while in recovery?
Should I reboot the phone now, or just flash the rom I was planning on flashing originally? Or should i try to return everything to stock and start all over?
cbronson41 said:
Alright, so I just did the same exact thing you did... updated CWM from ROM manager and tried to backup the ROM, hung at HTC screen. I haven't gone through the steps to reverting my CWM yet but I did get it to boot. Pull the battery, put it back, boot into HBOOT and let it do its thing, go to fastboot and then reboot. Give it a minute. Mine came back, set for a while at the boot image but it came back.
I just did the whole thing again but with out the HBOOT process and it worked too. Didn't take nearly as long as before at the boot image. Try both or see if you can't get to recovery from HBOOT. I'm pretty new to the Vivid since this is my wifes phone and its a lot different from my Inspire, the process of everything that is
Now reading your 1st post again, I didn't do the exact thing you did but close...
Click to expand...
Click to collapse
Thanks man. I got into recovery and fixed the CWM problem, but now I'm not sure what kernel I have running so I don't know if its safe to reboot.
Though I know how to use CWM I couldn't tell you how to check your kernel and whatnot from there. Best thing I can think of, or what I'd do, would be to wipe everything out and restore a nandroid, granted if you have one I've never really messed with kernels untill now so I don't even know if that would work
I realized I could just reflash the kernel while I was in recovery. It hung at the htc screen on the reboot like before, but i just pulled the battery, went back into recovery, flashed the rom, and now everything is working perfectly with the new rom. What a relief.
I think the original kernel flash may have actually worked, and I just freaked out when it hung at the htc screen and assumed it was because of the rom manager/cwm thing. It may have been fine all along.
Here is something that will help with flashing kernels.
http://forum.xda-developers.com/showthread.php?t=1423151
Flash Image GUI
ok i did the same thing awhile ago, i flashed new CWM then insatlled rom ...the Kernal did load thats the reason you got the white screen ..so just go ahead and load your rom you should be fine
Before I screw anything up any further I figured it's time to ask.
I'm using Odin and I flashed ICS(ICS_4.0.3_MR1-RC4.2_Captivate.zip) awhile back and everything had been running fine for a couple months now.
I noticed longer load times during loading animation when powered up(Figured it was just 'cause of more start up apps) eventually it stuck looping @ animation screen. Out of frustration I was hitting the lock key while loading up and somehow managed to stop the animation loop and lock the screen which enabled me to use the phone again for the day until my phone was turned off by accident
In my attempts to resolve this issue, I tried clearing all cache's(Delvik,Partition etc.) and reflashing the rom to no avail.
I figured if I formated /boot and than reinstalled it might work, *BIG* Mistake. I could only access download mode so I couldn't reinstall /boot
I reflashed using the speed kernel to get back recovery mode and than flashed my ICS.zip again only to be still stuck with this boot loop issue. I've found the topic http://forum.xda-developers.com/showthread.php?t=731989 as a last resort.
How can I recover from boot loop without losing my data? Thanks.
3randon said:
Before I screw anything up any further I figured it's time to ask.
I'm using Odin and I flashed ICS(ICS_4.0.3_MR1-RC4.2_Captivate.zip) awhile back and everything had been running fine for a couple months now.
I noticed longer load times during loading animation when powered up(Figured it was just 'cause of more start up apps) eventually it stuck looping @ animation screen. Out of frustration I was hitting the lock key while loading up and somehow managed to stop the animation loop and lock the screen which enabled me to use the phone again for the day until my phone was turned off by accident
In my attempts to resolve this issue, I tried clearing all cache's(Delvik,Partition etc.) and reflashing the rom to no avail.
I figured if I formated /boot and than reinstalled it might work, *BIG* Mistake. I could only access download mode so I couldn't reinstall /boot
I reflashed using the speed kernel to get back recovery mode and than flashed my ICS.zip again only to be still stuck with this boot loop issue. I've found the topic http://forum.xda-developers.com/showthread.php?t=731989 as a last resort.
How can I recover from boot loop without losing my data? Thanks.
Click to expand...
Click to collapse
First off what do you mean by data? Do you mean your photos and music that is stored on the internal or external SD or do you mean the apps you've installed and any data or settings related to them or your current setup? If you're talking music and pictures, with the exception of rare cases your internal and external SDs should never be effected by a basic flash but the link you provided suggests that it will wipe everything if you use the master clear option. If mean the other "data" I mentioned theres no way around that short of a backup prior to a flash.
Now as far as the link you posted I've never used it so I don't know if it would help. However I would suggest this... http://forum.xda-developers.com/showthread.php?t=1300843 go to the third post and use the KK4 one-click without bootloaders. That should hopefully fix your situation and again unless something weird happens it won't touch your photos and whatnot.
On a side note have you attempted getting back into recovery from the bootloop, rewiping the usual, and flashing the rom again? Sometimes that corrects problems.
m1batt1 said:
First off what do you mean by data? Do you mean your photos and music that is stored on the internal or external SD or do you mean the apps you've installed and any data or settings related to them or your current setup? If you're talking music and pictures, with the exception of rare cases your internal and external SDs should never be effected by a basic flash but the link you provided suggests that it will wipe everything if you use the master clear option. If mean the other "data" I mentioned theres no way around that short of a backup prior to a flash.
Now as far as the link you posted I've never used it so I don't know if it would help. However I would suggest this... http://forum.xda-developers.com/showthread.php?t=1300843 go to the third post and use the KK4 one-click without bootloaders. That should hopefully fix your situation and again unless something weird happens it won't touch your photos and whatnot.
On a side note have you attempted getting back into recovery from the bootloop, rewiping the usual, and flashing the rom again? Sometimes that corrects problems.
Click to expand...
Click to collapse
I should be more specific when refering to data, I need my text message, pictures and videos everything else is synced online. I'm looking into the link you've suyggested now and I have tried wiping the caches(delvik,partition) and reflashing the rom to no avail.
I've looked @ the kernels you've suggested and looks good except I'm not sure what it means by wipe(What will it wipe?) and why not the one with the bootloaders since I'm having bootloop issues?
Thanks
3randon said:
I should be more specific when refering to data, I need my text message, pictures and videos everything else is synced online. I'm looking into the link you've suyggested now and I have tried wiping the caches(delvik,partition) and reflashing the rom to no avail.
I've looked @ the kernels you've suggested and looks good except I'm not sure what it means by wipe(What will it wipe?) and why not the one with the bootloaders since I'm having bootloop issues?
Thanks
Click to expand...
Click to collapse
Pictures and videos shouldn't be touched but unless you've backed up your messages they will be.
As far as what I linked they aren't kernels they are complete stock ROMs built into a one-click program to take you back to stock. It will wipe and repartition the internal memory that the ROM is installed on. It shouldn't touch your storage memory though.
As far as not using the one with boot loaders, you could but you already have the boot loaders installed if you're on ICS and reflashing boot loaders can potentially hard brick your device. Also flashing ROMs don't touch the boot loaders so they should be intact and using the one-click without boot loaders is the safer choice.
Sent from my SGH-i927 using xda app-developers app
Droid 4 - flashed CM10 onto (following the step-by-step guide) and on stock, no issues with bluetooth, on the ROM, I can't even turn on the BT functionality. Is this a known issue somewhere, or am I alone in this? Thoughts on what I can do to fix it?
CM10 Problem
I flashed CM10 to my stock system today and it WILL NOT boot. I followed all the guides and I made sure to make a backup of my stock ROM to flash back in recovery and restore my stock ROM but I have waited hours for it to boot up and have got nothing at all, just a black screen. As far as bluetooth Idk but if i could get mine working again, I'll be in good shape. I'm sticking with stock for now on. I just have to charge the battery and boot into AP Fastboot mode to reflash it or by holding the volume up and down keys while pressing power and boot into recovery. I hate TWRP Recovery and am looking for an alternate as well. As far as bluetooth issues, there are a lot of issues with non stock ROM's, you just have to find the right ROM that has everything working on it. Continue the good fight man,as am I.
marvin_rock said:
Droid 4 - flashed CM10 onto (following the step-by-step guide) and on stock, no issues with bluetooth, on the ROM, I can't even turn on the BT functionality. Is this a known issue somewhere, or am I alone in this? Thoughts on what I can do to fix it?
Click to expand...
Click to collapse
After installing any nightly or any version of CM10.1, after 1 restart, bluetooth won't come back on. Why??
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.