Database Develop

update 2.3.6 failled. Why??????

In this day I am trying update my nexus one but when I try appear this sentence:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Why??????
Anyone can help me????

Are you doing it via ota or via zip if your doing it by zip then try redownloading the file your's may be corrupted if it's via ota then you could just try via zip.

I have just try to do redownloading file zip but the sentence not chenge. Do you know why or what means it???
Sent from my Nexus One using XDA App

Try a different browser to download. Maybe z Firefox put Chrome of you're not already on those

Which carrier are you with, and where did you get your phone - it's possible that you have a carrier specific ROM...

Ski_55 said:
In this day I am trying update my nexus one but when I try appear this sentence:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Why??????
Anyone can help me????
Click to expand...
Click to collapse
Are you running a custom recovery? Toggle off signature verification.

no, I have everything stock

Ski_55 said:
no, I have everything stock
Click to expand...
Click to collapse
If you are Vodafone, you are probably running a Vodafone "stock" ROM. You cannot use the update on a Vodafone ROM.
Go to Settings-->About phone. What Android version and what build number do you see?

Android version: 2.3.4
Build: GRJ22
But if I want root my nexus one, can I????
Sent from my Nexus One using XDA App

Ski_55 said:
Android version: 2.3.4
Build: GRJ22
But if I want root my nexus one, can I????
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Well, that looks stock. In the same area, what do you see under kernel version?
If you can't update, you can root by flashing an older shipped image like FRG83 (from here: http:/www.shipped-roms.com) and root that, then upgrade carefully so you do not loose root. You need to download the zip file, rename it to PASSIMG.zip, place it in the root of your sdcard, then boot into the bootloader. Otherwise, just unlock your bootloader, and things become much more simple, and you can have root on any build easily.

Applying the N1 OTA 2.3.6 (GRK39F) update via any recovery: Is this as simple as it sounds?
Download the package, rename to update.zip, copy to root of SD, boot into recovery and apply the update.zip from the SD card?
FYI - I'm using running stock 2.3.4 at the moment, but already unlocked my bootloader and flashed RA-passion-v2.2.1.

Wulfbane said:
Applying the N1 OTA 2.3.6 (GRK39F) update via any recovery: Is this as simple as it sounds?
Download the package, rename to update.zip, copy to root of SD, boot into recovery and apply the update.zip from the SD card?
FYI - I'm using running stock 2.3.4 at the moment, but already unlocked my bootloader and flashed RA-passion-v2.2.1.
Click to expand...
Click to collapse
Yes, it's that simple. However, you need to toggle signature checking in recovery before you apply the update.zip.
P.S. There is no need to rename it to update.zip

efrant said:
Well, that looks stock. In the same area, what do you see under kernel version?
If you can't update, you can root by flashing an older shipped image like FRG83 (from here: http:/www.shipped-roms.com) and root that, then upgrade carefully so you do not loose root. You need to download the zip file, rename it to PASSIMG.zip, place it in the root of your sdcard, then boot into the bootloader. Otherwise, just unlock your bootloader, and things become much more simple, and you can have root on any build easily.
Click to expand...
Click to collapse
I also tried to rotate but I can not downgrade to any previous fersione Android. Can you help me? If I can not unlock the bootloader to not lose the warranty.
With root permissions, then I can install any rom with "Rom manager" right?

Ski_55 said:
I also tried to rotate but I can not downgrade to any previous fersione Android. Can you help me? If I can not unlock the bootloader to not lose the warranty.
With root permissions, then I can install any rom with "Rom manager" right?
Click to expand...
Click to collapse
What is your main version? To find out, connect your device to your PC in fastboot mode, and type this into a terminal window:
fastboot getvar mainver
If it is higher than 2.18.1700.1, then you are out of luck, and there is no way to root without unlocking your bootloader. If it is lower or the same, then you CAN use a PASSIMG.zip file to downgrade to an earlier, rootable version of Gingerbread.

