Develop Bugs

[Q] Having major problems on Sense roms, help!

I haven't found any solution with this. About 3 or 4 weeks ago my Evo went crazy so I rebooted and was missing many apps. I did a nand to another sense rom and every time I tried to install an app (either download or from sd card) it would reboot. The odd thing is, it only does it with sense roms. I can use CM 6 or 7 fine and install whatever I want. I was originally one Myn's rls5, I also tried the Fresh roms. I have non clue what's causing this, tried googling and all said clear the market cache or try an older market, which I've done both. Any help would be greatly appreciated.

tricky one. have you tried flashing a stock sense rom, and seeing how things work for you there?

Don't use a backup. Flash a sense ROM and install everything manually.
Sent from my PC36100 using XDA App

shogun26 said:
tricky one. have you tried flashing a stock sense rom, and seeing how things work for you there?
Click to expand...
Click to collapse
I haven't tried a stock rom yet, once I get things back up I'll find one and try it.
gqstatus0685 said:
Don't use a backup. Flash a sense ROM and install everything manually.
Click to expand...
Click to collapse
I can't install anything. period. as soon as I try to install any apk from my sd card or anything from the market that doesn't come installed in the rom, as soon as it "finishes" the installation part it will reboot, but not a full reboot, it will go out to the boot screen (but not all the way to the htc screen).

Since going from AOSP to Sense what was your procedure for flashing? Just want to make sure your starting with a clean slate.
- What steps to you take?
- Full wipe? Data, cache, sd-ext?
- SD format?
The more info you can give the better and maybe we can help you track it down.

Ive done the standard full wipe, data, cache, dalvik. I do that everytime between roms. Not sure what the ext does and in haven't formatted my sd card since then
Sent from my PC36100 using XDA App

Update - I flashed the stock rooted 3.70 and was able to install. This was after formatting my sd card. Then tried to flash Myn's rls5 again and had the same problems as before. Only difference is with the 3.70 I forgot the flash the radios, but still had a fine signal. I flashed the radio updates with Myn's. Any help/advice is greatly appreciated.

At this point all I can think of doing is unrooting your device and getting it completely back to stock, then try re-rooting and make a nandroid of your rooted, stock sense rom.
Maybe you can root through a different methods than what you did originally.
After that, try another sense rom, make sure the md5 checks out too.
Sent from my PC36100 using XDA App

What recovery are you using and what version? I thought there were known issues with ClockWork 3.x.x.x version of recovery not wiping cache correctly? If you are using ClockWork you might want to try switching to Amon_RA 2.2.1. to see what happens. There is also a zip floating around (which I have attached) that can be used to wipe everything, you may want to give that a shot then reinstall the ROM. I have not used this zip, so use it at your own risk as I cannot guarantee the results. I have read about others using this and it working just fine.

[Q] Rom manager installs corrups phone

Everytime I install a custom rom on rom manager, it has corrupted my phone and each and everytime I'd have to restore it. Is there any way to fix it? I've seen comments on the custom roms and people have commented that it works fine on the DHD.

Hi drkhrsy
Kindly explain further by your meaning of corrupt? This would allow us here to clearly understand the problems you're facing. Thanks.

Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.

drkhrsy said:
Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Did you do a full wipe before flashing those roms, multiple fcs normally indicate that you didn't try a full wipe then reflash either of your chosen roms.

Full wipe as in factory settings?
Well I've installed a new RUU after the boot loop problem, isn't that considered as a full wipe? or should I just do a wipe again now?

I had that horrible boot loop aswell after installing Rom.manager but I fixed it with a ruu
Sent from my Desire HD using XDA App

Installing a new RUU does not constitute that you have full wipe any data and cache. As the ROM you tend to flash is, in a small or large extent, relatively different from that of RUU. That why we always advised to do a full wipe whenever we wish to flash ROMs. Else it will cause some issues such as Force Close issues.
You have to boot into recovery and select Wipe Data and Wipe Cache. That you will consider yourself that you have wipe those data and caches. Then now you can flash the desired ROM in your list.
In addition, before flashing is best to do a Nandroid back-up.
Also do check on your recovery version before you flash any ROMs as different ROMs need/may require different version in order to be flashed successfully(i.e. no or minimal issues)
Cheers mate.

