Related
Hey guys, looking for some assistance here as I am at a complete loss.
Decided tonight to root my 4.2.2 Nexus 10 using the Nexus Rootkit v1.6.3 and the aid of a YouTube video. All went swimmingly up until the TWRP wipe. The video I followed failed the wipe attempt and the guy showed how to get the N10 out of the bootloop and do a 'wipe data/factory reset' via Recovery Mode in the Bootloader and then restart.
Problem is, my wipe never failed like his did in the video (great I thought!) and so I restarted after that and now I find my N10 booting up to the Google Logo (with the padlock at the bottom) and it just sits there. Doesn't even get to the 'X' logo which should come after.
I've tried a few things including the manual wipe data/factory reset from the bootloader and restart but everytime it gets stuck at the Google Logo. I am also now at the point where my N10 doesn't show in Device Manager as it did before. It now shows under 'Portable Devices' as a 'MTP USB Device'.
I am really at a loss here and searching various solutions is just confusing me even more and would appreciate it if someone could help me out, even just getting back to stock for now. That's if it isn't goosed?
Thanks in advance
Have you tried using a different usb port on the PC, and rebooting the PC?
bigmatty said:
Have you tried using a different usb port on the PC, and rebooting the PC?
Click to expand...
Click to collapse
I have yeah. Left my PC off overnight and went back to it again this morning and same issue.
Plug it into the PC (this time using a USB port on the back) and it initially comes up 'installing device driver software' quickly followed by 'device driver software was not installed successfully', quickly followed by 'installing device driver software' again and that's when it shows up in Device Manager as 'MTP USB Device' under Portable Devices, whereas before during the root attempt it was show as 'Nexus 10'.
When I first read the subject line I thought it was "another one of these" where OP hadn't searched on the existing boards. But when I read OP I see you did try "the usual suggestions". Hoping a more seasoned pro jumps in here to help...
I can say that on the handful of "really bad" posts like this that I've seen they usually end with the person saying something like "well I don't know what happened I just kept trying all the power button / charge recommendations and finally it worked" - so don't underestimate the effectiveness of repeatedly trying it like a mad man!
Some random suggestions I have that may help:
-Can you leave it on, on the Google screen, to where the battery 100% drains, maybe this could act as a "battery pull"
-Try a different USB cord
-Try rebooting it via the power buttons while the device is plugged into the wall charger
-Download the Android SDK, then use its "update manager" to update its USB drivers to today's definitions
-Try another PC
Good luck!
Thanks for the suggestions bigmatty, I'll certainly give them a go when I get in later.
I think my biggest concern is that there doesn't seem to be any OS on it, possibly to do with the wipe during TWRP and then I rebooted - was I supposed to reboot at that stage? That's where I got into this loop. And now it doesn't detect it as 'Nexus 10' in my Device Manager on my main PC. Only this MTP USB Device - sometimes showing a conflict warning triangle, sometimes not and no longer showing as a storage device in My Computer.
I did connect it to my Netbook (Running XP) earlier and it detected it as an 'Android Device' under Other Devices in Device Manager. Tried installing it with the naked drivers on the Android SDK and it now lists it under 'Android Device' in my Netbook's Device Manager as a 'ADB Device' (I think, would need to double check as I'm not on it at the moment.)
I just want to find some way of getting it back to factory settings and stock OS if possible and then take it from there again. Don't fancy at £319 paperweight! I'm usually alright with these things too.
Thanks again (And if anybody else has any other input in the meantime I would be grateful - I'll try anything at this stage!)
I'd say its a good thing that the PC exhibits varying behavior - because that means there is still hope!
It really boils down to if you can open an adb.exe shell to the device. Can you? It would not be when its showing as MTP but it would be when its showing as adb in Device Manager. If you can then here is a thread where I explain (pretty good, I think) how to get back to stock:
http://forum.xda-developers.com/showthread.php?t=2185123
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
bigmatty said:
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
Click to expand...
Click to collapse
Can't really get into much on the Tablet itself. It boots up, gets to the Google logo (with the padlock symbol at the bottom suggest it has been partially rooted (?)). I can get into the Bootloader by holding down the Power + 2 vol buttons. Once in the Bootloader I have the options of Start/Power Off/Recovery Mode/Restart Bootloader.
When I go into Recovery Mode I can get access to the blue menu where I get the options to restart/something about adb/wipe data/factory reset/delete cache partition (paraphrasing here).
Don't know how many times I've tried the wipe data/factory reset option and reboot but always get sent back to the same loop.
I'll give you're other idea a shot as well later. Thanks again.
bigmatty said:
I'd say its a good thing that the PC exhibits varying behavior - because that means there is still hope!
It really boils down to if you can open an adb.exe shell to the device. Can you? It would not be when its showing as MTP but it would be when its showing as adb in Device Manager. If you can then here is a thread where I explain (pretty good, I think) how to get back to stock:
http://forum.xda-developers.com/showthread.php?t=2185123
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
Click to expand...
Click to collapse
bigmatty, you the man!
Managed to get back to factory stock following yours and styckx's guidelines. Couple of little teething problems along the way but nothing I couldn't get around.
I now have a fully functioning Tablet again and I thank you for it.
Might give the Rooting a miss for now but if I come back around to the idea I'll be sure to follow the guides on here this time instead.
Thanks a bunch again for taking your time out to reply to my thread and get me back up and running again. :good:
Scotman57 said:
bigmatty, you the man!
Managed to get back to factory stock following yours and styckx's guidelines. Couple of little teething problems along the way but nothing I couldn't get around.
I now have a fully functioning Tablet again and I thank you for it.
Might give the Rooting a miss for now but if I come back around to the idea I'll be sure to follow the guides on here this time instead.
Thanks a bunch again for taking your time out to reply to my thread and get me back up and running again. :good:
Click to expand...
Click to collapse
Awesome! Glad it worked out
A bit of an SOS situation if anyone knows the right steps please
Well, I restored a Titanium Backup and mistakenly toggled the "restore system apk". It ran fine, all restored and then when I rebooted got stuck.
By "stuck", it re-boots constantly. It shows the LG animation, then all I can see is two messages before it starts booting again:
1) "Unfortunately, Google Play Services Has Stopped"
2) "Unfortunately, System UI has stopped
... and then it does the entire boot sequence, animation, again, and again.
Here is what I can do:
* It is in USB debug mode.
* I have drivers on laptop
* I am able to connect with adb and also shell into phone.
* With adb, I have output to the file an "adb bugreport" as well as an "adb logcat".
* I have several backups:
a) The modemsst1.img and modemsst2.img created by Titanium Backup
b) Titanium backups (full apps and data)
c) an "adb backup - all" backup
* I managed to get it into firmware update mode by pressing the volume up button and the power button and then when it flashed red a few times, just the up button. So, I can get it into Firmware update mode.
Of course, I have never really used adb before, except to dabble a bit. So, I am encouraged that I can somehow get into with shell.
I am not unplugging it until I know what to do!
Since then I have been able to turn the phone off and also put it into charging on USB.
This is what worked:
* Hold down power and volume down button until booting stops and phone turns off completely.
When it does shut down, I kept buttons down until it flashes logo again and then shuts down again. Then I let go. Phone is off and when I plugged in the charger it shows charging animation.
Now, after inspecting the bugreport, I noticed a lot of these messages for all the system apps like this one:
"I/PackageManager(21318): Expecting better updatd system app for com.lge.sizech"
I think the cause of all this shralp is this, I did a LG Mobile Support Tool "Upgrade Recovery" and then in Titanium Backup I restored an older backup (incl system apks). At least that makes sense seeing all the "Expecting better apdat system app" messages in the bugreport.
Still not sure what to do next
I tried the very good instructions here:
[Guide] Unroot/Unbrick - flash official factory firmware with LG Launche
http://forum.xda-developers.com/showthread.php?t=2471370
The update succeeded. However, when I rebooted the phone it is in the same boot-loop with message that it was before.
I used the BELL D803B10D_00.kdz file. Now I will try with the earlier version BELL D803BA_00.kdz file.
We will see what happens ...
do you have nandroid backup from previous rom?
I have three backups:
1) Titanium Backup (full)
* This was my first backup performed right after rooting device and installing Titanium Backup.
2) Titanium Backup (full)
* Did this 2 days ago. Device was working OK and did as precaution.
3) ADB BACKUP. I did this one before my Titanium restore.
I restored the first titanium backup and that (ooooppps!) was after I did an LG Firmware update.
ALSO:
I am on Windows 7 64 and although adb works fine, fastboot does not. I understand that might be a problem with windows 7 64.
So, unless anyone objects, I am going to redo on my windows 32 machine and also "fastbook oem unlock".
Since firmware is OK, if I do the fastboot oem unlock, that will wipe everything. But I can still boot and re-setip the phone, right?
Just checking before I fudge everything up here ..
ALSO ALSO:
I had antivirus/theft security installed and I disabled it partway through last restore.
Maybe that has somethng to do with this all .
But I am still cool because I can ADB and also firmware install seems ok.
ADB works and that is the one good sign.
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
zekurosu said:
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I don't (didn't) have TWRP installed. How can I sideload without it?
Also, should I adb oem unlock to get it wiped at this point?
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
asdfvtn said:
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
Click to expand...
Click to collapse
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
I used adb uninstall package for many user packages and it was success. But I still see the packages listed in the bugreport?
For example: I already uninstalled "com.benhirashima.skiplock" and also "com.lookout".
Why? What to do to really zap them for good?
Sorry, I posted the wrong link earlier.
This was the guide I used which succeeded but made no difference to the boot-loop.
LG G2 Stock Firmware (Go Back to Stock)
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=d803
Just figured out how to do a factory reset.
http://www.youtube.com/watch?v=3ogBvzbPikc
The hard reset worked and now I am configuring the phone settings!
So, again, this is what I did:
1) http://forum.xda-developers.com/showthread.php?p=45293512
2) http://www.youtube.com/watch?v=3ogBvzbPikc
Not sure if it all worked but I am setting the phone up as we speak (or as I type)
natureburger said:
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
Click to expand...
Click to collapse
Hmm that's strange. Unfortunately for me, I'm already on 64-bit and it still isn't picking it up.
ALL FIXED UP
WORKING 110%
:good:
natureburger said:
ALL FIXED UP
WORKING 110%
:good:
Click to expand...
Click to collapse
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
zprovo said:
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
Click to expand...
Click to collapse
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Then .. do hard reset, exactly like this:
http://www.youtube.com/watch?v=3ogBvzbPikc
Does the hard reset screen show and give you hard reset options?
natureburger said:
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Click to expand...
Click to collapse
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
zprovo said:
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
Click to expand...
Click to collapse
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
4) Which kpz version did you restore to?
5) Did your "adb devices" ever work? Did your "adb shell" ever work?
natureburger said:
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
Click to expand...
Click to collapse
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
zprovo said:
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
Click to expand...
Click to collapse
Hmmmm..... why your adb devices is not working? But the re-pair works and you can then do hard reset.
But that is good information you shared.
Maybe someone else can chime in.
From my experience:
1) adb usb access seems spotty. My win 7 64 connected fine and it even kept the shell through the reboot cycle. But on my win 7 32 machine it was only detecting device and then not able to shell.
2) I was also able to use from the LG website LG MOBILE SUPPORT TOOLS.
Download the LG MOBILE SUPPORT TOOL
I downloaded the most recent one from the LG website and make sure to select your options >> country and then the correct phone model at the upper right hand corner of the tool.
Then install USB driver for correct phone model.
Then see if USB works, "adb device" should return the device code.
"adb shell" should show the shell prompt.
3) There is always fastboot. But I an noob and know 0% about how to properly connect and use it.
Some others please chime in and help this droid bro!
I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks
lejars1 said:
I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks
Click to expand...
Click to collapse
It is possible that your system and/or boot partitions have become corrupted.
If that is the case, you'll need to reinstall the ROM. The best way to do this is to install a custom recovery like twrp or clockworkmod, reformat your partitions, and proceed from there.
Hi - thanks for this.
I got it sorted in the end.
Here's a link to what happened.
http://forum.xda-developers.com/showpost.php?p=60970017&postcount=1597
Hello guys.
I have an LG L5 (E610) that is having a very strange behavior.
It started by throwing a lot of ANR with different applications (Google Play Store, Play Services, Facebook, and others).
So, seeing this, I decided to do a factory reset. After reboot, what is my surprise that I see everything as I had before. All the applications, all the data, everything.
With this, I tried almost everything at the moment. And by saying that, I mean:
- Tried to follow the key combination for the recovery, it goes to recovery, I see the Android and some progress bar moving, but after the reboot, the system remains with no change;
- When on the system, I uninstall applications, they seem to be uninstalled, but after a reboot all the applications are back.
- Tried to root the phone with more than one process, no success. I cannot install any application. Not via play store, not via adb install, there is no way;
- Tried to flash a recovery img, to try to clean cache partition from there, no luck. From Fastboot it says everything went well, but when I reboot, everything is the same;
- In fastboot, I tried to erase cache and userdate partitions, no luck. When I try, i have a message saying "FAILED (status read failed (Too many links))". This happens with all the partitions. I even tried to erase the system partition, and I have the same response. Strange thing is that after this error, the phone reboots and goes directly to the system;
- Tried with KDZ images and tools to install different versions, I receive errors during the deployment and at the end the phone reboots. Again, the same system is installed as before. No changes.
As of now, I was trying to understand if there is any problem with the internal flash system. Maybe it is corrupted and is causing all these issues.
The thing is, as the phone is not rooted, I cannot launch a e2fsck to the maybe faulty mmcblk0pXX
The phone has a stock ROM based on Android 4.0.3 (build IML74K / LG-E610-V10e-JUN-30-2012)
I am out of ideas, I've looked around here at XDA, Google and I have no other ideas to try.
Does anyone have another suggestion?
Is there something else I can do to try to make the phone live again?
Any help someone can provide will be very much appreciated..
Now this is what I call a coincidence.
About 2 years ago, a friend of mine asked me for help with her E610. Almost all actions were giving us ANRs. Whatever you do, i.e. unsinstall, install, change, delete... after reboot/reset were all there, even notifications! Tried KDZ updater, and, while the update was OK without signs of errors or so, after reboot - nothing, everything was like before. After trying to find a solutions by hundreds of ways, with adb and fastboot commands (all partitions&folders were locked, no read, no write, and you can't see any file, tried root to no avail), L5 got bricked. She already got a new phone and this LG was laying there without any use.
Three days ago I decided to try again, with no hope tbh No screen, no vibration, nothing, apparently dead. But, I could install Qualcomm drivers and my Windows can see it in download mode. I think that the only way is to flash the phone with LGFlashTool and using COM port. I already extracted *.dz from *.kdz but I need the dll for FlashTool. Found 2 or 3 webs with this dll, but you need a 100 bucks subscription :crying: If anyone can upload that dll I'd be very happy to try to flash this phone I'm really big n00b in this, just a plain phone user, nothing more, so don't blame me if I said something wrong
Many thanks in advance.
same problem
Hello! Same problem...
My L5 is making me crazy... It has CyanogenMod 10 nighlty. A friend of mine was using it and he tried to install the GAPPS after he did a factory reset. I have no idea what guide he used but it got soft bricked... It's constantly showing a "stopped working" message and after a while reboots by itself.
I tried to do a factory reset but it always returns to the same point, same apps installed, everything like the reset never happened. I even used CWM to reset it and it allways goes back to the same recovery point.
After a while I decided to flash a stock room but here's the problem: I can't get into emergency mode.
After reading ALL post about it I found that there's at least three ways of entering EM, (1) down VOL and plug in usb cable without battery; (2) down+up VOL and plug in usb; (3) down+up VOL + power botton.
Conclusions:
(1) - gives me a screen full of code like a command line
(2) - White screen
(3) - White screen
I've read ALL the unbrinking post on the internet, including xda, and none of them helped.
The KDZ Updater never recognizes the phone. I installed all the drivers but everytime I plug in the phone it installes the same LGE MTP drive...
Can anyone help, please?!
How to enter Emergency mode? How to flash another rom?
Hello,
I am writing this thread for a friend of mine. He owns a Z1 - stock ROM, locked bootloader.
Today it started looping and I tried to fix it (telling him over a chat what to do). It goes through the bootanimation and then dies or while optimizing apps, or while starting them.
What we tried:
1) Wipe cache
2) Factory reset
3) adb sideload the current official CM onto it
Nothing helped, the error stays the same. We also tried this http://forum.xda-developers.com/showpost.php?p=64458076&postcount=4 but it never really recognised the phone (despite using the correct drivers and following the procedure) - it did not appear under ports (Windows 10?).
Is there any other way to unlock this goddamn phone? My Androids so far had an easily unlockable bootloader via fastboot. This would have, too, but in order to unlock the bootloader via fastboot you first have to allow this in the developer settings - which we can not reach due to the loop.
If you know some way to get a working ROM onto it, we would be very happy. In the end we will end up unlocking the bootloader and flashing another Recovery and ROM anyway. We only need some way to achieve this. I expect the way to do this will be the QPST thingy. Any ideas why it did not recognise the phone? He does not own a PC with another OS than Win10...
Thanks in advance for your help,
Moritz
EDIT: Looks like the sideload did work - after tens of reboots it finally succeeded and bootet straight into the ROM.
Took a lot of attempts, strangely.
Proceeding to unlock it
Mine does the same boot loop on CM13. After tons of different tries to fix it, i think it could have something to do with my fingerprint sensor which is not working anymore.
Maybe there is some kind of hardware malfunction and android crashes while initializing that piece of hardware.