Develop Bugs

Stuck on Restart

After 3 yrs on custom ROMs, I've managed to screw up my Note 2, and I'm lost as to how to restore my phone.
I've been on the Jedi Touchwiz ROM for ages, and about a year ago, changed over to Cyanogen.
I went from the Cyanogen 0825-Nightly to the latest 1017-Nightly by:
-backing up my data in Titanium Root,
-going into Recovery and doing a Wipe Data/Factory Reset,
-install the new 1017-Nightly image
-install GAPPS for Android 5.1
then reboot.
All is good on reboot, and I enter my Google info, mount desktop. I then install the Titanium Root app, and it reports that I've lost Root.
So I try to update SuperSU, and it fails to do it directly, and trying to do it with CWM Recovery fails as well.
I then use Recovery to Wipe Data/Factory Reset again,
reinstall 1017-Nightly and GAPPS 5.1
and reboot, thinking I must have missed something.
Now... I'm stuck on the Cyanogen Loadscreen (pulsing Blue Head). I haven't let it go longer than 10mins, but I don't think it should take that long.
I tried going back to my 0825-Nightly after this point, and no luck, I'm stuck on the Loadscreen.
Here are my questions:
1. I do not understand what being stuck on the Loadscreen means... what do I need to fix? Can I do it via Recovery?
2. How do I obtain Root again? The methods I originally used were for Jellybean... are there updated methods now?
3. What prevents SuperUser from updating?
Thanks for any help guys... I need my phone back!

on your second attempt you got stuck on boot screen??
i think you can wait for some more time and check..
remove battery re-insert and check whether it boots or not.. or else do a factory reset n check whether it boots or not..
if not do a factory reset and re flash the CM to check.
. if all failed then flash n7100 stock firmware via odin ..
about rooting.. if you have a custom recovery you can try to re root via custom recovery.. simply flash supersu.zip in your custom recovery...
https://download.chainfire.eu/696/SuperSU

Hi Tornado,
BTW, Tornados, esp the IDS variant, are great planes. Nice to see your avatar :good:
I had a comment from elsewhere, so I tried this:
-wipe data/factory reset inside CWM Touch Recovery
-formatted /system partition
-installed the 20151007 CM 12.1 Snapshot
-installed GAPPS 5.1
and then let it reboot. LOL, I've been worried about screen burn in, but I left it run for over an hour... no joy. It never left the loadscreen.
Just for grins, I tried the older CM11 version, and whilst the loadscreen problem still persisted, I did recognize the older boot animation.
At this point, am convinced I have soft-bricked the phone, since I have Recovery and Bootloader (thank goodness) still working, but something else is either not clearing or is corrupted.
I'm definitely thinking about flashing stock firmware again, but not sure if I should go back to Jellybean? or find an Android 5 image?
Am also looking into ADB commands to see if there is something deeper I can flush out, but I really don't want to make things worst.
I'm hoping that someone else has run into a similar situation... cheers for your suggestions!
tornado92 said:
on your second attempt you got stuck on boot screen??
i think you can wait for some more time and check..
remove battery re-insert and check whether it boots or not.. or else do a factory reset n check whether it boots or not..
if not do a factory reset and re flash the CM to check.
. if all failed then flash n7100 stock firmware via odin ..
about rooting.. if you have a custom recovery you can try to re root via custom recovery.. simply flash supersu.zip in your custom recovery...
https://download.chainfire.eu/696/SuperSU
Click to expand...
Click to collapse

Enter custom recovery.. and find mount and unmount area.. and select mount system then restart phone n tell me result

I went into Recovery:
-selected Mount System
-Reboot
Phone stayed on Loadscreen for 30 mins. After that, I yanked the battery.
I'm going to go into Bootloader, and swap out CWM for TWRP to see if that makes a difference. If any changes, will report back.
tornado92 said:
Enter custom recovery.. and find mount and unmount area.. and select mount system then restart phone n tell me result
Click to expand...
Click to collapse