efrant said:
What is your main version? To find out, connect your device to your PC in fastboot mode, and type this into a terminal window:
fastboot getvar mainver
If it is higher than 2.18.1700.1, then you are out of luck, and there is no way to root without unlocking your bootloader. If it is lower or the same, then you CAN use a PASSIMG.zip file to downgrade to an earlier, rootable version of Gingerbread.
Click to expand...
Click to collapse
I don't understand where I must wrote "fastboot getvar mainver".
I Turn off my device
Turn on with power and trackball
Bootloader
fastboot
connect device to pc
and write "fastboot getvar mainver", but where????
Thank you so much

Ski_55 said:
I don't understand where I must wrote "fastboot getvar mainver".
I Turn off my device
Turn on with power and trackball
Bootloader
fastboot
connect device to pc
and write "fastboot getvar mainver", but where????
Thank you so much
Click to expand...
Click to collapse
On windows open your command prompt and navigate to wherever your fastboot executable is (you can use Windows Key + R and type in cmd and hit enter to open the command prompt).

bassmadrigal said:
On windows open your command prompt and navigate to wherever your fastboot executable is (you can use Windows Key + R and type in cmd and hit enter to open the command prompt).
Click to expand...
Click to collapse
I wrote in the prompt but it say that "fastboot is not eseguible"

I am not sure how well I understand the translation. What OS are you running? Because windows shouldn't complain about whether a file is executable or not.

Ski_55 said:
I wrote in the prompt but it say that "fastboot is not eseguible"
Click to expand...
Click to collapse
I think you have one of two possible problems: 1) you don't have the USB driver installed properly or 2) you are issuing the command in the same directory as the fastboot executable.
Sent from my Nexus One using Tapatalk

I found this guide http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/ what do you think?

[Q] cannot root: hboot 2.0 ver. 2.3.5

Hello community!!
I'm new to the HTC/Incredible S world, I have a rooted/cfw LG P500 and now I bought this great phone. Problem is that I updated it to the last official version before this try.
So I went to the official site and I followed successfully the HTC site steps to unlock the bootloader (golden card?) and now I'm trying to follow the guide
http://forum.xda-developers.com/showthread.php?t=1385084
But I have some problems.
First of all clearly the revolutionary program doesn't work (HBOOT 2.0).
I booted to the bootloader (power+volume down) and I had the error "main version is older" then I copied on the SD card the file for the recovery PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip, I renamed it PG32IMG.zip, it loads it but when I press recovery it gives me an allert icon (the phone with a red triangle + red "!" ) and it does nothing.
I installed the SuperUser app like it is written in the post but when I type SU under the adb shell and it gives me "permission denied".
What could I do?
Is it even possible to downgrade it to a rootable/customable version?

If someone write a guide for rooting with the last update installed from original s-on step to step will be very util and a lot of people will be gratefull!
Inviato dal mio HTC Desire usando Tapatalk

Bootloader unlock and goldcard are 2 seperate things. Bootloader unlock is required at the moment for flashing recovery and superuser for rooting the phone.
Gold card is required for flashing another carriers rom.
Read this thread about recovery http://forum.xda-developers.com/showthread.php?t=1104765
After that you can enter recovery mode and flash a superuser zip file http://goo-inside.me/superuser/
My guide should be able to downgrade your rom and get s-off after that (if after researching you decide you require it) http://forum.xda-developers.com/showthread.php?t=1373697
Hope this helps

Thanks, I'm going to try this as soon as I can, I'll write back the results
edit:
It seems like I can't even pass the first step, the 4EXT Recovery Updater doesn't work, it crushes at EVERY menu item....
(I waited 5+minutes and I had the internet connection on).
I checked and the boot loader says "unlocked". Notice that my device is, of course, NOT rooted (at least for what I know for "rooted", it is still unlocked by the HTC official method)....

you need root to use the recovery updater.
download the recovery image and flash it in fastboot

Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...

