Develop Bugs

[problem] desire restarting after cyanogen flash

Heya,
I was using the LeeDroid ROM until today, when I desided I want Cyanogen.
I backed up the phone using ROM Manager, wipe and flashed Cyanogem 6.1 RC2. The phone restarted, turned on - but it cn't load the actual android OS - just keeps restarting on the blue wheel-thing animation.
I can boot my phone into recovery, but can't do much from there since its S-ON.
The recovery windows says:
bravo pvt1 ship s-on
hboot-0.80.0000
microp-031d
touch panel-synt0101
radio-5.10.05.23
fastboot
recovery
clear storage
simlock
what can I do to get my phone working again? Will a simple restore using HTC software do the trick (followed by root with unrevoked)?
Thanks

CoreOxide said:
Heya,
I was using the LeeDroid ROM until today, when I desided I want Cyanogen.
I backed up the phone using ROM Manager, wipe and flashed Cyanogem 6.1 RC2. The phone restarted, turned on - but it cn't load the actual android OS - just keeps restarting on the blue wheel-thing animation.
I can boot my phone into recovery, but can't do much from there since its S-ON.
The recovery windows says:
bravo pvt1 ship s-on
hboot-0.80.0000
microp-031d
touch panel-synt0101
radio-5.10.05.23
fastboot
recovery
clear storage
simlock
what can I do to get my phone working again? Will a simple restore using HTC software do the trick (followed by root with unrevoked)?
Thanks
Click to expand...
Click to collapse
Which version of Clockworkmod recovery did you fakeflash? There is an issue with the latest one that makes your SDcard unaccessible afterwards. It also mess up your USB.
Here is a thread that guides you how to fix it: http://forum.xda-developers.com/showthread.php?t=691639

I used the latest one, 2.5.1.7 I think.
Isn't there a way to restore the phone with the HTC software, sonething lite the iphone+itunes combo?

Is your sd card not being recognzed?
As you said you created a backup using rom manager before you flashed the new rom. So why dont you just enter hboot, go to recovery and the restore youre phone to the backup that you made using rom mabager before you flashed?

When I select "recovery" using the HBOOT I get a picture of a phone, and a red triangle with an exclamation mark. Does this mean I have to do the USB brick fix?

hmmm thats odd ... sounds like it could be a usb brick related issue, im not sure as i havnt had the same problem before or seen anyone else in the forum experiencing this problem.
I think you should read up more about the usb brick fix, hopefully there is something there that would be able to help you ... if its already known that the latest version of clockworkmod does give this problem then im sure its this and you would be able to find a solution to this problem.
Good luck

UPDATE:
My bad, I was supposed to press volumeup+power to see the recovery screen.
Now, when I do that I get "E:Can't open /cache/recovery/command", and get only 4 options:
reboot system now
apply sdcard:update.zip
wipe date
wipe cache
Is this related to the USB BRICK thing?

You need to wipe data when switching roms, this will fix the bootloop.
I would also suggest you flash a permanent recovery for ease of use. You need to use unrevoked to do this.

CoreOxide said:
UPDATE:
My bad, I was supposed to press volumeup+power to see the recovery screen.
Now, when I do that I get "E:Can't open /cache/recovery/command", and get only 4 options:
reboot system now
apply sdcard:update.zip
wipe date
wipe cache
Is this related to the USB BRICK thing?
Click to expand...
Click to collapse
This is the default android recovery screen. The error "E:Cant open...." is something I also get.
Do you have an update.zip on your SDcard? Like the clockworkmod recovery? http://forum.xda-developers.com/showthread.php?t=839640Use 2.5.0.7 and not 2.5.1.2 (has the fail you most likely see now). If correct update.zip on SDcard, try to press apply sdcard. If youre able to do so, you are accessing your sdcard. If youre getting problems applying this update file. I suggest following the thread I told you in my first post You then have to make your SDcard accessible with a fastboot command.
You are accessing fastboot by holding vol down while powering your phone on. Select fastboot. Plug your USB. Download the Android SDK or only fastboot.exe. Run this command from cmd: "fastboot oem enableqxdm 0". You should get a return command like "okay", and your SD card should be accessible again. Now you will need to follow the guide and fix your USB. However, you should be able to flash a new ROM now when your SDcard is accessible again, or just restore the nandroid backup that gave you this problem to begin with
Update: post #30, weee!

