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
Related
So after seeing a Jelly Bean rom on here, I decided to download it and flash it. I did a nandroid backup first and then flashed the rom. Wouldn't boot. Basically it would vibrate with the Google screen then reboot over and over again. Tried to do a nandroid RESTORE and it gave me an error about restoring /data. Tried other backups and they gave me the same error. Tried to flash a completely different ROM and bootlooped on the Google screen. I saw that people were having errors with the TOUCH CWM so I reflashed the nontouch Recovery Image and I am getting the same results. I think I ****ed my phone. I have no other ideas so I am turning to the communty for help with this. I'm out of ideas. PLEASE HELP! Thanks!
Might be a stupid question but did you do the wipe/factory reset, wipe cache, wipe dalvik prior to the flash? Just asking...
drew_grant said:
So after seeing a Jelly Bean rom on here, I decided to download it and flash it. I did a nandroid backup first and then flashed the rom. Wouldn't boot. Basically it would vibrate with the Google screen then reboot over and over again. Tried to do a nandroid RESTORE and it gave me an error about restoring /data. Tried other backups and they gave me the same error. Tried to flash a completely different ROM and bootlooped on the Google screen. I saw that people were having errors with the TOUCH CWM so I reflashed the nontouch Recovery Image and I am getting the same results. I think I ****ed my phone. I have no other ideas so I am turning to the communty for help with this. I'm out of ideas. PLEASE HELP! Thanks!
Click to expand...
Click to collapse
I'm guessing you flashed the Vicious Version? Same thing happened to me today except it booted for like an hour then shut itself down and never booted all the back up. I had to flash a factory image through GNex Toolkit. I tried all kinds of things; restore a nandroid of cm9, Aokp, Stock, reflashing, nothing. So I hate to say it but looks like your going to be spending some time with fastboot tonight...
I really hope someone can prove me wrong though, cuz factory img wipes everything including SD.
Mikef3j said:
Might be a stupid question but did you do the wipe/factory reset, wipe cache, wipe dalvik prior to the flash? Just asking...
Click to expand...
Click to collapse
First thing I did.
xIC-MACIx said:
I'm guessing you flashed the Vicious Version? Same thing happened to me today except it booted for like an hour then shut itself down and never booted all the back up. I had to flash a factory image through GNex Toolkit. I tried all kinds of things; restore a nandroid of cm9, Aokp, Stock, reflashing, nothing. So I hate to say it but looks like your going to be spending some time with fastboot tonight...
I really hope someone can prove me wrong though, cuz factory img wipes everything including SD.
Click to expand...
Click to collapse
I'm all out of ideas. I've been spending 2 hours on this. This looks like my only option. Even worse for me, I can't access the GNEX Toolkit because I have a Mac. Do you have the file or the link to the file you flashed?
drew_grant said:
I'm all out of ideas. I've been spending 2 hours on this. This looks like my only option. Even worse for me, I can't access the GNEX Toolkit because I have a Mac. Do you have the file or the link to the file you flashed?
Click to expand...
Click to collapse
Use fastboot.
Sent from my Xoom using xda premium
Has anyone determined why this is happening with the new JB roms? I got stuck in this situation last night and would love to try again if I could just figure out where I went wrong the first go around.
This is srsly the last time I'm posting this.
Code:
adb pull /data/media/ /SDBACKUP/
To get your SD contents back.
Then fastboot flash back to stock.
JB changes the directory that your data resides in...which seems to be why many are having problems.
I, however, have swapped back to an AOKP nandroid just fine.
Hi xda,
I ran into a problem I've never faced today. Before you start assuming, I've done my research. I've searched all over the forums, tried multiple solutions (none worked) and... potentially permabricked it?
Rooted for 7 months, running Jedi Mind Tricks v5.1 Android 4.0.3
How it happened: Today I noticed my phone running really wierdly. It would crash apps constantly, which didn't happen yesterday. So I put it on *close all apps after exiting* on developer options and limited it to run 2 background apps. Throughout the day, my phone would just restart out of absolutely nowhere: in the middle of a text, after unlocking my phone. Each time progressively got shorter between the restarts. It would also freeze a lot of the time. This never happened before today. Maybe a freeze or two, but not this bad.
Did a few battery pulls, no dice. Then this is where it gets worse. The time between boot loops were from 1-2 minutes now. I was getting pissed, so I decided I needed to wipe it and install a new rom. I enter recovery mode CMW 5.0 and do an initial factory reset. Half way through, it crashes again. Now all it does is vibrate constantly until I turned it back on into recovery. Launches recovery. I try to super wipe it. Half way through, crashes again. I try this several times in conjunction with battery pulls. Doesn't work.
I pull sim card, SD card and battery out, let it rest before I reset it.
Then I tried to Odin its ass. I bricked it into the yellow warning screen about a updated system error because I fail with Odin. I searched around to find a solution. I redid Odin to stock kernel it. When it revived, it went into the loading screen. Yes! Progress! It was 99% done with loading when it froze on it. Fml. Battery pull, reboot, and it goes back into its habitual boot loop pattern. I can still access CMW, but it still crashes when I try to super wipe/wipe it.
I have to fix this because, well I bought this from someone with no warranty and using a no contract provider.
Help?
UPDATE: I was able to successfully superwipe my phone, then reinstall Mind Tricks as the rom of choice onto it. It doesn't freeze. Simply bootloops again and again. I don't know what to do.
eaudexs said:
UPDATE: I was able to successfully superwipe my phone, then reinstall Mind Tricks as the rom of choice onto it. It doesn't freeze. Simply bootloops again and again. I don't know what to do.
Click to expand...
Click to collapse
Firstly I suggest upgrading your recovery to 6.x via odin. Then superwipe. Redownload mind trick fresh, flash mind trick, wipe data/factory reset via recovery and try to boot letting it settle for about five minutes. If this fails, flash back to stock via Odin to rule out hardware faults.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
Firstly I suggest upgrading your recovery to 6.x via odin. Then superwipe. Redownload mind trick fresh, flash mind trick, wipe data/factory reset via recovery and try to boot letting it settle for about five minutes. If this fails, flash back to stock via Odin to rule out hardware faults.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I've been looking through some how-to's but I can't seem to find how to upgrade recovery using odin. I can only find the .img file and instructions on how to do it via command lines. Any advice?
Thanks
Good suggestion but better yet ...... I had the same issue on cwm.... get twrp 2.2 look for the flashable download....... 2.3 has a few bugs so stick wit .2
Sent from my SGH-T989 using xda app-developers app
Definitely get twrp on it. Flashing twrp solved 99% of my problems running cm10. Zero rr in weeks. If I were you I would go back to stock for your device. After confident its running like it should. Then root and and go nuts.
I've personally never really had to pull the battery, very rarely. I'm worried about your ram. Could it b corrupted? A short somewhere? All unrecoverable.
I wonder if you could somehow mount your device using Linux. And run memory tests or drive diagnostics.(just thinking out loud).
Twrp is definitely a must. Good luck
Sent from my cm_tenderloin using xda app-developers app
Try doing complete wipes and reflashing a different more stable rom and see if it happens again. There are scripts to do complete and total wipes just to make sure you get a clean install (kind of like the others suggested) atleast yours can turn on so your not hard-bricked.
That's great how you guys are saying twrp solved your issues! It's really funny when cm10 supports cwm recovery. But op, let me see if I still have mine.
Sent from my SGH-T999 using Tapatalk 2
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
eaudexs said:
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
Click to expand...
Click to collapse
my sgs2 did this last month i did the same you did. after no fix i installed a cwmtouch through odin just to be able to restore a back up and worked flawlessly. After that i switched to TWRP again flashed it with no problem through odin and my s2 has been working fine ever since, but fyi i updated twrp to its 2.3.1.1 version and now i get errors can still restore but cant flash jb roms and can only do dirty flashes of ics roms
I'm currently in the process of trying to flash twrp. Is it uncommon that when I went into recovery, it also boot looped on me several time?
eaudexs said:
I'm currently in the process of trying to flash twrp. Is it uncommon that when I went into recovery, it also boot looped on me several time?
Click to expand...
Click to collapse
what version of TWRP are you trying to use? NO it does not bootloop
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
eaudexs said:
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
Click to expand...
Click to collapse
Nah my man you do not use the script with CWM6 thats your problem right there
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
eaudexs said:
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
Click to expand...
Click to collapse
Come on now the flashable version is in the thread...tisk tisk tisk also there are a few version in flashable form in there as well my friend. Got to get your hands dirty sometimes.... LOL Good luck
http://forum.xda-developers.com/showpost.php?p=32984410&postcount=380
Thank you my friend. I was able to finally find a 2.2 TWRP and I flashed it via odin. Did full wipes, full cache wipes, flashed a rom. Fixed permission and all that good stuff. Left it off for 10 minutes. Came back, it started running through initialization. About 4 minutes in, it crashes again. I'm starting to think this could be hardware problem.
eaudexs said:
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
Click to expand...
Click to collapse
Do not use scripts with the new CWM 6 as it will cause this. Manually wipe everything and do not use scripts. You can use scripts with twrp but not the latest cwm
Sent from my SAMSUNG-SGH-T989 using xda premium
I really hate to start a new thread but I really can't find a reason/solution to this issue. It's just as the title says. I tried flashing the MIUI ROM just as any ROM and got a failed error. Then went to do my nandroid restore and it just hangs on the splash screen (boot screen). Anyway I thought there could be a bad download so I took out the SD and redownloaded synergy on my laptop, then put it back in the phone and nothing but the nandroid should let me restore. I even tried moving the files to the internal SD and nothing. The only thing I can think of is to Odin back to stock? Is it the same method as rooting? I'm sure I can find that out, but I'm just confused why it seems TWRP doesn't want to work. Thanks for any help, it's 4 a.m. here and I'm dog tired.
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
DarkManX4lf said:
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
Click to expand...
Click to collapse
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
jtadak said:
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
Click to expand...
Click to collapse
Can I just reflash recovery from the state I'm in, or do I still need to unroot? I've moved some of my files to the ext SD within recovery but some things won't move and I really don't want to wipe it.
jd14771 said:
Try wiping everything 3X, then go to the reboot menu, and reboot system, wipe both the cache and dalvik cache and try to restore.
Click to expand...
Click to collapse
Do you mean reboot recovery? I can't reboot system. Sorry, not trying to split hairs, just trying to be specific.
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
mexiking713 said:
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
Click to expand...
Click to collapse
Yes, that's what I did. I'm just bummed I had to wipe storage. Oh well, it's inevedible... I dig that sig though, with phone line up.
lovekeiiy said:
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Click to expand...
Click to collapse
I tried multiple ROMs, but not a stock one. Hmm, I was on 2.3.2.3. I did'nt get a special error, just said a red message saying failed.
Evo_Shift said:
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
Click to expand...
Click to collapse
Tried that. Did'nt work.
jd14771 said:
no, i meant reboot system, the recovery will warm you that there is no os installed but go fourth with it, it will turn off and reboot back to recovery. at that point in time, wipe cashe/dalvik cache and try to install.
Click to expand...
Click to collapse
Ok, I was'nt sure. I just went back to stock. I just wanted to know what exactly was going on and why.
The only thing different on my phone is I got a 32 gig SD card. I transfed some of my files a couple days before doing anything of this. That's the only thing I can think of. Even after root/unroot it STILL won't do my nandroid restore. I had so much time and work into the apps I set up, games, ect. Really freakin sucks. I even went into the the TWRP backup folder and made sure the backup files were there before doing anything. I never even got to flash many ROMs, I kinda just stayed on Jellybomb.
I had the uTorrent app installed and I noticed that it changed a lot of files with the "u" in front that the uTorrent app has. Anyone know why that is?
Sent from my SPH-L900 using xda app-developers app
This is what it did to a lot of my files. But not the ones I tried to flash.
Sent from my SPH-L900 using xda app-developers app
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919
aLdaRiS said:
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919
Click to expand...
Click to collapse
Interesting.
I was about to try odin'ing back to stock and reflashing twrp.
The only thing I wonder if may be related is when you restore a backup with TWRP it gives options of all sorts of partitions besides system/data/cache etc... preload etc. It's possible it doesn't like mucking with those.
Interesting to note: If I install a CM nightly, it will allow me to reboot. Wickedv2 or my backup of wickedv2 no go.
Testing further.
Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.
saldebot said:
Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.
Click to expand...
Click to collapse
Righto. Sounds like a valid idea.
Unfortunately, the download links in konane's thread are timing out for me mid download. Tragic.
Managed to snag it from another location. Flashed back to stock firmware/recovery via odin.
Letting it boot to see what it does.
EDIT:
That did it.
Restored my backup and most everything is working correctly (restoring my titanium backup of all apps now.)
Few things were messed up (swiftkey was missing a language pack etc?)
But looks like AOSP/AOKP roms do something to the partition table as you said that requires flashing back the original.
Good to know and thanks for the help!
Don't wipe system in twrp.
makomek said:
Don't wipe system in twrp.
Click to expand...
Click to collapse
Does this cause issues? Didn't know.
I found that only CM nightlies would reboot fine. restoring via odin stock official then going back and putting on wicked again seemed to work to fix it and I can now reboot in a touchwhiz based rom.
re: stuck
bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
If you want a 95% sure way of fixing it so it boots completly,
then try this, it usually always works.
Get the phone into recovery mode twrp/cwm does not matter.
Then simply do a "factory reset" and I am fairly certain that it
will boot completly, I have seen this issue so many times
already not just here in the S4 thread but also in the S3.
The factory reset will not delete any of your music, videos and pictures.
Good luck!
Alright guys, getting a little frustrated here. I'm trying to go from Carbon to OptimusDE ZVC, When I flash OptimusDE, everything boots up fine but there isn't data to start with. I go into settings to update PRL and as soon as it starts to update, the phone reboots. Try to connect to WiFi, the phone reboots. Also, Exchange Services crash immediately after boot up.
What I've tried - Re-flashing, wiping caches and then also doing a factory reset, flashing ZVC radio.
Nothing seems to be getting this working. Anyone know what I need to do to get things working here? Any help would be much appreciated. Thanks!
latrotoxin1986 said:
Alright guys, getting a little frustrated here. I'm trying to go from Carbon to OptimusDE ZVC, When I flash OptimusDE, everything boots up fine but there isn't data to start with. I go into settings to update PRL and as soon as it starts to update, the phone reboots. Try to connect to WiFi, the phone reboots. Also, Exchange Services crash immediately after boot up.
What I've tried - Re-flashing, wiping caches and then also doing a factory reset, flashing ZVC radio.
Nothing seems to be getting this working. Anyone know what I need to do to get things working here? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Try flashing the new Stocktimus ROM and see if the same thing happens. If it does, you may just have to re-root.
Sent from my Optimus G using Tapatalk
iamterence said:
Try flashing the new Stocktimus ROM and see if the same thing happens. If it does, you may just have to re-root.
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
I'm not sure how root would pertain to this issue. I'll give Stocktimus a try, but I tried engine's other stock ROM's a month or so back and had the exact same issue.
Weird. Did you try actually activating?
Sent from my Optimus G using Tapatalk
AFschizoid said:
Weird. Did you try actually activating?
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
The phone is activated, but trying to run the activation in settings causes reboot. Receives phone calls no problem. Just downloaded Stocktimus O and same thing. No data, crash on PRL update or Profile update, crash on WiFi activation. I really don't understand what's going on...
Yeah I've not had that issue and I've flashed back and forth from stock based to aosp and vice versa. Might be your efs got screwed up. Try lgnpst or LG flash tool (I prefer the latter because it takes it to an 'out of the box' state, activation required ) and try activating again
Sent from my Optimus G using Tapatalk
That has happened to me before going from an AOSP rom to one of the available stock roms. Don't remember which one.
But I remember flashing the TWRP recovery. I was on Philz Touch Clockworkmod.
And then performed all the required wipes and reset then flashed Stockimus-D and viola, no FC's. no reboots. No more problems.
If problems persist used TeenyBins via LGNPST
A couple other things to try also:
Make sure you're wiping /system also.
Sometimes CM/AOSP Roms can mess up your SD. You may need to wipe it also. Just make sure you back it up first. That's happened to me a few times.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
A couple other things to try also:
Make sure you're wiping /system also.
Sometimes CM/AOSP Roms can mess up your SD. You may need to wipe it also. Just make sure you back it up first. That's happened to me a few times.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol, so funny story. I did LGNPST and got back to full stock. I had to use an oldddd ZVC .bin file, not a teenybin. Re-rooted, unlocked, put CWM 6.0.4.6 back on the phone and created a stock backup. I didn't mention before but I had long deleted my stock backups, so I didn't have a stock ROM on my phone at all to flash back to. Anyways, back on full stock, everything is working great, go into CWM, create a backup and flash Stocktimus O. It says it installed successfully, so I reboot...just the normal Sprint boot screen, everything is total stock. I'm wondering if perhaps, like a previous poster brought up, it's a CWM issue. I'll switch over to TWRP and give it a shot, report back later. I prefer CWM because I don't have any issues flashing AOSP ROM's whereas TWRP, on all versions I've tried, will fail with some ROM's while others work fine.
latrotoxin1986 said:
Lol, so funny story. I did LGNPST and got back to full stock. I had to use an oldddd ZVC .bin file, not a teenybin. Re-rooted, unlocked, put CWM 6.0.4.6 back on the phone and created a stock backup. I didn't mention before but I had long deleted my stock backups, so I didn't have a stock ROM on my phone at all to flash back to. Anyways, back on full stock, everything is working great, go into CWM, create a backup and flash Stocktimus O. It says it installed successfully, so I reboot...just the normal Sprint boot screen, everything is total stock. I'm wondering if perhaps, like a previous poster brought up, it's a CWM issue. I'll switch over to TWRP and give it a shot, report back later. I prefer CWM because I don't have any issues flashing AOSP ROM's whereas TWRP, on all versions I've tried, will fail with some ROM's while others work fine.
Click to expand...
Click to collapse
So LGNPST got everything working. But when you installed Stocktimus O you got stuck on the Sprint boot screen?
Did you give it about 4min to make sure it booted up?
It should work with both TWRP and CWM. I installed with both when I built them.
I know you've flashed before, but just in case, wipe /system, /data, /dalvic, and /cache.
If you don't want to do this next part, I'll see if it's something on my end:
If it doesn't install with TWRP, could you wipe your SD and try it again? I know it'd be a pain, but at least it would let me know if I need to fix the updater scripts.
Make sure your phone boots up. Then in recovery wipe "internal data" or SD and reboot. Your phone should still boot as long as you don't wipe /system.
If for some reason it won't boot, you may need to ADB sideload a rom, or LGNPST again.
Just trying to cover everything.
engine95 said:
So LGNPST got everything working. But when you installed Stocktimus O you got stuck on the Sprint boot screen?
Did you give it about 4min to make sure it booted up?
It should work with both TWRP and CWM. I installed with both when I built them.
I know you've flashed before, but just in case, wipe /system, /data, /dalvic, and /cache.
If you don't want to do this next part, I'll see if it's something on my end:
If it doesn't install with TWRP, could you wipe your SD and try it again? I know it'd be a pain, but at least it would let me know if I need to fix the updater scripts.
Make sure your phone boots up. Then in recovery wipe "internal data" or SD and reboot. Your phone should still boot as long as you don't wipe /system.
If for some reason it won't boot, you may need to ADB sideload a rom, or LGNPST again.
Just trying to cover everything.
Click to expand...
Click to collapse
It didn't get stuck, it just booted as though I hadn't flashed Stocktimus O even though it said it had successfully installed. Kinda weird...but it's definitely not on your end. I've done something, at some point, that has borked my ability to flash stock. I've thought about totally wiping SD....just LGNPST after that. I dunno.
TWRP didn't give me any different results. Same deal, just booted with the original Sprint screen, not your boot animation, nothing had changed...
latrotoxin1986 said:
It didn't get stuck, it just booted as though I hadn't flashed Stocktimus O even though it said it had successfully installed. Kinda weird...but it's definitely not on your end. I've done something, at some point, that has borked my ability to flash stock. I've thought about totally wiping SD....just LGNPST after that. I dunno.
TWRP didn't give me any different results. Same deal, just booted with the original Sprint screen, not your boot animation, nothing had changed...
Click to expand...
Click to collapse
It's gotta be on the SD. I don't know how, or where, no file explorer shows anything weird, but CM/AOSP ROM'S have got to be putting something on it for it not to flash. I've had issues more than once when I've had to wipe my SD to fix it.
We gotta got you going so you can get us some more Carbon, LS970 style.
engine95 said:
It's gotta be on the SD. I don't know how, or where, no file explorer shows anything weird, but CM/AOSP ROM'S have got to be putting something on it for it not to flash. I've had issues more than once when I've had to wipe my SD to fix it.
We gotta got you going so you can get us some more Carbon, LS970 style.
Click to expand...
Click to collapse
I'm TRYING to build it right now. Getting some really unusual errors. The last time I got one of them, I just restarted the build and it finished fine. This time though I'm getting Java Runtime Environment crashes though and something else...not sure what's up with that. Keep chipping away at it though
latrotoxin1986 said:
I'm TRYING to build it right now. Getting some really unusual errors. The last time I got one of them, I just restarted the build and it finished fine. This time though I'm getting Java Runtime Environment crashes though and something else...not sure what's up with that. Keep chipping away at it though
Click to expand...
Click to collapse
I had the reboot issue when it connected to data too when flashing back and forth from cm/aosp ROMs to stock. What resolves the issue for me is to use TWRP and go to advanced wrote and wipe everything EXCEPT internal. I used to have that issue all the time when using cwm recovery but philz recovery also seems to be ok when flashing back and forth hope this helps!
Sent from my LG-LS970 using XDA Premium 4 mobile app