sariel82 said:
Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...
Click to expand...
Click to collapse
Could I get a couple of screenshots to help with debugging please?

Sure, ASAP

Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.

edit:
It seems I cannot post the images, too noob ....
Anyway:
I had a photo of the phone in the custom recovery mode, another of the phone with the 4EXT recovery successfully flashing his recovery, another of the script of your post running with this message:
(no errors)
Do you have an unlocked bootloader from htcdev.com (I have)
y OR n:y
<waiting for device>
...
(bootloader) Lock successfully..
FAILED (status read failed (Too many links))
finished. total time: 0.239s
Note: run the RUU in fastboot mode
If all steps etc etc
Now if I try to run RUU NOT in fastboot mode I receive the message:
The Utility of ROM udating can't update the Android device.
Take a valid ROM updating Utility and try again
(I'm translating from Italian)
If I try to go to fastboot after running the script I need to go to hboot using volume down+power since you can go to fastboot only through bootloader and HIS first step is to check the bootloader file (am I right?)
so, since it is again LOCKED the custom boot file I was using PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed
doesn't work anymore and the old one neither so I have to unlock it again and it goes the loop......
So this is the situation, I hope I will be able to post some image soon...

sergiopat said:
Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.
Click to expand...
Click to collapse
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.

sariel82 said:
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.
Click to expand...
Click to collapse
OK, I thought you only wanted to root.

Thank you anyway

You don't need s-off for CFW's, just the unlocked bootloader. I cannot help you any further until I see screenshots as I'm getting lost in your descriptions. Ctrl prtscrn, paste in paint.

Well, I have the screenshots but I can't post web links in the forum (new user).
Let's see if I can flash some cfw in the mean time

Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)

sariel82 said:
Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)
Click to expand...
Click to collapse
After you flash a custom ROM in recovery, you have one last step to do to prevent the hang. You extract the boot.img file from the ROM's zip file and then manually flash it in FASTBOOT mode on the phone:
FASTBOOT flash boot [path to boot.img]

That totally solved the problem
Thank you ALL!!!

sariel82 said:
That totally solved the problem
Thank you ALL!!!
Click to expand...
Click to collapse
Hi,
Please list the methods you use from the start. I have also 2.3.5 and hboot 2.0. cant manage to downgrade, i always getting an error.
Thanks

htc developer site -> unlock bootloader
find and download this file:
PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio _20.2810.30.085AU_3805.06.03.16_M_release_199684_s igned.zip
copy it on the sd card and renamto to pg32IMG.zip
reboot in power+volume down mode
go in fastboot
from your pc use fastboot to flash this recovery:
http://forum.xda-developers.com/showthread.php?t=1104765
copy to sd card the superuser file:
http://goo-inside.me/superuser/
enter recovery mode and flash the zip
Then if u want to flash a custom rom you dont need to downgrade, just copy the zip into the sd card, flash it, copy on the sd card the boot.img you find inside the rom zip file and reboot in fastboot (power+volume down)
FASTBOOT flash boot [path to boot.img]
and reboot and the job is done!

Doesn't go into recovery

I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?

It is most likely you did something wrong when you flashed the recovery img, just follow the tuto again and make sure to follow each step.
Here is a guide made by mike: http://forum.xda-developers.com/showthread.php?t=2265618

I have done that. Tried a few times. I am fairly "in the know" with rooting ect, but I just can't figure this out.

Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta

Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.

samflorin said:
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried that.
TarekElsakka said:
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
Click to expand...
Click to collapse
Tried that to.
When I press perm root, it just reboots normal like recovery doesn't even exist.

Have you tried flashing stock recovery and trying to boot in it? I know that doesn't fix anything, I am just curious if your device will actually boot into any recovery state at all. I have read on XDA about some devices not being able to boot into recovery for some reason.
Here's the stock recovery, just in case: http://forum.xda-developers.com/showthread.php?p=38504123

