So ive been having issues with dhacker29's roms making my phone reboot and hang on the bootloader. Well the latest one, the selinux build which he put more bugs into an already screwed up reboot cycle it worked good when I first installed it, than it did one of its forced reboots.
Phone hasnt booted since, restored to previous rom that worked fine. Stock, all kinds of things tried. It just hangs on the motorola logo now.
Anybody got any ideas for me?
When you go back to other ROMs are you restoring apps and data along with them via Titanium Backup or another backup app? If so, that might be the cause. It may be something in your apps, not the ROM. And as always wipe cache and dalvik cache after any flash.
Just restoring back to a TWRP backup. not using tibackup or anything like that,
Ive tried wiping dalvik, Tried a factory reset on these backups. Even tried fix permissions. Still nothing.
Probably a bad backup
If you wipe fully (yes I mean a full wipe) and then restore a back up from working phone and it just loops, chances are you had a bad backup
Just wipe clean and flash a new rom
Sent from my Nexus 4 using xda premium
demkantor said:
Probably a bad backup
If you wipe fully (yes I mean a full wipe) and then restore a back up from working phone and it just loops, chances are you had a bad backup
Just wipe clean and flash a new rom
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I did some posting in the thread for the rom. 2 others had the same issue where none of there backups worked after flashing that rom version and after it crashed and rebooted it never came back. So I doubt it was a bad backup just something weird with the rom
Sent from my XT926 using Tapatalk 2
Unless there is something very strange about this ROM (as in it corrupts other partitions but so highly doubtful), backups are 100% separate from another ROM, this means a full wipe will erase everything about you current ROM and then restoring a backup from a previous ROM will work, so long ad the backup is good and the wipe is clean.
Sent from my Nexus 4 using xda premium
I don't know. The rom does have a form or selinux in it so maybe that caused it. I don't know the specifics of what selinux does internally just what the goal is
Sent from my XT926 using Tapatalk 2
Doesn't sound like it should brake anything, if the ROM won't boot for you that's one thing, but completely wiping your phone then flashing a new ROM should fix your issue.
I am highly suspect that the ROM in question could have done anything at all to your recovery or your backups.
You said you are using twrp, have you tried wiping/formating all partitions and then flashing a known working ROM? Does your phone have fast boot mode? If so this may be an even cleaner wipe to do prior to the flash
Sent from my Nexus 7 using xda premium
I had to fastboot back to stock to get anything to work.. No rom I tried would boot
Sent from my XT926 using Tapatalk 2
Again, without knowing anything about your phone, the ROM would not affect your bootloader/radio/recovery no firmware should be changed just by flashing a rom,.
If it won't boot after a full wipe then there is some other issue, but if you were able to fix things by flashing back to stock then good.
Without knowing more specifics about your phone or the ROM you had issues with I guess I can't help you any further, so long as your are up and running now I would suggest just to stay away from any ROM you have had issues with, make new backups and test them (yes fully wipe before a restore and being your phone has fastboot wipe there) and best of luck to you
Happy flashing!
Sent from my Nexus 7 using xda premium
RAZR hd... Cm10.1 on the post started by epinter.. You can read how others had the same issue. I had 4 backups and non boot looped. It would hang at the bootloader and never even make it to the boot animation. Apparently it's something nobody's seen before but me and 2 others there have experienced it. So it's not a 1 time fluke.
Sent from my XT926 using Tapatalk 2
Related
Im currently running the first flight Rom and wanted to go back to alpha 2...i tried a reflash but my phone is still on the other Rom, i did another reset and reflash of alpha but it still hasn't change. I than tried to use my nandroid backup which ice used before but when i try to use it it tells me nothing on file...what do i do
Sent from my SAMSUNG-SGH-I717 using xda premium
After about 4 attempts i was able to flash alpha 2 and my back ups seem to be there as well...not just empty folders like before, weird
Sent from my SAMSUNG-SGH-I717 using xda premium
That is odd. Make sure you always factory reset multiple times as well as wipe cache multiple times when switching roms.
So you would:
- factory reset x3
- wipe cache x3
- wipe dalvik x1
- flash new rom
This should help with experiencing less if these type issues as well as other bugs.
Sent from my SAMSUNG-SGH-I717 using xda premium
Coffinfeeder said:
That is odd. Make sure you always factory reset multiple times as well as wipe cache multiple times when switching roms.
So you would:
- factory reset x3
- wipe cache x3
- wipe dalvik x1
- flash new rom
This should help with experiencing less if these type issues as well as other bugs.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I actually do those steps. I flashed one of the other ics roms and I didn't really like it so I tried to flash alpha back, after reboot I was still on the other rom...I tried again with same result, finally I used my backup. This time the same thing happened but I was on a different rom, the only difference was I wasn't able to use my back up, backup folder said "no file" when trying to flash, so I was pretty much forced to keep trying to flash alpha, finally it worked and I checked my cwm folder and my backups are there and are not empty. Odd
Sent from my SAMSUNG-SGH-I717 using xda premium
nash2000 said:
I actually do those steps. I flashed one of the other ics roms and I didn't really like it so I tried to flash alpha back, after reboot I was still on the other rom...I tried again with same result, finally I used my backup. This time the same thing happened but I was on a different rom, the only difference was I wasn't able to use my back up, backup folder said "no file" when trying to flash, so I was pretty much forced to keep trying to flash alpha, finally it worked and I checked my cwm folder and my backups are there and are not empty. Odd
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
weird considering when you do a restore it erases boot partition before starting to restore so unless you used the wrong backup file it should've worked the first time.
roloracer said:
weird considering when you do a restore it erases boot partition before starting to restore so unless you used the wrong backup file it should've worked the first time.
Click to expand...
Click to collapse
I only used the restore one time a week or so ago because everytime I tried to flash back to alpha I was still on the collective rom. Thats when I used my backup and it worked but this time the same time happened....flashed alpha like 3 times and nothing happened, I than tried to use my backup but my phone told me the backup file was empty, I have 2 backups and my phone told me the same thing on both. I continued to flash alpha over and over again with wiping date etc each time and it finally worked, and my backups have data in them unlike before.
Sent from my SAMSUNG-SGH-I717 using xda premium
So, i performed a nandroid backup so i wouldnt get screwed later down the road and all went well. Went to reboot now and no go, just sits on the big M. What is the problem. So many problems lately with this....
Just do a battery pull. If that doesn't work get into recovery and clear cache.
Sent from my MB870 using xda app-developers app
i did the battery pull, cleared cach and dalvick, let it sit for 10 minutes and nada from anything. Anything else i should try. If i format wipe data am i able to flash the nandroid i made
The only other things I can suggest are a data wipe or sbf. If you opt to do the sbf you may as well do the data wipe first and see if that fixes it. If so you can potentially restore the nandroid you just made without going through the hassle of sbf.
Sent from my MB870 using xda app-developers app
What rom are you running ? If cm9..make sure you are using the cm7 patched bootstrap recovery ...I made the mistake of not swapping to it after flashing to cm9, did a nandroid and had the exact problem....all you have to do is flash your nandroid you just made and then flash cm9 again......it will boot up again with nothing lost....but may act crazy like its running things on its own.....just shutdown and reboot and you'll be good to go.....then install the patched cm7 recovery and you'll never have the problem again.
sent from a pimpin DX2 CM9DX2 Beta1 V6supercharged !
I have the motor a4 bar. Is that the correct one. I had to sbf and do a whole new install but added blue sleep before rebooting all working well now. Oh running aokp 6.
Ok. so long story short, I rooted, unlocked my bootloader, made a backup in cwm(when i went to restore it i got (md5 mismatch) and then proceeded to install the base .7. after starting installation i clicked reboot now and it's been stuck on the nexus 4 boot animation. Any ideas why?
I've also run into this issue. Havent managed to find any fixes so far. Done full wipes and flashes back to stock and back to base and back and back, no dice on anything I've tried.
Hell, sometimes the ROM decides to skip the semantics and locks up my phone during installation. Have to hard reset & flash backups.
Anyway, back to the point on hand -- I'd also greatly appreciate any input on this issue.
I'd recommended installing the flashable stock ROM available in The Development section. Then flash The Base without wiping anything.
Sent from my A500 using XDA Premium HD app
ChefAnt said:
Ok. so long story short, I rooted, unlocked my bootloader, made a backup in cwm(when i went to restore it i got (md5 mismatch) and then proceeded to install the base .7. after starting installation i clicked reboot now and it's been stuck on the nexus 4 boot animation. Any ideas why?
Click to expand...
Click to collapse
If you got md5 errors you're using an early release of cwm for us that doesn't work right. You need to update it to a good recovery if you can and flash that first. It will help with the wipe issues too. That recovery, if I'm not mistaken, had some issues wiping, too. sk8terwitskil put out a new one early this morning.
Sent from my LG-E970 using xda app-developers app
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
edit: See my post here for details on what I've found so far, I may have fixed the problem but needs more testing http://forum.xda-developers.com/showthread.php?t=2397438&page=2
TWRP!!!!
SellswordShev said:
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
Click to expand...
Click to collapse
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
thepianoman77 said:
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
Click to expand...
Click to collapse
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
SellswordShev said:
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
Click to expand...
Click to collapse
oh dude.... I was on v2.6... I think we have an issue.
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
i had a very bad experience with CWM... never using it again man.... no way.
thepianoman77 said:
i had a very bad experience with CWM... never using it again man.... no way.
Click to expand...
Click to collapse
Lol ok :thumbup:
Sent from my SCH-I545 using Tapatalk 2
I've been using TWRP too. I panicked last night when I couldn't boot at all. I couldn't even get to recovery. I then tried the no wipe odin without luck. I finally got the stock odin image to work but I've been having serious issues with booting on this phone since I got it this weekend and it could be TWRP I suppose. I was using it on my note 2 with no issues. Very strange. I'm back to stock and running fine now.
Sent from my SCH-I545 using xda premium
Still having odd issues with TWRP after updating to 2.6, getting stuck on boot as before, and sometimes flashing a ROM will just fail and the data partition becomes read only, and I can't push anything to it till I reformat /data.
Going to try CWM today, really hope this is just a recovery issue. Are there any tests to check the health of on board memory? I am really hoping I don't have bad hardware here.
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
ruffneckZeVo said:
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Root / recovery methods will be the same for everyone, regardless of what guide / thread you followed, in the end you will have a loki-patched recovery and kernel, as thats the only way to run unsigned images on these phones. Whats relevant here is which recovery and kernel you are using, as these are the only 2 things that could effect errors in the boot logo state (aka freezes before the ROM boot animations kick in). Ive been looking through various ROM threads of people reporting this issue and its pretty widespread, and usually is linked to recoveries rather than ROMs. If you can post your recovery + ROM here that would be helpful. Here is what I've done so far:
I was initially on TWRP 2.5.0.2, which had possible bugs that could corrupt /data, leading to failed flashes, and being unable to read/write from /data entirely (including /sdcard). After switching to 2.6.0.0 I was still getting stuck on the boot animation. (All of this running the CM10.2 ROM with the stock kernel here http://forum.xda-developers.com/showthread.php?t=2384470). Note I did not do a full wipe after switching to 2.6.0.0, so that recovery MAY still be ok if someone wants to test it out.
I am now running CWM (official installed off ROM Manager). After flashing this I did a full re-format (/system, /data (including /data/media), etc.). And so far I haven't had any problems, going to do some more fiddling / flashing tonight to try and see if its really fixed, but I know for sure that atleast the reboot bug is gone.
So my advice is to flash the official CWM recovery, do a full re-format using that recovery, and then re-install your ROM.
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Monkz said:
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Click to expand...
Click to collapse
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
SellswordShev said:
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
Click to expand...
Click to collapse
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Monkz said:
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Click to expand...
Click to collapse
is PhilZ a recovery?
thepianoman77 said:
is PhilZ a recovery?
Click to expand...
Click to collapse
Yes its a custom build of CWM maintained by an xda dev here http://forum.xda-developers.com/showthread.php?t=2322675
Im still having the issue with philz. Everything was fine for the first 4-5 weeks. Now about every 3rd reboot or if battery dies I have to wipe data and nandroid. Im running stock with several tweaks. Going to try and odin restore to stock re root snd install cwm tonight and see if that helps will report back
Sent from my SCH-I545 using xda premium
Alright, I'm almost 99% sure this problem is gone after I switched to the official CWM. I've tried everything from restoring nandroids to flashing TWiz / AOSP 4.2 and 4.3 ROMs, everything boots and reboots and /data is no longer getting corrupt. I also loki patched the official CWM touch recovery (the one on their site is not patched), and flashed + used it successfully. Its pretty simple to do this, just follow the guide here: https://github.com/djrbliss/loki and use this recovery: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.2-jfltevzw.img
The only issue I've been having is that when I reboot to recovery, it sometimes gets stuck and I have to do a battery pull and go back into recovery.
Sent from my SCH-I545 using Tapatalk 4
I'm having the same issue on TWRP 2.6. Tried with multiple ROMs. Everytime I reboot I have to format /Data. So frustrating. I will try CWM now.
Not sure what went wrong, but I've just had to use flashtool. I decided to flash one of the stock roms available. I don't feel any of what resulted was fault of the Rom so I won't specify. I made another backup of my tweaked Rom, and wiped as instructed and installed. Everything flashed ok but the Rom was a little buggy so I decided to restore my tweaked backup. Rebooted to reovery, wiped then selected which backup to restore. In short, the backup was showing no partitions available to restore and wouldn't work. So, I chose my original backup of stock and that showed everything so I restored. From there, the backup said complete so I rebooted. I ended up with the flashing red and blue led and could only boot to twrp. I tried to reflash the Rom zip but it failed to open. So here I am after using flashtool, which was an adventure as well. I'm curious if anyone else at all has had a similar experience? Is it possible my twrp was corrupt in some way?
Sent from my LGLS990 using Tapatalk
Had you ever tried to restore you backups prior? Just to make sure you had a good backup.
Did you use compression in TWRP? It's been an issue in the past. At least with the OG it was.
I have no other ideas. Sorry you had to go through that. But at least you got it fixed.
I hadn't restored prior to this, no. I think I did use compression on the second backup. Good point. One good thing, I don't have the ugly yellow spark boot ani any more. [emoji6]
Sent from my LGLS990 using Tapatalk
Evolution_Freak said:
I hadn't restored prior to this, no. I think I did use compression on the second backup. Good point. One good thing, I don't have the ugly yellow spark boot ani any more. [emoji6]
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Is this after Flashtool? The only way I know of to get it back is ##RTN#. And you'll need your MSL.
You shouldn't have Wi-Fi calling either then. That's the clincher.
Be safe and backup your EFS first though.
Evolution_Freak said:
I hadn't restored prior to this, no. I think I did use compression on the second backup. Good point. One good thing, I don't have the ugly yellow spark boot ani any more. [emoji6]
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
i also used compression for my backup did you figure out if that was what caused the problem?
kMogs17 said:
i also used compression for my backup did you figure out if that was what caused the problem?
Click to expand...
Click to collapse
To be safe, boot into recovery and try to restore your backup. If you don't see the partitions listed, then it's probably compression.
Edit:
Don't wipe anything though!
Sent from my LGLS990 using Tapatalk
Evolution_Freak said:
To be safe, boot into recovery and try to restore your backup. If you don't see the partitions listed, then it's probably compression.
Edit:
Don't wipe anything though!
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Yep yep - Im glad this is my second LG, I never use compression thanks to all I've learned from the lgog. That sucks though dude, but lesson learned.
For the record, I've flashed several things and restored several backups already(I have two, odexed stock and deodexed stock) without any issues.
Evolution_Freak said:
Not sure what went wrong, but I've just had to use flashtool. I decided to flash one of the stock roms available. I don't feel any of what resulted was fault of the Rom so I won't specify. I made another backup of my tweaked Rom, and wiped as instructed and installed. Everything flashed ok but the Rom was a little buggy so I decided to restore my tweaked backup. Rebooted to reovery, wiped then selected which backup to restore. In short, the backup was showing no partitions available to restore and wouldn't work. So, I chose my original backup of stock and that showed everything so I restored. From there, the backup said complete so I rebooted. I ended up with the flashing red and blue led and could only boot to twrp. I tried to reflash the Rom zip but it failed to open. So here I am after using flashtool, which was an adventure as well. I'm curious if anyone else at all has had a similar experience? Is it possible my twrp was corrupt in some way?
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Noticed that you said you wiped before restore. I did that once on my G2 and ended up having to use flashtool.
leroybrute said:
Noticed that you said you wiped before restore. I did that once on my G2 and ended up having to use flashtool.
Click to expand...
Click to collapse
You should always wipe first IMO. There's always ghosts in the machine. It's just an added measure to give you a clean restore/flash. Most people that have issues with roms don't wipe, and dirty flash/restore.
I've never had an issue wiping all 4. And compression just seems to never work right. At least with all the G series.
engine95 said:
You should always wipe first IMO. There's always ghosts in the machine. It's just an added measure to give you a clean restore/flash. Most people that have issues with roms don't wipe, and dirty flash/restore.
I've never had an issue wiping all 4. And compression just seems to never work right. At least with all the G series.
Click to expand...
Click to collapse
If you wipe all four and your twrp isn't on your external SD card you're screwed if you want to restore.
I always wipe when installing roms, just not restoring. Habit from using phones without ext.
I also thought I saw a wipe script built into the restore option.
I called Sprint today to get my MSL. I needed to use the ##RTN# code to get the WiFi calling app and the other stuff back after flashtool. They had me do a factory reset first to see if that would do it but then gave me my MSL without question.
Thanks again for all the info learned in this thread. I finally got around to re-rooting and re-bumping and all were smooth and easy.
Sent from my Stump'd & Bump'd Sprint LG G3
engine95 said:
You should always wipe first IMO. There's always ghosts in the machine. It's just an added measure to give you a clean restore/flash. Most people that have issues with roms don't wipe, and dirty flash/restore.
I've never had an issue wiping all 4. And compression just seems to never work right. At least with all the G series.
Click to expand...
Click to collapse
I only had a problem with compression once on my OG for the rest of the time it worked fine and was a necessity because it had no external storage but anyway i just checked the compressed backup i made and the partitions show up under restore, but i havent tried it yet because i have no reason to. maybe when aosp comes out