I just got my phone. Downloaded the motochopper.zip which is available for the other variants of S4, tried it, and no work.
I pushed 'busybox', 'pwn', and 'su' manually, did the chmod. Then I 'adb shell', and ran ./pwn . This is what you get:
[+] This may take a few minutes.
[-] Failure
Bummer.
blulite said:
I just got my phone. Downloaded the motochopper.zip which is available for the other variants of S4, tried it, and no work.
I pushed 'busybox', 'pwn', and 'su' manually, did the chmod. Then I 'adb shell', and ran ./pwn . This is what you get:
[+] This may take a few minutes.
[-] Failure
Bummer.
Click to expand...
Click to collapse
yes we know.. develper is working on it now.
slackwaresupport said:
yes we know.. develper is working on it now.
Click to expand...
Click to collapse
It's probably not going to. Based on version this kernel very likely contains a root block.
Meaning even if you do get su on it will be ignored.
Did kernel source drop yet?
A kernel built with those flags off (at the bottom of the common defconfig) will allow root.
I can put out an earlier kernel that shouldn't have that block also.
If not Sprint has the defconfigs and we probably can build an equivalent for you guys.
(But I assume both may need that unlocked bootloader to play)
Q: In previous models - If you get a full restore - bootloader, modem, etc. and wipes data - will that take via Odin?
If so I might have a quicker solution to at least get root.
garwynn said:
Q: In previous models - If you get a full restore - bootloader, modem, etc. and wipes data - will that take via Odin?
If so I might have a quicker solution to at least get root.
Click to expand...
Click to collapse
I recently had to do a full restore to my Samsung Galaxy S III using Odin. With the stock ROM. I used Odin to do it. Does that answer your question? There are also rooted (but otherwise stock ROMs) that you can install using Odin on the SGS3.
garwynn said:
It's probably not going to. Based on version this kernel very likely contains a root block.
Meaning even if you do get su on it will be ignored.
Did kernel source drop yet?
A kernel built with those flags off (at the bottom of the common defconfig) will allow root.
I can put out an earlier kernel that shouldn't have that block also.
If not Sprint has the defconfigs and we probably can build an equivalent for you guys.
(But I assume both may need that unlocked bootloader to play)
Q: In previous models - If you get a full restore - bootloader, modem, etc. and wipes data - will that take via Odin?
If so I might have a quicker solution to at least get root.
Click to expand...
Click to collapse
Are you making it up or is this really true? Cause that would suck.
He's correct, here is an explanation.
http://www.androidpolice.com/2013/0...os-galaxy-s4-update-but-this-is-a-good-thing/
Sent from my SCH-I545 using xda app-developers app
Patience, we'll get root access through a pre-rooted stock formware flashable in Odin like we have with prior Samsung devices. Dan Rosenberg
tweeted this morning he had successfuly rooted and booted a custom recovery on a VZW S4.
I posted a kernel on the MDK restore thread that shouldn't have the root block. You'll still need to flash it... which I thought still requires the unlocked bootloader.
Sent from my SPH-L900 using Tapatalk 2
garwynn said:
I posted a kernel on the MDK restore thread that shouldn't have the root block. You'll still need to flash it... which I thought still requires the unlocked bootloader.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=41702577
Sent from my SPH-L720 using Tapatalk 2
sextape said:
http://forum.xda-developers.com/showthread.php?p=41702577
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Successfully flashed the kernel and rooted my VZW S4 this morning. Thanks for this!:good:
Happy to have been wrong about the bootloader requirement to get rooted. Let the party begin!!!
Sent from my SPH-L900 using Tapatalk 2
Related
Hey guys,
Do any of you know how I can place my rom, and push it as an OTA Update like Sprint. What files do I need to accomplish this? I have already looked at OTA update center and its great, I would just like to push them without my people having to root. I have a server set up, just don't know how to have everything point to the right place. I'm familiar with the boot_delta.bin and android_delta.bin files along with others needed for an OTA Update. Also, i know you have to edit things in the build.prop as well. I hope someone can point me in the right direction. Thanks
I want it too, I think it's a great idea.
You wan't to add it to your custom rom which is not even rooted? WHAT???
Sent from my GT-S7500 using xda premium
lokeshsaini94 said:
You wan't to add it to your custom rom which is not even rooted? WHAT???
Sent from my GT-S7500 using xda premium
Click to expand...
Click to collapse
My custom rom is rooted, but I am wanting people who get the device from a specific company to not have to go through the rooting process and just push my Rom OTA to their device using a server just like Sprint does. Hope this makes some sense, thanks
jd3107 said:
My custom rom is rooted, but I am wanting people who get the device from a specific company to not have to go through the rooting process and just push my Rom OTA to their device using a server just like Sprint does. Hope this makes some sense, thanks
Click to expand...
Click to collapse
Not possible....the way sprint or other carriers are able to do it is because they pass the security/verification checks...unless you can figure out an exploit/hack its not possible
Basically you would need to figure out how to first root the phone, and then get a custom recovery...there have been some apps in the past that can achieve root...but most phones have those patched by now...so it definitely is possible, just not probable
Sent from my SGH-I997 using Tapatalk 2
You can take a look at goo.im the users will still have to have a custom recovery to flash the ROM
Sent from my LG-P990
mg2195 said:
Not possible....the way sprint or other carriers are able to do it is because they pass the security/verification checks...unless you can figure out an exploit/hack its not possible
Basically you would need to figure out how to first root the phone, and then get a custom recovery...there have been some apps in the past that can achieve root...but most phones have those patched by now...so it definitely is possible, just not probable
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, by any chance do you think this will work?
http://www.igottadroid.com/ModMarke...746F6D20726F6D73207B44455653204F4E4C597D.html
C0D3N1N3R said:
You can take a look at goo.im the users will still have to have a custom recovery to flash the ROM
Sent from my LG-P990
Click to expand...
Click to collapse
Thanks, I already have a custom recovery I have made, I just wanted to try to push my custom roms with an OTA without having people need root or a recovery. Just like Sprint and Verizon. Thanks
jd3107 said:
Thanks, I already have a custom recovery I have made, I just wanted to try to push my custom roms with an OTA without having people need root or a recovery. Just like Sprint and Verizon. Thanks
Click to expand...
Click to collapse
You can't bro, get over it. THEY need too root, THEY need to flash it. Period.
lithid-cm said:
You can't bro, get over it. THEY need too root, THEY need to flash it. Period.
Click to expand...
Click to collapse
Thanks man, I appreciate your answer. I was hoping their was a way but I guess not.
jd3107 said:
Thanks man, I appreciate your answer. I was hoping their was a way but I guess not.
Click to expand...
Click to collapse
Well, with a custom recovery it IS possible without root.
What you also could do is make an app who's exploiting a bug in the Android system to gain root. Do this with the permission of your users. If you execute the exploit, you have a root prompt, you could fetch the device name, and download a suitable recovery for it. Let the user confirm this, and download it.
I recommend to wrap it in a nice UI, like this.
- Get root
- Fetch recovery (menu to choose device)
- Flash recovery
From there, you CAN execute your OTA updater app. Note this only works on devices where all partitions are writable with root. For example my phone's (i9300) recovery partition is writable with root.
Hope this helps,
CodeOMG
CodeOMG said:
Well, with a custom recovery it IS possible without root.
What you also could do is make an app who's exploiting a bug in the Android system to gain root. Do this with the permission of your users. If you execute the exploit, you have a root prompt, you could fetch the device name, and download a suitable recovery for it. Let the user confirm this, and download it.
I recommend to wrap it in a nice UI, like this.
- Get root
- Fetch recovery (menu to choose device)
- Flash recovery
From there, you CAN execute your OTA updater app. Note this only works on devices where all partitions are writable with root. For example my phone's (i9300) recovery partition is writable with root.
Hope this helps,
CodeOMG
Click to expand...
Click to collapse
Very cool, you come up with that idea all by yourself? Reguardless, there is user intervention required. Whether it be for the custom recovery, bootloader unlock, root. Nothing, when it comes to this comes that easy. ****, even the Nexus phones you need to reboot into the bootloader, no app from the device can do it all sorry.
Most of us are messing up our sboot or bungling up other portions of the ROM making CASUAL freak out and fail on you during ODIN flashing. Do the following first and I guarantee casual will work without incident.
Download this http://www.mediafire.com/?z2bd5u4esh73mbv
Put the update.zip into your adb folder commonly known as your platform-tools folder.
Boot your phone into stock recovery
Choose adb side load
Then type "adb sideload update.zip" with no quotes.
This will update you to the latest VRALL release. Once this updates it will fix your corrupt sboot file and you are ready for CASUAL boot loader unlock and root.
Sent from my SCH-I605 using xda premium
You do realize most the time is the ROM messed up? That's why the alternate restore that doesn't write sboot fixes it. However, this is a cool alternate restore method never really thought of. Have you done this when on the new ota yet, I'm wondering if it accepts sboot then?
Sent from the dark on a Note 2
kintwofan said:
You do realize most the time is the ROM messed up? That's why the alternate restore that doesn't write sboot fixes it. However, this is a cool alternate restore method never really thought of. Have you done this when on the new ota yet, I'm wondering if it accepts sboot then?
Sent from the dark on a Note 2
Click to expand...
Click to collapse
Yes I have done on new OTA... works great.
das7982 said:
Yes I have done on new OTA... works great.
Click to expand...
Click to collapse
Good to know.
Sent from the dark on a Note 2
Just a minor addition, I had a second device, plugged into my computer when trying to run casual and it would fail saying unsupported kernel detected. Just throwing this out there.
Sent from my SCH-I605 using Tapatalk 2
@Chainfire has released his CF-Auto-Root for the SM-G900T (T-Mobile US) Galaxy S 5.
I take no credit whatsoever for this, just posting a link to his main thread for all to see.
Please go and thank Chainfire!
With this root accomplished, we can confirm that the T-Mobile bootloader is UNLOCKED.
ROMS/Kernels/Recovery will soon follow from our awesome devs here on XDA.
Link to CF-Auto-Root Main Thread(Multi-variants)
THIS WILL TRIP KNOX COUNTER TO 0x1
ODIN Instructions - Copied from Main CF thread
Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
Click to expand...
Click to collapse
Download links taken from main thread:
SM-G900T (T-Mobile US): CF-Auto-Root-kltetmo-kltetmo-smg900t.zip
Other models
CF-Auto-Root is not yet available for all models - one stock firmwares for these models become available, let me know, and I'll make the corresponding CF-Auto-Roots.
Click to expand...
Click to collapse
Good stuff, downloaded the zip, just waiting for my device to get here....we have to run the update the Kies first, right? Also, any word about CWM or TWRP? They've already made recoveries for the international versions.
stevew84 said:
Good stuff, downloaded the zip, just waiting for my device to get here....we have to run the update the Kies first, right? Also, any word about CWM or TWRP? They've already made recoveries for the international versions.
Click to expand...
Click to collapse
You can run the auto-root on both the updated version from kies, or straight outta the box.
I am trying to get in touch with the developers about TWRP and CWM, but I am sure they are busy trying to get all variants working.
I wouldn't Odin the international TWRP or CWM though. I would wait for a version for us.
idtheftvictim said:
You can run the auto-root on both the updated version from kies, or straight outta the box.
I am trying to get in touch with the developers about TWRP and CWM, but I am sure they are busy trying to get all variants working.
I wouldn't Odin the international TWRP or CWM though. I would wait for a version for us.
Click to expand...
Click to collapse
For sure, I don't want to brick the damn thing. Luckily I've been here before!
ill wait for a none trip counter version or triangle away to come out. should be to long.
khshapiro said:
ill wait for a none trip counter version or triangle away to come out. should be to long.
Click to expand...
Click to collapse
I wouldn't count on it. at least the Triangle away...Knox still hasn't been figured out for previous devices on how to reset it, so I wouldn't count on it for this device. As for getting root without tripping knox, Maybe kingo will update, or root-de-la-vega....who knows at this point.
khshapiro said:
ill wait for a none trip counter version or triangle away to come out. should be to long.
Click to expand...
Click to collapse
There basically won't be a way of resetting Knox.
Because of it being more a hardware flag, once it is tripped it is not reversible.
There might eventually be a way to do it without tripping it, but I wouldn't expect that for a while.
Got my S5 and ran the CFAuto worked like a champ... Rooted in 30 seconds.. Yes it tripped Knox but I really don't care.
Sent from my SM-G900T using XDA Premium 4 mobile app
Come ooonnnnn customer recoveries!
Edit: This is such great news, I'll be buying this version and unlock it to use it on T-Mobile.
Sent from my Nexus 7 using Tapatalk
tankmurdock said:
Got my S5 and ran the CFAuto worked like a champ... Rooted in 30 seconds.. Yes it tripped Knox but I really don't care.
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Now just to see if WiFi tether for root users works.
He he
And Y_E_S tethering works like a chiz-amp!
Sent from my SM-G900T using XDA Premium 4 mobile app
Since we have root, does that mean 100% that we can flash recoveries and ROMS? Both TW and AOSP?
Worked perfectly.
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
stevew84 said:
Since we have root, does that mean 100% that we can flash recoveries and ROMS? Both TW and AOSP?
Click to expand...
Click to collapse
Yes, though root has nothing to do with this. The bootloader is unlocked, which is why root was obtainable via Chainfire's custom recovery. We have no restrictions on flashing custom ROMs/kernels/recoveries/etc.
I may start working on a custom TW kernel myself once Samsung uploads the source...
zaventh said:
Worked perfectly.
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
Yes, though root has nothing to do with this. The bootloader is unlocked, which is why root was obtainable via Chainfire's custom recovery. We have no restrictions on flashing custom ROMs/kernels/recoveries/etc.
I may start working on a custom TW kernel myself once Samsung uploads the source...
Click to expand...
Click to collapse
Wait, CF custom recovery has nothing to do with root? I thought that was the point of CF "autoroot", am I missing something?
TheArtiszan said:
Now just to see if WiFi tether for root users works.
He he
Click to expand...
Click to collapse
Do u have a link to this?
Sent from my SM-G900T using XDA Premium 4 mobile app
Tmo warranty
Hi,
I'm debating if I should upgrade to SGS5, now that we can root the phone.
Does anyone knows for sure that a tripped Knox means no warranty with T-mo? I'm under the Jump plan and the idea is that I will be able to have warranty on the device if something happens to it (and I do have some apps that must use root...)
Thanks,
Gil.
zaventh said:
Yes, though root has nothing to do with this. The bootloader is unlocked, which is why root was obtainable via Chainfire's custom recovery. We have no restrictions on flashing custom ROMs/kernels/recoveries/etc.
Click to expand...
Click to collapse
Are we 100% certain that the bootloader is indeed unlocked. I know that chainfire stated this (although he currently doesnt own the s5).
I just came from HTC, and it states when you boot whether the bootloader is locked or unlocked. Im assuming there is no simple way of knowing whether the bootloader is locked or unlocked like the HTC devices
Phew glad to see the bootloader is not locked. Gonna root as soon as I get my replacement S5. Can't wait for the custom ROMs
Sent from my SM-G900T using XDA Premium 4 mobile app
el7145 said:
Are we 100% certain that the bootloader is indeed unlocked. I know that chainfire stated this (although he currently doesnt own the s5).
I just came from HTC, and it states when you boot whether the bootloader is locked or unlocked. Im assuming there is no simple way of knowing whether the bootloader is locked or unlocked like the HTC devices
Click to expand...
Click to collapse
There are reliable sources saying yes it is unlocked and there are reliable sources saying no it still hasn't been confirmed until someone successfully flashes a custom rom/kernel/recovery.
The consensus around here seems to be that it is unlocked but its just people repeating the words of the original few that debated it. And of course since we all want it to be unlocked, it is easier to believe that it is.
I personally don't want to jump to conclusion so i want there to be more discussion on the matter. Therefore i requested the "boot loader un/locked" thread to be reopened in Q/A.
i want to walk down to the store and buy one right now but until its confirmed im waiting it out. $650 bet!
This CWM/TWRP flashable zip is 4.4.4 from my dump of 212.44.26.ghost_att.ATT.en.US (ATT xt1058).
The stock ATT 4.4.4 kernel is within the zip and must be flashed manually.
Safestrap and root are 'baked in', but the rom is otherwise stock.
I am using the modem from 4.4.2 without issue, and I plan to create a new zip when the official sbf is available.
The instructions below are mostly for rooted, locked ATT phones using safestrap.
This zip does not alter your bootloader.
I was able to upgrade from 4.4.2 without a wipe/factory reset.
This rom installs Safestrap. (I welcome exact instructions on removing this from the rom.)
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
Instructions for ATT locked phones:
If you can still get permanent root (pre 4.4.2 bootloader), then you can use safestrap to install this zip of ATT 4.4.4 and get root again.
Prerequisite:
Rootable Moto x (not temporary root)
Have fastboot (motorola version for this phone) and PC drivers installed and working
BACKUP ANYTHING YOU DON'T WANT TO LOSE.
Instructions:
root (thanks jcase)
install safestrap (thanks Hashcode and Team Win)
Make a nandroid and copy it off the phone!?
download zip to sdcard (motox-444-212.44.26.ghost_att-from-dump-ss.zip, link below)
extract boot.img to the fastboot directory of your PC
enter safestrap recovery (twrp) and activate the stock-slot
twrp: flash rom (motox-444-212.44.26.ghost_att-from-dump-ss.zip) to the stock-slot
twrp: reboot to bootloader (home -> reboot -> bootloader)
on pc: execute fastboot commands (below) then power on normally.
install supersu (thanks chainfire) from play store
Fastboot command to flash the kernel:
Code:
fastboot flash boot boot.img
Fastboot command for locked phones not using MotoWPNoMo with pre 4.4 bootloaders:
Code:
fastboot flash recovery boot.img
Thanks to touchpro247 for making the raw OTA available. Also thanks to iKrYpToNiTe for his safestrap selinux metadata code.
Download:
motox-444-212.44.26.ghost_att-from-dump-ss.zip: http://www.androidfilehost.com/?fid=23622183712458373
anyone try this one yet?
Installed this on my DE. Works perfectly. I actually have better reception. I'm on ATT btw.
Thanks a lot!
Sent from my XT1058 using XDA Free mobile app
bahhh now all I need is one from VZW
Thanks! This seems to work fine for my unlocked Brazil XT1058 using TWRP. The only thing is now that whenever I start the phone there's a 2-3 second screen saying Safestrap disabled (I've never installed Safestrap). Is there a logo flash that will remove this?
would this work on 1053 on att or nah
Sent from my XT1053 using XDA Free mobile app
goonigoogoo said:
Thanks! This seems to work fine for my unlocked Brazil XT1058 using TWRP. The only thing is now that whenever I start the phone there's a 2-3 second screen saying Safestrap disabled (I've never installed Safestrap). Is there a logo flash that will remove this?
Click to expand...
Click to collapse
Because this came from my /system dump, it has safestrap there. I'm not sure of the easiest way to perfectly remove it, and I welcome input on the issue.
I'll update the op.
hey guys i have a 1053 rooted i am a noob sorry how can i get this to work for me
g4ess said:
would this work on 1053 on att or nah
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Yep. Works well. I now have visual voicemail.
Sent from my XT1058 using XDA Free mobile app
can't get it to install how to u manually flash kernel
Sent from my XT1053 using XDA Free mobile app
Weapondrift said:
bahhh now all I need is one from VZW
Click to expand...
Click to collapse
This one doesn't work? http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
Has anyone seen if Faux's kernel will work? I'm waiting for my phone to charge before I flash. I'll report whether or not if no one else does.
Edit: So far, it's working great on my 1053 DE with Faux's latest kernel on AT&T.
nice
Thanks Ctrl-Freak for this. I appreciate you putting it together. I just upgraded from 4.4.2 to 4.4.4.
C:\>adb shell getprop ro.boot.write_protect
0
Click to expand...
Click to collapse
Sorry if this question is aggravating but if I flash this on my rooted XT1053 will it wipe my internal? Just trying to be sure, never flashed anything carrier specific. I flash and reboot right? Or do I also need the kernel? I read the OP but I'm wondering if I do all of that and or need safestrap.
Edit: I think I got it.
I did this update as instructed on my AT&T, locked bootloader XT1058 but I skipped the fastboot commands entirely. Installed under stock slot with root from 4.2 android and Safestrap. Went through like a charm. Still have root, had to reboot to write protect off mode and install Xposed again, but otherwise everything is as it was...except that I'm on 4.4.4 now! I didn't even lose my original bootloader (the globe one that looks so sexy) that I had to manually install after their damn PlayStore update replaced. Not sure if this will stick for others that haven't done that already.Thanks!!!
---------- Post added at 02:17 PM ---------- Previous post was at 02:14 PM ----------
Apollo_316 said:
I did this update as instructed on my AT&T, locked bootloader XT1058 but I skipped the fastboot commands entirely. Installed under stock slot with root from 4.2 android and Safestrap. Went through like a charm. Still have root, had to reboot to write protect off mode and install Xposed again, but otherwise everything is as it was...except that I'm on 4.4.4 now! I didn't even lose my original bootloader (the globe one that looks so sexy) that I had to manually install after their damn PlayStore update replaced. Not sure if this will stick for others that haven't done that already.Thanks!!!
Click to expand...
Click to collapse
I should clarify. I had the old root from 4.2 that was on the phone when I purchased it. Updating to 4.4.4 was coming from 4.4.2 previously.
Apollo_316 said:
I did this update as instructed on my AT&T, locked bootloader XT1058 but I skipped the fastboot commands entirely.
...
Click to expand...
Click to collapse
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Ctrl-Freak said:
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Click to expand...
Click to collapse
I'll have to agree with you on the 4.4.4 kernal and the android is bug. I was using Faux's 4.4.3 kernal with this ROM and still had the os bug. Now, it's all gone after I manually flashed the new kernel.
iSecks said:
This one doesn't work? http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
Click to expand...
Click to collapse
nope. That didn't do anything
Ctrl-Freak said:
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Click to expand...
Click to collapse
beefgoat said:
I'll have to agree with you on the 4.4.4 kernal and the android is bug. I was using Faux's 4.4.3 kernal with this ROM and still had the os bug. Now, it's all gone after I manually flashed the new kernel.
Click to expand...
Click to collapse
Ctrl-Freak said:
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Click to expand...
Click to collapse
You were quite right. I'm having battery issues (now) and my WiFi/Bluetooth won't turn on at all, even in safe mode. Was getting 52 hours consistently on battery, now I'm down to 36 hours tops! Phone started being 'awake' while the screen was off. I went back and flashed the boot, all good now. I'll report back on the battery issue. Thank you guys for setting me strait! :highfive:
Possible anyone knows how to disable the annoying OTA updates permanently? Remedied for now, being on 4.4.4, but I was trying to avoid 4.4.4 for now and the update notification that I couldn't kill, greenify, stop on boot, etc., is what drove me to this post. I'd love to turn these off and upgrade at my leisure in the future.
This is what I've been waiting for. Android OS is where it's supposed to be. Thank you Ctrl Freak for the upload.
OK, the pic didn't upload.
**Required** FlashFire - Play BETA - PREVIEW
Downloads:
- I545_OF1_Stock_Rooted_ROM
- I545_OF1_Stock_Rooted_Deodexed_ROM
Instructions:
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main Uncheck all options under "EverRoot" and use default "Reboot" setting.
6. Last, press the lightning bolt then "Ok" to begin the flash .
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the Verizon splash screen for about 2 - 3 minutes (10 - 15 mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Optional:
- I545_OF1_TetherAddOn.zip (Flash using FlashFire's "Flash .Zip or OTA" option).
Known Issues:
- None!
Notes:
1. The ROM's will update your Modem, Non-hlos, Kernel, Recovery, and System to OF1 but no bootloader will be flashed.
2. No need to wipe prior to flashing! The ROM's will automatically perform a factory data reset.
3. If you do not already have root access (or to unbrick) Odin flash the I545_Downgrade_tC1.tar (untested on devices that have taken the OF1 ota update), root using Kingroot Desktop version, use Super-Sume Pro to replace Kingroot files with SuperSu, then follow the above instructions.
4. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Credits:
@bangdosa - for capturing and sharing the OF1 ota.zip
Forgive the likely stupid question, but if I want to flash back to stock for some reason after doing this (I'm on NC5), I can just Odin back, yes?
Thanks for the mention!! wow so quick!! less than 3hrs since I uploaded the update. How do you make updated rom file so quickly? And is there a way to update without doing a full wipe?
Just waiting for deodexed thanks Muniz
Sent from my SCH-I545 using XDA Free mobile app
EdrickMG said:
Just waiting for deodexed thanks Muniz
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Deodexed version added to OP.
Can this be installed on a rooted non MDK (OC1) bootloader phone?(
Loaded this and Bluetooth isn't working. Do I need to do something to fix it. Worked before loading this.
bangdosa said:
Thanks for the mention!! wow so quick!! less than 3hrs since I uploaded the update. How do you make updated rom file so quickly? And is there a way to update without doing a full wipe?
Click to expand...
Click to collapse
doing a wipe will generally fix most bugs encountered by people who take OTAs. all those normals you see being like "oh my phone got an update and its sooooo slow now omg I'm gonna get an iphone"
they're just doing it wrong.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 10:55 AM ---------- Previous post was at 10:52 AM ----------
phil0sophic said:
Can this be installed on a rooted non MDK (OC1) bootloader phone?(
Click to expand...
Click to collapse
yes. make sure you switched from kingroot to superSU if you used that method. flashfire requires superSU.
muniz, will all new mods have to be created for of1 or can oc1 mods be used?(to enable native tethering and such)
Sent from my SCH-I545 using Tapatalk
sooo.... likely not the best idea, but is there a way to dirty flash this with FlashFire? it is, after all, still 5.0.1. Not really looking forward to starting over again after just getting OC1 up a few weeks back. Not to mention re-doing xposed
skepticmisfit said:
doing a wipe will generally fix most bugs encountered by people who take OTAs. all those normals you see being like "oh my phone got an update and its sooooo slow now omg I'm gonna get an iphone"
they're just doing it wrong.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 10:55 AM ---------- Previous post was at 10:52 AM ----------
yes. make sure you switched from kingroot to superSU if you used that method. flashfire requires superSU.
muniz, will all new mods have to be created for of1 or can oc1 mods be used?(to enable native tethering and such)
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
THANKS!!!!
@muniz_ri, to reiterate this important question: will all new mods have to be created for of1 or can oc1 mods be used?(to enable native tethering and such)
Thanks for answering
guho said:
@muniz_ri, to reiterate this important question: will all new mods have to be created for of1 or can oc1 mods be used?(to enable native tethering and such)
Thanks for answering
Click to expand...
Click to collapse
The initial question on this was just posted about an hour ago... sheesh. Please be patient when waiting for an answer.
ToastyZ71 said:
sooo.... likely not the best idea, but is there a way to dirty flash this with FlashFire? it is, after all, still 5.0.1. Not really looking forward to starting over again after just getting OC1 up a few weeks back. Not to mention re-doing xposed
Click to expand...
Click to collapse
the zip has a script in it that automatically wipes data
would you rather take the time to set up all your stuff or deal with incredibly buggy firmware due to a dirty flash?
Sent from my SCH-I545 using Tapatalk
skepticmisfit said:
the zip has a script in it that automatically wipes data
would you rather take the time to set up all your stuff or deal with incredibly buggy firmware due to a dirty flash?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I may be lazy, but not completely stupid
Sir_Eagle said:
Loaded this and Bluetooth isn't working. Do I need to do something to fix it. Worked before loading this.
Click to expand...
Click to collapse
Can anyone confirm or deny this?
Hey, I'm new and a noob here, so if I flash the deodexed ROM and on my s4 with root on OC1, I will keep all my files, right?
hithisisme said:
Hey, I'm new and a noob here, so if I flash the deodexed ROM and on my s4 with root on OC1, I will keep all my files, right?
Click to expand...
Click to collapse
this has been stated before. if you flash either deodexed or odexed rom using flashfire, you'll be wiping all your stuff, apps, contacts, txt msgs... etc... it will be as if you went and factory reset the phone. only now you're on OF1
so im still new to this if my phone is not rooted but already updated to 0f1 i cant root now without flashing back to an older version first?
crazyjls said:
so im still new to this if my phone is not rooted but already updated to 0f1 i cant root now without flashing back to an older version first?
Click to expand...
Click to collapse
you can't root at all. not until some sort of exploit gets found. I'm pretty sure kingroot was patched with of1
Sent from my SCH-I545 using Tapatalk
skepticmisfit said:
you can't root at all. not until some sort of exploit gets found. I'm pretty sure kingroot was patched with of1
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
i have not been able to get it to work from the pc or app phone it gets to about 55% then fails everytime