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?

[Q] Bricked, only fastboot is working

Hello.
My English is quite bad, and I'm sorry for that. Anyway, I hope that someone of you can help me with my problem, and will understand what I wanted to say.
So, at first I unlocked bootloader. After that, with InsecureBootandRoot script I wanted to root phone. When I did it, in "cmd" it stuck on "Daemon started successfully".
From then, I can't run my phone. Bootloader is working, fastboot USB aswell. I tried to install few recoverys, but none of them were working. ADB is also not working, it can't see my device(Probably because it's not working in fastboot. And if my phone is not in fastboot, computer don't recognise my device). Also, I can't "throw" any files to phone because computer see my device only in fastboot.
I tried to use HTC ONE S AIO kit . It show me my CID(HTC 0_32) and version(3.16.401.8), but that's all. Other commands are not working at all.
I also installed sdk and all drivers. That didn't help, meh.
Any ideas what should I do to have my phone working again? :c

Pisay said:
Hello.
My English is quite bad, and I'm sorry for that. Anyway, I hope that someone of you can help me with my problem, and will understand what I wanted to say.
So, at first I unlocked bootloader. After that, with InsecureBootandRoot script I wanted to root phone. When I did it, in "cmd" it stuck on "Daemon started successfully".
From then, I can't run my phone. Bootloader is working, fastboot USB aswell. I tried to install few recoverys, but none of them were working. ADB is also not working, it can't see my device(Probably because it's not working in fastboot. And if my phone is not in fastboot, computer don't recognise my device). Also, I can't "throw" any files to phone because computer see my device only in fastboot.
I tried to use HTC ONE S AIO kit . It show me my CID(HTC 0_32) and version(3.16.401.8), but that's all. Other commands are not working at all.
I also installed sdk and all drivers. That didn't help, meh.
Any ideas what should I do to have my phone working again? :c
Click to expand...
Click to collapse
There is no matching RUU, but i will upload you the matching boot+recovery. Will take some minutes. Download both files and flash them via fastboot.
DOWNLOAD

I should add that my phone is S3.
Anyway thanks for the answer, didn't knew someone is going to help me so fast :3.

pisay said:
i should add that my phone is s3.
Anyway thanks for the answer, didn't knew someone is going to help me so fast :3.
Click to expand...
Click to collapse
then dont flash the files. I'll have a look for the matching files.
Are you sure you have a ville c2 (S3) ??? Because 3.16.401.8 is the official EU S4 Jellybean release...
---------- Post added at 09:26 PM ---------- Previous post was at 09:17 PM ----------
LS.xD said:
then dont flash the files. I'll have a look for the matching files.
Are you sure you have a ville c2 (S3) ??? Because 3.16.401.8 is the official EU S4 Jellybean release...
Click to expand...
Click to collapse
You can see your model ID here:
{
"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"
}
Whats your MID??

oh well, I'm quite shocked.
When I bought this phone, they told me that it's 560e.
But I looked now, and it's Z520e.
Sorry for that, didn't knew that I have S4. Can you upload files for S4 again?

Pisay said:
oh well, I'm quite shocked.
When I bought this phone, they told me that it's 560e.
But I looked now, and it's Z520e.
Sorry for that, didn't knew that I have S4. Can you upload files for S4 again?
Click to expand...
Click to collapse
You're lucky LINK S4 files

If you say so ._.
I flashed them, what should I do now?

Pisay said:
If you say so ._.
I flashed them, what should I do now?
Click to expand...
Click to collapse
Phone should be fine again

Well, I still can't turn it on.
My computer still can't see him.
I can't describe it as "working phone" ;_;
Recovery also still not working.

Pisay said:
Well, I still can't turn it on.
My computer still can't see him.
I can't describe it as "working phone" ;_;
Recovery also still not working.
Click to expand...
Click to collapse
May you post a link to the software you have flashed to your phone?
Have you already tried PhilZ recovery? --> LINK

Dunno if I can paste links here.
Anyway I was trying to root my phone with this tutorial: http://theunlockr.com/2012/04/22/how-to-root-htc-one-x/ .
*Yeah, I'm stupid and I thought my phone is HTC ONE X, not HTC ONE S*
@edit
This recovery is also not working.
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4 <- I have this RUU on PC. Will it work on my phone?

You have the wrong CID for the RUU.
Sent from my beloved HTC One S using (most time buggy) Tapatalk
---------- Post added at 09:55 PM ---------- Previous post was at 09:55 PM ----------
Did you perform "factory reset" in bootloader Mode already?
Sent from my beloved HTC One S using (most time buggy) Tapatalk

