Related
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.
WARNING: This procedure applies to View only
If you are S-OFF on honeycomb, do not under any circumstances run this procedure.
Don't bother asking for help if you try to do this on a virtual machine, you won't get any
run on a real machine.
If you updated using the Official OTA and want to downgrade to GB this is the procedure you want.
Perform a HTC unlock using the HTC unlock website
Download this recovery MD5: cb0683f249e6ad2d754949719104c1a8
Boot the view to fastboot mode
Flash recover
Code:
fastboot flash recovery cwm-4.0.1.4-express-HC.img
Reboot to recovery
Proceed with the downgradre procedure below.
Downgrade
First download the RUU for the view: (Download here) (Zip version for Linux/MacOS)
Download and extract misc_version from this file
From the screen on the view, select "Mounts and storage->Mount sdcard"
Run the following commands:
Code:
adb push misc_version /
adb shell chmod 777 /misc_version
adb shell /misc_version -s 1.22.651.1
You will see a message about backing up and patching partition 29
Reboot to fastboot:
Code:
adb reboot bootloader
[*]Relock the bootloader:
Code:
fastboot oem lock
Run the RUU
How to run RUU for Linux/MacOS:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.0531_NV_2.28_SPCS_release_198141_signed.zip
[color=blue][i]You will get error 90 after this first flash, so flash again[/i][/color]
fastboot flash zip RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.0531_NV_2.28_SPCS_release_198141_signed.zip
At this point you can perform a Revolutionary S-OFF and re-upgrade to Honeycomb with S-OFF if you so wish.
Reserved for me.
Also reserved for me
Globaltron
I think I will need your help regarding this now... I'm stuck at the situation where I will have to go back to the stock GB as somehow my copy of HC is bad and a restore/recovery is impossible (somehow a mismatched MD5), now I'm stuck the recovery as I am not sure if the GB would work on a HC HBoot.
What exact hboot do you have?
Procedure added.
globatron said:
At this point you can perform a Revolutionary S-OFF and re-upgrade to Honeycomb with S-OFF if you so wish.
Click to expand...
Click to collapse
On your "[View]S-OFF Honeycomb, Custom recovery, root" topic, you wrote:
globatron said:
Do not perform this procedure if you are HTC unlocked, it will not work
Click to expand...
Click to collapse
So how would I upgrade to S-OFF Honeycomb, if one of the steps for HC->GB downgrade is to use the HTC unlock? Or is step 5 ("Relock the bootloader") undoing the HTC unlock?
Step 5 covers that.
globatron said:
Download this recovery download MD5: cb0683f249e6ad2d754949719104c1a8
[*]Boot the view to fastboot mode
[*]Flash recover
Code:
fastboot flash recovery cwm-4.0.1.4-express-HC.img
Click to expand...
Click to collapse
There is no "cwm-4.0.1.4-express-HC.img" in the compressed archive linked >.>.
ok, give me a sec...
EDIT: Fixed
Nice Job sir, Thanks for the development and share
Just a suggestion to Globatron:
When/if you build RUU for the downgrade, maybe it will be possible to check first whether the device is s-off in HC and if so, refuse to run.
Trying to save some support time.
Upon running the RUU, I get:
"ERROR [140]: BOOTLOADER VERSION ERROR - The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
What I did:
HTC Unlock (bootloader says ""UNLOCKED", and "S-ON")
Get into FASTBOOT, then:
Code:
C:\Android>fastboot flash recovery cwm-4.0.1.4-express-HC.img
sending 'recovery' (4712 KB)... OKAY [ 0.624s]
writing 'recovery'... OKAY [ 0.703s]
finished. total time: 1.328s
Then reboot bootloader, enter recovery (blue "REVOLUTIONARY" cwm), then:
Code:
C:\Android>adb push misc_version /
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
3581 KB/s (454748 bytes in 0.124s)
C:\Android>adb shell chmod 777 /data/local/tmp/misc_version
chmod: /data/local/tmp/misc_version: No such file or directory
C:\Android>adb /misc_version -s 1.22.651.1
Android Debug Bridge version 1.0.26
<bunch of how-to use ADB messages>
I think the problem is right there; what am I doing wrong?
Nothing it's my error, I mis-edited an update.
ok, updated now, also note the addition of step 3 ( you can run that at any point before the last command in step 4 )
globatron said:
Nothing it's my error, I mis-edited and update.
Click to expand...
Click to collapse
Code:
adb /misc_version -s 1.22.651.1
Running that just gives a massive "how to", such as (excerpt):
Code:
C:\Android>adb /misc_version -s 1.22.651.1
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with the given serial number. Overrides ANDROID_SERIAL
And nothing about backing up / patching partition 29 >.>.
adb shell chmod 777 /data/local/tmp/misc_version
Question, after i run this command, I get No such file or directory.
Did i do something wrong?
Edit Sorry I see someone else already posted that
yea fixed...it's very late here so a few mistakes crept in. It should be all good now. I've gone back over it line by line this time.
Maine_Coon said:
Just a suggestion to Globatron:
When/if you build RUU for the downgrade, maybe it will be possible to check first whether the device is s-off in HC and if so, refuse to run.
Trying to save some support time.
Click to expand...
Click to collapse
Not possible to do it in that way, but yeah.
Thank you! It worked, and I am now back to Gingerbread =D.
OUTSTANDING!! Worked for me as well Thanks!!
I'm trying to flash something a update.zip package that contains su and busybox programs, and I know what you think, I'm rooting a device.
I've googled and there's the adb shell and fastboot programs that can help me but, how can flash it by commands?
Copy pasting the updater-script commands and the busybox installer too?
Please help me out! D:
Install su by using "fastboot flash update.zip" without recovery ROM (CWM or TWRP)?
Similar for me.
I'd like to install su and busybox as well on my Lenovo A8 (A5500-F, A8-50) tablet with Android KitKat (4.4.2).
However there's no CWM or TWRP for my device and I read other tools do not work.
But can I install a file called "update.zip", containing su, superuser and busybox (and installation script) using fastboot?
Like: "fastboot flash update.zip" ?
Using a file like this one:
http://forum.xda-developers.com/xperia-u/general/cwm-universal-busybox-su-flashable-zip-t1903752
Any ideas if this should work?
Rogier
No, that definitely wouldn't work. You have to have the bootloader unlocked and most likely if that was possible then there would already be a custom recovery for it...
Hi guys, my phone is Infocus M2 3G and I have rooted it earlier. Now I accidentally removed some services and now getting errors. I want to flash stock rom so it can be like previous one.
I installed ADB and fastboot in my system.
When I tried the command
Code:
fastboot flash recovery recovery.img
the following error came:
Code:
sending 'recovery' (10240 KB)...
OKAY [ 0.417s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017
)
finished. total time: 0.430s
I searched and I got to know that this may be because of bootloader lock.
So I tried the command
Code:
fastboot oem unlock
and
Code:
fastboot flashing unlock
For oem unlock it showed unknown command and for flashing unlock it showed all options of fastboot.
I installed Rom Manager and select boot into recovery option, it took me to Android Recovery System 3e.
I have stock rom files downloaded and just want to put stock rom in my phone. Any Ideas that can help?
sumit77seo said:
Hi guys, my phone is Infocus M2 3G and I have rooted it earlier. Now I accidentally removed some services and now getting errors. I want to flash stock rom so it can be like previous one.
I installed ADB and fastboot in my system.
When I tried the command
the following error came:
I searched and I got to know that this may be because of bootloader lock.
So I tried the command and
For oem unlock it showed unknown command and for flashing unlock it showed all options of fastboot.
I installed Rom Manager and select boot into recovery option, it took me to Android Recovery System 3e.
I have stock rom files downloaded and just want to put stock rom in my phone. Any Ideas that can help?
Click to expand...
Click to collapse
You can try putting the stock ROM zip file on the root of your sdcard (As in not located in any sub folders) and renaming the ROM file to update.zip then use the stock recovery to flash the ROM. Let me know if you still have questions!
Hi there everyone, i want to know, how can i take a backup of stock rom of my device.
Do i need to root my device before taking a backup? If not then is there any other way to take backup of Stock Rom (i.e boot.img etc) with the help of PC (here Ubuntu Linux in my case) via using ADB, Fastboot and not using custom recoveries like TWRP, Orange Fox, SHRP.
Also do i have to root my device before installing any custom recovery in it?
I am very sorry for any inconveniences, as i am a newbie please accept my apologies.
as already mentioned in other thread one can't do anything on locked bootloader, therefore backup is impossible
https://forum.xda-developers.com/t/a-question-from-a-newbie.4407343
akram0010 said:
Hi there everyone, i want to know, how can i take a backup of stock rom of my device.
Do i need to root my device before taking a backup? If not then is there any other way to take backup of Stock Rom (i.e boot.img etc) with the help of PC (here Ubuntu Linux in my case) via using ADB, Fastboot and not using custom recoveries like TWRP, Orange Fox, SHRP.
Also do i have to root my device before installing any custom recovery in it?
I am very sorry for any inconveniences, as i am a newbie please accept my apologies.
Click to expand...
Click to collapse
Assuming that the bootloader is unlocked.
aIecxs said:
as already mentioned in other thread one can't do anything on locked bootloader, therefore backup is impossible
https://forum.xda-developers.com/t/a-question-from-a-newbie.4407343
Click to expand...
Click to collapse
Sorry i forgot to mention, but still unlocking bootloader doesn't root device.
I think the question is still valid
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
aIecxs said:
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
Click to expand...
Click to collapse
Is root needed
aIecxs said:
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
Click to expand...
Click to collapse
Can you please tell me what is this recovery.img, and where would i get it (in Fastboot rom or recovery rom).
As i said earlier i am a newbie in this field and very much confused with these terms.
no root required click on the first link above and download TWRP for your device (TWRP-3.4.2.b_lancelot.zip)
I assume you are running windows?
extract zip file and place recovery.img on your PC in platform-tools directory. connect phone in fastboot mode, install android_winusb.inf "Android Bootloader Interface" drivers and from cmd.exe check fastboot devices
if you can see device serialno you are ready to boot TWRP from fastboot with above first command.
for linux just install android-tools-fastboot
As i am using Ubuntu i installed ADB, FASTBOOT using the APT :
Code:
sudo apt install android-tools-adb android-tools-fastboot
.
Therefore i don't have the platform-tools directory.
Also I am unable to quote reply, its showing error (Oops, we broke the Matrix, someone call Neo)
yes that's right. it doesn't matter which directory files are placed. that way you installed fastboot binary is already in PATH. linux is far more easier and doesn't require additional drivers. it might require additional udev rules to make fastboot work, but you can simply by-pass with sudo fastboot for now...