n00b question, I guess. I came to the Inspire from a borrowed Cliq. I've rooted and flashed GB 2.3.4 successfully, but I hit a bump tonight.
I found other threads about the white screen when doing a Nandroid backup, but my situation didn't really fit.
I've had my Inspire for a month and have created two Nandroid backups - one when I rooted and one when I flashed Gingerbeast. Both times everything was fine.
I want to modify by APN settings (via henrybravo's thread), so earlier tonight I started to backup through ROM Manager. The phone shut down and came back up to the HTC screen... and stayed there. No Clockwork recovery.
I found the Guide to fix softbricking and pulled the battery. I let it sit for a minute and booted it back up normally. It came up fine. Everything was intact.
Was there something else I should have done? Should I flash Clockwork 3.0.2.6? I'm using 3.0.2.5 right now.
Any help would be great. Thanks in advance!
You should update cwr. In my experiences rom manager would always act a little funky. On several ocassions I would get a soft brick when flashing roms. So I do my flashing and nandroid straight from cwr and all my issues were gone.
You should try doing the nandroid from cwr and see if that helps you
Sent from my TARDIS using XDA App
Related
I've tried more than twice now, and I'm sure it's something simple, but I can't recover my backup. Last night for example, wanted to try another rom, a 2.3.4, I was quite happy with my mosaic setup, as usual, and I was running xcal's 2.0 kernel without issue so I backed up through cwm 3. Flash got me into a bootloop so I tried to recover the nandroid but it wasn't the right one. I chose the right date but the b/u was the rom that failed, the bootup screen. So I had to start from scratch to get the setup I liked. Of course when I tried to flash the new rom there were different kernels etc. But that shouldn't matter should it. What am I doing wrong? Thanks ahead of time.
Sent from the frozen tundra known as Canada.
Do you're trying to restore a 2.3.3 backup (Mosaic) to a 2.3.4 rom?
*phone sig* If you're not on Gingerbread you should be flogged! *
Uh, no. you misunderstood.
Sent from the frozen tundra known as Canada.
Those back ups are not to use to recover with. Those are to restore your set up and stuff, you flash the rom it was backed up from THEN restore and its like you never flashed the the other rom.
studacris said:
Those back ups are not to use to recover with. Those are to restore your set up and stuff, you flash the rom it was backed up from THEN restore and its like you never flashed the the other rom.
Click to expand...
Click to collapse
Thanks studacris, yeah, tried that and got an error message and couldn't restore. Sorry I didn't take the message down, I'll try again if it happens again, thanks.
Sent from the frozen tundra known as Canada.
hey all, was hoping someone would be able to help me out, since im still pretty new at all this.
i've had my phone for about 2 months, been rooted since the first week, and have flashed roms before with no problem, this is the first time something like this has happened.
im currently running eternity r186, have been for awhile.
ok, so heres what i did: i downloaded liquid-nonsense 3.2 rom from over at rootzwiki and copied the zip to my SD (this is the rom i was planning to flash)
i made a nandroid of my current rom
i booted into recovery using rom manager (reboot into recovery)
i wiped data and cache, everything went as normal
i went to wipe davlik, hit yes for wipe, and the screen went black and vibrated. then it rebooted to the white htc screen. now it's stuck between the white htc screen that says "quietly brilliant" and the beats audio screen (if you've booted up eternity before you know what i mean)
ive tried holding down power and the vol keys to reboot into recovery but it just takes me back to the bootloop
ive tried a battery pull
i really have no idea wtf to do, please help?
thanks
edit: i figured it out i think. i got into hboot after a battery pull and got into recovery that way, restoring nandroid now. hopefully it restores
but...that was kinda scary for a new flasher such as myself! anyone have any idea why it did that?
Good to hear you got it figured out. Liquid 3.2 is my Fav AOSP.
Since the forums move slower at night next time you have a big problem try and hop on to one of the IRC chats.
No idea why it would do that. Do you have the most recent CWR? If not try and update it. If you do then try and roll back a version unless the rom you're flashing needs the most current version.
Sent from my ADR6400L using Tapatalk
thanks for the reply.
im running the latest version of CWR
after i restored my nandroid I wiped everything as normal and flashes the rom.
i gotta say, i'm really digging this ROM. Barring any major bugs I could see this becoming my daily!
I searched the forums and cannot find a fix for this... now this is my first time looking and I may have missed something, or searched using the wrong words or phrases...
I just recently upgraded my skyrocket to the UCLD2 4.2d build, from http://forum.xda-developers.com/showthread.php?t=1602216
I followed the instructions to the letter, but now whenever I try to power off my phone it freezes, and the only way to fix it is to remove the battery.
I am very new to rooting, and this entire process, but I did double check everything before I did the install process.
Please point me in the right direction to fixing the issue.
download darkside. zip...to acheive full wipe...then flash rom again while still in recovery .....
Sent from my SGH-I997 using xda premium
Mine is doing the same thing after I restored from nandroid. It was fine before. I'm rooted with stock ICS and Mohan kernel. Everything else works fine. It just hangs on the powering off screen. Do you think darkside wipe and redoing my nandroid restoration would fix this? I am also still learning, but have been reading my a$$ off.
Okay guys, I'm only 14 and this really confused me.
I was running the Rom Glorious Overdose V2 and everything was as smooth as butter for several of weeks. All of a sudden everything started force closing and everything became unusable. So I wanted to restore the backup I made with the red Voodoo recovery. I watched all of the logs run and say I had a successful recovery from the backup. When I rebooted the phone, I was stuck at the Sidekick boot screen.
Eventually I was able to ODIN back to the stock Rom but I'm still very confused as to why restoring a backup bricked the phone.
Does anyone know or have ideas why it happened?
Sounds like a permission thing, could've ran a fix. Also mightve been a certain change from your point, to the point in time where you made a backup.
P.S. I'm 12.
Sent from my rooted gift from God 4G running a Gloriously Overdosed ROM using the expensive XDA app
You also can run into problems trying to roll back to the stock kernel and file system.
It's a known issue if you read around the forum a little bit.
Here's what's going on. I flashed an aosp rom(all I ever use). Didn't like it and restored a previous rom I had backed up(I do this all the time). After the restore was done or so i thought the phone just rebooted and wouldn't load anything past the Samsung screen just black and then reboot followed by the same thing. I pulled the battery loaded up recovery manually and tried another backup I had and same thing. I finally ended up going back into recovery manually again and loaded up a rom. It worked but now the phone won't wipe I forget what it says when I try to wipe. Iv since loaded up several roms with the same wipe errors and all seems good. Just weird. I'm using twrp btw. Any ideas on what happened?
Sent from my Galaxy Nexus using Tapatalk 2
djj624 said:
Here's what's going on. I flashed an aosp rom(all I ever use). Didn't like it and restored a previous rom I had backed up(I do this all the time). After the restore was done or so i thought the phone just rebooted and wouldn't load anything past the Samsung screen just black and then reboot followed by the same thing. I pulled the battery loaded up recovery manually and tried another backup I had and same thing. I finally ended up going back into recovery manually again and loaded up a rom. It worked but now the phone won't wipe I forget what it says when I try to wipe. Iv since loaded up several roms with the same wipe errors and all seems good. Just weird. I'm using twrp btw. Any ideas on what happened?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well, if you're GS3 is running then I wouldn't worry too much. However it couldn't hurt to make a nandroid, restore back to stock, and redo the STOCK>root>unlock>flash recovery>flash rom process. You may have messed something up along the way. Either way, happy flashing. PS: you should try out paranoidkangdroid if you love the AOSP experience. CM base with a ton of tweakability.
Anybody else ever experience anything like this?
Sent from my SCH-I535 using Tapatalk 2
A thought.... I flashed a wrong kernel once, I would see the boot animation, then black screen. Maybe you have a wrong kernel?
Sent from my PACmaned SCH-I535