Hey!
A few months ago I rooted my Mate 10 Pro (UK version on Three) using that all-in-one tool. It installed TWRP and Magisk.
I've been having a pending OTA update for months and it fails when trying to install rebooting onto TWRP.
Is there a safe way to go back to stock recovery, let the phone update and then root back? (without wiping the whole thing?) If so, could you please guide me giving some very specific steps? Many thanks!
Use hrupdater 0.4 and twrp, but read well how to do it, if you are on a xloader2 version, you can't install xloader1 version. First read well all threads you can and then if you know what are you doing, update and root again. If you only want to update and you don't mind about root, install the stock recovery and unroot and update via OTA.
Huawei is a diificult smartphone for rooting in my view, be carefull and do all by your own risk, there are many people that have bricked this smartphone due to the lack of knowledge of what they were doing (and others due to bad luck of the downgrade of xloader)
My question is how can you flash to the lastest OTA EMUI 9.0 if twrp doesn't support emui 9.0.
durc12 said:
Use hrupdater 0.4 and twrp, but read well how to do it, if you are on a xloader2 version, you can't install xloader1 version. First read well all threads you can and then if you know what are you doing, update and root again. If you only want to update and you don't mind about root, install the stock recovery and unroot and update via OTA.
Huawei is a diificult smartphone for rooting in my view, be carefull and do all by your own risk, there are many people that have bricked this smartphone due to the lack of knowledge of what they were doing (and others due to bad luck of the downgrade of xloader)
Click to expand...
Click to collapse
I just wanted to continue to expand on this. All the info I gathered is pulled from the link below.
Xloader checker
https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you are rooted can also dump your own xloader if you want to see what you're currently on.
Download Terminal Emulator from the play store and open it
Type the following
Code:
su
dd if=/dev/block/sda of=/sdcard/xloader.img
hungrymr2 said:
I just wanted to continue to expand on this. All the info I gathered is pulled from the link below.
Xloader checker
https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you are rooted can also dump your own xloader if you want to see what you're currently on.
Download Terminal Emulator from the play store and open it
Type the following
Code:
su
dd if=/dev/block/sda of=/sdcard/xloader.img
Click to expand...
Click to collapse
Thank you so much for taking the time to help me out. However, I clicked on that link and I don't understand anything!
My goal is to install the update and keep my phone rooted (a must!). So I downloaded terminal emulator and followed your instructions, now I have an "xloader.img" on my SD card and I don't know what to use to open it or do next. Please have some patience and help me out?
93starletgt said:
Thank you so much for taking the time to help me out. However, I clicked on that link and I don't understand anything!
My goal is to install the update and keep my phone rooted (a must!). So I downloaded terminal emulator and followed your instructions, now I have an "xloader.img" on my SD card and I don't know what to use to open it or do next. Please have some patience and help me out?
Click to expand...
Click to collapse
"You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02."
I'm a little confused too.
---------- Post added at 10:14 PM ---------- Previous post was at 09:35 PM ----------
hungrymr2 said:
"You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02."
I'm a little confused too.
Click to expand...
Click to collapse
I just did an OTA update with HiSuite 9.0.2.304, it was ridiculously easy. I simply clicked update. There's a chance you might lose root.
hungrymr2 said:
"You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02."
I'm a little confused too.
---------- Post added at 10:14 PM ---------- Previous post was at 09:35 PM ----------
I just did an OTA update with HiSuite 9.0.2.304, it was ridiculously easy. I simply clicked update. There's a chance you might lose root.
Click to expand...
Click to collapse
Thanks for the tip. Were you rooted before the update? If so, was it Magisk or SuperSu? Also, did you have TWRP installed?
I was not rooted when I installed the ota
hungrymr2 said:
I was not rooted when I installed the ota
Click to expand...
Click to collapse
Right, that's my main problem. If I wasn't rooted I could do the normal update through HiSuite or OTA. I'll click on those links you sent and read thoroughly. Thanks.
First restore stock recovery, flash this script in TWRP to do that https://mega.nz/#!8Swx3QaC!3JQ9imU70E9O1BxgO53Z754lGCZxCbKGgSHqvTEcXsQ
(assuming you haven't modified eRecovery as it will copy its ramdisk to recovery).
Secondly you can go to menu in System Updater and Download Latest full. That one will not fail to install. OTA can fail if you have modified ramdisk, kernel, system, vendor, product, cust (but not all are checked/patched in all OTA).
Full will not wipe data.
ante0 said:
First restore stock recovery, flash this script in TWRP to do that https://mega.nz/#!8Swx3QaC!3JQ9imU70E9O1BxgO53Z754lGCZxCbKGgSHqvTEcXsQ
(assuming you haven't modified eRecovery as it will copy its ramdisk to recovery).
Secondly you can go to menu in System Updater and Download Latest full. That one will not fail to install. OTA can fail if you have modified ramdisk, kernel, system, vendor, product, cust (but not all are checked/patched in all OTA).
Full will not wipe data.
Click to expand...
Click to collapse
I just noticed your reply! So, if I understand correctly, that Mega script is a flashable Zip through TWRP that will restore the stock recovery?
93starletgt said:
I just noticed your reply! So, if I understand correctly, that Mega script is a flashable Zip through TWRP that will restore the stock recovery?
Click to expand...
Click to collapse
Yes. It will write eRecovery_ramdisk to recovery_ramdisk (these partitions are exactly the same, only different entrypoints).
So as long as you have not modified eRecovery_ramdisk by flashing TWRP to it, it will restore your stock recovery.
ante0 said:
Yes. It will write eRecovery_ramdisk to recovery_ramdisk (these partitions are exactly the same, only different entrypoints).
So as long as you have not modified eRecovery_ramdisk by flashing TWRP to it, it will restore your stock recovery.
Click to expand...
Click to collapse
Thank you very much! I booted into TWRP, uninstalled Magisk (by flashing Magisk Uninstall Zip), flashed the stock recovery through TWRP (using the file on the link you gave me: https://mega.nz/#!8Swx3QaC!3JQ9imU70...bKGgSHqvTEcXsQ), rebooted and phone was stock again! I appreciate your help!
Related
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
I recently bought Teclast Master T10 Tablet but I can't find any way to root it.
I googled this, but the problem is that there is no TWRP for this device, so I can't flash Magisk.
Any idea or guide would be really appreciated!
Thank you all in advance!
konstantinos3 said:
I recently bought Teclast Master T10 Tablet but I can't find any way to root it.
I googled this, but the problem is that there is no TWRP for this device, so I can't flash Magisk.
Any idea or guide would be really appreciated!
Thank you all in advance!
Click to expand...
Click to collapse
here. I think you need to be registered https://translate.google.com/translate?depth=1&hl=en&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=https://4pda.ru/forum/index.php%3Fshowtopic%3D841203%26view%3Dfindpost%26p%3D66359338
Maybe someone can upload the files from that russian site to another file sharing site so we can get them. Thank you!
You can use the 4PDA android app to register and download. I was able to root my Teclast T10 just now. If you have a location where to upload the files I can do that as well.
TWRP for Teclast T10:
https://cloud2.zoolz.com/s-hd3KCVJg
Where can I find scatter file for flashing with spflashtool?
Or is there another way to flash the twrp recovery?
We cant flash without the scatterfile. Maybe it will get uploaded soon.
---------- Post added at 01:38 PM ---------- Previous post was at 01:33 PM ----------
We have a new rom here, but cant download it.... https://pan.baidu.com/s/1jIzPU8Q
T10 (E3C5)-Android7.0-V1.28-A320.rar
Scatter file
Here is is the scatter file.
Just noticed there is a new OTA available through TeclastOTA. What would be the steps to get this OTA installed?
It is IMPORTANT to flash also SuperSu in TWRP!
Otherwise BootLoop!
Phuturist said:
Just noticed there is a new OTA available through TeclastOTA. What would be the steps to get this OTA installed?
Click to expand...
Click to collapse
I have updated before flashing TWRP.
Anyone tried to update with TWRP and or Root?
Maybe it will help to flash stock Boot.img and Recovery.img from latest Version (before Update) from Needrom.
Could anyone post a guide to root Teclast T10? Is this guide correct?
How to root telcast t10
Can anyone please give me a step by step guide of how to root telcast t10 or at least remove everything to making it stock OS.
Thanks
nJoy-Android said:
I have updated before flashing TWRP.
Anyone tried to update with TWRP and or Root?
Maybe it will help to flash stock Boot.img and Recovery.img from latest Version (before Update) from Needrom.
Click to expand...
Click to collapse
First tried without doing anything extra. TeclastOTA boots into TWRP recovery and is not able to upgrade. I tried flashing the original boot and recovery afterwards but was unable to boot, it got stuck on the Teclast logo. You could probably flash the clean factory rom will become available on needrom but I don't wanna lose all my data.
Phuturist said:
Just noticed there is a new OTA available through TeclastOTA. What would be the steps to get this OTA installed?
Click to expand...
Click to collapse
konstantinos3 said:
Could anyone post a guide to root Teclast T10? Is this guide correct?
Click to expand...
Click to collapse
Of course, it's ok.
In Russia forum they told to format data in recovery.
Otherwise you don't see any data with TWRP.
Worked for me.
Don't forget to flash also SuperSu or magisk, otherwise the system won't boot...
konstantinos3 said:
Could anyone post a guide to root Teclast T10? Is this guide correct?
Click to expand...
Click to collapse
That's the one I followed and which works of you have the correct scatter and recovery.img as posted in this topic. I flashed Magisk instead of SuperSU though.
Phuturist said:
First tried without doing anything extra. TeclastOTA boots into TWRP recovery and is not able to upgrade. I tried flashing the original boot and recovery afterwards but was unable to boot, it got stuck on the Teclast logo. You could probably flash the clean factory rom will become available on needrom but I don't wanna lose all my data.
Click to expand...
Click to collapse
Maybe it goes through, if you unroot before.
Because SuperSu make changes in System Partition.
Or you can flash also factory System Partition too.
nJoy-Android said:
Of course, it's ok.
In Russia forum they told to format data in recovery.
Otherwise you don't see any data with TWRP.
Worked for me.
Don't forget to flash also SuperSu or magisk, otherwise the system won't boot...
Click to expand...
Click to collapse
The reason I ask is that I have done the OTA Update today.
Are these TWRP and scatter file compatible?
konstantinos3 said:
The reason I ask is that I have done the OTA Update today.
Are these TWRP and scatter file compatible?
Click to expand...
Click to collapse
I have used this TWRP
http://www.mediafire.com/file/5q650gcdcu568v0/Teclast_T10.zip
The scatter from previous post (extracted from Needrom V1.24)
And SuperSu or Magisk
nJoy-Android said:
I have used this TWRP
http://www.mediafire.com/file/5q650gcdcu568v0/Teclast_T10.zip
The scatter from previous post (extracted from Needrom V1.24)
And SuperSu or Magisk
Click to expand...
Click to collapse
Thank you!
Did you firstly get the OTA Update and afterwards you flashed TWRP and root?
In the Russian forum say that "Recovery compiled on the basis of the kernel firmware Android 7.0 version V1.24 / Wed Oct 11 20:24:36 CST 2017 "
After today's Update the kernel version is V.1.28_20171120
Return to Un-modded Stock:
Bootloader unlocked and TWRP and Root included
The file is 4gb compressed to 2gb. Depending on your connection it will probably take 20 to 45 minutes to download.
Be Advised
Do your research before flashing anything, I am not responsible for any damage caused to your device, due to impatience and missed steps. However, rest assured this recovery is solid and will absolutely return your X720 or X727 to stock 5.8.21s (with the bootloader already unlocked, TWRP installed and rooted)
I was asked by several people if I would be willing to share a link to my Stock X727 recovery, I created this thread to provide the 5.8.21s recovery for anyone who is experiencing dire issues or is simply wanting to restore the last official x727 recovery, as a daily driver or as a means to troubleshoot their issues by returning to the fully stock rom, stock partitions and ready to start over.
Attached is my full stock TWRP Recovery for my Le Eco Pro 3, version: 5.8.21s (X727)
It is a clean TWRP backup recovery that I did not mod in any way other than unlocking the bootloader.
The link is to my Google Drive account. https://drive.google.com/open?id=19dtLHmE5bsx5mdtEXOns4Z5drpeY79Em
The file is compressed
Ensure that you perform a full wipe before applying this recovery, and that you know what you are doing before attempting to install.
Please note that any changes that you make to your device is done at your own risk.
Please use caution and make sure that you have TWRP recovery installed.
Be in the habit of booting back to recovery before booting to system....This is a good practice for ensuring TWRP stays installed
You must unpack the downloaded 7zip file, before it will be useable.
As long as you can boot into TWRP and have root access you will have the full permissions needed to install anything , and reverse any actions that do not workout as planned.
Personally, I make a backup of my existing installation prior to making any changes. I recommend that you do the same. If you buy an OTG adapter and a USB 3.0 drive it takes 5 minutes.
The steps provided on the following link can be used to install my recovery file. https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
When clicking the link, Google will attempt to scan. Click download to see the file, and then choose download if wanted.
Flash the appropriate files below for which ever device you own. ( X727 - Not needed, I provided the files anyway just in case.)
Firmware - X720
https://mega.nz/#F!kDgFQJ6R!MDhxCFw5KjfB0CfxAWwr9w
Firmware - X727
https://drive.google.com/open?id=136-4UpUUsj3exNsTc3d5n2iQuYUxr00H
Modems
X720: https://mega.nz/#F!pZ4WGARZ
Key : !2oG3Z2LS_wP8BzcWUQjfHg
X727: https://mega.nz/#F!NJ5VHS7Z
Key : !p0iO7bDiZ4kXny03EiAlWw
Build Prop Fix Device ID Tool ( Credit to @Ascertion )
https://mega.nz/#F!oAZ3yC4b
Key: !MDwbHXNTRdrpgMvQ42yviw
EFS:
Warning : Use this only if you have unrepairable IMEI Issues! Otherwise its not needed, and you could forever lose your original IMEI info.
https://drive.google.com/open?id=10n2VjwBYHmrq_PllcWmTaGUtMIeYynZ7
[B ]Just for Fun[/B] - Boot Screens and Boot Animations -
https://mega.nz/#F!JB51zbwR
Key: !sG_wXTPqyKpugg5QIZFo9w
These splash-screens and animations came from various sources. If you created them contact me so i can give you credit.
The Red Splash came from the Couco modified EUI : version 5.9.028s VR4
Other Helpful Hints and Tips More to Come!
Unlock Bootloader and Flash Roms, Gapps and Magisk https://forum.xda-developers.com/showpost.php?p=75009966&postcount=692 ( If using original Stock
Viper Settings : https://forum.xda-developers.com/showpost.php?p=75449097
Installing Viper and Dolby: https://forum.xda-developers.com/showpost.php?p=76362493&postcount=19
Edit
October 8, 2018:
I uploaded the Leeco Full Stock Rom 5.8.26s to my MegaDrive.
If you are selling your phone and want it to have stock without TWRP and without root , just flash this Rom and your stock radio driver "firmware" for your device
Link for EUI 21S : https://mega.nz/#!FRhh1ArL
Key: V5ua3oj91kFtgvLYBhl1X6Oq3bsScyDFruN3UptkWN0
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Soul0Reaper said:
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Click to expand...
Click to collapse
Thats Awesome! I am glad that it helped you.
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
dunas2331 said:
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
Click to expand...
Click to collapse
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
tsongming said:
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
Click to expand...
Click to collapse
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Hi tsongming, you know if can work on a x720?
thanks
Toni Moon said:
Hi tsongming, you know if can work on a x720?
thanks
Click to expand...
Click to collapse
Yes x720 and x727 are practically identical phones.
Sent from my LEX720 using XDA Labs
Scruffdog1978 said:
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Click to expand...
Click to collapse
I don't have time at the moment to provide lengthy instructions. With respect, I am providing a working, clean unlocked recovery file and pointing the way to instructions already that exist all throughout the LeEco forums.
But here's a quick answer
First use TWRP to reset your phone with a clean wipe, like you would for any ROM. Set developer options to the standard settings.
Next, your storage is encrypted. So it needs to be formatted. Use TWRP format the storage only. Then reboot to recovery.
****Important****
Don't ever format the storage without ensuring that you have a TWRP recovery. Always check the boxes to check if TWRP is installed before swiping. If you don't have a recovery you have a soft brick.
For you information, TWRP recovery is installed on it's on it very own partition. Formatting the storage does not affect the TWRP partition. Nonetheless, if you see the check box option, make sure they are checked.
I would suggest that you install the all in one tool : https://www.google.com/amp/s/forum....pment/tool-tool-one-mauronofrio-t3580611/amp/
This tool helps a lot and makes this stuff easier if are new to flashing custom Roms.. The all in one tool will update the Google driver and ADB installation on your computer.
After you format your drive you will have to flash the recovery from the PC. The links provided show all of the steps, or you can use the all for one tool. When your storage is encrypted you have no choice but to format.
If you use the all in one tool , see their page for instructions.
Read the instructions, then read them again. when learning something new it's a good idea to take notes.
Do not deviate from those steps or you could brick your phone.
There have been many people that have messaged me by PM who successfully returned to stock using my recovery, so it will work as long as you are careful and follow the instructions verbatim and you will be fine. Plus, It's a great idea to create your own working recovery before you begin.
Reminder, you are restoring to stock under you own discretion, I am not responsible if you miss a key step, have a power outage, use faulty cables or brick your device.
One final suggestion, when you install the recovery make sure your phone is fully charged. Unplug all unneeded external peripherals from your desktop computer.
Temporarily, disable antivirus, insert USB cable into the back of your desktop PC. Those outlets provide more power.
Please look past any typos, I typed this on little keys.
One last suggestion
Read this
http://www.androidtipsz.com/top-5-things-to-do-before-installing-a-custom-rom-on-your-android-device
Sent from my LEX720 using XDA Labs
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
meh4life321 said:
Will I keep twrp after restore? Thanks
Click to expand...
Click to collapse
Also, could I just restore the system?
Could I just flash this in TWRP and keep twrp as my recovery?
meh4life321 said:
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
Also, could I just restore the system?
Click to expand...
Click to collapse
No it will not keep twrp. follow the instructions in the link I provided above, there was no reason to duplicate the instructions on my post.
The difference is that my backup will restore your phone to Eui 5.8.21s with bootloader unlocked. You will need to reflash Twrp and root the phone with Magisk if you want to keep Twrp recovery ( that is what I would do) You will not be able to get OTA updates. But that doesn't matter because there probably not be any more OTA updates for the x727
Thank you, sir! This is great work. I was able to restore back to stock.
On the strange side of thing, my TWRP was saved. Previously, I was running AICP, but having multiple sound issues with it.
Here are the steps I followed to restore:
1) Move the file to OTG flash drive
2) Restore through TWRP via Restore
For my 727, it just reboot on logo, and doesn't go past it.
rob_z11 said:
For my 727, it just reboot on logo, and doesn't go past it.
Click to expand...
Click to collapse
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
tsongming said:
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
Click to expand...
Click to collapse
Will try again. How long is while? ?
rob_z11 said:
Will try again. How long is while?
Click to expand...
Click to collapse
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
tsongming said:
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
Click to expand...
Click to collapse
It actually worked for second time without any issues. Just can't get the root, but will follow your instructions.
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
blanktape said:
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
Click to expand...
Click to collapse
This recovery is stock EUI 5.8.21s. The exception is that the bootloader is unlocked, and it has TWRP Recovery instead of EUI Recovery. I do not remember which version of Magisk I Installed. I would advise that you flash the newest version of Magisk and you will not have any safety net issues.
If you are wanting a complete return to stock, you should instead reflash the stock Full Rom, which will reinstall EUI recovery and lockdown the bootloader.
I'm currently sitting at TWRP and was going to restore my backup... it's gone. I was going to reboot to OS... TWRP warns me I have no OS installed.
In my tired state trying to solve an unrelated problem I must have killed my backup a few hours ago without noticing and then decided to use TWRP to format my phone so I could restore my backup... that I previously killed.
What can I do from this state? My brain is fried from hours of trying various troubleshooting threads across the internet and I'm just at a loss how to install the OS again without bricking and I don't want to make a mistake.
Appreciate the help. I do have US998820e_02_0910.kdz downloaded on my PC which is the latest KDZ I have downloaded.
teknomedic said:
I'm currently sitting at TWRP and was going to restore my backup... it's gone. I was going to reboot to OS... TWRP warns me I have no OS installed.
In my tired state trying to solve an unrelated problem I must have killed my backup a few hours ago without noticing and then decided to use TWRP to format my phone so I could restore my backup... that I previously killed.
What can I do from this state? My brain is fried from hours of trying various troubleshooting threads across the internet and I'm just at a loss how to install the OS again without bricking and I don't want to make a mistake.
Appreciate the help. I do have US998820e_02_0910.kdz downloaded on my PC which is the latest KDZ I have downloaded.
Click to expand...
Click to collapse
If you did format stuff and yur backup then nothing can help
Mrxyzl said:
If you did format stuff and yur backup then nothing can help
Click to expand...
Click to collapse
I feel that's not correct... could I not use LGUP or copy over a basic backup provided by someone here just to get me back to point where I can get back to stock?
If I plug the phone into the PC I can access the storage.... could I not copy something over and then use the running TWRP to install it?
teknomedic said:
I feel that's not correct... could I not use LGUP or copy over a basic backup provided by someone here just to get me back to point where I can get back to stock?
If I plug the phone into the PC I can access the storage.... could I not copy something over and then use the running TWRP to install it?
Click to expand...
Click to collapse
Oh i mean that your backup is already gone completely no way to get back your backup. And ofcourse you can flash a new rom anew
Lol, that's what I thought... But I'm also very tired.
Can I just copy over my KDZ and then install via TWRP? I've always just used backups in the past.
This is a secondary phone that was wiped before anyways so I haven't lost anything important.... The backup was only there to speed things up.
If you are in TWRP, connect to PC and drag over your firmware TWRP flashable zip and Magisk. And whatever else you need, maybe encryption disabler, root check disabler. With Oreo TWRP flashable zip (since you have US998), all you need is the zip file and Magisk.
In TWRP file explorer, find location where you just copied them. Then install them.
US998 20h TWRP flashable zip
https://androidfilehost.com/?fid=1395089523397941723
I've attached Magisk 18 to this post. You can update after you reboot to system. (TWRP 18.X is friendlier with Oreo TWRP-FLASHABLE zips.)
Sent via open market LG US998 V30/V30+
teknomedic said:
Lol, that's what I thought... But I'm also very tired.
Can I just copy over my KDZ and then install via TWRP? I've always just used backups in the past.
This is a secondary phone that was wiped before anyways so I haven't lost anything important.... The backup was only there to speed things up.
Click to expand...
Click to collapse
If your kdz is twrp flashable zip you can copy it over to your phone and flash via recovery.
If the kdz is not twrp flashable you will lose twrp/ root (if available) and will revert to stock recovery.
pvramk said:
If your kdz is twrp flashable zip you can copy it over to your phone and flash via recovery.
If the kdz is not twrp flashable you will lose twrp/ root (if available) and will revert to stock recovery.
Click to expand...
Click to collapse
Yes, TWRP flashable zip is available for his US998 phone.
See post above.
---------- Post added at 08:54 AM ---------- Previous post was at 08:45 AM ----------
teknomedic said:
Lol, that's what I thought... But I'm also very tired.
Can I just copy over my KDZ and then install via TWRP? I've always just used backups in the past.
This is a secondary phone that was wiped before anyways so I haven't lost anything important.... The backup was only there to speed things up.
Click to expand...
Click to collapse
No, don't copy over KDZ. Copy over the TWRP flashable zip version of the KDZ.
See my post above. I give download link to latest Oreo US998 TWRP flashable zip. Also Magisk. I attached that to the post. Flash both, then reboot.
Hey, at least you now have a VERY clean install! This is the technique some people do on purpose to start fresh.
Thank you ChazzMatt... why did I suspect you'd be my hero once again, ha.
ChazzMatt said:
If you are in TWRP, connect to PC and drag over your firmware TWRP flashable zip and Magisk. And whatever else you need, maybe encryption disabler, root check disabler. With Oreo TWRP flashable zip (since you have US998), all you need is the zip file and Magisk.
In TWRP file explorer, find location where you just copied them. Then install them.
US998 20h TWRP flashable zip
https://androidfilehost.com/?fid=1395089523397941723
I've attached Magisk 18 to this post. You can update after you reboot to system.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
LOL... I wasn't opposed to starting fresh... that was my ultimate goal, but I've not been in this exact situation before as I've always kept my backups. Being tired and in a hurry was my downfall this time. I just didn't want to go any further without proper advice as I was worried about bricking and just wanted to double make sure I wouldn't do that on my next attempt to "fix" it alone.
ChazzMatt said:
Yes, TWRP flashable zip is available for his US998 phone.
See post above.
---------- Post added at 08:54 AM ---------- Previous post was at 08:45 AM ----------
No, don't copy over KDZ. Copy over the TWRP flashable zip version of the KDZ.
See my post above. I give download link to latest Oreo US998 TWRP flashable zip. Also Magisk. I attached that to the post. Flash both, then reboot.
Hey, at least you now have a VERY clean install! This is the technique some people do on purpose to start fresh.
Click to expand...
Click to collapse
There are basically several options here.
If you can still boot into fastboot or even TWRP there's nothing to fear. It's really hard to completely brick a phone anyways.
So as suggested either use a flashable kdz (you can even adb sideload it to avoid the copying) or just flash (or sideload) any other ROM. Good luck
teknomedic said:
I feel that's not correct... could I not use LGUP or copy over a basic backup provided by someone here just to get me back to point where I can get back to stock?
Click to expand...
Click to collapse
Connect the phone to the computer, and push a stock TWRP zip to the device and flash it. If you have an ad card port on the PC, then push it to the SD card and put it in the phone.
Sent from my LG-H932 using XDA Labs
NM, saw my man @ChazzMatt using his forum superhero Powers again.
Download any zip of your choice and reboot. Then let Google backup restore your apps and settings.
Running into a new issue... after flashing 20H TWRP and Magisk I rebooted the phone. Android OS did it's first install and I made it to the setup screen... then while I was typing in my wifi password the phone simply shut down (played the shutting down LG logo animation). I turned the phone back on and same results... after loading to the Android setup screen around 1 to 15 seconds later the phone shuts down again. Phone has never done this before.
Any thoughts?
I'm not sure if it matters, but this was originally a US Verizon V30 that I unlocked and rooted following the guides here which "converted" to a US998.
ChazzMatt said:
If you are in TWRP, connect to PC and drag over your firmware TWRP flashable zip and Magisk. And whatever else you need, maybe encryption disabler, root check disabler. With Oreo TWRP flashable zip (since you have US998), all you need is the zip file and Magisk.
In TWRP file explorer, find location where you just copied them. Then install them.
US998 20h TWRP flashable zip
https://androidfilehost.com/?fid=1395089523397941723
I've attached Magisk 18 to this post. You can update after you reboot to system. (TWRP 18.X is friendlier with Oreo TWRP-FLASHABLE zips.)
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
teknomedic said:
Running into a new issue... after flashing 20H TWRP and Magisk I rebooted the phone. Android OS did it's first install and I made it to the setup screen... then while I was typing in my wifi password the phone simply shut down (played the shutting down LG logo animation). I turned the phone back on and same results... after loading to the Android setup screen around 1 to 15 seconds later the phone shuts down again. Phone has never done this before.
Any thoughts?
I'm not sure if it matters, but this was originally a US Verizon V30 that I unlocked and rooted following the guides here which "converted" to a US998.
Click to expand...
Click to collapse
Okay I think I know what the problem is... you may have to flash 20, F, g, H all back-to-back. Then reflash Magisk
Or flash the full 20h KDZ in LGUP , reinstall TWRP and reflash the three root files. Your choice.
The problem is there were so many changes between 20e and 20H with the TWRP flashable zips that you have to flash them all back to back to get the full firmware.
You can stack them in TWRP and flash them all at the same time followed by magisk.
lol... okay... I'll get to downloading, lol. Any recommended custom ROM suggestions? lol
ChazzMatt said:
Okay I think I know what the problem is... you may have to flash 20, F, g, H all back-to-back. Then reflash Magisk
Or flash the full 20h KDZ in LGUP , reinstall TWRP and reflash the three root files. Your choice.
The problem is there were so many changes between 20e and 20H with the TWRP flashable zips that you have to flash them all back to back to get the full firmware.
You can stack them in TWRP and flash them all at the same time followed by magisk.
Click to expand...
Click to collapse
teknomedic said:
lol... okay... I'll get to downloading, lol. Any recommended custom ROM suggestions? lol
Click to expand...
Click to collapse
Sorry, no, I'm still running rooted stock firmware. But others who use custom ROMs may have suggestions for your gaming issue, mentioned in your PM.
Check this out below and see if it helps you any.
https://forum.xda-developers.com/lg-v30/how-to/guide-enable-gps-change-rubber-banding-t3889811
Sent via open market LG US998 V30/V30+
I downloaded and installed ROM 20E from this thread under older zips.... https://forum.xda-developers.com/lg-v30/development/rom-fw-us99820e-twrp-zip-t3868415
still doing the same behavior. First boot Android does setup, then if I let it sit a few seconds it shuts down and reboots, gets to Android and then shuts down again... over and over.
ChazzMatt said:
Sorry, no, I'm still running rooted stock firmware. But others who use custom ROMs may have suggestions for your gaming issue, mentioned in your PM.
Check this out below and see if it helps you any.
https://forum.xda-developers.com/lg-v30/how-to/guide-enable-gps-change-rubber-banding-t3889811
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Okay, think it's working. Having looked through the ROM maker's thread Magisk v18 is... needed? I previously installed a newer version (v19.2) which can cause this boot loop issue.... I also installed the ROM without any Magisk which still caused the boot loop which is why I wasn't thinking Magisk was the issue.... but after trying 20H with v18 Magisk... no more boot loop. Go figure.
teknomedic said:
I downloaded and installed ROM 20E from this thread under older zips.... https://forum.xda-developers.com/lg-v30/development/rom-fw-us99820e-twrp-zip-t3868415
still doing the same behavior. First boot Android does setup, then if I let it sit a few seconds it shuts down and reboots, gets to Android and then shuts down again... over and over.
Click to expand...
Click to collapse
teknomedic said:
Okay, think it's working. Having looked through the ROM maker's thread Magisk v18 is... needed? I previously installed a newer version (v19.2) which can cause this boot loop issue.... I also installed the ROM without any Magisk which still caused the boot loop which is why I wasn't thinking Magisk was the issue.... but after trying 20H with v18 Magisk... no more boot loop. Go figure.
Click to expand...
Click to collapse
Well, glad you got it working.
But the Magisk thing is why I had specifically attached Magisk 18 to my first post in this thread and said to use it... I even explained why.
I assumed you were using it.
Long story short, I rooted my N200 T-Mobile variant to A12 DE2118_11_C.15 (Full OTA) not a long time ago with no issues. However to be able to update to DE2118_11_C.16 (Incremental update, w/July 2022 Patch) I had to uninstall Magisk first, then update it to c.16. Now my phone is updated to c.16 but I am very unsure how to root it again to avoid bootloop;
1. Can I use c.15 stock boot image since c.16 was an incremental update? or I need c.16 version?
2. If c.16 boot image is already extracted please share.
3. If none above, how and where I can find the OTA file to extract payload.bin and then boot.img?
I would really appreciate if somebody help me with this, thank you.
HTCore said:
Long story short, I rooted my N200 T-Mobile variant to A12 DE2118_11_C.15 (Full OTA) not a long time ago with no issues. However to be able to update to DE2118_11_C.16 (Incremental update, w/July 2022 Patch) I had to uninstall Magisk first, then update it to c.16. Now my phone is updated to c.16 but I am very unsure how to root it again to avoid bootloop;
1. Can I use c.15 stock boot image since c.16 was an incremental update? or I need c.16 version?
2. If c.16 boot image is already extracted please share.
3. If none above, how and where I can find the OTA file to extract payload.bin and then boot.img?
I would really appreciate if somebody help me with this, thank you.
Click to expand...
Click to collapse
The steps below is what I do since Android 12 update:
**Automatic system updates should be unchecked on Developer options.**
Prerequisites: Rooted with Magisk (v25.2 recommended) / Have stock boot image available.
Preparation:
A. Restore active slot boot img with stock boot on adb shell with root
ex) dd if=/sdcard/boot_a.img of=/dev/block/bootdevice/by-name/boot_a
OR
B. Uninstall Magisk with Restore Image option if available
--------------------------------------------------------------------------------------------------------------
**If you do A first and Direct Install with Magisk, then B option will be available.
1. Update OTA and DO NOT PRESS Restart Button.
2. Backup the new stock boot image. If your current boot is b, then new stock boot is a
ex) dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/boot_a.img
3. Patch the newly extracted stock boot with Magisk -> Reboot -> Reboot to fastboot
4. Flash the newly magisk patched image
ex) fastboot flash boot_a new_magisk_boot.img
5. Reboot
OR you can try to install Magisk with in-active slot option at Step #3, then restart with OTA, not with Magisk; however, I've been told that it sometimes makes an issue such as bootloop. Up to you.
follow A1.1 to get your boot.img.
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
After your phone is rooted again, go in developer options and disable automatic system updates so it won't restart without your consent in future OTAs. when it asks for you to restart, go into the magisk app and press install and then "install to inactive slot". Then go back to the system update screen and press restart.
That's it. If you followed the steps correctly, your device should be updated and you should still have root!
Thank you both of you for your help and thorough explanation.
I suppose since I already restarted my device after update I have no chance with @lentm's method.
Now I'm going to follow what @justauserthatusesaphone posted and see what happens.
I will post the result here if somebody else is interested too.
HTCore said:
Thank you both of you for your help and thorough explanation.
I suppose since I already restarted my device after update I have no chance with @lentm's method.
Now I'm going to follow what @justauserthatusesaphone posted and see what happens.
I will post the result here if somebody else is interested too.
Click to expand...
Click to collapse
All you need is the stock boot img file, and here's the latest one:
11_C.16_DE18CB_tmobile_stock.7z is available for download
Click to access the 11_C.16_DE18CB_tmobile_stock.7z (35.3 MB) download with TransferNow
www.transfernow.net
Thank you for posting boot.img @lentm!
I was middle of what @justauserthatusesaphone posted when you attached the boot.img! So thank you very much being mindful of others!
However, just to learn more and be prepared for future updates I tried the other method and it worked perfectly! My device is now rooted with latest update thanks both of you guys!
Next I'm gonna use your method for another N200 which hasn't been updated yet and experience that one as well.
HTCore said:
Thank you for posting boot.img @lentm!
I was middle of what @justauserthatusesaphone posted when you attached the boot.img! So thank you very much being mindful of others!
However, just to learn more and be prepared for future updates I tried the other method and it worked perfectly! My device is now rooted with latest update thanks both of you guys!
Next I'm gonna use your method for another N200 which hasn't been updated yet and experience that one as well.
Click to expand...
Click to collapse
glad to hear you got it!
lentm's link didn't work for me so for anyone else who needs the stock image here is a non-expiring link for stock boot image for Tmobile DE2118 11_C.16:
boot_11_C.16_DE2118_tmobile_stock.img | by towardsdawn for Nord N200 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Could someone please tell me if it's possible to root this device running the latest July 5th update mentioned above without a pc ?
And if so where to find or how to do it ?!
I've been searching everywhere and have only come across a bunch of "one clock root options" that haven't worked .
Brisingrmischief said:
Could someone please tell me if it's possible to root this device running the latest July 5th update mentioned above without a pc ?
And if so where to find or how to do it ?!
I've been searching everywhere and have only come across a bunch of "one clock root options" that haven't worked .
Click to expand...
Click to collapse
One click root APKs don't have access to fastboot to flash a rooted boot.img, which is what you need to do for permanent root for newer Android devices. Also I wouldn't trust those anyway, most are not open source and might contain malware/ads/etc.
You can have a temporary root if your bootloader is unlocked by using a DSU, however if your bootloader has not been unlocked (which you need a PC to do) do NOT attempt to do this. Multiple people have reported bricking their devices attempting to do this so you have been warned.
All files on the DSU will be deleted when you discard the DSU since it is a different system image from the original. If you really know what you're doing you might be able to flash a Magisk rooted boot.img to the original system image from the DSU, I don't know how to do this. You can play around with making the DSU persist through reboots using this guide, I don't know if that works with updates or if all files will have to be discarded if you want to update. I recommend using DSU sideloader with a GSI from phhusson, when it says to run the shell script over ADB you can use a terminal app like Termux instead.
towardsdawn said:
One click root APKs don't have access to fastboot to flash a rooted boot.img, which is what you need to do for permanent root for newer Android devices. Also I wouldn't trust those anyway, most are not open source and might contain malware/ads/etc.
You can have a temporary root if your bootloader is unlocked by using a DSU, however if your bootloader has not been unlocked (which you need a PC to do) do NOT attempt to do this. Multiple people have reported bricking their devices attempting to do this so you have been warned.
All files on the DSU will be deleted when you discard the DSU since it is a different system image from the original. If you really know what you're doing you might be able to flash a Magisk rooted boot.img to the original system image from the DSU, I don't know how to do this. You can play around with making the DSU persist through reboots using this guide, I don't know if that works with updates or if all files will have to be discarded if you want to update. I recommend using DSU sideloader with a GSI from phhusson, when it says to run the shell script over ADB you can use a terminal app like Termux instead.
Click to expand...
Click to collapse
Thank you for your help !
I assume that since my bootloader is not unlocked and I don't have access to a pc I'm pretty much out of luck on rooting this device until I can get access to one .
Guess I'll have find a way to access one .
Much appreciated though !