I wasn't thinking and tried to apply the latest update (20f i think) OTA while I was rooted with TWRP working. My phone rebooted, but now only boots to TWRP, even if I select "System" in the reboot options it comes back to the TWRP screen. Is there any easy way to fix this, or do I need to do a full fresh install from scratch? I'm hoping there is a quick fix.
Thanks,
Dave
dbs179 said:
I wasn't thinking and tried to apply the latest update (20f i think) OTA while I was rooted with TWRP working. My phone rebooted, but now only boots to TWRP, even if I select "System" in the reboot options it comes back to the TWRP screen. Is there any easy way to fix this, or do I need to do a full fresh install from scratch? I'm hoping there is a quick fix.
Thanks,
Dave
Click to expand...
Click to collapse
Technically the OTA should have failed, so odd if it actually installed, but never take otas whole rooted. Anyways, first thing to try is this:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Let it go into TWRP and go to advanced and terminal and type the above and reboot. Hopefully that will help, if not do the following:
1) Use lgup or uppercut to flash 20A kdz.
2) use recowvery method for TWRP and root
3) visit autoprimes thread and download the 20F complete zip that you can flash in TWRP (make sure to reflash SuperSU or magisk after flashing 20F, also I recommend deleting the recovery from boot.p file after flashing new 20F update to ensure you don't lose TWRP).
To flash v20a via LGUP --> https://forum.xda-developers.com/lg-g5/how-to/info-autos-g5-thread-t3350648/
To root --> https://forum.xda-developers.com/tmobile-lg-g5/how-to/guide-root-twrp-lg-g5-using-t3580264
To download TWRP Flashable stock rom zips --> https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-10j-rom-flashable-zips-imgs-t3491363
jeffsga88 said:
Technically the OTA should have failed, so odd if it actually installed, but never take otas whole rooted. Anyways, first thing to try is this:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Let it go into TWRP and go to advanced and terminal and type the above and reboot. Hopefully that will help, if not do the following:
1) Use lgup or uppercut to flash 20A kdz.
2) use recowvery method for TWRP and root
3) visit autoprimes thread and download the 20F complete zip that you can flash in TWRP (make sure to reflash SuperSU or magisk after flashing 20F, also I recommend deleting the recovery from boot.p file after flashing new 20F update to ensure you don't lose TWRP).
Click to expand...
Click to collapse
I was too far down the rabbit hole once I saw your post to try. I just ended up putting 20A back on, using recowvery and then putting Autoprimes 20F overtop. Worked great, just took me more time than I had planned to mess with my phone. I guess that is what I get for not thinking.. Thanks for the tip anyway, maybe it will come in handy for someone else.
Thanks,
Dave
dbs179 said:
I was too far down the rabbit hole once I saw your post to try. I just ended up putting 20A back on, using recowvery and then putting Autoprimes 20F overtop. Worked great, just took me more time than I had planned to mess with my phone. I guess that is what I get for not thinking.. Thanks for the tip anyway, maybe it will come in handy for someone else.
Thanks,
Dave
Click to expand...
Click to collapse
Well at least you were able to get it fixed. You may want to Diane otas so you don't have that issue anymore. Only issue with disabling the otas on T-Mobile is that it leads to Google play services wakelocks and battery drain. I used to have a fix on MM that disabled otas and got rid of the wakelocks, but it didn't seem to work on N. Here's the commands to disable otas from autoprimes thread:
Code:
adb shell "su -c 'pm disable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver'"
adb shell "su -c 'pm disable com.google.android.gms/.update.SystemUpdateService$Receiver'"
adb shell "su -c 'pm disable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver'"
Related
is there a way to unroot and lock the bootloader again ?
quattro_rs said:
is there a way to unroot and lock the bootloader again ?
Click to expand...
Click to collapse
Yes.
Several discussions about it already in here.
To relock the bootloader is as simple as "fastboot oem lock" command.
There's a couple of different ways to get the root out, they're all mentioned in the thread for it.
but as of now no way to flash the stock recovery
slowz3r said:
but as of now no way to flash the stock recovery
Click to expand...
Click to collapse
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
distortedloop said:
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
Click to expand...
Click to collapse
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
slowz3r said:
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
Click to expand...
Click to collapse
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
can someone explain how to do it step by step im new at this ?
ok i managed to lock the bootloader but im still not sure how to unroot the device !
distortedloop said:
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Click to expand...
Click to collapse
Oh, alright
google hasnt released a full OS for flashing have they?
quattro_rs said:
can someone explain how to do it step by step im new at this ?
Click to expand...
Click to collapse
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
In the event you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 . This will restore everything, including the stock recovery image. Then as mentioned above go into the bootloader/fastboot mode and enter "fastboot oem lock" in ADB.
(All credit goes to the original author(s) of the linked thread!)
Click to expand...
Click to collapse
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
slowz3r said:
Oh, alright
google hasnt released a full OS for flashing have they?
Click to expand...
Click to collapse
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
distortedloop said:
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
Click to expand...
Click to collapse
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
slowz3r said:
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
Click to expand...
Click to collapse
Ditto.
Ditto.
Ditto (for the most part, CWM isn't bad, but I also prefer Amon_RA).
distortedloop said:
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
Click to expand...
Click to collapse
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Requirements:
-Clockwork recovery or other custom recovery
Click to expand...
Click to collapse
quattro_rs said:
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Click to expand...
Click to collapse
the stock recovery does not allow you to flash custom/unsigned roms or other files for that matter.
so a custom Recovery is required, as of now the only one I believe is available is ClockWorkMod
got it all working now thanks to you and distortedloop .
thanks a lot guys.
Ok people, in the interest of making a new recovery for the A701, I need a stock recovery image from a JB build.
Right now, there are way too many versions of CWM, mostly for the A700.
If you have JB installed, "and" unlocked bootloader, you need to fastboot my full ADB R/W boot.img from here; This will allow ADB commands.
http://forum.xda-developers.com/showthread.php?t=1934056
NOTE: If you have "some" version of CWM installed, don't try. I need a "stock" Recovery image.
Commands are as follows via ADB:
adb shell dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/sdcard/stock-recovery.img
adb pull /sdcard/stock-recovery.img
adb shell rm /sdcard/stock-recovery.img
MD
if you apply the latest OTA Update an let the Recovery be Restored, than you´ve got the Stock Recovery back.
After that you can dump it
or am i wrong?
meier2009 said:
if you apply the latest OTA Update an let the Recovery be Restored, than you´ve got the Stock Recovery back.
After that you can dump it
or am i wrong?
Click to expand...
Click to collapse
The problem, is that I have a CWM installed on JB. But, it doesn;t work on the 701 for installing the latest 701 update. Even after modifying the installer script.
Unless I am missing something Meir, so if I am, please tell me.
Want to try installing with a stock recovery. So far, the update fails using CWM. Did you use a different Version of CWM? Too many versions to keep track of.
Which is why I need a stock recovery of 701 JB.
MD
Here you go : http://vache-android.com/Tablets/A701/JB_A701_Stock-Recovery.img
Dumped from the latest update (1.027.00 / RV05RC07_WW_GEN1) !
paugustin said:
Here you go : http://vache-android.com/Tablets/A701/JB_A701_Stock-Recovery.img
Dumped from the latest update (1.027.00 / RV05RC07_WW_GEN1) !
Click to expand...
Click to collapse
Many thanks mate. Will give this a shot when I get home. Hopefully that update will take now.
MD
Heres the latest update from LG.
Must be at least 20f with TWRP to flash this.
To get TWRP go here: (Kdz to 20f if on 20g)
https://forum.xda-developers.com/showthread.php?t=3533338
Do NOT wipe system or you might get stuck in twrp bootloop.
**********************
FLASHING INSTRUCTIONS
**********************
1. MUST BE IN 20F.
2. DO NOT FORMAT SYSTEM.
2. TWRP BACKUP FIRST
3. Flash from TWRP.
DOWNLOAD
LG-V521-20G-Stock-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705254
LG-V521-20G-Stock-Debloated-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705822
***********************************
LG-V521-TWRP.ZIP (Thanks to shabbypenguin)
***Also adds flashing TWRP to recoverybak so if an error comes up your stock recovery doesn't get reflashed.
https://www.androidfilehost.com/?fid=673368273298934005
***********************************************
COMING FROM ANOTHER ROM FLASHING INSTRUCTIONS
***********************************************
1. TWRP BACKUP FIRST
2. PLACE ROM IN INTERNAL STORAGE
3. WIPE DATA, CACHE, DALVIK/ART CACHE, SYSTEM
4. FLASH ROM FROM INTERNAL STORAGE.
*****IF IT REBOOTS BEFORE FINISHING FLASH, PRESS AND HOLD VOLUME DOWN AND POWER TILL OFF.
*****THEN ON REBOOT WITH VOLUME DOWN AND POWER PRESS, LET GO OF POWER ONLY FOR A SLIT SECOND AND *****REPRESS TO GO INTO FACTORY RESET MODE. THEN SAY YET, AND IT WILL GET YOU BACK TO TWRP.
*****IN TWRP, GO TO REBOOT AND SELECT POWER OFF. THEN GO TO STEP 4.
**************
ERROR???
**************
If you wipe system then flash a rom you might get stuck in twrp bootloop.
Here's a fix by ralphwiggum1:
https://forum.xda-developers.com/showpost.php?p=70851933&postcount=39
If that fix fails, then flashing stock recovery is another option. Then you'll have to reroot and get twrp again. If your on 20g, you'll have to kdz 20f and start over.
LG-V521-STOCK-RECOVERY.zip
https://www.androidfilehost.com/?fid=745425885120710531
Sent from my LG-H811 using Tapatalk
Thank you!, working 100%
LG-V521-20G-Stock-Debloated-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705822
Sent from my LG-V521 using Tapatalk
MicroMod777 said:
LG-V521-20G-Stock-Debloated-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705822
Sent from my LG-V521 using Tapatalk
Click to expand...
Click to collapse
what was debloated?
SiNJiN76 said:
what was debloated?
Click to expand...
Click to collapse
Most gapps and tmo bloat.
Sent from my LG-V521 using Tapatalk
SuperSU is not detecting root in LG-V521-20G-Stock-Debloated-Rooted.zip
LG-V521-20G-Stock-Debloated-Rooted.zip doesn't seem to have TWRP either.
Am I missing something?
rbadh91 said:
SuperSU is not detecting root in LG-V521-20G-Stock-Debloated-Rooted.zip
LG-V521-20G-Stock-Debloated-Rooted.zip doesn't seem to have TWRP either.
Am I missing something?
Click to expand...
Click to collapse
Odd. Flash just SuperSU then:
https://forum.xda-developers.com/showthread.php?t=3452703
Sent from my LG-H872 using Tapatalk
MicroMod777 said:
Odd. Flash just SuperSU then:
https://forum.xda-developers.com/showthread.php?t=3452703
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
It went back to stock recovery after flashing the zip. adb reboot recovery takes me to stock recovery.
Vol Down + Power to boot, and letting go of Power holding down Vol Down, then pressing Power & Vol Up takes me to the "hard reset" prompt, and it actually wipes device when selecting yes. I'm thinking the recovery has changed in 20G and it wipes the device instead of taking you to recovery.
Joey's Root Checker shows "Sorry! Root access is not properly installed on this device". SuperSU shows "There's no SU binary installed and SuperSU cannot install it. This is a problem."
I have a feeling I'll have to downgrade to 20F using KDZ.
EDIT: Weird...FlashFire shows "Root was found, but access could not be acquired! Supported roots: SuperSU, Magisk, CM SU (SELinux/Permissive)) Found root: (null)".
Installed SuperSU app, no luck. Tried Superuser app, no luck.
rbadh91 said:
SuperSU is not detecting root in LG-V521-20G-Stock-Debloated-Rooted.zip
LG-V521-20G-Stock-Debloated-Rooted.zip doesn't seem to have TWRP either.
Am I missing something?
Click to expand...
Click to collapse
I had the same issue. Lost root and twrp. Had to downgrade and start from scratch.
NoMoreBackdoors said:
I had the same issue. Lost root and twrp. Had to downgrade and start from scratch.
Click to expand...
Click to collapse
Yea I've had this happen multiple times now. Twrp is somewhat buggy where if theres a crash during flashing, or if you format the system partition, somehow theres a failsafe feature that restores the stock recovery.
I thought I had it figured out and made a flashable zip for twrp that also flashes it to the recoverybak partition. But it happened aga7n.
Sent from my LG-V521 using Tapatalk
MicroMod777 said:
Yea I've had this happen multiple times now. Twrp is somewhat buggy where if theres a crash during flashing, or if you format the system partition, somehow theres a failsafe feature that restores the stock recovery.
I thought I had it figured out and made a flashable zip for twrp that also flashes it to the recoverybak partition. But it happened aga7n.
Sent from my LG-V521 using Tapatalk
Click to expand...
Click to collapse
There's another update on my tablet...(after flashing your zip from 2-22). Will you be doing another zip with this new update?
New update is 95.22MB. I'm guessing security update. I would be wary, as the 20g update patches dirty cow, but still allows downgrade to 20f. This could block downgrade. Any brave souls out there want to confirm?
LvDisturbed1 said:
New update is 95.22MB. I'm guessing security update. I would be wary, as the 20g update patches dirty cow, but still allows downgrade to 20f. This could block downgrade. Any brave souls out there want to confirm?
Click to expand...
Click to collapse
I know I'm late, but I just picked one of these tablets up this week. I didn't think much about what I was doing, and did all OTA updates that where available. This was on 10/25/2017 or so. I was able to then use Uppercut and LGUP to flash backwards to V52120i_00_0619.kdz and successfully root, and install TWRP.
I didn't keep stock long, I jumped over to Lineage OS 14.1.
Be warned though, on Lineage OS the weekly on 10/27/2017 will cause a bootloop in TWRP. At least it did for me. After install, and while stuck in bootloop it is pretty easy to fix:
1. Open ADB Shell and run the following 2 commands:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Then reboot and all will be well.
sgrant said:
I know I'm late, but I just picked one of these tablets up this week. I didn't think much about what I was doing, and did all OTA updates that where available. This was on 10/25/2017 or so. I was able to then use Uppercut and LGUP to flash backwards to V52120i_00_0619.kdz and successfully root, and install TWRP.
I didn't keep stock long, I jumped over to Lineage OS 14.1.
Be warned though, on Lineage OS the weekly on 10/27/2017 will cause a bootloop in TWRP. At least it did for me. After install, and while stuck in bootloop it is pretty easy to fix:
1. Open ADB Shell and run the following 2 commands:
Then reboot and all will be well.
Click to expand...
Click to collapse
QUOTE
I've been running stock for a while and had this in a drawer for a year. I decided I'd start using it in my kitchen to pull up recipes on chrome. I decided to do a "factory reset" to start "clean" forgetting the warning not to do it. Now I'm stuck in a TWRP bootloop.
How can I get out of this?
Or should I switch to lineage?
Why there is no LG-V521-20N version?
THIS IS NOT AN EASY METHOD, THIS IS NOT FOR NOOBS, SOMEONE CAN SIMPLIFY IT, BUT AS OF RIGHT NOW ITS SOMEWHAT COMPLICATED
IF YOU'RE PHONE IS NOT ALREADY ON THE DIRTYSANTA BOOTLOADER THEN THIS WILL NOT WORK FOR YOU
Thanks to @me2151 for giving us these backup files and clearing up the method!
Prerequisites:
Your device needs at least 6GB free on the internal SD Card
Your device needs to be able to boot into TWRP and fastboot mode
You need access to a computer to run ADB commands to the phone
Technical Explanation (I suggest you ignore this.)
Basically, we're going to put the ZV3 system.img on the sdcard, then dd if= it to the system partition, then boot into the bootloader and flash the aboot and boot images and then preform a userdata wipe and reboot.
Instructions!
Backup your phone, this will wipe EVERYTHING off of it.
Download the ZV3 System Image and the aboot and boot backup from the 2nd post on this thread.
Extract both of these to a folder and have ADB accessable in that folder.
Now boot the phone into recovery mode, this can be done easiest by running "adb reboot recovery" from CMD when the phones connected.
Once your phone is loaded into TWRP, and you're in the directory with system.img, please run "adb push system.img /sdcard/" and wait for the file to copy over.
You can check how far it is by opening the SD Card in the file explorer and checking what the file size is, once it's at 5.46GB it's done.
Type into CMD "adb shell" and then paste "dd if=/sdcard/system.img of=/dev/block/platform/soc/624000.ufshc/by-name/system"
This process will also take a lot of time, but you cannot check how far it is, CMD will just give a blinking prompt with something around the lines of "~ # [6n" once it's done.
After it's finished and you see "~ # [6n" type exit and press Enter.
Once you see "~ # [6n" type "TWRP reboot bootloader" into the prompt and press Enter.
Once your phone is recognized and you see fastboot open on your phone type "fastboot flash boot bootbackup.img" followed by "fastboot flash aboot abootbackup.img" RUN EACH OF THESE 3 TIMES
Once that's completed type "fastboot format userdata", once that's completed type "fastboot reboot"
The phone should reboot back to stock firmware! Enjoy!
Video Tutorial if it helps:
https://www.youtube.com/watch?v=DXnfm002l6o
If you have any questions or get stuck somewhere, DO NOT TURN THE PHONE OFF, REPLY TO THE THREAD AND GET HELP SO YOU DON'T BRICK THE ENTIRE PHONE TO A UNRECOVERABLE STATE.
Link for the System Image: https://drive.google.com/file/d/0B390u0mt1F4CSzAxZ2ZLd0xwMW8/view?usp=sharing
Link for the aboot and boot backups: https://drive.google.com/file/d/0B390u0mt1F4CNi1ybW9kVW5KZUk/view?usp=sharing
I will definitely try it.
There, I added a video to make it a bit easier if that helps.
Can the zv3 be downloaded and flashed to the LS997 using flash tool so that i can root with dirty santa . i currently have the zv8 on my device. I want to root and have twrp. If so is there further instructions you can post in order for me to do this? Any help appreciated. Thank you
DavidBeckett.db said:
Can the zv3 be downloaded and flashed to the LS997 using flash tool so that i can root with dirty santa . i currently have the zv8 on my device. I want to root and have twrp. If so is there further instructions you can post in order for me to do this? Any help appreciated. Thank you
Click to expand...
Click to collapse
Unforunatenely zv8 has rollback protection so this won't work.
DavidBeckett.db said:
Can the zv3 be downloaded and flashed to the LS997 using flash tool so that i can root with dirty santa . i currently have the zv8 on my device. I want to root and have twrp. If so is there further instructions you can post in order for me to do this? Any help appreciated. Thank you
Click to expand...
Click to collapse
Yeah if there's a method that allowed for downgrading, it'd be very public, sorry!
Thanks guys if i could try if i could flash twrp on this dreaded zv8...any help appreciated..thanks
DavidBeckett.db said:
Thanks guys if i could try if i could flash twrp on this dreaded zv8...any help appreciated..thanks
Click to expand...
Click to collapse
unfortunately u can't root zv7 or zv8
Worked perfectly. And thanks for the video made it so much easier to follow.
Hello, is this possible on zv6 firmware?
golinale said:
Hello, is this possible on zv6 firmware?
Click to expand...
Click to collapse
No
Sent from my LG-LS997 using Tapatalk
I know zv7 and zv8 was mentioned, but does this work with zv6?
Also, those with the unlocked Sprint version purchased from eBay, did anyone update to a new version and retain unlock ?
joeminati said:
I know zv7 and zv8 was mentioned, but does this work with zv6?
Click to expand...
Click to collapse
This is to return to stock after you've used dirty Santa. Are you in zv6 and bootloader unlocked/rooted? Then this will work to return to stock and get rid of the debug bootloader red triangle.
I am on ZV6 but dirty santa never worked with ZV6.
Just up to ZV5...
joeminati said:
I am on ZV6 but dirty santa never worked with ZV6.
Just up to ZV5...
Click to expand...
Click to collapse
Oh right, then you don't need this because you're not bootloader unlocked anyway. This basically reverses dirty Santa.
Oh I ask cause I could use the ZV3 to actually DirtySanta this phone since I am on ZV6. :s
But thanks.
joeminati said:
Oh I ask cause I could use the ZV3 to actually DirtySanta this phone since I am on ZV6. :s
But thanks.
Click to expand...
Click to collapse
You can do it to go back to zv3.... Once on the zv6 bootloader... This is only for people thatvrooted and did the dirty santa
Sent from my LG-LS997 using Tapatalk
YOU ARE AWESOME! This worked perfectly - my phone is back to stock. No more "untrusted" screen on boot. Full stock like the day I bought it.
I'm passing on my phone to another person, so I wanted it back to original software. This rocked it.
This worked with no problems. I want to thank you as I've been looking for a way to do this for a while.
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
good luck on building lineage, the g6 never had any development so i dont anticipate the g7 will get much either. if i was you id concentrate on twrp so we can at least flash gsi based roms.
Is this the original factory signed rom? (I.e. is it possible to fully flash and relock bootloader?)
Also wondering if anyone has the latest full rom (29.114-16-7).
Thanks in advance!
ptn107 said:
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
Click to expand...
Click to collapse
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
smokinu said:
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
Click to expand...
Click to collapse
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
ptn107,
Thanks for the write-up. I'm familiar with a similar approach using TWRP (booted, but not installed) and dd copying the individual partitions. I will give your script a try. Should save a lot of time!
Is there a way to copy partitions without root? My biggest concern is taking on an OTA update (currently 16-7), without having the original signed images to revert back to stock and relock the bootloader. Motorola has historically been bad at providing factory roms. If there is a clever way to unroot, take an OTA, save original, and re-root....I'd be a happy camper!
/dev is user root and group root so root is necessary.
Is there a clever way to take an OTA update and get a copy of the new boot.img? From what i understand, you have to unroot to take an OTA update.
BTW...good luck with the newborns!! Mine is now 3 and is still as much of a handful as when he was a newborn.
ptn107 said:
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
Click to expand...
Click to collapse
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
clcombs262 said:
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
Click to expand...
Click to collapse
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
smokinu said:
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
Click to expand...
Click to collapse
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
ptn107 said:
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
Click to expand...
Click to collapse
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
smokinu said:
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
Click to expand...
Click to collapse
Wow. That actually worked. I had to do both commands like 6 times one after the other but it worked.
Thank you!
No problem! Glad I could help. Found that one by accident.
smokinu said:
No problem! Glad I could help. Found that one by accident.
Click to expand...
Click to collapse
I would have never found that out.
fastboot without root
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
The zip file itself cannot be flashed as it's not in proper update format. You'll have to extract and flash the contents via fastboot. To get to fastboot, power off the device then hold power and volume down until you see the bootloader screen, and then connect it via USB to a pc
Follow the instructions here to get back to stock
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
Sounds like you wiped the system partition then tried to flash the unflashable zip file (hence, no system)
First, always make backups.
Second, you can still get into fastboot and manually update/restore
You can also use the moto software to recover the device.
Get it into fastboot, start from there. It is 100% an easy recovery process
warBeard_actual said:
You can also use the moto software to recover the device.
Click to expand...
Click to collapse
This fixed it in a jiffy. Making backups from now on!
Question to the experts:
Unlocking the bootloader and rooting a phone is stressful times for those of us who (like me) only do this once every few years when we buy a new phone. On some phones, after attempts at routing, I've been stuck for days without a phone till some distant helpful person helped me back to a working rooted phone. Other times it was very simple. But the experience leaves you scared.
Yes I know it's my own (and similar other uneducated) fault because we did something wrong that would be obvious to any expert. But it happens to the rest of us no matter how many threads we read.
So my question is, if the phone becomes non functional following erroneous commands or files (my own unintentional error), will this same 'moto recovery' restore things?
Where do I find out more 'how' to use this Moto software and where this 'Moto software recovery' is to be found?
Thank you.
Edit
Just to clarify things, this is my first Moto phone which is why I don't know what the Moto software recovery is. Is it what you get by pressing Power-volume down?