Last year (around October I think) I got tired of having a custom "non-stock" ROM, so I flashed a stock Android 5.x using Odin (again, I think. it's been a while) and everything worked fine, except the stock Android updates. They would always leave me on the bootloader screen without actually updating anything, so I eventually gave up.
Recently though, I heard about the new Assistant feature coming to Android 6, so I obviously wanted to update. I figured it would be completely safe to flash a stock-like version of Android 6 with the TWRP recovery I already had installed, so I got LineageOS (version 14.1). I had previously wanted to install CM, but I didn't know that the OneM8 ROMs also work for E8, so I never got around to it.
When I got into the install phase in TWRP, I always got error messages (I don't remember them now though), so I though that maybe a factory reset or a few cache wipes would "make everything better." Well, I stopped getting the error messages, but when I tried to reboot to the system it sent me straight to the bootloader screen.
Current Bootloader Screen:
*** Software status: Modified ***
*** UNLOCKED ***
MEC_WHL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.09.20.0209
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-
eMMC-boot 2048MB
Aug 18 2015,17:23:12.22983
I tried reinstalling, but even though TWRP said "Successful" it still sent me back to the bootloader. Even factory resets don't work. I tried taking it to the Sprint store, just in case, but they predictably said they couldn't do anything because it was rooted previously.
I would really prefer fixing this phone before getting a new one, but I unfortunately need a working phone by this Friday. Any constructive suggestions are welcome and will be quickly tested
Which rom did you flash?
It seems that the boot.img is wrong.
Related
Allright, I've got S-OFF, it's rooted, and I've switched between Sense and CM7.1ALPHA's for a few times, but I'm mainly using Sense (CM just isn't stable enough, yet ), and since the latest OTA update, I'm looking for ways to install that, though simply following http://forum.xda-developers.com/showthread.php?t=1228648 does not work because there doesn't seem to be any TMO_NL ruu for the sensation.
I've tried using the EU version from the previously mentioned thread, but that failed at
"7. When the application finishes flashing, press <No> which will reboot into recovery."
I pressed no, but it did not go to recovery, instead it siimply rebooted, and it looked like it had reset itself to factory settings.
I tried to download and install the OTA update anyway but to no avail.
I've heard about unbranding by changing the CID, will this make me able to use other recovery images to then install the OTA?
Current Software number: 1.45.114.1 / TMO_NL_1.45.114.1
Carrier: T-Mobile NL
Desperate bump.
I was using an older ViperXL ROM and loved it. I decided to update to the latest Full ROM currently posted here. Followed the guide from that thread. After completing the process seemingly successfully, I cannot use the device anymore. It has been continuously rebooting for over 12 hours. I left it trying overnight to see if it would eventually gain sanity... no joy. I can force to the TWRP configuration choices and have tried a couple of times with the .zip file that I validated for MD5 hash for ViperXL.
I have been choosing to omit a bunch of the apps such as Facebook, Twitter, etc. during the process. Just mention this in case there might be some interaction with the omission process.
Advice?
You haven't provided your bootloader details, we need those please, the first five lines.
Sent from my Evita
Flashing with some twrp versions and some boatloads is problematic. I had a similar issue. S-off fixed everything right up.
So... Are you s-off?
That's what I was getting at when asking to see the bootloader details. Also need the other details as well as the s-on/s-off status.
Sent from my Evita
Thanks. Issue resolved by reloading the image.
Thanks to all who tried to help. Issue resolved by reloading the image from scratch. Interestingly enough, I recently decided to go back to stock with the HTC RUU for AT&T load because I needed to get the new HBOOT which is included. The RUU process went seemingly flawlessly but got stuck in the same type of continuous reboot for more than 11 hours as well. I went back and reapplied the RUU and everything is fine now too.
Hello. I decided to start a new thread. I have a Moonshine s-off phone. Recently I reset the phone put stock recovery on it and ran the newest RUU. It worked I got the new software[emoji3] . Then I unlocked the phone using the HTCDev method and my old unlock key, everything worked, when I went into BOOTLOADER phone said TAMPERED UNLOCKED S-OFF.
The only thing missing is my camera. Sometimes it turns on, but very rarely ( maybe 1/200 tries ). It tells me Unable To Start The Camera.
I think it's a software glitch, as with previous version of Android I had no issues. Also with the new OS the flash is BUSY sometimes. When I want to use a flashlight phone tells me PHONE SCREEN WILL BE USED FOR ILLUMINATION SINCE THE FLASH IS IN USE BY OTHER APP. There is no other app running...
I tried flashing TWRP but fastboot just hangs, I left it on for 3 hours and it never finished. I tried using the SD IMG method. It goes thru, tells me to reboot. When I do I'm on the same stock recovery...
I have backups of my phone. But they are all done with TWRP and I can't install it. I tried CWM as well, same result, timeout.
I might try running a lower version RUU and see if that fixes all...
It's been a long night and I'm at a complete loss as to what to look for next...
Around 9PM last night, my phone randomly rebooted... it's done this a few times before, and i thought nothing of it. When it finally booted back up, I was at the "choose your language" setup screen. WTF.
I lost literally EVERYTHING.
FYI, this was on stock rom, and I didn't even have the OTA(s) because I was rooted and was content with 4.4.2
Well, since all my data was gone, I figured it was about time to see what I could get with a custom ROM. The phone's been sluggish lately, so I figured a bloat-less upgrade would help.
Long story short, I loaded the 5.1 firmwares for VZW, and the HBOOT as well, and flashed GPE_5.1 on it. It took it like a champ, but refused to boot. I tried changing the kernels during the GPE install, but none of them worked. Some would loop, some would kick me into recovery, and one would just stall and the animation would run forever. No worries, I'm sure I can go to a stock 5.x rom! But that's a big NOPE. I just get "installation aborted" with no reasoning or errors in CWM (I had TWRP at one point as well, and it didn't get me anywhere either) Or I get "symlink: some symlinks failed" ... it depends what rom i'm flashing.
I've tried stock and custom, rooted and not... literally nothing will take.
ALSO, in my attempts to remedy the problem, I tried to reflash the firmware, but fastboot starts that there's not enough space. A quick google search pointed to "not enough ram in the PC" which is BS because it's done it on 2 different systems, both with 16GB ram, one running Win8.1 and the other Win7.
To top it all off, somehow I relocked the phone (but i still have S-OFF) and without being able to boot into the OS, I can't unlock it with SunShine/Firewater.
Hopefully, someone can point me in the right direction...
Welp... It's working now...
Not 100% sure what I ended up doing that worked, but I was able to run the unlocker via creating a new unlock_code.bin from htcdev and ran that with the all in one toolkit.
From there, I was able to use the toolkit to flash a stock ruu rom (I flashed the 5.0.1 RUU, but when it booted, I was still in 4.4.2)
It apparently didn't like somwething in the boot order other than the ROM itself.
I'm now running S-OFF, relocked but rooted 5.0.1 after it took several OTAs. Not sure how many more OTA's are pending, but it just keeps prompting me lol...
At this point, I'm just happy it's booting, stock or not. I don't even know what recovery I'm running at this point...
Did you update your recovery??? To the latest one
Sent from my HTC6525LVW using XDA Premium 4 mobile app
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.