Database Info

Bricked MAXX, Need Help

Hello,
I have been crack flashing for a long time, but when I got the Droid Maxx from verizon I was disappointed at the lack of an unlocked bootloader. I had been running safestrap and was getting the phone ready to return for a refund so I can get the developer edition.
So, it looks like using safestrap I completely wiped the system partition. I can get the phone to boot to flashboot mode or to the safestrap flash screen but that is all.
Using RSDlite I attempted to flash 12.9.0, but get the return message "Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL. On the phone it said:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT."
So it looks like the issue might be because I am flashing the FXZ file for 12.15.15, but I cannot find the FXZ file for it.
I also tried using House of Moto. Attached is a screen shot of what I get.
So basically it looks like I have no ROM whatsoever. Is there a way out of this so I can return the phone for a refund?
Thanks in advance!

I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?

kclantz said:
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
Click to expand...
Click to collapse
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.

ahjee said:
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
Click to expand...
Click to collapse
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.

rds217 said:
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
Click to expand...
Click to collapse
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing

So I just got back from the Verizon store, I went in to see if they could flash the files I need. They told me they couldn't but gave me a number at motorola to see if they would e-mail the files to me.
Unfortunately that didn't work. Motorola said I could send the phone in for a repair, and that was my only option.
I think I'll take the second option and wait until someone posts the files and flash them with RSD Lite.
I just hope that happens soon, as I am wanting to return the phone and get the developer edition. I have until Saturday to return it and I doubt they will give me a refund with it in this state.

ahjee said:
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
Click to expand...
Click to collapse
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
jcase said:
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse

rds217 said:
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
Click to expand...
Click to collapse
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.

kclantz said:
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
Click to expand...
Click to collapse
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk

erishasnobattery said:
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Thanks, that was what I was afraid of. I guess now I will check obsessively for the new FXZ files. Got have some way to spend my day (you know, as opposed to doing my job ).

OTA downloaded, and captured... It begins || update 5/7/16

