Database Users

[Q] Seeks Expert Help on Bricked ATT LG G2 using Straight Talk Sim

Elite thanks in advance. No, seriously, thanks. I'm a broke single parent of 2 kids and I realized my phone is about my only guilty pleasure after giving my kids 200% of my time and money. Any help would be appreciated.
I have an LG G2 that I apparently bricked by using an app to "freeze" the latest OTA software update that was pushed to my ATT LG G2 about a month + ago if not slightly longer. I unfroze the process and the update suddenly appeared and said it would reboot the phone and or apply the update it in 30 seconds. I panicked and held the power button in to turn the phone off.
Once the phone was turned back on I was greeted with tiny white text that said "error: Boot certification verify" From here I was unable to get into down load mode, do a hard reset. I was able to see fast boot mode but wasn't sure what to do with it. I was able to see the phone in Windows 7 Pro Sp1 device manager but it was listed as QHSUSB_BULK
After initially freaking out which lasted about 20 mins, I was able to compose myself and start researching my new seemingly serious problem. After a few hours of reading a dozen or so treads / hundreds of replies it seemed I would have to load into Ubuntu and push some files to my LG G2.
I followed this guide - http://forum.xda-developers.com/showthread.php?t=2582142
I was very careful to follow this guide to the letter and everything went as expected the first, 2nd and 3rd time only the results were worse and worse and worse.
The first time I lost fast boot, the 2nd time I lost the boot certification verify error, After the 3rd attempt I get a split second LG Logo and that's it. What did I do during those 3 attempts? The first time, the 4 files and the recovery as directed. The 2nd time, the same files, plus the boot.img and a different recovery. The 3rd time, all the files and yet a different recovery. All the files were pulled from here - http://downloads.codefi.re/autoprime/LG/LG_G2/D800
The other recovery.imgs were for the correct model, just older, newer variants. I was very careful to push the right files to the right partitions.
I can still see the phone via Ubuntu. I'm scared to do anything else along the lines of what I've been doing. In fact I'm lost as to what to do next.
Can anyone here help me push more / different files via Ubuntu that would help bring my phone back to life? I'm completely dead in the water. Or perhaps an exe package / program that can fix my problem? If I sound stupid, it's because this is all new to me.
Thanks in advance, Tom

@rthefley Go back to the autoprime downloads and get the boot, aboot and laf image. Follow the ubuntu guide and flash those images only.

@art
Thank you for taking the time to stop and help me. I greatly appreciate it. I followed your instructions and pushed those 3 files in the order you gave me. Results were the same, nothing. I still get a very brief LG logo but nothing more. I can get into the hard reset but it does nothing as well.
Here are pics I took of the files and directories from my phone connected via usb through Ubuntu. There are a few wrong commands, ignore them. GF was behind me talking and I wasn't focused. I can assure you the proper cmds were given when it counted.
Well ....... I guess I cannot post links ............. so they are edited out. I wanted to show that my highest number was sbe43 so I had to use sbe
Im using the files from the D800 dir which is the ATT LG G2. Or should I tried another directory or files? I can still access the phone via Ubuntu ... THANK GOD
I am still hopeful.

rthefley said:
@art
Thank you for taking the time to stop and help me. I greatly appreciate it. I followed your instructions and pushed those 3 files in the order you gave me. Results were the same, nothing. I still get a very brief LG logo but nothing more. I can get into the hard reset but it does nothing as well.
Here are pics I took of the files and directories from my phone connected via usb through Ubuntu. There are a few wrong commands, ignore them. GF was behind me talking and I wasn't focused. I can assure you the proper cmds were given when it counted.
Well ....... I guess I cannot post links ............. so they are edited out. I wanted to show that my highest number was sbe43 so I had to use sbe
Im using the files from the D800 dir which is the ATT LG G2. Or should I tried another directory or files? I can still access the phone via Ubuntu ... THANK GOD
I am still hopeful.
Click to expand...
Click to collapse
In that case, you should try to push a recovery image, too!

Raymonf said:
In that case, you should try to push a recovery image, too!
Click to expand...
Click to collapse
I've pushed 4 or 5 different recovery images. Should I try something different than the recovery images suggested? I am willing to try anything at this point.

rthefley said:
I've pushed 4 or 5 different recovery images. Should I try something different than the recovery images suggested? I am willing to try anything at this point.
Click to expand...
Click to collapse
Did you lokify them?

