Alcatel 6045 Recovery & ROM varients - Onetouch Idol 3 Q&A, Help & Troubleshooting

I have a 6045 that I could not get to run the Resurrection Remix ROM, probably due to the fact that it won't read TWRP 3+. Even with the older TWRP, running Linage 14.1 didn't recognize the sim card. So, I went with CM 12.1, abd GAPPS Nano; which has been fine. However I just got another 6045 that wouldn't unlock bootloader via Fastboot. I understand that they took away the option to unlock the bootloader via Fastboot. HOW UNSAVORY!! However I was able to use Sahara & Firehose Test to flash a later version (3.0+) of TWRP. I got RR to run on it, and WOW!! What a difference!! Reminds me of when I modded my first Huawei smartphone with CWM and CM7 back in 2010!! What a GREAT Rom!! I'm so satisfied with RR, everything is great!! My question is, How do I put RR on an older model of the 6045?? I haven't found a strategy. Does anyone on here know how to?? All thought and Ideas are welcome on this thread.

Were you able to get twrp on the idol 3?

KUJO1001 said:
Were you able to get twrp on the idol 3?
Click to expand...
Click to collapse
Yes, on both devices....however one device wouldn't take the newer version of TWRP, and the older version won't flash RR, unfortunately.

Related

Flashing MIUI rom via TWRP without bricking

Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
dark_prince said:
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
Click to expand...
Click to collapse
Thanks for your reply. That surprises me that there still isn't an miui 8 developer ROM out yet for this device. Probably shall never come in that case.
Good to hear that f2fs is supported by cm14 though. Will certainly be running this once I receive my new cases to replace the girly pink cover my mi4c currently houses
danbrown162 said:
Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
Click to expand...
Click to collapse
Just flash miui 8 from xiaomi.eu ones. It supports flashing via twrp.

Failed to flash twrp in nougat 7.0

Is it possible to flash twrp in honor 6x BLN-L22 Android version (Nougat 7.0) ?. Have tried to flash it using fastboot, after that my device is stuck in "your device is booting now" screen, Is it possible?
RAHUL3387 said:
Is it possible to flash twrp in honor 6x BLN-L22 Android version (Nougat 7.0) ?. Have tried to flash it using fastboot, after that my device is stuck in "your device is booting now" screen, Is it possible?
Click to expand...
Click to collapse
Yes its possible to flash twrp...
What error it gives while you try to flash twrp...
What version. Of twrp you used??
It is possible that it doesn't boot, and... This happens if you flashed the TWRP available on official TWRP site (I remember that, it happened to me also).This is because they've uploaded a version that doesn't work with our device (it's there from months now, i don't understand why it is still there... I have to report that), but no worries; you can solve this easily flashing the OpenKirin version of TWRP that you can grab here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 flash it via fastboot like you already did with the actual TWRP, and you're ready to go. I tried it on different builds, it always works and i still thank OldDroid's work on it for making TWRP working on Honor 6X.
hassanjavaid8181 said:
Yes its possible to flash twrp...
What error it gives while you try to flash twrp...
What version. Of twrp you used??
Click to expand...
Click to collapse
Thank you so much for responding. It doesn't give me any error while flashing it, going to bootloader using cmd and fastboot flash recovery twrp.img, it shows ok successful but after that i entered fastboot boot twrp.img... it's stuck in your device is booting now. I have used every available twrp in official website.. American and European ones. Nothing worked.
RedSkull23 said:
It is possible that it doesn't boot, and... This happens if you flashed the TWRP available on official TWRP site (I remember that, it happened to me also).This is because they've uploaded a version that doesn't work with our device (it's there from months now, i don't understand why it is still there... I have to report that), but no worries; you can solve this easily flashing the OpenKirin version of TWRP that you can grab here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 flash it via fastboot like you already did with the actual TWRP, and you're ready to go. I tried it on different builds, it always works and i still thank OldDroid's work on it for making TWRP working on Honor 6X.
Click to expand...
Click to collapse
Thank you so much for responding. Will try and get back to you with the result.
RedSkull23 said:
It is possible that it doesn't boot, and... This happens if you flashed the TWRP available on official TWRP site (I remember that, it happened to me also).This is because they've uploaded a version that doesn't work with our device (it's there from months now, i don't understand why it is still there... I have to report that), but no worries; you can solve this easily flashing the OpenKirin version of TWRP that you can grab here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 flash it via fastboot like you already did with the actual TWRP, and you're ready to go. I tried it on different builds, it always works and i still thank OldDroid's work on it for making TWRP working on Honor 6X.
Click to expand...
Click to collapse
It worked :laugh: Have been working on this for three days. It's true TWRP which is available officialy is not working. Thank you so much man.
RAHUL3387 said:
It worked :laugh: Have been working on this for three days. It's true TWRP which is available officialy is not working. Thank you so much man.
Click to expand...
Click to collapse
Nothing hard to do dude, the important is that it works now

