So I got the 5.12.10 update for the weekly developer ROM and it installed stock recovery over TWRP and unrooted my phone. The first time I rooted I managed to flash TWRP with stock recovery, but it isn't working this time. I've had a lot of trouble trying to install via ADB drivers. Help please?
PytSkee said:
So I got the 5.12.10 update for the weekly developer ROM and it installed stock recovery over TWRP and unrooted my phone. The first time I rooted I managed to flash TWRP with stock recovery, but it isn't working this time. I've had a lot of trouble trying to install via ADB drivers. Help please?
Click to expand...
Click to collapse
Did you rename TWRP to update.zip and put it on the root of the internal storage before flashing? If yes and it still failed, you'll have to give us a bit more info as to why it failed to flash (any error messages f.e.?). Should be fairly trivial to flash TWRP and SuperSU
elaurens said:
Did you rename TWRP to update.zip and put it on the root of the internal storage before flashing? If yes and it still failed, you'll have to give us a bit more info as to why it failed to flash (any error messages f.e.?). Should be fairly trivial to flash TWRP and SuperSU
Click to expand...
Click to collapse
It wasn't too difficult the first time, but the recovery seems to be using some sort of signature on the ROM's. All it tells me is that "Install update.zip failed! update.zip signature verification failed." It is named update.zip on the root of internal storage.
PytSkee said:
It wasn't too difficult the first time, but the recovery seems to be using some sort of signature on the ROM's. All it tells me is that "Install update.zip failed! update.zip signature verification failed." It is named update.zip on the root of internal storage.
Click to expand...
Click to collapse
Hm, from what I've found on the miui forum, you're not the first one having this issue. These are the "possible" solutions I've gathered from a couple of threads.
1) Flash TWRP using fastboot (rename twrpxxxx.zip to recovery.zip and place it in the same folder as the fastboot executable):
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
2) Update your current ROM (stable/developer) to the latest version if that isn't the case yet and try flashing TWRP again trough the update app
3) Flash TWRP using Flashify
1. download flashify app from playstore and give root acces
2. download img of twrp for redmi 2 note and put in your sd card (I prefer sdext root folder)
3. Open flashify, select "recovery image", find the img file you've downloaded
4. confirm flash, wait until it's done
4) Re-download a copy of TWRP or use a different one (like this one for example)
Let me know how it went..
So I tried Flashify and every time I tried to use it, the app froze right before/after selecting the recovery image. I did, however, manage to make the ADB and fastboot methods work on my desktop PC. I have no idea what I did wrong before, maybe the wrong ADB drivers? Anyway, I did get it working, so thank you
PytSkee said:
So I tried Flashify and every time I tried to use it, the app froze right before/after selecting the recovery image. I did, however, manage to make the ADB and fastboot methods work on my desktop PC. I have no idea what I did wrong before, maybe the wrong ADB drivers? Anyway, I did get it working, so thank you
Click to expand...
Click to collapse
Used windroid to do all these: http://en.miui.com/forum.php?mod=viewthread&tid=167882&extra=pag
Sent from my Redmi Note 2 using Tapatalk
timberwolf60 said:
Used windroid to do all these: http://en.miui.com/forum.php?mod=viewthread&tid=167882&extra=pag
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
I remember seeing this right after I ordered my phone. I had totally forgotten about it by the time I got it though, as it was more than a month later But thanks for reminding me, I already have it installed on my home PC!
Related
Really didn't want to make a new thread about this but honestly people just jumped to conclusions without being helpful in my previous thread.
Long story short I'm trying to manually get 4.4.2: http://forum.xda-developers.com/showthread.php?t=2664561
I saw that I needed to get s-off, which requires root. Bootloader was already unlocked and so did everything here: http://forum.xda-developers.com/showthread.php?t=2273376
I installed CWM. It said to install a superuser tool so I installed SuperSU.
"You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead." was the next line. <-- I saw that message. Installed a kernel that he recommended: http://forum.xda-developers.com/showthread.php?t=2255900
After reboot I get SuperSU error: There is no SU binary installed and SuperSU cannot install it. If you just upgraded to Android 4.3, you need to manually re-root- consult the relevant forums for your device etc.
Can anyone help me get the proper SU Binary installed? Not a beginner to rooting as I've had had several previous phones before. Never encountered something as annoying as this.
On 4.3, 3.17.502.3.
I had the same issue when I installed 4.4.2 on my international One.
What I done to root was;
- downloaded SuperSU v1.80 zip from here.
- download SuperSu from the Play Store
- in SuperSU, select the option to install binaries via TWRP/CWM. (If it doesn't reboot to recovery, manually enter recovery)
- flash the supersu v1.80 zip and reboot
- open SuperSu and install the binaries using the normal option.
That then enabled my root. I'd tried quite a few different variations and this was the only method that worked for me.
Sent from my HTC One or Note 3 via XDA Premium 4
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
mch277 said:
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
Click to expand...
Click to collapse
You seem very confused about the whole rooting process ... what was the point in flashing the stock recovery ? Are you trying to install the OTAPkg.zip ?
what Rom are you wanting to install and whats flashing stock recovery have to do with it ?
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
mch277 said:
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
Click to expand...
Click to collapse
I wrote the thread you linked too
http://forum.xda-developers.com/showthread.php?t=2659374
and yes it is necessary to have stock recovery to take an OTA, but your post didn't mention taking OTA it said you had no SU installed.
to get into stock recovery
boot to bootloader
choose recovery
wait for black screen, hold vol up and then power
you will see something about sdcard fail .. ignore it till the menu comes up
then choose to flash OTAPkg.zip from sdcard
Has anyone got any pointers on how to get out of recovery on the oneplus x. The phone 'was' rooted, but I unrooted to allow the update. However it failed and now just boots inot recovery.
I have wiped data and cache, formatted device, but no luck in getting the phone to boot. It hasn't had a custom rom or recovery.
How do I go about flashing the latest update manually?
I'm able to get into fastboot mode, should I update the recovery to stock? This seems a little weird as I haven't replaced the stock rom, but I was wondering if this might help.
veearrsix said:
I'm able to get into fastboot mode, should I update the recovery to stock? This seems a little weird as I haven't replaced the stock rom, but I was wondering if this might help.
Click to expand...
Click to collapse
If you have stock recovery, just download the full OS and install it. However, you will need to have a computer and a way to save the ROM onto the micro SD card.
Full ROM 2.1.3
http://forum.xda-developers.com/showthread.php?t=3244996
If you can't do that and you have an unlock bootloader. You can flash twrp, then adb sideload the ROM onto the phone. Then re-flash stock recovery again and install the ROM.
You can flash OTA from twrp, follow this thread.
http://forum.xda-developers.com/showthread.php?t=3245185
Sent from my ONE E1005 using Tapatalk
So,
I have added OnePlusOxygen_14_OTA_004_all_201511031712.zip to an sd card. Booted into recovery with the sd card installed, select 'Install from local' and nothing happens.
Am I missing something?
Also, I am unable to unlock the bootloader as the enable oem unlock wasn't set and I'm now unable to boot into the system to set it.
Also, Im pretty sure usb debugging wasn't enabled either.
Did you manage to fix your phone? I had a similar issue, what I did was;
Load the full ROM into the root of my internal storage (not SD card)
Boot into stock recovery
Install from local - this should list the ROM
Select the ROM and follow the instructions.
How do you load the ROM onto the internal storage? I am not able to adb push in sideload mode and adb sideload doesn't work.
So I've tried to follow both of the methods listed here, but I've had no luck.
Trying the sd card route I am not offered the option to install from sd card, I only get 'Install from local' and 'Install from USB'.
When I try to 'Install from USB' I receive the error:
error: protocol fault (no status)
And the message on the phone says installation failed.
Do I have any other options?
I have the same problem
veearrsix said:
Has anyone got any pointers on how to get out of recovery on the oneplus x. The phone 'was' rooted, but I unrooted to allow the update. However it failed and now just boots inot recovery.
I have wiped data and cache, formatted device, but no luck in getting the phone to boot. It hasn't had a custom rom or recovery.
How do I go about flashing the latest update manually?
Click to expand...
Click to collapse
i have got the same problem. Did you solved it ?
No,
I ended up returning the phone to oneplus. They sorted it (or gave me another one).
veearrsix said:
So I've tried to follow both of the methods listed here, but I've had no luck.
Trying the sd card route I am not offered the option to install from sd card, I only get 'Install from local' and 'Install from USB'.
When I try to 'Install from USB' I receive the error:
error: protocol fault (no status)
And the message on the phone says installation failed.
Do I have any other options?
Click to expand...
Click to collapse
Did you fix your phone yet
veearrsix said:
Has anyone got any pointers on how to get out of recovery on the oneplus x. The phone 'was' rooted, but I unrooted to allow the update. However it failed and now just boots inot recovery.
I have wiped data and cache, formatted device, but no luck in getting the phone to boot. It hasn't had a custom rom or recovery.
How do I go about flashing the latest update manually?
Click to expand...
Click to collapse
i had a similar issue. i installed twrp and backed up my rom. restored rom to get ota but it failed everytime i tried. tried to flash stock recovery but locked the bootloader before flashing stock recovery using fastboot oem lock command and the stock recovery installation failed everytime as the bootloader was locked. tried fastboot oem unlock with status success but while checking always show me bootloader lock status true. The bootloader won't unlock unless you have a stock recovery. installed cm13 using twrp, copied stock recovery and oxygen os zip 2.2.0 downloaded from oneplus website to internal memory, flashed stock recovery using twrp and flashed stock rom using stock recovery.
completed 2.2.1 ota and it worked.
How to flash stock recovery using twrp recovery... Please send me link
Thanks in advance
veearrsix said:
Has anyone got any pointers on how to get out of recovery on the oneplus x. The phone 'was' rooted, but I unrooted to allow the update. However it failed and now just boots inot recovery.
I have wiped data and cache, formatted device, but no luck in getting the phone to boot. It hasn't had a custom rom or recovery.
How do I go about flashing the latest update manually?
Click to expand...
Click to collapse
Just download this file http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_2.2.3/ and paste it into the sd card as it is dont extract and do not paste that file into any folders. Select install from local then select sd card, you will see this file first on the list select it after getting success just reboot it!
Done Enjoy!
no solutions yet? i have the same problem as well.
debbensakye said:
no solutions yet? i have the same problem as well.
Click to expand...
Click to collapse
Of course there are solutions, but explain where you are exactly.
Or you can use the Mega Unbrick Guide
Hi to all. I'm new in Honor world and I've stopped my Android experience with KitKat so I'm a little bit confused ...
I've read several guides (on XDA too) that that three steps to obtain root are unlock bootloader, flash TWRP via ADB and then install Magisk or SuperSU via TWRP. But in the thread on TWRP is clearly written that to install Magisk decryption is needed and to have decryption we must flash a kernel with encryption disabled in fstab. But no guide says anything about this step. Can someone explain me how encryption/decryption work doing a standard installation of TWRP ? Is needed a flash of a modified kernel ? And where find it ?
And another question (if it's not too much ). Since I don't need to install custom rom (I want root only to use some apps like Titanium) how can I make a backup of stock rom, boot.img, efs partition and all that can be useful to restore phone to the starting point if, by chance, I need Huawei warranty ?
Thanks a lot
Hi, apparently there's a way to get root on an encrypted system. Follow the rebrand guide and then flash supersu in TWRP via ADB sideload. It worked for me and a few others, there is no comment from the developers as of right now.
So basically in short follow this guide until you are finished with the TWRP section:
https://forum.xda-developers.com/honor-9/how-to/one-guide-recovery-os-roms-t3661829
Then
- enter twrp
- adb sideload supersu
Afterwards follow the "rooting!" section with point 2
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
unvisigoth said:
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
Click to expand...
Click to collapse
The method is also working fine with Magisk. Let me know if you need help
zxz0O0 said:
The method is also working fine with Magisk. Let me know if you need help
Click to expand...
Click to collapse
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
unvisigoth said:
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
Click to expand...
Click to collapse
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
shiboby said:
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
Click to expand...
Click to collapse
Here what I have done:
Unlock bootloader
install adb drivers (find something that is right for your PC. For example minimal ADB found on XDA weren't suitable for me. Google adb drivers...). Open a command windows (shift+right click). If typing "adb devices" your phone is found that's ok
Enable usb debugging and oem unlock (or in other words disable FRP, factory reset protection)
Put the phone in fastboot mode ("adb reboot bootloader"). If all ok typing "fastboot devices" your phone is found
Type "fastboot oem unlock xxxxxxxx" (xxxxxxxx is the code provided by Huawey)
Bootloader unlocked
Flash TWRP
Download TWRP recovery for Honor 9 (link found on other thread on this forum)
Put the phone in fastboot mode
Type "fastboot flash recovery xxxxx.img" (where xxxx.img is the recovery downloaded)
Reboot phone directly in Recovery to avoid erecovery overwrite TWRP. Booting on TWRP let TWRP patch to avoid erecovery booting
Now here I've had some issues as said (read previous post). My tip is the following:
after rebooting in TWRP make all wipes then reboot again in TWRP
Install Magisk.zip (for me download here https://geekaxe.com/root-honor-9-twrp-bootloader-unlocking/)
Reboot recovery
All wipes
Reboot to system
If it's all OK you can install magisk.apk and you are rooted
I suggest after flashing TWRP to make backup of all partitions on external SD (for some reasons, maybe encryption, backup on internal storage gives error). Again I suggest to copy all files that you need (i.e. magisk files) on external sd before starting all.
Pay attention that if you update firmware after this procedure I think that you must repeat all. For me I remain on original firmware found on phone (B100). B130 seems to have some bugs, B120 doesn't seem improve much. Moreover all releases are 7.0 based. I wait for Oreo, hopefully in some custom rom!
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Zuzler said:
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Click to expand...
Click to collapse
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
unvisigoth said:
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
Click to expand...
Click to collapse
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
adriansticoid said:
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
Click to expand...
Click to collapse
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Observe and be careful man.
Sent from my Honor 8 Pro using XDA Labs
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Which TWRP version did you use?
I had a similar problem after formatting all data with the OpenKirin TWRP 3.1.1 Perhaps its an issue with this TWRP release?
I was able to recover in similar circumstances by flashing a stock boot.img over fastboot. Based on this, it's looking like Magisk is really the way to go for rooting atm. Making sure to pull my twrp backup with adb this time though.
If I'm lucky enough to install magisk and not get a bootloop the safetynet always fails. Anyone got a valid method of actually getting magisk working fully?
I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
I do everything step by step, but every time after rebooting to recovery there is not TWRP but only stock recovery. I have unlocked bootloader. The device is active using the "fastboot devices" command. USB debugging mode is ON. Please help me solve this problem
install Magisk then official twrp app and flash twrp from the app to recovery
PanRyba said:
I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
I do everything step by step, but every time after rebooting to recovery there is not TWRP but only stock recovery. I have unlocked bootloader. The device is active using the "fastboot devices" command. USB debugging mode is ON. Please help me solve this problem
Click to expand...
Click to collapse
The only way it worked for me was to install official twrp app, and flash twrp-3.3.1-0-Armor_6.img from the app to recovery, then click on reboot to rrcovery also in the app.
Twrp will only be available one time after the reboot (so it is not really flashed)
(Adb flash recovery doesn't work for me)
In order to use official twrp app, i rooted with magisk
U welcome
I'm confused now. How did you root with magisk without TWRP. The Magisk installation was basically the only reason for me to flash TWRP
PanRyba said:
I'm confused now. How did you root with magisk without TWRP. The Magisk installation was basically the only reason for me to flash TWRP
Click to expand...
Click to collapse
Same as twrp
Install magisk app and do it from there:
Go to github website and download MagiskManager-v7.3.4.apk
https://github.com/topjohnwu/Magisk/releases
From the apk you will be able to flash your boot partition with magisk (it will save a boot image flashed with magisk on your phone)
The second step is simply to transfer that .img on your computer, install platform tools (in order to use adb command line)
Launch cmd.exe in platform tools folder
Connect your phone to computer via a usb cable and usb debug enabled
Type the command "adb devices" to check if your device is recognised (if a window appear on your phone to enable connection click ok)
Then type "adb reboot bootloader" (you are now in fastboot mode)
Then type "fastboot flash boot (then the name of your flashed with magisk boot image.img that you previously put in platforms tool folder in order to not search for the path)"
Then type "fastboot reboot"
Then from magisk manager app update magisk
That's it
No need for a recovery in the first place to root with magisk
finally works. thanks you dude. I really appreciate your help
PanRyba said:
finally works. thanks you dude. I really appreciate your help
Click to expand...
Click to collapse
You're welcome
Glad to help
PanRyba said:
I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
Click to expand...
Click to collapse
I also used that guide and couldn't get TWRP or Magisk to install on my new Armor 6E. I was able to use "Method 2" and SP Tool to flash TWRP 3.3.1-0, then I was able to flash Magisk using TWRP recovery.
I flashed Magisk-v20. 0(20000).zip
MD5 checksum: 56f82549e9f3c659a11f1f459e56489f
Now I seem to be stuck with the "Orange State" message at boot.
When I attempt to use TWRP to flash "no-verity-opt-encrypt-6.0.zip" I get the following :
-----
Installing zip file '[file path]'
Checking for Digest file...
Verifying zip signature...
Zip signature verified successfully.
##dm-verity and forced encryption disabler by jcadduono version 6.0##
Unpacking the installer...
Updater process ended with ERROR: 1
Error installing zip file' no-verity-opt-encrypt-6.0.zip'
Updating partition details...
... done
-----
The file has this MD5 checksum:
caea927e96c755f3568e85dbded88923
When I attempt to use TWRP to flash "orange_state_disabler_MTK Only.zip" I get the following:
-----
Installing zip file '[pathname]'
Checking for Digest file...
Verifying zip signature...
Zip signature verification failed!
Error installing zip file 'orange_state_disabler_MTK Only.zip'
Updating partition details...
... done
-----
That file has this MD5 hash:
30b01bb314d26643b6cc1dfce1d81cf5
I get nearly the same result when I attempt to install "ROMProvider.COM_orange_state_disabler 0.3.zip"
(Zip signature verification failed!)
That file also has the same MD5 hash:
30b01bb314d26643b6cc1dfce1d81cf5
TWRP asks for a password when I first boot into recovery. I also tried to contact them at the unofficialtwrp.com website (where I downloaded the zip files), but their contact page seems to loop back on itself.
Has anyone else run into this (and stuck with Orange State warning at boot)?
ndt44 said:
Now I seem to be stuck with the "Orange State" message at boot.
Click to expand...
Click to collapse
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
This was my output:
-------------------------------
Installing zip file '[pathname]'
Checking for Digest file...
--- 'Orange State' disabler v0.3 - - -
##### Created by XopmoH97 #####
Current zip - > 'ROMProvider.COM_orange_state_disabler_v0.3.zip'.
Unzipping binaries to '/tmp'...
Success!
Set execute flag to 'tmp/sed-arm'.
Set execute flag to 'tmp/xxd-arm'.
Checking CPU architecture...
CPU architecture 'arm64-v8a' is supported!
Searching 'lk' block in GPT...
Success! 'lk' block = '/dev/block/mmcblk0p27'
Saving '/dev/block/mmcblk0p27' to '/tmp/lk.img'...
Testing NEW algorithm...
NEW algorithm is available!!!
Patching '/tmp/lk.img'...
Success!
Writing '/tmp/lk.img' to '/dev/block/mmcblk0p27'...
Success!!! Please reboot your device!
Updating partition details...
... done
-----------
Unfortunately, the no-verity.ZIP still will not flash!
ndt44 said:
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
This was my output:
-------------------------------
Installing zip file '[pathname]'
Checking for Digest file...
--- 'Orange State' disabler v0.3 - - -
##### Created by XopmoH97 #####
Current zip - > 'ROMProvider.COM_orange_state_disabler_v0.3.zip'.
Unzipping binaries to '/tmp'...
Success!
Set execute flag to 'tmp/sed-arm'.
Set execute flag to 'tmp/xxd-arm'.
Checking CPU architecture...
CPU architecture 'arm64-v8a' is supported!
Searching 'lk' block in GPT...
Success! 'lk' block = '/dev/block/mmcblk0p27'
Saving '/dev/block/mmcblk0p27' to '/tmp/lk.img'...
Testing NEW algorithm...
NEW algorithm is available!!!
Patching '/tmp/lk.img'...
Success!
Writing '/tmp/lk.img' to '/dev/block/mmcblk0p27'...
Success!!! Please reboot your device!
Updating partition details...
... done
-----------
Unfortunately, the no-verity.ZIP still will not flash!
Click to expand...
Click to collapse
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Pergmen said:
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Click to expand...
Click to collapse
mvyrmnd said:
The 6 and 6E are very similar devices. The TWRP listed here works on the 6E. Magisk also works as described.
I cannot confirm for the 6 (but is likely), but the 6E works with all phh-based GSI ROMs.
These phones use A/B images.
Click to expand...
Click to collapse
Can't post links even when quoting so you just have to google "treble project github"
I have gotten roms to work (use A/B even if treble check says its only A for somereason).
I wasn't able to get liniageOS to work (from the pie roms, i think everyting else seems to work) and android Q ones even thou it should be able to from what i have gathered.
IMPORTANT! It seems like every rom is missing basic features like gestures, i dont know if it has to do with the kernel maybe? Im nubie.
VERY IMPOTANT!! Lost my IMEI number from messing around with the phone so be careful! Im not responsible.
Pergmen said:
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Click to expand...
Click to collapse
Would it be possible to get an MD5 checksum and filename which worked for you so that I might compare them? Did you get that file from the unofficial twrp page linked above then? Also were the "system and data EXT4 partitions" on the phone Internal Storage or the USB OTG?
ndt44 said:
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
Click to expand...
Click to collapse
I obtained this file here:
https://www.google.com/amp/s/rompro...ange-state-fixer-fix-orange-state/amp/?espv=1
I just ordered this armor 6e phone. I will be able to answer my own question next week, I suppose. Bit, in the armor 6 thread it is mentioned few times that there twrp works on 6e, now I found this thread, which says twrp will not stay flashed to phone.
Which one is correct?
If the armor 6 twrp does work, does it work to flash gapps? Because the y is not pie, and as such is not system-as-root, which from other devices, I know that makes recovery see the phone file structure different
Ie : /system_root/system not just /system
This difference needs different build of twrp.
I will give it a try when I receive it I suppose.
mrmazak said:
I just ordered this armor 6e phone. I will be able to answer my own question next week, I suppose. Bit, in the armor 6 thread it is mentioned few times that there twrp works on 6e, now I found this thread, which says twrp will not stay flashed to phone.
Which one is correct?
If the armor 6 twrp does work, does it work to flash gapps? Because the y is not pie, and as such is not system-as-root, which from other devices, I know that makes recovery see the phone file structure different
Ie : /system_root/system not just /system
This difference needs different build of twrp.
I will give it a try when I receive it I suppose.
Click to expand...
Click to collapse
I have found a TWRP that stays on. And i have seen some that dont stay. Im able to flash gapps with it to my 6e.
poohju said:
I have found a TWRP that stays on. And i have seen some that dont stay. Im able to flash gapps with it to my 6e.
Click to expand...
Click to collapse
Thanks. Do you have links?
mrmazak said:
Thanks. Do you have links?
Click to expand...
Click to collapse
First maybe try out the unofficial TWRP (https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/) maybe it works. I think i didnt get it to stick but its worth a shot ig and you can also try with the TWRP app (havent tried the app way). Sadly i dont remember where i got the file that sticks for me. If unofficial dosent work i can upload it to somewhere. I used ADB tools to download TWRPs. If you use SP tools to flash it while like doing a fresh install. It will go to RED state. You can use SP tools if you first install stock then unlock bootloader and flashing then only installing the recovery. You can install gapps mostly but u cant use dm veryeti disabler it messes with the IMEI at least for me. Im not that savy to know how to fix it. Its my first phone ever messing with. MAGISK works.
poohju said:
First maybe try out the unofficial TWRP (https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/) maybe it works. I think i didnt get it to stick but its worth a shot ig and you can also try with the TWRP app (havent tried the app way). Sadly i dont remember where i got the file that sticks for me. If unofficial dosent work i can upload it to somewhere. I used ADB tools to download TWRPs. If you use SP tools to flash it while like doing a fresh install. It will go to RED state. You can use SP tools if you first install stock then unlock bootloader and flashing then only installing the recovery. You can install gapps mostly but u cant use dm veryeti disabler it messes with the IMEI at least for me. Im not that savy to know how to fix it. Its my first phone ever messing with. MAGISK works.
Click to expand...
Click to collapse
Thanks. I looked at unofficial, and unpacked there image. It is set to terrible enabled = no, and is not setup for system-as-root.
Also the prop file says it is for armor 6 not 6e, so I will just build fresh one and use that.
mrmazak said:
Thanks. I looked at unofficial, and unpacked there image. It is set to terrible enabled = no, and is not setup for system-as-root.
Also the prop file says it is for armor 6 not 6e, so I will just build fresh one and use that.
Click to expand...
Click to collapse
Good luck to you maybe you can share it when your done
poohju said:
Good luck to you maybe you can share it when your done
Click to expand...
Click to collapse
My phone is still not delivered. But I did compile twrp from source, using the September update files from ulefone site.
I started with the device tree from the armor 6, and made few changes that I have found to work for treble devices and system as root on other recent mtk phones I have.
But I can't confirm the build works. If you want to beta test it, let me know.
The TWRP for the HD1910 works perfectly on the HD1925. Decryption works too. Install TWRP by using the installer.
Exact the img from the installer zip.
Boot to fastboot
Open a CMD within the extracted TWRP installer folder and type in
"fastboot boot recovery.img"
Once TWRP boots, then install the TWRP installer zip file.
I flashed magisk and it flashed with no issues. I used the latest version here.
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
dl.twrp.me
NOTE: I did it on the latest version, 11.0.1.18 So I'm not sure if it works on any older versions but I would assume so.
Yep, been out a while now. Works perfectly! However I highly highly recommend not using the twrp installer zip on our phones nor installing it by doing "fastboot flash recovery name_of_twrp.img"
Just download the latest .img and do "fastboot boot name_of_twrp.img" whenever you need to go into twrp recovery. Or you're just asking for trouble with OTA updates definitely no longer working (until you restore the stock recovery that matches the exact version of OOS that you are running) and a good possibility of getting a Qualcomm Crash-dump and losing or breaking all kinds of stuff.
starcms said:
Yep, been out a while now. Works perfectly! However I highly highly recommend not using the twrp installer zip on our phones nor installing it by doing "fastboot flash recovery name_of_twrp.img"
Just download the latest .img and do "fastboot boot name_of_twrp.img" whenever you need to go into twrp recovery. Or you're just asking for trouble with OTA updates definitely no longer working (until you restore the stock recovery that matches the exact version of OOS that you are running) and a good possibility of getting a Qualcomm Crash-dump and losing or breaking all kinds of stuff.
Click to expand...
Click to collapse
I already know about all that. I've had this phone over a year, so I'm familiar with the hidden "secrets".
starcms said:
Yep, been out a while now. Works perfectly! However I highly highly recommend not using the twrp installer zip on our phones nor installing it by doing "fastboot flash recovery name_of_twrp.img"
Just download the latest .img and do "fastboot boot name_of_twrp.img" whenever you need to go into twrp recovery. Or you're just asking for trouble with OTA updates definitely no longer working (until you restore the stock recovery that matches the exact version of OOS that you are running) and a good possibility of getting a Qualcomm Crash-dump and losing or breaking all kinds of stuff.
Click to expand...
Click to collapse
BTW, with unlocked bootloader OTA's are not available no matter what type of recovery you have installed. Unless you have reinstalled the reserve.img after unlocking the bootloader
AntiSocialSingh said:
@BobbyLynn I followed your tutorial to install the CrDroid recovery. Can you tell me how to flash TWRP? Bit of a noob for this phone.
Click to expand...
Click to collapse
Exact (Unzip) the zip folder. Within the extracted folder you'll see some other files. One of them is a recovery.img file. Open a command or PowerShell in the extracted folder. Reboot to fastboot.
Boot to fastboot and run this command
"fastboot boot recovery.img"
Once it boots into TWRP, then click on "install" and locate the TWRP installer zip and select it. It'll most likely be in the download folder. Just make sure you know where the TWRP installer zip is located before you even boot into TWRP
BobbyLynn said:
Exact (Unzip) the zip folder. Within the extracted folder you'll see some other files. One of them is an .img file (recovery). Open a command or PowerShell in the extracted folder. Reboot to fastboot.
Boot to fastboot and run this command
"fastboot boot recovery.img"
Once it boots into TWRP, then click on "install" and locate the TWRP installer zip and select it. It'll most likely be in the download folder. Just make sure you know where the TWRP installer zip is located before you even boot into TWRP
Click to expand...
Click to collapse
BTW download this TWRP from the link in my thread "twrp-installer-3.6.1_11-0-hotdog.zip"
AntiSocialSingh said:
@BobbyLynn Do i need to flash both a & b like i did in the case of crDroid?
Click to expand...
Click to collapse
Not at all. The installer will take care of all that once you boot into TWRP
AntiSocialSingh said:
@BobbyLynn Should I take a backup? Would it wipe my storage? or it would be as it is?
Click to expand...
Click to collapse
No it won't wipe data or anything else. But it's always good to have a backup just in case anything goes sour.
AntiSocialSingh said:
@BobbyLynn I am on the screen which says Install, Wipe, Backup, restore...... what should i do to install the zip file now?
Click to expand...
Click to collapse
Just click on "install" then located the installer zip file then select it and install it
AntiSocialSingh said:
I copied the .zip file on my phone but cannot navigate to it since all it shows is (Up A level), does not show the directories inside the storage
Click to expand...
Click to collapse
Select up a level then scroll down until you see a file called "storage" that'll take you to your storage. If it doesn't, the go back and click on "sdcard" But I'm almost certain it's in the storage folder
AntiSocialSingh said:
I think i need to flash it once via TWRP, i'll try it later, but thank you, it means that this TWRP works!
Click to expand...
Click to collapse
I just checked..... The "sdcard" folder is the one that takes you to the internal storage where the download folder is located. But as soon as you hit 'install" it should've taken you straight to the internal storage. If it didn't, then it sounds like it's still encrypted. If that's the case, then remove any screen locks on your phone before flashing TWRP
AntiSocialSingh said:
@BobbyLynn Let me try once again with the screen lock removed.
Click to expand...
Click to collapse
When I installed TWRP I didn't have a screen lock. But after installing TWRP I set a screen lock and TWRP decrypted just fine. So I'm guessing if you install TWRP while you have a screen lock it doesn't install properly so it can't decrypt. It appears that any screen locks must be removed before installing and after installing reapply a screen lock
AntiSocialSingh said:
@BobbyLynn It worked! So basically, I had to remove both fingerprint and pattern locks to get it to work. Thanks a ton!!
Click to expand...
Click to collapse
No problem
BobbyLynn said:
No problem
Click to expand...
Click to collapse
I'm kinda curious, why did you install TWRP? Are you fixing to "test drive" some custom ROM's or flash some mods? Or did you install TWRP just for the hell of it?
AntiSocialSingh said:
@BobbyLynn The latter yes, test driving some mods, and I am used to the interface of TWRP, not crDroid much, personal preference hahahaha....Thank you so much once again. you're a legend.
Click to expand...
Click to collapse
I'm more use to TWRP myself. I started using TWRP about 10 years ago, it was and still is the best recovery out there. I just happened to install crDroid the other day just to test something. And that test turned out to be a great discovery of a simple way to root the stock firmware. Since I have a extra McLaren, I do quite a bit of testing and modding and experimental stuff. I'm currently working on installing the global firmware (unbranding) it. No luck yet, but I might be getting close.
AntiSocialSingh said:
@BobbyLynn I will be the first one to follow your tutorial if you manage to flash the Global ROM on it sir. I promise haha!
Click to expand...
Click to collapse
You can bet your ass that if I pull off that trick it'll get LOT'S of comments from people thanking me lol. We've been wanting to install the global firmware on this phone, but nobody can figure out how to mod the ROM to make it flash on this phone. There's some very smart developers that own this phone, so I'm surprised that none of them have figured it out yet. So I've been tinkering around with trying to install it. It's looking like I'm going to have to make some modifications to the global ROM and/or the phone too to make the MSM tool see the phone as a comparable device
BobbyLynn said:
BTW, with unlocked bootloader OTA's are not available no matter what type of recovery you have installed. Unless you have reinstalled the reserve.img after unlocking the bootloader
Click to expand...
Click to collapse
Well, yeah, restoring reserve.img is a prerequisite to get OTAs with the bootloader unlocked, but it only has to be done once. After that, for each ota, just restore the boot image to stock (uninstall magisk) and you're good to go
starcms said:
Well, yeah, restoring reserve.img is a prerequisite to get OTAs with the bootloader unlocked, but it only has to be done once. After that, for each ota, just restore the boot image to stock (uninstall magisk) and you're good to go
Click to expand...
Click to collapse
I wanted to do OTA how should I restore my reserve.img?