Develop Bugs

[Q] JB OTA update fails on rooted Vodafone One X

Hello guys,
I have a HTC One X from Vodafone, rooted, unlocked, stock rom, custom recovery, and today (FINALLY ) I received the OTA update to Jelly Bean.
I downloaded it and tried to install it using the custom recovery but it was failing on some assert. I guessed that it was because of the recovery so I flashed back the stock recovery and tried to install; fail again.
Went online and found the directory for the update log and saw an entry saying that there was a problem trying to verify the stock Dropbox apk that comes with the phone and that is placed on /system/apps. I read somewhere that if you modify something on the stock apks the OTA would fail, and unfortunatelly I did, I flashed the Galaxy S3 Dropbox apk on my phone, but that's not the problem, the problem is that I deleted the flashed Dropbox and the stock Dropbox from /system/apps without knowing it and the OTA is still failing.
My guess is that if I can flash the stock Dropbox apk to /system/apps, the OTA will try to verify it and will succeed, and therefore I'll have finally Jelly Bean on my branded device (as I said, is just a guess) so if someone could please send me the stock Dropbox apk, the one located in /system/apps as well as any other file located there that could possibly be related to Dropbox app, it will be very very appreciated.
If you guys think that I'm missing something here and even after flashing the stock Dropbox apk the OTA will still fail for some karma related reasons, please let me know and help me out.
If you need any other info from my phone let me know too.
If you need the .zip file with the official update from Vodafone I have it too.
Thanks in advance.

TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.

nemer12 said:
TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.
Click to expand...
Click to collapse
Well yes I have stock recovery (replaced the custom recovery yesterday) and stock kernel, I haven't changed the kernel yet, and according to the log the problem is with Dropbox. I'll try to find it and paste it here so you guys can see it.
Thanks.

Just flash the RUU, update OTA and reroot.

Alright, will do and I'll let you know how it goes. Thanks

Netrunner16 said:
Alright, will do and I'll let you know how it goes. Thanks
Click to expand...
Click to collapse
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex

prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
If you only unlocked the bootloader the update should run fine !!! If it fails you did change some more !

prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.

And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !

Netrunner16 said:
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.
Click to expand...
Click to collapse
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level

prankstarr said:
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level
Click to expand...
Click to collapse
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !

MarcelHofs said:
And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !
Click to expand...
Click to collapse
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...

Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:

prankstarr said:
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...
Click to expand...
Click to collapse
But you said you had CWR, you need to flash the stock recovery back and then try the update.

MarcelHofs said:
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !
Click to expand...
Click to collapse
Okay cool - will try although I thought I flashed stock recovery. I got rid of CMR when I got in from work today ... recovery img was in the fastboot folder i used when unlocking bootloader.
---------- Post added at 12:20 AM ---------- Previous post was at 12:14 AM ----------
Netrunner16 said:
But you said you had CWR, you need to flash the stock recovery back and then try the update.
Click to expand...
Click to collapse
Yes, I thought i flashed stock before but am about to confirm

The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense

MarcelHofs said:
Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:
Click to expand...
Click to collapse
Yes, sorry - i did read it and it did say 2.17xxx...I downloaded the recovery you pointed me to but expect i need to re-unlock the bootloader. (I re-locked it before thinking that was causing the issue...)
Anyway, soon I should know if this works
By the way, I really appreciate you helping me - i've been trying to sort this out all evening!
---------- Post added at 12:34 AM ---------- Previous post was at 12:29 AM ----------
MarcelHofs said:
The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense
Click to expand...
Click to collapse
There is a good chance you are correct. The file in my fastboot folder said recovery and I assumed it was what I was after but it may have been connected to something that I was told to download in the unlocking process (I followed a guide on Youtube by a chap called cursed4eva)
I'm reunlocking the bootloader now because I got an error wh3n i tried to flash that recovery img. "writing 'recovery'... FAILED (remote: not allowed)"
---------- Post added at 01:24 AM ---------- Previous post was at 12:34 AM ----------
Okay - so I
1/ reunlocked the bootloader which basically wiped the phone back to its initialt state all be it with an unlocked bootloader.
2/ once again completed the OTA download of Vodafone Jellybean for the One X
3/ flashed the 2.17 recovery img that Marcel provided
4/ tried to update
5/ am currently looking at a download / progress bar! (YESSSS!)
6/ am hoping this works!
Thanks a lot Marcel. I very much appreciate your patience!

