Related
Hello
I have researched alot but didn't get my answer. There are alot of threads on this but still no luck.
I have a bell htc incredible S that came with s-off. I rooted through alpharx and flashed a custom rom of core droid.
Rom: http://forum.xda-developers.com/showthread.php?t=1096056
Everything works great except there is no call sound. I am trying to update the radio provided in the link above but I keep getting "model id incorrect" error.
Idk if I am flashing it properly or missing something in the process. Can someone please help I am new to this.
I put PG32IMG.zip file into K:\PG32IMG.zip and ran through Fastboot.
Thanks in advance
humm
umer215 said:
Hello
I have researched alot but didn't get my answer. There are alot of threads on this but still no luck.
I have a bell htc incredible S that came with s-off. I rooted through alpharx and flashed a custom rom of core droid.
Rom: http://forum.xda-developers.com/showthread.php?t=1096056
Everything works great except there is no call sound. I am trying to update the radio provided in the link above but I keep getting "model id incorrect" error.
Idk if I am flashing it properly or missing something in the process. Can someone please help I am new to this.
I put PG32IMG.zip file into K:\PG32IMG.zip and ran through Fastboot.
Thanks in advance
Click to expand...
Click to collapse
try this thread
http://forum.xda-developers.com/showthread.php?t=1129014&highlight=radio
maybe your flashing a froyo radio on ginger bread?>
^^^^ thanks
I am flashing a GB radio and I already looked at that link but still no luck. Idk if I have a radio s-off. How to check that? I was on froyo before I got custom coredroid and I never touched radio.
AlphaRevX doesn't give you radio S-OFF, that's why you're having problems.
doctorsax said:
AlphaRevX doesn't give you radio S-OFF, that's why you're having problems.
Click to expand...
Click to collapse
Can u please post a link on how to get radio s-off? I searched around but couldnt find any. My phone is unlocked tho.
umer215 said:
Hello
I have researched alot but didn't get my answer. There are alot of threads on this but still no luck.
I have a bell htc incredible S that came with s-off. I rooted through alpharx and flashed a custom rom of core droid.
Rom: http://forum.xda-developers.com/showthread.php?t=1096056
Everything works great except there is no call sound. I am trying to update the radio provided in the link above but I keep getting "model id incorrect" error.
Idk if I am flashing it properly or missing something in the process. Can someone please help I am new to this.
I put PG32IMG.zip file into K:\PG32IMG.zip and ran through Fastboot.
Thanks in advance
Click to expand...
Click to collapse
Hi i to have a Bell HTc incredible S, and could not flash a new radio, and could not get methods already outlined to work, so i did this method...
go here http://forum.xda-developers.com/showthread.php?t=1070348, follow this guide to install eng hboot then,
extract radio.img
Copy radio.img to a location where fastboot can find it. (wherever adb is)
Boot your phone into fastboot mode (power on while holding down the volume key)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash radio radio.img
Code:
D:\SDK>adb shell
# busybox md5sum /sdcard/vivo_enghboot.img
busybox md5sum /sdcard/vivo_enghboot.img
b1829cfb7cf5d462660a58aa5449d27c /sdcard/vivo_enghboot.img
# dd if=/sdcard/vivo_enghboot.img of=/dev/block/mmcblk0p18
dd if=/sdcard/vivo_enghboot.img of=/dev/block/mmcblk0p18
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.552 secs (1899594 bytes/sec)
# reboot bootloader
reboot bootloader
D:\SDK>fastboot flash radio radio.img
sending 'radio' (25472 KB)...
OKAY [ 5.347s]
writing 'radio'...
OKAY [ 4.844s]
finished. total time: 10.194s
That's what I'm saying - your phone has an unlocked HBOOT (bootloader) but the radio is still locked. There is at least one thread on the forum here explaining how to flash a radio manually. Radio S-OFF can only be achieved using a hardware solution like an XTC clip, as far as I know.
test this out?
doctorsax said:
That's what I'm saying - your phone has an unlocked HBOOT (bootloader) but the radio is still locked. There is at least one thread on the forum here explaining how to flash a radio manually. Radio S-OFF can only be achieved using a hardware solution like an XTC clip, as far as I know.
Click to expand...
Click to collapse
can some one test out ali3nfr3ak method is it possible with soft ware S-OFF to manually flash a radio
^^^
I tried but I keep getting "permission denied" error when I enter "su" and I cant get a # sign in the process of Ship S-OFF to ENG S-OFF.
I am new to this forums so I cant post in the development section.
I cant get Ship S-off to ENG-Soff. I also have a question
If I get ENG S-OFF, will my phone become a Radio S-OFF. How do I check if my phone is Radio S-off or Radio S-on?
Thanks guys
umer215 said:
^^^
I tried but I keep getting "permission denied" error when I enter "su" and I cant get a # sign in the process of Ship S-OFF to ENG S-OFF.
I am new to this forums so I cant post in the development section.
I cant get Ship S-off to ENG-Soff. I also have a question
If I get ENG S-OFF, will my phone become a Radio S-OFF. How do I check if my phone is Radio S-off or Radio S-on?
Thanks guys
Click to expand...
Click to collapse
Ok so either the rom u r using does not have root permissions, or maybe you are not allowing root permissions on your phone when you type "su" in adb shell, ... what i mean is, after typing "su" in adb shell, on your phone a popup should appear asking for root permissions. U need ROOT permissions and busybox installed to flash eng-boot.
MY phone came shipped to me with s-off, i didnt use an xtc clip.
ali3nfr3ak said:
Ok so either the rom u r using does not have root permissions, or maybe you are not allowing root permissions on your phone when you type "su" in adb shell, ... what i mean is, after typing "su" in adb shell, on your phone a popup should appear asking for root permissions. U need ROOT permissions and busybox installed to flash eng-boot.
MY phone came shipped to me with s-off, i didnt use an xtc clip.
Click to expand...
Click to collapse
Hey bro thanks for ur help
ur method is amazing. Now finally i got Eng S-off and GB radio 20.2804.30.085AU_3805.04.03.22_M. currently, I am using froyo so I have no call sound that means I have got a GB radio and I just need to put back coredroid rom.
Thanks again
jul644 said:
can some one test out ali3nfr3ak method is it possible with soft ware S-OFF to manually flash a radio
Click to expand...
Click to collapse
yes his method did work sorry for the other post
umer215 said:
Hey bro thanks for ur help
ur method is amazing. Now finally i got Eng S-off and GB radio 20.2804.30.085AU_3805.04.03.22_M. currently, I am using froyo so I have no call sound that means I have got a GB radio and I just need to put back coredroid rom.
Thanks again
Click to expand...
Click to collapse
Sweet. Nice one, well done.
once you have flashed the radio, there is no need for the "eng-hboot" so if you were feeling confident...
download the attached zip.
extract and place hboot_1.13.0000_CRC_8a731c6e_0401.img [MD5=C0845E6348123828F918FDB48B74F349] in the same place you put the radio.img
Boot your phone into fastboot mode (power on while holding down the volume key)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash hboot hboot_1.13.0000_CRC_8a731c6e_0401.img
Code:
C:\Users\Administrator>d:
D:\>cd sdk
D:\SDK>fastboot devices
HT15GTA00*** fastboot
D:\SDK>fastboot flash hboot hboot_1.13.0000_CRC_8a731c6e_0401.img
sending 'hboot' (1024 KB)...
OKAY [ 0.411s]
writing 'hboot'...
OKAY [ 0.421s]
finished. total time: 0.832s
Will flashing ENG HBOOT onto a AlphaRevX'd S-OFF phone cause it to go back to S-ON?
charch said:
Will flashing ENG HBOOT onto a AlphaRevX'd S-OFF phone cause it to go back to S-ON?
Click to expand...
Click to collapse
Well that i do not know %100. I wouldnt think so tho. I cannot test this for you as I didnt need to use AlphaRevX to s-off
It kinda worries me though... If I get ENG HBOOT and it returns to S-ON then would there be a way to S-OFF it again? Or would I be stuck forever?
Sent from my HTC Incredible S using XDA App
charch said:
It kinda worries me though... If I get ENG HBOOT and it returns to S-ON then would there be a way to S-OFF it again? Or would I be stuck forever?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Well there is only one way to find out, All I can say is that my phone came with s-off, flashing the eng-hboot did not return me to s-on, the eng-boot is an engeering hboot so i dont see that it would return to s-on
EDIT: this from your other thread..
vimfreak said:
Flashing RUU will return S-ON.
I've S-OFF my phone with alpharevx and then flashed official GB RUU - phone was S-ON again.
However its not a big deal since you can use alpharevx trick again - phone will be S-OFF again (worked for me)
Click to expand...
Click to collapse
It depends on whether or not it checks if the hardware is S-OFF or not... Because if it does then Im screwed... But Ive looked at the Desire Z forum and they soft mod S-OFF and are able to install ENG HBOOT S-OFF... But... If it does happen to fail, since Im already rooted, wouldnt I be able to flash a HBOOT from the Optus rom or something?
EDIT: yes, but AlphaRevX relies on the stock HBOOTs to operate...
EDIT 2: did some research... ENG HBOOT is unlocked by nature... Apparently its impossible for it to revert you to S-ON xD thanks for your help
Sent from my HTC Incredible S using XDA App
works
i can confirm that this works here was my log
PHP:
C:\AndroidSDK\platform-tools>fastboot devices
HT13RTA05966 fastboot
C:\AndroidSDK\platform-tools>fastboot flash radio radio.img
sending 'radio' (25472 KB)... OKAY [ 5.328s]
writing 'radio'... OKAY [113.161s]
finished. total time: 118.490s
C:\AndroidSDK\platform-tools>
thos 118 seconds were scary
jul644 said:
i can confirm that this works here was my log
PHP:
C:\AndroidSDK\platform-tools>fastboot devices
HT13RTA05966 fastboot
C:\AndroidSDK\platform-tools>fastboot flash radio radio.img
sending 'radio' (25472 KB)... OKAY [ 5.328s]
writing 'radio'... OKAY [113.161s]
finished. total time: 118.490s
C:\AndroidSDK\platform-tools>
thos 118 seconds were scary
Click to expand...
Click to collapse
Was your phone S-OFF out of the box or did you use AlphaRevX?
EDIT: I decided to risk it and install ENG HBOOT... IT WORKED! Installing the Optus RUU!
This is the latest hboot from HTC for the DINC that allows the bootloader to be OEM unlocked.
HBOOT 1.02.0000
1. Enable usb debugging
2. Run RUU(make sure to use the HTC drivers or RUU wont work)
3. Use htc dev process to oem unlock bootloader
4. Enjoy pwnage of ur DINC
P.S. I have attached the PB31IMG.zip for those who dont kno how to RUU
Question (anyone)?
If you are already S-off, rooted, and using the .92 bootloader, will flashing the zip cause a loss of S-off, or any other disasters?
Considering giving it a shot, but don't want to spend the evening rerooting or getting into something I can't get back out of.
Input welcome...
sorry...I was on the phone
omniatic said:
Question (anyone)?
If you are already S-off, rooted, and using the .92 bootloader, will flashing the zip cause a loss of S-off, or any other disasters?
Considering giving it a shot, but don't want to spend the evening rerooting or getting into something I can't get back out of.
Input welcome...
sorry...I was on the phone
Click to expand...
Click to collapse
No. I did that and was fine. I used the PB31IMG.zip
Sent from my Galaxy Nexus using Tapatalk 2
OK flashed it fine. Now, I see that the unlocking process wipes the phone clean. Will I still be able to boot into CWM recovery and restore a nand backup? Or will I have to reflash CWM 5.0.2.0?
Edit: I'll still be S-off, right?
omniatic said:
OK flashed it fine. Now, I see that the unlocking process wipes the phone clean. Will I still be able to boot into CWM recovery and restore a nand backup? Or will I have to reflash CWM 5.0.2.0?
Edit: I'll still be S-off, right?
Click to expand...
Click to collapse
Actually I think the wipe process with unlocking fails if you're on CWM. I didn't lose CWM or data when I did it.
Yes. I still am S-OFF when I did it rooted.
But you may not need this unlocked bootloader as you can already flash radios and recoveries from the bootloader (HBOOT) and kernels, ROMs and recoveries from CWM with s-off alone.
I got it just so I could use fastboot to flash kernels which if you flash with fastboot on this device you may need to still manually push the corresponding wifi module if the version string changes - not necessarily each time you switch kernels either. For my gingersense kernels that would only be if you switch between gingertiny 2.6.35.10, gingertiny-v2 2.6.35.13 and gingertiny-2.6.35.14. For incredikernel that may be quite different.
Sorry, I'm rambiling and should be asleep but just so hyper.
Yeah, I know it wasn't needed. But I felt it had to be done. Anyhow, something got wiped, cause it hung on the boot screen forever. Finally pulled the battery, booted into recovery, and restored my fresh backup. 1.02 bootloader, unlocked, and up and running again.
Thanks for all the help. I see you edited your post about the same time I was banging away in command prompt. All my SDK tools were scattered around and needed updating, which stretched it out. Once again, that feeling you get when something works despite your best efforts.
Thanks+
After a gut-wrencher like that, some sleep sounds good.
Sorry if this is the wrong thread in which to post but I'm getting pretty confused. I have an HTC incredible I just received with S-Off
It says:
HBOOT-0.92.9999
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
I am in fastboot usb, but I cannot flash the cwm 5.0.2.0 img,
I try fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img and receive the error:
C:\Android\android-sdk\platf
sending 'recovery' (3064 KB)
OKAY [ 0.494s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.498s
Does this mean that I don't have root access, even though I am S-off?
Not sure about flashing a newer recovery through fastboot.....but you can also download rom manager from the market and update your cwm that way....
The Bootloader
can you update the hboot while running a custom rom without bricking.
Asylum1621 said:
Sorry if this is the wrong thread in which to post but I'm getting pretty confused. I have an HTC incredible I just received with S-Off
It says:
HBOOT-0.92.9999
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
I am in fastboot usb, but I cannot flash the cwm 5.0.2.0 img,
I try fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img and receive the error:
C:\Android\android-sdk\platf
sending 'recovery' (3064 KB)
OKAY [ 0.494s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.498s
Does this mean that I don't have root access, even though I am S-off?
Click to expand...
Click to collapse
How are you trying to flash it? You just take this file http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip, and place it on your sdcard in no folders. Then boot to hboot and wait a few secs. It should automaticly find the file and prompt you to press vol up to update.
Fastboot flashing images wont work unless your bootloader in unlocked.
Edit: Didnt realize this post was so old.
---------- Post added at 10:31 PM ---------- Previous post was at 10:27 PM ----------
zachf714 said:
can you update the hboot while running a custom rom without bricking.
Click to expand...
Click to collapse
Yes you can as long as your s-off. This thread is actually old and a newer version hboot 1.07
DOWNLOAD: http://dinc.does-it.net/Hboots/Hboot_1.07/PB31IMG.zip
MD5: http://dinc.does-it.net/Hboots/Hboot_1.07/PB31IMG.zip.md5 has been released. However if your s-off there is no need to update, as you can already flash thru hboot. The only advantage is being able to fastboot flash imgs.
If you s-on the only way to update is to do an ruu, which will wipe the phone and require you to reroot and flash a backup.
cmlusco said:
Yes you can as long as your s-off.
Click to expand...
Click to collapse
Oh really? s-off users can simply flash the new HBOOT in HBOOT then do the unlocking process on HTC-Dev?
That unlocks and keeps s-off?
ardax said:
Oh really? s-off users can simply flash the new HBOOT in HBOOT then do the unlocking process on HTC-Dev?
That unlocks and keeps s-off?
Click to expand...
Click to collapse
Correct.
Are you guys flashing HBOOT without checking the md5?
Sounds gutsy...
Sent from my Droid Incredible using xda app-developers app
ccbiker said:
Are you guys flashing HBOOT without checking the md5?
Sounds gutsy...
Sent from my Droid Incredible using xda app-developers app
Click to expand...
Click to collapse
You can get the md5 by adding .md5 to the download url. ( http://dinc.does-it.net/Hboots/Hboot_1.07/PB31IMG.zip.md5 ) All files on dinc.does-it.net have an md5.
ccbiker said:
Are you guys flashing HBOOT without checking the md5?
Click to expand...
Click to collapse
Are you nutters? I'll both verify md5 and check zip file integrity before attempting to flash something like an hboot or radio!
cmlusco said:
You can get the md5 by adding .md5 to the download url. ( http://dinc.does-it.net/Hboots/Hboot_1.07/PB31IMG.zip.md5 ) All files on dinc.does-it.net have an md5.
Click to expand...
Click to collapse
Oh nice. I just saw the PB31IMG zip in the attachment in the OP and was like, "what?! these people are crazy!" Good to know!
ardax said:
Are you nutters? I'll both verify md5 and check zip file integrity before attempting to flash something like an hboot or radio!
Click to expand...
Click to collapse
Yeah.. I feel the same way! I was just confused since I didn't see the md5 posted. I wondered what I was missing.
So I kno its so late but I'd rather be sure than sorry lol...I can flash hboot 1.07(or what ever it is) and have both s-off and be unlocked? I thought you could only have one at a time? Someone help plz
Sent from my rooted GameBoy Advance! ^¬^
Yeah. Get S-OFF first if you haven't already. Then flash the latest HBOOT. You'll still have S-OFF after that. Then just unlock the bootloader on htcdev.com according to their directions.
Viola! S-OFF and unlocked bootloader.
Thanks will do!
Sent from my rooted GameBoy Advance! ^¬^
Why do you guys do this? Are you already rooted and running custom roms
Sent from my ADR6300 using xda app-developers app
I think I may have soft bricked my HTC Raider.
I was attempting to flash CM9 on my HTC. I followed the pre-flash procedures (Wiping Data, etc). Then, once it was complete, I rebooted the phone. The phone could not get past the CM9 Blue Tunnel animation. I left it there for about an hour, but nothing happened. I can still access my recovery and bootloader. I have tried flashing another ROM, as well as restoring a Nandroid backup I made, but they all lead to the white HTC screen. My Raider has S-ON.
User MzzSarahx3 had an extremely similar case, except that person had an AT&T Vivid, as seen here:
http://forum.xda-developers.com/showthread.php?t=1416836&page=51
MzzSarahx3 managed to fix the problem by running an RUU, so that is why I believe I can fix my situation by doing the same. I am aware of the RUU Collection that Football uploaded, but clicking on a link on FileFactory will give me an error saying that all download slots are in use.
So could somebody please link me, or upload, an ICS RUU for the HTC Raider on Rogers? Help would be much appreciated.
Just means site is busy keep checking
Sent from my HTC PH39100 using xda premium
ronnie498 said:
Just means site is busy keep checking
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
I have been clicking on that link since this morning. And it still gives me the same message. I will continue to check, though.
Does anyone have an alternate solution?
The stock Bell ICS RUU should work fine on your Rogers Raider. ( I have a Bell Raider but installed it on my buddy's Rogers Raider).
I'm uploading the stock Bell ICS RUU to Depositfiles right now but its gonna take an hour. I'll update my post with the link when it's done.
You can probably find the stock Bell ICS RUU on various threads in the forum. I believe that's where I got it from originally.
Note that if you have unlocked your bootloader (via htcdev), the stock RUU will refuse to install !
LaZiODROID said:
The stock Bell ICS RUU should work fine on your Rogers Raider. ( I have a Bell Raider but installed it on my buddy's Rogers Raider).
I'm uploading the stock Bell ICS RUU to Depositfiles right now but its gonna take an hour. I'll update my post with the link when it's done.
You can probably find the stock Bell ICS RUU on various threads in the forum. I believe that's where I got it from originally.
Note that if you have unlocked your bootloader (via htcdev), the stock RUU will refuse to install !
Click to expand...
Click to collapse
Thank you very much for uploading it!
I am definitely looking forward to using my phone again!
BTW I have looked around for the Bell ICS RUU on these forums, but did not find anything. The closest thing I found was this:
http://forum.xda-developers.com/showthread.php?t=1672800&highlight=bell+ics+ruu
But they said it was not a RUU so.....
I have uploaded the Bell ICS RUU to DepositFiles. You're welcome!
Filename: RUU_HOLIDAY_ICS_35_S_BM_3.38.666.2_Radio_3.04.4740.11_34.29.701040.22_release_255916_signed.exe
http://depositfiles.com/files/ofalwm57q
LaZiODROID said:
I have uploaded the Bell ICS RUU to DepositFiles. You're welcome!
Filename: RUU_HOLIDAY_ICS_35_S_BM_3.38.666.2_Radio_3.04.4740.11_34.29.701040.22_release_255916_signed.exe
Click to expand...
Click to collapse
Umm, well I downloaded the RUU file you kindly uploaded, but I have encountered a problem.
ERROR [131]: CUSTOMER ID ERROR
I have tried many times. Got this error every time. I guess it is because I have a Rogers phone and attempting to update using a Bell RUU.
Any suggestions?
LeoCFZ said:
Umm, well I downloaded the RUU file you kindly uploaded, but I have encountered a problem.
ERROR [131]: CUSTOMER ID ERROR
I have tried many times. Got this error every time. I guess it is because I have a Rogers phone and attempting to update using a Bell RUU.
Any suggestions?
Click to expand...
Click to collapse
Damn... I don't remember having to do that for my buddy's Rogers Raider. Sorry.. it was some time ago.
He's here so I just checked his phone... we must have put in the SuperCID back then (which may accept any RUU?)
C:\Users\Master>fastboot getvar cid
cid: 11111111
finished. total time: 0.000s
and I ran mine (actual Bell Raider).:
C:\Users\Master>fastboot getvar cid
cid: BM___001
finished. total time: 0.000s
Feeling adventurous? I'm not sure if you need to be S-OFF to do this (or have unlocked bootloader, or even both) but...
You can change the CID via fastboot.
Fastboot commands that you can do: (thank you jmone from showpost.php?p=25187040&postcount=199)
(to check your current CID - write it down?)
fastboot getvar cid
(to write a new CID to the phone)
fastboot oem writecid 11111111 (where the 11111111 contains the CID you want - you can try the 11111111 (is that known as SuperCID?) or you can try mine, which is BM___001 as specified above)
(then reboot into bootloader mode)
fastboot reboot-bootloader
(then if it reboots back into fastboot mode, you can run this to verify your desired CID made it)
fastboot getvar cid
Then maybe the RUU will allow itself to install?
LaZiODROID said:
Damn... I don't remember having to do that for my buddy's Rogers Raider. Sorry.. it was some time ago.
He's here so I just checked his phone... we must have put in the SuperCID back then (which may accept any RUU?)
C:\Users\Master>fastboot getvar cid
cid: 11111111
finished. total time: 0.000s
and I ran mine (actual Bell Raider).:
C:\Users\Master>fastboot getvar cid
cid: BM___001
finished. total time: 0.000s
Feeling adventurous? I'm not sure if you need to be S-OFF to do this (or have unlocked bootloader, or even both) but...
You can change the CID via fastboot.
Fastboot commands that you can do: (thank you jmone from showpost.php?p=25187040&postcount=199)
(to check your current CID - write it down?)
fastboot getvar cid
(to write a new CID to the phone)
fastboot oem writecid 11111111 (where the 11111111 contains the CID you want - you can try the 11111111 (is that known as SuperCID?) or you can try mine, which is BM___001 as specified above)
(then reboot into bootloader mode)
fastboot reboot-bootloader
(then if it reboots back into fastboot mode, you can run this to verify your desired CID made it)
fastboot getvar cid
Then maybe the RUU will allow itself to install?
Click to expand...
Click to collapse
I typed in the commands and I got this:
c:\Users\Leo Zheng\Desktop\Vivid Toolkit\Data>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO holiday_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.076s]
finished. total time: 1.076s
c:\Users\Leo Zheng\Desktop\Vivid Toolkit\Data>fastboot getvar cid
cid: ROGER001
finished. total time: 0.002s
So, that means the SuperCID did not manage to write. I searched around and found hints about something called Radio S-OFF or Gold Card, but it was for a different HTC phone...
Is there a guide to follow so i could get this?
BTW SuperCID would allow the user to use any RUU.
LeoCFZ said:
I typed in the commands and I got this:
c:\Users\Leo Zheng\Desktop\Vivid Toolkit\Data>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO holiday_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.076s]
finished. total time: 1.076s
c:\Users\Leo Zheng\Desktop\Vivid Toolkit\Data>fastboot getvar cid
cid: ROGER001
finished. total time: 0.002s
So, that means the SuperCID did not manage to write. I searched around and found hints about something called Radio S-OFF or Gold Card, but it was for a different HTC phone...
Is there a guide to follow so i could get this?
BTW SuperCID would allow the user to use any RUU.
Click to expand...
Click to collapse
Ahhh.. so you need to be S-OFF it seems. The S-OFF procedure isn't super easy, but it's nice to have (because with S-OFF, the custom roms you install will be able to automatically flash their kernel. With S-ON, to run a custom rom, you need to flash the kernel separately... not a huge deal, but having S-OFF is convenient if you like to try different custom roms). To S-OFF, you have to be willing to void your phone's warranty.
Theres gotta be the Roger RUU out there somewhere (that is ICS). I have the Rogers Gingerbread RUU... but I think it will only work if you havent upgraded your phone to ICS yet...
LaZiODROID said:
Ahhh.. so you need to be S-OFF it seems. The S-OFF procedure isn't super easy, but it's nice to have (because with S-OFF, the custom roms you install will be able to automatically flash their kernel. With S-ON, to run a custom rom, you need to flash the kernel separately... not a huge deal, but having S-OFF is convenient if you like to try different custom roms). To S-OFF, you have to be willing to void your phone's warranty.
Theres gotta be the Roger RUU out there somewhere (that is ICS). I have the Rogers Gingerbread RUU... but I think it will only work if you havent upgraded your phone to ICS yet...
Click to expand...
Click to collapse
I also have the Gingerbread RUU and yes, it does not work. You were right about the ICS RUU out there somewhere.
I dug deeper into the comments of Football's thread on the Shipped RUU Collection to see if anyone had trouble downloading from FileFactory and somebody requested the Rogers ICS RUU mirror there. I downloaded it any now my cell is back to being operational!
http://forum.xda-developers.com/showthread.php?t=1338919&highlight=football&page=14
Thanks to LaZiODROID, ronnie498,and Gene Poole for all their help!
Well, I also like to make sure I don't make the same mistake again. Anyone know why my phone ended up the way it is?
LeoCFZ said:
I also have the Gingerbread RUU and yes, it does not work. You were right about the ICS RUU out there somewhere.
I dug deeper into the comments of Football's thread on the Shipped RUU Collection to see if anyone had trouble downloading from FileFactory and somebody requested the Rogers ICS RUU mirror there. I downloaded it any now my cell is back to being operational!
http://forum.xda-developers.com/showthread.php?t=1338919&highlight=football&page=14
Thanks to LaZiODROID, ronnie498,and Gene Poole for all their help!
Well, I also like to make sure I don't make the same mistake again. Anyone know why my phone ended up the way it is?
Click to expand...
Click to collapse
Amazing! Glad it worked out. Thanks for that link. I'll be archiving a copy of that Rogers RUU.
As for why your phone wouldnt boot with CM9... Is CM9 still in development? Maybe you should try a different ROM.
I'm using Pegasus right now and enjoying it. (As per kozmik I did have to do an extra step to get my LTE going, but it was pretty easy).
Remember to do a backup and your 4 wipes (data, cache, dalvik,and /system) before you install the rom, of course!
OK, thanks for the tips and the ROM suggestion.
I'll try Pegasus next.
LeoCFZ said:
OK, thanks for the tips and the ROM suggestion.
I'll try Pegasus next.
Click to expand...
Click to collapse
Thanks for this post. I had the same problem and was looking on the site to find an answer....
I uploaded all the RUU's here including the rogers one
http://forum.xda-developers.com/showthread.php?t=2013122
from my HTC PH39100 using xda premium
Here's today's brain teaser of a question: if you have Super CID on, do you need to have the bootloader re-locked in order to run any RUU?
Spazmogen said:
Here's today's brain teaser of a question: if you have Super CID on, do you need to have the bootloader re-locked in order to run any RUU?
Click to expand...
Click to collapse
Yes, I am pretty sure you do. I re-locked mine whenever I had to use a RUU.
HTC Holiday - At&t Vivid
***RELOCKED***
HBOOT-1.85.0024
S-ON RL
CID: CWS_001
Version Installed:
3.26.502.54 710RD
Kernel Version:
3.0.16-gea0e914
[email protected] #1
Baseband:
3.02.4740.14_34.22.701040.19L
Build:
3.25.502.54 CL302737
Issue:
I am trying to return to stock so I can sell this phone. I RELOCKED it using the "fastboot oem relock" and got the famous error message that it failed with "too many links". But it still shows that it is relocked.
When running the RUU with the phone booted it errors out with error 155. When I try and run it through fastboot it just sits on "Sending" and doesn't go anywhere. I had it sit for 12 hours yesterday and it didn't budge.
I've tried these two files, which are the exact same I know...
htc_vivid_att_RUU_3.26.502.56_US.exe
RUU_HOLIDAY_ICS_35_S_Cingular_US_3.26.502.56_Radio_3.02.4740.14_34.22.701040.19_release_246712_signed.exe
I need to re-flash something to it, whenever the damn thing boots up (even after a factory reset) it says "Updating Android". And it says it every time. I can't sell a phone that does that.
I have tried to unlock and lock again. It's been while since I have done this, but I thought it had something to do with the error while re-locking, or the HBOOT version.
I've read some other places that I need to get S-OFF first to be able to return to stock, WTF, unless something has change, I've never had to do that before with this device to return to stock.
**EDIT**
I just tried to go into the recovery to see if there was one still installed and it flashed back to the fastboot screen and now says ***SECURITY WARNING*** under the relock. I have not seen that before.
Squeaky369 said:
HTC Holiday - At&t Vivid
***RELOCKED***
HBOOT-1.85.0024
S-ON RL
CID: CWS_001
Version Installed:
3.26.502.54 710RD
Kernel Version:
3.0.16-gea0e914
[email protected] #1
Baseband:
3.02.4740.14_34.22.701040.19L
Build:
3.25.502.54 CL302737
Issue:
I am trying to return to stock so I can sell this phone. I RELOCKED it using the "fastboot oem relock" and got the famous error message that it failed with "too many links". But it still shows that it is relocked.
When running the RUU with the phone booted it errors out with error 155. When I try and run it through fastboot it just sits on "Sending" and doesn't go anywhere. I had it sit for 12 hours yesterday and it didn't budge.
I've tried these two files, which are the exact same I know...
htc_vivid_att_RUU_3.26.502.56_US.exe
RUU_HOLIDAY_ICS_35_S_Cingular_US_3.26.502.56_Radio_3.02.4740.14_34.22.701040.19_release_246712_signed.exe
I need to re-flash something to it, whenever the damn thing boots up (even after a factory reset) it says "Updating Android". And it says it every time. I can't sell a phone that does that.
I have tried to unlock and lock again. It's been while since I have done this, but I thought it had something to do with the error while re-locking, or the HBOOT version.
I've read some other places that I need to get S-OFF first to be able to return to stock, WTF, unless something has change, I've never had to do that before with this device to return to stock.
**EDIT**
I just tried to go into the recovery to see if there was one still installed and it flashed back to the fastboot screen and now says ***SECURITY WARNING*** under the relock. I have not seen that before.
Click to expand...
Click to collapse
First of all, I must say, THANKS for posting so many details! That makes it much easier to fully understand your issue. I wish everyone would be so concise.
Next, these are errors I have never seen.. This Security Warning is news to me... I wonder if you should maybe try to re-flash the original HBOOT... That is the most risky of all flashes, so I'd maybe wait for someone who has experienced this issue to pipe up before attempting it.
It sounds to me that HBOOT is where your problem lies though. I hope someone else can be of more help on this issue.
ess.boyer said:
First of all, I must say, THANKS for posting so many details! That makes it much easier to fully understand your issue. I wish everyone would be so concise.
Next, these are errors I have never seen.. This Security Warning is news to me... I wonder if you should maybe try to re-flash the original HBOOT... That is the most risky of all flashes, so I'd maybe wait for someone who has experienced this issue to pipe up before attempting it.
It sounds to me that HBOOT is where your problem lies though. I hope someone else can be of more help on this issue.
Click to expand...
Click to collapse
Thank you! I've been around this site for around 4 years now and it's EXTREMELY annoying when searching for answers when someone just posts:
"i cant flash"
Or whatever...
As for the actual issue, that's what I was thinking. There was something awhile back I thought I had read about that version of the HBOOT being an issue. So, hopefully someone around here can help out. I searched for it but I couldn't find anything. So either I am thinking of another phone or it's just lost in the depths of the unknown.
Squeaky369 said:
Thank you! I've been around this site for around 4 years now and it's EXTREMELY annoying when searching for answers when someone just posts:
"i cant flash"
Click to expand...
Click to collapse
Amen to that!
As for the actual issue, that's what I was thinking. There was something awhile back I thought I had read about that version of the HBOOT being an issue. So, hopefully someone around here can help out. I searched for it but I couldn't find anything. So either I am thinking of another phone or it's just lost in the depths of the unknown.
Click to expand...
Click to collapse
I think your best bet may be to just try reflashing the HBOOT. Check Hasoons All-in-one tool kit as I believe it contains the original HBOOT and the one that comes with the S-OFF tools. If it's not there, you should be able to find it somewhere around the forum. Maybe there's a link in the superguide.
Hopefully with a fresh HBOOT, you can get locked, and the RUU will work again. I have flashed the RUU a few times, and each time for me, relocking the bootloader worked fine.
It's worth a whirl.
http://forum.xda-developers.com/showthread.php?t=1416836
SECOND OPTION (PH39IMG.zip flash)
- Put this file for AT&T or this file for Rogers on a microSD card as is (it should be named PH39IMG.zip)
- Power down the phone, insert microSD and boot back into bootloader (power button + vol down)
- It should automatically find the zip file and flash the stock image (this includes recovery, system, everything stock.)
- If you returned to stock because of a bug or issue, and want to root again, make sure to go back and follow the steps PRECISELY to perm root, flash CWM, flash a ROM, flash a kernel, etc. Remember, flash ROM IMMEDIATELY after flashing the kernel
Click to expand...
Click to collapse
ess.boyer said:
Amen to that!
I think your best bet may be to just try reflashing the HBOOT. Check Hasoons All-in-one tool kit as I believe it contains the original HBOOT and the one that comes with the S-OFF tools. If it's not there, you should be able to find it somewhere around the forum. Maybe there's a link in the superguide.
Hopefully with a fresh HBOOT, you can get locked, and the RUU will work again. I have flashed the RUU a few times, and each time for me, relocking the bootloader worked fine.
It's worth a whirl.
Click to expand...
Click to collapse
Ripped the original HBOOT out of the RUU that I had from HTC.
When I try and flash though I get this:
---------------------------------------------------------------------------------------------------------
C:\Android>fastboot flash hboot hboot.nb0
sending 'hboot' (1023 KB)... OKAY [ 0.297s]
writing 'hboot'... FAILED (remote: not allowed)
finished. total time: 0.614s
---------------------------------------------------------------------------------------------------------
I don't need to be S-OFF to flash the HBOOT do I? I unlocked the bootloader again, so that is not what is causing the issue.
Brand New said:
http://forum.xda-developers.com/showthread.php?t=1416836
Click to expand...
Click to collapse
That's the first thread I went through when starting this
I have actually been looking for the PH39IMG.zip file for At&t because that's how I used to do this...
But the file in that link isn't there anymore. It seems that every search I do and find where someone has posted it, it's been removed because of copyright infringement or some other stupid political BS.
Got it.
Created my own PH39IMG.zip using the RUU I got from HTC and got the HBOOT updated and everything returned to stock.
Thank you for the assistance everyone.
Ha! Rocking! Glad you're back up and running.
Squeaky369 said:
Got it.
Created my own PH39IMG.zip using the RUU I got from HTC and got the HBOOT updated and everything returned to stock.
Thank you for the assistance everyone.
Click to expand...
Click to collapse
I am having the exact same issue. Any chance you could share that PH39IMG.zip you made or explain how you did it?
I'll be putting the links up for the PH39IMG.zip in the next hour or so
---------- Post added at 11:36 AM ---------- Previous post was at 11:30 AM ----------
For both AT&T and Rogers Ripped straight from the RUU
Hi Guys,
1 month ago I chaged my HTC ONE into Google Play Edition. Then Yesterday I wanted to get it to stock sense.
What I did:
*) restore CID to HTC__032 (do not know if it is right CID, network: P4 play for Poland)
*) restore stock via TWRP
*) downgrade bootloader from 1.54 to 1.44
*) locked (reveone)
*) S-On
Now, my phone got always bootoader with a msg: "Security Warrinig"
Canno go to recovery - phone always reboots. System doesn't start.
I'm assuming that to repair my phone the first thing I have to do is S-OFF. I cannot do this via HTCDEV unlock file, every time when i fire "fastboot flash unlocktoken unlock_code.bin"
file is successfully sent and that's all. "Swipe - unlock" screen doesn't appear. As we know ADB PUSH won't work in fastboot mode.
How I can transfer reveone file into internal storage to get my phone s-Off again and corretley flash a bootloader (1.54)?
Regards.
rwachowiak said:
Hi Guys,
1 month ago I chaged my HTC ONE into Google Play Edition. Then Yesterday I wanted to get it to stock sense.
What I did:
*) restore CID to HTC__032 (do not know if it is right CID, network: P4 play for Poland)
*) restore stock via TWRP
*) downgrade bootloader from 1.54 to 1.44
*) locked (reveone)
*) S-On
Now, my phone got always bootoader with a msg: "Security Warrinig"
Canno go to recovery - phone always reboots. System doesn't start.
I'm assuming that to repair my phone the first thing I have to do is S-OFF. I cannot do this via HTCDEV unlock file, every time when i fire "fastboot flash unlocktoken unlock_code.bin"
file is successfully sent and that's all. "Swipe - unlock" screen doesn't appear. As we know ADB PUSH won't work in fastboot mode.
How I can transfer reveone file into internal storage to get my phone s-Off again and corretley flash a bootloader (1.54)?
Regards.
Click to expand...
Click to collapse
so let me get this straight:
1- S-On
2- LOCKED
3- No functioning ROM
if yes, you're pretty much stuck
did you get a new unlocktoken from HTCdev or are you using the old one. try registering a new account with HTCdev and get a new unlock file.
nkk71 said:
so let me get this straight:
1- S-On
2- LOCKED
3- No functioning ROM
if yes, you're pretty much stuck
did you get a new unlocktoken from HTCdev or are you using the old one. try registering a new account with HTCdev and get a new unlock file.
Click to expand...
Click to collapse
yes, I have tried - no success.
At first, the HTC Dev Unlock does NOT give you S-Off. It just unlocks your bootloader. And why did you change your CID if you didnt know if it was the right one? Google will help you to find the right one.
In case this IS the right one, I dont think you need S-Off as you're able to flash a new Recovery without S-Off. Try HTC aio Tool for example or via adb/fastboot flash. If this worked you'll be able to flash a new firmware.
Good Luck
http://xda7.androidrevolution.nl/db_mirror/Grafika/Sygnatura/User_banners/atticus182-2.png
Gesendet von meinem HTC One mit Tapatalk
rwachowiak said:
yes, I have tried - no success.
Click to expand...
Click to collapse
did you try with a new email account?
So you were s-off before then back to s-on. Or how you downgraded from 1.54 to 1.44 ? I am confused now
Sent from my HTC One using xda app-developers app
Thank's for all your responses.
So:
@nkk71 - tried with new account - still no success.
@Frask3r - as long as I'm not able to run anything except bootloader: adb commant won't work(no way to perform push), fastboot only works.
@polariscon - I wanted to flash my googles' bootloader with the orginal one from HTC, so I flashed via fastboot.
I can confirm that CID is correct one HTC__032. I do not know if it will help.
You can flash with fastboot commands
http://xda7.androidrevolution.nl/db_mirror/Grafika/Sygnatura/User_banners/atticus182-2.png
Gesendet von meinem HTC One mit Tapatalk
Frask3r said:
You can flash with fastboot commands
Click to expand...
Click to collapse
Ok.. so to do it, I need: RUU 1.29.401.12 Radio 4A.18.32.63.15 for model PN0710000.
This software version I have installed on my HTC ONE. As far as I know I cannot flash it with any other RUU.
Am I correct?
Regards.
rwachowiak said:
Ok.. so to do it, I need: RUU 1.29.401.12 Radio 4A.18.32.63.15 for model PN0710000.
This software version I have installed on my HTC ONE. As far as I know I cannot flash it with any other RUU.
Am I correct?
Regards.
Click to expand...
Click to collapse
oh I just saw you downgraded to 1.44, try an RUU (windows exe) from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
which is compatible with your MID & CID (use fastboot getvar all, to determine MID & CID)
Hello.
I need help to fix my htc one.
I did delete everything on my internal sdcard. Cause i want to make it as new to give it to my girlfriend. But when i did that. Its stopped working. I've tried to use all in one kit by squabbi. But it won't work to change boot or anything. Maybe i did smt wrong.
When i turn on my htc one. Its stuck in boot. White screen with htc logo on it. I cant even turn it off again. I have to wait when the battery its empty. And then i can turn it on to fastboot. Before all that. I came into recovery and then its stands no OS on the phone.
But after i yried to fix it by myself then it will not be able to even touch the recovery. I push the screen,but nothing happend. I think i did it worse or smt. Pleas help if somebody can. It would be great.
Sent from my C6603 using XDA Premium HD app
Sent from my C6603 using XDA Premium 4 mobile app
nkk71 said:
oh I just saw you downgraded to 1.44, try an RUU (windows exe) from here...
which is compatible with your MID & CID (use fastboot getvar all, to determine MID & CID)
Click to expand...
Click to collapse
Thanks nkk71. I will try this, but I'm not to sure if I can do it without S-OFF especialy when I have a higher firmware version installed (1.29.401.12). I will let you know as soon as I'm done.
rwachowiak said:
Thanks nkk71. I will try this, but I'm not to sure if I can do it without S-OFF especialy when I have a higher firmware version installed (1.29.401.12). I will let you know as soon as I'm done.
Click to expand...
Click to collapse
if the ruu.exe doesnt work, then there's this: http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
flashable with s-on and locked using fastboot in RUU mode, let me know if you need the exact commands and remember the flash zip has to be done twice, one after another!!
rwachowiak said:
Thanks nkk71. I will try this, but I'm not to sure if I can do it without S-OFF especialy when I have a higher firmware version installed (1.29.401.12). I will let you know as soon as I'm done.
Click to expand...
Click to collapse
doesn't work:
updating signature....
error[140] bootloader version error
I will try with dectypted version.
nkk71 said:
if the ruu.exe doesnt work, then there's this: http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
flashable with s-on and locked using fastboot in RUU mode, let me know if you need the exact commands and remember the flash zip has to be done twice, one after another!!
Click to expand...
Click to collapse
Doesn't work.
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
system msg:
FAILED (remote:12 signature verify fail)
Any suggestions?
rwachowiak said:
Doesn't work.
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
system msg:
FAILED (remote:12 signature verify fail)
Any suggestions?
Click to expand...
Click to collapse
After reading OP i think you have many things mixed up so plz clarify
What happens when you try to boot into recovery...if its stock recovery it takes some time for red triangle to appear.
Which "swipe-unlock" screen are you talking about in unlocking bootloader.
When using RUU zip try more than once sometimes it takes 2 - 3 tries to work
grayhawk11 said:
After reading OP i think you have many things mixed up so plz clarify
What happens when you try to boot into recovery...if its stock recovery it takes some time for red triangle to appear.
Which "swipe-unlock" screen are you talking about in unlocking bootloader.
When using RUU zip try more than once sometimes it takes 2 - 3 tries to work
Click to expand...
Click to collapse
so..
What happens when you try to boot into recovery... phone reboots to bootloader mode
Which "swipe-unlock" screen are you talking about in unlocking bootloader.fastboot flash unlocktoken Unlock_code.bin
When using RUU zip try more than once sometimes it takes 2 - 3 tries to work -I have tried more then 5 times
I think that my bootloader is corrupted...
rwachowiak said:
so..
What happens when you try to boot into recovery... phone reboots to bootloader mode
Which "swipe-unlock" screen are you talking about in unlocking bootloader.fastboot flash unlocktoken Unlock_code.bin
When using RUU zip try more than once sometimes it takes 2 - 3 tries to work -I have tried more then 5 times
I think that my bootloader is corrupted...
Click to expand...
Click to collapse
But you can still boot into hboot so it might not be all lost
When was the last time you able to boot normally (after each steps you mentioned in OP)
I'm Sorry for answering so late. My phone just came back from "local" GSM repair center.
So what they done?
They destroyed my back cover and using JTAG changed cid to: HTC_02_2 and version-main to 1.00.000.00
and they told me that I'm not able to flash my phone with any current ROM version because I have to wait for
the latest one.
I have tried to update my phone with RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe on my own.
I changed my cid in android-info.txt but after "signatures checking" step i received error msg no 131 (customer id)
Now I'm wondering, if I will procceed with below steps:
*) change cid to: 11111111 (using JTAG)
*) still s-on (i cannot change it - bootloop)
*) bootloader locked
are there any chances to make it works again?
Cheers
Robert
Can you unlock bootloader, flash custom recovery, root, and install a custom rom?
Then S-Off, and move to a HTC__001 based International HTC One RUU file.
What is your hboot version? or fastboot getvar all output?