Raymonf said:
Did you lokify them?
Click to expand...
Click to collapse
@Raymonf first let me thank you for taking the time to try and help me sort out my ... what I consider a serious issue. Thank you!
I've not read about lokify. So I am not sure what that is but I can absolutely tell you, I'm a great listener. I've spent 12 or 13 hours reading all over the internet, tread after tread and post after post. So I somehow missed the instructions on lokifying the files.
Tom

rthefley said:
@Raymonf first let me thank you for taking the time to try and help me sort out my ... what I consider a serious issue. Thank you!
I've not read about lokify. So I am not sure what that is but I can absolutely tell you, I'm a great listener. I've spent 12 or 13 hours reading all over the internet, tread after tread and post after post. So I somehow missed the instructions on lokifying the files.
Tom
Click to expand...
Click to collapse
Okay, are you now able to go into download mode?

1127
Art Vanderlay said:
Okay, are you now able to go into download mode?
Click to expand...
Click to collapse
No, I've never been able to get into the download mode.
The only way I can access my phone is via Ubuntu. Hard Reset doest work even though I can get to that screen and initiate the process, it doesn't complete.
One other person that's also trying to help me out asked if I've lokify those img files. No I haven't. I've not come across those instructions yet. Would that make a difference?
I also sent you a private PM with links to pics I took of my directory structure from my ATT LG G2 via usb / Ubuntu

rthefley said:
No, I've never been able to get into the download mode.
The only way I can access my phone is via Ubuntu. Hard Reset doest work even though I can get to that screen and initiate the process, it doesn't complete.
One other person that's also trying to help me out asked if I've lokify those img files. No I haven't. I've not come across those instructions yet. Would that make a difference?
I also sent you a private PM with links to pics I took of my directory structure from my ATT LG G2 via usb / Ubuntu
Click to expand...
Click to collapse
Your directories are fine. But if you successfully flashed those 3 partitions, you should Have a working download mode. Make sure you fully power off the phone, you might have to hold the button down for a while.

Art Vanderlay said:
Your directories are fine. But if you successfully flashed those 3 partitions, you should Have a working download mode. Make sure you fully power off the phone, you might have to hold the button down for a while.
Click to expand...
Click to collapse
Yes I'm pretty sure it's completely powered off. I will try again but I've held the power button in for several several seconds and saw the screen go solid black. I've flashed those 3 files just as instructed. Nothing is working sadly. Maybe I am missing some key procedure others take for granted that I just personally do not know about
Is there anything else I could try doing? I'm going in circles here.

Do your results match the one in the forum when you type gdisk -l /dev/sdb in the terminal.? Also is your fastboot still gone.?
Sent from my LG-LS980 using Tapatalk

LilDemon124 said:
Do your results match the one in the forum when you type gdisk -l /dev/sdb in the terminal.? Also is your fastboot still gone.?
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
No they are different, I actually gdisked all of the different letters but I have an sda,c,b and e, I even have have an sde1. All the numbers follow sde however up to 42 or 43. So when I gdisk -l /dev/sde that's when I see all the files.
I've tried to gdisk sdb but I get a mbr / gpt or something error saying something is corrupted so I just leave it alone.
Should I be looking at a different letter then? If so, I can't seem to get into any of them other than the one I mentioned, sde

Guys, I'm now offering a $40 paypal bounty directly to your pocket or a donation to this web site for help allowing me to get back into my phone.

I will try my best to help you. Im at work, but will be home soon so that I can do some snooping.. From what your saying you MIGHT have a corrupt storage OR you might have a corrupt file.
Sent from my LG-LS980 using Tapatalk

Im going to have to work on this a bit later. Worked all day. I'm still here and around just need to get a little sleep before I even think of trying to dive into this again. Thanks.

Update moto E XT1022 to Android 5