Okay give me a shot at that.
I noticed after flashing recovery, mine doesn't tampered like it should?

The stock recovery says it's not available anymore.

If it doesn't say TAMPERED then the recovery must have not been flashed to begin with and that is why it's not booting into it. Which recovery are you trying to install? I use TWRP 2.5.0 and I flashed it with fastboot then restarted and it booted fine. My device is S-ON, by the way, and running Trickdroid 7.5.
US Developer Edition Recovery: http://d-h.st/b5g
T-Mobile Recovery: https://www.dropbox.com/s/hvs38223dfrzsny/recovery_tmobile.img
I am not sure if either one will work with your device since I am guessing it's international? But they might be worth a shot.
Never mind, I found the stock international recovery for you: https://dl.dropboxusercontent.com/u/22045273/htc1-stock-recovery.img it was on page 4 of the thread. Give it a go.

I flashed the stock recovery and it still boots like there is no recovery there. and it doesn't say "tampered"
This is crap
EDIT: Yeah I figured it's not being flashed since it's not tampered, but no matter what I try it won't flash.
I'm navigating to the folder: CD C:\One_All-In-One_Kit_v\Data\Recoveries then typing fastboot flash recovery recovery.img and it doesn't work.
It says it's flashed ect, but doesn't boot into it, nore show tampered.

This is very weird and unfortunately I do not know the solution to that. I do not use the All-In-One-Kit, actually, but just a mini-SDK with fastboot files inside. I use shift + right click and "open command prompt window here" rather than navigate to the location, it's just much easier that way. Can you try flashing the latest TWRP recovery?

aussiesausage said:
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
Click to expand...
Click to collapse
Are you under s-off ?

tash2013 said:
Are you under s-off ?
Click to expand...
Click to collapse
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.

Would ADB be any better?

Ugh man that's horrible. I honestly do feel your frustration because I have faced similar situations with my HTC devices (One X and One) countless times, and it sucks because you know the correct steps yet it's not working. I sure hope someone knowledgeable about this can come in and help you. Best of luck.
EDIT: I have only used ADB to sideload a ROM but I don't know about flashing recoveries. If you know how to do it, then why not? It's worth a shot for sure.
EDIT #2: And if you're not familiar with ADB, this article should get you started: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Make sure you follow all the steps to the word and also install HTC Sync Manager for the proper drivers to be loaded.

I know right, driving me nuts.
I've never done adb to flash a recovery before but don't know if I would want to be the pidgeon to try lol

aussiesausage said:
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Click to expand...
Click to collapse
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again

tash2013 said:
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
Click to expand...
Click to collapse
Tried that, no go.
Also checked the drivers, re-installed no go.
I am quite up there with adb, but not with flashing recovery with a HTC device lol.

There seems to be another method for flashing recoveries besides fastboot.
http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
This is an HTC Evo section but it could work for the One as well, although I am not sure of it. I have done some Googling and I did not come across any articles/threads saying that it is possible to flash a recovery using ADB, so that might not be possible.

[Q] Can not sideload, push, or restore.

