Database Info

In a right mess trying to return to stock

Please could someone help ! I'm trying to unlock my XT1032. I have the correct Sim-Unlock (network unlock) code from my old telco, but... it won't work because the phone is rooted, bootloader unlocked (S-ON) running CM13.
I figured that returning it to a stock build would allow me to unlock the phone, then I could re-root and return to CM13 on my new network.
However..... there are about a dozen guides on returning a Moto G to stock and the first one I tried left the phone stuck on the 'Warning: Bootloader is unlocked' message. Since then, I've tried several other guides and have got nowhere fast. I've been on this for four hours now and the only thing I seem to be able achieve is to get TWRP or CWM recovery on there by flashing from fastboot. Every other image I try either gives 'preflash validation failed' messages, sticks on the Bootloader Unlocked screen or gets it stuck in a bootloop!
I just want to switch networks... Why is this so bloody difficult ?

What Firmware did your XT1032 originally come with? or which Carrier?

Kitkat I think, and it's Tesco (UK).
I subsequently did the OTA update to Lollipop and then.... WHOAAAAA.... hold on... it's booting !!!
I don't know how, or what I've done to get this far, but the only thing I can think of that's changed is that the battery is now at 100% charge. It appears as though it's successfully flashed the 5.1 untouched ROM from http://forum.xda-developers.com/devdb/project/?id=7981#downloads
But, I've tried flashing that loads of times this evening and it's failed everytime.
Having said that it's booting, it's sitting here on the Motorola logo - and it hasn't got that far in the last five hours.... I'll be back shortly !
Update: It worked ! It completed the boot, I put the new SIM in, it asked for the unlock code and this time it worked OK. Now I'm tackling putting CM13 back on it. I think I'll stick with TWRP rather than CWM recovery, as long as TWRP can handle the automatic updating for the CM nightlies.
I have no idea what went wrong there - maybe it was just that the battery had to be at 100% ?? Who knows... Thankfully I doubt I'll be tackling that again !