WARNING:- DO THIS AT YOUR OWN RISK I'll NOT BE RESPONSIBLE IF ANYTHING HAPPEN TO YOUR PHONE.
Its just for an Indian retail version only. yes, even after updating using the methods given below, you will get future updates
Notes -
Make sure that you are running completely stock version of android before applying the update. Do not try to apply the update with custom recoveries as it may hardbrick your device.Make sure that you have an indian retail version of the Moto E. You can check this by going to Settings->About Phone and scroll down and check if your system version is 21.12.40.condor_retaildsds.retaildsdsall.en.03reteu only.Make sure that you have atleast 50% battery before applying the update.Make a backup of all your apps and data before applying the update. (The update won’t wipe any data on your device, but still, it is safe to do so.)
Method 1*-
Download the update zip from here*http://bit.ly/1FCw68p*(Mediafire Link). This is a soak test update which was captured during the soak testing programme. Soak test isn’t*a*beta update or unstable. It’s just the final build but it rolls out to earlier than the global update.Download Motorola Update Services apk from here*http://bit.ly/1z9Lox0. Install it.Put the zip file which you’ve downloaded in the root of your internal memory as well as external memory. (Root means simply internal or external memory. It means that you have to place the file directly in the internal or external memory and not in any folder inside internal or external memory.)Reboot your phone 2-3 times and leave the device as it is for 15-20 minutes.Now go to Settings->About Phone->System Updates. You will see a screen stating “New system software available”. Click on “Yes I’m in”.Now, a download will begin and you can see that in the status bar. Once the download is complete, swipe down the notification bar and click on Install system update->Install now.Now, your phone will reboot into recovery and install the update update automatically for you. You just have to wait and watch for around 10-15 minutes.When you phone will start booting, just let it boot and don’t panic. Since this is a big software update, so it will take some time to boot up the device.
Method*2 -
I did found that a lot of users are not able to update their device by the above procedure. So I have found one another way of doing the update.Turn on USB debugging on your device. This can be done by doing the following steps – Go into Settings->About Phone and tap on build number 8-10 times. Now press back button and you will see a new option called developers options in the settings. Tap on developers option and enable USB debugging from there.Download motorola device manager from here*http://bit.ly/1MgFKCn.Install the device manager and connect your phone to the PC. The device manager will automatically install all the necessary drivers for you. Now disconnect the phone from the PC.Download minimal adb fastboot from here*http://bit.ly/1ArhfOe.Install it. Now go to My computer->C Drive->Programme Files(x86)->Minimal Adb and fastboot and copy the update zip there. (Do not rename it.)Now go into the recovery mode on your Moto E.This can be done as follows – Power Off your phone. Now press volume down and power buttons simultaneously for 10 seconds. This will take you to the bootloader.Now press volume down which will highlight ‘Recovery’ and then press volume up. Now your device will show up a dead android.Now press volume up first then, while pressing the volume up button, press power button. now release the power button first and then volume up button. Now you will see recovery.Now use volume down button to scroll to ‘Apply update from adb’ and then press power button to select it.Now connect your phone to the PC.Now, open Minimal adb and fastboot from the start menu and type the following command
Code:
adb sideload Blur_Version.21.12.40.condor_retaildsds.retaildsdsall.en.03.zip
This will update your phone.
Congratulations! You’ve got Lollipop on your Moto E! I guess this is the first guide out there.
Do thinks and post your phone screenshots who ever is updating.
Sent from my XT1022 using XDA Free mobile app

link is not working
please fix it

Its working perfectly
Sent from my XT1022 using XDA Free mobile app

Akhil137 said:
Its working perfectly
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Can u plz check if u can mount script on link2sd app mine not working plz confirm...

will it work on unlocked bootloader

No it will not
Sent from my XT1022 using XDA Free mobile app

Akhil137 said:
No it will not
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
How much time dos it take to update using the ADB? I mean its stuck at Patching system files since 5 minutes.... i have followed all the procedures correctly....
Edit : Guys, It takes Around 15-17 mins. to complete the process in the phone itself... It may get stuck at patching system, etc.... But remember that do not power off the phone or unplug during adb transfer in any case
Regards
Andy

U have to put it in internal only no other thing works in it.
Sent from my XT1022 using XDA Free mobile app

Link
aksudhakar said:
please fix it
Click to expand...
Click to collapse
Use this much only
http://bit.ly/1FCw68p
@Akhil137 Thanks for this
Kindly edit your post to put a space between "http://bit.ly/1FCw68p" and "*(Mediafire" so it will not cause any trouble to members while clicking on the link and it will work perfectly and directly.
---------- Post added at 07:33 PM ---------- Previous post was at 07:29 PM ----------
Can anybody provide screenshot for this ?

