I just flashed CM10.1 on my Sprint S3.
I am trying to flash the latest nightly and I am getting the following error in both CWM and TWRP
Assert failed: getprop("ro.bootloader" == "l710vpbLj7" ... and it repeats that line specific to other versions (L710VPBMA6 etc)
I had an older version of CWM ... but still a 6+ when I flashed it. I since installed (via goomanager) TWRP as it looked cool. I started getting this error. Next, I used CWM to install the latest 6.0.3.1 version of CWM. It's still not wokring.
I seem to be able to download the goomanager latest DL and that's what I used to get the initial flashable zip.
Any ideas? I'm kinda at a loss. I'd do a full wipe but I'm afraid that if I do that I'll be SOL - as I have a current functional ROM right now.
Thoughts???
Sent from my SPH-L710 using xda app-developers app
Ha ha. You're still in the same, incorrect (international GT-i9300) forum. Try here:
http://forum.xda-developers.com/forumdisplay.php?f=1707
gregory15 said:
I just flashed CM10.1 on my Sprint S3.
I am trying to flash the latest nightly and I am getting the following error in both CWM and TWRP
Assert failed: getprop("ro.bootloader" == "l710vpbLj7" ... and it repeats that line specific to other versions (L710VPBMA6 etc)
I had an older version of CWM ... but still a 6+ when I flashed it. I since installed (via goomanager) TWRP as it looked cool. I started getting this error. Next, I used CWM to install the latest 6.0.3.1 version of CWM. It's still not wokring.
I seem to be able to download the goomanager latest DL and that's what I used to get the initial flashable zip.
Any ideas? I'm kinda at a loss. I'd do a full wipe but I'm afraid that if I do that I'll be SOL - as I have a current functional ROM right now.
Thoughts???
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem on the spring gs3 and I can't figure it out.
Whew, someone else with the Asset faled: getprop error
Have you learned anything more about this? I have found I was able to install CM10.1 up to nightly 0511 but nothing after that.
gregory15 said:
I just flashed CM10.1 on my Sprint S3.
I am trying to flash the latest nightly and I am getting the following error in both CWM and TWRP
Assert failed: getprop("ro.bootloader" == "l710vpbLj7" ... and it repeats that line specific to other versions (L710VPBMA6 etc)
I had an older version of CWM ... but still a 6+ when I flashed it. I since installed (via goomanager) TWRP as it looked cool. I started getting this error. Next, I used CWM to install the latest 6.0.3.1 version of CWM. It's still not wokring.
I seem to be able to download the goomanager latest DL and that's what I used to get the initial flashable zip.
Any ideas? I'm kinda at a loss. I'd do a full wipe but I'm afraid that if I do that I'll be SOL - as I have a current functional ROM right now.
Thoughts???
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
FlagPonder said:
Have you learned anything more about this? I have found I was able to install CM10.1 up to nightly 0511 but nothing after that.
Click to expand...
Click to collapse
**** UPDATE *****
****THIS SOLUTION and LINKS ARE ONLY APPLICABLE TO SPRINT GALAXY S3 PHONES ... FYI FYI FYI******
yes. I have. The problem is that we have an old version of the FIRMWARE. If you flash the following to update your firmware to MD4:
http://forum.xda-developers.com/showthread.php?t=1910947 and install Galaxy-S-fre3-MD4FirmwareModemAIO.zip from CWM.
There are some new checks that happen that require the MD4 stuff. For more information about that - you can check https://plus.google.com/app/basic/stream/z13cdxpafunnexghb04cc5q4knbyjh4hprg0k
Also, clear cache/dalvik - not that it matters - but I did that - and i found things working. So, after flash, go into /cmupdate folder and flash the latest - it should work (unless i'm just lucky)
_G
gregory15 said:
**** UPDATE *****
****THIS SOLUTION and LINKS ARE ONLY APPLICABLE TO SPRINT GALAXY S3 PHONES ... FYI FYI FYI******
yes. I have. The problem is that we have an old version of the FIRMWARE. If you flash the following to update your firmware to MD4:
http://forum.xda-developers.com/showthread.php?t=1910947 and install Galaxy-S-fre3-MD4FirmwareModemAIO.zip from CWM.
There are some new checks that happen that require the MD4 stuff. For more information about that - you can check https://plus.google.com/app/basic/stream/z13cdxpafunnexghb04cc5q4knbyjh4hprg0k
Also, clear cache/dalvik - not that it matters - but I did that - and i found things working. So, after flash, go into /cmupdate folder and flash the latest - it should work (unless i'm just lucky)
_G
Click to expand...
Click to collapse
Thank you so much. Fixed my issue as well. One thing I have to add is that you should do Advanced > Reboot Recovery if you still cannot flash the ROM that gave you the assert problems.
I remember reading that from now on CM10.1 will need the MD4 bootloader or else you get that assert error.
Sent from my SPH-L710 using Tapatalk 2
anyone know if the sprint md4 firmware update will work with c spire's galaxy s3?
You should not flash firmware not intended for your exact device.
CNexus said:
You should not flash firmware not intended for your exact device.
Click to expand...
Click to collapse
What he said. Flashing modems is about the most dangerous thing you can do to your phone
Sent from my SPH-L710 using xda app-developers app
k good to know how would I be able to successfully flash cm10.1 on my c spire gs3?
Fazzl86 said:
k good to know how would I be able to successfully flash cm10.1 on my c spire gs3?
Click to expand...
Click to collapse
Shoot me a pm. I'll set ya straight
Virgin Mobile?
Anyone know if this will work for the Sph-l710 for Virgin Mobile? I'm trying to flash a 4.4 Rom and I'm wanting to try this but it sounds too risky.... Thoughts?
Ok, so I'm getting the same error as OP, trying to flash the CM10.2 Stable (via TWRP) and I understand that I may need to update my firmware or bootloader (are these different?). The only problem is, I may have accidentally installed the OTA 4.3 rom with Knox. I ended up reflashing right away after I realized what I'd done, and the rom I have now (4.3 stock w/ root) doesn't have any knox apps, nothing about knox in device manager, and root/superuser is working just fine.
That said, I'm a bit scared to update my firmware as I've heard stories about Knox working in the background and bricking. Is there a way I can be sure updating my firmware wont brick me? Can someone point me to the latest file I should be flashing here?
Thing in "About Device":
Model:SPH-L710
Version 4.3
Baseband: L710VPUCMK3
Kernel:[email protected] #1
Build: JSS15J.L710VPUCMK3
SE: Permissive
Hardware:L710.14
Thanks in advance. I've gotta get off the stock 4.3, battery life and sluggish behavior are killing me.
DC
Related
Can someone please tell me what I'm doing wrong. I'm on stock uvalh2, it is rooted but i checked temp unroot in superuser. I downloaded the JB leak update UVDLI7, and i put it on my external SD. I went into stock recovery and i hit "install from external sd" and hit the downloaded JB, file. And everytime i tried installing this came up
"E:error in /tmp/sideload/package.zip (status 7)
Does any one know what that is? I've updated my girlfriends sgs3 and my brothers and it worked flawlessly, but i can never seem to achieve it onon mine. If anyone could help, it would mean the world to me., thanks
Jake
Did u do a factory reset and full wipe I had that problem until I did that..
Sent from my SGH-T999 using xda app-developers app
DNASTY6997 said:
Did u do a factory reset and full wipe I had that problem until I did that..
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I didn't. Going to try that now. Thanks
DNASTY6997 said:
Did u do a factory reset and full wipe I had that problem until I did that..
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Ok, tried that. This time it says "Install Aborted". Only thing it did was reset my phone. If anyone knows what i need to do that would be great. Thanks anyways Dnasty
I recommend you verify the integrity of your LI7 file, then use Odin to flash ClockworkMod (links in my signature).
I think its about time people quit messing around with the worthless stock recovery.
Aerowinder said:
I recommend you verify the integrity of your LI7 file, then use Odin to flash ClockworkMod (links in my signature).
I think its about time people quit messing around with the worthless stock recovery.
Click to expand...
Click to collapse
Hey, i had root and cwm on uvalh2. But i was told that to update my phone to the leak JB 4.1.1 UVDLI7, I need to unroot And install it from stock not CWM. Plus ive read about 10 different directions on varius sites saying the Same thing. I was even told to change the file name to Update.zip. i still get the error tmp/sideload/package.zip status 7. I've already done it to 2 other Phones, i just can't get it on mine. If you know a way to flash the JB leak UVDLI7 thru Odin please tell me how. Thanks
I am not sure what error 7 means. It could mean your files didn't pass verification (the update checks them before it applies), or the zip file is corrupted, etc. Did you get it from here: http://www.sammobile.com/firmware/?page=3&model=SGH-T999&pcode=TMB&os=1&type=1#firmware?
My point is that this information about OTA flashing that you are seeing is outdated. People still swear by it, but they are no longer correct. Two months ago, they were correct. But not anymore. If you are using CWM 6.0.1.2, you absolutely do not need to do anything, except flash the leaked OTA update through CWM.
You don't flash the OTA updates through Odin. If you are on UVALH2 right now, here is what you do:
If you are using a modem that is not LH2, you need to flash to LH2.
Run OTA update through CWM.
Done.
Aerowinder said:
I am not sure what error 7 means. It could mean your files didn't pass verification (the update checks them before it applies), or the zip file is corrupted, etc. Did you get it from here: http://www.sammobile.com/firmware/?page=3&model=SGH-T999&pcode=TMB&os=1&type=1#firmware?
My point is that this information about OTA flashing that you are seeing is outdated. People still swear by it, but they are no longer correct. Two months ago, they were correct. But not anymore. If you are using CWM 6.0.1.2, you absolutely do not need to do anything, except flash the leaked OTA update through CWM.
You don't flash the OTA updates through Odin. If you are on UVALH2 right now, here is what you do:
If you are using a modem that is not LH2, you need to flash to LH2.
Run OTA update through CWM.
Done.
Click to expand...
Click to collapse
Thank you so much!!!! You solved my problem. You're the man
Jake
Aerowinder said:
I am not sure what error 7 means. It could mean your files didn't pass verification (the update checks them before it applies), or the zip file is corrupted, etc. Did you get it from here: http://www.sammobile.com/firmware/?page=3&model=SGH-T999&pcode=TMB&os=1&type=1#firmware?
My point is that this information about OTA flashing that you are seeing is outdated. People still swear by it, but they are no longer correct. Two months ago, they were correct. But not anymore. If you are using CWM 6.0.1.2, you absolutely do not need to do anything, except flash the leaked OTA update through CWM.
You don't flash the OTA updates through Odin. If you are on UVALH2 right now, here is what you do:
If you are using a modem that is not LH2, you need to flash to LH2.
Run OTA update through CWM.
Done.
Click to expand...
Click to collapse
And yes i had gotten it from sammobile
My friend Bought a SGSIII from Telus, i hope to get one to if this all works, and we were using the Android toolkit 2.3 to get Clockwork and TWRP onto the phone which worked(we tried both and got errors which ill show in pics)
When i copy the latest CM nightly to his SD and try to fail, i get this 'assert failed' error. Screenshot attached.
Current its on stock and rooted, but thats as far as we can go.
IS there a fix for this? I flashed using the latest toolkit.
Also, i cant seem to find a definitive answer on these forums regarding this, just alot of uncertainty and different opinions.
1.) Is there any harm in flashing a Rogers modem on a Telus device, or vice versa, wouldnt that just convert the phone into another carriers device since they carry it to.
2.) Are there ANY restrictions on what can be flashed, i realize 90% of roms will be AT&T, is there any chance of bricking by using this.
Thanks!
Update to newest cwm, or use twrp
Open the updater-script and delete the first few lines which check if you are flashing on the correct device.
Alternatively, you can just change your build.prop to "d2att" and it will flash. I'm pretty sure that the i747m will run the i747 ROMs, as long as you have the right radio flashed.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Got it all goin! Thanks guys!
Rekzer said:
Got it all goin! Thanks guys!
Click to expand...
Click to collapse
What was the resolution?
Tony_YYZ said:
What was the resolution?
Click to expand...
Click to collapse
Steps were
Use Tooklit to Install TWRP and Root Phone
Download a build.prop editor and change all d2can to d2att
Reboot phone
Install goo manager, menu button, install recovery script(should install the d2att one)
Reboot into recovery..flash CM
CM's self updater works after this cause i think the ATT boot loader is on there. Very good stuff!
You COULD maybe skip alot of it, and install the ATT boot loader from the toolkit, but this is what worked for me on 3 devices(coworkers/mine)
Or, you could have used ROM manager to upgrade to cwm 6.0.1.2 or newer.
Rpm manager supports sgs3? I was under the impression never use rom manager from s2 days.
Suped up S3
It works on s3. I've used it a couple times. Worked great on my old Inspire too.
I was able to successfuly root and flash a custom ROM onto my phone a few months back using CWM. However, when I try to install a new ROM after all this time, I have come to the realization that my bootloader is outdated.
I've followed the steps in the "if you are unable to install CM10.1" thread, but I still receive the same error (Status 7).
According to the error I get on my phone in CWM, it looks like I need either I747UCDLK3 & I747MVLDLK4. I am sure I will be able to find those on my own, however, going about installing those or updating my current bootloader onto my phone through a Mac computer, I am not positive.
I just need someone to point me in the right direction.
tl;dr Rooted S3 months ago, installed ROM, looking to install CM10.1, error 7, need to update bootloader, not sure how to using Mac.
Correct me if I'm wrong but I think status 7 error means out of date recovery. What version of cwm recovery are you running? The latest one is 6.0.3.1
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
You probably do need to update CWM.
How to do a bootloader: http://forum.xda-developers.com/showthread.php?p=41771519
Remember this is the most difficult thing to do on your phone and you could bork it!
Here are bootloaders: http://forum.xda-developers.com/showthread.php?p=41503727
AGAIN REMEMBER THIS IS SOMETHING THAT CAN BORK YOUR PHONE....
Domoo said:
Correct me if I'm wrong but I think status 7 error means out of date recovery. What version of cwm recovery are you running? The latest one is 6.0.3.1
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nope, I have an up to date CWM (version 6.0.3.1)
oldbbman said:
You probably do need to update CWM.
How to do a bootloader: http://forum.xda-developers.com/showthread.php?p=41771519
Remember this is the most difficult thing to do on your phone and you could bork it!
Here are bootloaders: http://forum.xda-developers.com/showthread.php?p=41503727
AGAIN REMEMBER THIS IS SOMETHING THAT CAN BORK YOUR PHONE....
Click to expand...
Click to collapse
So I just used CWM to update my bootloader to the one that CyanogenMod said you needed for 10.1 (d2att: I747UCDLK3 & I747MVLDLK4) and I still get the same error.
Edit: So, I downloaded Rootchecker, while my "About Phone" says I have the new bootloader I installed, Rootchecker says I have the old one. I believe it is still an issue of the bootloader being out of date but I'm not sure how to update it without Odin.
Edit 2: This (http://d-h.st/yqV) is what I need to update my bootloader to, without using Odin. Is this possible?
kercmerk said:
Nope, I have an up to date CWM (version 6.0.3.1)
So I just used CWM to update my bootloader to the one that CyanogenMod said you needed for 10.1 (d2att: I747UCDLK3 & I747MVLDLK4) and I still get the same error.
Edit: So, I downloaded Rootchecker, while my "About Phone" says I have the new bootloader I installed, Rootchecker says I have the old one. I believe it is still an issue of the bootloader being out of date but I'm not sure how to update it without Odin.
Click to expand...
Click to collapse
See if this thread can help you: http://www.google.com/url?sa=t&rct=j&q=status%207%20installation%20aborted%20galaxy%20s3&source=web&cd=1&cad=rja&ved=0CCsQtwIwAA&url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQW1znjDLe-k&ei=OJLgUdOBO9LKqQHybQ&usg=AFQjCNHgYodJ06avMnRIFYOxGshpLssfIw&bvm=bv.48705608,d.aWM
kercmerk said:
Nope, I have an up to date CWM (version 6.0.3.1)
So I just used CWM to update my bootloader to the one that CyanogenMod said you needed for 10.1 (d2att: I747UCDLK3 & I747MVLDLK4) and I still get the same error.
Edit: So, I downloaded Rootchecker, while my "About Phone" says I have the new bootloader I installed, Rootchecker says I have the old one. I believe it is still an issue of the bootloader being out of date but I'm not sure how to update it without Odin.
Edit 2: This (http://d-h.st/yqV) is what I need to update my bootloader to, without using Odin. Is this possible?
Click to expand...
Click to collapse
You are confusing bootloaders and baseband. Baseband is the modem.
http://forum.xda-developers.com/showthread.php?t=2321310
This week help you update your bootloader
mrhaley30705 said:
You are confusing bootloaders and baseband. Baseband is the modem.
http://forum.xda-developers.com/showthread.php?t=2321310
This week help you update your bootloader
Click to expand...
Click to collapse
Thanks! I actually found that link before I read your post but I'm glad you posted it so others with the same problem have the solution right here.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Here is my dilemma, I recently unlocked and rooted my HTC One M7 for Verizon. I may not have performed a backup but I am oblivious to what the problem may be. I am a newb to rooting and unlocking so please spare me any negative feedback. S-off was successful using firewater. Phone is unlocked in bootloader. Phone was rooted through TWRP v2.7.0.0 and SU. After root was successful I did a factory reset then flashed CM11 with TWRP. CM11 installation was successful except for one problem. My mobile network is not available and a message appears on the screen(You need to refer to the SIM card instruction that came with your phone.) The CM11 file that I installed is: cm-11-20140407-NIGHTLY-m7.zip and after reading that the "Nightly" roms are not the most stable, I then flashed this one: cm-11-20140405-SNAPSHOT-M5-m7.zip. Here is what the Installation looked like in Recovery:
Updating partition details...
Full SELinux support is present.
Formatting Cache using make_ext4fs function.
Wiping data without wiping /data/media ...
Done.
Updating partition details...
Installing ' /sdcard/Download/cm-11-20140405-SN
APSHOT-M5-m7.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details..
Successful.
Following the successful flash, I then installed gapps-kk-20131208. Please be detailed in how I can fix this issue. Thanks so much in advance.
Have you ever updated to kk firmware? If your using a kk based rom, you also need kk firmware.
KK firmware
cmlusco said:
Have you ever updated to kk firmware? If your using a kk based rom, you also need kk firmware.
Click to expand...
Click to collapse
I don't understand. What is KK firmware? This may seem like a stupid question but I really don't know.
kk
I am going to feel really stupid if you meant kit kat and if you did then yes I have installed the version for kit kat 4.4.2
Zacb01 said:
I am going to feel really stupid if you meant kit kat and if you did then yes I have installed the version for kit kat 4.4.2
Click to expand...
Click to collapse
No he doesn't mean it has to do with the rom. Firmware is flashed separate from roms. Once you flash it, you don't have to worry about it unless a newer firmware gets released. Go to this thread: http://forum.xda-developers.com/showthread.php?t=2485319 and follow the instructions on the 2nd post. Use 3.11.605.1 NO Boot.img firmware.zip since you'll be doing custom roms.
Mobile service
Crawshayi said:
No he doesn't mean it has to do with the rom. Firmware is flashed separate from roms. Once you flash it, you don't have to worry about it unless a newer firmware gets released. Go to this thread: http://forum.xda-developers.com/showthread.php?t=2485319 and follow the instructions on the 2nd post. Use 3.11.605.1 NO Boot.img firmware.zip since you'll be doing custom roms.
Click to expand...
Click to collapse
I installed this successfully but I still can't make or receive calls. I am wondering if the version of cyanogenmod that I flashed might not be compatible but I did not get a status 7 error when installing. I am also wondering why I got the sim card message when first installing cm11. The version that I installed is stated above on my first post but cyanogenmod has m7 and m7vzw, I can install m7, which I believe is for GSM but I have a Verizon HTC One. When I try to flash the m7vzw version I get the status 7 error code. I tried to do a fix for it but I may have done this incorrectly since I got a status 6 error code. Plz help. I need this phone for work.
You want the m7vzw, the regular m7 is gsm. Status 7 refers to an error in the update script or an incompatible update binary. Does it give a specific error with that status 7? You should also update your twrp to version 2.7.0.4b-santod. http://www.androidfilehost.com/?fid=23329332407584851
Last i heard cm11 is only in preview and data and calls do not work. That may have changed though.
Error
I updated the twrp to v2.7.0.4b-santod, did a factory reset and tried to flash cm11 for m7vzw and was given this mssg...E:Error executing updater binary in zip ' /sdcard/Download/cm-11-20140124-NIGHTLY-M7VZW.ZIP' Setting performance mode OFF. Error flashing zip....etc.....
Why are you flashing an old nightly, and not the one from yesterday? http://download.cyanogenmod.org/?device=m7vzw&type=nightly
I think your issue is that your trying to flash an older nightly with a newer recovery. The newer recoveries have updated binaries that older roms arent compatie with. So either flash a newer nightly, or and older recovery.
If you want a stable rom, i would not use cm11, i would go with cm10.2.
Compatible
The twrp version you recommended and the yesterday's nightly don't work together. Do you have a recovery and a cm11 that are compatible that you can recommend?
Recommendation
cmlusco said:
Why are you flashing an old nightly, and not the one from yesterday? http://download.cyanogenmod.org/?device=m7vzw&type=nightly
I think your issue is that your trying to flash an older nightly with a newer recovery. The newer recoveries have updated binaries that older roms arent compatie with. So either flash a newer nightly, or and older recovery.
If you want a stable rom, i would not use cm11, i would go with cm10.2.
Click to expand...
Click to collapse
I decided to go with cm 10.2.1. Thanks for everything!
Zacb01 said:
The twrp version you recommended and the yesterday's nightly don't work together. Do you have a recovery and a cm11 that are compatible that you can recommend?
Click to expand...
Click to collapse
Hmm thats strange, mabey cm11 just dosent like twrp or something. Glad you got something figured out.
Upgrading to lollipop
Someone should please help on how to upgrade to lollipop 5.0 on HTC m7 complaining of md5 file not found
Bone stock google play edition ROM with stock kernel. (NOT ROOTED)
Only two changes from stock:
1 Fixed security settings and VPN by deleting a keystore lib.
2 Edited platform.xml to allow apps to write to external SD.
@dandroid13 used to release stock GPE ROMs in i9505 forums but since has not done 4.4.3 or 4.4.4, I am doing it here.
I9505 users, please flash a different kernel.
ATT users, the ROM is NOT Loki'd. PLEASE FLASH LOKI-DOKI AFTER FLASHING THIS ROM.
What I did: Repacked @SamuriHL's 4.4.3 Odin tar into a flashable stock 4.4.3 ROM and flashed it. Then made the 4.4.3-4.4.4 OTA zip flashable by modifying the updater script in it. Then flashed the OTA and then pulled the system, fixed the aforementioned bugs and packaged it into a ROM.
Credits:
@SamuriHL for 4.4.3 Odin tar
@Danvdh for updater script and binary
@broodplank1337 for init.d
Enjoy and this is my first ROM release so please be nice
Instructions:
1 Wipe data, cache and system
2 Flash ROM
3 Flash loki-doki
4 Reboot
Download stock version:
https://copy.com/qFMv8IivhUAMtrfb
Mirror: http://www.androidfilehost.com/?fid=23501681358553238
Download prerooted version with busybox and init.d support:
http://www.androidfilehost.com/?fid=23501681358553418
Sent from my GT-I9505G using Tapatalk
Hey, got my build ready here, will upload it later today. LOL
dandroid13 said:
Hey, got my build ready here, will upload it later today. LOL
Click to expand...
Click to collapse
lol
4.4.4 odin image was posted last night.
Sent from my GT-I9505G using Tapatalk
SamuriHL said:
4.4.4 odin image was posted last night.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Hey I know and thank for that but us ATT users cant flash that one so I made this one!
RK said:
Bone stock google play edition ROM with stock kernel. (NOT ROOTED)
Only two changes from stock:
1 Fixed security settings and VPN by deleting a keystore lib.
2 Edited platform.xml to allow apps to write to external SD.
@dandroid13 used to release stock GPE ROMs in i9505 forums but since has not done 4.4.3 or 4.4.4, I am doing it here.
I9505 users, please flash a different kernel.
ATT users, the ROM is NOT Loki'd. PLEASE FLASH LOKI-DOKI AFTER FLASHING THIS ROM.
What I did: Repacked @SamuriHL's 4.4.3 Odin tar into a flashable stock 4.4.3 ROM and flashed it. Then made the 4.4.3-4.4.4 OTA zip flashable by modifying the updater script in it. Then flashed the OTA and then pulled the system, fixed the aforementioned bugs and packaged it into a ROM.
Credits:
@SamuriHL for 4.4.3 Odin tar @Danvdh for updater script and binary
Enjoy and this is my first ROM release so please be nice
Instructions:
1 Wipe data, cache and system
2 Flash ROM
3 Flash loki-doki
4 Reboot
Download:
https://copy.com/qFMv8IivhUAMtrfb
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Can I flash this one on Canadian S4 SGH-I337M?
Oncet said:
Can I flash this one on Canadian S4 SGH-I337M?
Click to expand...
Click to collapse
Not sure but I think so. The worst case scenario is that you may have to flash a different kernel but I think even that won't be necessary.
Sent from my GT-I9505G using Tapatalk
RK said:
Not sure but I think so. The worst case scenario is that you may have to flash a different kernel but I think even that won't be necessary.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. Downloading Now. will install it and let you.
I will also look for 4.4.4 kernel for 337M just in case you know.
RK said:
Hey I know and thank for that but us ATT users cant flash that one so I made this one!
Click to expand...
Click to collapse
No I know but I mentioned it just in case you wanted to update your rom that you made from the 4.4.3 odin image.
Sent from my GT-I9505G using Tapatalk
Install was smooth and easy. Working flawlessly on Canadian s4. No need for other kernel installation.
Towelroot is not working for rooting.
Sent from my SGH I337M using XDA Free mobile app
Oncet said:
Install was smooth and easy. Working flawlessly on Canadian s4. No need for other kernel installation.
Towelroot is not working for rooting.
Sent from my SGH I337M using XDA Free mobile app
Click to expand...
Click to collapse
I know. Chainfire's supersu zips dont seem to work either. I have added a prerooted version to the OP if you want root.
Its here:
http://www.androidfilehost.com/?fid=23501681358553418
RK said:
I know. Chainfire's supersu zips dont seem to work either. I have added a prerooted version to the OP if you want root.
Its here:
http://www.androidfilehost.com/?fid=23501681358553418
Click to expand...
Click to collapse
It didn't work for me.
lilphil240 said:
It didn't work for me.
Click to expand...
Click to collapse
what did not work? Download? ROM? root?
RK said:
what did not work? Download? ROM? root?
Click to expand...
Click to collapse
Tried the rooted version but SuperSU, Towelroot, etc do not work. By the way, I'm on AT&T I337 if that matters.
kevinco1 said:
Tried the rooted version but SuperSU, Towelroot, etc do not work. By the way, I'm on AT&T I337 if that matters.
Click to expand...
Click to collapse
The rooted version comes with supersu preinstalled. Just flash the rom boot up, open supersu and update binary.
Do not flash supersu zip or try towelroot on the rooted version.
RK said:
The rooted version comes with supersu preinstalled. Just flash the rom boot up, open supersu and update binary.
Do not flash supersu zip or try towelroot on the rooted version.
Click to expand...
Click to collapse
Did not work for me. Also my custom recovery was lost after the flash. I had to towel root to get root access. Still unsure how to regain my custom recovery because whenever i try to install it, I get a message saying the system software isn't supported by AT&T. I don't know what to do. I have this Google Play Rom and root but no recovery.
Also my cell signal got noticeably worse after getting this Rom
lilphil240 said:
Did not work for me. Also my custom recovery was lost after the flash. I had to towel root to get root access. Still unsure how to regain my custom recovery because whenever i try to install it, I get a message saying the system software isn't supported by AT&T. I don't know what to do. I have this Google Play Rom and root but no recovery.
Also my cell signal got noticeably worse after getting this Rom
Click to expand...
Click to collapse
Are you sure you flashed the zip in the OP? This ROM (any version) does not touch the recovery at all.
Anyways, if you want to get your custom recovery back, very carefully follow the instructions here:
http://teamw.in/project/twrp2/174
You will need to install a terminal emulator app to do this.
This will give you a working TWRP V2.7.1.0. Then, you can flash your favorite recovery from TWRP
Root works
I just downloaded and flashed the ROM and root works perfectly fine for me.
Thanks for the link to get back my recovery. Weird how this ROM didn't work for me. Glad the guy above me had no issues. Someone at my work was complaining about their AT&T signal today, saying hers also got worse within the last two days. So maybe it wasn't the ROM that caused my weakened signal. I downloaded it two days ago, so I had to assume the issue was the ROM.
Thanks again!
I've been running the rom since he uploaded it and it has been running fine ever since. battery life is great also.