jmelhus said:
This is the default android recovery screen. The error "E:Cant open...." is something I also get.
Do you have an update.zip on your SDcard? If so try to press apply sdcard. If youre able to do so, you are accessing your sdcard. If youre getting problems applying this update file. I suggest following the thread I told you in my first post You then have to make your SDcard accessible with a fastboot command.
Click to expand...
Click to collapse
When i select that I get "E; failed to open sdcard\update.zip (no such file or directory)
E: signature verification failed"
Does this simply mean I don't have that file on my card?
If so, is there a way to access the card in mass storage mode while the phone is in HBOOT?

CoreOxide said:
When i select that I get "E; failed to open sdcard\update.zip (no such file or directory)
E: signature verification failed"
Does this simply mean I don't have that file on my card?
If so, is there a way to access the card in mass storage mode while the phone is in HBOOT?
Click to expand...
Click to collapse
Do you have a mem reader for windows/linux? Look if you have the file or not. If you don't have it, copy it there. If it's there, you have a problem with accessing the SDCard.
I would say, If I were you, I would try to "repair" the SDcard with the fastboot command first. Most likely, your ROM will boot again when it can read from your SDcard.
Other options would be to try to push the update file with ADB in Android Recovery. Most likely you can't push it either since your SDcard most likely is inaccessible. Try fastboot
Download Android SDK for Windows here: http://dl.google.com/android/android-sdk_r07-windows.zip
MD5: 69c40c2d2e408b623156934f9ae574f0
Unzip the file. Open CMD, navigate to the tools folder in SDK. Issue the command.
Source: http://developer.android.com/sdk/index.html

I ran the SDcard fix on CMD, it said "OKAY", but nothing changed in the phone's condition.
I put the SDcard on a card reader and saw there are backup files (.img) in the clockworkmod directory. how do i get the phone to recover from them?
The "update.zip" file, where can i get that one?

CoreOxide said:
I ran the SDcard fix on CMD, it said "OKAY", but nothing changed in the phone's condition.
I put the SDcard on a card reader and saw there are backup files (.img) in the clockworkmod directory. how do i get the phone to recover from them?
The "update.zip" file, where can i get that one?
Click to expand...
Click to collapse
You can get your update.zip file from here: http://forum.xda-developers.com/showthread.php?t=839640
Download the 2.5.0.7 zip file and rename to update.zip. Put on root of SDcard and apply sdcard: update.zip in android recovery. From here, go to nandroid, restore, and select your backup.

Doesn't the Update.zip file suppose to be a zipped ROM?

Not necessarily. A zip can flash a lot of different things. I'm not that much into it. But it all depends on the content of the zip file.

How do I " go to nandroid"?

CoreOxide said:
How do I " go to nandroid"?
Click to expand...
Click to collapse
Don't remember what it's called exactly. But when running update.zip (clockworkmod), you should have a restore menu somewhere...

Thanks a lot man! recovering right now.. will update when done.
About that S-ON thing, will the Unrevoked reflash option "Remove phone security" take care of this? Is there a risk in re-rooting?
I want to add some notifications sounds and the "system" folder is write protected
EDIT:
The restore works just fine!

[Q] Stuck on S-Off Screen

Hi, i've been using LeeDroid for a few months now and all has been well, however yesterday my Desire turned itself off and now won't come back on. Each time i try and power it up it freezes at the Alpharev S-Off screen. I went into the menu's with volume down + power, but i can't get into my recovery - it takes me to the same frozen screen as does trying to reboot etc. And i don't think it's being recognized by usb either. So i really don't know what to do now.. is my phone bricked? I was a complete noob before rooting and flashing a custom rom before, so now that i've hit a problem i'm clueless all over again. Any help would be greatly appreciated