Yeah, I already tried that. It stuck on logo then, like with recovery.

Pisay said:
Yeah, I already tried that. It stuck on logo then, like with recovery.
Click to expand...
Click to collapse
I have checked the link. The script "only" flashes a kernel (boot.img) + Superuser app. Flashing a new kernel should work for you. What command did you use to flash the boot.img ??

fastboot flash boot boot.img and then fastboot flash boot recovery.img
I'll try uninstalling sdk and all drivers, and then install them using tutorial from this forum. Maybe it will be easier, when adb will work .-.

Pisay said:
fastboot flash boot boot.img and then fastboot flash boot recovery.img
I'll try uninstalling sdk and all drivers, and then install them using tutorial from this forum. Maybe it will be easier, when adb will work .-.
Click to expand...
Click to collapse
Did you restart the bootloader after flashing? Have you cleared caches via fastboot also??
BTE adb will not help you without at least a working recovery...

Which command I should use to restart it?
And yeah, I cleared caches.
And thanks for trying to help me, I really appreciate it. U're wasting your time because some teenager destroyed his phone ._. . Oh god, I'm stupid.
@edit
When I tried to run bootloader, it showed me this:

Thats PhilZ CWM Perfect, you have a working recovery I'm off for 30 minutes. I can assisst you via Teamviewer when i'm back, if you want.
Sent from my beloved HTC One S using (most time buggy) Tapatalk

Not at all, these commands under it mean that anything in recovery won't work.
Also, from now I can't even start bootloader ._. .
Oh well, I'll just give this phone to the service. If they can't turn it on, and also turn on bootloader, can they say to me something like "Hey, you tried to change system of this phone so we won't give you another one"?. :c

Pisay said:
Not at all, these commands under it mean that anything in recovery won't work.
Also, from now I can't even start bootloader ._. .
Oh well, I'll just give this phone to the service. If they can't turn it on, and also turn on bootloader, can they say to me something like "Hey, you tried to change system of this phone so we won't give you another one"?. :c
Click to expand...
Click to collapse
Philz has a option to boot into bootloader. Have you tried it? If you give it to service they'll recognize that you have modified thze phone. As you were able to flash philz, you should also be able to flash boot+recovery image. Then you'll have to perform "factory reset + clear storage" to fix the sd card issue. I'm sure its possible! Once done you can install a rom manually or change the CID to run a stock RUU EU unbranded.
As your warranty is void I'd suggest to fix it o ya own

[Q] Has my phone been flashed?

I bought a Nexus 5 on ebay, advertised as factory reconditioned. However, I have a suspicion that the device has already been flashed as it is on Android version 4.4.4 and won't update to Lollipop. Here's a screenshot of the device info.
Are my suspicions confirmed?
{
"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"
}

itchyfeet said:
I bought a Nexus 5 on ebay, advertised as factory reconditioned. However, I have a suspicion that the device has already been flashed as it is on Android version 4.4.4 and won't update to Lollipop. Here's a screenshot of the device info.
Are my suspicions confirmed?
http://s7.postimg.org/gjbvvsggr/Screenshot_2014_12_18_20_33_10.png
Click to expand...
Click to collapse
From what I can tell it looks fine. Is there a small pad lock icon on the bottom of the screen when you boot the phone up? If the bootloader is unlocked, I'm pretty sure you won't get OTA updates. I could be wrong though.

I don't see a padlock icon during bootup - should there be one? If the phone wasn't flashed, then surely I should be able to get OTA update to Lollipop?

Rarscaryfrosty said:
From what I can tell it looks fine. Is there a small pad lock icon on the bottom of the screen when you boot the phone up? If the bootloader is unlocked, I'm pretty sure you won't get OTA updates. I could be wrong though.
Click to expand...
Click to collapse
My buddy left his nexus 7 unlocked and still got the 5.0 update. I think if you're rooted you won't get it.
---------- Post added at 10:43 PM ---------- Previous post was at 10:40 PM ----------
itchyfeet said:
I don't see a padlock icon during bootup - should there be one? If the phone wasn't flashed, then surely I should be able to get OTA update to Lollipop?
Click to expand...
Click to collapse
What do you mean by flashed? Every phone is "flashed". That's how they get android on the device. If it is refurbished, I wouldn't worry about it. It's probably stock, and you'll just have to wait for the update or do it yourself.

