Database Info

Well I think I bricked her...

I only installed the software cwm recovery (not nvflash), so I have no way out now. I haven't done anything serious except flash paul's patch and use titanium to uninstall some crapware like qik, that reader software, polaris office, etc.. nothing OS related, just apps. I also removed the GPS software, so I don't know what killed it exactly.
After removing those apps with TB, everything ran fine except I kept getting a force close from Qik... so I rebooted. Now it doesn't load and freezes on the LG screen with the loading bar not moving.
I don't know of any other options at this point...

Load up nvflash and get CWM on there so you can vol down + power into it. Then wipe data/cache and reboot.
You're not bricked even tho you think you are

GideonX said:
Load up nvflash and get CWM on there so you can vol down + power into it. Then wipe data/cache and reboot.
You're not bricked even tho you think you are
Click to expand...
Click to collapse
brick means HARDWARE LOCK or SOFTWARE LOCK
if your screen turns on at all... there is hope
fallow gideonx instructions... they have a nice tut set up for Nvflash
plus a one click type thing in the development section

I'm bricked for the time being until I can get home. I'm locked out of the device manager here at work, so I can't install the nvflash driver. Ignorant sons o'....
Sometimes I really hate the IT department.
Hopefully this is a warning to everyone else that if they want a custom recovery, they should bypass the rom manager option as it's too dangerious and just do the nvflash option.

For now nvflash is a better option instead of RM.

So I got home and used nvflash to put the latest cwm recovery on it. I wiped cache and rebooted... it shutdown the phone instead. So I manually turned it back on and it did the same thing.
So I did a full wipe and flashed a rom... and now it bootloops. I may very well have a bricked device after all.

Flashed which rom?
Here's a nandroid restore you can use:
http://forum.xda-developers.com/showthread.php?t=1048274

Eagles Blood since it was the fastest available.
The stock backup image is taking a long time thanks to the slow download. It's really irritating when all I can get on my 20mbps connection is 64KB/s.

antoniouslj said:
Eagles Blood since it was the fastest available.
The stock backup image is taking a long time thanks to the slow download. It's really irritating when all I can get on my 20mbps connection is 64KB/s.
Click to expand...
Click to collapse
I'd do the nandroid restore if I were you...

antoniouslj said:
Hopefully this is a warning to everyone else that if they want a custom recovery, they should bypass the rom manager option as it's too dangerious and just do the nvflash option.
Click to expand...
Click to collapse
noone will heed that warning lol.

Not a brick bro...just a minor bump in the road..you will get wiser from this..
G2X

fcisco13 said:
Not a brick bro...just a minor bump in the road..you will get wiser from this..
G2X
Click to expand...
Click to collapse
Actually it is completely gone now... seems like I have a defective device.
It won't boot into recovery or anything for that matter now, it just freezes at the first LG screen (the one without the progress bar). What's even weirder is I haven't really done anything to it... just installed and ran apps/games. I shut it down so I could install CM, but it won't boot into recovery or anything.
I tried redoing nvflash and it went fine, but it still won't boot into recovery.
This really sucks too... right on the eve of CM for this thing.

lost CWM, now CWM 3.0.0.8 is broke?

so, last night my phone was acting wierd... slow, battery was getting destroyed literally in an hour or two so i cleaned it up..
somehow i lost clockwork recovery... no flippin idea what happened, i never flashed or installed anything, but i went to do a backup and all i got was samsung recovery.
i did not lose root...
tried to install via rom manager and it said it worked... yeah whatever, that program is rubbish and ALWAYS says it worked...
anyways rebooted to a black screen but the capacitive buttons would light up if i touched them.
finally it installed but nothing worked and the phone locked up.
by the way rom manager installed CWM 3.0.0.8 (orange)
so now i had to completely blow out the phone, reroot, reinstall CWM (which worked the first time) but nothing is working in clockwork again.
back up.. nope says error backing up.. thats it
restore... nope, something about only having 8gb of space on my SDcard
i can wipe cache,, or so it seems.
but
if i wipe dalvik it locks the phone and i completely lose CWM again.
its acting like CWM is only temporary or something.
so what the heck.. i have never seen this before... ever.

I cant do anything with regards to bqcking up or restoring.
I cant.flash anything either even though rom manager boots to a portion of cwm which tries to flash a eom. But the phone just reboots.
Sent from my SCH-I500 using Tapatalk

Can't lie - Karma's a *****

Try going back to stock and starting over.

foxfire450 said:
Try going back to stock and starting over.
Click to expand...
Click to collapse
please be sure you read my post in its entirety and not bits and pieces.
i did finally get the latest CM7 installed and its running ok.
havent tried to do other things in CWM yet

akellar said:
Can't lie - Karma's a *****
Click to expand...
Click to collapse
you aint kidding...
but
its a phone, my life doesnt end if my phone goes to hell
just wierd, i have never lost clockwork before.

