Related
Please help!
My magic (32A) suddenly changed its hboot to S-ON!!
Info in fastboot mode:
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-6.35.10.18
Now I can't flash anything in fastboot, I have RA recovery v1.5.3.1.
But I can't mount the sdcard for updating the hboot again.
I have goldcard, but usb connection error show up while verifying the phone..
Can anyone has same issue?
Thank you
littlestrong said:
Please help!
My magic (32A) suddenly changed its hboot to S-ON!!
Info in fastboot mode:
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-6.35.10.18
Now I can't flash anything in fastboot, I have RA recovery v1.5.3.1.
But I can't mount the sdcard for updating the hboot again.
I have goldcard, but usb connection error show up while verifying the phone..
Can anyone has same issue?
Thank you
Click to expand...
Click to collapse
Damn, I hate members like you.
a) You don't even tell us what you did wrong
b) What does this have ANYTHING TO DO TO BELONG IN THE MAGIC DEVELOPMENT?
I am sorry that I did not mention the whole story.
Where should I post this message to? myTouch 3G, Magic General?
I am using "Super-Hero (Build By AhmgskMod)" before came into this situation, I found that the phone can boot, and looping in the htc Magic screen.
Show I tried to wipe and flash the rom again. I flashed the rom for 5-6 times, but it still won't boot..
At the last one I tried to flash another rom from XDA, I found the sdcard can't mount in recovery mode. And I go to fastboot mode, S-ON is observed.
I flash my phone with sappimg.zip in hboot mode (Sdcard file can be loaded). Now I am with the rom in (RUU_Sapphire_HTC_Europe_304401), but the sdcard is not mounted after I boot up my phone.
I believe that this issue is due to the S-ON hboot, I am finding some way to flash the hboot again (I tried -- fastboot NOT OK, recovery can't mount sd)
Seek for help. Thank you very much.
littlestrong said:
I am sorry that I did not mention the whole story.
Where should I post this message to? myTouch 3G, Magic General?
I am using "Super-Hero (Build By AhmgskMod)" before came into this situation, I found that the phone can boot, and looping in the htc Magic screen.
Show I tried to wipe and flash the rom again. I flashed the rom for 5-6 times, but it still won't boot..
At the last one I tried to flash another rom from XDA, I found the sdcard can't mount in recovery mode. And I go to fastboot mode, S-ON is observed.
I flash my phone with sappimg.zip in hboot mode (Sdcard file can be loaded). Now I am with the rom in (RUU_Sapphire_HTC_Europe_304401), but the sdcard is not mounted after I boot up my phone.
I believe that this issue is due to the S-ON hboot, I am finding some way to flash the hboot again (I tried -- fastboot NOT OK, recovery can't mount sd)
Seek for help. Thank you very much.
Click to expand...
Click to collapse
u still hav hero recovery??? ( custom recovery)
Yes, I have the hero recovery (custom), I flash in by boot the hero recovery in fastboot, and flash using:
adb push recovery.img /
adb shell flash_image recovery /recovery.img
The problem is I cannot access to sdcard in recovery mode, also can't use the sdcard when I boot up the phone.
Updated: I copy the rom.zip and rom1.zip from RUU update. The rom.zip container radio and hboot. Should I flash the rom.zip in hboot, to recovery the radio and hboot?
s-on + no sd card.
This problem seems to be experienced by many people in the process of upgrading to the new radio. I have experienced it myself and i never managed to solve it. Luckily i manafed to get a replacement phone. I am still afraid of upgrading the radio on my new device in fact. I think that this seems to be a common problem which deserves to be given more attention by the devs. I. Believe there were a couple of people on the forum who managed to fix it but they are few and far between.
fastboot oem enableqxdm 0
There's been quite a few SD card problem forum threads. Try harder next time.
xaueious, Thank you very much! Now I can access the sdcard! I will try harder to search in forum before asking question next time.
And thank you for the support of everyone in this post too.
This command was not recognized by the phone in my case. It's not always that simple to solve. It would be better to know what causes it in the first place so that people can avoid it.
xaueious said:
fastboot oem enableqxdm 0
There's been quite a few SD card problem forum threads. Try harder next time.
Click to expand...
Click to collapse
Now I can use the rom in (RUU_Sapphire_HTC_Europe_304401), I use hboot mode and flash the rom1.zip from the captioned rom (renamed to sappimg.zip)
But I can't start any custom rom for new radio from XDA here (installed in recovery mode, update from zip). It just stuck at the htc Magic screen, can't boot into phone.
My SPL/Hboot is still 1.76.2007 S-ON. I have tried flash the "update-hboot-1762007-signed.zip" in recovery mode, but the Hboot is still S-ON.
I believe the problem is due to the S-ON Hboot, so I can't start any custom rom. Any way I can turn the Hboot to S-OFF?
Thank you!
Update to Amon_RA's newest hero recovery. You should be able to mount your SD card in that.
Thank you sindrefyrn. I updated to the latest RA hero recovery.
I can mount sdcard with hero recovery 1.5.3.1 too.
But problem is I can't boot my phone with custom rom, only stock rom will work.
My ENG SPL 1.76.2007 is S-ON instead of S-OFF.
I will tried to flash the RUU update to replace my existing radio and SPL tomorrow, my home PC using win7 and can't verify my phone while RUU update, I will tried it tomorrow in office with winXP.
Hope it works, will report here.
littlestrong said:
Thank you sindrefyrn. I updated to the latest RA hero recovery.
I can mount sdcard with hero recovery 1.5.3.1 too.
But problem is I can't boot my phone with custom rom, only stock rom will work.
My ENG SPL 1.76.2007 is S-ON instead of S-OFF.
I will tried to flash the RUU update to replace my existing radio and SPL tomorrow, my home PC using win7 and can't verify my phone while RUU update, I will tried it tomorrow in office with winXP.
Hope it works, will report here.
Click to expand...
Click to collapse
You can flash a RUU with higher manversion then your previous ROM.
I often find that when I go into recovery my sdcard is not mounted. The solution (for me) is to:
adb shell
mount /sdcard
exit
And that's it.
No idea why the sdcard is mounted sometimes but not other times though
sindrefyrn said:
You can flash a RUU with higher manversion then your previous ROM.
Click to expand...
Click to collapse
Is that mean I can't downgrade my SPL and radio?
I can't use fastboot to flash my SPL and radio, because S-ON SPL not allow me to do so.
Could I copy the rom.zip from RUU which contain SPL and radio, then renamed it to sappimg.zip and flash in Hboot mode?
The only thing I want to do is change my SPL back to S-OFF. What can I do?
Thank you for your help.
update: Is there any SPL.zip I can use to flash my SPL in recovery mode?
update 2: I tried flash the ENG SPL 2007.zip in recovery mode, but it can't change my SPL back to S-OFF. Is it because the SPL are in same version, so, I am not upgrading my SPL by this action?
littlestrong said:
Is that mean I can't downgrade my SPL and radio?
I can't use fastboot to flash my SPL and radio, because S-ON SPL not allow me to do so.
Click to expand...
Click to collapse
No reason you can't downgrade your SPL and radio that way, as long as the mainver of the RUU you're flashing is newer than your current.
Could I copy the rom.zip from RUU which contain SPL and radio, then renamed it to sappimg.zip and flash in Hboot mode?
Click to expand...
Click to collapse
Yes, that's possible. However, the mainver still needs to be higher than your current.
The only thing I want to do is change my SPL back to S-OFF. What can I do?
Click to expand...
Click to collapse
If you haven't yet tried, apply this as normal trough recovery.
update: Is there any SPL.zip I can use to flash my SPL in recovery mode?
Click to expand...
Click to collapse
Yes, see above.
etibon said:
This command was not recognized by the phone in my case. It's not always that simple to solve. It would be better to know what causes it in the first place so that people can avoid it.
Click to expand...
Click to collapse
That only works with the 1.76.xxxx SPL, which he has.
From personal experience, I can tell you that I screwed my phone up by flashing hboot and radio in the wrong order.. Ultimately, it prevented me from flashing the Hero recovery... So basically, I was stuck with new SPL/Radio with Sapphire recovery for a while. But here is where things got worst: I attempted to flash BACK to the OLD SPL/Radio, which worked. However, somewhere along the way enableqxdm(1.76.x only) was turned ON, and stayed on. The only thing I was able to do was go back to the stock Rogers RUU (old radio), but left with no SD card which really sucks. When Sense was released for Rogers, I flashed the new ROM and Radio (via USB) and turned enableqxdm off. All fixed at the cost of being rooted
littlestrong; which ROMs are you trying to flash? There could be a really simple explanation as to why they don't work.
1. Did you WIPE data/dalvik/ext before flashing? <- this is pretty important
2. Flash a ROM specific to the new radio?
And if you're trying to reflash your radio and SPL, what errors do you get?
sindrefyrn:
I have tried update your SPL 1.76.2007 from recovery. It remain S-ON afterward.
So, I downgrade my SPL to 1.76.0007 and raido 6.35.07.xx from HK stock sense rom (Hboot mode -> sappimg.zip). The SPL and radio are successful downgraded. Then, I flash the SPL the 1.76.2007 in recovery. No luck.. SPL has been upgraded to 1.76.2007, but it is still S-ON..
pyee0124:
I flash all roms below with full wipe (all 5 wipes in recovery), they all are for new radio:
--[ROM][32A][6.35] SenseUI 2.1 based on DROID Eris dump. Both v01 and v02.
--Super-Hero (Build By AhmgskMod) [Based On Eris Dump].
--Eclair AME [Android 2.1] MADE BY ME [Only For New Radio] [28th Feb]
I also restore a nandroid backup which it was backup with Eclair AME rom, when my phone in good condition.
All the above roms can't boot up, all stop at htc Magic screen..
I search this forum and found 2 topics about making ENG SPL to S-OFF from S-ON.
1. Flash the nandroid backup boot.img file to the phone, might be one of them will make the SPL to be S-OFF.
2. Remove the battery for a couple of day, and leave the phone as it is .The phone might change to S-OFF itself.
Another problem, I can't flash my magic in RUU. ERROR 170 was found both in XP and win7. I tested it in computer with and without htc sync. I have install proper driver.
I have one more question, I can flash custom rom for new radio here in recovery mode. But all 3 roms I had tried won't boot up and stuck in htc Magic screen. Can anyone flash custom rom with S-ON SPL and found no problem in boot??
You should still be able to flash custom ROMS regardless of S-ON. One of the other things you should try is formatting your SD card again.. Try a full FAT32, then try partitioning afterwards. I found that I could only boot Ahmgsk with FAT32/Swap/Ext2.
pyee0124: I have flashed the [ROM][32A] CursorSense32A-1.2.6.1, it can boot up with my S-ON SPL.
I will test flashing others rom and see if I can use Android 2.1.
My device is a HTC MAGIC 32A, the phone cid is HTC__038
Hey I had flashed Rogers RUU 2.1 update over a rom with old radio and old spl
The update failed and I had to take out the battery
Now my phone only opens in the ruu white screen where its written SAPPHIRE 32A SHIP S-ON
HBOOT- 1.76.0010 s-on H
CPLD-12
RADIO-3.22.20.17
Jan 14 2010,00:14:58
And there is a chip with a cross at the bottom
I have fastboot acces but have tried almost all the known commands but to no avail
TRIED FASTBOOT FLASH RECOVERY XXXX... but gives signature fail
fastboot flash zip rom.zip gives main version older in case of official roms and signature error even in extracted roms
fastboot boot recovery xxxx... nothing happens just after the cmd shows booting
tried fastboot erase recovery/system /booot all of them give remote not allow
I have tried to run other official ruu(all of these found here forum.xda-developers.com/showthread.php?t=659403 ) with goldcard butr all of them give error 140 bootloader version error and show main version older on phone screen
I have tried to run the official rogers 2.1 ruu again but it gives error 132- signature error
When running ruu the current device image shows version 3.54.631.7
Tried everything in this thread http://forum.xda-developers.com/showthread.php?t=793704&page=5
and this one
http://forum.xda-developers.com/showthread.php?t=824633
PLEASE HELP ME!!
Either a signed rom(hex edited) with image version greater than 3.54 or a way to get adb working or turn s-on to s-off through fastboot would do the trick
Or simply if somebody could tell me how to revive a phone with S-ON with rom version 3.54 using FASTBOOT Thanks
If you are getting an error main version older with goldcard, then it is not a goldcard. If you can get another goldcard, or still have the numbers to get another goldcard image and remake your goldcard it will work. I have been in the same position and remade the goldcard and it worked. I don't know why or if it happens all the time or with just certain brands, the goldcard no longer works after using it. I don't have a Kiingston only a Samsung microSD and have had to remake it twice. I would get the remote:not allow when trying to flash or boot recovery from fastboot, but when I remade my goldcard it worked.
housry23 said:
If you are getting an error main version older with goldcard, then it is not a goldcard. If you can get another goldcard, or still have the numbers to get another goldcard image and remake your goldcard it will work. I have been in the same position and remade the goldcard and it worked. I don't know why or if it happens all the time or with just certain brands, the goldcard no longer works after using it. I don't have a Kiingston only a Samsung microSD and have had to remake it twice. I would get the remote:not allow when trying to flash or boot recovery from fastboot, but when I remade my goldcard it worked.
Click to expand...
Click to collapse
Hey I dont have a spare phone to check the above, but with the current goldcard I have I am able to pass the CID check with any rom(otherwise get cust id error) but am not able to get past the Main version check so will making a goldcard again help
hEY MY CURRENT ROM VERSION IS 3.54 AND THE OTHER RUU'S AVAILABLE HAVE MAX UPTO 3.05 AND I AM UNABLE TO DOWNGRADE EVEN WITH A PROPER GOLD CARD. PLEASE HELP!!
i have same problem, did you fixed?
primux said:
i have same problem, did you fixed?
Click to expand...
Click to collapse
Almost, got access to adb with su priveleges but by mistake flashed wrong flash_image file and ruined it, now my phone is lying with HTC care who are thieves and say the "Phone is EXITING while we are trying to update your software" then they call me and say that that they will have to change my motherboard despite my hardware being completely fine(I think they have taken out all my original parts and initially say my warranty has expired, then do something that makes my phone not even boot and then say i have warranty, just hope they give back my phone soon ) ..
My advice would be to try the below else perform JTAG as HTC care are greedy, unprofessional, illiterate cheats.
Type fastboot oem boot or fastboot boot oem while in fastboot and your phone will boot and keep restarting every 2 min
Good Luck
i see, can you tell me how you got adb access? i just have RUU MODE and when i tried to upload a new flash stuck in SYSTEM - unzipping, my phone it's same version as yours. i'll appreciate any help
The whole story is a little bit long.
I still can access to fastboot. On the RUU screen, I can read the following information:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0008(SAPP10000)
CPLD-12
RADIO-3.22.20.17
Nov 3 2009, 15:56:29
Here is how it happened. I flashed the radio to 3.22 and run a wrong RUU file (RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe). The problem comes: after unsuccessfully flash the RUU file (as the radio in the RUU is 6.35), the security is turned ON (S-ON). Those RUU files with radio 3.22.XX have different version of SPL from 1.76.XXX. I cannot find a RUU file with SPL 1.76.008 and radio 3.22.XX. Therefore, I cannot use any RUU file to change the situation (I got a goldcard).
The security is turned on and I cannot change the radio, SPL or recovery in fastboot (cannot pass the infoSignature checking).
Now I still can access to fastboot (such as fastboot devices).
I don't know why I cannot use fastboot to boot a recovery (fastboot boot recovery-RA-sapphire-v1.7.0H.img). I was able to send the recovery img to the device. But the booting of recovery takes for ever.
I can only enter fastboot mode now using any combination of buttons.
Please give your comment and help to solve this.
Thank you very much!
htchd2sg said:
The whole story is a little bit long.
I still can access to fastboot. On the RUU screen, I can read the following information:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0008(SAPP10000)
CPLD-12
RADIO-3.22.20.17
Nov 3 2009, 15:56:29
Here is how it happened. I flashed the radio to 3.22 and run a wrong RUU file (RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe). The problem comes: after unsuccessfully flash the RUU file (as the radio in the RUU is 6.35), the security is turned ON (S-ON). Those RUU files with radio 3.22.XX have different version of SPL from 1.76.XXX. I cannot find a RUU file with SPL 1.76.008 and radio 3.22.XX. Therefore, I cannot use any RUU file to change the situation (I got a goldcard).
The security is turned on and I cannot change the radio, SPL or recovery in fastboot (cannot pass the infoSignature checking).
Now I still can access to fastboot (such as fastboot devices).
I don't know why I cannot use fastboot to boot a recovery (fastboot boot recovery-RA-sapphire-v1.7.0H.img). I was able to send the recovery img to the device. But the booting of recovery takes for ever.
I can only enter fastboot mode now using any combination of buttons.
Please give your comment and help to solve this.
Thank you very much!
Click to expand...
Click to collapse
Many of this was answered, search the forum.
Here is the thing you have wrong spl radio combination,you have perfected spl. You can do a fastboot boot xxxxxx.img and enter recovery. Then you must flash eng spl 1.33.2010.And you will be unbricked
Thank you for the reply.
I tried fastboot recovery-RA-sapphire-v1.7.0H.img. But after the sending of the image is over, it will stay in booting for ever. I don't understand why I cannot boot the recovery.
htchd2sg said:
Thank you for the reply.
I tried fastboot recovery-RA-sapphire-v1.7.0H.img. But after the sending of the image is over, it will stay in booting for ever. I don't understand why I cannot boot the recovery.
Click to expand...
Click to collapse
You cant boot that recovery try the one hero recovery Ra-magic1.6.2H smthing recovery
I downloaded the 1.6.2 recovery from http://forum.xda-developers.com/showpost.php?p=4549551&postcount=1
But I still cannot boot the recovery(I can send the recovery)
htchd2sg said:
I downloaded the 1.6.2 recovery from http://forum.xda-developers.com/showpost.php?p=4549551&postcount=1
But I still cannot boot the recovery(I can send the recovery)
Click to expand...
Click to collapse
Hmm did you try the sappimg.nbh to restore your magic???
Updated: I tried to use sappimg.nbh in fastboot mode. However, it responses that the main version is older. This is because I have run the RUU (RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_No Driver.exe), whose main version is 3.05 while the sappimg.nbh is older than this number.
Now I can access fastboot and the hboot, but not the recovery. Of course, I cannot boot the android OS either. Is there a method to root just in the fastboot mode? I have the security turned on (S-ON)?
Anyone got suggestion? Thanks!
Can anyone help on this? really get frustrated
htchd2sg said:
Updated: I tried to use sappimg.nbh in fastboot mode. However, it responses that the main version is older. This is because I have run the RUU (RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_No Driver.exe), whose main version is 3.05 while the sappimg.nbh is older than this number.
Now I can access fastboot and the hboot, but not the recovery. Of course, I cannot boot the android OS either. Is there a method to root just in the fastboot mode? I have the security turned on (S-ON)?
Anyone got suggestion? Thanks!
Click to expand...
Click to collapse
You need to create a goldcard www.theunlockr.com at How to's and then use sappimg.nbh
I got gold card already. . Thank you!
Do you solve this? I got the exactly problem with you =(
I actually had this same issue months ago and nothing worked. Unfortunately I ended up getting another phone.
Sent from my SGH-T959 using XDA App
r3v4N said:
I actually had this same issue months ago and nothing worked. Unfortunately I ended up getting another phone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
What a bad news =( I had sent this phone to repair, but all of their experts cannot fix as well.
That's lame.... did you try the unroot process?
Sent from my SGH-T959 using XDA App
You could try unbricking by flashing the Rogers or Brazilian Android 2.1 RUU. The main version is newer and a goldcard should make it work.
Please make sure your battery is full and that you have a PROPER GOLDCARD!!! Otherwise this will most likely fail.
I've uploaded the sappimg to http://www.multiupload.com/WO0S35S53S
Rename it to sappimg.zip, copy it to the root of your SD card and boot into fastboot (vol-down and power). That SHOULD fix your phone. Then again, it could also brick it even worse, but what do you have left to lose?
After loaded sappimg, it checking sappimg, then went back to HBOOT. Nothing happened. I've tried to recreate my gold card, no luck with it =(
Hi.
i need some advice to see what can i do to get the phone working again.
case:
htc magic 32A.
ENG S-OFF H.
hboot-1.33.2005
radio.3.22.20.17.
i had cyangoenmod 6. working just fine! for several months. a couple a days ago (without installing anything new) it crashed, and now it gets stuck in the splash screen.
symptoms:
i can enter fastboot. fastboot devices lists the phone.
i can't enter recovery. fastboot boot recovery.img doesnt work, still stuck in splash screen. fastboot flash recovery.img doesnt work either.
i thought the next step would be a factory reset so i got a friend to copy the sappimg.zip on my sdcard and tried to run hboot mode, but it says NO IMAGE! when checking SAPPIMG.zip
should i use RUU? whats the procedure there?. from where i run it?. also i don't know whats the right one for my phone. i see this list: http://forum.xda-developers.com/showthread.php?t=659403.
and fastboot getvar version-main gives me: 3.05.529.9. while CID gives BSTAR301
i dont see that exact version in the list, and the only one with that cid is 2.20.515.5 HTC Chile BrightStar/Entel. im a little confused here...
thanks for any help!.
the problem seems to be bigger. I decided to go with the RUU directly from Htc site. For my device, i gave my serial no. and downloaded the .exe for magic_brightstar. It did successfully updated everything (?), radio, hboot, recovery, system, splash....
But i start the phone and it is still stuck in the freaking init screen.
I don't understand, what else can i do?.
Can you enter the recovery now?
No. the recovery doesn't enter. still frozen.
I'm trying to have a working goldcard, but it has been a little tricky without another phone to convert the sd. I'm following what amon_ra suggested here http://forum.xda-developers.com/showthread.php?t=548218. Because right now my hboot is locked (after running the factory RUU) and i can't run any of the flashing fastboot commands.
will post what happens...
ok the goldcard did its job, i have again eng spl with all fastboot flashing enabled. but i cant get into recovery yet, no matter what.
at this point i'm thinking on flashing the original hboot, radio and go claim the guaranty...
Any ideas before throwing the towel???
i was thinking that if it is a hardware/firmware problem, it should be possible to test via fastboot oem commands, isn't?
Download my fastboot commander from my signature (the magic version).
It has a special 32A tab.
Using the tool, flash the old combo and see if you can enter recovery afterwards.
You can also flash the new combo and give it try...
Guys please help mee
I tried to root the Desire Z of my friend and now I think i [email protected]#@ his phone.
I have installed clockwork recovery and i have unlocked the bootloader from htcdev but I have a S-ON.
I tried to install through clockworkmod the rom Android Revolution HD™ 7.0.2 and now i can nott restore the phone.
Is there any Rom that can be install with S-ON or not?
Any solution?
searius said:
Guys please help mee
I tried to root the Desire Z of my friend and now I think i [email protected]#@ his phone.
I have installed clockwork recovery and i have unlocked the bootloader from htcdev but I have a S-ON.
I tried to install through clockworkmod the rom Android Revolution HD™ 7.0.2 and now i can nott restore the phone.
Is there any Rom that can be install with S-ON or not?
Any solution?
Click to expand...
Click to collapse
HTC's method won't give you S-OFF better to use any of the other methods to root, What happened when you tried installing the rom?
I am stuck at HTC logo.
can I put any rom that does not require s-off?
all custom roms need soff to be flashed from recovery. if you unlocked your hboot then you need to flash via fastboot. your best to root your phone the proper way by following the wiki:
http://forum.xda-developers.com/wiki/HTC_Vision
may seem hard but its easy if you read first - but i believe you need to relock your bootloader first
i dont understand. why i need to relock my bootloader?
right now I have:
***UNLOCKER***
VISION PVT SHIP S-ON
HBOOT-0.85.0015
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Dec 20 2011, 16:21:13
I can install the stock recovery if i want or clockwork.
I tried this RUU :
http://shipped-roms.com/download.ph...60.25_26.10.04.03_M_release_199043_signed.exe
is this right?
But i can not finished it.
it say image version 1.00.000.0 after some minutes it is stuck at the black screen with htc logo.
I have this error:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
relock hboot and try again.
this time you should be fine (htc bootloader unlock is a crock)
http://forum.xda-developers.com/showthread.php?p=21563546
This is from a guide here in the general section on how to get root and s-off with the HTC unlock tool.
In the future if you are trying to gain root and s-off, i suggest using an other method like gfree because you can always go back to stock and have your warrenty. The phone you are now trying to get s-off on is registered at HTC and warrenty is most likley void now
Sent from my HTC Desire Z using xda premium
So I locked the bootload and used the RUU above and I stuck at the black screen with HTC logo after this everything is flawless.
Thanks guys for your help.And I'm glad to be in this friendly forum.
Thanks again.
You have to flash the boot.img file in DZ
Okay, I experienced sth before but some kind people have told me how to do ^^
Okay, you should have followed the HTCdev unlock guide and you should have prepared the file for adb and fastboot.
So, in that rom zip file, find, "kernel" folder, and find "rcmix.img", copy it to you adb folder (Me : C:\Android)
Then, open a command prompt (Start -> run -> cmd)
change the directory by inputing:
Code:
cd C:\Android
change your folder destination as you prepared
then , connect your phone and make it into bootloader by inputing:
Code:
adb reboot bootloader
Now, you phone should be in bootloader (white bg)
then input these to flash the rcmix.img into ur phone
Code:
fastboot flash boot rcmix.img
reboot ur phone and wait,the forst boot should take longer time
If it doesnt work, find another .img file in the "kernel" folder in the zip and do these setps, rmb to change rcmix.img into that file name
If it is not working, freenode, #G2ROOT channel, you will find nice guy yo help you
thx m8 I resolved my problem by locking down the bootload and now I have a S-OFF.
But thanks anyway for your help.