ADDED INSTRUCTIONS AT END OF POST*****
Got it.... Rooted, twrp, the whole deal. On 6.0. I'll post instructions in the middle of the week for everybody.
Unfortunately if you already did the other method, you are screwed for now. Because the method I used required me to flash a stock 5.1.1.
Standby
_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|
So there I am sitting on my computer last night, when a notification pops up on my V10 .... The old "congratulations, you've won first prize in an update contest!"
Lo and behold, the MM update had downloaded (at record speeds I might add).
Without wasting a minute, I navigated to the cache partition and copied it to my internal folder (see attachment), then backed it up on drive.
So... We'll just skip to the good part...
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
I'll save you all the curiosity and let you know that I am going to look into this option to flash the OTA this weekend. I'm going to assemble a compatibility analysis and if everything checks out, I'll flash it.
Standby for carnage.
****INSTRUCTIONS
OK... I really owe everybody here an apology for taking so long to get an official instruction up. Work has been crazy this week. But I wanted to be able to take some time to do this. So here we go...
But wait... Before we even start, please for the love of God do your homework here. Please go read through chains thread about his app, how it works, etc. The interface is straight forward enough, but there are other things to understand. Please just understand what you are doing, and please verify checksums of anything you download. This is very important.
And thank chainfire, not me.
PRE-FLASH REQUIREMENTS:
1. First and foremost, you MUST be on the latest version of MM TWRP. There is a thread in the development section for this, with instruction on how to flash it, find that thread. Get it installed. This is a must. You must also verify adb and fastboot are working fully on your device.
2. You must be 100% Stock (but rooted) on the latest TMO V10 5.1 1 firmware and ROM, no custom kernels, nothing. Stock, with the exception of working root, and the latest 3.0.2.0 Marshmallow TWRP. When I say stock I mean no deodex, no system apps removed, this is an absolute requirement. The reason for this is mostly to avoid the update.zip from aborting as it does checks for presence of apps within system, etc. If you have to flash a stock ROM before doing this, don't do it as an "in line" queue before you flash the OTA in flashfire. Do it separate.
3. You must have the official OTA downloaded and on your internal SD card. Also, put the latest superSU version 2.67 on an external card, and remove the SD card from the device. The md5 for the OTA is 280ad51eb96457df097df5a088a535af9
Once you have checked those 3 boxes. You are ready to proceed.
4. Install flashfire. I was on version 32.
5. Open flashfire, grant it root
6. Go into the setting of the app, check the "Flash boot loaders" and "Freeload" box.
7. Find the OTA package, queue it up with "flash zip or ota" (small + sign at the bottom right of the screen)
It is important to note that after the flashing process completes, you will want to power off the device, and boot it into fastboot mode to unlock the boot loader.
8. Execute the update.
9. After it finishes, power off the device.
10. Boot into fastboot by holding down the volume down button, and with the button held down, plug the USB cable into your computer.
11. Once in fastboot, type the following command and hit enter:
Code:
fastboot oem unlock
Let it run for a bit, it is going to wipe your data.
12. After it completes (your terminal should give you a time displayed for the operation).... Unplug the phone, and yank the battery.
13. Pop in your Micro SD card (with superSU 2.67 flashable on it) then manually boot the phone into recovery mode. You are going to flash superSU again as a sanity check. I did this because if for some reason FF didn't flash superSU, and then the system wrote over your recovery during your first boot... You'd be absolutely dicked stuck on stock MM with no way of getting root back for now. I like verification...
To boot the v10 into recovery mode manually, simply have the device powered off, then hold the volume down and power button at the same time. AS SOON as you see the boot screen (not to be confused by the boot animation) released the power button for just a little less than a second then press and hold it again (keep the volume down button pressed the whole time). It may or may not be absolutely critical that you don't screw this part up. You need to get into recovery at this point to validate root being installed.
This should take you into 2 sequential screens, both asking about clearing data, select yes for both (don't worry, it won't, it will take you into TWRP.
Once in twrp... Mount your SD card in the twrp settings, and flash superSU.
Reboot afterwards. Done.
After you do this, you will be in 100% stock, rooted MM.
You might need to flash twrp again (do it the normal way, you are done with flash fire now), but root, you will have, and full functionality, you will also have, with everything working.

Dont do it. No root for MM at the moment.

Double0EK said:
Dont do it. No root for MM at the moment.
Click to expand...
Click to collapse
Unless you use Eliminator74's rooted rom which is the official MM update from T-Mobile.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

what he's considering guys is flashing the ota.zip via flashfire which can with some devices maintain root and recovery.

markbencze said:
what he's considering guys is flashing the ota.zip via flashfire which can with some devices maintain root and recovery.
Click to expand...
Click to collapse
I'm debating that myself
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

Standing by!
Sent from my pretty nifty brand new LG V10

Ok. Im actually interested in the outcome.

I think a lot of us are curious to see if it works. For all we know this is the solution that we've had the entire time. the question is, is anyone brave/crazy/foolish enough to try it? It might work great, but then again it could brick your phone given LG devices are untested trying this. there are several devices that were also untested that it did work on so who knows. But the app does have the capabilities to flash a stock update.zip and maintain boot root and recovery. I would think you'd have to reunlock your bootloader after flashing though in order to boot.

anyone know where exactly update.zip downloaded to? mine just downloaded and I don't see anything large in /cache

In for results

dimm0k said:
anyone know where exactly update.zip downloaded to? mine just downloaded and I don't see anything large in /cache
Click to expand...
Click to collapse
Mine is in my cache folder. It says update.zip and it is 1.03 GB
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

A think tank.
If the update is zip, can the flash be done with TWRP plus superSU?!

truckerdewd said:
Mine is in my cache folder. It says update.zip and it is 1.03 GB
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Click to expand...
Click to collapse
interesting... everyone's seems to be there, but after running a search of the filesystem I see /data/data/com.google.android.gms/app_download/update.zip

truckerdewd said:
Mine is in my cache folder. It says update.zip and it is 1.03 GB
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Click to expand...
Click to collapse
so is mine

dimm0k said:
interesting... everyone's seems to be there, but after running a search of the filesystem I see /data/data/com.google.android.gms/app_download/update.zip
Click to expand...
Click to collapse
That's weird. Wonder why your's went there?
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

See OP... got it.

warBeard_actual said:
See OP... got it.
Click to expand...
Click to collapse
Got what? Is in you used Flashfire and updated via ota and were able to retain root and TWRP? Sorry, I"m running g on almost no sleep cause my truck broke down and is in the shop and it's hard to sleep in the customer lounge of a Freightliner dealership.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

Can't wait for that guide @warBeard_actual. You are one brave soul for taking the risk. Props.

crashnova said:
Can't wait for that guide @warBeard_actual. You are one brave soul for taking the risk. Props.
Click to expand...
Click to collapse
I couldn't agree more. Noe just need to get the time to do it on my phone.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

truckerdewd said:
I couldn't agree more. Noe just need to get the time to do it on my phone.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Click to expand...
Click to collapse
I woke up to the OTA this morning. I find it odd tho because i thought OTAs were disabled on siraltus rom. I would try FF but don't eant to risk bricking until OP shares the steps he took.

Root 20l w/Dirty Cow

I had been reading up on the Dirty Cow exploit/root method, and it seemed to be compatible with all Android devices, so I took a little chance with my v10, and it worked perfectly! I was on the stock unrooted 20l update, and followed all the steps here: https://github.com/jcadduono/android_external_dirtycow#running
Notes:
-I put our TWRP image and SuperSu zip on the root of my sdcard
-For the very last command, replace 'twrp.img' with the name of your TWRP image file(or change the name of your TWRP fiile to twrp.img ).
-Like it says in the instructions, the phone did look like maybe it bricked at one point, with a strange backlighting on the Tmobile boot screen. It worked out tho!
-My boot loader was unlocked prior to doing these steps
Info thread, v20: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Got all the files here: https://build.nethunter.com/android-tools/dirtycow/arm64/

YrrchSebor said:
I had been reading up on the Dirty Cow exploit/root method, and it seemed to be compatible with all Android devices, so I took a little chance with my v10, and it worked perfectly! I was on the stock unrooted 20l update, and followed all the steps here: https://github.com/jcadduono/android_external_dirtycow#running
Notes:
-I put our TWRP image and SuperSu zip on the root of my sdcard
-For the very last command, replace 'twrp.img' with the name of your TWRP image file(or change the name of your TWRP fiile to twrp.img ).
-Like it says in the instructions, the phone did look like maybe it bricked at one point, with a strange backlighting on the Tmobile boot screen. It worked out tho!
Info thread, v20: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Got all the files here: https://build.nethunter.com/android-tools/dirtycow/arm64/
Click to expand...
Click to collapse
Great job. You know technically these same instructions should work for ANY of the v10 variants ..verizon...at&t etc....including the ones that up till now didn't have root at all.

Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app

YrrchSebor said:
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
It requires an unlocked boot loader.

YrrchSebor said:
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes but for example verizon's comes with an unlocked bootloader...they just only had root for the 5.x rom's and none for the 6.0.

famewolf said:
Yes but for example verizon's comes with an unlocked bootloader...they just only had root for the 5.x rom's and none for the 6.0.
Click to expand...
Click to collapse
Gotcha yeah, it seems like good news for all phones with unlockable bootloaders until Google, and then the OEMs, patch the exploit.
Sent from my LG-H901 using XDA-Developers mobile app

will this factory reset my phone?

CrimsonSaber5G said:
will this factory reset my phone?
Click to expand...
Click to collapse
Nope. Unlocking your bootloader will but this won't in itself.
Sent from my LG-H901 using XDA-Developers mobile app

thank you, and i have the tmobile variant, that means my bootloader is already unlocked??

CrimsonSaber5G said:
thank you, and i have the tmobile variant, that means my bootloader is already unlocked??
Click to expand...
Click to collapse
No, it means it's unlockable, but you have to actively unlock it. There should be a thread here somewhere if you haven't done that yet, but it's just boot into bootloader and then 'fastboot oem unlock'
Edit: in case you need it there are great instructions in the v20 thread that I linked in the first post.
Sent from my LG-H901 using XDA-Developers mobile app

YrrchSebor said:
Gotcha yeah, it seems like good news for all phones with unlockable bootloaders until Google, and then the OEMs, patch the exploit.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
The cow method means copy on write...
This means as anything is written it is copied (or flashed or burned; whatever you want to call your desired definition)
You could in theory copy dummy files to a temp location and actually write to a permanent location...
Or am I thinking wrong about it?
If this is a viable option to ALL phones I don't think Google or manufactures could (or would for that matter) actually patch this kind of exploit as it would be super time consuming.

just confirming that Root 20l w/Dirty Cow does work.
Finally got my replacement V10 back, and all is a go again. Stock rooted,
Not sure the novice should try this, as its pretty nerve racking. If you follow the directions correctly it does work great.
Surprised they have closed this backdoor yet,
thanks for being the first to try this on a V10.

je2854 said:
The cow method means copy on write...
This means as anything is written it is copied (or flashed or burned; whatever you want to call your desired definition)
You could in theory copy dummy files to a temp location and actually write to a permanent location...
Or am I thinking wrong about it?
If this is a viable option to ALL phones I don't think Google or manufactures could (or would for that matter) actually patch this kind of exploit as it would be super time consuming.
Click to expand...
Click to collapse
I think it's considered a very serious vulnerability that must and will be patched soon. They can't have root access so easily obtained on any device.

Amd4life said:
just confirming that Root 20l w/Dirty Cow does work.
Finally got my replacement V10 back, and all is a go again. Stock rooted,
Not sure the novice should try this, as its pretty nerve racking. If you follow the directions correctly it does work great.
Surprised they have closed this backdoor yet,
thanks for being the first to try this on a V10.
Click to expand...
Click to collapse
You're welcome, and thanks for confirming. That one step where the screen goes weirdly backlit with the Tmo splash screen is a bit nerve-wracking, and so is writing recovery this way, but I was comforted by the fact that you can just tell it to to write to the recovery partition rather than having to know the more technical name/location(not sure if this was possible a few years back?)
Anyway, if I did brick I was gonna go straight to the store and buy a ZTE Zmax Pro for $180 haha.

Which reminds me, does anyone know if there is a way to simply push su into /system once you have the root shell, instead of writing recovery to flash SuperSu? Just curious. I sorta wanted to do that but then I just went with TWRP.

YrrchSebor said:
Which reminds me, does anyone know if there is a way to simply push su into /system once you have the root shell, instead of writing recovery to flash SuperSu? Just curious. I sorta wanted to do that but then I just went with TWRP.
Click to expand...
Click to collapse
No. The shell has limited access...it has just enough permissions to write recovery and access some things on boot...you need to get it a recovery where you can then flash a zip to install superuser.

Thanks so much for this info, I was actually about to post a new thread to see if root for 20L had been achieved.
But a few questions:
Is there a KDZ/TOT available for 20L? Or is it delivered in update.zip format via OTA?
Is there a way to root 20L without touching system partition? Like, you know, systemless root? I was thinking that maybe it might be possible to flash Magisk from TWRP then install systemless phh Superuser or (less preferable for me) SuperSU. This way I can still take the official Nougat OTA when it hits, without losing root. But the catch is, TWRP needs to be accessible first.
Well, time to sleep for now, it's been a long 3 days, subsisting on Monster and cigs. I'll tackle this when I eventually wake up.

Like the last guy, I've got a million questions on this. I need to find the changelog on 20L to begin with, because if they didn't fix the VoLTE silence on calling, then it's useless to me. I wonder where the OP was with his existing V10.. because I'm currently on 20J rooted with twrp. Seems with the instructions posted, I would have to use LG bridge to go back to 100% stock, then upgrade to 20L then hope this works. Again, the radios are probably modified so there's probably some kind of anti-rollback involved as well.
Great post though! Great work discovering this! Definitely in the right direction!

AnonVendetta said:
Thanks so much for this info, I was actually about to post a new thread to see if root for 20L had been achieved.
But a few questions:
Is there a KDZ/TOT available for 20L? Or is it delivered in update.zip format via OTA?
Is there a way to root 20L without touching system partition? Like, you know, systemless root? I was thinking that maybe it might be possible to flash Magisk from TWRP then install systemless phh Superuser or (less preferable for me) SuperSU. This way I can still take the official Nougat OTA when it hits, without losing root. But the catch is, TWRP needs to be accessible first.
Well, time to sleep for now, it's been a long 3 days, subsisting on Monster and cigs. I'll tackle this when I eventually wake up.
Click to expand...
Click to collapse
There is a 20l KDZ floating around in some other threads. Not sure if there is or will be a systemless root, never even done it myself [emoji4]
Sent from my LG-H901 using XDA-Developers mobile app

joesee said:
Like the last guy, I've got a million questions on this. I need to find the changelog on 20L to begin with, because if they didn't fix the VoLTE silence on calling, then it's useless to me. I wonder where the OP was with his existing V10.. because I'm currently on 20J rooted with twrp. Seems with the instructions posted, I would have to use LG bridge to go back to 100% stock, then upgrade to 20L then hope this works. Again, the radios are probably modified so there's probably some kind of anti-rollback involved as well.
Great post though! Great work discovering this! Definitely in the right direction!
Click to expand...
Click to collapse
The Volte silence bug is fixed in 20l, as many have reported. I had updated officially to 20l and was stock unrooted prior to this. But for people who are rooted on 20j or earlier, I believe Eliminator has released a pre-rooted update, so maybe you'd wanna do that instead.
Sent from my LG-H901 using XDA-Developers mobile app

7.1.2 Upgrade Help

Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.

Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available

bush911 said:
Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available
Click to expand...
Click to collapse
I have tried to stay away from flash fire because I know a couple buddies who soft-bricked by using it.

xxbilxx said:
Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.
Click to expand...
Click to collapse
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2

TonikJDK said:
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
Click to expand...
Click to collapse
I don't have to sideload the March security patch first?

xxbilxx said:
I don't have to sideload the March security patch first?
Click to expand...
Click to collapse
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).

