I've made TWRP for the Onetouch Idol 3. It should work when you flash it, but using it is still a try at your own risk procedure. Your bootloader must be unlocked ONLY on LP (MM is locked so cant flash on it)to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, adb reboot bootloader
To permanently flash it:
Code:
fastboot -i 0x1bbb flash recovery twrp.img
Update through existing TWRP:
Code:
Flash as image > recovery
The download is up on the AndroidFileHost
Device source:
Kernel
Device
Tester: @Demetris @Alek Dev
XDA:DevDB Information
[RECOVERY] TWRP for Onetouch Idol 3, Tool/Utility for the Alcatel Onetouch Idol 3
Contributors
FireLord
Source Code: https://github.com/omnirom
Version Information
Status: Stable
Created 2017-05-28
Last Updated 2017-05-28
Try to flash this recovery from older TWRP recovery. I don't have problems.
Download the latest TWRP image file (.img) from the download link.
Boot into the TWRP recovery. ( ...
Go to install and find and select the Images button. ( ...
Browse to the image that you downloaded and select it.
Choose recovery and swipe to flash.
You are done!
Little notice, Restarting to recovery won't do. You will have to manually start it to recovery by VolUP+Pow. Especially if you're on 6.0+
Huskied said:
Little notice, Restarting to recovery won't do. You will have to manually start it to recovery by VolUP+Pow. Especially if you're on 6.0+
Click to expand...
Click to collapse
Works just fine here.
Myrage2000 said:
Hey,
I still have some issues flashing this, which is weird considering I can flash other versions of TWRP of this forum.
I'm updating to this version from my current twrp. The flash seems to succeed but then the recovery mode is broke and I got the fastboot mode starting instead...
I also tried to flash it from fastboot, the same issue is happening.
So I finally tried to do a fastboot boot to try it, and I got this error : "dtb not found".
I have a french 6045Y
Update :
According to this video https://www.youtube.com/watch?v=kTdKmceC5xU I should update the bootloader of my phone, which seems a good idea because my 6045Y might have a custom bootloader made by my mobile provider.
Is it possible to update the bootloader of my phone ? Where can I find one ? There's nothing on google
Update 2 :
My bootloader is likely to be old because I never received the MM update, I only have Android 5 (my phone provider is not updating it)
Click to expand...
Click to collapse
Your stock (made by Alcatel) bootloader is different than custom made here by devs. You'll first have to unlock it, push by fastboot commands to the phone custom one, than you can install roms, etc. Try searching the threads here on forum, I done this part 2yrs ago, so I can't recall every step.
Myrage2000 said:
Update 2 :
My bootloader is likely to be old because I never received the MM update, I only have Android 5 (my phone provider is not updating it)
Click to expand...
Click to collapse
I had the same problem. Solved it by flashing the GooGly ROM: https://forum.xda-developers.com/idol-3/development/rom-idol3-6045y-eu5-2-mm-googly-t3519943
Flashing takes a long time but it updates everything. Note that you will lose flashboot and will have to flash things through TWRP from then on.
---------- Post added at 03:23 AM ---------- Previous post was at 03:21 AM ----------
@FireLord I made a version with decryption working. Here is the link: https://www.androidfilehost.com/?fid=745425885120738038
Maybe you could mention it in OP for those who want encryption/decryption.
Myrage2000 said:
Thanks !
I made a backup of my aboot to restore flashboot commands (and I hope it won't restore the old bootloader with it x) )
Click to expand...
Click to collapse
Good luck. If the aboot works, I may be interested.
Myrage2000 said:
Hey I'm flashing it at the moment.
I don't know if I'm going to try to restore aboot, because if it fails, I have no way to repair my phone since fastboot commands won't be enable.
And I can't try to flash a new twrp, because if it fails, again I have no way to do something...
I saw a lot of threads for fastboot commands on idol 4.7 6039, but none for idol 5.5 6045
Click to expand...
Click to collapse
Yep, not sure there's a way to get back the fastboot commands. But as long as we have TWRP, then it
s fine.
Myrage2000 said:
Yes !
But I hope we will never have to update TWRP, because if it fails, it fails x)
I saw a new thread with a tool alcatel flasher that works without fastboot commands.
Anyway, ...
Click to expand...
Click to collapse
Should be fine, we can use stuff like rashr to flash from the ROM and TWRP to flash from recovery. As long as we don't change both at once, we should always have at least one to flash the other with!
guiniol said:
Yep, not sure there's a way to get back the fastboot commands. But as long as we have TWRP, then it
s fine.
Click to expand...
Click to collapse
This thread is about getting fastboot back on the 6045:
https://forum.xda-developers.com/idol-3/development/6045-mm-hybrid-bootstack-t3436808
JoeyPPC said:
This thread is about getting fastboot back on the 6045:
https://forum.xda-developers.com/idol-3/development/6045-mm-hybrid-bootstack-t3436808
Click to expand...
Click to collapse
I did try that but couldn't boot the latest LOS14.1 with it. Others have reported success so it may be due to the exact variant.
I have realized that this version of TWRP (3.1.1) doesn´t backup EFS partition but "firmware" partition, what means backup of firmware?
Works great with 6045Y
Thanks you for your work
Hello.
I'm trying to restore a backup (for going back to stock rom coming fro LineageOS 13.0 for Alcatel ONETOUCH IDOL 3 4.7 rom by alecbl.).
That backup was maden with this https://forum.xda-developers.com/id...-2-r5-twrp-t3574214/post73664585#post73664585, but launching 'adb restore Backup_14052017.bak' on command line I get this message in the phone (in TWRP):
command is: 'adbrestore' and there is no value
E:Unable to find file system (first period).
E:Unable to find file system (first period).
E:Unknown restore method for '/system'
E:ADB restore failed
Done processing script file
I'm using TWRP 3.1.0-0 and I've been told to use your version.
The problem is my phone is 6039, while in your download page I see
twrp-3.1.1-idol3.img
for the Alcatel Idol 3 5.5, by FireLord
Does this mean it works only with 6045?
And do you know how I can restore that backup?
ciclolars said:
I have realized that this version of TWRP (3.1.1) doesn´t backup EFS partition but "firmware" partition, what means backup of firmware?
Click to expand...
Click to collapse
Any idea?
Related
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
LucasBS1 said:
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
Click to expand...
Click to collapse
Sometimes booting recovery doesn't work...You will have to flash it. Perhaps you can flash the stock recovery after successful root? though i am not sure that will work
Also try booting into CWM
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
LucasBS1 said:
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
Click to expand...
Click to collapse
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
giaur said:
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
Click to expand...
Click to collapse
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
LucasBS1 said:
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
Click to expand...
Click to collapse
None of them worked. I'm going to resign, because there is nothing I can do. Seems you have exactly the same problem as me. What I tried:
- fastboot boot recovery.img. Phone hangs on bootlogo
- flash recovery, then use go to recovery option in fastboot menu. In this case, 2 possibilities: with usb cable connected, it boots normally to system, not to recovery. With usb cable disconnected, screen goes black and phone looks like powered off. You will need to power it on and it will boot to system.
- On running system with usb debugging enabled. If you type "adb reboot recovery", you will end with dead robot and "no command" error. You can however press VolUP +Power on this screen and you will see Android 3e recovery.
If you have the same problem as me, you are completly lost and it's impossible to intall recovery on your device. I'm close to resign and say "**** this ****ty phone" because (as you already mentioned), there is no any attention on my questions, twrp support was dropped long time ago etc.
Flashing recovery should not wipe your data, so once you try to flash twrp or cwm, please let me know about your results. I'm sure I will never able to solve this problem, but I will feel better knowing that I'm not alone whit it
---------- Post added at 06:05 PM ---------- Previous post was at 06:00 PM ----------
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
Still the same, I'm on stock recovery. In console, no errors:
Code:
[email protected]:~/android/DO_MOTOROLI/twrp/2.8.5$ fastboot flash recovery twrp2.8.5.0-recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (9046 KB)...
OKAY [ 0.312s]
writing 'recovery'...
OKAY [ 0.860s]
finished. total time: 1.172s
But "adb reboot recovery" - "No command". Damn it...
---------- Post added at 06:26 PM ---------- Previous post was at 06:05 PM ----------
Ok, I'm finished. It's not possible. F U C K Motorola and good night. My advice: don't waste your time if you have the same problem. You will get nothing, except wasted time. It's good that it's not my phone (I own OnePlus One). But I was asked to install CM12.1 on my friend's phone. It's impossible, so I will need to tell him I was failed with that.
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Seeing giaur on that situation puts me stepping back...
LucasBS1 said:
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Click to expand...
Click to collapse
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
giaur said:
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
Click to expand...
Click to collapse
Cool
Regarding to safety
Should I flash CWM or TWRP ? Why ?
Regarding the method
Flash through usb->Fastboot or through Apk (like CWM)
Or a third method ?
And why
Between TWRP 2.7 and 2.8, which one is safer ?
And of course...why ?
And a last question, before I leave you guys alone:
Did you manage to root the phone, despite the poblems occurring to you, giaur ?
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Yo !
Flashed TWRP
But wiped things I shouldnt
How to put the ROM back via USB ?
EDIT:
NEVERMIND
Found how to use SD to do that
giaur said:
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Click to expand...
Click to collapse
I was also struggling a lot many days into getting twrp and cw loaded on to a Moto E. The problem was that I was pressing the Power button to activate the recovery menu and that will not activate the recovery option. You got to press the UP button instead of power after executing
Code:
fastboot.exe flash recovery twrp-2.8.1.0-condor.img
. This is quite counter intuitive but described well in most posts, but as experts we assume up button is to go up the menu.
Sunish Issac
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
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.
Here is the last version at the moment of the Maze alpha ROM (tested only in 4GB version)
It's a complete ROM, not an OTA update, it can be flashed using the provided TWRP 3.2.1 version, I ported from a Jemmini (many thanks) version for Bluboo S1.
Unfortunately, the TWRP cannot be flashed (issue with the touch panel), only launched by fastboot.
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
There is also a SPFlashTool clean version of this ROM, useful in case of troubles (as official: no root, no busybox)
1- Reboot you phone in fastboot mode : adb reboot bootloader
2- Flash the provided TWRP : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3- Reboot to TWRP recovery
4- copy in your SDCARD and install, in the running TWRP, the downloaded ROM V09 : Maze_Alpha_4GB_v09_TWRP.zip
The first boot take some minutes so be patient.
Here the SPFlashTool versions :
MAZE_Alpha_4GB_V09_SPFT.zip
Here, if needed, my V09 TWRP backup (new one from 21/04/2018) :
TWRP_BACKUP_MAZE_Alpha_A_V09.zip
Credits to Jemmini and Magisk team.
Can you make this for the 6 gb version?
many thanks gonna ty it soon
Nautilus99 said:
Can you make this for the 6 gb version?
Click to expand...
Click to collapse
I do not have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
dreambo said:
I do note have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
Click to expand...
Click to collapse
Yes i know its sad, i did a backup of mine and root it but it didnt work the backup i had to do clean flash, if we can manage to have a twrp and a source of the stock roms we could make a deabloat and put update apps ( menssages, calendar etc) and put mods for awsome features i dont see RR or lineage putting thier hands on this phone
Thanks for this Rom.
Is there any root for the maze alpha x?
here
WiddleyScudds said:
Is there any root for the maze alpha x?
Click to expand...
Click to collapse
read
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
Click to expand...
Click to collapse
thorfr said:
read
Click to expand...
Click to collapse
I have an alpha x, not alpha.
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
rzoli71 said:
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
Click to expand...
Click to collapse
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
thank you
After I installed this rom, and freezed the hot knot, baidu_location FM Radio, etc, the BT connection did not break.
dreambo said:
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
Click to expand...
Click to collapse
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
ahorntaler said:
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
Click to expand...
Click to collapse
No I not have any source, I am just a simple user like any other.
If I have any source or if I can make a ROM for MAZE Alpha X, I will do it and I will share it with every body, as I do until now for the MAZE Alpha 4/64
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
iBolitN said:
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
Click to expand...
Click to collapse
Unfortunatly no. As you will see repeated times in the forum, people have issue with phone not booting after changing from stock recovery to twrp. This is do (most likely from) to verified boot setting. And by unlocking bootloader we can bypass verified boot. So without unlock you might get a successfull load into twrp, but android will not boot.
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
stargazer78 said:
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
Click to expand...
Click to collapse
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Thanks a lot for your reply....
the problem is that i cant boot into fastboot to unlock bootloader....
the phone bootloops all the time, shows the red state alert and even with vol+ pressed the menu to choose recovery or fastboot doesn't apear... thanks again.
dreambo said:
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Click to expand...
Click to collapse
Is there any way to unlock the bootloader in my situation or/and enter the fastboot mode in order to follow your steps... thanks.
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'