Related
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.
hi,
i need help my GN is not starting after I flashed a theme all i can just get into clock mode recovery even i didn't have any back up or any restore point it just shows google logo when i start. Please helppppppppppppppppppp pleaseeeeeee
thankzzz
now i am stuck on below attachment please help thnkzz so much for all reply till now
since you didn't do a Android your basically screwed so all you data is gone you only hope is to transfer a file through fastboot(can you even do that?) Or boot to Odin mode and flash a stock image
Sent from my Galaxy Nexus using XDA App
GSM or LTE Gnex? What ROM were you running?
Golden rule: Do a backup before doing anything to your phone!
Now all you can do is to download EXACTLY same ROM as you were using by now, wipe cache/dalvik-cache, flash this ROM once again and hope that i'll boot. If it won't you'll have to wipe /data is well.
Sleuth255 said:
GSM or LTE Gnex? What ROM were you running?
Click to expand...
Click to collapse
HI
its gsm i tried to flashed the same rom but still the same only i can access is to recovery
cordell507 said:
since you didn't do a Android your basically screwed so all you data is gone you only hope is to transfer a file through fastboot(can you even do that?) Or boot to Odin mode and flash a stock image
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
tnkz bro but i am new to android please help how to do it with Odin
well since you can boot into recovery try searching in your sdcard folders if youve left a ROM .zip there laying around and if this is the case just flash it and youre back on track
nonione said:
well since you can boot into recovery try searching in your sdcard folders if youve left a ROM .zip there laying around and if this is the case just flash it and youre back on track
Click to expand...
Click to collapse
unfortunatly i delete system file and data file also in recovery i tried to flash the zip update but no result helpppppppppppppppp
salym said:
unfortunatly i delete system file and data file also in recovery i tried to flash the zip update but no result helpppppppppppppppp
Click to expand...
Click to collapse
This will help you get back to stock
http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile
Change your spark plugs.
Sent from my Nexus in Texas.
spaceman860 said:
This will help you get back to stock
http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile
Click to expand...
Click to collapse
Hi bro i tired with Odin but stops on userdata any help thnkzzzz
salym said:
hi,
i need help my GN is not starting after I flashed a theme all i can just get into clock mode recovery even i didn't have any back up or any restore point it just shows google logo when i start. Please helppppppppppppppppppp pleaseeeeeee
thankzzz
Click to expand...
Click to collapse
i am stuck on this now please help
ouch... softbrick.
put your phone down.
take a deep breath or two.
If you are old enough, grab a beer and relax for a bit. Think calming thoughts.
Now, start learning about how to mod your GNex. We can help.
Here's your First assignment:
find out if you still have a bootloader by booting into fastboot mode. Report back with your findings and a screenshot!
Sleuth255 said:
ouch... softbrick.
put your phone down.
take a deep breath or two.
If you are old enough, grab a beer and relax for a bit. Think calming thoughts.
Now, start learning about how to mod your GNex. We can help.
Here's your First assignment:
find out if you still have a bootloader by booting into fastboot mode. Report back with your findings and a screenshot!
Click to expand...
Click to collapse
Still have a bootloader? Are you serious? You need to learn how to use an android device as well.
To the OP: Do a factory reset in Clockwork and go to mounts
and format /system. Flash the ROM zip. Profit.
Absolutely serious. Have you been reading this thread? The OP needs to start at ground zero and stop just trying every tool he/she sees. My purpose was to get this person to do some research and I was establishing a knowledge baseline. One plan I was considering was to help the OP install the GNex toolkit then locate stock images and obtain a working build. Your cryptic one liner bit should prove vastly more useful to this guy though. I'll let you have at it and go back to my dev work. lol at least this post was a good way to make sure gapps/root capabilities are properly cooked into my latest test build ....
Sent from my Full AOSP on Toro using xda premium
Sleuth255 said:
ouch... softbrick.
put your phone down.
take a deep breath or two.
If you are old enough, grab a beer and relax for a bit. Think calming thoughts.
Now, start learning about how to mod your GNex. We can help.
Here's your First assignment:
find out if you still have a bootloader by booting into fastboot mode. Report back with your findings and a screenshot!
Click to expand...
Click to collapse
U r right i am not good in android but i tried to be and this happens, meanwhile nothing shows after i start the device it shows the !!!! mark with device the PC logo,this happens due to ODin actually the SUMSUNG ADB interface shows ! mark because i cant debug from device even no bootloader works any more thnkz for replying
*facepalm*
OP, you are holding it wrong.
I can think of at least 2 ways to recover from a situation like this. Both are well described in these forums (search works 99% of the time).
....
Oh come on, you don't have the zip of the last rom you flashed, get another one, hey, its free right? **** we dont know nothing about but we'll flash it anyways!
Man...If you have cwm recovery, you're safe. No need to go messing with fastboot (forget odin) just yet. Now stop wasting everybody's time and learn to help yourself.
Here's a few tags to get you started:
cwm, recovery, adb, bootloader, fastboot
bk201doesntexist said:
*facepalm*
OP, you are holding it wrong.
I can think of at least 2 ways to recover from a situation like this. Both are well described in these forums (search works 99% of the time).
....
Oh come on, you don't have the zip of the last rom you flashed, get another one, hey, its free right? **** we dont know nothing about but we'll flash it anyways!
Man...If you have cwm recovery, you're safe. No need to go messing with fastboot (forget odin) just yet. Now stop wasting everybody's time and learn to help yourself.
Here's a few tags to get you started:
cwm, recovery, adb, bootloader, fastboot
Click to expand...
Click to collapse
i tried more than one day on this issue its only starts with !!! mark on it nothing else, i have attached the pic i cant access any bootloader or any cwm or any thing all i did with Odin and stuck to attached pic even i start the device its shows the same pic.
http://www.youtube.com/watch?v=WdM2M8Nz6QQ this I used on Odin
thnkzz
As I suspected earlier, it appears that the OP may have trashed his bootloader partition when he tried using Odin to flash the 4.0.2 factory image (which includes a bootloader). At one point he had CWM but not any more since he can't boot to the recovery partition.
Another possibility is that the Odin tool itself places the device in this mode and it can't be manually reverted by starting up in fastboot mode. Looking at the picture, it literally appears that the phone is saying that a flashing operation is half finished but the phone has lost the PC connection... This would be a lot like what I've experienced with iPhones.
In either case, I can deduce that Odin is the tool to use to clear this softbrick.
Hopefully, it'll be flame-off now Sdobron. Perhaps you might want to help out here since I'm not up to speed on the Odin tool myself and would like to learn more about it.
@salym: I know this may be redundant but I need to establish your problem baseline empirically. Once again, can you verify that when you hold vol down/vol up then press power that you get the image you posted?
Use Fastboot!
Dude, it looks like your problem is with crappy boot sector.
While turning on your phone, hold both volume up and volume down buttons, and long press power button untill you feel single vibrate feedback.
Then connect your phone to the computer via USB, and if it doesn't detect drivers, google "samsung android usb driver". Additionally you can install PDANet application (X64 or x86 depending on you system).
THen download Fastboot - there are plenty of instructions how to flash it, and flash stock images (that come with radio, boot sector, rom itself, etc) - there are also plenty of discussions about how to do it. PM if you have any other questions!
I was flashing a TrickDroid ROM just now, having had Jellytime 17.1 previously. I did a full backup and full wipe before attempting to flash the TrickDroid ROM.
I got distracted during the process, and when I came back to my phone, it was showing the Jellytime boot animation, but never gets to the UI.
OK, so I figure I can hold the power and volume down button and get into recovery. Nope. When I try to select Recovery from the boot loader, it doesn't do anything at all.
Am I hosed up for good here?
When you get into hboot does it do the normal check? After that it should let you choose.
If that doesn't work try pulling the battery for a few minutes and try again.
If you have adb you can type:
adb reboot recovery
Sent from a dream.
Teichopsia said:
When you get into hboot does it do the normal check? After that it should let you choose.
If that doesn't work try pulling the battery for a few minutes and try again.
If you have adb you can type:
adb reboot recovery
Sent from a dream.
Click to expand...
Click to collapse
It does do the check. When I select "recovery" or "factory reset", it just comes back to the bootloader menu without doing anything.
Mike
TheImpalaKid said:
It does do the check. When I select "recovery" or "factory reset", it just comes back to the bootloader menu without doing anything.
Mike
Click to expand...
Click to collapse
Perhaps you need to re-flash a recovery but let's wait for someone to double check and confirm.
But then you get the same issue with factory reset (which you shouldn't do).
Sent from a dream.
If it goes into the bootanimation then you can use ADB. Connect the phone to pc and let it go into the bootloop and then use "adb reboot recovery" from the command line on your pc.
If it stil doesn't work then you'll need to reflash your recovery. Download a recovery image like ClockWorkMod, go into bootloader while connected to pc. It should show "Fastboot USB" on the bootloader screen. Then use ""fastboot flash recovery [name of the image.img]" to flash a new recovery.
Try going into recovery again and see if it helps.
Teichopsia said:
Perhaps you need to re-flash a recovery but let's wait for someone to double check and confirm.
But then you get the same issue with factory reset (which you shouldn't do).
Sent from a dream.
Click to expand...
Click to collapse
I tried removing the battery for about 10 minutes, and then tried getting into recovery. The same thing happens when I select "recovery".
I let it sit for about 40 minutes with the JellyTime boot animation running, hoping it would complete, but it never did.
I guess AT&T can reflash it but then I'll have to root it again. I guess that's better than losing the whole thing.
Mike
Its strange though.. flashing a ROM doesn't tamper the recovery partition so it shouldn't have happened.
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
TheImpalaKid said:
I tried removing the battery for about 10 minutes, and then tried getting into recovery. The same thing happens when I select "recovery".
I let it sit for about 40 minutes with the JellyTime boot animation running, hoping it would complete, but it never did.
I guess AT&T can reflash it but then I'll have to root it again. I guess that's better than losing the whole thing.
Mike
Click to expand...
Click to collapse
You won't need to give it to AT&T.. just run an RUU and root it again if it comes to it.
Just do what the previous member suggested. You both posted at the same time so you might not have seen it.
Sent from a dream.
Teichopsia said:
Just do what the previous member suggested. You both posted at the same time so you might not have seen it.
Sent from a dream.
Click to expand...
Click to collapse
Thanks, I hadn't seen that other reply.
I have been flashing ROMs for about a year, and had never run across this problem. I've never had anything happen that messed up recovery until now.
I will try this when I get home from work today. Thanks to both of you for the help and suggestions.
Mike
TheImpalaKid said:
Thanks, I hadn't seen that other reply.
I have been flashing ROMs for about a year, and had never run across this problem. I've never had anything happen that messed up recovery until now.
I will try this when I get home from work today. Thanks to both of you for the help and suggestions.
Mike
Click to expand...
Click to collapse
Ofcourse.. and It shouldn't have happened. ROM's don't mess with the recovery. Even if anything happened during flashing the ROM the recovery partition should not be affected. This is a strange situation indeed.. should be brought to attention of the 4ext recovery developer...
if4ct0r said:
Ofcourse.. and It shouldn't have happened. ROM's don't mess with the recovery. Even if anything happened during flashing the ROM the recovery partition should not be affected. This is a strange situation indeed.. should be brought to attention of the 4ext recovery developer...
Click to expand...
Click to collapse
I thought it was pretty weird, too. I've flashed ROMs a ton of times with no problems.
I am using ClockworkModRecovery.
Mike
TheImpalaKid said:
I thought it was pretty weird, too. I've flashed ROMs a ton of times with no problems.
I am using ClockworkModRecovery.
Mike
Click to expand...
Click to collapse
Oh.. my bad. I thought I read that you use 4EXT.. :silly:
In anycase.. All is well and solvable if you can reach the bootanimation Just use ADB.
if4ct0r said:
Oh.. my bad. I thought I read that you use 4EXT.. :silly:
In anycase.. All is well and solvable if you can reach the bootanimation Just use ADB.
Click to expand...
Click to collapse
I guess... I can't get my laptop to recognize the phone or load any drivers for it. So when I try to run adb, I get no devices.
I have a teenage son who I may sic on this problem.
Mike
You have HTC Sync installed? You have ADB as well? Make sure you have it installed. It installs connectivity drivers for your phone.
If you're indeed getting into bootanimation your phone should be recognized by ADB. After installing HTC Sync, try running "adb devices" if it shows no devices try running "adb kill-server" and then "adb devices" again. If all drivers are correctly installed it should recognize your phone.
Tips: You can get adb by running the advanced ace hack kit once
Update
My two sons were able to finally get the phone reset to factory spec sometime last night. :victory: So I'll have to re-root the phone and then I can restore my ROM from the backups.
One weird thing... the speaker/microphone doesn't work now. This is no big deal as I rarely receive or make calls.
I'm probably not your typical Android user in that I'm 55, and I love to try out the different ROMs that are available. Favorites are BlackIce, Trickdroid, and JellyTime.
Most of my peers have some sort of iPhone and really don't care anything about behind-the-scenes or jailbreaking, etc.
Thanks to everyone who's offered help and information.
Mike
TheImpalaKid
Hi, I was flashing a new rom but I accidentally select the sideload option and now I'm stuck there,
I tried to hold power button 30 seconds, even more,(also volume down + power button) but nothing happens.
Any idea?
It says:
"ClockworkMod Recovery v6.0.2.3
Sideload started...
Now send the package you want to apply
to the device with "adb sideload <filename>"
Please help I'm n00b -.-
I did that once and I didnt know how to get out of it either. Just pull the battery and restart.
jsgraphicart said:
I did that once and I didnt know how to get out of it either. Just pull the battery and restart.
Click to expand...
Click to collapse
Thank you so much man, that worked!
ARMIGUER said:
Thank you so much man, that worked!
Click to expand...
Click to collapse
No problem. Dont try that when something is running though. That might mess things up. But the sideload thing isnt running anything. Its just waiting for a command. They need to put a back or a cancel button on that.
jsgraphicart said:
No problem. Dont try that when something is running though. That might mess things up. But the sideload thing isnt running anything. Its just waiting for a command. They need to put a back or a cancel button on that.
Click to expand...
Click to collapse
Thanks for the advice but now I'm installing the crossbones ROM 2.3.0 but I'm stuck installing it,
I used to flash roms in my other phone a galaxy s3 and I've never had this kind of problems...
It says this:
Formatting system
Installing Crossbones ROM
that's all
What would you recommend me in this case?
Should I remove the baterry again? I've been waiting for almost 15 minutes and nothing again :/
ARMIGUER said:
Thanks for the advice but now I'm installing the crossbones ROM 2.3.0 but I'm stuck installing it,
I used to flash roms in my other phone a galaxy s3 and I've never had this kind of problems...
It says this:
Formatting system
Installing Crossbones ROM
that's all
What would you recommend me in this case?
Should I remove the baterry again? I've been waiting for almost 15 minutes and nothing again :/
Click to expand...
Click to collapse
I'm going to assume your phone is unlocked and rooted already. Are you using the latest version of whatever recovery you are using? Are you using the ROM made specifically for your phone?
but rdleye
jsgraphicart said:
I'm going to assume your phone is unlocked and rooted already. Are you using the latest version of whatever recovery you are using? Are you using the ROM made specifically for your phone?
Click to expand...
Click to collapse
The phone is unlocked and rooted,and yes, I'm using the Clockworkmode v6.0.2.3 latest version.
My phone is the galaxy nexus (sprint)
And I download the ROM from here
http://forum.xda-developers.com/showthread.php?t=2101334
I wiped, data,cache and dalvik.
But I don't know what happens, I'm pretty n00b but I flash 4 roms before in my galaxy s3 and all is fine.
Thanks for your help man.:good:
ARMIGUER said:
The phone is unlocked and rooted,and yes, I'm using the Clockworkmode v6.0.2.3 latest version.
My phone is the galaxy nexus (sprint)
And I download the ROM from here
http://forum.xda-developers.com/showthread.php?t=2101334
I wiped, data,cache and dalvik.
But I don't know what happens, I'm pretty n00b but I flash 4 roms before in my galaxy s3 and all is fine.
Thanks for your help man.:good:
Click to expand...
Click to collapse
You did everything right then. I dont know why it would hang. Id say pull the battery but like I said, it could mess something up if its actually doing something. Especially if it says it already wiped the system. If that happens, you're going to have to restore a factory image and start all over again. Its up to you if you want to take the chance. A ROM flash shouldnt take that long.
jsgraphicart said:
You did everything right then. I dont know why it would hang. Id say pull the battery but like I said, it could mess something up if its actually doing something. Especially if it says it already wiped the system. If that happens, you're going to have to restore a factory image and start all over again. Its up to you if you want to take the chance. A ROM flash shouldnt take that long.
Click to expand...
Click to collapse
Well I took the risk and removed tha battery after waiting for almost 30 minutes,
and I will try again all the process.
Once again thanks for your help man :good:
ARMIGUER said:
Well I took the risk and removed tha battery after waiting for almost 30 minutes,
and I will try again all the process.
Once again thanks for your help man :good:
Click to expand...
Click to collapse
No problem. I hope you get it working. Or at least to boot up again.
Supposedly sideload in cwm is a bug with no way to back out unless you pull the battery or have usb connected [exit in command prompt?]. I was starting to like the touch recovery option, but recently i've accidentally pressed a couple of things i shouldnt have.
Sorry to hijack, but I'm attempting to sideload the 4.2.2 update from stock, and my sideload command seems to do nothing. I'm sure i'm connected as it displays my device number and "sideload" next to it. Using the sideload command simply displays the "help" list of the adb commands.
Is it a driver issue perhaps? Something else? (i noticed my batter was low just before attempting this).
Now i'm stuck in the waiting for adb sideload file.
hippochris: update your adb, or look in the help output to see if the sideload command is there. Also, i did this via stock recovery, selecting it in there.
bodh said:
hippochris: update your adb, or look in the help output to see if the sideload command is there. Also, i did this via stock recovery, selecting it in there.
Click to expand...
Click to collapse
I do NOT see the sideload option in the help output. I have all the latest updates from the SDK manager. Maybe i need to reinstall the SDK. I will give that a go. Thanks.
Edit: Downloaded the latest SDK/ADB and that worked. From 1.0.29 to 1.0.31
I've messed my phone with SideLoad, please help
I booted my Galaxy Nexus into custom recovery (CWM) for some other task but mistakenly gone into sideload menu!
Got no option to get back to main menu or reboot, i took the battery out and re-inserted. Now, my cell is not turning on since then!
Tried another time, took battery off but no luck..... what to do?
I've custom ROM, MIUI V5 4.2.2. My cell is unlocked and rooted, of course.
Please help.
What if the battery is non-removable?
Had stuck in that *** sideload on my SM-E500H and been waiting for the battery to drained it up all.
Yep, tried hardware button combinations as many times as I could.
if you can't take out the battery of your device and if longpressing whatever does not solve it
1. install adb on pc.
2. connect device with usb cable to pc
3. enter following command
Code:
adb sideload /dev/null
the device will complain that file is not valid but it will come out of the sideloading state
lesmanaz said:
if you can't take out the battery of your device and if longpressing whatever does not solve it
1. install adb on pc.
2. connect device with usb cable to pc
3. enter following command
Code:
adb sideload /dev/null
the device will complain that file is not valid but it will come out of the sideloading state
Click to expand...
Click to collapse
What if I'm still in sideload and get this error?
Code:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I have spent the last 3 days searching XDA & trying every possible fix, no luck!
Here's my dilemma.....
I have custom recovery, TWRP 2.6.3.3, don't know what I did after trying to flash something........ I wiped everything except SDcard by accident. Like a darn fool, forgot after backing up everything via computer, to put a spares on my SDcard. Sooooo, I tried restoring by using LG FlashTool..... Here's where my problems began:
1. I can't load into download mode, it sticks at the logo to enter download mode but doesn't connect.
2. I tried ADB Sideload, sticks at "STARTING ADB SIDELOAD FEATURE.........."
3. No matter what mode (including Fastboot) I try, just won't connect to my computer the way I need it to. (*ALL DRIVERS HAVE BEEN REINSTALLED NUMEROUS TIMES, STILL NO LUCK.*) When I look in DEVICE MANAGER, it shows in "OTHER DEVICES" as "LG-LS980" (*Which is a good thing right? *)
At this point i'm at my wits end...... I tried to HARD FACTORY RESET, but didn't go thru. I'm afraid that if I tried it again, I could cause even more damage.
I've been without my phone for days & I'm about to go crazy if I have to pay LG or Sprint again for another phone!!!! I'd rather use my $600 on something else.
PLEASE TELL ME SOMEONE HAS FOUND A WAY TO GET AROUND THIS!
I've searched just about every forum & tried different methods.
Forgot to add that every time I power off from recovery, I get a the message about my device not being rooted, would I like to install..... When I swipe to install, nothing happens. Just powers off.
MsOhSoPhresh said:
I have spent the last 3 days searching XDA & trying every possible fix, no luck!
Here's my dilemma.....
I have custom recovery, TWRP 2.6.3.3, don't know what I did after trying to flash something........ I wiped everything except SDcard by accident. Like a darn fool, forgot after backing up everything via computer, to put a spares on my SDcard. Sooooo, I tried restoring by using LG FlashTool..... Here's where my problems began:
1. I can't load into download mode, it sticks at the logo to enter download mode but doesn't connect.
2. I tried ADB Sideload, sticks at "STARTING ADB SIDELOAD FEATURE.........."
3. No matter what mode (including Fastboot) I try, just won't connect to my computer the way I need it to. (*ALL DRIVERS HAVE BEEN REINSTALLED NUMEROUS TIMES, STILL NO LUCK.*) When I look in DEVICE MANAGER, it shows in "OTHER DEVICES" as "LG-LS980" (*Which is a good thing right? *)
At this point i'm at my wits end...... I tried to HARD FACTORY RESET, but didn't go thru. I'm afraid that if I tried it again, I could cause even more damage.
I've been without my phone for days & I'm about to go crazy if I have to pay LG or Sprint again for another phone!!!! I'd rather use my $600 on something else.
PLEASE TELL ME SOMEONE HAS FOUND A WAY TO GET AROUND THIS!
I've searched just about every forum & tried different methods.
Click to expand...
Click to collapse
So try this...
Push the power button to turn the device on. Let it sit.
After you know that the g2 is on and trying to do its think, Press and hold power buttton, do not let go. It will force turn off the phone, but it will start to turn back on, if you keep holding the power button till it shuts off for the second time, you'll be set and the device will be fully off.
Have Lg Flash Tool open, make sure you have manual mode on and you point to the right dll and right tot file, could be zv7 zv8 or zva.
Click the arrow to have the flash tool biin check the files. when that is ready, do this next part fast. Plug in your phone, and immeditaly press and hold Volume up and Power. Download mode should appear.
and you should be good from there! If you try to enter download mode by using volume and up without the cable plug in, you'll hit the factory reset menu which is tied to the recovery, it'll do nothing, only take you to recovery. I hope this is of some help!
Edit:try new boot loader or system flasher via twrp
proplem i faced is one button which used to enter recovery is damged
Flash stock Ignoring the unmonted ianot able to be mounted then change system partitions u will be able to mount
Enjoy
bmxerkid954 said:
So try this...
Push the power button to turn the device on. Let it sit.
After you know that the g2 is on and trying to do its think, Press and hold power buttton, do not let go. It will force turn off the phone, but it will start to turn back on, if you keep holding the power button till it shuts off for the second time, you'll be set and the device will be fully off.
Have Lg Flash Tool open, make sure you have manual mode on and you point to the right dll and right tot file, could be zv7 zv8 or zva.
Click the arrow to have the flash tool biin check the files. when that is ready, do this next part fast. Plug in your phone, and immeditaly press and hold Volume up and Power. Download mode should appear.
and you should be good from there! If you try to enter download mode by using volume and up without the cable plug in, you'll hit the factory reset menu which is tied to the recovery, it'll do nothing, only take you to recovery. I hope this is of some help!
Click to expand...
Click to collapse
This isn't working. I've tried this numerous times..... No luck.
myaservip said:
Edit:try new boot loader or system flasher via twrp
proplem i faced is one button which used to enter recovery is damged
Flash stock Ignoring the unmonted ianot able to be mounted then change system partitions u will be able to mount
Enjoy
Click to expand...
Click to collapse
I'm now completely lost.....
Ok... So i made a little progress....
I am now able to boot into fastboot mode.... No recovery now tho. If someone can help me with manually pushing everything I need to restore my phone, it would make my day!
I'm having withdrawal symptoms now. LOL! I MISS MY PHONE!
Problem solved!
Flashed all the partitions 1by1 via fastboot, was able to then reboot into download mode. Now using LG FlashTool to return to stock! I am now a very happy camper after a week w/o my phone!
MsOhSoPhresh said:
This isn't working. I've tried this numerous times..... No luck.
Click to expand...
Click to collapse
MsOhSoPhresh said:
I am now able to boot into fastboot mode.... No recovery now tho. If someone can help me with manually pushing everything I need to restore my phone, it would make my day!
I'm having withdrawal symptoms now. LOL! I MISS MY PHONE!
Click to expand...
Click to collapse
MsOhSoPhresh said:
Flashed all the partitions 1by1 via fastboot, was able to then reboot into download mode. Now using LG FlashTool to return to stock! I am now a very happy camper after a week w/o my phone!
Click to expand...
Click to collapse
Glad to see you've fixed your problem! I myself haven't been around, had some down time to. My sim reader magically stopped working and then randomly started working days later. Anyway, congrats!!!
MsOhSoPhresh said:
Flashed all the partitions 1by1 via fastboot, was able to then reboot into download mode. Now using LG FlashTool to return to stock! I am now a very happy camper after a week w/o my phone!
Click to expand...
Click to collapse
Glad you figured it out. I was about to basically explain the steps to do exactly what you did.
Welcome back to the land of the living!
agentfusion said:
Glad you figured it out. I was about to basically explain the steps to do exactly what you did.
Welcome back to the land of the living!
Click to expand...
Click to collapse
After she got it the first time, which we both congratulated her for, something went completely wrong. She dug herself even deeper, but broke download mode. That was extremely fun to fix.