Ok, I have been rooting etc. since the d1, but I think I have really messed up this time.
I flashed an incompatable theme over gummy 1.8.1 and everything started forceclosing. Well, I thought no big deal, cause I still have Odin, or cwm to help me fix this. So I decided to disable lagfix before flashing anything new, and of course when the phone booted back up, everything was still fc'ing so I took the battery out and now i can't get to cwm or odin. The phone won't go into download mode, What can I do Now.
I am totally against taking my phone back for something I did, Please Help me!!
EDIT:
Sorry, kinda freaked out too early, I was holding down the volume up button instead of the volume down (what a dummy) Now let's see if I can this thing going again.
Are you recovered?
jsminnis said:
Ok, I have been rooting etc. since the d1, but I think I have really messed up this time.
I flashed an incompatable theme over gummy 1.8.1 and everything started forceclosing. Well, I thought no big deal, cause I still have Odin, or cwm to help me fix this. So I decided to disable lagfix before flashing anything new, and of course when the phone booted back up, everything was still fc'ing so I took the battery out and now i can't get to cwm or odin. The phone won't go into download mode, What can I do Now.
I am totally against taking my phone back for something I did, Please Help me!!
EDIT:
Sorry, kinda freaked out too early, I was holding down the volume up button instead of the volume down (what a dummy) Now let's see if I can this thing going again.
Click to expand...
Click to collapse
go here>>>>
http://forum.xda-developers.com/showthread.php?t=1137917&page=2
Look at post 19...worked like a charm!
UPDATE: Sorry I didn't post back sooner, Yes I recovered my phone by flashing the ee4.tar I found in a thread by imnutz. So for now Im running stock with the blue honeycomb theme, Rooted of course, but all is good.
Related
Hey all
Before anyone mentions that i should be searching around more, i would like to say that i've been on multiple threads and they all state the same thing (use NVflash to flash CWM and then boot into CWM but the solution did not work for me past flashing CWM and then trying to access recovery after) and i wasn't able to find one that had a similar problem as mine.
I have CWM flashed through NVflash and was running CM7.1 RC1. I took a screenshot with the 'shootme' app and proceeded to look at the gallery to make sure it came out okay. The gallery crashed and i was sent to the home screen. I swiped to a different homescreen when my phone froze halfway through the transition to the next screen. No combination of buttons/long presses were able to get me out of it so i went ahead and did a battery pull. So my dilemma is that now i'm stuck at the LG boot logo with no blue status bar under it. It freezes there and will not do anything every time i boot up. volume down+power does not give me access to recovery nor does any other button combo get me past the LG boot logo.
Are there any other methods i might be able to use like ADB or what not to get myself out of this situation? or at least into recovery? Any comments or suggestions would be greatly appreciated as i've been searching for hours with little help and my eyes are starting to get strained.
hmmm.. I know it's a simple question, but I gotta ask.. are you holding the pwr and volume down button long enough? you have to keep holding it even after you see the LG screen.. Keep holding until you see the 2nd screen?
If so.. do the nvflash again? Edit: Not sure if I would do this without getting further guidance tho..
schmit said:
hmmm.. I know it's a simple question, but I gotta ask.. are you holding the pwr and volume down button long enough? you have to keep holding it even after you see the LG screen.. Keep holding until you see the 2nd screen?
Click to expand...
Click to collapse
This. I remember when I boot looped my phone I had the problem of letting go of the volume key too early, you need to hold down volume and power from a totally powered off phone until recovery actually starts and you see the green "android" logo of CWM.
Try re-flashing CWM, NVFlash CAN fail. There is literally nothing you can do within the OS that will prevent recovery from working. Either you did something wrong somewhere along the recovery process or you discovered an entirely new problem with the phone. I'm going to hazard a guess and say it's the former.
Thanks for the response guys. I wish that it was the case of not holding the buttons long enough. I have tried numerous times with the buttons held down for a long period of time. I even held the combo down for almost 5 minutes a few times.
Every time i try to boot up, it won't go past the LG boot screen so i would pull the battery out and go through flashing CWM through NVflash again. I'm sure I'm not missing anything because everything goes through and gets sent to the phone successfully.
I did happen to run into a thread that was closely similar to mine but his method was to just keep reflashing CWM and the stock recovery back and forth every time it failed until it turned on. I might have to try that if i cannot figure out this problem out soon. Not being able to use this phone is killing me! heh.
I just joined your club. Wow this sucks.
So apparently this is a whole new problem that's been found? Every other help thread seems to point to using NVflash or remaking the partitions due to a bad flash using an O2x based file instead of G2x.
But none of those solutions come close to doing anything. There has been some people with the same problem as me but aren't proactive at all enough to get someone's attention, so i'm guessing this problem is getting pushed to the side with people just going about getting their phones replaces/buying new ones.
I did happen to run into a thread on paulobrien/modaco's forum that had people using NVflash to get out of any sticky situation like this. It just reverts everything back to the stock factory settings but with root. We cannot use this though because he hasn't built it to be compatible with our LGP999's because everything was built for their UK LGP990's. Maybe that's a start to getting this solution fixed?
I hate to say this, bit you might have to call t mobile and get a replacement. Flash back to stock recovery and they won't know you messed with anything.
Sent from my Nexus 5g using XDA Ultimate App
Don't send back....you'll get same defacement a battery pull go into nvflah and go back stock then flash nv flash fix pArtitions
As I have mentioned before, NVflash does NOT give me access to my recovery let alone solve anything else. NVflash DOES work and does sucessfully send both CWM and the stock recovery but when I try to boot into either of them, let alone just power on normally, it simply DOES NOT go past the LG boot screen. it just hangs there doing nothing at all until I pull the battery out and do the same process over until it just hangs again.
while it is on/stuck at the LG screen, my computer does not recognize it so i cannot even try and run ADB commands. It does however, recognize it when I plug it in using the volume buttons held down when I use NVflash but there's nothing else I can do besides use NVflash obviously.
Jduhb said:
As I have mentioned before, NVflash does NOT give me access to my recovery let alone solve anything else. NVflash DOES work and does sucessfully send both CWM and the stock recovery but when I try to boot into either of them, let alone just power on normally, it simply DOES NOT go past the LG boot screen. it just hangs there doing nothing at all until I pull the battery out and do the same process over until it just hangs again.
while it is on/stuck at the LG screen, my computer does not recognize it so i cannot even try and run ADB commands. It does however, recognize it when I plug it in using the volume buttons held down when I use NVflash but there's nothing else I can do besides use NVflash obviously.
Click to expand...
Click to collapse
Did you ever find a solution to this issue? Because my phone is doing this...
I attempted to restore my phone back to the wrong backup that was from a galaxy sII (2.3.4 i think); needless to say, the restore failed. I then restarted my phone from CWM and it gets stuck at LG screen.
I have tried to NVflash back to stock; nothing. same thing reflashing back to CWM.
ideas?
have you tried this link out yet?
http://forum.xda-developers.com/showthread.php?t=1180331
same problem..... anybody find something to fix this yet?
From what I heard is that you need to remove the battery, then boot into recovery or something.
Sent from my G2X
Use smartflash for the p990 but only use the p999 ap.bin file which will put the rom and kernel back to stock p999.
Rom for recovery always fixes any soft brick back to stock 2.3.3 OTA. It's saved my phone multiple times from stuck on S/W screen to being stuck on lg logo or even the dreaded can't mount sdcard-cache errors in cwm.
Sent from my LG-P999 using xda premium
I used the following method when Clockworkmod became corrupted and was unable to mount my sd card. I had just wiped everything on my phone intending to install a new rom when the issue happened. I could not even get to the S/W upgrade screen. It saved my phone. Hope it works for you.
http://forum.xda-developers.com/showthread.php?p=17258229
jcbofkc said:
I used the following method when Clockworkmod became corrupted and was unable to mount my sd card. I had just wiped everything on my phone intending to install a new rom when the issue happened. I could not even get to the S/W upgrade screen. It saved my phone. Hope it works for you.
http://forum.xda-developers.com/showthread.php?p=17258229
Click to expand...
Click to collapse
omg thank you so much! It worked! Not only that but i was stuck on frodo 2.2.2 before which is why i was messing with my phone in the first place and now its on gingerbread. Awesome! thank you!!!!
sabotage99 said:
omg thank you so much! It worked! Not only that but i was stuck on frodo 2.2.2 before which is why i was messing with my phone in the first place and now its on gingerbread. Awesome! thank you!!!!
Click to expand...
Click to collapse
Glad for you that it worked.
Kwes1020 pointed me in the right direction last week. Be sure to give a thanks to ILUHA_89 who came up with the fix.
Amazing how people are soo lost without providing them link after link to other threads. They are soo lazy and can't follow simple directions, each time i get a new phone i go to that section on xda and soak up all the information as it usually is already there. It's just funny is all i guess.
d12unk13astard said:
Amazing how people are soo lost without providing them link after link to other threads. They are soo lazy and can't follow simple directions, each time i get a new phone i go to that section on xda and soak up all the information as it usually is already there. It's just funny is all i guess.
Click to expand...
Click to collapse
It's really not that big a deal. I was brand new to android once and asked all sorts of things.
I, like you, happen to read everything I can get my hands on. Some struggle going through all the info. I was here the day the forum opened, so I kind of remember where everything is.
Some are lazy and others just have no idea what the heck is going on and are intimidated by certain processes. I would rather help someone instead of listening to them ***** about their broken phone.
Hi all
Yesterday, I rooted my I5801 (on Orange network) using z4root. Everything went as expected and I used Titanium Backup to remove all of the horrible Orange game demos/bloatware etc. After doing this, everything was working fine and I used the phone for all of today without issue.
I became curious reading about the key-combo for recovery mode and (stupidly) thought I'd take a look. I forgot the exact key-combo, so I just turned the phone off and tried holding vol up + vol down + home + power. Now whenever I try to start the phone, I get a yellow exclamation mark in a white triangle with the Android below. If I push the home button while on this screen I get an open box with an arrow pointing out of it and what looks like a progress bar below that, but it just takes me right back to the exclamation mark screen.
I can get into Download Mode by taking the battery out, putting it back in and holding vol down + power, if this helps.
I've read that it should be possible to reflash, but I really want to try and avoid this if possible, as I don't see why my OS would have died without trying to reflash in the first place.
Is it possible to get back into the OS without reflashing? And if I do need to reflash, can anyone make any recommendations?
Thanks in advance for any answers!
Welcome to the forum
First of all, thats a weird story you got there I have no idea what happened to your phone to be honest. The fact that you can get into download mode is a good sign, it means your phone is not hardbricked (yet) .
I really don't know how I would get around this problem without reflashing, maybe someone else knows a possible solution? I think flashing a new Rom (Android OS) is the way to go. Do you know the buildnumber of your current Rom? You can search for your current Rom in this thread: http://forum.xda-developers.com/showthread.php?t=1063940. Download it and flash it with Odin via pc to your phone (while in download mode). That should fix it, its a pretty drastic method though.
Good luck
BTW: I'd prefer One-click-root as a method for rooting in the future, you need software on pc to do that. But thats my opinion.
Thanks for the reply! I'm not sure which build I was on.
I'm going to try and put on I5800XXJPU with Odin found here: http://forum.xda-developers.com/showthread.php?t=1497261
Hopefully because there is no bootloader this won't hardbrick my phone!
Morley93 said:
Thanks for the reply! I'm not sure which build I was on.
I'm going to try and put on I5800XXJPU with Odin found here: http://forum.xda-developers.com/showthread.php?t=1497261
Hopefully because there is no bootloader this won't hardbrick my phone!
Click to expand...
Click to collapse
Sounds good
Good luck.
In fact, I've just read that if you're going from Eclair (I was definitely on Eclair) to Froyo (which I believe that ROM is) then you need to have a ROM with a bootloader for it to work.
Guess I'll try Kyrillos!
Morley93 said:
In fact, I've just read that if you're going from Eclair (I was definitely on Eclair) to Froyo (which I believe that ROM is) then you need to have a ROM with a bootloader for it to work.
Guess I'll try Kyrillos!
Click to expand...
Click to collapse
Huh? Never seen that, where did you read it? Maybe I can check it out?
http://forum.xda-developers.com/showthread.php?t=1372414
PersianSphinx said:
EDIT: If you are coming from eclair, install a froyo ROM and make sure it has a bootloader
Click to expand...
Click to collapse
Well yeah, I guess you're right... I still really don't quite understand what's up with bootloaders.
never heard about "coming from eclair, bootloader ROM needed for froyo update"!
My original FW was also eclair and I never ever flashed a bootloader!
But try and see if you get a brick with flashing a bootloader! I wouldn´t dare doing that, but it´s up to you.
I would open another thread and ask specially that question. Why?
Then you get more opinions to make your choice.
Good luck and keep us informed about the progress.
Sorted, I ended up giving the phone to a friend who is more phone competent than myself!
Here's the solution:
http://forum.xda-developers.com/showthread.php?t=1565841
Thanks for the advice folks!
Morley93 said:
Hi all
Yesterday, I rooted my I5801 (on Orange network) using z4root. Everything went as expected and I used Titanium Backup to remove all of the horrible Orange game demos/bloatware etc. After doing this, everything was working fine and I used the phone for all of today without issue.
I became curious reading about the key-combo for recovery mode and (stupidly) thought I'd take a look. I forgot the exact key-combo, so I just turned the phone off and tried holding vol up + vol down + home + power. Now whenever I try to start the phone, I get a yellow exclamation mark in a white triangle with the Android below. If I push the home button while on this screen I get an open box with an arrow pointing out of it and what looks like a progress bar below that, but it just takes me right back to the exclamation mark screen.
I can get into Download Mode by taking the battery out, putting it back in and holding vol down + power, if this helps.
I've read that it should be possible to reflash, but I really want to try and avoid this if possible, as I don't see why my OS would have died without trying to reflash in the first place.
Is it possible to get back into the OS without reflashing? And if I do need to reflash, can anyone make any recommendations?
Thanks in advance for any answers!
Click to expand...
Click to collapse
First of all going into download , must hold home + vol down + power , that's first mistake. Nothing bad happened to your phone yet , go and reflash any froyo with or without bootloader i did it countless times when no one on this forum had a firmware without bootloader starting from old JPF , yes there is a risk but the reflashing is the only solution Good Luck
But anything that may change the state would be a huge help if you have a thought?
All I have right now is a quick LED and battery charge signal for a second then gone.
I can't get into download or recovery mode or power on.
I switched CWM versions (after a nandroid and attempting to reinstall the previous CWM would error) and then tried to flash cm10.
I went into bootloop and tried to pull the battery since i couldnt force it to recovery so i could restore factory but nothing now.
Again, I think i screwed myself, but if you can save me money I'd appreciate any thoughts.
dont know how to help man. unless you know how to jtag, it sounds like you are hard bricked. by the way, you do know that cm10 is SUPPOSED to bootloop for a few minutes on every boot right? or maybe your battery was really low during flash, or maybe you got a bad md5 sum for your download? more info on what you did to make this happed would make it easier to help you.
Make sure your doing the right combination for download mode. Volume down home button and power.
Sent from my SCH-I535 using Tapatalk 2
Stryker1297 said:
dont know how to help man. unless you know how to jtag, it sounds like you are hard bricked. by the way, you do know that cm10 is SUPPOSED to bootloop for a few minutes on every boot right? or maybe your battery was really low during flash, or maybe you got a bad md5 sum for your download? more info on what you did to make this happed would make it easier to help you.
Click to expand...
Click to collapse
yeah. it rebooted over a dozen times.
im not sure if when i updated CWM to touch and a newer version if for whatever reason it didnt recognize the nandroid from an hour earlier.
but that doesnt really make sense.
i have to think i did something wrong with the recovery img
so now there is no response to any of the hardware buttons.
crap. and thanks.
How about listing the steps on what you did to get where you are now.?
I've had somewhat similar problem. Mine turned out to be dead battery and phone wouldn't charge. I ended up charging battery on buddies phone, which allowed phone to boot. Then I wiped everything and started from scratch. Everything returned to normal
A few details before I start
I am on Galaxy S3 i535 from Verizon, was running CleanROM 5.6 for a few hours after coming from Codename Android that I was using for a few days(I've been going crazy with trying roms lately.)
I flashed LiquidSmooth 2.0 with CWM (never have used odin)
On all of these flashes before i did so I wiped system/factory reset, wiped cache and dalvik cache, and formatted system, cache, and data.
I had just finished flashing Liquid Smooth about an hour ago and was installing a few things with titanium back up. everything up until this point was going fine, got all my apps instaIlled and ready to go, and I head into the settings and try to turn on a few things and edit some settings in the Liquidsmooth settings.
Now my phone is stuck in a bootloop and I'm not sure what to do. I have tried power/volume down, power/home/volume up, power/home/volume down, and nothing will get it to reboot. I dont know whether or not it is safe to take out the battery and start from there, so if that is the route I should take, please let me know.
I have no experience with odin, but I can most definitely look that up so I wont need help there. Just some help on whether or not I should take out the battery or do something else. I just don't want to brick it in any way if that is avoidable:fingers-crossed :fingers-crossed:
Thanks to whoever can help me!
Edit:
I used the search a little better this time and saw people say pull battery on similar cases, and I did that, and I'm still stuck in bootloop. (It seems like in most of the threads I found pulling the battery was a given so people didnt mention it, but I needed to know for sure.) So I am still in the bootloop and am just going to boot into download mode and go from there.
Alright I was able to odin to stock, and now im back to square one.
Not sure how to delete threads :S
Toastiesyay said:
A few details before I start
I am on Galaxy S3 i535 from Verizon, was running CleanROM 5.6 for a few hours after coming from Codename Android that I was using for a few days(I've been going crazy with trying roms lately.)
I flashed LiquidSmooth 2.0 with CWM (never have used odin)
On all of these flashes before i did so I wiped system/factory reset, wiped cache and dalvik cache, and formatted system, cache, and data.
I had just finished flashing Liquid Smooth about an hour ago and was installing a few things with titanium back up. everything up until this point was going fine, got all my apps instaIlled and ready to go, and I head into the settings and try to turn on a few things and edit some settings in the Liquidsmooth settings.
Now my phone is stuck in a bootloop and I'm not sure what to do. I have tried power/volume down, power/home/volume up, power/home/volume down, and nothing will get it to reboot. I dont know whether or not it is safe to take out the battery and start from there, so if that is the route I should take, please let me know.
I have no experience with odin, but I can most definitely look that up so I wont need help there. Just some help on whether or not I should take out the battery or do something else. I just don't want to brick it in any way if that is avoidable:fingers-crossed :fingers-crossed:
Thanks to whoever can help me!
Edit:
I used the search a little better this time and saw people say pull battery on similar cases, and I did that, and I'm still stuck in bootloop. (It seems like in most of the threads I found pulling the battery was a given so people didnt mention it, but I needed to know for sure.) So I am still in the bootloop and am just going to boot into download mode and go from there.
Alright I was able to odin to stock, and now im back to square one.
Not sure how to delete threads :S
Click to expand...
Click to collapse
ok i only read the first few lines but manually boot into cwm by either vol up or down and multi function and power at the same time and upload a rom like synergy i know it works and u should be good
WOW!
This I cant believe!
Toastiesyay said:
I have tried power/volume down, power/home/volume up, power/home/volume down, and nothing will get it to reboot.
Click to expand...
Click to collapse
wingtytn said:
ok i only read the first few lines but manually boot into cwm by either vol up or down and multi function and power at the same time and upload a rom like synergy i know it works and u should be good
Click to expand...
Click to collapse
Yeah, we noticed you only read the first few lines. :what:
If you are gonna try to help at least read the whole OP.
And to manually boot recovery its: Volume up+home+power.
Not
wingtytn said:
EITHER vol up or down and multi function and power at the same time
Click to expand...
Click to collapse
Sent from my SPH-L710 using xda premium
OP you are missing the point here. You have to take the battery out and put it back in before going to recovery. Once you have done that try vol-up/home/ power at the same time. Once samsung logog appears look at the top left if you see words release. it will boot to recovery. You can take it from there.
Sorry everyone for this annoying post but I have done research enough to think that I may be out of luck so you guys are my last hope here.
Here is the senario;
I have been running Cyanogenmod 12 (courtesy of Sultan). Once the ROM was discontinued I decided to give Paranoid 5.1 a shot. I downloaded the new rom, suggested SuperSU and Gapps and booted to the most up to date TWRP. I flashed the rom, then supersu, and finally Gapps and then rebooted my phone. The phone stayed in the boot screen for about 45 minutes (maybe even an hour) so I powered off the phone, pulled the battery, and attempted to boot back into recovery using the power and volume buttons but nothing was working. The phone would just keep vibrating (pulsing) until i let the buttons go and then jump right back into the booting screen until I turned the phone off again. Hopefully I am doing something wrong and there is an easy fix but Im afraid that I now havae a brick on my hands.
Please help,
SuperNewb
[Update]
Now the phone will hold the boot screen for a couple minutes then the screen just goes black. Not sure what that means.
Also, just so you guys dont think im too ignorant, I will say that I I have flashed at least 10 different ROMs before this so I would like to think that I have a decent understanding of how this all should work.
Finally got back into recovery using advise from this post
http://forum.xda-developers.com/showthread.php?t=1769102
hopefully a traditional whip can get me back on track
I had to use ODIN, go back to stock rom, reflash TWRP and then install paranoid. But were all good now. Sorry guess I didnt do as much research as I thought.
Help
harrisd23 said:
I had to use ODIN, go back to stock rom, reflash TWRP and then install paranoid. But were all good now. Sorry guess I didnt do as much research as I thought.
Click to expand...
Click to collapse
i made a factory reset and my phone doesn't want to pass the "upgrading app"