Here is a guide on updating your branded/unbranded non developer edition HTC ONE M8 to the developer edition android 5.0 (lollipop) update and also converting your device to a developer edition device by modifying the MID and CID of your device.
(this will also get you new updates as soon as HTC releases them as your phone is now a developer edition phone)
REQUIRES S-OFF AND POSSIBLY UNLOCKED BOOTLOADER
GPE CONVERTED DEVICES NEED TO GO BACK TO SENSE FIRST
HTC Drivers - https://mega.co.nz/#!9cpz0Soa!rZH0H5djENbFN2xkS9S7yUlXzX_vcC5yOHhmUR55kUM
ADB + Fastboot - https://drive.google.com/file/d/0B1S0LCuXCnnmOWhnUk1ZWVdQakE/view
First thing you want to do is boot the device and enable adb then type the below lines
Code:
adb shell
su
DO NOT MESS UP THE BELOW COMMAND - COPY AND PASTE IT - ENTERING IT WRONG COUlD BRICK YOUR DEVICE
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
Code:
adb reboot bootloader
fastboot oem writecid BS_US002
fastboot reboot-bootloader
Download this file RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.1540.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_411207_signed_2.exe
(STOCK LOLLIPOP 5.0 RUU FOR UNLOCKED + DEVELOPER EDITION HTC ONE M8 [this is what you have now since you changed CID and MID])
CRC32: 665CF81E
MD5: FDB3C48A40F1D42165783D75CFF4B846
SHA-1: 0B3C785F7735133ED11852E2FFAD29949A514DB1
Once it is downloaded, type the following commands
Code:
fastboot oem rebootRUU
FLASHING RUU'S WILL WIPE YOUR INTERNAL SD (/DATA/MEDIA)
Run RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.1540.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_411207_signed_2.exe and just press next/confirm etc. ignore the usb connection instructions, once that is done, the device will reboot and you will be on lollipop
CLICK FOR OLD METHOD
Download this file - http://dl3.htc.com/application/RUU_..._2G_20.63.4196.01_release_394319_signed_2.exe (Mirror)
(STOCK RUU FOR UNLOCKED + DEVELOPER EDITION HTC ONE M8 [this is what you have now since you changed CID and MID])
CRC32: 79E8DE54
MD5: 5040B8D54D0ADA150531C66D899ABBE9
SHA-1: A1E39A089A23417DDF5A682BB6A23C9BDE77025B
Once it is downloaded, type the following commands
Code:
fastboot oem rebootRUU
flashing the RUU will most defintely wipe your internal sd (/data/media)
Run RUU_M8_UL_K444_SENSE60_MR_BrightstarUS_WWE_3.28.1540.5_Radio_1.21.21331147A1.19_2G_20.63.4196.01_release_394319_signed_2.exe and just press next/confirm etc. ignore the usb connection instructions
once that is done, the device will reboot and you will be able to check for updates and find the lollipop update.
OPTIONAL Zip file for the OTA https://docs.google.com/uc?id=0B0lhP19GCj8fVDNCeE9WZUI5ZTQ&export=download - Boot to stock recovery, press vol+ and vol- and power when at the triangle thingy, then select the zip
This method isn't the quickest if you are already on a compatible version but if your not then this will get you sorted, i spent multiple hours getting this sorted.
Credit for the mid/cid stuff goes to this thread http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
ROOT: Either flash TWRP and let it do it's thing when u go to exit without root or flash a SuperSU Flashable ZIP!
{
"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"
}
great guide! will this guide if altered [or not] work for cdma [Verizon] version working. thanks
Does this work if I converted to GPe earlier?
Just wanted to get one thing clear. If I have SuperCID, I don't need to change my CID to the one provided above, right?
Stupid question ahead: Will my data be whiped during the RUU flashing? Or will it just update it, with keeping everything in place. I just don't want to reinstall everything I am already S-Off and unlocked BL
mzrdisi said:
*nevermind*
Click to expand...
Click to collapse
OK
pavankvn said:
Does this work if I converted to GPe earlier?
Click to expand...
Click to collapse
I never tested on GPE device or GPE converted device sorry.
Jamal Ahmed said:
Just wanted to get one thing clear. If I have SuperCID, I don't need to change my CID to the one provided above, right?
Click to expand...
Click to collapse
Not sure try it if you want. it's not difficult to change it though.
Tilgi said:
Stupid question ahead: Will my data be whiped during the RUU flashing? Or will it just update it, with keeping everything in place. I just don't want to reinstall everything I am already S-Off and unlocked BL
Click to expand...
Click to collapse
I believe it will wipe all data including internal sd (atleast it did for me)
Not working, the Updater complains that the ID isn't a match, i updated it to the one you provided and it does NOT work.
---------- Post added at 03:02 PM ---------- Previous post was at 02:57 PM ----------
maxupp said:
Not working, the Updater complains that the ID isn't a match, i updated it to the one you provided and it does NOT work.
Click to expand...
Click to collapse
And another thing: Why do you link a Brightstar RUU? Shouldn't this be an unbranded RUU?
OP,
Please add big warning in your post about dangers of changing MID. You must specifically warn about not messing up any character in command line. :good::good:
09Ram said:
OP,
Please add big warning in your post about dangers of changing MID. You must specifically warn about not messing up any character in command line. :good::good:
Click to expand...
Click to collapse
And he should change it to Super CID to be on the safe side.
---------- Post added at 03:52 PM ---------- Previous post was at 03:35 PM ----------
Adding to my statement above:
Using the RUU posted in the OP, it is NOT possible to install the 5.0.1 update.
I just downloaded it and was informed that i cannot update because the OS has been modified.
Please remove this entire thread or update the OP to be correct.
No problem with OP, follow instructions and everything works like a charm. Wish I had known RUU's wipe internal memory though
Many, many thanks! It worked out just perfectly! There is the OTA notification, great
Well, ill try this on a different computer because after doing "fastboot oem rebootRUU", tried to run the exe file but nothing happened (it kinda installed but it closes without any warning or any confirmation) . Now im stuck at the bootloader only saying RUU. Any tips?
maxupp said:
Not working, the Updater complains that the ID isn't a match, i updated it to the one you provided and it does NOT work.
---------- Post added at 03:02 PM ---------- Previous post was at 02:57 PM ----------
And another thing: Why do you link a Brightstar RUU? Shouldn't this be an unbranded RUU?
Click to expand...
Click to collapse
Works perfectly fine, Obviously did something wrong. Brightstar RUU is unbranded. and only 1 i could find for Developer Edition.
09Ram said:
OP,
Please add big warning in your post about dangers of changing MID. You must specifically warn about not messing up any character in command line. :good::good:
Click to expand...
Click to collapse
Done!
maxupp said:
And he should change it to Super CID to be on the safe side.
---------- Post added at 03:52 PM ---------- Previous post was at 03:35 PM ----------
Adding to my statement above:
Using the RUU posted in the OP, it is NOT possible to install the 5.0.1 update.
I just downloaded it and was informed that i cannot update because the OS has been modified.
Please remove this entire thread or update the OP to be correct.
Click to expand...
Click to collapse
Super CID didn't work for me, Using the RUU in OP it work's fine, i did it myself and others confirmed it worked. Make sure you don't have a custom recovery and haven't modified the system. the screenshots in the 2nd post is from the RUU that is linked on OP the MID and CID from the OP aswell!
bazzi12 said:
No problem with OP, follow instructions and everything works like a charm. Wish I had known RUU's wipe internal memory though
Click to expand...
Click to collapse
Thanks, glad it worked, Added to OP about wiping RUU (although i did mention it in a previous post already). leave a press on the thanks if you haven't already
Tilgi said:
Many, many thanks! It worked out just perfectly! There is the OTA notification, great
Click to expand...
Click to collapse
Thanks, Glad it worked, leave a press on the thanks if you haven't already
--------------------
maxupp said:
Please remove this entire thread or update the OP to be correct.
Click to expand...
Click to collapse
ADDITIONALLY I AM NOT SOME NOOB ON XDA SO DON'T TREAT ME LIKE ONE AND INSTEAD RESPECT OTHER MEMBERS. DO NOT TELL ME WHAT TO DO! JUST CUZ IT DIDN'T WORK FOR YOU DOESN'T MEAN IT DOESN'T WORK FOR EVERYONE ELSE
diogoribeiro said:
Well, ill try this on a different computer because after doing "fastboot oem rebootRUU", tried to run the exe file but nothing happened (it kinda installed but it closes without any warning or any confirmation) . Now im stuck at the bootloader only saying RUU. Any tips?
Click to expand...
Click to collapse
disable anti-virus and run as admin. official HTC software so no risk of virus.
It worked fine for me.
Installed easily and took 5.0.1 OTA right after setup was complete.
Only problem I'm having now is that I am unable to boot TWRP through ADB to backup recovery.
After running cmd "fastboot boot TWRP.img" It downloads fine, then command says booting, but nothing happens and phone is stuck on bootloader screen. Any suggestions?
HBoot 3.19
I tried to follow your instructions and below was my result when i tried changing the MID to developer. I was on developer edition rom already, but i had the international MID. my phone is an AT&T variant. I changed MID's so x.xx.401.x stock rom would accept OTA's without a problem. i changed my MID back when i was on either 1.12 or 1.54 base, i dont remember. Now the OTA for 4.16 does not install. installing from android, it keeps saying download is corrupt. installing from recovery simply throws an unknown error. my guess is the MID being messed up. any information is greatly appreciated. in the meantime, im on 3.28 and the phone functions correctly for now at least.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT********** [edited for obvious reasons]
(bootloader) imei: xxxxxxxxxxxxxxx [also edited]
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000n.satn tnwo ot53
amns
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
Click to expand...
Click to collapse
chevyjohn01 said:
It worked fine for me.
Installed easily and took 5.0.1 OTA right after setup was complete.
Only problem I'm having now is that I am unable to boot TWRP through ADB to backup recovery.
After running cmd "fastboot boot TWRP.img" It downloads fine, then command says booting, but nothing happens and phone is stuck on bootloader screen. Any suggestions?
Click to expand...
Click to collapse
you can't fastboot boot twrp any more you will need to fastboot flash recovery twrp.img
fma965 said:
disable anti-virus and run as admin. official HTC software so no risk of virus.
Click to expand...
Click to collapse
Well, couldnt make it work on this computer. Used another and everything went smothly, maybe i had a bad download or something on my computer was blocking the program from even starting. Thank you for your quick reply and for your amazing job i really appreciate it.
diogoribeiro said:
Well, couldnt make it work on this computer. Used another and everything went smothly, maybe i had a bad download or something on my computer was blocking the program from even starting. Thank you for your quick reply and for your amazing job i really appreciate it.
Click to expand...
Click to collapse
Great, glad you got it working hit the thanks button if you want
Related
I've been searching for hours here but can't find a solution that works...
My wife's Wi-Fi Nexus 7 (running stock, unrooted) suddenly got stuck in a boot loop during the white Google logo (never gets to the Nexus "X" animation). I figured I'd simply restore to stock through fastboot/adb.
The problem is when I try to unlock the bootloader (which is needed to be able to flash the factory image) I get this error message:
Code:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
[COLOR="Red"][B]FAILED (remote: ()[/B][/COLOR]
finished. total time: 2.736s
Because of this, I can't go any further. I can't flash anything because it tells me I need to unlock the bootloader. I tried a couple of different toolkits with the same results.
I get fastboot access, and the device is listed when I type "fastboot devices" but I don't get adb access. When I type "adb devices" I simply see:
Code:
>adb devices
List of devices attached
...and nothing else. No devices listed. If I try other adb commands, I get "error: device not found".
I've tried installing the Google drivers as well as other USB drivers from toolkits. No change. But I can send it commands through fastboot fine.
{
"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"
}
I can get into recovery, but can't flash anything. I am able to factory reset from recovery, but it doesn't help. The tablet just keeps boot-looping.
Am I screwed? Any ideas? Thanks in advance to anyone who responds
I had to put mine in PTP mode to get it recognized. I also had a heck of of time getting the drivers installed correctly. I had to un-install and re-install several times before it worked correctly
bigdaddy619 said:
I had to put mine in PTP mode to get it recognized. I also had a heck of of time getting the drivers installed correctly. I had to un-install and re-install several times before it worked correctly
Click to expand...
Click to collapse
What's PTP mode? Were you having the same issue I'm having?
The thing is my tablet is getting recognized, at least in fastboot. Just not in adb but I'm thinking that's because it never had debugging turned on.
Wrong input.
grisoxxl said:
If you can acces recovery make full wipe.
Click to expand...
Click to collapse
Already did that several times. Doesn't help Still stuck in a boot loop and still can't unlock the bootloader to try to flash stock image.
ecaggiani said:
Already did that several times. Doesn't help Still stuck in a boot loop and still can't unlock the bootloader to try to flash stock image.
Click to expand...
Click to collapse
Why don't you flash the Google stock firmware?
Edit: i don't think unlock is necessary for flashing Google stock image
Sent from my Nexus 7 using xda premium
ganeshp said:
Why don't you flash the Google stock firmware?
Edit: i don't think unlock is necessary for flashing Google stock image
Click to expand...
Click to collapse
That's what I'm trying to do! The guides I've seen have me unlock the bootloader to be able to flash stock firmware. Can you point me to a guide? Is there an RUU maybe?
ecaggiani said:
Am I screwed?
Click to expand...
Click to collapse
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip.
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
bftb0 said:
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip.
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
Click to expand...
Click to collapse
Yeah I was afraid of that. Thanks for the response. I'll be contacting either Google or ASUS soon.
ecaggiani said:
Yeah I was afraid of that. Thanks for the response. I'll be contacting either Google or ASUS soon.
Click to expand...
Click to collapse
Hi, im having the exact problem you're having, did you end up contacting ASUS? how was your experience like? Did you get it resolved? I think I voided my warranty by trying to pull the battery ):
Hi all,
I've also got what seems to be a similar problem.
I've tried many (all?) the options to get this thing unlocked.
All I get is:
Code:
fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 4.753s
or if I try a factory flash:
Code:
fastboot flash bootloader bootloader-tilapia-4.13.img
sending 'bootloader' (2096 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.013s
Also a "restart bootloader" from the recovery screen or
Code:
fastboot reboot-bootloader
takes me to a blank screen.
Holding the power button to reset the Nexus then the power + Vol Down takes me back to recovery with no change.
(I'm looking at this for a friend so not sure exactly what he did, but I doubt it was anything major!)
the machine vars are:
Code:
fastboot getvar all
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000700f00000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.161s
your help please?
regards
Ricey
Ricey_uk said:
Hi all,
I've also got what seems to be a similar problem.
I've tried many (all?) the options to get this thing unlocked.
All I get is:
Code:
fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 4.753s
or if I try a factory flash:
Code:
fastboot flash bootloader bootloader-tilapia-4.13.img
sending 'bootloader' (2096 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.013s
Also a "restart bootloader" from the recovery screen or
Code:
fastboot reboot-bootloader
takes me to a blank screen.
Holding the power button to reset the Nexus then the power + Vol Down takes me back to recovery with no change.
(I'm looking at this for a friend so not sure exactly what he did, but I doubt it was anything major!)
the machine vars are:
Code:
fastboot getvar all
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000700f00000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.161s.
your help please?
regards
Ricey
Click to expand...
Click to collapse
Hi, Ricey_uk...
Mmm... not sure, but I think you're trying to flash the wrong factory image for your device...
Reason being, is because (QUOTE: fastboot flash bootloader bootloader-tilapia-4.13.img) 'tilapia' refers to the 3G/GSM variant of the Nexus 7.
But you appear to have a (QUOTE: (bootloader) product: grouper) 'grouper' device. Which is WiFi only... this seems to be supported by the two lines in your output...
(bootloader) version-baseband: N/A
(bootloader) version-cdma: N/A
... which suggests your N7 has no 'radio' capability.
You need the factory stock image for "nakasi" for Nexus 7 Wi-Fi only (device board "grouper").... NOT "nakasig" for Wi-Fi & Mobile (device board "tilapia").
(See my sig for download links).
-----------
In short, there is an incongruity/contradiction in your reported outputs.... the device is either 'grouper' or it's 'tilapia'
It can't be both.
If it has a SIM card (like a mobile phone), or a space for a SIM card, then it's 'tilapia'... if it doesn't, then it's 'grouper'.
Ensure you are flashing the correct factory stock for your device.
-----------
But having said all of that... (and if there is confusion, it needs to be cleared up)... it doesn't explain why something as straightforward and innocuous as...
Code:
fastboot oem unlock
...isn't working.
Two possibilities occur to me...
1) A bad USB connection. Try a different USB port on your PC... Or, maybe, a different USB cable.
Once the fastboot oem unlock command is issued at the PC end, it will need to be confirmed at the Nexus 7 end (see attached thumbnail). Use either of the two VOL buttons to choose YES and confirm by pressing the POWER button.
2) It's possible there could be a hardware failure... some problem with the EMMC flash memory chip. As alluded to by a previous poster...
bftb0 said:
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
Click to expand...
Click to collapse
Whilst I don't discount the possibility that it COULD be EMMC chip failure, I'm not inclined to think that this is a likely possbility. More prosaic explanations need to be explored first.
First... check the integrity of of your USB connections - at both ends; change to different USB ports on your PC; if you can, try a different PC; try a different USB cable. And confirm at the Nexus 7 end, once the unlock command has been issued. (again, see attached thumbnail).
Second... if you are going to try to fastboot flash back to Android factory stock... make sure you do so with correct version for your device. If you're device is Wi-Fi only, you need the 'grouper' version... if not, the 'tilapia' version.
Hope this helps.... and good luck.
Rgrds,
Ged.
Hi Ged,
thanks for the info, I was wondering about the .img versions - but I can't seem to find the 'grouper' version of 4.13 anywhere. It's not on the factory downloads page (google)
As for the unlock, it does indeed come up with the screen as you showed, and pressing the power button for 'yes' says that it is unlocking. When it then reboots itself it just stays blank. A hard power cycle back to recovery states that it is still locked.
thought?
cheers
Ricey_uk said:
Hi Ged,
thanks for the info, I was wondering about the .img versions - but I can't seem to find the 'grouper' version of 4.13 anywhere. It's not on the factory downloads page (google)
As for the unlock, it does indeed come up with the screen as you showed, and pressing the power button for 'yes' says that it is unlocking. When it then reboots itself it just stays blank. A hard power cycle back to recovery states that it is still locked.
thought?
cheers
Click to expand...
Click to collapse
Hi, Ricey_uk...
Yeah... that, unfortunately, does not sound good at all. Unlocking the bootloader just sets some 'flag state' on the internal EMMC flash chip. Specifically, somewhere in the mmcblk0boot0 partition, where the bootloader lives.
There's some technical info here... http://forum.xda-developers.com/showthread.php?t=2068207
If fastboot oem unlock is performing as you describe, then it strongly suggests some sort of hardware failure. It just shouldn't behave that way... once you have confirmed the oem unlock request on the Nexus 7, the PC should display (if I remember correctly), the following...
Unlocking....
The device is unlocked now...
The whole procedure should take no more than a few seconds. Blank screens and forced reboots have happened many times on my Nexus 7... but never whilst unlocking the bootloader (and yes, I have locked and relocked several times, when I was experimenting with the 'motochopper' root exploit).
----------------------------------
Incidentally, you won't find 4.13 on the factory downloads page, as that number refers to the bootloader version for JellyBean 4.2 and 4.2.1. (It's not always the case that with each new version of JellyBean the bootloader is updated).
Anyway... looking through my collection of system images on my laptop, I find the following...
JellyBean 4.1.2 -> bootloader-grouper-3.41.img
JellyBean 4.2.0 -> bootloader-grouper-4.13.img
JellyBean 4.2.1 -> bootloader-grouper-4.13.img
JellyBean 4.2.2 -> bootloader-grouper-4.18.img
JellyBean 4.3.0 -> bootloader-grouper-4.23.img
With JellyBean 4.3 being the latest, and it updating the bootloader to 4.23.
If you're still stuck on bootloader version 4.13, then that means it was last updated with the rollout of JellyBean 4.2, sometime around November 2012.
----------------------------------
All of which is technically interesting... but probably doesn't help you.
I think there is a hardware problem on your Nexus 7, that is preventing the bootloader-lock-state flag from being correctly set.
Wish I could be of more assistance.
Rgrds,
Ged.
Thanks Ged,
great info - I was looking for the factory image for JB 4.2.0 to get the bootloader image out of, but that version of JB isn't on the factory page
my theory being if I re-flash the same version it might fix the bootloader?? But it being locked it would need the exact same version?
perhaps if you could mail me the .img file I could try it? I can pm you my address??
cheers!
Ricey_uk said:
Thanks Ged,
great info - I was looking for the factory image for JB 4.2.0 to get the bootloader image out of, but that version of JB isn't on the factory page
my theory being if I re-flash the same version it might fix the bootloader?? But it being locked it would need the exact same version?
perhaps if you could mail me the .img file I could try it? I can pm you my address??
cheers!
Click to expand...
Click to collapse
Give me half an hour or so, and I'll upload it to my dropbox and I'll post a link. Gotta get it of my laptop first.
Although I'm not convinced it will solve your problem... but I suppose you have nothing to loose by trying.
Rgrds,
Ged.
---------- Post added at 12:53 PM ---------- Previous post was at 12:21 PM ----------
OK... here is the bootloader .img file - v4.13... extracted from nakasi-jp40d-factory-6ac58a1a.tar... or in English, Jellybean 4.2.1.
https://dl.dropboxusercontent.com/u/37483979/bootloader-grouper-4.13.img
Code:
File size: 2.05 MiB (2,146,892 bytes)
MD5: a119629c89ad06c7e49bebd260df9cf3
SHA-1: fd60a0d9da5c814e2c1ee049f537700cbbe2c3cc
Flash as follows....
Code:
fastboot flash bootloader bootloader-grouper-4.13.img
---------------
Be careful with this.
Flashing a bootloader is the riskiest single operation you can undertake on the Nexus 7.
All it takes is one false step, and you have a hardbrick.
The device will never boot again.
Make sure you have good USB connections at both ends... and before flashing... type...
Code:
fastboot devices
If you don't see a serial number, you have either a driver problem OR a possible dodgy USB connection.
Do not proceed with this flash until you see a serial number.
Normally, I would suggest test flashing something innocuous first, like a recovery, for example.... but since your bootloader is locked, that's not possible.
I'm not even sure flashing a bootloader is possible with a locked bootloader... but then, I've never directly flashed a bootloader before.
Very best of luck - really hope this fixes your problem.
Rgrds,
Ged.
Many thanks Ged,
tried it to no avail - still getting the 'Bootloader is locked'
It won't even re-flash the existing
I checked all the cables and used a different USB port.
thanks for your help
Ricey
Ricey_uk said:
Many thanks Ged,
tried it to no avail - still getting the 'Bootloader is locked'
It won't even re-flash the existing
I checked all the cables and used a different USB port.
thanks for your help
Ricey
Click to expand...
Click to collapse
Damn... thought that might happen... but wasn't 100% sure.
You can't use fastboot with a locked bootloader, even to flash a bootloader... and you can't unlock it because - well, who the hell knows why (but I suspect a problem with the internal EMMC).
What is the precise current status of your Nexus 7?
Android version?
Rooted?
Stock or Custom ROM/kernel?
Custom recovery (CWM/TWRP) installed?
Did you receive any OTA notifications regarding the recent release of Android 4.3? and if so did you allow the OTA update to proceed? What happened?
Rgrds,
Ged.
I know! I'm stuck in a loop!
I don't know the exact Android version, but it's fairly new and the owner hasn't updated it as far as I know.
Apart from that, completely stock and unrooted!
The last thing to happen was that it was left for a while to go flat (battery) then when re-started it got stuck at the Google logo and no further.
All I can get apart from the Google logo is the recovery with the andoid on his back with his tummy open
cheers
Ricey_uk said:
I know! I'm stuck in a loop!
I don't know the exact Android version, but it's fairly new and the owner hasn't updated it as far as I know.
Apart from that, completely stock and unrooted!
The last thing to happen was that it was left for a while to go flat (battery) then when re-started it got stuck at the Google logo and no further.
All I can get apart from the Google logo is the recovery with the andoid on his back with his tummy open
cheers
Click to expand...
Click to collapse
You can get the Android version info by going to SETTINGS>>ABOUT TABLET.
Without further details, what is odd about your predicament is this...
If your bootloader is v4.13, then that means the device hasn't been updated since November of last year. Since then, there have been, I think, 3 official updates from Google... the most recent being JellyBean 4.3 about a couple of weeks ago
Normally, when an OTA update is pending, you get pestered endlessly with an endless stream of notifications.
Upon the user accepting the lastest update (whatever that might be - but is currently JellyBean 4.3)... the device downloads the OTA, runs a checksum test on the current files in /system... and then'patches' them, meaning it brings them up to date.
The very last thing the OTA does is update the bootloader, by dropping BOOTLOADER.RAW into the USP(staging) partition. Upon automatic reboot, the new bootloader is then copied (from the USP/staging partition) into the bootloader partition proper... thus obviating the risks associated with flashing the bootloader partition directly.
Since November, the bootloader has been updated by this means twice... 4.13->4.18 (in, I think February, when JellyBean 4.22 was rolled out) and just recently 4.18->4.23 when JellyBean 4.3 was rolled out.
It's odd you haven't received any notifications of any OTA updates.
----------------------------------
Anyway.... A possible workaround...
A slightly rhetorical question... why do you want to unlock the bootloader anyway?
I assume it's because you want to root... or maybe flash a custom ROM...
That 'might' still be possible...if you're running a version of Android THAT ISN'T JellyBean 4.3, you can root via 'exploit'.
Details here - http://forum.xda-developers.com/showthread.php?t=2233852
This requires no fastboot commands and thus, no need for an unlocked bootloader.
It's really simple to implement. Indeed, I ran my Nexus 7 for several month BOOTLOADER locked, but rooted.
(But with the advent of JellyBean 4.3, root exploits no longer work.... so I've had to root the old fashioned way).
But it might be useful to you...
Anyway... once you are rooted, you can then flash a Custom Recovery... like CWM or TWRP.
Normally this would be done via fastboot. But there are two great apps available that will 'write' a recovery partition... directly from the Nexus 7.
These are Flash Image GUI and Flashify.
Both will request root access.
It doesn't matter which one you use, as they essentially do the same job... but IMHO, Flashify is the better of the two.
Once you have a Custom Recovery installed, the metaphorical gateway is open to whatever Custom ROMs or Custom Kernels you like.
----------------------------------
It's possible none of the above will work... maybe for the same reason why you can't unlock the bootloader. A suspected fault with the internal EMMC chip.
But it just might... and it's gotta be worth a shot.
To summarize
Root via 'exploit'
Use Flashify or Flash Image GUI to install a Custom Recovery
Good luck.
Rgrds,
Ged.
With the arrival of S-OFF for the HTC One we also got the possibility to flash a custom splash screen. Many of us used this already on their previous devices and now it's possible for the HTC One too.
Preparing image for flashing:
First you need the image of your choice. Make sure you it has the size 1080x1920 !!!. It must have been already the correct size because the converter doesn't re-size it. The image can be in the format BMP, JPG or PNG.
Grab EZ Splash Screen Flasher and Image Converter and convert your image. Instructions how to convert it are in the original thread.
Take the custom.img in the place-image-here folder and rename it to splash1.nb0.
Download the attached splash.zip and replace the splash1.nb0 inside.
Have a look at the android-info.txt file and check if your CID is present inside. IF not than add it. I have already added a lot of CID's but if there are some missing I will update it from time to time.
Requirements for flashing:
S-OFF
Steps for flashing:
Boot your HTC One into bootloader and enter fastboot mode
adb reboot bootloader
Start RUU Flash mode
fastboot oem rebootRUU
Flash the custom splash screen
fastboot flash zip splash.zip
Make sure that there are no error messages when flashing
Reboot your device
fastboot reboot
If someone is interested this is the actual image in the splash.zip
{
"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"
}
If you want to go back flash the splash_stock.zip
fastboot flash zip splash_stock.zip
THX for Tutorial, here my splashscreens.
Thanks for the tutorial, now i'm S-Off i can see me turning into a splash flashaholic!
thx for sharing..works fine here..cheers~
Hi chrisch1974,
I do not own this device myself, but Sneakyghost and I have been playing around a bit, and he confirms that this works for the One. It seemed appropriate to offer it up here in your thread..
For the One-S Ville, I have an online boot splash zip generator. You can upload a picture and it will generate a recovery flashable .zip file. I have now made a version for the One M7 that's identical, except it uses a different resolution and block device. (1080x1920 into P13 instead of 540x960 into P14) For people who don't have a windows box available, this might be an easier option.
http://jobiwan.net:81/bootsplash-one
I don't know whether S-Off is required or not. On the Ville you have to be either S-Off or on a lower hboot version. Again, the .zip files this generates are recovery flashable, not fastboot-RUU flashable, unlike yours.
Enjoy,
-Jobo
(PS: This is my original thread for the One-S Ville: http://forum.xda-developers.com/showthread.php?t=1777223 The online generator is introduced in post#115.)
chrisch1974 said:
With the arrival of S-OFF for the HTC One we also got the possibility to flash a custom splash screen. Many of us used this already on their previous devices and now it's possible for the HTC One too.
Preparing image for flashing:
First you need the image of your choice. Make sure you it has the size 1080x1920 !!!. It must have been already the correct size because the converter doesn't re-size it. The image can be in the format BMP, JPG or PNG.
Grab EZ Splash Screen Flasher and Image Converter and convert your image. Instructions how to convert it are in the original thread.
Take the custom.img in the place-image-here folder and rename it to splash1.nb0.
Download the attached splash.zip and replace the splash1.nb0 inside.
Have a look at the android-info.txt file and check if your CID is present inside. IF not than add it. I have already added a lot of CID's but if there are some missing I will update it from time to time.
Requirements for flashing:
S-OFF
Steps for flashing:
Boot your HTC One into bootloader and enter fastboot mode
adb reboot bootloader
Start RUU Flash mode
fastboot oem rebootRUU
Flash the custom splash screen
fastboot flash zip splash.zip
Make sure that there are no error messages when flashing
Reboot your device
fastboot reboot
Click to expand...
Click to collapse
I attempted to flash with these instructions and received the following:
C:\Users\brandon\Downloads\One_M7_All-In-One_Kit_v1.3\Data>fastboot flash zip sp
lash_stock.zip
sending 'zip' (20 KB)...
OKAY [ 0.233s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.666s
I edited the text file to add my CID (BS_US001) but no luck...
I am S-OFF but did not change the CID.
MG
Hey Chrisch!
Nice thread really! I was a bit frustrated first when i found it because i spent all afternoon working out where splash is, how to convert it etc. Now you have been faster!
Well, at least Touch of Jobo can offer his form for recovery flashable zips as a supplement.
I will link your thread to my hboot modification thread so people who edit out the red warning have easy access to custom splash screens (in my eyes these two always go together somehow )
Well done mate! Thanks a lot!
touch of jobo said:
Hi chrisch1974,
I do not own this device myself, but Sneakyghost and I have been playing around a bit, and he confirms that this works for the One. It seemed appropriate to offer it up here in your thread..
For the One-S Ville, I have an online boot splash zip generator. You can upload a picture and it will generate a recovery flashable .zip file. I have now made a version for the One M7 that's identical, except it uses a different resolution and block device. (1080x1920 into P13 instead of 540x960 into P14) For people who don't have a windows box available, this might be an easier option.
http://tibook.jb.b4m.com:81/bootsplash-one
I don't know whether S-Off is required or not. On the Ville you have to be either S-Off or on a lower hboot version. Again, the .zip files this generates are recovery flashable, not fastboot-RUU flashable, unlike yours.
Enjoy,
-Jobo
(PS: This is my original thread for the One-S Ville: http://forum.xda-developers.com/showthread.php?t=1777223 The online generator is introduces in post#115.)
Click to expand...
Click to collapse
It won't flash I n recovery, I tried to open up the zip and it fails
Sent from my HTC One using Tapatalk 4 Beta
superchilpil said:
It won't flash I n recovery, I tried to open up the zip and it fails
Click to expand...
Click to collapse
I've tested it myself and it creates valid .zip files. I can not flash them because I don't have a One. Is the z.ip file you get zero bytes? Can you (zip up and) post the picture you tried to upload?
Edit to add: can 2 or 3 others please report? So as to see whether this is a special case, or it just doesn't work at all..
Edit2: I used the metallica picture you posted, and it generated a 905K .zip file. (attached)
touch of jobo said:
I've tested it myself and it creates valid .zip files. I can not flash them because I don't have a One. Is the z.ip file you get zero bytes? Can you (zip up and) post the picture you tried to upload?
Click to expand...
Click to collapse
The zip I got is about 1.11 kb
Here's the image http://db.tt/rZlKDiBZ
Sent from my HTC One using Tapatalk 4 Beta
---------- Post added at 12:09 PM ---------- Previous post was at 12:02 PM ----------
I figured out my issue, it was my phone. Tried it on a computer and it works just fine
Sorry for the troubles
superchilpil said:
The zip I got is about 1.11 kb
Here's the image http://db.tt/rZlKDiBZ
Sent from my HTC One using Tapatalk 4 Beta
---------- Post added at 12:09 PM ---------- Previous post was at 12:02 PM ----------
I figured out my issue, it was my phone. Tried it on a computer and it works just fine
Sorry for the troubles
Click to expand...
Click to collapse
Your zip is broken. THats not right. Re-Do the process. It worked for me totally ok.
I just tried it again. My zip is 139KB from an image with only 23KB.
[EDIT] lol i just saw you fixed it already. Totally overseen that haha!
---------- Post added at 07:20 PM ---------- Previous post was at 07:14 PM ----------
moregadget said:
I attempted to flash with these instructions and received the following:
C:\Users\brandon\Downloads\One_M7_All-In-One_Kit_v1.3\Data>fastboot flash zip sp
lash_stock.zip
sending 'zip' (20 KB)...
OKAY [ 0.233s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.666s
I edited the text file to add my CID (BS_US001) but no luck...
I am S-OFF but did not change the CID
MG
Click to expand...
Click to collapse
It doesn't say FAILED custom id check (CID) but model id check (MID)
I have that on my thread for the hboots as well. I am still trying to find out if there are ONE devices with a different Model ID.
[EDIT]
OK thanks to Mike1986 Website i found the answer already.
There are three MID's
PN0710000
PN0711000
and a third one Mike didn't specify.
You can try to change the MID in your android-info.txt and see if that helps Maybe it flashes then!
Phone would not get past Rootbox bootanimation after successful flashing (the splash showed up fine). fastboot erase cache seems to have fixed it though. Thanks for the how-to!
modelid: PN0712000
cidnum: 11111111
Sneakyghost said:
It doesn't sai FAILED custom id check (CID) but model id check (MID)
I have that on my thread for the hboots as well. I am still trying to find out if there are ONE devices with a different Model ID.
Can you run fastboot getvar all for me to get me your model id? Thank you!
Click to expand...
Click to collapse
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
MG
Thanks, it worked great! I recreated the Nexus splash screen and posted it below if anyone wants it.
just a theoretical scenario, if I were to flash the custom splash screen and then revert to S-ON, would the splash screen stay? and would my phone become a brick?
Stargazer418 said:
Thanks, it worked great! I recreated the Nexus splash screen and posted it below if anyone wants it.
Click to expand...
Click to collapse
I'm guessing you've managed to remove the "this is for development purposes" message?
dh2311 said:
just a theoretical scenario, if I were to flash the custom splash screen and then revert to S-ON, would the splash screen stay? and would my phone become a brick?
Click to expand...
Click to collapse
Only a RUU or maybe an OTA can reset your splash back to stock, so yes, it will stay. The splash image is not signed. Having a modified splash on S-On will not brick you. (Having a modified hboot on S-On will brick you tho!)
Simba501 said:
I'm guessing you've managed to remove the "this is for development purposes" message?
Click to expand...
Click to collapse
There's another thread on how to do that, look for hboot mod
Sent from my HTC One using Tapatalk 4 Beta
Simba501 said:
I'm guessing you've managed to remove the "this is for development purposes" message?
Click to expand...
Click to collapse
No, I didn't. I saw the thread about removing it, but I don't know if it will overwrite the splash I already flashed. It doesn't seem to show up every boot, though, so it's not that bad in my opinion.
At last my device is back to life, unlocked, rooted and S-OFF.
My device was restarting every two minutes because of unknown baseband and no IMEI plus the com.HTCdialler is not responding . it was S_ON HBOOT 1.57 so i couldn't flash the RUU.
So below the steps i done.
1. check your OS version which is written in your bootloader and download it from here http://forum.xda-developers.com/showthread.php?p=39588860 . i have downloaded the exe version.
2. download another RUU Rom that doesn't match your rom with newer version than yours. ( I did that by mistake and that helped me alot )
3. your bootloader must be locked or relocked to flash RUU . you can do that by using this command '' fastboot oem lock '' .
4. Because your device is S-ON RUU will not brick your device. So install the wrong RUU version which will give you a 155 error i think and put your device in recovery mode ( Black HTC screen)
5. Don't worry, that was for having a clean formatted device. Now install the same OS version of your device and your baseband and IMEI will be back to normal.
6. unlock your bootloader ( it's better to use HTC One Toolkit {M7} thanx to squabbi, it was very helpfull )
7. download TWRP recovery and flash it using HTC One Toolkit {M7}
8. root your device using HTC One Toolkit {M7} and open the SU installer from your device to complete rooting your device.
9. now we will S-OFF the device using firewater method. download it from here http://firewater-soff.com/firewaterdownload-3 and put it in HTC One Toolkit {M7} folder. hold the shift key and right click any where and choose '' open command window here ''. now use the following commands :
adb reboot <–important!!!!
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
answer Yes with capital Y and wait till it says your device is S-OFF.
retype the last command if it didn't respond till it says that your device is S-OFF.
Sorry for talking too much
what happened up there ??
why don't you s-off and flash a custom rom or a suitable ruu zip ??
Thank pro
S-OFF Hboot 1.57
CID_044
{
"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"
}
pinbacninh_city said:
Thank pro
S-OFF Hboot 1.57
CID_044
Click to expand...
Click to collapse
Did your phone S Off after 1.57 hboot ?
The first bottle is open
chugging..........
ERROR: kernel contains HTC anti-firewater patch!
****** Try again with a different kernel ******
[email protected]:/ #
My rom is of T-mobile brand.
Help please .Thanks
elementary or kangaroo test kernel
pinbacninh_city is it safe to unlock the phone after the new update sense 6 . this my issue if u can help me of that
M7-UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.11.401.10
eMMC-boot 2048MB
http://forum.xda-developers.com/showthread.php?p=53206170
Does anyone have the latest RUUs compiled anywhere since Bugsy is in recovery? Heck.. I just need the latest Sprint RUU. My beautiful One is stuck in limbo!!
Sent from my Nexus 5 using XDA Free mobile app
frankmasc said:
The first bottle is open
chugging..........
ERROR: kernel contains HTC anti-firewater patch!
****** Try again with a different kernel ******
[email protected]:/ #
My rom is of T-mobile brand.
Help please .Thanks
Click to expand...
Click to collapse
I am still facing like this
Please help me as well
frankmasc said:
The first bottle is open
chugging..........
ERROR: kernel contains HTC anti-firewater patch!
****** Try again with a different kernel ******
[email protected]:/ #
My rom is of T-mobile brand.
Help please .Thanks
Click to expand...
Click to collapse
Flash CM rom (I use 2014 february nightly) and with this working great. In development settings enable to access adb and apps, and enable the authorization without question (don't remember the menu name). In phone one time enable the access pop-up. After working great the firewater.
(When cugging a lot and don't jump to bottle 2-3 etc is not working, so try again and again. I suffered with this two days.)
Steve1207 said:
Flash CM rom (I use 2014 february nightly) and with this working great. In development settings enable to access adb and apps, and enable the authorization without question (don't remember the menu name). In phone one time enable the access pop-up. After working great the firewater.
(When cugging a lot and don't jump to bottle 2-3 etc is not working, so try again and again. I suffered with this two days.)
Click to expand...
Click to collapse
Thats what i get!! Im in hboot 1.57 stock rom! Please help I need to get my device for warranty :/
Code:
D:\HTC>adb devices
List of devices attached
MB352W909733 device
D:\HTC>adb reboot
D:\HTC>ad wait-for-device push firewater /data/local/tmp
'ad' is not recognized as an internal or external command,
operable program or batch file.
D:\HTC>adb wait-for-device push firewater /data/local/tmp
4198 KB/s (4522136 bytes in 1.051s)
D:\HTC>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 8.0.6.3 ===========================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
yes
yes
Type 'Yes' or 'No'
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, h
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, h
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, h
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********
DETAILS ABOUT MY PHONE
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.707.104
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****************
(bootloader) imei: ************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4223mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
i got an erro something about wrong kernel any help please
rayenvs said:
i got an erro something about wrong kernel any help please
Click to expand...
Click to collapse
Flash custom kernel.
Bulletproof or Elemental X.
pinbacninh_city said:
Thank pro
S-OFF Hboot 1.57
CID_044
Click to expand...
Click to collapse
i want thissss how to do, i have hboot 1.57 and no CID
Had a major FUBAR when I Unlocked and Rooted phone, took me two days but I got it back. However when I look at the Boot screen OS shows nothing!
Is that a problem?
rayenvs said:
i got an erro something about wrong kernel any help please
Click to expand...
Click to collapse
Try this method. http://forum.xda-developers.com/showpost.php?p=51576339&postcount=385
Flash CM11 Nightly from april, I used Snapshot M5 and flash the teamSeven_57 Kernel. Allow root for adb on setting and use firewater instructions.
tazeo said:
Had a major FUBAR when I Unlocked and Rooted phone, took me two days but I got it back. However when I look at the Boot screen OS shows nothing!
Is that a problem?
Click to expand...
Click to collapse
Are you using TWRP 2.7.x.x this is due to twrp nukeing misc partition you restore it by 're-flashing or updateing firmware. TWRP 2.6.3.3 doesn't cause this problem
pinbacninh_city said:
Thank pro
S-OFF Hboot 1.57
CID_044
Click to expand...
Click to collapse
Can you please tell me how to do this?
Danny201281 said:
Are you using TWRP 2.7.x.x this is due to twrp nukeing misc partition you restore it by 're-flashing or updateing firmware. TWRP 2.6.3.3 doesn't cause this problem
Click to expand...
Click to collapse
Are you by chance referring to the Unknown baseband and IMEI issue?
Also, Swansea, MA?
themod said:
Are you by chance referring to the Unknown baseband and IMEI issue?
Also, Swansea, MA?
Click to expand...
Click to collapse
No this is a different issue, some versions of TWRP wipe the misc partition. So when you boot into the bootloader os version is blank. And if you do getvar all version main: will be blank also. But It has no real negative effect on the phone. It just bugs me
Swansea South Wales UK
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Hello folks,
as for me such guides were really helpful in the past, and there are alway poeple who are new to a device and modding it, I decided to do one on my own, to show you how to perform a reset of your HTC U11 to Full Stock ROM/Firmware.
In many points I tried carrying together all that has been written down prior to this guide in many others, by many others. Thus I - in some kind - just consolidate the fact, using my own words and a little bit different structure than others. Anyway I'll show you my steps again in this tutorial as I think it is of importance to many that they can read the hole to do in one thread. But I advise everyone.
Please note that I will not accept any responsibility for possible occurring bricks. I can only confirm that this tutorial has been used by me, for my specific unit and all went successful.
Look here for [Collection] HTCU U11 – RUU/Firmware/Recovery/OTA/Backups
Regards
{
"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"
}
Restore using a Nandroid Backup
Restore using a RUU
Knowledge of adb/fastboot
htc_fastboot and adb installed
HTC U11
07 RU_CID_FAIL: CID in android-info.txt does not match your phone’s CID
10 RU_MODELID_FAIL: MID in android-info.txt does not match your phone’s MID
12 SIGNATURE FAIL: phone expects an HTC signature and can't find one; or found a wrong one
22 RU_HEADER_ERROR: something wrong with your zip; check md5 of download
23 PARSING IMAGE FAIL: something wrong with the image within the zip
24 ANDROID-INFO FAIL: something wrong with android-info.txt within the zip
32 HEADER ERROR: the zip couldn't be read and unzipped properly; seems same as 22.
33 NOT KNOWN YET: might indicate hardware failure.
35 FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT <PartitionName>): means you can’t flash an image in download mode, as it has to be done in bootloader mode.
41 WRONG MODEL ID: means the RUU is menat for a different device
42 WRONG CUSTOMER ID: means you got to swap CID first
90 PRE-UPDATE FAIL: means it only flashed aboot and you have to run the process again immediately to flash all other partitions. The htc_fastboot.exe now auto-reboots on Error 90!
99 UNKNOWN: usually indicates you are S-ON, but sometimes also recognizes other Security related issues.
130 WRONG MODEL ID: see 41
155 INDICATES DIFFERENT THINGS:
the need to relock bootloader; if S-ON
the RUU cannot be executed, because the software versions of ROM, Firmware and RUU aren't matching
170 CHECK USB: RUU won’t run because ADB isn't working properly
171 USB ERROR: happens all the time when the RUU reboots the phone to download mode. For some reason the device is losing its connection and making a RUU flash virtually impossible . There is an incompatibility between USB 3/3.1 and Fastboot/ADB, as well as an issue with Windows Device Detection on the newer Windows 10 builds.
171 USB ERROR FIX by @Sneakyghost:
How to fix RUU error 171 on Windows 10x64 easily
System: Win 10 Redstone (1607) x64 with Intel based USB3.0 and USB2.0 ports:
Sync Manager from HTC Website
Imported Reg-File from Post #1
Reboot
Click to expand...
Click to collapse
Restore using a Nandroid
flash TWRP custom recovery
download custom recovery at https://twrp.me
reboot to download mode
Code:
adb reboot download
flash recovery image
Code:
htc_fastboot flash recovery nameoftwrp.zip
Restore your Nandroid. If you got none yourself, it might be possible that you’ll find one here.
unzip the according Nandroid
copy Nandroid to TWRP/Backup/SerialNo/Nameofbackup on your extSD
restore Nandroid by using TWRP > RESTORE and choosing above copied Nandroid
Flash incremental OTA firmware
reboot to download mode
perform
Code:
htc_fastboot getvar all
and note down your original software version
download all incremental OTA firmwares to your PC, starting with the one above your current firmware version, up to the software version number of your above choosen Nandroid Backup (ATTENTION: If you are S-OFF it will suffice to download the latest Incremental OTA as well as the latest Combined Full Wipe firmware according to the above choosen Nandroid Backup)
flash all incremental OTA firmwares – one after another – following the below named steps (ATTENTION: If you are S-OFF you start with the Combined FullWipe, and proceed with the Incremental OTA one, to ensure that you’ll be able to receive upcoming OTA updates)
Code:
htc_fastboot flash zip nameoffirmeware.zip
(ATTENTION: this has to be done twice to comlete, and it will flash full firmware, thus TWRP will be replaced by stock recovery)
As soon as you restored the Nandroid and flashed all incremental firmware file up to the current build number of your Nandroid, that's it. Your are now Full Stock again!
Restore using a RUU
reboot to download mode
perform
Code:
htc_fastboot getvar all
and note down your original software version
download the latest Stock RUU for your device over here.
flash your RUU to revert to stock
rename RUU to 2PZCIMG.zip
copy 2PZCIMG.zip to root directory of SD card
reboot to download mode
press Volume Up button to confirm flash of RUU
As soon as your RUU has been flashed sucessfully, that's it. Your are now Full Stock again!
Reserved just in case
Thanks you for this Always needed thread
Is it possible to install a non-branded RUU on a branded device, but otherwise keep things completely stock?
Zico 10 said:
Is it possible to install a non-branded RUU on a branded device, but otherwise keep things completely stock?
Click to expand...
Click to collapse
Not possible for as long as S-OFF isn't available. Will do a de-branding thread as soon as it becomes available.
Sent from my htc_ocnuhl using XDA Labs
deleted
Will this wipe my data?
5m4r7ph0n36uru said:
Not possible for as long as S-OFF isn't available. Will do a de-branding thread as soon as it becomes available.
Click to expand...
Click to collapse
Dying to unbranded my HTC U11 as well...
Will the bootloader say "Relocked" or "Locked" if i use this method and restore it to stock?
Sorry for the basic question.. Its been a long time used a HTC phone.
rkrishnamurthy said:
Will the bootloader say "Relocked" or "Locked" if i use this method and restore it to stock?
Sorry for the basic question.. Its been a long time used a HTC phone.
Click to expand...
Click to collapse
It will say relocked. A real locked state might be possible if S-OFF hits, but no way to do it until then.
Sent from my htc_pmeuhl using XDA Labs
Nice info when in the future want to go back to stock.
Sent from my HTC U11 using XDA Developers 2016 Premium
Hi,
I'm new to android. I was advised to root my HTC U 11 but after doing so and exploring options I decided I'd rather just remove root and return to stock. However, I'm a noob and didn't do a backup before flashing the recovery and rooting. I found this thread and it seems to have what I need but I'm hesitant to take the next step as I don't want to brick my new phone. Can someone explain what I need to do to return to stock in as simple/dumbed down way as possible?
It's a single sim variant, carrier is Optus (Australia) and the original software version was 1.03.710.7
There's only this step by step guide. Couldn't be more precise at what to do. If you don't understand such a detailed guide I'm a little bit irritated at why you rooted in the first part, if you don't know what happens by doing so and how to revert back properly
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
There's only this step by step guide. Couldn't be more precise at what to do. If you don't understand such a detailed guide I'm a little bit irritated at why you rooted in the first part, if you don't know what happens by doing so and how to revert back properly
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
i've did all the steps and still my bootloader will not relock with the RUU method.
Stock RUU flash not working, her is fail message. Any ideas?
Error code 19 RU_MAIN_VER_FAIL os-version in android-info missing or i
mr573162 said:
i've did all the steps and still my bootloader will not relock with the RUU method.
Click to expand...
Click to collapse
RUU any method does not relock bootloader, you have to manually do it in fastboot. Download mode, CMD type fastboot oem lock
---------- Post added at 08:31 AM ---------- Previous post was at 08:27 AM ----------
andybg40 said:
Stock RUU flash not working, her is fail message. Any ideas?
Error code 19 RU_MAIN_VER_FAIL os-version in android-info missing or i
Click to expand...
Click to collapse
Are you flashing the correct RUU?
schmeggy929 said:
RUU any method does not relock bootloader, you have to manually do it in fastboot. Download mode, CMD type fastboot oem lock
---------- Post added at 08:31 AM ---------- Previous post was at 08:27 AM ----------
Are you flashing the correct RUU?
Click to expand...
Click to collapse
Yes I have tried the command of fastboot oem lock and it tells me failed unknown command.
C:\adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.004s
mr573162 said:
Yes I have tried the command of fastboot oem lock and it tells me failed unknown command.
C:\adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.004s
Click to expand...
Click to collapse
You really doing it in download mode, or are you in bootloader?!
Sent from my htc_pmeuhl using XDA Labs
Hello Team, Please help me with ROM or RUU for below phone info
I had my phone rooted and installed TWRP recovery on it.
Now i am trying to go back stock and unroot, installed stock recovery and phone worked well, as soon as i locked the bootloader, the phone loads the first boot splash with red test for a second then shuts down.
If i Unlock the bootloader then it works fine.
Also, i tried factory reset from Stock Recovery but still the same problem.
The phone when booted properly i can always see TWRP application present in my phone even when the phone is on Stock recovery and Full Reset.
Please help.
My Phone info is below.
kernel: lk
product: htc_acawhl
version: 1.0
max-download-size: 1141600000
serialno:
current-slot:
imei:
version-main: 1.33.425.6
boot-mode: download
version-baseband: 01.02_U114401031_125.01.70524G_F
version-bootloader: 1.0.0.0000
mid: 2PYB20000
cid: HTC__059
Hello ......................................
@b8engl said:
Hello Team, Please help me with ROM or RUU for below phone info
I had my phone rooted and installed TWRP recovery on it.
Now i am trying to go back stock and unroot, installed stock recovery and phone worked well, as soon as i locked the bootloader, the phone loads the first boot splash with red test for a second then shuts down.
If i Unlock the bootloader then it works fine.
Also, i tried factory reset from Stock Recovery but still the same problem.
The phone when booted properly i can always see TWRP application present in my phone even when the phone is on Stock recovery and Full Reset.
Please help.
My Phone info is below.
kernel: lk
product: htc_acawhl
version: 1.0
max-download-size: 1141600000
serialno:
current-slot:
imei:
version-main: 1.33.425.6
boot-mode: download
version-baseband: 01.02_U114401031_125.01.70524G_F
version-bootloader: 1.0.0.0000
mid: 2PYB20000
cid: HTC__059
Click to expand...
Click to collapse
Here you go 1.38.615.7
---------- Post added at 03:56 PM ---------- Previous post was at 03:51 PM ----------
Just format a microSD to fat32 and add that ZIP to the root.
Then reboot to download mode ( volume down + power button )
Let it search for the microSD and the phone will update it self
b8engl said:
Here you go 1.38.615.7
---------- Post added at 03:56 PM ---------- Previous post was at 03:51 PM ----------
Just format a microSD to fat32 and add that ZIP to the root.
Then reboot to download mode ( volume down + power button )
Let it search for the microSD and the phone will update it self
Click to expand...
Click to collapse
Didn't work, prompted CID Mismatch error.
I am S-on, unlocked not rooted.
[email protected] said:
Didn't work, prompted CID Mismatch error.
I am S-on, unlocked not rooted.
Click to expand...
Click to collapse
I was exception that error, can't view the CID from this side.
Tomorrow at work, I will view your version 1.33.425.6 and let you know.
here 1.33.425.6 htc_059
https://drive.google.com/file/d/1qA4q2icc9oUztySgAV4abYMYYrYvvuJ0/view?usp=sharing
rename to 2PYBIMG.zip
Thank you so much for the help Buddy.
Thank you so much for the help Buddy.
lcdkhoa said:
here 1.33.425.6 htc_059
https://drive.google.com/file/d/1qA4q2icc9oUztySgAV4abYMYYrYvvuJ0/view?usp=sharing
rename to 2PYBIMG.zip
Click to expand...
Click to collapse
[email protected] said:
Thank you so much for the help Buddy.
Click to expand...
Click to collapse
okay, hope it helps
lcdkhoa said:
okay, hope it helps
Click to expand...
Click to collapse
I lost the Network after boot.
lcdkhoa said:
okay, hope it helps
Click to expand...
Click to collapse
I am in India, Mumbai
lcdkhoa said:
okay, hope it helps
Click to expand...
Click to collapse
I think i need a India Radio for this. Please help if you can.
[email protected] said:
I think i need a India Radio for this. Please help if you can.
Click to expand...
Click to collapse
I flash the same ROM again and it worked the second time but only after reboot.
Wow, Thank you so much.
[email protected] said:
I flash the same ROM again and it worked the second time but only after reboot.
Wow, Thank you so much.
Click to expand...
Click to collapse
After flashing 1.33.425.6, you could update to 1.38.615.7 by flashing boot.img and system.img from #3 link.
lcdkhoa said:
After flashing 1.33.425.6, you could update to 1.38.615.7 by flashing boot.img and system.img from #3 link.
Click to expand...
Click to collapse
How to extract the zip, i am not able to open the zip.
Tried 7zip too to open but no luck.
Use this tool
https://www.google.com.vn/amp/s/for...niversal-htc-ruu-rom-decryption-t3382928/amp/
lcdkhoa said:
Use this tool
https://www.google.com.vn/amp/s/for...niversal-htc-ruu-rom-decryption-t3382928/amp/
Click to expand...
Click to collapse
Wow, great.
This helped, Thank you so much Buddy.
lcdkhoa said:
here 1.33.425.6 htc_059
https://drive.google.com/file/d/1qA4q2icc9oUztySgAV4abYMYYrYvvuJ0/view?usp=sharing
rename to 2PYBIMG.zip
Click to expand...
Click to collapse
Could you re-upload, please?
geojoking said:
Could you re-upload, please?
Click to expand...
Click to collapse
Yours here: https://drive.google.com/file/d/1mXFBo3FELef9QpMHY9LDOdVJ7L_AukRB/view
lcdkhoa said:
here 1.33.425.6 htc_059
https://drive.google.com/file/d/1qA4q2icc9oUztySgAV4abYMYYrYvvuJ0/view?usp=sharing
rename to 2PYBIMG.zip
Click to expand...
Click to collapse
will this work for cid HTC_060?
HTC cid-1111111
Mid 2pyb20000
OS 1.33.425.6
??? Why friend
No IMEI no baseband etc after flashing