wolfen69 said:
My buddy left his nexus 7 unlocked and still got the 5.0 update. I think if you're rooted you won't get it.
---------- Post added at 10:43 PM ---------- Previous post was at 10:40 PM ----------
What do you mean by flashed? Every phone is "flashed". That's how they get android on the device. If it is refurbished, I wouldn't worry about it. It's probably stock, and you'll just have to wait for the update or do it yourself.
Click to expand...
Click to collapse
Sorry, what I mean is I think the phone has been rooted, which I really don't want. I presume the OTA updates has gone out to official Nexus 5's already, and the reason mine won't recognise an update is because it's been rooted.

itchyfeet said:
Sorry, what I mean is I think the phone has been rooted, which I really don't want. I presume the OTA updates has gone out to official Nexus 5's already, and the reason mine won't recognise an update is because it's been rooted.
Click to expand...
Click to collapse
Not every nexus 5 has gotten the update yet. Be a little patient. Or do it yourself.

Rarscaryfrosty said:
From what I can tell it looks fine. Is there a small pad lock icon on the bottom of the screen when you boot the phone up? If the bootloader is unlocked, I'm pretty sure you won't get OTA updates. I could be wrong though.
Click to expand...
Click to collapse
wolfen69 said:
My buddy left his nexus 7 unlocked and still got the 5.0 update. I think if you're rooted you won't get it.
Click to expand...
Click to collapse
OTA Updates arrive even if you are rooted and your Bootloader is unlocked. I received my OTA Update two days back though am rooted and my Bootloader is unlocked

keylocker said:
OTA Updates arrive even if you are rooted and your Bootloader is unlocked. I received my OTA Update two days back though am rooted and my Bootloader is unlocked
Click to expand...
Click to collapse
Cool. Shows how much I know. I just want people to chill out. ............

To find out if your bootloader is unlocked, boot into fastboot mode..from power off hold volume down and power button. It will say on the bottom if it is unlocked. There are apps that will check for root. Google them. There may be a chance that it was once rooted and/or unlocked but flashed back to stock and relocked. In this case the OTA should work just fine. As stated, you should receive notification of update regardless. If rooted or unlocked the OTA will fail when you try to install it.

If you are concerned about the state of the device I would learn how to flash factory images gotten straight from Google. This will completely wipe the device (your data and the ROM) and reinstall it from scratch. There are plenty of tutorials on how to do this and it will give you peace of mind that your device is, from a software perspective, in new condition.

Sekn said:
If you are concerned about the state of the device I would learn how to flash factory images gotten straight from Google. This will completely wipe the device (your data and the ROM) and reinstall it from scratch. There are plenty of tutorials on how to do this and it will give you peace of mind that your device is, from a software perspective, in new condition.
Click to expand...
Click to collapse
This was my exact thought as well. I figure if he had just purchased it, then why not just flash the 5.0.1 factory image and completely wipe the device and start fresh? It's the cleanest way to get the latest everything without having to mess with saving data etc.

keylocker said:
OTA Updates arrive even if you are rooted and your Bootloader is unlocked. I received my OTA Update two days back though am rooted and my Bootloader is unlocked
Click to expand...
Click to collapse
Yes you will being rooted has nothing to do with it. As long as you are running your stock Rom and recovery you will get them no problem.
Sent from my super duper HTC m8 custom beast machine
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
itchyfeet said:
I don't see a padlock icon during bootup - should there be one? If the phone wasn't flashed, then surely I should be able to get OTA update to Lollipop?
Click to expand...
Click to collapse
Did it say that the phone was rooted and bootloader unlocked when you bought it? Use this to see.
market://details?id=com.jrummyapps.rootchecker
http://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker
Either way if it's unlocked and rooted bonus but that will have nothing to do with ota updates. Unless you have a custom recovery installed. Try to boot into recovery and you'll know if it's stock is not
Sent from my super duper HTC m8 custom beast machine

wolfen69 said:
My buddy left his nexus 7 unlocked and still got the 5.0 update. I think if you're rooted you won't get it.
---------- Post added at 10:43 PM ---------- Previous post was at 10:40 PM ----------
What do you mean by flashed? Every phone is "flashed". That's how they get android on the device. If it is refurbished, I wouldn't worry about it. It's probably stock, and you'll just have to wait for the update or do it yourself.
Click to expand...
Click to collapse
Stop lying

