My One is bricked and need help - AT&T HTC One (M7)

I wanted to go back to stock so I went to the [rom][stock][twrp] http://forum.xda-developers.com/showthread.php?p=47851504#post47851504
page and did what was written only to get to step restore system and boot.
I am unable to get to fastboot and am stuck at the htc One splash screen.
I was on cleanroom 6.0 (I think) with twrp
I am using win8 and my work comp is a mac.
What do I need to do?
Thank you guys in advance

sixk said:
I wanted to go back to stock so I went to the [rom][stock][twrp] http://forum.xda-developers.com/showthread.php?p=47851504#post47851504
page and did what was written only to get to step restore system and boot.
I am unable to get to fastboot and am stuck at the htc One splash screen.
I was on cleanroom 6.0 (I think) with twrp
I am using win8 and my work comp is a mac.
What do I need to do?
Thank you guys in advance
Click to expand...
Click to collapse
did you backup your cleanrom install before trying the stock nandroid ?
Do you have Fastboot and ADB working on your windows 8 pc ?
Post the results from
fastboot getvar all
and I can help finding you the correct RUU

clsA said:
did you backup your cleanrom install before trying the stock nandroid ?
Do you have Fastboot and ADB working on your windows 8 pc ?
Post the results from
fastboot getvar all
and I can help finding you the correct RUU
Click to expand...
Click to collapse
I am using the minimal adb and fastboot to use adb
I think I made backup but not a stock backup
Also I am unable to get the fastboot getvar all on adb....
its just stuck on the white HTC one boot screen.
After coming from Samsung to htc everything seems to confusing...
and now that im on a note3 I forgot everything about htc... sad

sixk said:
I am using the minimal adb and fastboot to use adb
I think I made backup but not a stock backup
Also I am unable to get the fastboot getvar all on adb....
its just stuck on the white HTC one boot screen.
After coming from Samsung to htc everything seems to confusing...
and now that im on a note3 I forgot everything about htc... sad
Click to expand...
Click to collapse
Its no problem
just hold the power button down for 10 - 15 seconds to reboot the phone (be sure your in a well lite area or under a bright light)
hold volume down to reboot to recovery and see if you can restore your backup
To run fastboot, hold down the power button and volume down to enter the bootloader
it should say fastboot - now plugin to the PC it should change to fastboot usb
this is where you run the fastboot getvar all command

clsA said:
Its no problem
just hold the power button down for 10 - 15 seconds to reboot the phone (be sure your in a well lite area or under a bright light)
hold volume down to reboot to recovery and see if you can restore your backup
To run fastboot, hold down the power button and volume down to enter the bootloader
it should say fastboot - now plugin to the PC it should change to fastboot usb
this is where you run the fastboot getvar all command
Click to expand...
Click to collapse
Thanks clsA
you were really good with this stuff specially on the cleanrom forum
I will try this out tonight after work.
Thanks again!!!

sixk said:
Thanks clsA
you were really good with this stuff specially on the cleanrom forum
I will try this out tonight after work.
Thanks again!!!
Click to expand...
Click to collapse
just reply to this when you get back
and if your not s-off you should consider doing that first thing
here's the Revone thread if needed ->> http://forum.xda-developers.com/showthread.php?t=2314582
if your already s-off and you just need a RUU the files are here
->> http://www.htc1guru.com/downloads/ruu-file-downloads/
you need the one that's x.xx.502.x for an AT&T Phone
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 - is the newest for AT&T
Also Read here ->> http://forum.xda-developers.com/showthread.php?t=2358738

clsA said:
just reply to this when you get back
and if your not s-off you should consider doing that first thing
here's the Revone thread if needed ->> http://forum.xda-developers.com/showthread.php?t=2314582
if your already s-off and you just need a RUU the files are here
->> http://www.htc1guru.com/downloads/ruu-file-downloads/
you need the one that's x.xx.502.x for an AT&T Phone
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 - is the newest for AT&T
Also Read here ->> http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I uh.... fastboot usb didn't work but I did a recovery in hboot and it returned to factory lol
So I am good!
:good:
Thanks a bunch clsA!

sixk said:
I uh.... fastboot usb didn't work but I did a recovery in hboot and it returned to factory lol
So I am good!
:good:
Thanks a bunch clsA!
Click to expand...
Click to collapse
that's no problem glad you got it working

clsA said:
just reply to this when you get back
and if your not s-off you should consider doing that first thing
here's the Revone thread if needed ->> http://forum.xda-developers.com/showthread.php?t=2314582
if your already s-off and you just need a RUU the files are here
->> http://www.htc1guru.com/downloads/ruu-file-downloads/
you need the one that's x.xx.502.x for an AT&T Phone
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 - is the newest for AT&T
Also Read here ->> http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
hey i also got stuck at the same spot as OP. So these RUU files are exe files. how do I work with them, doesn't my phone need to boot up first?
edit: i get this from getval all
"commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable"

matase said:
hey i also got stuck at the same spot as OP. So these RUU files are exe files. how do I work with them, doesn't my phone need to boot up first?
edit: i get this from getval all
Click to expand...
Click to collapse
the command is
fastboot getvar all
to run a RUU you simply lock the bootloaded from fastboot
fastboot oem lock
and run the ruu from your windows PC

