Hey there,
I wanted to S-OFF my HTC Desire using alpharev.
Unfortunately I didnt read that this wont work when you were on a GingerBread Rom Which I was ....(GingerVillain).
I'm stuck in HBOOT now (0.80.0000)
Recovery Mode doesn't work either (red exclamation mark)
Tried several RUUs always got Error 131 wrong user-id
Unbranded my Desire with a Goldcard a year or 1.5 years ago. ( Was on Vodafone Germany before)
Anyone got an Idea how to solve this problem?
Cheers
Tried flashing a new recovery image using android-sdk and fastboot.
But then I get this error :
D:\android\tools>fastboot flash recovery b.img
sending 'recovery' (3398 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
probably because my desire is S-ON
?
problem solved !!!!
found my old gold card, and guess what RUU update worked with goldcard inserted
Related
hey guys,
tried everything in my knowledge to try root my desire, going through tutorials on this forum and other forums but seem to get stuck in the same place,
when using the r4 or r5 root method on the step2 part where you try push the files to the phone itself , it cannot find the device
'error: device not found'
ive tried rectifying this by making sure usb debuggings on,
my desire is t-mobile branded so ive been using a goldcard, first of al used the gold card generator thanks to klutsh then when i thought that was the problem i tried making my own with the help of the guide on this forum,
,
just seem stuck in a rut at the moment ,
if some one could shed some light spent houses yesterday trying to figure it out
BTW ive used the windows and tinycore methods
my radio is 4.05.00.11
t mobile uk
on 0.75 base and 1.15 rom
You need a gold card, make sure the one u made works! Even try making it again, i was getting the exact same error on my unbranded desire, i tried lyk 10 times, i made a goldcard and was rooted 5 mins later
yeah tried 2 different ways going to try my wifes sd card when shes back also going to try linux
think win xp sp3 has issues connecting to the phone so.....
ill see how linux goes
Maybe its somthing diffrent mate but until i made my goldcard adb was giving me the exact same device nt found error! Can you use fake flash without root? Maybe just try flashing, rootedupdate.zip from recovery?
not tried using fake flash , tried with a different sd and its the same
think must be something to do with the gold card like you said,
what tutorial did you use?
sutty86 said:
not tried using fake flash , tried with a different sd and its the same
think must be something to do with the gold card like you said,
what tutorial did you use?
Click to expand...
Click to collapse
this is the tutorial i used to root my desire
http://nimbu.amorvi.com/2010/05/how-to-root-your-htc-desire/
Try the r6 method from Paul @ http://desire.modaco.com
Sent from my HTC Desire using Tapatalk
Hey sutty86 I had same problem.I tried rooting unbranded Desire with r6 method. I have windows 7 x64.No luck.Then I switched to Ubuntu x64 and right from start everything gone OK.It is probably windows x64 drivers problem.
I had this problem too on Win7 x86 but I installed HTC Sync and rebooted my computer and it worked like a charm.
Sent from my HTC Desire using Tapatalk
It's a driver issue. As suggested above, double-check the HTC Sync installation or use the Linux rooting method.
If you need to make a Gold Card, try using this tool:
http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
getting really annoyed now just reinstalled windows 7 again 32 bit,
tried again still getting error
About to start flash...
< waiting for device >
sending 'zip' (137446 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
sending 'zip' (137446 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys
and power button to select the RECOVERY option.
Click to expand...
Click to collapse
this is using r6 method and when i try to update it comes up with
failed to verify whole-file signature
sutty86 said:
getting really annoyed now just reinstalled windows 7 again 32 bit,
tried again still getting error
this is using r6 method and when i try to update it comes up with
failed to verify whole-file signature
Click to expand...
Click to collapse
if you look at the log, it keeps failing the cid check, its defo a prob with ur goldcard, try a diff sd card
try this tutorial http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
When making the GoldCard are you choosing physical or logical in the hex editor?
i used the tool and ive used the hex i belive its a problem with the brand of sd card sandisk, tried with two different sandisk and a unbraded 8gb one,
going to buy a kingston tomorrow hopefully that will help
Hello,
I am reading for hours and lost the overview...
My Desire had CM7 installed and had many reboots lately (maby caused by juice defender or the dalvic cache on the ext) but now it just wont boot at all. Not even into recovery.
Bootloader and Fastboot work but I cant flash anything or boot a recovery
S-ON
HBOOt-0.93.0001
RADIO-5.11.05.27
Code:
fastboot flash recovery recovery-clockwork-2.5.1.3-z71.img
sending 'recovery' (3742 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Code:
fastboot boot recovery-clockwork-2.5.1.3-z71.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
I am using a Mac but could also use a Win7 or Ubuntu maschine if this is necessary...
Please help
Ruu?
Sent from CM7
Is the custom recovery flash failing because the phone is s-on?
If so would it help to run alpharev on it?
Not sure, just a thought!
From what I understood you need to be able to boot to use alpharev or RUU?
I started the RUU .exe and stole the ROM.zip from TEMP but either the CID is not correct (I have VODAP102) or the version is older since CM7 is 2.3.3 I guess.
00droid said:
Is the custom recovery flash failing because the phone is s-on?
Click to expand...
Click to collapse
I guess so. Isn't S-OFF the thing you need to flash custom roms? I had it rooted and installed the recovery with clockwork or so from within OS without changing S-ON.
I got a UK VODA RUU to start at least (SD inside, sim not) but fails with ERROR[170] USB-Connoction Error
Afterwards it booted magically, I could backup data, flash LeeDroid to (what I thought) would solve the instability problem but it crashed again (connected cable is not good). And now its the same all over again but this time I cannot reproduce the luck from the first time.
Should I keep trying and then S-OFF, dwongrade bootloader and upgrade radio? What else could I do.
But I dont think the attepted flashing will work again...
magreet said:
From what I understood you need to be able to boot to use alpharev or RUU?
I started the RUU .exe and stole the ROM.zip from TEMP but either the CID is not correct (I have VODAP102) or the version is older since CM7 is 2.3.3 I guess.
Click to expand...
Click to collapse
Hmm, I think you're right actually, it's been a while since s-off for me!
S-OFF is indeed needed to flash the custom recovery via fastboot.
RUU - so probably you need a branded RUU for your phone (VODA-Germany VODAP102).
Or do the above mentioned method - take the ROM.zip and put it on your SD Card, but RENAME it to PB99IMG.zip.
Since you are branded, you need to create a goldcard, to avoid CID error:
Here's how
The phone needs to boot to create a GoldCard Luckily this happens from time to time.
But since 2.3.3 is newer than the newest 2.2 RUU the GoldCard CID fix wont work in my oppinion...
Even I am struck with the same issue. Only fastboot access with an Orange desire. I do not have a gold card to try out anything.
My phone's CID: ORANG001
Bootloader throws up the following error:
Loading...[PB99DIAG.zip]
No image!
Loading...[PB99DIAG.nbh]
No image or wrong image!
Loading...[PB99IMG.zip]
No image!
Loading...[PB99IMG.nbh]
No image or wrong image!
Any suggestions?
Could you flash a RUU from within Windows? I tried many, at least one of them tried to start and failed but the phone started at least. If a boot loop occurs remove the battery and retry as long as it takes. Worked for me.
Maybe without sim.
Some people reported being able to boot WITHOUT sd in the phone. Try it.
Hi Guys,
I have searched everywhere about this with no luck so have been forced to start a new thread...
I am running amon-ra v2.0.0 on my S-ON Desire.
I flashed the latest CWM that rom manager provides and it works... then i flashed this: http://forum.xda-developers.com/showthread.php?t=1039954
Cool, it worked. But when i reboot it goes back to amon-ra????
I am thoroughly confused..
any suggestions?
Did you use fastboot?
Flashing the .zip is only temporary, to permanently flash recovery you have to use fastboot to flash recovery-clockwork-3.0.2.8-bravo.img
http://forum.xda-developers.com/showthread.php?t=1039954&page=15
has some details.
Hi sorry, i should have mentioned that when i tried 'fastboot flash recovery recovery-clockwork-3.0.2.8-bravo.img' i got the following error...
sending 'recovery' (3036 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
you need to be S-OFF in order to flash recovery through fastboot (S-OFF disables signature checking in fastboot)
if you dont want to go s-off (it is easy, seriously) you can unroot, then while rooting again choose AmonRA in unrevoked.
Hi everyone,
I've rooted my Wildfire and now it has 0.80.0007 bootloader with cyanogen 7.0.0 ROM. I'd like to flash my kernel but it says:
$./fastboot flash boot boot.img
sending 'boot' (2816 KB)... OKAY
writing 'boot'... FAILED (remote: not allowed)
I've also tried to flash zimage:
$./fastboot flash zimage zImage
sending 'zimage' (2414 KB)... OKAY
writing 'zimage'... FAILED (remote: not allowed)
I've read that this can be beacuse I have a locked bootloader but others on the forum have successfully flashed it. Do I have to upgrade HBOOT to 1.01.0001?
Please help
VandorTsab
Don't even think of upgrading to HBoot 1.01. This is unrootable and you will lose even the basic ability to install Custom ROMs like Cyanogenmod.
What you are trying to do requires S-OFF. Most probably, your device is still S-ON. S-OFF can be achieved using an XTC Clip (Which, incidentally works on HBoot 1.01), which is why there are others who can do it. AlphaRev 2.0, when it will be released, will also allow S-OFF on Wildfires with HBoot 0.80 which is already pre rooted.
Thank You for your answer.
The boot loader says it is S-OFF.
What else could it be?
When I start the command that I've written above, a green progressbar appears on the upper right corner on my wildfire and than it dissappears. Then ubuntu says the errors I've mentiond above.
VandorTsab
There are a couple of solutions here:
http://forum.xda-developers.com/showthread.php?t=731657
Since I personally use an S-ON phone, not very familiar with these commands.
I've been trying to flash CM7.2 and every other rom to no avail. I've tried going back to stock rom 2.3.3 and 2.3.4 but they won't flash either.
C:\Android>fastboot flash recover recovery_signed.img
sending 'recover' (3746 KB)... OKAY [ 1.144s]
writing 'recover'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.613s
Click to expand...
Click to collapse
Backlog:
1. I started with a stock droid incredible phone.
2. I followed a tutorial to "Root Your Droid Incredible 2 VIA HTC Bootloader Unlock"
3. I wiped everything and tried installing Cyanogenmod 7.2 but it get's stuck on the HTC boot screen
4. I thought I could just install new ROMs after installing CWM and getting root. But now, I read somewhere I need to have S-OFF. I'm S-ON.
Also, no nandroid backup prior to wiping
pco052 said:
I need your help.
Here's my situation:
1. I started with a stock droid incredible phone.
2. I followed a tutorial to "Root Your Droid Incredible 2 VIA HTC Bootloader Unlock"
3. I wiped everything and tried installing Cyanogenmod 7.2 but it get's stuck on the HTC boot screen
4. I thought I could just install new ROMs after installing CWM and getting root. But now, I read somewhere I need to have S-OFF. I'm S-ON.
How do I proceed now? I no longer have access to the stock ROM because I did not do an nandroid backup prior to wiping.
Please help, might battery might soon be dead with no options of charging it.
Click to expand...
Click to collapse
edit:
I tried returning into stock following this thread: http://forum.xda-developers.com/showthread.php?t=1599767
1.a Downloaded "RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si"
1.b renamed it to PG32IMG.zip
2. I go to the bootloader, it loads the PG32IMG.zip
3. But I don't get this menu afterwards: https://www.youtube.com/watch?v=qvZAHc-LAr4&t=114s
The loading bar disappears, It just goes back to the bootloader with no noticeable difference.
Guys, how do I flash the RUU?
I've tried renaming it to PG32IMG.zip, but it throws an error stating "wrong zipped image" or something of that sort.
I've tried flashing it through flashboot:
C:\Android>fastboot flash recover recovery_signed.img
sending 'recover' (3746 KB)... OKAY [ 1.144s]
writing 'recover'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.613s
Click to expand...
Click to collapse
Both don't work for me, any ideas?
You would be better off getting s-off. Less of a pita.
You gotta pull the kernel and flash it in hboot seperately, you probably missed this step which is why nothing is working. I'm not completely familiar with the process because I am soff but you should be able to find it on here
Sent from my Incredible 2 using xda app-developers app