I am having a really weird issue I'm hoping someone can help me out with. I was on 4.1.2 Clean ROM which was working great. I wanted to move to 4.3 Clean ROM (8.1 Core Edition). I did the upgrade and then flashed my modem to ML1 both via TWRP.
The ROM setup fine and ran great. However the first time I did a reboot, the phone gets stuck at the Samsung Galaxy S3 logo and never goes anywhere. I left it sit there for 30 minutes and it was hard locked. Only a battery pull would reset it. Through numerous reboots/pulls, the same thing would happen. I tried wiping Dalvik and Cache in TWRP and fixing permissions, to no avail. Reinstalling Clean ROM 8.1 via TWRP without formatting data did not fix the issue either. The only way to get my phone back up and running was a complete wipe and reinstalling from scratch. Then as soon as I reboot the first time, the issue comes back. I've tested this on a clean install - letting the phone go through the initial setup process but not installing or updating any apps - and it still happens.
So I moved on to try AllianceROM build 22, also a 4.3 build and wiped to do a clean install. No matter what options I choose in the setup, the same problem happens. Interestingly in AllianceROM I always get a acore process has failed error on the first boot.
Then I went to download the Knox-free rooted version of stock 4.3 available from Scott's website. I have the same issue with this. Also a wipe with clean install.
It's obvious there is something my phone doesn't like about moving from 4.1.2 to 4.3. In total, I have probably installed three different ROM's about 20 times now after the past couple days.
I've searched about this problem extensively and the only thing I found is a thread for the AT&T S3 that talks about this exact issue, and using Odin to go to stock 4.3 and loading a custom ROM to fix the issue. But I am under the impression that a 100% stock 4.3 will lock my bootloader.
What I plan to do next is use Odin to flash a stock 4.1.2, then go through the process of moving to a custom 4.3 ROM again.
If anyone knows of a tar'd version of 4.3 that won't lock my bootloader, I would be grateful!
If anyone knows of a different way to fix my problem, I would be grateful for that too!
Well I think I can declare victory. My phone is running Clean Rom 8.1 CE and has survived a reboot after every app install for a total of 15 so far.
As it turns out, I think being on TWRP 2.5 and trying to upgrade to Android 4.3 was the issue. Before I went the route of flashing a stock 4.1.2 release, I thought to check if my version of TWRP was the latest, and it was not. I flashed TWRP 2.7, and did a complete wipe and clean install of Clean Rom 8.1 CE, and it's running like a champ.
I know, I know...the install guide on most every ROM says to use the latest version of your recovery - until now I thought that was a "recommendation" or "best practice" and not a hard requirement. Turns out, at least for me, that it is very much a hard requirement. In reading the release notes for TWRP 2.6 and 2.7, they both appear to implement things specifically for Android 4.3 or 4.4.
Hopefully this info helps someone who may be having the same issue.
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.
Hello guys,
I was using CM12 (Lollipop 5.0.2) but I had some issues — my phone would very often reboot, sometimes for no reason as I wasn't even doing anything — so I wanted to switch ROM but wasn't able to install DU 5.1. TeamWin wouldn't work properly so I gave up. I then decided to at least upgrade to a more recent version of CM12, so I installed another recovery to do that, but it didn't work as well, so I put Philz back on my phone and tried to flash the exact same ROM I had before and now it won't install anymore and I'm left with nothing. Do you have any idea how I can get something back (and maybe then get an upgrade?).
Thanks in advance!
Edit: Ok, I got it to work again by downgrading step by step. CM11 Snapshot works but I'd like to get back upwards now and it still won't work even though I'm doing the same thing I did to get 5.0.2. :/
Edit 2: Now I'm back on 5.0.2, figured it out all by myself.
Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
QuesteU said:
Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried any of the CM based roms from xda ? You may only need to update your recovery. Both of these should work on your device
https://forum.xda-developers.com/ga...0-1r61-rom-resurrection-remix-v5-7-3-t3449444
https://forum.xda-developers.com/ga...m-unofficial-lineageos-14-1-gt-n51xx-t3533329
Latest twrp
https://forum.xda-developers.com/galaxy-note-8-0/development/recovery-twrp-2-8-5-0-t3035004
Good Luck
Sawdoctor
Hi!
Will try to be very brief.
So I've had the falcon xt1032 for 4 years now.
For the past 3 years I've used a custom ROM, Cyanogenmod then LineageOS. Never had any major problems, maybe a random reboot every once in a while due to a nightly rom.
About a month ago it started rebooting and freezing into a blue screen after reboot. Googled an XDA'd about it it looked like it was time to replace the phone.
I tried clean installing custom roms, nightly (Nougat 7.1) and stable (Marshmallow 6.0.1), and had the same issue (blue screen).
So I got a new phone.
I decided to change the bootloader to the original version and install the latest official release (Lollipop 5.1).
Used it for a week without a sim card and then put a prepaid sim card and it's been working ok for 2 weeks now.
What the hell could have happened?
For 3 years it worked ok with custom roms (stable and nightly). And now this.
Any ideas?
Thanks.
well all things aside, if you installed the stock ROM with fastboot, that sort of resets every issue supposedly introduced with using custom ROMs. who know maybe it is ready again for a bout of custom ROMs again