dr9722 said:
Just flash the RUU, update OTA and reroot.
Click to expand...
Click to collapse
I already have the RUU for my phone, and I was planning to follow this tutorial: http://forum.xda-developers.com/showthread.php?t=1660807
But I was thinking, what if I flash only the system.img instead of all the 3 files? I already have the stock recovery (the one you provided) and I've never changed the boot.img so I still have the stock one.
What about if I flash the system.img only, and then try the OTA update? Do you think that would work?
Thanks for the help.

Yes you can try that, the phone is already wiped with unlocking the bootloader, i never tried it. But in logical terms it is possible yes. If doesn't work you can always run the complete ruu !

That's weird, I'm getting error 00000006 when trying to flash the system.img.
Reading on other posts that's related to the size of the file, which is around 1 GB. If I can't flash the system.img I think I wont be able to run the entire RUU either.
Do you know a way to bypass this error?

[H] KitKat & root: screen mirroring work-around

Normally many methods to get root-rights break the Samsung screen-mirroring. The same for the Note and until now only for 4.3 exists a fix. With KitKat we have to choose: root or screen-mirroring.
But there is a work-around which works for me:
- after you got your root-rights flash the stock recovery back via Odin (make a backup of your data before - like always).
PS. The explanation is that a custom-recovery and not the changes for root-right breaks the screen-mirroring.
PPS. I still try to patch the corresponding library.
PPPS. I attached the recovery from MJ4 and still busy to build a zip for ND1. But the old from MJ4 also works.

Elim said:
Normally many methods to get root-rights break the Samsung screen-mirroring. The same for the Note and until now only for 4.3 exists a fix. With KitKat we have to choose: root or screen-mirroring.
But there is a work-around which works for me:
- after you got your root-rights flash the stock recovery back via Odin (make a backup before).
PS. The explanation is that a custom-recovery and not the changes for root-right breaks the screen-mirroring.
PPS. I still try to patch the corresponding library.
PPPS. I attached the recovery from MJ4 and still busy to build a zip for ND1. But the old from MJ4 also works.
Click to expand...
Click to collapse
Thanks - will this fix (and recovery) work with either the COO or US 4.4 updates?
With regards to the recovery - you mentioned the other option is to back up / restore the recovery ourselves. So I'd backup the current 4.4 recovery (i'll google the procedure) and just restore it after per your instructions?
Thx,
Praz

prazvt said:
Thanks - will this fix (and recovery) work with either the COO or US 4.4 updates?
Click to expand...
Click to collapse
I got for both versions screen-mirroring to work with this method.
prazvt said:
With regards to the recovery - you mentioned the other option is to back up / restore the recovery ourselves.
Click to expand...
Click to collapse
Oops, here I was not clear. No, the only method until now (for KitKat) is to restore a stock recovery. The backup I mentioned was about your data because every flash includes the possibility of losing the data.

Elim said:
I got for both versions screen-mirroring to work with this method.
Oops, here I was not clear. No, the only method until now (for KitKat) is to restore a stock recovery. The backup I mentioned was about your data because every flash includes the possibility of losing the data.
Click to expand...
Click to collapse
Hey Elim - thanks for the explanation. Right now I'm trying piece together the process to root and then restore screen mirroring functionality. It sounds like I need to install TWRP recovery for the root process. Then when I'm done, I'd flash the stock recovery back.
Could you clarify the process here? Do I extract the stock recovery.img from the US kitkat image, zip it and flash it within TWRP recovery?
EDIT: I think I'm good. I used a script to convert the recovery.img to a tar.md5 file. After rooting and installing SuperSU, installed the kitkat stock recovery. Will try screen mirroring once I get home

THANKS. ... got mine working again with your instructions!
Sent from my SM-P600 using Tapatalk

Could someone provide a step by step instruction? ... I am new with Odin and there are a bunch of buttons you can click and boxes to check... Would really appreciate a step by step process
Thank you!
Sent from my GT-N7105 using XDA Premium 4 mobile app

Thanks for your tip!
Unfortunately for me with xkat v3.2.1 this does not seem to work...
any ideas?

[Q] Rooting z1 compact stock lollipop

We all have gotten a sneak peek of Sony's lollipop update onto our beloved z1 compact. Through the many ways available I for instance used an ftf file. But they do not come pre-rooted like the zip file alternatives.
The only way to root ftf I am told is to flash a kernel pre-installed with a recovery then flash SuperSU zip. I have flashed like 3 different boot.imgs only to find no TWRP/Philz/cmw recovery.
Can anyone give me a WORKING kernel that will boot into a recovery? Would really appreciate this.
Found my solution
Edit: I just found a cm11 snapshot boot.img kernel, flashed it. Booted to recovery and flashed a pre-rooted rom zip. Easy as pie.
Thanks all.

Just flash KK firmware 108, root it, install recovery latest version, and afterwards flash any customised prerooted ROM of your choice.

kokkss said:
Just flash KK firmware 108, root it, install recovery latest version, and afterwards flash any customised prerooted ROM of your choice.
Click to expand...
Click to collapse
This is too much work. Work that I have to do. It's the only way to root this ftf. damn it

It's up to you.

I've done it.
I made a pre-rooted ftf using PRF creator and compiling the SUPERSU v2.37 and Z1C locked dual recovery 2.8.12 from Nuts site.
You can use Xperifirm to download the the firmware, then use Flashtool to decrypt the fileset and create the FTF, then you're good to go.

Hello guys.Does this method works??Without unlocking the bootloader? http://techchomps.com/root-14-5-a-0-242-android-5-0-lollipop-on-sony-xperia-z1-compact/

kos25k said:
Hello guys.Does this method works??Without unlocking the bootloader? http://techchomps.com/root-14-5-a-0-242-android-5-0-lollipop-on-sony-xperia-z1-compact/
Click to expand...
Click to collapse
Hello,
No don't work. With LB, you can't flash boot.img.

So i must unlock it right??Can anyone please send me the directions on how to unlock and root?

martin091 said:
I've done it.
I made a pre-rooted ftf using PRF creator and compiling the SUPERSU v2.37 and Z1C locked dual recovery 2.8.12 from Nuts site.
You can use Xperifirm to download the the firmware, then use Flashtool to decrypt the fileset and create the FTF, then you're good to go.
Click to expand...
Click to collapse
Awesome, which version region did you use? Mind sharing?
I am almost running out of options

So after everything done can we restore TA partition and relock the bootloader?
Not sent by me!

bumjrah said:
Awesome, which version region did you use? Mind sharing?
I am almost running out of options
Click to expand...
Click to collapse
I'm from the UK but I used the "Customized US" version. It works all the same, I've put together a UK one now but I'll need to wipe data before I can use it.
I'd share if I didn't have awful internet. The file is massive, unfortunately.
You'll find multiple threads on how to do different parts.
You need to create your pre-rooted firmware, then you'll need to download KK with Xperifirm (probably .108) and flash it with Flashtool.
Root KK using Easy Root Tool and install XZDualRecovery using the desktop client.
Once you're rooted with SuperSU/SuperUser and Recovery you can install the pre-rooted firmware (PRF) as a flashable zip within Recovery itself.
There's also work arounds for Xposed which you can find too, I've used them and it's all working as it should for now.
I also have a locked bootloader, so don't worry about unlocking it. I'll have a look around for the threads I used and post any I find.
---------- Post added at 08:38 AM ---------- Previous post was at 08:24 AM ----------
Working Xposed work-around
http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123?
FR pre-rooted firmware with extras (not sure on your region or if it'll work properly. Worth a try?)
http://forum.xda-developers.com/sony-xperia-z1-compact/general/14-5-0-242customizedfrpre-t3083055
PRF Creator
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Xperifirm
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Flashtool
http://forum.xda-developers.com/showthread.php?t=2335555
I'll leave you to find your own SuperSU or SuperUser zip, same with XZDualRecovery as they're frequently updated so you're better off finding the latest versions.

But how can you flash 108 if you are already on 242 and you have a locked bootloader? You must unlock it first...
Not sent by me!

BlackArtsInc said:
But how can you flash 108 if you are already on 242 and you have a locked bootloader? You must unlock it first...
Not sent by me!
Click to expand...
Click to collapse
What I did is that I downgraded with Flashtool, rooted KK, and then flashed a prerooted rom through the recovery. No need to unlock the bootloader.

c6nsor9d said:
What I did is that I downgraded with Flashtool, rooted KK, and then flashed a prerooted rom through the recovery. No need to unlock the bootloader.
Click to expand...
Click to collapse
How did you downgrade really?
You just flashed the 157 FTF in flashmode? It's doable?
Not sent by me!

BlackArtsInc said:
How did you downgrade really?
You just flashed the 157 FTF in flashmode? It's doable?
Not sent by me!
Click to expand...
Click to collapse
OK, there seems to be some loss in translation somewhere. Hope this will clear up some stuff:
1. Flash KitKat (kernel, system, everything).
2. Root it.
3. Install recovery (here)
4. Since you don't want to make your own pre-rooted firmware, here. Click on 'Google Drive' for the zip, and FTF. You need both.
5. Put the zip in your SD card/internal.
6. Boot into recovery and clear all data (dalvik, system, data, everything).
7. Flash the zip. DO NOT REBOOT.
8. Shutdown and use Flashtool to flash the .ftf you downloaded. Check System and Baseband on the 'exclude' column.
9. Have fun!

@dazzerfong OK,first of all thanks for your answer. What I'm asking is how did you do the first step with locked bootloader.
Flashtool->Flashmode->KitKat 157 FTF->Then root it blah blah?
Are these steps correct or not? Im about to try today cos I really miss root on my phone.
If you are already on Lollipop and your bootloader is locked you can get root this way.
1.Download the correct KitKat (.157) ROM for your country/operator using Xperifim.
Convert it to FTF using Flashtool. (there are tutorials,search)
2.Flash the FTF you created using Flashtool's Flashmode. Include everything.
3.Root your KitKat (.157) using the forum's tutorials and also install [NUT]'s recovery.
4.Boot into recovery and flash your pre rooted ROM in flashable zip format.
(There are also tutorials on how to create this with Xperifim and PRF programs).
5.Enjoy rooted Lollipop with locked bootloader.
Not sent by me!

BlackArtsInc said:
@dazzerfong OK,first of all thanks for your answer. What I'm asking is how did you do the first step with locked bootloader.
Flashtool->Flashmode->KitKat 157 FTF->Then root it blah blah?
Not sent by me!
Click to expand...
Click to collapse
Yep! All done with locked bootloader (or, if you want, unlocked, but you're wasting your time if you're unlocked). So, first you flash the FTF of a KitKat ROM.
Rooting, use Towelroot or something. No idea why, but Towelroot refuses to play with my TWRP (recovery), so I used the old method.

@dazzerfong
One last question cos I just did all the steps but I couldnt reboot into Lollipop after flashing my pre rooted rom zip file.
6. Boot into recovery and clear all data (dalvik, system, data, everything).
7. Flash the zip. DO NOT REBOOT.
8. Shutdown and use Flashtool to flash the .ftf you downloaded.
Check System and Baseband on the 'exclude' column.
Click to expand...
Click to collapse
On step 8 which FTF you mean exactly? I assume you mean the FTF from which you created
your pre rooted zip initially? In my case the Customized GR version?
N.

BlackArtsInc said:
@dazzerfong
One last question cos I just did all the steps but I couldnt reboot into Lollipop after flashing my pre rooted rom zip file.
On step 8 which FTF you mean exactly? I assume you mean the FTF from which you created
your pre rooted zip initially? In my case the Customized GR version?
N.
Click to expand...
Click to collapse
You should have downloaded 2 things so far: the zip, and the FTF. That FTF is Lollipop stock: doesn't matter where it's from. Flash that in Flashtool, but remember to check 'System' and 'Baseband' in the 'Exclude' column.

BlackArtsInc said:
How did you downgrade really?
You just flashed the 157 FTF in flashmode? It's doable?
Not sent by me!
Click to expand...
Click to collapse
Downgrade to .108 (with flashtool) in order to directly root the phone, whereas with .157, you'll have to flash an older kernel with flashtool in order to get root.
Once rooted, just get yourself a flashable prerooted firmware (zip file) and flash it from the recovery (after a wipe factory reset; wipe data; wipe cache; wipe Davilk Cache and Wipe System).

[Odin] [Official] Firmware / Kernel / Modem / Recovery [M919UVUFOK3] TW 4.4.4

[Firmware] [Odin] [Official] Firmware / Kernel / Modem / Recovery [M919UVUFOK3] TW 4.4.4
This is a Odin-flashable official firmware, kernel, modem & recovery for T-Mobile Samsung Galaxy 4 (M919)
How to install:
1. Extract the *.tar.md5 file using 7-Zip
2. Extract Odin v3.09 & open it
3. Reboot to Download Mode (press and hold Home + Power + Volume Down)
4. Connect phone and wait until you get a blue sign in Odin
5. Add the *.tar.md5 file to AP / PDA
6. Make sure re-partition is NOT ticked
7. Click the start button, sit back & wait a few minutes
Full Firmware:
https://www.androidfilehost.com/?fid=24338798368260486
Stock Kernel : Flash via Recovery, not needed if you use Full Firmware
https://www.androidfilehost.com/?fid=24338798368260505
Stock Recovery: Flash via Recovery, only needed if you want to go back to stock recovery, not needed if you use Full Firmware
https://www.androidfilehost.com/?fid=24338798368260507
Modem : ODIN Flashable
link removed as so many people are having issues with it

IS this the latest firmware? I bricked my phone trying to install a modem and I"m trying to get a usable phone again..

reilus said:
IS this the latest firmware? I bricked my phone trying to install a modem and I"m trying to get a usable phone again..
Click to expand...
Click to collapse
Yes OK3 is the latest firmware per T-Mobile site.
Sent from my GT-I9505 using Tapatalk

a103 said:
Yes OK3 is the latest firmware per T-Mobile site.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
You're a lifesaver. I had tons of problems with my phone and it kept failing flashes over and over again but I finally got it working with this firmware and now I'll have to see if I can root! Thank you so much! =)
---------- Post added at 09:14 PM ---------- Previous post was at 08:55 PM ----------
How do I root this firmware? I finally got past a boot issue...

reilus said:
You're a lifesaver. I had tons of problems with my phone and it kept failing flashes over and over again but I finally got it working with this firmware and now I'll have to see if I can root! Thank you so much! =)
---------- Post added at 09:14 PM ---------- Previous post was at 08:55 PM ----------
How do I root this firmware? I finally got past a boot issue...
Click to expand...
Click to collapse
You will need to flash TWRP first and then supersu.
Sent from my GT-I9505 using Tapatalk

Is the bootloader the same as the previous one?

Hmm....it looks like Xposed no longer works with this update. This is the error when you try to install it:
Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)
Click to expand...
Click to collapse
Update: The Xposed_v2.6.1_by_SolarWarez_20151129.apk variant works with this release! Search for it on Google if the stock versions wouldn't run on your phone!

Arkain2K said:
Hmm....it looks like Xposed no longer works with this update.
Click to expand...
Click to collapse
Can anyone else confirm? Thanks
Sent from my SGH-M919 using XDA Free mobile app

Use the old Xposed Installer v2.6.1 with TW 4.4.4, and you can directly install the xposed framework within the app.

Just a heads-up for anyone having trouble flashing any of these. I tried several times and re-downloaded the modem and the full firmware. They failed multiple times in multiple versions of odin(for me). I gave up on the modem but kept working on the full and it finally took but I was stuck at t-mo boot screen more than once and it wouldn't fully boot. Finally I flashed the newest twrp before taking any other measures and it finally booted.

technut said:
Just a heads-up for anyone having trouble flashing any of these. I tried several times and re-downloaded the modem and the full firmware. They failed multiple times in multiple versions of odin(for me). I gave up on the modem but kept working on the full and it finally took but I was stuck at t-mo boot screen more than once and it wouldn't fully boot. Finally I flashed the newest twrp before taking any other measures and it finally booted.
Click to expand...
Click to collapse
In case it gets stuck at T-Mobile boot screen after successful firmware flash, just hold the power button till your device turns off,
Then go into stock recovery by using power+home+volume up button and do a factory reset.
It should boot fine.
Sent from my SGH-M919 using Tapatalk

a103 said:
In case it gets stuck at T-Mobile boot screen after successful firmware flash, just hold the power button till your device turns off,
Then go into stock recovery by using power+home+volume up button and do a factory reset.
It should boot fine.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I forgot to list that I did that also. For me at least this S4 was very stubborn to take on this flash. I was mostly posting so if anyone else ran into this so they wouldn't panic. All is well now though. It came around eventually.:good:

I searched this out because I'm looking for a Stagefright fix for the S4 (my wife's phone). It looks like the other ROMs were last updated prior to Stagefright, so I expect they are not fixed. However, I'm OK with stock as long as it is rooted.
Are there any issues with rooting? I read in this article that T-Mobile put a SetUID restriction on the kernel and the normal process for TWRP and SuperSU doesn't work.
The author was writing about the UVUAMDL firmware, and offers a link to download a patched MDL kernel with the restriction removed.
Since this thread is about the UVUFOK3 (a later version), it seems likely that the SetUID restriction still exists. However the article also says "MAKE SURE YOU ARE ON UVUAMDL build OTHERWISE THIS KERNEL WILL BREAK THINGS IN YOUR PHONE!" So does that mean "UVUAMDL only - nothing newer or later" or "UVUAMDL or later"? No way to know since the article has not been updated since UVUAMDL.
Has any one successfully rooted the S4 after installing this firmware? (M919UVUFOK3_M919TMBFOK3_TMB)
Is the kernel provided in M919UVUFOK3_Stock_Kernel.zip already "fixed" to remove the root restriction?

timg11 said:
I searched this out because I'm looking for a Stagefright fix for the S4 (my wife's phone). It looks like the other ROMs were last updated prior to Stagefright, so I expect they are not fixed. However, I'm OK with stock as long as it is rooted.
Are there any issues with rooting? I read in this article that T-Mobile put a SetUID restriction on the kernel and the normal process for TWRP and SuperSU doesn't work.
The author was writing about the UVUAMDL firmware, and offers a link to download a patched MDL kernel with the restriction removed.
Since this thread is about the UVUFOK3 (a later version), it seems likely that the SetUID restriction still exists. However the article also says "MAKE SURE YOU ARE ON UVUAMDL build OTHERWISE THIS KERNEL WILL BREAK THINGS IN YOUR PHONE!" So does that mean "UVUAMDL only - nothing newer or later" or "UVUAMDL or later"? No way to know since the article has not been updated since UVUAMDL.
Has any one successfully rooted the S4 after installing this firmware? (M919UVUFOK3_M919TMBFOK3_TMB)
Is the kernel provided in M919UVUFOK3_Stock_Kernel.zip already "fixed" to remove the root restriction?
Click to expand...
Click to collapse
I don't know about the restriction you talking about but I have successfully flashed a custom ROM on latest OK3 firmware.
Sent from my SGH-M919 using Tapatalk

timg11 said:
I searched this out because I'm looking for a Stagefright fix for the S4 (my wife's phone). It looks like the other ROMs were last updated prior to Stagefright, so I expect they are not fixed. However, I'm OK with stock as long as it is rooted.
Are there any issues with rooting? I read in this article that T-Mobile put a SetUID restriction on the kernel and the normal process for TWRP and SuperSU doesn't work.
The author was writing about the UVUAMDL firmware, and offers a link to download a patched MDL kernel with the restriction removed.
Since this thread is about the UVUFOK3 (a later version), it seems likely that the SetUID restriction still exists. However the article also says "MAKE SURE YOU ARE ON UVUAMDL build OTHERWISE THIS KERNEL WILL BREAK THINGS IN YOUR PHONE!" So does that mean "UVUAMDL only - nothing newer or later" or "UVUAMDL or later"? No way to know since the article has not been updated since UVUAMDL.
Has any one successfully rooted the S4 after installing this firmware? (M919UVUFOK3_M919TMBFOK3_TMB)
Is the kernel provided in M919UVUFOK3_Stock_Kernel.zip already "fixed" to remove the root restriction?
Click to expand...
Click to collapse
Nothing is modified as it is a stock package, stock kernel is only required if you flash some custom kernel and wanted to go back to stock by just installing the kernel instead of full ODIN.
This is what I always use to root:
1) Install latest TWRP via ODIN
2) Boot into recovery
3) Flash latest SuperSU zip using TWRP.

pvsgh said:
Nothing is modified as it is a stock package, stock kernel is only required if you flash some custom kernel and wanted to go back to stock by just installing the kernel instead of full ODIN.
This is what I always use to root:
1) Install latest TWRP via ODIN
2) Boot into recovery
3) Flash latest SuperSU zip using TWRP.
Click to expand...
Click to collapse
So it should be a fairly straightforward process? The issues technut experienced are unusual? Has anyone else installed and rooted using this ROM? Please report on how it went.
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
a103 said:
I don't know about the restriction you talking about but I have successfully flashed a custom ROM on latest OK3 firmware.
Click to expand...
Click to collapse
a103, when you say "flashed a custom ROM", do you mean a different ROM than the one in the OP of this thread? (since this one isn't really custom) If a different ROM, which did you flash? I didn't find many options that contained the OK3 firmware.

pvsgh said:
Nothing is modified as it is a stock package, stock kernel is only required if you flash some custom kernel and wanted to go back to stock by just installing the kernel instead of full ODIN.
Click to expand...
Click to collapse
The phone currently is running Wicked V8 custom ROM, so I think I need to flash everything. What are the steps for updating all three; firmware, kernel, and modem? Is there a particular order to flash them in Odin?
I read in another place that the firmware contains the Modem so I wouldn't need to flash the modem in addition to the full firmware (M919UVUFOK3_M919TMBFOK3_TMB.zip). Is that true in this case? Does it include both modem and kernel?
Edit - After searching out how to open tar.md5 files I can now see that the full firmware does include the kernel and modem files. So installing that one should sufficient to update everything.

timg11 said:
The phone currently is running Wicked V8 custom ROM, so I think I need to flash everything. What are the steps for updating all three; firmware, kernel, and modem? Is there a particular order to flash them in Odin?
Click to expand...
Click to collapse
Just flash the firmware, it has the kernel and modem in it.
Sent from my GT-I9505 using Tapatalk

a103 said:
Just flash the firmware, it has the kernel and modem in it.
Click to expand...
Click to collapse
a103, did you have any of the problems reported by technut above? Was it a smooth process of flashing?
Here's what I think has been said:
0) Before starting - copy UPDATE-SuperSU-v2.46.zip, Titanium Backup APK, and Titanium Backup data onto ExtSD card.
1) start phone into download mode, Use ODIN to flash M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_HOME.tar.md5
2) restart into stock, let it stabilize.
If any problems or stuck on Tmo screen, restart into stock recovery and do factory reset
3) once booted into stock FW, power off.
4) restart into download mode, use Odin to flash openrecovery-twrp-2.6.0.0-jfltetmo.tar
5) boot into TWRP
6) install UPDATE-SuperSU-v2.46.zip
7) reboot into Android - phone is now rooted again and ready to go.
8) restore user apps (not system apps or data) from TiBu, restore TiBu XML data for SMS and call logs, etc.

timg11 said:
a103, did you have any of the problems reported by technut above? Was it a smooth process of flashing?
Here's what I think has been said:
0) Before starting - copy UPDATE-SuperSU-v2.46.zip, Titanium Backup APK, and Titanium Backup data onto ExtSD card.
1) start phone into download mode, Use ODIN to flash M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_HOME.tar.md5
2) restart into stock, let it stabilize.
If any problems or stuck on Tmo screen, restart into stock recovery and do factory reset
3) once booted into stock FW, power off.
4) restart into download mode, use Odin to flash openrecovery-twrp-2.6.0.0-jfltetmo.tar
5) boot into TWRP
6) install UPDATE-SuperSU-v2.46.zip
7) reboot into Android - phone is now rooted again and ready to go.
8) restore user apps (not system apps or data) from TiBu, restore TiBu XML data for SMS and call logs, etc.
Click to expand...
Click to collapse
I didn't encounter any issues.
Sent from my GT-I9505 using Tapatalk

HTC M8 cannot update to android 6.0. Please Help

Hello,
I have a HTC M8 rooted (Super SU) with TWRP Recovery and Android ver. 5.0.1, Software ver. 4.19.111.4, Baseband ver. 1.25.2145000021.06G_20.68.4196t.01_F.
Last couple of days, I received a notification to update for android 6.0, but after I downloaded the update and press to "install now", the phone always restarted to TWRP recovery and do not install the update. Any Idea Why ?!!!.
Could any one help me to install the update?
Thanks

moh19814 said:
Hello,
I have a HTC M8 rooted (Super SU) with TWRP Recovery and Android ver. 5.0.1, Software ver. 4.19.111.4, Baseband ver. 1.25.2145000021.06G_20.68.4196t.01_F.
Last couple of days, I received a notification to update for android 6.0, but after I downloaded the update and press to "install now", the phone always restarted to TWRP recovery and do not install the update. Any Idea Why ?!!!.
Could any one help me to install the update?
Thanks
Click to expand...
Click to collapse
Replace the recovery to stock recovery and relock the bootloader. If you installed the modified firmware, reflash the stock firmware, you will be good

Cashreedhar said:
Replace the recovery to stock recovery and relock the bootloader. If you installed the modified firmware, reflash the stock firmware, you will be good
Click to expand...
Click to collapse
how to replace recovery with the stock one. Where I can find it.
Do i lose all my application data doing so.
No, I am using the stock firmware, so I suppose no need to reflash it.
Thnaks

moh19814 said:
how to replace recovery with the stock one. Where I can find it.
Do i lose all my application data doing so.
No, I am using the stock firmware, so I suppose no need to reflash it.
Thnaks
Click to expand...
Click to collapse
Here you should find the stock recoveries: http://www.andromods.com/download-files/htc-one-m8-stock-recovery-verizon-sprint-att-tmobile.html
download the right recovery.img file and follow these instruction on how to flash - http://androiding.how/how-to-install-twrp-recovery-via-fastboot/ - in this just change the twrp recovery.img to the one you downloaded and run the code in command prompt.
It is recommended to do I clean install to avoid any further reported errors. Once you relock the bootloader you will lose all the data (like hard reset).

Cashreedhar said:
Here you should find the stock recoveries: http://www.andromods.com/download-files/htc-one-m8-stock-recovery-verizon-sprint-att-tmobile.html
download the right recovery.img file and follow these instruction on how to flash - http://androiding.how/how-to-install-twrp-recovery-via-fastboot/ - in this just change the twrp recovery.img to the one you downloaded and run the code in command prompt.
It is recommended to do I clean install to avoid any further reported errors. Once you relock the bootloader you will lose all the data (like hard reset).
Click to expand...
Click to collapse
Thanks again for the info.
Unfortunately, I could not find the right stock recovery in the link you provided, so I use another one: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
However, I have to ask, if I am on stock firmware; only rooted through SuperSU and with TWRP recovery,
do I need to reinstall (reflash) or restore to sotck firmware as in steps # 7 to 9 in the post (link) I added, or
can I directly flash the stock recovery and then relock the bootloder and start downloading the update 6.0
Thank.

moh19814 said:
Thanks again for the info.
Unfortunately, I could not find the right stock recovery in the link you provided, so I use another one: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
However, I have to ask, if I am on stock firmware; only rooted through SuperSU and with TWRP recovery,
do I need to reinstall (reflash) or restore to sotck firmware as in steps # 7 to 9 in the post (link) I added, or
can I directly flash the stock recovery and then relock the bootloder and start downloading the update 6.0
Thank.
Click to expand...
Click to collapse
you can directly flash

moh19814 said:
Thanks again for the info.
Unfortunately, I could not find the right stock recovery in the link you provided, so I use another one: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
However, I have to ask, if I am on stock firmware; only rooted through SuperSU and with TWRP recovery,
do I need to reinstall (reflash) or restore to sotck firmware as in steps # 7 to 9 in the post (link) I added, or
can I directly flash the stock recovery and then relock the bootloder and start downloading the update 6.0
Thank.
Click to expand...
Click to collapse
First thing .. you cannot do OTA with a rooted stock ROM, you need a non-rooted ROM.
Secondly .. there is no need to relock bootloader - read the note in my thread.
Just read again post #1 and follow all the 14 steps, you should be fine.
Anything, you can ask in my thread as I'm not following your thread.

ckpv5 said:
First thing .. you cannot do OTA with a rooted stock ROM, you need a non-rooted ROM.
Secondly .. there is no need to relock bootloader - read the note in my thread.
Just read again post #1 and follow all the 14 steps, you should be fine.
Anything, you can ask in my thread as I'm not following your thread.
Click to expand...
Click to collapse
thanks a lot for the info