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.
Related
KIW-L24 B151 Stock Roms
Here's All my Stock roms from the new update B151
Choose the one you like. I can't test these on L21/L22 so flash at your own risk
UPDATE: Do Not flash the Deodexed Roms on L21 / Or L22 unless you remove the cust.tar.gz from the Rom first. They include the USA Local.prop and your phone may not boot
KIW-L24-B151-Stock (Boot.img - System - System/Priv-App Only)
KIW-L24-B151-Stock.Rooted.DeOdexed (Boot.img - System - System/Priv-App - /cust - /data)
KIW-L24-B151-Stock.Rooted.DeOdexed.Xposed (Boot.img - /Data - System - System/Priv-App - /cust) With xposed / Busybox / Quick Boot / SDfix / ES File Explorer
B151.noCust.no.swap.deodexed.Xposed.NOVA.R5.zip (Boot.img - System - System/Priv-App ) (No /data and No /cust) With xposed / Busybox / Quick Boot / SDfix / ES File Explorer / Nova - May require a factory reset and a couple of boots to get it going, if it hangs on the 2nd Honor screen simply reboot and it should load.
Clean flash is recommended - Dirty Flash may be OK
KIW-L24-B151-Stock.Rooted.DeOdexed.Xposed will take about 10 - 15 minutes for first boot
Note: I have noticed The phone is charging faster after the update with my Quick Charge 2.0 18W Wall Charger.
Also, Messages can be answered from the popup notification
clsA said:
KIW-L24 B151 Stock Roms
Here's All the Stock roms from the new update B151
Choose the one you like. I can't test these on L21/L22 so flash at your own risk
KIW-L24-B151-Stock (Boot.img - System - System/Priv-App Only)
KIW-L24-B151-Stock.Rooted.DeOdexed (Boot.img - System - System/Priv-App - /cust - /data)
KIW-L24-B151-Stock.Rooted.DeOdexed.Xposed (Boot.img - /Data - System - System/Priv-App - /cust) With xposed / Busybox / Quick Boot / SDfix / ES File Explorer
Clean flash is recommended - Dirty Flash may be OK
KIW-L24-B151-Stock.Rooted.DeOdexed.Xposed will take about 10 - 15 minutes for first boot
Note: I have noticed The phone is charging faster after the update with my Quick Charge 2.0 18W Wall Charger.
Also, Messages can be answered from the popup notification
Click to expand...
Click to collapse
Downloading now...will report back later. Ty
---------- Post added at 11:56 AM ---------- Previous post was at 11:32 AM ----------
Cleaned install the DeOdexed without Xposed, the phone won't boot - stuck at hornor for the brave screen.
Twrp error: mounting system: failed to mount/dev/block/boot devive/by-name/system at/systemevice or resource busy
Please help
Caltinpla said:
Downloading now...will report back later. Ty
---------- Post added at 11:56 AM ---------- Previous post was at 11:32 AM ----------
Cleaned install the DeOdexed without Xposed, the phone won't boot - stuck at hornor for the brave screen.
Twrp error: mounting system: failed to mount/dev/block/boot devive/by-name/system at/systemevice or resource busy
Please help
Click to expand...
Click to collapse
reboot recovery and flash it again ... I tested all 3 files myself last night and this morning their all fine
Remember the DeOdexed roms boot slow the first time
clsA said:
reboot recovery and flash it again ... I tested all 3 files myself last night and this morning their all fine
Remember the DeOdexed roms boot slow the first time
Click to expand...
Click to collapse
It might be a bad download over the phone...I'll try it at home later. Ty
---------- Post added at 01:14 PM ---------- Previous post was at 01:10 PM ----------
Caltinpla said:
It might be a bad download over the phone...I'll try it at home later. Ty
Click to expand...
Click to collapse
I reflashed the stock B151 you posted yesterday and the phone booted fine
Will it be possible to have this version made it work for the l21?
ldmauro said:
Will it be possible to have this version made it work for the l21?
Click to expand...
Click to collapse
Download first one if you want stock
And other versions, you have to extract the ROM and remove cust then flash it
@clsA
Nice work again, i think adding cust in separate zip for l24 users only is better ?
And can you please check changing current with Ampere ?
Thanks
clsA said:
reboot recovery and flash it again ... I tested all 3 files myself last night and this morning their all fine
Remember the DeOdexed roms boot slow the first time
Click to expand...
Click to collapse
I finally got it booted after the second flash and it took a while to finish booting. The new B151 update seems run much smoother imo, will report later.
Thank you
AL_IRAQI said:
Download first one if you want stock
And other versions, you have to extract the ROM and remove cust then flash it
@clsA
Nice work again, i think adding cust in separate zip for l24 users only is better ?
And can you please check changing current with Ampere ?
Thanks
Click to expand...
Click to collapse
At 78% it was charging at 1020mA
Not sure what that means its the first time I used Ampere
Sent from my KIW-L24 using Tapatalk
Caltinpla said:
I finally got it booted after the second flash and it took a while to finish booting. The new B151 update seems run much smoother imo, will report later.
Thank you
Click to expand...
Click to collapse
I noticed the exact same thing.
To the dev, thank you for all your hard work! These ROMs have been excellent.
although it might not work, tried it on L-22, got the same error reported earlier in the thread even after 3 tries
I am installing this - (KIW-L24-B151-Stock.Rooted.DeOdexed.Xposed)
Twrp error: mounting system: failed to mount/dev/block/boot devive/by-name/system at/system: Device or resource busy
- OK, I missed the reboot recovery part, I did that and the install went just fine....will report back on boot up and whether it works at all for L-22
Boooo hooo!! the phone goes into a boot loop and on the second reboot after honor logo, gets automatically into TWRP. But TWRP is stuck, no touch response and no actions can be done. I can't restore my back up either now ouch!
So folks, don't try this yet on non-L24 devices! I hope someone can help me get out of this mess of a phone now, lol, experimented and well punished!
nandakalyan said:
although it might not work, tried it on L-22, got the same error reported earlier in the thread even after 3 tries
I am installing this - (KIW-L24-B151-Stock.Rooted.DeOdexed.Xposed)
Twrp error: mounting system: failed to mount/dev/block/boot devive/by-name/system at/system: Device or resource busy
- OK, I missed the reboot recovery part, I did that and the install went just fine....will report back on boot up and whether it works at all for L-22
Boooo hooo!! the phone goes into a boot loop and on the second reboot after honor logo, gets automatically into TWRP. But TWRP is stuck, no touch response and no actions can be done. I can't restore my back up either now ouch!
So folks, don't try this yet on non-L24 devices! I hope someone can help me get out of this mess of a phone now, lol, experimented and well punished!
Click to expand...
Click to collapse
Sorry .. you'll have to reflash the stock L22 Update.App, My roms for the L24 include the /cust partition that you have to remove to use them on L21 / L22
As I don't have those phones I can't dump the /cust partition to help you
Flashing this should return you phone to working order >> http://forum.xda-developers.com/honor-5x/development/rom-r1-modaco-custom-rom-t3336458
clsA said:
Sorry .. you'll have to reflash the stock L22 Update.App, My roms for the L24 include the /cust partition that you have to remove to use them on L21 / L22
As I don't have those phones I can't dump the /cust partition to help you
Flashing this should return you phone to working order >> http://forum.xda-developers.com/honor-5x/development/rom-r1-modaco-custom-rom-t3336458
Click to expand...
Click to collapse
Thanks for the tip, been trying to flash the update.app, I downloaded that from the honor India site itself....but since TWRP is not letting me do anything (can't even swipe to unlock), I am only since trying fastboot commands.
I have the cust.img file for my device, but trying to flash it in fastboot is not working...it says "Remote: Command not allowed".....am sooo screwed! I even tried flashing back stock recovery and HiSuite seems to not support this device!!
SOLVED: Downloaded the official firmware, placed the "dload" folder which contains the update.app in the root of the sd card, went into download mode on phone (vol up + vol dow + power) and the system installed the firmware automatically.....booted back into the stock system now, next will reflash TWRP and restore back up
nandakalyan said:
Thanks for the tip, been trying to flash the update.app, I downloaded that from the honor India site itself....but since TWRP is not letting me do anything (can't even swipe to unlock), I am only since trying fastboot commands.
I have the cust.img file for my device, but trying to flash it in fastboot is not working...it says "Remote: Command not allowed".....am sooo screwed! I even tried flashing back stock recovery and HiSuite seems to not support this device!!
Click to expand...
Click to collapse
How did you get TWRP messed up ?
If you restored stock recovery the phone will flash the update.app it's self
The update.app must be in a folder on the sdcard called dload
then boot the phone with power plus volume Up and down when the screen goes black release the power key but hold volume up / down till the flash starts
and the phone should start the flash on it's own.
I can reproduce it on my phone with the above instructions
When you get the phone back up and running it would be a good idea to make a backup of your /cust partition for the future instruction on how to dump it and create your own rescue rom are here >> http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
I'm getting an odd play store error after I install 1 app I get the error (error retrieving information from server) and the only way to fix it is to reboot
Sent from my KIW-L24 using XDA-Developers mobile app
clsA said:
How did you get TWRP messed up ?
If you restored stock recovery the phone will flash the update.app it's self
The update.app must be in a folder on the sdcard called dload
then boot the phone with power plus volume Up and down when the screen goes black release the power key but hold volume up / down till the flash starts
and the phone should start the flash on it's own.
I can reproduce it on my phone with the above instructions
When you get the phone back up and running it would be a good idea to make a backup of your /cust partition for the future instruction on how to dump it and create your own rescue rom are here >> http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
Click to expand...
Click to collapse
I have no idea what hap to TWRP....I am not at all techie, so only generally using common sense and following instructions but awesome advice on the cust partition back up and the rom, thanks a zillion for that!:good:
voldomart13 said:
I'm getting an odd play store error after I install 1 app I get the error (error retrieving information from server) and the only way to fix it is to reboot
Sent from my KIW-L24 using XDA-Developers mobile app
Click to expand...
Click to collapse
I got the same error with play store...matter worse, I can't play any of google app such music, movie, drive,...
Anyone else???
voldomart13 said:
I'm getting an odd play store error after I install 1 app I get the error (error retrieving information from server) and the only way to fix it is to reboot
Sent from my KIW-L24 using XDA-Developers mobile app
Click to expand...
Click to collapse
Can you tell me which rom you used
Caltinpla said:
I got the same error with play store...matter worse, I can't play any of google app such music, movie, drive,...
Anyone else???
Click to expand...
Click to collapse
Which Rom ?
I'm was getting a playstore sync error and it was not syncing my contacts. I removed the account and rebooted and reinstalled the same account and it worked
clsA said:
Can you tell me which rom you used
Which Rom ?
I'm was getting a playstore sync error and it was not syncing my contacts. I removed the account and rebooted and reinstalled the same account and it worked
Click to expand...
Click to collapse
The B151-DeOdexed without Xposed...I reflashed back to stock B151 and everything works fine
Caltinpla said:
The B151-DeOdexed without Xposed...I reflashed back to stock B151 and everything works fine
Click to expand...
Click to collapse
well that helps narrow it down .. your on L24 correct ?
it may be something in the /cust messing it up. I'll try some things
clsA said:
well that helps narrow it down .. your on L24 correct ?
it may be something in the /cust messing it up. I'll try some things
Click to expand...
Click to collapse
Yes, I'm on L24 and thank you for your hard work...really appreciated!!!
Can you tell me how to split the notification and ring volume so I can adjust them individually? Ty
Hello there! thanks for your time.
I swear that I tried everything.
I received my HTC 10 like 1 almost 2 weeks ago.
I unlocked the bootloader, flashed the recovery, supersu, everything just fine. Everything works. Except that when I boot into the recovery TWRP ask for the password to decrypt /data. I put my pin = password failed. I tried to resetting the pin, tried putting a password, leaving it blank (tested default_password too) but I cant make TWRP work mounting /data. It always says that password is incorrect.
I even tried factory reset 2 times.
the version is: 3.0.2-2
Any ideas?
Thanks again guys! have a great day!
Anytime its asked me for a password I just press cancel.
My understanding is that the HTC 10 in encrypted by a proprietary HTC code.
Yep - just hit Cancel on that screen.
See the TWRP thread here - http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139
"NOTE: TWRP CANNOT decrypt HTC Sense ROMs!!"
And this in the second post
"5. My storage is encrypted, and TWRP can't decrypt it. How am I supposed to flash anything?
First, hit the "Cancel" button at the decryption prompt to continue to the TWRP Main Menu. Storage doesn't need to be decrypted to root the device or flash custom ROMs. If storage is decrypted on this device, mobile network will stop working.
6. Is it possible to retain encryption AND make a data partition backup in TWRP?
No. TWRP cannot currently decrypt /data on this device. That is due to HTC's use of proprietary encryption. Until someone figures out a way around that, the only way to access /data in TWRP is to unencrypt using the "Format Data" option in TWRP and disabling the forceencrypt flag in the ramdisk (which will break mobile network in Android)."
Hey! thanks!
That is what I did, I hit cancel and flashed everything. But now there is an OTA Update. I downloaded, hit install, and the phone reboots on recovery, I thought that the password was needed in order to process the update.
well thanks again guys!!
deftoner said:
That is what I did, I hit cancel and flashed everything. But now there is an OTA Update. I downloaded, hit install, and the phone reboots on recovery, I thought that the password was needed in order to process the update.
Click to expand...
Click to collapse
That's exactly what I did. And I just learnt (see my question here) that you can't install OTA updates with a custom recovery image installed. It seems, you'll either have to give up on the OTA update or you need to flash the stock recovery image to be able to install the OTA update.
There's a stock ROM in this thread. I THINK that rverts the recovery image as well. But it's a Euro ROM, not sure how that impacts other region phones.
---------- Post added at 01:21 AM ---------- Previous post was at 01:03 AM ----------
Here's the stock ROMs and stock Recovery image thread:
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
You need to get the CID and MID of your phone first. I followed these instructions very easily.
I'm going to try flashing the OTA update for my model.... once I've read it all.
iteese said:
That's exactly what I did. And I just learnt (see my question here) that you can't install OTA updates with a custom recovery image installed. It seems, you'll either have to give up on the OTA update or you need to flash the stock recovery image to be able to install the OTA update.
There's a stock ROM in this thread. I THINK that rverts the recovery image as well. But it's a Euro ROM, not sure how that impacts other region phones.
---------- Post added at 01:21 AM ---------- Previous post was at 01:03 AM ----------
Here's the stock ROMs and stock Recovery image thread:
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
You need to get the CID and MID of your phone first. I followed these instructions very easily.
I'm going to try flashing the OTA update for my model.... once I've read it all.
Click to expand...
Click to collapse
Hey, thanks for your reply.
In fact its easier than that, on this guide you have the recovery images to flash it back. http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
I flash the recovery back, and applied the ota, I have an error about the version of the ota for the phone, but you may have better luck.
btw I guess I flashed the incorrect recovery. Need to select the correct version I'm trying that now
iteese said:
That's exactly what I did. And I just learnt (see my question here) that you can't install OTA updates with a custom recovery image installed. It seems, you'll either have to give up on the OTA update or you need to flash the stock recovery image to be able to install the OTA update.
There's a stock ROM in this thread. I THINK that rverts the recovery image as well. But it's a Euro ROM, not sure how that impacts other region phones.
---------- Post added at 01:21 AM ---------- Previous post was at 01:03 AM ----------
Here's the stock ROMs and stock Recovery image thread:
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
You need to get the CID and MID of your phone first. I followed these instructions very easily.
I'm going to try flashing the OTA update for my model.... once I've read it all.
Click to expand...
Click to collapse
deftoner said:
btw I guess I flashed the incorrect recovery. Need to select the correct version I'm trying that now
Click to expand...
Click to collapse
If you're US unlocked variant, you can follow my guide, here:
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
If you're another variant, reply in the above thread and I can help you find the versions of the files you need to flash.
deftoner said:
Hey, thanks for your reply.
In fact its easier than that, on this guide you have the recovery images to flash it back. http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
I flash the recovery back, and applied the ota, I have an error about the version of the ota for the phone, but you may have better luck.
Click to expand...
Click to collapse
Reboot download
Make sure your mid matches the US one (I had super cid for mine but apparently if the mid doesn't match it will give error as well)
fastboot getvar all
will tell you
then once it was all set
fastboot flash zip nameof_file.zip
DO IT TWICE!
Then reboot your download to see if the changes took place
You then have to reflash your TWRP recovery because the zip will flash stock recovery
if you are still getting the password box, click cancel for TWRP, wipe > advance and wipe data
good luck
With this encryption thing going on I can't even do a complete advanced wipe: "unable to mount storage"
Orch4rd said:
With this encryption thing going on I can't even do a complete advanced wipe: "unable to mount storage"
Click to expand...
Click to collapse
Are you asking for help?
jollywhitefoot said:
Are you asking for help?
Click to expand...
Click to collapse
No... I'm just complaining.
Orch4rd said:
No... I'm just complaining.
Click to expand...
Click to collapse
OK cool. Carry on then.
Orch4rd said:
With this encryption thing going on I can't even do a complete advanced wipe: "unable to mount storage"
Click to expand...
Click to collapse
you could...i do it often before flashing new build....
Thanks for this thread. I spent an hour typing all of my different passwords into the phone trying to figure it out what it was. Then I hit cancel per this thread.
CryptoJones said:
Thanks for this thread. I spent an hour typing all of my different passwords into the phone trying to figure it out what it was. Then I hit cancel per this thread.
Click to expand...
Click to collapse
hay I really need help as in phones setting in security tap is says "encrypt phone - phone is encrypted".
is that a good thing? I want my phone to be "data" unlocked if u know what I mean? help
also I got my phone about 3 weeks and unlocked the bootloader but S-on and I live in Europe.
I try the rom with f2fs support and always when I try to boot the rom with "data" and "cache" formatted as f2fs it doesen´t boot and I try to boot the compatible rom and kernel with ext4 first and when I got a full boot I go to recovery to format cache and data as f2fs but this time when it boots "data" reverts back to ext4 and cache stays as f2fs?
any idea!
I use disk info app and is it because my phone is encrypted data never stays as f2fs or something else as I don´t know much about "decrypt or uncrypt" and the other...
thnx!
TWRP not PIN Pattern
Moved this post to main TWRP
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.
Hello XDA, I am trying to figure out all the steps to get mainly Twrp, Magisk, Viper and, Substratum working correctly without any hiccups. I have been reading the forums all day and trying to get all the files necessary to get all that working and the files to revert to stock if it doesn't work. I know after the Bootloader is unlocked I won't be able to relock it due to no Moto signed boot images. I just don't want to brick it and be here with other problems later.
So far I have done the following
1. Installed ADB and Fastboot + Drivers
2. Done everything to get the code to unlock bootloader
3. Downloaded the files to flash twrp from (https://forum.xda-developers.com/z2-force/development/twrp-3-1-1-0-moto-z2-force-nash-t3687421)
4. Downloaded the latest stock NCX26.122-59-8 to extract the boot img and patch it with Magisk manager from (https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859)
I think I have everything I need to get it rooted. Here's where I get kinda confused. My phone (XT1789-03 Sprint) is on NCXS26.122-59-8-11 November patch (I think the S is for sprint lol). Would It be okay to flash the Magisk patched boot img from the one I downloaded after I unlock the bootloader? Is Twrp necessary? Is there anything else I need to know about? Thanks in advance.
This forum just died? What the hell noone helps anymore???
Sent from my XT1650 using Tapatalk
TWRP is official now. Download the bootable image from https://twrp.me/motorola/motorolamotoz2force.html and the corresponding zip. Boot to twrp and flash the zip. Flash Magisk and install what you want that needs root. Hint: I'd advise the Viper4Android from Magisk modules in the magisk app.
Uzephi said:
Boot to twrp and flash the zip.
Click to expand...
Click to collapse
What do you mean by this? Fastboot flash TWRP, but then flash what zip?
breakerfall said:
What do you mean by this? Fastboot flash TWRP, but then flash what zip?
Click to expand...
Click to collapse
Do NOT flash the twrp img. "Fastboot boot imagename.img" then flash the twrp zip if you wish to have it as your recovery. You can find both on twrp.me.
This hard.. even with instructions u don't know what to flash where and what it will achieve lol. I just want unlock and root. What's the easiest way to do that on sprint z2 force?
So far I understand u need to install twrp to root with magisk, then use twrp to flash magisk Img, then boot up install magisk apk and u should be rooted. Hope I've got that all right.
But do any of the images on this site also unlock gsm on sprint or TMobile?
Sent from my Moto Z (2) using Tapatalk
Uzephi said:
Do NOT flash the twrp img. "Fastboot boot imagename.img" then flash the twrp zip if you wish to have it as your recovery. You can find both on twrp.me.
Click to expand...
Click to collapse
Not trying to be a **** here, but what exactly do you mean by imagename.img? .. the twrp.img file? and if I don't want TWRP as recovery, then are you saying that it will remain stock if I don't flash the twrp.zip file?
I recently did this on an Essential phone, and the process was: fastboot flash TWRP.img, reboot to TWRP (recovery), flash stock boot.img, then flash magisk.zip.
The last phone I rooted/rommed before that was a Nexus 6, and **** was different then.
breakerfall said:
Not trying to be a **** here, but what exactly do you mean by imagename.img? .. the twrp.img file? and if I don't want TWRP as recovery, then are you saying that it will remain stock if I don't flash the twrp.zip file?
I recently did this on an Essential phone, and the process was: fastboot flash TWRP.img, reboot to TWRP (recovery), flash stock boot.img, then flash magisk.zip.
The last phone I rooted/rommed before that was a Nexus 6, and **** was different then.
Click to expand...
Click to collapse
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!!
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
jmagi said:
So far I understand u need to install twrp to root with magisk, then use twrp to flash magisk Img, then boot up install magisk apk and u should be rooted. Hope I've got that all right.
Click to expand...
Click to collapse
You don't flash the TWRP.img file!!! You fastboot boot it. It will temp boot to twrp
Uzephi said:
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!
Click to expand...
Click to collapse
Ahhhh!
Fastboot boot TWRP.img, then just flash the magisk.zip in TWRP, right?
Thank you!
Also, @jmagi -- you shouldn't have to manually install the magisk apk. Flashing the magisk.zip in TWRP should result in a Magisk app in your "all apps" next time you boot.
Uzephi said:
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!!
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
You don't flash the TWRP.img file!!! You fastboot boot it. It will temp boot to twrp
Click to expand...
Click to collapse
Ohhh thats how it works. So i dont have to install twrp from playstore?
Sent from my Moto Z (2) using Tapatalk
jmagi said:
Ohhh thats how it works. So i dont have to install twrp from playstore?
Click to expand...
Click to collapse
No, you don't
Uzephi said:
No, you don't
Click to expand...
Click to collapse
Ok got it thank you. So fastboot boot twrp, and from twrp flash magisk.img then run magisk after bootup.
I too havent rooted a phone since droid4 which was just doubleclick a bat file lol. All this twrp stuff is new to me. Hope i got it right. Love this phone. Might get another one soon and the qwerty keyboard mod is expected on amazon within a couple months. Only reason i upgraded.
Sent from my Moto Z (2) using Tapatalk
jmagi said:
Ok got it thank you. So fastboot boot twrp, and from twrp flash magisk.img then run magisk after bootup.
I too havent rooted a phone since droid4 which was just doubleclick a bat file lol. All this twrp stuff is new to me. Hope i got it right. Love this phone. Might get another one soon and the qwerty keyboard mod is expected on amazon within a couple months. Only reason i upgraded.
Click to expand...
Click to collapse
Some people had issues and needed to wipe user data after flashing magisk
LG V30 T-Mobile H932 20r ROM
For U.S. T-mobile H932 ONLY. Do NOT install this on any other V30/V30+/V30S except U.S. T-mobile H932. You will brick your phone.
DISCLAIMER : I do not hold responsiblity for any of the following but not limited to : Bricks due to not reading, nuclear war, cat dying. I will not be held responsible for any damage of any kind due to the result of this zip. It is held under your own risk. This does not mean that i wont help in any way shape or form to recover from anything that may happen at the result of flashing this zip. PLEASE FLASH RESPONSIBLY! PS. This zip has NOT been tested by me!
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This zip is created from the original KDZ. It contains almost the complete 20r firmware, but the partition table rewriting part and recovery image is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition. This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited / advanced it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
Stock build made from official KDZ
Stock Build.prop
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
Added DTS build prop
Added all lockscreen weather animations build prop
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already, otherwise you wouldn't need this zip )[Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
H93220r.zip [Download]
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20r firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occure, maybe you need to do a factory reset to start fresh*
Flash the 20r zip, then Magisk zip when you need root, then reboot to System = you're DONE
P.S.: could be, that you first need to boot up your fresh install and set it up before you can flash magisk.
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Rom Version
Android Version: 8.0 Oreo
Android security patch level: 2019-1-1
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
#RESERVED
Please to anyone who had issues with the zip.....
We have a fix!
Flash this zip
https://www.androidfilehost.com/?fid=1395089523397908552
Then flash a rom from your SD CARD
ONLY FLASH THIS OF YOU HAD A BRICK FROM 20R!!
Zip is live! Enjoy!
your zip name is wrong.. should be h93220r* ( it doesnt matter but i was confused at first)
also, i flashed it and nothing happened. my system is still the same as i was before (20p)
and in the script, i think it says 'model=VS996' or something. since it just words, it may not matter.
but maybe you used the wrong script for h932
In any case, the zip did nothing for me. flashing only took about 10 secs in total, and flashing system barely took a second.
So seems theres an issue with the zip. Maybe upload didn't quite finish as I did it while at work via rdp to my pc at home. Will look into it when I get off work
JohnFawkes said:
So seems theres an issue with the zip. Maybe upload didn't quite finish as I did it while at work via rdp to my pc at home. Will look into it when I get off work
Click to expand...
Click to collapse
Did you remove the file?
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Did you remove the file?
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour
JohnFawkes said:
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour
Click to expand...
Click to collapse
Ahh ok, thought I was missing something.
Sent from my LG-H932 using XDA Labs
JohnFawkes said:
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour
Click to expand...
Click to collapse
looking forward to the fix.
I figured people might want these files.
Root-System-Media
Uploading new zip now! figured out all issues
JohnFawkes said:
Uploading new zip now! figured out all issues
Click to expand...
Click to collapse
Awesome thank you!
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Awesome thank you!
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
no problem. should be live in about 15 minutes
zip is live!
Awesome. Woke up this morning to the system update notification. Glad there are still T-Mobile users around here that works to get this stuff out. Downloading now. Will report back after I flash it.
---------- Post added at 07:43 AM ---------- Previous post was at 07:19 AM ----------
BROKEN1981 said:
I figured people might want these files.
Root-System-Media
Click to expand...
Click to collapse
Are these new in this update?
JohnFawkes said:
zip is live!
Click to expand...
Click to collapse
At the end of the flash it looks like it flashed fine but then it tells me it failed to mount everything. When I go to reboot into the system it tells me there is no OS. I was just going to flash the 20p zip I had but then it restarted and now I can't get into TWRP again. Now it just restarts into fastboot mode
UPDATE: I was able to get back into TWRP by going through the factory reset option (Volume down + Power, etc.) I'm now flashing the 20p zip I have.
UPDATE 2: Didn't work. Got into a bootloop. Restoring an old Lineage backup I have. Should have made a backup of my current state before flashing but I wasn't thinking
UPDATE 3: That didn't work either. Everything I flash it tells me failed to mount '/persist-lg' and just boot loops. I guess the next thing to do is try and use LGUP to restore
Same here as above. Doesnt mount system persist cache.
sunmybun said:
Same here as above. Doesnt mount system persist cache.
Click to expand...
Click to collapse
Flashing anything else doesn't fix it either. My phone is chillin' in recovery mode until I can figure it out
im working on fix guys. zip is removed for now. no clue why this is happening. but a fix is being worked on
JohnFawkes said:
im working on fix guys. zip is removed for now. no clue why this is happening. but a fix is being worked on
Click to expand...
Click to collapse
Thanks. Searching around, I see there have been people having issues like this before with other devices. Something to do with the persist.img. Did the last zip include one? Also, I hope whatever it is can be fixed with a new zip. I don't know why restoring a backup or flashing an old full stock zip wouldn't fix anything.
This is basically what I'm getting
http://en.miui.com/thread-467490-1-1.html