TonikJDK said:
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).
Click to expand...
Click to collapse
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.

xxbilxx said:
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.
Click to expand...
Click to collapse
Correct, you want N2G47E.

TonikJDK said:
Correct, you want N2G47E.
Click to expand...
Click to collapse
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!

xxbilxx said:
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!
Click to expand...
Click to collapse
No problem at all. Second to the last post in the same thread I linked you to before. It all still works fine on 7.1.2. Did all of this myself yesterday afternoon.

Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways

Download the OTA, Flash it from TWRP, reflash twrp and reboot

mikeprius said:
Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways
Click to expand...
Click to collapse
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.

robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
yeah saved it. There was only one section that had the w- and it was right before the update image. I can try it again at some point later on but that's what I did. I tried to sideload adb the OTA first which does not wipe data but kept getting an error saying device not found and emulator.

robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
Your instructions worked perfectly for me. I'm nor sure what setup the other guy had, but I did make sure I removed the -w like 20 times.

Juli112 said:
Download the OTA, Flash it from TWRP, reflash twrp and reboot
Click to expand...
Click to collapse
are you on the latest twrp rc2 or rc1?

Has anyone received the update ota on a stock google pixel XL for verizon. Mine keeps telling me I am current?

Help to recover LG-V20 H990DS AME

