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

CM7 question

I just flash it like a normal ROM right? I mean flash the ROM w/ the kernel then flash the gapps.
Sent from my SCH-I500

Yes.......

Hows the battery life?
Sent from my SCH-I500

Good. Not the best ever for me but some people say it is amazing. Try for yourself.
Sent from my CM7 SCH-i500

Okay so if I want to go back to H57 can I just do a restore? And CM7 flashes CWM3 right?
Sent from my SCH-I500

I have tried to flash this several times with little luck guess I am missing something.
Currently I have Heinz_57.Hybrid_v5_7_11_OTB_edify and using the heinz57 custom blue cwm.
I flashed MESMERIZE Cyanogenmod 7 first and the proper GAPPS second. When I reboot the Android pops up and does nothing else I have waited five minutes no luck. I wind up having to reflash and go back to Heinz 57. I did wipe Data also noticed when flashing Cyanogenmod 7 it doesn’t give me the blue random words I get when flashing other kernels.
Please tell me what I am doing wrong.

I also did the exact same as the poster above me, from the same ROM and CWM custom blue recovery and have had no luck... I have also tryed about every other combination I can think of, with the same results. Which for me, is after reboot i get stuck on the samsung logo. I've let it run the course for over 10-15-mins with no change just for good measure but still nothing. I can flash and run ANY other rom so far besides cm7, including cm 7.0.3. So.. I'm verry baffled atm myself..

I'm am in no way sure about this since i have not flashed cm7 but you may have to odin froyo and start from scratch, i had this problem with another rom and my best guess is it was do the the kernel that was installed was not the correct one. Another thing to try is a wipe and install a non-vodoo aosp kernel reboot recovery and then try to flash zip again

Jack off. That helps.

Load an soap kernal first then flash cm7 and gapps. I don't know why this works but its what I have to do every time I load cm7.
Sent from my SCH-I500 using XDA Premium App

wired-turtle said:
Load an soap kernal first then flash cm7 and gapps. I don't know why this works but its what I have to do every time I load cm7.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
cm7 has the kernel built in, you shouldn't need to flash one separately.
Sent from my CM7 SCH-i500

sageDieu said:
cm7 has the kernel built in, you shouldn't need to flash one separately.
Sent from my CM7 SCH-i500
Click to expand...
Click to collapse
Yeah that's what many of us assumed. Unfortunately that doesn't appear to be the case as we learned. There were a number of us that ended in boot loops or frozen on the splash screen if you just flash the rom and gapps.

Sorry for jacking this thread but which recovery allows you to do a legit nand? The otb gives me a boot img error and ti's makes 3 separate on CM7? I thought I solved all my nand problems before I flashed this by doing bdemartinos posted fix.
Sent from my SCH-I500 using XDA App

Nandroid never works for me... what am I doing wrong?

Ok. So ever since I've had this device it's been rooted and as such, i've tried a number of roms. The problem is whenever I start with a rom I really enjoy (currently the stock one... go figure) then i do a nandroid back up.. try a new one.. to find some glaring shortcoming i just have to have (a2dp) and try to restore my nandroid. On my G2 this process was absolutely seamless!
What happens is i restore nandroid... but it doesn't restore my apps... all the space is definitely gone.. like they're in teh file system and cards... but they don't show up in teh launcher and my wallpaper is back to stock... just as if i had a stock device.
Any ideas?

btate0121 said:
Ok. So ever since I've had this device it's been rooted and as such, i've tried a number of roms. The problem is whenever I start with a rom I really enjoy (currently the stock one... go figure) then i do a nandroid back up.. try a new one.. to find some glaring shortcoming i just have to have (a2dp) and try to restore my nandroid. On my G2 this process was absolutely seamless!
What happens is i restore nandroid... but it doesn't restore my apps... all the space is definitely gone.. like they're in teh file system and cards... but they don't show up in teh launcher and my wallpaper is back to stock... just as if i had a stock device.
Any ideas?
Click to expand...
Click to collapse
Does this happens with all your nandroids or only one specifically?
Sent From My G2x Running CM7 Nightly 70

So far... none of them have worked. however... they all happen to be backups of the stock rom.. don't think I've ever tried restoring any other rom.

btate0121 said:
So far... none of them have worked. however... they all happen to be backups of the stock rom.. don't think I've ever tried restoring any other rom.
Click to expand...
Click to collapse
What version of CWM are you using?
Sent From My G2x Running CM7 Nightly 70

Are you initiating the backups thru rom manager or directly from recovery? If you're initiating them from rom manager try booting directly into recovery and then making a backup.

I'm using 3.0.2.7 (the one that rom manager tells me to use). but i always backup while booting directly into CWRM because as we all know... Rom Manager doesn't see the external SD but CWRM does.

I would reflash CWM again.
Do a Nandroid, put it in the sd card and try restoring again.
Sent From My G2x Running CM7 Nightly 70

I think your problem is that you're using rom manager. Try doing it the real way (nvflash).
Rom manager is great on phones in which it doesn't use fakeflash, but I would stay away from the program on phones in which it utilizes fakeflash.
Sent from my LG-P999