Video Tutorial
Here's a Working Moto E Lollipop Update Tutorial: Here's a tutorial i made on How to Install Lollipop on Moto E as there seem to be many problems with people trying different methods: https://www.youtube.com/watch?v=Refs73469IA

Hello, is this an official update or soak test?
I own a Moto G but my friend asked me to keep track of this nonsense for the Moto E
XT1022 = Indian Moto E?
It's pure official stock build, correct? No modifications so that my noob friend can update to the next (possibly 5.1?) whenever it comes out if it does?
He's really doesn't know how to unlock bootloader or anything and doesn't even have a WiFi network so I'm going to download it for him and flash it via stock recovery...
Thanks in advance

Working
thanks for info...just flash it and work flawlessly :good:

failed!
all stock files but recently unrooted and flashed stock recovery. anyone knows the solution?

Chirag_1537 said:
Hello, is this an official update or soak test?
I own a Moto G but my friend asked me to keep track of this nonsense for the Moto E
XT1022 = Indian Moto E?
It's pure official stock build, correct? No modifications so that my noob friend can update to the next (possibly 5.1?) whenever it comes out if it does?
He's really doesn't know how to unlock bootloader or anything and doesn't even have a WiFi network so I'm going to download it for him and flash it via stock recovery...
Thanks in advance
Click to expand...
Click to collapse
This is not official update , Its just the soak test. So May be you should wait for one or two weeks for the official update.

rkmiks said:
This is not official update , Its just the soak test. So May be you should wait for one or two weeks for the official update.
Click to expand...
Click to collapse
Haha, I just spent the last half an hour attempting to explain to my friend how to install the update via adb haha. He's got that mob mentality. The update is there. It's installable. He must have it. Well I failed explaining to him so I'm going to his house tomorrow to upgrade it for him. I couldn't do the Motorola update.apk method. I have no idea how to do that. I have a question. Why doesn't the Moto E stock recovery install anything from SD card?! It works perfectly on my Moto G but here it just says installation from SD card complete.
Also, I'm using the Moto G soak test and it's pratically bug free. I'm sure this'll be fine too

Chirag_1537 said:
Haha, I just spent the last half an hour attempting to explain to my friend how to install the update via adb haha. He's got that mob mentality. The update is there. It's installable. He must have it. Well I failed explaining to him so I'm going to his house tomorrow to upgrade it for him. I couldn't do the Motorola update.apk method. I have no idea how to do that. I have a question. Why doesn't the Moto E stock recovery install anything from SD card?! It works perfectly on my Moto G but here it just says installation from SD card complete.
Click to expand...
Click to collapse
Well I actually updated from the sdcard . I had to copy the Update Zip to both internal and external sdcards and reboot and wait for one or two minutes after reboot and applied the update from the motorola update manager and it worked. Well this update is fine but there are issues about the limited internal storage and link2sd is also not perfectly working. And also if you need to downgrade to kitkat , just don't downgrade to 4.4.2 as it could brick your device as many people have reported.
Also, I'm using the Moto G soak test and it's pratically bug free. I'm sure this'll be fine too
Click to expand...
Click to collapse
I thought final update was already out for Moto G.

rkmiks said:
Well I actually updated from the sdcard . I had to copy the Update Zip to both internal and external sdcards and reboot and wait for one or two minutes after reboot and applied the update from the motorola update manager and it worked. Well this update is fine but there are issues about the limited internal storage and link2sd is also not perfectly working. And also if you need to downgrade to kitkat , just don't downgrade to 4.4.2 as it could brick your device as many people have reported.
Click to expand...
Click to collapse
Maybe I didn't name the file correctly so it wasn't reading it. I'm not sure why it didn't work.
Hahahaha should've told me that in Jan. I bricked my device exactly by downgrading to 4.4.2. It's common sense why you shouldn't do it. I wasn't thinking. I had one of my toughest subject exams the very next day. And I accidentally deleted build.prop and didn't have 5.0.2 factory image. But it's common sense why it will brick lol.
Also I was struggling to explain to my friend the spelling of fastboot and how there's no space in between. I'm sure he won't have problems with link2sd because he's not a SuperUser ?
He has issues with the limited internal but he survives.

