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.
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.
Hi guys, I made a mistake while playing with Smelkus (Ra-supersonic-v4.3-smelkusMOD).
While in recovery, I went into the Developer Menu and entered on the "Install eng (unguarded) su" option, which after rebooting, disabled root access from my EVO. Now, every time I try to get root access I get a segmentation fault error.
I'm using MazWoz 4.2.1 Jelly Bean B4.
Short of re-flashing the ROM, Is there anything I can do to regain root access? I really got it working the way I want it, so I don't want to wipe everything if I can avoid it.
Thanks! Oh, by the way, I made no back up ...(I know, my mistake).
Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.
Edit: Sorry, earlier it was in the dev section.
connman said:
Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.
Click to expand...
Click to collapse
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?
Krazy4evo said:
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?
Click to expand...
Click to collapse
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium
the.emilio said:
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.
Krazy4evo said:
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.
Click to expand...
Click to collapse
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.
connman said:
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.
Click to expand...
Click to collapse
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.
Krazy4evo said:
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.
Click to expand...
Click to collapse
Hmm. I'm running Smelkus in Provision/Jellyvision, which is a JB rom (great rom, by the way and very stable on our Evo). In fact, smelkusmod was recommended by the developer of Provision/Jellyvision as the recovery. It's based on AmonRA, so should be pretty compatible regardless.
Install unguarded su installs some old superuser hack as the su binary. Not sure what it was for, but it had a purpose at some point. The regular "Install or fix su & superuser" choice installs a normal (but quite old) version of the superuser.apk and binary and sets their permissions. Both should be avoided at this late stage of Evo use. I think Diablo updated to SuperSU on his version, but if you need to install Superuser (koush), SuperSU, or SuperUser it would be better to use the latest version of their respective flashable zips.
Recovery is entirely separate from the ROM and kernel you are running, so it doesn't matter if you have Jelly Bean, ICS, GB or even Android at all for that matter. All recoveries - stock, CWM, TWRP, RA, etc - are basically a mini-OS with their own kernel and init. It boots and runs the program, recovery. Recovery then executes built in commands and scripts included with it. When a ROM developer recommends a recovery, they are just promoting what they like. Any recovery can do the job in their own manner.
In your case, after installing that unguarded su, you could have done any of the following steps to recover:
Flashed a current Superuser zip if it was already on your phone
adb pushed one and flashed
Booted up the ROM, downloaded one, go back to recovery and flash
Flashed the ROM and gapps again, wiped cache and dalvik and rebooted
Restored backup if available