Hi guys
I have re-downloaded the ROM, and also tried flashing with a completely different one, one Sense based the other generic android 2.1 based... That one freezes on the 4 colour pyrotechnics nexus splash screen.
Any ideas how to get around this?
Thanks
Mark
UPDATE:
It seems that I CAN restore to a nanbackup and get back to Sense, but without my settings intact. As soon as I try to flash to ANY rom again, it will still freeze at quietly brilliant or the nexus 4 colour splash.
Ive tired an SD repair, wiped everything I could wipe using the bootloader menu... so why all of a sudden this, I have often flashed with no problem in the past.
Tx
Mark.
yeah dat happens to mine now iv had to revert back to the stock android 1.5, im still rotted tho... its disappointing
Same here, tried the Villain Mod, freezes on this screen.
Attempting to restore now...
Related
okay so the weirdest thing just happened i was restoring a nand of cm7 and it just bootlooped on the splash screen so i tried a full wipe and fresh install but no dice the weird thing is i just nanded to nights ago to do the prl thing and everything worked fine. so i decided to restore my sense rom and it worked fine.
has that ever happened to anyone else.
Yup happened to me quite a few times. It seems like with my phone when I come back from sense it throws my system for a loop at times. Then at times it fine. I just reflash my recovery and its fine when it throws it off.
Root/Hack-Mod_Always *
it freaked me out when it did it, because ive never had it bootloop on the splash screen like that before.
A your not the only one. One time I was pissed because I had a time limit which was the wife with the ""your always on the phone thing"".
Root/Hack-Mod_Always *
My phone does the opposite, loops when I go back to Sense, works fine when I come back.
Booty loops everywhere lol.
sent from a series of tubes.
Boot loops like a BOSS!!
Just today I had a boot loop for flashing a sense ROM so I can update the PRL. Had to Hboot that bizatch and start from scratch. >_<
I want a boot animation that looks like a boot loop.
posted via tappa tappa tappa
For me this only happens going back to Sense. It also happens if I forget to flash fr-boot >_<
Hi all,
I'm having a little problem. I have researched but everything I've found leads me back to square one...
So I followed this guide to installing CM7 on my M2. Please note that I have in the past successfully rooted my phone, installed the Argenstone ROM and one other basic Great Britain Rom. So I'm not a total nub. However at this stage I have a phone that's is useless to me...
My phone is rooted. I have Droid2Bootstapper installed and I managed to get the CWM 3.X installed. I downloaded the all-in-one.zip file from the CM7 ROM thread (the zip is actually called EndlessCM7-110901-nightly_build.zip - hope that's not an issue?)
I booted into CWM and applied the EndlessCM7-110901-nightly_build.zip and after (without a reboot) wiped everything (I had backed it up previously).
I rebooted the phone and...well I get the Google logo with the Motorola M and the Cyanogen bot as the 2 'O' characters. Then after a while a 3D rotating 'square' and the android writing and logo 'shimmering' in and out but that just goes on forever. I left it for an hour at one point and just gave up.
Now I can't even get past the Google logo. I've tried restoring my previous back up but that won't work either. I can't boot into the OS to actually use RSD lite to flash a known working ROM over the top.
When the LED turns blue and I hit the volume key it displays "Android BootMenu <v1.0.3>" which is different to the CWM 3.X that I was getting prior to applying the EndlessCM7-110901-nightly_build.zip file.
From here I can select to recover the last 'latest recovery' which when done loads into CWM-based Recovery v4.0.1.6-defy.
Basically I'm at this point where I seem to be able to load just about every boot menu under the sun and do everything but actually launch the damn OS.
How can I get out of this hole? Preferably I'd like to get everything back to the stock ROM the phone came with so that I can start from scratch again.
Any bodies help would be more than appreciated.
Cheers,
- Matt
EDIT: I have even used CWM 4.X+ to try and restore the Argenstone ROM. it goes through the whole process of checking the MD5 sums, restoring the system and boot images etc and seems to work without any issues. I then wipe all data and reboot. Nothing - still the same cyanogen Google logo and the only thing I can do is boot into all the CWM menus.
*sigh*
Argh feel like a true idiot now. It took me about an hour of searching earlier but I've only just found/remembered how to get RSD lite to see my phone (pwr+volume+camera) and I'm wiping the whole thing to the factory (vodafone) ROM. Might take the opportunity to take it to Vodafone and tell them it never gets a damn 3G connection lol...provided this flash works (touch wood).
Hi, I was running Android on my HD2 for almost 9 months, currently HyperDroid5.5.2. Till now, without any problem whatsoever. Suddenly, when I checked my phone this morning it didn't respond. So I waited a while, then tried pulling the battery. Booting got stuck at Android logo. No problem I thought, I periodically do nandroid backups just in case. Tried to restore it - stuck at restoring data. Then I tried advanced restore, only boot and system... either of them didn't work. After this, I decided to reinstall from scratch - task29, radio, magldr, cwm. The ROM installation got stuck again. So I tried flashing stock SPL and stock ROM from HTC site. SPL okay, ROM not. Got error 262 from the RUU. Tried searching the forum but there is so much stuff that it's impossible to get through. So please don't bash me from beeing a noob. Can anyone please help?
Edit: After the phone finally accepted WM back, I want to put Android back on it... ROM installation gets stuck at restoring Batterystats.bin... any ideas?
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
thebullfrog said:
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
Click to expand...
Click to collapse
You might try and flash the stock kernel which should not allow any under/over clocking or under/over volting. Otherwise flash back to stock using the manual way here http://forum.xda-developers.com/showthread.php?t=1907796 or download the Nexus 7 toolkit and use it to do the same.
Try WugFresh's Nexus Root Toolkit. It has an option to go back to stock if you're soft-bricked.
Well I just did a factory restore/wipe (because Im SO looking forward to setting everything up again...) and it made zero difference. I'll try the stock kernel if someone could point me in the right direction to find a copy of it.
NVM found it. I'll give it a shot.
Ummmm okay then. I had my N7 turned off while looking for a solution to this fiasco. I picked it up so I could flash the stock kernel, and it had turned itself back on. Not only that, but it was fully booted up. Granted it's back to the initial setup after doing a factory restore, but there we go. It automagically fixed itself. Now to spend a couple hours putting everything back how it was. Yay.
Protip children: Always. Be. Nandroiding.
Hi, I've had a S4 LTE for over a year, tried quite a few different roms on it and eventually settled for Diamond John's RR 5.8.5 version. This was working more or less okay until a few weeks ago when the phone crashed during some activity with that blue screen thing.
After that I could not start the rom properly again, it always either boot loops or displays the blue screen. I then tried reinstalling the rom, other roms, bootloader and eventually the stock rom but it still behaves the same - crashes, bootlops and/or blue screen.
I think I did follow the recommended procedures, ie wiping everything, starting from scratch and using appropriate files but can't be 100% sure since I'm not an Android wiz. Hence my question: do you think there is something else I can try to recover this phone or does this look like hardware failure?
Thanks in advance