Related
So either I suck or I literally have the process wrong, but I was trying to install 6.0.1 last night for 2 hours. Originally I had 6.0 installed rooted, twrp, etc. OTA didnt work because I'm guessing twrp was installed as it errored out. So I decided to take WUG downloaded the binaries/newest stuff and decided to just manually flash 6.0.1. However at the same time I wanted to use the decrypter tool here.
My process was/is:
Flash Stock/Unroot button in WUG (with newest 6.0.1 already downloaded
Root button and flash customer recovery button/checkbox
Flash the perm recovery zip, supersu, and busybox
Flash the decrypter zip
Wipe data/cache/system/davik/etc and then freshly reboot
The problem is, it just hangs on the animation screen and never loads. I've tried it twice now, and its driving me insane. Where could I have went wrong? What is flawed about my process or maybe I'm using the wrong stuff. Thank you in advance guys!
chugger93 said:
So either I suck or I literally have the process wrong, but I was trying to install 6.0.1 last night for 2 hours. Originally I had 6.0 installed rooted, twrp, etc. OTA didnt work because I'm guessing twrp was installed as it errored out. So I decided to take WUG downloaded the binaries/newest stuff and decided to just manually flash 6.0.1. However at the same time I wanted to use the decrypter tool here.
My process was/is:
Flash Stock/Unroot button in WUG (with newest 6.0.1 already downloaded
Root button and flash customer recovery button/checkbox
Flash the perm recovery zip, supersu, and busybox
Flash the decrypter zip
Wipe data/cache/system/davik/etc and then freshly reboot
The problem is, it just hangs on the animation screen and never loads. I've tried it twice now, and its driving me insane. Where could I have went wrong? What is flawed about my process or maybe I'm using the wrong stuff. Thank you in advance guys!
Click to expand...
Click to collapse
I don't think the NRT is updated to properly root on 6.0.1 (Could be wrong).
Get the Latest SuperSU-v2.62-3 and flash that, It will modified the boot.img for you and include no forced encryption.
As long as you remove the encryption of the data partion in twrp from this guide
You shouldn't need the decrypter zip, also if you flash TWRP and boot into it before booting the system, you also won't need perm recovery.
Going by what I have read, still encrypted on my Device.
corkiejp said:
I don't think the NRT is updated to properly root on 6.0.1 (Could be wrong).
Get the Latest SuperSU-v2.62-3 and flash that, It will modified the boot.img for you and include no forced encryption.
As long as you remove the encryption of the data partion in twrp from this guide
You shouldn't need the decrypter zip, also if you flash TWRP and boot into it before booting the system, you also won't need perm recovery.
Going by what I have read, still encrypted on my Device.
Click to expand...
Click to collapse
ok so everytime I flash the supersu, it does its thing, then I format data, the reboot and twrp says supersu is not installed, do you wanna install it now? You can swipe to install or do not install.
Which I dont get becuase clearly I flashed the supersu zip a sec ago. if I continue to just flash it like it says, when I boot up, all I see in my drawer is the "SuperSU Installer" I have no idea what I'm doing wrong. If I dont have twrp install it when it asks, I got nothing in my app drawer
think I may have gotten it, had to download supersu from play store, then reflash, then let twrp flash it when it says it needed too, not I can launch supersu from the app drawer and it works.
Next problem is encryption. Under security it still says "Encrypted" do I need to actually hit the "Format Data' button in twrp? I just did a factory wipe slide.
chugger93 said:
ok so everytime I flash the supersu, it does its thing, then I format data, the reboot and twrp says supersu is not installed, do you wanna install it now? You can swipe to install or do not install.
Which I dont get becuase clearly I flashed the supersu zip a sec ago. if I continue to just flash it like it says, when I boot up, all I see in my drawer is the "SuperSU Installer" I have no idea what I'm doing wrong. If I dont have twrp install it when it asks, I got nothing in my app drawer
Click to expand...
Click to collapse
From the linked SuperSU thread
From the linked SuperSU thread said:
If TWRP offers you to keep /system read-only, indeed keep it read-only.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!
Click to expand...
Click to collapse
This is do with the new systemless root and TWRP needs to be updated to reflect this change.
chugger93 said:
think I may have gotten it, had to download supersu from play store, then reflash, then let twrp flash it when it says it needed too, not I can launch supersu from the app drawer and it works.
Next problem is encryption. Under security it still says "Encrypted" do I need to actually hit the "Format Data' button in twrp? I just did a factory wipe slide.
Click to expand...
Click to collapse
From the linked guide above said:
11.Once in TWRP, hit “cancel” when asked for the password and then erase/wipe data and make sure MTP is enabled (dig around the menus in TWRP, it’s all in there somewhere). This erases the encrypted partition and allows you to use adb to push files to your sdcard.
Click to expand...
Click to collapse
Answers in quoted messages.
Never had to get SuperSU app from the store, maybe because I already had it installed, the app is also in the SuperSU zip.
Hello all. I've been trying to flash Helios rom for my s7 edge but I keep failing. First of all, my device is exynos so it should be good to root. However, when I check TWRP page it says ''This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.''
I've tried flashing TWRP but failed into a bootloop, flashed a stock rom to recover. The rom needs TWRP to be installed and I just can't get it working. Maybe I'm using a wrong version of TWRP, or doing something wrong? Any help is appreciated, thank you.
Edit - I faced ''recovery is not seandroid enforcing'' on my last try. Been trying different rooting files to find anything works. Couldn't find anything yet.
Hi all people,
first of all, I want excuse me for not my perfect English.
I have Honor 9 from few days. And I think to have bricked it.
I have unlocked bootloader correctly.
I have flashed recovery this TWRP recovery with the intention to proceed to root with Magisk or SuperSu. I accidentally and unconsiuosly do factory reset then the phone goes bootloop. (it power off and power on continuously) with the alert "your device has been unlocked and..etc".
Yesterday, reading this thread, I flashed, from fastboot console, boot, recovery and system, the phone resets two/three times then goes to eRecovery where I do a factory reset.
After a factory reset the phone works correctly and seems successfully unbricked. So I re-flash TWRP recovery.
But this morning, during the attempt to install from TWRP one between Magisk or SuperSu (I don't succeed to do it beacuse the phone was crypted and I don't see zip files from TWRP). I have reset the phone but goes bootloop again.
I tried to re-flash boot, recovery, system and cust more (that I don't have flashed yesterday). Now the phone goes eRecovery and ask me to connect to download latest version and recovery, but don't ask me to do a factory reset.
Now I don't know what I can do.
How I can solve this situation? I want only unlock bootloader (done!), install TWRP and have root permission. Now I don't think to change rom.
Something similar happened to me. It seems like the TWRP provided has some issue..... After installing TWRP I had a bootloop problem. I have resolved installing Magisk. It seems that Magisk patchs something. If you can access TWRP try to install Magisk (put the zip file on external sd). In other words: copy magisk zip on sd card - during the bootloop you have the chance to power off phone - Power off - Power on in recovery mode. If you have TWRP correctly installed Honor should go in recovery using TWRP . Install Magisk and see what happens...
unvisigoth said:
Something similar happened to me. It seems like the TWRP provided has some issue..... After installing TWRP I had a bootloop problem. I have resolved installing Magisk. It seems that Magisk patchs something. If you can access TWRP try to install Magisk (put the zip file on external sd). In other words: copy magisk zip on sd card - during the bootloop you have the chance to power off phone - Power off - Power on in recovery mode. If you have TWRP correctly installed Honor should go in recovery using TWRP . Install Magisk and see what happens...
Click to expand...
Click to collapse
I have tried to flash TWRP recovery again to do install Magisk from sd card. I have done it but the phone doesn't work fine.
So I have put rommco05 TWRP Backup into sd card then restored it from TWRP restore (boot and vendor img). Now the phone seems have bootloader locked, in fact I don't have bootloader warning at the power on. Now in fastboot mode the phone says me that I have Phone locked and FRP unlocked.
How can I exit from this situation?
Try this
Killus3 said:
Hi all people,
first of all, I want excuse me for not my perfect English.
I have Honor 9 from few days. And I think to have bricked it.
I have unlocked bootloader correctly.
I have flashed recovery this TWRP recovery with the intention to proceed to root with Magisk or SuperSu. I accidentally and unconsiuosly do factory reset then the phone goes bootloop. (it power off and power on continuously) with the alert "your device has been unlocked and..etc".
Yesterday, reading this thread, I flashed, from fastboot console, boot, recovery and system, the phone resets two/three times then goes to eRecovery where I do a factory reset.
After a factory reset the phone works correctly and seems successfully unbricked. So I re-flash TWRP recovery.
But this morning, during the attempt to install from TWRP one between Magisk or SuperSu (I don't succeed to do it beacuse the phone was crypted and I don't see zip files from TWRP). I have reset the phone but goes bootloop again.
I tried to re-flash boot, recovery, system and cust more (that I don't have flashed yesterday). Now the phone goes eRecovery and ask me to connect to download latest version and recovery, but don't ask me to do a factory reset.
Now I don't know what I can do.
How I can solve this situation? I want only unlock bootloader (done!), install TWRP and have root permission. Now I don't think to change rom.
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-9/help/bootloader-locked-help-to-enable-usb-t3683145
Rommco05 said:
Again unlock bootloader
Click to expand...
Click to collapse
I have unlocked bootloader again and do a factory reset from TWRP recovery, now the phone seems works correctly!!!:good:
Now I should try to root the phone with Magisk or SuperSu, right?
I have a question about TWRP. From TWRP's file manager I don't see the files that I put in the internal memory. It's because I have used finger print to lock the phone that encryptes files?
raw_jay said:
https://forum.xda-developers.com/honor-9/help/bootloader-locked-help-to-enable-usb-t3683145
Click to expand...
Click to collapse
This is to re-brand the phone from Chinese to EU version...I don't think is my case.
Rommco05 said:
Take a backup before make root. You don't see files because is some issue with decryption in TWRP. I achieved root with Magisk but I don't remember exactly steps
Click to expand...
Click to collapse
I think it's too late
Anyway I can re-flash all thing from begin.
Then I can't use TWRP with the phone encrypted ( PIN, password, fingerprint, etc...) ?
Rommco05 said:
I'm not sure about thatz Huawei roms are encrypted somehow by default
Click to expand...
Click to collapse
After I have installed Magisk (v14.0) now I have problem with google play services which don't download and do updates apps.
If I do a factory reset again I can solve it?
Update:
After I done a factory reset from TWRP recovery
and formatting data partition the phone seems working perfectly (I don't know why, but before format data the phone says me that I have only 150mb of memory space)
I say "seems" because there's something getting me in trouble, for example, I don't have anymore ringtones in the settings menu.
And I don't know if I have lost something else.
Exists a possibilty to restore all contents of the phone?
You could try this and flash your phone back to stock. But then you would need to unlock your bootloader and install TWRP again. Another way would be to unpack an image of your ROM and flash system and other parts via fastboot. Of course this could be risky and you could brick the device.
Meranico said:
You could try this and flash your phone back to stock. But then you would need to unlock your bootloader and install TWRP again. Another way would be to unpack an image of your ROM and flash system and other parts via fastboot. Of course this could be risky and you could brick the device.
Click to expand...
Click to collapse
If I understand it well...
I have 2 options:
1) Rebrand the phone and flashin, then at end I have back the phone stock.
2) Unpack the image of ROM (what it means?) and flash system and other parts via fastboot. (Which are those parts? How?) But this procedure is more hazardous then rebrand procedure?
I have understand right?
1. Yes, correct. I would recommend that. Everything is explained in the thread I linked. Of course everything you do could potentially harm your phone, but you should know that already.
2. Get an update.app file for your specific phone model (there are threads already here, just search a bit, or use Firmware Finder), open it with the Huawei Update Extractor and extract the parts you want to flash (like system or recovery). Then flash them via fastboot. I tried this because I was in a situation like yours, but it didn't work for me. But in theory it could, because you would replace the faulty parts of your firmware.
Killus3 said:
I have understand right?
Click to expand...
Click to collapse
Could you solve your problem?
Meranico said:
Could you solve your problem?
Click to expand...
Click to collapse
Hi, I don't say it because I have replaced the phone with another same.
Now I'm starting to unlock bootloader, installing recovery TWRP and rooting the phone.
I hope to avoid bootloop this time.
Goodmorning everyone!
Yesterday I have:
- Unlocked bootloader correctly!
- Installed TWRP correctly!
- Make a TWRP Backup of all partitions of the device, except data partition because TWRP gives me an error during backup attempt.
- Then I start the device.
- After start the device I go to recovery TWRP to install Magisk, but the phone goes bootloop.
After reboot 2-3 times on the screen appears for a few moments a message of eRecovery that have restored something but I don't know. Then the device shows me the eRecovery that asks me to make a factory reset.
At this point I shutdown the device, go in TWRP to flash Magisk unistaller and the device goes out bootloop and works fine but without root.
How I can solve this problem and install Magisk and have root finally?
Some question:
-When I flashed TWRP (via fastboot) and I configurate it, example language, hours, etc... TWRP don't save the settings, in fact when I go in TWRP again I do remake the settings. Why?
-Then I go in sdcard I don't navigate files, I see folders with casual characters. This is an effect of encryption of the device?
Killus3 said:
Goodmorning everyone!
Yesterday I have:
- Unlocked bootloader correctly!
- Installed TWRP correctly!
- Make a TWRP Backup of all partitions of the device, except data partition because TWRP gives me an error during backup attempt.
- Then I start the device.
- After start the device I go to recovery TWRP to install Magisk, but the phone goes bootloop.
After reboot 2-3 times on the screen appears for a few moments a message of eRecovery that have restored something but I don't know. Then the device shows me the eRecovery that asks me to make a factory reset.
At this point I shutdown the device, go in TWRP to flash Magisk unistaller and the device goes out bootloop and works fine but without root.
How I can solve this problem and install Magisk and have root finally?
Some question:
-When I flashed TWRP (via fastboot) and I configurate it, example language, hours, etc... TWRP don't save the settings, in fact when I go in TWRP again I do remake the settings. Why?
-Then I go in sdcard I don't navigate files, I see folders with casual characters. This is an effect of encryption of the device?
Click to expand...
Click to collapse
Answers to all your concerns go here mate---> TWRP doesn't decrypt data. Done.
Hence: weird folders in there, nowhere to store its settings prefs, about Magisk it's another story, if you want root go SuperSU latest beta.
Regards.
a basically did what that guy did, got root installed via TWRP but my google apps are all busted.
I tried flashing the update_data_full_public.zip and update_full_hw_usa.zip I found using the russian device lookup link switching trick but I the HW errored when I tried to flash it in TWRP and my play store still broken.
Hey I just picked up this phone and decided I would like to maximize it to its fullest potential, and root it as I have done with previous phones. This ones giving me a hard time, and I just can't seem to find the proper info for it.
I have unlocked the bootloader, flashed TWRP 3.1.1 and want to gain root access. I have followed several guides, used every possible one-click unsuccessfully, and tried installing SuperSU with TWRP. After I reboot, SuperSU is installed. I'll open it up and it tells me the binaries are occupied. I've tried downgrading and updating the binaries but I get errors. (I believe this is because it must be rooted first - of course.)
So I'm stuck unable to get any further. If anyone has any suggestions, I would appreciate it. Is this phone with this configuration unrootable? There must be a way if I have recovery right?
Asus Zenfone 4 Z01KD/ZE554KL
Android Nougat 7.1.1 - 14.1060.1708.63 (NOT 1708.70)
TWRP 3.1.1 installed
One thing I have not tried is using Magisk. When I try it, it stops because I already patched with SuperSU (even though it failed). I never backed up before I did it with SuperSU I really thought it would work.
I read of people doing it with Magisk after updating to Oreo. I want to give that a try but I can't OTA or flash from TWRP. All attempts result in error 7.
I can't find a stock recovery to flash to do the update either. Is there a way to undo this, OTA and repatch with Magisk? Even if I don't bother updating, I would like to find a stock image to flash so I can try patching with Magisk.
Stock rom recovery.img anywhere? Am I alone?
i dont own this device but i read this and it might apply to you. also did you flash the supersu uninstaller and them try magisk?
https://forum.xda-developers.com/zenfone-4-2017/development/twrp-3-1-zenfone-4-2017-ze554kl-t3690349
hey i have the zenfone 4 ze554kl i updated it to android 9 unlocked the bootloader and got Twrp running but not correctly and i can't root the phone .....
I'm having major problems with TWRP, and I need help.
I have a Samsung Galaxy S4 with a properly unlocked bootloader (MDL), rooted, that has had a working version of TWRP 2.8.7.0 and running an older version of Cyanogen.
I'm overhauling the phone, so the first thing I tried to do was to update TWRP.
Since TWRP v2.8.7 supports flashing itself, I booted into recovery and flashed the TWRP update (v3.2.1.0) directly through TWRP. No errors that I saw.
But when I try to boot into recovery, I now get "System Software Not Authorized By AT&T Has Been Found On Your Phone". Fortunately, I can still boot normally - it's only recovery that I'm locked out of.
In trying to fix this, I tried re-flashing TWRP with three different methods:
1. I tried to flash TWRP again through the TWRP app. But I get "Flash Failed".
2. I tried Odin and got "FAIL! (Auth)"
3. I tried flashing v3.2.2.0 using the dd method. This I was able to do without any errors, but I'm still locked out of recovery mode with that same "System Software Not Authorized By AT&T Has Been Found On Your Phone" error.
Help?
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
HippoInWindow said:
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
Click to expand...
Click to collapse
ADB works fine for me, but fastboot does not. It says "waiting for any device". From what I understand, this is a common issue with Samsung phones. I'm using Windows 10, if that helps.
However, I came across a bug report for TWRP here, that reports the exact same problem from 3.0.0.0, and it's still open. That tells me that this may be a general issue with TWRP that they never bothered to fix.
So on a hunch, I tried re-flashing v2.8.7 using the dd method (since that's the only one I can get to work). And SUCCESS! I can now boot into recovery again!
So here's what I need to know:
1. Is there any way to get the latest version of TWRP to work on this phone?
2. Is it safe to flash a current version of LineageOS using this version of TWRP (v2.8.7)?
I'm really wary about that second question, because the last thing I want to do is brick my phone because an old version of TWRP doesn't know how to work with a new version of Lineage/Android. (This phone currently has KitKat on it)
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
HippoInWindow said:
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
Click to expand...
Click to collapse
I finally found an explanation and solution - it would appear that TWRP 3.x does not have the Loki exploit applied. So nothing 3.0+ will work unless it's been Lokied.
Fortunately, the current versions can be Loki patched, so once that's done, they'll install and work properly. Whew!