WI501Q - M6E69X - TWRP Backup of System & Boot - stockrecovery.img (28 Feb 2017) - Asus ZenWatch 2

M6E69X only for WI501Q
TWRP Backup & stockrecoveryM6E69X: uploaded by @Lrs121
【Version】
WI501Q _M6E69X
【Model Name】
ZenWatch 2
【Release Date】
???
【Release Note】
???

@RoyanArt
I won't be able to have access to adb till late tonight at the earliest, can you pull it using the following command?
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/ of=/sdcard/
Those commands should copy the stock recovery IMG to your sdcard directory
Edit. Last command might be
dd if=/dev/block/platform/msm_sdcc.1/by-name/ of=/sdcard/stockrecovery.IMG
I think you have to specify the destination IMG file name
Sent from my ONEPLUS A3000 using Tapatalk

RoyanArt said:
MWD59 to M6E69N update.zip (adb sideload) : go to this thread
TWRP Backup : googledrive
Who can help to pull the stock recovery ? @Lrs121 , @slothdabski
【Version】
M6E69N
【Model Name】
ZenWatch 2
【Release Date】
2016/10/17
【Release Note】
1.Fix security vulnerabilities ( Update to Sep 2016 of Android Security Bulletins )
2.Fix issue "Watch could not pair with iPhone 7"
Click to expand...
Click to collapse
FYI: The stock recovery link is broken.

I can get to it in a couple hours. Out running errands and I've been meaning to make a backup
Here it is: Stock M6E69N recovery

slothdabski said:
@RoyanArt
I won't be able to have access to adb till late tonight at the earliest, can you pull it using the following command?
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/ of=/sdcard/
Those commands should copy the stock recovery IMG to your sdcard directory
Edit. Last command might be
dd if=/dev/block/platform/msm_sdcc.1/by-name/ of=/sdcard/stockrecovery.IMG
I think you have to specify the destination IMG file name
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
sorry, i cant do it, because i've flashed twrp recovery :good:
Lrs121 said:
I can get to it in a couple hours. Out running errands and I've been meaning to make a backup
Here it is: Stock M6E69N recovery
Click to expand...
Click to collapse
Thanks for the stock recovery, ill put your post to top :good::good:

