Related
Hi all, long time lurker, first time poster!
I've just installed the InsertCoin v20 on my S-OFF, CM7 Hboot HTC desire, and it has been stuck on the htc screen for ages now.
I've reflashed it many times, including the radio (32.44.00.32U_5.09.05.30_2), the recovery (clockwork v3), and the rom. nothing seems to be working.
I have a feeling it might have been the bootscreen I flashed - I flashed the original HTC boot screen from alpharev website.
Does anybody have any ideas! I did a full wipe before flashing this rom (I came from Cyanogen 7)
8ball2253 said:
Hi all, long time lurker, first time poster!
I've just installed the InsertCoin v20 on my S-OFF, CM7 Hboot HTC desire, and it has been stuck on the htc screen for ages now.
I've reflashed it many times, including the radio (32.44.00.32U_5.09.05.30_2), the recovery (clockwork v3), and the rom. nothing seems to be working.
I have a feeling it might have been the bootscreen I flashed - I flashed the original HTC boot screen from alpharev website.
Does anybody have any ideas! I did a full wipe before flashing this rom (I came from Cyanogen 7)
Click to expand...
Click to collapse
Does the rom fit the cm7 partition table? If it's too big then the phone won't boot, though Iffr think recovery should still work in that scenario.
Also check the md5sum of the boot image file - search on Google for a free tool for doing this.
Are you able to boot to bootloader?
stringer7 said:
Does the rom fit the cm7 partition table? If it's too big then the phone won't boot, though Iffr think recovery should still work in that scenario.
Also check the md5sum of the boot image file - search on Google for a free tool for doing this.
Are you able to boot to bootloader?
Click to expand...
Click to collapse
Insertcoin should work on CM7 hboot, so they say, so it's some other problem he's experiencing I guess. Maybe he forgot to make an ext partition on the SD card...
CSharpe you hit the nail on the head...I completely forgot to make the ext3 partition on my SD card. It was driving me mad last night, I only wish you had told me sooner, I was up until 6am sorting it out!
Thank you!
Hi, I ran the AlphaRev s-off software,
When it rebooted my phone it got stuck in a boot loop.
My phone now no longer boots so i cant restore it to stock or try and s-off again.
Ive reflashed the rom i started with (RCMix S 2.0) and i tried leedroid as well but it still bootloops.
Os there anyway i can replace the HBoot with stock without the phone being booted up as im guessing that is what is corrupted. fastboot maybe?
I really hope my phone isn't bricked.
Thanks
did the splash screen changed ? do you see the Joker with Why So Serious and so on.... ???
do you have 1 GB EXT partition AFTER fat32 ???
the alpha rev procedure didnt finish, as one of the steps it boots into hboot or similar and then restarts the phone. at this point it got stuck in a bootloop showing the splash screen from the rom i had on b4. my SD card is formatted with 1gb ext3 after my fat 32.
I think its fixed. I copied PB99IMG_stock onto my phone from http://alpharev.nl/ and renamed it. i then reflashed a rom and it booted
Im gonna flash the standard RUU for my carrier and then try again.
i think i know what you did wrong.
you cant do S-OFF if running a A2SD+/data2ext/data2sd/data2whatever ROM
RcMiX S is an A2SD+ ROM....
so
you can either ran a RUU then ROOT and S-OFF while still on stock ROM.
or flash a stock rooted rom now, and S-OFF
if you cant S-OFF while on stock rooted rom, try with Oxygen ROM (some users report that Oxygen was the only way to S-OFF for them)
i flashed RUU_Bravo_HTC_WWE_1[1].21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed
then rooted using unrevoked. so far so good. However im now stuck on the second step of alpharev again with my phone not booting.
alpharev says "Dozing off for about a minute while we wait", its been about 10 minutes.
Shall i try again with the oxygen rom?
Thanks
make sure you have Debugging Enabled in Android settings
and if that doesnt help then i guess try oxygen
yeh it was. im trying now
thanks
Firstly, I do apologise if this is a repeat question, so if you could redirect me to where the relavent information is, I'd be most grateful.
I am a newbie to all this flashing and hboots etc... but I would love to flash this rom as it would give me a taste of the gingerbread version as HTC seems to be taking ages to release the new version for the HTC Desire.
These are some specifications:-
Bravo PVT4 SHIP S-OFF
Boot 6.93.1002
Microp-051d
Touch Pannel-Synt0101
Radio - 5.17.05.23
I am currently running Froyo stock rom and my hboot was a stock hboot as well. (I think)
Having read your post, I decided to install the SGBS v1.7 rom to my phone. I may have mis-read or something, but I have failed misserably and would be most grateful if you could help.
I have tried to upgrade my hboot to cm7r2 using a dowload from the AlphaRev site, and flashed it using FastbootCommander. The flash goes through without a problem, and when I restart the phone in fastboot mode, the letters CM7 r2 have been added next to the name AlphaRev (in pink).
Following this, I erased all the memories, and installed the ROM in question. Upon reset however the phone hangs at the splash screen. Have I done something wrong?
I have also tried the Data++ ROM and this gets installed (with a stock hboot only) however it comes to a place where it says "Please wait loading...." and after about 15 mins, force closes.
From a recently made recovery backup, System - 250MB, Data - 56.5MB, cache 2MB. Is this the issue because AlphaRev states that hboot cm7r2 is System - 145MB, data - 287MB, cache 5M.
What would be your recommendation in order to install the sgbs rom.
Many thanks, your help is much appreciated.
Regards,
A.
Did you remember,go into recovery and turn off signatur verfication (till now its not signed)
First of all, hello to all forum members!
I had not been particularly active here in the forum,
but I read a lot here and build some knowledge.
so far I have solved all my problems due to browse and read.
But now I am facing a problem, where I need help.
I got a desire from a friend with wrong nexus one blackrose hboot.
I managed to install alpharev hboot on it, but its not booting the rom, neither the recovery.
I decided to get a ruu on it, to reflash boot, system, recovery, etc.
After i did:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <rom.zip>
the phone is stuck in fastboot RUU mode. No matter if I pull the battery and power on with vol-, vol+ or back, the fastboot RUU mode starts (Black screen with htc logo in the middle and 4 exclamation marks in the corners).
What Ive done so far:
Tried different RUUs(Europe, WWE) via fastboot. Most of them fail while writing radio image.
Tried to flash the radio image via fastboot. Most of them stuck while writing.
Asked a friend with exactly matching hardware to send me his working nand backup, his hboot is CM7 r2, so I flashed it
to match his nand backup.
I flashed his boot/recovery/system/cache and the latest radio, matching the nand backup.
The latest radio was flashed successfully.
The recovery in his nand backup was 4EXT Touch 1.0.0.3
So, after flashing boot, recovery, system, cache and even misc and userdata (AND erasing them prior on second try), the behaviour stays the same, the phone wont boot the rom or recovery and no matter what buttons I press on power on, it boots at fastboot RUU mode.
I tried
Code:
fastboot oem boot
, but that keeps stucking in the white htc splash1
If I plug in the usb cable and pull it out again, I see the hboot infos:
AlphaRev CM7 r2
BRAVO PVT1 SHIP S-OFF
HBOOT-6.92.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
<date>
RUU
After a lot of research, Ive found several opinions:
-its a brick (sure it is ;D)
-its a radio brick (ive sucessfully flashed the newest radio, so I doubt it)
Almost all users wo tried it hardly, and havent given up after the second try,
recovered their phone from this fastboot RUU mode.
I can run all fastboot extended commands, and flash RUUs over it.
So: what have I done wrong? Is there anything missing?
Can someone who knows what he says please take a look over it?
Thank you really much
criestr
After "a lot" of research you still haven't looked at my guide, well done.
Sure Ive looked at your guide,
I work with linux, and I hate flashing tools.
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
Click to expand...
Click to collapse
Is it any difference to use
Code:
fastboot flash hboot bravo_alphaspl.img
instead of using Android Flasher?
I dont think so, and Ive already done the steps in your guide, except using Android Flasher to flash the AlphaRev stock version.
Or is there another point in your guide that Im missing?
If so, then I am sorry for wasting your time.
I know, I am "new" here, so thats the standard answer for all newbs from you.
Thats ok. But Ive fixed a lot of phones without open even one thread, just with hours of research. But after google search for about 8 hours, several tries and following several guides and tips I didnt find an answer yet.
New update: Ive managed to push and boot the 4EXT Recovery image.
Fair enough, but the guide was meant to be made as easy to use as possible.
All you had to do was flash the stock hboot, or the downgrader, and then try a RUU.
The reason for it being stuck, is because alpharev hboots have write protection (meaning they won't be overwritten until you use the downgrader), and since you had the cm7r2 partition flashed, there was not enough space in /system for the stock ROM.
Hi again,
thanks for your answer.
I had the right stock hboot whilst flashing the RUU, so that wasnt the problem.
The RUU always failed to write the radio. A few hours ago i figured out that
the problem was because of a faulty battery. I changed the battery, loaded it
half an hour, and voila! the RUU was running quite fine.
The stock rom wasnt booting yet, but from then it was possible to go into the HBOOT/Fastboot, so it was making progress ;D
After another research I found out that my misc partition was screwed, maybe because the blackrose hboot, maybe because of the pre-owner.
Fixed the misc partition with cid, kernel commandlines & rom version.
After that I wiped cache and data, and did fastboot oem boot.
The rom was booting, but did random reboots/crashes after about 3-5 mins.
After 3 or 4 reboots the phone is now stuck at htc splash1, and isnt booting anymore.
For now I will try to flash the nand backup again, see if that works out.
Anyone has an better idea?
Thanks alot
criestr
New update:
The phone switched randomly between bootable and non-bootable bootloop/stuck in splash1.
I tried different radios, different boot & system.img from RUUs.
I can flash a new recovery, tried 4 different ones, none of them is booting,
not over hboot->recovery and also not over
Code:
fastboot oem gencheckpt
.
The only thing that worked was to erase cache and immediatly do
Code:
fastboot boot recovery.img
,
so after the stock rom randomly reboots, I decided to install a custom rom for CM7 r2 hboot. So I flashed the CM7 r2 hboot again, erased cache, booted the recovery and flashed rom.
The rom was booting! But again, after fiddling with flashing a new recovery with 4EXT Updater, the rom rebooted into splash1 and stuck there.
After this first time, it has yet never rebooted again. So I twist my fingers that it was a custom rom bug on first boot.
Flashing the recovery via 4EXT Updater worked for me, despite of none of the recoverys flashed via fastboot had booted before.
Anyway, thanks for the help.
Hopefully it helps someone with the same problem,
but I doubt there are many people dumb enough to flash blackrose hboot on a desire
Cheers
criestr
I had a similar problem with my old Magic. I have Desire now but never had that problem. I hope not.
Anyways, the way I solved it was to flash the right radio.img. I supposed you can try to fastboot flash radio radio.img. Make sure you use the right radio.img. That is what I did if I recall correctly and it worked for me on Magic. I don't know if it is will work on Desire that way.
The other thing is when Ruu failed at radio, I think it is because the lower version of radio.
I hope this helps.
Try it and let me know.
bortak said:
After "a lot" of research you still haven't looked at my guide, well done.
Click to expand...
Click to collapse
link please
Hi guys!
Today, I was messing with my Desire (S-OFF, rooted, stock android 2.3.3) and I had to do a factory reset (I went to settings and wiped all data (including SDcard))...
So after that, the phone DID work, but Superuser had constant crashes and I didn't have root (no matter how many times I flashed the su or su binary .zip).
And I decided to go with a custom ROM, so I put a NAND backup of Aurora v6 (sense 3.0 rom) into sdcard>clockworkmod>backup.
Tried that and it didn't work... I was stuck in a loop:
boot logo>boot animation>power off>repeat
So I took the battery out, went to recovery and mounted my SDcard to my PC and put the ROM's zip file onto it... Tried installing and it didn't work (again, the boot loop). I also tried with a different ROM (runnymede's sense 3.5), but the result was the same...
Does anyone know what I did to pi** my Desire off so much?
And how do I fix it?
I've been at it for hours now, but no matter what I do in recovery (or hboot or fastboot), nothing seems to work!
EDIT1: Downloading a stock RUU, hope this helps...
EDIT2: The stock RUU didn't work... Guess I'd have to have a working Desire for this...
EDIT3: I've noticed that the boot animation isn't HTC's anymore... It's text, saying 'android'... Now I'm really out of ideas...
EDIT4: I pressed the 'clear data' or something similar button in bootloader... Seems that caused the weird boot animation? Trying to flash ROMs now
A few questions first:
1. Which hboot do you have?
2. Which RUU did you use?
3. What error did you get using RUU?
4. Which method for RUU did you use (run from PC or PB99IMG.zip?
5. How you did partition your sd card and did you make sd-ext (all advance roms sense 3.0 and 3.5 require sd-ext)?
Do these ROMs require ext partitions. Check in ROM threads. If nothing works best to downgrade hboot and run ruu 2.3. Thereafter run revolutionary.
Sent from my HTC Desire
A few answers (only correct if RUU is sort of an android installer)
1.I have the stock hboot (unless I broke that somehow with all my button pressing...)
2.The RUU's name is RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed
3.Well, since I was only able to try in the bootloader and in the recovery (mount USB storage), both times the error was the same; the installer was unable to detect my Desire...
4.I don't quite understand that (I'm a noob when it comes to 'codenamed' thingies)... What I did was I just downloaded the .exe file and ran it
5.I've tried both with a completely blank SDcard and a partitioned one (256MB size, 0MB swap size)...
Just to point out though that the Aurora ROM didn't need a partitioned SDcard the first time I installed it (when my Desire wasn't in this weird state).
Thanks for your quick reply!
EDIT1:
@handy5876: Yes, they both recommend an ext3 or ext4 SDcard partition. But as said above, the Aurora v6 ROM worked just fine with no partition at all!
someone755 said:
A few answers (only correct if RUU is sort of an android installer)
1.I have the stock hboot (unless I broke that somehow with all my button pressing...)
2.The RUU's name is RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed
3.Well, since I was only able to try in the bootloader and in the recovery (mount USB storage), both times the error was the same; the installer was unable to detect my Desire...
4.I don't quite understand that (I'm a noob when it comes to 'codenamed' thingies)... What I did was I just downloaded the .exe file and ran it
5.I've tried both with a completely blank SDcard and a partitioned one (256MB size, 0MB swap size)...
Just to point out though that the Aurora ROM didn't need a partitioned SDcard the first time I installed it (when my Desire wasn't in this weird state).
Thanks for your quick reply!
Click to expand...
Click to collapse
Ok, if you mean stock hboot, which stock Alpharev or HTC? If you have HTC one continue reading. If not reboot phone with power and volume down and see what is written on the top of the screen.
Download 2.3 RUU you have a guide in my signature.
Run RUU from bootloader, not recovery just reboot phone with power-volume down and run it from white screen.
I tried with the Aurora ROM again... Now it's just stuck at the bootimage!
Time to listen to a pro
My Hboot doesn't say anything about alpharev... But nobody ever changed that, so it must be HTC, right?
So, the *almost* top of the screen should say 'HBOOT USB PLUG' while running the RUU...?
I already tried that with (I think) Android 2.2 but it didn't detect my phone...
Downloading the 2.3 RUU
someone755 said:
I tried with the Aurora ROM again... Now it's just stuck at the bootimage!
Time to listen to a pro
My Hboot doesn't say anything about alpharev... But nobody ever changed that, so it must be HTC, right?
So, the *almost* top of the screen should say 'HBOOT USB PLUG' while running the RUU...?
I already tried that with (I think) Android 2.2 but it didn't detect my phone...
Downloading the 2.3 RUU
Click to expand...
Click to collapse
Then you're ready to go with RUU, just run it from that screen.
Sorry for the slow response, I had to eat meh lunch (while the battery was charging)
I'm getting the 'LOW MAIN BATTERY POWER' error [120]... apparently the battery level is under 30%, even after a 1h charge...
Waiting some more for it to charge, and I have a feeling this 2.3.3 RUU thing just might fix meh problems
Lol the 2.3 upgrade has saved a good few phones this past week
Sent from my HTC Desire
jmcclue said:
Lol the 2.3 upgrade has saved a good few phones this past week
Click to expand...
Click to collapse
Yeah, tell me about it
This is the ultimate HTC Desire un-brick tutorial in this thread
Here is the explanation how all that works.
Okay, so my phone is still not working, as the RUU thinks its battery is under 30%, even though my Desire is fully charged up...
Is wiping battery stats a good idea?
@nlooooo: Thanks! Now I finally! have at least part of the idea how it all works
EDIT: The RUU thinks my battery is less than 30%, even though it has been charging since my last post (and the green LED confirms it's full).
Why?? I just wiped the battery stats, should I do anything else?
EDIT2: Switched from BOOTLOADER USB to FASTBOOT USB, it now seems to work...
As I understand, from here on I can restore NAND backups?
I'm only asking so I wont have to go through this all again -.-'
EDIT3: Just installed Revolutionary CWM (the easiest way to get CWM), flashed su zip... Superuser finally works and my su binary was auto-updated (after many months of manual updates)
Still, can I do NAND restores safely right now?
You'll have to s-off your device and the tool you need to use will flash recovery.
For s-off see this:
revolutionary.io
And read the guide given. Don't worry it will ask you for your IMEI when you start download it's just for the purpose of building your beta license key.
After you flash recovery I think you know what to do...
I already s-off'd the first day I got the thing seems like S-OFF never disappears...?
Just flashed CWM with revolutionary, too (I'll update later) and just flashed su zip.
But is it safe for me to restore NAND backups of other roms? Or must I first install the rom and then restore the NAND?
Now you are on stock hboot with data partition at 147 MB. If your NAND backup data partition is more than 147MB you will get into trouble.
How can my NAND backup partition be different than the one I have now (stock) if I've always had it...? This is sort of confusing... :S
someone755 said:
I already s-off'd the first day I got the thing seems like S-OFF never disappears...?
Just flashed CWM with revolutionary, too (I'll update later) and just flashed su zip.
But is it safe for me to restore NAND backups of other roms? Or must I first install the rom and then restore the NAND?
Click to expand...
Click to collapse
You can restore just backup you don't need to flash rom. But first try to boot with stock 2.3.
So RUU finished with no problems? Now I'm not sure which hboot you have cause if you s-off with revolutionary on the top of the screen pink revolutionary should be written, and it doesn't disappear because RUU can't overwrite custom flashed hboots (alpharev or revolutionary).
---------- Post added at 05:39 PM ---------- Previous post was at 05:35 PM ----------
handy5876 said:
Now you are on stock hboot with data partition at 147 MB. If your NAND backup data partition is more than 147MB you will get into trouble.
Click to expand...
Click to collapse
He was on stock before so no problems should occur.
I'd be much happier if you wrote that in your native language (Serbian), since I didn't get any of that... (and yes, I understand Serbian)
I think I have the stock hboot, but I never changed it, so what else could it be?
I S-OFF'd my Desire using Revolutionary, and no RUU, ROM flash or ZIP install could ever make it S-ON'd...
And on top of hboot there is a pink 'Recolutionary' sign...