Hi, I S-OFF my phone by alpharevx and used 4ext touch recorvery. Today I try flash RUU.
1) From goo-inside.me/stock/vivo/ruu I downloaded PG32IMG_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.zip,
2) renamed to PG32IMG.zip
3) copied to sdcard
4) restart phone
5) I confirm update.
And now echo this:
img: ales.nejdr.cz/incs.jpg
I try unlock bootloader from htcdev, but
Code:
[skeeve:~]$ fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
Revolutionary doens't work, because adb doesn't work (only fastboot).
I try make golden card from this tutorial: mikesouthby.co.uk/2010/08/htc-desire-creating-goldcard-using-mac-or-linux/ , but with this I still can't flash RUU.
Now phone is brick. What can I do to turn the phone work?
I know, my english is ugly, sorry.
ales.n said:
Hi, I S-OFF my phone by alpharevx and used 4ext touch recorvery. Today I try flash RUU.
1) From goo-inside.me/stock/vivo/ruu I downloaded PG32IMG_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.zip,
2) renamed to PG32IMG.zip
3) copied to sdcard
4) restart phone
5) I confirm update.
And now echo this:
img: ales.nejdr.cz/incs.jpg
I try unlock bootloader from htcdev, but
Code:
[skeeve:~]$ fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
Revolutionary doens't work, because adb doesn't work (only fastboot).
I try make golden card from this tutorial: mikesouthby.co.uk/2010/08/htc-desire-creating-goldcard-using-mac-or-linux/ , but with this I still can't flash RUU.
Now phone is brick. What can I do to turn the phone work?
I know, my english is ugly, sorry.
Click to expand...
Click to collapse
Can you access Fastboot/Recovery?
Sent from my HTC Incredible S using xda premium
When I turn on the phone booted straight to recorvery, but nothing much to do here. When connected the phone to my computer than fastboot command works, but adb don't.
Code:
[skeeve:~]$ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Now I tried another way, but without success.
Code:
[skeeve:~]$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.171s]
finished. total time: 0.171s
[skeeve:~]$ fastboot oem rebootRUU
...
OKAY [ 0.168s]
finished. total time: 0.168s
[skeeve:~]$ fastboot flash zip Stazene/PG32IMG_Vivo_Gingerbread_S_HTC_WWE_2.12.405.7_Radio_20.2804.30.085AU_3805.04.03.22_M_release_187295_signed.zip
sending 'zip' (254241 KB)...
OKAY [ 42.201s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 84.778s
ales.n said:
Now I tried another way, but without success.
Code:
[skeeve:~]$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.171s]
finished. total time: 0.171s
[skeeve:~]$ fastboot oem rebootRUU
...
OKAY [ 0.168s]
finished. total time: 0.168s
[skeeve:~]$ fastboot flash zip Stazene/PG32IMG_Vivo_Gingerbread_S_HTC_WWE_2.12.405.7_Radio_20.2804.30.085AU_3805.04.03.22_M_release_187295_signed.zip
sending 'zip' (254241 KB)...
OKAY [ 42.201s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 84.778s
Click to expand...
Click to collapse
You are trying to flash a RUU that is older than the last one you flashed. Please reboot into Fastboot USB mode and enter
Fastboot getvar all
And post the results here so we can help you determine which RUU you need to flash.
Solved
Solved!
Code:
[skeeve:~]$ fastboot getvar all
...
(bootloader) version-main: 2.32.1010.1
...
Then I flashed
Code:
PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip
Although 2.32.1010.1 is probably a Korean version of the rom, but I tried it and the second attempt is OK.
All works fine! Thanks
I have a soft-bricked Raider that I dont know the history of and looks like it was updated to a ICS ROM with out updating the hboot, it has hboot 1.83.0014 and unlocked, a getver all shows the version-main to be 1.65.666.3 so I google that up and found this ICS image...
OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip
http://forum.xda-developers.com/showthread.php?t=1498003
So it appear I need to lock my bootloader and update the hboot.
When I run oem lock this is what I get.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Unknown error))
finished. total time: 0.022s
I let it sit for 15 minutes but no change.
what do I need to do to get my bootloader relocked?
That's relocked. Reboot into hboot.
Sent from an HTC Vivid via XDA Premium
I have do.e fastboot OEM lock 5 or more times on this phone and it says *** locked *** when I reboot into hboot
http://forum.xda-developers.com/showthread.php?t=1421760
Maybe you can try this tool to wipe your device. I have no idea if it will work. It's worth reading up on though.
Tx I will check that when I get home
MORE BAD NEWS
I yanked zom.zip out of the RUU for my Raider.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.197s]
finished. total time: 0.199s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) [SD/EMMC]Error status=0x400008
(bootloader) DATA_TIMEOUT
(bootloader) SD: write failed in CMD25.
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 1.184s]
finished. total time: 1.186s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip c:\
junk\zom.zip
sending 'zip' (420878 KB)...
OKAY [ 39.172s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 40.786s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
so ends up the EMMC chip has bad sectors and this is a problem with this phone. I ended up on freenode at #htc-holiday and had a good chat with IOMonster, so I will try to return the phone to HTC 866.449.8358 and if not I will do the following.
by the way fastboot boot recovery-beta2.img did get me into recovery -- strange no one pointed that out to me...
The above error is how I found out the EMMC chip has write errors.
I will try to remember to come back and post what happens when I call HTC tomorrow.
bobmutch2 said:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) [SD/EMMC]Error status=0x400008
(bootloader) DATA_TIMEOUT
(bootloader) SD: write failed in CMD25.
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 1.184s]
finished. total time: 1.186s
Click to expand...
Click to collapse
Did you solved it? I have a same problem [SD/EMMC]Error status=0x400008.
Hi Guys, i my Google nexus one stuck on boot screen.i had read lots of post on XDA to solve this problem but not able to solve.
My Nexus one has unlocked bootloader.
I flash recovery from fastboot and it successfully flashed.
but when i try to boot into recovery mode, device stuck on boot screen with lock symbol below, which denots unlock bootloader.
Please can any buddy tell what the problem or how can it flash custome rom into it .
Thanks .
try wipe all partition again
Code:
fastboot -w
fastboot erase recovery
fastboot reboot-bootloader
and reflash recovery
must use 4ext recovery
Edited: fixed
Replace hboot with fastboot in the above commands
Sent from my Nexus 4 using xda premium
HTC Nexus One Problems- All Self-inflicted
demkantor said:
Replace hboot with fastboot in the above commands
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Hi, First off, I'm so damn new I don't even qualify yet to be called "Noob". I bought an HTC Nexus One on eBay and it was loaded with 2.3.4. But I could not get it to update. I then took a look at the build # "3.11.405.2CL81940" with "release keys" added in a line below. Google came up with two or three hits, all starting with "Weird Build....", so I decided to get rid of it by rooting the phone. Over three days of fooling around with it and I am asking for help: after doing ALL KINDS OF THINGS (can't even remember the sequence), I'm stuck with a phone which when powered on no longer goes to the "X" splash screen but to "htc" with small yield signs with exclamation points in the four corners of the screen. The only way to power it down is to remove the battery. If I connect it to my Windows PC, it is recognized (I've downloaded the drivers, SDK Manager and AVD Manager) and I can perform certain functions using the command line within the SDK. But I can't format and start all over with a "stock" release let alone Jelly Bean which was my goal when starting all this. Additional information I can provide: when I remove the phone from the USB, the Black "htc" screen disappears and a white screen replaces it with the following: Line 1) BlackRose-Made by LeCache dl95244; line 2) STOCK 145/95/196; line 3) NEXUS ONE PV(or U)T S-off; line 4) HBOOT 7.3.5.5017 (PB9910000); line 4) TOUCHPANEL SYNT0103; line 5) RADIO-5.12.00.00; line 6) Apr 21 2012, 04:53:16; line 7) RUU. Line one, "BlackRose...", is black with white characters. Lines 2-6 are green characters on a white background (resembling the old boot screen) and finally, line 7, the "RUU" characters are white in an orange background, as though it's highlighted, asking for something. As said above, no buttons work (Track ball, Vol up/Vol down), and this is where the battery has to be pulled to power it down. Can anyone help?? I'll do my best to reply with any specifics that I DO remember, but I've done so many, many things in the past three days I've lost track. Thanks.
When you plus your phone into PC does it make a noise as if the phone is recognized? When you first get to the screen with the black rose text does some words flash then disappear?
And really no buttons work at all?
Sent from my Nexus 4 using xda premium
In response to your question:
demkantor said:
When you plus your phone into PC does it make a noise as if the phone is recognized? When you first get to the screen with the black rose text does some words flash then disappear?
And really no buttons work at all?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Let me describe it from the start. After insuring the device is fully charged I power it off the only way I can, pulling the battery, waiting 5 seconds, then reassembling the battery and back.
I get out the USB cord and insert it into the Windows PC. Then, (either powered on BEFORE insertion of the Micro USB or AFTER), when the device is powered on it goes to a new splash screen with "htc" in white on a gray/black background with caution signs at each corner of the screen. The device will stay that way for hours, plugged into a PC or powered on without tethering. THE ONLY WAY to access the white screen (which resembles the old boot screen without skateboards) is to unplug the device from the USB/PC WHILE POWERED ON.
When you do this, you have the "BlackRose" in white on a black line, then the rest as described, with "RUU" in orange.
There is one additional detail I do remember doing: I downloaded and installed "HTC One (M7//T-Mobile/AT&T/Sprint) AIO Kit by Hasoon2000v2.1 and Flashed CWM (GSM Only) Recovery. That was the last time the screen was at all responsive: lot's of lines rolling upward and then the words, I think, "Update failed".
Hasoon2000, I believe, is a member of this Forum and lives in Orland Park, IL, a suburb frustratingly close to me, in Chicago!!
---------- Post added at 07:02 AM ---------- Previous post was at 06:55 AM ----------
demkantor said:
When you plus your phone into PC does it make a noise as if the phone is recognized? When you first get to the screen with the black rose text does some words flash then disappear?
And really no buttons work at all?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Short answer, yes: Device Manager recognizes it and I hear a "cer-chunk" when its plugged in.
now you can enter bootloader or not?
bootloader
hxq88 said:
now you can enter bootloader or not?
Click to expand...
Click to collapse
Yes. I can access bootloader. Just finished the following:
fastboot device HT0ALP801351
---------- Post added at 09:29 AM ---------- Previous post was at 09:09 AM ----------
rickz41 said:
Yes. I can access bootloader. Just finished the following:
fastboot devices HT0ALP801351
Click to expand...
Click to collapse
OKAY [ 4.628s]
formatting 'userdata' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 2.230s]
formatting 'cache' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.019s]
finished. total time: 6.903s
C:\android-sdk\platform-tools>fastboot erase r
erasing 'recovery'...
OKAY [ 0.097s]
finished. total time: 0.099s
C:\android-sdk\platform-tools>
its ok . did you run commands in post #2?
let try full wipe all and try it from beginning 1 more time. or use PASSIMG method to fast restore stock rom.
edit: ok full wiped, now reflash recovery ( try 4ext or TWRP, sorry i dont know link, you can find in search forum )
Post 2
rickz41 said:
Yes. I can access bootloader. Just finished the following:
fastboot device HT0ALP801351
---------- Post added at 09:29 AM ---------- Previous post was at 09:09 AM ----------
OKAY [ 4.628s]
formatting 'userdata' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 2.230s]
formatting 'cache' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.019s]
finished. total time: 6.903s
C:\android-sdk\platform-tools>fastboot erase r
erasing 'recovery'...
OKAY [ 0.097s]
finished. total time: 0.099s
C:\android-sdk\platform-tools>
Click to expand...
Click to collapse
Was following your guide in post 2, yes. It accepted the first two commands but the third, "fastboot reboot bootloader" caused the terminal window to only scroll my options. I don't know what you call that but I think it means it did not work.
rickz41 said:
Was following your guide in post 2, yes. It accepted the first two commands but the third, "fastboot reboot bootloader" caused the terminal window to only scroll my options. I don't know what you call that but I think it means it did not work.
Click to expand...
Click to collapse
wrong command: it must be fastboot reboot-bootloader
command
hxq88 said:
wrong command: it must be fastboot reboot-bootloader
Click to expand...
Click to collapse
Success!!
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.028s]
finished. total time: 0.029s
C:\android-sdk\platform-tools>
(Phone powered off- heard PC disconnect then reconnect, now screen is still same: whit "htc", black background with caution marks, all four corners....
enter bootloader again and reflash recovery cuz all was wiped. but after wipe phone will auto-enter bootloader, i never see htc caution before.
let try reflash recovery ( 4ext or TWRP ) hope it will work.( with my phone, it somtimes stuck if i enter recovery after flash, just turn off the phone, wait 5-10 mins, idont know why )
edit: its the name of recovery, i miss some letter cuz fast type
additional info
hxq88 said:
enter bootloader again and reflash recovery cuz all was wiped. but after wipe phone will auto-enter bootloader, i never see htc caution before.
let try reflash recovery ( 4ext or TWRP ) hope it will work.( with my phone, it somtimes stuck if i enter recovery after flash, just turn off the phone, wait 5-10 mins, idont know why )
Click to expand...
Click to collapse
Here I must repeat, I am not even Newbie or Noob- I am less than Noob!! What is 4ext, TWRP?? I will download them and do as you say but give detailed instructions for I am only an infant!! (when it comes to this, at least!)
---------- Post added at 10:55 AM ---------- Previous post was at 10:09 AM ----------
THANK YOU SO VERY MUCH FOR GETTING ME THIS FAR!!
It is greatly appreciated.
I will leave for awhile now, but thank you again.
Those are recoveries, personally 4ext tends to be the best for all phones I've used it in but for some reason I have had issues with this on my n1, the only recovery that has never given me an issue on the n1 is amonra so that's what I use, feel free to use what you like.
That screen you were stuck in earlier is RUU mode which is meant to be used flashing official HTC RUUs, I don't think you will have an serious issues, just follow directions posted earlier
fastboot erase system -w
fastboot erase boot
fastboot flash recovery recovery.img
Then scroll to recovery option in bootloader to go into whatever recovery you chose and the flash a compatible ROM at this point
If you want to learn more about fastboot see here
http://forum.xda-developers.com/showthread.php?p=41374534
Sent from my Nexus 4 using xda premium
Progress thus far:
demkantor said:
Those are recoveries, personally 4ext tends to be the best for all phones I've used it in but for some reason I have had issues with this on my n1, the only recovery that has never given me an issue on the n1 is amonra so that's what I use, feel free to use what you like.
That screen you were stuck in earlier is RUU mode which is meant to be used flashing official HTC RUUs, I don't think you will have an serious issues, just follow directions posted earlier
fastboot erase system -w
fastboot erase boot
fastboot flash recovery recovery.img
Then scroll to recovery option in bootloader to go into whatever recovery you chose and the flash a compatible ROM at this point
If you want to learn more about fastboot see here
http://forum.xda-developers.com/showthread.php?p=41374534
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you for joining in and I must say at that I am in complete agreement with your feelings re: apple/MAC/iOS, etc.: they can go to Hell.
Let me post the results after following your instructions above:
C:\android-sdk\platform-tools>fastboot erase system -w
erasing 'system'...
OKAY [ 3.406s]
erasing 'userdata'...
OKAY [ 4.608s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.023s]
erasing 'cache'...
OKAY [ 2.223s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.022s]
finished. total time: 10.293s
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.054s]
finished. total time: 0.057s
C:\android-sdk\platform-tools>fastboot flash recovery recovery-RA-passion-v2.2.1
.img
sending 'recovery' (3366 KB)...
OKAY [ 0.483s]
writing 'recovery'...
OKAY [ 1.082s]
finished. total time: 1.570s
But the n1 is still showing the gray/black splash with htc and the caution/yield signs at the corner. The line: "Erase successful, but not automatically formatting. Can't determine partition type." when erasing user data and formatting cache, is this something to be looked into?
I've flashed, I believe, successfully, AmonRa before but when I try to flash a 'Stock' passion image, it fails.
I'll continue reading your most helpful guides and hope for a step-by-step reply- I feel as though I am very close to solving this!
Again, many thanks!
Update
Sorry to report I've not made any progress since my last post despite the Guides provided.
A couple important points:
a) I cannot enter to cmd prompt level, fir whatever reason
b) This leave me with Fastboot and when the device is again wiped and prepared, Fastboot is entered, and I type Fastboot update update.zip with the following results attempting different "Stock Passion Images":
C:\android-sdk\platform-tools>
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 7.35.5017
Baseband Version.....: 5.12.00.08
Serial Number........: HT0ALP801351
--------------------------------------------
checking mid...
OKAY [ 0.003s]
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is '7.35.5017'.
Update requires '0.35.2017' or '0.35.0017'.
finished. total time: 0.047s
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\android-sdk\platform-tools>
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 7.35.5017
Baseband Version.....: 5.12.00.08
Serial Number........: HT0ALP801351
--------------------------------------------
checking mid...
OKAY [ 0.003s]
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is '7.35.5017'.
Update requires '0.35.2017' or '0.35.0017'.
finished. total time: 0.047s
Any further thoughts??
Also, USB debugging is OFF complicating thins a lot, preventing me from getting a token from HTC's site!!
Bootloader should be unlocked being you have black rose, try different RUUs
http://forum.xda-developers.com/showthread.php?p=7495397
You may also try to change your cid to 11111111 this will allow you to flash any version
Sent from my Nexus 4 using xda premium
Questions:
How would I change cid ?
I've been searching the universe for RUU's and came up with one:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe . That's it. in your link I see a number of Factory Images. Which would you suggest?
---------- Post added at 03:03 PM ---------- Previous post was at 02:48 PM ----------
rickz41 said:
How would I change cid ?
I've been searching the universe for RUU's and came up with one:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe . That's it. in your link I see a number of Factory Images. Which would you suggest?
Click to expand...
Click to collapse
Took the advice here:
http://forum.xda-developers.com/showthread.php?t=2264322
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem readcid
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files\Android\android-sdk\platform-tools>fastboot devices
HT0ALP801351 fastboot
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem readcid
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.007s
C:\Program Files\Android\android-sdk\platform-tools>
---------- Post added at 03:20 PM ---------- Previous post was at 03:03 PM ----------
C:\Program Files\Android\android-sdk\platform-tools>cd c:\mini-adb
The system cannot find the path specified.
C:\Program Files\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Program Files\Android\android-sdk\platform-tools>adb reboot bootloader
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>fastboot devices
HT0ALP801351 fastboot
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvarcid
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
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
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 7.35.5017
(bootloader) version-baseband: 5.12.00.08
(bootloader) version-cpld: None
(bootloader) version-microp: 0c15
(bootloader) version-main: 2.16.405.1
(bootloader) serialno: HT0ALP801351
(bootloader) product: nexusone
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9910000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4162mV
(bootloader) partition-layout: STOCK-145/95/196
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 0c3a097c
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.024s
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem writecid 111111
11
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem writecid 111111
11
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 7.35.5017
(bootloader) version-baseband: 5.12.00.08
(bootloader) version-cpld: None
(bootloader) version-microp: 0c15
(bootloader) version-main: 2.16.405.1
(bootloader) serialno: HT0ALP801351
(bootloader) product: nexusone
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9910000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4162mV
(bootloader) partition-layout: STOCK-145/95/196
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 0c3a097c
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.019s
C:\Program Files\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.026s
C:\Program Files\Android\android-sdk\platform-tools>
It rebooted back to the same ole' 'htc' screen!
Try
fastboot oem getvar cid
To read it and
fastboot oem write cid 11111111
To write
As for which ruu to pick I'm not sure, never ran one on my n1, I did see a thread not to long ago where someone was trying to grab every official update from HTC, you can also try HTC directly and try to find the latest one
Sent from my Nexus 4 using xda premium
There HTC 626G, revision 1.79.401.100. During the study, on new devices starting with the revision (build) 1.72.401.101, with modified firmware recovery phone goes bootloop. Initially it was assumed that the problem was incompatible version recovery (old and new versions). new recovery was made under my revision, and after flashing turned bootloop.
When loading stock version:
fastboot flash recovery recovery_stock.img responses with:
sending 'recovery' (10240 KB)...
OKAY [ 0.417s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017
)
finished. total time: 0.430s
Since version error recovery not confirmed, it remains an unlocked bootloader.
When you enter the command:
C:\Users\bugae\Desktop\android>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.007s
C:\Users\bugae\Desktop\android>fastboot oem identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.006s
C:\Users\bugae\Desktop\android>fastboot oem token
...
FAILED (remote: unknown command)
finished. total time: 0.020s
fastboot oem unlock (the tablet responses with a question screen where I can select "yes, unlock bootloader" and "no, don't unlock bootloader", but when I select yes it responses with an error "Unlock failed - Err:0x7000")
Standard methods do not work!(
How to be? What to do?
Backup 4pda.ru/forum/index.php?s=&showtopic=756527&view=findpost&p=53005677
Try using win droid toolkit, I had the same issue with my 626 and I fixed mine here's a link
http://forum.xda-developers.com/devdb/project/?id=1314#downloads
https://forum.xda-developers.com/showpost.php?p=77300835&postcount=2