unable to install twrp over 3.1.1.1 on mi4c (trying to go from android 7.1 to 8 or 9)

Hey everyone,
i usually don't post questions but i've been on pretty much every forum the web has to offer and am still stuck so i'll try my luck here.
i'm currently running lineage 7.1 on my mi4c, i've used another phone for a while but now that my mi4c has a new battery i wanted to start using it again, is also decided this would be the time to update it to android oreo or pie, this however seems to be impossible.
i can only use twrp up to 3.1.1.1, all higher (and unofficial versions) will not boot via fastboot 'dtb not found' or when flashed via older twrp will freeze on boot screen.
whenever i try to install a new rom it tells me 'error code 7', when i remove the 'assert' lines in the update it gives me 'error code 6'
my device is unlocked, i have checked this in fastboot.
do i have to install miui again before installing another rom? do i have to go back to the standard recovery? i'm currently running out of ideas and hope you guys might be able to help me. maybe i'm overlooking something simple.
kind regards,
Monstreys
Hi! I don't know if this is a coincidence or not, but I was about to start a similar thread.
I try to do exactly what you are doing. I want to install LineageOS 16, unofficial ROM.
For this you need a newer TWRP, like 3.2.3.0, but it doesn't work 'dtb not found' like you said. I found out that this doesn't work because you need to have nougat bootloader. Most probably you have lollipop bootloader like I have, and thats why newer versions of TWRP are not working. I think the only way to update your bootloader to a nougat one is to flash the latest MIUI ROM. But, unfortunately, when you do that the bootloader gets locked, and I can't unlock it via MiUnlock due to Error:20091 when I try to link the phone to the Mi account. In MiUnlock it gives me the "this account cannot unlock the phone" or something like that.
Now I removed the "assert" lines from my rom and flashed it without the error 7 or 6. Some error still apears, but it also apears when I flash LineageOS 14.1, and that version is working even with those 2 errors I can't remember during flash.
After I flashed LineageOS, I flashed gapps and then superSU, and now my mi4c is stuck on mi logo for about 20 minutes, and I think it will remain that way.
So, there are 2 things we need to solve. We need to find a way to install latest MIUI without relocking the bootloader because I can't unlock it via MiUnlock, or to find out why after I flashed LineageOS 16 it gets stuck on MI logo.
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
i
i was unable to install the patch file, this nonetheless fixed my problem, thanks!!
if above not working, another method to do it based on my method.
https://forum.xda-developers.com/showpost.php?p=81573941&postcount=199
makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
My MI4C has been successfully flushed into lineage-17.1-20200220-UNOFFICIAL-libra.zip. It has been updated on TWRP 3.1.1 and keeps reporting error 7, and then abandoned TWRP3.1.1 and flashed into OrangeFox-R10.0-1-Stable-libra.zip After brushing libra-aqua_firmware_7.2.9.zip on this REC, you can flash lineage-17.1. I do n’t think it will be impossible to refresh because of partition problems. If you only need to upgrade lineage-17.1, you can refer to this method.:good::good:(Translation is not easy to use)
celrau said:
There is a 3.2.x around. If you don't want to bother go in the zip, /META-INF/com/google/android/ and delete the first lines (the ones starting with "assert") from updater-script, save and flash again.
Click to expand...
Click to collapse
rianawirawan said:
Right now, i'm using 3.1.1 -1 btw
It's latest twrp ver from official
Click to expand...
Click to collapse
TWRP-20190418-3.3.0.0-libra.img for the Xiaomi Mi 4c, by GuaiYiHu :
https://androidfilehost.com/?fid=1395089523397945946
Latest firmware for the Xiaomi Mi 4c libra :
https://github.com/XiaomiFirmwareUp...iui_MI4c_V10.1.1.0.NXKCNFI_13b9b312d0_7.0.zip