Chirag_1537 said:
Maybe I didn't name the file correctly so it wasn't reading it. I'm not sure why it didn't work.
Hahahaha should've told me that in Jan. I bricked my device exactly by downgrading to 4.4.2. It's common sense why you shouldn't do it. I wasn't thinking. I had one of my toughest subject exams the very next day. And I accidentally deleted build.prop and didn't have 5.0.2 factory image. But it's common sense why it will brick lol.
Also I was struggling to explain to my friend the spelling of fastboot and how there's no space in between. I'm sure he won't have problems with link2sd because he's not a SuperUser
He has issues with the limited internal but he survives.
Click to expand...
Click to collapse
Well I hope the flashing goes well and your friend finds lollipop sweet enough. Actually I really feel the smoothness in the UI and If he doesn't mind the thing about link2sd etc he will probably love it.

Actually this build is quite bug free, but to some extent , don't know why but It is comparatively slow than Kitkat... So I reverted back to Cyanogenmod making a nandroid backup on twrp so that I can restore it whenever necessary...... So I think if you have not unlocked bootloader, you should wait for stable moto e lollipop release... I hope they will give it out soon!!
Regards
Andy

Andy1911 said:
Actually this build is quite bug free, but to some extent , don't know why but It is comparatively slow than Kitkat... So I reverted back to Cyanogenmod making a nandroid backup on twrp so that I can restore it whenever necessary...... So I think if you have not unlocked bootloader, you should wait for stable moto e lollipop release... I hope they will give it out soon!!
Regards
Andy
Click to expand...
Click to collapse
I did a factory reset after updating to lollipop and it is much more smooth than what it used to be on kitkat and also battery performance has improved after 2-3 days of flashing lollipop.

Successful Root and Unlock HTC One M8 with VZW Lollipop

Hey guys,
I have never posted a thread like this so please tell me if I have done anything wrong. I don't have enough time to write a proper guide but if someone wants to they are more then welcome. I take no credit for any of this information, I just took the risk and attempted an M7 root and unlock method on my M8. And it worked! But just a little differently. I followed the steps in this thread but with a few minor changes: http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099
Okay so basically instead of using the mobile app of Kingroot I used the desktop version and had a much higher success rate. Once I gained temporary root for the first time I ran sunshine and finished all of the compatibility tests. The phone will reboot and you will need to re-root. Once you've gained root again run sunshine. It'll only take a couple of minutes. It may crash. That's fine you should now be unlocked. This is as far as I have gotten do to time constraints and not knowing exactly what recovery to flash. If someone knows please let me know! As stated in the original thread this is super finicky but will work. Just have some patience.
Also, I didn't get official software status. In case that's a problem for anyone.
My Phone:
VZW HTC One M8 running lollipop 5.0.1
Ill try to clean this up when I get home from work but I just wanted it to be out there so everyone knows. I will remove this thread if someone posts a better one. Thanks!

UPDATES?
i need this working bro, my m8 is pissing me off, king root wont work i followed all your instructions
also what version of kingroot did you have?
radiowavedev said:
Hey guys,
I have never posted a thread like this so please tell me if I have done anything wrong. I don't have enough time to write a proper guide but if someone wants to they are more then welcome. I take no credit for any of this information, I just took the risk and attempted an M7 root and unlock method on my M8. And it worked! But just a little differently. I followed the steps in this thread but with a few minor changes: http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099
Okay so basically instead of using the mobile app of Kingroot I used the desktop version and had a much higher success rate. Once I gained temporary root for the first time I ran sunshine and finished all of the compatibility tests. The phone will reboot and you will need to re-root. Once you've gained root again run sunshine. It'll only take a couple of minutes. It may crash. That's fine you should now be unlocked. This is as far as I have gotten do to time constraints and not knowing exactly what recovery to flash. If someone knows please let me know! As stated in the original thread this is super finicky but will work. Just have some patience.
Also, I didn't get official software status. In case that's a problem for anyone.
My Phone:
VZW HTC One M8 running lollipop 5.0.1
Ill try to clean this up when I get home from work but I just wanted it to be out there so everyone knows. I will remove this thread if someone posts a better one. Thanks!
Click to expand...
Click to collapse

I'll work on creating a step by step when I get home. I've just been really busy. It's just a lot of trial and error but it should work at some point. Keep a look out for my reply tonight.

xercurial said:
i need this working bro
Click to expand...
Click to collapse
Such a polite way of asking someone to go out of their way to help you or write a guide for you.