UGH. Still no joy.
Changed out CWM Recovery to TWRP,
-did Full Reset
-Advanced Wipe of System, Data, Int Storage
-install 1007 Snapshot of CM12.1
-install GAPPS 5.1
then reboot.
After 35mins of loadscreen, yanked the battery.
I can change Recovery images like a Boss now at least :silly:
motionmonk said:
I'm going to go into Bootloader, and swap out CWM for TWRP to see if that makes a difference. If any changes, will report back.
Click to expand...
Click to collapse

Best option for you now is to unbrick your device to official stock firmware... and then try to install custom rom again... i can make ur device boot normally at this stage.. but ur phone will boot on factory imei..meaning wont detect sim .. so first unbrick your device to be at safer place to avoid further corrupting the efs.. hahahaaa
---------- Post added at 12:05 PM ---------- Previous post was at 11:56 AM ----------
Install official firmware.. and enter stock recovery.. and try to reeset ur phone.. if u get a error code e/failed.to.mount efs.. ur efs is.messed up which is preventing ur phone from booting.. but if dont get any error your phone will boot normally
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
tornado92 said:
Best option for you now is to unbrick your device to official stock firmware... and then try to install custom rom again... i can make ur device boot normally at this stage.. but ur phone will boot on factory imei..meaning wont detect sim .. so first unbrick your device to be at safer place to avoid further corrupting the efs.. hahahaaa
---------- Post added at 12:05 PM ---------- Previous post was at 11:56 AM ----------
Install official firmware.. and enter stock recovery.. and try to reeset ur phone.. if u get a error code e/failed.to.mount efs.. ur efs is.messed up which is preventing ur phone from booting.. but if dont get any error your phone will boot normally
Click to expand...
Click to collapse
Keep updating me. I will guide u further

Just so I don't dig a deeper hole, I want to clarify a few points...
1. by going back to stock firmware, do you mean a certain OS version? If I find a stock Android 5 version, is that ok? or would going back to like Jellybean be better?
2. you mentioned that the factory imei will not detect my sim, so the radio won't work? If so, there is a way to fix this?
3. again for stock firmware... my phone is an American N7100 GSM (T-Mobile) version. About 2 years ago, it became an Int'l N7105 LTE mod, since I liked the feature set more, plus one of my past ROMs (Jedi-X?) I think changed it to the N7105.
-should I go back to a pure N7100 stock firmware, or a N7105 firmware?
Will start looking for firmware options in the meantime.
tornado92 said:
Best option for you now is to unbrick your device to official stock firmware... and then try to install custom rom again... i can make ur device boot normally at this stage.. but ur phone will boot on factory imei..meaning wont detect sim .. so first unbrick your device to be at safer place to avoid further corrupting the efs.. hahahaaa
Install official firmware.. and enter stock recovery.. and try to reeset ur phone.. if u get a error code e/failed.to.mount efs.. ur efs is.messed up which is preventing ur phone from booting.. but if dont get any error your phone will boot normally
Keep updating me. I will guide u further
Click to expand...
Click to collapse

There is no 5.0 stock firmware for n7100 . Latest is 4.4.2 if your phone model is n7100 in download mode. Then your phone isnt tmobile.. and about factory imei .. first unbrick your device to check the status of your imei.. it could be fine also...right now phone not booting up.. so i cant tell...

Understood, grabbing 4.42 Stock Images.
From this page: http://forum.xda-developers.com/showthread.php?t=2740496
I grabbed the first 2x Installers.
-KitKat 4.4.2. Stock Rom by robalm
-4.4.2 DN3 (Ditto Note 3) Rom from E-Team
Both are these are .zip files; the one by robalm suggests using Odin for install. The 2nd one by Electron Team using custom Recovery (CWM/TWRP).
Will try Electron Team first, and if nothing happens, will try Odin and 1st one.
tornado92 said:
There is no 5.0 stock firmware for n7100 . Latest is 4.4.2 if your phone model is n7100 in download mode. Then your phone isnt tmobile.. and about factory imei .. first unbrick your device to check the status of your imei.. it could be fine also...right now phone not booting up.. so i cant tell...
Click to expand...
Click to collapse