v_lestat said:
please be sure you read my post in its entirety and not bits and pieces.
Click to expand...
Click to collapse
In fairness, it's not immediately clear what you did after getting CWM Orange 3 installed---and really, ROM Manager should only ever be used on our phones if you're using the latest (CWM 4) on an MTD ROM.
That said: IF you think you need to do this (it sounds like if you got CM7 installed, you don't, but offering the advice all the same): take foxfire450's advice. Then do the entire process all over again. I've heard of people having issues with a lagfux or MTD removal unless they did the process twice. You might even consider the RFS Formatter if you're still having trouble.
Again though, that's all largely academic if you're running fine now. *shrug* Up to you to try if you think it's worth bothering at this point.

HELP

installed a custom rom = ''http://forum.xda-developers.com/showthread.php?t=1198684''
works fine , then installed "LeeDroid 3.1.0 Kernel "
and all of a sudden my phone just stays on HTC white and green screeen :/
dont know what to do tried installing other kernels but all have the same effect stays on HTC screen for minutes

give it al least 10 to 15 mins, before u jump to conclusion, it always takes a while when you first flash!
Just give it time,

ok ok thanks i will

Its been about 30 mins and still just the HTC screen CAN ANYONE help me!

It has been 16 minutes, not 30.
Be patient. Try reflashing if you can get to recovery.
Sent from my GT-I9100 using XDA App

Warchief337 said:
Its been about 30 mins and still just the HTC screen CAN ANYONE help me!
Click to expand...
Click to collapse
It's a bad flash or won't work on your device. Flashing a kernel with a speed to high for your CPU can do that, for example. Do a restore via recovery or try and flash a different version of that kernel or a different kernel.

no its been 30 i let it stay on that screen for a whole game of dota lol i just had it on my laptop while i played and it stayed white and HTC the entire time

oh ok ill try that , im new to the rooted phone scene was just using revolution hd but i like the insertcoin version better ill try another kernel

Firstly custom kernals dont work with sense 3.5 roms, that could be your problem, wipe everything in recovery, data wipe, factory reset, go to advanced and wipe dalvik cache, then just install the rom and see what happens, or else restore (assuming you made a backup)

ok so i wiped and reloaded rom and we are in business thanks everyone for your help DDDDD hahaha im releived

Warchief337 said:
ok so i wiped and reloaded rom and we are in business thanks everyone for your help DDDDD hahaha im releived
Click to expand...
Click to collapse
You will most likely run into it again in your flashing future (the stuck boot screen). It doesn't always require a full wipe or restore to fix. You could have most likely fixed it by flashing the kernel that came with the ROM.
The easiest thing you can do for yourself is to always make a nandroid backup before flashing anything, even a theme. Just remember to delete old backups you know you won't use, they take up a lot of sdcard space.

digiholic said:
You will most likely run into it again in your flashing future (the stuck boot screen). It doesn't always require a full wipe or restore to fix. You could have most likely fixed it by flashing the kernel that came with the ROM.
The easiest thing you can do for yourself is to always make a nandroid backup before flashing anything, even a theme. Just remember to delete old backups you know you won't use, they take up a lot of sdcard space.
Click to expand...
Click to collapse
thaey sure do take a lot of space. when I do an nandroid backup it always saves the rom with the date. can i rename it so I can keep them all straight? THis is a very NOOB question

[Resolved] [Q]AOKP boot loops after premature battery pull

I've had AOKP (can't remember which version..) installed for a while now and it's been acting funny, boot looping from time to time, but a simple battery pull fixed it each time.
Today I was turning off the phone to switch out the battery, and pulled out the battery before it had finished shutting down the "proper" way. Now when I turn it on, it gets stuck at "Initiating Swagger" with the pink unicorn. I've tried wiping the dalvik cache and formatting /cache.
I'd like to preserve some of the photos and texts, as well as all my apps which I, completely stupidly, didn't back up with Titanium Backup even though I've been meaning to for a little while now. I'm ready to reset and install a new rom if I have to, but I was wondering if there was a simple fix I'm overlooking since all I did was pull the battery out too early, rather than having done anything substantial like installing a new rom. Really appreciate any help, I've been phoneless all day and would love to not go through the motions of a whole new rom.
I JUST DON'T UNDERSTAND

Amb1valence said:
I've had AOKP (can't remember which version..) installed for a while now and it's been acting funny, boot looping from time to time, but a simple battery pull fixed it each time.
Today I was turning off the phone to switch out the battery, and pulled out the battery before it had finished shutting down the "proper" way. Now when I turn it on, it gets stuck at "Initiating Swagger" with the pink unicorn. I've tried wiping the dalvik cache and formatting /cache.
I'd like to preserve some of the photos and texts, as well as all my apps which I, completely stupidly, didn't back up with Titanium Backup even though I've been meaning to for a little while now. I'm ready to reset and install a new rom if I have to, but I was wondering if there was a simple fix I'm overlooking since all I did was pull the battery out too early, rather than having done anything substantial like installing a new rom. Really appreciate any help, I've been phoneless all day and would love to not go through the motions of a whole new rom.
I JUST DON'T UNDERSTAND
Click to expand...
Click to collapse
Looks like pulling the battery while it was shutting down corrupted some essential scripts on your device. So you have to flash a Rom to fix this. Dont worry coz there is something i do which can help you if you want to keep your apps n all. What you have to do is take a clockwork mod recovery backup right now. Then wipe everything including data,cache and dalvik cache. Now flash your Rom. If you want your apps n all then flash the same Rom you had. Now after it is flashed and working, boot to cwm recovery. select backup and restore then go for advanced restore. Select the backup you took. And restore data alone. This should make your phone look like it had never been flashed again with the Rom. Just like you had it before. And if even now the bootloop continues, do the same but first flash the kernel then Rom then do what i asked you to do. Hopes this helps...

