Since there's no thread about it yet (in here then), I'll just make this one so that there won't be any more confusion for TWRP links.
Do keep in mind that if you use the official bootloader unlock method, you won't receive OTA updates anymore from Asus.
Have a great day and happy flashing
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
I'm using more current Twrp and magisk 16 I do not know which is preventing the biometric reader
rinampa said:
I'm using more current Twrp and magisk 16 I do not know which is preventing the biometric reader
Click to expand...
Click to collapse
At the time, I do not know either what is causing this. Because the Oreo rom is rather bugged a bit. (Lower audio, wifi not turning on once it's off and now this)
What twrp should i use for nougat version?
HnsAlczr said:
What twrp should i use for nougat version?
Click to expand...
Click to collapse
Since it's nougat, preferably use 20180304. Once on Oreo, you can flash the latest.
+)KEV1N(+ said:
Since it's nougat, preferably use 20180304. Once on Oreo, you can flash the latest.
Click to expand...
Click to collapse
After i flash twrp thru adb reboot it on twrp works properly but when i reboot to system im stuck at Asus Logo, did i do something wrong on the process?
HnsAlczr said:
After i flash twrp thru adb reboot it on twrp works properly but when i reboot to system im stuck at Asus Logo, did i do something wrong on the process?
Click to expand...
Click to collapse
Did you upgrade your system to Oreo? If so, did you have substratum themes on?
I wonder when he opens the twrp he asks for the PIN number , password or something?
How do I unlock the ZenFone 3 Zoom bootloader on Android Oreo ?
ZueiraBR said:
How do I unlock the ZenFone 3 Zoom bootloader on Android Oreo ?
Click to expand...
Click to collapse
https://www.asus.com/br/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_Download/,Select the android operating system, Versão UnlockTool_2018_0629(android O)
2018/06/29740.7 KBytes.
Read the instructions carefully.
+)KEV1N(+ said:
Since there's no thread about it yet (in here then), I'll just make this one so that there won't be any more confusion for TWRP links.
Do keep in mind that if you use the official bootloader unlock method, you won't receive OTA updates anymore from Asus.
Have a great day and happy flashing
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Hi all, does not work with WW-80.30.76.10 . Help me please
personal I flashed the twrp by adb fastboot soon then I entered i REBOOTED-SYSTEM by own twrp! but when I turned it off and put it in recouvery mode (twrp) it goes into the original factory recovery! Does anyone know the solution ??
Delaias1995 said:
personal I flashed the twrp by adb fastboot soon then I entered i REBOOTED-SYSTEM by own twrp! but when I turned it off and put it in recouvery mode (twrp) it goes into the original factory recovery! Does anyone know the solution ??
Click to expand...
Click to collapse
Installed twrp by fastboot goes into recovery in twrp restart the always by twrp.
After updating to twrp new version I can not update more firmware, I have to download recovery stock
I am having problems in twrp I can not install rom always error 7 in this last update how to solve?
Please, I appreciate your help.
+)KEV1N(+ said:
Since there's no thread about it yet (in here then), I'll just make this one so that there won't be any more confusion for TWRP links.
Do keep in mind that if you use the official bootloader unlock method, you won't receive OTA updates anymore from Asus.
Have a great day and happy flashing
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Is there any UN-OFFICIAL unlock method ? tks
Can someone help me? I can't find the correct version (or doesn't even exist) of twrp for my zenfone zoom s.
(UL-Z01H-WW-80.30.76.74)
Related
Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
undesputed said:
Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
Click to expand...
Click to collapse
Reinstallt it try this TWRP http://www.mediafire.com/download/15g5i63gke9ddgp/kiwi_twrp_3-21_recovery.img its version 3.0.2.0 (Most recent)
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
mooms said:
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
Click to expand...
Click to collapse
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Arobase40 said:
Do you mean 3.0.2.0 is newer and supports more partitions than 5-14 ???
Click to expand...
Click to collapse
Their both 3.0.2.0 the one I just posted has more features
Sent from my SM-N920T using Tapatalk
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
@clsA
frp is labeled as "UNLOCK" as oppsed to bootloader labeled as "UNLOCKED".
If it's just about removing my google account, will this be resolved the next time I do a factory reset?
Nevertheless, thank you so much for the command fastboot boot twrp.img, I realized that that was what I had used the last time.
I'm currently able to boot into TWRP this way. Awesome!
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
mooms said:
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
Click to expand...
Click to collapse
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
clsA said:
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
Click to expand...
Click to collapse
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
mooms said:
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
Click to expand...
Click to collapse
USB-OTG works flawlessly on the 5-14 version I was not able to use it with the newer one @yuweng posted in his guide
the screen shots show all the partitions it's able to work with
Arobase40 said:
I thought 3.0.2.0 was just an interim version between twrp_2-27 and twrp_5-14... ^^
Click to expand...
Click to collapse
your confusing TWRP versions with TWRP release dates
2-27 and 5-14 are release dates where as 3.0.2.0 is the version of TWRP not the date
the first version of TWRP for this device was actually 2.8.7.0 and was released on 2-16-2016
Same issue
Hey so I have the same exact issue umm did you ever resolve this problem becuSe I can't seem to crack it and it's a bit frustrating cuz by no means am I a pro but coming from using the OnePlus one the OnePlus 2 the OnePlus x and the Nexus 6 rooting them and restoring them after many failed attempts resulting in bricking my phone and even eventually unbrick them I do know a thing or two and I am stumped please help you are the only other person in this world other then my self that seems to be having this issue if you don't mind would you be so kind and email gmail me cuz I don't use or check this forum often thanks millerfamily805
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
Can it be used with other honor devices?
Got my answer... Thanks...
Sent from my PLK-L01 using XDA Labs
It depend on the device
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
Hi guys,
Before you say again a topic on a non bricked One Plus X, I would like to let you know that I've checked and try almost all of the tutorial I've seen on xda and one plus forum.
I was on CM14.1 with this ROM : https://forum.xda-developers.com/oneplus-x/orig-development/rom-cyanogenmod-14-onyx-t3452150
Unfortunately, I made the 25-12-2016 update and it totally broke up the phone..
I download the OnePlus X OxygenOS 3.1.4 on the One Plus website. So I flash it on the stock recovery, it tells me "Install success" then I reboot and it stays on the bootlogo.
For information, I can't access the oem unlock menu if needed, but when I ask the oem device info it says unlocked. The phone is detected by the computer sometimes with unknown device and sometimes correctly with the qualcomm drivers..
I have a back up made from TWRP, I can access the device by the fastboot mode, it seems that all the operations written here worked but it doesn't install or even boot on TWRP..
Thanks for your help guys.
Are you using latest TWRP from website think version 3.0.3?
Exodusche said:
Are you using latest TWRP from website think version 3.0.3?
Click to expand...
Click to collapse
I'm not even using TWRP, since I can't boot on it.. But I tried to flash the twrp-3.0.2-2 from blue spark v41, after the installation via Flashboot, it doesn't boot up on the recovery..
So after flashing TWRP you use fastboot boot recovery.img and nothing happens?
Exodusche said:
So after flashing TWRP you use fastboot boot recovery.img and nothing happens?
Click to expand...
Click to collapse
Exactly, the phone is stuck on the one plus logo..
defqon_1 said:
Exactly, the phone is stuck on the one plus logo..
Click to expand...
Click to collapse
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod, worked for me.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Divyesh49 said:
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod, worked for me.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Click to expand...
Click to collapse
Didn't work. I tried to lock and then unlock to be sure but not is stay in false for tempered AND unlocked.
So I don't have any idea on how make android back on my phone.
I just have access to Fastboot mode. No recovery, nothing else..
EDIT : phone is not starting anymore. I try to charge it hoping it just a low battery problem..
You should send it to RMA
Trimis de pe al meu Redmi 3S folosind Tapatalk
Finally, I resolved the problem I don't know how but for the moment I have stock recovery and stock rom ! :laugh:
I will wait for a stable rom for Nougat. Thanks for the help guys !
PS : how do I close or write resolved at the top of the subject ?
Help Pls
defqon_1 said:
Finally, I resolved the problem I don't know how but for the moment I have stock recovery and stock rom ! :laugh:
I will wait for a stable rom for Nougat. Thanks for the help guys !
PS : how do I close or write resolved at the top of the subject ?
Click to expand...
Click to collapse
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
UBCM said:
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
Click to expand...
Click to collapse
Start by seeing if you can fastboot flash stock recovery from any 2.X.X OOS. Then fastboot flash twrp 3.0.2. If your on new bootloader meaning latest ROMs or OOS3 then you need to boot into 3.0.2 and from there you can flash IMG of twrp 3.0.3. Make sure you boot right back into recovery after flashing any twrp or it won't stick. This worked for me when I lost my recovery twice but always remember at your own risk. Not responsible if you make your phone into a paper weight.
Fix It!
Exodusche said:
Start by seeing if you can fastboot flash stock recovery from any 2.X.X OOS. Then fastboot flash twrp 3.0.2. If your on new bootloader meaning latest ROMs or OOS3 then you need to boot into 3.0.2 and from there you can flash IMG of twrp 3.0.3. Make sure you boot right back into recovery after flashing any twrp or it won't stick. This worked for me when I lost my recovery twice but always remember at your own risk. Not responsible if you make your phone into a paper weight.
Click to expand...
Click to collapse
Done! finally i can reinstall stock rom and recovery with drivers by usb.
UBCM said:
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
Click to expand...
Click to collapse
I have tried multiple tools that I find on XDA. I put all the zip files like bootloader update and rom on my sdcard. And by a great night, the OOS 3.1.4 finally booted up ! So I don't have a miracle solutions that can help you..
Done
defqon_1 said:
I have tried multiple tools that I find on XDA. I put all the zip files like bootloader update and rom on my sdcard. And by a great night, the OOS 3.1.4 finally booted up ! So I don't have a miracle solutions that can help you..
Click to expand...
Click to collapse
Don't worry i have restored my OPX 5 days ago. I used the method of this video: https://youtu.be/R4SVSovw4Jo and files from this thread: https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 , if it can help someone.
Unlocking Bootloader1. Make sure you have a sim and active mobile data. Then go to about phone tap build number 7-8 times. After that go to advanced settings > developer options > turn on OEM unlocking and then check if this device is secure and click add account and device.
2. Download Mi unlock tool from here. Extract it and paste it in C:/unlock. or else your device won't be recognized for unlocking.
3. Open Mi unlock tool and then enter the Mi account which was on your device. Put your device in fastboot mode by pressing vol- and power and then connect to PC. Press unlock and if it tells you to wait you have no other option but to wait. If your mi flash tool shows connect your device even after you have connected it. Follow this guide here.
4. After you have unlocked your bootloader reboot your phone.
Flashing TWRP and Rooting via magisk
1. Download this TWRP image here. Thanks to the original developer mauronofrio.
2. Download adb and fastboot tools here and install it.
3. Now put your phone in fastboot mode and connect it with your pc. Now where you have downloaded the TWRP file rename it to TWRP.img and open a CMD window there if you don't know how just google.
4. Type the following commands
1. fastboot devices
2. fastboot flash recovery TWRP.img
3. fastboot reboot recovery.
Click to expand...
Click to collapse
5. Your phone will boot into TWRP now. But TWRP will be overwritten by stock miui recovery to stop that you need to flash Magisk. Download this zip move it to internal storage then flash by tapping on install and swipe to flash. Reboot your device. Reboot to recovery again to check if TWRP is present.
Now your device is rooted
OR
Flash latest OrangeFox Recovery if you don't want magisk.
Flashing A rom
1. Download.
2. Flash.
3 Format Data.
Done
Feel free to ask any questions. And don't point a finger at me for messing your device.
My mi unlock tool says can't get info. I using Indian version miui 12
Thanks for the useful guide. I have a quick question, does this works with MIUI 12?
igeekyayush said:
My mi unlock tool says can't get info. I using Indian version miui 12
Click to expand...
Click to collapse
Sorry for late reply. Have you installed the drivers correctly? Try using another port in your pc or use this mi unlock tool version zip
Doombuggie85 said:
Thanks for the useful guide. I have a quick question, does this works with MIUI 12?
Click to expand...
Click to collapse
Yes, it does.
hello,
thanks for the reply sir. yes i've tired changing port, pc everything. today i've factory reset my phone and added mi account and now i'm getting 7 days wait time. let's see now
LoadOP2 said:
Sorry for late reply. Have you installed the drivers correctly? Try using another port in your pc or use this mi unlock tool version zip
Click to expand...
Click to collapse
igeekyayush said:
hello,
thanks for the reply sir. yes i've tired changing port, pc everything. today i've factory reset my phone and added mi account and now i'm getting 7 days wait time. let's see now
Click to expand...
Click to collapse
Okay keep the sim inserted and use the device for 7 days. And if it doesn't work try using older version of unlock tool.
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
_benedict_ said:
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
Click to expand...
Click to collapse
Flashing a custom rom is optional. You don't NEED to flash a rom to get TWRP...
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
I've unlocked the bootloader using the unlock tool and waited for 7 days,
But i rooted the device using a different method where i patched a boot.img and flashed that to the device.
Will this method still work for me as I'm already rooted but just want TWRP so i can flash other ROMs.. The post says you have to flash magisk from the (temporary) TWRP for the TWRP to stay as the recovery..
Will the magisk on my phone and the magisk installed here collide?
I just want TWRP so i can switch to a custom rom, so any input is appreciated!!
_benedict_ said:
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
Click to expand...
Click to collapse
Skip the flashing a rom part and you will be good to go.
But i rooted the device using a different method where i patched a boot.img and flashed that to the device.
Will this method still work for me as I'm already rooted but just want TWRP so i can flash other ROMs.. The post says you have to flash magisk from the (temporary) TWRP for the TWRP to stay as the recovery..
Will the magisk on my phone and the magisk installed here collide?
I just want TWRP so i can switch to a custom rom, so any input is appreciated!!
Click to expand...
Click to collapse
You can flash twrp and then check if it persists. If not flash magisk again their is no thing as magisk colliding lol. Just make sure you flash a newer version. And if nothing works flash stock rom and then twrp.
If you have the stock boot IMG flash it and then intsall twrp and magisk.
smsry said:
Flashing a custom rom is optional. You don't NEED to flash a rom to get TWRP...
Click to expand...
Click to collapse
LoadOP2 said:
Skip the flashing a rom part and you will be good to go.
Click to expand...
Click to collapse
Haha, makes sense! Thank you for your answers
Nevermind.. i got it to work pretty easily..
I have twrp on this device and Pixel Experience ROM and it's working all fine..
But there's this one thing where when booting to recovery, it asks me to input a password for User(0) when i try to input anything it says password failed..
From reading the log, it says it's for decrypting data(8f I'm not mistaken)
Is this important? Do i need to decrypt it?
Currently the ROM works fine with no errors, so I'm not gonna bother, but would still like to know what this "decrypting" thing is..
smsry said:
Nevermind.. i got it to work pretty easily..
I have twrp on this device and Pixel Experience ROM and it's working all fine..
But there's this one thing where when booting to recovery, it asks me to input a password for User(0) when i try to input anything it says password failed..
From reading the log, it says it's for decrypting data(8f I'm not mistaken)
Is this important? Do i need to decrypt it?
Currently the ROM works fine with no errors, so I'm not gonna bother, but would still like to know what this "decrypting" thing is..
Click to expand...
Click to collapse
Yes, If you use a lock screen enter that password it will be decrypted. You will have to format data if you decide to flash any other rom anyway.
flashed twrp but not able to boot into recovery.
igeekyayush said:
flashed twrp but not able to boot into recovery.
Click to expand...
Click to collapse
There can be many reasons for that. Please tell me the error or what's actually happening. Then only I can be of help.
Sir ive used xiaomi flashtool v2 after that and it worked. Thanks sir. After that i updated to latest twrp from that chinese one.
LoadOP2 said:
There can be many reasons for that. Please tell me the error or what's actually happening. Then only I can be of help.
Click to expand...
Click to collapse
Joyeuse
Hello, Does it work for Joyeuse (European version)?
The name of TWRP says Curtana -Unified
rfguy said:
Hello, Does it work for Joyeuse (European version)?
The name of TWRP says Curtana -Unified
Click to expand...
Click to collapse
Yes Unified means all Snapdragon 720g Devices which include Joyeuse, Curtana, Gram, Excalibur.
Hey buddy, thank you for this quick step-by-step guide. I flash ROMs since 2012 and you know what? It helped me the same. Having all stuff needed for go from stock to custom concentrated in one place (plus some useful tip like the Magisk flash at the end) it's always useful and time-saving. Thank you
2 Micro-notes about fastboot btw:
- write 'fastboot (with lowered 'f'): it may confuse some newbie
- it's 'reboot' instead of 'boot'
I want to access /data/system/users//settings_ssaid.xml to know what my game unique id is.
But after some research i learned that i have to root to able to get there but i have almost zero knowledge about it.
Are there any guide to root Redmi Note 10 from the scratch? Thanks.
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
alonsoj636 said:
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
Click to expand...
Click to collapse
Hi, I'm on official global ROM 12.5.3.0 RKGMIXM
And i turned on OEM Unlocking in developer mode yesterday (Which is confuse me a little a guide said i have to wait for 7 days for this but mine is nothing it's just switched to on)
OEM Unlocking is only one of the steps, but it does not unlock the bootloader. File a request with Xiaomi.
unlock bootloader
i recommend only booting to twrp, not flashing it
flash magisk 23
hide magisk
inn0ichi said:
...
i recommend only booting to twrp, not flashing it
...
Click to expand...
Click to collapse
Why do you recommend to only booting to TWRP instead of flashing it?
Pasarireng said:
Why do you recommend to only booting to TWRP instead of flashing it?
Click to expand...
Click to collapse
because the twrp developer instruction is to booting , not flashing
alonsoj636 said:
because the twrp developer instruction is to booting , not flashing
Click to expand...
Click to collapse
Aside of that instruction, actually is it 'dangerous' if we install the TWRP? What 'bad things' would/may happen if we install it? (Because I see some guides about installing it on RN10, like this one for example, and I was almost followed that guide).
Risk of bootloop
Pasarireng said:
Aside of that instruction, actually is it 'dangerous' if we install the TWRP? What 'bad things' would/may happen if we install it? (Because I see some guides about installing it on RN10, like this one for example, and I was almost followed that guide).
Click to expand...
Click to collapse
Risk of bootloop and fastboot loop... because this twrp is modded to be booted and then flashed (you can found the option in advanced)
One time i faced a fastboot loop once i flashed directly the twrp , that's why i recommend booting it first and then , flashing
Y
alonsoj636 said:
Risk of bootloop
Risk of bootloop and fastboot loop... because this twrp is modded to be booted and then flashed (you can found the option in advanced)
One time i faced a fastboot loop once i flashed directly the twrp , that's why i recommend booting it first and then , flashing
Click to expand...
Click to collapse
Yes, I mean that, (booting it first then flashing,.. (the TWRP right?).. I think the guide (which the youtube link I attached above) is also told to do that, right? (Or do I misunderstand this?)
Pasarireng said:
Y
Yes, I mean that, (booting it first then flashing,.. (the TWRP right?).. I think the guide (which the youtube link I attached above) is also told to do that, right? (Or do I misunderstand this?)
Click to expand...
Click to collapse
Yes , is the correct way
inn0ichi said:
unlock bootloader
i recommend only booting to twrp, not flashing it
flash magisk 23
hide magisk
Click to expand...
Click to collapse
Please confirm these;
*So we can:
Use TWRP only temporarily, only to root the phone (by flashing Magisk v23),
and then,
back to using the stock recovery on our RN10 afterward,
even if the RN10 is already rooted?
**If the answer for my question above is yes, then (in RN10 condition of Unlocked Boot Loader, Rooted, Stock MIUI & Stock Recovery) ;
Would we still get official OTA Update from Xiaomi (and can download and install the update- as how it's like before rooting the phone)?
Thank you in advance
It's an unnecessarily complicated procedure. Just flash a modified boot.img for your Miui using fastboot from your PC. If you don't have the ability to modify the boot.img on another rooted phone yourself, request a modified boot.img with the exact update version of your Miui here.
StaryMuz said:
It's an unnecessarily complicated procedure. Just flash a modified boot.img for your Miui using fastboot from your PC. If you don't have the ability to modify the boot.img on another rooted phone yourself, request a modified boot.img with the exact update version of your Miui here.
Click to expand...
Click to collapse
Thanks again, (and maybe I will try your suggestion later).. but (sorry)... your reply doesn't answer my questions.
(I think my questions are very clear and probably very easy to be answered by someone who has experience/knowledge about it (like you?).. no?)
Forgive my nooby questions.
But I really want to know as much as I can (especially about the answer for some questions I have inside my head about the matter, like I asked above),.. before executing doing something about my phone.
oops... I'm sorry for double send
In the past I rooted Miui and then continued to get OTA updates. However, this cannot be confirmed for all versions of Miui. Each new update changes the phone software and so what worked before may not work today.
alonsoj636 said:
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
Click to expand...
Click to collapse
Hi, I'm unlocked my phone and installed the orange fox it's the custom recovery right? Because it say so.
If yes, By Flash Magisk ZIP how to do that? Please explain the detailed steps, Thanks.
First of all, I would like to point out that Magisk (root) is a security risk. Without understanding the issues, the phone is more easily exploitable.
To install, just download the magisk file with the ZIP extension. In recovery, select the install option and select this file. Once installed, exit recovery and boot the system. Once the system boots, use magisk and complete the installation it requests.
Lolitary said:
Hi, I'm unlocked my phone and installed the orange fox it's the custom recovery right? Because it say so.
If yes, By Flash Magisk ZIP how to do that? Please explain the detailed steps, Thanks.
Click to expand...
Click to collapse
the answer above is right ... but i would suggest to flash Orange Fox zip and then Magisk zip... to avoid problems
isn't there decrypt.zip for RN10?
How to decrypt this phone?
I usually did that along with rooting with my android phones before this.
Edit:
Update:
It's ok now I understand how, after watching this video.