Develop Bugs

[ACS][Odin]Stock EG30 Deodexed with Root 3.0/Busybox 1.18.4

Big thanks to RoadRAGEN for helping me figure out an ext4 issue! Odin this to get Deodexed stock EG30 with latest root and su binary and Busybox 1.18.4.
This does not wipe data.
I am not responsible for anything that happens to your phone. You do this at your own risk.
I have only tested this with the stock kernel and Bubby's CWM kernel.
Download​
IMPORTANT: Make sure you have installed the proper XP or Win7 drivers before starting. Also, remove the SD card from the phone (this may not be necessary, but having the SD card installed has caused Odin to fail for a number of people, so might as well just do it).
1. Extract the contents of the zip file to a folder
2. Open odin
3. Put your phone in download mode (Shut it off, wait for lights to all go out, then hold v-down + power)
4. connect phone (you should see odin put a Com4 or something like that in the first box. The actual number is NOT important what is important is something popped up there when you connected your device, meaning ODIN can see it)
5. The only box that should be checked is Auto Reboot.
6. You do not need to choose a pit file.
7. In the PDA Section choose the tar file. (Deodexed-Rooted-Busybox-EG30.tar)
8. Hit start. It will do its thing.
9. If it fails than try a new cable.
10. If the phone hangs for any reason take the battery and sdcard out and let it sit for an hour. Put it back together and try again.

reserved just in case

reserved again

Awesome crawrj. You do great work.
Sent From My Evo Killer!!!

Dumb question..... Will this flash the stock kernel that was released with the phone or is this the stock kernel source that is available from Samsung? Awesome Work sir!
Samsung Galaxy S II

Cannot wait to try, lol

stangdriverdoug said:
Dumb question..... Will this flash the stock kernel that was released with the phone or is this the stock kernel source that is available from Samsung? Awesome Work sir!
Samsung Galaxy S II
Click to expand...
Click to collapse
This does not contain a kernel. This is a stock file system that is rooted with busybox. I have tested on the root kernel and Bubby's CWM kernel. I have not tested on the Zedomax kernel.

Cool thanks!
Samsung Galaxy S II

File is up.

My phone is not rooted. If I flash this I will be rooted with the Kernel that was on the phone out of box? Also if I then flash Clock work recovery will it change the Kernel to the one others are claiming LOS on?

redram38 said:
My phone is not rooted. If I flash this I will be rooted with the Kernel that was on the phone out of box? Also if I then flash Clock work recovery will it change the Kernel to the one others are claiming LOS on?
Click to expand...
Click to collapse
That is correct. It will be just like flashing with the stock kernel which I have done. If you flash CWM it will change the kernel. Whether or not you get the LOS is up in the air. I have been using it for days and haven't had it yet.

Just so I have this straight, this is a stock rom, no kernel, deoxed so once installed I can flash a theme over it.
I flashed buddies kernel with cwm rooted and flashed back to the stock kernel is there anything I need to do with my kernel or can I just flash this rom?
Edit: he beat me to it, must have been typing at the same time.
Sent from my Samsung Epic Touch 4G

skyward01 said:
Just so I have this straight, this is a stock rom, no kernel, deoxed so once installed I can flash a theme over it.
I flashed buddies kernel with cwm rooted and flashed back to the stock kernel is there anything I need to do with my kernel or can I just flash this rom?
Sent from my Samsung Epic Touch 4G
Click to expand...
Click to collapse
That is correct. Just flash and go.

Im on starburst rom with zedomax v3..could i just flash the stock kernel and then flash this on top of starburst?

Awesome work. Does the Odin flash give you CWM as well? Or just SuperUser?
Sent from my Galaxy S II

jayv1717 said:
Im on starburst rom with zedomax v3..could i just flash the stock kernel and then flash this on top of starburst?
Click to expand...
Click to collapse
This will overwrite everything regardless of what setup you are on.
Sent from my SPH-D700 using xda premium

crawrj said:
That is correct. It will be just like flashing with the stock kernel which I have done. If you flash CWM it will change the kernel. Whether or not you get the LOS is up in the air. I have been using it for days and haven't had it yet.
Click to expand...
Click to collapse
Ok...so the only way to have CWM is to change the kernel? I guess rom manager doesn't work for flashing CWM? Sorry if its a stupid question but I have been all over these threads for a week trying to decide which way to root and which way is better.

