Related
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!
CDMA GALAXY NEXUS> Hey guys, I was running Romanbb's 4.0.4 build earlier today. I clicked on a video (which may or may not have been on a porn site) all of a sudden my screen went all wacky. Where it was kind of fuzzy and running diagnal across the screen. I could only see part of it. I thought I might have gotten a virus or something because i have never had one of my devices do this before. So I immideatly rebooted the phone into recovery and wiped eveything including formatting system. I went to flash a nandroid I had of black ice and in the middle of flashing that my phone rebooted itself and stayed there (bootlooping at the google logo) I can get into fastboot and I can get into recovery about one out of every ten times but I cant do anything in recovery because the phone turns itself off insted of booting recovery most of the time (I have clockwork touch) When I do get into recovery without it turning off it reboots if I try to flash anything. It seems to be stable in fastboot (thank god!) but When I get it connected in Wugs Root tool kit and try to flash the stock image it goes through the motions and says FAILED on every step exept the first (which I believe is checking radio). It says ( error too many links) on the first two) and I cant remember the error on the last four but I have tried it a couple times so I can replicate it if needed. Can anyone tell me what to do from here? I really appreciate in advance!!! If this is a hardware error then I would like to get it back to stock to get it replaced. It is weird that it happened while running a rom. Its not like I messed up while flashing or anything.
ADB will recognize it in Fastboot. I already set all of that up when I rooted. when I try to flash the stock+unroot option on wugfresh's toolbox it errors out on every step like there is something wrong with my internal sd on my phone? Im wondering if I should try odin. IDK? Im hoping somebody who has seen this or had this happen before will save the day and tell me what to do.
lol why did you rush into CWM and start wiping things? you should have let it reboot and it probably could have been a one off..
you can try this http://rootzwiki.com/topic/14145-od...actory-odin-restore-402-with-radios-unrooted/
It is stable in fastboot but in cwr it is still geeking out
It still is glitching in cwr. most of the time it either turns off or reboots when I try to go into cwr. i can wipe but if I flash anything it freezes at the point where it starts writing to storage. I have never seen anything like this before.
I have now tried oden as well
It looks like it is a problem with the hardware. The phone is only a couple months old if that. So I really wish I could flash the stock image or at least get rid of cwm. but that is not looking likely. Here are a couple pics of odin showing the problem. Any guidace would be much appreciated. This SUCKS
Why in the heck are you trying to use Odin?
I can only get into fastboot and odin.
CWM wont let me do anything. it crashes and reboots into a bootloop if I try to flash anything. The poster above suggested odin. I dont know what else to do. Please help if you can!
Can you get a screencap of when it fails fastbooting the stock images?
yes
yes, give me couple min and I will post it. Thank you!
I guess I cant. This is all I get now
drumdestroyer said:
yes, give me couple min and I will post it. Thank you!
I guess I cant. This is all I get now
Click to expand...
Click to collapse
How are you attempting to access fastboot?
Vol + and Vol - and power all at the same time
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
That screen says you (now) have a corrupt partition.
At this point, you must use Odin, which is unfortunate. What URL did you use to download the image? The current image in that thread was on multiupload.
drumdestroyer said:
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
Click to expand...
Click to collapse
during my rooting attempt I had a problem with the two vol buttons. It was quite frustrating. Keep trying them and try pressing the power button a fraction of a second sooner.
I downloaded the one later in the thread
Here's the Modem: http://dl.dropbox.co...15.EK02_LTE.tar
Here's the System: http://dl.dropbox.co...L53F_signed.tar
from this thread on page 3 housry23 posted them from his dropbox:
http://rootzwiki.com/topic/14145-od...restore-402-with-radios-unrooted/page__st__30
there were a couple other posts right around the same time with it but they all were the same file name
I thought I saw the same files in the xda thread i found also
I used that thread because it is the one that the second post linked for me.
drumdestroyer said:
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
Click to expand...
Click to collapse
Send it to me. I might be able to fix it. PM me.
Sent from my Galaxy Nexus using xda premium
loveubuntu said:
during my rooting attempt I had a problem with the two vol buttons. It was quite frustrating. Keep trying them and try pressing the power button a fraction of a second sooner.
Click to expand...
Click to collapse
no luck with that. it seems to only open to the "corupted partision" screen. Thanks for the suggestion.
ljwnow said:
Send it to me. I might be able to fix it. PM me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I pm'd you to ask how you could fix it. Just wondering if I could do it. I can follow instructions well. I have never had a problem and have been flashing stuff for a year or so. IDK what happened here.
I can't help but I wanted to share that I had a similar experience. I was bonne stock and clicked on a you tube video and my phone immediately shut down and tried to reboot itself, but only would boot loop. I had to manually reformat my partitions to recover. Sounds like your case might be even worse. Still don't know what my problem was.
Sent from my Galaxy Nexus using XDA
Thanks. Any feedback is appreciated.
so you can't get into bootloader or odin screen any more? if so try using a Jig it works to get the phone into odin mode for me. i used the same usb jig i made for the captivate.
I got the same suggestion from someone else. I have to wait until radio shack opens in the morning and I will give it a shot. Otherwise, I went by verizon and they are having samsung send me a replacment. I would much rather keep this one if I can though
I tried flashing the stock image from fastboot and it failed though when I could get there, and I also tried flashing the stock image through oden when I could get there and both failed multiple times so I don't have much hope. I think something broke.
I am headed to radio shack now. Be back soon with a answer as to wheather I can save my baby or not.
Hi everybody,
I'm so angry with my Nexus 7 (wifi 2013) because I just made it mess up.
Let me tell you how stupid I was.
First, I tried to root but it failed.
Second, I used 'Back to Stock' with 'Nexus Root Toolkit v1.7.2'. Finally, I got stuck at Google logo
I tried some solutions on the internet but it still unchanged anything.
Could you show me how to fix it, please?
Thank you so much.
This is the images of error that I got (I'm sorry I cannot insert image because I'm a new member of this forum, could you go to the link below to see more details?)
s1019.photobucket.com/user/namserious/media/Error_Nexus7.png.html
Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Restoring Successfully
sfhub said:
Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Click to expand...
Click to collapse
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg
How did you do that?
namserious said:
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg
Click to expand...
Click to collapse
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.
nexussucks said:
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.
Click to expand...
Click to collapse
If you didn't root the device or do anything else with it, you should be able to get into Recovery Mode and do a factory reset.
https://support.google.com/nexus/answer/2668187?hl=en
Even recovery doesn't work
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.
nexussucks said:
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.
Click to expand...
Click to collapse
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb
RenderBroken said:
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb
Click to expand...
Click to collapse
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
You could try re-flashing the factory image.
http://forum.xda-developers.com/showthread.php?t=2487757
Latest factory image build is JSS15R
https://developers.google.com/android/nexus/images#razor
nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.
Success
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:
nexussucks said:
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:
Click to expand...
Click to collapse
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Name change
RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username
nexussucks said:
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username
Click to expand...
Click to collapse
This is the price we pay for the cutting edge. Also , at least for me, this is part of the fun. Now I have a much better understanding of Android than if I did being an avg. user. I was thinking the same about the name change. lol
RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
Hey, know it's been a little bit but my nexus 7 says no OS in TWRP recovery. I tried flashing it back to stock but it doesn't work. The bootloader is locked and when I try to do anything manually it just hangs on stuff like erasing 'system'/cache etc... in fastboot. I have not been able to find anything to work. And when I try to fastboot oem unlock it gets stuck when i press volume up and power to accept unlocking it. I have tried different cables and another computer. maybe I should try a third computer.. Do you have any suggestions?
RenderBroken said:
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.
Click to expand...
Click to collapse
I know this is an old thread, but I'm having this exact issue. I'm just stuck on the google screen. I can get into the bootloader just fine, but not the recovery. I followed these directions. Flashed the factory image and everything. But I still can't get past the google logo. I've followed every bit of advice I could find on this issue and I can't seem to get it working. Any help would be greatly appreciated!
*bump*
Does anyone know what's going on? I've tried everything I could find. Multiple times. From the suggestions listed here to the WUG kit to this http://forum.xda-developers.com/showthread.php?t=2381582
Nothing is working. I goes through the reflashing successfully. The command prompt says that everything is done. And then it just gets stuck at the Google screen again. I'm at my wits end and have no idea what to try next. I know that because I can get into the bootloader still, there has to be SOMETHING that will work. But I just don't know. Any ideas?
is there a android L Developers Preview flashable zip? thanks
Sent from my Nexus 7 using XDA Free mobile app
Anyone figure out what is causing this? I got a remanufactured 2nd Gen N7 16G yesterday. Updated to 4.4.4 over the air. Then unlocked the bootloader and rooted. Everything went fine. I installed Franco's latest kernel (r17) over stock and all was well. However, this morning, while using the device in the middle of GoW, it rebooted to the Google Screen and froze there. I could boot into the bootloader and have my comp recognize the device, so could ADB and Fastboot, however, I could not get into recovery. (I had installed TWRP 2.7.1.1 when I rooted). Trying to get into recovery would just freeze at the Google Screen.
So, I then tried both manually ADB'ing commands, as well as using Wug's Toolkit, and both methods seemed to complete successfully without error (I was using the latest Razor-Flo 4.4.4 files from Google's Dev Page so it is not an issue where I am using the Gen 1 files for Grouper or anything like that in error), however, neither method allowed me to boot into recovery, and left me at the same place. No matter what I did, I was stuck at that screen. I ended up calling Asus to RMA.
So, while it is not a current issue for me, I am interested to know if anyone has sorted what the root cause is, and whether it is an issue on the hardware side. I am not a complete noob to the N7 (I have 2 Groupers), and have been modding for a few years on Samsungs, and until this morning, have never had a soft brick I could not fix. This time, I gave up.
Same problem here, I have a Deb 32g, it went a little wonky and then rebooted. No amount of flashing and wiping and fastbooting has been able to recovery it. Gets stuck on Google Logo no matter what I do. Can't get recovery. Can't boot past Google. It will do fastboot without errors, but that's the only thing it will do.
Last night I installed geefree on my phone from the app store and used it to install TWRP. I downloaded a nightly CM11 and an appropriate gapps. Using geefree I rebooted to recovery (never figured out the button combination to boot to recovery "naturally") and installed both of the zips. This could be where I made my mistake, I installed both at the same time.
Now my phone loops, displaying the LG logo for a few seconds, then shutting off and rebooting before repeating the process. I can't seem to get it to go into download mode or the recovery menu. I've tried power+up, power+down, down+up and each of those while plugging the device in, etc. I can get the device to a hardware key control mode, though it doesn't seem too useful.
How can I save my phone? This forum has been a great resource in the past and I'm very grateful for the many tutorials I've followed rooting other devices. Hopefully you guys can save the day once again!
Volume up plus power is how to access recovery on sprint.
What stock sw version were you on before you flashed cm?
Did you wipe data before flashing?
Sent from my LG-LS970 using xda app-developers app
I was using stock 4.2.2, I believe. I didn't wipe the data (shame on me), a bad habit that I picked up from my first rooted device, the Samsung Moment. It didn't ever matter on that one, afaik. Thanks for the reply!
Edit: Volume up and power whether plugged in or not takes me to the hardware key control mode screen.
Second Edit: http://forum.xda-developers.com/showthread.php?t=2432476&page=35 I also found this thread where someone seems to be experiencing similar issues and they fix it with "LG Utility." Is that a PC application? It's a little vague to google, but I've been trying!
I have a bootloop issue every time i flash a rom i have to wipe all but sd flash roms and gapps the i do a restore from twrp and oly restore my boot image only and they boot no prob
I'm kind of starting to suspect my power button doesn't work at all for whatever reason. I have a lot of difficulty getting the phone to shut down, then it doesn't seem to easily power up. It's a strange collection of problems. Would a Sprint repair place be able to fix this?
If they have parts on hand if not either a swap out or a sendoff
Same problem here - bootloop and no download mode - CWM works! - urgently need help
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Device is recognized but can´t be mounted - bricked forever?
Parinibbana said:
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Click to expand...
Click to collapse
I tried a few things on Linux.
After terminal-command "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
So sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
Does it mean that the phone isn´t mounted or what? Now I´ve connected my phone to another Linux machine with the same result. It is recognised (p.e. as sdd), but there is no sdd1. Seems as if it is recognized, but can´t be mounted. Does that mean my device is bricked for good? That´s it?
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb into the phone first then hold VOL+ and plug into usb port on the computer.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, it will shut off eventually!!
plug the phone in while in download mode to install drivers and set com ports, then unplug before you begin your flash with LGFlashTool, hope this helps you out.
Cronic2009 said:
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb in first then hold VOL+ and plug into usb port.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, hope this helps
Click to expand...
Click to collapse
Thanks Cronic2009 for your advice.
There are, however, szenarios where download-mode is not accessible any more. Neither by using the hardware-keys, nor by using the adb-command.
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of that thread: http://forum.xda-developers.com/showthread.php?t=2451696
Worked like a charm.
Thanks everyone for your advice.
no problem buddy, glad you got it figured out, good luck to you from here on out!
FYI, that link doesn't work
I just wanted to ask anyone who might know, since the bootloader of the LS980 is locked, we cannot "break" this correct, so no matter what commands we decide to run through root, we cant touch the true bootloader there for LS980 fail safe? (Besides Acts of God, EMP, ect)
Cronic2009 said:
no problem buddy, glad you got it figured out, good luck to you from here on out!
Click to expand...
Click to collapse
Thanks for letting me know. I corrected the link in my previous post.
Be sure if you use a aosp based rom to flash the ZV8 modem. Your can use dr87 or furnance kernals after you flash the zva modem althought i have encountered soft brick due to this.
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
pitbullmommy45245 said:
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
Click to expand...
Click to collapse
Thank You for sharing you fixed your issue pittbullmommy but the link you posted points back to a post about a failed run on LGFlashTool, will you please fix the link and point it to the post/guide you used to fix your phone, it may help others stuck in a similar situation, glad to hear you got it fixed and working, best of luck with it from here on out!
Hi all
was just about to start a new thread but didn't want to get into trouble..anyway I am in need of some assistance please.my ls980 has been bricked for some time now been searching all over the internet for a solution to be stuck back at square one.found this video on youtube which is pretty much exactly what my phone is doing.I have used lg flash tool to revert to stock and still nothing I lost root doing that but last night,I managed to regain root access I have no idea how but it happened when i clicked ioroot batch file i went into download mode and it stated bottom left ROOTED in red so i managed that but that is it still doing what is being shown in the video its on youtube
watch?v=PjLF-pBhZSY
please if anyone has the know how I would like to fix this phone rather then bin it thank you all happy 4th everyone
After using tot and flash tool to get back to stock, did you try going into stock recovery and do a factory data reset? I know it sounds stupid especially after a tot but try it. Couldn't hurt
Sent from my LG-LS980 using Tapatalk
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Yes sir I've tried that and more to no avail is there anything I can do through adb I'm on stock recovery phone doesn't stay on long enough to install anything
sarfdawg said:
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Click to expand...
Click to collapse
You ever get her fixed?
My pixel xl(1st gen) purchased from Google store in Jan 2017, and in bootloop a week ago.
I contact google support, they told me my device out of the 1-yr warranty, and redirect me to UbreakIfix for repair, cost on myself.
I contacted UbreakIfix, get a quote for 300+ to change motherboard.
As of today, the Pixel XL only worth $130 trade-in value, and the condition need to be perfect.
So clearly I won't spend $300 to save a device only worth $130.
About the issue, I had some level of experience with fastboot/adb command:
* tried re-image all latest Google Stock Image of Android 7/8/9 individually with boot-loader unlocked, no luck;
* tried adb sideload ota image of Android 7/8/9 individually, with boot-loader locked/unlocked, no luck;
* tried change active slot to a and b with combination of above two items, no luck;
* checked the recovery logs, the boot-loader did take whatever Android stock image I feed to to it, and I do almost every time can get in to both boot-loader or recovery-mode successfully, and has no limit to run any fastboot/adb commands, but these are all I can do, and still not to get the phone boot into Android OS.
* in a very few times, the static "Google" in the white screen did spinning into a big rainbow "G", but it was frozen right after, and eventually reboot again.
I don't know if it worth spend more time on it, and feel very frustrated about spending my time on this doomed device and dealing with the Giant company as a individual customer.
I am not a picky guy, I accept the device running slow, or buggy sometime, but doesn't accept it dead in 2 years as a premium phone.
What do you think, guys?
By the way, many thanks to XDA forum, I learnt a lot from many brilliant and kind people here.
It's not acceptable, but it's the norm. Look at buying a new tv - Some mfg warranties are like 90 days labor and 6 months to a year on parts...It's a shame you pay all that money for something that could be a paperweight in a year.
Acceptable for a phone, or any gadget worth $800 to die in 21 months? LMAO. If this acceptable to some group of people, please redirect them to the best psychic facility available on this planet.
Like you said, you can just grab another one for $130. Phones are put through a lot and used every day so it's hard to say. Lots of people have no issues for several years.
Sent from my Pixel XL using Tapatalk
lafester said:
Like you said, you can just grab another one for $130. Phones are put through a lot and used every day so it's hard to say. Lots of people have no issues for several years.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I used my Pixel as a regular way, never root it, never even boot into bootloader before the bootloop issue, always use ota in os to get update. No water spilt, never get drop or hit. In another word, I never "abuse" the phone, and the phone has no accident.
Yeah, whatever, for the phone issue, I'm just having bad luck, like you said, many people have no issues. What I upset about is a $800 phone became a brick within 2 years with a normal usage, and Google not even give this case as an exception to cover it out of warranty.
You may say, or like Google said, then what the warranty stands for, right? I say, if only a few people got this issue, then as a Giant company, should cover since no fault on customer, and it would be a small cost to Google; if a lot of people got this issue, then still Google need to cover, since it becomes a general issue to this phone, which indicates this is a failed model at all.
Please don't think I'm a cheap guy, and trying to take advantage from Google, just trying to think the logical here. BTW, I'm not just complaining Google without putting in effort to solve the issue by myself, I did a little bit research and pickup learning, regard this issue, I'm not alone, many other users have the same issue as well, some of them get it "resolved" by reimage, but the other just has no luck like me.
You don't have to agree with me, I'm a kind of guy would love to discuss with people no matter they have same point view as mine or not.
What is the actual problem with the phone? You can get into the boot loader screen then correct? When you try to install the latest stock factory image from Google with fastboot what happens?
Phalanx7621 said:
What is the actual problem with the phone? You can get into the boot loader screen then correct? When you try to install the latest stock factory image from Google with fastboot what happens?
Click to expand...
Click to collapse
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Lei.SHI said:
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Click to expand...
Click to collapse
I'm having the exact same issue and Phalanx7621 tried helping me out but unfortunately it looks like there's no solution for it.. Just like your issue, everything successfully flashes, but I got a little past the Google logo a couple of times, but no more. My phone wasn't dropped, never wet, nothing at all. Yesterday morning I woke up and the screen was just black and it started boot looping.
Funnily enough, 2 weeks after I paid the phone off. 1 week after Verizon called to let me know they had open enrollment on their insurance plans and I turned it down since, yanno, I don't mistreat my phone.. "Coincidence" I guess..
My post btw https://forum.xda-developers.com/pixel-xl/help/possibly-bricked-t3861057#post78033420 if any of that helps you hopefully.
That is the weirdest thing. So everything flashes and it reboots like it's going into the operating system and then just reboots in a boot loop? unless someone else times in its possible is a hardware failure.
Lei.SHI said:
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Click to expand...
Click to collapse
Phalanx7621 said:
That is the weirdest thing. So everything flashes and it reboots like it's going into the operating system and then just reboots in a boot loop? unless someone else times in its possible is a hardware failure.
Click to expand...
Click to collapse
I've made it far enough in to setup my device, receive and send a text message and then it will completely freeze up for a few seconds and restart. Then it may or may not make it past the Google logo, usually it'll stick on the Google logo or the G before freezing and restarting. But one out of every dozen or two restarts it'll load all the way into the OS before freezing and restarting after a few minutes.
premedicated said:
I've made it far enough in to setup my device, receive and send a text message and then it will completely freeze up for a few seconds and restart. Then it may or may not make it past the Google logo, usually it'll stick on the Google logo or the G before freezing and restarting. But one out of every dozen or two restarts it'll load all the way into the OS before freezing and restarting after a few minutes.
Click to expand...
Click to collapse
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Phalanx7621 said:
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Click to expand...
Click to collapse
Sure. Gimme a couple minutes and I'll report back
---------- Post added at 08:15 PM ---------- Previous post was at 07:40 PM ----------
Phalanx7621 said:
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Click to expand...
Click to collapse
So it loaded up TWRP, then I remembered that I didn't set a pin after the latest reflash. So I went into software and setup a pin and moved the TWRP files over onto the phone as well as the kernal before it restarted. But now I can't get 'fastboot boot twrp.img' to actually load TWRP on the phone.. Command prompt says "downloading boot.img, booting, finished. And then on the phone it loads up the google logo and then just freezes and restarts.. I'll dink with it some more and see if i can make it work
Yeah you don't want a pin or password in TWRP. Any pin or password would've been erased with the wiping we did via fastboot earlier before we installed the newest factory image.
Phalanx7621 said:
Yeah you don't want a pin or password in TWRP. Any pin or password would've been erased with the wiping we did via fastboot earlier before we installed the newest factory image.
Click to expand...
Click to collapse
Alright so I guess I'll wipe everything again, then get far enough into the software to pull TWRP and the Kernel over? Or is there a way I can do all that from fastboot?
premedicated said:
Alright so I guess I'll wipe everything again, then get far enough into the software to pull TWRP and the Kernel over? Or is there a way I can do all that from fastboot?
Click to expand...
Click to collapse
If I were you I would wipe everything with fast boot and flash-all.bat again. See if you can get it to boot up once into Android, then reboot to the bootloader, fastboot boot TWRP.img and from TWRP because it's connected to your PC it will allow you to transfer files. download The flash kernel on your PC and just transfer it over to your phone and flash it, then reboot into Android to see if it works. But be careful whenever you reboot for the first time from TWRP because it will ask you to install TWRP as a system file or something. make sure to always hit do not install because if you swipe it will install it. That can definitely mess things up.
Phalanx7621 said:
If I were you I would wipe everything with fast boot and flash-all.bat again. See if you can get it to boot up once into Android, then reboot to the bootloader, fastboot boot TWRP.img and from TWRP because it's connected to your PC it will allow you to transfer files. download The flash kernel on your PC and just transfer it over to your phone and flash it, then reboot into Android to see if it works. But be careful whenever you reboot for the first time from TWRP because it will ask you to install TWRP as a system file or something. make sure to always hit do not install because if you swipe it will install it. That can definitely mess things up.
Click to expand...
Click to collapse
Well, knock on wood, I'm about 10 minutes into it and it seems to still be working.. But earlier it was on for a good bit of time before restarting as well. I'll report back!
premedicated said:
Well, knock on wood, I'm about 10 minutes into it and it seems to still be working.. But earlier it was on for a good bit of time before restarting as well. I'll report back!
Click to expand...
Click to collapse
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Phalanx7621 said:
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Click to expand...
Click to collapse
Done, done and done.
I flashed TWRP through the zip, so it's a more permanent fixture. Magisk is installed as well as the kernel adiutor. What type of data/info am i looking for through the kernel program?
---------- Post added at 11:19 PM ---------- Previous post was at 10:47 PM ----------
Phalanx7621 said:
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Click to expand...
Click to collapse
Apparently i didn't knock on wood hard enough. Was working for a solid 45 minutes to an hour, but then as I was reading through some stuff it froze up and went back into boot looping..
premedicated said:
Done, done and done.
I flashed TWRP through the zip, so it's a more permanent fixture. Magisk is installed as well as the kernel adiutor. What type of data/info am i looking for through the kernel program?
---------- Post added at 11:19 PM ---------- Previous post was at 10:47 PM ----------
Apparently i didn't knock on wood hard enough. Was working for a solid 45 minutes to an hour, but then as I was reading through some stuff it froze up and went back into boot looping..
Click to expand...
Click to collapse
No! OMG I'm sorry man. I thought we had this problem on its way to being solved. So it's now boot looping again ? Same exact thing as before ?
Phalanx7621 said:
No! OMG I'm sorry man. I thought we had this problem on its way to being solved. So it's now boot looping again ? Same exact thing as before ?
Click to expand...
Click to collapse
Well here's the deal.. Right after I posted that it started bootlooping again. It went through about 6 bootloops before I said 'eff it' and then just plugged it into the charger and walked away. I came back to it a little bit ago and according to the Kernel manager, it has an uptime of an hour and 32 minutes. So I grabbed it and was dinking around for a minute with it. Downloaded hulu, no problems. Downloaded netflix, no problems and then I was writing out a text and all of a sudden it froze and rebooted. Bootlooped once, then on the second try it started up. It's been up for about half an hour now.
Are there some sort of .log files with Android that could possibly show exactly what it is that's causing it to restart? Maybe something in the Kernel manager could help?