I don't know if things have changed, but I would be careful with OTA Updates in CM. People have hard-bricked (phone is effectively destroyed) applying updates in this way. I also suggest you avoid official Motorola updates, rather use the factory firmware images available here: (which already include the content of OTA Updates)
[INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images​

Thanks for replying anyway mate. In the end, it's all good now. Unlocked and back on CM13 and on my new network !

Ahhh... not so good after all. The phone reboots every time you try to uninstall an app. I've tried flashing back to CM12.1, the latest stable release, and it does the same, so I've obviously screwed something up along the way.
Could someone help me flatten this thing completely and get it working normally please?
I've tried reflashing loads of times, even tried Cyanogen Recovery instead of TWRP but nothing I do gets rid of this reboot problem.
Can anyone assist please?

OK, so I've followed the procedure detailed here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 and flashed the Untouched 5.0.2. EU Stock ROM successfully, but it still reboots when you try to uninstall any app.
Whatever it is that's causing this is not getting overwritten by the flashing procedures I'm using is it ?
HELP !!!!!

@aneng64 - You have not done what I told you to do. Read my post again.

Yes I did... and I still had the same problem. It was only once I stopped trying to flash zips from TWRP and used mfastboot to flash the whole set individually (non-hlos, motoboot etc) that I got it to behave. The issue, incidentally, seemed to be the same one mentioned elsewhere here that also causes settings to crash when you try to go into settings, security.
Once it was stable with a stock ROM, I was able to flash CM13 again and it's now sorted. Thanks for your help anyway.

Has Anyone Gotten a Custom ROM onto a BLN-L24 (US Variant)?

I have tried quite a few ROMs, and all ended up going back to stock firmware because they wouldn't boot. I know I have to format data, and some ROMs ask you to change the data partition as f2fs.
Still, I think that there may be no ROMs that currently work for the US variant. One guy said LOS 13 worked, but when I flashed it, it failed. If someone has gotten it to work, can you please post as many steps as you remember on how to get it work?

Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050

RedSkull23 said:
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
Click to expand...
Click to collapse
Thanks, but wouldn't there be more issues down the line with a debranded phone? What if I soft-bricked my phone, it seems like it'd be really hard to restore? Has anyone actually ever done this on a BLN-L24?

Hello all,
I too am having issues with flashing roms to this device, US variant (BLN-L24). In my particular case, the rom boots up (EliteRom v7.1) and will actually function. However, wifi does not work, as well as I have no sound whatsoever. Youtube also will not play, nor will any videos, which I'm guessing is tied to whatever issue is with the sound. I have flashed multiple times per the step by step instructions, as well as following the Youtube video, all with the same result over the last few days. At this point, my phone is effectively useless to me, though cellular data does still work, just no calls can be answered. Anyone have any suggestions I might be able to follow? Also, even my TWRP backup that I made before installing the rom will not restore at this point. Any help is appreciated, thanks.

Jessooca said:
You must be missing a step or something, because [Elite ROM][EMUI 5.1] Elite ROM v7.1 for Honor 6X by HassanMirza01 works on the L24 us variant without issues, I have none.
Perhaps go back to stock and start over. I haven't had any issues with his rom and I didn't do anything more than what's needed to root/install twrp and flash the rom per his instructions.
Click to expand...
Click to collapse
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop

i4ybrid said:
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
Click to expand...
Click to collapse
On one of the attempts that I did for installing, I installed the patch and it put me in a boot loop. Maybe not installing the patch can help you?

I cant get anything to work for the US version. Sure stuff boots but some of it is just broken. On octOS i am unable to use root unless i switch supersu to automatically grant root to apps. I cant get root access by using prompt because nothing pops up. On crdroid i have the same exact issue. Id rather have the prompt than allow any app root access without my knowledge. With ELITE ROM my first boot brings up a home screen with no keyboard. It completely skips any kind of setup screen. I can get the setup screen by flashing a keyboard from an aroma gapps installer but then i lose google services. The US version also seems to be forgotten as for most roms you wont see it anywhere under supported lists.

I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?

code_name_duchess said:
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
Click to expand...
Click to collapse
It really sucks that nothing seems to work. Ive tried flashing using multiple recoveries and ive tried all kinds of flashing to fix issues with the ROMS. Nothing helps. If anyone has successfully gotten a ROM fully working on BLN-L24 they need to tell people exactly what they did step by step.

It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.

TurtlePwr82 said:
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
Click to expand...
Click to collapse
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing. Most recoverys say Open Kirin Edition when booting. What confuses me is why we need to debrand to get the ROMS to work. If the phone pretty much run on the same hardware then why is L24 having so many issues? Why are the devs not testing on these devices?

BakedOnSomeSour said:
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing
Click to expand...
Click to collapse
Right, that's what I was thinking. For any phone I've ever rom'd, there was always just one twrp that everyone worked from.
Edit: found this while looking through the roll back to stock forum. I don't know if it will help anyone else, but figured I'd put it here as well if it might. All credit for this goes to the original poster johnnyrichter:
johnnyrichter said:
Tried this method after being on LineageOS for a week or two and having poor LTE signal, no MMS, and voicemail issues so I'm trying to go back to stock so I can have a fully functional phone since I rely on it heavily for work. Followed all steps using BLN-L24 B360 firmware. On step 10 I rebooted to update and it went right to "5% Installing Update" and stuck there for 5 mins, then rebooted itself, has been sitting at "honor" boot screen for 14 minutes so I made it reboot to EMUI recovery, wiped/factory reset, rebooted, loaded EMUI afte 2 more minutes. Appears to have worked and hopefully my issues are fixed!
Edit: Signal, mms, and voicemail issues fixed.
Click to expand...
Click to collapse
Hopefully will benefit someone here as well.

When debranding the BLN-L24, and branding it to BLN-L21, are there any issues with the ROMs once they're installed? I imagine the radios, and such are different for the two models??

BakedOnSomeSour said:
Why are the devs not testing on these devices?
Click to expand...
Click to collapse
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?

galapagos said:
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
Click to expand...
Click to collapse
well, many don't want to give them a phone because most developers here tend to stop work on a ROM and leave people hanging.

I have gotten several ROMs working on L24 variant...
Yes it seems to me any Elite kernel based ROM works or should work on the L24. But /data must be ext4 format. Then even that the ROM works, the fingerprint scanner never allows a complete successful scan. I think because it must be f2fs format for that encryption to work or something. This is the link to those ROMS https://hassanmirza01.blogspot.com/p/custom-roms.html?m=1
On the other hand the LOS based ROMs never work or at least they reboot and the screen is always black or the ROM branding just stays there flashing. This sucks cause I want to run the newest Resurrection ROM but I ask the developer about why I have that problem or how long that ROM takes to boot and I never get an answer. He also just put a new beta AOKP ROM up and it does the same black screen thing too.
I am also suspicious it has to do with the version of TWRP. I think some are capable of formatting f2fs correctly or the encryption or whatever. Point is some of the devs need to be a little more consistent answering questions at a minimum. I know it takes time to fix bugs but give us a little heads up.

TWRP Freezes on 1st instal

I have asked on a few threads including the TWRP thread but no one seems to be answering for some reason so I thought I'd risk putting up a separate post to try and get an answer.
I followed the instructions to the letter on how to install TWRP from the thread and it installed all ok, the only problem is that the screen is totally frozen and there is nothing I can do to get it to work. I have now gone back to Oreo via Odin until I can get help on what's gone wrong. Would it make a difference if I tried from Nougut 7.0?
I have rooted and installed roms, TWRP's pretty often last year with my M10, M8 etc so I'm not that new to this but it's got me foxed this time.

Good question. I had an issue after installing CarHDROM, v9 for a bit where I could get into TWRP, but the phone would boot loop getting out of TWRP and I had a hard time getting back into recovery or download mode.
I re-flashed the phone and TWRP as well, and after that all was well. I did not change anything on the re-flash.
Sometimes things just get mux'ed.

Help needed. Bootlooped into recovery

Good day,
Help is needed..
I flashed TWRP on the phone since it was not long ago updated to version 10.3 (China).
It flashed well (without errors).
The reboot was successful. No data was lost.
In the morning I decided to check the email, turned on the WIFI, and it went off after 2-3 seconds (everything was OK in the evening, it worked like usually). I thought that restarting the phone would fix the flaw, but alas, I was stuck in BOOTLOOP. Starts with the Mi. LOGO, then goes out, then shows again and goes into Recovery. Recovery runs. All data can be accessed. Restarting is possible only into RECOVERY and FASTBOOT.
What could be the snag here and how to solve it?
P.S. Have tried 'dirty flashing' 10.3 and 10.2 versions from TWRP, changing the kernel (androplus 7-9), reflashing Magisk (recommended by some users on a russian forum), recovering the boot.img (since it it the only recovery I have got).. All that to no avail.
Bootloader was always unlocked since I bought it and rooted. It was MIUI v10.0 then.
MI MIX 3 8/256
Stable 10.3 Chinese ROM with twrp (10.2 before update, with root and twrp)
Had no root but unlocked bootloader

z1ldj1an said:
Good day,
Help is needed..
I flashed TWRP on the phone since it was not long ago updated to version 10.3 (China).
It flashed well (without errors).
The reboot was successful. No data was lost.
In the morning I decided to check the email, turned on the WIFI, and it went off after 2-3 seconds (everything was OK in the evening, it worked like usually). I thought that restarting the phone would fix the flaw, but alas, I was stuck in BOOTLOOP. Starts with the Mi. LOGO, then goes out, then shows again and goes into Recovery. Recovery runs. All data can be accessed. Restarting is possible only into RECOVERY and FASTBOOT.
What could be the snag here and how to solve it?
P.S. Have tried 'dirty flashing' 10.3 and 10.2 versions from TWRP, changing the kernel (androplus 7-9), reflashing Magisk (recommended by some users on a russian forum), recovering the boot.img (since it it the only recovery I have got).. All that to no avail.
Bootloader was always unlocked since I bought it and rooted. It was MIUI v10.0 then.
Click to expand...
Click to collapse
Back up, wipe, flash, restore

Ok. That was the one thing I tried to avoid, since my backup is 27G (nandroid) and internal storage is 133G..
Will try and feedback.

Hi all,
Got it back again, of course with all data and apps gone. I have done nandroid backups (since there is no other way of backing things up from TWRP, except copying everything) from recovery before starting the upper described process. I figure they are of no use to me now or are they?
Please advise

P.S. restoring from nandroids brought me back to square 1..

z1ldj1an said:
P.S. restoring from nandroids brought me back to square 1..
Click to expand...
Click to collapse
Something not right with your data so start over

Restarted, redone. Recovered only Data. Looks ok but works a little laggy..
Upd.: needed to set up the screen lock after had done that and a restart, all works like it was, except with a new OS version

Install TWRP from xiaomi.eu, the official one from here seems to be a lot more buggy.

Isopropil said:
Install TWRP from xiaomi.eu, the official one from here seems to be a lot more buggy.
Click to expand...
Click to collapse
I took it from twrp themselves, not bothering to search any forums. It's not like digging for gold or the like
Upd.:
I read that the official TWRP doesn't support some mounts migrating from EU to global or CN-->EU V Global. It was discovered that it has some bugs with mounting paths. People recommend the LR Team TWRP over the official because of that, besides it has more options under Advanced tab e.g.
Personally I prefer the one that does the job for the moment and is the latest, so it was an easy choice for me ? especially installing a fresh OS update.

How to downgrade HTC U11+ from Android Pie?

Already created thread in the wrong place https://forum.xda-developers.com/showthread.php?t=3952280
I have HTC U11+ TW version. Ever since I got the Pie update, my phone is freezing a lot. I need to force restart it 10+ times a day. I tried factory reset, clear cache, etc. Nothing works. I did not have any experience with flashing, but I have been reading a lot. I have my bootloader unlocked with S-ON.
My current build number is 2.15.709.1, since I wanted to downgrade, I tried flashing stock image HTC_U11+_TW_1.24.709.999_Images_OTA using fastboot (no TWRP). My phone went into a bootloop when I did that. I think this is because I can only flash an image with the same build number? Anyway, I flashed a HTC_U11+_TW_2.15.709.1_Images_OTA image and my phone is back to where it was, Android Pie (no bootloop), but still freezing a lot.
I found the HTC_DevInfo_Tool.zip tool on this thread https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481, but I am not sure if it will work on my phone.
Can someone advise what should I do to downgrade? Also did anyone face a similar problem after the update?

I found someone tried what I wanted to do here
https://forum.xda-developers.com/htc-u11/help/error132-signature-error-downgrade-htc-t3948079
Looks like it wont work?