Does anyone have any clues about why all my apps force close after marshmallow OTA? I am 100% stock but SOFF. I was rooted before but I have restored a stick system image. The update seems to go OK. The hone does the final reboot then goes through the process of optimising all the apps. Finally I get a lock screen but when I unlock I am bombarded with force close messages. If I do a factory rest the phone boots OK but I am interested to know why it doesn't like my data partition? Anyone have any thoughts on this?
The same thing happened to me after I tried to trick my phone to accept my data partition from KK 4.4.2 into Lollipop 5.01. So, I made a twrp backup, flashed 5.0.1 RUU, then immediately, restored my KK data partition, and ended up with everything crashing. Obviously, it won't work that way. What worked for me was to allow the phone to complete the first boot, THEN restore my old data partition
Cheers
shirreer said:
The same thing happened to me after I tried to trick my phone to accept my data partition from KK 4.4.2 into Lollipop 5.01. So, I made a twrp backup, flashed 5.0.1 RUU, then immediately, restored my KK data partition, and ended up with everything crashing. Obviously, it won't work that way. What worked for me was to allow the phone to complete the first boot, THEN restore my old data partition
Cheers
Click to expand...
Click to collapse
Thanks. I did try that but alas no cigar. Thanks anyway.
Related
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
chrowley said:
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
Click to expand...
Click to collapse
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
ashwin77sgg said:
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
Click to expand...
Click to collapse
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
chrowley said:
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
Click to expand...
Click to collapse
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
ashwin77sgg said:
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
Click to expand...
Click to collapse
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
chrowley said:
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
Click to expand...
Click to collapse
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
ashwin77sgg said:
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
Click to expand...
Click to collapse
i already tried it sir but it didnt solve the problem, it passes the setup but after a few minutes the phone reboots.
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
naufalhadyan said:
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
Click to expand...
Click to collapse
This is probably the best explained and most direct definition of what to do and what may be happening with our ever-rebooting Grands.... Thank you!!!
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
victorsmarotta said:
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
Click to expand...
Click to collapse
Even iam facing the same issue
phone reboots automatically and doesnt even start... infinite bootloop. Was working fine and suddenly this issue came up from nowhere(past 2 weeks) ..
Iam using Resurrection rom 5.7.4 (Marshmallow)
Damn I was on AICP 11, when this exact strange bootloop problem occurred for no rhyme and reason. I know the hardware is fine, the issue arises from installing apps from playstore, the moment it goes beyond a certain app limit in the device, it will start endless bootloop, I am sure this is Google's doing. Anyways this is not a hardware issue and I know more people will be coming here looking for answer to this issue. I have tried both the opengapps and deltagapps, same behaved this way, it never happened before and lately google have introduced one other app which is google's android instant app that will sit in your device, even though you need it not not. very well google for using our precious internal data to around 500Mb to 1Gb.
formating data partition solves this issue, temporarily but you lose your apps and data.
I had successfully avoided this issue when I stopped installing more apps on my device, It took me 2 tries and I found a perfect balance of 4-5 apps, it came crashing again when I tried installing the 7th app.
I don't know if other ROMs will be able to handle this bug, but I know it's time for me to look for another ROM, I was happy with AICP 11, for more than a year. Sad.
Reading about this issue, I came to know this is prevalent on all CM marshmallow based ROMs. So, going to flash Nougat or kitkat or the stock ROM should probably fix this.
Try a new battery.
Greetings,
I would have liked to post this questions, where it belongs to, but I'm new to this forum, so I put it here.
Last September I've updated my DHD following the instructions given in the thread mentioned in the headline and everything was fine. Yesterday in the evening, I got the notification to restart using the recovery mode, because something in the context of the superuser should be updated or modified. Because it was not the first time, I just did it. But this time, after rebooting, the device stopped with the HTC bootscreen (green HTC on white background).
After 10 minutes I took out the battery and restarted again. Again I was able to choose recovery mode, but while starting the DHD got stuck with the bootscreen. I decided to wait and just put it aside showing the boot screen, but the result this morning was that the battery is empty and nothing changed.
Does someone know about that issue and what do I need to do to get the device to work again? Why was this update needed in the first place?
Thanks a lot in advance...
im not sure why
but have you tried re-flashing the ROM?
PHOENIX-9 said:
im not sure why
but have you tried re-flashing the ROM?
Click to expand...
Click to collapse
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
If you don't wipe your data partition (dirty flash) and you flash the exact same ROM, you shouldn't lose data.
KKrittel said:
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
Click to expand...
Click to collapse
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
PHOENIX-9 said:
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
Click to expand...
Click to collapse
Tried to make a backup, but it recovering did not work. Doesn't matter. I just flashed the same image again, downloaded 'my' apps and restored the status from before the crash.
Nevertheless the same notification showed up, saying that the superuser kernel needs to be updated and I should use 'recovery mode' again. With a bad feeling, I did it again, but this time it works.
So to sum it up: device was useless for some days, restored it with some effort and now it works again. But I need to get prepared for the next time and to think of an app to backup all apps including app-data.
...but as always, this is a task for laaaaater
Thx,
Karl
Ok, here is my dilemma. I panicked a bit and downgraded to KitKat 4.4.4 from Lollipop 5.0.2 while there was some concern over it killing N7's. As is usual, I rooted the install, which means the 5.0.2 OTA will fail to install.
In the meantime, I started playing Agent Alice. (Don't laugh, I like hidden object games) However, unlike most apps, backing it up in TiBu doesn't preserve your progress. If you restore the backup, you start out at the beginning. I'm not sure how or why, but it appears I can't do my standard backup and push to the server routine. Which means I really don't want to blow away user data.
So, I looked into using the factory restore images with the modified flash-all.bat. I haven't yet pulled the trigger on that, because I have been told that going from KitKat to Lollipop without clearing user data can cause problems. I'm tempted to use TWRP to back up the whole thing and give it a go, but I'd prefer to go in as well-armed as possible.
What's the best way to get from KitKat 4.4.4 to Lollipop 5.1 without losing installed apps and user data when an OTA isn't an option?
I used factory images with a modified batch file to go from 4.4.4 to 5.0, then 5.0 to 5.0.1 and 5.0.2. I haven't updated to 5.1 yet.
I didn't lose any data. I installed the factory images, booted once and then ran Chainfire Autoroot each time to get root back. Zero issues, no lost data. As long as your bootloader is already unlocked (assuming it is if you're rooted and have already flashed back and forth), you won't lose anything.
You could still make a nandroid backup and worst case, flash factory images back to whatever version you did the backup from, restore and try again.
Hey guys Im running stock rooted and for some reason my phone SD is saying im full. I have literally nothing on it. Any ideas?
I tried once to install a ROM but it borked so I went back to a backup I had and it was fine.
Via windows it says my SD only has around 8 gigs used but android is saying 24?!?!?!?
WTF MATE?
Try wiping userdata in twrp.
Illogi.xbone said:
Try wiping userdata in twrp.
Click to expand...
Click to collapse
thanks, I was about to try and just redo the device with a ROM. Clear cahces and such.
I was actually wrong, every time I go into the phone in windows its giving me different storage use #'s. One time its 8 then 17 then 23 then 9. its weird. I think when I tried dirty flashing it just screwed it all up. I have nothing on the SD I care about really so maybe Ill just back up what I want (TWRP backup and titanium apps) and start from scratch if I Cant solve this.
That might be the best. Try backing up to an OTG then completely wiping and installing a fresh ROM. After backing up apps and such.
ugh IM having trouble using any roms on my 5x. No matter the way I install the phone always boots to "internal problem with device"
Ive tried installing different roms (I only like stock style ones) and the vendor.zip and it just doesnt work for me. Ive gone back to my backup for the moment until I figure this out. Never had these issues with my nexus 5
this is odd now my pattern no longer work since my restore back to my TWRP backup! GOD DAKNIT!
let me do the start patttern fine for android then when unlocing the phone it tells me "pattern needed to start device"
what the hell man!
tevil said:
this is odd now my pattern no longer work since my restore back to my TWRP backup! GOD DAKNIT!
let me do the start patttern fine for android then when unlocing the phone it tells me "pattern needed to start device"
what the hell man!
Click to expand...
Click to collapse
Try 1st: Completely wipe device, System, data etc. Including Internal Storage and flash a new rom. If that does not fix the issue try flashing stock firmware and start from scratch. Use THIS guide to flash the stock images.
Flash vendor.img that matches your rom base. MMB29Q is the February OTA base. February AOSP roms are based on MMB29U master code but MMB29Q vendor file works fine.
For password issues after TWRP restore, do this: http://forum.xda-developers.com/showthread.php?t=3245070
Sent from my Nexus 5X using Tapatalk
SERIOUS ISSUE!
Bricked the phone!
CRAP, this whole thing went downhill. Can get into TWRP, and get the android crash logo (triangle) was trying to restore back to stock to start fresh and it bombed completely!
Any tips!!!
Been a while since I used ADB or fast etc, but man if I have to relearn I will
The phone updated to Marshmallow and now all downloads just hang. Nothing happens at all for hours.
Googling suggests that I need to wipe the cache partition (well something to try before a full wipe) and I in order to that I need to get into recovery.
And that's where my problems start (well besides the initial problem). I can't get the phone to boot into recovery. Does it perhaps not have a stock recovery (international version)?
If it doesn't what recovery should I install? (Phone is currently not rooted and has a locked bootloader as far as I know). Just want something to wipe the cache partition, nothing fancy as the phone is meant to stay as stock as possible.
Or how else should I proceed (before I get to the full wipe/factory restore option)?
Don't bother, just go for the full wipe now and save yourself days of wasted time.
Marshmallow update requires a factory wipe after installation, I don't know why LG didn't make this part of the update but they didn't.
If it's still broken afterward then flash the full firmware again using bridge.
Well that's fantastic news....
I really didn't want to resort to that.
The rest works great/as good as before, it's just the downloads that are stuck...sigh...oh well. Thanks.
Here's to 2-3 days of downloading and setting everything up again anyways (slow net) :/
Use the LG backup app, it isn't perfect but I was up and running again within a couple of hours.