Database Info

[RUU/ROM] Final Gingerbread OTA Build 2.11.605.5 (Untouched and Rooted versions)

Official Final GingerBread RUU Released
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thunderbolt owners have been waiting a long while to get Gingerbread -- too long, considering this phone was once Verizon's flagship. We've seen several leaked builds come around, all of which experienced a variety of problems. The most recent leak seemed to be the most stable so far, but it was still chock-full of annoying little bugs.
Fortunately, we've gotten a hold of a newer build (2.11.605.5) that fixes a lot of the issues from the 605.3 build, so HTC is clearly heading in the right direction.
Here's a summed up version of what's new in this build:
• HTC Logger removed
• Voicemail notification fixed
• Front facing camera/Gtalk fixed
• MMS/SMS Fixes
• Weather syncing fixes
• ...and more
Sound good? I thought it might. Head below for download and installation instructions.
Click to expand...
Click to collapse
Installation Instructions​
• After downloading it, rename it to "PG05IMG.zip"
-Note: If you're doing this from a Windows machine, make sure you don't rename the file "PG05IMG.zip.zip," as Windows hides known file extensions by default.
• Drop the file on the root of the SD Card
• Turn off your device
• Hold Volume Down + Power to reboot into the bootloader -- the file should automatically be detected and the flashing process will begin.
• Wait for your device to complete the process and reboot
Click to expand...
Click to collapse
Source
Download (RUU)
Mirror 1
Mirror 2
Mirror 3
Mirror 4
Download (Rooted/Odex)
Download (Rooted/Deodexed/Zipaligned)

I assume it's not rooted? And if not, can it be rooted w/ revolutionary?
jv

johnnyv5 said:
I assume it's not rooted? And if not, can it be rooted w/ revolutionary?
jv
Click to expand...
Click to collapse
Follow these steps to achieve root:
1) Wipe data, cache, and dalvik (this will erase all your data so backup anything before this step)
2) Download Thunderbolt_Patched_hboot.zip from XDA by Shadowmite.
3) Open Thunderbolt_Patched_hboot.zip, you should see PG05IMG.zip inside. Take PG05IMG.zip and place it in the root of your microSD card. Reboot into Hboot.
4) It should detect PG05IMG.zip. Just install it. Then delete PG05IMG.zip
5) Download full RUU (from link in the OP) and rename the file to PG05IMG.zip and place it in the root of your microSD card (will lose root and clockworkmod).
6) Reboot into HBoot (Hboot should say UNLOCKED--highlighted in pink), it should detect PG05IMG.zip, install it, then delete PG05IMG.zip.
7) Download Clockworkmod (CWR5.0.2.1)PG05IMG.zip)
8) Rename the clockworkmod download to PG05IMG.zip. Place on root of your microSD card.
9) Reboot into HBoot, it should detect PG05IMG.zip, install it, then delete PG05IMG.zip. Now you have Clockworkmod.
10) Lastly, install Superuser (su-3.0.5-efgh-signed.zip) by downloading it from here. Place the file on your microSD and install Superuser from Clockworkmod. Reboot.
You are now flashed to the latest ROM, with root access, and clockworkmod.

How could I back up my app data if I'm not rooted?

Root is important to me, but not critical. I am installing this and then I will attempt the Revolutionary root method and report back ASAP.

Wait, how do you know this is the "final" build thats being released as an OTA update... has that process already started for some?

Sorry but another dumb question, if you are already rooted with Revolutionary shouldn't it block this RUU from overwriting hboot? I have old school root and my wife's tbolt has revolution.
jv

Finally! I'm curious where this was "found" though. Any ideas on when an official OTA might come in?

So far no rollout, at least not according to http://support.verizonwireless.com/system_update/thunderbolt.html. Still says it is coming soon. Curious if this is another "test" build like 605.0 and 605.1 were or if this is the one that will roll out. The update instructions on the vz site still have the picture showing 605.3 and the size of the .3 update, so that hasn't been updated either. Guess we will see in a couple days. In any case, thanks for the drop! It'll give me something to play with in the mean time.

