Database Users

[Q] Razr M Root and RSD fail constantly.

Hey all, im new to the forum. I have been a spectator for a while and decided to see if you could help me. I have a Razr M (Verizon) and i used to have it rooted and running eclipse. I wanted to switch roms to PACman but it wouldn't stop failing. So after much anger i decided to reflash firmwear to stock 4.1.2 and it worked. I tried to root again using motochopper but it fails every time. I have tried to reflash with RSDlite but it also fails every time on step 1/19. Nothing i try is working and im loosing faith haha. Ive looked threw a lot of the other boards but all solutions never work for me. The goal is to have a Razr M running PACman but for right now its still on the ugly stock rom Any help or insight at all is greatly appreciated.

Willybrown said:
Hey all, im new to the forum. I have been a spectator for a while and decided to see if you could help me. I have a Razr M (Verizon) and i used to have it rooted and running eclipse. I wanted to switch roms to PACman but it wouldn't stop failing. So after much anger i decided to reflash firmwear to stock 4.1.2 and it worked. I tried to root again using motochopper but it fails every time. I have tried to reflash with RSDlite but it also fails every time on step 1/19. Nothing i try is working and im loosing faith haha. Ive looked threw a lot of the other boards but all solutions never work for me. The goal is to have a Razr M running PACman but for right now its still on the ugly stock rom Any help or insight at all is greatly appreciated.
Click to expand...
Click to collapse
what recovery are you running? if TWRP (any version other than 2.4), then you should be able to place the ROM on the external SD card and flash it (after wiping system/factory reset) - and then install the GApps.

jco23 said:
what recovery are you running? if TWRP (any version other than 2.4), then you should be able to place the ROM on the external SD card and flash it (after wiping system/factory reset) - and then install the GApps.
Click to expand...
Click to collapse
I was running safestrap but now im not running anything, the device has been Firmwear flashed and factory reset. Safestrap would also fail, made it basically useless. It wouldn't even correctly activate the stock rom slot.

Willybrown said:
I was running safestrap but now im not running anything, the device has been Firmwear flashed and factory reset. Safestrap would also fail, made it basically useless. It wouldn't even correctly activate the stock rom slot.
Click to expand...
Click to collapse
UPDATE: i got to step 6/19 in RSD, Here is a screenshop of it, i hope it helps.

Willybrown said:
UPDATE: i got to step 6/19 in RSD, Here is a screenshop of it, i hope it helps.
Click to expand...
Click to collapse
Post about phone info. Unlock status. Hold all 3 keys til black then let off pwr pause 2 sec. Let go vols. V down to fast boot v up.

Willybrown said:
I was running safestrap but now im not running anything, the device has been Firmwear flashed and factory reset. Safestrap would also fail, made it basically useless. It wouldn't even correctly activate the stock rom slot.
Click to expand...
Click to collapse
PAC and all other 4.2.2 ROMs can only be installed via TWRP/CWN, not SS.

aviwdoowks said:
Post about phone info. Unlock status. Hold all 3 keys til black then let off pwr pause 2 sec. Let go vols. V down to fast boot v up.
Click to expand...
Click to collapse
Not combination of key presses has any result, the only thing i get is fastboot, and its a razr m with an unlocked bootloader...

Willybrown said:
Not combination of key presses has any result, the only thing i get is fastboot, and its a razr m with an unlocked bootloader...
Click to expand...
Click to collapse
I DO not know. Bad XML Redownload?

aviwdoowks said:
I DO not know. Bad XML Redownload?
Click to expand...
Click to collapse
No go, ive tried redownloading everything and no luck. Im also getting errors of fastboot is not a recognized command from RSD. Ive tried matts tool with same result. The phone rejects everything i try to do to it.

