Hey Folks!
After the dead of my desire (7 buzzes / vibrates -> indicates a broken soc/motherboard) and the new rising (got a motherboard of a desire with a broken screen) the old lady worked again!
I got the s/n and system from the one with the broken screen - this is normal because it's stored on the mainboard. It was a CM v7 as I remember.
Here as a list of things I did and where I stuck now:
flashed an up-to-date recovery TWRP -> worked
tried to install a new rom with a new hboot which -> didn't worked out
Since here I only can access the recovery
All attempts to flash something (via recovery or fastboot) -> doesn't work
also tried to use revolutionary (even it's already unlooked and s-off) -> but the app stucks
I could only flash the boot logo via fastboot the rest results in different errors like:
CID incorrect (pb99img.zip method)
Error (When trying to flash a .zip via recovery)
And an other Error i forgott (when flash via fastboot)
Also i can't get an information via fastboot (-getvar all). There is always a errormessage.
Here is my hboot-screen
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
I'm not sure if something went wrong while trying to put a new hboot (partition-layout).
I have no idea what to do. Read about the half of the internet....
Anyone any idea?
Here is an other error message i get when running this fastboot command
Code:
fastboot getvar all
getvar:all FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I'm realy appreciate any help!
BTW: I'm not a robot!
Des!re said:
CID incorrect (pb99img.zip method)
Error (When trying to flash a .zip via recovery)
And an other Error i forgott (when flash via fastboot)
Also i can't get an information via fastboot (-getvar all). There is always a errormessage.
Here is my hboot-screen
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
I'm not sure if something went wrong while trying to put a new hboot (partition-layout).
I have no idea what to do. Read about the half of the internet....
Anyone any idea?
Click to expand...
Click to collapse
So good news is that it's not bricked if you can reach bootloader and recovery screen. Sounds like a driver issue or bad download of ROM, or both.
A few things to note:
- You haven't changed hboot because it still says 'Alpharev' on top of the bootloader screen. It should say the name of the hboot e.g. Alpharev CM7R2 if successful.
- CID incorrect happens when you try to flash a different region RUU. You should have tried the 2.3.3 GB WWE RUU, many threads in Q&A cover this.
- You should always try 'fastboot devices' command before flashing anything via fastboot, this will tell you straight away if you have driver issues.
This info I must have learnt reading the other half of the internet ...
What I would do:
- Confirm that fastboot is working first, check your drivers. Did you flash the recovery using fastboot? Flashing an hboot is largely the same method.
- Verify that the md5sum of the ROM.zip is correct on PC before flashing. Test several ROMs to be sure.
- Verify that the ROM is also compatible with the hboot as well or it won't boot.
- Make sure you nandroid backup if you have anything to save, then full wipe (wipe data/factory reset) before flashing the ROM.
- Make sure your sd card is correctly partitioned if the ROM requires one., as some put parts of the ROM on the partition. You will need a partition to install more than a few apps anyway.
- Post / research the exact error message if it's still not working, and at least state which ROMs you've tried.
eddiehk6 said:
So good news is that it's not bricked if you can reach bootloader and recovery screen. Sounds like a driver issue or bad download of ROM, or both.
A few things to note:
- You haven't changed hboot because it still says 'Alpharev' on top of the bootloader screen. It should say the name of the hboot e.g. Alpharev CM7R2 if successful.
- CID incorrect happens when you try to flash a different region RUU. You should have tried the 2.3.3 GB WWE RUU, many threads in Q&A cover this.
- You should always try 'fastboot devices' command before flashing anything via fastboot, this will tell you straight away if you have driver issues.
This info I must have learnt reading the other half of the internet ...
Click to expand...
Click to collapse
Thanks for your reply. Some things I forgot to mention in the thread above.
I successfully rooted, s-off, and flashed a new hboot & rom to my old desire.... all before she died. I remembered I needed some tries for the hboot... but it worked out fine in the end.
I also need to say that I tried (with the new/repaired one) different clients (hardware and os, win & linux) and different cables. Just to be sure.
I also went sure that fastboot is working (fastboot devices) and there always was my serial -> so it's good for sure
I read something about that the Alpharev hboot (with the repaired phone there was also the bootsplash with 'alpha-rev s-off / why so serious?' before I flashed it away to the stock 'htc') is somehow write-protected itself which can cause issues???
I tried to flash the "Alpha Jelly (250/5/182) hboot" to be able to install CarbonRom 1.0 (4.4.4) by spezi77 (http://forum.xda-developers.com/showthread.php?t=2658853). But I didn't succeeded at all.
eddiehk6 said:
What I would do:
- Confirm that fastboot is working first, check your drivers. Did you flash the recovery using fastboot? Flashing an hboot is largely the same method.
Click to expand...
Click to collapse
I think I flashed the recovery via fastboot, it just worked once. When I tried to flash CWM it didn't worked anymore.
eddiehk6 said:
- Verify that the md5sum of the ROM.zip is correct on PC before flashing. Test several ROMs to be sure.
Click to expand...
Click to collapse
I did checked the md5sum's and I tested a couple of Roms (more than 3)
eddiehk6 said:
- Verify that the ROM is also compatible with the hboot as well or it won't boot.
Click to expand...
Click to collapse
My old devices was a PVT4 and the repaired one is a PVT1 - there should be no difference for the hboot i guess?
eddiehk6 said:
- Make sure you nandroid backup if you have anything to save, then full wipe (wipe data/factory reset) before flashing the ROM.
Click to expand...
Click to collapse
This I should have done straight after I repaired the hardware and I was able to boot in CM7.... To late for now but if I have a working state I definitely do this!! :good:
eddiehk6 said:
- Make sure your sd card is correctly partitioned if the ROM requires one., as some put parts of the ROM on the partition. You will need a partition to install more than a few apps anyway.
Click to expand...
Click to collapse
I don't have a booting system yet so I need to postpone this. To be able to do the pb99img.zip method i formatted the whole sd-card with one partition as fat32. But when I have (hopefully) soon a working system I need to partion it correctly - easy!
eddiehk6 said:
- Post / research the exact error message if it's still not working, and at least state which ROMs you've tried.
Click to expand...
Click to collapse
I'm the resarcher! I'm going down to reasearch - I will report!
Thanks for your help so far!
I'm the resarcher! I'm going down to reasearch - I will report!
Click to expand...
Click to collapse
I went down to research!
I tried to flash hboot 'Bravo Stock' by Alpharev.
Code:
fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)...
OKAY [ 0.104s]
writing 'hboot'...
OKAY [ 0.160s]
finished. total time: 0.264s
looks good for me!
the bootscreen changed from
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
to
Code:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
so first and third line changed!
And because it's so nice to flash hboot i also flashed AlphaRev Jelly successfully!!
I try flash a rom now :fingers-crossed:
After I successfully flashed my hboot (twice!)....
I'm not able to wipe or install stuff....
Team Win Recovery Project v2.7.1.0
WIPE -> Factory Reset (Wipe Data, Cache and Dalvik)
Code:
Factory Reset Complete
Failed
E:Find_File: Error opening '/sys/class/backlight'
E:Unable to recreate and-sec folder.
Updating partition details...
E:Unable to mount storage
E:Unable to mount /sdcard during GUI startup.
Full SELinux support is present.
E:Unabke to mount /sdcard/TWRP/.twrps when trying to read settings file.
MTD Formatting "cache"
Done.
MTD Formatting "userdata"
Done.
Updatting partition details...
E:Unable to mount storage.
### FAILED ###
Team Win Recovery Project v2.7.1.0
Install -> ZIP
Code:
Zip Install Complete
Failed
E:Find_File: Error opening '/sys/class/backlight'
Updating partition details...
Full SELinux support is present.
Installing '/sdcard/roms/CARBON-KK-UNOFFICIAL-20140914-1119-bravo.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Could not create file for updater extract in '/tmp/updater'
Error flashing zip '/sdcard/roms/CARBON-KK-UNOFFICIAL-20140914-1119-bravo.zip'
Updatting partition details...
### FAILED ###
Maybe there is something "broken" with the filesystem?
As always I appreciate any help
Did a 'clear userdata' in the boot menu and then a wipe via TWRP.
Now it was successful but with this errors in the console:
Code:
Factory Reset Complete
Successful
E:Find_File: Error opening '/sys/class/backlight'
Updating partition details...
Full SELinux support is present.
MTD Formatting "cache"
Done.
MTD Formatting "userdata"
Done.
Wiping Android Secure
Formatting SD-Ext using make_ext4fs function.
Updating partition details...
But I wonder where are these errors from
Installing a rom still doesn't work. I think the problem is this line:
Code:
E:Could not create file for updater extract in '/tmp/updater'
There is BIG FAT BUG in the newest TWRP (v2.7.1.0)
You can't install anything before manually create the tmp directory
You have to do the following steps to flash any files :
- boot into recovery mode
- choose 'Advanced'
- choose 'Terminal Command'
- You're now on the '/' (root of the file system). Choose 'Select'
- Type : 'mkdir tmp' without quotes, then Hit the enter key of your keyboard.
- Return to the main screen (Go back 3 times)
- Choose 'Install' and select the file.
Click to expand...
Click to collapse
>>> http://forum.xda-developers.com/showthread.php?t=2595654&page=12
This is to bad - it's the most recent version and the recovery has a bug like this!
Code:
Installing Carbonrom 4.4.4. for HTC Desire
Homemade by spezi77
Next shot should be Lollipop :victory:
[ROM/WIP] [5.0.2] [Jan-17] [UNOFFICIAL] ParanoidAndroid 5.0 Alpha
>>> http://forum.xda-developers.com/htc-desire/development/rom-paranoidandroid-5-0-alpha-t3002046
Des!re said:
There is BIG FAT BUG in the newest TWRP (v2.7.1.0)
You can't install anything before manually create the tmp directory
>>> http://forum.xda-developers.com/showthread.php?t=2595654&page=12
This is to bad - it's the most recent version and the recovery has a bug like this!
Code:
Installing Carbonrom 4.4.4. for HTC Desire
Homemade by spezi77
Next shot should be Lollipop :victory:
[ROM/WIP] [5.0.2] [Jan-17] [UNOFFICIAL] ParanoidAndroid 5.0 Alpha
>>> http://forum.xda-developers.com/htc-desire/development/rom-paranoidandroid-5-0-alpha-t3002046
Click to expand...
Click to collapse
I've personally never used TWRP on the Desire.
I recommend trying with 4EXT Recovery, never had any issues with it.
If you can successfully flash an hboot, you should be able to flash the recovery.img using the same method.
Related
Whenever I try to flash a rom, i get this error:
E:Can't chown/mod /system/etc/init.d (No such file or directory)
E:Failure at line 64: set_perm etc.
Installation aborted!
The roms i have tried are: Pinky's Rom, Leedroid, Official(rooted) rom
Hboot; Version: 0.93
I can't figure out what to do! Someone please help!
Did you root with alpharev?
If not do it and install alpharev recovery as you root it and will be fine.
I had same issue and that fixed it
Sent from my HTC Desire using XDA Premium App
08r3308 said:
Did you root with alpharev?
If not do it and install alpharev recovery as you root it and will be fine.
I had same issue and that fixed it
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
You cannot root with alpharev! Alpharev seets you s-off. Before alpharev can do this, you need root access. This you get by rooting your phone e.g. with unrevoked. Alpharev does not have an own recovery, it is clockworkmod.
@Umair.K:
Did you root your phone already?
So you run unrevoked then alpharev? Or only unrevoked? Because with mine i had to run untrvoked then alpha to be able to use recovery
Sent from my HTC Desire using XDA Premium App
08r3308 said:
So you run unrevoked then alpharev? Or only unrevoked? Because with mine i had to run untrvoked then alpha to be able to use recovery
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Yes. First unrevoked to get root + recovery and then alpharev to s-off.
Ok thank you i hope this helps op as well
Sent from my HTC Desire using XDA Premium App
Oh sorry should have given all those details before, here you go:
Bravo Pvt3 S-off
Hboot- 0.93.1000
Radio: 5.09.00.20
And as you can see, I am rooted and plus S-off with Alpha rev... The weird part is that I can flash Cm7-Stable mod and its working but whenever i try to flash any other rom, i get the error!
E:Can't chown/mod /system/etc/init.d
(No such file or directory)
E: Failure at line 65:
set_perm_recursive 0 0 0777 0777 SYSTEM:etc/init.d
Installation aborted.
and the last rom i tried to flash was "Bravo_WWE_2.29.405.5_v5"
Umair.K said:
Oh sorry should have given all those details before, here you go:
Bravo Pvt3 S-off
Hboot- 0.93.1000
Radio: 5.09.00.20
And as you can see, I am rooted and plus S-off with Alpha rev... The weird part is that I can flash Cm7-Stable mod and its working but whenever i try to flash any other rom, i get the error!
E:Can't chown/mod /system/etc/init.d
(No such file or directory)
E: Failure at line 65:
set_perm_recursive 0 0 0777 0777 SYSTEM:etc/init.d
Installation aborted.
and the last rom i tried to flash was "Bravo_WWE_2.29.405.5_v5"
Click to expand...
Click to collapse
You have partition for CM7, so any sense rom don't have enough space in /system.
Repartition your phone (look in alpharev site) as sense (default) partition. /system must be 250mb
Sent from my pocket using a pen
mendozinas said:
You have partition for CM7, so any sense rom don't have enough space in /system.
Repartition your phone (look in alpharev site) as sense (default) partition. /system must be 250mb
Sent from my pocket using a pen
Click to expand...
Click to collapse
Oh Thankyou soo much man! Thats exactly what I didn't think of before
But could you give me a guide line on how to partition my sd card like that? Because I purchased the phone from someone else, and he had done all the work himself!
It would be really helpful! Thanks!
You cant partition your sd like that ... you should flash STOCK HBOOT... find it at Alpha Rev pages... and there you will find diferent HBOOT's and everything will be clear for you... You partition your SD for needs of diferent ROM's but when it comes to HBOOT there is only few of them... I suggest CM7 HBOOT.. the one with 130 Mb for system, but pay attention on which ROM you flash...
bluzermajstor said:
You cant partition your sd like that ... you should flash STOCK HBOOT... find it at Alpha Rev pages... and there you will find diferent HBOOT's and everything will be clear for you... You partition your SD for needs of diferent ROM's but when it comes to HBOOT there is only few of them... I suggest CM7 HBOOT.. the one with 130 Mb for system, but pay attention on which ROM you flash...
Click to expand...
Click to collapse
Ha ha.
He is having problems because of CM7 hboot and you suggest to flash it? He needs stock hboot.
Sent from my pocket using a pen
bluzermajstor said:
You cant partition your sd like that ... you should flash STOCK HBOOT... find it at Alpha Rev pages... and there you will find diferent HBOOT's and everything will be clear for you... You partition your SD for needs of diferent ROM's but when it comes to HBOOT there is only few of them... I suggest CM7 HBOOT.. the one with 130 Mb for system, but pay attention on which ROM you flash...
Click to expand...
Click to collapse
Alright thats quite clear but the instructions aren't quite clear on Alpha Rev's page!
It says "If you are already S-OFF, you can get our newest patched HBOOTs from here. (without going through the entire procedure again).
Please read the entire table and pick the partition table with the correct sizes for your ROM. One easy way to switch partition tables, is to nandroid backup,
and verify that the sizes of your backup are indeed the ones listed in the table (or smaller), and restore after flashing hboot"
-So afterwards I tried to use the PB99.img by placing it on the root of my sd card and flashing it via recovery, but didn't work!
-Then i tried to use "Android Flasher(1.76)" to flash the new hboot, but that failed aswell! :S
So do i have to repeat the whole S-off procedure again or do i need to use cmd and type in commands to flash a new H-boot? This is getting confusing :O!
If your phone is s-off, you do not have to s-off again. To recognize if your phone is s-off:
1.) Splash screen is the joker
2.) If you boot into hboot (starting with pressed volume down button) first line should be "alpharev" and in the second line the last should be "s-off".
When you use android flasher, you must not use the file PB99_IMG-XXX.zip. You have to use the file bravo_alphaspl-xxx.img ("xxx" stands for the hboot you want).
When you use the method with PB99IMG_XXX.zip, you have to rename the file into PB99IMG.zip and copy it to the root of you sd-card (just watch out, you do not rename it to PB99IMG.zip.zip, because windows hides known file extensions).
Wether you decide for android flasher or directly the method with the zip files, make a complete nandroid backup first. Then download the hboot you want and you need for the method you decided (Do not forgot to check md5 after downloading the hboot!) and run the update.
How you do this:
Android flasher:
1.) Make sure you have usb debug mode on, the behaviour when usb is connected is on "only load" and you have installed hboot dand htc drivers
2.) Connect the phone with your computer
3.)
4.) Choose the file bravo_alphaspl-xxx.img and run the update (android flasher will say you when it's finished)
PBIMG99.zip:
(...)Start the phone in HBOOT mode (VolDown+POWER) to flash the HBOOT without a PC.
Click to expand...
Click to collapse
(from alpharev website)
In both methods now boot into recovery, wipe everything and restore the nandroid backup.
No warranty for any damage!
I get this while using android flasher
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* daemon started successfully *
fastboot.exe flash hboot hboot.img
< waiting for device >
sending 'hboot' (512 KB)...
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
OKAY [ 0.161s]
finished. total time: 0.248s
rebooting into bootloader...
OKAY [ 0.096s]
finished. total time: 0.096s
finished. total time: 0.096s
erasing 'cache'...
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
Del hboot.img
fastboot.exe reboot
rebooting...
Is this right or is there something wrong?
finished. total time: 0.000s
Umair.K said:
I get this while using android flasher
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* daemon started successfully *
fastboot.exe flash hboot hboot.img
< waiting for device >
sending 'hboot' (512 KB)...
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
OKAY [ 0.161s]
finished. total time: 0.248s
rebooting into bootloader...
OKAY [ 0.096s]
finished. total time: 0.096s
finished. total time: 0.096s
erasing 'cache'...
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
Del hboot.img
fastboot.exe reboot
rebooting...
Is this right or is there something wrong?
finished. total time: 0.000s
Click to expand...
Click to collapse
Download and install the app quick system info pro:
http://www.appbrain.com/app/quick-system-info-pro/org.uguess.android.sysinfo.pro
After starting you can compare the showed partition sizes to these of downloaded hboot. If it's fitting, everything is all right. I remember i had the same "issue" and everything is fine.
hi, i'm new to tis, i've root my phone (i thought so) ...
i've root using Unrevoked and S-OFF using AlphaRev....
---AlphaRev---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051D
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
Aug 10 2010, 17:52:18
i've done it for quite a while, but until now i still cant flash any ROM to my phone... really meant it, cant flash any ROM...
when i try to flash, smthing like this pop out...
--Installing: SDCARD:update-cm-6.1.1-Desire-signed.zip
E:Can't find MISC:
Finding update package...
Opening Update package...
Installing update...
Welcome to CyanogenMod-6.1.1-Desire!
assert failed: write_raw_image('/tmp/boot.img'.'boot')
E:Error in /sdcard/update-cm-6.1.1-Desire-signed.zip
(status 7)
Installation aborted.
is it because of my SD Card...??? Im using Samsung 16G, but i've tried using few other brand of 2Gb SD Card, still unsuccessfull...
can anyone help me...??? sorry coz i'm a noob...
MatDrOiD said:
You cannot root with alpharev! Alpharev seets you s-off. Before alpharev can do this, you need root access. This you get by rooting your phone e.g. with unrevoked. Alpharev does not have an own recovery, it is clockworkmod.
@Umair.K:
Did you root your phone already?
Click to expand...
Click to collapse
you don't need a rooted rom for revolutionary or alpharev... When the utility runs it gains temp root and is able to continue. The proof is in the wildfire AND me running it straight after I used a RUU on my Desire and used it without rooting
HTC Desire (ojan) said:
is it because of my SD Card...??? Im using Samsung 16G, but i've tried using few other brand of 2Gb SD Card, still unsuccessfull...
can anyone help me...??? sorry coz i'm a noob...
Click to expand...
Click to collapse
I doubt it's your sd-card. Okay since you've got S-OFF lets flash a different recovery. Follow these steps:
All you have to do is downlaod fastboot commander, and the java jdk for the tool to work.
Then, download the Ra Desire recovery
Once you've got that, but into fastboot (power off, hold back key & power), and plug in via USB.
run fastboot commander, navigate to the "misc" tab, select "recovery" "boot" "userdata" "system" "cache" "sd-ext"and nothing else and click "erase chosen partition(s)", then go back to the "Hboot, radio & rec" tab, choose "recovery", and find the recovery.img you have downloaded.
Then, simply press "flash recovery"
Once that's done, power off and reboot into recovery (power off, volume down & power, then use volume down key to navigate to RECOVERY and press power to select)
Then flash a ROM of your choice. For me this is the best way to flash new ROMs since it's a good, clean install and you don't get remaining crap left over from old ROMs
Did you wipe everything before flashing the rom?
Swyped from Oxygen with Transparent XDA App
yes, i'll try this and let u know if its working... thanks...
by the way, i've wipe everything before i try to flash a new ROM, wiping DalvikCache is unsuccesfull...
is this fixable ?
would converting it to android fix it ?
watercooled223 said:
is this fixable ?
would converting it to android fix it ?
Click to expand...
Click to collapse
I think you could learn a thing or two from this guy :
tytanick said:
Hello guys
BRAVO PVT3 SHIP S-ON
HBOOT-0.92.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.17.05.23
i have Recovery RA-desire-v2.0.0
1. Cant use revolutionary because my Hboot is unsupported
2. alpharev dont work either because of hboot version i suppose ?
3. Mounting SD in recovery ends: Can't mount /dev/block ...... (no such file or directory) E:Can't mount /sdcard
4. Partitioning dont work because recovery dont see SD (tried 2 differend sd cards, (i made even only fat32 under windows with EASEUS partition.
5. Everything i do in recovery on SD ends up with: Error: Run 'fs ext3' via adb !
6. fastboot oem enableqxdm 0 - wont work !
7. "fastboot erase system" - erasing 'system'...... FAILED (remote: not allowed)
8. i cant use Android Flasher cause i have S-ON
And still i cant make S-OFF because of hboot version ! WTF
Click to expand...
Click to collapse
watercooled223 said:
is this fixable ?
would converting it to android fix it ?
Click to expand...
Click to collapse
With this information it is impossible to help you! Read and follow what erklat posted or rather meant with it.
1. can you enter ure bootlaoder
2.do you have clockwork mod or a recovery installed ?
3. are you s off or s on ?
4. what did you do eg did you flash a certain file etc ?
Is it the "white htc screen" as in the boot animation? Or the boot logo? If it's the boot animation then a simple full wipe will solve all the problems but if it's the actual boot logo, then you may be in a big mess.
Hi,
I have HTC Wildfire Buzz which had a problem getting stucking at HTC logo and kept rebooting. I decided to unlock the bootloader and flash a custom rom, I downloaded CWM recovery and tried flashing a custom rom but got an error and then I tried flashing different variations of CM roms such as update-cm-7.1.0.1-buzz-signed.zip and cm_buzz_full-256.zip but I got different types of errors including Err 7.
The other custom rom I tried to install was Android_Freedom_Wildfire_By_MONI69_a2sd but I kept getting the following error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
I tried running different relevant RUUs based on my phone region but always ended up with error due to the fact that the firmware version currently installed is 2.46.0.0 and all the RUUs have versions lower than it.
I would appreciate providing me with your guidance and advice, my phone info is provided below.
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: SH13TPY12305
INFOimei: xxxxxxxxxxxxxx
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 4211mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
yabdali said:
Hi,
I have HTC Wildfire Buzz which had a problem getting stucking at HTC logo and kept rebooting. I decided to unlock the bootloader and flash a custom rom, I downloaded CWM recovery and tried flashing a custom rom but got an error and then I tried flashing different variations of CM roms such as update-cm-7.1.0.1-buzz-signed.zip and cm_buzz_full-256.zip but I got different types of errors including Err 7.
The other custom rom I tried to install was Android_Freedom_Wildfire_By_MONI69_a2sd but I kept getting the following error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
I tried running different relevant RUUs based on my phone region but always ended up with error due to the fact that the firmware version currently installed is 2.46.0.0 and all the RUUs have versions lower than it.
I would appreciate providing me with your guidance and advice, my phone info is provided below.
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: SH13TPY12305
INFOimei: xxxxxxxxxxxxxx
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 4211mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
Click to expand...
Click to collapse
Hello dude...i have the same phone with exactly same specs n had d same prob
go to fastboot,connect usb
now u have a .img file in ur rom's zip.
extract it to fastboot folder
via cmd go to fastboot folder with ur ph connected.. type
fastboot flash boot xxx.img
it will take some time
nxt flash cwm if u dont hv it
then get a micro sd wid ur rom(unedited) and flash it via cwm...disable signature verification if needed
press d thanks button n voila u have ur nw rom
ontheflames said:
Hello dude...i have the same phone with exactly same specs n had d same prob
go to fastboot,connect usb
now u have a .img file in ur rom's zip.
extract it to fastboot folder
via cmd go to fastboot folder with ur ph connected.. type
fastboot flash boot xxx.img
it will take some time
nxt flash cwm if u dont hv it
then get a micro sd wid ur rom(unedited) and flash it via cwm...disable signature verification if needed
press d thanks button n voila u have ur nw rom
Click to expand...
Click to collapse
Hi, Thanks for your advice, unfortunately it didnt work! I tried the following:
Extracting the rom zip and flashing boot.img via fastboot then using CWM flashing the rom xxxx.zip.
update-cm-7.1.0.1-buzz-signed.zip error:
assert failedackage_extract_file("boot.img","/tmp/boot.img")
E:error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 7)
Installation aborted
Android_Freedom_Wildfire_By_MONI69 error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
Hope this gives further insights about the problem, any suggestion advise would be highly appreciated.
hey man, silly question but are you sure you are doing a full factory wipe, data wipe cache wipe and dalvick cache wipe?
you should do the wipes every time you try to flash a new rom.
heavy_metal_man said:
hey man, silly question but are you sure you are doing a full factory wipe, data wipe cache wipe and dalvick cache wipe?
you should do the wipes every time you try to flash a new rom.
Click to expand...
Click to collapse
Yes, I use CWM to do factory reset, cache, dalvick wipes everytime I flash a rom!
yabdali said:
Hi, Thanks for your advice, unfortunately it didnt work! I tried the following:
Extracting the rom zip and flashing boot.img via fastboot then using CWM flashing the rom xxxx.zip.
update-cm-7.1.0.1-buzz-signed.zip error:
assert failedackage_extract_file("boot.img","/tmp/boot.img")
E:error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 7)
Installation aborted
Android_Freedom_Wildfire_By_MONI69 error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
Hope this gives further insights about the problem, any suggestion advise would be highly appreciated.
Click to expand...
Click to collapse
Another alternative is formating all partitions before flashing..
and btw did u extract the whole zip for boot.img?
what is ur cwm version?
did u try disabling signature check and script asserts??
ontheflames said:
Another alternative is formating all partitions before flashing..
and btw did u extract the whole zip for boot.img?
what is ur cwm version?
did u try disabling signature check and string asserts??
Click to expand...
Click to collapse
Hi, thanks for your continous support, I tried the following but not matter what rom I flashed I still get some sort of an error. As for your question regarding the boot.img, yes I extracted the xxxx.zip flashed boot.img via fastboot pulled the batter started CWM and installed the original xxxx.zip. I tried the partiations formatting, below are the details.
ClockworkMod Recovery v2.5.0.7
Green color
wipe data/factory
wip cache
wipe delivak (E: can't mount /dev/block.mmcblk0p2)
format system
format boot
format data
format cache
toggle script asserts/signature (disabled)
Rom: cm-buzz_full-256.zip
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/cm-buzz_full-256.zip
(Status 7)
Installation aborted.
Rom: update-cm-7.1.0.1-buzz-signed.zip
E:Error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 0)
Installation aborted
I also get package_extract_file("boot.img","/tmp/boot.img") error in some other roms.
yabdali said:
Hi, thanks for your continous support, I tried the following but not matter what rom I flashed I still get some sort of an error. As for your question regarding the boot.img, yes I extracted the xxxx.zip flashed boot.img via fastboot pulled the batter started CWM and installed the original xxxx.zip. I tried the partiations formatting, below are the details.
ClockworkMod Recovery v2.5.0.7
Green color
wipe data/factory
wip cache
wipe delivak (E: can't mount /dev/block.mmcblk0p2)
format system
format boot
format data
format cache
toggle script asserts/signature (disabled)
Rom: cm-buzz_full-256.zip
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/cm-buzz_full-256.zip
(Status 7)
Installation aborted.
Rom: update-cm-7.1.0.1-buzz-signed.zip
E:Error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 0)
Installation aborted
I also get package_extract_file("boot.img","/tmp/boot.img") error in some other roms.
Click to expand...
Click to collapse
Strange...btw how did ur wf stop booting all of a sudden? I think u have failed to get proper root and unlocked bootloader
pl verify it in hboot..on top it must display 'UNLOCKED'
more when u comment
Hit thanks if i helped u
ontheflames said:
Strange...btw how did ur wf stop booting all of a sudden? I think u have failed to get proper root and unlocked bootloader
pl verify it in hboot..on top it must display 'UNLOCKED'
more when u comment
Hit thanks if i helped u
Click to expand...
Click to collapse
Its my wife's phone. Out of the blue started getting stuck in HTC logo and kept rebooting. Yes, its unlocked using HTCDEV and it shows that in hboot "UNLOCKED".
Appreciate your further feedback..
I'd first try a different sd card, it looks to me like it's not reading properly with some of those errors, mount /system from Cwm mounts and storage option before wiping and flashing the new rom too, if that fails try fastboot flashing Cwm 5.0.2.0, then try again. I've never seen this problem before so my apologies if I'm way off the mark.
Sent from my HTC Wildfire using xda premium
i have the same problem here.
hboot 1.02.0000 - won't downgrade for anything in the world
s-on
in cwm i cannot install any rom. says "status 0 installation aborted" or "bad"
the ruu's are not working either.
i don't have a backup or a rom installed. if there's anyone who can provide me a buzz backup so i can restore into my phone, i would much appreciate it. i think is the single thing i didn't try.
seagerfreak said:
i have the same problem here.
hboot 1.02.0000 - won't downgrade for anything in the world
s-on
in cwm i cannot install any rom. says "status 0 installation aborted" or "bad"
the ruu's are not working either.
i don't have a backup or a rom installed. if there's anyone who can provide me a buzz backup so i can restore into my phone, i would much appreciate it. i think is the single thing i didn't try.
Click to expand...
Click to collapse
It already has been mentioned a few times here in the forum: htcdev won't give you s-off and it's not absolutely clear (= not confirmed) that can get s-off after the htcdev unlock (because you can't downgrade the HBOOT).
I have no idea if there's a possibility but it doesn't look good - there are 2 other threads regarding this issue here in Q&A or General section - you might want to have a look.
For the install problem I'm pretty sure that's something different as you usually should be able to install a ROM...
i have looked into othet threads. nothing works
seagerfreak said:
i have looked into othet threads. nothing works
Click to expand...
Click to collapse
You need to relock your boot loader for an ruu to work. relock the bootloader and remove the rom.zip from the htcdev bootloader unlock ruu. Remember an ruu with a lower hboot will not run. Rename it to pc49img.zip and put it on the root of your sdcard. Boot to hboot and allow the bootloader to flash the rom. but if I was you I would just try to get access to an xtc clip and fully s-off the phone. Then it will run any ruu and custom rom.
Sent from my HTC Sensation using xda premium
heavy_metal_man said:
You need to relock your boot loader for an ruu to work. relock the bootloader and remove the rom.zip from the htcdev bootloader unlock ruu. Remember an ruu with a lower hboot will not run. Rename it to pc49img.zip and put it on the root of your sdcard. Boot to hboot and allow the bootloader to flash the rom. but if I was you I would just try to get access to an xtc clip and fully s-off the phone. Then it will run any ruu and custom rom.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
thanx for the answer. i have relocked my bootloader. renamed the rom and put it on the root of the sdcard. the hboot shows a loading bar, but after loading, nothing happens. the part with the removing the rom.zip from the htcdev bootloader unlock ruu i didn't understand. can you be more specific? thanx
quick edit: when running a ruu, it gives me usb connection error
Here's the quick guide
Install hTc drivers successfully on pc.
Remove hTc sync and other related apps.
Now download clockworkmod recovery(whichever you want) and fastboot+adb kit on pc.
Open fastboot.
Connect ur phone. Load the bootloader and then fastboot. Fastboot mode(something like that) should be on your phone. Paste recovery and boot image in fastboot folder.
Type fastboot devices
Type fastboot flash boot boot.img(i faintly remember what this was, sorry )
Type fastboot flash 'recoveryname'.zip
After that disconnect ur phone.
Select recovery.
(If u dont see anything, it was unsuccessful, hold vol up+power to see default recovery.)
Now install roms like this(http://forum.xda-developers.com/showthread.php?t=1851096):p(my rom) via recovery.
Hit Thanks.
You are done
Note:s off is not required for flashing a custom rom, however an unlocked bootloader is.
Edit: Hey sorry didnt read my earlier posts, after all wf is slow on internet.
However this is the problem where u you are flashing incorrect boot.img
Make sure its from your rom, or try using the one in cm7, try both as Im not exactly certain. If u have cwm it asserts that u have root and you can flash roms.
ontheflames said:
Here's the quick guide
Install hTc drivers successfully on pc.
Remove hTc sync and other related apps.
Now download clockworkmod recovery(whichever you want) and fastboot+adb kit on pc.
Open fastboot.
Connect ur phone. Load the bootloader and then fastboot. Fastboot mode(something like that) should be on your phone. Paste recovery and boot image in fastboot folder.
Type fastboot devices
Type fastboot flash boot boot.img(i faintly remember what this was, sorry )
Type fastboot flash 'recoveryname'.zip
After that disconnect ur phone.
Select recovery.
(If u dont see anything, it was unsuccessful, hold vol up+power to see default recovery.)
Now install roms like this(http://forum.xda-developers.com/showthread.php?t=1851096):p(my rom) via recovery.
Hit Thanks.
You are done
Note:s off is not required for flashing a custom rom, however an unlocked bootloader is.
Edit: Hey sorry didnt read my earlier posts, after all wf is slow on internet.
However this is the problem where u you are flashing incorrect boot.img
Make sure its from your rom, or try using the one in cm7, try both as Im not exactly certain. If u have cwm it asserts that u have root and you can flash roms.
Click to expand...
Click to collapse
i made every step you told me to. this is what i get.
the only way i can make the phone visible in adb, is in recovery. being unable to boot a rom, i cannot set the usb debugging mode. so, everything that i will make, is via fastboot or ruu. but ruu gives me usb connection error or error [155] in fastboot, and baterry < 30% in adb mode.
What if you unlock your bootloader again and flash a recovery.img from fastboot? Maybe there is problem with your cwm recovery. I guess you have already tried formatting you sd card, tried a different sd card and tried different custom roms.
I would definitely try to get some more charge in your phone first because if you loose power while flashing it could end up really bad. An RUU won't install on low battery (i thought you needed >70%) what if you charge up and run ruu from adb again?
Rename your CID to HTC_001 (fastboot writecid HTC__001). Relock your bootloader using fastboot oem lock. Run a WWE RUU. Use the rooting link in my sig.
Done, and don't ever root with HTCDev again.
hans moleman said:
What if you unlock your bootloader again and flash a recovery.img from fastboot? Maybe there is problem with your cwm recovery. I guess you have already tried formatting you sd card, tried a different sd card and tried different custom roms.
I would definitely try to get some more charge in your phone first because if you loose power while flashing it could end up really bad. An RUU won't install on low battery (i thought you needed >70%) what if you charge up and run ruu from adb again?
Click to expand...
Click to collapse
i tried every possible combination of cwms and roms.
usaff22 said:
Rename your CID to HTC_001 (fastboot writecid HTC__001). Relock your bootloader using fastboot oem lock. Run a WWE RUU. Use the rooting link in my sig.
Done, and don't ever root with HTCDev again.
Click to expand...
Click to collapse
i get this error
C:\android sdk\platform-tools>fastboot oem writecid HTC__001
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
C:\android sdk\platform-tools>
Click to expand...
Click to collapse
just to be clear, the phone was in this state, it's not mine. i am only trying to put whatever rom i can so i can make it work
By mistake I have tried to update my HTC One X with an EVITA rom, now my Phone is not booting at all.
Tried installing the original RUU_ENDEAVOR exe, but it gives ma a 156/158 error. During the update of the signature (translated).
I guess because it is assuming I have a (not working) 4.18.401.2 ROM now and it only sets the stock back if it is equal or newer to that version (no where to be found).
Secondly when I try to install any rom the fastboot commando is returning "remote: not allowed".
The bootloader is giving me the following information:
*** UNLOCKED ****
ENDEAVORU PVT SHIP S-ON RL
GBOOT-1.72.0000
COKD-None
MICROP-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
Jun 21 2013, 18:24:41
I can enter RECOVERY with has ClockWorks installed, when I try to install a custom rom there with sideload it says "remote: not allowed"
Cleared all Cash and cleaned the device, Relocking the bootloader does not help, leaving the phone shutdown for a while, are things I did try my self already.
I am totally stuck and would appreciate any advice you might have !
Zaleo said:
By mistake I have tried to update my HTC One X with an EVITA rom, now my Phone is not booting at all.
Tried installing the original RUU_ENDEAVOR exe, but it gives ma a 156/158 error. During the update of the signature (translated).
I guess because it is assuming I have a (not working) 4.18.401.2 ROM now and it only sets the stock back if it is equal or newer to that version (no where to be found).
Secondly when I try to install any rom the fastboot commando is returning "remote: not allowed".
The bootloader is giving me the following information:
*** UNLOCKED ****
ENDEAVORU PVT SHIP S-ON RL
GBOOT-1.72.0000
COKD-None
MICROP-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
Jun 21 2013, 18:24:41
I can enter RECOVERY with has ClockWorks installed, when I try to install a custom rom there with sideload it says "remote: not allowed"
Cleared all Cash and cleaned the device, Relocking the bootloader does not help, leaving the phone shutdown for a while, are things I did try my self already.
I am totally stuck and would appreciate any advice you might have !
Click to expand...
Click to collapse
Go into recovery, mount the sd card. Copy a rom on there, full wipe and flash it
Stefan0vic said:
Go into recovery, mount the sd card. Copy a rom on there, full wipe and flash it
Click to expand...
Click to collapse
As long as you can still get into recovery, you can probably still flash a new rom. Do a full wipe (including dalvik cache). If you can not get into recovery try flashing recovery first from fastboot (fastboot flash recovery recovery.img), place recovery.img in fastboot folder
Stefan0vic said:
Mount the sd card. Copy a rom on there
Click to expand...
Click to collapse
If I go in recovery and mount my sdcard, how do I copy something on the cart ?
Assuming there is a sdcard in the phone internal somewhere, my device does not seem to have a slot to put one in.
Ok, found new info...
When booting in the bootloader it if giving errors (screen goes a way quickly after, needed 6 resets before I could type it over):
SD Checking...
Failed to open usb master mode
[Preload] Failed to open usb master mode
Loading PJ46IMG.zip image...
Failed to open usb master mode
Please plug off USB
Does this give any hints?
Ok, I had to go in the recovery to 'Mount USB device'.. Then Windows got a drive and I could copy a rom (zip) to the sdcart..
That one I installed in the recovery menu. after some minutes it did say it was done, and now the phone is working with a custom rom !!
Thanks Agil1ty !!!
Good.
Sent from my HTC One X using xda app-developers app
Zaleo said:
Ok, found new info...
When booting in the bootloader it if giving errors (screen goes a way quickly after, needed 6 resets before I could type it over):
SD Checking...
Failed to open usb master mode
[Preload] Failed to open usb master mode
Loading PJ46IMG.zip image...
Failed to open usb master mode
Please plug off USB
Does this give any hints?
Click to expand...
Click to collapse
This is because you had a USB plug in when starting bootloader. That's all.
Still having the problem? Wipe your cache and dalvik cache. Restore backup. If your on JB, try flashing your ROM afew times to get it working proper. Did about 5 times on Saturday before I got my phone back to normal.
I accidentally tried to flash a rom with S-on (I wasn't thinking and was in a hurry). I have recovery still. But I cannot get any rom (stock or otherwise) to flash successfully -- when I flash CM or LS I just get "{phone|nfc|system} services have stopped working".
I've tried to flash via sideload in recovery and the fastboot sideload always stops at 76%. I'm not quite sure what my options are. I've googled around for a few hours, but cannot find anything that is what I need.
TWRP cannot mount data or cache...
Is it possible to S-off in recovery?
My hboot is:
M8-UL PVT SHIP s-on
Mar 4, 2014 - 3.16.0.0000
Radio-1.14.21331931.LA02_2g
OpenDSP-v26.2.2-005380M8974.0106
Sounds like you have the wrong recovery for your phone.
lilott8 said:
I accidentally tried to flash a rom with S-on (I wasn't thinking and was in a hurry). I have recovery still. But I cannot get any rom (stock or otherwise) to flash successfully -- when I flash CM or LS I just get "{phone|nfc|system} services have stopped working".
I've tried to flash via sideload in recovery and the fastboot sideload always stops at 76%. I'm not quite sure what my options are. I've googled around for a few hours, but cannot find anything that is what I need.
TWRP cannot mount data or cache...
Is it possible to S-off in recovery?
My hboot is:
M8-UL PVT SHIP s-on
Mar 4, 2014 - 3.16.0.0000
Radio-1.14.21331931.LA02_2g
OpenDSP-v26.2.2-005380M8974.0106
Click to expand...
Click to collapse
What version of TWRP are you using? I'm only using 2.7.1.0 - I know that previous versions had sometimes issues. As far as I know you can't get s-off in recovery. Only when being in fastboot (bootloader).
lilott8 said:
I accidentally tried to flash a rom with S-on (I wasn't thinking and was in a hurry). I have recovery still. But I cannot get any rom (stock or otherwise) to flash successfully -- when I flash CM or LS I just get "{phone|nfc|system} services have stopped working".
I've tried to flash via sideload in recovery and the fastboot sideload always stops at 76%. I'm not quite sure what my options are. I've googled around for a few hours, but cannot find anything that is what I need.
TWRP cannot mount data or cache...
Is it possible to S-off in recovery?
My hboot is:
M8-UL PVT SHIP s-on
Mar 4, 2014 - 3.16.0.0000
Radio-1.14.21331931.LA02_2g
OpenDSP-v26.2.2-005380M8974.0106
Click to expand...
Click to collapse
fastboot erase cache
load twrp, do not click side load
adb push rom.zip /sdcard/
try to flash rom, takes a while to send rom over, about 400 sec for 1.5 gigs. Wait till your prompt comes back up before flashing
If this doesn't work, yuou will need to format data so make sure your internal card is backed up if needed
No soff, phone must be booted with stock kernel to gain soff.
[solved] Fixed it!
an0ther said:
fastboot erase cache
load twrp, do not click side load
adb push rom.zip /sdcard/
try to flash rom, takes a while to send rom over, about 400 sec for 1.5 gigs. Wait till your prompt comes back up before flashing
If this doesn't work, yuou will need to format data so make sure your internal card is backed up if needed
No soff, phone must be booted with stock kernel to gain soff.
Click to expand...
Click to collapse
I was/am using Philz recovery.
Thanks, what ended up happening is the /data AND the /cache partitions were corrupted so I had to e2fsck those partitions. I then could reload a stock image, get s-off and am now in a happy place