PHONE MODEL: Motorola Moto E 2014 Condor XT1021, with the bootloader unlocked.
Hello. I'm not kinda sure if this is the correct place to post this, so I apologize if that's the case.
Well, this is what's happening to me: first I tried to install an alternative ROM (I was using Lollipop 5.1 stock before that), it was the Slim 7 one. It never booted, so I did the following thing:
1 Downloaded TWRP.img from official webpage (the latest version).
2 Downloaded LineageOS from official webpage (14.1 version) for Moto E 2014.
3 Booted my phone in fastboot mode.
4 Installed the TWRP image ("fastboot flash recovery twrp.img"). It was successful, without giving me any errors (the fastboot program was downloaded through XDA forum post).
5 Booted in recovery (TWRP menu).
6 Wiped everything (advanced wipe -> select all).
7 Copied the LineageOS, SU addon and Gapps (nano) .zip files to SD Card.
8 Flashed everything (Lineage+SuperSU+Gapps, in that order). It gave me no errors.
9 Restarted it.
So, now my phone is stuck at boot animation (that tiny blue circle moving from one side to another) after aprox. 40 minutes of 'booting'.
Details of the software I'm using:
Recovery image: "twrp-3.1.1-0-condor.img"
LineageOS: "lineage-14.1-20170925-nightly-condor-signed.zip"
Gapps: "open_gapps-arm-7.1-nano-20171001.zip"
Root: "addonsu-14.1-arm-signed"
¿Can the community give me any useful information to troubleshoot this problem?
Thanks really much, in advance.
Best regards, viciecal.
edit: installed carbonrom and solved it. thx
viciecal said:
PHONE MODEL: Motorola Moto E 2014 Condor XT1021, with the bootloader unlocked.
Hello. I'm not kinda sure if this is the correct place to post this, so I apologize if that's the case.
Well, this is what's happening to me: first I tried to install an alternative ROM (I was using Lollipop 5.1 stock before that), it was the Slim 7 one. It never booted, so I did the following thing:
1 Downloaded TWRP.img from official webpage (the latest version).
2 Downloaded LineageOS from official webpage (14.1 version) for Moto E 2014.
3 Booted my phone in fastboot mode.
4 Installed the TWRP image ("fastboot flash recovery twrp.img"). It was successful, without giving me any errors (the fastboot program was downloaded through XDA forum post).
5 Booted in recovery (TWRP menu).
6 Wiped everything (advanced wipe -> select all).
7 Copied the LineageOS, SU addon and Gapps (nano) .zip files to SD Card.
8 Flashed everything (Lineage+SuperSU+Gapps, in that order). It gave me no errors.
9 Restarted it.
So, now my phone is stuck at boot animation (that tiny blue circle moving from one side to another) after aprox. 40 minutes of 'booting'.
Details of the software I'm using:
Recovery image: "twrp-3.1.1-0-condor.img"
LineageOS: "lineage-14.1-20170925-nightly-condor-signed.zip"
Gapps: "open_gapps-arm-7.1-nano-20171001.zip"
Root: "addonsu-14.1-arm-signed"
¿Can the community give me any useful information to troubleshoot this problem?
Thanks really much, in advance.
Best regards, viciecal
edit: installed carbonrom and solved it. thx
Click to expand...
Click to collapse
if device's bootloader is unlocked and TWRP is installed then its so easy to resolve your problem. I just actually want to know what do you exactly want to resolve???
do you just want to start up your device or anything else?
Related
I Unlocked the bootloader 3 days ago and flashed Cyanogenmod 12.1 with exact gapps and was able to use the phone perfectly ,today I searched for xposed and found that it could be only installed by manual flashing for android lollipop , so I downloaded the zip file and rebooted my phone in Recovery Mode [ TWRP ] and flashed the zip file just after that the phone stuck at bootloop. Restarted the phone 3 time's but no luck so finally I got into bootloader by pressing the volume down button and the power button and opened recovery mode to factory reset the phone and reflashed the CM 12.1 with gapps , now the problem begin's when I restarted the phone it is stuck at "Warning Bootloader Unlocked" and even the recovery mode is stuck at beginning screen of twrp , Im only able to use the bootloader . Even tried to reflash TWRP Recovery from computer but thier's no change it is still stuck at the recovery screen .
Any help would be really appreciated
try reflashing and then wiping cache's before rebooting ?
like the regular cache and dalvik cache.
also don't expect the first boot to work quick.. leave it for a long time...
good luck.
Actully the problem is , when i try to open recovery mode it stucks at teamwin logo (twrp)
"I searched for xposed and found that it could be only installed by manual flashing for android lollipop"
Click to expand...
Click to collapse
that quote is confusing.. what did you mean exactly.
What TWRP ? From Where + what version # ?
If i were you i would re-download it then MD5 hash it.. verify it !
I always check the md5 hashes on any phone roms or firmware etc.
I have had tons of incomplete downloads and there is nothing wrong with my internet connection either.
The more detailed you can be the more likely someone can help.
Once you are positive your TWRP is downloaded properly if i were you
i would re-flash it with fastboot. (if you can)
Can you power off the phone and put it in bootloader mode then connect to pc ?
power it off then hold volume down + power then plug in USB
then right click the empty space in the windows folder (assuming no Linux)
select open command prompt here then type:
adb devices
Is it listed ?
I also assumed you have "Minimal ADB and Fastboot" installed.
Sounds like you flashed a 5.1 firmware package ?
yes ? which one ?
And watch out many sites have cut off my download on me while downloading them.
and if you then flashed a half completed download you could prob damage the phone.
for checking hashes on windows i use HashSlash.. it's clean / free and has a GUI ..google it
Basically , first I flashed Android 5.1.1 AOSP for my device and then Cyanogenmod 12.1 Nightly Surnia . and yes I tried to reflash TWRP Recovery but it is stuck at the same Teamwin Logo screen , and i flashed the latest version of twrp which was available on xda . Can you provide me worth some kind of image file which I can flash to Factory reset my device from computer or anything else which can help.
And by the way Thanks for the quick reply
sabungolfer0011 said:
Basically , first I flashed Android 5.1.1 AOSP for my device and then Cyanogenmod 12.1 Nightly Surnia . and yes I tried to reflash TWRP Recovery but it is stuck at the same Teamwin Logo screen , and i flashed the latest version of twrp which was available on xda . Can you provide me worth some kind of image file which I can flash to Factory reset my device from computer or anything else which can help.
And by the way Thanks for the quick reply
Click to expand...
Click to collapse
https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
i used that.. but didn't flash my phone yet.
that is all firmware packages stock for Moto-2015
You still have not mentioned a lot like where did you get TWRP and what version ?
What carrier is your phone ?
I take it you unlocked the bootloader or did you get it like that ?
I'm guessing the bootloader loads TWRP
so either of those is probably damaged i bet.
I would try and get it stock then work from there getting TWRP back on and rooting etc.
What i was trying to ask you is..
Was your phone on 5.02 and you tried to update it to v5.1 ?
Because i have seen other people here who had problems with that.
Relocking the bootloader can cause problems and so can reverting to an old ver from 5.1 to 5.02
I used a custom kernel and TWRP from Squid here on the forum and rooted
and his kernel is only good for me up to version 5 but he has way newer versions out..
but they are only for users who updated to 5.1
So you have to be VERY careful what your doing.
I might have screwed up my phone if i didn't notice the fine print.
Also just search the forum for some guides on flashing firmware
and verify the downloads
My Bootloader is unlocked , TWRP Recovery Version 2.8.6.0 . My phone was on Android 5.0.2 [ Official Non Rooted ] , so I thought of updating it to 5.1.1 which was available as custom rom So I unlocked the bootloader flashed TWRP version 2.8.6.0 by copying Recovery.img in minimal adb folder and oped CMD and flashed the custom recory and it was no problem , then 2 days ago I flashed Cyanogenmod.12.1.Surnia.20150829.zip and it worked fine no issues then I flashed Xposed Modular in recovery mode , now when I tried to restart the system it stuck at bootloop so I entered Bootloader and again restarted 2, 3 times but no luck so I again entered bootloader and entered Recovery Mode ( TWRP 2.8.6.0) and wiped all my data , But unfortunately I was outside so I dint had the firmware and gapps so I switched the phone off in hope that ill flash the firmware and gapps when i reach back home . So when I vame back home and pasted the firmware and gapps in memory card and inserted it baxk in the phone and tried to enter recovery mode , that was the first time when I experied That teamwork logo stuck at recover mode and the further story you laready know
hey all!
So this is a first for me... I've been rooting and playing with android for a very long time (going back to the g1 days) and this is the first time I've ever seen this.
So I was on an old version of CM and decided it was time to update finally. I had unrooted a long time ago, but was still running cm perfectly fine. I went to install a new version of recovery (so I could update) and now when I try to boot into recovery I just get the oneplus logo. Here's the strange part, the phone isn't soft bricked... I can still boot into android no problem.
Anyone else every seen this problem? Do I need to start over (unlock bootloader, root, recovery, rom)?
Anyone else ever seen this happen on Oneplus One or any other phone for that matter?
Thanks in advance!
Same Problem Here
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Click to expand...
Click to collapse
I tried it and I got the following error:
/system/bin/sh: wipe_misc: not found
Click to expand...
Click to collapse
I don't know what else to do now. Please help.
janc_z said:
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
I tried it and I got the following error:
I don't know what else to do now. Please help.
Click to expand...
Click to collapse
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
zbt1985 said:
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
Click to expand...
Click to collapse
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
janc_z said:
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
Click to expand...
Click to collapse
Lucky you!
I on the other hand can't connect via adb, only fastboot...
Hello! i have used the search tool to see if there is a custom recovery for my device but i am unable to find any. I found TB-X103F custom twrp but im unsure about trying it!.
I may be rather early as this tablet only recently came out.
Lenovo X 104F- 1 GB RAM
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
Care to share any links?
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
kpfx said:
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
Click to expand...
Click to collapse
I've been looking for one also and was gonna see about working on one
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
I can attest to this, I flashed the last Resurrection Remix Oreo GSI (12/21/18) and a (Magisk) rooted kernal I got from firmware (Lenovo MOTO Smart Assistant). And so far everything seems to be working fine.
So I also flashed resurrection remix pie gsi... it works as well... only thing is it doesn't come with gapps... and without twrp i can't flash a gapps package. The resurrection remix I used was the final oreo build... zt has gapps pre-installed... you have to register the device with google because it is not certified... but after that everything seem good. One thing to mention is both the oreo and pie builds are "go edition" so some features are missing because of that... one in particular I noticed is notification access for 3rd party apps... go edition devices don't have that feature
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
44Guest said:
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
Click to expand...
Click to collapse
Use Lenovo MOTO Smart Assistant to repair your tablet (you wont actually repair tablet, just using to get firmware)
Follow steps to get to download the firmware (it will save to ProgramData folder, its hidden folder... in widows anyway)
Take the boot image (boot.img) from firmware folder and transfer to storage on tablet
Instal magisk manager and use to patch the boot image you transfered from computer
Transfer patched boot image back to computer
Download the latest oreo gsi for resurrection remix or lineage
Use fastboot to unlock bootloader
Use fast boot to flash gsi
Use fastboot to flash patched boot image
Google anything you need help with...
I used the resurrection remix oreo also because there is a build that has gapps pre-installed... the pie version works but doesn't have gapps pre-installed and without twrp I couldn't find a way to install them
After tablet boots up install magisk manager and you will be rooted
You will need to register your device with google because it will not be certified... that was a pain to get done even though the process is pretty straight forward
So far only "issues" I have encountered are not actually issues they are due to the fact that the resurrection remix gsi is android "go edition" I haventr tried lineage because I like the customization options that resurrection remix offers
Here is the magisk patched boot image I made so you can skip that part...
https://www.mediafire.com/download/x4d3xp8w3e8bw3g
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
4niner4 said:
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
Click to expand...
Click to collapse
So you want all files on the computer at first...
When you unlock bootloader it will wipe the tablet.
Flash the the gsi image then the magisk patched boot image using fastboot (there are instructions on xda regarding flashining gsi... you have to wipe system before flashing)
After tablet reboots to resurrection remix move the magisk manager apk to the tablet and install it... open magisk manager and you should have magisk installed giving you root and so much more.
Before you attempt this make sure you familiarize yourself with all the steps... search google/xda.
Also... I will say this... I tried to just root the tablet first but it wouldn't boot after so I tried to fix it using the Lenove tool and it failed... flashing the resurrection remix gsi with the patched boot image saved me from a lot of headache and wasted time... I would prefer if it was not a "go edition" rom but its still better than stock.
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
4niner5 said:
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
Click to expand...
Click to collapse
Make sure you fastboot flash unlock and fastboot flash unlock_critical. Just look an here for the links for lineage gsi. It flashes just fine and is super easy. I have resurrection remix on my 104f. I'm trying to compile twrp for it right now but hard to do with kids lol also if you use the lenovo tool you can download the recovery files which has boot recovery and all that in it and you can use magisk to patch the boot.ing and then copy that to the Lenovo tool and replace the stock boot img then recover it and you now have a working patched boot.img. I went through the same thing
Any Luck?
Any luck with that twrp? I'm willing to test it out...
Would like to be able to use the resurrection remix pie rom with gapps. So I can hopefully give some helpful feedback... one warning I am an amateur at anything beyond using fastboot and some adb commands, but I can learn pretty quick if i have the time to spend...
Another warning I have a sub-par windows pc to work with (and its the wife's) it prob can't run Linux in VM.
Disable "go edition" in Resurrection Remix Oreo
Using root explorer...
Navigate to /system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Navigate to /sbin/.magisk/mirror/system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /sbin/.magisk/mirror/system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Reboot
This allowed me to set notification access again (its disabled in "go edition")
Hey guys, I'm trying to follow the steps in this thread to install Resurrection Remix Pie on the tablet using fastboot but whenever I try to flash a ROM to the system partition I get a (remote: size too large) error.. Does anyone know why this could be? I've tried using flags like -S, I've wiped the partitions and I don't know what else I can try. I have tried with Lineage, AOSiP and RR GSIs.
Thanks.
I cant get this to work.. What version of RR or Lineage OS works with tb-x104f?
up..................
I got the final version of rr oreo running fine... no luck with the latest rr pie unfortunately...
Anyone know if this is an A or AB device?
Sorry if this is posted in the wrong place but I could not find anywhere to post it by following Help threads I just went round and round in circles. Hi I am fairly new to phone modding. I updated my moto e XT1524 to LineageOS 16.1 some months ago. Yesterday I decided to update to 17.1. I followed the instruction to install. I have wiped phone and ran fastboot adb as instructed. I keep gettting -This packeage is for XT1514,XT1524,XT1526......... ect and error7. I have ammended the updater-script as detailed in the "How to fix error 7 " document but the rom will still not load. same error message. I have now noticed that * Required * firmware version must be based on Marshmallow on the Installation section on the main forum page. Can someone help me get the phone back to stock rom or any other rom for that matter. I can get the phone into recovery mode and I have TWRP installed i aslo have SDK tools installed on PC.
@rddxda
TWRP can't be used to flash Stock ROMs. In your case you need QFIL ( read: Qualcomm Flash Image Loader ) to flash a Stock ROM, and also the Motorola USB driver installed on PC.
jwoegerbauer said:
@rddxda
TWRP can't be used to flash Stock ROMs. In your case you need QFIL ( read: Qualcomm Flash Image Loader ) to flash a Stock ROM, and also the Motorola USB driver installed on PC.
Click to expand...
Click to collapse
Thanks for your help, could you please help a little further as I cannot find a stock rom. I have been on the motorola site and followed a few links on the internet but only to find the file is no longer available. Any idea where I can get a stock rom from or can I use QFIL to load a non stock rom?
I have found a stock rom XT1524_SURNIA_RETEUALL_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml.zip this is not an mbn file, however if I open the zip folder there is a fsg.mbn file in there along with boot, bootloader gpt.bin etc. Is this the file to use with QFIL. Sorry to be a pain but I don't want to make the situation worse.
Also can you tell me if restoring to stock rom will this re-lock the bootloader?
UPDATE: First of all thank-you for all your help - I have learned a lot over the past 6 days (that's how long I have been trying to fix it). I flashed lineage-17.1-20200814-recovery-surnia and then sideloaded adb sideload lineage-17.1surnia.zip. Phone now rebooted in normal mode and showing on PC now OK. So old Moto E XT1524 on Lineage OS 17.1.
Hello everyone!
I'm new to this. I have a kate and was able to unlock the bootloader. I installed a fastboot rom (8.1.4) that I downloaded from <https://xiaomifirmwareupdater.com>. I also downloaded a twrp from <https://twrp.me/> and installed it successfully via adb. Then there's this:
If I reboot to the system after twrp installation, it boots normally but when I try to enter twrp, it's not there, it enters standard recovery mode. So it seems it's not kept after rebooting.
If from Windows cmd I boot into twrp, there's no decryption process at the start (as I've seen in videos) and I can't install root (the option is not there). And worst of all, when I leave twrp and reboot the phone it wont start.
So because I'm quite limited in technical knowledge, my temporary solution is to reinstall the old rom again (8.1.4) and get the phone reset. I've already done this twice today.
I suppose I need to install some kind of zip file while I'm inside twrp to make it stay after rebooting (I've seen that for other devices). Is that correct? If yes, how can I identify and find this file, since at <https://twrp.me/> there was just the twrp listed for this device. No zip files there for kate/kenzo.
Any patient friend who would shed some light on this, please?
Thank you very much for reading this and for any help you can offer!
Best wishes!
GZ
Although I found it a little overwhelming at first, I found everything I needed here:
[NEWBIE GUIDE v2.0] MIUI ROMs, TWRPs, ZIPs, BACKUP, FLASH, RESTORE
UPDATED NEWBIE GUIDE v2.0 FOR REDMI NOTE 3 SNAPDRAGON (KENZO) (WORKS FOR ALL MIUI / AOSP / CM BASED ROMs) GUIDE SECTIONS : QUICK LINKS#1 : MIUI ROM | TYPES OF MIUI ROM | TWRP | TYPES OF TWRP #2 : TWRP FLASHABLE ZIPs | FULL PARTITION BACKUP |...
forum.xda-developers.com
Thank you!