lol sorry about that man i did however end up rooting it , now im having trouble
redpoint73 said:
Such a polite way of asking someone to go out of their way to help you or write a guide for you.
Click to expand...
Click to collapse
i am having trouble iwth twrp

xercurial said:
i am having trouble iwth twrp
Click to expand...
Click to collapse
Is there a question you are intending to ask?
And you need to describe the "trouble" exactly and precisely.
What version TWRP?

twrp issues
redpoint73 said:
Is there a question you are intending to ask?
And you need to describe the "trouble" exactly and precisely.
What version TWRP?
Click to expand...
Click to collapse
i have the one the ends with 7.0.1 i believe i cannot check right now, i am servicing it because i have to replace the jack and get a new housing which will take a coupe days to ship, i did however get root s off after trying for the longest time. my issue now is whenever i try to boot into the recovery, most of the time it will take me to stock or show the error triaangle which indicates there is none installed which there is (very frustrating) once in a blue moon however i will finally get into twrp and whenever i try to do a backup, it says failed or some kind of error. and EVERYTIME i try to reboot my system it would bootloop into recovery! and when that happens i would be forced to re install a rom and the whole proccess starts again. So i just stuck with the gpe rom basically and i tried to do a backup and the whole recovery issue just pissed me off so i just decided to to my hardware fix by replacing the frame and the headphone-charging port which ended up not being compatable with the verizon model so i had to re order (very frustrating) will probably by the at&t model at some point instead
anyways sorry for being rude earlier and thanks for your patience!

Alright, sorry that I lied about going home and typing up a step by step things are just hectic ya know? Anyways i'm here now so let me gather myself and get you some help. lol

xercurial said:
i have the one the ends with 7.0.1 i believe i cannot check right now, i am servicing it because i have to replace the jack and get a new housing which will take a coupe days to ship, i did however get root s off after trying for the longest time. my issue now is whenever i try to boot into the recovery, most of the time it will take me to stock or show the error triaangle which indicates there is none installed which there is (very frustrating) once in a blue moon however i will finally get into twrp and whenever i try to do a backup, it says failed or some kind of error. and EVERYTIME i try to reboot my system it would bootloop into recovery! and when that happens i would be forced to re install a rom and the whole proccess starts again. So i just stuck with the gpe rom basically and i tried to do a backup and the whole recovery issue just pissed me off so i just decided to to my hardware fix by replacing the frame and the headphone-charging port which ended up not being compatable with the verizon model so i had to re order (very frustrating) will probably by the at&t model at some point instead
anyways sorry for being rude earlier and thanks for your patience!
Click to expand...
Click to collapse
If I remember correctly all I did was go to twrp's website and download the most recent version for the VZW M8 (I think it might have just been one for all versions not sure) then installed it through adb and it has been working flawlessly. I since installed ViperOne without any problems. The version of twrp I got was 2.8.7.0. Once you get your phone going again i'd suggest reinstalling twrp through adb.

xercurial said:
i have the one the ends with 7.0.1
Click to expand...
Click to collapse
As noted by the previous response, you should get the latest version of TWRP (2.8.7.0) if you are on Lollipop firmware. TWRP versions 2.7 are known to be problematic on LP.
---------- Post added at 11:32 AM ---------- Previous post was at 11:07 AM ----------
radiowavedev said:
If I remember correctly all I did was go to twrp's website and download the most recent version for the VZW M8 (I think it might have just been one for all versions not sure)
Click to expand...
Click to collapse
You're correct, TWRP for CDMA (Verizon, Sprint) and GSM versions (most other M8 versions) was merged some time ago.

Possible way to save any bricked Nexus device!

Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!

That explains why the OTA for the N preview was the same size as the image, and why after upgrading to March security release I didn't have to download a different OTA to get to N

So is this usable in all situations? If yes then should download it & store it safely

Interesting thing, can this update bypass factory reset protection?

iluvatrix said:
So is this usable in all situations? If yes then should download it & store it safely
Click to expand...
Click to collapse
I would assume this could be used in any situation where you have a paper wait. So say you're on marshmallow build and somehow things go wrong ,bootloader locked USB debugging not check ,with this ota you can still sideload but it will be an N build which is fine at least you'll have a working device that now you can revert back to your original build. So I'm keeping this as well. I really don't need to but its nice to have just in case. I normally keep my bootloader unlocked at all times anyways just in case things go haywire... Someone correct me if I'm not correct please. Have a nice weekend all?
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Good question..

Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Most likely not, because normally when receiving an OTA all of that remains intact but, I think it's worth a test.