Thanks man, that's a great idea, I didn't even think of that. Unfortunately I tried it, without and then with the kernel and it still didn't work.
What I ended up doing (for any of our posterior who happen upon this post) is installed the newest version of AOKP (which I actually didn't have previously), and downloaded an app called nandroid manager, which pulls apps/data, SMS messages, call logs, everything from any nandroid backup. I'm restoring all my stuff right now. Thank god.
Interestingly enough, even after I wiped everything multiple times, when I connected my phone to the computer it had all my photos & other data still on the internal storage. Weird as hell. But whatever.

Amb1valence said:
Thanks man, that's a great idea, I didn't even think of that. Unfortunately I tried it, without and then with the kernel and it still didn't work.
What I ended up doing (for any of our posterior who happen upon this post) is installed the newest version of AOKP (which I actually didn't have previously), and downloaded an app called nandroid manager, which pulls apps/data, SMS messages, call logs, everything from any nandroid backup. I'm restoring all my stuff right now. Thank god.
Interestingly enough, even after I wiped everything multiple times, when I connected my phone to the computer it had all my photos & other data still on the internal storage. Weird as hell. But whatever.
Click to expand...
Click to collapse
Thats pretty interesting.. I never tried AOKP so dunno much bout the way it works. Anyway happy for you man..

Amb1valence said:
Thanks man, that's a great idea, I didn't even think of that. Unfortunately I tried it, without and then with the kernel and it still didn't work.
What I ended up doing (for any of our posterior who happen upon this post) is installed the newest version of AOKP (which I actually didn't have previously), and downloaded an app called nandroid manager, which pulls apps/data, SMS messages, call logs, everything from any nandroid backup. I'm restoring all my stuff right now. Thank god.
Interestingly enough, even after I wiped everything multiple times, when I connected my phone to the computer it had all my photos & other data still on the internal storage. Weird as hell. But whatever.
Click to expand...
Click to collapse
That's because a wipe does not affect sd card or internal storage

brandonarev said:
That's because a wipe does not affect sd card or internal storage
Click to expand...
Click to collapse
Well.. It do affect internal memory on low phones. I am not sure bout devices having large internal storage but wiping data usually removes everything on my internal.

[SOLVED] Storage Space Running Out - 8GB Free

I just rooted my phone, restarted made sure it was working (not the first time I've rooted), then I installed a few zips, restarted my phone a couple times and it was all working fine. I then made a nandroid backup with TWRP, and restarted my phone and it's suddenly running really slow, and I have the constant message saying "Storage Space running out" even though I have over 8GB free. I even just restored my phone to this backup, but as I expected, same error. Any ideas?:crying:

Jimmeeehhhh said:
I just rooted my phone, restarted made sure it was working (not the first time I've rooted), then I installed a few zips, restarted my phone a couple times and it was all working fine. I then made a nandroid backup with TWRP, and restarted my phone and it's suddenly running really slow, and I have the constant message saying "Storage Space running out" even though I have over 8GB free. I even just restored my phone to this backup, but as I expected, same error. Any ideas?:crying:
Click to expand...
Click to collapse
Did you wipe /cache in TWRP?

beekay201 said:
Did you wipe /cache in TWRP?
Click to expand...
Click to collapse
Yup, had no effect at all.. I resorted to flashing the factory image and re-rooting and installing zips. Still interested in a fix for this though, on the small chance it happens again[emoji16]

Jimmeeehhhh said:
Yup, had no effect at all.. I resorted to flashing the factory image and re-rooting and installing zips. Still interested in a fix for this though, on the small chance it happens again[emoji16]
Click to expand...
Click to collapse
The next step I was going to suggest was to flash /system again. Some people posted wiping /cache was enough for them, but others had to reflash /system.

beekay201 said:
The next step I was going to suggest was to flash /system again. Some people posted wiping /cache was enough for them, but others had to reflash /system.
Click to expand...
Click to collapse
Ah that makes sense now that I think about it.. I flashed the entire image (boot, recovery etc.) but should have just done system, would have been quicker. Easy solution right there

Jimmeeehhhh said:
Ah that makes sense now that I think about it.. I flashed the entire image (boot, recovery etc.) but should have just done system, would have been quicker. Easy solution right there
Click to expand...
Click to collapse
Yep, glad it worked.
Could you please just add "[SOLVED]" to the thread title? Thanks