Ok, I know I'm going to catch all kinds of hell probably for posting this. But, I'm stuck. This is the first question I have asked on this forum, and have literally spent days on end searching, and trying new things. What happened is I think I tried flashing a GSM rom (the new android revolution 30.0) onto my Sprint HTC One. I just got this phone two weeks ago, and unfortunately upgraded to the 4.3 with the 1.55 hboot. So, S-on. I was using slimbean as my dd, but wanted to give revolution a try. When I dl the rom, it stated for m7wls, so thought I was good. Well, went into a kind of bootloop where it would upgrade android like 41 out of 120, then it would restart. When it finally would boot up, I had about fifteen seconds before it would reboot again. I tried to wipe and restore, but same thing was happening. I read that the partitions may have been screwed up from the gsm to cdma so, I wiped data and everything. I was going to relock and flash an RUU. Then I find out that there isn't one yet for the 4.3. I tried the Guru reset, updating drivers, sideloading, flashing cwm from twrp, pushing and had a rom boot up once, but no service or gapps. In cmd fastboot, my phone is recognized. But, when I use adb, it can't find it.I can get into recovery, and I have the official android 4.3 stock rom on my laptop ready to flash, but just can't get it to the phone. I am a noob, so I am sorry for that, but we all were at one time or another. I researched, tried to learn as much as I could before I took the plunge. I've read thread upon thread here and in other forums trying to find a fix. Everything that I've tried from some of these posts just didn't work for me. I don't know what I'm doing wrong, and I am not sure what you guys would need from me as far as more info. But, I would be grateful if someone could steer me in the right direction. Thanks in advance, and again apologies if I'm not doing things right for you guys. Just trying to learn and do.
C:\Users\Guest\Desktop\Fastboot>fastboot devices
FA38DS904955 fastboot
C:\Users\Guest\Desktop\Fastboot>fastboot flash rom.zip Dev-3.22.1540.1-Stock-Roo
ted-DE-ODEX.zip
target reported max download size of 1526722560 bytes
sending 'rom.zip' (1061169 KB)...
OKAY [ 47.135s]
writing 'rom.zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 169.469s
This is what cmd tells me when I try to flash the rom.

Dev-3.22.1540.1-Stock-Rooted-DE-ODEX.zip
Click to expand...
Click to collapse
Is not a Sprint rom

bigdaddy619 said:
Is not a Sprint rom
Click to expand...
Click to collapse
Even when I tried to flash slimbean, same thing happens. Thank you for the reply though.
I downloaded super one rom to laptop, tried using adb sideloader, but it doesn't detect my device. I went into mounts and storage on cwm and tried mounting usb, but doesn't toggle. I really am in desperate need of directions. I would even pay if I could lol.

bbjay351 said:
Even when I tried to flash slimbean, same thing happens. Thank you for the reply though.
I downloaded super one rom to laptop, tried using adb sideloader, but it doesn't detect my device. I went into mounts and storage on cwm and tried mounting usb, but doesn't toggle. I really am in desperate need of directions. I would even pay if I could lol.
Click to expand...
Click to collapse
Installed universal usb drivers, got sideload working. But now after installing the rom it is in bootloop.
Installed slimbean, I can get into the rom, but only for a minute or two. I have no service at all. When I go into about phone phone status it shows unknown network, out of service, unknow phone number etc. How do I get that back up and running? And, how do I get it to stop rebooting after a few minutes? Thank you guys

Your partitions are borked from flashing a non Sprint Rom. To fix them
if you are s-on, flash the 4.3 full firmware http://www.androidfilehost.com/?fid=23159073880933344
if you are s-off, flash the modified firmware http://www.androidfilehost.com/?fid=23159073880933456
Then side load your Rom and you should be golden.
Sent from my HTCONE using xda app-developers app

Konfuzion said:
Your partitions are borked from flashing a non Sprint Rom. To fix them
if you are s-on, flash the 4.3 full firmware http://www.androidfilehost.com/?fid=23159073880933344
if you are s-off, flash the modified firmware http://www.androidfilehost.com/?fid=23159073880933456
Then side load your Rom and you should be golden.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Tried sideloading this and fails saying zip file is corrupt.

bbjay351 said:
Tried sideloading this and fails saying zip file is corrupt.
Click to expand...
Click to collapse
I hate to say it but use the Format Data option within TWRP to format your sdcard the try to sideload
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
bbjay351 said:
Tried sideloading this and fails saying zip file is corrupt.
Click to expand...
Click to collapse
Check PM

Get a signed download of the firmware and flash thru fastboot if nothing else.
Sent from my HTCONE using XDA Premium 4 mobile app

Big thanks
Just wanted to say thanks again to Bigdaddy619! Spent the time with me to walk me through. Learned a lot from him. And a thanks to all that replied. Love learning new stuff, even if it makes me pull my hair out lol