aiight sweet, I'll give that a go.
Cheers!

You're most welcome.

drkhrsy said:
aiight sweet, I'll give that a go.
Cheers!
Click to expand...
Click to collapse
Memory serving EVERY ROM says you MUST perform a wipe of data and cache if coming from a different ROM. This is custom ROM 101. Please read instructions thoroughly before doing things like this. The ROM devs don't spend their free time writing instructions just for the hell of it.
Regarding ROM Manager, don't you get asked if you want to wipe data and cache when you flash a new ROM (or is that not an option on the free version)?

Yeh I do get asked for wiping data and cache, I do that and it just seems to still screw up. Also backing up my files through clockwork seems to make my phone get stuck on the HTC boot up screen which requires me to reformat using the RUU file.

I would suggest re-flashing the recovery.img file.
Also, are you using the same cwm-r version to restore as used to create backup? For example, If version 2.x.x.x was used to backup you can't use 3.x.x.x to restore.
Sent using witchcraft via XDA Developers Premium App.

I've just checked my CWM-R version and its recovery version is at 3.0.2.6 hmm now I cant get into the recovery boot screen :S. I'd just most likely restore the phone again and try root the phone again. but thanks anyway

nvm I got in the recovery boot. Yeh the CWM-R are the same version.

drkhrsy said:
nvm I got in the recovery boot. Yeh the CWM-R are the same version.
Click to expand...
Click to collapse
I think you miss understand. I don't mean do they match wherever you look.
Did you make the original backups using version 3.0.0.x or 2.5.x.x?
Sent using witchcraft via XDA Developers Premium App.

drkhrsy said:
I'd just most likely restore the phone again and try root the phone again.
Click to expand...
Click to collapse
You don't need to do that, just redo the recovery.img
Sent using witchcraft via XDA Developers Premium App.

Need some help asap

ok well i just downloaded and flashed the chopsuey kernel and now when im rebooting, my phone only sits at the htc evo 4g screen.. someone PLEASE HELP.. i think my phone just got bricked

No problems mate,just pull your battery,replace it,when turning on hold your volume button down,when you entered the bootloader,scroll to recovery and wipe your phone then find restore/nandroid then restore your phone to your latest backup,hopefully you did back up,if not reinstall the rom again after you wipe everything,then next time set your CPU to a lower setting,then move up gradually.I hope this helped.

blah.. so new to this i didnt know i could backup through recovery.. thought it meant like my apps and what not =/ guess i have to wipe

I set my phone to high the first time and it did the same thing and of course i freaked,lol.After bricking your phone a few hundred times,you remember to do a backup regularly.

what rom are you using? Hopefully not a AOSP cause Chop Suey is a sense kernel.

well my set cpu wasnt working because i was using stock kernel.. all i did was flash the chopsuey rom and then i just hit reboot and i was stuck at the htc evo 4g white screen.. what did i do wrong?

i am using team nocturnals sense 3.0 themed rom. more specifically, shooterRLS_3.1

ReapersDeath said:
well my set cpu wasnt working because i was using stock kernel.. all i did was flash the chopsuey rom and then i just hit reboot and i was stuck at the htc evo 4g white screen.. what did i do wrong?
Click to expand...
Click to collapse
Ok i'm not sure that roms compatible with chopsuey,try freedom kernel... Freedom Kernel

I am rooted. and i meant chopsuey is a kernel.. but the rom im using is shooterRLS_3.1.. im guessing i just flash the rom, and then the kernal and im done?

i just retryed and now its actually starting up so blah.. is it actually not compatable or not?

If its running ok,use it.

oh ok.. i dont want to screw up my phone.. so blah.. thanks for the help.. almost had a heart attack

