(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.
Related
I've been doing research on this for a while, and I decided to sign up and ask about this question. Majority of the topics here dealing with bricking either have solved it because of access to fastboot, or some users have given up and either retired their devices or sent them in to ASUS.
Long story short, I installed Clockwork Recovery Mod and Cyanogen mod with no issues. After a couple of weeks, I decided I wanted to go back to stock. I did some research and found a topic which said I needed TWRP in order to flash back the stock ROM. I installed TWRP, but some things seemed to have gone awry with that install and I no longer have access to the fastboot menu and the tablet keeps booting straight into recovery.
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2). So far, I think I can get it back on track if I could somehow install a new recovery, or start my device from scratch somehow.
Also whenever I transfer to device memory, if I reboot the tablet, everything gets erased and the log is littered with errors about not being able to find and mount /data. From what I've read, it should be solved with a simple format of the file system. However, all of my attempts to use the recovery's built in wiping/formatting tools have ended with no success. If I put in a microSD, that gets wiped as well so in order to load a ROM, I have to push it using adb.
I thought I had fully bricked it, but it seems that since it's accessible through adb, it's still somewhat fixable. I know about backing up everything with nvflash, now, I guess I just didn't do enough research before getting into this. Any ideas, feedback, is appreciated, so far I'm learning a lot about android devices from this experience.
lino4 said:
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2).
Click to expand...
Click to collapse
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
_that said:
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
Click to expand...
Click to collapse
Yeah I found that thread not too long ago, I pushed the bootloader and was able to load the stock rom and get everything going.
Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
branmuffin17 said:
Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
Click to expand...
Click to collapse
The phone with the red triangle is what you are supposed to see. When you see that, you need to hit Vol-Up + Vol-Down and Power and it will take you into recovery. With that, you should be able to do the OTA to 4.4.3. I'm not sure if you need to flash the 4.4.2 firmware first or not. You can give it a try. If it fails then go ahead and flash back to the 4.4.2 firmware from Tigerstown's thread and try it again.
branmuffin17 said:
Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
Click to expand...
Click to collapse
SCrosler has posted a stock rooted 4.4.3 ROM. If you flash that you will all up to date (or you could flash Viper 2.4 or NuSense 2.0) essentially flashing any 4.4.3 ROM will get you where you want to be.
Here is the link to the stock, rooted ROM: http://forum.xda-developers.com/ver...m-stock-rooted-vzw-ota-2-21-605-2-wp-t2874699. With your updated firmware and that ROM you will be stock, and up to date on 4.4.3
@BladeRunner & @jsaxon2, thank you very much for your replies and the help. Looks like this was covered to some degree, and has answered my questions.
Going to try dirty-flashing the ODEX rom. I want to flash Viper pretty badly, but don't want to have to wipe everything right now. When Android L comes out, that will be fully worth starting from scratch. I have just enough patience to wait.
Will confirm shortly that everything has worked.
FYI, dirty flash of the ODEX (just wiped cache/dalvik, left data alone) worked perfectly. Software is now reading 4.4.3. Thanks to @scrosler for the stock ROM!
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 have an HTC One M9 (Sprint) software version 2.11.651.19 (OPJA2) with Android v5.1
Within the last couple months I unlocked the devices bootloader, and rooted it. Last night I left the phone under my laptop and I'm thinking it got way way way too hot, somehow the thing is still alive, however when I went to turn it on in the morning, I had no wifi or cellular capabilities. At first I assumed this was a hardware issue, however I then unrooted the device on a whim, and this fixed it (Until I turned it off again, to my dismay).
I'm thinking somehow my phone overheated (Which explains why my battery life won't go over 47%) and somehow my flash memory must have been corrupted because I can no longer boot into recovery mode, which is my serious catch 22. Since I figure this is some issue related to my firmware, which I would LIKE to reflash (This is my goal here). To my dismay, in order to flash a stock RUU or firmware to the device, you must have your bootloader relocked. However in order to relock your bootloader you must have root, and like an idiot I unrooted it. I can't reinstall SuperSU through my TWRP recovery because my phone refuses to boot into recovery mode. I attempted to re-flash TWRP to the device through download mode, the flashing is completed successfully, however I still cannot boot into my recovery. To break it down simply:
-Want to reflash stock firmware
-Must have root to reflash stock firmware/RUU
-Don't have root because I uninstalled it
-Can't re-root because my recovery is corrupted
-Can't re-flash TWRP (Already tried and it's not working)
-Can't re-root because I can't flash TWRP
-Can't reflash stock firmware because I can't disable it with root
Regardless of this I attempted to use adb and echo to relock the bootloader however instead of getting # I get $, so I'm not really able to do this either. Is there ANY way I can repair my recovery, has anyone ever run into an issue like this before? Or am I just completely screwed, hahaha.
Do you think I might be able to reflash Android V5.1 to try and fix the corruption and then maybe that would allow me to get into recovery mode so I can flash Super SU so I can at least factory reset my device with TWRP, or possible reload stock firmware and factory reset from there?
Thanks guys for any help you can provide.
*EDIT
If anyone wants to provide any advice great, but for now I'm going to try using HTC Sync Manager to load Marshmallow (v6.0) onto the HTC and see if this may allow me to actually get into recovery mode. Downloading the file from here: *nevermind can't post links yet, under 10 posts, you can find it on HTC's website* (This is for the HTC One M9, Sprint) in case anyone else EVER has to run into this awful issue, lol.
Moderators please feel free to update the thread to SOLVED status, I was able to update my phone to marshmallow to resolve the issue. This time around I WILL be backing up my phone, probably not going to root it this time around either, I have like 3 other phones so I'll just root them instead, lol. If you would like the download link I am happy to provide it VIA PM so you can update my OP with the link for the full fix. My phone is able to get wifi and texts now without an issue, unfortunately all my data is wiped but honestly I don't really care!!
Thanks everyone!
Good job on solving your issue.
If you have further questions or want to help out others, you can do so here
http://forum.xda-developers.com/sprint-one-m9/help
http://forum.xda-developers.com/sprint-one-m9
Thread closed