Dj21o said:
Awesome work. Does the Odin flash give you CWM as well? Or just SuperUser?
Sent from my Galaxy S II
Click to expand...
Click to collapse
That what I was going to ask. You said we could flash a theme over this so I assume CWM is in there as well right?
Sent from my SPH-D700 using xda premium

JohnCorleone said:
This will overwrite everything regardless of what setup you are on.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
thanks bro.. One more question does this wipe internal sd card?

This does not have the kernel. I left it out for people to make their own decision on what kernel to use. Once we get a completely stock kernel with stock CWM I will update it. But for now it is just the system partion.

[KERNEL] SPH-L710 (Galaxy S III SPRINT) ROOTED INSECURE KERNELS - Latest: L710VPALF9

Hi Guys,
Here you can find rooted stock kernels (without any modifications, only "insecure" root added) for SPRINT's version of Galaxy S III (SPH-L710).
This WILL rise your custom binary counter.
Insecure Means that adb daemon on phone is working as root. If you need more answers on what is insecure kernel, search over xda forums, the answer is there.
To flash, use latest ODIN (3.07) : Download Here!
*LATEST* - 29.06.2012 - L710VPALF9
23.05.2012 - L710VPALEN
Enjoy!
Code:
Instructions:
- Run odin
- unpack zip (you should see .tar file inside)
- point to this TAR file in odin as PDA
- click flash
- done

What exactly does insecure do for me?
Sent from my SPH-L710 using Tapatalk 2

Does this allow for adb remount?
Sent from my SPH-L710 using xda premium

If the device is rooted, what is the utility of the rooted kernel?
Sent from my SPH-L710 using Tapatalk 2

Insecure == allows adb remount by default. which means that adb on phone is working as root. If you need more answers on what is insecure kernel, search over xda forums, the answer is there

do we have to reset google wallet for this?

initial said:
do we have to reset google wallet for this?
Click to expand...
Click to collapse
You shouldn't have to, but wallet isn't working anyway.

AdamLange said:
Hi Guys,
Here you can find rooted stock kernels (without any modifications, only "insecure" root added) for SPRINT's version of Galaxy S III (SPH-L710).
This WILL rise your custom binary counter.
Insecure Means that adb daemon on phone is working as root. If you need more answers on what is insecure kernel, search over xda forums, the answer is there.
To flash, use latest ODIN (3.07) : Download Here!
*LATEST* - L710VPALEN
Enjoy!
Code:
Instructions:
- Run odin
- unpack zip (you should see .tar file inside)
- point to this TAR file in odin as PDA
- click flash
- done
Click to expand...
Click to collapse
any word on this being updated for latest kernel?

Which is the latest? you mean kernel from OTA? if so, not. i dont have this ota, its not available trough samsung servers. And for sure, we dont know if the kernel was changed (it may not be touched by OTA).
If you're after OTA, please PM me, we will find out.

Rooted kernel for latest OTA added to first post! Enjoy!

Is this supposed to change the baseband version in the about phone section? still old baseband if it is...????

Baseband is MODEM not KERNEL KERNEL will only change Kernel version.

AdamLange said:
Baseband is MODEM not KERNEL KERNEL will only change Kernel version.
Click to expand...
Click to collapse
true, but kernel number does not reflect any change either??? (That is, in settings, about phone...) no change...

No. Kernel is kernel, the only change u will see on your eyes is kernel version/build info.
PS: Cut the sig man, it takes huge space even on my 24" monitor.

Can we flash this with mobile Odin?

So maybe a dumb question......and after reading the post I can see this was KIND OF answered, but what does updating the kernel actually do?? My phone is rooted, but I still keep getting the "update available" message. If I accept the update is it just a kernel update and by flashing this kernel instead, it's already root compatible?? I'm not sure if Im even making sense! LOL

Karma79 said:
So maybe a dumb question......and after reading the post I can see this was KIND OF answered, but what does updating the kernel actually do?? My phone is rooted, but I still keep getting the "update available" message. If I accept the update is it just a kernel update and by flashing this kernel instead, it's already root compatible?? I'm not sure if Im even making sense! LOL
Click to expand...
Click to collapse
In theory if you just update your build.prop the update notification should go away.
Sent from my SPH-L710 using Tapatalk 2

Respecting other members is a forum rule
Thanks
FNM

Will this make a custom boot animation possible?
Sent from my SPH-L710 using xda app-developers app

No, its just a rooted stock kernel.

[Q] Unable to flash new kernel

Hi everyone,
I just got the Samsung Galaxy S3 and I was able to root and flash a custom ROM. I'm currently on Axis ROM: (4.1.2 customized Touchwiz) Link:
http://forum.xda-developers.com/showthread.php?t=2089801
The kernel I had right now is stock and I'm not every satisfied with the battery life. Therefore, I try to flash a different one but keep getting error in recovery. I tried TWRP recovery, it shows the red error Fail. I also tried Clockmod touch, get the same error saying unable to extract/flash the zip.
Yes, I did wipe cache several times before flashing. Additionally, I had download different kernel zip (more than 10 of them) in case it's a bad download. Nothing works. I do have a decent experience flashing ROM and stuff with Android devices and this is the strangest thing I ever ran into.
I'm on T-mobile Galaxy s3 by the way. Any insight is appreciated. Thank you!

Make sure you're flashing a compatible kernel. There are touchwiz and aosp kernels, the title for the rom should say what kind of base it has.
Edit: looks like it's a touchwiz rom so make sure you flash a kernel that's compatible with touchwiz. What kernel are you trying to flash?
Oh and also make sure the download is correct.
Sent from my SGH-T999

What versions of twrp and cwm did you use?
When you booted into recovery did it look the same each time? I ask because you got some red error fail on both???
Open a root capable browser and go to /system
Look for install-recovery.sh
If its there, delete it and reinstall twrp/cwm.
Sent from my SGH-T999L using xda premium

marcoxx626 said:
Make sure you're flashing a compatible kernel. There are touchwiz and aosp kernels, the title for the rom should say what kind of base it has.
Edit: looks like it's a touchwiz rom so make sure you flash a kernel that's compatible with touchwiz. What kernel are you trying to flash?
Oh and also make sure the download is correct.
Sent from my SGH-T999
Click to expand...
Click to collapse
Yes, they are compatible. Kinetic Pulse, Darkside, KT kernel, all three of them fail.
DocHoliday77 said:
What versions of twrp and cwm did you use?
When you booted into recovery did it look the same each time? I ask because you got some red error fail on both???
Open a root capable browser and go to /system
Look for install-recovery.sh
If its there, delete it and reinstall twrp/cwm.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
I didn't find such file in /system. The recovery looks different. I do know how they look like since I used both of them before. TWRP shows error in Red (Fail). cwm doesn't, but show error that unable to extract zip.
CWM Touch 6.0.2.3
TWRP 2.4.2.0
Yes, all these recovery and kernel are T-mobile. I tried full wipe/no wipe but nothing helps.
P.s: thank you for replying though.

Do you have busybox installed?
Sent from my SGH-T999L using xda premium

Yes I do. Just check it in Terminal.
Sent from my SGH-T999 using Tapatalk 4 Beta

Try using the latest recoveries.
Twrp - 2.5.0.0
Cwm - 6.0.3.1
Sent from my SGH-T999L using xda premium

[APP] Flashable AOSP Browser

Hello,
I needed a flashable AOSP browser, so I made one and flashed in my GE HTC One. Works fine.

thanks it worked

In 4.3?

Ivixmax said:
In 4.3?
Click to expand...
Click to collapse
I'm running stock GE 4.3 with root, and I flashed it. Didn't seem to do anything.
I also tried a whole variety of methods, some of which people reported working on 4.3, and I've had no luck.

thanks, works well

jabza said:
I'm running stock GE 4.3 with root, and I flashed it. Didn't seem to do anything.
I also tried a whole variety of methods, some of which people reported working on 4.3, and I've had no luck.
Click to expand...
Click to collapse
System folder is write protected by default even with root on stock kernel. Flar2 just posted a stock kernel in the Dev section with write protection disabled.
Sent from my HTC One using xda premium

jabza said:
I'm running stock GE 4.3 with root, and I flashed it. Didn't seem to do anything.
I also tried a whole variety of methods, some of which people reported working on 4.3, and I've had no luck.
Click to expand...
Click to collapse
I'm having a similar problem. I flashed the zip using TWRP 2.6, but it doesn't seem to install the apk anywhere. Running ARHD GE 3.0 currently.
augie7107 said:
System folder is write protected by default even with root on stock kernel. Flar2 just posted a stock kernel in the Dev section with write protection disabled.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I just flashed the new kernel Flar2 posted, write protection should be disabled now. Although, I tried to copy browser.apk into my system/app folder and I got an "Permission denied" error.

T5BRICK said:
I'm having a similar problem. I flashed the zip using TWRP 2.6, but it doesn't seem to install the apk anywhere. Running ARHD GE 3.0 currently.
I just flashed the new kernel Flar2 posted, write protection should be disabled now. Although, I tried to copy browser.apk into my system/app folder and I got an "Permission denied" error.
Click to expand...
Click to collapse
Once you flash a kernel, you will lose root. You need to re-root the device again after flashing flar2's kernel.

augie7107 said:
Once you flash a kernel, you will lose root. You need to re-root the device again after flashing flar2's kernel.
Click to expand...
Click to collapse
I saw the note about that in Flar2's thread, so I reflashed SuperSU 1.5.1 immediately after flashing the kernel, it still wouldn't work. I ended up installing a different ROM with the 4.3 AOSPBrowser built iin, but I'm running into a similar problem where I can't install the Chrome bookmark sync...I'm sure I'll figure it out eventually.

Root Access Possibly Lost Fix Root?

I have my N7 on bone stock, rooted with superSU 1.60 installed. I flashed the .zip made by Chainfire, and no matter the recovery CWM non-touch , CWM, or TWRP after making a backup , I hit reboot system, and I get this message every time.
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
I've selecting option 1 multiple times and I still get the same message after a backup ,and before rebooting!! Root access works fine on all my apps and everything else I'm just curious as to why I'm seeing this via any recovery thanks. I'm sure its silly and an easy fix.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Try v1.55
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip

Disabled auto-update SuperSU in the playstore , flashed v1.55 ,and problem solved . Thank You!
Sent from my Nexus 7 using XDA Premium 4 mobile app

I tried the latest version today, and It seems as though the problem still exists in SuperSU v1.65. I just flashed back to v1.55
Sent from my Nexus 7 using XDA Premium 4 mobile app

Jewveeski said:
Disabled auto-update SuperSU in the playstore , flashed v1.55 ,and problem solved . Thank You!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've done this, i disable auto-update, flashed the v1.55 in CWM and rebooted. Now i cant use SuperSU anymore? tells me i have to update binaries. And i know that if i do the "root access possbibly lost" error comes again? any solutions?

In settings there is an option for reinstall as seen in the pic below click that then reboot your device , then reboot to recovery flash version v1.55 and make sure you still have the auto update feature in the play store unchecked. See if that works.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Same issue on a Galaxy Nexus running 4.3 stock rooted... SU requires an update and then the recovery thinks root has been lost (this is not actually the case)... any ideas?

lost root and twrp
so i first discovered i lost root when it said no binary found then when i was going into twrp to reflash the zip all i get is a dead android on its back with a red triangle hovering over it. Went back into adb and flash recovery twrp.img and it says successful but i still get the same thing. any one know the correct thread to point me to? ive looked but cant find this problem. my device boots fine and i can get to the boot loader just not recovery.

Same thing happens with my Nexus 4, I always hit No because it says root may have been lost even if I just enter CWM without flashing any rom or doing any action but rebooting to system

Jewveeski said:
I tried the latest version today, and It seems as though the problem still exists in SuperSU v1.65. I just flashed back to v1.55
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same message on my SGS4 with stock Android 4.3 and SuperSU v1.80.