bbjay351 said:
Just wanted to say thanks again to Bigdaddy619! Spent the time with me to walk me through. Learned a lot from him. And a thanks to all that replied. Love learning new stuff, even if it makes me pull my hair out lol
Click to expand...
Click to collapse
Updated steps for below
So this is what we did:
1.We downloaded the s-on firmware zip from the link provided by @Konfuzion
2.Renamed it firmware.zip (put the firmware.zip into the folder you use to open your cmd window)
3.Booted to bootloader
4.Then used these commands
Code:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot
He got an error so I had him re-lock his bootloader
5.Ran the commands again
Got another error
Code:
failed 90 hboot pre-update! please flush image again
press the UP Arrow on your keyboard and press enter to issue the command again.
6.He was able to unlock the bootloader again and re-flash TWRP and sideload or adb push a rom to his phone.
7. S-OFF using Rumrunner
8.Win lol

bigdaddy619 said:
So this is what we did:
1.We downloaded the s-on firmware zip from the link provided by @Konfuzion
2.Renamed it firmware.zip (put the firmware.zip into the folder you use to open your cmd window)
3.Booted to bootloader
4.Then used these commands
Code:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot
He got an error so I had him re-lock his bootloader (not sure if it was needed but...)
5.Ran the commands again
Got another error
Code:
failed 90 hboot pre-update! please flush image again
press the UP Arrow on your keyboard and press enter to issue the command again.
6.He was able to unlock the bootloader again and re-flash TWRP and sideload or adb push a rom to his phone.
7. S-OFF using Rumrunner
8.Win lol
Click to expand...
Click to collapse
Ok so I am in a similar position with one of my Sprint devices (I have 2 my kids and mine...) Anyway the device is s-off and had gone into TWRP and formated everything in anticipation of loading a new ROM that 4.3 based so wiped everything and then was going to push the rom with ADB... Problem I am having is that ADB doesn't see the device.
Now it shouldn't be a driver issue as I connected my other device to it with no problem and adb sees it fine.
@bigdaddy619.
I followed steps 1-4 except I used the zip for s-off and received no errors so I went back to twrp and attempted to sideload and still won't work.
Thanks for the assistance.
MG
EDIT: Well looks like it was a driver issue, odd since I wasn't having trouble connecting with my other Sprint HTC One but I changed to the Universal Windows ADB Driver listed here in this post. I also updated to the latest Android-SDK and was able to sideload... Thanks all for the info in this thread!
MG

ROOT HTC U PLay

This is a short guide on rooting for thous who are new to this stuff
Steps:
1: download adb platform tools from here
2: Unlock bootloader. follow the guide on htcdev.
make sure you have htc drivers installed so that you can use oem command in fastboot mode for unlocking
3: Download TWRP
4: Download SuperSU and copy it to your phone's internal memory
5: Enable USB debugging and type "adb reboot-bootloader" from pc
6: Type: "fastboot boot twrp-3.1.1-0-alpine.img"
make sure you have twrp image in same folder as adb.
7: Wait for sometime you will boot into twrp recovery from there select install and select the SuperSU zip file
8: reboot and check for root
Links:
http://www.supersu.com/download
https://developer.android.com/studio/releases/platform-tools.html

has anybody tried this? I'm a bit scared to be the first one

javnostra said:
has anybody tried this? I'm a bit scared to be the first one
Click to expand...
Click to collapse
You should make sure you get a pristine backup at hand, or a RUU appropriate to your device. Otherwise you'll never be able toreturn to a full stock system.
On the U11 it is possible to boot TWRP from fastboot, without flashing it and thus without touching stock recovery. That way I've been able to flash Magisk what's coming with MagiskSU and the possibility to use some Modules. And all without altering the system or replacing stock recovery in the first place.
Sent from my HTC U11 using XDA Labs