This will NOT bypass factory reset protection. This is just an update.zip that is a signed "FULL" image rather than a "DIFFERENCE" image. That means that it just doesn't need to perform the verification step before proceeding to install the update.
There is also another "problem" with relying on these as the ultimate unbrick files, which is that if you happen to install some official build that is NEWER than N-pre1, then the recovery will refuse to "downgrade". So while it may be useful for now while nobody is running anything newer than N-pre1, it isn't a permanent solution.

This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish

Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
doitright said:
This will NOT bypass factory reset protection.
Click to expand...
Click to collapse
The first N preview apparently has a bug that will allow a user to bypass FRP (if they are on the first N preview)
http://www.androidpolice.com/2016/0...ory-reset-protection-workaround-on-android-n/

flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
I'm glad to hear it worked for you

Works for me boss
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:

mowgli762 said:
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:
Click to expand...
Click to collapse
Why didn't you just flash the system.IMG if the bootloader was unlocked?

holeindalip said:
Why didn't you just flash the system.IMG if the bootloader was unlocked?
Click to expand...
Click to collapse
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).

mowgli762 said:
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).
Click to expand...
Click to collapse
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.

holeindalip said:
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.
Click to expand...
Click to collapse
Good - case specific information needs no apology - Diplomacy has never been alluded to as being in my skill set (too much glass in my house to throw stones).
Thanks for your interest and info.

TriguyRN said:
Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!
Click to expand...
Click to collapse
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .

atef79 said:
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .
Click to expand...
Click to collapse
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face

TriguyRN said:
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face
Click to expand...
Click to collapse
I already shared your post in my topic that I made in the Nexus 6p section to help all who bricked there devices with locked bootloader, and thx again .
This is my topic link
http://forum.xda-developers.com/nexus-6p/help/command-t3308390/post66086939#post66086939

just want to ask would this method work if the phone has not been authorized to a specific PC ?

iluvatrix said:
just want to ask would this method work if the phone has not been authorized to a specific PC ?
Click to expand...
Click to collapse
I'm not sure what you mean by "if the phone has not been authorized to a specific PC". As far as I am aware Android phones are not authorized to a PC, that is an Apple thing...

Rooting The T-Mobile V20

Trying to get my V20 rooted I figured since it's been awhile I'd try and ask hopping not to get my head ripped off about rooting this beast. I would greatly appreciate some help. Tried in the past failed miserably.

ice5192 said:
Trying to get my V20 rooted I figured since it's been awhile I'd try and ask hopping not to get my head ripped off about rooting this beast. I would greatly appreciate some help. Tried in the past failed miserably.
Click to expand...
Click to collapse
I am coming from the Note 7 and Samsung background. I was apart of the Tekhd team. When the note 7 starting exploding and I had to turn it in I got the v10 to test then I prefer ordered the v20.
I just need some pointers on what I need to do the rooting process on this phone is very different from what I have been used to...

how have you failed ? what methods have you used? .. ill help you out as much as i can. i had trouble rooting before so i feel your pain

Just updated to lastest version.

xDEMON87x said:
how have you failed ? what methods have you used? .. ill help you out as much as i can. i had trouble rooting before so i feel your pain
Click to expand...
Click to collapse
Which version should I use? I have the lastest update now.

Hey,
Just follow the Recowvery thread, then install whatever ROM you want after you have TWRP.
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594

I'll try I do have the newest build. December release.

ice5192 said:
I'll try I do have the newest build. December release.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=fZEL96MPLvY , follow this guide..

xDEMON87x said:
, follow this guide..
Click to expand...
Click to collapse
O tried this but when I got to type the dirtycow commands it simply doesn't find it it says no such file directory exist

egren58 said:
O tried this but when I got to type the dirtycow commands it simply doesn't find it it says no such file directory exist
Click to expand...
Click to collapse
Before copy twrp.img to internal storage, make sure the name is exactly twrp.img (it MUST be all lower case).
SuperSU file must be copied to memory card.

Anyone free this Saturday willing to help me root I have tried every method... I do where I have done wrong

