Related
So it look like the JB OTA update is here for the USA. Mine is rooted, and has already download the update, but I haven't applied it yet, as I'm rooted and I don't know if I have to do something special first.....
Any one have any info on this?
Same Boat !!
Me too in same boat with P3113.See the post below yours :crying: Hope experts replies soon.
I went ahead and installed it on my daughters tab. CWM protected itself, and root. I'm still poking around, but thus far no issues beyond it says "update failed" but clearly didn't.
I'm wondering if I should remove CWM and unroot it first...
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Updated with Root ?
sheepdog elite said:
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Click to expand...
Click to collapse
So if i understand correctly , you allowed the OTA with root and it wiped data ? I am suprised it installed with Custom recovery !!!
I have over 200 user apps. Will i retain those Apps (dont mind data being wiped)
No, it didn't wipe data. I wasn't worried about it "if" it did, because it's my daughters, and I have TIBU for all her games from like last week.
Just to be perfectly clear. NOTHING went wrong. It installed the new O.S., booted fine, said the update failed, but the update didn't fail. Probably because CWM preserved root, and bootloader, so verification failed.
I ran it..... It updated thru CWM... Once done said update failed, but I had a new agreement to agree too. Sys info says its running 4.1.1.
If I have and issue, ill update here.
Failed for P3113
Based on your experience thought I would try too... Unfortunately failed miserably... I have Cwm 6.0.2.3 and attached is the crash log... Maybe some experts can give their views..
I guess I'll post my successful config just for the sake of comparison.
I'm currently running CWM 6.0.1.1. The tab was rooted with a file called gtab2_jellybean_rooter (think I got it from XDA, but i'm not positive) and had no other modifications/roms/etc.
If you're running any sort of ROM you're definitely boned, gotta wait for a ROM update. Beyond that, I'm not really sure what to say
To do the proper update, you should un-root and then re-root once done. That way you get the full support with your update if needed.
I am rooted, running CWM 6.0.2.3. I accepted the update and hit the install thinking that it would fail just as it does on a rooted SIII. The notification said the install had failed, but as others here have indicated, it appears as though the install was successful. I retained root and all seems to be normal; with one exception: It appears that the Tab no longer "sleeps" but shuts down completely. Regardless of whether I turn it off with the power button (short press) or if the screen simply goes to sleep, I have to long press the power button and it goes through a full boot.
Is anyone else experiencing this? Is there a setting I am missing? I am not a noob at rooting, etc. as I have been doing it since my OG Droid on Verizon, but it surprised me when the update seemed to install (even Google Now is working), and I am stumped about this "shut down" that seems to happen.
I experienced the same thing. I was rooted and had installed CM10, went back to original backup, using latest CWM. I hit system update and it downloaded the update, asked me to continue. CWM asked me if I wanted to install unsigned zip, I accepted, and it went through. At first boot it said update failed, but like everyone else, it went through. I have had no issues at all. My tab goes to sleep correctly.
Have peace in mind.
I finished updating (unfortunately, the battery was 9%, so I had to wait for an hour to charge before doing anything) and I got "failed" error like everybody got, but the system shows 4.1.1 and the performance is improved, and I applied root again.
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Try putting twrp back on and flashing stock Lollipop Rom. http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 You can also try aosp, cm12.1 or any other lollipop ROM.
The Lollipop OTA is very picky, I believe any modifications to the stock firmware will cause the update to fail. You will need to have a completely stock system for the OTA to install successfully. Find the correct KitKat firmware for your phone and flash it then try upgrading.
Hi.
I'm having a similar problem with te OTA being picky (topic here).
Is there a stock firmware "file map" so that we can check manually what is wrong and erase/add needed files ?
Maybe this could be done by checking a flashable stock rom ?
Thanks a lot guys.
EDIT : Found a solution here http://forum.xda-developers.com/mot...osing-apps-t2979971/post57658072#post57658072.
Worked perfectly !
OP, I am in the same situation. I did the same as you, and got the same results. Have you managed to solve it? It would be nice if you tell what you decide to do and what's the outcome. Thanks!
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Update to 5.1 success..... erm, well it's all relative
Eventually managed to update my XT1039 to 5.1 via ota.
Started with a fully charged phone and flashed 4.4.4 stock firmware (http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619).
Once completed, powered up phone and signed into google play then updated the motorola update services app.
DO NOT install a custom recovery or root yet or the update will fail!
Start the update by going into settings/about phone/system updates.
After first boot into 5.1, do a factory reset.
To root once the upgrade is completed, download cf autoroot (http://forum.xda-developers.com/moto-g/4g-development/root-xt1039-cf-auto-root-peregrine-t2942406) and unzip to a folder on your pc. Open a command prompt and change directory to this folder. Powerup handset in bootloader mode (hold vol down while switching on), connect USB and run 'root-windows.bat' from the command prompt.
So far I'm hugely disappointed in the update as I use WiFi tethering alot and it appears to be a massive fail. I know it wasn't 100% in 4.4.4 or CM12 5.1 with both reqiuring an occasional reboot, but in 5.1, something's just not right and it's basically unusable (could it be updated radio or something?). Fortunately, USB tethering appears flawless.
Another obsrvation seems to be abscence of a + appearing in the HSPA signal indicator, I seem to be getting just the H appearing regardless.
Also no more bluetooth visibilty timeout setting.
After installing CWM 6.0.5.0, I got gliches with the display in recovery mode but it works.
Now after I have it rooted, ad free and de-bloated, fixed the power on logo and installed CWM 6.0.5.0, I'll stick with it for a while to just to see how the battery lasts.
In hindsight I should've stuck with CM12 5.1.
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