can you use fastboot? If so just flash a new recovery and all should be fine... chill out it can be fixed

What would i need for that? That's going into new territory

j3nni said:
What would i need for that? That's going into new territory
Click to expand...
Click to collapse
Can you access recovery? If no can you access bootloader (vol down + power on)

I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use

j3nni said:
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
Click to expand...
Click to collapse
Use amon_RA ... Download and flash onto ur phone and ur phone should be fixed
Plenty of guides around man, good way of learning fastboot

to use fastboot you need to download several things. Instead of using fastboot with cmd, I'd just recommend using fastboot commander, which does the job for you. In order to use that however, you will need the adb drivers, and Java SDK.
Once you've got all that, simply boot into fastboot, run "fastboot commander.exe", go into the "misc" tab, wipe Recovery, system, cache, boot, and userdata. Once you've done that download recovery, navigate to the "Hboot, radio & Rec" tab on fastboot commander, select recovery, find the recovery.img you just downloaded, and flash it. Once you've done that just boot into recovery and install any ROM you want.

Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again

j3nni said:
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
Click to expand...
Click to collapse
try do a full wipe of everything like I've mentioned before and then a different HBOOT

Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93

j3nni said:
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
Click to expand...
Click to collapse
www.alpharev.nl download a HBOOT and flash it through fastboot. Just make sure to check MD5 (you need a MD5 utility AFAIK)

I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!

j3nni said:
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
Click to expand...
Click to collapse
For any sense UI ROMs you would use the Sense HBOOT, remember to nandroid backup before you do so! because you might find that you get a bootloop after flashing the HBOOT.
And don't worry about asking questions! it's what we're all here for.
By the way if you don't know what different HBOOTs do: they change the partition sizes for /system /cache and /data. So by using a different HBOOT instead of the stock one you may get more storage for apps etc. if you choose one with a larger /data partition.... if that makes sense

Ok the sense one it is =)
Ah i see! Thanks for explaining cos underneath the nerd in me would have been wondering what it did lol.
Not sure how to get a nandroid done when i can't get into recovery though

I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further

