so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.
omega52390 said:
so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.
Click to expand...
Click to collapse
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?
XxZombiePikachu said:
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?
Click to expand...
Click to collapse
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
edit hang on ive got a 10.2 nightly and jb gapps i might have something here will report shortly... nvm i think... it locks up saying "using legacy property environment for update-binary...please upgrade to latest binary"
omega52390 said:
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
Click to expand...
Click to collapse
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup
XxZombiePikachu said:
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup
Click to expand...
Click to collapse
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.
omega52390 said:
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.
Click to expand...
Click to collapse
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm
XxZombiePikachu said:
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm
Click to expand...
Click to collapse
thats the thing i've only ever had trouble with adb coudl never wrap my head around it let alone get it to work
w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD
omega52390 said:
w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD
Click to expand...
Click to collapse
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
for some reason cm is still failing to load im going to try installing cm then putting on furnace kernel
edit i remember and succeeded in recreating my secret recipe. first i have an old twrp and 10.2 unofficial nightly thats where i am now. next ill put on a new CWM philz and try putting my CM backup on
another update i finally got my cm 11 backup running however it appears there is damage to the install from back when i made the backup do you know of anyway of repairing an install w/o having to do a reset? really the only noticable problem right now is that i can't use any live wallpapers :/
Related
I Think i have bricked my nexus s ......it wont startup and goes to do first setup but force closes....i can access recovery but when i flash a rom it aborts ....only just bought it
U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App
afishpie said:
U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Please can you elaborate...or point me in right direction......recovery is now only accessible by flashing it first....phone just wont do anything
download a 2.3.3 nandroid backup and restore to it using clockwork recovery
ignore odin.
http://forum.xda-developers.com/showthread.php?t=884093
update to 2.3.3 using http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
or just download CM7 and flash that along with gapps (wipe dalvik/cache/factory)
and your phone is not bricked. the definition of a bricked phone is a phone who cannot access recovery/fastboot/etc.. can access absolutely nothing
Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?
distortedloop said:
Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?
Click to expand...
Click to collapse
Many thanks to both of you.....for your help .....so much appreciated......i have got past first setup screen after applying a nandroid backup......it finally worked after 5 times trying....but i have stock android recovery but rom manager on phone .....how can i get clockwork mod back as everytime i flash it.....i get to use it for that one instance ans then it returns to stock android recovery
I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?
menov321 said:
I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?
Click to expand...
Click to collapse
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
sano614 said:
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....
menov321 said:
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....
Click to expand...
Click to collapse
No it doesn't. You're fine. The latest is android 2.3.3 with GRI40.
Sent from my Nexus S using Tapatalk
Here's the rundown:
I installed the Dark Paranoid Android (Grouper) ROM this morning. I flashed Gapps, and rebooted the device. No issues at that point, because I came from another ROM I did a clean install and got through the registration screens no problem. Once at the home screen, I remembered I had not flashed the Trinity (Grouper) kernel like I had planned, so I rebooted to recovery and flashed it.
That's when I ran into problems. Rebooted device and it stuck at the Google screen. Tried to bootloader into recovery, I still get stuck at the Google screen. Have tried to boot up both the recovery and into Android several times from bootloader, but I always get stuck at the Google screen. I guess my device didn't like the kernel, or somehow installing it damaged my recovery maybe?
Basically, I am asking if I am soft-bricked and have to restore factory and therefore wipe the device clean. Doing that would suck, but it's better than not having the device.
Also, I'd like to know if it's possible to flash stock through the Wugfresh toolkit without removing root. I just want to get back to stock so I can reinstall the ROM and try a different kernel.
liquid150 said:
Also, I'd like to know if it's possible to flash stock through the Wugfresh toolkit without removing root. I just want to get back to stock so I can reinstall the ROM and try a different kernel.
Click to expand...
Click to collapse
Try to wipe everything and reinstall
kinhbang1989 said:
Try to wipe everything and reinstall
Click to expand...
Click to collapse
Impossible with my device in the state I described.
Since the answers were fairly slow I already flashed factory image from Google with the toolkit. Issue was resolved, just will take a while to get everything put back on it.
Sent from my Paranoid Galaxy Nexus
Did you check the md5 on the kernel download? If there wasn't an md5 supplied, download the file a few times and compare the md5's between them for consistency. Could've been as simple as a bad download.
mustbepbs said:
Did you check the md5 on the kernel download? If there wasn't an md5 supplied, download the file a few times and compare the md5's between them for consistency. Could've been as simple as a bad download.
Click to expand...
Click to collapse
I did not check it. Maybe I will try it again later. Was able to right the problem by using the Nexus Toolkit to flash 4.1.2. Then I put DarkPA on it and started over. Not really the end of the world, just slightly time consuming.
I love the Trinity kernel on my phone. I want to use one for Nexus but I didn't see a stable one yet, all are in experimental phase.
Sent from my Paranoid Galaxy Nexus
Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Tylorw1 said:
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I don't see how that could be the case. I didn't flash anything. I just loaded TWRP, created a backup, and rebooted my phone. No ROM\kernel change. Nothing more than creating a backup in TWRP.
scott14719 said:
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Click to expand...
Click to collapse
I tried searching, the closest one I could find on the first few pages was this one. I just didn't see any specific to my situation because nothing was flashed. Like my response to Tylorw1, all I did was boot into recovery, create a backup, and reboot my phone. Didn't flash a ROM, change a kernel, format anything, etc...
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
STVERDI said:
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
TheAxman said:
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
Click to expand...
Click to collapse
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Simonzi said:
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
Click to expand...
Click to collapse
And you have to be ****ing kidding me. I rebooted into recovery while typing my initial response, just to verify I was still on the 2.5.x.x TWRP. Booted up TWRP, verified that, choose "Reboot System", and same thing. Back to sitting at the Samsung screen. Nandroid backups or not, ditching TWRP as soon as I get it able to boot back up.
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
somebody had mentioned this...
http://forum.xda-developers.com/showpost.php?p=44629460&postcount=8
make sure you have the correct firmware and proceed as you are. likely your best bet.
Simonzi said:
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
Click to expand...
Click to collapse
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
scott14719 said:
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
Click to expand...
Click to collapse
Yeah, I meant 1.6gb firmware package. Just forgot the "gb". That's what I'm currently downloading, but trying to recover it with Kies while waiting.
I would like to report I had the same problem.
After changing roms and making a nandroid, and then deciding to switch roms again, I ran into the stuck at Samsung Custom with a lock boot screen. Most roms would boot up once, but a restart or power down would lead to being stuck. I was flashing through TWRP.
I went into TWRP and flashed OUDHS recovery which overrode TWRP and wiped/flashed through OUDHS a new rom.
Problem solved.
S3 at&t stuck in TWRP booting screen.
xBeerdroiDx said:
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Click to expand...
Click to collapse
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Lnjames said:
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Click to expand...
Click to collapse
Wrong forum. Please go to the s3 section with your question.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Had this problem just now, solved it by fixing permissions.
I am running an MDL based S4, and screwed the pooch. I was going to wipe the internal storage and made the mistake of doing it through TWRP 2.5. Now, I have the same problem of being stuck on the custom boot screen. I have tried to change from TWRP to OUDHS Recovery, but still boot loops to Custom screen. I have tried fresh installs of 4.2 ROMs and 4.4.2 Google Editions. Do I need to flash via ODIN?
Flame away....I know better than this!!!!
Help would be greatly appreciated.
Sent from my GT-N8013 using Tapatalk 4
[Q] How can I remove custom recovery? Ran into some problems and want to "start over"
So I recently rooted my VZW G2 thanks to wyrdtrtle on IRC (HUGE thanks, btw). I had lots of issues and he helped me out for about 3ish hours. It ended off with me asking him which recovery I should use (CWM vs TWRP) and he said he uses TWRP for it's touch interface, so I went ahead and installed it via FreeGee. Fast forward to yesterday night, I decide to flash CM 10.2 (I'd prefer starting out on a guaranteed stable build instead of a nightly since I've been on Android since January and know very little). I find and watch a tutorial (can't link since i am a new user) and proceed to download the CM10.2 zip and the gapps. After a few seconds, it fails. I try looking for more tutorials, specifically for G2 and CM and it still fails. I then tried installing CWM (maybe TWRP was the problem?) via FreeGee and again, flashing failed. I thought it might be CM and I was going to try ParanoidAndroid or Mahdi (think that's the name) and see if that works but I now want to remove both recoveries and "restart" as if I had just rooted my phone. Decided to post here before I potentially brick my phone. Sorry for wall of text, but any help is appreciated.
_tyler_ said:
So I recently rooted my VZW G2 thanks to wyrdtrtle on IRC (HUGE thanks, btw). I had lots of issues and he helped me out for about 3ish hours. It ended off with me asking him which recovery I should use (CWM vs TWRP) and he said he uses TWRP for it's touch interface, so I went ahead and installed it via FreeGee. Fast forward to yesterday night, I decide to flash CM 10.2 (I'd prefer starting out on a guaranteed stable build instead of a nightly since I've been on Android since January and know very little). I find and watch a tutorial (can't link since i am a new user) and proceed to download the CM10.2 zip and the gapps. After a few seconds, it fails. I try looking for more tutorials, specifically for G2 and CM and it still fails. I then tried installing CWM (maybe TWRP was the problem?) via FreeGee and again, flashing failed. I thought it might be CM and I was going to try ParanoidAndroid or Mahdi (think that's the name) and see if that works but I now want to remove both recoveries and "restart" as if I had just rooted my phone. Decided to post here before I potentially brick my phone. Sorry for wall of text, but any help is appreciated.
Click to expand...
Click to collapse
how'd you root your phone first? through what?
MuzakaTheBeast said:
how'd you root your phone first? through what?
Click to expand...
Click to collapse
I followed the IORoot22 instructions along with clarification from wyrdtrtle on IRC
Try patching cm10.2 with freegee in the menu with three lines and you should see something called update Loki in zip tap that and go to where you placed cm and tap cm and it will take a couple minutes to patch if it fails try to redownload cm but do not skip previous steps it will softbrick your phone.
I DO NOT take responsibility for bricks soft/hard bricks when you root,flash ROMs you risk bricking your device
Happy modding welcome to the world of android
Sent from my LG-VS980 using Tapatalk
spinninbsod said:
Try patching cm10.2 with freegee in the menu with three lines and you should see something called update Loki in zip tap that and go to where you placed cm and tap cm and it will take a couple minutes to patch if it fails try to redownload cm but do not skip previous steps it will softbrick your phone.
I DO NOT take responsibility for bricks soft/hard bricks when you root,flash ROMs you risk bricking your device
Happy modding welcome to the world of android
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Oh, right, I remember reading that Loki bypasses locked Bootloaders (which somehow led me to think only CWM had Loki support and would work when TWRP didn't). I'm gonna try this now.
spinninbsod said:
Try patching cm10.2 with freegee in the menu with three lines and you should see something called update Loki in zip tap that and go to where you placed cm and tap cm and it will take a couple minutes to patch if it fails try to redownload cm but do not skip previous steps it will softbrick your phone.
I DO NOT take responsibility for bricks soft/hard bricks when you root,flash ROMs you risk bricking your device
Happy modding welcome to the world of android
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Didn't work. Still get an error saying it failed
_tyler_ said:
Didn't work. Still get an error saying it failed
Click to expand...
Click to collapse
did you try redownloading cm 10.2 downloads get corrupted sometimes it is very annoying
spinninbsod said:
did you try redownloading cm 10.2 downloads get corrupted sometimes it is very annoying
Click to expand...
Click to collapse
apparently the 10.2 rom i was trying to flash wasn't compatible with my phone (not too sure on the specifics) but I tried the latest nightly for cm11 and I've been running it since last night.
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware): https://mega.co.nz/#F!0JdRkIZR!AqqKdbvba_Hpg5VrCmrbPw
i7vSa7vi7y said:
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
Click to expand...
Click to collapse
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Does it matter that I can't get into recovery to clear the cache first before trying new roms?
silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Maybe I'm doing something foolish but every time I try to download files from the link you gave I get a decryption error so I can't download them zip or original.
rmngorelov said:
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
Click to expand...
Click to collapse
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
i7vSa7vi7y said:
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
Click to expand...
Click to collapse
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
Depends what recovery you had and what version. I personally like Philz touch recovery but TWRP is good. Now wipe and flash a ROM my friend or restore a backup
rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
im having similar issues. which version of TWRP worked for you?
thank you
fearthemarchx said:
im having similar issues. which version of TWRP worked for you?
thank you
Click to expand...
Click to collapse
I recommend flashing the newest one here using odin
http://teamw.in/project/twrp2
Then once you are able to boot into recovery go to wipe and perform both factory reset and format data. Then install whatever rom you like, I used Sprint Galaxy S4 SPH-L720 VPUFNAE (Androdi 4.4.2) found here
http://galaxys4root.com/galaxy-s4-stock-firmware/ (or maybe find a newer stock rom if this one gives you errors)
Just copy the zip file to the phone, boot into twrp, do wipe factory reset again, select install then select the zip in whatever directory and you should be good to go. Make sure you do a back up in twrp once you get the phone to boot so you can always revert to stock.
I hope I was thorough enough that some of the information was useful. Let me know if you need any more help.
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
fearthemarchx said:
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Format with philztouch that works then try flashing a new stock rom with odin. That should bring everything back to stock including the recovery.
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
fearthemarchx said:
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
You're in download mode when you flash from odin right? If you your getting an error flashing, try a different stock rom after reformating/resetting to factory (it's crucial to clear the cache before trying a different rom). I had to try a few roms before I found one that worked.