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
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
I was on Booster Shot, did a backup in recovery, complete wipe and modified wipe, flashed Cool ICS ROM, wanted to go back, so I restore my backup from recovery, and now 4G (Wimax) is busted. It gets stuck at "obtaining IP address from Sprint" and goes no further. Any idea of how I can fix this?
Did you do a wipe before restoring your backup? Restoring a backup on top of a different Rom could cause issues like this. Try going into recovery and flash a super wipe like Chad's and then restore your backup.
Sent from my PG86100
saboxerman said:
I was on Booster Shot, did a backup in recovery, complete wipe and modified wipe, flashed Cool ICS ROM, wanted to go back, so I restore my backup from recovery, and now 4G (Wimax) is busted. It gets stuck at "obtaining IP address from Sprint" and goes no further. Any idea of how I can fix this?
Click to expand...
Click to collapse
I had that happen to me as well. I fixed it by entering ##3282# in the dialer, then going to edit mode (you'll need your msl). Then go in to WiMAX and reset the realm to sprintpcs.com. (even if it already says that, just re enter it). Then in the top right corner it sys save I think, or commit or something. Just make sure to save and commit. Then it should reboot. For me, 4g worked after that on more than one occasion. It's been happening after changing Roms.
Sent from my PG86100 using Tapatalk 2
coal686 said:
Did you do a wipe before restoring your backup? Restoring a backup on top of a different Rom could cause issues like this. Try going into recovery and flash a super wipe like Chad's and then restore your backup.
Sent from my PG86100
Click to expand...
Click to collapse
Didn't try this, however, will do next time I want to do a full restore. However, I think the issue lies in what I mention below.
k2buckley said:
I had that happen to me as well. I fixed it by entering ##3282# in the dialer, then going to edit mode (you'll need your msl). Then go in to WiMAX and reset the realm to sprintpcs.com. (even if it already says that, just re enter it). Then in the top right corner it sys save I think, or commit or something. Just make sure to save and commit. Then it should reboot. For me, 4g worked after that on more than one occasion. It's been happening after changing Roms.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
I finally fixed the issue after a clean wipe and fresh install of everything. However, according to what someone else suggested to me in another forum I posted this question as well to see if peeps there had an idea of what the issue was, it was mentioned issues in restoring data from an ODEX ROM to a DEODEX ROM, and vice versa I suppose, and this is what I did. Booster Shot is ODEX. Cool ICS is DEODEX. I'm sure that is where the problem fell.
Thank you both for your assistance. All is well now!
saboxerman said:
Didn't try this, however, will do next time I want to do a full restore. However, I think the issue lies in what I mention below.
I finally fixed the issue after a clean wipe and fresh install of everything. However, according to what someone else suggested to me in another forum I posted this question as well to see if peeps there had an idea of what the issue was, it was mentioned issues in restoring data from an ODEX ROM to a DEODEX ROM, and vice versa I suppose, and this is what I did. Booster Shot is ODEX. Cool ICS is DEODEX. I'm sure that is where the problem fell.
Thank you both for your assistance. All is well now!
Click to expand...
Click to collapse
Odex to Deodex (and vice versa) data restores cause problems even using the same Rom if the dev changes from one to the other.
Sent from my PG86100
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
this question was originally posted as my phone stuck in bootloop by itself
I've been using Slim Bean very neatly for the past 3 months until today
I charged my phone and I saw only battery icon (you know like when you charge it from no battery)
I unplugged and there is a red ! on top left corner in the GT-i9300t boot screen.
I was able to get to TWRP recovery, fortunately.
ok now I get it to boot what I did I restored to my NEATROM that I have backed up long time ago and before that I failed to restore to Slim Bean also.
I was happy it worked but
I'm now so confused as my newly RESTORED Neat rom looks like a new flash, with Samsung welcome screen and gmail login and all.
I have been restoring ROMS for some time now I know this ain't right, it should look like the state when I BACKED IT UP.
Is something wrong with my phone????
You must have backed up and restored a stock type rom .
Phone cannot change to stock by itself .
jje
I'm pretty sure it's not stock because I have been restoring it before and all the apps are there
now there's nothing
pinmemo said:
I'm pretty sure it's not stock because I have been restoring it before and all the apps are there
now there's nothing
Click to expand...
Click to collapse
Sounds like it failed to restore data
slaphead20 said:
Sounds like it failed to restore data
Click to expand...
Click to collapse
perhaps
This is getting even weirder, I cannot install Slim Bean or any AOSP ROM, only able to restore Samsung ROM with the same result...
grr
pinmemo said:
perhaps
This is getting even weirder, I cannot install Slim Bean or any AOSP ROM, only able to restore Samsung ROM with the same result...
grr
Click to expand...
Click to collapse
Time for a completely clean install,full wipe, Odin flash of stock firmware I reckon and start from scratch, easiest solution imho
slaphead20 said:
Time for a completely clean install,full wipe, Odin flash of stock firmware I reckon and start from scratch, easiest solution imho
Click to expand...
Click to collapse
your 'start from scratch' solution work thanks a lot! although different method
first I tried internal wipe, nothing changes
then here comes FORMAT DATA bam that fixed it :good:
unfortunately I didn't fulfill my curiosity as to what just happened
and I thought NANDROID back up is the best way to prevent any disaster ROM wise
it may not be made to withstand partition problem which is what I think happened.
The problem, to my recent realization actually happened after I recorded a very long video (20mins)...
Backup could have corrupt if in internal sd.
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
Backup could have corrupt if in internal sd.
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
but it's in my external card. Copied over from my computer even.
Moving / copying files can also be a catalyst for corruption.
I've had the same issue with a backup from computer before.
My reference to internal sd was if your partitions are messed up, its likely your backup was corrupt.
It could even be the backup just didn't take properly. If you have md5 checking turned on then that is more likely.
Anyway, it can happen from time to time
Sent from my GT-I9300 using Tapatalk 4 Beta
ok next time I'll make sure MD5 was checked.
I've done something that I haven't been able to remedy yet and it had made it so no matter what touchwiz ROM I use the phone app won't even open and getting a call reboots or locks up the phone. I have successfully installed AICP and all is working. Any ideas what I've done? Boot loader is mdk.
Sent from my jflte using Tapatalk
I'm just guessing here but did you anything that would've touched your efs folder? If you've made an efs backup (or a full backup, they usually include efs by default) I would suggest restoring it
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
I'm just guessing here but did you anything that would've touched your efs folder? If you've made an efs backup (or a full backup, they usually include efs by default) I would suggest restoring it
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
When this first happened I restored a backup I had from Hyperdrive Rls 15 (tw rom) and everything was there however the phone didn't work. I just ran through a tutorial of backing up and restoring my efs folder using terminal emulator and the results i got were the same on the video so I believe that to be in order.
I did flash one file which could possibly have caused this but if so I'm not sure how to reverse it. It was an NC2 WIFI fix after trying to install gdux v2.0
dogg94 said:
When this first happened I restored a backup I had from Hyperdrive Rls 15 (tw rom) and everything was there however the phone didn't work. I just ran through a tutorial of backing up and restoring my efs folder using terminal emulator and the results i got were the same on the video so I believe that to be in order.
I did flash one file which could possibly have caused this but if so I'm not sure how to reverse it. It was an NC2 WIFI fix after trying to install gdux v2.0
Click to expand...
Click to collapse
So personally when there's a problem I can't fix, I use odin to start my phone over. If I were you I would flash the full wipe tar that matches my boot loader. It's up to you though. That's a totally fresh stock start so you have redo root and everything.
I would also suggest PMing surge1223 and jkruse if you really can't lose the data on your phone and don't wanna go through Odin. Keep in mind they're both very busy.
Sent from my SCH-I545 using Tapatalk
Thank you for the advice I will probably end up using Odin as this seems to be a unique situation
Sent from my jflte using Tapatalk