j3nni said:
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
Click to expand...
Click to collapse
Hi.
As I can see the only way to restore is using a RUU to go back to stock then root and S-Off the phone again.
First: Preparation.
1. If you have a custom HBOOT (e.g.: 6.93.0001) you need first to flash the HBOOT Downgrader (found on alpharev site), then flash the RUU.
2. You will gonna need a Gold Card if your phone was branded.
Second: Starting
1. Make your Gold Card using someone's else phone (it has to be running Android) - the Gold Card is unique per SD Card, not per phone.
2. Use this tool to make the Gold Card: HERE
3. Guide how to make a Gold Card in Linux: HERE
4. get the latest RUU WWE 2.29.405.5. Extract the PB99IMG.zip file from the RUU: here it is how: http://forum.xda-developers.com/showthread.php?t=880268 -2nd post.
5. Reboot in bootloader (Volume-Down + Power)
7. Select fastboot
8. Flash the HBOOT Downgrader (don't forget to check the MD5 of the file you have downloaded from alpharev)
9. Extract the PB99IMG.zip and put it on root of SD Card.
10. Reboot in bootloader (scroll to REBOOT and select)
11. It will automatically load the img and ask you if you want to install
12. Check Yes and follow onscreen progress.
13. Wait untill it finnishes
14. I think it will reboot itself, if not scroll down to the Reboot obtion and press Power button to select.
IMPORTANT WARNING!!!
droidzone said:
Whatever you do, DO NOT turn off the device manually unless the software tells you to. If something goes wrong, dont switch off phone. Keep the phone on while trying a solution. Newer RUUs dont usually wreck a phone, and with a goldcard, you can always recover. But, the flash SHOULD NOT be interrupted by switching off or disconnecting the cable.
Always start with a battery with >50% power (full recommended).
Click to expand...
Click to collapse

Or if you want to go to stock and it is an unbranded phone you can just run ur ruu when the phone is in fastboot
Sent from my HTC Desire using XDA App

Think i may be the happiest girl in the world today lol i finally got it all fixed. I had a bit of trouble making the goldcard as at first my sd card kept saying it needed to be reformatted after, but after formatting it with SD Formatter program rather than Vista's own, it worked. All the rest went without a hitch. Now just gotta root, s-off and grab my new ROM and this past week can all get forgotten about =)
Thankyou so much to everyone that helped!
Incase anyone does read this far, is the procedure still the same as when i first used it back in April.. from here? http://forum.xda-developers.com/showthread.php?t=1016084

It is still the same.

If you like sense -
http://forum.xda-developers.com/showthread.php?t=1054435
░█░ [ROM][28/06] ✰.Reflex S v2.1.7 Gingerbread 2.3.3· ░█░ · |SenseGingerB 2.1+3.0|
You might like it...

[Q] another bricked phone thread; help needed

I've looked around for solutions as much as I could before posting
I've outlined everything I've done so far, not sure how much is relevant
Was running LeeDrOiD HD V3.3.1 before the phone became bricked
I rebooted the phone at one point, and the battery fell out during a reboot
Next time I rebooted it got to the ascii art android logo, onto a part with text on, and got stuck in a boot loop, the text had a progress part "so&so out of 2703kb" or something to that effect
(can't remember the text exactly)
After a few tries at rebooting it went to the home screen, however nothing loaded onto the home screen for 20 minutes, and the only function that worked was locking the screen, I couldn't turn it off or anything.
After this, everytime I booted it got stuck in a boot-loop on a splash screen of
"ANDROID" in silver writing
This is what I currently get when I boot my phone
When booted into recovery mode (hboot) I first get the message;
SD Checking...
Loading...[PC36DIAG.zip]
No image!
Loading...[PC36DIAG.nbh]
No image or wrong image!
Loading...[PC36IMG.zip]
No image!
Loading...[PC36.IMG.nbh]
No image or wrong image!
Click to expand...
Click to collapse
After I get this message I am free to go into fastboot and recovery menu
The PC recognises the phone in fastboot (I'm running windows 7)
I tried reflashing the leedroid rom straight from the recovery menu, didn't affect anything at all.
Went on to reformat sd card entirely.
Tried updating to the latest ruu, as there was no ruu that was exactly the same as mine, my phone was originally on virgin mobile and there were no ruu's with the same baseband
RUU used; RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
But the update fails part way through (after it reboots the phone) and gives
ERROR 131: CID ERROR
Rom update utility cannot update your phone at this time
Please get the correct rom update utility and try again
Click to expand...
Click to collapse
Current information that hboot gives me;
Bravo PVT1 SHIP S-ON
HBOOT-0.80.0000
TOUCH PANEL-SYNT0101
RADIO-5.11.05.14
Click to expand...
Click to collapse
Can anyone help?

if you can go into recovery, try reflash the zip file again and let it do its job. your hboot is not screwed so it shall restart with a new flash. recommending you download oxygen and save it on your sdcard. due to its fastest to load and most stable.

Just FYI: bootloop is not any kind of brick, and you're not bricked either.
Just do full wipe and reflash the ROM.
If you want to go back stock, you will need goldcard when running RUU.
SD Checking...
Loading...[PC36DIAG.zip]
No image!
Loading...[PC36DIAG.nbh]
No image or wrong image!
Loading...[PC36IMG.zip]
No image!
Loading...[PC36.IMG.nbh]
No image or wrong image!
Click to expand...
Click to collapse
Everyone is getting this upon entering bootloader...

Flashed oxygen, rebooted, left for 5 minutes
I'm still stuck in a boot loop, however the 'ANDROID' text splashscreen is now the 'OXYGEN' splashscreen

Did you do Full Wipe/Factory reset & dalvik cache wipe before flashing new ROM?
Do you have any partitions on SD card?

k3lcior said:
Did you do Full Wipe/Factory reset & dalvik cache wipe before flashing new ROM?
Do you have any partitions on SD card?
Click to expand...
Click to collapse
I wiped both
Yes, I partitioned it as instructed in the stickied noob guide
4GB partioned to 1GB of Ext3, the rest is FAT32. The partition is still there.

Probably something went wrong when you was creating ext partition, what i suggest is downloading this recovery:
http://forum.xda-developers.com/attachment.php?attachmentid=661317&stc=1&d=1311251519 (md5sum zip: 170785457774834c7ae58e331d6f4ab4)
Put it onto your sdcard (root of SD, not in any folders), rename it to "PB99IMG.zip" and boot into bootloader.
It should ask if you want to update, choose yes.
Partition your SD in new recovery, it will also perfectly align it, try to flash with this should be good.

k3lcior said:
Probably something went wrong when you was creating ext partition, what i suggest is downloading this recovery:
http://forum.xda-developers.com/attachment.php?attachmentid=661317&stc=1&d=1311251519 (md5sum zip: 170785457774834c7ae58e331d6f4ab4)
Put it onto your sdcard (root of SD, not in any folders), rename it to "PB99IMG.zip" and boot into bootloader.
It should ask if you want to update, choose yes.
Partition your SD in new recovery, it will also perfectly align it, try to flash with this should be good.
Click to expand...
Click to collapse
Didn't ask if it wanted to update
Text said loading image, A progress bar automatically appeared on the right, after it was done loading, it said 'checking image' then just went straight back into the bootloader

Are you sure you renamed file to PB99IMG.zip ? You can also try to rename it to PB99IMG (without extension)

k3lcior said:
Are you sure you renamed file to PB99IMG.zip ? You can also try to rename it to PB99IMG (without extension)
Click to expand...
Click to collapse
Yep, just double checked and tried a few more times, redownloaded and tried again just to be sure.
When renamed without extension the phone didn't find it, renamed with .zip extension the phone seemed to recognise it, but stopped after saying "checking image"

If you are branded try to put in you gold card and then try...
btw.
What did you used to partition your SD card?

k3lcior said:
If you are branded try to put in you gold card and then try...
btw.
What did you used to partition your SD card?
Click to expand...
Click to collapse
I'm just trying to create a gold card now (didn't know about them until after I flashed)
I used Gparted

You can also try to repartition in the recovery you have right now, might help who knows.

I'm crossing my fingers for the repartitioning from current recovery mode to work
because I'm not entirely sure on how to create a goldcard without being able to boot my phone normally
*edit*
Yes, that did indeed work
seems the file structure got fudged up when the battery fell out for a reboot
such a simple solution that I overlooked at the beginning sorry
Thanks for all your help

Create goldcard and bring your phone back to stock with the ruu you already wanted to use. With three goldcard you won't get the cid error.
Run unrevoked again, but this time you use a custom recovery:
http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
I can highly recommend rmd recovery:
http://forum.xda-developers.com/showthread.php?t=1137763
Download the zip, extract it and check the md5 of the image.
Standard amonra recovery:
www.android-hilfe.de/attachments/ro...-0-0-14-11-2010-recovery-ra-desire-v2.0.1.zip
Configure your phone correctly for using unrevoked.
Start unrevoked>file>custom recovery>choose the downloaded recovery image.
Run unrevoked.
If successfully done, go into recovery and flash custom rom.
The one k3lcior provided cannot be used as long as one is not s-on. So you cannot use it.
@k3lcior: Take care of this when you tell people to flash this recovery.
Swyped from Oxygen with Transparent XDA App

Change the room

Hey guys. I just wanted to tell u that am in Cyangonen room and my cell phone is already s-off and I did the partion to internal memory for Cm r2 but I want to try another room which is muiu room. But I can't flash it through recovery. Is it because of the partion? If yes; how can I flash it again?
Sent from my HTC Desire using Tapatalk

Why you cant flash it, any error?

Make sure you configured your sd card corresponding to the miui version you flash.

when using the cm7 hboot you need to flash the market cache fix after you flash the ROM.. and if you're unable to flash it through recovery I'd try turning off signature verification (in advanced settings).
If I were you I'd use the Data++ hboot for MIUI though.. worked better for me on that. And always remember to check the MD5Sums when flashing hboots, as a corrupted file can brick your phone.
MatDrOiD said:
Make sure you configured your sd card corresponding to the miui version you flash.
Click to expand...
Click to collapse
and +1 to that, you need an EXT partition, you can use gparted or minitool partition wizard. I'd recommend EXT4 since it's meant to give better performance, but cation: not all ROM's support EXT4

k3lcior said:
Why you cant flash it, any error?
Click to expand...
Click to collapse
don't know really. it takes a long time ( more than 30 min). so i removed the battery for 5 min. and i wipe data and everything else than I went back to CM room
and it works fine for me

MatDrOiD said:
Make sure you configured your sd card corresponding to the miui version you flash.
Click to expand...
Click to collapse
mine is ext 3 and when i looked up in their website they said they support ext 3
but it's not working.

bortak said:
when using the cm7 hboot you need to flash the market cache fix after you flash the ROM.. and if you're unable to flash it through recovery I'd try turning off signature verification (in advanced settings).
If I were you I'd use the Data++ hboot for MIUI though.. worked better for me on that. And always remember to check the MD5Sums when flashing hboots, as a corrupted file can brick your phone.
Click to expand...
Click to collapse
Thank you so much sir.
But i used the CM R2 partion, can i use the data++ partion on the it from flashing it through recovery?
if yes how?
because I was thinking to make the phone s-on again and use the room then i'll make it s-off again and do the partion thing?
Do u think this will work??
Thanks you again

If you have 1 EXT partition make sure you are flashing A2SD version.
Also full wipe/factory reset & dalvik wipe prior to flashing new ROM.

bundy1 said:
Thank you so much sir.
because I was thinking to make the phone s-on again and use the room then i'll make it s-off again and do the partion thing?
Click to expand...
Click to collapse
you don't need to go S-ON and then back to S-OFF to change the hboot..
visit www.alpharev.nl and flash it through FASTBOOT NOT recovery
and again, remember to check the MD5 with the tool I gave you!!!

bortak said:
you don't need to go S-ON and then back to S-OFF to change the hboot..
and flash it through FASTBOOT NOT recovery
and again, remember to check the MD5 with the tool I gave you!!!
Click to expand...
Click to collapse
how can i flash it through the fastboot?!!! i only know how to do it through the recovery?
Thanks dude

you can either do it with cmd or you can use fastboot commander to do it, fastboot commander would be easier as it has a GUI that is easy to work with, however it requires Java JDK and Android SDK. It's use is pretty self explanatory, so you should understand how to use it pretty easily.
If you would like to do it through cmd (also requires android sdk.. or at least fastboot.exe) then put your downloaded hboot.img into c:\ and type:
Code:
cd c:\android-sdk/tools
fastboot flash hboot c:\bravo_alphaspl-data.img
fasboot reboot bootloader
fastboot erase cache
fastboot reboot
"bravo_alphaspl-data" is the name of the hboot, that will obviously change if you want to flash a different hboot
Also, the fact that it's not installing *might* somehow be a recovery problem... I'd replace it just in case lol (I'd recommend the one from my signature), download it and put it in c:\
Code:
cd c:\android-sdk/tools
fastboot erase recovery
fastboot flash recovery c:\recovery-RA-desire-v2.0.0.img
Note: if you downloaded the CM "themed" recovery then it will be called "recovery-RA-desire-v2.0.0-CM.img" instead.

Replace framework-res.apk > Bootloop. Help!

Hi all!
I using root explorer to replace framework-res.apk
But now, my HTC Desire Z have a bootloop. I try to factory reset, wipe cache date, using update.zip but not not effective.
When I up rom in recovery (3e), the system show: E:signature verification failed
Help me fix the bootloop. Thanks!

well first off I hope you made a nandroid backup of your ROM before you did this. If so, just pull the battery, boot straight into recovery, and restore that nandroid backup.
Where did you get this framework-res.apk? did you edit it yourself? if so, what did you change? If you or someone else has changed anything decently major, the .apk needs to be re-signed. Looks like it wasn't.

Everybody help me!
I can't solve this problem

minhquang_ns said:
Everybody help me!
I can't solve this problem
Click to expand...
Click to collapse
Where did the framework-res.apk you are using to replace the stock on come from?
Or is the issue now just trying to get your phone booting again?

cjward23 said:
Where did the framework-res.apk you are using to replace the stock on come from?
Or is the issue now just trying to get your phone booting again?
Click to expand...
Click to collapse
I get framework-res.apk in Uot kitchen > Show all pickup file
I get one in this and replace. I didn't think about consequences

minhquang_ns said:
I get framework-res.apk in Uot kitchen > Show all pickup file
I get one in this and replace. I didn't think about consequences
Click to expand...
Click to collapse
Like I said in my first post that you didn't respond to, did you make a nandroid backup? If you didn't, you should at least have the stock framework-res.apk set aside to go back to? If you don't, and you can boot directly into recovery, then you're going to have to re-flash a fresh ROM in order to break the issues you caused with your current problem.
So if your phone is still bootlooping and you don't have a backup to go to, then follow the normal steps to flash a new ROM from recovery (this will probably be your only option if you don't have a backup):
1) download your ROM of choice
2) enter recovery, mount as USB storage
3) place ROM.zip on root of your SD card
4) install zip from SDcard > select ROM.zip
5) reboot
you'll probably lose your data, unless you flash the exact same ROM as you had before, there may be a chance that it won't.
Here's a lesson to be learned! Backup before messing with major things, and save the old framework-res.apk. And don't just willy-nilly flash random Uot Kitchen framework-res.apk's without precautions. It looks like you just got a framework-res.apk that wasn't signed properly and it messed your ROM up.

