Related
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??
I am currently running andybonestock ROM as my "stock" ROM. I've wanted to try out the newer Sense ROMs but I keep running into a problem. Every ROM no matter what will eventually (and it usually happens after an hour) start endlessly rebooting. Let me clarify, it will reboot, load initially and then start rebooting all over. Now let's specify what I do every time I try to flash one, and maybe I'm doing something wrong.
My first step is always to backup in recovery. The next thing I do is run the super wipe script, followed by wiping cache, dalvik, and then running super wipe again. Then I choose the update file and update. I reboot my system and let it fully load. I run and complete the setup where it asks you for email and wifi etc. Finally I install and run Titanium. Now maybe this is my problem but I've read many times this is how to do it but correct me if I'm wrong. I selected batch restore and let it restore missing apps with data.
I'd really like to run a ROm I liked but can't deal with the rebooting. Any help would be greatly appreciated. And I've tried searching to no avail.
Thanks
Sent from my Droid Inc2 using Tapatalk
Try to restore apps, but not their data. You're going from sense to sense rom, so it seems like that shouldn't be an issue, but I think you should give it a shot.
but then what's the point of Titanium? if I'm losing the data, it's no different then restoring it via Google
Its either the data or the super wipe scipt seems they cause more problems than they help.
What recovery are you using? I've been running ext4 and the format all except SD and it never gave me any problems. What's with everyone wanting super wipes when you should be able to do everything in whatever recovery your using?
I'm using clockwork and I figured superwipe is more efficient
Maybe idk all that technical stuff. Try 4ext recovery its a lot better than cwm. If you don't wanna mess with a new recovery then just try using the wipes in cwm
Linch89 said:
Maybe idk all that technical stuff. Try 4ext recovery its a lot better than cwm. If you don't wanna mess with a new recovery then just try using the wipes in cwm
Click to expand...
Click to collapse
I appreciate the help but I doubt it's that but ill try it. Anything else
Sent from my Droid Inc2 using Tapatalk
what are you restoring with titanium backup? restoring app data for market apps is fine, dont restore system data though
nitsuj17 said:
what are you restoring with titanium backup? restoring app data for market apps is fine, dont restore system data though
Click to expand...
Click to collapse
Yup, I have made that mistake myself.
I've flashed many different sense roms and AOSP roms. I recommend getting 4ext recovery because it has a format partition option that's really easy to do. I format all partitons (except sdcard) and then i wipe data/factory reset. I've never had any issues with flashing roms sense or AOSP. Titanium Backup I only restore data for games, but going from AOSP you must just restore apps.
hakoreh said:
Every ROM no matter what will eventually (and it usually happens after an hour) start endlessly rebooting. Let me clarify, it will reboot, load initially and then start rebooting all over.
Click to expand...
Click to collapse
I have the exact same problem (only with Sense 3.5 ROMs, though), and it happens even when not restoring apps/data.
It's kind of sad, as I was enjoying trying out different ROMs, but no amount of wiping with different recoveries or superwipe have helped.
I half wonder if many of the roms are OCed, and my phone can't handle that, but I've tried flashing different kernels right after the rom, and it still happens.
I must say i don't re-flash to AOSP, but i restore my nandroid backup. However, I do format my partitons and wipe data/reset before restoring. I can try flashing MIUI 1.12.9 and then flashing sense 3.5 rom again. I'll be able to do it tomorrow. I'll let you know.
I guess I'll just try a Sense 3.0 rom
Sent from my ADR6350 using Tapatalk
hakoreh said:
I guess I'll just try a Sense 3.0 rom
Sent from my ADR6350 using Tapatalk
Click to expand...
Click to collapse
so I tried a Sense 3.0 ROM and even a Sense 2.1 ROM and still no dice. While the ROM did last a whole day without restarting, it did not hold and went into its usual boot loop again.
I'm really annoyed but want to try something new. I have 4EXT recovery now.
Does anyone know anything else I can try???
TY
OK I've had it. I even tried it without restoring anything from scratch and still eventually get restart errors
Sent from my Droid Inc2 (ICS wanted) with Tapatalk
hi all,
i've got a problem installing ROM as of few days back. let me explain the details.
i'm running Seb's AIO 6.1.1, CM7r2 hboot, s-off, touch recovery, 1GB ext4. the rom works well, as any i've tried before. no matter was it gb ROM, hybrid sense 2+3, ics, with different required hboots, you name it....
no problems at all, except i'm constantly near "low internal memory" warning (i like to try many apps). so i wanted to reinstall but with INT2SD script. (did that too, before, and it worked). i did nand backup, full wipe (everything but sdcard), installation went fine from same downloaded .zip file as before, no problems at all. but... of course, but...
now i'm stuck at htc logo for about 40 minutes. no boot animation, no nothing... battery pull and retry didn't help either. so i tried reinstalling, with classic a2sd, with ad2sdx, with m2sd, with int2sd again... every time same result - stuck at htc logo.
but, this is curious part: nand restore works like a charm!! i'm clueless at this point. i'm only imagining it could be something on sd card. i tried K900's ics rom before trying to reinstall AIO, and i also installed this tweak (http://forum.xda-developers.com/showthread.php?t=991276) which left some things on sdcard, but i deleted them and again no result.
does anyone have some vague idea what could be going on? i left formating sd card as a last resort. i'll do that if nothing else works. so, any suggestions? any help appreciated...thx!
Don't you need the custom hboot with large system partition for an INT2SD install (sorry wasn't clear if you changed that or not). Presume nandroid works fine as it fits in CMR2 hboot.
First of all the V6 Supercharger it's not the problem!
After that, wich a2sd method use your nandroided ROM? Have you tried to check if the EXT4 partition is alligned and don't have a corrupted fs?
Last resort is to try to format again your SD card with 4ext; remember to do an SD backup an do things "from scratch"
there are 2 int2sd versions. for int2sd-m you need special hboot, but for int2sd-s cm7r2 is just fine.
i did change it to cm7r2 for this rom, and it had worked so far without problems.
for second suggestion, i formated sd card with 4ext recovery, so it's good. i'm going to format sd card tonight and see how it goes. don't have more options atm, i'm afraid...
thx, guys. any more thoughts on this?
edit: nandroided uses built in a2sd. but new install with it doesn't boot. and i always do full wipe. that should clear things, right?
Sent from my HTC Desire using Tapatalk
Never happened something like this to me
It's really strange, it seems like you have a problem with the "install from SD" in recovery! If after the repartition of your SD you still have this problem, try to flash again your recovery from fastboot! Hopes this will help you
thank you, i'll try that. i've reformated sdcard yesterday, zipaligned it and ext4 partition, still no luck.
maybe it really is recovery issue. and i'll try another rom also, just to be sure...
Sent from my HTC Desire using Tapatalk
again, no luck!
i've updated 4ext recovery via update app, downloaded again cm7r2 boot image, just in case my got corrupted somehow, flashed it again - in hboot says alpharev cm7r2, so i guess all is fine.
i've installed sandvolds ICS (supports cm7r2) just to try something different, and it BOOTED WITHOUT A PROBLEM!! the phone booted just fine, quick, everything was as it should be. then, i went to install Seb's rom again. guess what? no luck. again stuck at htc logo. i don't get it anymore.
the recovery works fine, hboot seems OK, other roms install fine, sdcard is not an issue (since it was completely empty last night), seb's rom is also fine i guess since i've installed it couple of times before and i've downloaded it again and checked md5 sum.
i've got damn poltergeist in my phone!!!! i quit. don't know what else could i try. good thing that nandroided install of the same seb's rom still works. go figure!!! what could be the issue here is beyond me. i think i've tried everything.
thx for your help anyway. i'm still open for suggestions...cheers!
Well... now the problem it's only the ROM zip or the SD card try to install the ROM after you restore your nandroid and do a factory reset (not full wipe!).
If it still not boot, try to delete the a2sd scripts from /system/etc/init.d with adb and reboot.
If it still not work, try another SD! Wich class it's your SD? Remember that class 10 SD cards don't work well with the desire!
hm...shouldn't full wipe have cleared those things? i mean, system partition gets formated also...
can i delete a2sd script from root explorer before booting into recovery and wiping/flashing? (i'm not so familiar with adb )
i've got class 4 card...
heraSK said:
hm...shouldn't full wipe have cleared those things? i mean, system partition gets formated also...
can i delete a2sd script from root explorer before booting into recovery and wiping/flashing? (i'm not so familiar with adb )
i've got class 4 card...
Click to expand...
Click to collapse
No, i mean:
Restore your backup
Enter recovery and do a factory reset
Install the ROM
Reboot
If it isn't working try to delete via fastboot & ADB the a2sd files in init.d
doh! sorry, i'm at work, trying to do this between customers...;-)
okay, after restore i did factory reset and install rom again over it. of course, no go. now i'm trying to find init.d folder via adb. again no luck. (maybe i should just drop this and go knit or something...) i did see init.d folder via root explorer but can't find it anymore.
i'll try a bit more, if this doesn't work i'll just call it a day, restore nandroid and wait for a new version from seb. maybe things'll sort themselves out.
thx a lot for your help, buddy. cheers!!
heraSK said:
doh! sorry, i'm at work, trying to do this between customers...;-)
okay, after restore i did factory reset and install rom again over it. of course, no go. now i'm trying to find init.d folder via adb. again no luck. (maybe i should just drop this and go knit or something...) i did see init.d folder via root explorer but can't find it anymore.
i'll try a bit more, if this doesn't work i'll just call it a day, restore nandroid and wait for a new version from seb. maybe things'll sort themselves out.
thx a lot for your help, buddy. cheers!!
Click to expand...
Click to collapse
Eheheh, no problem at all!
Last try! Check the last "todo" i sent you and before the number 3 do:
Open a copy of the ROM with WinRAR or 7zip
Go to /system/etc/init.d
Delete everything that have a2sd, mount etc in the name
Install the ROM
Well, we are at the point we need to run the damned ROM to verify what's doesen't working
If this isn't working... well, you have to wait! Have you tried an older version of the rom? When you restore your nandroid everything run without problem? You can see every apps you have installed?
you could be on right track here. i'm too guessing it's something script related. i've installed it with built in a2sd script. then i flashed m2sd (this rom supports init.d), but this script didn't work, it didn't move dalvik to sdext (hence me trying to do it from scratch in a first place).
few minutes ago i found m2sd thread where people are saying same things but with different roms: doesn't move apps, data, dalvik or whatever, and they're stuck at boot logo.
now i just have to clear all these scripts, and your method might work. but how is it so that full wipe doesn't undo all what i've made? i thought that "full wipe" means "delete all"...
i'll try nand restore and flash new m2sd script version which should clear all other scripts. after that i'll try clean install and again flash new m2sd. if THAT doesn't work i'll grab a bear and hide damn phone somewhere untill tomorow. i've been digging around this whole day, i didn't notice the time...need some rest!!
EDIT: yeah, i tried older versions, all was fine. nandroid works like a charm, all apps are there. i'm guessing something is stuck on the phone which conflicts with fresh install. but, how come ICS from sandvold installed without a problem?
thx again!
heraSK said:
doh! sorry, i'm at work, trying to do this between customers...;-)
okay, after restore i did factory reset and install rom again over it. of course, no go. now i'm trying to find init.d folder via adb. again no luck. (maybe i should just drop this and go knit or something...) i did see init.d folder via root explorer but can't find it anymore.
i'll try a bit more, if this doesn't work i'll just call it a day, restore nandroid and wait for a new version from seb. maybe things'll sort themselves out.
thx a lot for your help, buddy. cheers!!
Click to expand...
Click to collapse
Can normally find scripts in system/etc/init.d folder - soz, not familiar with INT2SD as you probably guessed.
Maybe Gparted for the partitioning instead of recovery?
heraSK said:
you could be on right track here. i'm too guessing it's something script related. i've installed it with built in a2sd script. then i flashed m2sd (this rom supports init.d), but this script didn't work, it didn't move dalvik to sdext (hence me trying to do it from scratch in a first place).
few minutes ago i found m2sd thread where people are saying same things but with different roms: doesn't move apps, data, dalvik or whatever, and they're stuck at boot logo.
now i just have to clear all these scripts, and your method might work. but how is it so that full wipe doesn't undo all what i've made? i thought that "full wipe" means "delete all"...
i'll try nand restore and flash new m2sd script version which should clear all other scripts. after that i'll try clean install and again flash new m2sd. if THAT doesn't work i'll grab a bear and hide damn phone somewhere untill tomorow. i've been digging around this whole day, i didn't notice the time...need some rest!!
EDIT: yeah, i tried older versions, all was fine. nandroid works like a charm, all apps are there. i'm guessing something is stuck on the phone which conflicts with fresh install. but, how come ICS from sandvold installed without a problem?
thx again!
Click to expand...
Click to collapse
I had the same problem with m2sd! I found from the log (in terminal: su - m2sd log) that another script mounted my ext before m2sd... after install i've removed 05Mountsd from init.d and the script started working it seems the script doesn't recognize all the scripts that mount the SD before him!
Edit: full wipe means every partition get formatted, while the factory reset only data (not only dalvik) and cache, leaving system intact; some ROMs don't wipe system before install, so i hoped your previous system had some of the missing file in the new system this part is hard to explain with my lack in english
Edit2: why you like so much AIO? I'm not a sense enthusiast (i love minimalistic graphic like ICS) and i'd like to know what's the strenght of AIO !
hehe, i guess you would have to be Sense fan to like AIO. it's probably most stable and complete GB rom right now. but that's just my opinion.
ics doesn't do it for me as GB. yet, that is... ;-)
Sent from my HTC Desire using Tapatalk
just to inform you, i've succeeded to instal damn thing finally. after restore i've deleted all scripts from init.d folder, even those supercharger made, via root explorer. then, in recovery wiped it all, and installed the rom with int2sd script.
i didn't want to use it, since it's a bit slower than regular a2sd script, but i gave it a go and it worked. i don't know if deleting scripts did the trick or this int2sd script. i don't have the strength to try again with a2sd or m2sd.... i'll see how it behaves, maybe i just have to give it some time to settle down so the lag will go away...
cheers mate!
heraSK said:
just to inform you, i've succeeded to instal damn thing finally. after restore i've deleted all scripts from init.d folder, even those supercharger made, via root explorer. then, in recovery wiped it all, and installed the rom with int2sd script.
i didn't want to use it, since it's a bit slower than regular a2sd script, but i gave it a go and it worked. i don't know if deleting scripts did the trick or this int2sd script. i don't have the strength to try again with a2sd or m2sd.... i'll see how it behaves, maybe i just have to give it some time to settle down so the lag will go away...
cheers mate!
Click to expand...
Click to collapse
Grats!!! At least you did it
But... by "wiped it all" you mean a full wipe? If you did that you erased everythin' in system too, so you installed a brand new ROM as before and your erased init.d means nothing! If it's that the case i cannot point out your problem
I'm curious about you trying another AIO rom you became my guine pig
Now that everything is almost setted, i suggest you to try Total Commander for Android instead of Root Explorer, it's a little hard to learn but gives great results if you want to know how to use it pm me
Ryther said:
by "wiped it all" you mean a full wipe? If you did that you erased everythin' in system too, so you installed a brand new ROM as before and your erased init.d means nothing! If it's that the case i cannot point out your problem
I'm curious about you trying another AIO rom you became my guine pig
Click to expand...
Click to collapse
that's exactly what's been bugging me the whole time! but the fact is that the issue has wanished after I've deleted scripts and supercharger from init.d folder. of course, that could only be coincidence, and the real reason could be God knows what.
thx for your suggestion but I'm fine with root explorer. but I'll be happy to provide you with AIO info. just pm me with anything you would like to know.
Sent from my HTC Desire using Tapatalk
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.
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