Willybrown said:
No go, ive tried redownloading everything and no luck. Im also getting errors of fastboot is not a recognized command from RSD. Ive tried matts tool with same result. The phone rejects everything i try to do to it.
Click to expand...
Click to collapse
How much battery do you have? Also, which version of RSD are you using? I can barely read the version in your screenshot, it looks like 6.1.5, but I can't tell.

just got the phone to boot using SDK. I am using RSD 6.1.5 im going to try rooting and installing PACman. What recovery should i use?

SDK worked! the phone is now operating on the stock rom. problem is motochopper (by itself or in Matt's utility) fails every time. here is a screenshot. anyone have any ideas because i am lost.

N4 upgrade failed

Help me XDA, you're my only hope...
First, background: I bought my Nexus 4 over the internet, because it was never officially released in Belgium. I had to have the screen replaced, and let a 3rth party do it. Glass damage isn't covered by the warranty and it would mean sending my phone by international mail if i used the official warranty people. They told me that the also had to replace the proximity sensor.
My phone worked perfectly afterwards. Until I tried to install the automatic upgrade to 4.3.
First it stopped at the X-logo screen and became very hot. I contacted play support and did all the things they advised (including a factory reset, rebooting in safe mode), none of it works. I found someone with the same problem who managed to get past the X-screen by flashing back the 4.2.2 radio version. And that worked: the phone booted and the update started.
However, since that moment I got a lot of problems:
- random shutdowns
- random locking of the SIM card
- phone not starting unless plugged in charger.
Worst of all, reflashing stock images for 4.2 and 4.2.2 or AOKP does nothing to solve these problems. I also tried a new SIM card, and still nothing.
I'm at my wit's end now. Could there be a driver issue? Any other things I can try?
TIA

Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Click to expand...
Click to collapse
any suggestions for a good kernel that can run stock android?

If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.

BobWalker said:
If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.
Click to expand...
Click to collapse
Well, I tried again. (For the 6th time this month) No different as before: it's been stuck on the X screen for 20 minutes now and getting warmer.
EDIT: I finally managed to get into the recovery menu. No idea why it wouldn't let me use volume up + power...

As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?

Joenr76 said:
As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?
Click to expand...
Click to collapse
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Click to expand...
Click to collapse
I never did that before: do I flash the kernel first or the Rom first? Are there any guides?
EDIT: I just read that Paranoid Android comes with the halfbreed kernel included. Is that the one you linked too?

Before jumping into the kernel thing (also because i wanted to be able to work with a device that can actually boot), I reinstalled the 4.2.2 factory image. It took about 5 minutes for the first shutdown to happen. *sigh*
And without plugging it in, it goes into a boot loop (going to x screen for a while, then restarting.) When I plug it in, it starts immediately, but shows the battery as empty. It was 63% when it shut itself down.
It's a clean install, I just don't understand...

Okay so, I'm assuming you have a custom recovery like TWRP. Open it and flash the newest boot loader and radio. Then flash Paranoid Android and GApps. Then try flashing Faux kernel and clearing cache/dalvik. If you still have problems, then I have no idea
Sent from my Nexus 4 using xda premium

Open up your phone to see the battery is securely checked and to see if all the components are okay. Then look do a full wipe of cache,dalvik,system,data,and sd (internal storage). Then use wugs toolkit to a upgrade on a clean flash. Double check to make sure you wipe everything!
Sent from my Nexus 4 using Tapatalk 4

TheNerd:] said:
Open up your phone to see the battery is securely checked and to see if all the components are okay.
Click to expand...
Click to collapse
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...

Joenr76 said:
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...
Click to expand...
Click to collapse
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.

tykate said:
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.
Click to expand...
Click to collapse
Tried that before. I did some research and I guess this is relevant: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/ Especially since I ordered my Nexus from the Netherlands.
I'll have to wait until that bug gets fixed until I can upgrade my radio.

[Q] How can I remove custom recovery? Ran into some problems and want to "start over"

[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.

[Q] soft bricked ls980

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 :/

[Q] Help a noob, cannot boot after trying to flash stock rom

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.