martonikaj said:
Like I said in my first post that you didn't respond to, did you make a nandroid backup? If you didn't, you should at least have the stock framework-res.apk set aside to go back to? If you don't, and you can boot directly into recovery, then you're going to have to re-flash a fresh ROM in order to break the issues you caused with your current problem.
So if your phone is still bootlooping and you don't have a backup to go to, then follow the normal steps to flash a new ROM from recovery (this will probably be your only option if you don't have a backup):
1) download your ROM of choice
2) enter recovery, mount as USB storage
3) place ROM.zip on root of your SD card
4) install zip from SDcard > select ROM.zip
5) reboot
you'll probably lose your data, unless you flash the exact same ROM as you had before, there may be a chance that it won't.
Here's a lesson to be learned! Backup before messing with major things, and save the old framework-res.apk. And don't just willy-nilly flash random Uot Kitchen framework-res.apk's without precautions. It looks like you just got a framework-res.apk that wasn't signed properly and it messed your ROM up.
Click to expand...
Click to collapse
Thank you, but I don't have clockmod recovery
When I using Recovery 3e (default), I choose "update.zip"
I try many roms but the system warning:
E: signature verification failed
FAILED TO VERIFY WHOLE-FILE SIGNATURE
Installation aborted.
Click to expand...
Click to collapse

