Database Info

[Q] Activation Problem - Boot Loop

So I sold an unopened, sealed Nexus 5 to someone last night and he's having a problem activating the device.
Here is his description of what happened:
"I popped in the SIM card, the loading proceeded as normally. It said it was activating and then a box popped up saying that "android is upgrading system files" or something like that. It restarted and went back to the language selection screen. I pressed English, next and then it went to the connect to wifi screen, froze and then restarted before I could even connect. Now it just loads on the boot"
I had him boot into recovery and do a factory reset, but the result is the same. I had him do a 2nd factory reset just be sure, but again, same result.
My thought is the system upgrade didn't happen correctly and not is corrupted.
What's the best course of action? Can I use the WugFresh toolkit to flash stock and unroot, or would I have to do it through ADB since the phone can't boot into the system?
I don't want to leave the buyer hanging, he seems like a nice guy, but I'm just not sure how to proceed?

Use ADB and flash the factory image for him.

Synyster06Gates said:
Use ADB and flash the factory image for him.
Click to expand...
Click to collapse
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.

SeanPlunk said:
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.
Click to expand...
Click to collapse
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!

switchfo0t said:
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!
Click to expand...
Click to collapse
Hello, I am the buyer of this Nexus device. I was able to successfully do these steps above, and reload the stock image for the Nexus 5. However, I am still running into issues.
WITH SIM:
I was able to get to the home screen after the initial setup, sent a few test text messages to my Google Voice number successfully, and browse on Chrome for a little bit before the device froze and restarted. After it restarted, I let it load up again, tried setting up my Google account on the device, then it froze again. All of the freezing happens within 3-5 minutes of using the phone.
So I decided to go into the bootloader, and do a factory wipe/cache wipe, and proceed without having the sim card in. I was able to get to the wifi selection screen, select my router, but as soon as the keyboard was suppose to pop up, the device froze and restarted. I am now just stuck on the welcome screen.
Any ideas now?
---------- Post added 29th November 2013 at 12:45 AM ---------- Previous post was 28th November 2013 at 11:56 PM ----------
Update: So I'm not sure what happened, but I ended up locking the device through Wug's Nexus Toolkit, inserted my sim card, and proceeded to set up the phone normally. So far everything has been working perfectly fine. I can receive/send texts, make and receive calls, and do normal functions with the phone without it locking up and restarting. Fingers crossed it'll stay like this.
Any idea on why this would've happened in the first place with the device?
---------- Post added at 01:38 AM ---------- Previous post was at 12:45 AM ----------
Update 2: Well, I noticed that it will randomly reboot every half hour or so it seems. It's kind of random, but I'm not sure what else could be causing these random reboots. The phone itself is working fine, but I just started experiencing random restarts.

Are you still on the stock rom or custom?

neomorphix said:
Are you still on the stock rom or custom?
Click to expand...
Click to collapse
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
---------- Post added at 01:49 AM ---------- Previous post was at 01:48 AM ----------
Jaybot said:
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
Click to expand...
Click to collapse
It was working fine earlier. I put it on the charger and got it to about 50%, used it for a little bit, then bam. It froze, and restarted all over again. I can use the phone maybe 5 - 10 minutes before it starts to recharge. Sometimes It'll automatically reboot after even unlocking the device.

I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.

neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.

Jaybot said:
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.
Click to expand...
Click to collapse
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.

neomorphix said:
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.
Click to expand...
Click to collapse
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.

Jaybot said:
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.
Click to expand...
Click to collapse
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.

neomorphix said:
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.
Click to expand...
Click to collapse
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.

Jaybot said:
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.
Click to expand...
Click to collapse
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.

neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.

Jaybot said:
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
Ok. This just sucks. But as with any mass produced product there is bound to be the ocasional issue.

neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.

theesotericone said:
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.
Click to expand...
Click to collapse
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.

Jaybot said:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
neomorphix said:
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.
Click to expand...
Click to collapse
Just saw that. OP by your earlier symptoms I rules out a stuck power button. With the new info I'd look into it further. If the phone is just looping over and over it could be a stuck power button, Mash the power button repeatedly for a minute. Then try and reboot. A few other people have had this on the N5 already and it's a notorious issue on some Samsung phones.

neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
If it comes to that, how do I go about transferring the warranty over?
I feel really bad, I just don't get it. I bought two of them, the other buyer hasn't had any problems. Both brand new, sealed, in the box. Go figure.

[Q] Stuck in a bootloop, dev ed, root, OTA

I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!

carmike692000 said:
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
Click to expand...
Click to collapse
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra

Caseyk621 said:
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Click to expand...
Click to collapse
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?

carmike692000 said:
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
Click to expand...
Click to collapse
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra

Caseyk621 said:
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Click to expand...
Click to collapse
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
EDIT - I'm sure one problem with the computer not listing the phone as a device is it cannot find the device driver to install for it, and I've not been successful googling for it. So in the Windows Device Manager list, my XT1080 has a yellow exclamation mark by it. Also, just installed TiB and froze "Motorola OTA" since I had to wait five minutes to post this edit anyways.

carmike692000 said:
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
Click to expand...
Click to collapse
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra

Caseyk621 said:
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Click to expand...
Click to collapse
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.

carmike692000 said:
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
Click to expand...
Click to collapse
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra

Caseyk621 said:
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Click to expand...
Click to collapse
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!

carmike692000 said:
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
Click to expand...
Click to collapse
Glad I could help! Don't forget to make a backup in TWRP! You may find yourself wanting to go back to stock sooner than you think! I keep trying ROMs but always end up missing active notifications and touch less as well as some others!
Sent From Droid Ultra

I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance

nubia11 said:
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
Click to expand...
Click to collapse
Flash the stock recovery with fastboot. I forget if you need to also unroot or not. Also make sure you have any apps that were disabled or frozen enabled/defrosted

[Q] Nexus 5 Bootloop

So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
EDIT: More googling today. Looks like my E:/Persist partition is corrupted or something, trying to figure out how to repair it right now.

Anjo_Smash said:
So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
Click to expand...
Click to collapse
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.

bitdomo said:
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.
Click to expand...
Click to collapse
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.

Anjo_Smash said:
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.
Click to expand...
Click to collapse
I made a thread about it. Here it is http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576

bitdomo said:
I made a thread about it. Here is it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.

Anjo_Smash said:
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.
Click to expand...
Click to collapse
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.

bitdomo said:
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.
Click to expand...
Click to collapse
Thanks for the offer. I'll try on my own and get back to you maybe tomorrow if I can't get it down.

Alright so I am definitely having problems running adb shell. even if I change the directory in cmd to my adb.exe location (android\android-sdk\platform-tools) I keep getting the error adb shell is not a recognized blah blah blah....
NVM got it working. Whenever I get frustrated enough to make a post I end up finally finding a solution.

ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?

Anjo_Smash said:
ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?
Click to expand...
Click to collapse
Just copy them to the root of your internal storage, then follow the guide.
I mean you just open the phone's internal storage from your PC and you dont open any folder. You just copy it there.
The guide is for nexus 5, but some people refer to the internal storage as sdcard too. I know it is a bit confusing. Thanks to point it out. I will make clear in my guide now.

AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.

Anjo_Smash said:
AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.
Click to expand...
Click to collapse
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.

bitdomo said:
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.
Click to expand...
Click to collapse
Should I try formatting it again?

Anjo_Smash said:
Should I try formatting it again?
Click to expand...
Click to collapse
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.

bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
Ok I'm going to install team viewer then.

bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
I'm all set up, so let me know when you are available friend, thanks for your help.

Anjo_Smash said:
I'm all set up, so let me know when you are available friend, thanks for your help.
Click to expand...
Click to collapse
I am here, send the login infos -> [email protected]

Help, I can't get past the WIFI screen and I can't flash a new rom on this phone