Want to root/twrp Zenwatch 2 m6e69n - ANY HELP would be GREAT!!!
I got my Z2 m6e69n about a week ago (10/16/16) and it's great but I want root & twrp like I have on my other Android devices. Don't know that it matters, I'm using LS990 (Sprint LG G3 on KK 4.4.2). I've been searching XDA and YouTube for clear, detailed info on how to root and get TWRP on the watch but not having a lot of luck.
What I have found is:
- I have activated developer options
- How to get into recovery, how to access bootloader, how to unlock bootloader (http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623) THANKS to arbitercu
...but nothing detailed about installing TWRP. Maybe I'm blind or just not understanding but any help would be great. I simply don't want to BRICK my Zenwatch.
- ALSO, VERY LITTLE EXPERIENCE with ADB and side loading which I think might be important to mention.
- Last thing, basically want to get some of the BLOAT off the device and get the most out of it.
Almost forgot:
- Zenwatch 2 m6e69n Sparrow (1.63")
Thanks in advance!

dsabine said:
I got my Z2 m6e69n about a week ago (10/16/16) and it's great but I want root & twrp like I have on my other Android devices. Don't know that it matters, I'm using LS990 (Sprint LG G3 on KK 4.4.2). I've been searching XDA and YouTube for clear, detailed info on how to root and get TWRP on the watch but not having a lot of luck.
What I have found is:
- I have activated developer options
- How to get into recovery, how to access bootloader, how to unlock bootloader (http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623) THANKS to arbitercu
...but nothing detailed about installing TWRP. Maybe I'm blind or just not understanding but any help would be great. I simply don't want to BRICK my Zenwatch.
- ALSO, VERY LITTLE EXPERIENCE with ADB and side loading which I think might be important to mention.
- Last thing, basically want to get some of the BLOAT off the device and get the most out of it.
Almost forgot:
- Zenwatch 2 m6e69n Sparrow (1.63")
Thanks in advance!
Click to expand...
Click to collapse
How about a little more googling. http://forum.xda-developers.com/zenwatch-2/orig-development/wip-unofficial-twrp-v2-8-7-0-t3321199/
Be careful what you remove. The watch won't function properly without some apps.

edit : no issue quick for wear

Thanks for the thread. :laugh::laugh::laugh:

Could someone provide fastboot flashable .IMG files?
I've ****ed up my watch quite hard by grabbing the wrong system image while the watch was still locked, now I can't even boot it anymore or restore a TWRP backup because the file system seems to be corrupt. I can't save anything in /sdcard without it getting wiped again after a reboot.

EpicLPer said:
Could someone provide fastboot flashable .IMG files?
I've ****ed up my watch quite hard by grabbing the wrong system image while the watch was still locked, now I can't even boot it anymore or restore a TWRP backup because the file system seems to be corrupt. I can't save anything in /sdcard without it getting wiped again after a reboot.
Click to expand...
Click to collapse
What happens when you boot twrp using fastboot? If you can get into twrp, with the bootloader unlocked you might be able to reformat the partitions.
On a side note I think you can format the partitions from fastboot mode

Lrs121 said:
What happens when you boot twrp using fastboot? If you can get into twrp, with the bootloader unlocked you might be able to reformat the partitions.
On a side note I think you can format the partitions from fastboot mode
Click to expand...
Click to collapse
Yeah, I've managed to repair the partitions by erasing and formatting them via fastboot, for whatever reason only formatting them didn't help... I have no clue why. Except boot I've erased + formatted every partition, then booted TWRP via "fastboot boot TWRP" and then was able to push TWRP backup files onto /data/media (/sdcard was broken still for whatever reason). After the first boot it somehow fixed /sdcard too tho it was missing all of its files on there. I simply did a factory reset of the watch after this and now it seems to be back and working again, tho I'm not fully sure because TWRP seems to have some problems still but that could be due to the wonky and, sorry, "****ty" port of TWRP 3.0 someone else made.

EpicLPer said:
Yeah, I've managed to repair the partitions by erasing and formatting them via fastboot, for whatever reason only formatting them didn't help... I have no clue why. Except boot I've erased + formatted every partition, then booted TWRP via "fastboot boot TWRP" and then was able to push TWRP backup files onto /data/media (/sdcard was broken still for whatever reason). After the first boot it somehow fixed /sdcard too tho it was missing all of its files on there. I simply did a factory reset of the watch after this and now it seems to be back and working again, tho I'm not fully sure because TWRP seems to have some problems still but that could be due to the wonky and, sorry, "****ty" port of TWRP 3.0 someone else made.
Click to expand...
Click to collapse
That's good you got it working. As for twrp if I remember right there were some issues with 3.0.0 regarding Android wear that were fixed in later versions. Ever since my galaxy s3, I've taken to building my own for the devices I have or have had. I make them available on my website.

Can anybody provide this for a Zenwatch 2 Wren? It would be appreciated a lot.

Can you help to pull the M6E69S stock recovery ? @Lrs121 , @slothdabski

RoyanArt said:
Can you help to pull the M6E69S stock recovery ? @Lrs121 , @slothdabski
Click to expand...
Click to collapse
Sorry had it pulled the moment the ota went out. I just didnt have it pushed to my server. Sparrow Stock recoveries

OP EDITED & UPDATED
M6E69S
-Version-
WI501Q _M6E69S
-Model Name-
ZenWatch 2
-Release Date-
2016/12/07
-Release Note-
1.Fix security vulnerabilities ( Update to Nov 2016 of Android Security Bulletins

Hey bud, watch just got an update today dec 29th, im rooted with twrp. Ill install a stock recovery sometime but in the mean time it would be nice to get that up for people to side load!
Dont know what the build is called, but i was running M6E69S when i got it.

Can you help to pull the M6E69V stock recovery ? @Lrs121 , @slothdabski

RoyanArt said:
Can you help to pull the M6E69V stock recovery ? @Lrs121 , @slothdabski
Click to expand...
Click to collapse
@RoyanArt Could you please upload the TWRP backup of latest firmware? It would be so appreciated ???

Related

[FIX] Stuck in Custom Recovery [TWRP/CWM] (After trying OTA)

LG G3 Stuck in Recovery Fix
Background
This thread is to help those who get stuck in custom recovery every time they try to boot into the rom.. usually after trying to take an OTA. Now that we're all rooted and unlocked this might be needed soon. Inspired by IOMonster's [FIX] Installed TWRP and now you're stuck after OTA? thread for the LG G2. Sometimes wiping FOTA was not enough and wiping the misc partition was also needed. But wiping the entire partition isn't the best idea. I've made a flashable zip to automate this process to properly fix being stuck in TWRP/CWM due to "stuck fota" or "stuck misc"
This should work on the G2, G Flex, G Pro 2, G3... and possible other LG devices that use the MISC and also have a custom recovery.​Fix
Flash LG_G3_Flash2FixStuckRecovery.zip to backup the current stuck fota/misc partitions and then fix them to allow proper booting.
Flashing LG_G3_Flash2FixStuckRecovery.zip creates a backup of your FOTA and Misc partitions in the /sdcard/FOTAnMisc_Backup/ folder.
1. Download the LG_G3_Flash2FixStuckRecovery.zip and place it on your phone.
You can use TWRP's MTP feature to copy it from computer to phone, use OTG w/connected storage containing zip or use adb push to get the file onto your phone...
Code:
adb push LG_G3_Flash2FixStuckRecovery.zip /sdcard/
DOWNLOAD FROM CODEFIRE HERE
2. Flash LG_G3_Flash2FixStuckRecovery.zip in recovery
or use adb commands below to fix boot issues..
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
[SIZE="1"]dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=256 count=1 conv=notrunc[/SIZE]
reboot
3. Finished
If you are still booting into TWRP/CWM then you may have accidentally flashed the custom recovery img to the boot partition slot instead of the recovery partition slot. Reflash the rom in TWRP/CWM which should fix the boot.img... or download the required boot.img, place on root of internal storage ( /sdcard/ ) and flash the boot.img in TWRP/CWM...
Code:
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
reboot
Click to expand...
Click to collapse
word
I had this problem yesterday, spent hours trying to fix the situation. Had to flash stock firmware and all to solve the issue. NOW you bring this fix when i already fixed my phone lol
all good thanks for this, i will prob need this in the future
autoprime said:
LG G3 Stuck in Recovery Fix
Background
This thread is to help those who get stuck in custom recovery every time they try to boot into the rom.. usually after trying to take an OTA. Now that we're all rooted and unlocked this might be needed soon. Inspired by IOMonster's [FIX] Installed TWRP and now you're stuck after OTA? thread for the LG G2. Sometimes wiping FOTA was not enough and wiping the misc partition was also needed. But wiping the entire partition isn't the best idea. I've made a flashable zip to automate this process to properly fix being stuck in TWRP/CWM due to "stuck fota" or "stuck misc"​Fix
Flash LG_G3_Flash2FixStuckRecovery.zip to backup the current stuck fota/misc partitions and then fix them to allow proper booting.
Flashing LG_G3_Flash2FixStuckRecovery.zip creates a backup of your FOTA and Misc partitions in the /sdcard/FOTAnMisc_Backup/ folder.
1. Download the LG_G3_Flash2FixStuckRecovery.zip and place it on your phone. You can use TWRP's MTP feature to copy it from computer to phone, use OTG w/connected storage containing zip or use adb push to get the file onto your phone...
Code:
adb push LG_G3_Flash2FixStuckRecovery.zip /sdcard/
DOWNLOAD FROM CODEFIRE HERE
2. Flash LG_G3_Flash2FixStuckRecovery.zip in recovery or use adb commands below to fix boot issues..
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=256 count=1 conv=notrunc
reboot
If you are still booting into TWRP/CWM then you may have accidentally flashed the custom recovery img to the boot partition slot instead of the recovery partition slot. Reflash the rom in TWRP/CWM which should fix the boot.img... or download the required boot.img, place on root of internal storage ( /sdcard/ ) and flash the boot.img in TWRP/CWM...
Code:
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
reboot
Click to expand...
Click to collapse
I wish i saw this post yesertday............
I had this problem accidentally installing 10L wish I had this then. Had to run a fix in lg pc suite and start all over again. Great job tho. I know where to come next time I have this problem.
Help !
I have this very problem and I try to flash your file. Now I don't have any recovery any more (I had twrp 2.8.0.0) and the phone has black screen with only "fastboot mode started" on the top left corner. I'm lost, if anyone could help, I have lg g3 d855 with stock v10h installed.
Edit : problem solved, I managed to boot in download mode and flash a kzd rom using flashtool.
your the best! worked like charm!
Also wish i wouldve seen this, had to reflash stock software, lost 80%of my pics.... Thanks for posting, hopefully this will help others not repeat my mistake.....
Thanks!
Worked like a charm, accidentally took the OTA and this fixed things!
---------- Post added at 11:26 AM ---------- Previous post was at 11:18 AM ----------
Is this fix specific to the G3? I have a friend that is having the same issue on an unlock Moto X. Took an OTA update by accident and phone is stuck in a recovery boot loop.
Thoughts?
thanks bro your work is much appreciated
Will this method also work to restore download mode? (Can't connect to fastboot, windows can't recognize my phone).
received OTA file and prevently flashed LG_G3_Flash2FixStuckRecovery.zip
I just received a new OTA file from LG and prevently flashed LG_G3_Flash2FixStuckRecovery.zip.
This created 2 files named stuckfota.img and stuckmisc.img in /sdcard/FOTAnMisc_Backup/ folder.
But when I lanched OTA installation, I get stuck in TWRP. What did I miss ?
How can I have OTA installation finished ? Thanks
So I've been at it for quite a while. The zip.file is on the internal sdcard. went to instal in twrp, selected the file and flashed. got a Zip signature verification failure: 1 Error flashing zip ' /sdcard/LG_G3_Flash2FixStuckRecovery.zip'
Any suggestions are much appreciated. Meanwhile still searching
Thanks
After trying different things I found this and it worked.
http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
This worked to allow me to boot
What caused the issue? I didn't accept the OTA and even blocked it in the phone menu
nest75068 said:
This worked to allow me to boot
What caused the issue? I didn't accept the OTA and even blocked it in the phone menu
Click to expand...
Click to collapse
Same thing happened to me. I disabled it in the phone menu as well and when I got up today it was on TWRP.
Luckily I found this.
Yep
Mine did the same BS. Blocked the OTA as well as the notification. Woke up this morning to this crap.... Thank you for the fix!!! WOOT!
MizSxxyBych said:
Mine did the same BS. Blocked the OTA as well as the notification. Woke up this morning to this crap.... Thank you for the fix!!! WOOT!
Click to expand...
Click to collapse
Same thing happened to me this morning... Is there a way to for sure block this update and this happening again?
same thing to me also. drove to work listened to pandora all the way. clocked in and all i see is team win screen. this fix worked great. hope i can do a nandroid backup now.
nest75068 said:
What caused the issue? I didn't accept the OTA and even blocked it in the phone menu
Click to expand...
Click to collapse
From what I understand, AT&T forced an update lastnight, causing the issue for many of us. (of course, i'm only speaking for AT&T users)
I guess I'm SOL since my partition is encrypted?
Thanks for this. Wish I did a better search before I restored back to stock then re-rooted. Lost all that temporarily important personal data. Glad I know this is here now so I can use it if I foolishly click "Update now" again.

[WIP][Experimental] Twrp v2.8.7.0 [Please go to my updated thread!]

Go here for a updated TWRP thread!
Hey guys I have twrp here however I need help from the community.
The Twrp i have compiled, i have not tested everything yet, so please do not try any function yet, If you want to test out functionality, I found that reflashing stock system.img, boot.img, and recovery.img will probably reverse some damages, however I dont want anyone to mess their watch up (unless you are really brave) also guys flashing this twrp renders android wear useless so please do not flash it, this is going to be a tethered recovery for now. Only fastboot boot this thing anyways, with this itll help advance custom roms.
I have compiled the latest kernel, and I want to see if there is differences in the boot.img's that i have, and the ones that everyone else is running.
The kernel was giving me loads of build errors, but recently i had it built but I cant get it to boot android wear. My theory is that the boot.img i have, has .67, and i compiled .87, and there is something weird there. Unless my fixes broke the kernel, I have no idea but this will hopefully shine light on my issue. I did try .67 multiple times but untar'ing it gives errors and building it doesnt boot it, .87 doesnt have tar issues so IDK
Thanks /u/hamagc! Hopefully ill have something happen within a week or so!
Make sure you have adb & fastboot: This installer is for windows, and it installed adb, fastboot, and drivers with a few key presses
Download twrp here: and place it in a folder of your choice.
force the watch to power down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
Plug your watch in your computer and wait a few seconds then type in the CMD fastboot boot recovery.img and you should have a recovery to make backups or to flash supersu if needed
links:
System.img:
https://www.dropbox.com/s/pq03vrapclz3684/system.img?dl=0
Boot.img:
https://www.dropbox.com/s/p16n60s0s7wdbhh/boot.img?dl=0
good luck!!
hamagc said:
so attempting this for you, i get to twrp and push the fastboot dd if=/dev/block/mmcblk0p28 of=/sdcard/system.img command and i am left with a <waiting for device>.
scratch that, put commands into adb instead of fastboot and it's working. will have something for you shortly!
Click to expand...
Click to collapse
I forgot one step, with twrp on the watch, type in
adb shell
and then try the dd commands
T10NAZ said:
I forgot one step, with twrp on the watch, type in
adb shell
and then try the dd commands
Click to expand...
Click to collapse
yep, exactly what i had to do lol.
many thanks to you two
T10NAZ said:
I forgot one step, with twrp on the watch, type in
adb shell
and then try the dd commands
Click to expand...
Click to collapse
Fastboot booted the recovery and it boots into twrp just fine nice work!
EDIT: just took a full system and data backup and rooted the device with supersu and all is working fine
noahvt said:
Fastboot booted the recovery and it boots into twrp just fine nice work!
EDIT: just took a full system and data backup and rooted the device with supersu and all is working fine
Click to expand...
Click to collapse
Im really excited to hear that this is all working a-ok!!
noahvt said:
Fastboot booted the recovery and it boots into twrp just fine nice work!
EDIT: just took a full system and data backup and rooted the device with supersu and all is working fine
Click to expand...
Click to collapse
I thought if you rooted you get screwed for any and all future OTA updates? I swear I've heard that for multiple Android Wear watches.
parkerlreed said:
I thought if you rooted you get screwed for any and all future OTA updates? I swear I've heard that for multiple Android Wear watches.
Click to expand...
Click to collapse
I took a full twrp backup before root so I doubt that I won't get any available updates when I restore that backup
parkerlreed said:
I thought if you rooted you get screwed for any and all future OTA updates? I swear I've heard that for multiple Android Wear watches.
Click to expand...
Click to collapse
yes, that is my understanding, but if you make backups of everything before you root, and reflash it when an ota drops, you should be alright. However if I can get everything in working order, we can keep up with ota's in flashable rom form.
we now have access to clean system and boot images too if twrp decides not to restore your backups for some reason
Sweet!
Holy crap guys, I have a source built kernel booted!
Im adding some more features and seeing how stable it runs, so far i hit 1 random reboot, but it looks like its holding strong

TWRP not installing/Stuck on Stock Recovery after a Revert to Stock

Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
undesputed said:
Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
Click to expand...
Click to collapse
Reinstallt it try this TWRP http://www.mediafire.com/download/15g5i63gke9ddgp/kiwi_twrp_3-21_recovery.img its version 3.0.2.0 (Most recent)
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
mooms said:
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
Click to expand...
Click to collapse
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Arobase40 said:
Do you mean 3.0.2.0 is newer and supports more partitions than 5-14 ???
Click to expand...
Click to collapse
Their both 3.0.2.0 the one I just posted has more features
Sent from my SM-N920T using Tapatalk
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
@clsA
frp is labeled as "UNLOCK" as oppsed to bootloader labeled as "UNLOCKED".
If it's just about removing my google account, will this be resolved the next time I do a factory reset?
Nevertheless, thank you so much for the command fastboot boot twrp.img, I realized that that was what I had used the last time.
I'm currently able to boot into TWRP this way. Awesome!
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
mooms said:
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
Click to expand...
Click to collapse
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
clsA said:
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
Click to expand...
Click to collapse
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
mooms said:
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
Click to expand...
Click to collapse
USB-OTG works flawlessly on the 5-14 version I was not able to use it with the newer one @yuweng posted in his guide
the screen shots show all the partitions it's able to work with
Arobase40 said:
I thought 3.0.2.0 was just an interim version between twrp_2-27 and twrp_5-14... ^^
Click to expand...
Click to collapse
your confusing TWRP versions with TWRP release dates
2-27 and 5-14 are release dates where as 3.0.2.0 is the version of TWRP not the date
the first version of TWRP for this device was actually 2.8.7.0 and was released on 2-16-2016
Same issue
Hey so I have the same exact issue umm did you ever resolve this problem becuSe I can't seem to crack it and it's a bit frustrating cuz by no means am I a pro but coming from using the OnePlus one the OnePlus 2 the OnePlus x and the Nexus 6 rooting them and restoring them after many failed attempts resulting in bricking my phone and even eventually unbrick them I do know a thing or two and I am stumped please help you are the only other person in this world other then my self that seems to be having this issue if you don't mind would you be so kind and email gmail me cuz I don't use or check this forum often thanks millerfamily805
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
Can it be used with other honor devices?
Got my answer... Thanks...
Sent from my PLK-L01 using XDA Labs
It depend on the device

Please check-in here if your wifi is not working after flashing/bootloops

Hoping to use this thread to help members who are having bootloops/wifi/etc. issues after flashing different kernels/system images.
If wi-fi is not working (A2017U B20):
bkores said:
Boot into TWRP, then connect your phone to your computer making sure adb is working then execute:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384
This should be your output:
/dev/block/platform/soc/624000.ufshc/by-name # dd if=/dev/zero of=/dev/block/boo
tdevice/by-name/modemst1 bs=16384
dd: writing '/dev/block/bootdevice/by-name/modemst1': No space left on device
129+0 records in
128+0 records out
2097152 bytes (2.0MB) copied, 0.001917 seconds, 1.0GB/s
/dev/block/platform/soc/624000.ufshc/by-name # dd if=/dev/zero of=/dev/block/boo
tdevice/by-name/modemst2 bs=16384
dd: writing '/dev/block/bootdevice/by-name/modemst2': No space left on device
129+0 records in
128+0 records out
2097152 bytes (2.0MB) copied, 0.001829 seconds, 1.1GB/s
/dev/block/platform/soc/624000.ufshc/by-name #
Click to expand...
Click to collapse
You also need the crossed out boot.img from Here
If you're using an SD card, reboot your phone to TWRP. Make sure external SD is mounted in TWRP. On your PC, in the folder where your downloaded and extracted the boot.img, type:
Code:
adb push boot.img /external_sd/b20b_boot.img
adb shell if=/dev/block/sde12 of=/external_sd/boot_backup.img
adb shell if=/external_sd/b20b_boot.img of=/dev/block/sde12
adb reboot
Please post the steps you took to end up with bootloops/wifi issues, what exact issues you are having (wifi/bluetooth/cell/boot logo) as well as which recovery (stock/twrp) you currently have installed.
You and me both my friend, I created a thread like a week ago to gather info about what you are saying here, but seems like they don't want to participate for a fix.
http://forum.xda-developers.com/axon-7/help/post-current-boot-issues-read-posting-t3447987
DrakenFX said:
You and me both my friend, I created a thread like a week ago to gather info about what you are saying here, but seems like they don't want to participate for a fix.
http://forum.xda-developers.com/axon-7/help/post-current-boot-issues-read-posting-t3447987
Click to expand...
Click to collapse
Well, we got two sub-forums covered now. Let's see if anyone bites.
Well I did Draken's B20_Boot TWRP Backup Xposed+Root Edition Provided by DrakenFX , which cause a no boot situation, with no access to recovery. used tenfar's root without bootloader unlock to flash boot and recovery, then Draken's software image booted but no wifi. Still haven't fixed that one yet.
@thjoca3 do you know what system.img file you used? Is it a b20_boot system.img?
jkuczera said:
@thjoca3 do you know what system.img file you used? Is it a b20_boot system.img?
Click to expand...
Click to collapse
That I'm not sure, it's whatever system is packaged with Draken's backup
@thjoca3 here are my current boot and system files. They are both b20_boot.
https://drive.google.com/folderview?id=0Bx04wovXfQGeYlpqSHhvS3Noc28
Exactly what this thread says to do...http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
I downloaded the TWRP backup from that thread, and then downloaded Tenfar's tool from his own thread. I used his thread(Tenfar's) for the acquiring of the tool, as well as downloading a2017U B20 (since B20_boot unlocked is crossed out?). I then flashed the boot and recovery .img(using Tenfar's tool), then restored to the TWRP backup in TWRP provided by rcriderz. Afterwords, my phone booted up, but did not have Wifi access. That seems to bethe only feature missing... At this point I think I'd just rather wait for the first cyanogenmod release, but this is how I got to this point. I did this in the first place because I bricked my device by using GravityBox and rebooting so the settings would kick in. Device info: US Variant, unlocked bootloader via ZTE request form, TWRP installed
jkuczera said:
@thjoca3 here are my current boot and system files. They are both b20_boot.
https://drive.google.com/folderview?id=0Bx04wovXfQGeYlpqSHhvS3Noc28
Click to expand...
Click to collapse
maybe not totally sure how to use this, but I can't seem to get anything bigger than 5gb or so to load on to my sd card, or extract anything that size onto the sd card.
jkuczera said:
@thjoca3 here are my current boot and system files. They are both b20_boot.
https://drive.google.com/folderview?id=0Bx04wovXfQGeYlpqSHhvS3Noc28
Click to expand...
Click to collapse
I know this is not my thread but having it little more info in the following form will help a lot lIssue
- Model :
- Previuos Version :
- Current Version :
- Issue / Problem :
- How happen :
That will help a lot figure things out.
DrakenFX said:
I know this is not my thread but having it little more info in the following form will help a lot lssue
- Model : A2017u
- Previous Version : locked bootloader, twrp, stock rom, was never able to get full root, and always had password needed in twrp, b20_boot
- Current Version : same other than using your system, from the B20_Boot TWRP Backup Xposed+Root Edition (still no root) had to flash boot and recovery from tenfar to get it to boot.
- Issue / Problem : no wifi, cannot copy anything over 5gb to sdcards... cant get back to stock
- How happen : flashed B20_Boot TWRP Backup Xposed+Root Edition via twrp, never lost wifi, till I flashed this.
That will help a lot figure things out.
Click to expand...
Click to collapse
zz
thjoca3 said:
maybe not totally sure how to use this, but I can't seem to get anything bigger than 5gb or so to load on to my sd card, or extract anything that size onto the sd card.
Click to expand...
Click to collapse
The problem is likely the format of your SD card. It needs to be in a format that accepts files > 4GB. I believe exFAT or ext4 should work.
http://kb.sandisk.com/app/answers/d...rger-file-to-a-usb-flash-drive-or-memory-card
Well found an sdcard reader and was able to get files to the sdcard. Restored with warofhero's system image, and my stock boot and recovery, no change with wifi. Also loaded the b20_boot with stock recovery and no wifi.
thjoca3 said:
Well found an sdcard reader and was able to get files to the sdcard. Restored with warofhero's system image, and my stock boot and recovery, no change with wifi. Also loaded the b20_boot with stock recovery and no wifi.
Click to expand...
Click to collapse
Recovery should have zero effect on the outcome of Wi-Fi functioning during normal boot. I believe the issue with wi-fi is a mismatch of boot.img and system.img.
Do you know if warofhero's system image a b20 or a b20_boot?
jkuczera said:
Recovery should have zero effect on the outcome of Wi-Fi functioning during normal boot. I believe the issue with wi-fi is a mismatch of boot.img and system.img.
Do you know if warofhero's system image a b20 or a b20_boot?
Click to expand...
Click to collapse
I tried both on his, neither worked for me. Then I did this
Download rczrider's TWRP System backup, restored in twrp with the boot from tenfar's post - a2017u B20 http://d-h.st/LqR5 (modified from @rczrider‘s backup real stock b20 boot.img) and my wifi is back.
thjoca3 said:
I tried both on his, neither worked for me. Then I did this
Download rczrider's TWRP System backup, restored in twrp with the boot from tenfar's post - a2017u B20 http://d-h.st/LqR5 (modified from @rczrider‘s backup real stock b20 boot.img) and my wifi is back.
Click to expand...
Click to collapse
That's awesome, glad you got it fix.
So you have a full operational device now? Hope this solution help others.
DrakenFX said:
That's awesome, glad you got it fix.
So you have a full operational device now? Hope this solution help others.
Click to expand...
Click to collapse
Yes, appears everything is working now, with the modified boot.
I posted this somewhere else as well but here it goes again.
The booti.img and system have to match and be from the same set. So if you use stock B20 (not _Boot) boot.img then you have to use the same /system. In this case this would be
For locked bootloader use rcrider's boot(no root) + system or tenfar's boot(root) + rcrider's /system
For unlocked bootloader you would use B20_Boot boot+system like one jkuczera posted upthread
Do not mix and match files form different region's either, these are both from US A2017U model.
When bootlooping, there are multiple reasons why this could be:
- wrong modle boot.img
- unrotted boot.img and modded recovery or system while BL is locked
- /system flashed with unsuported SU or Xposed
- boot.img flashed with unsupported kernel/ramdisk patch
- junk in cache/dalvik
- junk in /data
- /data encrypted with key which cannot be decrypted due to altered cryptochain
The way to fix it most of the time is to flash proper boot and system and wipe all user partitions. tenfar's tools can restore boot and recoveries very painlessly. TWRP can take care of the /system and wipes. The only unknown at this point is if the system image can be flashed in TWRP in a OTA consistent state on the B20 version. This should be doable by running TWRP in read only mode but i do not know if that will still let you restore system. It also has to be "System Image" backup (6GB one) from TWRP and not just the /system partition for block consistency. Hope this helps sort out the problems. I might try all this out once i am certain I'll keep the phone, it is currently in trial mode for few more weeks. The full "System Image" for B20_boot was posted here http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53 , (edit: jkuczera's is also System Image and same size). maybe rcrider can put up one for B20 Stock on his MEGA
peramikic said:
The only unknown at this point is if the system image can be flashed in TWRP in a OTA consistent state on the B20 version. This should be doable by running TWRP in read only mode but i do not know if that will still let you restore system. It also has to be "System Image" backup (6GB one) from TWRP and not just the /system partition for block consistency.
Click to expand...
Click to collapse
Thanks for clarifying @peramikic.
For the quote above, I don't understand what you mean by OTA consistent state. Do you mean a state in which OTA would still occur even after bootloader unlock?
jkuczera said:
Thanks for clarifying @peramikic.
For the quote above, I don't understand what you mean by OTA consistent state. Do you mean a state in which OTA would still occur even after bootloader unlock?
Click to expand...
Click to collapse
This probably goes more for the B20 folks, since i doubt we will see an OTA from ZTE that will work on B2-_Boot. But in essence the System Image backups are supposed to produce bit level mirror image of the /system partition so that OTA update will properly hash it. Chances are very high that when you restore regular ext4 backups, while the files are the same they will not be laid out on the partition the same way. That's why /system is strictly read-only now. Even just enabling that RW access in TWRP can alter it. For instance the image you and swehes have posted differs slightly in first 4MB of the files (his has some stuff while your is all 0s) and then again in offset 69bd000 or so where one file is missing from your's i think it's the recovery-from-boot file. It is likely TWRP removed it so it would not get flashed over after reboot with stock recovery, if you allowed RW access to system.

Possible to Root Huawei Mate SE BND-L34 on 8.0 Oreo?

Hello all. Just joined the forum. I recently got a Huawei Mate SE and without thinking about it, I let it do the OTA update and upgraded to Oreo. Now I'm trying to root, but having some issues.
I was able to unlock the bootloader and all that, but when I went to flash the recovery.img I was getting failed (remote: partition length get error).
I don't really want to do any customization like custom roms etc quite yet. The main purpose for root is wanting to remove the bloatware and other misc things.
Any help would be greatly appreciated. Thanks.
Did you end up figuring this out? I also want to get rid of all the bloatware. There's about 30 bloatware apps on there that I can't get rid of its really annoying
i got as far a you, i followed this:
https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
i get the same error trying to upload twrp, i used there twrp, i didnt use the new twrp, i cant even find our device on twrp's website
i dont want to try and brick my device,
I just unlocked the bootloader (supposedly they are going to be stopping the service next month) on my BND-L34 and currently wait for a TWRP for it.
werkmnstr2002 said:
I just unlocked the bootloader (supposedly they are going to be stopping the service next month) on my BND-L34 and currently wait for a TWRP for it.
Click to expand...
Click to collapse
If I may ask how, everytime I try any 2 of my IMEI numbers the website kicks back to me as if they are wrong.
This is what I am getting each time... after the verification codes are keyed.
"Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID."
Jimi Mack said:
If I may ask how, everytime I try any 2 of my IMEI numbers the website kicks back to me as if they are wrong.
This is what I am getting each time... after the verification codes are keyed.
"Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID."
Click to expand...
Click to collapse
Hmmmm... I got mine to go through the first time on IMEI 1.
Is the serial number correct? Did you make sure the captia was case sensitive?
werkmnstr2002 said:
Hmmmm... I got mine to go through the first time on IMEI 1.
Is the serial number correct? Did you make sure the captia was case sensitive?
Click to expand...
Click to collapse
3 days of trying and it finally went through, the verification code kept holding me up... Thanks.
I'm in the same situation re:TWRP and Android 8.0. I was able to unlock my Mate SE w/o problems.
I was able to root my 8.0 Mate SE using the twrp found here
Edit: Much better TWRP here. Working decryption for /sdcard/ partition, working backup.
With fastboot:
Code:
fastboot flash recovery_ramdisk recovery_image.img
I then rebooted to system, then:
Code:
adb reboot recovery
Taking me to twrp. Then from my external sd I flashed Magisk-v16.0.zip.
The /sdcard/ partition seems to be encrypted, this version of twrp wouldn't read files on it or backup to it.
jocala said:
I was able to root my 8.0 Mate SE using the twrp found here
Edit: Much better TWRP here. Working decryption for /sdcard/ partition, working backup.
With fastboot:
Code:
fastboot flash recovery_ramdisk recovery_image.img
I then rebooted to system, then:
Code:
adb reboot recovery
Taking me to twrp. Then from my external sd I flashed Magisk-v16.0.zip.
The /sdcard/ partition seems to be encrypted, this version of twrp wouldn't read files on it or backup to it.
Click to expand...
Click to collapse
Worked like a charm for me, much appreciated! I did the same as many others, got my new Mate SE and ran updates right out of the box. Managed to get the bootloader unlocked, but none of the TWRP install or root methods were working for me until I saw this. Many thanks, jocala!
jocala said:
I was able to root my 8.0 Mate SE using the twrp found here
Edit: Much better TWRP here. Working decryption for /sdcard/ partition, working backup.
With fastboot:
Code:
fastboot flash recovery_ramdisk recovery_image.img
I then rebooted to system, then:
Code:
adb reboot recovery
Taking me to twrp. Then from my external sd I flashed Magisk-v16.0.zip.
The /sdcard/ partition seems to be encrypted, this version of twrp wouldn't read files on it or backup to it.
Click to expand...
Click to collapse
So there is no direct way of booting into TWRP, need to Fast-boot to get to it, not a Power and volume option as it boots up as with most phone?
Jimi Mack said:
So there is no direct way of booting into TWRP, need to Fast-boot to get to it, not a Power and volume option as it boots up as with most phone?
Click to expand...
Click to collapse
There's a key combo, I think power & volume up.

Categories

Resources