custom roms keep puttimg me back into fastboot

So long time android user. I have the tmo variant of the Oneplus7 pro with unlocked bootloader via exploit found. Have twrp installed amd stock rom rooted with magisk. I tried installing the Havoc and the Aosip rom followed directions step by step. Havoc booted to the first gteen splash screen then reboots to fastboot. Aosip gets to the settimg up wifi then reboots to fastboot. I made a backup of the stock rom before installing anything and im able to restore it with twrp and root. I looked in the threads but didn't find anything unless i missed it. Also been sitting on telegram waiting on someone to shed some light.
fordstang99 said:
So long time android user. I have the tmo variant of the Oneplus7 pro with unlocked bootloader via exploit found. Have twrp installed amd stock rom rooted with magisk. I tried installing the Havoc and the Aosip rom followed directions step by step. Havoc booted to the first gteen splash screen then reboots to fastboot. Aosip gets to the settimg up wifi then reboots to fastboot. I made a backup of the stock rom before installing anything and im able to restore it with twrp and root. I looked in the threads but didn't find anything unless i missed it. Also been sitting on telegram waiting on someone to shed some light.
Click to expand...
Click to collapse
Trying the canary build
It worked with canary 19.4
Mods please delete if need be

My story and a couple of questions

Hi All,
I have a new-to-me Oneplus 7 Pro. I have been trying to get Lineage with MicroG running. Well it has been quite the adventure and I have it to the point where I have Lineage running fine, and go to reflash TWRP and have bricked the phone, which takes a bit of time to get back to the point of having Linage running again. Specifics:
Lineage version: lineage-19.1-20221219-microG-guacamole.zip
TWRP Versions: I have found that twrp-3.6.1_11-0-guacamole.img works since my phone is at Android 11.
My questions are:
Are TWRP versions tied to Android versions?
When I am trying to get the last version of TWRP installed I have tried 2 approaches:
fastboot flash recovery
fastboot flash boot
Neither worked, phone always ends up bricked. I have used:
TWRP-3.5.1-guacamole-Nebrassy-3.img
twrp-3.6.1_11-0-guacamole.img
twrp-3.6.2_11-0-guacamole.img
I also have tried to boot the images 1st using: fastboot boot twrp-3.6.1_11-0-guacamole.img
and that bricks things.
What am I doing wrong?
Thanks
Ray
rbahr said:
Hi All,
I have a new-to-me Oneplus 7 Pro. I have been trying to get Lineage with MicroG running. Well it has been quite the adventure and I have it to the point where I have Lineage running fine, and go to reflash TWRP and have bricked the phone, which takes a bit of time to get back to the point of having Linage running again. Specifics:
Lineage version: lineage-19.1-20221219-microG-guacamole.zip
TWRP Versions: I have found that twrp-3.6.1_11-0-guacamole.img works since my phone is at Android 11.
My questions are:
Are TWRP versions tied to Android versions?
When I am trying to get the last version of TWRP installed I have tried 2 approaches:
fastboot flash recovery
fastboot flash boot
Neither worked, phone always ends up bricked. I have used:
TWRP-3.5.1-guacamole-Nebrassy-3.img
twrp-3.6.1_11-0-guacamole.img
twrp-3.6.2_11-0-guacamole.img
I also have tried to boot the images 1st using: fastboot boot twrp-3.6.1_11-0-guacamole.img
and that bricks things.
What am I doing wrong?
Thanks
Ray
Click to expand...
Click to collapse
If you look at the official installation page for your phone, you will see that Lineage OS 20 and 19.1 are supported. So you should reinstall Lineage OS 18.1 again, and then follow the steps on this page. Don't bother reinstalling GAPPS until after you upgrade it.
If for whatever reason you don't want an Android version higher than 11, let me know.
I specifically don't want GAPPS or anything remotely Google related. I had tried OS 20 and found that I had a problem installing apps - probably user error, but I don't need the latest and greatest. I am currently at Android 11.
I will read through the instructions, although the number of tutorials I have gone through is craze.
Can you tell me what the relationship between TWRP and Android version is, and are you able to sus out what I did wrong with my efforts to get TWRP loaded over the lineage 19 version I was using?
Thanks
Ray
rbahr said:
I specifically don't want GAPPS or anything remotely Google related. I had tried OS 20 and found that I had a problem installing apps - probably user error, but I don't need the latest and greatest. I am currently at Android 11.
I will read through the instructions, although the number of tutorials I have gone through is craze.
Can you tell me what the relationship between TWRP and Android version is, and are you able to sus out what I did wrong with my efforts to get TWRP loaded over the lineage 19 version I was using?
Thanks
Ray
Click to expand...
Click to collapse
rbahr said:
I have been trying to get Lineage with MicroG running
Click to expand...
Click to collapse
So I guess you don't want GAPPS, just MicroG. Definitely read through the instructions I gave you, as they are the official installation and upgrade instructions.
I would recommend installing Lineage OS 20, because it is the version that is being maintained right now.
I will attempt to guide you through the steps, but I need to know what your situation is right now: Is your bootloader unlocked? What OS do you have installed right now? What recovery are you using? etc.
I appreciate your help. Currently I am looking at a freshly updated phone with Android 11, and Oxygen 11.0.9.1.GM21AA.
The phone is a GM1917
Bootloader is unlocked and I am in developer mode. I have adb and fastboot loaded on my computer. I also have a working version of msm as I have bricked this thing 6 or 7 times...
Several times now, I have done the following:
Install TWRP
Install Lineage
Try and reflash TWRP <-- consistently fails at this point, gets stuck in a boot loop in the bootloader screen
Thanks
Ray
rbahr said:
I appreciate your help. Currently I am looking at a freshly updated phone with Android 11, and Oxygen 11.0.9.1.GM21AA.
The phone is a GM1917
Bootloader is unlocked and I am in developer mode. I have adb and fastboot loaded on my computer. I also have a working version of msm as I have bricked this thing 6 or 7 times...
Several times now, I have done the following:
Install TWRP
Install Lineage
Try and reflash TWRP <-- consistently fails at this point, gets stuck in a boot loop in the bootloader screen
Thanks
Ray
Click to expand...
Click to collapse
"Try and reflash TWRP" what do you mean, update the OS over TWRP?
I mean trying to re-install TWRP after installing Lineage
rbahr said:
I mean trying to re-install TWRP after installing Lineage
Click to expand...
Click to collapse
OK. Can you try following the installation instructions and skip the unlock bootloader step? Do so at your own risk, because the steps say you have to be on Android 12 first. If you do follow them, just make sure you follow them very carefully.
rbahr said:
I mean trying to re-install TWRP after installing Lineage
Click to expand...
Click to collapse
To my knowledge the guides that are provided on the TWRP site don't work for Android 12 and 13. From what I've heard, you have to root your phone and then install TWRP through Magisk.
Honkette1738 said:
To my knowledge the guides that are provided on the TWRP site don't work for Android 12 and 13. From what I've heard, you have to root your phone and then install TWRP through Magisk.
Click to expand...
Click to collapse
The guides I linked to point to the official Lineage OS instructions, right?
ethical_haquer said:
The guides I linked to point to the official Lineage OS instructions, right?
Click to expand...
Click to collapse
Yeah, but I was just saying how they should probably reflash TWRP instead of how TWRP's site says to, which doesn't work
Honkette1738 said:
Yeah, but I was just saying how they should probably reflash TWRP instead of how TWRP's site says to, which doesn't work
Click to expand...
Click to collapse
This build uses Lineage OS Recovery instead of TWRP.
ethical_haquer said:
This build uses Lineage OS Recovery instead of TWRP.
Click to expand...
Click to collapse
I know, but TWRP can be installed with Android 13 custom roms according to the TWRP thread.

Categories

Resources