I don't need help with this, my phone is S-OFF, SuperCID and the lot, however, I'd still like to know why we can't install OTA's manually, from the stock recovery while S-ON.
Over at a Swedish forum, a lot of people have reported that installing the latest OTA manually does not work, period. They enter the stock recovery, press and hold power and volume up, and choose to install the OTA. However, the phone reboots. CID is matching, so no issue there.
Why do you need to be S-OFF when installing an OTA manually, with the stock recovery?
Theshawty said:
I don't need help with this, my phone is S-OFF, SuperCID and the lot, however, I'd still like to know why we can't install OTA's manually, from the stock recovery while S-ON.
Over at a Swedish forum, a lot of people have reported that installing the latest OTA manually does not work, period. They enter the stock recovery, press and hold power and volume up, and choose to install the OTA. However, the phone reboots. CID is matching, so no issue there.
Why do you need to be S-OFF when installing an OTA manually, with the stock recovery?
Click to expand...
Click to collapse
Interested, subscribed. @Sneakyghost any ideas?
Sent from my iPod touch using Tapatalk
Could be security needs to actually be on to flash the OTA. Seen that before.
signatures are for girls
Sneakyghost said:
Could be security needs to actually be on to flash the OTA. Seen that before.
signatures are for girls
Click to expand...
Click to collapse
But as @Theshawty said, and I have seen once, when my phone was new, one can't flash an OTA manually on a completely stock phone which is s-on. So, security needs to be off. For HTC signed stuff. Now, the question is why..
n1234d said:
But as @Theshawty said, and I have seen once, when my phone was new, one can't flash an OTA manually on a completely stock phone which is s-on. So, security needs to be off. For HTC signed stuff. Now, the question is why..
Click to expand...
Click to collapse
Exactly. My little brother even tested on his completely unmodified phone.
Sent from my HTC One using Tapatalk
Theshawty said:
I don't need help with this, my phone is S-OFF, SuperCID and the lot, however, I'd still like to know why we can't install OTA's manually, from the stock recovery while S-ON.
Over at a Swedish forum, a lot of people have reported that installing the latest OTA manually does not work, period. They enter the stock recovery, press and hold power and volume up, and choose to install the OTA. However, the phone reboots. CID is matching, so no issue there.
Why do you need to be S-OFF when installing an OTA manually, with the stock recovery?
Click to expand...
Click to collapse
I faced this annoying problem and tried every thing but finally i found that this is due to ( preload ) folder and its content was deleted from data
So u can put them back and apply right permissions and it will work without any problem
If u don't have backup of preload folder, tell me and i will upload it to you when go home
Sent from my HTC One using Tapatalk
mido.fayad said:
I faced this annoying problem and tried every thing but finally i found that this is due to ( preload ) folder and its content was deleted from data
So u can put them back and apply right permissions and it will work without any problem
If u don't have backup of preload folder, tell me and i will upload it to you when go home
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Preload folder? What do you mean exactly?
I don't need it as I don't run stock and worry about OTA's. I'm a custom ROM kind of guy. I want to know for everyone else. Like I said, my little brother tried this with his phone and he hasn't rooted or unlocked or anything, yet he can't apply the OTA. It either says "wrong CID" or just reboots. His CID is correct, though.
Hmm, are there any HTC experts who could answer this?
@beaups @jcase @EddyOS
Theshawty said:
Preload folder? What do you mean exactly?
I don't need it as I don't run stock and worry about OTA's. I'm a custom ROM kind of guy. I want to know for everyone else. Like I said, my little brother tried this with his phone and he hasn't rooted or unlocked or anything, yet he can't apply the OTA. It either says "wrong CID" or just reboots. His CID is correct, though.
Click to expand...
Click to collapse
/data/preload gets deleted when you unlock using HTCdev, the 1.xx can be found here: http://forum.xda-developers.com/showthread.php?t=2200628
this used to interfere with 1.xx and 2.xx OTA updates, but shouldn't be a problem in 3.xx+ OTAs as they are no longer checked.
But still, I don't understand why the OTA can't be applied.... i'm not sure, but i do think people were able to manually install OTAs even with S-On (I could very well be wrong), but the fact that it says "wrong CID" would lead me to believe it's the wrong OTA file.
do you have his "fastboot getvar all" and which OTA he's trying to apply?
nkk71 said:
/data/preload gets deleted when you unlock using HTCdev, the 1.xx can be found here: http://forum.xda-developers.com/showthread.php?t=2200628
this used to interfere with 1.xx and 2.xx OTA updates, but shouldn't be a problem in 3.xx+ OTAs as they are no longer checked.
But still, I don't understand why the OTA can't be applied.... i'm not sure, but i do think people were able to manually install OTAs even with S-On (I could very well be wrong), but the fact that it says "wrong CID" would lead me to believe it's the wrong OTA file.
do you have his "fastboot getvar all" and which OTA he's trying to apply?
Click to expand...
Click to collapse
Believe me when I say this, mate, it IS the right OTA. I opened the OTA myself using winRAR and confirmed that the CID HTC__Y13 is supported (the android-info.txt in the OTA contains all SuperCID's (11111111, 22222222 etc) and all standard EU CID's and the Nordic HTC__Y13 CID).
The OTA is right, it's for the correct base. Everyone who tried to apply it over at Swedroid who were S-ON got the "check CID failed" and they all had unmodified phones (i.e. never been unlocked using HTCdev, never S-OFF'd, etc). Only the ones who had S-OFF could apply it without issues.
Theshawty said:
Believe me when I say this, mate, it IS the right OTA. I opened the OTA myself using winRAR and confirmed that the CID HTC__Y13 is supported (the android-info.txt in the OTA contains all SuperCID's (11111111, 22222222 etc) and all standard EU CID's and the Nordic HTC__Y13 CID).
The OTA is right, it's for the correct base. Everyone who tried to apply it over at Swedroid who were S-ON got the "check CID failed" and they all had unmodified phones (i.e. never been unlocked using HTCdev, never S-OFF'd, etc). Only the ones who had S-OFF could apply it without issues.
Click to expand...
Click to collapse
I do believe you
But strange indeed
nkk71 said:
I do believe you
But strange indeed
Click to expand...
Click to collapse
Yes, strange indeed. It's doesn't make any sense at all.
Theshawty said:
Yes, strange indeed. It's doesn't make any sense at all.
Click to expand...
Click to collapse
mixed results here too: http://android-revolution-hd.blogspot.com/2013/12/how-to-manually-install-ota-update.html
I'm gonna look back a bit, cause I remember people manually installing OTAs but can't remember if they were all S-Off. If I find something I'll let you know
cheers
---------- Post added at 05:27 PM ---------- Previous post was at 04:35 PM ----------
Well makes no sense whatsoever , but you are correct S-Off seems necessary to manually apply, here are a couple of threads:
http://forum.xda-developers.com/showthread.php?t=2500424
http://forum.xda-developers.com/showthread.php?t=2637699
summary: S-Off works fine, S-On -> CID mismatch and reboot
hmm, wondering what getprop("ro.cid") returns when in stock recovery, and selecting "apply ..."
maybe try an updater-script which outputs
getprop("ro.bootloader")
getprop("ro.cid")
getprop("ro.product.device")
getprop("ro.build.product")
Basically, I'm thinking that during a normal OTA update, the system reboots with a "proper" default.prop, whereas when you manually apply that info is not there (or incorrect/incomplete somehow), and the default.prop checks don't pass... just a thought
nkk71 said:
mixed results here too: http://android-revolution-hd.blogspot.com/2013/12/how-to-manually-install-ota-update.html
I'm gonna look back a bit, cause I remember people manually installing OTAs but can't remember if they were all S-Off. If I find something I'll let you know
cheers
---------- Post added at 05:27 PM ---------- Previous post was at 04:35 PM ----------
Well makes no sense whatsoever , but you are correct S-Off seems necessary to manually apply, here are a couple of threads:
http://forum.xda-developers.com/showthread.php?t=2500424
http://forum.xda-developers.com/showthread.php?t=2637699
summary: S-Off works fine, S-On -> CID mismatch and reboot
hmm, wondering what getprop("ro.cid") returns when in stock recovery, and selecting "apply ..."
maybe try an updater-script which outputs
getprop("ro.bootloader")
getprop("ro.cid")
getprop("ro.product.device")
getprop("ro.build.product")
Basically, I'm thinking that during a normal OTA update, the system reboots with a "proper" default.prop, whereas when you manually apply that info is not there (or incorrect/incomplete somehow), and the default.prop checks don't pass... just a thought
Click to expand...
Click to collapse
My first thought as to why the OTA might fail when S-ON is because there is a write protection on the system when security is on, but that shouldn't matter when you're in the recovery, right?
Theshawty said:
My first thought as to why the OTA might fail when S-ON is because there is a write protection on the system when security is on, but that shouldn't matter when you're in the recovery, right?
Click to expand...
Click to collapse
yeah i don't think that matters in recovery, and the OTA isn't even getting to that part (writing system)... you've obviously already taken a look at the updater-script and the CID check is like the 2nd or 3rd thing it checks, so the "/system/build.prop" fingerprint checks out, but CID fails.
i think ro.cid is just returning "" (nothing ), and due to S-On fails
i guess you could edit the OTA to include cid == "" and it could work... lemme check something....
nkk71 said:
yeah i don't think that matters in recovery, and the OTA isn't even getting to that part (writing system)... you've obviously already taken a look at the updater-script and the CID check is like the 2nd or 3rd thing it checks, so the "/system/build.prop" fingerprint checks out, but CID fails.
i think ro.cid is just returning "" (nothing ), and due to S-On fails
i guess you could edit the OTA to include cid == "" and it could work... lemme check something....
Click to expand...
Click to collapse
but if you edit the zip, you break the integrity of the zip, right?
Theshawty said:
but if you edit the zip, you break the integrity of the zip, right?
Click to expand...
Click to collapse
as far as i can tell, only the firmware.zip inside the OTA is encrypted and HTC signed; the OTA.zip itself, doesn't look encrypted (but possibly apk signed).
i can't test this code on the M7 at the moment (due to phone calls), but I did test it on the HTC Sensation (in custom recovery) and worked fine.
Code:
# output OTA check info
ui_print("Mounting /system");
mount("ext4", "EMMC", "system", "/system");
ui_print("ro.build.fingerprint=" + file_getprop("/system/build.prop", "ro.build.fingerprint") + "\n");
ui_print("ro.bootloader=" + getprop("ro.bootloader") + "\n");
ui_print("ro.cid=" + getprop("ro.cid") + "\n");
ui_print("ro.product.device=" + getprop("ro.product.device") + "\n");
ui_print("ro.build.product=" + getprop("ro.build.product") + "\n");
ui_print("-----------------------");
ui_print("bootloader check: " + is_ship_bootloader(getprop("ro.bootloader")) + "\n");
ui_print("cid check: " + check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "HTC__001" , "HTC__E11" ,
"HTC__102" , "HTC__203" , "HTC__405" , "HTC__Y13" , "HTC__304" ,
"HTC__032" , "HTC__A07" , "HTC__J15" , "HTC__016") + "\n");
ui_print("mid1 check: " + check_mid("full", "PN0710000") + "\n");
ui_print("mid2 check: " + check_mid("simple", "PN0710000") + "\n");
ui_print("device check: " + getprop("ro.product.device") + "\n");
ui_print("product check: " + getprop("ro.build.product") + "\n");
ui_print("Unmounting /system");
unmount("/system");
it should be run on a stock recovery to see what kind of output you get... if i get a chance later, i'll flash back a stock recovery and run it.
then it would have to be run on an S-On device, ...... if it doesn't allow it to run, then we'd need to apk sign it (or whatever the appropriate term is ), and see which check fails. that would at least narrow it down
well that did NOT go as expected
not only was i not able to to run that file using stock recovery (yeah, can't be that simple)... i also managed to wipe everything off my phone (before even attempting to apply that file.... i really don't get it, why does installing stock recovery sometimes wipe the phone completely???)
nkk71 said:
well that did NOT go as expected
not only was i not able to to run that file using stock recovery (yeah, can't be that simple)... i also managed to wipe everything off my phone (before even attempting to apply that file.... i really don't get it, why does installing stock recovery sometimes wipe the phone completely???)
Click to expand...
Click to collapse
Hmmm, really weird! What is up with this? Haha.
Theshawty said:
Hmmm, really weird! What is up with this? Haha.
Click to expand...
Click to collapse
not funny :silly:
once it happened to me... (hence i had a nandroid backup made just before and pulled it off the phone, cause the internal storage got wiped too)... and another time i flashed enough stock recoveries and messed with them, and nothing got erased. go figure
oh well, a couple of wasted hours, but i've never had so much free space on my internal storage
Related
Hi,
Thanks in advance for anyone who tries to help me.
A few weeks ago I tried to gain root access to HTC Eris. I followed the prereq and part one of the guide but stopped there. Rebooted my phone, checked the version (2.1) and went about reinstalling apps and such.
Now I want to install a different ROM so I went back and tried to start from the beginning and put PB00IMG.zip on my phone, went to hboot, let run but then I get the message "Main Version is older! Update Fail! Do you want to reboot device?"
So when I move onto III in the walk through, I get an error on the command
adb push flash_image /system/bin
It would seem like I've lost root right? Is there anyway I can check to see if I accidentally installed the leak w/o root?
Thanks,
Nate
Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.
I am anticipating the next question, so here is your answer. If you did indeed root your phone, you should have loaded a recovery image as jcase mentioned.
First, load the new ROM onto the root of your sd card. Next, power off your phone. Then, hold down the vol up button and turn on your phone. It should boot into the recovery console. From here to load another ROM, you need to perform a wipe and then load your new ROM by flashing. You should see a Wipe and Flash from Zip menu option in recovery.
In the Wipe menu, choose the first two options in order (factory reset and cache). Wait for each to complete. Next, pressing vol down should get you back to the main menu. From here choose Flash from Zip and then select the ROM zip file you loaded onto your sd card and wait for the update to complete. Last, reboot your phone from the menu.
jcase said:
Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.
Click to expand...
Click to collapse
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?
try su
xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.
jcase said:
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?
Click to expand...
Click to collapse
I followed a guide a few weeks ago that must have been for the leaked version of 2.1.
thisismyanonymousaccount said:
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.
Click to expand...
Click to collapse
I get
su: permission denied
Click to expand...
Click to collapse
I guess that means my phone I'm stuck with it...FML!
xnatex21 said:
I guess that means my phone I'm stuck with it...FML!
Click to expand...
Click to collapse
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.
g00gl3 said:
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.
Click to expand...
Click to collapse
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?
xnatex21 said:
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?
Click to expand...
Click to collapse
Technically, modifying your device would void warranties. Even if they could "restore" the device, it would still have the newer bootloader that is causing the rooting issue. Some people have "lost" or "broken" the device bad enough that they could get a replacement from Verizon. However, there is mixed results as to what bootloader the refurbished devices come back with.
I posted before about the safety of re-rooting my eris from 1.5 to a rooted 2.2 rom, and due to lack of responses on any forums over the web, I jumped the gun today. First off my Eris after un-rooting it, wouldn't take the OTA update for 2.1, it downloaded and verified that, but after it rebooted, it was still at 1.5 saying no new updates are available. I cannot download the eris 1 click root app as it's only for 2.1 I'm assuming because it says it's not compatible with 1.5 firmware when I download it. I tried to follow this guide [Walkthrough] From stock (1.5) to rooted 2.1 (update - new link) - xda-developers and when I installed the PB00IMG.zip it downloaded but failed to flash and the screen read "Main version is older". I tried this guide All-In-One Auto-Root Script - Page 4 - xda-developers and when it says it's flashing the root image, it goes straight to a screen with only two options "recovery" something and "fastboot". None of which are listed as options in the guides. I am just trying to root my 1.5 eris and flash the KaosFroyo V3 eris rom with Amon Ra's recovery image. Thanks if anyone can help my problem, or shed light on the situation! Sorry if there's been a fix to this problem already stated, I've desperately been browsing many forums and hundreds of replies to no avail. Thanks again.
It looks to me like you got a pretty reasonable answer to the same question over on Android Forums
bftb0
Hey everyone. I just received another update, FRG83D, on my mytouch. Does anyone got it? I forgot to check details. What for is this one?
I just got the prompt as well but I havent flashed it yet..... wonder what it is. It says its a security patch I believe but for who?? T-mobile or the end user. I noticed a thread on tmobile forums about someone losing usb tethering over this, he said they are trying to charge 14.99 a month to use it. If thats the case Ill be rooting once more.
O and I manually pushed the 2.2 ota so those of you wondering, yes you will get the update automated still. its a 9.6mb file.
Yes I flashed the update. I had my phone rooted and this update unrooted me so I re-rooted with the Super 1-click app. I saw that it was a security patch as well. I still have usb tethering and all that comes with froyo. So from what I know it is a security patch
Sent from my T-Mobile myTouch 3G using XDA App
I got the update too. When it rebooted to flash, it failed the signature check and didn't install. I guess it's because i have Amon RA recovery. My SPL is the perfected one 0013. Hmmmmm.
EDIT. So the update file is in my cache folder but my phone is ignoring it. When i check for updates it says "up to date". I have run the checkin service and made calls but still no more notification that i need to update. Can i flash this file myself using hboot? Do i need to rename the file? Hmmmmmm. Anyhow, i copied the file to my sdcard for safe keeping.
Saw in another thread that there is a new radio? Perhaps this is it?
firedude12 said:
I just got the prompt as well but I havent flashed it yet..... wonder what it is. It says its a security patch I believe but for who?? T-mobile or the end user. I noticed a thread on tmobile forums about someone losing usb tethering over this, he said they are trying to charge 14.99 a month to use it. If thats the case Ill be rooting once more.
Click to expand...
Click to collapse
I do not believe that is the case. I got the FRG83D and usb teather works if you 1st plug it in to your usb and activate the check box. I also have Super One Click Root working. Phone seems to run better
XfooYen said:
I got the update too. When it rebooted to flash, it failed the signature check and didn't install. I guess it's because i have Amon RA recovery. My SPL is the perfected one 0013. Hmmmmm.
EDIT. So the update file is in my cache folder but my phone is ignoring it. When i check for updates it says "up to date". I have run the checkin service and made calls but still no more notification that i need to update. Can i flash this file myself using hboot? Do i need to rename the file? Hmmmmmm. Anyhow, i copied the file to my sdcard for safe keeping.
Click to expand...
Click to collapse
Hmmm, I have the same issue (also running Amon RA 1.7).
I suppose we need an unsigned zip with Recovery removed (to flash and still keep Amon RA).
XfooYen said:
I got the update too. When it rebooted to flash, it failed the signature check and didn't install. I guess it's because i have Amon RA recovery. My SPL is the perfected one 0013. Hmmmmm.
EDIT. So the update file is in my cache folder but my phone is ignoring it. When i check for updates it says "up to date". I have run the checkin service and made calls but still no more notification that i need to update. Can i flash this file myself using hboot? Do i need to rename the file? Hmmmmmm. Anyhow, i copied the file to my sdcard for safe keeping.
Click to expand...
Click to collapse
thedrickster said:
Hmmm, I have the same issue (also running Amon RA 1.7).
I suppose we need an unsigned zip with Recovery removed (to flash and still keep Amon RA).
Click to expand...
Click to collapse
Uhhh, you need the oem recovery TO flash the ota update.
If you've modified your system directory in any way you won't pass security check. Have you installed/uninstalled/frozen with TB any system apps? If so, your update won't install.
The only thing I changed was removing amazon mp3 and that was enough to make my original update to 2.2 fail.
If you really want I can make a nandroid of 1.6 and post it up for you.
Phateless said:
Uhhh, you need the oem recovery TO flash the ota update.
Click to expand...
Click to collapse
Right, but I want to keep Amon_RA (and not mess around re-installing the OEM Recovery). I ended up removing the recovery component of the OTA zip, self signing and then flashed the zip from Amon RA.
All looks well.
thedrickster said:
Right, but I want to keep Amon_RA (and not mess around re-installing the OEM Recovery). I ended up removing the recovery component of the OTA zip, self signing and then flashed the zip from Amon RA.
All looks well.
Click to expand...
Click to collapse
Well aren't you slick! I was gong to suggest simply rerooting using superoneclick. That's what I did.
There is a procedure to fool OTA system in order to make it receive the OTA again. So you have a second chance to grab the filename and make a lot of people here happy
Update: Thanks to @Sleeepy2 we know this method works in the nexus 6 :good:
DISCLAIMER: It's an unharmed procedure, but be warned, you will change build.prop so anything (bad) should happen if you do it incorrectly, most probably a bootloop. If you have doubts, don't do it.
Needs to be rooted.
So if there is a brave enought one, the procedure is just to change two values of the /system/build.prop file to make it looks a previous android version for the OTA system.
For instance, If you have received to OTA to LMY47M your build.prop file will have these values:
ro.build.date.utc=1425686543
and
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys
If you change these lines by the equivalent lines from another version of android, the OTA system will check the OTA availability with the other android version. So, If before receiving the OTA your android version was 5.0.1 LRX22C you can change both lines with:
ro.build.date.utc=1416527965
and
ro.build.fingerprint=google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys
That are the LRX22C version lines.
Save build.prop file and reboot your nexus 6.
Once rebooted check for OTA updates (It will be checked as LMY47D) and download it, if it's not downloading yet (don't apply the OTA, just download it).
While it's downloading, or even after it's download, open a terminal emulator (for instance this one: https://play.google.com/store/apps/details?id=jackpal.androidterm) and execute these two commands (will ask for superuser permission):
su
logcat | grep zip
And wrote down the OTA link for us
When you finish just revert the build.prop changes done and delete the file /cache/update.zip (it's the OTA downloaded, and you don't need it), then reboot your system to leave it in it's normal situation.
Thank you very much in advance.
And, If you are kindly enough, you may check for the rest of OTAs from other android versions (the LMY47E OTA to LMY47M should be very useful too). Here are all known versions build.prop lines to play with:
Code:
LMY47M
ro.build.date.utc=1425686543
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys
LMY47I:
ro.build.date.utc=1425442825
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47I/1767468:user/release-keys
LMY47E:
ro.build.date.utc=1424577649
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47E/1748839:user/release-keys
LMY47D:
ro.build.date.utc=1424322888
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47D/1743759:user/release-keys
LRX22C:
ro.build.date.utc=1416527965
ro.build.fingerprint=google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys
LRX21O:
ro.build.date.utc=1415319727
ro.build.fingerprint=google/shamu/shamu:5.0/LRX21O/1570415:user/release-keys
LNX07M:
ro.build.date.utc=1414346119
ro.build.fingerprint=google/shamu/shamu:5.0/LNX07M/1543455:user/release-keys
-----
KXH21.6-F1.12:
ro.build.date.utc=1416355004
ro.build.fingerprint=motorola/shamu_factory/shamu:4.4.4/KXH21.6-F1.12/25:userdebug/release-keys
Most of them will give you old and known OTAs, but some will give new OTAs for all of us. And the final test build probably doesn't give any OTA
Thanks and best regards.
I changed by build.prop and rebooted and no update which I checked.
xpack90 said:
I changed by build.prop and rebooted and no update which I checked.
Click to expand...
Click to collapse
But you previously installed the LMY47M/E, no?
If yes, Please, wait several minutes and keep checking, you eventually must receive the OTA again before the rest of people.
Check too if build.prop file was correctly changed (sometimes a number is missing or something).
Thanks and best regards.
No sorry I thought this was for people who wanted the update not those who had it
xpack90 said:
No sorry I thought this was for people who wanted the update not those who had it
Click to expand...
Click to collapse
Don't worry and thanks for trying.
Rogers Canada
http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
Sleeepy2 said:
Rogers Canada
http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
Click to expand...
Click to collapse
First of all, thank you very much. Unfortunately that's one of the known OTAs.
You can see all known OTAs here:
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493
But as I said, thank you very much. You demonstrated the method works for Nexus 6 too
oops, yeah it is know. I didn't fully read and thought you just wanted confirmation that it works on the N6.
And yes it does
OK, I got the OTA you're looking for (47M) but am currently unlocked and not rooted. If I oem unlock and perform this, how do we know for sure that it will prompt me again for the OTA?
I'm certainly willing to try when I get home later this evening (if no one has posted it by then), but would hate for my data to get wiped for nothing ...
YankInDaSouth said:
OK, I got the OTA you're looking for but am currently unlocked and not rooted. If I oem unlock and perform this, how do we know for sure that it will prompt me again for the OTA?
I'm certainly willing to try when I get home later this evening (if no one has posted it by then), but would hate to for my data to get wiped for nothing ...
Click to expand...
Click to collapse
Unfortunately I cannot guarantee that you receive the OTA again.
In my opinion it shouldn't work because the GMS/GCS ID is used to check OTAs, and if you perform an "oem unlock" you will lose your data so a new GMS/GCS ID will be assigned to your device, making it a totally different device for google.
If I were you I shouldn't try. It's a pity, but I'm being sincere.
Thanks and best regards.
VivaErBetis said:
Unfortunately I cannot guarantee that you receive the OTA again.
In my opinion it shouldn't work because the GMS/GCS ID is used to check OTAs, and if you perform an "oem unlock" you will lose your data so a new GMS/GCS ID will be assigned to your device, making it a totally different device for google.
If I were you I shouldn't try. It's a pity, but I'm being sincere.
Thanks and best regards.
Click to expand...
Click to collapse
I appreciate you being straight up about it! I will hold off as I'd prefer not to lose my data and not be able to get the community what they want/need.
If only I had know that it would be this long before people started receiving the OTA I definitely would have held off on installing it!! Don't know why I was the "chosen one" LOL
YankInDaSouth said:
I appreciate you being straight up about it! I will hold off as I'd prefer not to lose my data and not be able to get the community what they want/need.
If only I had know that it would be this long before people started receiving the OTA I definitely would have held off on installing it!! Don't know why I was the "chosen one" LOL
Click to expand...
Click to collapse
Don't worry, the OTA will eventually show up, sooner or later. The real problem is our lack of patience
I've added the build.prop info for 5.1 LMY47I build. The OTA seems to be delivered for Australian users.
I've made simplier way to unlock the bootloader of ZE551ML/ZE550ML.
Update! Version 2.
Now it's not required to flash/downgrade droidboot.img. But you still need to flash one of compatible ROM.
Currently compatible versions are:
For ZE551ML: v2.19.40.18, v2.19.40.20, v2.19.40.22 and future newer versions unless opposite mentioned.
For ZE550ML: v2.19.40.12, v2.19.40.13, v2.19.40.23 and future newer versions unless opposite mentioned.
For example, you can flash full ROM v2.19.40.22 and then use unlocker v2.
Just unzip everything from attached archive and then start unlock_one_click_v2.bat
If you've enable USB debugging then phone will automatically reboot to bootloader and will unlock the bootloader. If you didn't enable USB debugging, then you need to reboot to bootloader manually (Turn the phone off and disconnect USB, then press Power+VolumeUp keys at the same time and keep it pressed till you see ASUS logo, then you may connect USB cable).
Either way, unlock_one_click_v2.bat will proceed to unlock in fully automated way.
If initial boot splash screen become inverted, then bootloader has been unlocked!
If you don't like white boot screen, then you can flash original black one:
http://forum.xda-developers.com/zen...-black-white-splashscreen-twrp-flash-t3141945
Originally, it's developed for WW firmware but should work on any region.
Works on CN firmware. Confirmed by @corrsea
Based on unlock method discovered by @shakalaca
Based on fastboot hack by @social-design-concepts
Version 1 (old)
To use this version, you need to flash ROM not older than v2.19.40.18 for ZE551ML, and v2.19.40.12 for ZE550ML. And then downgrade (if required) droidboot to compatible droidboot.img
Code:
fastboot flash fastboot droidboot.img
For ZE551ML, known compatible droidboot.img versions are 2.19.40.18, 2.19.40.20.
For ZE550ML, known compatible droidboot.img versions are 2.19.40.12.
Important note for Stock ROM lovers:
Although, unlocker v2 works with v2.19.40.22, there is no warranty, it will continue to work on future versions. It is up to ASUS decision. Unlocking process still requires several files from /system partition including special version of if.bin (/system/etc/firmware/if.bin). These files are still supplied with v2.19.40.22, but in the future they can be removed by ASUS together with disable of downgrade ability for if.bin.
So, if you will flash future stock ROM through official update procedure (which includes bootloader update - from ifwi.zip) then you may loose unlocked bootloader! And of course, ASUS may completely block unlocking procedure (at least unofficial way).
So, if unlocked bootloader is important for you, then
1) unlock it ASAP while current firmware allows.
2) don't use official updates. You need to remove all lines from update script containing ifwi.zip references and then flash through TWRP (you need to remove lines checking recovery version as well).
thank you very much for making this way easier, hope it will help many people, good job bro
@sorg, thanks for the tool. One ques. Will it wipe off the data? And does it keeps OTA taking ability or will it break off? If it breaks, what can be done to get it back?
itskapil said:
@sorg, thanks for the tool. One ques. Will it wipe off the data? And does it keeps OTA taking ability or will it break off? If it breaks, what can be done to get it back?
Click to expand...
Click to collapse
you will continue receiving OTA update.
---------- Post added at 05:20 AM ---------- Previous post was at 05:12 AM ----------
sorg said:
Important note for Stock ROM lovers:
Although, unlocker v2 works with v2.19.40.22, there is no warranty, it will continue to work on future versions. It is up to ASUS decision. Unlocking process still requires several files from /system partition including special version of if.bin (/system/etc/firmware/if.bin). These files are still supplied with v2.19.40.22, but in the future they can be removed by ASUS together with disable of downgrade ability for if.bin.
So, if you will flash future stock ROM through official update procedure (which includes bootloader update - from ifwi.zip) then you may loose unlocked bootloader! And of course, ASUS may completely block unlocking procedure (at least unofficial way).
So, if unlocked bootloader is important for you, then
1) unlock it ASAP while current firmware allows.
2) don't use official updates. You need to remove all lines from update script containing ifwi.zip references and then flash through TWRP (you need to remove lines checking recovery version as well).
Click to expand...
Click to collapse
Hi
Is there anyway other than installing a third-party recovery to verify if the boot-loader is unlocked or locked ?
will it void warranty of the phone.
If you unlock the bootloader it will void the warranty, as there's no way currently to lock the bootloader again.
Hi
Is there anyway other than installing a third-party recovery to verify if the boot-loader is unlocked or locked ?
will it void warranty of the phone.
Click to expand...
Click to collapse
Are there news for the ZE500CL version?
I currently have .22 via OTA, so I can just proceed with unlocking the bootloader without any issues? because in the other thread, they are still saying there is no way to unlock bootloader without downgrading to .20 or .18.. TIA!
jarjarbingie said:
I currently have .22 via OTA, so I can just proceed with unlocking the bootloader without any issues? because in the other thread, they are still saying there is no way to unlock bootloader without downgrading to .20 or .18.. TIA!
Click to expand...
Click to collapse
can you read what i've wrote in first post?
For example, you can flash full ROM v2.19.40.22 and then use unlocker v2.
Click to expand...
Click to collapse
man, a simple "yes" would have been easier to type and more polite.. of course, I've read it, same with all the threads here.. that's why I've seen a conflicting statement in the bootloader thread, hence the attempt to "clarify".. not everyone here is as good as you are.. thanks anyway..
great tool ! thanks
So im on v2.19.40.22 and ran Version 2
Phone rebooted went into stock recovery but it did nothing on there. The prompt on the PC said it was unlocked.
I manually rebooted my phone and the splashed looked the same.
Did i do something wrong?
Am i unlocked?
Can i verify if it's unlocked?
Thank You for you help.
Major
sorg said:
Now it's not required to flash/downgrade droidboot.img. But you still need to flash ROM not older than v2.19.40.18 for ZE551ML, and v2.19.40.12 for ZE550ML.
For example, you can flash full ROM v2.19.40.22 and then use unlocker v2.
Click to expand...
Click to collapse
Hello,
I am a little confused by these 2 lines.
The first line says:
But you still need to flash ROM not older than v2.19.40.18 for ZE551ML, and v2.19.40.12 for ZE550ML.
The second line says:
For example, you can flash full ROM v2.19.40.22 and then use unlocker v2.
So do I need a ROM no older than 2.19.40.18 or does 2.19.40.22 works fine?. As far as I know. 2.19.40.22 is older than 2.19.40.18.
Please clarify for me.
Thanks
Jeannette
V1 for anything under x.20
V2 for x.22
I think this is what it means but i may be wrong. Flash at your own risks
Sent from my ASUS_Z00AD using XDA Free mobile app
.18 is older than .22 I believe..
jeanne8fr said:
Hello,
I am a little confused by these 2 lines.
The first line says:
But you still need to flash ROM not older than v2.19.40.18 for ZE551ML, and v2.19.40.12 for ZE550ML.
The second line says:
For example, you can flash full ROM v2.19.40.22 and then use unlocker v2.
So do I need a ROM no older than 2.19.40.18 or does 2.19.40.22 works fine?. As far as I know. 2.19.40.22 is older than 2.19.40.18.
Please clarify for me.
Thanks
Jeannette
Click to expand...
Click to collapse
jarjarbingie said:
.18 is older than .22 I believe..
Click to expand...
Click to collapse
Which makes it even more confusing.
Why don't you say which rom we can use instead of which we cannot.
jeanne8fr said:
Which makes it even more confusing.
Why don't you say which rom we can use instead of which we cannot.
Click to expand...
Click to collapse
Because I've made unlocker not for one specific ROM version, but for any existing starting from .18 and newer.
.18 is older than .22, where is confusing?
I understand, that we live in time of smart phones and stupid people, but try to be on par with your phone at least. I've tried my best to explain in the OP what ROM versions you can use. I've made some bold text, some red text to take some attention. I've wrote example especially for .22 version! If it doesn't help, then i don't know what else can i do. How .18 cannot be obviously older than .22?
I've updated the OP, wrote compatible (as of today) versions. If even this is not clear enough, then i give up.
Awesome Work Mate. U ROCK!!!
For now, S-OFF from SunShine on the htc u11 is temporary. Changes you make while S-OFF will stay, they are not temporary, just the S-OFF flag is. All the same features, with exception of the ability to use custom hboot/aboot. Seriously, aboot patchers, don't bother trying at this point. Once you reboot into Android or Recovery, the device will reset back S-ON.
Changing mid, changing cid, downgrading etc all still work fine. If you want to change it a second time, just run sunshine again.
If/when a forever s-off comes, those with temp s-off will be upgraded at no cost.
jcase said:
For now, S-OFF from SunShine on the htc u11 is temporary. Changes you make while S-OFF will stay, they are not temporary, just the S-OFF flag is. All the same features, with exception of the ability to use custom hboot/aboot. Seriously, aboot patchers, don't bother trying at this point. Once you reboot into Android or Recovery, the device will reset back S-ON.
Changing mid, changing cid, downgrading etc all still work fine. If you want to change it a second time, just run sunshine again.
If/when a forever s-off comes, those with temp s-off will be upgraded at no cost.
Click to expand...
Click to collapse
Thanks man. I been holding off unlocking for a while waiting for this to come.
Many thanks @jcase for explanation. What about 2PZC RUU zip files flashing in case of temporary S-OFF? You know device reboots many times. Can we convert my devices to different variants?
Sent from my HTC U11 using XDA Labs
blueberry60 said:
Many thanks @jcase for explanation. What about 2PZC RUU zip files flashing in case of S-OFF? You know device reboots many times. Can we convert my devices to different variants?
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
It only clears if booting into android or recovery. You can reboot into download/bootloader without clearing it
jcase said:
It only clears if booting into android or recovery. You can reboot into download/bootloader without clearing it
Click to expand...
Click to collapse
Deleted
Sent from my HTC U11 using XDA Labs
@jcase
After getting Temp-S-Off, and later entering the DownloadMode mode, we see "S-Onn" (which is natural for temporary).
In the "OpenDSP" section there is "UNKNOWN".
And in the bootloader flag has changed status to "Modified".
regards
q.
qriozum said:
@jcase
After getting Temp-S-Off, and later entering the DownloadMode mode, we see "S-Onn" (which is natural for temporary).
In the "OpenDSP" section there is "UNKNOWN".
And in the bootloader flag has changed status to "Modified".
regards
q.
Click to expand...
Click to collapse
what's wrong with that? it is the same for me since I unlocked the bootloader. 2 months ago. both unknown and modified.
also can confirm now all works, changed CID twice (don't ask)
velimirchek said:
it is the same for me since I unlocked the bootloader. 2 months ago. both unknown and modified.
Click to expand...
Click to collapse
Same here.
velimirchek said:
changed CID twice (don't ask)
Click to expand...
Click to collapse
Why did you change CID twice?
Kisakuku said:
Same here.
Why did you change CID twice?
Click to expand...
Click to collapse
Because of @tbalden and you
I changed to 060 and then to 622.
Kisakuku said:
Is it safe to flash custom splash images?
Click to expand...
Click to collapse
I'll answer my own question. No issues flashing custom splash images in bootloader (nb0) or download mode (zip with android-info.txt), but obviously can't use recovery-based scripts (no S-OFF in recovery). Splash images made for the 10 work fine, since the screen resolution hasn't changed.
Kisakuku said:
I'll answer my own question. No issues flashing custom splash images in bootloader (nb0) or download mode (zip with android-info.txt), but obviously can't use recovery-based scripts (no S-OFF in recovery). Splash images made for the 10 work fine, since the screen resolution hasn't changed.
Click to expand...
Click to collapse
Thanks, I would have answered you but was sleeping
qriozum said:
@jcase
After getting Temp-S-Off, and later entering the DownloadMode mode, we see "S-Onn" (which is natural for temporary).
In the "OpenDSP" section there is "UNKNOWN".
And in the bootloader flag has changed status to "Modified".
regards
q.
Click to expand...
Click to collapse
OpenDSP should show unknown while s-on, that is normalm. Modified is normal as well, as you have an unlocked modified phone. You can clear that with a ruu most likely
My understanding with S-Off was that the bootloader can be unlocked and relocked without HTC noticing - is that the case?
For what it's worth I've not had a device fail on me over the years, but given their recent change of policy towards unlocking, the the screen issues and etc, I've not placed a custom ROM on this phone incase it does go all wrong and I need the warranty...
Could someone please confirm?
Doughnut said:
My understanding with S-Off was that the bootloader can be unlocked and relocked without HTC noticing - is that the case?
Click to expand...
Click to collapse
Support for S-OFF Locked is coming at some point in the future.
Follow this thread thanks Jcase for your hard work
jcase said:
OpenDSP should show unknown while s-on, that is normalm. Modified is normal as well, as you have an unlocked modified phone. You can clear that with a ruu most likely
Click to expand...
Click to collapse
Nope, flashing RUU and even relocking bootloader it stays modified.
velimirchek said:
Nope, flashing RUU and even relocking bootloader it stays modified.
Click to expand...
Click to collapse
At least on the HTC 10 S-OFF/Inlocked/Modified became S-OFF/Unlocked/Official after flashing a RUU Using the SD card method. It didn't when using an exe. Maybe this needs permanent S-OFF.
Sent from my HTC U11 using XDA Labs
Changed CID to superCID and... and I think there isn't much more that we need to do with S-OFF.
The downside of this method is the possibility to lose the ability go get S-OFF with future updates.
qriozum said:
@jcase
After getting Temp-S-Off, and later entering the DownloadMode mode, we see "S-Onn" (which is natural for temporary).
In the "OpenDSP" section there is "UNKNOWN".
And in the bootloader flag has changed status to "Modified".
regards
q.
Click to expand...
Click to collapse
velimirchek said:
Nope, flashing RUU and even relocking bootloader it stays modified.
Click to expand...
Click to collapse
will look into it
SunShine v3.5.8
Enhanced HTC U11 S-OFF Support