Dear All,
2 days back I was trying to unlock my LG-V20 phone using DirtySanta Method on this thread
https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296?nocache=1
For me it is not working & I want to return it to original LG ROM something goeas wrong & I was stuck on grey ribbon on screen (which I can't read anything) or I can boot it to fastboot command. I was trying to put phone on download mode to use it with LGUP but the program give me unknown device. When I check the forum they said I have to flash kernel. I was trying alot but nothing works with me. Suddenly LGUP define my device as US996 instead of H990DS. So I download the official ROM of US996 & flash it to my device it accept it & screen works normally but the device keeps restarting. It boots to welcome screen or even LG logo then restart. I can't even set it up. anyone can help on this problem??? How can I return it back to original H990DS ROM???:crying::crying::crying:
Another thing is that fastboot commands can't do anything like format & wipe it says device is locked

Hey, no worries. Your device can be saved. Dirty santa can be a bit** to get it to work. Took me like 2 days and several tries...
I'm quite sure I came across this ribbon screen. For me it looked like grey static from a tv without signal, quite scary.
So, the only not good thing you did was to flash the US996 ROM. You have a H990DS, it will not work... But it can be fixed, don't panic.
It's normal that the H990 is seen as US996 by LGUP after flashing the engineering bootloader. Every rooted H990 runs on this one, because there is no unlocked BL available other then this. So that means you came quite far with dirty santa...
I believe the reason that you phone can't start is, LGUP changed your partition layout from H990 to US996 (which will not work)
I'm going from memory here, so I'm not sure about the details. There is a thread in the forum explaining well how to recover a V20 with LGUP / (Uppercut could be important to fix unknown device / allow to cross flash). Follow this one and use the right H990DS Rom to reflash everything and repartition your device correctly. Maybe you have to play with the options like upgrade or repartition. BUT DON'T DO ANYTHING THAT IS NOT MENTIONED AS SAFE TO DO. You could even erase you BL. Then you have a nice brick...
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
You should be able to try with dirtysanta again, I promise it will work, and then you effort wasn't for nothing.
Here in the guide it even tells you that that phone will be detected as US996, the tipps here are good as well..
https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
Let me know how it went...
Best regards
Daniel

NoName! said:
Hey, no worries. Your device can be saved. Dirty santa can be a bit** to get it to work. Took me like 2 days and several tries...
I'm quite sure I came across this ribbon screen. For me it looked like grey static from a tv without signal, quite scary.
So, the only not good thing you did was to flash the US996 ROM. You have a H990DS, it will not work... But it can be fixed, don't panic.
It's normal that the H990 is seen as US996 by LGUP after flashing the engineering bootloader. Every rooted H990 runs on this one, because there is no unlocked BL available other then this. So that means you came quite far with dirty santa...
I believe the reason that you phone can't start is, LGUP changed your partition layout from H990 to US996 (which will not work)
I'm going from memory here, so I'm not sure about the details. There is a thread in the forum explaining well how to recover a V20 with LGUP / (Uppercut could be important to fix unknown device / allow to cross flash). Follow this one and use the right H990DS Rom to reflash everything and repartition your device correctly. Maybe you have to play with the options like upgrade or repartition. BUT DON'T DO ANYTHING THAT IS NOT MENTIONED AS SAFE TO DO. You could even erase you BL. Then you have a nice brick...
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
You should be able to try with dirtysanta again, I promise it will work, and then you effort wasn't for nothing.
Here in the guide it even tells you that that phone will be detected as US996, the tipps here are good as well..
https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
Let me know how it went...
Best regards
Daniel
Click to expand...
Click to collapse
Thanks a looooooooooot Daniel. Finally my LG is back to normal. I don't want DirtySanta anymore. My device was out for more than 20 days because of this.

Im very glad, that I could help you. It's a nice device and even better when working correctly.
Thanks for letting me know that it worked.
All the best to you too

Philadelphia said:
Thanks a looooooooooot Daniel. Finally my LG is back to normal. I don't want DirtySanta anymore. My device was out for more than 20 days because of this.
Click to expand...
Click to collapse
Its a bit of an op for real, but worth it when done

dornz said:
Its a bit of an op for real, but worth it when done
Click to expand...
Click to collapse
Does it pass SafetyNet with edXoposed installed?

iTzFeRReTTi said:
Does it pass SafetyNet with edXoposed installed?
Click to expand...
Click to collapse
Nope,

iTzFeRReTTi said:
Does it pass SafetyNet with edXoposed installed?
Click to expand...
Click to collapse
Worth the root

dornz said:
Nope,
Click to expand...
Click to collapse
Are you using the edXposed canary?

iTzFeRReTTi said:
Does it pass SafetyNet with edXoposed installed?
Click to expand...
Click to collapse
Glad you mentioned that about safety net, flashed me the Oreo rooted to check that, :silly: