Here is the OTA update zip.
http://www.androidfilehost.com/?fid=22946563261203148
d0c70dc593bdd729b14688a1be473102
http://tinyw.in/RwRh
d0c70dc593bdd729b14688a1be473102
Dammit, beat me to the punch lol. Thanks bud!
Sent from my SPH-L720 using Tapatalk 2
1) install update
2) adb pull /proc/config.gz
3) extract using 7zip/winrar etc
4) open config with wordpad
5) copy all and paste to pastebin.com
6) control + f setuid
that will tell ya if the switch has been flipped or not
shabbypenguin said:
1) install update
2) adb pull /proc/config.gz
3) extract using 7zip/winrar etc
4) open config with wordpad
5) copy all and paste to pastebin.com
6) control + f setuid
that will tell ya if the switch has been flipped or not
Click to expand...
Click to collapse
Will do. Running a backup right now and will install after that.
Putting stock back on.
Wiping Data
Installing update
Yep it is blocked.
crawrj said:
Yep it is blocked.
Click to expand...
Click to collapse
k gimme about 40-50 mins and ill have a workaround. mind posting that config file btw?
you planning on doing a rooted odex/deodex'd rom?
shabbypenguin said:
k gimme about 40-50 mins and ill have a workaround. mind posting that config file btw?
you planning on doing a rooted odex/deodex'd rom?
Click to expand...
Click to collapse
Yeah I plan on it. Attached the gz.
Pulling source now to run a diff and see what has changed in kernel beyond the obvious.
Be interested to see if they left that in the defconfig since they know someone will probably flip it back.
anyone check to see if kies would update em? would be a nice thing to have the tar for it as well
Just to confirm the obvious rooting did not work.
Installing the stock MDC kernel allows rooting.
if you dont mind, have mdl kernel installed, flash cwm/twrp. boot into recovery and dd the kernel. i wish to compare ramdisks
Well, that diff was actually productive.
They have made the change in the common defconfig for all i9505 variants.
So expect this to be coming to the rest of them soon.
Looks like on the kernel side a majority of the changes are to 3 files:
firmware/ssp_rev03.fw.ihex
firmware/tsp_synaptics/synaptics_b0_5_1.fw.ihex
firmware/tsp_synaptics/synaptics_b0_5_1_fac.fw.ihex
Beyond those 3, many of the changes pertain to ATT and EUR variants.
Attaching a zip of the diff file for reference as I'll be spreading the word.
Guess I'll get with Agat to make an MDL kernel with that flipped off...
*Update 2* As Shabby mentioned, only Tmo and Sprint have seen this so far... so AT&T results can be ignored.
www.shabbypenguin.com/OUDstuff/Sams...-Kernel/TW/Stable/Stock-MDL-Stable-spr-TW.zip
sorry for teh delay, had to make breakfast for my daughter this is a MDL source built kernel, but with MDC ramdisk until i can get MDL ramdisk. it will allow root however
shabbypenguin said:
if you dont mind, have mdl kernel installed, flash cwm/twrp. boot into recovery and dd the kernel. i wish to compare ramdisks
Click to expand...
Click to collapse
The boot.img is in the update.zip already. Or do you still need it DD?
crawrj said:
The boot.img is in the update.zip already. Or do you still need it DD?
Click to expand...
Click to collapse
oh didnt know they included a full one. i didnt download the update.zip (doesnt do me any good )
ok recompiling now, seems only a minor edit in ramdisk but may be worthwhile to include it. new kernel is up at same old link crawj you have permission if youd like to include it in a odex/deodex'd rootable zip rom
Well, may not be as bad as we read a few days ago.
AT&T threads saying motochopper still working - we'd have to test CF Auto Root.
Also OTA Root Keeper supposedly working.
In the end I'll just flash a kernel that plays nice. Thanks Shabby!
garwynn said:
Well, may not be as bad as we read a few days ago.
AT&T threads saying motochopper still working - we'd have to test CF Auto Root.
Also OTA Root Keeper supposedly working.
In the end I'll just flash a kernel that plays nice. Thanks Shabby!
Click to expand...
Click to collapse
I haven't looked at the at&t threads but I would say they are wrong. You can install root but the kernel kills it. So it won't run. I have tried all three methods of install and it doesn't work.
1. Installing custom recovery and flashing supersu
2. Oding CFAutoRoot
3. Moto
shabbypenguin said:
oh didnt know they included a full one. i didnt download the update.zip (doesnt do me any good )
ok recompiling now, seems only a minor edit in ramdisk but may be worthwhile to include it. new kernel is up at same old link crawj you have permission if youd like to include it in a odex/deodex'd rootable zip rom
Click to expand...
Click to collapse
So you have the new kernel working? Where is that same old link again And thanks!
garwynn said:
Well, may not be as bad as we read a few days ago.
AT&T threads saying motochopper still working - we'd have to test CF Auto Root.
Also OTA Root Keeper supposedly working.
In the end I'll just flash a kernel that plays nice. Thanks Shabby!
Click to expand...
Click to collapse
crawrj is correct, its not a matte rof re-rooting its the binary is being killed as it tries to launch. att didnt get it in an update yet, only tmo and sprint for the us carriers.
crawrj said:
So you have the new kernel working? Where is that same old link again And thanks!
Click to expand...
Click to collapse
http://www.shabbypenguin.com/OUDstu...-Kernel/TW/Stable/Stock-MDL-Stable-spr-TW.zip
I have not rooted yet and im trying to push the OTA update now. once it goes through, you want me to try one of the rooting methods???
Related
Warning! There is a huge risk that you will permanently loose root with no way to regain root. Do not flash s-on before you flash this RUU. You will permanently loose root if you do!!!
Incredible_C_GB_S_VERIZON_WWE_4.06.605.2_Radio_2.1 5.10.07.07_NV.zip - 180.6 MB
MD5 Sum: 096d841530dd2f223ef4a1b701c7d429
Install Instructions:
•Rename the file to PB31IMG.zip
•Drop it on the root of the SD Card
•Boot into the bootloader
•Flash as usual
Next go here* to learn how to get root back. Your phone must still be s-off in order to regain full root.
*Sorry guys link is down. I'll add in the instructions here tomorrow.
Want to contact unrEVOked on IRC about the root situation and how you can help?You can speak to the unrEVOked team live.
Go to: unrEVOked IRC
IRC Instructions:
1. Type in a nickname into the nickname box. This is your name that will be displayed during the chat.
2. Type in the captcha.
3. Press connect.
Once connected the page will load and give some brief info. The page will fully load and you will notice a list of usernames on the right. These are all the people currently in the IRC chat. You will also notice a text box at the very bottom of the page. Just type what you want to ask or say there and press [enter] on your keyboard to send your message. Just wait after you send your message. Someone will soon reply. The IRC is similar to an instant messenger, its just web based.
Hopefully this will help some of you to know where to go to get the info you need for this issue.
Disclaimer Please do not abuse this IRC channel. I'm sure unrEVOked is very busy trying to keep up with all these demands for new root patches. Lets not spoil this line of communication while we have it. Keep your questions clear and to the point. Also try to include only important information during your chat. Most importantly, be respectful and professional.
Click to expand...
Click to collapse
now someone pull the radio from this and post it.
k.electron said:
now someone pull the radio from this and post it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1227215
So I pulled the RUU today, extracted system.img via yaffsexpert app from the market. Transferred to my PC for inspection. build.prop is exactly the same as the other leak using diff. I don't see any significant difference but we'll wait to hear from one of the official devs if there is a difference.
tiny4579 said:
So I pulled the RUU today, extracted system.img via yaffsexpert app from the market. Transferred to my PC for inspection. build.prop is exactly the same as the other leak using diff. I don't see any significant difference but we'll wait to hear from one of the official devs if there is a difference.
Click to expand...
Click to collapse
Also, the boot.img from the RUU broke adb for me. Maybe I have to do something special with it.
So everybody who did this is unrooted now or what
Ignore: I'm goofy and flashed the old zip instead of the new.
evilstewie23 said:
So everybody who did this is unrooted now or what
Click to expand...
Click to collapse
If you flashed the zip file in the OP then it will return you to stock recovery and you will be unrooted yes. I don't know about S-OFF though, I'm not sure if it reverts it. It will install the bootloader but I thought S-OFF was deeper in the system than that. Maybe someone who installed this can tell us. If you're still S-OFF you should be able to flash a custom recovery. It will say S-ON or S-OFF at the top of the bootloader.
tiny4579 said:
Also, the boot.img from the RUU broke adb for me. Maybe I have to do something special with it.
Click to expand...
Click to collapse
Check the build.prop for sdk level and make sure your sdk is updated to what is required by this rom. Your Android drivers may be out of date? I'm just talking to hear myself talk, but it sounds good enough to check our bases here.
evilstewie23 said:
So everybody who did this is unrooted now or what
Click to expand...
Click to collapse
Yes if you flash this as is you are now unrooted.
I got the nag on first boot but havent after that
tiny4579 said:
If you flashed the zip file in the OP then it will return you to stock recovery and you will be unrooted yes. I don't know about S-OFF though, I'm not sure if it reverts it. It will install the bootloader but I thought S-OFF was deeper in the system than that. Maybe someone who installed this can tell us. If you're still S-OFF you should be able to flash a custom recovery. It will say S-ON or S-OFF at the top of the bootloader.
Click to expand...
Click to collapse
K thanks guess ill just wait to get this when I unroot for the official ota as soon as it cones out and someone discovers another rooting method for 2.3
davwman said:
I got the nag on first boot but havent after that
Click to expand...
Click to collapse
I rebooted a few times and got it every time. Hmm... I wonder if it's just me. I think I've figured out how to stop it though. Testing to make sure.
EDIT: LOL! I may have flashed the original one I had. Let me double check.
I'm pretty sure I flashed the original instead of the new. I had them named to close to the same. Sorry.
wildstang83 said:
Check the build.prop for sdk level and make sure your sdk is updated to what is required by this rom. Your Android drivers may be out of date? I'm just talking to hear myself talk, but it sounds good enough to check our bases here.
Yes if you flash this as is you are now unrooted.
Click to expand...
Click to collapse
I actually compared the build.prop in this to the build.prop in the rooted zip released earlier this week using diff and they're identical. It was the first thing I did as soon as I extracted the system.img from the RUU.
When I reverted to the earlier boot.img from the rooted zip or the boot.img from the leak a few months ago I got adb back. I don't think it's a change to the kernel but I bet they modified the ramdisk to disable adb.
Yep, confirmed it was disabled in the ramdisk. If you want/need adb access don't use the boot.img from the RUU today.
tiny4579 said:
I actually compared the build.prop in this to the build.prop in the rooted zip released earlier this week using diff and they're identical. It was the first thing I did as soon as I extracted the system.img from the RUU.
When I reverted to the earlier boot.img from the rooted zip or the boot.img from the leak a few months ago I got adb back. I don't think it's a change to the kernel but I bet they modified the ramdisk to disable adb.
Yep, confirmed it was disabled in the ramdisk. If you want/need adb access don't use the boot.img from the RUU today.
Click to expand...
Click to collapse
+1 just tried it and ADB is disabled.
jermaine151 said:
+1 just tried it and ADB is disabled.
Click to expand...
Click to collapse
Do you know how to edit and repack boot.img files?
If so all you have to do is to unpack and change default.prop to this:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
Try attached. It should work with adb and I believe have module compatibility with my OTA modules zip.
davwman said:
I got the nag on first boot but havent after that
Click to expand...
Click to collapse
Okay, after enough reboots I can say the following about the location nag:
1) If "Standalone GPS" is enabled, you get the nag on every reboot. If you disable that, you don't.
2) If "Fast Boot" is enabled and you power down, then boot up, you won't get it. Reboot doesn't use "Fast Boot" so you get the nag after every reboot. I guess we'll have to hack it to get rid of that.
3) If "Fast Boot" is disabled and you power down, then boot up, you get nagged.
I still see no reason why they delayed the OTA since nothing seems to be changed.
tiny4579 said:
I actually compared the build.prop in this to the build.prop in the rooted zip released earlier this week using diff and they're identical. It was the first thing I did as soon as I extracted the system.img from the RUU.
When I reverted to the earlier boot.img from the rooted zip or the boot.img from the leak a few months ago I got adb back. I don't think it's a change to the kernel but I bet they modified the ramdisk to disable adb.
Yep, confirmed it was disabled in the ramdisk. If you want/need adb access don't use the boot.img from the RUU today.
Click to expand...
Click to collapse
jermaine151 said:
+1 just tried it and ADB is disabled.
Click to expand...
Click to collapse
Hmm, thats nice to know. I wonder if you guys remembered to go check the adb check box? If so and it isn't working and is disabled how hard it would be to enable it.
jermaine151 said:
Okay, after enough reboots I can say the following about the location nag:
1) If "Standalone GPS" is enabled, you get the nag on every reboot. If you disable that, you don't.
2) If "Fast Boot" is enabled and you power down, then boot up, you won't get it. Reboot doesn't use "Fast Boot" so you get the nag again. I guess we'll have to hack it to get rid of that.
I still see no reason why they delayed the OTA since nothing seems to be changed.
Click to expand...
Click to collapse
Maybe because of the wifi issue. Has anybody checked to see if we have wifi back now?
wildstang83 said:
Hmm, thats nice to know. I wonder if you guys remembered to go check the adb check box? If so and it isn't working and is disabled how hard it would be to enable it.
Click to expand...
Click to collapse
Yep, that's with USB debugging enabled.
tiny4579 said:
Do you know how to edit and repack boot.img files?
If so all you have to do is to unpack and change default.prop to this:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
Try attached. It should work with adb and I believe have module compatibility with my OTA modules zip.
Click to expand...
Click to collapse
Are you saying you got adb to be enabled?
Stock Rooted OTA 4.08.605.19 710RD Rom
Stock rooted ota 4.08.605.19 710RD rom. It is rooted, zip aligned, has busybox and comes in odexed or deodexed versions. Other than that it is untouched. Enjoy
[standard flashing disclaimer here]
Do a full wipe (boot, system, data, datadata, cache, android secure) except for sdcard and emmc, then flash like any other rom.
Stock rooted ota 4.08.605.19 rom may be able to be flashed over Stock rooted ota 4.08.605.15 rom, but is untested. If you flash over and have issues, do a full wipe and fresh install.
DOWNLOAD ODEXED - MD5 - Mirror
DOWNLOAD DEODEXED - MD5 - Mirror
_
2-13-2013 - Fixed TWRP flashing issues.
3-13-2013 - Fixed Superuser issues.
Sweet! Thank your sir.
Been waiting for this- One question I forget on the Dinc can you delete system apps on the phone?
I just activated my dinc again on pagepluscellular($12) I have to say for it's age the little guy holds up well. Looking forward to more roms and hopefully no more 2am reboot issue.
ToyTank said:
Sweet! Thank your sir.
Been waiting for this- One question I forget on the Dinc can you delete system apps on the phone?
I just activated my dinc again on pagepluscellular($12) I have to say for it's age the little guy holds up well. Looking forward to more roms and hopefully no more 2am reboot issue.
Click to expand...
Click to collapse
Just grab a root file explorer.
Sent from my Nexus 7 using Tapatalk 2
Osiris19 said:
Just grab a root file explorer.
Click to expand...
Click to collapse
Thank you I forgot dinc has that level of system access just with root. IIRC titanium bu can also.
ToyTank said:
Thank you I forgot dinc has that level of system access just with root. IIRC titanium bu can also.
Click to expand...
Click to collapse
I pulled out my old Incredible to see if I could breathe some new life into it and updated it to TWRP 2.4.1.0 and made a NANdroid backup of my old ROM. Went to go install it and get the Status 2 error, so I put in a newer update-binary. Not a big deal. I go to flash it again, and I get the Status 7 error, meaning I need to update to a newer version of my recovery. Not possible! So I re-flashed recovery and tried again. No dice. I can still restore my backup, so it's still alive right now. I'm curious to know if anyone else is experiencing this. Does anyone have any ideas?
IceDragon59 said:
I pulled out my old Incredible to see if I could breathe some new life into it and updated it to TWRP 2.4.1.0 and made a NANdroid backup of my old ROM. Went to go install it and get the Status 2 error, so I put in a newer update-binary. Not a big deal. I go to flash it again, and I get the Status 7 error, meaning I need to update to a newer version of my recovery. Not possible! So I re-flashed recovery and tried again. No dice. I can still restore my backup, so it's still alive right now. I'm curious to know if anyone else is experiencing this. Does anyone have any ideas?
Click to expand...
Click to collapse
Let me do some testing. I made it twrp compatible but never tested with twrp only cwm. I may have messed something up.
EDIT: FIXED!! Thanks for bringing it to my attention. I haven't gotten much feedback so far. Just redownload and flash.
cmlusco said:
Let me do some testing. I made it twrp compatible but never tested with twrp only cwm. I may have messed something up.
EDIT: FIXED!! Thanks for bringing it to my attention. I haven't gotten much feedback so far. Just redownload and flash.
Click to expand...
Click to collapse
Your zip works now. What was the problem?
Also, I've always been able to edit ROM zips and delete and add apks without any issue, but I can't now with this one. It keeps giving me the status 7 error about 80% through the install when all I do is delete some Verizon bloat from the zip file. Your zip is fine, it's just when I modify it that it's giving me a problem. I'm not using the MD5 file, so it shouldn't affect anything. Also, I don't think it should let me get 80% done with the install before it breaks only because of some deleted files.
IceDragon59 said:
Your zip works now. What was the problem?
Also, I've always been able to edit ROM zips and delete and add apks without any issue, but I can't now with this one. It keeps giving me the status 7 error about 80% through the install when all I do is delete some Verizon bloat from the zip file. Your zip is fine, it's just when I modify it that it's giving me a problem. I'm not using the MD5 file, so it shouldn't affect anything. Also, I don't think it should let me get 80% done with the install before it breaks only because of some deleted files.
Click to expand...
Click to collapse
Had to update the update-binary, and edit the mount commands in the updater-script.
Deleteing apps from /system/app in the rom zip should not affect the zip in any way. Are you just deleting them from within 7zip, or are you unziping, deleting, and then rezipping it?
Status 7 usually reffers to an error in the updater-script. Since it stoped about 80% thru, about 80% thru the updater-script is where the issue is.
cmlusco said:
Had to update the update-binary, and edit the mount commands in the updater-script.
Deleteing apps from /system/app in the rom zip should not affect the zip in any way. Are you just deleting them from within 7zip, or are you unziping, deleting, and then rezipping it?
Status 7 usually reffers to an error in the updater-script. Since it stoped about 80% thru, about 80% thru the updater-script is where the issue is.
Click to expand...
Click to collapse
Deleting them in WinZip. That's how I've always successfully done it before.
IceDragon59 said:
Deleting them in WinZip. That's how I've always successfully done it before.
Click to expand...
Click to collapse
I will try it and see if it does the same for me.
cmlusco said:
I will try it and see if it does the same for me.
Click to expand...
Click to collapse
Any luck?
IceDragon59 said:
Any luck?
Click to expand...
Click to collapse
Sorry for the long wait. Yes i can remove system apps from the zip using 7zip without issues. Make sure you also delete the apks odex file too if using the odexed rom.
cmlusco said:
Sorry for the long wait. Yes i can remove system apps from the zip using 7zip without issues. Make sure you also delete the apks odex file too if using the odexed rom.
Click to expand...
Click to collapse
Thanks so much =), honestly I am surprised updates are still being released. I really need to get to a Verizon store and snag the 4G version but I've been traveling a lot so my Blackberry has been getting a workout thanks to the international SIM support. Regardless I still use my Dinc for Google Auth (2-pass auth FTW!) and other activities everywhere (in network or not).
Fixed issues with superuser. For those who have already downloaded reflash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip thru recovery.
Trying to install. Unlocked CWM 5.0.2.0 Error 7. Bar goes full the over the full and fails.
leo72793 said:
Trying to install. Unlocked CWM 5.0.2.0 Error 7. Bar goes full the over the full and fails.
Click to expand...
Click to collapse
Did you do a full wipe or a flash over. Was there a line before the status 7, what did it say? Symlink failed, expecting # arguments, unexpected? I will have a look at it, the last test i did was with twrp.
cmlusco said:
Did you do a full wipe or a flash over. Was there a line before the status 7, what did it say? Symlink failed, expecting # arguments, unexpected? I will have a look at it, the last test i did was with twrp.
Click to expand...
Click to collapse
having pertition error :/
leo72793 said:
having pertition error :/
Click to expand...
Click to collapse
What kind of partition error?
I tested both cwm and twrp with both a flashover from stock rom 605.15 and a clean install and all worked just fine. Did you check the md5? Try redownloading.
Just got my INC back from my little sister after she upgraded and i'm excited to have this as my backup! Thanks for uploading this for everyone!
This will allow native hotspot and tethering. Thanks to everyone that helped with testing.
I am not responsible for anything that happens to your phone. You do this at your own risk.
Downloads:
Download MJA Deodexed: http://sdrv.ms/1dPK9wF
MD5: 97f54234b4fff191f7226b2093aa9ea7
Download MJA Odexed: http://sdrv.ms/1gdncEK
MD5: c613aa88ae9de96e1ae0daece3fd7a47
Download MF9 Deodexed: http://sdrv.ms/11AxqqH
MD5: 4af4b80d037f8525fa230a32eb5b8bea
Download MF9 Odexed: http://sdrv.ms/11Axxmc
MD5: b1f54ecf82719255ff39eb88d0095ccd
Download MDL Deodexed: http://sdrv.ms/1ehg9W2
MD5: c55400ec0af9f6974ea39bc6646c9a80
Download MDL Odexed: http://sdrv.ms/1ehgdoV
MD5: 56d1553e4d6a286ed46753fd47425560
Download MDC Deodexed: http://sdrv.ms/11AxJSq
MD5: d038cf4e49189751ca842692532240b7
Download MDC Odexed: http://sdrv.ms/11AxNBr
MD5: bb5cc5af7f599592a18f253508cbbf44
Mirrors:
Androidfilehost
Copy
Installation Instructions:
Make sure you install the right version for your phone. Go to settings| More| About device. Look at build number. Match that with the zip. If you are odexed flash odex and vice versa. If you aren't sure use a root file explorer and check in system/app. If you see .odex files you are odexed. If not you are deodexed.
Installing Custom Recovery
How To Use Odin
How To Use ADB To Install A Custom Recovery
Custom Recovery Method-This is the only installation method I recommend using
How To Install A Zip With CWM
How To Install A Zip With TWRP
The following installation options are not recommended. They can cause your phone to hang on boot
File Manager Method
How To Use A Root File Manager To Install A Mod
ADB Method
How To Use ADB To Install A Mod
Adding Hotspot Toggle
Below is a tutorial on how to add the WiFiHotspot button to the notification panel using the free sqlite Database Editor
Thanks to DJSmoove for his find and to wicked for his original work located here http://www.galaxys4forums.net/forum...d-add-wifi-toggle-your-verizon-galaxy-s4.html.
sqlite Database Editor Instructions
How To Add WiFiHotspot To The Notification Panel
Missing Hotspot Option In Settings
Those of you that have the Hotspot option missing in settings, use the instructions for adding the toggle. Only this time you are going to choose the secure table instead of system. Select * for everything or chameleon_tethereddata. If the value for chameleon_tethereddata is not 3 change it to 3. Reboot the phone and see if Hotspot is showing up now in settings.
If you can't edit the database on 4.3
If you can't edit the database on 4.3 download, install and run the TB Restore Fixer from playstore.
http://forum.xda-developers.com/attachment.php?attachmentid=2381599&d=1384013849
Please use this thread for all Hotspot related discussions. I will take anything notable, like confirmed issues, and put them here.
http://forum.xda-developers.com/showthread.php?t=2256980
Thanks
Sent from my SPH-L720 using xda premium
crawrj said:
This will allow native hotspot and tethering. Thanks to everyone that helped with testing.
We don't have a Deodexed Rom yet. That file is for when we do. Hopefully soon.
I am not responsible for anything that happens to your phone. You do this at your own risk.
Download MDC Deodexed: http://www.androidfilehost.com/?fid=22926241640220330
MD5: a7198c559a7347ac56c0192e9ad13ab9
Download MDC Odexed: http://www.androidfilehost.com/?fid=22926241640220329
MD5: ebd189283f3d984ef59c13648ce0b607
Mirrors:
Click to expand...
Click to collapse
Man I'm glad to have you on same phone as mine.
Now I don't have to wait for all the goodies you can make.
You were really missed in GS3.
I know as a dev, you know exactly what to do with these files & any prerequisites, but if you could give us slightly less informed on how to manage flashing these, that would be appreciated.
General instructions are in the OP now.
crawrj said:
General instructions are in the OP now.
Click to expand...
Click to collapse
Donkey Chains.
Got a report from tester is working under LTE.
Sent from my SPH-L900 using Tapatalk 2
crawrj said:
I don't have access to 4G so if someone could test that for me I would appreciate it. I have tested the Odexed version on my phone and one other phone.
I will post the smali changes later on.
Click to expand...
Click to collapse
4G works on odexed version. I installed via zip (not adb). Thank you very much.
Using WiFi Tether seems to break HotSpot until a reboot. AP is created but no internet passthrough.
Is there another method of flashing this? I seem to remember a way of getting into another mode other than recovery where you could flash something via cmd? Does that apply here? After reading the current state of some of the recoveries, I'm not ready to flash them yet.
I have put up an alternate install method in post 2 until we get a fully working CWM.
LAYGO said:
Is there another method of flashing this? I seem to remember a way of getting into another mode other than recovery where you could flash something via cmd? Does that apply here? After reading the current state of some of the recoveries, I'm not ready to flash them yet.
Click to expand...
Click to collapse
The CWM is fine for the purpose of flashing zipfiles like the modded HotSpot. It won't mess up your phone, and you can always flash the newer stable version when it comes out (or TWRP).
The 2nd post details the steps that you're probably referring to.
thx, it worked on my samsung galaxy s4
Link isnt working and there are no mirrors... anyone?
MedicWill said:
Link isnt working and there are no mirrors... anyone?
Click to expand...
Click to collapse
Links are fixed. Sorry about that.
This seems strange....
So I used ODIN to push the CWM recovery, rebooted into revocery then installed the hotspotmod.
Then rebooted.
I cant find the hotspot menu anywhere... an I missing something?
MedicWill said:
This seems strange....
So I used ODIN to push the CWM recovery, rebooted into revocery then installed the hotspotmod.
Then rebooted.
I cant find the hotspot menu anywhere... an I missing something?
Click to expand...
Click to collapse
that sounds familiar. the hotspot menu installs with the sprint apps once you activate.
Thank you,
Sorry for the rookie move, wont happen again!
Surprised by the lack of activity in this thread, as this is a huge bonus to have so soon, I guess I will drop in my input of my experience. First, of the two recoveries that are public, TWRP did not load properly for me (redraw issue as others have reported) so I used CWM. This recovery has a little issue not showing visual responses to every other navigation button press, but no big deal if you are aware of it. All functions work (backups, wipes, flashing of zips).
Since I originally rooted my device with the motochopper root method, I flashed CWM and installed the Odex zip. After a reboot, I had success with the hotspot, but my S4 seemed to run abnormally hot (hit 40C when normally well under 30C)...the warming of the device was independent of running the hotspot, as I only tested the hotspot for about 3 minutes. With no other assumption as to why, I decided that, due to the release of the Deodexed zip, I would move over to a clean install that version, as I intended to do eventually anyway.
After a full wipe and install of the Deodexed ROM zip, restoration of my Google accounts and apps via Titanium Backup, I installed the Deodexed hotspot hack and it works swimmingly as well.
All in all, both Odex and Deodex versions have been tested on my end with both the stock system after motochopper and the Deodexed zip. My random heating issue was possibly unrelated as I have not heard of anyone else with the issue...if someone has experienced this, please add it into the thread.
quick99si said:
The 2nd post details the steps that you're probably referring to.
Click to expand...
Click to collapse
2nd post wasn't there when I posted my question! I believe he responded with that post to my question.
Thanks to Calkulin for use of the install script. Thanks to Chainfire for SuperSU. Thanks to dsixda for the Kitchen. Thanks to shabbypenguin for the custom MDL kernel. Thanks to romracer for the Deodexed Wallet fix.
Flash this to get Deodexed/Odexed stock MDL with latest root (SuperSU), su binary and Busybox 1.20.2. These Do Not include a kernel or any other firmware.
All of the zips wipe cache and dalvik for you so no need to do that separately.
I am not responsible for anything that happens to your phone. You do this at your own risk.
As with everything I release, you are welcome to use this any way you need. Just remember where it came from:good:
There is a version for no data wipe and data wipe. Make sure you don't get them mixed up. The data wipe versions do not delete the /data/media folder.
The Rom has been updated with the new SuperSU and the fixed Deodexed Google Wallet. Removed the Nagfix and custom kernel links as they are no longer needed. Also no need to freeze seandroid or delete Knox.
Currently, the only way to install the modem is by using the OTA zip
Custom kernels will still give you a nag. A kernel dev will have to fix that. For now freeze seandroid.
Downloads:
Download Odexed No Data Wipe Zip
MD5: 5692e0c16caec65386ff7609cdaabc21
Download Odexed With Data Wipe Zip
MD5: bda6609aa9dce4a0679e08f782d34483
Download Deodexed No Data Wipe Zip
MD5: 8b0f097ccd111c674e803ef54370ee36
Download Deodexed With Data Wipe Zip
MD5: 375efa883c628faea23413dfa31111b1
Download Stock MDL Kernel
MD5: a236bae1683b08c715d19195da1eb45f
Download Stock MDL Recovery
MD5: f384764bcdbdf39b862edbbd0e871f44
Download Stock MDL Firmware No Boot Or Recovery *This gives you the updated firmware without replacing the kernel, recovery or the modem.
MD5: 3c92a10586d5aac222afb307eaa28d85
Download Stock MDL Firmware Complete Except For Modem *This gives you all of the stock firmware, including recovery and kernel, except the modem.
MD5: 816add37400ee77920ef97c8b74cf9da
Mirrors:
Skydrive
Copy
Installation Instructions:
If you don't want the Modem do the following.
Install custom recovery
Make a backup
Install stock MDL kernel or custom MDL kernel zip *Custom kernel will still give you a nag forcing you to freeze seandroid
Install stock MDL firmware no boot or recovery zip
Install the rom zip of your choice
If you want the Modem do the following.
Install custom recovery
Make a backup
Factory reset
Odin complete stock MDC from http://forum.xda-developers.com/showthread.php?t=2258107. If you are already on MDL you might have to do this twice, check About device to make sure everything says MDC
Copy the ota to your external sdcard http://forum.xda-developers.com/showthread.php?t=2269426 or just let the OTA install if you already have the notice
Boot into recovery and install update from external sdcard
Choose the OTA zip and complete the install
Let the system boot and load completely
You can skip all of the new setup unless you don't want to restore data
Check About device to make sure everything is updated to MDL, if not repeat steps 6 - 8
Install custom recovery
Install the rom zip of your choice
Restore data only
Installing Custom Recovery
How To Use Odin
How To Use ADB To Install A Custom Recovery
Custom Recovery Method
How To Install A Zip With CWM
How To Install A Zip With TWRP
Please use this thread for all discussions http://forum.xda-developers.com/showthread.php?p=41192376#post41192376
Thanks for this Crawj!!
Can you do a diff or a winmerge on the MDC/MDL and find out what's all changed?
Unknownforce said:
Can you do a diff or a winmerge on the MDC/MDL and find out what's all changed?
Click to expand...
Click to collapse
Yeah I plan on it. Doing yard work and family stuff at the moment.
Sent from my SPH-L720 using xda premium
crawrj said:
Yeah I plan on it. Doing yard work and family stuff at the moment.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Not a problem. I just downloaded it anyways too, just in case I need to rebuild based on this one.
Unknownforce said:
Not a problem. I just downloaded it anyways too, just in case I need to rebuild based on this one.
Click to expand...
Click to collapse
323 file changes. Diff attached.
For some reason I can't download the mdl updated rom from any of the mirrors
---------- Post added at 10:54 PM ---------- Previous post was at 10:45 PM ----------
It just stalls out
opz187 said:
For some reason I can't download the mdl updated rom from any of the mirrors
---------- Post added at 10:54 PM ---------- Previous post was at 10:45 PM ----------
It just stalls out
Click to expand...
Click to collapse
Still uploading. The main links will be first.
crawrj said:
Still uploading. The main links will be first.
Click to expand...
Click to collapse
My bad. Thanks dude
Do we have the official Tarball from this release?
Unknownforce said:
Do we have the official Tarball from this release?
Click to expand...
Click to collapse
Not that I have seen anywhere. But haven't been looking. Tracking down where the nag is coming from right now.
crawrj said:
Not that I have seen anywhere. But haven't been looking. Tracking down where the nag is coming from right now.
Click to expand...
Click to collapse
Well, even though the files themselves are different, it's only because they've just re-compiled the same things... I've decompiled a few and compared them to the old ones... they are identical... Even though their file sizes are different... They contain the same exact code...
I'm going to write a script to decompile everything and then run a full compare on the code... to find out what's actually changed...
Unknownforce said:
Well, even though the files themselves are different, it's only because they've just re-compiled the same things... I've decompiled a few and compared them to the old ones... they are identical... Even though their file sizes are different... They contain the same exact code...
I'm going to write a script to decompile everything and then run a full compare on the code... to find out what's actually changed...
Click to expand...
Click to collapse
The only two I have broken down are services and android.policy and both of those changed.
crawrj said:
The only two I have broken down are services and android.policy and both of those changed.
Click to expand...
Click to collapse
It makes sense that those have changed, I would expect the much of the framework to change, but more than half of the apk files have changed, but yet on the few I've checked, they have the same identical code.
Ok nag fix is posted in the OP. I have broken my wifi and sdcard. It is 1:22am and it has been a long day. I am going to bed and will pick this up again in the morning. If anyone knows how to decompile the two files in the fix so we can try and find the difference that would be great.
How did u fix the nag notification?
Sent from my SPH-L900 using xda premium
I applied the patch but I'm still getting nagged.
Sent from my SPH-L720 using Tapatalk 2
musclehead84 said:
How did u fix the nag notification?
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Long and tedious trial and error I knew something in the system was causing it because I could flash between MDC and MDL and it always came up on MDL. So first I found all of the file changes. I ruled out apk and framework. Then I began copying MDC over a few at a time until I could get it to go away. Then I kept going until I found which two were throwing it. I restored back and replaced those two again to make sure it went away.
Sent from my SPH-L720 using xda premium
this is it ...........thanks everybody for days and days of work...........http://forum.xda-developers.com/showpost.php?p=60415124&postcount=245
works with nce apk also.........everyone should be familar with ss same steps as above only from safestrap
ryan0720 said:
i just flashed this rom and is working great...any questions ask
Click to expand...
Click to collapse
http://forum.xda-developers.com/att-galaxy-s5/general/experimental-flashing-g900aoc4-5-0-t3080437
If you don't mind posting in the above thread with a link to the ROM thread and steps on how you installed that way it can be morely confirmed and put into the list.
ryan0720 said:
i just flashed this rom and is working great...any questions ask..I used the nce flasher apk. Takes u right to ss.. used stock slot wiped and installed twisted..the put the lollipop kernel back in throuhave Odin rebooted took 10 mind at boot up screen the bam. There it is so simple...thanks everyone who created these tools..
Click to expand...
Click to collapse
Dude that's awesome. It would be great if you could post the steps so that other people can do it too
Thanked you bro!
this is what i did.......
step 1......use nce flasher apk.......this takes you straight to safestrap.....
stwp 2... wipe everything but sd card on stock slot.......then install your rom....
step 3...... reboot into download mode and put the lollipop kernal back with odin......
step 4..... thats it......so far ive done alliance from verizon.....twisted from t mobile and still going........
just a tip....it takes a long time to boot so be patient.........
ryan0720 said:
this is what i did.......
step 1......use nce flasher apk.......this takes you straight to safestrap.....
stwp 2... wipe everything but sd card on stock slot.......then install your rom....
step 3...... reboot into download mode and put the lollipop kernal back with odin......
step 4..... thats it......so far ive done alliance from verizon.....twisted from t mobile and still going........
just a tip....it takes a long time to boot so be patient.........
Click to expand...
Click to collapse
How did you put the kernel back in with Odin?
put the OC4_stock kernal in ap slot in odin
Nyxerosoir said:
http://forum.xda-developers.com/att-galaxy-s5/general/experimental-flashing-g900aoc4-5-0-t3080437
If you don't mind posting in the above thread with a link to the ROM thread and steps on how you installed that way it can be morely confirmed and put into the list.
Click to expand...
Click to collapse
Just use Muniz_ri method then install the NCE flasher apk. Then it'll take you to SS, flash your new ROM or mods or whatever then just flash the OC4 kernel and you're back in the game.
http://forum.xda-developers.com/showthread.php?t=3087450
From my Allianced S5!
K-alz said:
Just use Muniz_ri method then install the NCE flasher apk. Then it'll take you to SS, flash your new ROM or mods or whatever then just flash the OC4 kernel and you're back in the game.
http://forum.xda-developers.com/showthread.php?t=3087450
From my Allianced S5!
Click to expand...
Click to collapse
Couldn't you just unzip the Twisted Lollipop ROM .zip file and replace the boot.img that they have with the stock OC4 one, re-zip it up and flash via FF?
Seems a lot simpler...
That's what I did @dorqus and flashed the kernel zip to be safe but after a couple fails found out it will not work unless your lollipop already had to Odin back twice lol but its running good so far 1st boot super long phone got to got for me rebooted and it updated 26 apps and started up fine
pyro43284 said:
That's what I did @dorqus and flashed the kernel zip to be safe but after a couple fails found out it will not work unless your lollipop already had to Odin back twice lol but its running good so far 1st boot super long phone got to got for me rebooted and it updated 26 apps and started up fine
Click to expand...
Click to collapse
So just to be sure, all i need to do is replace the boot.img to the oc4 one and rezip and i should be able to flash it. I'm on 5.0 using muniz method. I'm running alliance 7.1 right now but have been wanting Twi5ted for a while now.
dirtydodge said:
So just to be sure, all i need to do is replace the boot.img to the oc4 one and rezip and i should be able to flash it. I'm on 5.0 using muniz method. I'm running alliance 7.1 right now but have been wanting Twi5ted for a while now.
Click to expand...
Click to collapse
Yep if you want to be safe chase it with the kernel zip too but kernel sway should be sufficient... I'll do a test real quick with mine with just the swapped kernel no extra zip I'll be back with results for ya shortly
dorqus said:
Couldn't you just unzip the Twisted Lollipop ROM .zip file and replace the boot.img that they have with the stock OC4 one, re-zip it up and flash via FF?
Seems a lot simpler...
Click to expand...
Click to collapse
A lot simpler than just two flashes? First one when you open the app and it flashes the NCE for you and takes you to safestrap. And the second one is when you're done flashing whatever you want just flash the OC4 kernel and boot back up to your phone.
I've tried FF and it was more complicated for me. Also, not everyone knows how to replace the boot.img like you did. I guarantee you that a lot of don't even know what it is. LOL
K-alz said:
A lot simpler than just two flashes? First one when you open the app and it flashes the NCE for you and takes you to safestrap. And the second one is when you're done flashing whatever you want just flash the OC4 kernel and boot back up to your phone.
I've tried FF and it was more complicated for me. Also, not everyone knows how to replace the boot.img like you did. I guarantee you that a lot of don't even know what it is. LOL
Click to expand...
Click to collapse
Easy now. Lol. I'm still learning myself. I just extracted the OA1 boot loader that muniz uploaded for the "5.0 update and keep root" copied all that was in that folder and placed in the Twi5ted folder and removed the Twi5ted "boit.img" is that not what should be done? I haven't flashed yet.
pyro43284 said:
Yep if you want to be safe chase it with the kernel zip too but kernel sway should be sufficient... I'll do a test real quick with mine with just the swapped kernel no extra zip I'll be back with results for ya shortly
Click to expand...
Click to collapse
yea jus boot img swap is good just re flashed mine from full wipe and worked perfectly, i was also unable to get nce to work without safestrap recovery installed this seems to be the easiest way for me atleast lol
ryan0720 said:
i just flashed this rom and is working great...any questions ask..I used the nce flasher apk. Takes u right to ss.. used stock slot wiped and installed twisted..the put the lollipop kernel back in throuhave Odin rebooted took 10 mind at boot up screen the bam. There it is so simple...thanks everyone who created these tools..
Click to expand...
Click to collapse
running alliance rom.......
Downloaded twi5ted v4, unzipped it and extracted the boot.img from the G900A_OC4_Stock_Rooted_Firmware.tar.md5 in the g900a update to 5.0 thread, and deleted the one in the rom zip and replaced it, and rezipped. Upon trying to load it into flashfire I got a crash as someone as the verification got to 100, I tried 4 times, all of them with the same java.lang.outofmemory error, which was confusing cause I have plenty of memory free. I'm giving it another shot, if it works I'll come back here and give a link to the zip for anyone else who wants to do it with some steps that worked for me.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Rakuu said:
Downloaded twi5ted v4, unzipped it and extracted the boot.img from the G900A_OC4_Stock_Rooted_Firmware.tar.md5 in the g900a update to 5.0 thread, and deleted the one in the rom zip and replaced it, and rezipped. Upon trying to load it into flashfire I got a crash as someone as the verification got to 100, I tried 4 times, all of them with the same java.lang.outofmemory error, which was confusing cause I have plenty of memory free. I'm giving it another shot, if it works I'll come back here and give a link to the zip for anyone else who wants to do it with some steps that worked for me.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
That would be great.
Rakuu said:
Downloaded twi5ted v4, unzipped it and extracted the boot.img from the G900A_OC4_Stock_Rooted_Firmware.tar.md5 in the g900a update to 5.0 thread, and deleted the one in the rom zip and replaced it, and rezipped. Upon trying to load it into flashfire I got a crash as someone as the verification got to 100, I tried 4 times, all of them with the same java.lang.outofmemory error, which was confusing cause I have plenty of memory free. I'm giving it another shot, if it works I'll come back here and give a link to the zip for anyone else who wants to do it with some steps that worked for me.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
I'm back after attempt number 5, still no dice, it gets to 100% crashes, I'll go ahead and post the zip anyway in case anyone else wants to give it a shot. The exact process I did, was download the v4 zip from here http://forum.xda-developers.com/showthread.php?t=3037766 then extract it with zarchiver, replaced the boot.img, then zipped it again with zarchiver, and the file size went from 1.25 gb to 1.26 gb. It seems strange this one fails to load but the stock lollipop tar which is double this one's size loads much faster and perfectly fine. If you want to give it a go, download the zip, reboot your phone (to clear out as much memory as possible) and then open flash fire and add the zip as a firmware package, as it won't even show up if you click "flash zip or ota", for me at least. As usual, I'm not responsible if you brick, and can't provide any assurance you won't since I haven't even been able to flash it in the first place.
Sent from my SAMSUNG-SM-G900A using Tapatalk
ryan0720 said:
running alliance rom.......
Click to expand...
Click to collapse
where did you get the KitKat Kernel tar from to flash with Odin? Odin only accepts .tar files and the only KitKat kernel i've found was from @K-alz and that's a flashable zip.
skyrocketeer said:
where did you get the KitKat Kernel tar from to flash with Odin? Odin only accepts .tar files and the only KitKat kernel i've found was from @K-alz and that's a flashable zip.
Click to expand...
Click to collapse
When you use nice apk it automatically takes your kernel back down to kitkat...so I assume...after your in as and install your ROM..you use oc4 kernel through Odin...am I getting your question right?