Did you wipe cache and Dalvik before you flashed the ROM? If that ever happens again, wipe those then try to boot again. If it still doesn't boot, wipe everything and reflash your ROM, err, start over, but since it was just a Kernel, that would probably wiork

Whenever you flash a new rom, wipe everything (data, cache, dalvik, system, boot, .android_secure, sd-ext). Whenever you flash anything that isn't a rom - kernels, themes, mods, boot animations, etc - or flash an update to your existing rom then wipe cache and dalvik only.
Always make a nandroid backup when you flash a new rom. I don't nandroid for everything I flash, but if you're flashing a new kernel and it has been a while since you did a backup then go ahead and do another one. You can always delete nandroid backups to save space, but keep at least one on your SD card. Also nandroid before modifying system files, like removing system apps.
Always read about what you're doing before you do it.
I know you solved your problem, just pointing some stuff out that you may have missed along the way. Good luck & happy flashing!
Supersonic Evo 4G | MIUI | Tapatalk

plainjane said:
Whenever you flash a new rom, wipe everything (data, cache, dalvik, system, boot, .android_secure, sd-ext). Whenever you flash anything that isn't a rom - kernels, themes, mods, boot animations, etc - or flash an update to your existing rom then wipe cache and dalvik only.
Always make a nandroid backup when you flash a new rom. I don't nandroid for everything I flash, but if you're flashing a new kernel and it has been a while since you did a backup then go ahead and do another one. You can always delete nandroid backups to save space, but keep at least one on your SD card. Also nandroid before modifying system files, like removing system apps.
Always read about what you're doing before you do it.
I know you solved your problem, just pointing some stuff out that you may have missed along the way. Good luck & happy flashing!
Supersonic Evo 4G | MIUI | Tapatalk
Click to expand...
Click to collapse
True that. I keep 5 Nandroids on my phone at all times: Original Stock/Rooted. Stock/Rooted with updated apps +TB & GPS Status, Last good setup, Current ROM before I added all my apps, etc. and Current ROM after a fresh flash.

HipKat said:
True that. I keep 5 Nandroids on my phone at all times: Original Stock/Rooted. Stock/Rooted with updated apps +TB & GPS Status, Last good setup, Current ROM before I added all my apps, etc. and Current ROM after a fresh flash.
Click to expand...
Click to collapse
Jeeze, I feel like I take so many shortcuts...I only keep a backup of my CM7 latest, and currently ICS, incase I had to switch for whatever reason.
I keep all my apps up to date in tb so that alleviates that issue.

Well, it's not about apps. I like to have the barebones, stock/rooted all the time. The updated stock is for when I need to run the Sense Fix for GPS, or just updating profile/PRL.
The last Good Setup is obvious, as is the current good setup.
The bare bones Nandroid for my current ROM is in-case I screw up, I can go back to that and start over

HipKat said:
Well, it's not about apps. I like to have the barebones, stock/rooted all the time. The updated stock is for when I need to run the Sense Fix for GPS, or just updating profile/PRL.
The last Good Setup is obvious, as is the current good setup.
The bare bones Nandroid for my current ROM is in-case I screw up, I can go back to that and start over
Click to expand...
Click to collapse
Well that makes sense. If I mess up, I just go back to the last backup. xp Though neither practice is bad.

Problems with cwm after installing paranoid android rom