rajuabju said:
Wait, how do you know this is the "final" build thats being released as an OTA update... has that process already started for some?
Click to expand...
Click to collapse
My mistake I didn't mean to say final (this is not a confirmed OTA yet). I have changed the title.
johnnyv5 said:
Sorry but another dumb question, if you are already rooted with Revolutionary shouldn't it block this RUU from overwriting hboot? I have old school root and my wife's tbolt has revolution.
Click to expand...
Click to collapse
Flashing an RUU will overwrite any previous HBoot you have unless you flash the patched HBoot I provided. That HBoot will never be rewritten and will remain unlocked even after full RUU flashes. I am not sure if Revolutionary already has this HBoot incorporated or uses the unlocked/unpatched version but I would recommend to follow the steps above and flash the patched HBoot so you won't have to worry.

johnnyv5 said:
Sorry but another dumb question, if you are already rooted with Revolutionary shouldn't it block this RUU from overwriting hboot? I have old school root and my wife's tbolt has revolution.
jv
Click to expand...
Click to collapse
Yes
Sent from my ADR6400L using xda premium

New ROM works great and is easily rootable via Revolutionary method. Cheers!

system6 said:
New ROM works great and is easily rootable via Revolutionary method. Cheers!
Click to expand...
Click to collapse
so if i am rooted i can just install this rom and root with revolution? we don't have to worry about creating bricks?

kidhudi said:
so if i am rooted i can just install this rom and root with revolution? we don't have to worry about creating bricks?
Click to expand...
Click to collapse
I can't promise anything there, but it worked for me. I just downloaded the SU file and ran it in recovery.....and ROOTED AGAIN.
It was that easy.

kidhudi said:
so if i am rooted i can just install this rom and root with revolution? we don't have to worry about creating bricks?
Click to expand...
Click to collapse
Please be advised that the Revolutionary tool does not actually root your device. It only flashes the HBoot to an unlocked S-OFF version and optionally flashes Clockworkmod recovery. In order to gain root, must follow step 10 of the method I posted here: Link. After that you should be all set.

Why not wait till its deodexed ...probably by the end of the day.

open1your1eyes0 said:
Please be advised that the Revolutionary tool does not actually root your device. It only flashes the HBoot....
Click to expand...
Click to collapse
Now you're just going to confuse people !!
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
ponyboy82 said:
Any ideas on when an official OTA might come in?
Click to expand...
Click to collapse
No one here knows (unless they work in VZW's engineering or related group). If someone posts a date, take it with a grain of salt.... How many updates have EVER been released on time ?

hallstevenson said:
Now you're just going to confuse people !!
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
No one here knows (unless they work in VZW's engineering or related group). If someone posts a date, take it with a grain of salt.... How many updates have EVER been released on time ?
Click to expand...
Click to collapse
Very true, on both counts. Point taken. So... maybe another year or so for VZW to push this out?

ponyboy82 said:
Very true, on both counts. Point taken. So... maybe another year or so for VZW to push this out?
Click to expand...
Click to collapse
Im betting 2 weeks after ICS code is released

Any bets on if restoring data will hose it? anyone, anyone?

[4.4 ROOT] SlapMyMoto 1.0 (Works with MotoWPNoMo)

My apologies for taking so long, life is hectic. This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4.
First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.
SlapMyMoto requires you to be on the 4.2.2 Camera update, you can find the firmware for your device below:
ATT- http://sbf.droid-developers.org/download.php?device=0&file=22
Verizon - http://sbf.droid-developers.org/download.php?device=0&file=55
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/showthread.php?t=2509590 or http://rootzwiki.com/topic/107098-root-rockmymoto-yes-even-the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Then either wait, or toggle your bluetooth. Once the device reboots, you will have root.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After taking the 4.4 OTA in step 3, if you then take on the 4.4.2 OTA update afterwards, the write protection off will be reverted and /system/ will once again be locked. There is no known way at this time to reverse this for users with locked bootloaders.
If you are on 4.2.x, you will be prompted for the 4.4 OTA update before getting the 4.4.2 OTA. You should complete step 4 before deciding to take on the 4.4.2 OTA or not.
Other relivent quotes from jcase:
jcase said:
XxSinisteRxX said:
The only thing i didn't understand was the "restore to 4.2.2 camera update" part, and [...] i'm already on 4.2.2.
Click to expand...
Click to collapse
[...]you skipped a step...
Rooted devices rarely handle OTAs very well, especially if they do not have a recovery anymore. Restore to [stock], and continue.
Click to expand...
Click to collapse
^(From another thread, but a comon question in this one)^
jcase said:
_litz said:
Quoting from Step 3: "Once the device has rebooted, please take the 4.4 OTA."
So what happens if the only OTA available is 4.4.2?
Click to expand...
Click to collapse
The device is not rooted at the step when you are taking the 4.4 OTA. The 4.4 update.zip is available from other sources and can be sideloaded in recovery.
Click to expand...
Click to collapse
_litz said:
FYI, for Verizon, I believe I've found the 4.4 update zip here :
http://downloadandroidfiles.org/download-blur_version-139-15-1-ghost_verizon-verizon-en-us-zip/
Click to expand...
Click to collapse
Possible mirror, not verified: magnet:?xt=urn:btih:CDARPSOTRY7CO4EY6K6SNWVASPBPX46S
jcase said:
_litz said:
Ok ... so what if you use the 0.5c method, where you replace the recovery with the customized boot image, that enabled write protection?
Click to expand...
Click to collapse
You can't boot a customized image.
_litz said:
Will that method work for 4.4.2 when it comes along?
Click to expand...
Click to collapse
No it won't work in 4.4.2, nor will it work with the 4.4 bootloaders.
Click to expand...
Click to collapse
jcase said:
lulajardim said:
I know you stated before that you have no intention on developing new root methods for the Moto X.
But is there any chance you have reconsidered and decided to take a look on 4.4.2?
Click to expand...
Click to collapse
No time, sorry.
No one mentions custom bootloader.
I am aware 0.5c works, but it has it's own flaws hence no longer beign available. Don't take OTAs with root, it is not a smart move.
JC
Click to expand...
Click to collapse
jcase said:
aviwdoowks said:
[What is] the benefit gained by this procedure.
Click to expand...
Click to collapse
Starting with the MotoX, Motorola started applying low level write protection to parts of the flash memory (in this case just /system). Root alone does not give us the ability to modify anything in system. My original hackjob that we used to bypass this has been fixed in Android 4.4. This is required if you want to actually install su into the /system partition.
Click to expand...
Click to collapse
jcase said:
tacitus54 said:
What happened to the flashing recovery.img, before taking the update to 4.4 and then flashing the 4.2.2 bootloader.
Click to expand...
Click to collapse
Previously we were using my workaround to write to system, now we are using MotoWPNoMo to gain write to system, as it is a better solution. No more recovery hackery needed.
Click to expand...
Click to collapse
Note: I will be reviewing threads and duplicating posts here to ease others finding them. PM me if you feel you have been misquoted or have something I missed.

You are the MAN!!! Amazing work!

Says he won't release a root method for 4.4, has to deal with whiny, entitled people that think he's selfish for doing so, and still ends up releasing something. Now that's what I call a class act.

i just went from 6 to midnight. damn, i love this community. now just need xposed for 4.4 and all will be right in the world.

10$ sent to you sir.
Thank you!

freak4dell said:
Says he won't release a root method for 4.4, has to deal with whiny, entitled people that think he's selfish for doing so, and still ends up releasing something. Now that's what I call a class act.
Click to expand...
Click to collapse
Actually, i didn't really release a new exploit, and I won't be. This is the same primary exploits as motoroot/rockmymoto/pwnmymoto, just instead of installing su, it plants a "backdoor". Since they allowed us to downgrade, we were able to do this.

jcase said:
Actually, i didn't really release a new exploit, and I won't be. This is the same primary exploits as motoroot/rockmymoto/pwnmymoto, just instead of installing su, it plants a "backdoor". Since they allowed us to downgrade, we were able to do this.
Click to expand...
Click to collapse
True, but a method is a method, in my eyes.
I gotta wonder if Motorola left the ability to downgrade as somewhat of a subtle way of making up to the community for not being able to unlock the AT&T and Verizon versions. They're just too good at making secure bootloaders to make me think that it was just overlooked.

Thank You!!!

Thank you for all the great and hard work you do for everyone in the consumer motox community.
I will not whine or nag, I will wait patiently until it is complete and ready. I don't have as much time for testing and tinkering like in the droidx days.
So again, jcase, thank you thank you!
Sent from my XT1060 using Tapatalk

wifi tethering
This is awesome news, however, does anyone know if wifi tethering works on 4.4? I've heard that it's broken on kk.

Thanks jcase! Rooting vzw on 4.4 worked great!

If I did these steps correctly, should I see the following message when opening SuperSU:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"

Do you mean gpt.bin and logo.bin? Those are only ones in the camera OTA. I really should have checked before pushing the setup.sh, cause now I just boot to fastboot and don't wanna flash the wrong thing.

Sinderan said:
Do you mean gpt.bin and logo.bin? Those are only ones in the camera OTA. I really should have checked before pushing the setup.sh, cause now I just boot to fastboot and don't wanna flash the wrong thing.
Click to expand...
Click to collapse
From the 4.2.2 camera firmware, I clarified in OP now.

jcase said:
From the 4.2.2 camera firmware, I clarified in OP now.
Click to expand...
Click to collapse
Ok, I thought so, but the .mismatched extensions made me a little nervous to flash.

Awesome! Can't test it yet though, as I am in Canada on Rogers and we haven't gotten the update yet. It's still a relief knowing that I can get root when I get the update though. Thanks!

goose71 said:
This is awesome news, however, does anyone know if wifi tethering works on 4.4? I've heard that it's broken on kk.
Click to expand...
Click to collapse
can anyone confirm this?

@jcase, i know we're waiting for an update/fix for the reboot recovery issue, but i thought i'd mention that step 5 didn't work as described for me:
Step 5)
adb push recovery.sh /data/local/tmp/setup.sh
adb reboot
(It will reboot, then quickly reboot straight to the bootloader)
Click to expand...
Click to collapse
the last part didn't happen. after pushing the recovery.sh file (to data local as setup.sh), then doing an adb reboot, the phone never automatically reboots to the bootloader. maybe i'm missing something though. are we supposed to "quickly reboot" or is this supposed to happen on its own?

mercado79 said:
@jcase, i know we're waiting for an update/fix for the reboot recovery issue, but i thought i'd mention that step 5 didn't work as described for me:
the last part didn't happen. after pushing the recovery.sh file (to data local as setup.sh), then doing an adb reboot, the phone never automatically reboots to the bootloader. maybe i'm missing something though. are we supposed to "quickly reboot" or is this supposed to happen on its own?
Click to expand...
Click to collapse
It is supposed to do it automatically, but the Verizon model is missing some dependency for this method.
Jcase said he has a fix and will work on it soon, but for now, do not do this on the Verizon model. Return to 4.2.2 for now.

Update arrived!

I am downloading an update that is 568.3 mb. GO GRAB IT!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Me too!
Manually went to update...

Update finally
AT LAST
Got it!!

5.1.1?

Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671

wildjeep said:
Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
Click to expand...
Click to collapse
You are 100% correct my friend... I hate when people hurry up and jump on the update, then complain non stop they lost root and can't get it back....
Sent from my SM-G925V using Xparent Green Tapatalk 2

Soooperstar said:
5.1.1?
Click to expand...
Click to collapse
+1

If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1

If anyone has taken the update, please report back on whether TWRP and/or Cf autoroot works

Sent from my SM-G925P using Tapatalk

dhonzik said:
If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1
Click to expand...
Click to collapse
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:

I will say, however, the device seems to run much smoother and early signs show battery improvement as well. Obviously it's early but it seems promising. Just wanted to share my stock experience as I chose to not root for the future payment platform

I updated but I am not root
no ram management .

If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?

Alpine- said:
If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?
Click to expand...
Click to collapse
Take a look at this thread: http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
It is not a looked boot loader that is the problem. T-Mobile solved it so I am sure it will be solved for us very soon.

wildjeep said:
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:
Click to expand...
Click to collapse
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.

dhonzik said:
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.
Click to expand...
Click to collapse
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery

Soooperstar said:
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery
Click to expand...
Click to collapse
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.

dhonzik said:
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.
Click to expand...
Click to collapse
Did you try to Odin our twrp?

Soooperstar said:
Did you try to Odin our twrp?
Click to expand...
Click to collapse
Yes, it was a no go, $75 later I'll have a new phone in a week

New AT&T OTA Update

I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.

yea i got it

Seanbest said:
I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.
Click to expand...
Click to collapse
It is the stage fright update
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app

Will we be able to flash it some other way?

ClearD said:
Will we be able to flash it some other way?
Click to expand...
Click to collapse
I'm sure there will be soon
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app

Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.

I confirm, it is a fix for Stagefright. Baseband version went from I337UCUFNJ4 to I337UCUFNJ5
+ SuperSU is working properly.
Below: Before & After the update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

New Update Came ..
https://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB419415&cv=820

ClearD said:
Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.
Click to expand...
Click to collapse
Were you rooted with the Flashfire method?

Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.

billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
nukesnooper said:
Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.
Click to expand...
Click to collapse
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.

billbillw said:
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.
Click to expand...
Click to collapse
That's exactly how I did it. My only concern is that it may install patches that could further restrict future modifications.
I also just completed running Lookout and it found no threats or vulnerabilities. I'm staying where I am until I hear more feedback.
Thanks for your advice. I'll be keeping an eye on it.

It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)

sim_pl said:
It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)
Click to expand...
Click to collapse
Please Upload .cfg File For Update My Device .. That OTA File /cache .. Check It And Upload It Please And Check fota Folder

UPDATED POST:
I upgraded with the install stock but "keep root" method, using flashfire...
The update failed at 29%.
I did a factory reset, and it still failed at 29%...
What are my options now?
Update:
I used Flashfire to install the tethering addon... I wonder if that is the culprit.
Installing without thethering... will update with results.
And It's a pain to download that ATT update each time. --- Their servers are SLOW!

Same story here. Update stops and phone reboots about a third of the way through. Defrosted all Samsung/AT&T bloat and tried again. Same story. Bummer.

I rooted my wife's 0C3 with Kingroot and tried to take the update. It failed.
Maybe I should try again since I just used triangle away to get rid of the "custom" nag at boot.
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network

billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Yes. Rooted with flashfire, on oc3 bootloader. I ran the update through the normal OTA method, not trying to install it through flashfire. It worked fine and root stayed normal. Verified when titanium backup ran last night on its normal schedule.

Well, it updated fine, using just the straight rooted rom, no additional flashes. No more fails at 29%...
It appears that adding in anything extra, de-bloat, hotspot enable, etc. will cause the update to fail.
/sk

Reinstalled the rooted stock ROM and the update worked fine. Still have root. All is groovy.

Root?

Is the zs551kl officially bootloader-unlockable and able to be rooted?
If that's the case, it would mean it's a much better phone than many of the latest flagships: sdcard, jack, FM radio, dual SIM, larger battery, stereo speakers, more complete GPS, good resolution screen, etc.

I haven't seen anything yet, but I assume it's coming. I don't think there will be a lot of roms though.

Let's pray that someone popup with that

rblanca said:
Let's pray that someone popup with that
Click to expand...
Click to collapse
Have you got this device? There is aTWRP available, but I'm not sure if anyone has successfully rooted, etc.

temporarium said:
Have you got this device? There is aTWRP available, but I'm not sure if anyone has successfully rooted, etc.
Click to expand...
Click to collapse
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader....but ASUS has made public the app to unlock the bootloader.
---------- Post added at 11:41 PM ---------- Previous post was at 11:33 PM ----------
temporarium said:
Have you got this device? There is aTWRP available, but I'm not sure if anyone has successfully rooted, etc.
Click to expand...
Click to collapse
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader neither install TWRP ....but ASUS has made public the app to unlock it.

rblanca said:
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader....but ASUS has made public the app to unlock the bootloader.
Click to expand...
Click to collapse
Have you tried this?
https://forum.xda-developers.com/zenfone-4-pro/development/recovery-twrp-3-1-1-0-zs551kl-t3692186
All you need is a way to flash root.

rblanca said:
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader....but ASUS has made public the app to unlock the bootloader.
Click to expand...
Click to collapse
Out of curiosity, what made you choose this phone over all the others? How do you like it so far? Pros\cons?

temporarium said:
Have you tried this?
https://forum.xda-developers.com/zenfone-4-pro/development/recovery-twrp-3-1-1-0-zs551kl-t3692186
All you need is a way to flash root.
Click to expand...
Click to collapse
No, because , like I said before...until we have a Rooted kernel available to download or a custom rom to install there is no point on install TWRP or unlock the bootloader....I'm pretty sure that in the next months there are going to be Roms and Custom Kernels (Rooted), it's too soon the phone was released on October (the past month).
About what made me chose this phone...it was
- Unlockeable Bootloader
- Snapdragon 835 as CPU
- 6 GB of Ram
- Good camera
- ASUS it's a good brand.
- FM raido
The phone its pretty damn fast...multitasking is amaizing...the battery dont seems so well like my, now broken, LG G5 but at least it runs for 1 day and a few hours but maybe its due the "new phone effect" (you play with it more the first days of use XD)

Magisk should give you root as long as bootloader can be unlocked.
I'll watch this space for root as I'm about to go get one myself because Snapdragon 835, then I have 15 days to test it on one game to decide whether to keep or return, lol.

motopig said:
Magisk should give you root as long as bootloader can be unlocked.
I'll watch this space for root as I'm about to go get one myself because Snapdragon 835, then I have 15 days to test it on one game to decide whether to keep or return, lol.
Click to expand...
Click to collapse
That's what I thought: once you unlock the bootloader and ADB-flash TWRP, you should be able to install SuperSU or Magisk (with corresponding manager app) and be good to go. So please test and let us know if you can.

temporarium said:
That's what I thought: once you unlock the bootloader and ADB-flash TWRP, you should be able to install SuperSU or Magisk (with corresponding manager app) and be good to go. So please test and let us know if you can.
Click to expand...
Click to collapse
Sorry to disappoint you but I'm not going to unlock my bootloader right now....the reason the phone its new (and expensive), there isn't a single rom to install or kernel to flash (on my LG G5 you have to flash another kernel in order to have root, but maybe that has change).
More importante there isnt any unbrick guide yet if something fails plus my phone it's not being selled on my country so there isn't any kind of warranty or repair service if something fails. WIth 6gb of ram I can deal with some ASUS apps pre installed so I dont need to root it right now.
But like a said before...its a great phone...damn faster one! i'll recommend it.

Even if one wanted to unlock the bootloader to try things out, it is not possible right now anyway.
Tried it with Asus' official unlock app (just got the phone today! :victory, and the app simply crashes before it even gets to talk to the bootloader, so there is currently no way to do it. Fastboot still reports the device as locked.
Maybe I should have tried it before applying the latest OTA update, but oh well!
rblanca has a point though, with no way to restore the phone should something go seriously wrong, I won't try any more exotic methods to try to crack open that bootloader at the moment either. The various guides that float around on the web look dangerous at best.

rblanca said:
Sorry to disappoint you but I'm not going to unlock my bootloader right now....the reason the phone its new (and expensive), there isn't a single rom to install or kernel to flash (on my LG G5 you have to flash another kernel in order to have root, but maybe that has change).
More importante there isnt any unbrick guide yet if something fails plus my phone it's not being selled on my country so there isn't any kind of warranty or repair service if something fails. WIth 6gb of ram I can deal with some ASUS apps pre installed so I dont need to root it right now.
But like a said before...its a great phone...damn faster one! i'll recommend it.
Click to expand...
Click to collapse
I understand your concern. No worries!

damnaliens said:
Even if one wanted to unlock the bootloader to try things out, it is not possible right now anyway.
Tried it with Asus' official unlock app (just got the phone today! :victory, and the app simply crashes before it even gets to talk to the bootloader, so there is currently no way to do it. Fastboot still reports the device as locked.
Maybe I should have tried it before applying the latest OTA update, but oh well!
rblanca has a point though, with no way to restore the phone should something go seriously wrong, I won't try any more exotic methods to try to crack open that bootloader at the moment either. The various guides that float around on the web look dangerous at best.
Click to expand...
Click to collapse
We'll just have to sit tight.

Root!
Good news!
Asus fixed the unlock app ( https://www.asus.com/de/Phone/ZenFone-4-Pro-ZS551KL/HelpDesk_Download/ ) and bumped it to version 9.1.0.0
It now successfully unlocks the device's bootloader. I went ahead and did it since I already voided my warranty when trying to unlock it with the previous, bugged version anyway.
Works fine, fastboot reports the bootloader as unlocked. Device contents got factory-wiped as per announced in the app, so make sure to back up your things if you wanna do it. :silly:
Edit:
Aaaaand rooted with Magisk.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After installing TWRP I just followed this guide here: https://forum.xda-developers.com/ze...ide-how-to-root-acces-magisk-manager-t3678678
Applies 1:1 to the Zenfone 4 Pro as well and worked flawlessly. :fingers-crossed:

Nice work! Does Android Pay work with magisk on this phone?

@bahua78
Android Pay isn't available in my country yet, so I can't test this. Maybe somebody else can find out. :0

Is it possible to update firmware via a memory card with root?