Related
Ok so I flashed it the first time and it was successful but noticed market was not opening so I flash the latest gapps for cyonogen mod and then everthing fc so wiped and flash and now it won't even boot it gets stuck on splash screen. Is it cause of SD card is on ext 4 or is it smellkus recovery or what?? Any help is much appreciative
Try wiping cache and dalvik then fix permissions in recovery.
Did you flash the correct ROM for your specific phone model and carrier? I had the the problem of flashing a T-Mobile ROM for my GS2 a while back, due to my excitement about using an ICS rom.
Ryan_28 said:
Did you flash the correct ROM for your specific phone model and carrier? I had the the problem of flashing a T-Mobile ROM for my GS2 a while back, due to my excitement about using an ICS rom.
Click to expand...
Click to collapse
Exactly...I've never heard of this rom for the evo. So I question it.
teh roxxorz said:
Exactly...I've never heard of this rom for the evo. So I question it.
Click to expand...
Click to collapse
no its for the evo its under evo general development it was just released
Can you boot into recovery? If so, I think your best bet is to restore a backup, delete the faulty ROM, and try reinstalling it if you want that specific ROM badly enough. That has worked for me a few times.
Ryan_28 said:
Can you boot into recovery? If so, I think your best bet is to restore a backup, delete the faulty ROM, and try reinstalling it if you want that specific ROM badly enough. That has worked for me a few times.[/Q
Yes I could go into recovery and I actually fixed the issue. I'm guessing it was the recovery itself that I was using because now I flashed Among RA recovery and now is booted and working fine. A great Tom overall. Thanks guys for your help
Click to expand...
Click to collapse
Not to bother anyone, but I was trying to run the droid GTRv2.0 ROM on my EVO 4G and it wont get past the first screen.
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
lordcheeto03 said:
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
Click to expand...
Click to collapse
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
Swetnes said:
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
SectorNine50 said:
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
Click to expand...
Click to collapse
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
SectorNine50 said:
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
Click to expand...
Click to collapse
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
drumist said:
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
Click to expand...
Click to collapse
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
You are correct, the Nitro is P930. And I'm sure this doesn't need pointing out, but when you download the ROM, make sure it's for P93x and not SU640. Most of the ROMS in the developer section have versions for both models.
Also, when you say you can't access CWM after flashing a ROM, how are you trying to access it? Holding Power+Volume down until the Factory Reset screen pops up? It still shows that screen even with CWM installed, but when you press the power button to perform the factory reset it SHOULD take you into CWM Recovery instead.
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
To access recovery, turn the device completely off. (If you're in a bootloop, pull battery or hold power button for ~20 seconds until screen stays off.) Then when phone is off, press and hold volume down and power buttons at the same time, not releasing until you see text asking if you want to factory reset. Press power button twice to confirm and you'll get to recovery.
Is this the method you're using to try to get to CWM?
My guess as to why you are getting bootloops is that you aren't wiping data first.
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
SectorNine50 said:
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
Click to expand...
Click to collapse
Good luck. Other possible things to try:
1) Check zip MD5 hash (or just redownload and replace) to make sure it's not corrupted.
2) Reformat entire SD card.
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
SectorNine50 said:
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
Click to expand...
Click to collapse
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
drumist said:
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
Click to expand...
Click to collapse
Ah, thank you! I must've been viewing an old thread. Now that I look at the version number, it appears that's the version I had been hunting for since the newest one didn't work.
Interesting, I most certainly misunderstood, I was under the impression that "rooting" the device was a filesystem level permission change. Good to know!
It seems like we are getting closer to a solution here. Thanks for your patience!
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
SectorNine50 said:
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
Click to expand...
Click to collapse
Yeah, the new one (6.0.1.5) just came out. I'll have to test it to see if it works for me.
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Malnilion said:
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Click to expand...
Click to collapse
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I really enjoy the integration Rom Manager/CM Updater has with CWM. If twrp is capable of running the install scripts those two use, I might consider trying it out, but I don't really like manually going through the steps to flash a rom every day.
OK, so I went into TWRP 2.6.0.0 and tried to flash CM 10.2. It came up with an error so I restored using the backup I had made, and after the restore it told me that root permissions had been lost, and asked if I wanted to fix it. I swiped to rix root permissions, and now it doesn't seem to be able to boot up.
It gets through the boot animation fine, bu gets stuck on the final screen where it flashes SAMSUNG across the screen. I can boot back into TWRP and have tried wiping data and starting fresh, installing a different ROM, everything I can to try to get it to start fresh, but the phone always gets stuck at the same screen flashing SAMSUNG.
Any ideas of what I should do to remedy this problem??
BlackHayze said:
OK, so I went into TWRP 2.6.0.0 and tried to flash CM 10.2. It came up with an error so I restored using the backup I had made, and after the restore it told me that root permissions had been lost, and asked if I wanted to fix it. I swiped to rix root permissions, and now it doesn't seem to be able to boot up.
It gets through the boot animation fine, bu gets stuck on the final screen where it flashes SAMSUNG across the screen. I can boot back into TWRP and have tried wiping data and starting fresh, installing a different ROM, everything I can to try to get it to start fresh, but the phone always gets stuck at the same screen flashing SAMSUNG.
Any ideas of what I should do to remedy this problem??
Click to expand...
Click to collapse
Start fresh again but this time in TWRP goto wipe/system that will rid all old rom files which sounds like your issue, worth a shot
SGSIIIJB said:
Start fresh again but this time in TWRP goto wipe/system that will rid all old rom files which sounds like your issue, worth a shot
Click to expand...
Click to collapse
Hopefully I can get a fast response here, I did that, but got a warning "No OS installed" before rebooting. Is that just telling me no ROM installed or does that literally mean that there is not an OS on the phone anymore? The second option seems unlikely but I don't want to risk it and mess things up even further.
BlackHayze said:
Hopefully I can get a fast response here, I did that, but got a warning "No OS installed" before rebooting. Is that just telling me no ROM installed or does that literally mean that there is not an OS on the phone anymore? The second option seems unlikely but I don't want to risk it and mess things up even further.
Click to expand...
Click to collapse
well after you wipe everything including system you need to install a rom. IF your NOT currently OTA updated to 4.3 use billard's zip:::::
[ROM/RESTORE][!MD4 OTA!](5-10)Quick Return to UNROOTED STOCK WITH FLASH COUNT RESET
Wipe everything :/system
Flash billards zip
Flash root.zip to keep root
Flash recovery zip to keep custom recovery
reboot
SGSIIIJB said:
well after you wipe everything including system you need to install a rom. IF your NOT currently OTA updated to 4.3 use billard's zip:::::
[ROM/RESTORE][!MD4 OTA!](5-10)Quick Return to UNROOTED STOCK WITH FLASH COUNT RESET
Click to expand...
Click to collapse
OK, I'll try to find a ROM to install really quickly just in case, but the problem comes in somehow I get an error on every single ROM I try to install, still don't know the issue, as I have installed many ROMs on my One without issue (this is my mom's S3, she just wants tethering to be a native feature on her phone.)
BlackHayze said:
OK, I'll try to find a ROM to install really quickly just in case, but the problem comes in somehow I get an error on every single ROM I try to install, still don't know the issue, as I have installed many ROMs on my One without issue (this is my mom's S3, she just wants tethering to be a native feature on her phone.)
Click to expand...
Click to collapse
If that's the case, I'd recommend this ROM: http://forum.xda-developers.com/showthread.php?t=2549136 I installed the SPHL710_ALLINONE_MK3_ODEX_12-04-2013_1030pm.zip which includes the latest stock 4.3 without all the KNOX stuff and with native tethering.
It also wipes the system partition for you.
Good luck!!
BlackHayze said:
OK, I'll try to find a ROM to install really quickly just in case, but the problem comes in somehow I get an error on every single ROM I try to install, still don't know the issue, as I have installed many ROMs on my One without issue (this is my mom's S3, she just wants tethering to be a native feature on her phone.)
Click to expand...
Click to collapse
Shouldnt be getting any errors installing/switching roms if your wiping correctly, If native tether is all your after then most if not all custom roms come with it enabled or you can keep stock rom and just flash the hotspot mod [MOD][Deodex][Odex][MB1][MC3][MD4][MK3]Hotspot Mod - Working 4G
BAReese said:
If that's the case, I'd recommend this ROM: http://forum.xda-developers.com/showthread.php?t=2549136 I installed the SPHL710_ALLINONE_MK3_ODEX_12-04-2013_1030pm.zip which includes the latest stock 4.3 without all the KNOX stuff and with native tethering.
It also wipes the system partition for you.
Good luck!!
Click to expand...
Click to collapse
Thank you! I will give this one a shot!
SGSIIIJB said:
Shouldnt be getting any errors installing/switching roms if your wiping correctly, If native tether is all your after then most if not all custom roms come with it enabled or you can keep stock rom and just flash the hotspot mod [MOD][Deodex][Odex][MB1][MC3][MD4][MK3]Hotspot Mod - Working 4G
Click to expand...
Click to collapse
I'm just as confused as anyone as to why I'm getting errors. The phone has proper root access and is running on TWRP, the same recovery I use on my One, and I have done at least 50-60 flashes of ROMs on that phone, without issue. I keep getting virtually the same error, something wrong with executing the updater binary in zip.
BAReese said:
If that's the case, I'd recommend this ROM: http://forum.xda-developers.com/showthread.php?t=2549136 I installed the SPHL710_ALLINONE_MK3_ODEX_12-04-2013_1030pm.zip which includes the latest stock 4.3 without all the KNOX stuff and with native tethering.
It also wipes the system partition for you.
Good luck!!
Click to expand...
Click to collapse
The ALLINONE worked! Thank you so much for the help guys! I appreciate it!
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Reflash in Odin.
Make sure you have the correct stock rom. If you flash the "md5" you may have flashed the wrong thing. The md5 is not tge firmware, that is just the code that verifies your firmware file is not corrupted.
If your old apps were still there, you flashed the wrong thing. There is no way to flash stock firmware in odin and not wipe the data partition.
You are correct then
Yeah, I flashed a tar.md5 in Odin. It gave me a new ROM but all my apps are there. After all that, I still can't go to recovery. I tried using the terminal and ROM Toolbox to go there, both didn't work. Can I just leave it as it is and find a way to recovery or is the only way to go to bootloader and flash a correct file to get to recovery?
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
serio22 said:
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
Click to expand...
Click to collapse
It depends on what you ate flashing.
If you are flashing a full stock factory image it will wipe user data. If you are just flashing a system partition it won't.
Essem G said:
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Click to expand...
Click to collapse
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
g7755725 said:
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
Click to expand...
Click to collapse
Also this. This gives you more control over the whole process
Skipjacks said:
Also this. This gives you more control over the whole process
Click to expand...
Click to collapse
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Essem G said:
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Click to expand...
Click to collapse
The first post of any customized stock rom will tell you if its deodexed. If it doesn't say it...its not.
@Essem G:
Any updates for us? I'm following this thread because I have similar problems with my WiFi not working after upgrading from 4.2.2.
Any luck getting TWRP flashed?
Also I believe that the stock firmwares do come as tar.md5's, as in the file: M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5 from ShinySide's stock firmware thread.
As for the WiFi issue, from the hours of reading I've done it looks like this problem occurs when you upgrade your firmware, but it no longer matches the bootloader. Such as bootloader (Baseband) showing MDL, but Build Number showing NH7, NK2, etc. What does your show?
This thread may be of use to you when you get back to a working ROM. Good luck!
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Essem G said:
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Click to expand...
Click to collapse
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
g7755725 said:
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
Click to expand...
Click to collapse
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks
Essem G said:
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks[/Q] it should
Click to expand...
Click to collapse
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Essem G said:
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Click to expand...
Click to collapse
Have you tried my gamerrom Ultimate 1 its basically stock touchwiz of if Official NK2 M919UVUFNK2 with stweaks and no bloatware here is the thread gru 1 is in.the botyom of the thread http://forum.xda-developers.com/galaxy-s4-tmobile/development/stock-os-gamerrom-ultimate-2-touchwiz-t3078467
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Essem G said:
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Click to expand...
Click to collapse
If you're trying to go back to complete stock then just Odin NK2 firmware. http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508 I used the NK2 from here about 2 days ago to go back to stock.
Hey guys. This is getting really frustrating. I was trying to find a custom kernel to use and so of course I made a backup. Backup is done, I go to flash kernel. Everything loads up, I think I'm golden. But to my surprise I can't connect to camera.
No big deal, I reboot to recovery restore backup and put my phone down to wait. Comeback later and my phone is stuck on white HTC logo not booting.
Do the button combination to restart in recovery and I go to wipe cache and dalvik thinking maybe that will help. Well it tells me it can't mount /system and I go to reboot after wiping and it says no OS is installed. Causing me to have to reflash whatever rom I was on(in this case it was Viper and the kernel I was trying to flash was elemental)
I am baffled as to why this is happening. Am I choosing the wrong partitions to backup?
I've had a lot of phones and I'm not new to TWRP or rooting and or S-Off for HTC devices. I am S-Off and bootloader is unlocked. Does anybody have any clues as to what the heck is going on?
Sent from my HTC 10 using XDA-Developers mobile app
inphamous36 said:
Hey guys. This is getting really frustrating. I was trying to find a custom kernel to use and so of course I made a backup. Backup is done, I go to flash kernel. Everything loads up, I think I'm golden. But to my surprise I can't connect to camera.
No big deal, I reboot to recovery restore backup and put my phone down to wait. Comeback later and my phone is stuck on white HTC logo not booting.
Do the button combination to restart in recovery and I go to wipe cache and dalvik thinking maybe that will help. Well it tells me it can't mount /system and I go to reboot after wiping and it says no OS is installed. Causing me to have to reflash whatever rom I was on(in this case it was Viper and the kernel I was trying to flash was elemental)
I am baffled as to why this is happening. Am I choosing the wrong partitions to backup?
I've had a lot of phones and I'm not new to TWRP or rooting and or S-Off for HTC devices. I am S-Off and bootloader is unlocked. Does anybody have any clues as to what the heck is going on?
Click to expand...
Click to collapse
Hey mate, camera has issues on new base with custom kernel. Has been mentioned many times in Viper thread. Might get fixed soon due to new kernel source release. Just use stock kernel until you have stable setup.
purple patch said:
Hey mate, camera has issues on new base with custom kernel. Has been mentioned many times in Viper thread. Might get fixed soon due to new kernel source release. Just use stock kernel until you have stable setup.
Click to expand...
Click to collapse
New kernels are already out for newer base.. You can try that and see
Sent from my HTC 10 using XDA-Developers mobile app
purple patch said:
Hey mate, camera has issues on new base with custom kernel. Has been mentioned many times in Viper thread. Might get fixed soon due to new kernel source release. Just use stock kernel until you have stable setup.
Click to expand...
Click to collapse
I had the same issue...turns out I just swiped to back up the default, on mine anyways, which was all boxes selected...just back up system, not system image, if you have that checked; and then boot and data. Maybe that will work for you.
hovercraftdriver said:
I had the same issue...turns out I just swiped to back up the default, on mine anyways, which was all boxes selected...just back up system, not system image, if you have that checked; and then boot and data. Maybe that will work for you.
Click to expand...
Click to collapse
Thank you, I'll try this.
Sent from my HTC 10 using XDA-Developers mobile app