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.
Related
Hey guys,
glad to say that ive been able to debrick my phone like 5 times in a row successfully which is a weight off my shoulders.
however, once im debricked, rooted, cwm installed, and all .img's pushed i try to flash a custom rom. i've tried every one and i get bootloops every time... they seem to install just fine. very normal timing and everything, no errors. any ideas?
Don't format /data. Are you doing that? Link the steps you're taking when you are in cwm to flash over the rom. Maybe something is amiss.
nope not formatting data. ive been doing wipe cache, wipe dalvik, and format /system.
Man I was in the same boat as you but was finally able to get it sorted this morning. What I highly, highly recommend is starting as fresh and as clean as you possibly can. That is before you do CWM or anything like that restore your phone with the Korean kdz, push all the images (system being last) then make sure you have a bootable, working phone. Also I would recommend using different/new/fresh .img files...I downloaded ones from the unbricking thread and only used a copy of my baseband.img. I had a feeling one of my files wasn't quite right so starting with all new ones may have helped.
Don't try anything from a backup or do a restore or anything-start fresh and make sure everything works as it should. From there do CWM and then do your ROMS. I know you're almost there and its a headache to keep starting from the bottom but do it all one step at a time, in order and you will find success.
Good luck!
good call. i havent been pushing all the .img's. just the three he mentioned above. let me try this for the 80th time. ill let you know how it goes. just curious, do you use the v10f or v10i kdz?
Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.
If i was you i would install the new CWM, once it installs the new CWM it'll work.
gte460z said:
Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.
Click to expand...
Click to collapse
yep i know that part. thanks
Revolution said:
If i was you i would install the new CWM, once it installs the new CWM it'll work.
Click to expand...
Click to collapse
new cwm?? as in the newest version available?does it work on the nitro?
[CWM][24/01] ClockworkMod 5 Recovery For LG Nitro HD
http://forum.xda-developers.com/forumdisplay.php?f=1448
Follow instruction's then try flashing a ROM it should fix your problem.
ive been using cwm... doesnt get rid of the bootloops
mic.mayorga said:
ive been using cwm... doesnt get rid of the bootloops
Click to expand...
Click to collapse
I'm not sure you understand bro, there is a NEW UPDATE
Update your CWM and it'll fix this issue.
I had the same problem for awhile. Had to use the Unbricker:http://forum.xda-developers.com/showthread.php?t=1412367
Followed ALL instructions, including "Restoring Nitro HD partition images" before flashing CWM. After that, no more bootloops and installed Revolutions rom w/out issue. Reboots just fine after.
I used the V10i-the direct download from LG...I think all the other recommendations are spot on but first and foremost get everything squared away with a fresh install of the kdz, all the images (in the proper order), the new version of CWM and then your rom of choice...Hope you're making some progress!
I'm on the new CWM and still have a loop if I reboot. Then I need to restore from CWM to get going again.
The soft brick boot loop I got was caused solely by format /system. I did not format /data.
I went through the whole deal last night and this morning and was able to get a fresh start on everything and am now running the HD ROM and haven't had a boot loop since I got everything back up and running...
I really think starting with the freshest install and making sure everything is functional step by step is where you'll be able to get through all that mess...just stay away from and restores or using any .img files that may have any software glitches as you'll get back to square one every time.
Hope you get it sorted out!
nah bro, i had the new update. no worries tho i pushed all the images in the debrick and fixed it. thanks for all the help guys B)
Tight work-glad you were able to get it straight! Now once you get it where you want make a new backup with Nandroid and CWM and you'll be golden in case anything else happens.
Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks
huydq5000 said:
Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks
Click to expand...
Click to collapse
Go look at the thread "[Solved] Unbricking solution...". Follow it to the T, however, i'd recommend using v10i.kdz rather than v10f.kdz. Definitely try the f version first but if it doesn't work try i. That's what I did. Basically what you're going to want to do is:
1. Restore the phone to a korean image using the v10i (or f) file and the LG software provided and referenced in the unblocking thread.
2. Once booted, root the phone. (specific instructions for v10i are in a thread somewhere linked by [email protected] v10f use either SuperOneClick root or DoomLord v4. Make sure you have adb installed for doomlord.
3. Once rooted use adb to push over stock .img files in this order: boot, recovery, firmware, baseband, system.
4. after the files are pushed boot into phone and root again (optional).
5. Install CWM5 through adb or terminal emulator.
Good luck, let me know if you have any questions and I can go into more detail.
---First off, let me preface this by acknowledging the fact that, yes, I am indeed a noob. And I'm sure some of the info I'm going to put in here probably isn't needed, but as I said, I am a noob, and thus am not entirely sure what is relevant and what is not. I also apologize if some of what I say and/or what I did doesn't make sense and/or is idiotic, but again, noob. That being said I don't have any techie friends and never really had a nack for this kind of stuff, but hey gotta start somewhere right? So, that being said, here's my dilemma:
This all started last week when I was downloading the CyanogenMod Nightlies *Rom. The download started and was going along just fine when my phone suddenly turned off and starting vibrating and then wouldn't turn back on. Everything I would press power it would just start vibrating in regular one second intervals over and over. Finally I remove the battery. It turns back on fine. Download resumes. And... Bam! Happens again. This time I try the same remove to no avail and about 15 minutes later I'm thinking that this is it for my phone when it finally reboots. So I decide, alright, lemme just download this Rom and try to flash it, or at the very least just restore the phone and hope this is a software issue. So I had also just downloaded Rom Manager and was going into recovery via Clockworkmod recovery as the instructions prompted me to in the CyanogenMod tutorial. Now every other time I have installed a new Rom I just manually boot into recovery as the phone turns on. This time I boot into the Clockworkmod recovery though cuz I wanna follow the directions to the "T" and I proceed to selecting the factory reset and it wipes the data and freezes when wiping the cache. So I'm sitting there like, "Oh s**t, what do I do now?" I let it sit for fifteen minutes hoping it will magically unfreeze and all will be right in the world, but it doesn't and I reset the phone via the power button. Then it boots up and tells ne there a issue with my custom OS and I'm not really are what to do here. So, i reboot it and it acts like the reset was successful and prompts me to set up my phone like I just flashed the Jedi Mind Trick Rom I've been using. So I tried again, and same thing. Got stuck on clearing the cache. Luckily it lets me set up the phone again after I interrupt the frozen factory reset. This time I try to boot into recovery manually, pressing the hard keys, and all the phone does is restart. So I try again. And again. And again to no avail. I look up the key sequence thinking I may have forgotten it and am doing it wrong, but after trying every combo I can find online, it still doesn't work. So I give up and go into recovery via clockworkmod and restore my phone to my very first nandroid backup I made before I ever started messing with custom roms, and everything goes fine it seems until it gets to a command about something revolving cache and it freezes again! I eventually have to reset it and it gets stuck in a loop where the Samsung logo comes up, it makes a loud annoying beeping noise for a few seconds before it turns off and does it all over again. Now I'm sure I've bricked my phone. I take out the battery, wait, put it back in, but still nothing. I do this a few more times, wait and hour, and it finally boots up. So now I try to go into recovery manually again, but still just get the phone resetting. I try to go uninstall clockworkmod and go into recovery via Rom toolbox pro, but I still get the clockworkmod recovery rather than the phone's normal recovery I used to be able to get to before I ever installed clockworkmod. So I'm stuck here. I know that's a lot of info, but I didn't want to leave anything out incase it was important. Thanks in advance for any advice and/or directions you can give me. *
P.S. I read in someone's post here that the first issue of the phone turning off and vibrating could be the result of a bad power sensor. So I wanted to add that since this two mysterious restarts and vibrations, nothing like that has happened in the... Approximately 5 days since (for whatever that's worth). *
Thanks again, and I apologize for any ignorance you have encountered while trying to read this post.
OK seriously... save yourself the trouble and just flash TWRP recovery instead.
Sent from my SGH-T989 using xda app-developers app
Missing some needed info...
Current status? What do you have access to? Recovery? Does the ROM boot?
Any issues with the phone right now? (You say no mysterious reboots for 5 day now, just confirming)
Recovery version? If you're using CWM I would suggest against using ROM manager. I would also suggest you do use the darkside scripts for wiping your phone.
Exact ROMs you flashed?
whatiznt said:
OK seriously... save yourself the trouble and just flash TWRP recovery instead.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Ok. Checked it out and got twrp. I clicked install openrecoveryscript. It downloaded. Didn't restart or anything. Now can I just flash the new Rom I want directly from there then? All it says it that I must have installed the recovery script. Just wanted to know though, is it still right that when I reboot into recovery it goes to the cwm recovery? Just wanna make sure before I go messing up my phone.
Thanks!
mintharis said:
Missing some needed info...
Current status? What do you have access to? Recovery? Does the ROM boot?
Any issues with the phone right now? (You say no mysterious reboots for 5 day now, just confirming)
Recovery version? If you're using CWM I would suggest against using ROM manager. I would also suggest you do use the darkside scripts for wiping your phone.
Exact ROMs you flashed?
Click to expand...
Click to collapse
Currently I'm running the stock ICS Rom for the phone. Ill attach a screenshot of the specifics. I can go into cwm recovery but anything related to cache freezes. No issues with the phone other than I can't use my hard keys to boot into recovery when restarting the phone, if that even counts. I'm using cwm v6.0.1.4 and really I don't want to use cwm, how do I go about changing that? And I downloaded the darkside supervise and cache wipe. Do I just use those instead of the factory reset in the cwm recovery? Or did I read into that wrong?
Thanks!
I thought the new version of CWM was freezing, but it just takes FOREVER to do your first backup because it's building the blobs or whatever they are called. The second backup went fine, however, I think it's too much headache and went back to the 5.0.2.7. Call me crazy but I'm still very hesitant to use TWRP after the wave of phone bricks that happened a few months ago from people installing it.. I'm still not convinced its totally safe and stable..
VoiD_Dweller said:
I thought the new version of CWM was freezing, but it just takes FOREVER to do your first backup because it's building the blobs or whatever they are called. The second backup went fine, however, I think it's too much headache and went back to the 5.0.2.7. Call me crazy but I'm still very hesitant to use TWRP after the wave of phone bricks that happened a few months ago from people installing it.. I'm still not convinced its totally safe and stable..
Click to expand...
Click to collapse
Now when you day forever, what are you talkin here? I waited a very long time. Regardless though sounds like an easy solution so ill try this real quick and see. You think just reverting back to use 5.0.2.7. Would solve the cache problems I've been running into or would I have to try to clear that up first and then this would work?
Thanks!
jalight27 said:
Currently I'm running the stock ICS Rom for the phone. Ill attach a screenshot of the specifics. I can go into cwm recovery but anything related to cache freezes. No issues with the phone other than I can't use my hard keys to boot into recovery when restarting the phone, if that even counts. I'm using cwm v6.0.1.4 and really I don't want to use cwm, how do I go about changing that? And I downloaded the darkside supervise and cache wipe. Do I just use those instead of the factory reset in the cwm recovery? Or did I read into that wrong?
Thanks!
Click to expand...
Click to collapse
Yes, the darkside scripts were used in older cwm recoveries because the default wipes didn't do the job. As for switching away from cwm I'm guessing you want to jump to twrp. You can do that by following the instructions at http://teamw.in/project/twrp2/101
same thing happened to me on cwm v6.0.1.4 so this is what i did
1. flash an older version of cwm thru odin (search "cwm recovery tar t989")
2. reboot to cwm
3. darkside cache wipe (hopefully that will get to your homescreen, if not, super wipe and new rom that *****)
4. when you are at your homescreen, download and install goomanager from store
5. open it, tap the menu button, hit Install OpenRecoveryScript
6. reboot to recovery
7. now you have twrp, have fun
Thanks for the steps there. Pretty much did a combo of what everyone was saying. Went back to an older version of cwm and used darkside wipes. Then wouldn't you know? It worked! Yay for me. So I'll just keep my older version of cwm, for now at least. Well, anyway, thanks to everyone for helping me figure this out. Much obliged!
jalight27 said:
Now when you day forever, what are you talkin here? I waited a very long time. Regardless though sounds like an easy solution so ill try this real quick and see. You think just reverting back to use 5.0.2.7. Would solve the cache problems I've been running into or would I have to try to clear that up first and then this would work?
Thanks!
Click to expand...
Click to collapse
Forever like being 10 minutes min, maybe 15
ClaireH said:
same thing happened to me on cwm v6.0.1.4 so this is what i did
1. flash an older version of cwm thru odin (search "cwm recovery tar t989")
2. reboot to cwm
3. darkside cache wipe (hopefully that will get to your homescreen, if not, super wipe and new rom that *****)
4. when you are at your homescreen, download and install goomanager from store
5. open it, tap the menu button, hit Install OpenRecoveryScript
6. reboot to recovery
7. now you have twrp, have fun
Click to expand...
Click to collapse
+1.
Just happened to me last night. I was using CWM 6.0.1.4 touch version and finally crash without reason.
I almost tried to ODIN back to stock/unroot, then I thought it might be possible just re-flash the CWM recovery to 5.0.2.7 version.
And it works!
try to avoid 6.0.1.4 version at this time. lots of issues.
btw, twrp is better than CWM? what's the difference? how do I activate the recovery menu from boot?
fe1ixs said:
+1.
Just happened to me last night. I was using CWM 6.0.1.4 touch version and finally crash without reason.
I almost tried to ODIN back to stock/unroot, then I thought it might be possible just re-flash the CWM recovery to 5.0.2.7 version.
And it works!
try to avoid 6.0.1.4 version at this time. lots of issues.
btw, twrp is better than CWM? what's the difference? how do I activate the recovery menu from boot?
Click to expand...
Click to collapse
Yep, same thing I ended up doing, thought I posted that but I guess I never did. I ended up using the darkside wipes and going back to an older version like you and someone else said. Now everything's just fine. And btw, to get into recovery from boot just restart it holding power, volume up, and volume down at the same time. Then once you see the Samsung logo let go of the power button but keep holding volume up and down till you see the recovery menu.
Hello all,
I have partially bricked my phone while attempting to root. Admittedly, I am very much so a novice when it comes to rooting android devices, but I have learned a lot while attempting to fix it. My problem is that when I power it up, it hangs at the white HTC splash screen and never boots past that. At first, I tried simply to flash a stock rom. No success. I have also tried using an RUU and a stock clockwork recovery image. No success with either of these. While fiddling around in recovery, however, I have noticed something that might be the cause of the problem. Anytime I attempt to do anything in recovery, most of the time the following messages are returned: "error mounting /data/!" and "error mounting /cache/!"
Now, it is my belief that somehow (and I'm embarrassed to admit I've done such a number on my poor little phone) I deleted or incorrectly formatted the internal partitions, rendering them unusable. I have been reading, and it seems that the solution lies within a tool called sdparted. However, I am very afraid to totally brick my phone, so I came here for some help. Basically, I'm hoping someone can explain it to me like I'm 12 years old, haha.
Anyway, are my assumptions correct, or do I have a totally different kind of problem? Ideally, I would like to just completely return this to stock and bring about the end of this nightmare. Anyone who can help, I'm begging for your expertise!
Here is all the data I could think to give you all about my phone:
S-On
HBoot:0.98.0000
Radio:1.09.01.0312
Recovery-
Build: RA-VIVOW-v3.0.8
Well first mistake was unlocking instead of s-off. Also, try a a newer recovery like 4ext.net
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4 Beta
tylerlawhon said:
Well first mistake was unlocking instead of s-off. Also, try a a newer recovery like 4ext.net
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4 Beta
Click to expand...
Click to collapse
Not sure you can flash 4ext through adb...isn't only an apk that installs the recovery (if I remember correctly). I would try the latest CWM recovery first. And I agree that you need to get S-OFF - try one of the guides (like the one by Prototype).
tylerlawhon said:
Well first mistake was unlocking instead of s-off. Also, try a a newer recovery like 4ext.net
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hmmmm... Just logging in real quick after a hard day of work, will try that tomorrow and let you know the results.
brymaster5000 said:
Not sure you can flash 4ext through adb...isn't only an apk that installs the recovery (if I remember correctly). I would try the latest CWM recovery first. And I agree that you need to get S-OFF - try one of the guides (like the one by Prototype).
Click to expand...
Click to collapse
Ok, I tried flashing several different CWM images. Do you mean install CWM recovery over my current Ra recovery? And then proceed? Because as it stands, after attempting to flash the images through recovery, (and while it goes through most of it while looking successful) it seems to finish too quickly. Then, after rebooting, nothing was changed.
How would I go about installing CWM recovery over my current recovery? Should I bother doing this? Or how can I achieve S-Off from my current state? I vaguely remember coming to the conclusion that I couldn't get to S-off until I just completely flashed it back to stock. But then again, it's been a week since I've played with this phone. And I'm a complete noob. So any further advice would be appreciated.
RRCriswell said:
Hmmmm... Just logging in real quick after a hard day of work, will try that tomorrow and let you know the results.
Ok, I tried flashing several different CWM images. Do you mean install CWM recovery over my current Ra recovery? And then proceed? Because as it stands, after attempting to flash the images through recovery, (and while it goes through most of it while looking successful) it seems to finish too quickly. Then, after rebooting, nothing was changed.
How would I go about installing CWM recovery over my current recovery? Should I bother doing this? Or how can I achieve S-Off from my current state? I vaguely remember coming to the conclusion that I couldn't get to S-off until I just completely flashed it back to stock. But then again, it's been a week since I've played with this phone. And I'm a complete noob. So any further advice would be appreciated.
Click to expand...
Click to collapse
Use prototype's guide in the dev section. Look for the cwm thread and click on the flash instructions through adb command.
Sent from my Ascended Dinc2.
i have the exact same issue with a Inc 1. i have tried everything (including sdparted) with absolutely no luck. tried flashing the stock RUU, even unrooted and nothing worked. never could find anyone to know of a fix. i wish you the best of luck. will be watching this in hopes that you figure something out.
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
I initially flashed all the way back to the TWRP build before 2.3.1 but stopped there. I'll report back with results of your recommendation in the morning!
prboy1969 said:
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
Click to expand...
Click to collapse
ROM Manager was something I tried as a last resort as well, it flashed the custom recovery alright, but soft bricked it with a redundant recovery bootloop. I got past that by Odin-ing back to stock.
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
prboy1969 said:
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
Click to expand...
Click to collapse
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
n3td3v said:
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
Click to expand...
Click to collapse
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
prboy1969 said:
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
Click to expand...
Click to collapse
I tried formatting the sdcard as well as without the sdcard and even with a different one to no avail. I'm still on the hunt for pda, csc, etc. Odin files. My last resort will be to figure out how to get it replaced at Sprint as a defective device lol
Sent from my SPH-L710 using xda premium
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
billard412 said:
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Yes, stock recovery allows clearing of cache, depending on whose stock recovery I flash. If I flash the toolkit version of stock, I can clear no problems. There are a couple of other stock recoveries, such as this one, in which everything fails as well.
FYI, I have even flashed the stock builds you have on sxtp with the same results.
Thanks for this -- you solved my problem...at least mostly.
I tried to root a new Sprint SG3 by ODIN'ing CWM and then flashing a root.zip file. That epic failed just like your situation where nothing would mount in recovery whether I used CWM or TWRP. I am assuming that something must've changed on the Sprint S3's and that root method must not work anymore (for whatever reason). So I decided to go back to stock recovery and just wait and see if anything further is discovered about this here (I'm not a dev, so I have to wait for other more talented people to solve my problems). However, the stock recovery image that I downloaded from the same "Easy Root" tutorial here didn't work and I still couldn't mount anything.
Saw your post where you stated that the Toolkit stock recovery image worked, so I just tried that and score! However...my poor little recovery android is on his back with a red triangle and a "!". Everything mounts, I can wipe cache, browse around for an update, etc., but I'm a little concerned that my little Android is sick. Should I be? Is that because I have a flash count of 5 so it thinks I have a custom ROM?
Sorry to hijack your thread a little, but my problems seems to be related.
n3td3v said:
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
Click to expand...
Click to collapse
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
swiggs98 said:
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
Click to expand...
Click to collapse
Same boat. Rooted probably 6 S3 before now and my wife's new S3 I am seeing same thing.
Sent from my SPH-L900 using xda app-developers app
I'm having the same issue. I finally downloaded an image that allowed me to flash it but I still cannot mount anything in recovery? Any help would be nice
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
n3td3v said:
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
Click to expand...
Click to collapse
Folks, A quick search would have led ya here : http://forum.xda-developers.com/showthread.php?t=2183910&page=4 This is a known issue with both TWRP and CWM recoveries on newer S3's. Devs are working on it to find a solution. Just a matter of being patient and waiting. IF you just want root access, you can odin a pre-rooted rom to the phone with no issues. You'll atleast have root at that point. Just unable to change rom/kernels on the fly.
I achieved root with virtually no issues but thank you for the link!
Sent from my SPH-L710 using xda premium
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.