Related
Hey guys, long time lurker, first time poster.
I finally gave in and fully rooted my EVO and successfully flashed the newest damagecontrol rom. Afterwards, I took some time and set up my phone like how it used to be with the apps, settings, etc. Just a few questions from after this.
If I wanted to flash a different ROM, it is recommended to do a data wipe, correct? And also a NAND backup. Does this mean that my phone will be reset to factory settings again - using the new ROM as a base? In other words, would I have to rearrange my screens, settings, etc. if I wanted to try out a new ROM?
If not a different ROM, but an updated version of my current ROM, do I just flash that on top of what I have? (i.e. DC4.0 is released, do I have to wipe everything again before upgrading?)
If the answer is yes to both these questions, what are the easiest/quickest ways to get my phone looking/acting the way I like when getting a new ROM?
also, I followed toast's method step by step, and got the Amon Ra recovery on my phone as well. What is the function of this? Sorry for all the questions, I have everything working fine, but I'm just curious as to what and how things work on the phone. What is the difference between the amon ra recovery and following steps to use clockword for recovery?
Thanks a lot
baxtercat said:
Hey guys, long time lurker, first time poster.
I finally gave in and fully rooted my EVO and successfully flashed the newest damagecontrol rom. Afterwards, I took some time and set up my phone like how it used to be with the apps, settings, etc. Just a few questions from after this.
1. If I wanted to flash a different ROM, it is recommended to do a data wipe, correct? And also a NAND backup. Does this mean that my phone will be reset to factory settings again - using the new ROM as a base? In other words, would I have to rearrange my screens, settings, etc. if I wanted to try out a new ROM?
2. If not a different ROM, but an updated version of my current ROM, do I just flash that on top of what I have? (i.e. DC4.0 is released, do I have to wipe everything again before upgrading?)
If the answer is yes to both these questions, what are the easiest/quickest ways to get my phone looking/acting the way I like when getting a new ROM?
Click to expand...
Click to collapse
baxtercat said:
also, I followed toast's method step by step, and got the Amon Ra recovery on my phone as well. What is the function of this? Sorry for all the questions, I have everything working fine, but I'm just curious as to what and how things work on the phone. What is the difference between the amon ra recovery and following steps to use clockword for recovery?
Thanks a lot
Click to expand...
Click to collapse
Hello there, iv done videos on this rom for youtube, if you want the links let me know but ill go as it follows.
Ok, if you want to test out new roms, just do a nand backup of the one you have now, after that. WIPE both Factory and Delvic cache. Then flash the new rom in your phone adn you will be fine.
Ok, i know DC does this, i dont know about the others yet, But if a new update comes out, just flash that DC update over yours and it will be fine. All user data will be there. YOU shouldn't have boot loop ether. If so, then you will have to wipe again. I didn't and im fine. ( I use fresh evo right now. loving it. )
As for the NAND backup. This saves EVERYTHING so once you are tired of a old rom and wanna try another, just restory the back up and your fine.
super-6-1 said:
Hello there, iv done videos on this rom for youtube, if you want the links let me know but ill go as it follows.
Ok, if you want to test out new roms, just do a nand backup of the one you have now, after that. WIPE both Factory and Delvic cache. Then flash the new rom in your phone adn you will be fine.
Ok, i know DC does this, i dont know about the others yet, But if a new update comes out, just flash that DC update over yours and it will be fine. All user data will be there. YOU shouldn't have boot loop ether. If so, then you will have to wipe again. I didn't and im fine. ( I use fresh evo right now. loving it. )
As for the NAND backup. This saves EVERYTHING so once you are tired of a old rom and wanna try another, just restory the back up and your fine.
Click to expand...
Click to collapse
Wow, thanks for the quick reply! That cleared up a lot of things for me.
So if I have everything set up the way I want, it is recommended to do a NAND backup at this point?
Also, what are the pros/cons of using Rom Manager (marketplace)?
Thanks a lot
baxtercat said:
Wow, thanks for the quick reply! That cleared up a lot of things for me.
So if I have everything set up the way I want, it is recommended to do a NAND backup at this point?
Also, what are the pros/cons of using Rom Manager (marketplace)?
Thanks a lot
Click to expand...
Click to collapse
well if i was you, wait till you wanna flash something else THEN do a nand back up.
as far as rom manager goes, i dont use it. I just come on here and see whats new and what going on, you get a lot more from here then on rom manager, Plus, its free
super-6-1 said:
well if i was you, wait till you wanna flash something else THEN do a nand back up.
as far as rom manager goes, i dont use it. I just come on here and see whats new and what going on, you get a lot more from here then on rom manager, Plus, its free
Click to expand...
Click to collapse
This is what I was thinking as well. Thanks
could you be kind enough to explain the different recovery files and their uses?
baxtercat said:
This is what I was thinking as well. Thanks
could you be kind enough to explain the different recovery files and their uses?
Click to expand...
Click to collapse
what do you mean? like the different kinds of recoverys? Really i just stay with toasts, his is more stable and as far as the clockmod one, It has issues with formatting the Factory cashe.
Honestly, for someone that is completely new to flashing roms, backing up etc., Rom Mgr. is the best thing for you. You may not have the absolute cutting edge of available roms, but it makes flashing/backing up extremely easy and straightforward. That is how I got started with my previous Droid until I felt comfortable enough to flash the old fashion way. I have literally flashed and backed up hundreds of times using clockwork mod (rom manager recovery) and have not had a single issue. Plus, the app is only a couple bucks if I remembe correctly. I would start there to gain some experience, then move on to flashing zips from here.
just my opinion.
Will rom manager work if I have Amon RA's Recovery?
I think it may replace your recovery
Ok so, I was flashing CM7-GX4...everything was going fine until I flashed GAPPS, now I'm stuck at two screens alternating between the CM7 boot animation and the screen that says "Welcome to PC36100", upon this screen loading it quickly restarts the CM7 boot animation, so on and so forth. I am able to get into CWM recovery. Please help.
Thank you in advance.
thats a boot loop, looks like you want to wipe everything and try again
elegantai said:
thats a boot loop, looks like you want to wipe everything and try again
Click to expand...
Click to collapse
What if the PC36IMG file is renamed? I changed the name previously per the instructions of some thread I saw somewhere. Could this be the problem?
well you lost me at the hboot image. The only time i have ever had to use a file like that is when i was rooting my phone.
I also do not use cwm, so i am kinda limited in the help i can provide. Did you wipe your system/data/cache before you flashed cm7?
I wiped everything. I've put the SD card in another phone and renamed it back to PC36IMG...lets see what happens LOL
Renamed file back to PC36IMG...still stuck in boot loop
What exactly are you using the pc36img for?
elegantai said:
What exactly are you using the pc36img for?
Click to expand...
Click to collapse
I'm not using it for anything. It's just there from back when I rooted the phone. I had renamed it a while ago. Everything was going fine, install CM7 GX4 ROM, rebooted, attempted to install GAPPS and thats when I got stuck going back and forth between the two screens. I have put the SD card in another phone and renamed it to the original PC36IMG (figuring since I was stuck at a screen saying Welcome to PC36100 it couldnt find the file or something), and I'm still having the same problems. I've wiped and wiped and wiped using CWM and reinstalled CM7-GX4 several times and am still getting the same bootloop.
I'm running a restore from CWM...hopefully that will take me back to a point where I can do something.
yeah, you dont need the pc36img after you root so that is not the problem. My only guess is that cwm is not wiping everything properly or you are missing a step in the install process. I guess you can try a few things:
See if your cwm recovery is up to date (i know earlier versions had issues clearing out properly, but that has since been fixed)
Start back from the beginning of the install process with that rom. Make sure to wipe data, system, and cache, and go back through step by step (sometimes it is easy to overlook a step). Also i noticed in the rom you are using it says to make sure to flash the wi-max kernel, so make sure you do that.
Lastly, I have never used that rom, but if you do not need 4g you can try flashing the actual cyanogenmod nightlies. They are very stable (its what i am running now), and you can grab the latest nightly from:http://mirror.teamdouche.net and grab the gapps from: http://goo-inside.me (universal package)
Sorry to lay a crap load of info on you, but i just don't know what would cause it. A bootloop (which is what you are experiencing with the going back and forth between screens) basically means something did not install right and is making your phone restart over and over.
elegantai said:
yeah, you dont need the pc36img after you root so that is not the problem. My only guess is that cwm is not wiping everything properly or you are missing a step in the install process. I guess you can try a few things:
See if your cwm recovery is up to date (i know earlier versions had issues clearing out properly, but that has since been fixed)
Start back from the beginning of the install process with that rom. Make sure to wipe data, system, and cache, and go back through step by step (sometimes it is easy to overlook a step). Also i noticed in the rom you are using it says to make sure to flash the wi-max kernel, so make sure you do that.
Lastly, I have never used that rom, but if you do not need 4g you can try flashing the actual cyanogenmod nightlies. They are very stable (its what i am running now), and you can grab the latest nightly from: mirror.teamdouche.net and grab the gapps from: goo-inside.me (universal package)
Sorry to lay a crap load of info on you, but i just don't know what would cause it. A bootloop (which is what you are experiencing with the going back and forth between screens) basically means something did not install right and is making your phone restart over and over.
Click to expand...
Click to collapse
I ran the recovery and got back to an old point. I guess I'll try again! Weird that it happened after flashing GAPPS as everything was fine up until that point. I'll grab the gapps from your source. Thanks!
nooomoto said:
I ran the recovery and got back to an old point. I guess I'll try again! Weird that it happened after flashing GAPPS as everything was fine up until that point. I'll grab the gapps from your source. Thanks!
Click to expand...
Click to collapse
Well, i would only use the gapps from the link i provided if you are going to flash the official cm7 nightlies. I wouldnt mix and match! i surely don't want to cause further problems for you! lol. I was reading over that rom and I am not sure why you would need to reboot between installing the rom and the gapps. But again, not familiar with that version!
Sorry i couldnt help more hope you get it!
elegantai said:
Well, i would only use the gapps from the link i provided if you are going to flash the official cm7 nightlies. I wouldnt mix and match! i surely don't want to cause further problems for you! lol. I was reading over that rom and I am not sure why you would need to reboot between installing the rom and the gapps. But again, not familiar with that version!
Sorry i couldnt help more hope you get it!
Click to expand...
Click to collapse
I used the gapps from your source and everything went fine. Thanks again for the help!
no problemo, glad you got it working!
Post Removed.
Add on
Post Removed.
maybe your phone not bricked
that say on cwm, your cwm cant mount everything right?
what cwm you use?
maybe your cwm doesnt support to mount ext4
because on my cm7 build, all partition will be ext4. except sdcard
have you try to format system, data, cache & sd-ext on your cwm?
now, all your partition must be at RFS again
and how you flash stock rom?
from odin? or?
Post Removed.
InMyBedNow said:
People with this phone, DO NOT FLASH CUSTOM ROMS THAT ARE MADE FOR JUST THE GTS5660 NOT THE M Model. I flashed CM7 ported by phiexz (amazing build btw) and when i wanted to flash back to stock, It bricked.
Click to expand...
Click to collapse
Sorry to hear about your issue but your assumption that you can't use other versions on an "M" is a little bit of a blanket statement. I've tried almost every release made and posted on xda and other than boot loops on occasion haven't had any lasting issues.
I do flash back to the lightly tweaked stock release by Darkshadow once in a while when starting fresh, which IS a "M" only release, but that's just so I have a clean starting point to upgrade from so I have the right WiFi and CSC already installed.
Heck, in my Odin ROM folder I have 7 different main release branches I liked and continue to follow from version to version. 3 of which I still switch between from week to week as new versions come up.
Like most things you just need to read, be careful, and try to know what your doing first. There will ALWAYS be risk, even with a stock ROM, that something will go wrong and brick your system but if you back things up and do your due diligence and wait until a trusted source posts a release with instructions you can mitigate the risk and get support.
As long as you can use Odin, CWM Recovery, or boot into phone you have a very good chance to fix or roll back. Just don't panic and/or fail to wait long enough for things to finish. Sometimes I've had to wait 5 minutes for a loop screen to reboot itself and complete...at other times pulling the battery was the only way to stop things. At other times a reboot into recovery to wipe all info was needed, including mounting all partitions first.
The only "M" versions I'm even aware of all come from Darkshadow....up to version 8 last time I checked.
So...yes...be careful...but to say you can't use GT-S5660 ROMs on a GT-S5660M isn't correct.
InMyBedNow said:
Yeah, from Odin. I'm pretty sure I was using the CWM from your Cm7 build, I installed it by flashing over my old cwm which was this one http://forum.xda-developers.com/showpost.php?p=16980117&postcount=559. I think i semi-bricked by pulling out the battery during bootloop, I shouldn't have. I'll probably sent it in to Samsung since I reflashed everything stock, even the recovery.
Click to expand...
Click to collapse
try to use your old cwm, and go to mount & storage
and you should format system. data & partition
and try to flash stock rom again
are u using adb?
can you paste here your log?
use: adb logcat
maybe i can help you
I thought the "rule" was don't flash the modem/radio - i.e. do a multi file Odin update and select nothing for modem/radio.
I took a stock s5660 2.3.5 rom from this forum and flashed my S5660m in this way, and it's fine.
Post Removed.
Post Removed.
Post Removed.
congratulation man
i'm happy to hear that ^^
Hey guys,
glad to say that ive been able to debrick my phone like 5 times in a row successfully which is a weight off my shoulders.
however, once im debricked, rooted, cwm installed, and all .img's pushed i try to flash a custom rom. i've tried every one and i get bootloops every time... they seem to install just fine. very normal timing and everything, no errors. any ideas?
Don't format /data. Are you doing that? Link the steps you're taking when you are in cwm to flash over the rom. Maybe something is amiss.
nope not formatting data. ive been doing wipe cache, wipe dalvik, and format /system.
Man I was in the same boat as you but was finally able to get it sorted this morning. What I highly, highly recommend is starting as fresh and as clean as you possibly can. That is before you do CWM or anything like that restore your phone with the Korean kdz, push all the images (system being last) then make sure you have a bootable, working phone. Also I would recommend using different/new/fresh .img files...I downloaded ones from the unbricking thread and only used a copy of my baseband.img. I had a feeling one of my files wasn't quite right so starting with all new ones may have helped.
Don't try anything from a backup or do a restore or anything-start fresh and make sure everything works as it should. From there do CWM and then do your ROMS. I know you're almost there and its a headache to keep starting from the bottom but do it all one step at a time, in order and you will find success.
Good luck!
good call. i havent been pushing all the .img's. just the three he mentioned above. let me try this for the 80th time. ill let you know how it goes. just curious, do you use the v10f or v10i kdz?
Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.
If i was you i would install the new CWM, once it installs the new CWM it'll work.
gte460z said:
Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.
Click to expand...
Click to collapse
yep i know that part. thanks
Revolution said:
If i was you i would install the new CWM, once it installs the new CWM it'll work.
Click to expand...
Click to collapse
new cwm?? as in the newest version available?does it work on the nitro?
[CWM][24/01] ClockworkMod 5 Recovery For LG Nitro HD
http://forum.xda-developers.com/forumdisplay.php?f=1448
Follow instruction's then try flashing a ROM it should fix your problem.
ive been using cwm... doesnt get rid of the bootloops
mic.mayorga said:
ive been using cwm... doesnt get rid of the bootloops
Click to expand...
Click to collapse
I'm not sure you understand bro, there is a NEW UPDATE
Update your CWM and it'll fix this issue.
I had the same problem for awhile. Had to use the Unbricker:http://forum.xda-developers.com/showthread.php?t=1412367
Followed ALL instructions, including "Restoring Nitro HD partition images" before flashing CWM. After that, no more bootloops and installed Revolutions rom w/out issue. Reboots just fine after.
I used the V10i-the direct download from LG...I think all the other recommendations are spot on but first and foremost get everything squared away with a fresh install of the kdz, all the images (in the proper order), the new version of CWM and then your rom of choice...Hope you're making some progress!
I'm on the new CWM and still have a loop if I reboot. Then I need to restore from CWM to get going again.
The soft brick boot loop I got was caused solely by format /system. I did not format /data.
I went through the whole deal last night and this morning and was able to get a fresh start on everything and am now running the HD ROM and haven't had a boot loop since I got everything back up and running...
I really think starting with the freshest install and making sure everything is functional step by step is where you'll be able to get through all that mess...just stay away from and restores or using any .img files that may have any software glitches as you'll get back to square one every time.
Hope you get it sorted out!
nah bro, i had the new update. no worries tho i pushed all the images in the debrick and fixed it. thanks for all the help guys B)
Tight work-glad you were able to get it straight! Now once you get it where you want make a new backup with Nandroid and CWM and you'll be golden in case anything else happens.
Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks
huydq5000 said:
Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks
Click to expand...
Click to collapse
Go look at the thread "[Solved] Unbricking solution...". Follow it to the T, however, i'd recommend using v10i.kdz rather than v10f.kdz. Definitely try the f version first but if it doesn't work try i. That's what I did. Basically what you're going to want to do is:
1. Restore the phone to a korean image using the v10i (or f) file and the LG software provided and referenced in the unblocking thread.
2. Once booted, root the phone. (specific instructions for v10i are in a thread somewhere linked by [email protected] v10f use either SuperOneClick root or DoomLord v4. Make sure you have adb installed for doomlord.
3. Once rooted use adb to push over stock .img files in this order: boot, recovery, firmware, baseband, system.
4. after the files are pushed boot into phone and root again (optional).
5. Install CWM5 through adb or terminal emulator.
Good luck, let me know if you have any questions and I can go into more detail.
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