As u wish buddy. I recommend odin one first as its a stock firmware

Tried the Ditto Note3 ROM; no luck.
Inside TWRP Recovery, I did:
-Factory Reset
-Format Data
-inside Mount settings, verified EFS, cache, System, Data, Ext_SDCard were selected
-install Zip FAILED:
Error flashing zip ‘/external_sdcard/N7100XXUFND3_N7100OXAFND3_XEF.zip'
updating partition details…
…done
That is the extent of the error reporting. Tried 2x, both had same error log.
Yanked battery, went into Recovery again and re-installed the CM12 1007 Snapshot. I am back to the same loadscreen loop issue.
Moving on to Odin and the KitKat 4.4.2 ROM by robalm
motionmonk said:
Understood, grabbing 4.42 Stock Images.
Will try Electron Team first, and if nothing happens, will try Odin and 1st one.
Click to expand...
Click to collapse

Something happening with your partitions probably, listen the advice of tornado and flash it via odin.
Sent from my GT-N7100

Oh bugger me. Can't think straight.
I installed the wrong ROM. I copied the 'robalm' 4.4.2 KitKat ROM to my ext SD card by mistake. No wonder it failed.
Tried the correct DittoNote4 ROM; it failed.
This is from the TWRP recovery log:
minzip: Error writing 8192 bytes from zip file from 0xbe88da44: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/usr/srec/en-US/g2p_fst"
about to run program [/tmp/floating_message.sh] with 1 args
- Symlinking files
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sdcard/DN4_v2.1_by_E-Team.zip'
Error flashing zip '/external_sdcard/DN4_v2.1_by_E-Team.zip'
Updating partition details...
I: Data backup size is 6MB, free: 11168MB.
Still going to give the "robalm" ROM a try in Odin.
motionmonk said:
Tried the Ditto Note3 ROM; no luck.
Inside TWRP Recovery, I did:
-Factory Reset
-Format Data
-inside Mount settings, verified EFS, cache, System, Data, Ext_SDCard were selected
-install Zip FAILED:
Error flashing zip ‘/external_sdcard/N7100XXUFND3_N7100OXAFND3_XEF.zip'
updating partition details…
…done
That is the extent of the error reporting. Tried 2x, both had same error log.
Yanked battery, went into Recovery again and re-installed the CM12 1007 Snapshot. I am back to the same loadscreen loop issue.
Moving on to Odin and the KitKat 4.4.2 ROM by robalm
Click to expand...
Click to collapse

Heeehe guide line
1: must have a working brain hahahah buddy

YAY! I'm in!
I used N7105XXDMA6_Deodex_Rooted_01_28_13-teshxx.zip and flashed via TWRP Recovery.
I was able to enter Google info in Samsung setup, and am up on device desktop.
Insert SIM Card, check About Device, I have this for a Status Check...
Network-unknown
Mobile Network Type-unknown
Service State-Out of service
Roaming-not roaming
Mobile network state-disconnected
My phone number-Unknown
IMEI-Unknown
IMEISV-Unknown
At least it's not the Loadscreen is all I can say!
Ok, gone for a few for a late lunch.
Will let the device settle in, and will check back for any further suggestions.
Thanks again Tornado!

WOT?
Life has an... Operations Manual?
hehe
tornado92 said:
Heeehe guide line
1: must have a working brain hahahah buddy
Click to expand...
Click to collapse

Your not in buddy.. ur efs partition is probably screwed up whats the use of a phone if it doest detect sim :s
---------- Post added at 11:06 PM ---------- Previous post was at 11:04 PM ----------
Flash stock firmware via odin to check whether imei comes back or not.. and dont mess too much with phone.. imei repair is not a easy thing.. ahaahah my advice for u
---------- Post added at 11:12 PM ---------- Previous post was at 11:06 PM ----------
whats ur actual model number.. is it n7100 or n7105 .. if ur phone is n7100 dont use n7105 firmwares.. a both are different hardware wisely yet your imei corrupted now due to different modem in n7105 firmware...