Ok so I have kind of a strange problem and i dont think its with cwm. I always make nandroid backups before flashing new roms as a precaution but in this case it did no good I recently installed Paranoid Android on my phone to try out Jelly Bean. It is pretty awesome But it is a little buggy with a few of the apps i like to run (rom toolbox and dropbox being the major ones). After restoring all my apps i decided to restore my messaging data. That caused the rom to not boot past the google screen. So I decided to go back to Black Ice AOKP with my backup. Didnt work, gave me the "error while restoring /data!". I also just recently updated to CWM Touch 6.0.0.5. I also tried an earlier backup with the same problem. I decided to use fastboot to flash a different CWM (5.8.*.* touch and regular) and basically has the same issue just a different response (could not find data.img, cache.img, and boot.img). Because i use Titanium backup anyway i decided to just wipe and flash Black Ice but when i do it boots for about 30 seconds and then the phone restarts. I tried this multiple times doing multiple formats to no avail. Just for sh*ts i decided to try to wipe and reinstall Paranoid Android. IT BOOTED!! But the weird thing is is that all my apps were still there including my messaging data that borked the install to begin with :/ Anyway to make a long story short, my phone is now working but im afraid that i can't restore my backup or even install a new rom without issues. It seems that CWM will not properly wipe my phone anymore. I am wondering what this new rom could have installed that would cause these issues? I didnt flash any new radios or bootloaders so i dont think that is an issue. Please help!! lol I would like to go back until this rom gets further development or AOKP goes to JB. Any help is appreciated. Thank you for your time
-Erik

I really don't think the ROM caused your recovery to not work correctly. Have you tried a different recovery, like TWRP?

Oh, and any problems you're having with apps on Paranoid can be easily fixed by changing what mode they display in via Paranoid Settings.

shode, ndomeopu
Thanks For The Quick Replies! My Swype Has Decided Too Capitalize Every Word And I'm Not Going Too Fix It Lol.. Anyway I've Tried Changing Modes With Rom ToolboxAnd It Made No Difference. i Will Try With Drop Box. It Seems Like Maybe This New Rom Messed With The Permissions And That's Why i Can't Properly Format? The Thing Is Is That CWM Worked Fine Before Booting This Rom. And i definitely Understand That My Conclusions Don't Make Sense But Neither Does The Problem Lol. i Guess What My Question Is Is Why Do The Previous Versions Off cwm That Worked Before Not Work Now? i Will Give The Other Recovery a Shot And Let You Know But i Prefer cwm Just Because It's What i Know And Had Always Worked... Until Now Of Course. Also i Don't Consider Myself anewbie At Thus Stuff But i Am Definitely No dev Lol. Any Suggestion Is Welcome. Thanks!

jesusice said:
Oh, and any problems you're having with apps on Paranoid can be easily fixed by changing what mode they display in via Paranoid Settings.
Click to expand...
Click to collapse
Silly Me For Not Thinking Of Changing The Settings. dropBox Now Works But My Swype Is Still Messed Up

Swype works fine for me at 320 dpi and phone mode. Which is the Gnex's default settings so if an app gives you issues try those settings. I'm not too sure about CWM, it's been a while since I've used it. If you want to try TWRP the easiest way is to just install Goo Manager and go to Flash ROMs and in the additional options select Flash Open Recovery Script.

well swype in general worked.. maybe its just my browser. Anyway I installed TWRP, makes me wonder why I wanted to keep CWM It worked.. im back to the old rom. Quick question.. does it save the backups to /sdcard like CWM? I thought it said it backed up to /data/media which means if i completely wipe /data ill lose my backups. Also does this mean I dont have as much space for backups? Thanks for your help.

Gimmemabrewski said:
well swype in general worked.. maybe its just my browser. Anyway I installed TWRP, makes me wonder why I wanted to keep CWM It worked.. im back to the old rom. Quick question.. does it save the backups to /sdcard like CWM? I thought it said it backed up to /data/media which means if i completely wipe /data ill lose my backups. Also does this mean I dont have as much space for backups? Thanks for your help.
Click to expand...
Click to collapse
/sdcard and /data/media are the same thing. I'm sure there's a better technical explanation but I think it's symlinked or something. So wiping data or factory reset in recovery will not wipe your SD contents. From within the ROM it might.

Problems Flashing and Restoring custom roms

