Related
Hello guys,
I had my Nexus 7 2013 (Wi-fi) for almost an year running stock rom and I decided to install CM12+ElementalX. It was all good untill yesterday when I returned it back to stock 5.0.2. When i started the tablet a message popped about 5.1 update and I started the update, but in the middle of the process it said "ERROR". I rebooted the device and now its stuck on the screen where you have to choose your language, with two errors constantly popping up - "PHONE HAS STOPPED WORKING" and "NFC Service has stopped working". I press OK like mad trying to skip some of the steps,but the "touch and go" (i think thats the name) is as far as i can go.
Is there any way I can flash the stock 5.1 without USB Debug Mode. There is no way i can get in the tablet's menu. I also saw some of the othere topics with this kind of problems, but i didn't find the answer.
You don't need USB Debugging to flash the factory images... use fastboot.
Telyx said:
You don't need USB Debugging to flash the factory images... use fastboot.
Click to expand...
Click to collapse
Can you please explain with few steps. I tried everything and i don't know what am I missing
P.s. I dont have custom recovery and i cant turn debug mode on
Ramirezz27 said:
Can you please explain with few steps. I tried everything and i don't know what am I missing
P.s. I dont have custom recovery and i cant turn debug mode on
Click to expand...
Click to collapse
I have installed ADB i Android SDK. Everythink is working fine on my Nexus 5 , but i cant do anything with my Nexus 7 which is now constantly rebooting after i managed to go through all the starting steps , when it started to install my 36 apps it rebooted by itself and now it keeps doing it.
i am having similar issue. i have tried the root tool several times with no success. ive been rooting devices since the samsung moment and i cannot get this tablet going at all. with the root tool i am able to flash twrp recovery, but for some reason it will not mount to put a rom on the internal memory. i have even tried pushing a stock rooted rom through adb fastboot and it just hangs. what else can i possibly do? could it be hardware related? this all happened after i was prompted for the latest 5.1.1 update. any tips or suggestions would be greatly appreciated. tia
Hey all, Before I start, ive searched and search and have not been able to find the solution.
I have my LS980 which was rooted. I learned about the zvg upgrade and tot back to stock zve.
Then I accepted the OTA to zvg and all was good so for I was at total stock ZVG.
I searched how to root and I tried the one click root method but something in the script would pause at the waiting for device...
so, I uninstalled all my LG drivers and root programs, Rebooted my computer and then made sure my phone was enabled debugging.
I then ran the LG root script v1.2, the program ran through without any problems. I entered download when it prompted me to and the phone was immediately detected and the su script continued. I left everything connected until it said don! then the control c and n to reboot.
This is the problem now, when the phone reboots it stays at the LG splash screen and the led alternates colors slowly. I cant get it into download mode but I'm able to boot back into stock recovery. I've tried to reboot system repeatedly for 4 or 5 times in a row (hoping something will change and let it boot), but nothing the longest I've left it at the LG screen is 45 minutes. I'm getting frustrated with this, Im really want to get this update rooted. So far the only way I can get the phone to boot is to side load the zvg ota update from stock recovery. can anyone tell me what I need to do to get past my last step and get rooted boot stock zvg?
thanks in advance. I usually can find all the information I need on xda but im stuck on this one.
Is zvg actually taking? I know with the GUI version. It would progress to 90%get stuck and never proceed. Them I would wait 5 minutes. Disconnect and reboot phone. I would have root
I can't tell.. The script run all the way through but i have yet been able to boot. It keeps hanging at the lg screen. Like i said ive waited up to 45 minutes on this state then from the screen I'll just adb to recovery and side load stock zvg update. To get the phone to boot but no root.
When the phone boots back up do you verify you are on zvg. Have you tried re-installing 1 click root for windows. Just in case
Yes I'mback on zvg, because since i can't get the phone to boot i have to adb to stock recovery and sideload the zvgupdate.zip. and then reboot I'm still on stock unrooted zvg.
jcsheriff said:
Yes I'mback on zvg, because since i can't get the phone to boot i have to adb to stock recovery and sideload the zvgupdate.zip. and then reboot I'm still on stock unrooted zvg.
Click to expand...
Click to collapse
Are you able to use the 1.3 version.
The problem i had with 1.3 was that it would hang after waiting for device.. So fast is why i went with 1.2.
I'll be home in a little bit and try the 1.3 Again, because i still had the problem when i switched to 1.2.. Until i deleted and reinstalled all drivers and root programs. I'll Report back
jcsheriff said:
The problem i had with 1.3 was that it would hang after waiting for device.. So fast is why i went with 1.2.
I'll be home in a little bit and try the 1.3 Again, because i still had the problem when i switched to 1.2.. Until i deleted and reinstalled all drivers and root programs. I'll Report back
Click to expand...
Click to collapse
From phone on, with USB debugging on. It should show an authorization key. Select always and OK. It will copy files over and day rebooting to download mode. That will fail. Unplug phone. Shut off. Hold volume up connect phone. The rest will go to 90%. Wait 5 minutes. Reboot phone to system.
I appreciate your advise.. I just deleted and reinstalled the lg drivers again and then ran v1.3. I got the same result..out loads the files then fails at reboot. I discover the phone and reboot to download mode then reconnect. Then i wait and wait..i hear the computer recognize the device but i continue to wait 20 minutes and nothing. I tried it several times with the same result. I then reinstalled the lg drivers uninstalled v1.3 and executed 1.2 when prompted to put device in download mode the device was connected/recognized after about 10 minutes out shows all the files installed and expanded then instructs me how too exit then reboot. I disconnect reboot and waited another 30 minutes.. Still nothing..so once again i adb to stock recovery then sideload the zvg update. Then the phone boots but still no root.
jcsheriff said:
I appreciate your advise.. I just deleted and reinstalled the lg drivers again and then ran v1.3. I got the same result..out loads the files then fails at reboot. I discover the phone and reboot to download mode then reconnect. Then i wait and wait..i hear the computer recognize the device but i continue to wait 20 minutes and nothing. I tried it several times with the same result. I then reinstalled the lg drivers uninstalled v1.3 and executed 1.2 when prompted to put device in download mode the device was connected/recognized after about 10 minutes out shows all the files installed and expanded then instructs me how too exit then reboot. I disconnect reboot and waited another 30 minutes.. Still nothing..so once again i adb to stock recovery then sideload the zvg update. Then the phone boots but still no root.
Click to expand...
Click to collapse
Question, when you connect in download mode and it just sits there. Go to device manager and check com port. Maybe it is connecting to the wrong port.
I think mine originally connect to port 41, when it should be 3.
I've verify the port assignment and I've tried port 3 port 4 and port 41...but the scripts always find the device and identify the port as Whatvi have assigned it to. I've even tied several other computer some running win 7 and others running win 8.1
I just read someone else's post that they were having problems but fixed with newer lg drivers, that his were old.
I noticed I've found a few variations of the driver. Any idea of link to the most current one?
finally rooted
Tekone said:
Maybe you should try this method. Restore to ZVE and rootz it with Lg one click v1.2. Once you confirmed it's rooted, then adb sideload on stock recovery to upgrade to ZVG. When you upgraded to zvg, try the Lg one click root v1.2 again Usually, that Lg One click root v1.2 will stuck on and take awhile, but it did it's job. Also to change the port number after used the LgFlashtool. Alot time, the port 41 don't work with Lg one click root.
Click to expand...
Click to collapse
This worked flawlessly for me. However once i rerooted after sideload. When the script ask you to put the phone inn download mode.. I saw the su script push but the machine appeared to stop working. I left it connected and waited 25 minutes to make sure all was good. Then i pressed and power button and held it down until the phone reset. The script showed complete and the phone booted all the way through. It did take about 10 minutes to boot, then super user was installed and i was rooted.
Hello, I managed to soft brick my phone while overseas and am writing this message at 2:00am in the morning (at least in this time zone) after two days of trying to fix it. Some background info--I'm usually based in the U.S., have a Samsung Galaxy S6 edge+ with service from T-mobile. Have never rooted or modified the phone in any way. I'm using a macbook pro laptop (running a windows virtual machine/vmware, on the mac) on this trip.
While on this current trip to Asia (currently in the Philippines) (much to my surprise it seems like the phone was getting 4G data here), I accidentally bumped the "yes" button on t-mobile's persistent OTA upgrade request box and the phone started a OTA upgrade, I assume to Android 6.0.1. I kept an eye on the phone as it went through various stages of progress in the upgrade. didn't see any error messages. It eventually restarted, got to the T-mobile screen, and got stuck there. That was two days ago. I've done quite a bit since that time to try to figure out what went wrong, searched all over online to find potential solutions. it goes without saying if there is any way possible i need to recover many important files on the device, so a reset is the option of last resort.
Long story short, seems like the farthest I can get on the phone is to Android Recovery mode, or the download screen. I installed the android tools and have "adb" working from the mac command line. Bad news is, it looks like I didn't have USB debugging mode activated on the phone, now I can't see any possible way to activate usb debug mode because the phone just won't boot past the t-mobile screen. I can get adb to detect the phone for a moment if I select "apply update from adb" on the recovery mode screen but that's about it, haven't been able to issue any other commands to the phone through adb other than detect and sideload.
tried to reload the android image...via command line adb sideload G928TUVU2DPD1 but get error messages about failure to verify (i think), anyways adb sideload wasn't happening. I installed Odin on my windows VM, attached the usb bridge from the mac to the windows vm and Odin was able to see the device. I was able to successfully push G928TUVU2DPD1 to the phone's download mode, both Odin and phone seemed happy about the file transfer, the phone went through a install process, restarted, with the exact same result as when the OTA update finished - phone stuck at the t-mobile screen after reboot.
I tried to load TWRP to the phone with hopes to run backups, and was actually able to transfer TWRP to the phone using Odin, yet TWRP wouldn't install -- the phone complained of the unauthorized binary. i guess the phone has to be rooted first or something else needs to be flashed to defeat the binary check, haven't tried that yet.
So I'm stuck with a soft bricked phone for now, yet instinct tells me with Odin working and talking to the phone, I should be able to install -something- that will get me back in business...that's why I'm posting this message, to ask for help as it seems like this group is the go to place for this type of specific info.
i am not at all familiar with custom android work yet have been active with tech stuff for the greater part of my life, plenty of coding and experience dating back years and have done dev work in most of the popular languages, very comfortable with command lines, log files and so forth...just never had a reason to mess around at a low level with my android phone until the past 48 hours, so i'm not really familiar. does anyone have any ideas? as a next step i'm thinking of trying to push a downgrade to the phone through Odin which I suppose would be Android 5.1.1 , although I haven't yet located binaries that feel exactly right for t-mobile and s6 edge+ ... sigh, this has been quite a time consuming way of learning the bricked phone recovery process..
:good:
thanks in advance for any ideas or help on this...it's quite disturbing to be on a business trip with no phone, and the past 6+ months worth of not backed up (gulp) data still sitting on the device (hopefully)..
here's some data from the Android Recovery screen:
6.0.1/MMB29K.G928TUVU2DPD1
samsung/zenltetmo/zenltetmo
was flipping through the recovery logs and i notice quite a few log entries about "couldn't find any tzdata when looking for localtime!" , I notice entries like "Starting recovery on Fri Jan 2 03:55:29 2015" -- i'm wondering if the phone is having trouble setting internal time and date which might be preventing it from booting...just a theory.
sorry for the long message, wanted to completely describe this fun scenario, just in case anyone has any ideas..thanks again
keep trying to load TWRP from the download screen on my phone...but get the "custom binary blocked by FTP lock" message. There's no way to change any settings on the phone as it still won't boot past the t-mobile screen..
platinum5 said:
keep trying to load TWRP from the download screen on my phone...but get the "custom binary blocked by FTP lock" message. There's no way to change any settings on the phone as it still won't boot past the t-mobile screen..
Click to expand...
Click to collapse
Can you download Odin?
Sent from my SM-N910T using Tapatalk
yes i have installed Odin and it's working fine...I can push files to the phone in download mode and it works fine, but the Android images i have loaded so far all seem to result in the phone getting stuck at the t-mobile screen...it won't go past there
Did you ever get this figured out? My guess is it has something to do with not being connected to t-mobile home network. The fact you can get to download mode & Odin sees your phone should mean all hope is not lost yet on recovering your files and getting it working again.
Twrp isn't going to work unless you had root installed with the USB debugging & oem unlock option turned on in developer mode.
Maybe try asking in some of the other s6 forums. There's a lot of knowledgeable people here & I'm sure someone knows how to fix this.
Goodluck, I hope you get it figured out, I know how frustrating it can be.
I've been watching several threads for the last few days, and have not seen this exact issue. I would greatly appreciate some help.
Device:
- Nexus 5X LGH790 32GB
- Stock bootloader / fastboot
- Never unlocked / rooted / etc.
The only advanced thing I've done is join the beta program a few months ago to get 7.0 early. Got that without any issue.
Issue:
I received the 7.1.1 OTA on the day it came out. Installed with no problems. The next day, the phone just froze in the middle of regular use. After about 15 seconds, it started boot looping to the Google splash screen. I can hold volume-down to enter fastboot, but when I select recovery mode, it just starts looping again. Pretty much all I could do was power it off. I did find out by accident that if I left it looping for long enough, sometimes it actually loaded normally (I even saw beta program warning/notice). But when I tried using it for more than a minute, it would freeze, reboot, and loop again.
What I've already tried:
- I tried using the WugFresh NRT fix softbrick method. I was able to quickly turn on debugging one of the times that I left it to loop. But when NRT sent a reboot the phone, it threw it back into the loop and NRT stopped recognizing the device.
- I tried to follow the unbrick procedure using a TOT file in this thread: http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766 But even after using LGUP, I still cannot even get into recovery mode.
- I filed a bug in the AOSP here: https://code.google.com/p/android/issues/detail?id=225802.
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
DC_Knight said:
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
Click to expand...
Click to collapse
Try fastboot/bootloader mode and fastboot flash the OTA manually.
Update 2: Seems like all the other things I tried over the last few days have caused various unofficial USB drivers to be installed. I've tried uninstalling most of them. I downloaded the google USB driver from latest SDK. But my 5X is still recognized as a Kedacom device when it is sitting at FastBoot.
However, I must have made some progress because I was able to start the sideload process. Unfortunately, I am now stuck on yet another error. The phone hangs at "verifying update package" and then after about 2 minutes... it reboots itself and starts looping again!
I thought I had it. So close. Now I want to throw the phone. Going to sleep, but would be grateful for any other suggestions in the morning.
- DCK
use nrt to erase all partitions, then download 7.1 factory image, unzip and flash one by one the partitions.
DC_Knight said:
...
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Click to expand...
Click to collapse
Sounds like the boot loop issue many people have been having (the hardware/solder issue). It happened to me a few weeks ago after upgrading to Android 7.0. I got a replacement device from google.
If you're bootloader is locked, NRT or any other method to flash the factory image is not going to work. The only suggestion I have is to un-enroll in the beta program and hope your device will boot long enough to flash the ota Google will send the device to get back to 7.0. Note, this will wipe your device.
Sent from my Nexus 9 using XDA-Developers mobile app
Same problem here. It can't be recognized after I reboot to fastboot. So I can't flash anything.
If the device isn't recognized try this http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33. It's worked for a few of us with the same problem
Sent from my Nexus 9 using XDA-Developers mobile app
Enter stock recovery then flash the full ota via adb sideload
ORIGINAL PROBLEM:
Pixel XL 128gb VS, received this morning with 63L.
1) Enabled debugging and OEM unlock.
2) Took the update as everyone said 63V is ok. But it turned out to be 63X(?) (I am on VZW network but phone purchased directly from google).
3) Used adb to get into bootloader mode and unlocked bootloader, which reset my phone and started fresh.
4) Enabled debugging again, OEM unlock was greyed out this time.
5) Rebooted, a message popped up something like 'needs to be locked to verify update' then google screen with unlocked lock symbol in the bottom.
6) Robooted again just to test. Still showed same thing, everything else seems to be working fine.
7) went back into adb mode and did fastboot boot boot-to-root.img
8) adb said successful
9) Phone restarted and showed the screen with bouncing dots. That was 55-ish minutes ago. Nothing else happening, but the screen with jumping dots.
Anyway to fix it or am I screwed?
Edit: Just tried and see if adb recognizes it now, nope.
@n3far1us,
A lot of discussion on SuperSU thread about this, but few answers yet.
Here > http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156/page57
cam30era said:
@n3far1us,
A lot of discussion on SuperSU thread about this, but few answers yet.
Thank you @cam30era for sending me to the right direction. Did not realize I needed to look into SuperSU thread for this. I was searching in the wrong areas.
Click to expand...
Click to collapse
Same issue here
Same issues here after taking V update which completed then immediately flashed elemental kernel then rerooted which said ok now stuck on jumping dots for atleast an hour? Any ideas how to fix this I followed the directions of a dveloper on here and it screwed me!
QUOTE=n3far1us;69558628]Pixel XL 128gb VS, received this morning with 63L.
1) Enabled debugging and OEM unlock.
2) Took the update as everyone said 63V is ok. But it turned out to be 63X(?) (I am on VZW network but phone purchased directly from google).
3) Used adb to get into bootloader mode and unlocked bootloader, which reset my phone and started fresh.
4) Enabled debugging again, OEM unlock was greyed out this time.
5) Rebooted, a message popped up something like 'needs to be locked to verify update' then google screen with unlocked lock symbol in the bottom.
6) Robooted again just to test. Still showed same thing, everything else seems to be working fine.
7) went back into adb mode and did fastboot boot boot-to-root.img
8) adb said successful
9) Phone restarted and showed the screen with jumping dots. That was 40-ish minutes ago. Nothing else happening, but the screen with jumping dots.
Anyway to fix it or am I screwed?
Edit: Just tried and see if adb recognizes it now, nope.[/QUOTE]
@kirschdog1,
Follow the SuperSU thread that I referenced above.
On it now but it doesnt look like anyone has an answer for us!
cam30era said:
@kirschdog1,
Follow the SuperSU thread that I referenced above.
Click to expand...
Click to collapse
THE FIX
After about 6 hours of bouncing dots and trying out various things, @dowlf finally saved my life.
To recover the phone, I followed-
1) Boot to bootloader
2) Select 'Recovery' then once in recovery hold power and vol-up buttons for 5 sec then let go of the vol-up (but keep pressing power)
3) From there, choose Apply Update from ADB
4) Run 'adb sideload blahblah.zip' (mine was 63X OTA)
5) Choose 'Reboot system now' once copying done.
THE ROOT
After figuring out how to fix it, I immediately went back trying to root it again.
However, this time I decided to do more research and it appeared that I may have used an outdated boot-to-root.img which kicked off the bootloop. The first file was dated 10/31 and the second one I found was dated 11/03. I decided to try the 2nd one this time with "fastboot boot" command and voila!
My Pixel is successfully rooted on 63x!
Thanks to @Chainfire for all the hard work!
Oh and this is the link where I found the second file from-
https://plus.google.com/+Chainfire/posts/24xhJN724HG
Please help!
Guys I have a 32gb Pixel XL from Verizon, I unlocked the bootloader, and today I tried the boot-to-root and now i'm stuck on the bouncing dots, I've downloaded the OTA update, tried the flash-all script, didn't work, failed out at one part,
i tried sideloading the ota.zip and it said failed to sideload ota.zip and i'm FREAKING out i just bricked this phone...
PLEASE ASSIST. My phone is my livelyhood for my job and without it i'm screwed.
YankelMyWankel said:
Guys I have a 32gb Pixel XL from Verizon, I unlocked the bootloader, and today I tried the boot-to-root and now i'm stuck on the bouncing dots, I've downloaded the OTA update, tried the flash-all script, didn't work, failed out at one part,
i tried sideloading the ota.zip and it said failed to sideload ota.zip and i'm FREAKING out i just bricked this phone...
PLEASE ASSIST. My phone is my livelyhood for my job and without it i'm screwed.
Click to expand...
Click to collapse
Try flashing everything manually.
Sent from my Pixel XL using XDA-Developers mobile app
YankelMyWankel said:
Guys I have a 32gb Pixel XL from Verizon, I unlocked the bootloader, and today I tried the boot-to-root and now i'm stuck on the bouncing dots, I've downloaded the OTA update, tried the flash-all script, didn't work, failed out at one part,
i tried sideloading the ota.zip and it said failed to sideload ota.zip and i'm FREAKING out i just bricked this phone...
PLEASE ASSIST. My phone is my livelyhood for my job and without it i'm screwed.
Click to expand...
Click to collapse
Make sure you have the latest android SDK for adb and fastboot or it won't play very well
Sent from my Google Pixel XL using XDA Labs
alright, so i got stuck in ALMOST same situation, rooted my device got stuck on dots.
googled my problem and found this thread and found it more helpful, the only thing creating confusion is the OTA required.
got my device on 11th of this month and i guess started using it on 12th or 13th, and when i turned it on it asked me for updates and straight away i downloaded all the updates, but unfortunately i forgot to check what build number i was on.
so could you guys please help me out with the OTA version?
shall i go with the latest one?
and the rest is the same right?
like after sideloading the OTA file my device will be back to stock and unrooted ?
OKAY SO I'VE SOLVED MY PROBLEM BY JUST INSTALLING OTA WITH SIDELOAD COMMAND.
Thank you for the solution guys.