str8str said:
Yes you will being rooted has nothing to do with it. As long as you are running your stock Rom and recovery you will get them no problem.
Sent from my super duper HTC m8 custom beast machine
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
Did it say that the phone was rooted and bootloader unlocked when you bought it? Use this to see.
market://details?id=com.jrummyapps.rootchecker
http://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker
Either way if it's unlocked and rooted bonus but that will have nothing to do with ota updates. Unless you have a custom recovery installed. Try to boot into recovery and you'll know if it's stock is not
Sent from my super duper HTC m8 custom beast machine
Click to expand...
Click to collapse
OTA`s will be downloaded but NOT installed if you have root privileges, you can flash factory images manualy though.

Go to the play store get root checker if you don't see a super.su app then most likely not
Turn off the phone hold vol down and power until you boot into fast boot use the volume keys as up and down scroll to recovery press the power button as enter if it pulls up twrp or clockwork mod then it has been rooted at one time if it pulls up a little android with its chest open saying waiting on command no custom recovery just hold down the power button for 10 seconds to reboot as normal

[ROM] SU4TL-49 100% Stock

SU4TL-49 Stock Image for XT1254: https://mega.nz/#!TwYShBCb!OFxwiUnUO2MiOHEVc8XluNP1uPSf5tTBaVdmyZ-mwSA
This package will flash every image in the SU4TL-49 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, download this: https://mega.nz/#!LwhxyCaZ!NZVi3pA77t7Qlxm1gFQr340SHurOAJEhDQsiR8QFbMc. Install it using the Install Image option in TWRP.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Deodexed version here for those who may want it: https://mega.nz/#!zxAEHJjS!hqNDjOGJoE3eI3rwL48h45Lovj764quxFsWP9IsN_Z4
If you need the full, non-TWRP version, here it is: https://mega.nz/#!ao4zmQQB!T2VClxKcTb-ePAhHotvlSR3NCxG0tRY1YEhMtti_H3k
If you get errors while flashing this, try using TWRP Mod 3 instead of Mod 4.

Used this today. Was coming from CM 13. Only notes I had are:
1. Make sure you use the Wipe from the main menu of TWRP and not just the available wipe after you install.
a. Caused my phone to boot but go black after this first half of the boot animation.
2. It asks to uninstall some Motorola services and that will persist. Not sure why but, I did uninstall them.
Overall, it works very well (only up and running 2.5 hours now so I'll have to wait and see if anything happens over the next day or so)
Thanks for this package and all your work...

Nice! Thanks a lot!

rjansen110 said:
Used this today. Was coming from CM 13. Only notes I had are:
1. Make sure you use the Wipe from the main menu of TWRP and not just the available wipe after you install.
a. Caused my phone to boot but go black after this first half of the boot animation.
2. It asks to uninstall some Motorola services and that will persist. Not sure why but, I did uninstall them.
Overall, it works very well (only up and running 2.5 hours now so I'll have to wait and see if anything happens over the next day or so)
Thanks for this package and all your work...
Click to expand...
Click to collapse
1. Yeah, that's kind of what I meant by the last sentence of the OP.
2. That always happens whenever you go from CM to stock. It's harmless.

So when I try to install this, it keeps coming back to me saying no OS is installed. I'm using twrp and have followed the instructions. Should I redownload the zip?
Sent from my XT1254 using XDA-Developers mobile app

joeriv5692 said:
So when I try to install this, it keeps coming back to me saying no OS is installed. I'm using twrp and have followed the instructions. Should I redownload the zip?
Sent from my XT1254 using XDA-Developers mobile app
Click to expand...
Click to collapse
I've seen that message before. I just rebooted to system anyway, and it booted just fine. Not sure why it shows up.

TheSt33v said:
I've seen that message before. I just rebooted to system anyway, and it booted just fine. Not sure why it shows up.
Click to expand...
Click to collapse
Ok, Ill give it a try. I was just afraid of moving forward and soft bricking my phone. Thanks alot.
---------- Post added at 07:56 PM ---------- Previous post was at 07:11 PM ----------
One more thing, If i flash the stock recovery for this....will it take TWRP off my phone? I cracked the **** out of my screen and having a replacement come in from Asurion tomorrow. And would this relock my bootloader? Im trying to make this phone bare stock the day I bought it with out going through computer. Is this possible?

Glad to see the return of @TheSt33v !! Thank you for your work!!
joeriv5692 said:
Ok, Ill give it a try. I was just afraid of moving forward and soft bricking my phone. Thanks alot.
---------- Post added at 07:56 PM ---------- Previous post was at 07:11 PM ----------
One more thing, If i flash the stock recovery for this....will it take TWRP off my phone? I cracked the **** out of my screen and having a replacement come in from Asurion tomorrow. And would this relock my bootloader? Im trying to make this phone bare stock the day I bought it with out going through computer. Is this possible?
Click to expand...
Click to collapse
the answers to "one more thing":
1) yes, if you flash stock recovery it will take TWRP off. 2) it will not relock your bootloader.
edit: ****** 3) it will *not* take away all traces you have modded/hacked/rooted
Stock.
NEXT DAY EDIT: i just restored pretty much stock 5.1 su-44. after all the uninstall crud there, i booted to twrp, and flashed this. all went perfectly. Thank you @TheSt33v !!!
{
"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"
}
[emoji92] [emoji95] [emoji95] [emoji95] [emoji95] [emoji109]
edit again: same line added to build.prop enables tethering on this build too.
net.tethering.noprovisioning=true

kitcostantino said:
Glad to see the return of @TheSt33v !! Thank you for your work!!
Click to expand...
Click to collapse
Haha the return? I didn't know I left. There just hasn't been all that much for me to do. Then again, the latest Witcher 3 expansion was running my life for the past few weeks, so maybe I did disappear.

TheSt33v said:
Haha the return? I didn't know I left. There just hasn't been all that much for me to do. Then again, the latest Witcher 3 expansion was running my life for the past few weeks, so maybe I did disappear.
Click to expand...
Click to collapse
TheSt33v said:
Now that we've got some Sunshine in our lives, sadly (not really) it is time for Turboid to be retired. We don't need it anymore.
I think that about covers it. Go forth and flash! Thanks for letting me play dev for a few months
Click to expand...
Click to collapse
Ha ha, brother. I guess i just took this post in the Turboid thread wrong.
-King of Unsolicited Advice

I did a system-only backup in TWRP after updating, so I don't think I need this, buuuut, never hurts to have a 2nd option! 44 did save my bacon so update was possible. ?

Thank you for the De-Odexed build!!!
-King of Unsolicited Advice

Has anyone had issues w this ROM or is it all good?

its all good.
-King of Unsolicited Advice

No luck with de-odexed version
De-odexed version seems to be causing Google Drive to fake load randomly. It'll be doing something, see it flash to Drive at the top with a blank page, then it goes back to what it was before. Was coming from a CM rom, but did do a factory reset via TWRP after installing the rom. Currently trying the non de-odexed version, just waiting for the install to finish.

yeah, i can confirm. same issue. the fix was wiping data for the app via TiBup. i use a transparent google drive, though, and had presumed it was just me.

sgeek7 said:
De-odexed version seems to be causing Google Drive to fake load randomly. It'll be doing something, see it flash to Drive at the top with a blank page, then it goes back to what it was before. Was coming from a CM rom, but did do a factory reset via TWRP after installing the rom. Currently trying the non de-odexed version, just waiting for the install to finish.
Click to expand...
Click to collapse
Weird. I forget, is Drive a system app in the stock rom? If so, maybe try removing it altogether with TiBu and reinstalling it from the play store?

It might be. The non de-odexed version is having no issues on my phone. Thanks for the idea just in case.

Hi, is this include the new .49 bootloader and radio package? or should I install it manually after flashing this rom?

Is anyone having issues with the play store crashing everything you start it up? I flashed the de-odexed and non-de-odexed but play store keeps crashing every time. Any ideas?
---------- Post added at 06:07 PM ---------- Previous post was at 06:05 PM ----------
snugroho3 said:
Hi, is this include the new .49 bootloader and radio package? or should I install it manually after flashing this rom?
Click to expand...
Click to collapse
It's included

Should we stay on stock for right now?

What should we do? For myself at this moment, I do not need root or custom roms. I have read many people recommending staying on stock for OTAs updates right now. The only reason I want TWPR is for the nandroid backups of the stock rom. Is it even possible to update stock, the OTA updates and reapply the unlock bootloader and TWPR afterwards? I know TWPR is still being working on at this moment. Also, is there even a stock rom [for FRD-AL04???] without root available through TWPR right now?
I believe I have FRD-AL04 which is the US/32 gig phone, right? Is this the correct model? Here is the link to amazon page.

Mine is the US 32gb black Honor 8 and model number is FRD-L04
Edit: Check your model number in the Settings > About Phone screen.
---------- Post added at 04:30 PM ---------- Previous post was at 04:22 PM ----------
On whether to stay stock or not... it's up to you. I unlocked my phone, which wipes it, then installed TWRP and SuperSU for root. Kept the ROM stock. But then I realized I forgot to do OTA updates first. Doing a quick update failed because TWRP didn't know what to do. I then selected a "Full Update" in the menu of the Updater. This actually completely wiped out my unlocked bootloader, recovery and root in one swoop. So now I am back to stock it seems so I'll have to unlock and start over if I want to redo it. But I'm not sure I am going to. I started using Helium made by the team that made ClockworkMod. It isnt able to back up ALL app data, but it does get a nice chunk of it which I think will be good enough for me for now.

Stay on stock until company stops pushing out OTA updates. I do this on all my phones.

tekkitan said:
Mine is the US 32gb black Honor 8 and model number is FRD-L04
Edit: Check your model number in the Settings > About Phone screen.
---------- Post added at 04:30 PM ---------- Previous post was at 04:22 PM ----------
On whether to stay stock or not... it's up to you. I unlocked my phone, which wipes it, then installed TWRP and SuperSU for root. Kept the ROM stock. But then I realized I forgot to do OTA updates first. Doing a quick update failed because TWRP didn't know what to do. I then selected a "Full Update" in the menu of the Updater. This actually completely wiped out my unlocked bootloader, recovery and root in one swoop. So now I am back to stock it seems so I'll have to unlock and start over if I want to redo it. But I'm not sure I am going to. I started using Helium made by the team that made ClockworkMod. It isnt able to back up ALL app data, but it does get a nice chunk of it which I think will be good enough for me for now.
Click to expand...
Click to collapse
Few questions if you don't mind.
1. Are you saying that even with unlocked bootloader and custom recovery you're still able to accept the OTA?
2. How would you restore the apps&data after accepting the OTA and going throu the unlocking/rooting process over again? Does Helium handle this w/o problems?
Thanks.

well, your question is complicated... but it has many type of sollutions
1.if its the nandroid backup is the only thing you want, then try backing up via honorsuit app,,
2.you can unlock the bootloader( dont worry you still be getting updates after this)
install twrp
make a backup
and find if someone did a backup with stock recovery
grab it
restore..
now you have your backup and youl be elligable for ota
3. if theres no one done a backup of stock recovery, dont worry... you can do it
unlock bootloader
now type fastboot devices
fastboot boot recovery twrp.img
this will temperorily boot twrp and you can have your backup
and BTW, you better be on stock, because, there is no stable custom rom yet and you are nearly getting a nougat update..:good:

mimin0 said:
Few questions if you don't mind.
1. Are you saying that even with unlocked bootloader and custom recovery you're still able to accept the OTA?
2. How would you restore the apps&data after accepting the OTA and going throu the unlocking/rooting process over again? Does Helium handle this w/o problems?
Thanks.
Click to expand...
Click to collapse
1. Yes, but only if you select the FULL download update in the menu of the updater (which says it's around 1.6GB). This will wipe out your unlock, TWRP and root though. At least it did for me.
2. I don't know, I didn't re-unlock it because it was going to wipe my phone again. I decided to stay stock for now using Helium backup to backup my apps, SMS, etc.

tekkitan said:
Mine is the US 32gb black Honor 8 and model number is FRD-L04
Edit: Check your model number in the Settings > About Phone screen.
---------- Post added at 04:30 PM ---------- Previous post was at 04:22 PM ----------
I started using Helium made by the team that made ClockworkMod. It isnt able to back up ALL app data, but it does get a nice chunk of it which I think will be good enough for me for now.
Click to expand...
Click to collapse
I can't even get Helium to get past asking me for PTP mode on my H8. Even though I select PTP in the notifications and/or in the dev settings.

scoobydu said:
I can't even get Helium to get past asking me for PTP mode on my H8. Even though I select PTP in the notifications and/or in the dev settings.
Click to expand...
Click to collapse
I also had this problem at first. I ended up having to switch from using their chrome add-on to installing the client for my OS (OS X in my case). So if you're using the chrome add-on try installing one of the clients instead.

tekkitan said:
I also had this problem at first. I ended up having to switch from using their chrome add-on to installing the client for my OS (OS X in my case). So if you're using the chrome add-on try installing one of the clients instead.
Click to expand...
Click to collapse
Ok thanks, but I am already using the OSX app myself. Managed to get it to work just now, had to reboot and now can't get it to work again. Some say to select 'midi' instead of ptp to get it to work, but that doesn't work for me either. Seems its a timing thing and I have't worked it out yet.
Not having a cross platform backup mechanism certainly doesn't help people stay stock without root imho.