I have had problems flashing and restoring Roms both stk and aosp. By problems I mean getting stuck at boot screen after flash and backups failing at data and if restored without data stuck at boot. The only remedy I have found is a total internal memory wipe. I have tried many wiping techniques none worked long term. Last night when I had these problems again before I did full internal data wipe I used twrp file manager and looked around and notice after factory reset wipe which is suppose to wipe all data but data/media I still had data/app and when I tried to manually erase it failed. even with system mounted I couldn't delete. Maybe someone else having troubles can also check to see if data/app is still there after wipe. I dont know if its recovery related or caused by the aosp sd format. Maybe a combination? I don't think im the only one having these problems so I wanted to start a thread to try to figuer this out. Any help is greatly appriciated.

Bdadd34 said:
I have had problems flashing and restoring Roms both stk and aosp. By problems I mean getting stuck at boot screen after flash and backups failing at data and if restored without data stuck at boot. The only remedy I have found is a total internal memory wipe. I have tried many wiping techniques none worked long term. Last night when I had these problems again before I did full internal data wipe I used twrp file manager and looked around and notice after factory reset wipe which is suppose to wipe all data but data/media I still had data/app and when I tried to manually erase it failed. even with system mounted I couldn't delete. Maybe someone else having troubles can also check to see if data/app is still there after wipe. I dont know if its recovery related or caused by the aosp sd format. Maybe a combination? I don't think im the only one having these problems so I wanted to start a thread to try to figuer this out. Any help is greatly appriciated.
Click to expand...
Click to collapse
yeah just happened to me just now too dammit... tried to restore my lifeless backup to update prl and profile... restore went fine but i get the lg logo flash then blacjk screen....going to try again but damn this is one issue that need resolving.. usually i have no problems which is weird cause im not doing anything different maybe been couple weeks since my last restore to lifeless using same backup that wont work now

spleef said:
yeah just happened to me just now too dammit... tried to restore my lifeless backup to update prl and profile... restore went fine but i get the lg logo flash then blacjk screen....going to try again but damn this is one issue that need resolving.. usually i have no problems which is weird cause im not doing anything different maybe been couple weeks since my last restore to lifeless using same backup that wont work now
Click to expand...
Click to collapse
I'm going to try deleting data/app before booting to recovery when I flash from now on to see if it helps. I think something to do with the size of that folder is corrupting data in recovery as it seems to happen only when I run a rom for a few days adding apps. If I flash right away it works fine.
spleef..If you can check data/ folder from twrp before wiping internal data...I wonder if the data/app is from backup or previous rom as I believe it is being corrupted to not be wipable.

spleef said:
yeah just happened to me just now too dammit... tried to restore my lifeless backup to update prl and profile... restore went fine but i get the lg logo flash then blacjk screen....going to try again but damn this is one issue that need resolving.. usually i have no problems which is weird cause im not doing anything different maybe been couple weeks since my last restore to lifeless using same backup that wont work now
Click to expand...
Click to collapse
Bdadd34 said:
I'm going to try deleting data/app before booting to recovery when I flash from now on to see if it helps. I think something to do with the size of that folder is corrupting data in recovery as it seems to happen only when I run a rom for a few days adding apps. If I flash right away it works fine.
Click to expand...
Click to collapse
I'm seeing this happen to a lot of people and I don't understand why. I've been flashing all the ROMS and restoring from backups for months now with no issues. Maybe I just got a lucky phone.
Maybe this will help many of you.
In TWRP 2.5.0.0
Click Wipe
Swipe to Factory Reset
Back button to the Wipe menu
Advanced Wipe
Tick all 4--
Dalvik
System
Data
cache
Back to main TWRP menu and restore/install
Like I said, I've had no issues doing it this way. May the Force be with you.

engine95 said:
I'm seeing this happen to a lot of people and I don't understand why. I've been flashing all the ROMS and restoring from backups for months now with no issues. Maybe I just got a lucky phone.
Maybe this will help many of you.
In TWRP 2.5.0.0
Click Wipe
Swipe to Factory Reset
Back button to the Wipe menu
Advanced Wipe
Tick all 4--
Dalvik
System
Data
cache
Back to main TWRP menu and restore/install
Like I said, I've had no issues doing it this way. May the Force be with you.
Click to expand...
Click to collapse
thanks for the advice but I have wiped every which way including rebooting recovery after wipe before installing..no luck
I think it started from initially wiping internal memory and reloading data from pc backup to get rid of the aosp stuff on the sd card..
My advice to anyone else who wants the sd card back to stock is to leave it alone.

