Hey guys, so I recently unlocked, rooted, and created a nandroid backup using TWRP with wugs program. Anyways I want to put on a new ROM and kernerl and I was thinking of either the CleanROM 3 (4.2.1) with m-kernel or the Linaro ROM and Kernel combo. Which one would you guys recommend? Does these ROMs support flash? And how do I use wugs program to do these steps as I am not good with adb haha.
oakleyguy89 said:
Hey guys, so I recently unlocked, rooted, and created a nandroid backup using TWRP with wugs program. Anyways I want to put on a new ROM and kernerl and I was thinking of either the CleanROM 3 (4.2.1) with m-kernel or the Linaro ROM and Kernel combo. Which one would you guys recommend? Does these ROMs support flash? And how do I use wugs program to do these steps as I am not good with adb haha.
Click to expand...
Click to collapse
you should first figure out what you are doing, what the rom and kernels are called. they arent called Linaro rom/kernel, linaro is the toolchain used to build them. and you shouldnt use root toolboxes, figure out how to flash roms and kernels right first(through your recovery), before you end up started a "i bricked my seven" thread.
simms22 said:
you should first figure out what you are doing, what the rom and kernels are called. they arent called Linaro rom/kernel, linaro is the toolchain used to build them. and you shouldnt use root toolboxes, figure out how to flash roms and kernels right first(through your recovery), before you end up started a "i bricked my seven" thread.
Click to expand...
Click to collapse
Can't I just go into boot recovery through goo manager and be able to wipe with TWRP and all that?
oakleyguy89 said:
Can't I just go into boot recovery through goo manager and be able to wipe with TWRP and all that?
Click to expand...
Click to collapse
you can go into your recovery a multitude of ways. in twrp, wipe data, flash your ROM, flash your kernel, then reboot. if you are just updating your ROM, you don't have to wipe a thing. if you are flashing a different ROM, then you have to wipe data(factory reset). don't worry about wiping dalvik or cache as they get wiped when you flash the ROM. when flashing kernels, you never have to wipe anything regardless of what you read. the dalvik and cache have nothing to do with kernels. I suggest you experiment with a few different Roms and kernels, I prefer the rasbean jelly ROM with the trinity kernel.
simms22 said:
you can go into your recovery a multitude of ways. in twrp, wipe data, flash your ROM, flash your kernel, then reboot. if you are just updating your ROM, you don't have to wipe a thing. if you are flashing a different ROM, then you have to wipe data(factory reset). don't worry about wiping dalvik or cache as they get wiped when you flash the ROM. when flashing kernels, you never have to wipe anything regardless of what you read. the dalvik and cache have nothing to do with kernels. I suggest you experiment with a few different Roms and kernels, I prefer the rasbean jelly ROM with the trinity kernel.
Click to expand...
Click to collapse
Cool, i will have to experiment but Im having troubles getting into recovery mode. I get into bootloader and selet recoverymode but then it doesnt bring up TWRP, it just shows the droid with the door to his guts open with an exclamation mark. I tried goo manager and then go into recovery but the same thing happens. I have to hold the power button just to get pass the error.
You need to install open recovery Script in the settings tab of goo and it will find and download the latest version of TWRP and install it for you, if you had a custom recovery and installed a ota then it deletes it and you are left without one.As long as you are unlocked and rooted you should be golden.
Kodiack99 said:
You need to install open recovery Script in the settings tab of goo and it will find and download the latest version of TWRP and install it for you, if you had a custom recovery and installed a ota then it deletes it and you are left without one.As long as you are unlocked and rooted you should be golden.
Click to expand...
Click to collapse
Sweet, it worked. Thanks man. So when TWRP was loading from wugs toolkit was it not flashed? Also when wiping do i just do factory reset?
oakleyguy89 said:
Sweet, it worked. Thanks man. So when TWRP was loading from wugs toolkit was it not flashed? Also when wiping do i just do factory reset?
Click to expand...
Click to collapse
no. even if you do it the right way(no root toolkits) there is a command to flash your recovery permanently or a command to just boot it once(fastboot flash recovery recoveryname.img as opposed to fastboot boot recovery recoveryname.img). yes, wiping = factory reset.
simms22 said:
no. even if you do it the right way(no root toolkits) there is a command to flash your recovery permanently or a command to just boot it once(fastboot flash recovery recoveryname.img as opposed to fastboot boot recovery recoveryname.img). yes, wiping = factory reset.
Click to expand...
Click to collapse
Thanks! So i downloaded the rascarlo grouper which i am guessing is the rasbean. Where do I put the zip file in the nexus? Also does rasbeanjelly include flash support?
oakleyguy89 said:
Thanks! So i downloaded the rascarlo grouper which i am guessing is the rasbean. Where do I put the zip file in the nexus? Also, TWRP homescreen shows "Install" Im guessing its the same thing as flash right?
Click to expand...
Click to collapse
you can leave it in downloads, just where you downloaded it to if you downloaded it straight to your device. yes, install is flash. just find it where it is in the filesystem. if you downloaded it straight to your device, it will be in the downloads folder. btw, trinity kernel goes great with rasbean. trinity kernels http://derkernel.com/jb-seven.php press the experimental tab, alpha0(4.2.1 kernel). flash the rom, then the kernel, then reboot. rasbean comes with the busybox installer app, open it after booting up, install busybox(you need it for root apps to work properly). install it to /system/bin, youll see the option.
simms22 said:
you can leave it in downloads, just where you downloaded it to if you downloaded it straight to your device. yes, install is flash. just find it where it is in the filesystem. if you downloaded it straight to your device, it will be in the downloads folder. btw, trinity kernel goes great with rasbean. trinity kernels http://derkernel.com/jb-seven.php press the experimental tab, alpha0(4.2.1 kernel). flash the rom, then the kernel, then reboot. rasbean comes with the busybox installer app, open it after booting up, install busybox(you need it for root apps to work properly). install it to /system/bin, youll see the option.
Click to expand...
Click to collapse
That was easy enough lol Thanks for the help man! Oh, for some reason I am not seeing the busybox installer app so will i have to find it in play store? Also, i flashed trinity kernel now how I use it? xD
oakleyguy89 said:
That was easy enough lol Thanks for the help man! Oh, for some reason I am not seeing the busybox installer app so will i have to find it in play store?
Click to expand...
Click to collapse
if its not there, its this one, the best one https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
and yea, its all very easy. its just a matter of learning what the terms mean, and getting over the fear of breaking your device. even rooting the device from scratch is very easy, to many easier than a root toolkit. its just the fear of doing it.
---------- Post added at 10:16 PM ---------- Previous post was at 10:10 PM ----------
oakleyguy89 said:
That was easy enough lol Thanks for the help man! Oh, for some reason I am not seeing the busybox installer app so will i have to find it in play store? Also, i flashed trinity kernel now how I use it? xD
Click to expand...
Click to collapse
there are free cpu control apps in the market, and on xda. but the best way is to use the trinity kernel toolbox(it has extra stuff included, that the free apps dont have, but its a paid app. its worth it, but its definitely your call). btw, everything thats included in the trinity kernel toolbox can be done free via the terminal emulator(many of those scripts are in my signature), but the app just makes things easier and gives support to a great dev.
simms22 said:
if its not there, its this one, the best one https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
and yea, its all very easy. its just a matter of learning what the terms mean, and getting over the fear of breaking your device. even rooting the device from scratch is very easy, to many easier than a root toolkit. its just the fear of doing it.
---------- Post added at 10:16 PM ---------- Previous post was at 10:10 PM ----------
there are free cpu control apps in the market, and on xda. but the best way is to use the trinity kernel toolbox(it has extra stuff included, that the free apps dont have, but its a paid app. its worth it, but its definitely your call). btw, everything thats included in the trinity kernel toolbox can be done free via the terminal emulator(many of those scripts are in my signature), but the app just makes things easier and gives support to a great dev.
Click to expand...
Click to collapse
How do I use those commands? Through command prompt? Is there a way to put flash on this browser other than side loading flash with Firefox?
oakleyguy89 said:
How do I use those commands? Through command prompt? Is there a way to put flash on this browser other than side loading flash with Firefox?
Click to expand...
Click to collapse
you can install flash on the browser via finding the apk here in the forums or via flash installers in the play market. rasbean is an aosp based rom, aosp roms have the aosp android browser, which supports flash. all you need to do is install the apk.
you use the command either in a terminal emulator app(many good ones free in the play market), or finding some of these locations in a root file explorer, then manually editing the variables. some of the scripts/locations in my signature are only for the galaxy nexus, but many are for the nexus 7 too.
simms22 said:
you can install flash on the browser via finding the apk here in the forums or via flash installers in the play market. rasbean is an aosp based rom, aosp roms have the aosp android browser, which supports flash. all you need to do is install the apk.
you use the command either in a terminal emulator app(many good ones free in the play market), or finding some of these locations in a root file explorer, then manually editing the variables. some of the scripts/locations in my signature are only for the galaxy nexus, but many are for the nexus 7 too.
Click to expand...
Click to collapse
Cool i might try the commands but for now I'll use no frills cpu controller what is a stable overclock for Trinity. So I installed the flash and its all static looking. Is there a way to fix that?
oakleyguy89 said:
Cool i might try the commands but for now I'll use no frills cpu controller what is a stable overclock for Trinity. So I installed the flash and its all static looking. Is there a way to fix that?
Click to expand...
Click to collapse
what version of flash?
I run 1700mhz stable. but mostly I use 1150mhz for every day use.
simms22 said:
what version of flash?
I run 1700mhz stable. but mostly I use 1150mhz for every day use.
Click to expand...
Click to collapse
11.1.115.27 ,it hangs the browser constantly. Even when going to this site browser would hang. Now that it's uninstalled browser isn't crashing. What's that benchmark that I see on the forums comparing the nexus 7 to the evo one x and transformer prime?
I fixed my problem. For some reason it was the rasbean ROM I think, because I flashed clean ROM and flash is working like butter. Although I put enable plug ins on demand because when I got on a website with several flash videos playing it would make browser freeze up.
Related
It is what it says on the box....
I accidentally flashed an updated 4.2.2 rom onto my rooted Nexus 4 that was only running 4.2.1
Now, I can't get by the repeated error messages.
In recovery mode have tried to wipe the cache, the dalvik... even tried a full new install of the SU binary.... but can't seem to recover from this error.
Any insight?
I'm only asking this because it's on the script us tech support people have to follow. Did you make a backup?
wipe data(factory reset), then reflash your 4.2.2 nexus 4 rom(and gapps if needed). just flashing the su binaries does nothing for you. i do stuff like this for fun sometimes, its neat seeing all those errors
benderunit9000 said:
I'm only asking this because it's on the script us tech support people have to follow. Did you make a backup?
Click to expand...
Click to collapse
Fair question -
I backed up all my data, yes.
And I had just done a fresh unlocking so I didn't think I needed to - I still had the SU binary in the root directory.
I tried to reflash, still won't boot up in a way I can get at the root directory to put new .zip ROMs on the root, etc.
simms22 said:
wipe data(factory reset), then reflash your 4.2.2 nexus 4 rom(and gapps if needed). just flashing the su binaries does nothing for you. i do stuff like this for fun sometimes, its neat seeing all those errors
Click to expand...
Click to collapse
Did the factory reset. But I don't know how to re-flash with 4.2.2 since it was 4.2.1 originally.
I've downloaded the binary... do I use a similar command ./fastboot .... etc. like I used for flashing the other things?
Robworldwide said:
Fair question -
I backed up all my data, yes.
And I had just done a fresh unlocking so I didn't think I needed to - I still had the SU binary in the root directory.
I tried to reflash, still won't boot up in a way I can get at the root directory to put new .zip ROMs on the root, etc.
Click to expand...
Click to collapse
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
Robworldwide said:
Did the factory reset. But I don't know how to re-flash with 4.2.2 since it was 4.2.1 originally.
I've downloaded the binary... do I use a similar command ./fastboot .... etc. like I used for flashing the other things?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
simms22 said:
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
Click to expand...
Click to collapse
Hmmm.
Okay. I'm using clockworkMod Recov 5.8.3.1
I don't see the sideload option, but I'll keep looking.
Robworldwide said:
Hmmm.
Okay. I'm using clockworkMod Recov 5.8.3.1
I don't see the sideload option, but I'll keep looking.
Click to expand...
Click to collapse
cwm should have it, twrp has it for sure.
simms22 said:
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
I've been trying for hours. NO IDEA how to do any of this with a MAC computer.
I at least get to my CDW recovery screen, but I don't have a clue what to do next.
1. Go back to 100% stock using efrant's guide on here
2. Read up on everything so you know what you're doing
3. Try again
EddyOS said:
1. Go back to 100% stock using efrant's guide on here
2. Read up on everything so you know what you're doing
3. Try again
Click to expand...
Click to collapse
For the benefit of those coming after me, who may run into the same problem I did:
I can attest to the wisdom of the above 3 simple steps. It took me several hours to *finally* get this right, but the ABSOLUTE SLAM-DUNK I'VE FINALLY GOT THIS SUSSED PROCESS happened start-to-finish in 20 minutes.
The key step: METICULOUS FOLLOWING EFRANT'S GUIDE.
Do not get sidetracked by other boards or 'short-cuts'.
Just do this... it works, and obviously I learned a lot along the way.
I'm now back to stock, and happily unlocking and rooting, installing custom ROMs just being cognizant of the difficulty if I flash a 4.2.2 ROM on a device that is currently 4.2.1 (which, I believe, is the stock Sprint even now as of April 23).
Thank you to EddyOS and Simms.
what you actually have to do when flashing a ROM with a higher android version than the one you are running? for example I am now on CM10.1, and when Android 5.0 comes out, I need to flash new bootloader and baseband to update to a 5.0 ROM and it will work? Or what?
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
what you actually have to do when flashing a ROM with a higher android version than the one you are running? for example I am now on CM10.1, and when Android 5.0 comes out, I need to flash new bootloader and baseband to update to a 5.0 ROM and it will work? Or what?
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The key for me was that in addition to flashing the new ROM (I was running 4.2.1 and wanted to put on a custom 4.2.2 ROM) I had to sequentially install the custom ROM then the gapps file while in the same session in recovery mode. Do NOT install just the ROM and then exit recovery mode and reboot! That is how mine got hung up and I had to do a full stock re-install (see Efrant's guide).
As I understand it, this was an issue due to the a change in directory structure or something, so YMMV - this may not apply to future versions of Android.
Robworldwide said:
The key for me was that in addition to flashing the new ROM (I was running 4.2.1 and wanted to put on a custom 4.2.2 ROM) I had to sequentially install the custom ROM then the gapps file while in the same session in recovery mode. Do NOT install just the ROM and then exit recovery mode and reboot! That is how mine got hung up and I had to do a full stock re-install (see Efrant's guide).
As I understand it, this was an issue due to the a change in directory structure or something, so YMMV - this may not apply to future versions of Android.
Click to expand...
Click to collapse
So you didnt actually have to do something special cause I always flash gapps in same session.
And baseband and bootloader, how did you do that? Just flash before installing ROM?
Sent from my Nexus 4 using xda app-developers app
When KLP finally comes out the first thing I will be doing is flashing the complete factory image when released from Google. This will update everything and then using a custom KLP ROM will be a sinch. This is my personal opinion and others may say otherwise but for me it works
EddyOS said:
When KLP finally comes out the first thing I will be doing is flashing the complete factory image when released from Google. This will update everything and then using a custom KLP ROM will be a sinch. This is my personal opinion and others may say otherwise but for me it works
Click to expand...
Click to collapse
Yeah but cant you just install new bootloader and baseband, and then flash a ROM? Much easier imo
Sent from my Nexus 4 using xda app-developers app
I, personally, prefer to flash everything first and then go custom. Dunno why, just do!
EddyOS said:
I, personally, prefer to flash everything first and then go custom. Dunno why, just do!
Click to expand...
Click to collapse
Meh, easier if you just flash stock ROM in CWM first if you want to...
But could someone please answer my question?
Sent from my Nexus 4 using xda app-developers app
I have just switched over from Iphone to S4 (AT&T) and I have rooted my phone and deleted some bloat apps with the app " NO BLOAT " . I read somewhere that if you do remove bloat apps you must flash the stock rom before you can factory reset?
Reason that I want to do this is because phone seems a little slow so want to remove all stuff and then re-root and flash over cyanogenmod.
Also... To flash over the stock ROM all I need is ODIN and follow those directions corred?
THEN....
When I decide to flash to cyanogenmod all I have to do is Root phone > Install CWM or Loki? (Not sure which one) > then Flash to cyanogen?
Sorry for not understanding much but just switched -- starting to get the hang of it though.
Any help is appreciated.
Thanks
To get the stock software yes just odin back to stock , then when you decide you want the custom ROMs then the easiest way to flash custom recoveries is download goo manager and once you open the app hit the menu button and click on "install open recovery script" let it download and install , then you will have twrp touch recovery and you can flash any ROM that has a Loki patched kernel , or any Loki patched kernel , if its not then you have to patch each one you flash .
But if you want cwm with the auto Loki then it takes care of all the Loki stuff , and you can down load it and flash it in twrp.
ncrispi said:
I have just switched over from Iphone to S4 (AT&T) and I have rooted my phone and deleted some bloat apps with the app " NO BLOAT " . I read somewhere that if you do remove bloat apps you must flash the stock rom before you can factory reset?
Reason that I want to do this is because phone seems a little slow so want to remove all stuff and then re-root and flash over cyanogenmod.
Also... To flash over the stock ROM all I need is ODIN and follow those directions corred?
THEN....
When I decide to flash to cyanogenmod all I have to do is Root phone > Install CWM or Loki? (Not sure which one) > then Flash to cyanogen?
Sorry for not understanding much but just switched -- starting to get the hang of it though.
Any help is appreciated.
Thanks
Click to expand...
Click to collapse
Follow the directions here:http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/
There is a youtube video on the website, I suggest you watch it through first. Make sure Make sure Make sure you download the correct stock software from the Galaxy S4 Stock Firmware section. Odin can be downloaded there as well. I have done this a couple of times, it works.
Bigtjmc said:
To get the stock software yes just odin back to stock , then when you decide you want the custom ROMs then the easiest way to flash custom recoveries is download goo manager and once you open the app hit the menu button and click on "install open recovery script" let it download and install , then you will have twrp touch recovery and you can flash any ROM that has a Loki patched kernel , or any Loki patched kernel , if its not then you have to patch each one you flash .
But if you want cwm with the auto Loki then it takes care of all the Loki stuff , and you can down load it and flash it in twrp.
Click to expand...
Click to collapse
Hello,
Your post confused me quite a bit... I think I read somewhere that TWRP does not work with AT&T or is very bugged? But what is goo manager exactly? and which custom recovery is better with Loki patched Kernel? ive heard a lot about CWM... but I know there is not a major difference in the two.
Which one is best and easiest for AT&T? -- And I believe I have to use the Loki Patch for AT&T bootloader correct?
Bigtjmc said:
To get the stock software yes just odin back to stock , then when you decide you want the custom ROMs then the easiest way to flash custom recoveries is download goo manager and once you open the app hit the menu button and click on "install open recovery script" let it download and install , then you will have twrp touch recovery and you can flash any ROM that has a Loki patched kernel , or any Loki patched kernel , if its not then you have to patch each one you flash .
But if you want cwm with the auto Loki then it takes care of all the Loki stuff , and you can down load it and flash it in twrp.
Click to expand...
Click to collapse
Video of Twrp install can be found here: http://galaxys4root.com/galaxy-s4-root/how-to-install-twrp-on-rooted-galaxy-s4-using-goo-manager/
Instructions for some Rom installs for ATT:
http://galaxys4root.com/category/att-galaxy-s4-roms/
I haven't tried to put any roms on mine yet, I have just been using the Nottach Xposed with xposed framework to customize mine.
http://forum.xda-developers.com/showthread.php?t=2285074
http://forum.xda-developers.com/showthread.php?t=1574401
CptGloval said:
Video of Twrp install can be found here: http://galaxys4root.com/galaxy-s4-root/how-to-install-twrp-on-rooted-galaxy-s4-using-goo-manager/
Instructions for some Rom installs for ATT:
http://galaxys4root.com/category/att-galaxy-s4-roms/
I haven't tried to put any roms on mine yet, I have just been using the Nottach Xposed with xposed framework to customize mine.
http://forum.xda-developers.com/showthread.php?t=2285074
http://forum.xda-developers.com/showthread.php?t=1574401
Click to expand...
Click to collapse
Can I uninstall Goo Manager after I install TWRP with it or no?
Yes but I just left it , its a small sometimes useful program,
If your not comfortable doing any mods then I would suggests not doing any until you are comfortable .
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
If you are stock , then first root the phone using mottochopper , then install goo and open the program (hit the menu button while in goo ) then install open recovery script .
---------- Post added at 10:39 AM ---------- Previous post was at 10:35 AM ----------
Then I would download the cwm recovery , flash it in twrp , download cymod rom/kernel and install in cwm and not worry about Loki ....that would be the most painless way IMO.
Bigtjmc said:
Yes but I just left it , its a small sometimes useful program,
If your not comfortable doing any mods then I would suggests not doing any until you are comfortable .
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
If you are stock , then first root the phone using mottochopper , then install goo and open the program (hit the menu button while in goo ) then install open recovery script .
---------- Post added at 10:39 AM ---------- Previous post was at 10:35 AM ----------
Then I would download the cwm recovery , flash it in twrp , download cymod rom/kernel and install in cwm and not worry about Loki ....that would be the most painless way IMO.
Click to expand...
Click to collapse
If I already have Open Recovery Script ( TWRP ) Why would I download CWM? Also is CYMOD both the ROM and the Kernel? Or would I have to do two separate things on this? I know flash ROM but never heard of the cymod kernel? Also What exactly does a kernel do? I know it can effect the Network and 4g and stuff but what is the point of it? -- Does one come with Cymod built in or would I have to find that separate?
http://forum.xda-developers.com/showthread.php?t=2275545
Bigtjmc said:
http://forum.xda-developers.com/showthread.php?t=2275545
Click to expand...
Click to collapse
Correct, So the ATT version comes with the Kernel already and it is already loki'd (That just means bootloaded?) to AT&T?
But I see people talking about flashing to other kernels while on the ROM? What is the difference aside from the Network... and what happens if I flash a Kernel that was not Loki'ed to AT&T ?
I believe it has a kernel, only reason I'm saying use the other recovery so you Dont have to Loki or look for Loki patches just choose the Rom you like and kernel if if does not have one , and some ROMs have gapps that your can download and flash , basically they are just app packages for certain ROMs .
A kernel is ,... Like ROM = car, kernel = drivetrain
Like a PC , windows can't operate without ram, and processors
Bigtjmc said:
I believe it has a kernel, only reason I'm saying use the other recovery so you Dont have to Loki or look for Loki patches just choose the Rom you like and kernel if if does not have one , and some ROMs have gapps that your can download and flash , basically they are just app packages for certain ROMs .
A kernel is ,... Like ROM = car, kernel = drivetrain
Like a PC , windows can't operate without ram, and processors
Click to expand...
Click to collapse
Oh, So if CWM does that automatically am I able to skip Goo and the other recovery and just follow
http://www.youtube.com/watch?v=VmkL9atpVHw (Get CWM on ATT S4) and not have to worry about any of that?
sorry about all of the questions - just hoping to understand it all before I try.
ncrispi;4238658art orrect said:
Loki is just a security patch over the boot loader check points , so the boot loader is untouched at this point.
And you can flash any att kernel that is lokied or you have to somehow Loki it yourself. But as far as flashing a kernel not lokied I Dont know what would happen , might be bad. And also make sure that the kernel is compilable with your ROM, such as (touch wiz) vs (aosp )
---------- Post added at 11:10 AM ---------- Previous post was at 11:07 AM ----------
ncrispi said:
Oh, So if CWM does that automatically am I able to skip Goo and the other recovery and just follow
http://www.youtube.com/watch?v=VmkL9atpVHw (Get CWM on ATT S4) and not have to worry about any of that?
sorry about all of the questions - just hoping to understand it all before I try.
Click to expand...
Click to collapse
Its all good man I'm try n to make it sound easy and it is once you get it , but if you have twrp all you have to do with cwm is flash it in twrp then you will have cwm recovery , now you won't have to deal with Loki it does it for you.
Click to expand...
Click to collapse
Bigtjmc said:
Loki is just a security patch over the boot loader check points , so the boot loader is untouched at this point.
And you can flash any att kernel that is lokied or you have to somehow Loki it yourself. But as far as flashing a kernel not lokied I Dont know what would happen , might be bad. And also make sure that the kernel is compilable with your ROM, such as (touch wiz) vs (aosp )
---------- Post added at 11:10 AM ---------- Previous post was at 11:07 AM ----------
Its all good man I'm try n to make it sound easy and it is once you get it , but if you have twrp all you have to do with cwm is flash it in twrp then you will have cwm recovery , now you won't have to deal with Loki it does it for you.
Click to expand...
Click to collapse
Okay so to sum it all up...
Once I do a fresh factory reset and root I can either install TWRC or CWM - No need for both - and then just flash the cyn rom.
Edit: so if I just have CWM then it will not automatically Loki for me?
ncrispi said:
Okay so to sum it all up...
Once I do a fresh factory reset and root I can either install TWRC or CWM - No need for both - and then just flash the cyn rom.
Edit: so if I just have CWM then it will not automatically Loki for me?
Click to expand...
Click to collapse
If you have twrp the you have done rooted , then I wouldn't bother going back factory just download the cwm file , open twrp flash the cwm file then if you have a rom that you want already downloaded then open recovery again now you cwm , make a backup then flash the new rom and gapps if it has any, cwm will loki for you yes.
---------- Post added at 11:23 AM ---------- Previous post was at 11:20 AM ----------
http://forum.xda-developers.com/showthread.php?t=2291956
That's the one that does the auto Loki.
Bigtjmc said:
If you have twrp the you have done rooted , then I wouldn't bother going back factory just download the cwm file , open twrp flash the cwm file then if you have a rom that you want already downloaded then open recovery again now you cwm , make a backup then flash the new rom and gapps if it has any, cwm will loki for you yes.
Click to expand...
Click to collapse
alright I think I understand now... I do not have twrp yet, only thing that i have done is rooted so it would not take much to un-root and re-root. but so I could just install CWM and just flash without the need for twrp? It sounds like twrp is just needed for one way to install cwm on to the phone then it is no longer needed... is that a correct assumption?
Also is this the same thing just different method or is this not auto-loki version?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
ncrispi said:
alright I think I understand now... I do not have twrp yet, only thing that i have done is rooted so it would not take much to un-root and re-root. but so I could just install CWM and just flash without the need for twrp? It sounds like twrp is just needed for one way to install cwm on to the phone then it is no longer needed... is that a correct assumption?
Click to expand...
Click to collapse
No need to unroot just , Dont get me wrong I like twrp as well as cwm , its just easier for me with all this Loki stuff.
Since your rooted , you can install goo and then use it to flash twrp without a computer and running commands and all that thru adb , just let goo manager install twrp then you can flash cwm thru twrp and then its easy as pie.
EDIT : after more researching is this what I need or will this completely mess my phone up?
http://forum.xda-developers.com/showthread.php?t=2297033
Apparently it can root and install CWM in one click... is that all I have to do?
ncrispi said:
EDIT : after more researching is this what I need or will this completely mess my phone up?
http://forum.xda-developers.com/showthread.php?t=2297033
Apparently it can root and install CWM in one click... is that all I have to do?
Click to expand...
Click to collapse
I'm sure this will work just the same I just did it a different way , if you do it that way just make sure to follow it to a t
Bigtjmc said:
I'm sure this will work just the same I just did it a different way , if you do it that way just make sure to follow it to a t
Click to expand...
Click to collapse
Alright I will go ahead and try this method when I get home as it seems to be by far the easiest. Has anyone else tried this method before and can confirm it works?
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
tigas68 said:
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Click to expand...
Click to collapse
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
thanks. :good:
tigas68 said:
thanks. :good:
Click to expand...
Click to collapse
Still isn't working...
When i tried to fastboot the recovery img the device turns off and never turns on again on is own!
Help please!
I like my root...!
here's the screens of waht happens.
This his what happens when i try to go into recovery mode...
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
zephiK said:
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
Click to expand...
Click to collapse
zephiK,
Already done that! I flashed the CWM recovery throught fastboot. The device turned off. When i turn it on again and tried to go into recovery mode, so i can flash the SU from chain fire, but got the image on my post!
The phone is unlocked!
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Johnsonyc said:
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
Click to expand...
Click to collapse
I used the sctock rom downloaded from the google developers website!
Johnsonyc said:
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Click to expand...
Click to collapse
What he said. The recovery flash isn't going through.
Sent from my Nexus 4 using Tapatalk 4 Beta
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Johnsonyc said:
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
Click to expand...
Click to collapse
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
sn0warmy said:
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
Click to expand...
Click to collapse
I don't even really use root explorer anymore just like having the ability to make nandroid backups. But after doing a clean install of 4.3 in fastboot and it only took 30 minutes from start to finish including app and data restores nandroids to me are not that useful anymore (I don't flash custom ROMs anymore). Google automatically re-installed all my apps as soon as I reconfigured my WIFI, they also restored my APN and my work WIFI settings but not Bluetooth. And I used Helium to restore the user app data and all my texts and helium doesn't need root access to work.
Here is the start of Koush's post on Google+ where he talks about superuser on 4.3.
I finally had a chance to dig into seeing why Superuser is broken on Android 4.3. https://android.googlesource.com/platform/dalvik/+/9907ca3cb8982063a846426ad3bdf3f90e3b87c2
Basically /system is mounted as nosuid to any zygote spawned process (ie, all Android apps). Root will still continue to work via adb shell, etc.
This is a pretty nasty change. It seems that SuperSU works around this by replacing install-recovery.sh to run a su daemon that pipes subsequent through it. Pretty hacky, but understandable why it was done this way.
Will need to look into how to do this in a less invasive fashion, if that is even possible. Of course, if building from source, this change can simply be reverted.
Here's a better explanation about superuser from Android Police.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/
Rooting for me is used for restoring my apps and stuffs using titanium backup. Another useful thing about rooting is the ability to check saved wifi passwords.
Just install twrp from fastboot and then flash the su zip file in twrp
Sent from my Nexus 4 using Tapatalk 2
EddyOS said:
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
Click to expand...
Click to collapse
@EddyOS
Your answer is what forums are not about! Instead of helping you had an atitude of an ass...!
@ Everyone else
After 5 or 6 attemps, doing it by the book, the CWD worked and i now have a Recovery mode! I didn´t did anything different, so i couldn´t really understand what went wrong before... SU from chainfire works perfectly! It´s now Rooted! And yes, the tuturials are idiot proof!
There´s something that´s bothering my mind... I can´t unistall some trash that cames with the 4.3 version using titanium backup, because he can´t find the apk files...! I could do it with the 4.2.2 version, but not with this one. I'm using the deoxed version.
Does anyone has the same problems?
Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.
jonraymond21 said:
Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.
Click to expand...
Click to collapse
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used
leaderbuilder said:
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used
Click to expand...
Click to collapse
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.
jonraymond21 said:
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.
Click to expand...
Click to collapse
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.
leaderbuilder said:
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.
Click to expand...
Click to collapse
man thanks so much. so i definitly got super user access. I'm about to do the goo manager. since you suggested the twrp i think i'm going to try that. since i have CWM recovery installed, do u think that will create any issues if I go to install TWRP from goo manager
actually i googled and it seems that goo manager will seamlessly overwrite cwm. sorry for the questions before searching. appreciate the help. i almost didn't come on here, which would of lead me to reverting to stock, doing cwm again, then being upset that i needed twrm for most roms lmao. I owe u one. If u ever need to learn how to make bad decisions, just shoot me a pm. I got u covered.
No it will just replace it.
I actually (and many around here too) prefer TWRP 2.5.0.2.
You can download the zip for that here, boot to recovery you have now (CWM) and then install that. Or use Goo to install lates TWRP and boot to recovery and then install zip and choose the 2.5.02 you downloaded and then save to your sd card
scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice
jonraymond21 said:
scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice
Click to expand...
Click to collapse
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try this Rom!
http://forum.xda-developers.com/showthread.php?t=2327692&page=43
works great!
I have rooted my mojo with towelroot v1, installed TWRP, flashed CM 12.1.
Then rebooted.
In the 12.1 install instructions it says "Install the ROM first then install the google apps". How do I install the google apps? Was I supposed to do that in recovery? Where do I get the gapps?
What do I need to do? Thanks.
Phoenix4848 said:
I have rooted my mojo with towelroot v1, installed TWRP, flashed CM 12.1.
Then rebooted.
In the 12.1 install instructions it says "Install the ROM first then install the google apps". How do I install the google apps? Was I supposed to do that in recovery? Where do I get the gapps?
What do I need to do? Thanks.
Click to expand...
Click to collapse
You should be able to find gapps from the following post: http://forum.xda-developers.com/showpost.php?p=65432534&postcount=301
You flash gapps from inside TWRP right after you flash CM, selecting the gapps zip you downloaded just as you did with the CM Rom. If memory serves, you can probably go back into TWRP and flash gapps without having to re-flash CM.
Sent from my C6730 using Tapatalk
TU
krikit said:
You should be able to find gapps from the following post: http://forum.xda-developers.com/showpost.php?p=65432534&postcount=301
You flash gapps from inside TWRP right after you flash CM, selecting the gapps zip you downloaded just as you did with the CM Rom. If memory serves, you can probably go back into TWRP and flash gapps without having to re-flash CM.
Sent from my C6730 using Tapatalk
Click to expand...
Click to collapse
Thanks, I made a little progress since I posted this. I found gapps 5.0 (someone elsewhere suggested 5.0 micro would be best for mojo).
Next question was 1) How to I re-enter recovery and can 2) Can I flash gapps after CM has already unpacked itself or whatever it does on initial run? You answered #2.
Is the only way to re-enter recovery by using some sort of quick reboot apk? Is there a combination of buttons on the controller you can press or something like that? Thanks again for your help.
Phoenix4848 said:
Thanks, I made a little progress since I posted this. I found gapps 5.0 (someone elsewhere suggested 5.0 micro would be best for mojo).
Next question was 1) How to I re-enter recovery and can 2) Can I flash gapps after CM has already unpacked itself or whatever it does on initial run? You answered #2.
Is the only way to re-enter recovery by using some sort of quick reboot apk? Is there a combination of buttons on the controller you can press or something like that? Thanks again for your help.
Click to expand...
Click to collapse
There is no button combo to do that, and of course the MOJO itself has no buttons (at least not where you can get to them). You can also enter recovery from fastboot, but installing quick reboot is easier. Just search the internet until you can find a download link, make sure you have "unknown sources" enabled in security settings, and install it from your download folder.
You should have no problems flashing GApps after CM is running, but if you do simply start over.
I think you'll have poor luck trying to flash a 5.0 GApps on CM12.1 though, you'll need a 5.1 file. I recommend flashing a pico version, then installing anything else you need (probably at least Google Play games) through Play Store.
http://opengapps.org/
If you need to enter recovery without the reboot app, I recommend reading the thread on recovery in the dev section again:
http://forum.xda-developers.com/mad...overy-twrp-2-8-2-0-recovery-mad-catz-t2973640
Solved.
After a failed attempt with a Quick Reboot apk I downloaded from somewhere (It didn't do the reboot part) I was able to find a flashify apk that allowed me to re-flash recovery and reboot into it.
Turns out you need 5.1 micro gapps. For lollipop 5.1. Who knew.
what did you use to root from 12.1 ?
i tried towelroot and many others. cant get any root with anything...
EDIT (its around 10/half at night in Germany)
OOOH,OOOOHHHHHH...ARE YOU ****INKKONG KIDDING ME ???
Root can be set in Developer settings.
I cant believe i missed it and wasted a complete day struggling in the internetz.
for the sake of **** - im done....... **** this **** ****
alliolli said:
what did you use to root from 12.1 ?
i tried towelroot and many others. cant get any root with anything...
EDIT (its around 10/half at night in Germany)
OOOH,OOOOHHHHHH...ARE YOU ****INKKONG KIDDING ME ???
Root can be set in Developer settings.
I cant believe i missed it and wasted a complete day struggling in the internetz.
for the sake of **** - im done....... **** this **** ****
Click to expand...
Click to collapse
Never so angry as when you're angry at yourself. Read the thread in the dev section...
alliolli said:
what did you use to root from 12.1 ?
i tried towelroot and many others. cant get any root with anything...
EDIT (its around 10/half at night in Germany)
OOOH,OOOOHHHHHH...ARE YOU ****INKKONG KIDDING ME ???
Root can be set in Developer settings.
I cant believe i missed it and wasted a complete day struggling in the internetz.
for the sake of **** - im done....... **** this **** ****
Click to expand...
Click to collapse
Haha. Yeah I was about to respond to that, but you beat me to it.