Hello guys,
I need your assistance with this issue. I got this Boost Mobile LG LS770/Stylo phone from eBay and when I wiped/restored it to clean everything from the other person, the phone still wants me to enter the information from the previous person before I can use it. Of course that is not an option. I tried.
Also, since I am unable to get to the Android OS, I cannot put it in debug mode either. So I tried a few things to no avail. This is what I have done so far:
Put the phone in ADB mode via recovery - Done, but I am unable to sideload anything. I get this error.. "* cannot read 'sideload' *"
Put the phone in download mode "Fireware Update" - Done, and I can see my port as COM3, but when I run the next step, I get a message that says... "Hello, my name is LAF....." and nothing happens.
I tried using the LG one click root tool, but that requires the phone to be in USB debug mode and like I said before, I am unable to even get to the welcome screen in android. I can't get past wifi setup in reality, I can't even skip it.
I have been at this all day today. Can you please help me out? I really appreciate any help you can provide.
Thanks

You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?

revulv said:
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
Click to expand...
Click to collapse
I have OTG cable... Can you help me out??

revulv said:
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
Click to expand...
Click to collapse
Thank you for your response. I have one. Please go ahead with the steps.

revulv said:
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
Click to expand...
Click to collapse
Also, I forgot to respond to your question. I did contact the eBay guy or lady that sold it to me, but since I'm the one that did the wipe, they are not taking responsibility and I get it. I just would like to be able to use the phone and not waste the money I spent on it. I really appreciate any help you or others can provide.

Have OTG cable & flashdrive
revulv said:
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
Click to expand...
Click to collapse
I am stuck in the same boat, bought what appears to be a brick. Would be most grateful if I could get the files/procedure you mentioned as well.

Sorry guys!
https://www.youtube.com/watch?v=xNSBbpVOmb4

Thank you for the suggestion , but this method does not work. I have already tried this and after the tool went through all the steps, it still asks for the previous account. I have found on some other forums that LG patched this flaw a few months ago and it is no longer possible to bypass FRP Factory Reset Protection. I guess I have a rock until someone can figure out how to bypass this "Feature", which in my opinion should be illegal because it forces people to buy devices from carriers only and you can no longer sell your phone online to anyone, as you cannot give them the account.

webmanny said:
but this method does not work..
Click to expand...
Click to collapse
It didn't work for me either... the last security patch disabled user from the settings menu. I did find a way after many hours of work.
Basically once I got to settings I clicked unknown sources and then enabled USB debugging and oem unlock. After that I flashed twrp and then a rooted system image. After that I used http://androiding.how/bypass-google-account-verification-on-lg-g4-g3-and-others and it worked
Sent from my HTC One M9 using XDA-Developers mobile app

bigp951 said:
Basically once I got to settings I clicked unknown sources and then enabled USB debugging and oem unlock. After that I flashed twrp and then a rooted system image. After that I used http://androiding.how/bypass-google-account-verification-on-lg-g4-g3-and-others and it worked
Click to expand...
Click to collapse
How did you get to settings? I am only able to get to the accessibility to turn on the voice stuff.

webmanny said:
How did you get to settings? I am only able to get to the accessibility to turn on the voice stuff.
Click to expand...
Click to collapse
I honestly don't remember. I'll try to figure it out and get back to you. I think it was through the keyboard. I returned the phone already so I do t have it on front of me.
Look for anything with terms of service. Once you're on the internet you can download the settings app that everyone uses on the internet.
Sent from my HTC One M9 using XDA-Developers mobile app

Web trust me i went crazy with this for 3 days. My friend gave me his Stylo from work to unlock and i had this same issue. Flashed back to 5.1.1e,i,j, using kdz files and all the exploits that these guys are using have been shut down. If your on MM forget it. The only thing that worked for me was that tool i linked in the other thread. I hope your wrong on the virus part, ill check my laptop, but your the first person to mention that. Either way i flashed back to 5.1.1 from MM, used the tool, rebooted and it worked i signed in with his gmail.