.
minhquang_ns said:
Thank you, but I don't have clockmod recovery
When I using Recovery 3e (default), I choose "update.zip"
I try many roms but the system warning:
Click to expand...
Click to collapse
How can you not have cwm, there isn't another custom recovery for the DZ that I'm aware of.
Hang on, do you still have the stock recovery? OK so I'm going to assume you are actually rooted. Do you nave the eng hboot installed?
Do Androids dream of electric sheep?

cjward23 said:
.
How can you not have cwm, there isn't another custom recovery for the DZ that I'm aware of.
Hang on, do you still have the stock recovery? OK so I'm going to assume you are actually rooted. Do you nave the eng hboot installed?
Do Androids dream of electric sheep?
Click to expand...
Click to collapse
I have HBOOT 0.85.009. How to flash a new rom with out clockmod

minhquang_ns said:
I have HBOOT 0.85.009. How to flash a new rom with out clockmod
Click to expand...
Click to collapse
You can't, you will need to install cwm.
Download rom manager, then select install clockworkmod recovery. Then boot your phone in to recovery and preform a wipe then flash custom rom.
Do you have s-off?
Do Androids dream of electric sheep?

cjward23 said:
You can't, you will need to install cwm.
Download rom manager, then select install clockworkmod recovery. Then boot your phone in to recovery and preform a wipe then flash custom rom.
Do you have s-off?
Do Androids dream of electric sheep?
Click to expand...
Click to collapse
I have a boot loop, my Desire Z stopped in "HTC quietly brilliant" so I can't install cwm. I has been rooted phone.