normally i have no problems going back and forth.... want to hear something even weirder.... restored my aokp and it booted into lifeless.... now either i restored lifeless again...which us possible big fingers and always in a hurry... or something very funny going on in my recovery i am on the older version 2.4.4 i think it is haven't updated it yet cause of all the issues people are having and the different wipe area... just seems weird top me but guess its time to do it and at least see if it will help
Sent from my LG-LS970 using xda premium

OK this is crazy...deleted data/app with ROM manager root browser..then entered recovery wiped everything in advanced wipe..system..both caches and data..then rebooted recovery checked data\ there was nothing but \media and a config XML file..then flashed a STK custom ROM...got stuck at lg boot logo. Got back to recovery went to filemanager and there it was data\app with all the apps had had installed in my aosp ROM. Loaded aosp backup and all is fine....but I deleted data\app with root browser and in recovery and still there.. :banghead:
Sent from my LG-LS970 using xda premium

Bdadd34 said:
OK this is crazy...deleted data/app with ROM manager root browser..then entered recovery wiped everything in advanced wipe..system..both caches and data..then rebooted recovery checked data\ there was nothing but \media and a config XML file..then flashed a STK custom ROM...got stuck at lg boot logo. Got back to recovery went to filemanager and there it was data\app with all the apps had had installed in my aosp ROM. Loaded aosp backup and all is fine....but I deleted data\app with root browser and in recovery and still there.. :banghead:
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
I usually wipe all data by all data I mean including data/media then I have no problems. Keep in mind this erases sdcard so you need to have rom on computer and adb push it to the sdcard to flash
Sent from my LG-LS970 using xda app-developers app

I think I will start from scratch with lgnpst and leave the internal memory alone this time and see if that was the cause.
update: Im back to stk going to root then unlock with freegee..Any advice for using freegee it soft bricked me last time and I had to flash tinybin

Well since I went back to unrooted and locked and started from scratch..tried using free gee then flashed tinybins all has gone well..no flashing problems anymore..I think messing with the internal memory is what caused my problems. Been almost a week and I have flashed between several roms and restored from backup many times.
Sent from my LG-LS970 using xda premium

I had not seen this thread before or I would have chimed in by now. My issues don't go back to the 28th; only over the last week. My issue goes like this: I built and flash my own Beanstalk 1.561 ROM, and had no real functionality issues. I played with it for a day or two before realizing I hadn't backed it up. Did that, and at reboot, got a loop. WTF? I immediately thought it was the ROM, so I wiped Factory, dalvik and cache, and ran one of my older back ups. No problem. Flashed a new build of JellyBeer, updated everything, and backed it up. Restart and loop. Now I'm REALLY pissed. Restored my original stock back up; no prob. Okay, now I'm more confused than angry. Go to update my recovery(already running TWRP 2.5, but wanted a fresh install) Install of fresh recovery fails. I forget what the fail was for though, I was spitting nails at this point. Soooooo, really long story a little shorter, I downloaded and reinstalled TWRP 2.5, no problems. Dumped all of my 'standard' flashing files(Banks Gapps, Smoocha kernel, newer ROM downloads, etc), and redownloaded everything. Installed a fresh download of Beanstalk 1.561(build 7/07; original problem was on build 7/05), updated it, and performed a back up. SAME ISSUE. I think you can imagine the string of curses I want to put here. So, for me all back ups older than last week work fine. ANY BACK UP MADE EVEN TODAY FROM ONE OF MY OLDER BACK UPS RESTORES AND BOOTS FINE. But, any back up made form any of my newer builds(7/01 to now) flakes out. I haven't had the time to try other ROMs, and to be honest, I haven't tried to run anyone else's work since trying to install Vectus a few weeks ago. Does anyone have any info, advise, similar experience? This is driving me nuts, so anything would be great. PM me if you want to

