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.
Related
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
It's a Huawei Y6II - CAM-L21.
My phone still works perfectly. I'm just concerned that if I ever do a factory reset the recovery image will overwrite the "main" image and nothing will work again. Is that a real concern?
I was trying to root it and followed the instructions in this thread. I just got confused because that image is for model KIW-L21 and mine is a CAM-L21. Needless to say, it wouldn't boot. Holding power and vol down took me back to the bootloader and after restarting it works.
I know how stupid that was. Once you're done laughing, can you tell me if that can be undone? I haven't found any default factory image for download.
Did you resolve? Did you root your phone?
Thanks
No, it's still in that state. As I was saying, it works fine as long as I don't try the recovery image. At this point I don't care much about rooting it, I'm just concerned about bricking it.
In the next days I'll extract recovery.img from my phone (I'll buy phone in the next days) and i'll try to send you.
You'll can flash with fastboot flash recovery recovery.img
May be...
In any case if you want try a new recovery you must use fastboot boot xxxx.img
I don't understand if you can power on your phone, or if your phone goes into loop.
Can you use adb?
Did you unlock the bootloader?
Thank you, that will be appreciated. Yes, I can power on my phone and it boots normally into the non-rooted system. I can use adb as well. The bootloader is unlocked and I get a warning screen at boot.
Just curious, how are you planning to read the original recovery image? As far as I know, fastboot doesn't have such a feature.
Adb shell
cat /proc/mtd
dd if=/dev/block/mtdblock0 of=/mnt/external_sd/dd.out/misc.img
But you cannot do that without rooting (permission denied), and once you've rooted it won't be the original recovery image anymore...
I'll try with fastboot boot xxxx.img
Did you unlock with the standard method, like other huawei?
Yes, like any other Huawei. Had some trouble because the links in the thread above were broken, and the Huawei login page redirects to the main site instead of providing the code. I don't remember exactly what I did in the end but I think I found a workaround to a site's bug to get the code when browsing the original site in Chinese autotranslated by Chrome. Sorry but I can't remember the details.
Good luck with that.
yoou may follow this tutorial to root or install TWRP on y6 ii
http://forum.xda-developers.com/android/general/rooting-huawei-y6-ii-cam-l21-t3501162
Solved recovery huawei y6ii
jameelmemon said:
yoou may follow this tutorial to root or install TWRP on y6 ii
http://forum.xda-developers.com/android/general/rooting-huawei-y6-ii-cam-l21-t3501162
Click to expand...
Click to collapse
Finally here is the recovery of huawei y6 ii cam l-21 it works perfectly
Try it http://dl.twrp.me/cherry/twrp-3.0.2-0-cherry.img.html
Thank you!
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 ???
Hi everybody
I've got a problem...
Downloaded latest OTA update from "xiaomi.eu", agreed to install, the phone then rebooted in to fastboot mode and does nothing else.
Rebooted the phone with adb command "fastboot continue" and this went well...it rebooted the system.
Now every time i restart the phone it reboots in to fastboot mode and i have to "fastboot continue" again.
I am also not able to enter recovery because the phone always enters fastboot mode.
Reinstalled recovery (Twrp-3.4.2B_toco_by.alex.msk1407.img) via ADB succesfully, but when i "fastboot reboot recovery" it reboots back into fastboot.
I'm also not able to boot into EDL mode.
Any solution?
Thanks
"MI NOTE LITE 8GB/128GB" running "MIUI by xiaomi.eu 12.1.1 | Stable 12.1.1.0(RFNMIXM)
Hi, I 'm in the same case, same model, same version.
I investigated and I can provide more details to help the community to look where to get a match to lightning our lanterns.
I downloaded the last OTA from built-in updater then the device was trapped in fastboot loop.
Unable to reboot/boot with adb/fastboot commands, but able to flash, I tried with différents recoveries,whose the last TWRP (testing version) let us discover the "super partition" (need fastbootd implantation to see it) This is the new OTA update partitioning.
We have to set up the proper flags via adb to perform successfully the update , or cancel the update process to retrieve original partitioning (non-updating state).
The commons way to restore recovery/fastboot might don't work, because system/vendor partitions are hidden inside "super partition" so might result of unknown/doesn't exist partition.
I am still seeking (Android dev super partitioning) and I'll be back when I'll discovered more...
EDIT : Doublon ? Another thread is open
https://forum.xda-developers.com/t/...astboot-after-updating-to-android-11.4223957/
EDIT: many users had a similar issue.
Will try with any another GSI rom, downloading...
opposatto said:
Hi, I 'm in the same case, same model, same version, I investigated and I can provide more details to help the community which lantern to pickup.
I downloaded the last OTA from built-in updater then the device was trapped in fastboot loop.
Unable to reboot/boot with adb/fastboot commands, but able to flash, I tried with différents recoveries,whose the last TWRP (testing version) let us discover the "super partition" (need fastbootd implantation to see it) This is the new OTA update partitioning.
We have to set up the proper flags via adb to perform successfully the update , or cancel the update process to retrieve original partitioning (non-updating state).
The commons way to restore recovery/fastboot might don't work, because system/vendor partitions are hidden inside "super partition" so might result of unknown/doesn't exist partition.
I am still seeking (Android dev super partitioning) and I'll be back when I'll discovered more...
EDIT : Doublon ? Another thread is open
https://forum.xda-developers.com/t/...astboot-after-updating-to-android-11.4223957/
Click to expand...
Click to collapse
Thank you. I'll be for updates
salsaecoentros said:
Thank you. I'll be for updates
Click to expand...
Click to collapse
Looking around https://source.android.com/devices/tech/ota/dynamic_partitions/implement
opposatto said:
Looking around https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Click to expand...
Click to collapse
EDIT : so here is the idea, not tried yet:
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Alex msk's twrp is not compatible with android 11. Use orangefox or pitchblack recovery.
Btw i would recommend not upgrading to android 11 at the moment. It has a lot of bugs.
ApexPrime said:
Alex msk's twrp is not compatible with android 11. Use orangefox or pitchblack recovery.
Click to expand...
Click to collapse
So that's the problem....didn't think about that.
Thanks...i Will try one of them and them get back to you.
Thanks
salsaecoentros said:
So that's the problem....didn't think about that.
Thanks...i Will try one of them and them get back to you.
Thanks
Click to expand...
Click to collapse
Hi...
Sorry for the late Replay.
So i did like you said and installed new twrp and...what do you know...ir worked like a charme. No more issues.
Thank you do much.
I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
sako21 said:
I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
Click to expand...
Click to collapse
Flash latest A13 update u will get stock recovery
pankspoo said:
Flash latest A13 update u will get stock recovery
Click to expand...
Click to collapse
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
sako21 said:
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
Click to expand...
Click to collapse
Just try keep unrooted boot. Img backup of your current rom.
Then go ahead though it's got currpted (one person faced that at insta but he used that commnads when he has twrp it must work with stock recovery) but after restoring boot imgae all was fine.
But try at u r own risk later don't tag [email protected] pankspoo - guide
Thanks. Will try that out.
And yes, wont tag you!
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
Wait u want to relock bootloader?
You need a otg adapter. Put Stock boot.img and the last ota update file to the usb storage.
flash stock boot.img via FKM
go to developer settings and lock oem
uninstall magisk with restore all (not image)
start phone in bootloader
fastboot flash relock
fastboot reboot recovery
select update from storage
use otg adapter with ota file
install
restart
done
For any assistance contact @sakarya1980
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
did you get the relock bootloader?
If you're still searching for the stock recovery, I've attached the .img file (unzip it first)