Hi guys, since the development is started i think that we also need a way to restore the watch to the stock FW.
HOWTO:
- download from the following links the boot, recovery and system image;
- reboot to fastboot and:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and then go to recovery and do a wipe data / factory reset.
EDIT:
For some strange reason the system img flash didn't work properly on a device i could test. Here is the workaround:
1- First of all download the TWRP from the other thread and fastboot boot it:
Code:
fastboot boot TWRP2.8.7.0-Sturgeon.img
2 - Then push the system.img in the sdcard so:
Code:
adb push system.img /sdcard/
3 - Now flash it:
Code:
adb shell
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
4 - reboot
Link:
https://mega.nz/#!rgRQHRrb!lgQCvqH-qkuqitPRRXfCad29MdmJ6ynaUHJDr0hjeLM
https://mega.nz/#!ahgjxA4R!y8Hb0CBVBRwUr0tA3HeFrrqh0ALAiMyqJu0pLsBsAD8
https://mega.nz/#!2pYVBDpA!wQJT8LDcffk7uxEmrsqna6MKWIODD-FqBO_k4Poml7g
What would be really awesome is TWRP.
brizey said:
What would be really awesome is TWRP.
Click to expand...
Click to collapse
My build pc is broken and on my macbook i dont have enought free space to build the twrp.
brizey said:
What would be really awesome is TWRP.
Click to expand...
Click to collapse
ok i compiled from my daughter's pc.... pls test it http://forum.xda-developers.com/hua...overy-twrp-build-huawei-watch-tester-t3222675
Skin1980 said:
ok i compiled from my daughter's pc.... pls test it http://forum.xda-developers.com/hua...overy-twrp-build-huawei-watch-tester-t3222675
Click to expand...
Click to collapse
Will try to get to it today. I am booted up on your kernel now as a test (just fastboot booted it). Will do the same to test the recovery once I get a chance.
Edit: btw...when I have pulled images before, I had always done something like
cat /dev/mtd/mtd2 > /sdcard/boot.img (or wherever the boot image is mounted).
in an ADB shell. Do these things even have an sdcard location to temporarily store the images? Just curious on how you pulled them.
brizey said:
Will try to get to it today. I am booted up on your kernel now as a test (just fastboot booted it). Will do the same to test the recovery once I get a chance.
Click to expand...
Click to collapse
Nice, thank you
Updated OP
return from what?
Motawa88 said:
return from what?
Click to expand...
Click to collapse
Having su installed. When you install skin1980's kernel, it uses chainfire's autoroot method, which modifies your system partition. So to make sure OTAs work, this is a way to get back to a clean system image that will pass the hash checks done by the OTA script.
I tried this and for some reason every reboot goes straight back to recovery. Did I do something wrong or am I screwed haha. everything seems to work correctly but then just reboots to recovery.
edit:
Now I just get an icon of an android on floor with chest open haha
Njzkrish said:
I tried this and for some reason every reboot goes straight back to recovery. Did I do something wrong or am I screwed haha. everything seems to work correctly but then just reboots to recovery.
edit:
Now I just get an icon of an android on floor with chest open haha
Click to expand...
Click to collapse
That's the stock recovery.
restore back to stock
question, did bootloader unlock flash twrp then immediately backup my watch before flash the kernel. if i restore this backup file will it get back to stock?
Thanx
vinny.1967 said:
question, did bootloader unlock flash twrp then immediately backup my watch before flash the kernel. if i restore this backup file will it get back to stock?
Thanx
Click to expand...
Click to collapse
If you flash the recovery (twrp) and reboot into twrp to backup then you are backing up the stock boot, system and data.
Flashing the kernel will replace the boot.img only so restoring the twrp backup prior to this will restore your stock boot, system and data. At this stage your recovery is still custom (twrp)
So I want to return to stock to sideload the LCB43B update. However, I'm having issues following the directions listed. The recovery img and boot img flash fine but when I try to flash the system img, I get:
Code:
target reported max download size of 63963136 bytes
Invalid sparse file format at header magi
So I follow the steps to boot into twrp and it boots fine but adb push and shell gives error no device found. I unlocked my bootloader and flashed your kernel so idk if that is causing the errors.
Kingdavid7 said:
So I want to return to stock to sideload the LCB43B update. However, I'm having issues following the directions listed. The recovery img and boot img flash fine but when I try to flash the system img, I get:
Code:
target reported max download size of 63963136 bytes
Invalid sparse file format at header magi
So I follow the steps to boot into twrp and it boots fine but adb push and shell gives error no device found. I unlocked my bootloader and flashed your kernel so idk if that is causing the errors.
Click to expand...
Click to collapse
You should check your drivers
Skin1980 said:
You should check your drivers
Click to expand...
Click to collapse
Nvm I got it
Skin1980 said:
You should check your drivers
Click to expand...
Click to collapse
Hi,
I have the same problem.... As it has solved ?
I'm uploading a zip file that can be flashed with twrp. It might restore stock system, boot and recovery so, after the flash, you should only relock bootloader anda you are good to go.
It's untested so only people that know how to restore the watch should try it.
Like i said, i dont own this watch so i can't test for you. Sorry.
https://mega.nz/#!vkBSCR4C!hZzbAMe7PZPBG88Bfm3mBi6hAfDHCpLMArIwpY6xhHc
Does anybody could be able to tall me what is the reason to root this watch? What are the benefits?
Sent from my SM-N920C using XDA Free mobile app
Skin1980 said:
I'm uploading a zip file that can be flashed with twrp. It might restore stock system, boot and recovery so, after the flash, you should only relock bootloader anda you are good to go.
It's untested so only people that know how to restore the watch should try it.
Like i said, i dont own this watch so i can't test for you. Sorry.
https://mega.nz/#!vkBSCR4C!hZzbAMe7PZPBG88Bfm3mBi6hAfDHCpLMArIwpY6xhHc
Click to expand...
Click to collapse
Has anyone thus far tried to relock the bootloader? I usually don't unlock any of my device until using them for a couple weeks to make sure I don't have a lemon. I'm curious if it's unlocked if Huawei would check, or if their system would show it was being previously unlocked.
Related
ok you need to have clockworkmod installed...
Code:
fastboot flash recovery recovery.img
(insecure boot.img)
unzip boot.img.zip, boot to bootloader and
Code:
fastboot flash boot boot.img
or flash JRN84D-insecure-boot.zip from recovery
-put the CWM-SuperSU-v0.92-mod.zip on your sd and flash
done. :good:
if you have problems...
flash Koush's Jellybean repack (IMM76I OR IMM30D) http://d-h.st/Gkh
If recovery isn't sticking for you, delete recovery-from-boot.p in /system
I can do this for the other superuser as well...this is chainfire's super su
Thanks. May I clarify if I have to do both to get root or either one?
mcdull said:
Thanks. May I clarify if I have to do both to get root or either one?
Click to expand...
Click to collapse
the boot image is insecure...not necessarily needed
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
mcdull said:
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
Click to expand...
Click to collapse
sure, give me a minute
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
bootloader mode -> reflash clockwork recovery using fastboot.
pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Thanks guys appreciate the tip.
not working
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
krishmasand said:
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
Click to expand...
Click to collapse
reboot, then open supersu and then update
Worked like a charm, I've got clockwork back after a little adb action and now I'm restoring some apps with titanium. Can't wait to see the development on this. Just think I almost sold this phone and bought a Galaxy S3 today, may wait a week or so now.
Thanks guys you are amazing!!!
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
tramane said:
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
Click to expand...
Click to collapse
ok your the second guy...first hasn't responded back. did you reboot and try again?
which "jellybean" version are you on? koush's on rom manager seems to be the best (no wifi issues for one)
ogdobber said:
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
other superuser
still doesn't work, do you think you can try the other SuperUser app? D:
Enhanced said:
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
Click to expand...
Click to collapse
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
[please delete]
IINexusII said:
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
Click to expand...
Click to collapse
I knew common sense told me that I would need to delete the /system/recovery-from-boot.p file, but it wasn't posted here so I didn't bother.
Thanks.
Hey guys, this is my first post on XDA forum.
So I've recently bought a nexus 7, I used wugfresh's root kit to root my nexus but then it didn't work... so I've tired the auto root by chainfire. Then I was able to get root. So then I went to playstore and downloaded rom manager to install CWM. I went to recovery then I get this message:
E : Cant mount /cache/recovery/log etc.....
I've tried everything I can do such as researching, changing recovery, and watching a youtube tutorial but nothing helped.
Thanks.
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
nhizzat said:
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
Click to expand...
Click to collapse
I tried to format using wugfresh couple times but still not working...
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- https://developers.google.com/android/nexus/images
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
_MetalHead_ said:
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- Link Removed
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
Click to expand...
Click to collapse
I tried to flash TWRP but its still the same error code
z3r0c311 said:
I tried to flash TWRP but its still the same error code
Click to expand...
Click to collapse
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
_MetalHead_ said:
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
Click to expand...
Click to collapse
It would be great if u could tell me the commands, im nubby with this fastboot thing.
z3r0c311 said:
It would be great if u could tell me the commands, im nubby with this fastboot thing.
Click to expand...
Click to collapse
I gave you the commands in my first post in this thread.
Here's a guide to get you started-
http://forum.xda-developers.com/showthread.php?t=2277112
Sorry for another nubby question but how do I get flash_all.bat?
z3r0c311 said:
Sorry for another nubby question but how do I get flash_all.bat?
Click to expand...
Click to collapse
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
_MetalHead_ said:
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
Click to expand...
Click to collapse
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
z3r0c311 said:
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
Click to expand...
Click to collapse
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
_MetalHead_ said:
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
Click to expand...
Click to collapse
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
z3r0c311 said:
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
Click to expand...
Click to collapse
Did the system image flash successfully?
_MetalHead_ said:
Did the system image flash successfully?
Click to expand...
Click to collapse
using flash-all command, yeah
z3r0c311 said:
using flash-all command, yeah
Click to expand...
Click to collapse
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
_MetalHead_ said:
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
z3r0c311 said:
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
Click to expand...
Click to collapse
No, you can only flash custom ROMs if you have a custom recovery.
My setup
Pixel XL from Verizon
Bootloader unlocked
Bootloader Version 8996-0121001-1611091517
Baseband 8996-012511-1611190200
Android 7.1.1 NOF26V
Kernal 3.18.31-g367e645 Dec 7, 23, 2016
Twrp Version 3.0.2.0 RC1
I have tried following this guide to get root access https://www.xda-developers.com/root-is-now-available-for-the-google-pixel-and-pixel-xl/
My steps are
1. boot phone into fastboot
2. from pc run fastboot boot boot-to-root.img
3. the phone reboots
4. Phone is stuck with the 4 colored dots jumping over each other
5. i've given this screen up to 30 minutes with no results.
6. Forcing a reboot causes the same issue
7. Flash stock android via the official google factory image method
I have attempted this other method as well http://www.theandroidsoul.com/root-pixel-xl-magisk/
But after TWRP says it's successful, i boot into my OS and there is no supersu and if i manually install supersu, it says no root access.
You are doing it the old way that was for 7.1.
You want SU 2.79 SR3
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
And you want TWRP RC1.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
I would not install TWRP at this point. So copy SU to your phone. Then boot to TWRP.
Fastboot BOOT twrp.img
With twrp.img being the correct name of the file. Then in TWRP install the SU you copied.
The old way... Sheesh, there's only so much space up here. But thank you. You've saved be a big headache when my XL finally arrives.
Edit: you boot TWRP, not flash through fastboot?
Larzzzz82 said:
The old way... Sheesh, there's only so much space up here. But thank you. You've saved be a big headache when my XL finally arrives.
Edit: you boot TWRP, not flash through fastboot?
Click to expand...
Click to collapse
You boot it, always.
If you want to install it you copy the twrp ZIP to the phone. Boot it with the TWRP image file then install the twrp zip from within twrp.
Gotta be done that way. Partition layout has changes, they are a bit intertwined now.
I dont install TWRP anymore.
That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.
Larzzzz82 said:
That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.
Click to expand...
Click to collapse
That might be doable, I am not a ROM guy. Root and kernel only....and I always got a PC.
so I would just want to pull down the twrp RC1 image file, boot from fastboot without flashing it, and use it to flash the SU SR3? All i want is root access at the moment on the pixel XL.
if i understand this right, this will just give me SU with root, and not install any form of TWRP.
steber04 said:
so I would just want to pull down the twrp RC1 image file, boot from fastboot without flashing it, and use it to flash the SU SR3? All i want is root access at the moment on the pixel XL.
if i understand this right, this will just give me SU with root, and not install any form of TWRP.
Click to expand...
Click to collapse
Exactly.
Larzzzz82 said:
That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.
Click to expand...
Click to collapse
You don't need a PC if you just install TWRP.
TonikJDK said:
Exactly.
Click to expand...
Click to collapse
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?
steber04 said:
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?
Click to expand...
Click to collapse
What files are you pushing that you cannot just load directly with the device powered up?
steber04 said:
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?
Click to expand...
Click to collapse
You will need fastboot, so you can fastboot boot twrp. I don't push the SU zip with adb, I just copy/download it to the phone before I reboot into Fastboot. Make sure you get Fastboot from Google, not the Minimal one.
https://developer.android.com/studio/releases/platform-tools.html
Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
I have not heard of anyone successfully loading an OTA through TWRP. Either restore stock recovery (install boot.img to both slots) and sideload with the Google instructions or run the flash-all (remove the -w) to use the factory image. Either way, you ere going to be reverting to stock recovery.
P.S. Your message doesn't make sense since you say you have TWRP on your device but then are showing that you used fastboot boot to run the TWRP .img file. If TWRP was on your device, you wouldn't have to use that command. You would just have entered TWRP with the adb reboot recovery command. I am guessing you are rebooting into the bootloader screen where either you run the TWRP .img or run the flash-all.
I also thought I saw a previous post somewhere that said you cannot skip an update, so going from December to February may not work.....not sure...
But definitely you need to load the OTA via regular Recovery using adb not TWRP....
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
parakleet said:
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
Click to expand...
Click to collapse
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
spotmark said:
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
Click to expand...
Click to collapse
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Badger50 said:
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Click to expand...
Click to collapse
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the factory zips. That doesn't mean my memory isn't shot either.
spotmark said:
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the Factory zips. That doesn't mean my memory isn't shot either.
Click to expand...
Click to collapse
Yeah, it was possible, just not many people knew about it, but it definitely works :good:
Flashing them that is.
I went from dec to feb update no problem
hilla_killa said:
I went from dec to feb update no problem
Click to expand...
Click to collapse
Sideloading or factory image method?
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Badbrad17 said:
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Click to expand...
Click to collapse
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Badger50 said:
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Click to expand...
Click to collapse
Yes that is what I did.
Badbrad17 said:
Yes that is what I did.
Click to expand...
Click to collapse
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Badger50 said:
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Click to expand...
Click to collapse
OH I di not know I could do it in TWRP. Will try that first. thanks
Badbrad17 said:
OH I di not know I could do it in TWRP. Will try that first. thanks
Click to expand...
Click to collapse
Just make sure you flash it to the boot partition :good:
raphytaffy said:
Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
Click to expand...
Click to collapse
I've installed 3 latest updates from twrp ...
Download the latest OTA, you have to be in stock Rom and Kernel stock ... and have last twrp on your phone... Flash OTA and twrp installer to keep twrp ... restart in twrp for magisk or restart system ... benefits
sorry for my bad english.
Badger50 said:
Just make sure you flash it to the boot partition :good:
Click to expand...
Click to collapse
How do I make sure of this? Sorry I'm a bit of a noob.
Badbrad17 said:
How do I make sure of this? Sorry I'm a bit of a noob.
Click to expand...
Click to collapse
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Badger50 said:
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Click to expand...
Click to collapse
Well I managed to do that, but now when my phone rebooted the touch screen no longer responds. Very strange. It all loads fine and I can see my screen but nothing works. I tried to go back into recovery and I get the little dead Android guy laying on his back with a red exclamation point and "No Command" below it.
Any ideas?
Warning! Warning! Warning!
All yours Data and files from internal storage will be lost. So make backup all what you need before continuing​
First read Bootloader Unlock and Root Instruction
So your bootloader is unlocked and you want TWRP-recovery on yours V35.
1. Download the necessary kernel
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware
Boot+TWRPv3.3.1-V35-Pie-ULM20E.img - boot.img from V350ULM20e firmware
2. Flashing
a) Via Root: if you already have unlocked bootloader and root just copy downloaded f-or-e.img on internal sdcard, run CMD on PC and type
adb shell
su
dd if=/sdcard/_downloaded_.img of=/dev/block/bootdevice/by-name/boot_a
or
dd if=/sdcard/_downloaded_.img.img of=/dev/block/bootdevice/by-name/boot_b
reboot recovery
b) Via Qfil: all you need to know is here Bootloader Unlock and Root Instruction
3. Go to recovery ( via buttons or adb reboot recovery )
In recovery you will see a message that the data is encrypted and you need a password, which you not have.
Click cancel, agree to change system files.
In main menu click Install and select attached file Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
In Wipe menu swipe right, then go back, Format Data - type "yes"
Install latest Magisk.zip
Reboot - System
Done!
Edit:
New Instructions in English: https://github.com/kaneorotar/LG-V35-Tinkering-Instructions/blob/master/README_EN.MD
Original:
I see that you are using my TWRP build.
Here is my original instructions (mainly in Chinese but has enough English to make sense): https://github.com/kaneorotar/LG-V35-Tinkering-Instructions
Yes, you are right. I just patched boot.img
thanks, it worked perfectly for me.
Thanks a lot, not a lot of development and love on this device, I just wanted to say some of us really appreciate this.
SaiLas said:
Warning! Warning! Warning!
All yours Data and files from internal storage will be lost. So make backup all what you need before continuing​
First read Bootloader Unlock and Root Instruction
So your bootloader is unlocked and you want TWRP-recovery on yours V35.
1. Download the necessary kernel
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware
Boot+TWRPv3.3.1-V35-Pie-ULM20E.img - boot.img from V350ULM20e firmware
2. Flashing
a) Via Root: if you already have unlocked bootloader and root just copy downloaded f-or-e.img on internal sdcard, run CMD on PC and type
adb shell
su
dd if=/sdcard/_downloaded_.img of=/dev/block/bootdevice/by-name/boot_a
or
dd if=/sdcard/_downloaded_.img.img of=/dev/block/bootdevice/by-name/boot_b
reboot recovery
b) Via Qfil: all you need to know is here Bootloader Unlock and Root Instruction
3. Go to recovery ( via buttons or adb reboot recovery )
In recovery you will see a message that the data is encrypted and you need a password, which you not have.
Click cancel, agree to change system files.
In main menu click Install and select attached file Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
In Wipe menu swipe right, then go back, Format Data - type "yes"
Install latest Magisk.zip
Reboot - System
Done!
Click to expand...
Click to collapse
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?
What's the benefit without ROM's for rooting your phone? Magisk modules?
notanymore said:
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
SaiLas said:
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
Click to expand...
Click to collapse
Hey thanks!
X-Nemesis said:
What's the benefit without ROM's for rooting your phone? Magisk modules?
Click to expand...
Click to collapse
Yes. On my V30 I've never installed a custom ROM. Rooted stock firmware when the TWRP custom recovery (gift by itself for backups), Magisk mods, Xposed mods. You can tweak yourself without having to install a ROM.
During flashing, you may see error messages about 'unable to unmount vendor'. This is fine as long as the zip flashing doesn't fail halfway.
Click to expand...
Click to collapse
realllllllllllly important. I kept getting unable to mount xx (one of vendor system systemroot randomly) and didn't notice it meant the magisk sticked until I gave up and was ready to settle with no twrp.
YUP
notanymore said:
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?
Click to expand...
Click to collapse
SaiLas said:
Yes, you are right. I just patched boot.img
Click to expand...
Click to collapse
links dont work
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware
SaiLas said:
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
Click to expand...
Click to collapse
after flashing twrp on a/b, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (http://Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip), and Magisk, my v35 wont boot, it got stuck on LG logo, I can go back to TWRP.
Is there any kernel, boot img I have to flash it? Im on this V350ULM20f_00_NAO_US_OP_0218.kdz Pie build
zfk110 said:
after flashing twrp on a/b, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (http://Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip), and Magisk, my v35 wont boot, it got stuck on LG logo, I can go back to TWRP.
Is there any kernel, boot img I have to flash it? Im on this V350ULM20f_00_NAO_US_OP_0218.kdz Pie build
Click to expand...
Click to collapse
Did you wipe your data after flashing the files?
The same happened to me once, I solved that by flashing via upgrade the stock firmware, and then re-rooted.
Excelstar said:
Did you wipe your data after flashing the files?
The same happened to me once, I solved that by flashing via upgrade the stock firmware, and then re-rooted.
Click to expand...
Click to collapse
I just went back to TWRP and used his boot.img to flash within TWRP to boot's partition and then I was able to boot without any issues, I was thinking the same, but it looked more work to do.
kaneorotar said:
Edit:
New Instructions in English: https://github.com/kaneorotar/LG-V35-Tinkering-Instructions/blob/master/README_EN.MD
Original:
I see that you are using my TWRP build.
Here is my original instructions (mainly in Chinese but has enough English to make sense): https://github.com/kaneorotar/LG-V35-Tinkering-Instructions
Click to expand...
Click to collapse
Just wanted to say thanks for the updated instructions. Worked like a charm.
Hello, can you help me with the TWRP file for the LG V350AWM?