Database Info

I think I managed to brick it :D

I think I managed to brick my Inspire some how I tried using a nandroid backup to restore to an older ROM. Everything restored correctly apparently, but when I go to restart it, I just get stuck on the HTC white screen.
Tried reflashing a few different ROMs, but its still stuck on the HTC screen. How long is this screen supposed to take after a fresh flash?
Any other ideas?
EDIT: SOLUTION FOUND. DO NOT USE CWM 3.X!! More info here: http://forum.xda-developers.com/showthread.php?t=956367

What is the longest you waited?

JCreazy said:
What is the longest you waited?
Click to expand...
Click to collapse
30 min
I just flashed CM7 and it booted right up. I think it's a problem with CWM 3.x and Froyo ROMs. From what I've gathered, CWM 3.x is unstable with Froyo based ROMs.
Just flashed CWM 2.5.1.3, gonna see if I can get this damn thing to work

The new clockwork requires changes to the update scripts be implemented by the devs/modders.
http://forum.xda-developers.com/showthread.php?t=954654
Sent from my ADR6300 using XDA App

Nandroid not taking

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.

Black screen on boot...flarg

Hey all,
Working to get Wallet going on my Verizon S3 and I am running into a snag. I booted into recovery using latest CWM Recovery and realize I had the zip file in the wrong spot so I restarted. After the Samsung logo and Galaxy logo display the screen goes black and does nothing. I can pull the battery and boot it again but it just does the same thing. The only thing I have changed, file wise, is the build.prop but this has never been an issue when booting on any of my other phones. Any ideas? Is this phone hosed?
Rooted stock rom

goinovr said:
Hey all,
Working to get Wallet going on my Verizon S3 and I am running into a snag. I booted into recovery using latest CWM Recovery and realize I had the zip file in the wrong spot so I restarted. After the Samsung logo and Galaxy logo display the screen goes black and does nothing. I can pull the battery and boot it again but it just does the same thing. The only thing I have changed, file wise, is the build.prop but this has never been an issue when booting on any of my other phones. Any ideas? Is this phone hosed?
Rooted stock rom
Click to expand...
Click to collapse
I had the same issue, rooted/debloated stock ROM. Your problem was that you adb pulled/pushed the build.prop file without changing the permissions. Restore a nandroid or reflash stock if you don't have one. The best thing you do if you don't know what you're doing with permissions is just to rename the file, copy it, and change it all in Root Explorer. It'll keep permissions that way. It's really easy to fix, don't worry.

Thanks. Going to flash to stock. I backed up through rom manager but not through nandroid. Wasn't expecting this one. Haha
Sent from my DROID RAZR using xda app-developers app

goinovr said:
Thanks. Going to flash to stock. I backed up through rom manager but not through nandroid. Wasn't expecting this one. Haha
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
It's easy to fix, just take a nandroid next time before you change build.prop to save some headaches. Also, make sure you don't update to the new version of Wallet because it broke my Wallet (not the SE, just the installation) for the time being.

Dysfunctional, insane One X????

Hi
Was running CM10 nightly from 12 Dec. Bluetooth froze while in car. I rebooted phone. It never came back up after booting, just looping Cyanogenmod logo.
Went into recovery, did a Nandroid, restored my previous backup from the 11th. Still looping Cyanogenmod logo.
Got home. Reflashed stock kernel. Went into recovery and flashed CM10 stable after wiping. Comes up with HTC logo, then black.
Tried to go back into recovery. Comes up with HTC logo, then goes black.
Now it lets me into fastboot, and into the bootloader menu, but recovery does not work. Neither does booting normally. Tried reflashing kernel AND recovery (stable TWRP). It just keeps looping the HTC logo.
HBOOT is 1.14.
Help, please. I'm going to destroy this piece of ****.

If all else fails, run a RUU and skip the thread.

yea, just ruu. i ruu'd a few days ago for kicks.
some car chargers and even wall chargers can make ur phone go wonky, my old moto backflip would randomly press buttons if i used a non-motorola charger.
on a side note, i never used the word "wonky" until this forum.
try running "fastboot erase cache"
also try a clean install instead of restoring nandroid, im assuming your also fastbooting the boot.img from all your nandroid backups. if not they probably wont boot.

strange...

I would say ruu and retry as well.. Sometimes accessories can make a phone go haywire.. Besides the phone is not a piece of crap.Roms can never give you complete stability while stock unrooted can.

Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.

Passa91 said:
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Click to expand...
Click to collapse
I always export my contact list to /sdcard if a change is made and then backup to google just in case

Passa91 said:
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Click to expand...
Click to collapse
I'd suggest keeping a boot.IMG and a stock ROM on the SD card along with adb drivers so you can fix it with a computer without downloading anything.
Sent from my Nexus 4 using xda premium

Problem (well kind of) after restoring a back up

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