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.

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?

Wifi issues after recent update

Hi. I'm running Q, rooted with the method described here:
https://forum.xda-developers.com/pixel-3a/how-to/root-3a-t3929053
Brief background is that the phone had been running fine for months, no wifi issues at all, both 2.4 and 5 GHz antennas working, but I stopped getting security updates after January 2020. Didn't like being that far behind on security updates, so I updated using this basic process:
1. Download latest stock factory image
2. Extract boot.img, copy to phone and patch using magisk, copy back to PC
3. Edit flash-all.sh to remove the -w (wipe) option
4. Run flash-all.sh, which flashed an updated bootloader.img, radio.img, and system image
5. Finally, flashed my patched boot.img
The process was successful, but since then I've had major wifi issues. 5 GHz just doesn't connect any more, period. 2.4 GHz will connect, but drops every few minutes. Every time I pick up my phone, I have to prod it a little and wait for wifi to connect, and even while actively using it, watching a youtube video or something, wifi just drops for a couple minutes then eventually reconnects.
Anyone else having this problem by chance? or more importantly, any suggestions on what I can do to fix it? Don't think it's a hardware issue because the phone was working damn near flawlessly before applying the July update.
Would appreciate any suggestions. Worst case I can wipe and re-install the January 2020 image, but would prefer to avoid that if there are any better options.
Thanks!

nitro32 said:
Hi. I'm running Q, rooted with the method described here:
https://forum.xda-developers.com/pixel-3a/how-to/root-3a-t3929053
Brief background is that the phone had been running fine for months, no wifi issues at all, both 2.4 and 5 GHz antennas working, but I stopped getting security updates after January 2020. Didn't like being that far behind on security updates, so I updated using this basic process:
1. Download latest stock factory image
2. Extract boot.img, copy to phone and patch using magisk, copy back to PC
3. Edit flash-all.sh to remove the -w (wipe) option
4. Run flash-all.sh, which flashed an updated bootloader.img, radio.img, and system image
5. Finally, flashed my patched boot.img
The process was successful, but since then I've had major wifi issues. 5 GHz just doesn't connect any more, period. 2.4 GHz will connect, but drops every few minutes. Every time I pick up my phone, I have to prod it a little and wait for wifi to connect, and even while actively using it, watching a youtube video or something, wifi just drops for a couple minutes then eventually reconnects.
Anyone else having this problem by chance? or more importantly, any suggestions on what I can do to fix it? Don't think it's a hardware issue because the phone was working damn near flawlessly before applying the July update.
Would appreciate any suggestions. Worst case I can wipe and re-install the January 2020 image, but would prefer to avoid that if there are any better options.
Thanks!
Click to expand...
Click to collapse
Hey, maybe something go wrong in your update process. To make sure its no issue on the official SW side, i would recommend to do a clean flash:
- backup all your important messaging stuff like whatsapp, telegramm, signal via inbuilt backup function.
- do a backup via the google backup function found in settings / sync photos via the google photos app
- if you have important files on your internal storage, do a backup of it on your pc / flash drive
- then, flash the latest factory image avaiable (use factory image, NOT OTA update) (dont use -w, to preserve data).
- After it setup your phone again. Patch the boot.img (extract it from the factory image you flashed) with magisk and flash it, install root (magisk).
This way you can ensure, that its not a SW error / bug from google.
When you want/need to manually apply a update, follow the instructions in the agisk thread for P3a: https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783
Really, thers is no need to flash the radio, etc files by yourself, just follow the instructions to preserve root and flash the ota.
It may take about 40mins of work, but you can be sure, that if the issue persist its not your fault.
Cheers!

Hi, bejunk. Thanks for taking the time to reply. I'm a little slow to respond because I was hoping someone else might chime in. Not that I don't appreciate your advice, but what you described is pretty much exactly what I did leading up to this point - flashing the latest factory image without -w to preserve my data. I also didn't really seek out to flash the radios myself, that's just part of the flash script provided with the factory image:
Code:
fastboot flash bootloader bootloader-sargo-b4s4-0.2-6355063.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-sargo-g670-00042-200421-b-6414611.img
fastboot reboot-bootloader
sleep 5
fastboot update image-sargo-qq3a.200705.002.zip
I guess I'll try wiping my data this time and trying again. Was hoping to avoid that. And failing that, flash back to the January image and see if that gets things working again, unless there are any other ideas.
Will post back the results.

Did a factory install again as mentioned, this time leaving -w enabled, and so far so good. Haven't noticed any wifi drops in the last couple of days, and I'm able to connect with 5 GHz again. No idea what failed previously, but glad things are back to normal now. Aside from that wifi issue, my 3a has been extremely reliable. Hated to see that record ruined.

I use to root everything from phones to tablets for years. But lately I've given it all up. I need reliability and security and you're not going to truly get that with some of these cooked ROMs. No matter how so-called reputable these chefs are. You really don't know anything about them.
Glad you got your situation fixed. I can remember going through the same thing many many times. Frustrating as hell.
Nylo

Android 12 Beta 2 GSI

Have anyone successfully booted Android 12 beta 2GSI?
I followed the guide from https://www.xda-developers.com/how-to-install-android-12/ multiple times, but every time Phones boots to fastboot.
Any Clue?

Having exactly the same drama with mine, either boots to existing system or bootloader. I flashed it back to stock on both slots and tried on each slot and booted to bootloader both attempts. next attempt was a factory reset and tried the dsu loader in developer options and still no dice, boots to existing A11 system every time.
I did have a brief trawl through the treble forum but didn't see much relating to a12 beta there, might have a better look another day as may be an answer in there somewhere.

(FIXED) Bootloader Locked but Device Won't Boot

I recently ran into the issue during custom rom work. I reflash the stock android ZIP, it starts booting, then I hard reset it with the power button and try to reach bootloader again. This, as it turns out, is terrible to do if you want a fast setup. The moment it starts and you reboot it, the boot image is corrupted (that's my guess) because escaping the boot screen during a clean flash bricks your phone. If you're reading this, it happened to you as well.
The answer is so flipping obvious and it took me an hour to figure it out - nowhere on the internet is there a "solution" for this problem, no matter how frequent it is. But there are lots of people who deal with this, whether still on their factory images (like the Pixel 3 EDL issue) or like me bouncing from custom to stock. So here's the answer:
ALL YOU HAVE TO DO IS SIDELOAD THE CURRENT SOFTWARE OTA OR A BETA OTA FROM ANOTHER FUTURE VERSION.
It doesn't recognize timestamps before your current software, so you'll need to assume you're on the latest of whatever you're on and do that. Future versions work as well, so if you wanted to reach 12 in one shot, your phone's bootloader would fully accept it as long as the file isn't corrupted. If you need a sideloading or flashing guide, here you go.
For me, I flashed the latest build of Android 11 (August patch) and rebooted during the boot up. What I did was download the OTA of the same exact file to my laptop, and entered adb sideload coral.xxx.x.zip. (The name of the file) It ran all the way through and it started up perfectly normal.
I hope this helps someone!
P.S. I don't have any pictures or tutorials, I only wrote this to help others understand what happened and how to fix it. Probably wouldn't have needed to say it if the forum for it existed.