egren58 said:
Anyone free this Saturday willing to help me root I have tried every method... I do where I have done wrong
Click to expand...
Click to collapse
I & a few others used this a few times,the still pics might be better since it gives you time to reread any step. I put some tips in the comment section. It's basically be the manual dirtycow way (thread with the 120+ pages).
http://android.gadgethacks.com/how-to/root-your-t-mobile-lg-v20-using-dirty-cow-0175329/

2muchspl said:
I & a few others used this a few times,the still pics might be better since it gives you time to reread any step. I put some tips in the comment section. It's basically be the manual dirtycow way (thread with the 120+ pages).
http://android.gadgethacks.com/how-to/root-your-t-mobile-lg-v20-using-dirty-cow-0175329/
Click to expand...
Click to collapse
I figured it out. It turns out that I was using the smaller portable version of adb I went ahead and install android sdk n all the files again n it worked perfectly!! ????

egren58 said:
I figured it out. It turns out that I was using the smaller portable version of adb I went ahead and install android sdk n all the files again n it worked perfectly!!
Click to expand...
Click to collapse
Congrats & welcome to the club!!!:good:
Don't forget not to do a factory reset from inside Android,only in TWRP.

2muchspl said:
Congrats & welcome to the club!!!:good:
Don't forget not to do a factory reset from inside Android,only in TWRP.
Click to expand...
Click to collapse
I formated data bia twrp when I first booted. But one thing is.. I cant figure out how to boot into twrp is it power and volume up?

egren58 said:
I formated data bia twrp when I first booted. But one thing is.. I cant figure out how to boot into twrp is it power and volume up?
Click to expand...
Click to collapse
Power and Volume down

2muchspl said:
Power and Volume down
Click to expand...
Click to collapse
Yeah.. Doesn't do anything but take a screenshot than it just sits there.. Wtf

egren58 said:
Yeah.. Doesn't do anything but take a screenshot than it just sits there.. Wtf
Click to expand...
Click to collapse
Sorry should have added this is during the boot up stage..here is a copy & paste I keep handy:
While the device is powered off, press and hold Vol - and Power button. When you see the LG logo quickly release only the power button and re-press and hold the power button (Never let go of the Vol - button) This will boot you into the LG Factory reset screen. ONLY USE THIS METHOD IF YOU HAVE TWRP INSTALLED!!!!! OTHERWISE YOU WILL FACTORY RESET YOUR DEVICE!!!!! Choose yes to both options and you will be rebooted into TWRP. TWRP intercepts this command and ignores the factory reset part.

xDEMON87x said:
https://www.youtube.com/watch?v=fZEL96MPLvY , follow this guide..
Click to expand...
Click to collapse
When you state follow this guide ( i have to say the LG dev community is kinda of rude and does not even explain anything to new comers from other devices...) Do you mean i need to follow every step or some steps this is why i say the LG Dev community is all over the place nothing is set in stone there is not one way to do like most Samsung users are used to. I would hope that you could elaborate a little more if you are offering to help.
I am not trying to be a jerk i'm just use to nicer dev community. I have done dev work... I have not had any other device besides Samsung for the longest time and i and will be switching back once the S8 or note 8 comes out.
To get me but i would like to root this device and i would like more then a point here to do it because you don't have some time to explain what needs to be done....
Again i am not trying to be rude just trying to learn the process on the LG dev side... Do not want to brick my device if i can prevent it.

ice5192 said:
When you state follow this guide ( i have to say the LG dev community is kinda of rude and does not even explain anything to new comers from other devices...) Do you mean i need to follow every step or some steps this is why i say the LG Dev community is all over the place nothing is set in stone there is not one way to do like most Samsung users are used to. I would hope that you could elaborate a little more if you are offering to help.
I am not trying to be a jerk i'm just use to nicer dev community. I have done dev work... I have not had any other device besides Samsung for the longest time and i and will be switching back once the S8 or note 8 comes out.
To get me but i would like to root this device and i would like more then a point here to do it because you don't have some time to explain what needs to be done....
Again i am not trying to be rude just trying to learn the process on the LG dev side... Do not want to brick my device if i can prevent it.
Click to expand...
Click to collapse
Yes every step i am new as well and i got to say this was the most complex toot i have ever done. But every single comand bust be typed.. Ignore the $ sign. Install sdk not the smaller version of adb.