BMP7777 said:
I had not seen this thread before or I would have chimed in by now. My issues don't go back to the 28th; only over the last week. My issue goes like this: I built and flash my own Beanstalk 1.561 ROM, and had no real functionality issues. I played with it for a day or two before realizing I hadn't backed it up. Did that, and at reboot, got a loop. WTF? I immediately thought it was the ROM, so I wiped Factory, dalvik and cache, and ran one of my older back ups. No problem. Flashed a new build of JellyBeer, updated everything, and backed it up. Restart and loop. Now I'm REALLY pissed. Restored my original stock back up; no prob. Okay, now I'm more confused than angry. Go to update my recovery(already running TWRP 2.5, but wanted a fresh install) Install of fresh recovery fails. I forget what the fail was for though, I was spitting nails at this point. Soooooo, really long story a little shorter, I downloaded and reinstalled TWRP 2.5, no problems. Dumped all of my 'standard' flashing files(Banks Gapps, Smoocha kernel, newer ROM downloads, etc), and redownloaded everything. Installed a fresh download of Beanstalk 1.561(build 7/07; original problem was on build 7/05), updated it, and performed a back up. SAME ISSUE. I think you can imagine the string of curses I want to put here. So, for me all back ups older than last week work fine. ANY BACK UP MADE EVEN TODAY FROM ONE OF MY OLDER BACK UPS RESTORES AND BOOTS FINE. But, any back up made form any of my newer builds(7/01 to now) flakes out. I haven't had the time to try other ROMs, and to be honest, I haven't tried to run anyone else's work since trying to install Vectus a few weeks ago. Does anyone have any info, advise, similar experience? This is driving me nuts, so anything would be great. PM me if you want to
Click to expand...
Click to collapse
Correct me if I'm wrong, but from some of your posts, i never hear you mention wiping /system. That could be some of the problem. Even restoring should have /system wipes.
Also on your backups are there at least 7 files in each? You might have ticked a button and aren't backing up /boot
Sent from my LG-LS970 using xda premium

engine95 said:
Correct me if I'm wrong, but from some of your posts, i never hear you mention wiping /system. That could be some of the problem. Even restoring should have /system wipes.
Also on your backups are there at least 7 files in each? You might have ticked a button and aren't backing up /boot
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Thanks for the response. I'll check into that advice and post what happened.
Checking on my one back up that I haven't deleted before anything else.This is what I have:
boot.emmc.win
boot.emmc.win.md5
data.ext4.win
data.ext4.win.md5
efs1.emmc.win
efs1.emmc.win.md5
efs2.emmc.win
efs2.emmc.win.md5
efs3.emmc.win
efs3.emmc.win.md5
recovery.log
system.ext4.win
system.ext4.win.md5
It looks right to me, but honestly, I never looked that closely at the files. Looks the same as the other backups.....

BMP7777 said:
It looks right to me, but honestly, I never looked that closely at the files. Looks the same as the other backups.....
Click to expand...
Click to collapse
Compared it to mine and it is. You just have the efs also. Maybe try formating /system then restore.
Also maybe try backing up without efs.
Just more options to try.
Sent from my LG-LS970 using xda premium
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
Also, have you tried a flashable TWRP?
Sent from my LG-LS970 using xda premium

I have had this problem and I thought it was just my ROM, I have been making changes to different apks and then flashing and if it bootloops I restore previous working version. Several times however the restores work and then bootloop or they fail in recovery. When this happens I wipe cache, dalvik, system, internal memory, data, factory reset. Then I go into download mode and LGPNST and flash original stock unrooted, then root then flash teeny bins, then I'm ok. It's a pain, thought it was just from me tinkering with things. Anyway that gets me working again, then I can reflash the ROM.

Update: More recently when I've had this happen I just format data and then push what I'm trying to flash into /data/media. Much easier.
Sent from my LG-LS970 using xda app-developers app