sshafranko said:
Web trust me i went crazy with this for 3 days. My friend gave me his Stylo from work to unlock and i had this same issue. Flashed back to 5.1.1e,i,j, using kdz files and all the exploits that these guys are using have been shut down. If your on MM forget it. The only thing that worked for me was that tool i linked in the other thread. I hope your wrong on the virus part, ill check my laptop, but your the first person to mention that. Either way i flashed back to 5.1.1 from MM, used the tool, rebooted and it worked i signed in with his gmail.
Click to expand...
Click to collapse
I understand and I apologize if I sounded like I was shutting your advise down. That was not my intention. I was just stating what my virus tools detected and my experience. Regardless, I decided to ignore the virus warning and let the tool run and do what the steps on the word document stated. It went through all the steps without issues and I got the same matching screen as in the tutorial document. However, after I reboot, I still get the same screen that reads, login with a google account previously associated with this device.
Now, the one piece I'm not sure I understand from your message above is the part about flashing to 5.1.1 from MM using kdz files. How can you flash the phone when you cannot get into the settings to enable usb debug mode? I have tried everything. I even downloaded a rom file image that I placed on an Micro SD card and tried running it from recovery to no avail.
Maybe you are correct and I am just missing a step. Would you mind expanding on the flashing 5.1.1 from MM part? Maybe what steps and files you had to use?
Also, I'm not sure I understand this portion of your message. You signed in with who's gmail?
sshafranko said:
i signed in with his gmail.
Click to expand...
Click to collapse
Thank you in advance for your assistance.

is there a software older than 5.1.1 that can be flashed to the device?

You can use touch assistant to get in to settings and then disable all google aps, works for me on lg stylo 6.0, PaulieP he is the person that found this method

Locking bootloader removes root? Also more Questions. [Phone Gone Now]

I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.

Superorb said:
I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.
Click to expand...
Click to collapse
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.

BakedOnSomeSour said:
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.
Click to expand...
Click to collapse
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?

Superorb said:
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985

BakedOnSomeSour said:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
Click to expand...
Click to collapse
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?

Superorb said:
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?
Click to expand...
Click to collapse
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.

BakedOnSomeSour said:
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.
Click to expand...
Click to collapse
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.

Superorb said:
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.
Click to expand...
Click to collapse
Same. if you need any additional help with the process just let me know.

BakedOnSomeSour said:
Same. if you need any additional help with the process just let me know.
Click to expand...
Click to collapse
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.

Superorb said:
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.
Click to expand...
Click to collapse
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.

BakedOnSomeSour said:
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.
Click to expand...
Click to collapse
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.

Superorb said:
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.
Click to expand...
Click to collapse
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.

BakedOnSomeSour said:
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.
Click to expand...
Click to collapse
Ok, I've downloaded all 3 zip files from my build at over 2gigs.

Superorb said:
Ok, I've downloaded all 3 zip files from my build at over 2gigs.
Click to expand...
Click to collapse
Ok now extract the files from the update.zip folder. Then take the UPDATE.app from the extracted files and open it with update extractor: https://forum.xda-developers.com/showthread.php?t=2433454
After that your ready to follow the steps on the other guide.

So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?

Superorb said:
So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?
Click to expand...
Click to collapse
Edit: Before trying below steps. Just put the files from "BLN-L24_hw_usa"(b360) into dload folder and flash with dload. It might update the version.img without the needs for the steps below. if that brings the build number back to b360 use the hisui(PC) application to connect to the phone and update
Ok i forgot to mention something. The reason you dont have a update option is because you are on b360 which never had a button. Your build number on your phone will say b366 but thats incorrect. You cant receive an ota automatically because the phone thinks its already on the latest version. You need to take the UPDATE.APP from the "BLN-L24_hw_usa" (b360) folder and extract the VERSION.IMG file. It needs to be flashed with TWRP because fastboot wont work for some reason. That file will fix the build number and change it back to b360 so you can receive the OTA which will also restore the missing apps and features. That means you have to unlock the bootloader. Flash twrp. Flash the vendor.img with twrp and then do the dload method.
You have all the files and have done it already so this time will be easier. Ive done this way too many times with this phone. Sorry i forgot the mention the one step

Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.

Superorb said:
Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.
Click to expand...
Click to collapse
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.

BakedOnSomeSour said:
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.
Click to expand...
Click to collapse
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.

Superorb said:
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.
Click to expand...
Click to collapse
Its not difficult. In order to connect to hisuite you need to enable developer settings and allow usb debugging or type hisuite in the settings search bar and click "allow HiSuite to use HDB". I got this phone for christmas and i already know a ton about it. It may seem complicated now but its really nothing.