Related
hey every one . i got a t989 today in good condition for decent price as a secondary phone . the phone is running on stock 4.1.2 .
i want to run newer custom rom ( probably c12.1 / cm13 ) . problem is it is my first samsung device to install a custom rom on and i am a bit confused so here what i know so correct me if i am wrong .
1- install odin then flash twrp 2.8.7
2- reboot to recovery so the stock rom won't go back to stock
3- from recovery install the latest version twrp 3.0.2
4- do a full wipe then install rom and gapps .
----
i downloaded twrp 2.8.7 from the twrp website . the .tar file
for the rom and twrp 3 i will download this one
http://forum.xda-developers.com/gal...unofficial-cyanogenmod-13-0-hercules-t3246059
so am i missing something ? is every thing ready to go ?
Go baby go
---------- Post added at 07:55 PM ---------- Previous post was at 07:52 PM ----------
before you fully wipe you must root your phone and then flash a new rom
there is no need to root your phone since you have flash twrp from odin make and make sure you flash the twrp of the owner
I just got one too and looking forward to get CM13, I've read something about a .pit file and "Virtual Partition"... what about it? do I need to flash something more? thanks in advance for your time, and sorry for the noobish question.
EDIT: nevermind, seems like I need to get my eyes checked. Here it is: http://forum.xda-developers.com/galaxy-s2-tmobile/help/qa-cyanogenmod-13-0-t3319195
Due to the disrespect of certain members here I will no longer share the tutorials.
how long does it take to move past the N/A screen. also where in this do you flash the stock boot.img if you get error 1s? please be more specific.
I should've seen this first
So... I found this thread AFTER the fact. Phone's a day old, rooted, and softbricked. I have TWRP and fastboot but kernel's gone.
You have everything there except the what if...
How'd you un-softbricked your device?
quotrice said:
how long does it take to move past the N/A screen. also where in this do you flash the stock boot.img if you get error 1s? please be more specific.
Click to expand...
Click to collapse
Hi, sorry for the late reply. Been busy tinkering with the phone.
It can take up to 30 seconds (granted, I counted out loud on reboot just now) to move past the N/A screen and go to the chick saying "hello Moto" and then the Metro PCS flash screen.
If you get the error1s the original boot.img may have either been corrupted, deleted, or the phone is being a **** and has somehow altered it where its modified, and therefore cannot start up right. With me, that happened after flashing different TWRPs and then repetitively flashing the files for root. That is why I said this:
5. Installing any of the .zip files may mess with the boot.img. I personally think unlocking the bootloader did that because I followed directions on here to a T and had problems eith Error 1 off the bat. So, if you start seeing Error 1 messages when you attempt to flash the necessary files for root in TWRP, you will have to do this step below I did.
5. Go into the Stock Rom file and extract the boot.img file. Put it in the Minimal ADB file folder (the same as you did for the recovery.img file).
-In Minimal ADB type "fastboot erase boot "
-In Minimal ADB type "fastboot flash boot boot.img" That should restore your original boot image to stock and correct any error 1 problems. And the best part is you don't have to erase and re-flash all the original stock rom files to get it back in order, potentially messing up the bootloader unlock!
Click to expand...
Click to collapse
You do not have to flash the rom unless you want to, and trust it is a pain as you have to extract all the contents of the ROM and flash them via TWRP one by one. I've updated in my original post on how to go about that. So, if the boot.img is your prob, all you have to do is extract the boot.img file from the rom and follow the instructions above. However, if you've deleted or altered more than the boot.img, you will have to flash the rom, but at this step you shouldn't of. I too had the error1 thing, and after tinkering with it for 9 hours, just flashing that boot.img on a humbug solved the problem alone. Just open it in WinRar/WinZip and pull it out, and follow the instructions above.
HmonGrL123 said:
So... I found this thread AFTER the fact. Phone's a day old, rooted, and softbricked. I have TWRP and fastboot but kernel's gone.
You have everything there except the what if...
How'd you un-softbricked your device?
Click to expand...
Click to collapse
My softbrick was the corruption of the boot.img. I was unable to get the phone to load past the N/A after that. Flashing the boot.img from the stock solved it.
If your kernel is truly gone, which please mention what guide you used to try and get root, you will have to flash stock via TWRP. And let me just say, it isn't as easy as flashing it as a ROM. You will have to extract the entire Stock Rom files to Minimal ADB Fastboot folder and flash the files one by one (refer to my updates in my original post on how to restore the stock rom).
---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------
Articul8Madness said:
My softbrick was the corruption of the boot.img. I was unable to get the phone to load past the N/A after that. Flashing the boot.img from the stock solved it.
If your kernel is truly gone, which please mention what guide you used to try and get root, you will have to flash stock via TWRP. And let me just say, it isn't as easy as flashing it as a ROM. You will have to extract the entire Stock Rom files to Minimal ADB Fastboot folder and flash the files one by one (refer to my updates in my original post on how to restore the stock rom).
Click to expand...
Click to collapse
I finally got it going. I had to flash system.sparsechunk. it failed a few times afterwards too but i figured it was su that was causing it. I finally got it back to stock. Flashed magisk, and now I'm running resurrection. Thank you
Should I post exactly what i did in case someone stumbles upon my same problem?
HmonGrL123 said:
---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------
I finally got it going. I had to flash system.sparsechunk. it failed a few times afterwards too but i figured it was su that was causing it. I finally got it back to stock. Flashed magisk, and now I'm running resurrection. Thank you
Should I post exactly what i did in case someone stumbles upon my same problem?
Click to expand...
Click to collapse
Couldn't hurt
HmonGrL123 said:
---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------
I finally got it going. I had to flash system.sparsechunk. it failed a few times afterwards too but i figured it was su that was causing it. I finally got it back to stock. Flashed magisk, and now I'm running resurrection. Thank you
Should I post exactly what i did in case someone stumbles upon my same problem?
Click to expand...
Click to collapse
PLEASE DO!!!! As you see we all are having different problems getting the E4 on the way to root. I encourage you to make a footnote of it in this thread, and I'll direct people to it on the original post. If we can't get this down, flashing a rom is going to be a *****. :good:
Articul8Madness said:
PLEASE DO!!!! As you see we all are having different problems getting the E4 on the way to root. I encourage you to make a footnote of it in this thread, and I'll direct people to it on the original post. If we can't get this down, flashing a rom is going to be a *****. :good:
Click to expand...
Click to collapse
So don't do this yet?
mookey1986 said:
So don't do this yet?
Click to expand...
Click to collapse
@HmonGrL123 had a specific issue when flashing, as a different guide was followed first. This guide is to simplify the process.
I just wanted to add:
At step
13. Hit Install and install Magisk.zip. Afterwards, go back to main menu.
Click to expand...
Click to collapse
I ran into the error 1 problem.
After that, I powered down the phone. Then I went into fastboot and flashed the boot.img
Then I used fastboot to get back into TWRP.
Then I went back to step 13.
And Rebooted.
And I finally got root. All working.
wktra said:
I just wanted to add:
At step
I ran into the error 1 problem.
After that, I powered down the phone. Then I went into fastboot and flashed the boot.img
Then I used fastboot to get back into TWRP.
Then I went back to step 13.
And Rebooted.
And I finally got root. All working.
Click to expand...
Click to collapse
Glad you got it working. Maybe no matter what step is taken is going to initially corrupt the boot.img, so reflashing that is probably going to be essential. I'll test it out on the significant other's phone and see if that is the case.
At the step after the wipe, no matter what I do and trying 2 different versions of twrp, I cannot get the data partition to mount. I can keep clicking it over and over but the box will not check.
Been searching and googling and I cannot figure it out.
nm after sever tries it mounted
Just wanted to thank the op for this awesome guide! Rooted, did a full back up and a nandroid back up, now I'm running resurrection remix to great effect.
Sent from my XT1765 using Tapatalk
Just so you know, the reason why you (and other people in the thread) keep getting error1 when installing Magisk is because of Step 12:
"12. Hit Install and install Superuser.zip. Afterwards, go back to main menu."
Installing the superuser.zip modifies the boot.img .... then the very next step, step 13, is when Magisk will complain about the boot.img being modified. You don't need the superuser.zip at all it's redundant, flashing magisk roots the phone as well. Skip step 12, I'm fully rooted without it and you will literally never get Magisk to say the boot.img is unmodified as long as you keep modifiying the boot.img right before it.
Rooted and bootloader unlock....roming now....wish me luck
So I have officially unlocked my motoE4 on metropcs and have installed superuser. Trying to custom rom and kill the stupid metro pcs bootloader. I deoxed it and removed bloat....but can we tweak? we'll c soon working on it all nite. ill keep you posted
InFamousD147 said:
So I have officially unlocked my motoE4 on metropcs and have installed superuser. Trying to custom rom and kill the stupid metro pcs bootloader. I deoxed it and removed bloat....but can we tweak? we'll c soon working on it all nite. ill keep you posted
Click to expand...
Click to collapse
Magisk works better for root (plus you get magisk modules) and can pass safetynet.
So how long does it take for it to flash each item in twrp? I flashed the first thing (no-verity), and it's just hanging out after it shows "Done Installing!" "Updating partition details...". How long is this suppose to take?
nekomancey said:
Just wanted to thank the op for this awesome guide! Rooted, did a full back up and a nandroid back up, now I'm running resurrection remix to great effect.
Sent from my XT1765 using Tapatalk
Click to expand...
Click to collapse
You're welcome! I went through a time getting this thing to root, so I just wrote what worked on my variant. How's the resurrection remix. Looking for a good rom.
Steel Froggy said:
Just so you know, the reason why you (and other people in the thread) keep getting error1 when installing Magisk is because of Step 12:
"12. Hit Install and install Superuser.zip. Afterwards, go back to main menu."
Installing the superuser.zip modifies the boot.img .... then the very next step, step 13, is when Magisk will complain about the boot.img being modified. You don't need the superuser.zip at all it's redundant, flashing magisk roots the phone as well. Skip step 12, I'm fully rooted without it and you will literally never get Magisk to say the boot.img is unmodified as long as you keep modifiying the boot.img right before it.
Click to expand...
Click to collapse
I am only going by what worked for me with the metropcs variant. I had tried other tutorials, but there was not a definitive one that dealt with the problems of the MetroPCS trying to get root. So I can't say it's redundant when it wasn't just as simple as flashing magisk on this version of the phone for me. And granted, I went by pieces of people's tutorials, trial, and error.
Every rom threads is being filled with people asking what to do with error 7. Same questions and same answers over and over.
The solution is simple and straightforward as below:
- Make sure you have latest TWRP.
- Make sure you have the right firmware.
All above can be downloaded if you look at 1st page of each rom threads. If not, go to Lineage 15.1 thread and get it from there.
Even with correct TWRP and firmware, you may still get error 7. In that case,
- Unmount (uncheck) System in TWRP.
I guarantee that those three will fix error 7 issues, especially the last part.
how to unmount twrp..?wrongly i deleted all data,caxhe system , and twrp cant install nothing, if i install linageos, it show error 7, if i instal an eui ZIP, it installs fastes (like 4 sec) and after boot to leeco logo...HELP.
error 7
Hello, I am new and french.
sorry for english do it by translator
I also have error 7 with los15.1 and I was in los14.1 before
I also tried the 3 methods but it did not work
I found on the internet a solution when you are sure to have the right rom
lineageosdownloads fix error 7
I can not link, I'm sorry again
so I looked for what was wrong with "META-INF »com» google »android» updater-script"
and that's the line that was not in the old rom
assert(leeco.verify_modem("2017-01-06 01:40:06") == "1");
I cleared this line and recompile and it works but I can not have the update
normal
who can tell me how it fits this line and how to fix thank you
---------- Post added at 08:04 PM ---------- Previous post was at 08:01 PM ----------
I deleted this line and it works but can not receive updates
who can tell me what this line is
and how to settle it thanks
---------- Post added at 08:14 PM ---------- Previous post was at 08:04 PM ----------
I bought it on grossoshop, 1year ago, there was 18s grossoshop rom I think and I went straight on los14.1
I'll have to put it back, put the 20s 26s
is it the bootlader that has changed? I am not an expert lol
it's not that I hope to help those who have x720
philourm2.0 said:
Hello, I am new and french.
sorry for english do it by translator
I also have error 7 with los15.1 and I was in los14.1 before
I also tried the 3 methods but it did not work
I found on the internet a solution when you are sure to have the right rom
lineageosdownloads fix error 7
I can not link, I'm sorry again
so I looked for what was wrong with "META-INF »com» google »android» updater-script"
and that's the line that was not in the old rom
assert(leeco.verify_modem("2017-01-06 01:40:06") == "1");
I cleared this line and recompile and it works but I can not have the update
normal
who can tell me how it fits this line and how to fix thank you
---------- Post added at 08:04 PM ---------- Previous post was at 08:01 PM ----------
I deleted this line and it works but can not receive updates
who can tell me what this line is
and how to settle it thanks
---------- Post added at 08:14 PM ---------- Previous post was at 08:04 PM ----------
I bought it on grossoshop, 1year ago, there was 18s grossoshop rom I think and I went straight on los14.1
I'll have to put it back, put the 20s 26s
is it the bootlader that has changed? I am not an expert lol
it's not that I hope to help those who have x720
Click to expand...
Click to collapse
Update your twrp.
Sent from my LEX727 using xda premium
mchlbenner said:
Update your twrp.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
I have the newest Trwp (3.2.1-0 by codeworkx), installed 20s firmware from linage thread unmounted /system and still get error 7 (e1001). When i try to install a nougat or marshmallow based rom it either says system cant be unmounted (eventhough i did before) or says it was succesful, but i'm not able to boot. When trying to restore a backup i also cannot boot. Just the Leeco splash screen shows till it goes into recovery.
ok but I have twrp 3.2.1.0
give a trwp 3.1 or 3.0 and try los14.1
philourm2.0 said:
give a trwp 3.1 or 3.0 and try los14.1
Click to expand...
Click to collapse
When flashing LOS14.1 in twrp 3.0.2 it gets stuck at somewhere like 90% (Patching system image unconditionally)
Are you guys getting this error?
If you do update your firmware.
Go get it from codeworkx
Sent from my LEX727 using xda premium
Thanks for your help
I installed twrp-3.2.1-0-20180407-codeworkx-zl1 and still this error 7
it's the line
assert (leeco.verify_modem ("2017-01-06 01:40:06") == "1");
which makes me wrong if I delete it in meta-inf ok
in the forum lost15.1 official on xda, they say firmwaire 20s minimun in red
I have never been in official 20s it would not be that?
or find udapte.zip 20s x720
I can try to put back original, put back 3.2.1 trwp and flash for test
thanks
Storm, you're stuck in any case if I understood
try on the site grossoshop leeco the pro 3
there is an automatic tutorial to put in 18s grossoshop
nothing to lose
then you try los 14.1 ok
Fixed it
I actually got this: "E1001: Failed to update system image." followed by Error 7.
So, i don't know how but it just fixed itself. My ADB Drivers suddenly didn't work correctly and after reinstalling clockworkmods Universal ADB Driver it worked out of nowhere. It could also have been a false USB Port scince i also plugged my cable in somewhere else. Now I can flash anything without problems
Hope this helps...
problem solved my turn
for those who have an error 7 with oreo which is a problem identification
you need the firmwaire 20s minimum if you start the custom rom with 18s or 19s
and the solution and in the tutorial aicp 13
so it's not necessarily the trwp that's always the problem
but thanks for the help
I was having the same error 7.
I just reflashed to stock 20s and the problem was fixed
Ferdinantstr said:
how to unmount twrp..?wrongly i deleted all data,caxhe system , and twrp cant install nothing, if i install linageos, it show error 7, if i instal an eui ZIP, it installs fastes (like 4 sec) and after boot to leeco logo...HELP.
Click to expand...
Click to collapse
Same Here!!
millkyway4 said:
Same Here!![/QUOTE
Is this tread still alive?
Click to expand...
Click to collapse
I read through this post and couldn't get past the error 7 issue. I finally got it solved by updating TWRP to the latest version and then I could flash lineage15 via adb sideload. Thanks for another great, informative, thread from the people of XDA developers.
I have a USA variant, just got the Oreo / EMUI 8.0 update. Everything is stock.
I got my bootloader unlock code from Honor support (via the Google forms the USA Support tweeted out).
All guides for unlocking the bootloader and rooting are for Nugat (7.0).
I am wondering a few things.
1) Has anyone unlocked/rooted Oreo? What steps did you take? What TWRP version are you using (a link is preferable, if you have one)? Did you use the multi-tool, or directly with adb?
2) What root solution did you use? I prefer SU over magisk (for the ability to use xposed), but I heard SU isn't working, only magisk? What version did you use?
3) What backup system do you use when your phone will wipe everything for unlocking the bootloader? Is the Huawei stock "Backup" app that it comes with any good? Any better ones to use?
Basically there's no walkthrough for rooting with the current setup. It'd be awesome if someone wrote one that was basically:
- Backup using W method (backup app, or alternative).
- Unlock bootloader using X method (adb/multi-tool/whatever).
- Root using Y method (TWRP version, SU or magisk, and version numbers)
- Do Z activity (anything else to flash after? xposed? etc.?)
Any thoughts appreciated.
arebelspy said:
I have a USA variant, just got the Oreo / EMUI 8.0 update. Everything is stock.
I got my bootloader unlock code from Honor support (via the Google forms the USA Support tweeted out).
All guides for unlocking the bootloader and rooting are for Nugat (7.0).
I am wondering a few things.
1) Has anyone unlocked/rooted Oreo? What steps did you take? What TWRP version are you using (a link is preferable, if you have one)? Did you use the multi-tool, or directly with adb?
2) What root solution did you use? I prefer SU over magisk (for the ability to use xposed), but I heard SU isn't working, only magisk? What version did you use?
3) What backup system do you use when your phone will wipe everything for unlocking the bootloader? Is the Huawei stock "Backup" app that it comes with any good? Any better ones to use?
Basically there's no walkthrough for rooting with the current setup. It'd be awesome if someone wrote one that was basically:
- Backup using W method (backup app, or alternative).
- Unlock bootloader using X method (adb/multi-tool/whatever).
- Root using Y method (TWRP version, SU or magisk, and version numbers)
- Do Z activity (anything else to flash after? xposed? etc.?)
Any thoughts appreciated.
Click to expand...
Click to collapse
Already covered in this thread.
https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
mrmazak said:
Already covered in this thread.
https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
Click to expand...
Click to collapse
That didn't even cover a fraction of the questions I posted. It *maybe* gave the relevant TWRP build, though even that is in question, as one of the most recent posts was "I couldn't get any of the TWRP versions listed in this thread to work fully. " and suggesting something else.
I'm curious if anyone has actually rooted stock 8.0 and what process they used.
arebelspy said:
That didn't even cover a fraction of the questions I posted. It *maybe* gave the relevant TWRP build, though even that is in question, as one of the most recent posts was "I couldn't get any of the TWRP versions listed in this thread to work fully. " and suggesting something else.
I'm curious if anyone has actually rooted stock 8.0 and what process they used.
Click to expand...
Click to collapse
It also said backup partitions when in twrp image mount, and flash magisk 16 for root.
I'm about to try this same exact thing the twrp Oreo thread is a little confusing.
K easy part done bootloader unlocked
Update: installed twrp. Did a few backups. Flashed magisk. Rooted now restoring apps in titanium backup. Adaway finally and going to clean up system. ? Safety net passes. Just a little confused on how to restore if I end up in a boot loop. I'm trying to backup still in twrp. But can't backup data and I don't see boot.img to backup. So yeah I'm scared.
arebelspy said:
That didn't even cover a fraction of the questions I posted. It *maybe* gave the relevant TWRP build, though even that is in question, as one of the most recent posts was "I couldn't get any of the TWRP versions listed in this thread to work fully. " and suggesting something else.
I'm curious if anyone has actually rooted stock 8.0 and what process they used.
Click to expand...
Click to collapse
I had posted that. Use this TWRP. Flash Magisk 16 through TWRP. Enjoy root.
---------- Post added at 11:45 PM ---------- Previous post was at 11:41 PM ----------
allrockedout said:
K easy part done bootloader unlocked
Update: installed twrp. Did a few backups. Flashed magisk. Rooted now restoring apps in titanium backup. Adaway finally and going to clean up system. Safety net passes. Just a little confused on how to restore if I end up in a boot loop. I'm trying to backup still in twrp. But can't backup data and I don't see boot.img to backup. So yeah I'm scared.
Click to expand...
Click to collapse
Flashing kernel.img and system.img from the Oreo update.zip should completely fix a bootloop/brick. I had messed around and bootlooped one of mine, and had to extract those .img files to flash them through fastboot to restore my phone. It will erase the system though so a backup of data through Titanium Backup should be safe.
ryang872 said:
I had posted that. Use this TWRP. Flash Magisk 16 through TWRP. Enjoy root.
---------- Post added at 11:45 PM ---------- Previous post was at 11:41 PM ----------
Flashing kernel.img and system.img from the Oreo update.zip should completely fix a bootloop/brick. I had messed around and bootlooped one of mine, and had to extract those .img files to flash them through fastboot to restore my phone. It will erase the system though so a backup of data through Titanium Backup should be safe.
Click to expand...
Click to collapse
Where can I get system.img and kernel.img can you share it. I'm barely able to reboot keeps rebooting and booting into safe mode. Takes me like 10 minutes to boot to system. can barely get into twrp
allrockedout said:
Where can I get system.img and kernel.img can you share it. I'm barely able to reboot keeps rebooting and booting into safe mode. Takes me like 10 minutes to boot to system. can barely get into twrp
Click to expand...
Click to collapse
Gonna upload them now. I'll edit this post when they're finished. Did you have root before updating to Oreo?
ryang872 said:
Gonna upload them now. I'll edit this post when they're finished. Did you have root before updating to Oreo?
Click to expand...
Click to collapse
No I waited for Oreo before I rooted. I just rebooted again and booted back to system fine. I made a bunch of backups in twrp. But there useless if you don't have booted.img system and data.
allrockedout said:
No I waited for Oreo before I rooted. I just rebooted again and booted back to system fine. I made a bunch of backups in twrp. But there useless if you don't have booted.img system and data.
Click to expand...
Click to collapse
there is no "boot.img" on oreo.
the traditional boot.img has been split into 2 partitions. kernel.img and ramdisk.img.
mrmazak said:
there is no "boot.img" on oreo.
the traditional boot.img has been split into 2 partitions. kernel.img and ramdisk.img.
Click to expand...
Click to collapse
So we need kernel.img ramdisk.img which is boot. Than we need system and data. How do you flash the kernel and ramdisk when in twrp? I'm guessing ramdisk we select recovery ramdisk...and kernel? I got system and data backed up
Flashing kernel.img through "fastboot flash boot kernel.img" absolutely solved my bootloop/brick problem. I am completely new to Huawei phones so if I'm wrong please don't let me spread misinformation.
---------- Post added at 12:43 AM ---------- Previous post was at 12:41 AM ----------
allrockedout said:
So we need kernel.img ramdisk.img which is boot. Than we need system and data. How do you flash the kernel and ramdisk when in twrp? I'm guessing ramdisk we select recovery ramdisk...and kernel? I got system and data backed up
Click to expand...
Click to collapse
You'd need to flash kernel as boot through fastboot(fastboot flash boot kernel.img). TWRP would be ramdisk (fastboot flash recovery_ramdisk *****.img). System and Data backed up through TWRP can be restored through TWRP. At least those worked for me in restoring a bootloop/brick.
---------- Post added at 01:00 AM ---------- Previous post was at 12:43 AM ----------
allrockedout said:
Where can I get system.img and kernel.img can you share it. I'm barely able to reboot keeps rebooting and booting into safe mode. Takes me like 10 minutes to boot to system. can barely get into twrp
Click to expand...
Click to collapse
system.img kernel.img
EDIT: This is for L34 update.zip. I'm going out on a limb by assuming that all honor 7x/mate se versions are the same minus the modem_***.img files. USE AT YOUR OWN RISK.
allrockedout said:
So we need kernel.img ramdisk.img which is boot. Than we need system and data. How do you flash the kernel and ramdisk when in twrp? I'm guessing ramdisk we select recovery ramdisk...and kernel? I got system and data backed up
Click to expand...
Click to collapse
Each partition is it's own. Kernel is kernel, ramdisk is ramdisk, etc.
Recovery_ramdisk is recovery_ramdisk
I preferred to make each partition backup as images. Using adb shell and DD commands.
I know it is not in this thread. But in the "(nougat) twrp complete" thread.
This is linked in I believe post two. Where it describes making backup useing DD.
But the partitions are different in oroe, so need to use different codes as in that thread.
I just posted almost same thing yesterday with the links.
Use this guide to make back up. But substitute the partition layout from the following link
Oreo layout
I might be putting together a script that does the backup form you . And put it into a zip file that you run as a twrp install.
I like that idea. Now I said it out load, yeah I like it
I made first draft of my dd back up install.
It makes new directory on external card "twrp_backup" then makes dd copies of all 56 partitions. It takes a while to complete. , but gives you all the partitions, as they are. I added echo lines to the script to give you stautus of the backup, but the output is not shown on trwp install window. And it appears to be doing all the lines of the script at same time, not one at a time. So even if the echo commands printed output , it would be all at once.
well hold off on that statement of "it works" 30 minutes plus and still running.
No errors in current log, Adb shell ls (backup directory) shows all partitions. But mtp only showing 42 out of 56.
It appears to be hanging somewhere.
Will update when I find it.
update..
It worked. All 56 partitions backed up. took over an hour. then I realized I had internal storage full of junk. Userdate backup took 23GB.
as long as your data is not so full, should be better time.
maybe someone else can help edit it to be better script.
completed recovery log attached. Truncated to remove screen timeout (sleep and wake messages)
mrmazak said:
I made first draft of my dd back up install.
It makes new directory on external card "twrp_backup" then makes dd copies of all 56 partitions. It takes a while to complete. , but gives you all the partitions, as they are. I added echo lines to the script to give you stautus of the backup, but the output is not shown on trwp install window. And it appears to be doing all the lines of the script at same time, not one at a time. So even if the echo commands printed output , it would be all at once.
well hold off on that statement of "it works" 30 minutes plus and still running.
No errors in current log, Adb shell ls (backup directory) shows all partitions. But mtp only showing 42 out of 56.
It appears to be hanging somewhere.
Will update when I find it.
maybe someone else can help edit it to be better script.
Click to expand...
Click to collapse
To return to stock recovery and factory reset what do I restore? Do I need to wipe anything?
allrockedout said:
To return to stock recovery and factory reset what do I restore? Do I need to wipe anything?
Click to expand...
Click to collapse
none of those would be stock recovery. Because in order to have made that backup, you would have been on twrp. So the backup would be also twrp.
need to get the stock oreo recovery from extracting the recovery_ramdisk from update.app. update.app is in the update.zip of your oreo update. The main zip , not the "public" or "hw" one.
once you have the image. select install menu in twrp. change to install image. And install to "recovery ramdisk" also can be done with fastboot.
mrmazak said:
none of those would be stock recovery. Because in order to have made that backup, you would have been on twrp. So the backup would be also twrp.
need to get the stock oreo recovery from extracting the recovery_ramdisk from update.app. update.app is in the update.zip of your oreo update. The main zip , not the "public" or "hw" one.
once you have the image. select install menu in twrp. change to install image. And install to "recovery ramdisk" also can be done with fastboot.
Click to expand...
Click to collapse
K im downloading the update.zip now from firmware finder. I want to do another clean install magisk is force closing now. I'm using the p10 lite twrp.
---------- Post added at 10:13 AM ---------- Previous post was at 09:39 AM ----------
mrmazak said:
none of those would be stock recovery. Because in order to have made that backup, you would have been on twrp. So the backup would be also twrp.
need to get the stock oreo recovery from extracting the recovery_ramdisk from update.app. update.app is in the update.zip of your oreo update. The main zip , not the "public" or "hw" one.
once you have the image. select install menu in twrp. change to install image. And install to "recovery ramdisk" also can be done with fastboot.
Click to expand...
Click to collapse
im having trouble extracting update.app i cant open it on my pc.
---------- Post added at 10:24 AM ---------- Previous post was at 10:13 AM ----------
allrockedout said:
K im downloading the update.zip now from firmware finder. I want to do another clean install magisk is force closing now. I'm using the p10 lite twrp.
---------- Post added at 10:13 AM ---------- Previous post was at 09:39 AM ----------
im having trouble extracting update.app i cant open it on my pc.
Click to expand...
Click to collapse
im downloading huawei update extractor
K I'm going to extract this
Here is stock recovery ramdisk for Honor 7x USA Oreo. https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=drivesdk
I haven't tested it yet. Going to flash in twrp. Hopefully boot back into stock recovery and factory reset.
I also extracted kernel.img.
I successfully flashed kernel and ramdisk recovery. I rebooted back into stock recovery. Going to try factory reset now.
?
Wouldnt boot up.
Flashed kernel.img through twrp didnt work had to flash through adb and it seems to be booting now.
HELL YEAH!! ok booted up to system now.
I have a Moto Z Play that had the stock current version of Oreo installed, and I was able to unlock my bootloader and I went through the steps in the guide to install TWRP and Magisk, followed by f2fsfix. After installing TWRP I could still boot to system, but then after installing Magisk and f2fsfix, I'm unable to boot to system I just get the screen saying my device isn't trusted and will boot in 5 seconds, but just stays on that screen.
I've tried using the magisk uninstaller and reinstalling, and it hasn't worked. I've tried uninstalling and reinstalling magisk by flashing and booting to TWRP, neither has worked. Also I've been using TWRP 3.2.3.0 Addison, and I've tried both Magisk 18.1 and 16.0.
Anyone have any idea as to what may be going on, or how I can rememdy the situation? Let me know if there's additional information you need about the device.
Same thing happened to me. Tried many times but after flashing magisk it couldn't boot to system just get stuck on bootlogo. Luckily i had a twrp backup, i just restored and I'm on nougat now with working imei. Only thing that makes me worry is now i have the stock nougat rom but oreo bootloader.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
I would suggest you to roll back to nougat
khanpatriot said:
Same thing happened to me. Tried many times but after flashing magisk it couldn't boot to system just get stuck on bootlogo. Luckily i had a twrp backup, i just restored and I'm on nougat now with working imei. Only thing that makes me worry is now i have the stock nougat rom but oreo bootloader.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
I would suggest you to roll back to nougat
Click to expand...
Click to collapse
So if I didn't have a TWRP recovery file would there be a version of the stock rom that I could download and flash to get things working?
So you have an efs backup? As it's something most important otherwise you will loose your imei(not permanently) but it won't show by *#06#. Or in settings.
---------- Post added at 05:10 AM ---------- Previous post was at 05:04 AM ----------
If u want to go back to stock nougat here's the owsum rom i tested and running currently.... by supahcookie.
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
But keep in mind first make your efs backup with chinese twrp. Sorry i forgot where from i downloaded but search a little bit hope u will find. Regards
khanpatriot said:
Same thing happened to me. Tried many times but after flashing magisk it couldn't boot to system just get stuck on bootlogo. Luckily i had a twrp backup, i just restored and I'm on nougat now with working imei. Only thing that makes me worry is now i have the stock nougat rom but oreo bootloader.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
I would suggest you to roll back to nougat
Click to expand...
Click to collapse
Just had a chance to do that and it looks like I'm back in buisiness. Thanks!
beebop483 said:
I have a Moto Z Play that had the stock current version of Oreo installed, ... [...]
Anyone have any idea as to what may be going on, or how I can rememdy the situation? Let me know if there's additional information you need about the device.
Click to expand...
Click to collapse
For Oreo Moto Z Play current and probably last version there exists a pre patched boot.img to flash at the end of the twrp thread. Please have a look there if you still need it, but be aware that it is only for the exact os version.
Alberto97 said:
I patched it for you, just flash this bootimage (only for OPNS27.76-12-22-9 build, it might break ...
Click to expand...
Click to collapse
Also note that I did not test it by now, just saved it for usage when I need root.
beebop483 said:
I have a Moto Z Play that had the stock current version of Oreo installed, and I was able to unlock my bootloader and I went through the steps in the guide to install TWRP and Magisk, followed by f2fsfix. After installing TWRP I could still boot to system, but then after installing Magisk and f2fsfix, I'm unable to boot to system I just get the screen saying my device isn't trusted and will boot in 5 seconds, but just stays on that screen.
I've tried using the magisk uninstaller and reinstalling, and it hasn't worked. I've tried uninstalling and reinstalling magisk by flashing and booting to TWRP, neither has worked. Also I've been using TWRP 3.2.3.0 Addison, and I've tried both Magisk 18.1 and 16.0.
Anyone have any idea as to what may be going on, or how I can rememdy the situation? Let me know if there's additional information you need about the device.
Click to expand...
Click to collapse
uninstall magisk with uninsatllmagisk.zip from twrp