Same message with my GT-i9300, CWM 6.0.4.4 Touch (i've tried also with CWM 6.0.4.3 NO Touch) and SuperSU v.1.80

I have the same problem too on my Galaxy Nexus GSM 4.3 build JWR66Y with SuperSu by Chainfire v1.8.6 and CWM Touch Recovery v6.0.4.3
Is there a solution?
Thanks in advance
Happy Holidays and Merry Christmas

Same message, S4 mini GT-I9195 4.3 su 1.86

Same message here...
I am running CM 10.2 with CWM Touch and SuperSUv1.86
Is this a big problem?
I think CWM should work just fine regardless of this message right?
If anyone has truly found a "recent" fix please let us know.
Oh i tried reinstalling CWM Touch and that did not fix the problem..
Thank you all for your time and assistance.

Same, CM10.2 cwm, SuperSU 1.86, S4 MINI, GT-I9195, never got this message with CM10.1.3, nor with any other 4.2 ROM. I think it's a 4.3 issue not just with CM, I tried 2 other 4.3.1 ROMs, they all said the same thing, yrs the device still works fine when selecting "yes fix root"
My concern is to WHY does this message appear?? And it's there a way to fix this permanently?
Sent from my GT-I9195

kamikaze702k said:
Same, CM10.2 cwm, SuperSU 1.86, S4 MINI, GT-I9195, never got this message with CM10.1.3, nor with any other 4.2 ROM. I think it's a 4.3 issue not just with CM, I tried 2 other 4.3.1 ROMs, they all said the same thing, yrs the device still works fine when selecting "yes fix root"
My concern is to WHY does this message appear?? And it's there a way to fix this permanently?
Sent from my GT-I9195
Click to expand...
Click to collapse
I figured that my device was okay, I mean root still worked just fine.
I bet it has to do with SELinux...
Thanks for the response. I also would love to find a way to fix this permanently. I just did a ROM backup with CWM Touch and I didn't have any issues so this just must be some warning message that doesn't affect anything. Was a bit scary though...
Hopefully someone will find a universal fix soon...
-droidshadow

droidshadow said:
I figured that my device was okay, I mean root still worked just fine.
I bet it has to do with SELinux...
Thanks for the response. I also would love to find a way to fix this permanently. I just did a ROM backup with CWM Touch and I didn't have any issues so this just must be some warning message that doesn't affect anything. Was a bit scary though...
Hopefully someone will find a universal fix soon...
-droidshadow
Click to expand...
Click to collapse
See, I did a rom backup also with rom manager, after the backup was complete the message still appears, it's more scary if your using a custom recovery because officially my device isn't on rom managers list of supported devices. Hopefully we can get a fix for this.
I'm sure we will it's only a matter of time I guess, I've flashed 4 roms in 3 days just to check the roms and this message came upon after installing 3. However it didn't appear with 4.2.2 so it has to be something with 4.3.x roms
Sent from my GT-I9195

maybe we should switch to TWRP?...
kamikaze702k said:
See, I did a rom backup also with rom manager, after the backup was complete the message still appears, it's more scary if your using a custom recovery because officially my device isn't on rom managers list of supported devices. Hopefully we can get a fix for this.
I'm sure we will it's only a matter of time I guess, I've flashed 4 roms in 3 days just to check the roms and this message came upon after installing 3. However it didn't appear with 4.2.2 so it has to be something with 4.3.x roms
Sent from my GT-I9195
Click to expand...
Click to collapse
Has anyone gotten this message with TWRP Recovery Manager? I am thinking that this might only be a problem with ROM's running Android 4.3+ with CWM Recovery Manager.
I have a Nexus 7 2013 tablet which runs like 3 different KitKat ROM's and one JB ROM (4.3.1) and I have never gotten a message like that on TWRP.
Maybe we should just switch to TWRP until CWM works this out or unless someone comes up with a permanent solution...
-droidshadow

droidshadow said:
Has anyone gotten this message with TWRP Recovery Manager? I am thinking that this might only be a problem with ROM's running Android 4.3+ with CWM Recovery Manager.
I have a Nexus 7 2013 tablet which runs like 3 different KitKat ROM's and one JB ROM (4.3.1) and I have never gotten a message like that on TWRP.
Maybe we should just switch to TWRP until CWM works this out or unless someone comes up with a permanent solution...
-droidshadow
Click to expand...
Click to collapse
Your right, my other device I'm using TWRP recovery and few days ago I installed a 4.3 liquid smooth ROM and never got this message!
It's an issue with CWM combined with 4.3 ROMS from what I've tested.
I only thought it was happening on my GT-I9195 because i was using a custom based CWM recovery, but now I know it's across most devices this message is occurring
Sent from my GT-I9195

TWRP is the way to go!
kamikaze702k said:
Your right, my other device I'm using TWRP recovery and few days ago I installed a 4.3 liquid smooth ROM and never got this message!
It's an issue with CWM combined with 4.3 ROMS from what I've tested.
I only thought it was happening on my GT-I9195 because i was using a custom based CWM recovery, but now I know it's across most devices this message is occurring
Sent from my GT-I9195
Click to expand...
Click to collapse
So i just switched my Verizon SGS3 (d2vzw) from CWM Touch to TWRP Touch 2.6.31 and i go to error message/warning about the SU binary being corrupted. This seems to be just an isolated incident with CWM and Android ROM's running 4.3+
With all of the work I have been doing with my Nexus 7 FLO + TWRP Recovery I decided to go ahead and switch my phone to TWRP. It was kind of hard to switch because I started out with CWM but I have just quickly become such a fan of TWRP.
If you don't want to wait for CWM to fix this issue which i am sure they will in their next update try out TWRP i think you will like it!
If you want an easy way to install TWRP recovery manager use the app "GooManager" from the Google Play store and use the your menu button on your phone and choose the open install open recovery script.
Or you could just as easily download the recovery image file from the official TWRP website and flash it with the app flashify.
Don't you just love technology!?
-droidshadow