minhquang_ns said:
I have a boot loop, my Desire Z stopped in "HTC quietly brilliant" so I can't install cwm. I has been rooted phone.
Click to expand...
Click to collapse
Ohh yeah, I forgot that. OK you will need to install recovery using fastboot. But to do that you will need to install the eng hboot. To do that please follow the instructions here http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html. But when you get to point 10 you will need to pull your battery out. And delete the PC10IMG.zip of your sd card.
Then reboot back in to bootloader and if all has gone well we will know have the DZ eng hboot installed.
The top line should now say vision eng s-off
You will then need to execute fastboot commands to install cwm. If you do not have fastboot installed download fastboot.exe from here http://developer.htc.com/adp.html and place in your platform-tools folder. You will is need the cwm recovery.img which you can get from here http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.2.4-vision.img and rename to recovery.img and place in your platform-tools folder
Open a cmd window and point it towards your platform-tools folder. Then we want to check fastboot is working, so make sure your phone is in bootloader and type fastboot devices and it should bring up your device serial number. Assuming that works type fastboot flash recovery recovery.img
All being well the recovery will flash then you will be able to boot in to recovery and flash a rom.
If you have any problems or are unsure about anything head over to the #G2ROOT irc http://webchat.freenode.net/
Do Androids dream of electric sheep?