Am still here, been trying to track down valid firmware images.
I believe my phone is a N7100. Somewhere in replacing ROMs in the past, I think I installed an Int'l N7105 TouchWiz ROM (Jedi-X) and stuck with that using a T-Mo modem file.
Found a stock 4.3 for my SGH-T889 T-Mobile GSM phone today. So, tried an install using JODIN, an open-source Odin app, but it didn't reboot the phone, so not sure if it took.
Going to install a Windows partition, load KIES and true ODIN and try again tomorrow. Will update then.

@motionmonk buddyy go to download mode(pres volume down +power+ home) and post screen shot of it..
Sent from my GT-N7105 using Tapatalk

TWRP and Encryption password for data.

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

What TWRP and SuperSU versions?

Hi all,
I'm on OpenBeta9 and have /data formatted with f2fs. Couldn't find a clear indication of what TWRP version (and SuperSU) is compatible with this setup.
Could you please assist?
Thanks

Normaly, twrp-3.0.2-1.28-oneplus3 and SR5-SuperSU-v2.78-SR5-20161130091551. But in my case, i had a encrypt problem with the recovery

MrSkyFail said:
Normaly, twrp-3.0.2-1.28-oneplus3 and SR5-SuperSU-v2.78-SR5-20161130091551. But in my case, i had a encrypt problem with the recovery
Click to expand...
Click to collapse
Hi MrSkyFail, thanks for the reply.
Was your problem preventing you to use TWRP normally, or something I could work around?
Also, would you have download links? SuperSU should be easy for me to find, by TWRP is always a mess, since it's a mod version.
Thanks

andrea.ippo said:
Hi MrSkyFail, thanks for the reply.
Was your problem preventing you to use TWRP normally, or something I could work around?
Also, would you have download links? SuperSU should be easy for me to find, by TWRP is always a mess, since it's a mod version.
Thanks
Click to expand...
Click to collapse
For TWRP : http://forum.xda-developers.com/devdb/project/dl/?id=21835
Yeah, i couldn't decrypt my phone in recovery. I try with beta 9 official i lose my TWRP recovery for offical recovery and works.
---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------
Look this : http://forum.xda-developers.com/oneplus-3/how-to/rom-oxygenos-beta-9-nougat-update-t3519069

