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.

Root + Flash Recovery was successful, but can't flash any roms?

Some background:
-This is my 4th Evo. Previous 3 were all rooted.
-Rec'd the new Evo last Thursday, rooted it immediately using the Auto Root method.
-Everything was successful, and Sprint Lover's ROM was automatically flashed on my phone, until I tried flashing a new rom.
Roms I tried flashing:
-MIUI
-BOS "Royal Liquid"
What happens:
-With MIUI, it flashes, restarts and then boots up all the way and then freezes after 20 secs and restarts, EVERY TIME.
-With BOS, stuck in bootloop. Keeps restarting at the white "htc EVO 4g" screen.
Tried both recoveries, Amon_RA AND Clockword Mod(CWM).
Yes, wiped every time. Even d/led "Calkulin's Format ALL" and flashed it (in Amon RA, it wouldn't let me in CWM.)
Please help, and ask me any questions you may need. I'll do my best to provide every answer.

I'm dealing with the same issues except i was trying to flash to Koni Elite 3

I'm can't even do a restore,cuz i get a recovery error.

Update i can do a recovery to an old backup

androidrookie84 said:
Update i can do a recovery to an old backup
Click to expand...
Click to collapse
Next time just update your same post or make a thread of your own. No sense of posting your problems in someone's else's problems thread. But I'm glad it's working for you now.
[Update]
Just d/led and flashed CM7 using ClockwordMod. Everything seems to be working fine.
I don't know what's going on anymore.
I am going to try to flash BOS Royal Liquid again and see what happens.

Make sure your device still displays "S-OFF" in the bootloader screen. Reflash amon RA or flash amon RA v2.3 and then go to the wipe menu and wipe EVERYTHING in it except the SD card itself. Now flash the rom you want to flash.
posting & replying via the XDA Premium app.

Yes Sir!
arozer said:
Next time just update your same post or make a thread of your own. No sense of posting your problems in someone's else's problems thread. But I'm glad it's working for you now.
[Update]
Just d/led and flashed CM7 using ClockwordMod. Everything seems to be working fine.
I don't know what's going on anymore.
I am going to try to flash BOS Royal Liquid again and see what happens.
Click to expand...
Click to collapse
Sent from my PC36100 using Tapatalk

dougjamal said:
Make sure your device still displays "S-OFF" in the bootloader screen. Reflash amon RA or flash amon RA v2.3 and then go to the wipe menu and wipe EVERYTHING in it except the SD card itself. Now flash the rom you want to flash.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
In the bootloader, my info reads:
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
Not sure if any of that means anything.
Also, I tried that, and nothing! =[
-D/led Amon_RA v2.3 from his post. Flashed it using Terminal Emulator.
-Flashed Calkulin's Format ALL
-Wiped everything but "SDCARD" and "SDCard:.android_secure"
-Flashed ROM BOS.. and same thing; bootloop...
One thing I noticed is that when I try to Wipe Dalvik Cache in Amon-RA, it says:
"Formatting DATA: dalvik-cache...
Formatting CACHE: calvik-cache...
Skipping format SDEXT:dalvik-cache...
DALVIK-CACHE: wipe complete!"
That 3rd line kinda has me worried.. I don't think I ever seen that before.
And when I try to Wipe Dalvik-Cache in CWM, it gives me:
"E: unknown volume for path [/sd-ext]"
even BEFORE I select "yes" from the menu.
Once I select "yes".. IMMEDIATELY it says "Dalvik Cache wiped."
I don't remember that either from my previous phones.
ALSO TRIED..
I just Flashed an older version of CWM(v2.5.0.7) that allows to flash Amend zips.
-Then tried wiping, and when I tried wiping "Dalvik-cache" this is what I got:
"E: Can't mount /dev/block/mmcblk0p2
(File exists)"
Could that be the problem?

[Another update..]
When I try to flash the Royal Liquid ROMS in CWM, it gives me an error saying something like:
"Cannot install because of Android 1.5 or something.
It was necessary to something something Android 3.0 Gingerbread" or something like that.
Does this mean I can only flash Gingerbread ROMS.. which is CM7 is the only one that works?

The error when trying to flash the BOS rom is because of how it is packed. A lot of people still like to packages their ROMs using an older way that I guess google and Kush are wanting to phase out. It should flash ok with clockwork 2.5 or Amon RA's.
With the reboot issue it sounds like something may have gotten corrupted on your phone. If you still have the autoroot folder on your computer try making a backup on just your Data and .android partitions, and then run the FlashZip script that comes with autoroot and use it to flash the PC36IMG_SprintLovers...zip. That one should give you a clean flash that you can work from. It may be a good idea to mount your sd card as a disk drive and scan it for errors too, a corrupt sd card can do all sorts of weird stuff.

xHausx said:
The error when trying to flash the BOS rom is because of how it is packed. A lot of people still like to packages their ROMs using an older way that I guess google and Kush are wanting to phase out. It should flash ok with clockwork 2.5 or Amon RA's.
With the reboot issue it sounds like something may have gotten corrupted on your phone. If you still have the autoroot folder on your computer try making a backup on just your Data and .android partitions, and then run the FlashZip script that comes with autoroot and use it to flash the PC36IMG_SprintLovers...zip. That one should give you a clean flash that you can work from. It may be a good idea to mount your sd card as a disk drive and scan it for errors too, a corrupt sd card can do all sorts of weird stuff.
Click to expand...
Click to collapse
Just tried it. Same thing bro.
What I did:
-Backed up CM7 in CWM.
-Flashed Amon_RA v2.3 via Terminal Emulator
-Backed up data and .android partitions in recovery
-Restarted phone and ran "FlashZip", chose Option 1 "SPrintLover....zip"
-Flashed it successfully.
-Restarted phone to make sure it works. Went back into recovery and wiped everthing (factory reset, cache, dalvik cache and data), also flashed "Format All"
-Tried flashing BOS and bootloop again.

arozer said:
Just tried it. Same thing bro.
What I did:
-Backed up CM7 in CWM.
-Flashed Amon_RA v2.3 via Terminal Emulator
-Backed up data and .android partitions in recovery
-Restarted phone and ran "FlashZip", chose Option 1 "SPrintLover....zip"
-Flashed it successfully.
-Restarted phone to make sure it works. Went back into recovery and wiped everthing (factory reset, cache, dalvik cache and data), also flashed "Format All"
-Tried flashing BOS and bootloop again.
Click to expand...
Click to collapse
Have you tried pulling your sd card to see if that could be doing it?
Sent from my PC36100 using XDA Premium App

xHausx said:
Have you tried pulling your sd card to see if that could be doing it?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I'm sorry, I don't know what you mean by "pulling the sd card". Care to elaborate?
Also an update:
While trying to get BOS to work, I was stuck in bootloop.
So I reflashed it again without wiping anything.
It bootlooped 4 times and then PHONE TURNED ON!! Using BOS rom.
However, same as MIUI, about 10 secs into it, the phone freezes and restarts.
What do you think it could be?
MIUI does the same thing, except the whole bootloop trial.

arozer said:
I'm sorry, I don't know what you mean by "pulling the sd card". Care to elaborate?
Click to expand...
Click to collapse
Try pulling the sd card out of the phone to see if anything changes. You can find it under the battery.
Sent from my PC36100 using XDA Premium App

xHausx said:
Try pulling the sd card out of the phone to see if anything changes. You can find it under the battery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Lol. Wow bro, way to put it like that and make me feel silly.
I thought maybe "pulling the battery" has a different means in terms of rooting.
And yes, I re-flashed BOS and powered the phone off,
-removed SD card
-Restarted and again, stuck in bootloop.
Btw, did you see my update in my previous post?
Also, I thank you VERY much for taking your time to try and help me.
Seems like only Gingerbread based roms (like CM7) are working. I haven't tried any other ones, other than Sprint Lovers and CM7, but they seem to work perfectly fine without ANY problems.

Have you tried:
Pulling the battery, going back to recovery and wiping dalvik and cache again then rebooting (sorry if I missed you doing this)
or
Re-downloading the BOS ROM, could be a bad download, esp if downloaded from your phone
or
Flashing a completely different ROM like Unleashed, Myn, EViO or MikFroyo?

Sorry, didn't mean for it to come across like that. It's possible there is just something about that ron that doesn't want to work with your phone.
If you want to send me the logcat I can take a look at it for ya.
Sent from my PC36100 using XDA Premium App

jstalford said:
Have you tried:
Pulling the battery, going back to recovery and wiping dalvik and cache again then rebooting (sorry if I missed you doing this)
or
Re-downloading the BOS ROM, could be a bad download, esp if downloaded from your phone
or
Flashing a completely different ROM like Unleashed, Myn, EViO or MikFroyo?
Click to expand...
Click to collapse
Yes. Just tried that brother and doesn't work. (referring to 1&2)
I will try downloading another rom now.
Hopefully BOS and MIUI are just having their own problems, as CM7 works just fine.
xHausx said:
Sorry, didn't mean for it to come across like that. It's possible there is just something about that ron that doesn't want to work with your phone.
If you want to send me the logcat I can take a look at it for ya.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Where do I find the logcat? Sorry.. just don't to send you the wrong one.

Spiicytuna said:
Option #1
1. Download aLogcat from the market
2. Launch the aLogcat
3. Go launch the program thats crashing, allow it to crash
4. Go back to aLogcat
5. Menu -> Send
6. Email it to yourself, then post it on here for shinzul/toast + thread
Option #2
1. Hook your phone to your computer with the usb cable
2. With your fav CLI type: "adb shell logcat > crashlog.txt" (w/o the " ")
3. On the EVO launch the program that's causing problems, allow it to crash
4. In the CLI hit "crtl+c" (to stop the logging process)
5. In the same folder as adb will be a text file called "crashlog.txt"
6. Post it on here so that shinzul/toast + thread can take a look at it
Option #3
1. open terminal on your phone
2. if the character showing is a '$' type "su"
3. type "locat > /sdcard/logcat.txt"
4. post the logcat.txt file on your SD card on here so that shinzul/toast + thread can take a look at it
Click to expand...
Click to collapse
Instructions on how get a logcat

[Q] tried supersonig nightly rom and something is wrong

first time trying to root and did it with su-2363 and it was fine
went to sd card deleted su-2363 file added the newest supersonis nightly file, went in to Hboot ran everything. chose reboot and now i just have a OMFGB door that opens to the painting of the evil gingerbread man over and over again, even after i pull batt and turn on this is all it does. can anyone help

tattoo jaco said:
first time trying to root and did it with su-2363 and it was fine
went to sd card deleted su-2363 file added the newest supersonis nightly file, went in to Hboot ran everything. chose reboot and now i just have a OMFGB door that opens to the painting of the evil gingerbread man over and over again, even after i pull batt and turn on this is all it does. can anyone help
Click to expand...
Click to collapse
Probably a bad flash or something. Turn on your phone while holding the volume down. Once in the boot-loader go into recovery. From recovery mount USB storage and try some other ROM. For simplicity i would go with CM7 stable it's always booted up for me just fine and ive never had problems flahing it. Remember before flashing to Factory reset data, wipe cache, wipe dalvik cache then flash the rom. Once your on CM7 or a different rom do some more research and try again.
Also please post your questions in the Q and A forum.
Oh btw if you have a nandroid backup restoring that might work. Making on of your stock rom would of been a good idea if you didnt.

sorry about posting here
phone had cm7 when i got it but it has lots of problems and i decided to take it to sprint and they put it back to stock.
and i hate stock so i tried to root it watching a utube video, with a rom i got here.
i did get into Hboot and put the SU- zip in the sd card and deleted the supersonic zip and tried to update with it but still having same prob, i'll try clearing the stuff you said to clear.

[Q] Stuck in Bootloop *done all the basics to fix*

First let me say...its been awhile since I have posted here, I love the auto search based on the title of a post lol. That is awesome. Needless to say I didn't find anything related to my issue...
Here we go,
I have had my phone rooted forever and a day. I have only ever used fresh roms since It's been rooted. ( about a week after launch ) The issue popped up about a few months or so ago with one of his updates. No matter how i tried to download or install it would always bootloop. I have done the full data, dalvic, cache wipes and got the same results. I figured *f* it and just went back to my nandroid of the old version and forgot about it.
There have been several releases that I have tried from fresh that did the same thing. I figured tonight I would try the synergy rom for something new and to see if my phone would take it. I was using clockwork mod for my recovery. I did a nandroid of my phone and away I went.
I flashed amon_ra since that is synergy's recovery of choice and went through the whole process.
3 hours later...here I am with a phone still stuck in a bootloop when i try the rom and now I learned for some reason that amon_ra nandroid restore is not compatiable with the ones from clockwork that i have on my phone. *quick edit* I have also tried downloading several other roms, and am having the same issues.....even tried redownloading the same roms several times thinking it was a corrupt download or something.
There was one restore available that took me back to what seems to be an unrooted phone. I still have access to the recovery and am able to flash roms, but all the sprint crap is back and I don;t have superuser on the phone anymore.
So there is my story. I am an old hand at flashing and know how to wipe and all that before installing and i seem stuck to use this OG sprint crap for the rest of my contract, unless one of you wonderful phone guru's can point me in the right direction.
~owl

There's a thread here with the SU 3.0
install that, go to menu in the app, make sure that permission is toggled on

HipKat said:
There's a thread here with the SU 3.0
install that, go to menu in the app, make sure that permission is toggled on
Click to expand...
Click to collapse
Well at least i can get SU back on the device...
any more advice as to why the phone is refusing to flash any rom??

Maybe try a superwipe script or wipe everything like boot and all except SD card
Sent From My Pocket

{ParanoiA} said:
Maybe try a superwipe script or wipe everything like boot and all except SD card
Sent From My Pocket
Click to expand...
Click to collapse
+1
I usually wipe everything 3 times in Amon then a superwipe zip after that.
Gotta be clean

YEah, do a wipe of everything except SDCard: and Battery stats, if you're not fully charged. Wipe Cache and Dalvik-Cache a few times each. I don't use superwipes myself, but anyhow, after that, flash a stock ROM. Make a nandroid of it, if your phone boots up fine.
Then go back, wipe everything again and flash the ROM you want to use.

I really want to thank all of you that have taken the time to post some ideas here for me, but as of right now I have had no love from my phone with any of them.
It will flash a radio just fine, flash wimax fine as well, but no love for the ROMS.
Anymore ideas out there??

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