I'm trying to go back to 5.0.1 from 5.1. 5.1 works ok but my favorite app no longer works (Puzzle and Dragons).
I flashed 5.1 by flashing bootloader, radio, boot, recovery and system images followed by fastboot format cache. The upgrade was no problem at all.
Now I'm trying to downgrade back to 5.0.1 and the same steps do not work. I just get the endless animation loop. I would like to keep what I have installed (no wipe).
Anyway have a good way to do this downgrade? I'm practically stock other than unlocked.
flintdragon said:
I'm trying to go back to 5.0.1 from 5.1. 5.1 works ok but my favorite app no longer works (Puzzle and Dragons).
I flashed 5.1 by flashing bootloader, radio, boot, recovery and system images followed by fastboot format cache. The upgrade was no problem at all.
Now I'm trying to downgrade back to 5.0.1 and the same steps do not work. I just get the endless animation loop. I would like to keep what I have installed (no wipe).
Anyway have a good way to do this downgrade? I'm practically stock other than unlocked.
Click to expand...
Click to collapse
It may be a data conflict with system apps, if flashing system.img and boot.img doesn't work. Try booting into a custom recovery then deleting the /data/data/whatever.app folder of some system apps such as SystemUI, framework, Settings.
Otherwise, you'll have to clean flash.
Elluel said:
It may be a data conflict with system apps, if flashing system.img and boot.img doesn't work. Try booting into a custom recovery then deleting the /data/data/whatever.app folder of some system apps such as SystemUI, framework, Settings.
Otherwise, you'll have to clean flash.
Click to expand...
Click to collapse
Seems like some guesswork?
flintdragon said:
Seems like some guesswork?
Click to expand...
Click to collapse
After you booted 5.1, app data would have been "upgraded" to accommodate the changes. This operation probably won't work in reverse, hence your bootloop.
Restore nandroid of 5.0.1.
Or make a backup of all your apps with TiBu, flash 5.0.1 and factory reset then restore user apps.
Aerowinder said:
Or make a backup of all your apps with TiBu, flash 5.0.1 and factory reset then restore user apps.
Click to expand...
Click to collapse
Thanks. I had to resort to this. The factory reset was also critical. I thought running the flash-all.sh script would clean everything up but apparently it doesn't.
Related
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
You can always flash the factory images here: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You can flash any ROM and that should fix your issue
You will not lose your unlocked bootloader unless you flash the stock one which is in the factory images
Your bootloader will not relock unless you lock it yourself using fastboot. Flashing roms or factory images won't lock it by themselves.
And even if it somehow did, one fastboot command and you're unlocked again.
And as far as root goes....it takes 5 minutes to reroot.
So just flash whatever factory image you need and then custom recovery, and you're done. Maybe need to download superSU from play store after.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
justinisloco said:
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
Click to expand...
Click to collapse
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
xfranchize said:
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
Click to expand...
Click to collapse
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
vin4yak said:
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
xfranchize said:
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
Click to expand...
Click to collapse
Maybe your flashing a bad version of GApps since the force closes are on google Calander?
Are you using a 4.4.2 GApps?
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
gee2012 said:
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
Click to expand...
Click to collapse
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
xfranchize said:
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
gee2012 said:
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
Click to expand...
Click to collapse
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
gee2012 said:
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
Click to expand...
Click to collapse
Okay ill give it a shot, thanks alot. Ill update here if im successful.
Sent from my Nexus 5 using Tapatalk
Hi guys, can somebody help me? I received the stagefright update this morning and after downloading it and rebooting, the phone stopped working. It shows the logo animation for a few seconds then the screen goes black. It's a rooted and unlocked phone so i don't know if thats the cause. Also, i can access the recovery mode pressing power and down. Other than that nothing.
If you were rooted and updated ya..the rooting may be the reason
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Jaydeep123 said:
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Click to expand...
Click to collapse
I always forget how peacefull people with knowledge can be. Thanks mate, will do that.
But, just for curiosity: rooted phones tends to have problems after updates?
Yes It may get error or Somthing Else Thats Why I prefer if a update is avaiable flash back to stock and then proceed
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
reinaldojr said:
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
Click to expand...
Click to collapse
Mod will move or merge.
Sent from my MotoG3 using XDA Free mobile app
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
hp420 said:
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
Click to expand...
Click to collapse
Hello HP429; reflashin full factory image would effectively wipe phone
sunandoghosh said:
Hello HP429; reflashin full factory image would effectively wipe phone
Click to expand...
Click to collapse
Not if you only flash the system, boot and recovery image files
Recover the factory
I did the update and as mentioned previously on the thread stales after the logo. (bootloader is unlocked)
I can not find my oem backup. I tried twrp on recovery and was able to backup other stuff. Is there a way to generate the OEM so that i can flash or any other roms that are compatible with Moto G 3rd generation?
Try wiping cache, dalvik cache and data with TWRP. Don't use stock recovery for the data wipe or you will lose all the files stored on your internal partition, as well.
Ok guys I'm stumped on this one. I got the OTA notification for 5.1 yesterday on my XT1034 and so I decided to preempt any issues I might have and just flash everything back to stock 5.0.2 in order to install the update.
I was able to flash everything fine then went to reboot, got the unlocked bootloader screen and...... nothing. It just stayed on the unlocked bootloader screen. I figured I did something wrong so I reset back to fastboot mode, tried again and sure enough I missed sparsechunk 3. So I tried again, restarted, and.... same thing.
OK then, reset again and reboot into recovery mode. It booted to the Motorola splash screen, ok this is different..... nope still not loading. Reset again and try flashing a custom recovery.
CWM, flashed ok, reset again, Moto splash
TWRP, flashed ok, reset, Moto splash
Philz, flashed, reset, splash
OK.. so I'm clearly doing something wrong. Did some research and tried:
- formatting the cache and userdata partitions
> cache formatted fine, userdata refused to format, not supported for filesystem type 'raw'
- tried flashing again without erasing the partitions
> flashed fine, no change in booting
- tried flashing back to 4.4.4
> flashed fine, no change in booting
- tried flashing all the custom recoveries with 4.4.4, no change
- I found a thread where someone else had a somewhat similar issue, and apparently resolved by unlocking their bootloader
> mines already unlocked, but sure it can't hurt, tried again, but nothing since it's already unlocked
I looked for anyone that had a stock 5.1 image other than the OTA, but couldn't find anything. I gave up on trying stock and looked at some custom roms, but all of them just start with, unlock your bootloader, load a custom recovery and flash the update zip file.
Soooo I'm stumped. I've tried just about everything I can think of. I made backups of everything so I'm not worried about the data I just want a working phone again. I refuse to accept that it's borked at this point since I can still get to fastboot.
OK so, no clue what changed, but I was finally able to boot into recovery, Philz
I wiped and reformatted everything and tried flashing 5.0.2 again
rebooted and it still hung on the bootloader unlocked screen
I'll try flashing Philz again and updating through there
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
tapman said:
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
Click to expand...
Click to collapse
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Umer520 said:
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Click to expand...
Click to collapse
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
moralesnery said:
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Click to expand...
Click to collapse
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
tapman said:
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
Click to expand...
Click to collapse
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
tapman said:
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
Click to expand...
Click to collapse
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Umer520 said:
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Click to expand...
Click to collapse
Yeah unlocking your bl doesn't affect ota's
moralesnery said:
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
Click to expand...
Click to collapse
I think at least in part what my issue was, was that the partition formatting got borked. If you can boot to a custom recovery you can wipe and reformat them. Then you should be able to reflash it normally.
I was just so tired of dealing with my phone at that point so I only tried once and gave up with stock, but I'm pretty sure that's what I need to do to fix it.
Edited the build.prop file by adding 1 line, restarted phone and now I keep getting System UI has stopped message.
Any way I can edit the file to fix my phone?
Have you tried to clear the cache in recovery? If that doesn't work, try a full factory reset.
If the phone is running a stock rom, try flashing just the system.img file in fastboot.
Before doing any of this, make sure you backup your data.
audit13 said:
Have you tried to clear the cache in recovery? If that doesn't work, try a full factory reset.
If the phone is running a stock rom, try flashing just the system.img file in fastboot.
Before doing any of this, make sure you backup your data.
Click to expand...
Click to collapse
Thank you, I ended up backing up the data and cache via USB, then did a flash of Cataclysm ROM. I'll let you know if it works.
Can I just restore the data ASAP after installation or do I need Google to finish restoring my backup first?
Edit: Well, restored data, stuck with the boot screen loop again, then goes to Android is upgrading... and shows it optimizing 10 apps, and back to the boot logo.
Did the phone boot without restoring data?
audit13 said:
Did the phone boot without restoring data?
Click to expand...
Click to collapse
No, I made sure it was completed.
Now Play Store keeps quitting when I try to install apps. I can only install specific ones.
I recommend flashing a stock rom to make sure there isn't a hardware problem. Don't restore anything until you are sure the phone works.
audit13 said:
I recommend flashing a stock rom to make sure there isn't a hardware problem. Don't restore anything until you are sure the phone works.
Click to expand...
Click to collapse
Alright, I was able to get all my apps installed besides United Airlines and can't update Chrome.
So the stock rom works fine?
audit13 said:
So the stock rom works fine?
Click to expand...
Click to collapse
Yes, thank you.
I don't think I want to do another custom ROM for now.
The stock rom is the best with the bloat taken out .I think the kernel can be improved though. I use EX
Throughout my phone's lifetime, I've made a lot of backups, most of which have ended up saved on my hard drive. I recently wanted to go back to stock from a custom rom, so I copied one of the emui backups over and restored to it. Everything seemed to go smoothly, no error messages, but attempting to boot only got stuck on the blue honor boot animation. Tried several other backups, some rooted and heavily customized, some fresh unmodded installs, but all of them did the same thing. Meanwhile, all my custom rom backups work just fine. What gives?
I tried it too and it doesn't work. I think its because to install a custom ROM we format the data using twrp which also removes the encryption of some sorts, when we restore the backup that encryption is lost so it stays stuck at the blue Honor logo. That's my two sense on this. I don't know the real details.
asaditya379 said:
I tried it too and it doesn't work. I think its because to install a custom ROM we format the data using twrp which also removes the encryption of some sorts, when we restore the backup that encryption is lost so it stays stuck at the blue Honor logo. That's my two sense on this. I don't know the real details.
Click to expand...
Click to collapse
That does make more sense than anything I've thought of so far. So to restore from one of these backups, would I just have to reinstall emui from scratch first to get that encryption back? Is there another way to restore them without first having emui? Or are they just useless now?
Gannondalf said:
That does make more sense than anything I've thought of so far. So to restore from one of these backups, would I just have to reinstall emui from scratch first to get that encryption back? Is there another way to restore them without first having emui? Or are they just useless now?
Click to expand...
Click to collapse
I haven't been able to find a solution to this. What I do is use firmware finder to download the firmware+region zip and then install them together in any order via twrp. By this process you lose the data and twrp too as it is replaces by stock recovery. Before booting you must try to get into the stock recover and hit factory reset. You'll get EMUI back but no matter what you do you won't get your data back. Twrp backup is helpless I think because I've tried all sorts of things to get my data back.
asaditya379 said:
I haven't been able to find a solution to this. What I do is use firmware finder to download the firmware+region zip and then install them together in any order via twrp. By this process you lose the data and twrp too as it is replaces by stock recovery. Before booting you must try to get into the stock recover and hit factory reset. You'll get EMUI back but no matter what you do you won't get your data back. Twrp backup is helpless I think because I've tried all sorts of things to get my data back.
Click to expand...
Click to collapse
I've tried flashing emui firmware through twrp before and the region zip always works, but I've never gotten it to load the update.zip (using adb sideload for everything). But I'll try a few different things and see if I can get that to work. Getting back to emui is my primary focus since most of my data is backed up somewhere else, but if I find a way to successfully restore data from backups I'll let you know.
Gannondalf said:
I've tried flashing emui firmware through twrp before and the region zip always works, but I've never gotten it to load the update.zip (using adb sideload for everything). But I'll try a few different things and see if I can get that to work. Getting back to emui is my primary focus since most of my data is backed up somewhere else, but if I find a way to successfully restore data from backups I'll let you know.
Click to expand...
Click to collapse
What I'm telling is probably the easiest way let me break it down for you again.
1. Download firmware+region zip file from firmware finder.
2. Go to twrp, clear everything (format data).
3. Install the two downloaded zip I usually flash firmware and then the region zip.
4. After installation is over don't reboot go back to twrp home screen and reboot to recovery, which will be stock.
5. Format data using stock recover and then clear cache.
6. Restart and everything should work.
And if you find a way to get the twrp backups do post here.