javnostra said:
has anybody tried this? I'm a bit scared to be the first one
Click to expand...
Click to collapse
Yes its working without flaws, i have tested it myself. also your not installing recovery this time your booting directly

dranzer006 said:
Yes its working without flaws, i have tested it myself. also your not installing recovery this time your booting directly
Click to expand...
Click to collapse
Thanks, I will try it then.

javnostra said:
Thanks, I will try it then.
Click to expand...
Click to collapse
It works. Thanks a lot. My phone is rooted

5m4r7ph0n36uru said:
You should make sure you get a pristine backup at hand, or a RUU appropriate to your device. Otherwise you'll never be able toreturn to a full stock system.
Click to expand...
Click to collapse
for anyone asking themselves how to backup
https://forum.xda-developers.com/showpost.php?p=53767160&postcount=2
or https://forum.xda-developers.com/showpost.php?p=53770286&postcount=4
or is there a different way these days? @5m4r7ph0n36uru
BerndM14 said:
Connect phone to PC, boot into bootloader mode and type fastboot boot name_of_recovery.img that'll just boot the custom recovery as opposed to flashing it, that way you can make a nandroid backup of all partitions including stock recovery.
Click to expand...
Click to collapse
an0ther said:
The guys method of using recovery to backup recovery will only work on Philz… Not twrp as it does not always backup stock recovery properly. The proper way to backup stock recovery is..
1. Root your phone, which can be done by towel root or by just booting a recovery like he said,
fastboot boot twrporwhatever.img, then flash supersu
2. Boot phone that has stock recovery
3. adb shell
4. su "watch your phone to grant root adb access if you haven't ever done it"
5. dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img
6. This will put flashable recovery.img on your internal sd card. Copy this and save it for later
7. "fastboot flash recovery recovery.img" will get you back to stock recovery, "fastboot flash recovery twrporwhatever.img" to flash custom recovery.
Click to expand...
Click to collapse

If possible and a TWRP recovery is available one should boot to bootloader and try if the command fastboot boot name_of_twrp.img works. Make sure to NOT grant r/w at first boot and leave it ro. Now you can perform a backup of stock recovery, boot and system image (not system partition!) to obtain a pristine backup.
All else will alter system partitions md5 and the backup won't be pristine any longer. Due to block based OTA policy introduced by Google you won't be able to OTA without a pristine system image.
Sent from my HTC U11 using XDA Labs

Bro My Boot Loader is Locked.
Htc dev Not Relised Htc u play Boot loader.

I think these are the instructions. You need to register to access the link
https://www.htcdev.com/bootloader/unlock-instructions
or use my login:
lizba
ALJSDBf234LJABSf
edit: dont use my login. you have to register. you'll get a mail with another page plus a .bin file
https://www.htcdev.com/bootloader/unlock-instructions/page-4/

I have two questions.
1. If I fastboot to TWPR will it stay (flash for good) or after disconnecting my phone it will be gone ?
2. Can I flash Magisk instead of SuperSU ?

Code:
fastboot oem get_identifier_token
FAILED (remote: unknown command)
how i can solve it?

ex71 said:
Code:
fastboot oem get_identifier_token
FAILED (remote: unknown command)
how i can solve it?
Click to expand...
Click to collapse
need enable "OEM unlock" in developers menu, reboot into bootloader and select "download mode". Next steps from original guide.

ex71 said:
need enable "OEM unlock" in developers menu, reboot into bootloader and select "download mode". Next steps from original guide.
Click to expand...
Click to collapse
But in download mode there is no fastboot active ?! Until you installed the correct drivers

no "fastboot" (like a "one s", etc) on this phone. no fastboot usb
"fastboot" command work in "bootloader menu" and "download mode"
fastboot oem only in download mode

Hello. Please explain what I am doing wrong. I will download what is in points. I download this adb something, but it does not work. Nothing starts. Does not communicate with the phone. OCB. Could anyone write this guide so that he could understand and act?