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.
Related
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
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
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
I'm pondering options with the vzw z2 tablet (sgp561) and before I start playing with this fire, I am curious what it would take to hard brick this so I know what NOT to try.
Any thoughts?
In theory as long as fastboot works it should be pretty tough to brick. I don't really know how fastboot works on Sony devices I have mostly Samsung devices but I assume download mode work largely the same as fastboot. I have brought back Samsung devices from being very near full hard brick. That said they were old and had unlocked bootloaders. I am not sure how relevant my two cents is but that is what I have. On another note I also have the 561 and am more than happy to help in any way I can. I really want some CM12 on this thing since VZW probably won't give it to us until everyone else has had it for 6 months.
Maxim512 said:
In theory as long as fastboot works it should be pretty tough to brick. I don't really know how fastboot works on Sony devices I have mostly Samsung devices but I assume download mode work largely the same as fastboot. I have brought back Samsung devices from being very near full hard brick. That said they were old and had unlocked bootloaders. I am not sure how relevant my two cents is but that is what I have. On another note I also have the 561 and am more than happy to help in any way I can. I really want some CM12 on this thing since VZW probably won't give it to us until everyone else has had it for 6 months.
Click to expand...
Click to collapse
Well, I can throw a couple of "kopeka's" (cents) in as well.
Fastboot is a life savior. Bar none. With it, you can wipe partitions and flash new partition images. Now this is taken that the fastboot capabilities in the given bootloader are "full" and not neutered in some way. Yes, it could possibly be so.
The only way I know, where you can perma-brick the device, is by flashing things on incorrect partition formats, or flashing a bootloader not meant for the device.
Incorrect custom recoveries are notorious for this, as they flash incorrect partition info. (been there, did that).
Also, nand memory can fail after some flashings. It happens. No rhyme or reason to it, it just does. Generally it gets corrupt to the point wipes and formats don't clean it.
Moscow Desire said:
Well, I can throw a couple of "kopeka's" (cents) in as well.
Fastboot is a life savior. Bar none. With it, you can wipe partitions and flash new partition images. Now this is taken that the fastboot capabilities in the given bootloader are "full" and not neutered in some way. Yes, it could possibly be so.
The only way I know, where you can perma-brick the device, is by flashing things on incorrect partition formats, or flashing a bootloader not meant for the device.
Incorrect custom recoveries are notorious for this, as they flash incorrect partition info. (been there, did that).
Also, nand memory can fail after some flashings. It happens. No rhyme or reason to it, it just does. Generally it gets corrupt to the point wipes and formats don't clean it.
Click to expand...
Click to collapse
In random readings, I've seen that "Unlock bootloader allowed=no" on some devices blocks fastboot. I can boot into fastboot mode, but I haven't tried flashing anything since I am not experienced in fastboot flashing. I think the easy test would be to read a partition in fastboot, then write it back. Do you know the commands to do so?
da_reeseboy said:
In random readings, I've seen that "Unlock bootloader allowed=no" on some devices blocks fastboot. I can boot into fastboot mode, but I haven't tried flashing anything since I am not experienced in fastboot flashing. I think the easy test would be to read a partition in fastboot, then write it back. Do you know the commands to do so?
Click to expand...
Click to collapse
You are correct. Some variants (Verizon for example), you can't unlock the bootloader. No unlock, no "full" fastboot or fastboot at all.
Although my original bootlocker was "unlockable" due to it turning out to be a "Demo" unit, I managed to flash an RU ftf, and got the unlocked bootloader. But it seems "some" carrier models don't allow for this. (as a sidenote, I've just reflashed my DRM keys back today, and now on a stock locked .167 build again. Just wanted to try it and see if it worked.)
Here's a list of useful commands (thanks to AndroidForums), but you can certainly find a ton by Google-it.
Code:
fastboot
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
A very useful thing to use, is for example;
fastboot boot boot.img
or
fastboot boot recovery.img
This is useful as it doesn't actually "write" the image to the device, but rather boots it in memory.
Usually how we test things such as new custom recoveries, boot.images and such.
Moscow Desire said:
You are correct. Some variants (Verizon for example), you can't unlock the bootloader. No unlock, no "full" fastboot or fastboot at all.
Although my original bootlocker was "unlockable" due to it turning out to be a "Demo" unit, I managed to flash an RU ftf, and got the unlocked bootloader. But it seems "some" carrier models don't allow for this. (as a sidenote, I've just reflashed my DRM keys back today, and now on a stock locked .167 build again. Just wanted to try it and see if it worked.)
Here's a list of useful commands (thanks to AndroidForums), but you can certainly find a ton by Google-it.
Code:
fastboot
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
A very useful thing to use, is for example;
fastboot boot boot.img
or
fastboot boot recovery.img
This is useful as it doesn't actually "write" the image to the device, but rather boots it in memory.
Usually how we test things such as new custom recoveries, boot.images and such.
Click to expand...
Click to collapse
Well I was going to give it a shot but I turned my tablet off to reboot without making any changes to it and now it won't turn back on. I haven't had time to RMA it yet. It did this before but it just started working again for no reason. It is probably a good thing since it sounds like I probably would have bricked it trying anyway.
Maxim512 said:
Well I was going to give it a shot but I turned my tablet off to reboot without making any changes to it and now it won't turn back on. I haven't had time to RMA it yet. It did this before but it just started working again for no reason. It is probably a good thing since it sounds like I probably would have bricked it trying anyway.
Click to expand...
Click to collapse
Wow, talk about "timing". Luckily you didn't make any changes. Had a similar issue with mine last night (coming out of fastboot coincidently).
Did a fastboot boot to TWRP, and when it went to reboot, I had to mess with the Vol + and - nd PWR combinations a few times before it would boot.
Do not play with verizon z2
I work with custom roms and such... I also have a Sony Z2 late tab... I built a rom for this device.... Never got to test it. Got two on it with no issues. And this is a pain as well due to anytime you use twrp you must reflash twrp or your in for a world of hurt. Well during my process twrp froze while wiping the system... I could get to fastboot but any command I tried to run It told me that it was locked and I couldn't use the command as I didn't have the rights. So long story short I wouldn't play with it till someone gets a unlock for it
Hello,
My A3 was unlocked with root, android 9 February security patch
Randomly Google play service stop working, after deleting cache it was fine.
Again randomly the prone start to act weird, restart it and then appear " Can't load android system. Your data may be corrupt."
The only options are try again and Factory data reset. ( like in the image https://i.redd.it/8nf9k5v33u1z.jpg )
Because i have important information i can't do factory reset so tried to flash stock fastboot rom with miflash.
Fastboot was accessible, BUT after trying to adb devices check it shows- List of devices attached* daemon not running. starting it now on port 5037 ** daemon started successfully * so it was not really able to connect. My Computer does not recognise it as Mi A3.
So after flashing fastboot Android One logo unlocked, appear several time, like blinking 4-5 times, and again jump in to fastboot mode.
First tried to flash V10.3.15.0.PFQEUXM, than V10.3.14.0.PFQEUXM. None of them did the work.
Attaching some logs.
By the way i use MiFlash20181115 it was the latest found
Thank you in advance , BE HAPPY and SAFE
Tried to add before fastboot %* reboot , fastboot $* set_active a , bur the result was the same
1. avoid downgrades, your data might get corrupted and you'll end up with factory reset anyway
2. per the logs it seems that everything flashes correctly, make sure that you have partition A as active (https://forum.xda-developers.com/showpost.php?p=81408355&postcount=2). Type both commands (one will fail) in cmd window with phone connected via fastboot.
_mysiak_ said:
1. avoid downgrades, your data might get corrupted and you'll end up with factory reset anyway
2. per the logs it seems that everything flashes correctly, make sure that you have partition A as active (https://forum.xda-developers.com/showpost.php?p=81408355&postcount=2). Type both commands (one will fail) in cmd window with phone connected via fastboot.
Click to expand...
Click to collapse
Phone is not recognised in cmd, only if use- Install from ADB option from recovery it show the device.
alexandarpb said:
Phone is not recognised in cmd, only if use- Install from ADB option from recovery it show the device.
Click to expand...
Click to collapse
You seem to confuse ADB and Fastboot. Connect mobile in FASTBOOT mode and type in those two commands. If there's an error, paste the output here.
_mysiak_ said:
You seem to confuse ADB and Fastboot. Connect mobile in FASTBOOT mode and type in those two commands. If there's an error, paste the output here.
Click to expand...
Click to collapse
PS C:\Users\Sashko\Desktop\platform-tools> fastboot set_active a
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
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 [bootloader] reboot device, optionally into bootloader
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.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\Users\Sashko\Desktop\platform-tools> fastboot --set-active=a
C:\adb\fastboot.exe: unknown option -- set-active=a
PS C:\Users\Sashko\Desktop\platform-tools>
alexandarpb said:
PS C:\Users\Sashko\Desktop\platform-tools> fastboot set_active a
usage: fastboot [ <option> ] <command>
...
PS C:\Users\Sashko\Desktop\platform-tools> fastboot --set-active=a
C:\adb\fastboot.exe: unknown option -- set-active=a
PS C:\Users\Sashko\Desktop\platform-tools>
Click to expand...
Click to collapse
Uninstall/remove existing fastboot.exe from all locations on your PC and use the latest version https://developer.android.com/studio/releases/platform-tools
_mysiak_ said:
Uninstall/remove existing fastboot.exe from all locations on your PC and use the latest version https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
From my previous PC i managed to get proper result
C:\Users\PC-1\Desktop\mi a3\platform-tools>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.002s]
Finished. Total time: 0.012s
C:\Users\PC-1\Desktop\mi a3\platform-tools>
Should i now use miflash again to flash the fastboot rom or?
Thank you so much for all your answers!!!
alexandarpb said:
From my previous PC i managed to get proper result
C:\Users\PC-1\Desktop\mi a3\platform-tools>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.002s]
Finished. Total time: 0.012s
C:\Users\PC-1\Desktop\mi a3\platform-tools>
Should i now use miflash again to flash the fastboot rom or?
Thank you so much for all your answers!!!
Click to expand...
Click to collapse
Just start the phone. Re-flash only if it won't boot.
_mysiak_ said:
Just start the phone. Re-flash only if it won't boot.
Click to expand...
Click to collapse
Thank you, you are my saviour, unfortunately my data is gone... but at least it work now.
Thank you for everything
alexandarpb said:
Thank you, you are my saviour, unfortunately my data is gone... but at least it work now.
Thank you for everything
Click to expand...
Click to collapse
I suppose that you already performed the factory reset, but for the future - you could try flashing TWRP first, backup/export data and perform factory reset only after that.
_mysiak_ said:
I suppose that you already performed the factory reset, but for the future - you could try flashing TWRP first, backup/export data and perform factory reset only after that.
Click to expand...
Click to collapse
Definitely, but i was thinking that if the phone is not recognised in adb command it would not be able to do anything with fastboot command. It is nonsense i know...
Thank again, by the way which recovery is better OrangeFox Recovery or TWRP ?
alexandarpb said:
Definitely, but i was thinking that if the phone is not recognised in adb command it would not be able to do anything with fastboot command. It is nonsense i know...
Thank again, by the way which recovery is better OrangeFox Recovery or TWRP ?
Click to expand...
Click to collapse
I haven't used custom recovery for A3 yet, but TWRP would be my first choice if a need occured.