MrSkyFail said:
For TWRP : http://forum.xda-developers.com/devdb/project/dl/?id=21835
Yeah, i couldn't decrypt my phone in recovery. I try with beta 9 official i lose my TWRP recovery for offical recovery and works.
---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------
Look this : http://forum.xda-developers.com/oneplus-3/how-to/rom-oxygenos-beta-9-nougat-update-t3519069
Click to expand...
Click to collapse
I found out that if you only flash OB9 from TWRP, even though you formatted your /data partition and is f2fs, if you don't flash SU before your first boot, your phone becomes encrypted and you will have TWRP pin issues.
The other issue I found was that if you flash OB9, then try flashing SU (I'm running SR5 right now), it doesn't want to boot. The only way I got it to work is after you flash OB9, Mount /system and delete a couple of google apps (for me, I deleted Calendar and gmail; you can download these after you boot up from playstore), then flash SU, then reboot, and profit.
So order of things for me:
1. Wipe (make sure /data is f2fs)
2. Flash OB9
3. Flash TWRP (modded 1-28)
4. Reboot to recovery (you may have to do a manual power off then volume down + power on)
5. Mount /system and delete calendar and gmail apps
6. Flash SU (SR5; I think there's a newer version but I haven't tried it with the new one).
7. Wipe Dalvik and Cache
8. Reboot System
If everything is done correctly, your phone will reboot twice.
You will have dm-verity and unlocked bootloader warning screens.
First boot takes about 3-5 min.

Why would deleting a couple google apps be necessary? I don't get it. And this applies for having cache f2fs too I assume?

Stupifier said:
Why would deleting a couple google apps be necessary? I don't get it. And this applies for having cache f2fs too I assume?
Click to expand...
Click to collapse
You may only need to mount /system before you flash SU. I can't find the post at the moment but this was mentioned (delete a few apps) when OB8 first came around.
Only the /data partition has F2FS support on stock OB8 and OB9.

Rooting 8.0 Guide?

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.

[Solved]TWRP doesn't work after official Pie update- decryption password required

I use stock recovery and official miui global rom in my phone along with magisk root. Everytime a new update comes i restore stock images from magisk, then apply the update, then again boot into twrp (just boot), flash the magisk and done. That way i maintain the stock recovery, OS, and root as well.
Yesterday i got the official Pie update from Xiaomi, i restored the stock images from magisk, updated to Pie. But now if i try to boot into twrp to flash magisk, it asks for decryption password. My phone is encrypted, from past one year twrp used to work completely fine after i entered the password (encrypted with lock screen pw) but now it says decryption failed. I have tried everything-
1. Removing the lock screen and encryption altogether.
2. Changing the encryption/lock screen pw to pattern/pin/password
But no luck, it says decryption failed. I'm unable to boot into twrp.
Also one weird thing, if i set pattern encryption pw, it asks for alphanumeric pw in twrp decryption screen. And vice versa. I've tried many twrp versions including the latest one. HELP!

Solved by using OrangeFox Recovery (OrangeFox-R9.0-2-whyred-MIUI-Pie.zip) from https://sourceforge.net/projects/orangefox/files/whyred/
Magisk works along with full encryption with lock screen password

Reboot took me to system reboot
avguser23 said:
Also updating twrp works same way
Click to expand...
Click to collapse
Reboot took me to system reboot and phone's stock recovery opened when I went to recovery mode
---------- Post added at 04:48 PM ---------- Previous post was at 04:26 PM ----------
akhu5 said:
Solved by using OrangeFox Recovery (OrangeFox-R9.0-2-whyred-MIUI-Pie.zip) from
Magisk works along with full encryption with lock screen password
Click to expand...
Click to collapse
Also, it would be really helpful, if you told me the steps and precaution to install orangefox, I am wishing to flash pixel experience and use Gcam. But I seem to be stuck in recovery flashing.

Binish Joshi said:
Reboot took me to system reboot and phone's stock recovery opened when I went to recovery mode
---------- Post added at 04:48 PM ---------- Previous post was at 04:26 PM ----------
Also, it would be really helpful, if you told me the steps and precaution to install orangefox, I am wishing to flash pixel experience and use Gcam. But I seem to be stuck in recovery flashing.
Click to expand...
Click to collapse
Cause orange didn't restart into recovery mode and booted into system.

akhu5 said:
Also one weird thing, if i set pattern encryption pw, it asks for alphanumeric pw in twrp decryption screen. And vice versa. I've tried many twrp versions including the latest one. HELP!
Click to expand...
Click to collapse
The dots translate into numbers in the following pattern:
1 2 3
4 5 6
7 8 9
Please note that this is what I read somewhere else when searching for my solution to the original problem (Can't decrypt Pie storage using password from Oreo).

arcanemachine said:
The dots translate into numbers in the following pattern:
1 2 3
4 5 6
7 8 9
Please note that this is what I read somewhere else when searching for my solution to the original problem (Can't decrypt Pie storage using password from Oreo).
Click to expand...
Click to collapse
This didn't work in my case, the only thing that worked was orangefox

Got problem with encryption in TWRP on brand new Mi Max 3 with Pie. I started with twrp-3.2.3-0-nitrogen, which ask about a pass after instalation. In this thread I found so OrangeFox Recovery should solve problem, but - this recovery is in .zip file to flash from recovery, which I did not have... In desperation I flashed twrp-3.3.1-0-nitrogen, and this
works!!