Installed 4.5.91 beta 3 over HKTW and stuck in bootloop. Has anyone found a fix this without flashing back to 4.1.26 or earlier stock builds? I've tried wiping user data, cache, and restoring HKTW through CWM and that loops as well. Wishful hoping I wouldn't have to flash back. Found no help in the 22 pages in the original developments portion of the forums.
Edit: Resolved with 4.1.83 service sbf flash ---> flash pudding ---> cwm ---> 4.5.91
Edit: Passing along warning with above method. http://forum.xda-developers.com/showthread.php?t=1160408
Wasnt an issue for me.
Wiped my HKTW, installed beta 3, wiped again and booted ok
Related
I'm installing CM7 on my Thunderbolt runing MR2 radio. I'm following this forum post: http://forum.xda-developers.com/showthread.php?t=1049542. I'm wiping data from the recovery mode. Also wiped Dalvik cache. After installing rom recovery mode and rebooting, it get stuck on the HTC white screen. It's been like 10+ minutes. Any ideas on how to get this installed? Do I need a special kernel, if so which one? Thanks!
fix
Got it fixed, nevermind.
For the benefit of others, the issue was that ClockworkMod (CWM)needed to be reflashed and updated. CWM wasn't wiping my data which caused CM7 not to work correctly. Flashing and updating CWM fixed this.
Hi
I went from 1.8.3 with Gingerblur 4.5 to this official build:
http://www.filesonic.fr/file/373046...OLE-31-release-keys-signed-Vodafone-EU.sbf.gz
(flashed with RSD). Before, I unlocked the bootloader with the IHOP. Then I installed romracer recovery, And rooted it with droid3oneclick. I also did the ramfix via the recovery. Everything is ok.
But (ONLY)when I remove the battery, I'm stuck into bootloop, on the M red logo "dual core" with the "unlocked" in the top left corner.
I tried to delete the cache and the date but it doesnt work. Only way to make the phone boot is to flash again the boot.img via fastboot or to flash the ramfix via fastboot. If I turn the cell off without pulling the battery it's ok, it's very weird.
Any idea appreciated !
ohh god did you rsd back to completely stock b4 flashing gingerbread if not then thats the culperit i was on 1.8.3 also with gingerblur i rsd back too 1.27 then ran the updates ota one at a time to 1.8.3 then unlocked bl then flashed gingerbread and all works fine try to wipe data wipe.cash and.in advanced wipe dalvic cash then reflash. gingerbread and pray
Sent from my MB860 using xda premium
I flashed the build I've mentionned above with RSD from 1.8.3 with gingerblur, without returning to 1.8.3. I will try a factory reset + reflash this evening and will keep you up to date
Thank you
I was able to unlock my bl after the OTA update to 141. However during it I must have corrupted something on my phone and now I cannot boot into any OS.
I've tied severl CM9 Kangs as well as the stock 141 sbf and the offical CM7 ROM.. and i get stuck in a reboot cycle.
Every time either my phone reboots right after the boot screen (att or cm9 or cm7) or it just hangs on the boot screen.
I've tried several solutions including: factory reset, wipe cache, wipe Dalvik cache, wipe /system & /cache & /data. Trie fastbooting 91 boot and system partition. Also tried flashing the 141 sbf that's been floating around *ooops*...
The good news is that I still have the ability to get into RSD or Fastboot and can hide the Unlocked msg by flashing back to the 141 sbf (in case I have to warranty the phone out)... but i'm hoping to figure this out instead... all i want in a CM9 kang
Any help is appreciated,
THX
-Alek
anyone the right way to wipe everything and re-install... and/or proceed here?
maybe your sd card is corrupted... You can try to download the rom again and use another micro sd card, and then start the role process again...
Tried two SD cards already, no luck. What sucks is that I can flash the whole stock sbf for 141 but that doesn't HELP!
i gave up and exchanged my phone. told them it's been rebooting after the 4.5.141 upgrade. got me a new atrix now... probly won't fk w/ this one
Just to let other people know who may have this problem, but I believe this requires an unlocked bootloader. Not sure.
I've seen it fixed by erasing data using fastboot itself. Fastboot does a more thorough job at it than any recovery.
To do so, type this for fastboot:
Code:
fastboot -w
Then follow romracer's instructions for installing his recovery here. (Again, requires unlocked bootloader. I know this one does)
Basically you want to fastboot wipe and then reinstall the recovery, then attempt to reinstall a rom.
Hey, I just flashed Neutrino and some of the addons. After all was done i did a reboot and was stuck on the neutrino bootup loop. I checked the forums and someone with the same problem was told to wipe dalvik and cache partition. Then do a reset, reboot into fast boot. Access fastboot from CMD on my PC and use command faastboot erase boot. It says it finished. I unplug and reboot my phone only to get stuck on the moto screen. Yes I am using romracers. Any help would be greatly appreciated as I would like to get my atrix back up and running. Unfortunatly I can't post in the thread that i read the fix in because im a new member. I might just stick with darkside ROM as i've used it before and never had any problems >.<
Is it safe for me to flash a new SBF. I know neutrino thread says do not flash old SBF but can I flash an updated SBF? If so can someone link me to the most current SBF. I'm on 2.3.6 ver 4.5.1 i think? 4.5. somethin lol.
I had the same problem when I flashed Neutrino 2.8 EE. Just flash Neutrino 2.8 GT and problem will be gone.
I have a sch-i500 that is rooted with cwm working.
I am very interested in running liquid smooth v 2.9 found here: http://forum.xda-developers.com/showthread.php?t=2245120
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
http://forum.xda-developers.com/showthread.php?t=1026746
seems to be the best way for me to recover from this (looks like I flashed a non voodoo rom without removing voodoo) but I am unable to get the phone into download mode with or without the battery in the phone.
please help......(update) Alright, I am a moron. needed to have a powered usb port. on my way to recovery. thanks for having all this great info in one place.
aircooledbusses said:
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
Click to expand...
Click to collapse
Oh so close.
When coming from 2.3.x ROM you will need to flash the rom (liquid: or other 4.2.x) you will need to flash 2 more times...
The 1st flash get you into the new recovery only,,, as you found out.
2nd flash will pop up with an error message about incompatible partition and telling you to re-flash again,,,
So 3rd flash actually installs your new ROM
Then install a current/compatible Google gapps
.
Enjoy
.
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
aircooledbusses said:
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
Click to expand...
Click to collapse
what does the error say besides status 7?
did you odin the CWM4 fixed for cm7 then install the ROM 3 times?
can you get a pic up for us to see?
just to be sure......using odin, I repartitioned with the pit, and flashed a E03 rom. rebooted the phone fine.
flashed the CWM4 fix for 7 and redid the GB bootloaders as well.
went into recovery and factory reset, wiped cache, and dalvik.
installed liquid-JB-v2.7-Official-fascinatemtd.zip this time first time took me directly to clockwork where I flashed again. prompted with install from sdcard complete. repeated and got same message.
factory reset, wipe, wipe and flashed gapps. Everything seems to have worked this time with the v2.7Official instead of 2.9. I will play with this for just a bit and probably try it again tonight with a fresh downloaded copy of v2.9. I really do appreciate your assistance and help and I would not have gotten this far without the forum.
update:
flawless installation of v2.9 since 2.7 was already installed. (installed via cloclwork mod recovery)
It was most likely an operator error that prevented me from installing 2.9 after E03. But I don't see the benefit of going back to recreate why it didn't work. Thanks again all is good and right.