diablos991 said:
I think your problem is that you're using rom manager. Try doing it the real way (nvflash).
Rom manager is great on phones in which it doesn't use fakeflash, but I would stay away from the program on phones in which it utilizes fakeflash.
Sent from my LG-P999
Click to expand...
Click to collapse
you may be the winning response.... i've been using rom manager to flash my CWRM.... I shall give that a go post haste.
Thank you all for your help! This forum is awesome!

ok... nvflashed my cwrm again... no go.. still nothing with the recovery.

You should be using CW 3.1.0.1

prettyboy85712 said:
You should be using CW 3.1.0.1
Click to expand...
Click to collapse
May the Lord make His face to shine upon you....
thank you.

prettyboy85712 said:
You should be using CW 3.1.0.1
Click to expand...
Click to collapse
Just curious why that is? I use 3.0.2.7 and have no issues whatsoever.

btate0121 said:
May the Lord make His face to shine upon you....
thank you.
Click to expand...
Click to collapse
Always a relief to get something working lol. Glad you got it working.

G2x in Recovery Bootloop

Ok Here is what I did:
First I flashed temesak's unofficial CM7 bulid then I couldn't access my sd card so I went to flash another rom (Hellfire's 7.2 super tweaked)
Recovery Used : CWM 5.8 Touch (Experimental)
I flashed and then I tried to reboot and then. *BOOM* Right back to the recovery screen. I tried a few more time but with the same outcome
I flashed a couple other roms like Eagle's Blood 2.3 and Weapon G2x but still had the same problem
Thinking it was my recovery I flash the 5.2 CWM and problems still there. Then I flash back a stock backup and a stock recovery thinking I just go back to stock to solve problem. NOPE i'm looking at a box with an arrow pointing at an Android.
I'm thinking I messed with something in the phone and now the command to set to boot normally is replaced with a command to boot into recovery.
Or
My volume down button is stuck but, that's unlikely considering I can use the recoveries just fine and flash roms, wipe dalvik everything too
Please help I bought this phone off of craigslist and been having trouble with it since day one (Unrelated to the seller) just general problems with LG

Try the G2x batch cleanup tool in the dev section. Sounds like your partitions may have been messed up. And stick with CWM 5.2
Sent from my LG-P999 using xda premium

IT WORKED PERFECTLY! It's Exactly what I needed. Not only did it fix my bootloop problem, I can now access my USB storage without a SD Card reader. Thanks Bro, And thank you mansa_noob (G2x Batch Cleanup Tool)

Odogray said:
IT WORKED PERFECTLY! It's Exactly what I needed. Not only did it fix my bootloop problem, I can now access my USB storage without a SD Card reader. Thanks Bro, And thank you mansa_noob (G2x Batch Cleanup Tool)
Click to expand...
Click to collapse
Glad it worked!
Sent from my LG-P999 using xda premium

Same Problem.
I have a same problem, also wanna add that every time I connect my phone too a charger it turns on by itself, and boots to CWM Recovery.
I tried using Batch Cleanup Tool but still having same issues. Please HELP!!! I cannot afford a new phone right now.
Thanks in advance for any suggestions.

Nata, what rom are you using? Try flashing something else
Sent from my LG-P999 using xda app-developers app

Flash Kernel

So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.

Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
I see that I have the Cyanogenmod Kernel installed currently which I suppose either is installed with Slimbean or it may have been installed because I tried the CM10 rom first, but it wouldn't boot.

what are you doing before flash the new rom?

juancaperez2000 said:
what are you doing before flash the new rom?
Click to expand...
Click to collapse
Wiping the device. Always best in the long run.
Sent from my Nokia RinGo far far away...

Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.

Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
Restore your stock rom format internal memory and flash clean rom ASAP brother you will be straight !!!
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 05:45 PM ---------- Previous post was at 05:44 PM ----------
And all the necessary wipes of course
Sent from my SCH-I535 using xda app-developers app

Cobinator said:
Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.
Click to expand...
Click to collapse
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash

andybones said:
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash
Click to expand...
Click to collapse
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.

Cobinator said:
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.
Click to expand...
Click to collapse
in theory AOSP ROMs should load faster than a Touch Wiz ROM as TW ROMs are around 1 gig for the ROM.zip and AOSP ROMs are about half that, but still I've had ROMs take over 15 mins to load, I know one time I thought it was the phone, but then I wiped fully again, and waited 20 mins and it loaded. I would say anything after 20 mins though, then it's definitely something wrong.

Ok backing stuff up then going to flash back to stock then try LiquidSmooth and see if it will let me boot up. Will let ya know how it goes.

So I install stock un-rooted rom. Then installed a stock rooted rom, then installed liquidsmooth and all I get is the Samsung symbol flashes then it goes black. Then it vibrates and the Samsung symbol flashes then blackness. Just repeats this over and over =(

I noticed you said that you're wiping cache and dalvik, but make sure you're also wiping data and system too.
Sent from my SCH-I535 using xda premium

Please read forum rules before posting
Questions and help issues go in Q&A and help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

My apologies moderator.
Anyways. I wiped everything on the phone before every rom installation. System restore, dalvik, and cache. The custom rom still won't boot.