Related
My desire is unlocked. I installed HTC stock rom of froyo. It installed but mobile network is missing and too much reboot/restart. I did not take any nandroid backup. Now I cannot use this 2.2 and also cannot go back to 2.1, what to do? Now bootloader is .80 and software number is 2.09.405.8
Please suggest.
Flash a new radio...if it´s the same...flash another rom....
edit: put the rom to sd card and go into recovery and flash the zip
Alex-V said:
Flash a new radio...if it´s the same...flash another rom....
edit: put the rom to sd card and go into recovery and flash the zip
Click to expand...
Click to collapse
Can you please post the link for the new radio. I have no idea about radio. Thanks
mirajrussell said:
Can you please post the link for the new radio. I have no idea about radio. Thanks
Click to expand...
Click to collapse
no problem
http://android.adamg.co.uk/bravo/radio/32.43.00.32U_5.09.00.20.zip
edit: flash it and wait for complete booting the system
Alex-V said:
no problem
http://android.adamg.co.uk/bravo/radio/32.43.00.32U_5.09.00.20.zip
edit: flash it and wait for complete booting the system
Click to expand...
Click to collapse
it's not working.
I copied the file to sd card and renamed it update.zip, then went to recovery mode and selected apply sdcard:update.zip
It said:signature verification failed.........installation aborted.
My current radio version is 4.06.00.02_2
Please suggest
mirajrussell said:
it's not working.
I copied the file to sd card and renamed it update.zip, then went to recovery mode and selected apply sdcard:update.zip
It said:signature verification failed.........installation aborted.
My current radio version is 4.06.00.02_2
Please suggest
Click to expand...
Click to collapse
if you have rooted with unrevoke you can disable signature...but there is no need to change it to update.zip...go to flash a zip (not a update zip)
did it work for you mirajrussell? I think I've got the same issue....
I used a gold card and flashed the rom again (didn't do radio update). now it's working.
Only one problem: The application from market downloads to the phone but during installation the phone restarts and therefore no market application can be installed.
bootloader is .80 and software number is 2.09.405.8
Radio version is 4.06.00.02_2
If you are still having the market probem you might need to reboot you phone into recovery and wipe the phone's cache. It worked for me and also sorted the problem I had when my phone restarted everytime I tried to record a video.
Here is my story:
I own a Desire Z,bought in Hong Kong with stock sense ROM.
I see the new Egypt RUU on the forum and tried to flash it(for testing the new Radio version).
As expected the RUU wipe my recovery and HBoot etc. But soon I found that it's unable to root(tried gfree/rage method/VINSIONary r14). Luckily I did gfree on my old ROM so I go back to 405.5WEE ROM, everything is fine -> root, ENG HBoot,-> ROM Manager -> Flash 2.5.1.3 recovery -> Restore backup from SD-Card
But it just freeze on the green HTC letters(recovery mode).
I went back to bootloader, flash ClockworkMod 2.5.1.1 using fastboot -> successfully enter recovery, restored old ROM
Then I tried to update to 2.5.1.3 again, boot into recovery, same freeze.
So the problem is: I was using 2.5.1.3, all working before I went to Egypt, but now it just didn't work.
Anyone has the similar experience with this? any suggestion to get 2.5.1.3 work again?
thanks
EDIT:Solved. Check the clockworkmod folder on the SD-Card and see if ROM Manager successfully downloaded the correct image. If not, delete and reinstall.
when you say you went back to your working stock rom, do you mean via an ruu?
If so then the fact you were on Egypt is nothing to do with what your experiencing now at all.
Lennyuk said:
when you say you went back to your working stock rom, do you mean via an ruu?
If so then the fact you were on Egypt is nothing to do with what your experiencing now at all.
Click to expand...
Click to collapse
No. I backed up my original ROM using ClockworkMod 2.5.1.3 before I went Egypt.
I restored it after rooting the WEE ROM which is flashed via RUU.
so, now I'm running my original ROM and everything is fine, except ClockworkMod 2.5.1.3
So I am using 2.5.1.1 now instead of 2.5.1.3.
Don't know why after these process, 2.5.1.3 won't load...
jzhyok said:
No. I backed up my original ROM using ClockworkMod 2.5.1.3 before I went Egypt.
I restored it after rooting the WEE ROM which is flashed via RUU.
so, now I'm running my original ROM and everything is fine, except ClockworkMod 2.5.1.3
So I am using 2.5.1.1 now instead of 2.5.1.3.
Don't know why after these process, 2.5.1.3 won't load...
Click to expand...
Click to collapse
try using rom manager and pressing the flash 2.5.1.3 button like 3-4 times before booting into recovery.
Lennyuk said:
try using rom manager and pressing the flash 2.5.1.3 button like 3-4 times before booting into recovery.
Click to expand...
Click to collapse
not working, still the same.
Tried to click 2.5.1.4, but always failed to flash
Seems only 2.5.1.1 works for my strange phone now
jzhyok said:
not working, still the same.
Tried to click 2.5.1.4, but always failed to flash
Seems only 2.5.1.1 works for my strange phone now
Click to expand...
Click to collapse
are you sure you have perma root and s-off following your crazy world trip? that would be the only reason I can think of that it would fail to flash.
Lennyuk said:
are you sure you have perma root and s-off following your crazy world trip? that would be the only reason I can think of that it would fail to flash.
Click to expand...
Click to collapse
I think so. If I don't get per-root I won't be able to use any recovery , right?
(well the message is actuly: "An error occurred while flashing your recovery.")
I followed a gfree test:
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
Click to expand...
Click to collapse
Sorry for wasting the time guys.
just found what the problem is.
It was a download crap... I checked the clockworkmod folder on SD-Card and find that the 2.5.1.3 image that it downloaded is only 94KB!!
So I deleted it and redownload using ROM Manager. Everthing is fine now.
jzhyok said:
Tried to click 2.5.1.4, but always failed to flash
Click to expand...
Click to collapse
Good that you got it working.
But 2.5.1.4 is not available for Vision, the latest is 2.5.1.3. For some reason if you choose the option to show you all available recoveries, it shows you version numbers that might be available for other phones but not yours
steviewevie said:
Good that you got it working.
But 2.5.1.4 is not available for Vision, the latest is 2.5.1.3. For some reason if you choose the option to show you all available recoveries, it shows you version numbers that might be available for other phones but not yours
Click to expand...
Click to collapse
I thought it just showed recoveries that were "experimental" and not full releases
Lennyuk said:
I thought it just showed recoveries that were "experimental" and not full releases
Click to expand...
Click to collapse
That's what I thought. But it shows 2.5.1.4, and I don't think any such version exists for Vision - e.g. check out the list at the dev's site at http://koush.tandtgaming.com/recoveries/
steviewevie said:
That's what I thought. But it shows 2.5.1.4, and I don't think any such version exists for Vision - e.g. check out the list at the dev's site at http://koush.tandtgaming.com/recoveries/
Click to expand...
Click to collapse
looks like your right, learn something new all the time
I presume it's actually a bug in ROM Manager ?
Need to update my recovery for successful flash of baadnewz desire S
port. Ive got the image, cant find the option in bootloader to install it
though. I am s-off. Searched everywhere but cant find a direct answer.
Any help is appreciated.
Use the fastboot commands to flash it, or the flasher app in ROM Development
EddyOS said:
Use the fastboot commands to flash it, or the flasher app in ROM Development
Click to expand...
Click to collapse
Thanks for the quick answer. Im going to try that now. Another question if i may, sorry if its
noobish just not up to date on this stuff, will say Leedroid or sense roms still work if i have
CM7 hboot?
Edit : Anyone in the same boat go here :
[UTILITY] Android Flasher(Recovery,splash1,Radio,HBOOT,bootanim)[V1.6.1](15/01/11)
Now i really need help. My phone is hanging in fasboot mode while i was
flashing hboot with the flasher. what to do next?
esk02k said:
Now i really need help. My phone is hanging in fasboot mode while i was
flashing hboot with the flasher. what to do next?
Click to expand...
Click to collapse
Can you get into recovery? If so, you could try restoring nandroid and checking that the hboot file downloaded OK - if it came with an MD5 it's worth checking that - before giving it another go.
I've never used the flasher, just adb commands. Never had a problem flashing hboot tables.
00droid said:
Can you get into recovery? If so, you could try restoring nandroid and checking that the hboot file downloaded OK - if it came with an MD5 it's worth checking that - before giving it another go.
I've never used the flasher, just adb commands. Never had a problem flashing hboot tables.
Click to expand...
Click to collapse
Yea my own stupidity i guess. well im gonna pull the battery. lets see what
happens then.
edit : its ok regained control after unpluging usb. how do i know if it installed.
i am familiar with adb. how do i flash the cm7 hboot via that?
I also had problem with the flasher when I started in windows, then the phone just couldnt start or flash a new rom, but when I started the phone with backbottom ipressed and then started Android flasher all worked perfect.
esk02k said:
Yea my own stupidity i guess. well im gonna pull the battery. lets see what
happens then.
edit : its ok regained control after unpluging usb. how do i know if it installed.
i am familiar with adb. how do i flash the cm7 hboot via that?
Click to expand...
Click to collapse
Good news! To check your recovery you can either just boot into recovery and see what version you have, or remain booted and look in /sdcard/clockworkmod.settings (open as text file) to see the version number.
To flash hboots - check the instructions on the Alpharev site: www.alpharev.nl
EDIT: I found this post helpful as the instructions at alpharev are a little minimal at first sight. Obviously you are using the CM7 table not the Oxygen one!
http://forum.xda-developers.com/showthread.php?t=882758
Hi guys, I'm a little stuck/confused. When I boot my phone in Recovery Mode it says I'm running Clockwork Mod v2.5.0.1.
I installed a new version of ROM Manager (v3.0.1.0) flashed ClckworkMod Recovery and that says I have v 2.5.0.7 - so:
1. How do I ensure that the recovery mode is v 2.5.0.7
2. Do I need to unistall ROM Manager or,
3. Just leave it be?
System details:
Rooted HTC Desire
Android version 2.2.1
Baseband version 32.54.00.32U_5.14.05.17
Kernel 2.6.32.36_rcmix_11032
Build number
RCMix HD v3.6.1 D2Ext Rotate
The numbers above don't mean much to me - I'm not a dev.
Thanks in advance.
*EDIT*
I've since downladed and installed the .zip found here: http://forum.xda-developers.com/showthread.php?t=839640
It worked but ROM Manager still says the current recovery is version 2.5.0.7 although when I rebooted the writing was orange. I hope that makes sense to someone...
djkaija said:
It worked but ROM Manager still says the current recovery is version 2.5.0.7 although when I rebooted the writing was orange. I hope that makes sense to someone...
Click to expand...
Click to collapse
This is perfectly normal as 3.0.0.5 isn't an 'official'/final release yet.
ok im truely frustrated after trying to figure this out in past 2 days and reading more than 60 threads/websites.
Problem:
my one x was running 4.0.4 rooted +supre user+CWM, till i got the notification for 4.1 update. i pressed install now and downloaded around 380 MB, during the update phase a red exclamation icon appeared and phone rebooted into 4.0.4.
relocked bootloader, flashed stock recovery and downloaded it again and this time copied the OTA file before pressing install. so i installed and same issue.
uninstalled Avast AV (android) and ran through the same process again, same thing, started up into 4.0.4 again.
unlocked the bootloader, flashed CWM 5.8.4, copied ota file into phone and renamed it to update.zip. ran it from recovery menu and got status 7 error.
downloaded and ran JBFWTOOL21 and followed the instructions, during one of the steps i encountered an error and after restarting the phone i was stock at "HTC One x" with "beatsound" logo at bottom.
NOW NOTHING WORKS
what ive tried so far:
relocked loader and flashed stock recovery and tried Factory Reset, no luck.
unlocked loader and flash CWM and tried wiping cache and wiping disk. nothing.
relocked loader,flashed recovery and ran stock RUU "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed" but it doesnt work, give an error related to version numbers or something.
extracted system.img, boot.img from RUU temp folder ROM.zip and tried to flash but cant flash system.img (918mb). something about not enough HEAP i think.
from the OTA JB zip extracted recovery.img, boot.img and recovery.img and flashed them. nothing.
downloaded "One_X_All-In-One_Kit_v2.1" and tried kernel flash, nothing.
clearing cache via fastboot command also doesnt work
really appreciate any helpful input guys, im really frustrated. thanks
Oh my.. First, stop unlock and relock of bootloader. Do you have a cwm backup from before all this started? Flashing cwm and restoring that backup will get you far.
The first ota attempt failed due to cwm, always return to stock recovery (recovery.img from your cwm backup image) before applying ota update!
Kind Regards
TwinAdk
unfortunately, no. no backup.
since it all started from the official update i didnt make any backups.
Stop trying flash randomly. Run the following command:
fastboot getvar version-main
it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4
woomera said:
it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4
Click to expand...
Click to collapse
Well that's why the older RUU wouldn't work. You have the latest.
You'll need to go to the ROM backups thread and see if you can get a backup and flash its boot.img and restore it from CWM.
Actually, reboot your PC and try to flash system.img and boot.img again. You will probably need to be locked.
but isnt that the boot.img from "OTA_ENDEAVOR_U_JB_45_S_HTC_ARA_3.16.415.4-2.17.415.2_release_304331jrfus698taf4vm1x"?
cause i have already tried it, didnt work. i have the OTA file.
Modified my post. Look up.
i have boot.img from firmware with hboot 3.16 and 3.19, which one to use?
and the system.img is from stock RUU which is "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed", will that work?
the OTA JB is a zip file and doesnt have system.img.
Err.. 1.39?
yes
the firmware included in "JBFWTOOL21" is 1.36 which is used by many to manually upgrade to JB but the firmware inside the OTA file itself is 3.19 which is also the version i updated to since i thought its the reason the update doesnt work.
the Hboot version on my phone is 1.39 at the moment.
Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.
BenPope said:
Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.
Click to expand...
Click to collapse
i dont understand, a backup of what? the system.img?
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
I thought about suggesting that too, but I'm new to flashing so I didn't feel confident enough to do it..
But off the top of my head, a custom rom, complete with boot.img and everything should work..
I'm using http://forum.xda-developers.com/showthread.php?t=2013506, it's super great and support all hboot versions.
No guarantees it will work though.
Kind Regards
TwinAdk
sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
guess it worth a try even though i'd rather fix the problem in hand in another fashion.
gonna give it a try and post the results.
k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM
woomera said:
i dont understand, a backup of what? the system.img?
Click to expand...
Click to collapse
A nandroid backup, like what Clockworkmod recovery makes.
woomera said:
k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM
Click to expand...
Click to collapse
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
NOTE: These instructions require that you have one of the ICS hboot versions in order to work (1.12.0000 or lower). If you have one of the new JB hboots 1.28, 1.31 or 1.33 there is currently no way to return to stock until a JB ruu is released for your device.
Click to expand...
Click to collapse
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk
BenPope said:
A nandroid backup, like what Clockworkmod recovery makes.
Click to expand...
Click to collapse
thanks for the clarification
TwinAdk said:
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk
Click to expand...
Click to collapse
i have read the same thing, also "BenPope" mentioned it. so with this version of Hboot (1.39) i cant restore unless its a nandroid backup.
but i dont wanna go back to stock ICS! i wanna finish what i was trying to do in first place, Upgrade to JB.
but no matter what i do i get the "status 7 error". i have tried it with the OTA my phone downloaded and also downloaded it again directly from HTC website via a link from one of the threads in forum.
so status 7 apparently is related to CRC error but how can that be? and what is my option right now to do the upgrade? also bear in mind that before all these happened the normal upgrade process via the "system update" also failed with a red icon error.
after 2 weeks of total depression, i succesfull unlocked my bootloader, and installed the cwm Recovery.
and i read a thread about installing custom roms after unlocking bootloader,
i downloaded the latest cyanogenmod for my desire HD and installed it with the "choose zip from sd" option,
i forgot to make a backup ( biggest fail ever), and now , when i try to start the device, it stops on the "Softbank" logo,
(for 1 week, i completely crashed it, and installed the JP softbank android)
i only wanted a custom rom, and thebest irony was, the most videos said me: "Custom rom in 5 minutes",
can anyone please help me?, thanks
Flash the boot.img from the ROM zip using fastboot.
bananagranola said:
Flash the boot.img from the ROM zip using fastboot.
Click to expand...
Click to collapse
which rom.zip?,
Karianos said:
which rom.zip?,
Click to expand...
Click to collapse
The one you tried to install...? Didn't you say you downloaded the latest CM?
i had installed the: "Softbank JP android version" then i tried to install "cm-7.2.0-ace" the latest Cyanogen mod via CWM Recovery , after this the device didn't started
Karianos said:
i had installed the: "Softbank JP android version" then i tried to install "cm-7.2.0-ace" the latest Cyanogen mod via CWM Recovery , after this the device didn't started
Click to expand...
Click to collapse
I don't know the softbank one, but the CM one should be packaged in a zip file. Flash it in recovery (sounds like you already did that) and then move it to your computer, unzip it, and flash the boot.img inside it from fastboot. Clearer directions are linked in the Ace Think Tank thread in DHD General.