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.
Related
I have an HTC One S, rooted and unlocked. I downloaded CM10, attempted to update to it, yes without wiping(my fail) and sent the phone into a bootloop. In my attempts to fix I lost the ability mount the SDCard.
I did this to fix the SDCard and it worked - http://forum.xda-developers.com/showthread.php?t=1630459&page=12
I have tried to do the RUU update to bring it back to stock but it failed with error 171, USB Connectivity lost so I abandoned that idea. I did play with drivers, HTC Sync, reinstalls and registry cleanups all to no avail. This is the process I wanted to follow but no luck.....http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html
When updating with CM10 it installed VERY quick, like 20ish seconds. This seemed very fast so I thought maybe a different ROM would work and I went with Dark Jelly http://forum.xda-developers.com/showthread.php?t=1848100
No matter what I do I am stuck in the bootloop. Looking for any guidance available of things to try. I have searched all over and tried the solutions that make sense but to no avail.
Fixed
So I did this: http://forum.xda-developers.com/showpost.php?p=33857020&postcount=2181
delete that file and it booted right up. Have not looked at the Dark Jelly rom to see fi it has that file too but that may have been the issue with the other ROM as well.
Summary - CM10 contains that file that needs to be deleted before upgrading if you have hboot of low versions...I know, not very descriptive but its all in my posts above.
nvm, you got it.
(HTC One M8 on Verizon. HTC6525LVW.)
Hi everyone.
Got S-OFF Through the Sunshine method a few days ago.
No matter what custom ROM I installed I wasn't able to boot -- even messing with custom after flashing the lollipop firmware (this thread: ) I finally got my first custom ROM to actually boot last night (ARHD 40.3), only to find the roaming icon in the status bar, with no data after I turned off roaming.
I was worried that, according to one warning elsewhere, I may have corrupted my "NV partition," and that was causing the data problems. However, a quick NANDROID restore of my previous working stock ROM (w/root) booted with full cell service no problem. So that indicates that I don't have a corrupted NV partition.
Am I missing something simple within the ROM? I've rebooted a few times, the SIM gets recognized and I have my correct phone number, and I've tried the typical 2G/3G/4G auto options/selections in the mobile data settings...to no avail.
----
As an aside, everytime I exit/reboot with CWM (using cwm_v6.0.4.8_m8vzw-3.img ), it says "You may lose root. Attempt to regain root? (This process is irreversible...) yes/no. I'm wondering if this matters at all? I have root just fine inside my stock ROM, and full S-OFF, so I don't think it matters but I thought I'd ask just to be sure.
Related note: Is TWRP "better"? I did try to FASTBOOT flash recovery of the latest TWRP (twrp-2.8.5.0-m8_wlv.img) for my phone, but that recovery doesn't boot. (I saw an indication yesterday that I might just need to flash this TWRP recovery from inside a ROM or something...but in any case, the recovery seems to be working fine overall.)
----
My apologies that this isn't in the right thread(s) -- I haven't a lot of time before I go on a trip next week, and figured I would just post to see who could point me in the right direction.
Thanks in advance for all the help!
Everyone around these forums, myself included, seem to be using twrp and you did describe the current version number. I would first recommend figuring out how to get twrp installed. It's weird that you were unsuccessful getting it flashed with fastboot. To make sure, the device was recognized by "fastboot devices" and you typed "fastboot flash recovery <name_of_file>.img" right? You might also try finding a copy of the recovery that has been loaded into a 0p6bimg file that can be flashed automatically in the bootloader. I think captain throwback posted one for a user somewhere in this forum a week or two ago.
Did you flash the latest s-off ruu? You need the latest firmware for most of the current roms. That is likely why none of them boot.
...
Up to speed =)
Thanks to the first two posters! I did get TWRP finally installed (seems more capable than cwm), and did flash the firmware prior to posting the thread, but the ROMs still didn't install or work properly.
After flashing the latest RUU, I flashed SkyDragon, which seems to be working well!
Also have learned a lot more about the entire process...
Thanks again!
There does seem to be a snag with TWRP and the new 5.0 firmware. Seems like you finally got around it. I was newly S-Off and wanted to go from 4..4.4 to 5.0.
I went this route using the top firmware which has TWRP built in:
http://forum.xda-developers.com/showthread.php?t=2723159
Another issue is it must be flashed twice. For me it took three times. I also flashed the new radio although it may have already been in the firmware. The dev that posted the above also wrote your ROM so found a good match.
schneid said:
There does seem to be a snag with TWRP and the new 5.0 firmware. Seems like you finally got around it. I was newly S-Off and wanted to go from 4..4.4 to 5.0.
I went this route using the top firmware which has TWRP built in:
http://forum.xda-developers.com/showthread.php?t=2723159
Another issue is it must be flashed twice. For me it took three times. I also flashed the new radio although it may have already been in the firmware. The dev that posted the above also wrote your ROM so found a good match.
Click to expand...
Click to collapse
What version of twrp did you flash? I haven't had any issues flashing ROM's. Some of them do take a long time to boot at first.
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.
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.