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
Related
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.
after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.
Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.
DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way
First off, I have a Verizon GS3 (SCH-I535). As of this morning, it was running the new 4.3 standard (no root, no unlocked bootloader, no custom recovery). I didn't like some of the UI changes in 4.3, and since I wanted to try custom ROMs out anyways, I figured now would be as good a time as any.
After doing hours of research, I was able to successfully get my phone rooted and TWRP installed (using the GooManager app). I had the AOKP d2vzw rom (milestone 1) downloaded and on my phone. I then tried to use GooManager to install the ROM. The phone rebooted into download mode, then gave an error message. I think I didn't properly unlock the bootloader.
After that, the phone wouldn't boot to a ROM at all. I've been trying to install stock ROMs using ODIN and was able to get the stock recovery back, but now all I can get to is the stock recovery and the Download Mode. Whenever the phone boots normally, I get the message, "System software not authorized by Verizon Wireless has been found on your phone . . ."
The biggest issue I've had is that it seem like nothing will install properly using ODIN. When trying to flash TWRP, it fails after NAND Write Start!!. When trying to flash a bootloader, it'll give a write/fail after aboot.
At this point, I'll be happy just getting it back to a working ROM. Any help would be appreciated.
WhiteRabbit44 said:
First off, I have a Verizon GS3 (SCH-I535). As of this morning, it was running the new 4.3 standard (no root, no unlocked bootloader, no custom recovery). I didn't like some of the UI changes in 4.3, and since I wanted to try custom ROMs out anyways, I figured now would be as good a time as any.
After doing hours of research, I was able to successfully get my phone rooted and TWRP installed (using the GooManager app). I had the AOKP d2vzw rom (milestone 1) downloaded and on my phone. I then tried to use GooManager to install the ROM. The phone rebooted into download mode, then gave an error message. I think I didn't properly unlock the bootloader.
After that, the phone wouldn't boot to a ROM at all. I've been trying to install stock ROMs using ODIN and was able to get the stock recovery back, but now all I can get to is the stock recovery and the Download Mode. Whenever the phone boots normally, I get the message, "System software not authorized by Verizon Wireless has been found on your phone . . ."
The biggest issue I've had is that it seem like nothing will install properly using ODIN. When trying to flash TWRP, it fails after NAND Write Start!!. When trying to flash a bootloader, it'll give a write/fail after aboot.
At this point, I'll be happy just getting it back to a working ROM. Any help would be appreciated.
Click to expand...
Click to collapse
When you are on 4.3, you can't unlock your phone anymore. That means no AOSP roms, but you can still use custom touchwiz roms based on 4.3. You're softbricked and you have to use this thread to fix it.
http://forum.xda-developers.com/showthread.php?t=2586319
After that completes, you can use this to root.
http://forum.xda-developers.com/showthread.php?t=2565758
Once you're rooted, this is the only recovery you can install, don't flash any other recovery.
http://forum.xda-developers.com/showthread.php?t=2605648
Read up on all the threads, 4.3 is completely different then 4.1 was.
Sent from my SCH-I535 using Tapatalk 2
Extra Info:
With Odin, I have made sure Kies is uninstalled. I've also tried multiple USB cables, including the ones the phone came with, and I've tried almost every USB port on my computer. Whenever Odin fails, it's in the exact same spot every time, which makes me think it's a software issue, not a hardware issue.
EDIT:
I was actually able to get the stock.vzw-root66 ROM installed by Odin without any errors. The phone rebooted immediately, then showed the android robot with the blue spinny thing in his chest, then the phone went back to the same Verizon error message.
BadUsername said:
When you are on 4.3, you can't unlock your phone anymore. That means no AOSP roms, but you can still use custom touchwiz roms based on 4.3. You're softbricked and you have to use this thread to fix it.
http://forum.xda-developers.com/showthread.php?t=2586319
After that completes, you can use this to root.
http://forum.xda-developers.com/showthread.php?t=2565758
Once you're rooted, this is the only recovery you can install, don't flash any other recovery.
http://forum.xda-developers.com/showthread.php?t=2605648
Read up on all the threads, 4.3 is completely different then 4.1 was.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This worked like a charm! Thank you. I admit I am fairly new at all of this and did a ton of research beforehand, but I apparently did not research the differences between 4.1 and 4.3. You saved my butt!
WhiteRabbit44 said:
This worked like a charm! Thank you. I admit I am fairly new at all of this and did a ton of research beforehand, but I apparently did not research the differences between 4.1 and 4.3. You saved my butt!
Click to expand...
Click to collapse
TW 4.3 discussion thread has most info consolidated in one place:
http://forum.xda-developers.com/showthread.php?t=2575661
Sent from my SCH-I535 using Tapatalk 4
(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.
First; I hate to be a double poster, but I'm on the back page of How to Upgrade to 5.0.1 and Keep Root. My apologies. I've spent several days trying to solve this and have no answers.
I did the 5.0.1 "Keep Root" when it first came out, but it acted buggy and unpredictable. I just got a Note 4, and hate that I can't root it, so I decided to try to resolve the problems with my S4. I re-did the process, as stated and it seemed to work fine. I downgraded, rooted, and upgraded to 5.0.1. Then the trouble started. I installed the "Stock" Kernel, Modem, and Recovery. When I rebooted; it gave me a nasty message like: "AT&T has discovered unauthorized software on your phone." and froze up. I booted back into download mode, re-flashed the NB1 file, and it seemed to work, except for no Wi-Fi. When I tried to re-flash the OC4 with Flashfire, it acted like it was going to do it, but only booted into the recovery screen. I've tried close to a hundred different combinations, but no joy.
It allows me to root the NB1 and install Flashfire, but cant get it above 4.3. I installed a terminal emulator APK file and checked my bootloader status and it shows OC4. If my understanding is correct; I'm screwed. Is there any way to get past this and upgrade to ANY working ROM that will allow Wi-Fi and be fairly stable?
BTW; I'm on AT&T.
Thanks in advance!
As far as I'm concerned, ODIN just puts back your phone to its original state. Have you tried following the guide on how to install a custom Lollipop ROM? You gotta flash a rootable NB1 firmware and then continue with the process explained in the thread.
Here, take a look and tell me how it goes http://forum.xda-developers.com/galaxy-s4-att/general/how-to-installed-custom-lollipop-rom-t3135396
Crash and Burn
Crash and burn. NB1 wouldn't think of loading with Odin. Fails almost immediately.
Thanks for the help, though. Any other ideas?
Here's a screenshot of my phone parameters.
http://dl-1.va.us.xda-developers.co....png?key=Hy1bNEcEPo2F55Cm_pjqYg&ts=1450058617
Guess it won't upload my photo...
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.