Good morning.
So I'm running KitKat on my Nexus 4 and everything was fine until I decided to install TouchControl to avoid using the power button that much. I'm not an expertise over kernel's so I followed the prompted instructions and I ended up flashing the stock kernel I guess.
So after that my phoned rebooted, and since then I can not connect to Wifi, it only says connecting. I don't have CWM on my phone because I have a problem connecting my phone to my computer since it got wet some weeks ago so now it only charges but I can not transfer any files into my phone.
I restored my phone to factory settings and nothing.
I know this will be tricky but I also know you guys can help me, I know the main issue will be the fact that I can not transfer files over USB.
Please your help you will be of so much help.
Thanks in advance
grillaxo said:
Good morning.
So I'm running KitKat on my Nexus 4 and everything was fine until I decided to install TouchControl to avoid using the power button that much. I'm not an expertise over kernel's so I followed the prompted instructions and I ended up flashing the stock kernel I guess.
So after that my phoned rebooted, and since then I can not connect to Wifi, it only says connecting. I don't have CWM on my phone because I have a problem connecting my phone to my computer since it got wet some weeks ago so now it only charges but I can not transfer any files into my phone.
I restored my phone to factory settings and nothing.
I know this will be tricky but I also know you guys can help me, I know the main issue will be the fact that I can not transfer files over USB.
Please your help you will be of so much help.
Thanks in advance
Click to expand...
Click to collapse
Does ADB work?
If the phone is rooted, grab Flashify off the Play Store and install CWM or TWRP from there.
Have a custom/stock kernel zip to flash on your sdcard.
PR0XiMA said:
If the phone is rooted, grab Flashify off the Play Store and install CWM or TWRP from there.
Have a custom/stock kernel zip to flash on your sdcard.
Click to expand...
Click to collapse
He can't. His internet connection doesn't work.
abaaaabbbb63 said:
He can't. His internet connection doesn't work.
Click to expand...
Click to collapse
Did it say that 3G didn't work?
Problem fixed
So at the end I figure that the problem was caused by the Touch Control App, I did not put the required attention to the prompted instructions and the kernel was flashed.
So, using my phone's BT I transferred the files to install CWM and then I flashed it with the stock ROM.
That's the way I recovered the WiFi Capability.
Thanks for your advice guys.
Cheers.
Related
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
calavera-pw said:
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
Click to expand...
Click to collapse
before you do anything, use your recovery to see if the rom zip is located in /data/media/0/. if its there, flash it from that location.
Are you able to boot into recovery?
If yes, it could be as simple as plugging your tablet into the computer and mounting the usb, drag and drop the rom, and flash it without using a toolkit (only recovery). I'm not familiar with jrom flasher, but i will say the more variables there are, the more chance of a problem.
If no, you're best off running the stock factory image through your computer, found here: https://developers.google.com/android/nexus/images#nakasi. I had your problem at one point, and could not even boot into recovery. After trying to install cwm through adb (which failed), and a number of toolkits, the factory image was what brought my nexus back to life.
I remember reading that sometimes a wipe can delete your recovery as well as your system (and whatever else you have on your n7), although i dont know if that was ever fixed, as i got my tab replaced a month or two ago and havent rooted it again yet. There was some type of command or .zip or something that should be used to keep recovery after wipes. When i expirienced problems such as yours, it was also from a bad wipe from a toolkit. Using just the recovery afterwards, i never expirienced any issues, even without the recovery fix.
I would definitely try simms suggestion first if you can access recovery. If that fails, try one of the above processes.
PS, even if you can access recovery, if at this point you just want to go completely stock, the factory image will work regardless.
cheers
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
calavera-pw said:
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
Click to expand...
Click to collapse
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
appoos said:
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
Click to expand...
Click to collapse
ADB
Sent from my Galaxy Nexus
Pirateghost said:
ADB
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This dint work in my windows 8
appoos said:
This dint work in my windows 8
Click to expand...
Click to collapse
You're holding it wrong. ADB works on my Win8 machine
Pirateghost said:
You're holding it wrong. ADB works on my Win8 machine
Click to expand...
Click to collapse
can you tell me the procedure..
appoos said:
can you tell me the procedure..
Click to expand...
Click to collapse
no.
in the other thread that YOU created, you were given links to follow and the instructions are already there. i dont hold hands
I could do it with ADB..thanks guys
Long story so please bear with me. I have a Sprint I9505. I had installed a rom which made me lose mobile data and I eventually called Sprint to help me restore it. I of course did not mention that They did a great job of helping me but one of the things that they made me do was a hard reset. I did so and went about going through the process of re-configuring my phone but it will not let me get past the wi-fi set-up screen because the wi-fi will not turn on. So that's where I am stuck. I rebooted into recovery mode and see that I still have CMW installed but it will not read my external 64g card nor will it let me mount it. My intent was to restore a nandroid back-up that I had made prior to installing the rom that gave me the issues. But no luck. I have my phone next to me and although it is not going past the wifi set up screen, I still hear my phone vibrate and the screen turns on so I assume that I'm still receiving notifications. I tried to install the I9505 firmware and go back to stock but it fails everytime with about 10 percent to go. I tried to download the firmware for Sprint but it gives me a download error after completion (I assume that it is a PC issue not a firmware issue). So I'm assuming that I'm not totally screwed since I can still get into recovery mode. I'm in a bit of a time crunch since I'm going out of the country Saturday and would like a working phone before then. Thanks to all of you in advance for any help that you can provide.
louie68 said:
Long story so please bear with me. I have a Sprint I9505. I had installed a rom which made me lose mobile data and I eventually called Sprint to help me restore it. I of course did not mention that They did a great job of helping me but one of the things that they made me do was a hard reset. I did so and went about going through the process of re-configuring my phone but it will not let me get past the wi-fi set-up screen because the wi-fi will not turn on. So that's where I am stuck. I rebooted into recovery mode and see that I still have CMW installed but it will not read my external 64g card nor will it let me mount it. My intent was to restore a nandroid back-up that I had made prior to installing the rom that gave me the issues. But no luck. I have my phone next to me and although it is not going past the wifi set up screen, I still hear my phone vibrate and the screen turns on so I assume that I'm still receiving notifications. I tried to install the I9505 firmware and go back to stock but it fails everytime with about 10 percent to go. I tried to download the firmware for Sprint but it gives me a download error after completion (I assume that it is a PC issue not a firmware issue). So I'm assuming that I'm not totally screwed since I can still get into recovery mode. I'm in a bit of a time crunch since I'm going out of the country Saturday and would like a working phone before then. Thanks to all of you in advance for any help that you can provide.
Click to expand...
Click to collapse
Try to flash the stock firmware + .pit file for your phone using Odin
Thanks, I'm the process of downloading the Sprint firmware from a different link from my previous one to see if that works or if it's my PC.
Aerys said:
Try to flash the stock firmware + .pit file for your phone using Odin
Click to expand...
Click to collapse
Sigh most wifi and data issues from roms come from a kernel issue never hard reset with faulty connections you should of imediately went into recovery and flashed the nandroid some roms arent out of the oven yet i would put that card in a card reader see if you can copy the nandroid and push it to the phones internal storage (if all possible) and see if it will boot off of that if not see if you can get the ruu
Sent from my HTC One X+ using xda premium
gothicasshole said:
Sigh most wifi and data issues from roms come from a kernel issue never hard reset with faulty connections you should of imediately went into recovery and flashed the nandroid some roms arent out of the oven yet i would put that card in a card reader see if you can copy the nandroid and push it to the phones internal storage (if all possible) and see if it will boot off of that if not see if you can get the ruu
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
this is Galaxy S4 my friend
Hello fellow internet users, I've been trying to resolve a problem I've been having with my Nexus 4 device, but given that I failed, I came here hoping somebody here could help me.
Recently I wanted to update CM Mod on my device (to the latest version supporting Android 4.3), but little did I know that it'd replace my recovery program from TWRP to ClockwordMod. Afterwards I proceeded to install Franco Kernel (r. 193) since from what I read it should have been compatible with my recently downloaded version of CM. After I flashed it, all the tints of blue on my screen turned into tints of orange/yellow (and vice versa). Afterwards I tried to fix it with flashing one of the supposedly stock kernels I found on the internet, however all it achieved was to make it unable for my phone to boot - now when I turn it on in normal mode all I see is a weird blue screen with intermittently flashing pink squares that create a checkered pattern. I tried to access the android root kit to unroot the phone and bring back the default kernel + rom, but so far I've been unable to access my phone from my PC. And in case you wonder, yes, I was stupid enough to not store any backups on the internal storage.
I hope there is a work around it, since I really need my phone to work , thanks in advance to whoever can provide me with some sound advice.
cubeth said:
Hello fellow internet users, I've been trying to resolve a problem I've been having with my Nexus 4 device, but given that I failed, I came here hoping somebody here could help me.
Recently I wanted to update CM Mod on my device (to the latest version supporting Android 4.3), but little did I know that it'd replace my recovery program from TWRP to ClockwordMod. Afterwards I proceeded to install Franco Kernel (r. 193) since from what I read it should have been compatible with my recently downloaded version of CM. After I flashed it, all the tints of blue on my screen turned into tints of orange/yellow (and vice versa). Afterwards I tried to fix it with flashing one of the supposedly stock kernels I found on the internet, however all it achieved was to make it unable for my phone to boot - now when I turn it on in normal mode all I see is a weird blue screen with intermittently flashing pink squares that create a checkered pattern. I tried to access the android root kit to unroot the phone and bring back the default kernel + rom, but so far I've been unable to access my phone from my PC. And in case you wonder, yes, I was stupid enough to not store any backups on the internal storage.
I hope there is a work around it, since I really need my phone to work , thanks in advance to whoever can provide me with some sound advice.
Click to expand...
Click to collapse
It sounds you had flashed a wrong version of kernel for JWR and JSS. If you can boot into recovery, then just download another ROM and save it to your phone. Wipe factory reset and then flash the new ROM.
taodan said:
It sounds you had flashed a wrong version of kernel for JWR and JSS. If you can boot into recovery, then just download another ROM and save it to your phone. Wipe factory reset and then flash the new ROM.
Click to expand...
Click to collapse
Thank you for the swift reply. The problem is, while I can boot into recovery, I can't save anything to my phone right now since I can´t access it from my PC.
cubeth said:
Thank you for the swift reply. The problem is, while I can boot into recovery, I can't save anything to my phone right now since I can´t access it from my PC.
Click to expand...
Click to collapse
Were you able to connect your phone to your PC prior to flashing the CM mod? If yes, then you can mount it while in recovery. If no, then I suggest you might want to spend some time reading the materials which software that you will need in order to connect your phone to your PC.
taodan said:
Were you able to connect your phone to your PC prior to flashing the CM mod? If yes, then you can mount it while in recovery. If no, then I suggest you might want to spend some time reading the materials which software that you will need in order to connect your phone to your PC.
Click to expand...
Click to collapse
Yes, the problem is that I did all the previous operations on another computer (on which nexus usb drivers were installed too), which I'll have access to in around 10 days. I was simply curious whether it is possible to find a workaround the fact that the computer I'm using currently doesn't recognise my device/can't install drivers, regardless of the mode my phone is in (bootloader, recovery or normal).
cubeth said:
Yes, the problem is that I did all the previous operations on another computer (on which nexus usb drivers were installed too), which I'll have access to in around 10 days. I was simply curious whether it is possible to find a workaround the fact that the computer I'm using currently doesn't recognise my device/can't install drivers, regardless of the mode my phone is in (bootloader, recovery or normal).
Click to expand...
Click to collapse
You'll have to install drivers manually.
Your problem is easily fixed. You don't need to wipe anything; that would be unnecessary. All you have to do is flash your ROM again. You can't use custom kernels with cm unless they are made specifically for it.
Sent from my Nexus 7 using Tapatalk
korockinout13 said:
You'll have to install drivers manually.
Your problem is easily fixed. You don't need to wipe anything; that would be unnecessary. All you have to do is flash your ROM again. You can't use custom kernels with cm unless they are made specifically for it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for your advice, I'll try to follow it and see if it works as soon as I've got back home.
Hi, I wanted to reply in the multirom thread but can't because I am still too newb. Hopefully someone here can point me in the right direction? I've tried everything I know how to do. I really appreciate any help I can get!
So here is my problem. I downloaded multirom for my n4, then I updated. I reopened, and noticed I had the red line of text saying I was missing a kernal or something, so I clicked that and install (so instead of just updating the app I updated my kernal? and I also clicked update recovery). I needed to finish in recovery mode so it rebooted. Then it soft bricked. It goes to the load screen (with countdown timer) and then just black screens indefinitely tmk (5+ minutes of adhd agony). I had already downloaded cm 10.2 and gapps on the device in preparation for multirom, so I rebooted into recovery again, launched multirom and added cm 10.2 with gapps. I first tried with sharing kernal because I don't have my laptop to install 4.3 .tar, but that failed, so I installed ROM without sharing kernal. It runs fine, except I can't use bluetooth or wifi... so it really doesn't run fine =/ everything else seems okay though.
All my data is already backed up on my hdd so no worries on losing that, but I would like my phone functioning sooner than later.
I'm on vacation and don't have laptop with me, any ideas on how I can fix this? I have my Nexus 7 too, so I can download stuff, but I don't know how to:
a) install 4.3 so I can get cm 10.2 fully running?
b) reinstall 4.4.2 to stock (I tried factory reset but it didn't do anything either)
I think the biggest problem is lack of laptop because I could easily just reset the phone with that and run my nandroid (which is on laptop too.... ftl) but if there is a solution please let me know! Thanks!!!
krkeco said:
Hi, I wanted to reply in the multirom thread but can't because I am still too newb. Hopefully someone here can point me in the right direction? I've tried everything I know how to do. I really appreciate any help I can get!
So here is my problem. I downloaded multirom for my n4, then I updated. I reopened, and noticed I had the red line of text saying I was missing a kernal or something, so I clicked that and install (so instead of just updating the app I updated my kernal? and I also clicked update recovery). I needed to finish in recovery mode so it rebooted. Then it soft bricked. It goes to the load screen (with countdown timer) and then just black screens indefinitely tmk (5+ minutes of adhd agony). I had already downloaded cm 10.2 and gapps on the device in preparation for multirom, so I rebooted into recovery again, launched multirom and added cm 10.2 with gapps. I first tried with sharing kernal because I don't have my laptop to install 4.3 .tar, but that failed, so I installed ROM without sharing kernal. It runs fine, except I can't use bluetooth or wifi... so it really doesn't run fine =/ everything else seems okay though.
All my data is already backed up on my hdd so no worries on losing that, but I would like my phone functioning sooner than later.
I'm on vacation and don't have laptop with me, any ideas on how I can fix this? I have my Nexus 7 too, so I can download stuff, but I don't know how to:
a) install 4.3 so I can get cm 10.2 fully running?
b) reinstall 4.4.2 to stock (I tried factory reset but it didn't do anything either)
I think the biggest problem is lack of laptop because I could easily just reset the phone with that and run my nandroid (which is on laptop too.... ftl) but if there is a solution please let me know! Thanks!!!
Click to expand...
Click to collapse
WHY DID THE ERROR HAPPENED?:Because multirom app sets the default kernel to 4.2.2 one, since you werent on 4.2.2 it soft bricked.
DO I NEED TO REINSTALL STOCK TO GET CM FULLY WORKING?: Nope, just search in the general section of our device, for the hybrid modem thread, download the hybrid .84 and flash on recovery
PS: I think you will need OTG to pass the file from your n7 to your n4 since no bluetooh,no data and no wifi....
Or search like crazy around google to see if there is a way to pass files thru nfc
Thanks for the quick reply, is that the 27 or the 33 / 84 download?
sites.google.com/site/bpearuploads/
Or does it not matter?
opssemnik said:
WHY DID THE ERROR HAPPENED?:Because multirom app sets the default kernel to 4.2.2 one, since you werent on 4.2.2 it soft bricked.
DO I NEED TO REINSTALL STOCK TO GET CM FULLY WORKING?: Nope, just search in the general section of our device, for the hybrid modem thread, download the hybrid .84 and flash on recovery
PS: I think you will need OTG to pass the file from your n7 to your n4 since no bluetooh,no data and no wifi....
Or search like crazy around google to see if there is a way to pass files thru nfc
Click to expand...
Click to collapse
Got it figured out thanks to your help!
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.