Related

Soft bricked

Well, I guess I unintentionally softbricked my Hero...
So the story:
I downloaded via OTA the update. And i tried to install, but in the middle the install just stopped, and... stood still for a long long time... ok, battery ran out and i plugged the charger and tried to turn on ... annnd stucked at HERO sign...
i tried hard reset and nothing.. im trying that with the SDK and CMD and the fastboot devices doesn't show anything.
I tried to boot one of millions of customed ROMs and nothing, i guess i had to root earlier, or something /noob here.
I kinda ran out of options here and i don't know what to do...
Could you guys please help me out?
Taiwanese version of HTC Hero here.
yep, and i'm kinda desperate here too.
---
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.08.29
Can you force into hboot/fastboot via holding volume down and power for a bit from cold start?
-------------------------------------
Sent via the XDA Tapatalk App
Yes, I Can access HBoot and fastboot...
aaaaaand i found my device at the fastboot devices.
HTxxxxxxxxxx64
Excellent then you should now be able to redo things ... let us know
OK, accessed the hero... then, tried to apply the update and...
E:Failure at line 11: run_program PACKAGE:checkspace -f /data 26214400 "ro.build.fingerprint=chunghwa/htc_hero/hero/hero:1.5CUPCAKE" FOTAERRORMESSAGES
actually i don't know what to do... :/
Try this ... http://forum.xda-developers.com/showpost.php?p=6714023&postcount=14
Basically go back into fastboot and try to install the official 1.5 (which will fail) but the process clears something up and allowed another member here to reflash cleanly ...
Try to wipe your data and then install the next ROM, i had the same problem
I do not think he has rooted or installed a modded recovery image if I read his first post correctly
i guess i had to root earlier, or something /noob here.
Click to expand...
Click to collapse
Yeah, i didn't root or anything... and i tried the other dude footsteps... and... blank, nothing...
and waiting for HTC Response team says something...
tried installing official rom, nothing.
tried updating the official update, also nothing.
tried wipe data, same thing.
well, i guess i have a new brick :/
If you can get it to fastboot ok and open the conversation, there must be something that can be done.
According to the definitive fastboot docs (http://android-dls.com/wiki/index.php?title=Fastboot) there might be a few options to try ...
HTML:
<pre>usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline</pre>
Perhaps the -w to clear those areas might do it ...
Alternatively, I _believe_ you could flash the 1.62 recovery image to the phone in fastboot and then wipe from in there, or flash an 'update.zip' style rom from in here as well ...
Good luck, someone more knowledgeable than I may have other ideas ...
Broken Root???????
WELLLLLL...
I'm not sure how I did it, but I cannot open my custom recovery image. Happened a couple weeks after I flashed a new image. When I tried to apply an update.zip, the image froze at the 'opening update package' stage. I tried multiple roms and wipes to fix the problem, but none worked.
I've flashed multiple images through the terminal, and cannot open any. I've tried using flashrec again, but command line error always pops up. The error in fastboot when trying to load the image is as follows "Wrong or no image!"
This error reoccurs several times as the image recovery is attemped to be retrieved several times.
My rom is Darchdroid 262, and works 100%.
chachi said:
If you can get it to fastboot ok and open the conversation, there must be something that can be done.
According to the definitive fastboot docs (http://android-dls.com/wiki/index.php?title=Fastboot) there might be a few options to try ...
Click to expand...
Click to collapse
I was having a play with those commands yesterday to see if it was possible to restore to a ROM through fastboot but had no luck unfortunately.
chachi said:
If you can get it to fastboot ok and open the conversation, there must be something that can be done.
According to the definitive fastboot docs there might be a few options to try ...
HTML:
<pre>usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline</pre>
Perhaps the -w to clear those areas might do it ...
Alternatively, I _believe_ you could flash the 1.62 recovery image to the phone in fastboot and then wipe from in there, or flash an 'update.zip' style rom from in here as well ...
Good luck, someone more knowledgeable than I may have other ideas ...
Click to expand...
Click to collapse
tried the fastboot -w and... not allow. I will try with the gold card.
Yeah, i'll try the 1.62, but the ADB don't find my device.
Try this,...
Go into fastboot on your phone.
Open CMD and type the following, obviously you will have to change slightly depending on where you extracted the sdk to.
cd c:\sdk\tools
fastboot oem rebootRUU
Then try running one of the 1.5 RUU .exe files on your pc/lappy.
ddotpatel said:
Try this,...
Go into fastboot on your phone.
Open CMD and type the following, obviously you will have to change slightly depending on where you extracted the sdk to.
cd c:\sdk\tools
fastboot oem rebootRUU
Then try running one of the 1.5 RUU .exe files on your pc/lappy.
Click to expand...
Click to collapse
i tried running one of the southeast asia RUU, the 2.73.728.5 file yesterday, and... nothing show up. Sayin' ive got to use the correct one.
The thing i thinked about is to rewrite the checksum in the update (the taiwanese 1.5 to 2.1 the one i've tried to update), verifying if its cupcake (in the fact that the update stopped in the middle), so if delete the verification code, it will continue the installation, and hopefuly, boot correctly.
-
update: ok trying to update again, then he says:
Error in checkspace (Status 256)
run_program PACKAGE:checkspace -f /data 26214400 "ro.build.fingerprint=chunghwa/htc_hero/hero/hero:1.5/CUPCAKE" FOTAERRORMESSAGES
Instalation aborted.
Click to expand...
Click to collapse
OK,... Now this,...
cd c:\sdk\tools
fastboot oem rebootRUU
fastboot erase cache
then try running the RUU again....... ?
Customer ID error... can't it erase the previous update?
it hasn't the original taiwanese RUU available?
the 2.73.751.13 file?
Customer ID Error?.... Ahaaaa,..... We might be on to something. Try with a goldcard now.
Use an old RUU with 1.5, not the new 2.1 ROM.
If you need to know how to make a goldcard follow BTDAGs guide linked in my signature.
ddotpatel said:
Customer ID Error?.... Ahaaaa,..... We might be on to something. Try with a goldcard now.
Use an old RUU with 1.5, not the new 2.1 ROM.
If you need to know how to make a goldcard follow BTDAGs guide linked in my signature.
Click to expand...
Click to collapse
This is beginning to sound like a happy ending is more than a remote possibility now
chachi said:
This is beginning to sound like a happy ending is more than a remote possibility now
Click to expand...
Click to collapse
Don't speak too soon, we might not be on to a winner just yet,.... Fingers crossed.

[Recovery and Rom] Stock US 1.6 Build 6601

Recovery
You should have fastboot installed properly on your system to be able to flash it.
Heres a quick guide for Mac (which is really similar to Linux, search for XP guides which are available all over)
FASTBOOT
Download Fastboot from http://developer.htc.com/adp.html
Unzip and move to whatever folder you want.
I put it in /Users/MyName/Android
OPTIONAL Rename from "fastboot-mac" to "fastboot" (makes following guides made for xp and linux easier)
Now you have to append it to your .bash_profile
Easy Way
Follow instructions on http://donovan.covblogs.com/archives/027838.html to edit the bash_profile visually with textwrangler.
Your .bash_profile should look like this:
Code:
export PATH=$PATH:/Users/MyName/Android
export PATH=$PATH:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
remember to edit the path to wherever you put your fastboot file (some people like to put it in the tools folder in the android sdk so adb is added to the .bash_profile as well)
or
Terminal Way
Code:
export PATH="$Path:/Users/MyName/Android"
Hit enter
Now refresh your .bash_profile
Code:
~/.bash_profile
To see if you've done it right
Code:
fastboot --help
or
Code:
fastboot --h
If the help text shows in terminal in another directory other than where fastboot is then you've got it right
Code:
$fastboot --help
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
To use the fastboot command your device has to be in fastboot mode
Enter FASTBOOT_MODE
Hold power button with device off and when the Home/Menu/Back buttons light up, release power button then press and hold the camera button
Dell logo will appear shortly followed by a white screen.
Tap fastboot in the top right
Thank you mzsigler from modaco for pointing out this simple step i missed.
finally:
FLASH RECOVERY IMAGE
Download the attached file and unzip it.
Make sure terminal is in the directory where the recovery-US6601.img is.
Use
Code:
pwd
to see which directory ur in
Code:
$ fastboot -i 0x413c flash recovery recovery-US6601.img
sending 'recovery' (3280 KB)... OKAY
writing 'recovery'... OKAY
$
Now reboot your device and hold both volume keys to get into recovery mode.
To the 6 people who downloaded it first, i might of uploaded the wrong one because i forgot that before i did nandroid backup i had flashed a different recovery to get clockword mod to work. This should be the right one now which was pulled using adb shell before clockworkmod.
Dell Streak stock US 1.6 Build 6601
There are several ways to restore/flash this i'll mention 2 Fastboot and nandroid
Fastboot
Code:
fastboot -i 0x413c flash boot boot.img
fastboot -i 0x413c flash system system.img
fastboot -i 0x413c flash cache cache.img
fastboot -i 0x413c flash userdata data.img
fastboot -i 0x413c flash recovery recovery.img
Technically you don't need to worry about flashing cache.img and data.img but i performed this backup after a factory reset so your not taking any of my personal info/data
fasboot didn't work for me for so i restored with nandroid
Nandroid
+Create a folder named "Clockworkmod" on your storage card
+In that folder create a folder named "backup"
+Create a folder in "backup" named whatever you want and place boot.img, system.img, cache.img, data.img, recovery.img and nandroid.md5 in that folder.
+Flash Clockworkmod Recovery
2.5.0.1 didnt work on mine but 1.8.1.7 did :/
+Enter clockworkmod recovery
-Power on device while holding both volume keys, then select "2. Software upgrade via Update.pkd on SD Card"
Now you should be in ClockworkMod Recovery
-Scroll down to nandroid using the volume keys and press the camera button to select it
-Select Restore and choose your folder (the one you placed in the backup folder)
Now although this flashes 1.6 build 6601 it doesn't return the baseband to *****31
this is what mine now reads
Basband version
GAUSB1A110421-US
Kernel version
2.6.29-perf
OEM version
GAUSB1a111231
Build number
6601
Click to expand...
Click to collapse
Also be warned that after i returned to 1.6 i got the crazy home/menu/back lights as seen in this video I'm guessing it has something to do with the 21 baseband and 31 oem version
I think this is worthy of a sticky great work my friend keep it up
thanks for the files. wonder how to restore the 6601 baseband.
johnnobts said:
thanks for the files. wonder how to restore the 6601 baseband.
Click to expand...
Click to collapse
Yep, trying to figure that out now.. well back it up first from a device that hasn't been messed with.
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Any ideas?
when i flashed the recovery my screen got stuck at a black screen after the reboot
Worked great for me. Back to the out of the box experience.
do you have flashing lights though? or did your baseband not change? Also, maybe after returning to 6601, you can apply the 31 build? Or you already tried that, didn't you, fone? No change to baseband?
http://forum.xda-developers.com/sho...date.dell.com/LatestBuild/LatestBuild_31.html
uberamd said:
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Any ideas?
Click to expand...
Click to collapse
Are the other items flashing?
lbj23numb1 said:
when i flashed the recovery my screen got stuck at a black screen after the reboot
Click to expand...
Click to collapse
which method did you use to flash and can you still access the recovery but holding down both volume buttons after you power your device on?
Bohemian said:
Worked great for me. Back to the out of the box experience.
Click to expand...
Click to collapse
Does your baseband end in 21-US or 31-US and are your capacitive button lights going crazy or normal?
johnnobts said:
do you have flashing lights though? or did your baseband not change? Also, maybe after returning to 6601, you can apply the 31 build? Or you already tried that, didn't you, fone? No change to baseband?
http://forum.xda-developers.com/sho...date.dell.com/LatestBuild/LatestBuild_31.html
Click to expand...
Click to collapse
My baseband is still at 21-US although OEM version is at 31. I have a suspicion that fastboot isn't properly writing the recovery.img for me..
I tried to use that latest update and half way through i got an error "FOTA model name mismatch"
I'm currently trying to figure a way to pull the baseband so we can do a true full restore. (now i'm worried if i can get 2.2 when its released since my device is at 21-US)
Bohemian said:
Worked great for me. Back to the out of the box experience.
Click to expand...
Click to collapse
Same here. Finally no O2 logo...
johnnobts said:
do you have flashing lights though? or did your baseband not change? Also, maybe after returning to 6601, you can apply the 31 build? Or you already tried that, didn't you, fone? No change to baseband?
http://forum.xda-developers.com/sho...date.dell.com/LatestBuild/LatestBuild_31.html
Click to expand...
Click to collapse
I had flashing lights. Flashing r2-4399-streak-superboot fixed the problem.
I am still at my original baseband. 21-EU
Stock 31 update is 4917. Why would you want to downgrade from 6601?
because we are in the US and are a little concerned we may not be able to apply the 2.2 upgrade with a modified baseband. fone, i don't think the baseband change will make a difference. i am concerned about the flashing lights as of right now.
fone_fanatic said:
Are the other items flashing?
which method did you use to flash and can you still access the recovery but holding down both volume buttons after you power your device on?
Does your baseband end in 21-US or 31-US and are your capacitive button lights going crazy or normal?
My baseband is still at 21-US although OEM version is at 31. I have a suspicion that fastboot isn't properly writing the recovery.img for me..
I tried to use that latest update and half way through i got an error "FOTA model name mismatch"
I'm currently trying to figure a way to pull the baseband so we can do a true full restore. (now i'm worried if i can get 2.2 when its released since my device is at 21-US)
Click to expand...
Click to collapse
I can still get to the recovery using the buttons but when I select the second option that's when I get stuck at a black screen. I flashed the recovery through fastboot
No change in numbers and now no flashing lights. Still can not get to recovery, clockworkmod just reboots and button mode goes to standard recover and selectin option 2 goes black screen.
Model; Dell Streak
Firmware; 1.6
Baseband; GAUSB1A111231-US
Kernel; 2.6.29-perf
OEM; GAUSB1A111231
Build; 6601
I haven't been able to find any information about backing up baseband in order to do a restore.
get stuck on dell logo boot
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Please help
Hi fone-fanatic
Could you explain how backing up the recovery.img to be able to flash it ?
Thanks
gomesj said:
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Please help
Click to expand...
Click to collapse
I am having the exact same issue. Any advice?
I initially flashed this via fastboot and was stuck at the dell logo. i then flashed to the 02 1.6 rom and re flashed the att rom via clockwork mod nandroid. i am up and running but the lights flash like crazy and everything has "an unexpected error" and closes. cant open contacts, set up gmail, open "phone" so i cant get to the dialer. am i the only one getting all the force closes?
I would reflash mate

"""WARNING"""

Just wanted to give everyone a heads up so no one makes the mistake i did. If you get into a postition where your bootlooping and no matter how much you wipe, flash, nand, whatever. And you still get htc bootloop. DO NOT flash any of the PG86IMG that are derived from the RUU(not saying there is anything wrong with those files). By doing that you will remove the revolutionary fastboot drivers from your hboot. Which in turn will lead to you not being able to fix the problem since fastboot will no longer work to run commands from your pc. So to make a long story short if you run into this problem just take the time to install SDK and use fastboot to flash and wipe the partitions(specifically the boot partition). Hope this helps someone.
Thanks for the tip bro
Sent from my 3VO
I figure id put it out there so we dont get anymore bricks. I know everyone says there not bricked unless you cant power into bootloader. But i have tried everything that i know of. Unless there is a way to remount and format the boot partition and flash just using adb instead of fastboot since adb works in recovery. who knows i bought a new one last night im still gonna play around and try to find a fix but i been without a phone for two days lol.
Just for the record I'm sure you've tried these:
http://android-dls.com/wiki/index.php?title=Fastboot
wiki said:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
Click to expand...
Click to collapse
an example of how to use it for the installation of revolutionary: (albeit in virtual box)
http://forum.xda-developers.com/showthread.php?p=16267669#post16267669
example said:
Next let's try fast boot.
With the phone, check the status of fastboot, in Settings>power>fastboot check marked.
Power off, remove battery, reboot while holding volume down key.
You'll see in red, "Fastboot Usb"
The VirtualBox usb icon should now show "Htc....[0100]".
Check mark it.
In terminal type "Fastboot devices (cr)".
You should get the serial number again.
Experiment until it's consistent.
Click to expand...
Click to collapse
Good luck
Yea tried all that. There is no working fastboot now that the hboot was flashed. I can only get the adb to connect while in recovery. If i try to run revolutionary from recovery it says sbin/sh bootloader not supported. And if i am in the bootloader or fastboot usb it just says waiting for device. I can however get revolutionary to start if i flash a custom ROM and try to reboot but it bootloops before the exploit can finish. Oh yeah even if the phone is off revolutionary will tell me device not supported.
Sent from my PG86100 using XDA App
IIRC revolutionary only works on certain hboot versions. You need to down grade if you're s-off. Actually google xda 3d hboot down grade.
Luck
willy900wonka said:
IIRC revolutionary only works on certain hboot versions. You need to down grade if you're s-off. Actually google xda 3d hboot down grade.
Luck
Click to expand...
Click to collapse
My phone has hboot 1.4 already
Sent from my PG86100 using XDA App

[How-To] From S-OFF to 100% Stock S-ON [Facepalm/JTAG/RevOne/Moonshine/Rumrunner]

ONLY FOLLOW THIS GUIDE FOR WARRANTY REPLACEMENTS OR IF YOU NEED TO BE STOCK FOR A SALE. THERE IS NO OTHER REASON TO FOLLOW THIS GUIDE.
ALSO MAKE SURE YOU FOLLOW THE GUIDE PROPERLY. FAR TOO MANY ERRORS ARE BEING MADE BY NOT READING OR FOLLOWING STEPS IN ORDER.
This guide will help you get your phone back to stock after using any of the 5 S-Off methods that either have been or are currently available to us.
Credit to Scotty1223. I edited his One S guide for the DNA.
First post is for Facepalm and JTAG S-off only. RevOne instructions are in the second post. Moonshine and Rumrunner is in post 3.
***IF YOU HAVE A CUSTOM SPLASH SCREEN INSTALLED, THE STOCK SPLASH SCREEN MUST BE FLASHED BEFORE DOING ANYTHING! SEE FOURTH POST FOR LINKS AND INSTRUCTIONS FOR FLASHING THE STOCK SPLASH SCREEN***
***DO NOT ISSUE ANY OF THE WRITESECUREFLAG COMMANDS ON AN ENG HBOOT AS IT WILL BRICK THE DEVICE. JUST FOLLOW THE GUIDE.***
For those who want to return to stock and have used the JTAG method for achieving S-Off, this guide will also work for you. It all depends on what you did AFTER you got your JTAG phone back. If you wrote a new CID using fastboot and HTCDev unlocked, follow the guide as it is written out.
If you didn't write a new CID and use HTCDev unlock and just merely flashed a modified/ENG HBOOT, then the process would be: Fastboot flash stock hboot, RUU to stock, fastboot oem writesecureflag 3, then allow phone to update using the OTA process. You can find the commands/files/steps for these 3 simple steps below as well.
Files needed:
Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
3.06 RUU: 3.06 RUU
Steps:
1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
Verify you are **LOCKED** If not, re-flash the zip. If still not locked, try downloading the file again and re-flashing.
IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4
3. run the RUU as admin (right click, run as administrator)
4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
5. Run the following:
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writecid VZW__001 (2 underscores)
fastboot reboot-bootloader
fastboot getvar cid (verify your stock CID)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Should now be 100% stock, S-ON, with CID 100% stock as well.
Returning to stock from RevOne
It is pretty much the same process, but with a slight deviation.
AGAIN, IF YOU HAVE A MODIFIED/ENG HBOOT, DO NOT ISSUE ANY WRITESECURE FLAG COMMANDS. JUST FOLLOW THE GUIDE.
First, download these two files:
Files needed:
Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
3.06 RUU: 3.06 RUU
Steps:
1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
Verify you are **LOCKED** If not, re-flash the zip. If still not locked, try downloading the file again and re-flashing.
IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4
3. run the RUU as admin (right click, run as administrator)
4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
5. Run the following:
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
You are now out of box stock.
Return to stock on Moonshine, Rumrunner and Firewater S-Off
Files needed:
Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
3.06 RUU: 3.06 RUU
Steps:
1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
You are locked. The s-off process removes the flag from displaying, but it is now locked.
IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4
3. run the RUU as admin (right click, run as administrator)
4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
5. Run the following:
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
You are now out of box stock.
FLASHING THE STOCK HBOOT:
*Credit to .torrented*
1. download 3.06 HBOOT: 3.06 HBOOT
2. Rename stock hboot file to : PL83IMG.zip and place in the folder that contains your fastboot.exe file (On your computer)
3. Flash hboot
Code:
Step 1) adb reboot bootloader
Step 2) fastboot oem rebootRUU
Step 3) CD to directory containing hboot zip (i.e. cd C:\sdk\)
Step 4) fastboot flash zip PL83IMG.zip
*** When it says it is done in the terminal/cmdprompt execute the following ***
[The green bar only fills up about 75% of the way]
Step 5) fastboot reboot-bootloader
Flashing the Stock Splash Image
*All credit goes to E.T.Heil
1. Download the stock splash image here.
2. Rename file to splash1.img
3. Place the file in the same folder you have adb.exe and fastboot.exe located.
4. Plug in your phone to a USB port, turn on USB debugging and open a command prompt. cd to the directory your adb/fastboot is located
5. Run the following:
Code:
adb devices (your device ID should be displayed)
adb reboot bootloader
Once in the bootloader, run:
Code:
fastboot flash splash1 splash1.img
Once complete, reboot the phone using the menu or
Code:
fastboot reboot
updated with RevOne and Moonshine...
If anyone sees anything I missed let me know. Otherwise guide is complete.
Thank you so much for making this post. This is exactly what I needed. I am not quite sure which method I uses but it was the first one that required changing the CID, unlocking via htc dev and all that stuff. Would that be facepalm? Sorry if this is a dumb question, it was so long ago that I don't quite remember.
Imacellist said:
Thank you so much for making this post. This is exactly what I needed. I am not quite sure which method I uses but it was the first one that required changing the CID, unlocking via htc dev and all that stuff. Would that be facepalm? Sorry if this is a dumb question, it was so long ago that I don't quite remember.
Click to expand...
Click to collapse
Yes that was the Facepalm method. So follow the OP guide for that.
I love you! (no homo).
when i run RUU i get error 155 so i tried to flash the 1.15 hboot and i get this error in cmd
D:\Documents and Settings\Jonathan\My Documents\HTC\adt-bundle-windows-x86-20130
219\sdk\platform-tools>fastboot flash zip PL83IMG.zip
sending 'zip' (2047 KB)...
OKAY [ 0.375s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 0.562s
am i doing something wrong? i want to get my phone back to complete stock because i flashed a rom after moonshining without making a backup first. so i really want to get to stock so i can do the whole process over again (moonshine again if needed)
Prodiigy said:
when i run RUU i get error 155 so i tried to flash the 1.15 hboot and i get this error in cmd
D:\Documents and Settings\Jonathan\My Documents\HTC\adt-bundle-windows-x86-20130
219\sdk\platform-tools>fastboot flash zip PL83IMG.zip
sending 'zip' (2047 KB)...
OKAY [ 0.375s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 0.562s
am i doing something wrong? i want to get my phone back to complete stock because i flashed a rom after moonshining without making a backup first. so i really want to get to stock so i can do the whole process over again (moonshine again if needed)
Click to expand...
Click to collapse
Possibly a bad download, Download the HBOOT again and give it another go.
Also, with that error you are getting during the RUU process, did you lock the bootloader back up before running the RUU? That error sometimes shows up from not doing that.
I don't know if this will help anyone or not, or if this was known and I was just being stupid, but I was getting the ERROR [155] as well when running the RUU and I knew my hboot was correct as well as locked so that wasn't the problem, so I attempted to run the RUU again and saw that it was saying my current version was 1.28.xxxxxx which made me realize that that was the Sense 5 roms version number and not the actual version number of my phone causing it to fail. What I then did was i downloaded an AOSP based rom (but I would surmise that a sense 4 DNA rom would work as well) and flashed that then tried again. After doing that it showed the correct version number in the RUU and processed correctly!!
For a little more in site I was on the following setup:
Moonshine S-OFF
Joelz Stock Sense 5 <-- What caused the Error 155
Carbon ROM (Built by Pio) <--- What fixed the error (Would work with any AOSP or Sense 4 Rom ***Needs tested***)
**Edit**
Also incase anyone was wondering I was doing this to fix my phones radio, for some reason when flashing certain roms it gets stuck in Roaming no matter what you do. To fix it I just take my phone completely back to stock S-ON etc, then go into the bootloader and hit factory reset with the stock recovery and it seems to fix it, then S-Off and unlock again and go about my business. I couldn't actually find an answer besides "RMA the thing" to fix the radio roaming issue, so i figured i'd add that incase anyone else was/is in the same boat.
Hmm... I'll do a bit of testing on that with random Sense 5 vs AOSP/Sense 4 ROMs. If that is the case, I'll edit the guide.
I successfully restored my droid dna to untouched stock with this method. I had to exchange my DNA for a new one due to problems I was having and I am trying to do everything I can to make sure that there is no evidence of my tampering. One thing someone mentioned was to take the OTA's to get the device up to current 2.06 since I have been rooted and such since the first day it was available and am on 1.15. I have tried manually checking for software updates and it doesn't seem to find anything. It hasn't prompted me yet and I am wondering if because I am so far behind if they update system isn't checking or something else it wrong. Any thoughts? Any ways to manually update to 2.06 like flashing a new RUU (if that exists)? Thanks.
Just leave the phone on... I did it a few weeks back. It will eventually update.
Phaded said:
Just leave the phone on... I did it a few weeks back. It will eventually update.
Click to expand...
Click to collapse
Thanks. Verizon is only giving me 5 days to ship it back haha. So I just wanted to figure it out as quickly as possible.
Confirmed that on Sense 5 ROMs it randomly errors out. Editing guide.
I flashed the hboot zip and the hboot version is1.33 The phone is s-off and locked on viper rom. The RUU will reboot the phone into the black screen with the silver HTC logo, then the RUU stops working and asks to close the program. I downloaded three times and checked the md5 each time and its good. I am stuck. Any suggestions?
gris1016 said:
I flashed the hboot zip and the hboot version is1.33 The phone is s-off and locked on viper rom. The RUU will reboot the phone into the black screen with the silver HTC logo, then the RUU stops working and asks to close the program. I downloaded three times and checked the md5 each time and its good. I am stuck. Any suggestions?
Click to expand...
Click to collapse
The RUU itself crashes on the computer or the phone crashes and reboots?
Also the hboot I have linked should give you version 1.31 I do believe.
Thanks for this, worked perfectly!
Phaded said:
Return to stock on Moonshine S-Off
First, download the stock RUU
Stock RUU: 1.15 RUU: Mirror #1 or Mirror #2
Plug your phone into a USB port, turn on USB debugging and open a command prompt. cd to the directory that has adb/fastboot.
**NOTE** I noticed on the XDA mobile app that it breaks the echo command line up and makes it look like 2 separate commands. Do not separate it. The command starts at echo and ends at 33796.
Run:
Code:
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Your bootloader is now locked. Lets verify...
Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
Verify you are **LOCKED**
Click to expand...
Click to collapse
I am having issues not getting the phone to return to "Locked" status. I have and am running the stock ROM. Just reset back to factory. I am following the commands to the T. Below is what my CMD prompt shows that I typed in, or copied and pasted for the echo command. I was trying to follow the note about the echo command but I could see nothing wrong with it... also in the end I had to type exit command twice for it exit and go back to the prompt for the next folder.
C:\android-adb>adb devices
List of devices attached
FA2C2S510423 device
C:\android-adb>adb shell
[email protected]:/ # su
su
[email protected]:/ # echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 s
eek=33796
d of=/dev/block/mmcblk0p3 bs=1 seek=33796 <
4+0 records in
4+0 records out
4 bytes transferred in 0.007 secs (571 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
C:\android-adb>
Click to expand...
Click to collapse

Stuck at Boot loader

I am trying to restock Verizon Droid DNA
Followed all the guided method , got to a point of where Relocked/S-ON
Unable to use RUU downloaded , check MD5 all correct
Try moonshine to enable S-OFF
flashed firmware and now stuck at 2.06 firmware
How do i restock?
I am unable to boot anything just the bootloader
fastboot is working fine
Unable to flash any zip hboot downloaded , keep getting signature fail
Unable to Unlocked the bootloader too
I am unable to execute adb commad tho
any suggestion?
BloodRaven2011 said:
I am trying to restock Verizon Droid DNA
Followed all the guided method , got to a point of where Relocked/S-ON
Unable to use RUU downloaded , check MD5 all correct
Try moonshine to enable S-OFF
flashed firmware and now stuck at 2.06 firmware
How do i restock?
I am unable to boot anything just the bootloader
fastboot is working fine
Unable to flash any zip hboot downloaded , keep getting signature fail
Unable to Unlocked the bootloader too
I am unable to execute adb commad tho
any suggestion?
Click to expand...
Click to collapse
You said you tried moonshine to get s-off? did it not work?
You need to be a bit more clear. You are trying to go complete stock or use moonshine to unlock and soff? What error do you get when trying to use ruu?
Hit thanks if I helped! Check out my site at www.circuitsaviors.com
Use moonshine to s off. Go to the thread on how to go back to stock. Follow the directions. The signature is obviously failing because you are s on...
Sent from my HTC6500LVW using xda app-developers app
You might want to check out my thread (http://forum.xda-developers.com/showthread.php?t=2438199), but it's not good news...
jtag is ur only answer. I have a htc dna sitting in my drawer because of this very same reason. I've looked and looked. Sorry
People, you need to RUU BEFORE issuing any s-on commands. I'm seeing this repeatedly.
Phaded said:
People, you need to RUU BEFORE issuing any s-on commands. I'm seeing this repeatedly.
Click to expand...
Click to collapse
This is where the problem rise
I did not realize that is no way to downgrade to stock HBOOT
and the worst part now is i cant do anything
yes , option is to JTAG
BloodRaven2011 said:
This is where the problem rise
I did not realize that is no way to downgrade to stock HBOOT
and the worst part now is i cant do anything
yes , option is to JTAG
Click to expand...
Click to collapse
You could've downgraded your hboot... This also needs to be done before issuing any s-on commands
I am unable to issue a new hboot , i got the signature verification failed. If anyone know how to , it be great , JTAG is my last option tho
Check your PMs. I'd be interested in your results.
I think I had the same signature error a few days ago u need to be on the 1.15 Hboot I couldn't figure it out until i read somewhere not to add a .zip when you rename the hboot zip file and it will flash correctly thru adb hope this helps
http://forum.xda-developers.com/showthread.php?p=42352912
Sent from my HTC6435LVW using Tapatalk 2
xaalfx said:
I think I had the same signature error a few days ago u need to be on the 1.15 Hboot I couldn't figure it out until i read somewhere not to add a .zip when you rename the hboot zip file and it will flash correctly thru adb hope this helps
http://forum.xda-developers.com/showthread.php?p=42352912
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
i am unable to use adb command.
I've been reading thru that before i ask this question
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
I'm confused. Maybe someone can answer.
He flashed the 2.06 firmware successfully. That will flash a the new hboot, radio and recovery.
Unless he has a custom splash screen, why would RUU'ing fail.
What happens if the 2.06 firmware it's flashed again?
Does it pass the checks?
Nvm: he can't RUU because the hboot has to 1.15.
Gungrave223 said:
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
Click to expand...
Click to collapse
all the above failing due to higher fw
and this causing sgnature verification fail
Gungrave223 said:
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
Click to expand...
Click to collapse
fr4nk1yn said:
I'm confused. Maybe someone can answer.
He flashed the 2.06 firmware successfully. That will flash a the new hboot, radio and recovery.
Unless he has a custom splash screen, why would RUU'ing fail.
What happens if the 2.06 firmware it's flashed again?
Does it pass the checks?
Nvm: he can't RUU because the hboot has to 1.15.
Click to expand...
Click to collapse
YEAP ,
It need 1.15
anyhow i can fake this to accept a lower hboot?
with a different sgnature?
BloodRaven2011 said:
YEAP ,
It need 1.15
anyhow i can fake this to accept a lower hboot?
with a different sgnature?
Click to expand...
Click to collapse
It's not a signature issue, it's encryption issue. Newer hboots are unable to decrypt the older ruu zip. If you have a "stockish" rom, you can reflash the 2.06 firmware zip. this will flash a signed kernel and recovery and allow the device to _attempt_ to boot to android. If you can get to android, you can then attempt to s-off again.
If moonshine repeatedly fails (don't drink and shine) and also revone repeatedly fails try this:
In moonshine folder you'll see dnashellroot.apk package
1.) adb install dnashellroot.apk
2.) adb shell
3.) am start -n c.fyf/.MainActivity
4.) (wait 10 seconds)
5.) /dev/sh ($ should turn into #)
6.) echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
^do NOT screw that command up, copy/paste it or risk a brick
7.) exit
8.) exit
9.) adb reboot bootloader
10.) fastboot getvar cid
if it's 22222222, you are good. Proceed to htcdev to unlock, then you can s-off using facepalm.
beaups said:
It's not a signature issue, it's encryption issue. Newer hboots are unable to decrypt the older ruu zip. If you have a "stockish" rom, you can reflash the 2.06 firmware zip. this will flash a signed kernel and recovery and allow the device to _attempt_ to boot to android. If you can get to android, you can then attempt to s-off again.
If moonshine repeatedly fails (don't drink and shine) and also revone repeatedly fails try this:
In moonshine folder you'll see dnashellroot.apk package
1.) adb install dnashellroot.apk
2.) adb shell
3.) am start -n c.fyf/.MainActivity
4.) (wait 10 seconds)
5.) /dev/sh ($ should turn into #)
6.) echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
^do NOT screw that command up, copy/paste it or risk a brick
7.) exit
8.) exit
9.) adb reboot bootloader
10.) fastboot getvar cid
if it's 22222222, you are good. Proceed to htcdev to unlock, then you can s-off using facepalm.
Click to expand...
Click to collapse
I wish i can execute adb command
What seems to be an issue
i dont have any ROM installed now , and the only thing that i can use is fastboot command
I am familiar with adb , and plus i've created custom ROM before but not for HTC
trying to help a cousin but hell , JTAG here is unfamiliar with this model ( not available in Malaysia )
so i would think , this is a deadend but i never gave hope.
Will try to figure something and all help is much appreaciated.

Categories

Resources