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
Related
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
Hi, sorry if this is a stupid question, but I just noticed Sprint pushed an OTA for 6.0.1 to my stock rooted device (S-on) and I'm just trying to figure out what the best way to get this OTA is going to be. I'm assuming I shouldn't download and install the OTA as-is due to the TWRP recovery and root.
After looking around a bit, it seems like the only option available is to use a stock 6.0.0 RUU file in the bootloader and basically reset the entire device back to factory settings (losing all apps and data in the process presumably), installing the OTA, then re-flashing TWRP and re-rooting.
I guess what I'm asking is - 1. is this the correct way to go about doing this? and 2. is there any better alternative perhaps that doesn't involve losing my data?
Thanks in advance guys.
Been googling around for the last few days and scouring this board for just as long and still haven't come to a definitive conclusion. From what little I've seen the documentation on this seems kind of spotty and I'm just wondering which direction to head in. Any help on this would be much appreciated.
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Thanks for the reply, man.. Thats kind of what I had gathered pouring over all these articles and board posts. I went ahead and RUU'd back to 1.10.651.1 for sprint.. Literally just moments ago though I downloaded the OTA and hit install and got presented with an error screen during the update. Phone rebooted back into the system normally, and I went to check the version # only to see it unchanged, along with a prompt to install the OTA for 1.57.651.1 again.
Any idea why this might've happened or how to remedy 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"
}
Wonders_Never_Cease said:
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Click to expand...
Click to collapse
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Wonders_Never_Cease said:
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Click to expand...
Click to collapse
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
txag2011 said:
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Click to expand...
Click to collapse
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Wonders_Never_Cease said:
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
Click to expand...
Click to collapse
Cool glad got it sorted...
txag2011 said:
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Click to expand...
Click to collapse
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Wonders_Never_Cease said:
Cool glad got it sorted...
Click to expand...
Click to collapse
First thing ya need to do is read how to install adb and fastboot and get away from toolkits... Download 2.67 from this thread...copy to device flash through twrp...
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
And didnt mean that in a snotty,sarcastic way... Those tools sometimes cause issues that could be avoided is all I was getting at...
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
I have to agree with Wonders_never_cease about the toolkits. I have used many different ones and they are great from a few things but not all things go right using them unlike adb/fastboot. You should have better results from using adb/fastboot here.
That being said.....it would be easier to achieve root by simply going to full stock using RUU or system/boot.img in fastboot, flashing TWRP, format data, reboot into TWRP, flash supersu 2.74 from your SD card either by itself to obtain normal root or follow steps here http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 for systemless root. it's that simple...or at least was for me. I never could get pushing supersu through adb right or to work really.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
Bond246 said:
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
Click to expand...
Click to collapse
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
mcbright80 said:
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
Click to expand...
Click to collapse
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Bond246 said:
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Click to expand...
Click to collapse
Ah so sorry, it was 4 am when i was replying so i missed that part on it installing correct, or confused it with the other question i was replying to at that same time haha......anyhoo....i looked for you as well and nothing was found on my end as well so I think you may be in the exact situation i was in when i bought the sprint variant of the A9. HTC has faults like all companies but the one that really pisses me off is their lack of proper support on ALL variants especially concerning firmware. The phone was released and i found NO RUU on their site or anywhere online and of course not many people had my specific variant which meant no one on here or anywhere had the means to get me the stock firmware i too needed to restore my phone.
The ONLY reason anyone here, who has SPRINT US VERSION, is able to then and NOW get the RUU on the HTC website is directly due to my incessant badgering and yelling at HTC damn near daily about having a handset on the market for sale but no firmware for it in case of tech service needs. You may have to do the same thing sadly.
I assume you have checked htc UK site for the rom downloads......contact their tech support and see whats up. Till then, like i had to when the sprint version came out....you'll have to just keep checking back on here and anywhere online for someone else who may post what you need or some other kind of solution.
Thanks mcbright80,
as you already said, HTC resists and says RUUs are only available in the US. I'm excited on their reaction that there are still lower RUU-versions of my UK-edition.
It is an annoying mess with all these different versions for tons of carriers, countrys and so on.
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
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?
I tiried to flash the new oxygen pie beta. For whatever reason something went wrong and now here I am.
First time i flashed the beat I got the "Your device is corrupt" error. It's not the typical unlocked boot loader error. The explanation point is red, there is no mention of unlocked bootloader and I need to press power button in order to proceed. I tried flashing again at this point and I wiped everything in TWRP, but that didn't help.
Afterwards I have decided to go back to oreo and just upgrade to pie by local upgrade, but after flashing oreo I still get the red "your device is corrupt". However, I can still boot to the oxygen os and it seem to be working fine.
think its the encryption so reformat the data partition and start from scratch
RiTCHiE007 said:
think its the encryption so reformat the data partition and start from scratch
Click to expand...
Click to collapse
Formatted data and wiped everything. Flashed the pie beta. I can boot to the os, but I still get the error..
RiTCHiE007 said:
think its the encryption so reformat the data partition and start from scratch
Click to expand...
Click to collapse
I am decrypt and still get the same warning. I'm sure it'll be fixed later.
mikex8593 said:
I am decrypt and still get the same warning. I'm sure it'll be fixed later.
Click to expand...
Click to collapse
Thing is I still got that error when I went back to 8.1, which suggests it's not the android pie issue. Well, phone is working fine so I guess I will live for now.
Edit:
Something is messed up as I can't pass safetynet, CTS profile fails
Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.
Can you post the link to the file?
Barsky said:
Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.
Click to expand...
Click to collapse
Guess it is actually form Oneplus site:
https://forums.oneplus.com/threads/...ficial-oxygen-os-roms-and-ota-updates.835607/
In rollback builds under Signed flashable zips (Android P Developer Preview)
Your device will work by hitting power twice at the red text/corrupt still but you can fix it so that your on Beta without it.
Anyone thats getting corrupt device/red text during boot after flashing this beta or any other I have figured the only solution I know of possible atm to get around it so you can have beta's without the error. You will need to use the unbrick tool to totally clear your device from anything that is causing the issue and after that update your phone through settings as normal with no issue. Here is the tool and info for anyone who needs it:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Every other way possible tried nothing else worked for me but this. Your device will be in the same state basically as it was in the box so *totally* cleaned.
{
"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"
}
Nameless said:
Your device will work by hitting power twice at the red text/corrupt still but you can fix it so that your on Beta without it.
Anyone thats getting corrupt device/red text during boot after flashing this beta or any other I have figured the only solution I know of possible atm to get around it so you can have beta's without the error. You will need to use the unbrick tool to totally clear your device from anything that is causing the issue and after that update your phone through settings as normal with no issue. Here is the tool and info for anyone who needs it:
https://forum.xda-developers.com/one...ional-t3798892
Every other way possible tried nothing else worked for me but this. Your device will be in the same state basically as it was in the box so *totally* cleaned.
View attachment 4587785
Click to expand...
Click to collapse
The URL you shared is giving 404 error
Please share correct URL
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
This worked for me , back to stock , then try PIE again
:good:
soldier1 said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
This worked for me , back to stock , then try PIE again
Click to expand...
Click to collapse
So you are now back to P beta 1 without the error? Hmm. I got my phone back to 8.1 without the area. But once I flashed it again, the same thing came back.
Thanks
Ended up using qualcomm tool, then flashed P beta 1, then unlocked bootloader, installed twrp, installed magisk7. Everything is good now.
Flashing stock didn't help me, I still had the error. I used the qualcom tool and now I'm on pie without the error.
Barsky said:
Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.
Click to expand...
Click to collapse
Also had the same and flashing back the roll back package fixed it, definitely keeping this zip!
Spoke too soon got the corrupt message after going back to 5.1.11 then to oos beta 1 so had to use the unbrick tool instead.
my guess is that the bootloader can not tell if phone is bootloader locked or unlocked. Has any1 tried flashing the bootloader files to see if that could fix it without debrick tool?
mati11233 said:
Thing is I still got that error when I went back to 8.1, which suggests it's not the android pie issue. Well, phone is working fine so I guess I will live for now.
Edit:
Something is messed up as I can't pass safetynet, CTS profile fails
Click to expand...
Click to collapse
No its not, safetynet will not pass, says so even in changelog
Yeah i got the same error, only solution for me was to use unbrick tool
Flash OOS Beta over H2OS beta, no need to wipe data between the two. But it works wonders.