cjward23 said:
Ohh yeah, I forgot that. OK you will need to install recovery using fastboot. But to do that you will need to install the eng hboot. To do that please follow the instructions here http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html. But when you get to point 10 you will need to pull your battery out. And delete the PC10IMG.zip of your sd card.
Then reboot back in to bootloader and if all has gone well we will know have the DZ eng hboot installed.
The top line should now say vision eng s-off
You will then need to execute fastboot commands to install cwm. If you do not have fastboot installed download fastboot.exe from here http://developer.htc.com/adp.html and place in your platform-tools folder. You will is need the cwm recovery.img which you can get from here http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.2.4-vision.img and rename to recovery.img and place in your platform-tools folder
Open a cmd window and point it towards your platform-tools folder. Then we want to check fastboot is working, so make sure your phone is in bootloader and type fastboot devices and it should bring up your device serial number. Assuming that works type fastboot flash recovery recovery.img
All being well the recovery will flash then you will be able to boot in to recovery and flash a rom.
If you have any problems or are unsure about anything head over to the #G2ROOT irc http://webchat.freenode.net/
Do Androids dream of electric sheep?
Click to expand...
Click to collapse
When I using fastboot recovery, cmd warning:
writing ‘recovery’… FAILED (remote: not allowed)
Click to expand...
Click to collapse
Similar, I type adb shell the system wanring:
error:devices not found
Click to expand...
Click to collapse