As the title says I recently flashed aospX rom and now I'm stuck on the loading screen, I've already tried waiting for over 30 minutes and still no joy. Really worried that I broke my phone for good. Any advice on how I can make my phone work again ?
It ain't broke.
Cellphone off. Press and hold the down volume button + power button. Go into recovery. Wipe everything that can be wiped except sd card. Find where you have your backup and flash that, if you don't have it flash existz rom again. When you are finished, read how to flash roms, what you have to wipe before doing it again.
Sent from a dream.
Teichopsia said:
It ain't broke.
Cellphone off. Press and hold the down volume button + power button. Go into recovery. Wipe everything that can be wiped except sd card. Find where you have your backup and flash that, if you don't have it flash existz rom again. When you are finished, read how to flash roms, what you have to wipe before doing it again.
Sent from a dream.
Click to expand...
Click to collapse
As you can tell I'm new to this, thanks for tip flashing after wiping worked like a dream ! I read that I should do this but totally forgot when I actually started the process.
razten said:
As you can tell I'm new to this, thanks for tip flashing after wiping worked like a dream ! I read that I should do this but totally forgot when I actually started the process.
Click to expand...
Click to collapse
No worries. I know what it feels like when one starts out. Just remember to back up before flashing.
Sent from a dream.
Related
I had rooted my phone a week ago and running the standard rom. Everything was fine but I wanted to try a ROM. Last night I tried CM7 and it installed but I forgot to get the gapps. I restored my backup and it was back to the way it was. Then I again used Rom Manager and this time chose to download CM7 & gapps. It worked, then I went onto the market and downloaded Titaninum backup because I couldn't find it. I set it up and restored all apps with data. BTW I had 200+ to go thru so if this isn't bricked I'm purchasing the PRO version. After I went thru all the apps, I rebooted and the screen is stuck at the cyanogen mod 7 screen with the arrow going around. It was like that for over an hour so I took out the battery and tried it again. Same thing, so I decided I'd go into hboot and restore my old backup. I took out the battery again and held down the power and vol down but nothing except a vibrate happened. I can still turn it on to the cyanogen screen but can't seen to hboot. What do I do???
Update: I pulled the battery and tried holding down the volume up and the power button but nothing happens except it vibrates. I can still hit the power and get to the cyanogen screen but it just spins. If I plug in the power the small power light comes on but doesn't stay on when I'm trying to get to hboot. Please tell me it's not bricked!!!
not sure if its bricked, but from what i do know, you never, ever restore data when you change roms. there has to be a way to get into hboot or recovery, im just not the guy who knows, but someone will tell you. if it goes to the cyanogen mod, which is a great rom, then your not bricked
BUMP,
Please someone tell me there is hope for my Droid Incredible? I was sure I followed the steps, My wife will kill me if this is bricked....
U might have to return completely back to stock by using ruu.
Dinc
Try " the ultimate get back to stock" thread, remember, dont restore data
Sent from my Incredible using XDA App
You're doing it wrong. Volume down + pwr is hboot.
Thank you for the help
I guess I was getting to hboot wrong. I was holding down the volume down and the power button and keeping them down. m6droid told me to hold the volumn down button then press and hold the power button for about 2 second and let go of the power button while continuing to hold down the volume down button.
It loaded hboot and I went to recovery. Man was that scary.
I was so nervous when I rooted my phone so I made sure I read every step. I'm going to have to read a lot more about flashing ROMs before I try that again.
Thanks for taking the time to reply
djgdroid said:
Thank you for the help
I guess I was getting to hboot wrong. I was holding down the volume down and the power button and keeping them down. m6droid told me to hold the volumn down button then press and hold the power button for about 2 second and let go of the power button while continuing to hold down the volume down button.
It loaded hboot and I went to recovery. Man was that scary.
I was so nervous when I rooted my phone so I made sure I read every step. I'm going to have to read a lot more about flashing ROMs before I try that again.
Thanks for taking the time to reply
Click to expand...
Click to collapse
You did everything fine, except for restoring data :/. That, and the getting into hboot technique lol. I'm glad its up and running now.
Sent from my Droid Incredible running Myn's Warm TwoPointTwo RLS5.3.
Why do I feel a need for a special degree to root my dinc and add new rom's
Sniperdog said:
Why do I feel a need for a special degree to root my dinc and add new rom's
Click to expand...
Click to collapse
Cuz you're getting freaked out for no reason. It's super easy and even when you mess up you can fix it, it just takes research. I thought I bricked my phone a couple times already and I always get it back with effort and research. Fear is the mindkiller.
Sniperdog said:
Why do I feel a need for a special degree to root my dinc and add new rom's
Click to expand...
Click to collapse
Its easy; things start to make sense after a while.
phaze one said:
Cuz you're getting freaked out for no reason. It's super easy and even when you mess up you can fix it, it just takes research. I thought I bricked my phone a couple times already and I always get it back with effort and research. Fear is the mindkiller.
Click to expand...
Click to collapse
Fear is the mindkiller. Good one.
Sent from my DINC using XDA Premium
wildstang83 said:
Fear is the mindkiller. Good one.
Sent from my DINC using XDA Premium
Click to expand...
Click to collapse
Dune ftw.
sent by carrier pigeon
Yeah hey,
So I was running Trinity kernel and noticed a lot of random system freezes and so I reverted back to stock kernel through this thread I just made. I flashed the 4.1.1 stock kernel zip over the trinity kernel.
My phone got stuck in Boot Screen (Didn't see a boot loop, just stuck there while the Animation plays for infinite time) I took the battery out, then rebooted... same thing.. So I was gonna wipe and reinstall the whole thing through recovery (CWM), I pulled the battery, held Power + Vol down.. I was expecting recovery, but then I saw a Fastboot screen ("Odin Mode" as labelled in the top left corner) with only one single option ("START") and a label that says "Downloading..."Then system info ("Tuna" and the other stuff)
Now MY MAIN QUESTION:
Did I lose my CWM recovery system restore zip?? The one in the virtual "SD" Card?! PLEASE SAY I DIDN'T!!!
Now second question, how do I get things back to normal?? :crying:
Vol up + vol down + power :highfive:
Then use the volume key to select Recovery
CMNein said:
Vol up + vol down + power :highfive:
Then use the volume key to select Recovery
Click to expand...
Click to collapse
Oh, Thanks.
Just tried that and DID get recovery as an option, clicked it, and just *poof*... Nothing happened..
I think the battery was 11% when it all started so I'll give it 30 minute and try again. And update this accordingly.
If you were referring to your clockworkmod folder in the first post, would be wise to pull it via adb in case you have to completely wipe your phone.
CMNein said:
If you were referring to your clockworkmod folder in the first post, would be wise to pull it via adb in case you have to completely wipe your phone.
Click to expand...
Click to collapse
Could you please guide me to somewhere where this method is explained? I really want to pull that file any way possible.
I'm not the best in using adb..
But I'm now about to install Win7 or Linux to be able to use adb.
This is probably the easiest to follow initially: http://forum.xda-developers.com/showthread.php?t=1058431
If in doubt there are dozens of other adb guides/tutorials on XDA and elsewhere. Just take your time.
CMNein said:
This is probably the easiest to follow initially: http://forum.xda-developers.com/showthread.php?t=1058431
If in doubt there are dozens of other adb guides/tutorials on XDA and elsewhere. Just take your time.
Click to expand...
Click to collapse
Thank you for the help. Recovery just worked and my restore file is still there.. So I'll try reflashing and if it failed I'll wipe and reflash.
I can manage on my own when recovery in intact.
Thank you -and people like you- for making this forum such an amazing place.
Got myself into a weird sitch, and don't know how to get out. Any help would be appreciated.
Have TWRP. Was going to flash a ROM
Took these steps
Boot into recovery
Wipe data/factory reset, wipe cache, and wipe dalvik cache, select Wipe then System
Here's where things went fail.
I was goofing around and went to mount and put a check next to system, and tried rebooting my phone.
Naturally it just hung there because there is nothing to boot up to. I was expecting that.
But... When I try to get back into recovery to continue I suddenly cannot get back into recovery.
I hit the correct key combonation, get the team win screen like its going into recovery and then it just vibrates and reboots again.
I am holding up+home+power, when i see that it is going into recovery I let go of power but continue to hold up and home. (Also have tried letting go of up and home).
Thanks.
Can you boot into download? Just as a test, your power button might be sticking
Making the iPhone jealous one user at a time.
mkfryan said:
Can you boot into download? Just as a test, your power button might be sticking
Making the iPhone jealous one user at a time.
Click to expand...
Click to collapse
Yes I can boot into download.
Forgot to mention, I tried reflashing TWRP through Odin, it was successful, but still same results. I guess I could try flashing CWM...
eff it, i flashed stock firmware. g2g
manther said:
eff it, i flashed stock firmware. g2g
Click to expand...
Click to collapse
When you say "g2g" do you mean "got 2 go" or "good 2 go"
I really hope everything worked out.
Unfortunately, I figured that would be the route you would have to go reroot and let the customization begin again! Good luck this time around
Making the iPhone jealous one user at a time.
yeah "good to go"
Thanks. Its kinda nice to go back to stock for a change of pace. Might actually keep it this way for a week or so.
So I rooted my LG Optimus G and wanted to download a new rom to try it out and heard that Cyanogenmod was pretty good. So I downloaded it and extracted it and tried to boot it from recovery on my phone. The problem though is that when it goes to boot up it just shows the cyanogenmod logo and the blue circle spinning. From what I understand it's most likely because I didn't restore to factory settings before hand. So I was wondering whether there's anything that I can do to try and fix it or whether I just got a new paperweight?
justsomedude23 said:
So I rooted my LG Optimus G and wanted to download a new rom to try it out and heard that Cyanogenmod was pretty good. So I downloaded it and extracted it and tried to boot it from recovery on my phone. The problem though is that when it goes to boot up it just shows the cyanogenmod logo and the blue circle spinning. From what I understand it's most likely because I didn't restore to factory settings before hand. So I was wondering whether there's anything that I can do to try and fix it or whether I just got a new paperweight?
Click to expand...
Click to collapse
Did you wipe data, system, dalvik and cache? Actually what recovery are you using? If it's TWRP, go to wipe and then advanced and wipe everything EXCEPT internal storage(data, system, dalvik, cache) then reinstall the rom and gapps. CWM(clockworkmod) is different and I haven't used it in awhile, but usually bootloops are because you didnt wipe atleast dalvik and cache(the factory reset in TWRP), but I usually wipe everything. Just not internal because that is where your files(and rom) reside.
If that doesnt work, you can try a different rom and use adb sideload from a pc. There are plenty of tutorials for that here on xda if you do a search.
But if its loading to the CM logo, it is not a paperweight. Worst case scenario you can use LGNPST and a stock bin file to go completely back to stock. But as long as you can get into recovery you shouldn't have to go to those lengths.
Hope this helps.
EDIT: I know it's your phone and if you are like me, it's probably your only phone. But don't panic, real bricks are rare and if you can get back into recovery you are usually fine!
HPTesla said:
Did you wipe data, system, dalvik and cache? Actually what recovery are you using? If it's TWRP, go to wipe and then advanced and wipe everything EXCEPT internal storage(data, system, dalvik, cache) then reinstall the rom and gapps. CWM is different and I haven't used it in awhile, but usually bootloops are because you didnt wipe atleast dalvik and cache, but I usually wipe everything. Just not internal because that is where your files(and rom) reside.
If that doesnt work, you can try a different rom and use adb sideload from a pc. There are plenty of tutorials for that here on xda if you do a search. Hope this helps.
Click to expand...
Click to collapse
No I did not, at the time apparently I wasn't thinking. I was using clockworkmod, but whenever I try and use adb on my pc it doesn't detect my phone anymore either. Rebooting it manually also doesn't work either since it just goes back to the loop cycle, I'll definitely look into sideloading though.
justsomedude23 said:
No I did not, at the time apparently I wasn't thinking. I was using clockworkmod, but whenever I try and use adb on my pc it doesn't detect my phone anymore either. Rebooting it manually also doesn't work either since it just goes back to the loop cycle, I'll definitely look into sideloading though.
Click to expand...
Click to collapse
Power your phone off completely, then hold the volume up button while you power it on. Once it loads, hit volume down twice then the power button to get back into recovery. Wipe dalvik and cache and reinstall cm and gapps. You should be ok after that.
I also added some edits to my first post. Again I use TWRP which has an adb sideload option under advanced settings......not sure about CWM. But this guide here is a great resource for our phone and has a lot of helpful links.
HPTesla said:
Power your phone off completely, then hold the volume up button while you power it on. Once it loads, hit volume down twice then the power button to get back into recovery. Wipe dalvik and cache and reinstall cm and gapps. You should be ok after that.
I also added some edits to my first post. Again I use TWRP which has an adb sideload option under advanced settings......not sure about CWM. But this guide here is a great resource for our phone and has a lot of helpful links.
Click to expand...
Click to collapse
Whenever I try and turn the power off, it automatically reboots itself back into the loop. That also happens whenever I try and put it into recovery mode so I can't delete anything. Would going through the annoying process of removing my battery potentially help with that?
I also don't know whether LNGPST would be able to help because if the normal manual commands such as the power down function don't work, then I probably won't be able to enter into download mode to use LGNPST.
On a side note, I really appreciate your help, but even if all else fails, I do have another phone I could use but it's old so I'd rather avoid that.
justsomedude23 said:
Whenever I try and turn the power off, it automatically reboots itself back into the loop. That also happens whenever I try and put it into recovery mode so I can't delete anything. Would going through the annoying process of removing my battery potentially help with that?
I also don't know whether LNGPST would be able to help because if the normal manual commands such as the power down function don't work, then I probably won't be able to enter into download mode to use LGNPST.
On a side note, I really appreciate your help, but even if all else fails, I do have another phone I could use but it's old so I'd rather avoid that.
Click to expand...
Click to collapse
How long have you held the power button in? For me sometimes its 20 seconds but Ive heard as long as a full minute. If you hold the power button down until the screen turns off, and it comes right back on try holding it for a minute straight and let it go. If not, you may have to do the battery pull which is a pain in the a**. But Ive had that power down, turn right back on and into the bootloop myself, holding the power button for a solid 20 count solved it - but again it may be longer. And you're welcome, Im here to help - one thing you will learn about fellow lgog users if you get that phone working again - lots of support!
EDIT: Also, if you do get it to power down and then are able to get into recovery - plug it into the wall. Wait until you get into recovery to do it - but if its been on this whole time your battery might be low and you dont want lithium batteries to drain completely. It shortens their lifespans.
HPTesla said:
How long have you held the power button in? For me sometimes its 20 seconds but Ive heard as long as a full minute. If you hold the power button down until the screen turns off, and it comes right back on try holding it for a minute straight and let it go. If not, you may have to do the battery pull which is a pain in the a**. But Ive had that power down, turn right back on and into the bootloop myself, holding the power button for a solid 20 count solved it - but again it may be longer. And you're welcome, Im here to help - one thing you will learn about fellow lgog users if you get that phone working again - lots of support!
EDIT: Also, if you do get it to power down and then are able to get into recovery - plug it into the wall. Wait until you get into recovery to do it - but if its been on this whole time your battery might be low and you dont want lithium batteries to drain completely. It shortens their lifespans.
Click to expand...
Click to collapse
Holding it for 20 seconds worked and from there I was able to put it into recovery. Thank you for all the help, if not for you I probably would've tried to remove the back and probably just break it even worse
justsomedude23 said:
Holding it for 20 seconds worked and from there I was able to put it into recovery. Thank you for all the help, if not for you I probably would've tried to remove the back and probably just break it even worse
Click to expand...
Click to collapse
Good stuff man, glad to hear it and you're welcome!
Well, i wanted to restore my backed up rom, i went to twrp and restored the rom without wiping data, dalvik cache ect. it went to boot loop saying " setup wizard stopped " after reaching lockscreen and went booting again.. then i found a way to go to recovery again, i wiped the cache and stuff and restored the same back up and the same problem now no change, now i cant go inside custom recovery whatever i try.. :/ . will i be able to go to recovery after the battery is drained?
or u know a method to go inside recovery?
Have you tried holding the volume down button down when the screen goes blank? This will get you into the bootloader. You can also hold power and volume up and when the screen goes blank hold volume down only.
Magnum_Enforcer said:
Have you tried holding the volume down button down when the screen goes blank? This will get you into the bootloader. You can also hold power and volume up and when the screen goes blank hold volume down only.
Click to expand...
Click to collapse
the screen dosent go blank when i press volume up and power it goes to HTC POWERED BY ANDROID screen and starts booting :/
live16 said:
the screen dosent go blank when i press volume up and power it goes to HTC POWERED BY ANDROID screen and starts booting :/
Click to expand...
Click to collapse
How long did you hold it for? You have to hold the buttons for a good ten seconds or so. You're saying the screen never goes black for a few seconds between loops?
Magnum_Enforcer said:
How long did you hold it for? You have to hold the buttons for a good ten seconds or so. You're saying the screen never goes black for a few seconds between loops?
Click to expand...
Click to collapse
thank u, it worked but now when i flash there is no on screen buttons and notifications at all and im stuck with 1 rom :/
the computer does not recognize my device as "on" itself!!
what to do plz help
Connect SD card reader to your computer and use it to put a ROM on removable SD. Insert the SD into the phone, and flash the ROM from recovery.
I also just came over this problem,
I've been using TWRP on all my phones for years and constantly flashing/restoring various roms.
Did I do something wrong?
I backed up using the default options and restored the same way as I always do but I had the same issue.
Roshi69 said:
I also just came over this problem,
I've been using TWRP on all my phones for years and constantly flashing/restoring various roms.
Did I do something wrong?
I backed up using the default options and restored the same way as I always do but I had the same issue.
Click to expand...
Click to collapse
Make sure you firmware corresponds to the nandroid you are trying to restore.
But if they do match (correct firmware for the ROM being restored) it might just be a random thing. TWRP on this (and other recent devices like my Sammy Galaxy Tab Pro 8.4) seems a little less reliable than in the past. As long as your TWRP version is up to date, there isn't much else you can do. Except maybe keep a few different nandroids (probably on your computer, since they take so much space) in case the most recent one doesn't restore correctly.
Thanks for the reply. I also tried installing the exact same ROM again and set it up, then tried to restore but still the same problem. Thanks anyway I'll maybe try another backup and delete the old one. Thanks again
If you're restoring a ROM through the TWRP restore function make sure you always wipe always wipe data and system before restoring unless you're only restoring data or just system itself. Then only wipe that certain parition. But never restore a backup of another ROM base onto a different base without installing the ROM you are restoring first. That will cause a lot of issues, constant FC, and bootloop.