My findings for Google Keyboard FC and different CIDs - One (M7) General

Ok so since I didn't get an answer in the Q&A section (126+ views) I figured I'd try a few things. I noticed the other day when I switched my CID to HTC__001 from CWS__001 when I rebooted I got a Google Keyboard FC. So I went through and tested 3 Hex edit CIDs with 3 different fastboot CIDs and these are the results:
The fastboot CIDs will be listed under the Hex ones that I tried. I'll put Yes if Google Keyboard worked and No if it FC'ed
Hex = CWS__001 (AT&T)
Fastboot CWS__001 - Yes
Fastboot 11111111 - Yes
Fastboot HTC__001 - No
Hex = HTC__001 (WWE)
Fastboot CWS__001 - Yes
Fastboot 11111111 - No
Fastboot HTC__001 - No
Hex = 11111111 (supercid)
Fastboot CWS__001 - Yes
Fastboot 11111111 - Yes
Fastboot HTC__001 - No
There have been quite a few posts that say there is no need to change the CID value (hex edit) in mmcblk0p19 but obviously it has some effect on at least one app. Also if you make your CID supercid through fastboot and your mmcblk0p19 is AT&T then the LTE icons are stock AT&T which is also true if you make mmcblk0p19 supercid and fasboot CID AT&T.
Can someone with more knowledge try to make sense of this? How come Google Keyboard won't work with anything HTC_001? I've done a full wipe and everything.
FWIW I'm using an AT&T HTC One. I flashed the Droid DNA eng-hboot and changed my model ID to PN0710000. After that I flashed back the 1.44 hboot from the One. I then changed my CID in both places to HTC__001 and flashed the 2.17 FW that mike posted.

SkizzMcNizz said:
Ok so since I didn't get an answer in the Q&A section (126+ views) I figured I'd try a few things. I noticed the other day when I switched my CID to HTC__001 from CWS__001 when I rebooted I got a Google Keyboard FC. So I went through and tested 3 Hex edit CIDs with 3 different fastboot CIDs and these are the results:
The fastboot CIDs will be listed under the Hex ones that I tried. I'll put Yes if Google Keyboard worked and No if it FC'ed
Hex = CWS__001 (AT&T)
Fastboot CWS__001 - Yes
Fastboot 11111111 - Yes
Fastboot HTC__001 - No
Hex = HTC__001 (WWE)
Fastboot CWS__001 - Yes
Fastboot 11111111 - No
Fastboot HTC__001 - No
Hex = 11111111 (supercid)
Fastboot CWS__001 - Yes
Fastboot 11111111 - Yes
Fastboot HTC__001 - No
There have been quite a few posts that say there is no need to change the CID value (hex edit) in mmcblk0p19 but obviously it has some effect on at least one app. Also if you make your CID supercid through fastboot and your mmcblk0p19 is AT&T then the LTE icons are stock AT&T which is also true if you make mmcblk0p19 supercid and fasboot CID AT&T.
Can someone with more knowledge try to make sense of this? How come Google Keyboard won't work with anything HTC_001? I've done a full wipe and everything.
FWIW I'm using an AT&T HTC One. I flashed the Droid DNA eng-hboot and changed my model ID to PN0710000. After that I flashed back the 1.44 hboot from the One. I then changed my CID in both places to HTC__001 and flashed the 2.17 FW that mike posted.
Click to expand...
Click to collapse
I've never had a google keyboard FC, and i've tried all of the cids you've mentioned with fastboot oem writecid. Maybe no one else has either, hence the lack of replies? Of course i've never hex edited any cid location so thats probably why. This looks to me like another reason NOT to hex edit, no errors when just doing fastboot cid.

I replied to the last thread!
Sent from my HTC One using xda premium

SkizzMcNizz said:
Ok so since I didn't get an answer in the Q&A section (126+ views) I figured I'd try a few things. I noticed the other day when I switched my CID to HTC__001 from CWS__001 when I rebooted I got a Google Keyboard FC. So I went through and tested 3 Hex edit CIDs with 3 different fastboot CIDs and these are the results:
The fastboot CIDs will be listed under the Hex ones that I tried. I'll put Yes if Google Keyboard worked and No if it FC'ed
Hex = CWS__001 (AT&T)
Fastboot CWS__001 - Yes
Fastboot 11111111 - Yes
Fastboot HTC__001 - No
Hex = HTC__001 (WWE)
Fastboot CWS__001 - Yes
Fastboot 11111111 - No
Fastboot HTC__001 - No
Hex = 11111111 (supercid)
Fastboot CWS__001 - Yes
Fastboot 11111111 - Yes
Fastboot HTC__001 - No
There have been quite a few posts that say there is no need to change the CID value (hex edit) in mmcblk0p19 but obviously it has some effect on at least one app. Also if you make your CID supercid through fastboot and your mmcblk0p19 is AT&T then the LTE icons are stock AT&T which is also true if you make mmcblk0p19 supercid and fasboot CID AT&T.
Can someone with more knowledge try to make sense of this? How come Google Keyboard won't work with anything HTC_001? I've done a full wipe and everything.
FWIW I'm using an AT&T HTC One. I flashed the Droid DNA eng-hboot and changed my model ID to PN0710000. After that I flashed back the 1.44 hboot from the One. I then changed my CID in both places to HTC__001 and flashed the 2.17 FW that mike posted.
Click to expand...
Click to collapse
I have an ATT One with SuperCID from fastboot oem and the hex edit in mm, and have never had a google keyboard FC.

I Have HTC_001 and I get FC's too. Ive tried 2 different roms, wiped and started fresh each time, including installig the keyboard first, but no dice. Constantly fc's. Only on 4.2.2 though, it worked fine before I upgraded...

To those getting FC's :
have you cleared cache & data for the Keyboard every time you changed CID/ROM's?
If not try it & post results. May be just some basic cache/ app data problem.

Tried that numerous times, still no luck...
x017in said:
To those getting FC's :
have you cleared cache & data for the Keyboard every time you changed CID/ROM's?
If not try it & post results. May be just some basic cache/ app data problem.
Click to expand...
Click to collapse

Posted in the other thread as well. Had issues with the HTC__001 cid as well. Changed it to the US Dev edition and now it works fine. I have done no hex editing. U

nugzo said:
I've never had a google keyboard FC, and i've tried all of the cids you've mentioned with fastboot oem writecid. Maybe no one else has either, hence the lack of replies? Of course i've never hex edited any cid location so thats probably why. This looks to me like another reason NOT to hex edit, no errors when just doing fastboot cid.
Click to expand...
Click to collapse
Download the official Google Keyboard and then change your CID to HTC__001 and reboot to see if it FC'S.
I never would have changed my CID through hex edit but I saw a post saying that we needed to and it wasn't until after I did it that other people started posting saying that person was wrong. =/
It shouldn't matter though because I changed it back to what it was. And like I said the hex edit also affects the LTE icons whether you have supercid or not. I wish there was a way to go completely back to stock. Something that wrote the mmcblk0p19 to what it was originally become any edits.
P.S. I've only tried this on ARHD 10.2. Had anyone who had this happen been on a different rom?
Sent from my HTC One using xda app-developers app

spitfire2425 said:
I replied to the last thread!
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Not before I posted this lol.
Sent from my HTC One using xda app-developers app

x017in said:
To those getting FC's :
have you cleared cache & data for the Keyboard every time you changed CID/ROM's?
If not try it & post results. May be just some basic cache/ app data problem.
Click to expand...
Click to collapse
Yes tried everything, full wipe, etc.
Sent from my HTC One using xda app-developers app

i dont get how changing the CID affects the apps, is it something to do with detecting regions?

I guess maybe i'm confused about the official google keyboard. i thought the keyboard you spoke of was what comes with the rom, i'll check the download version.

just go ahead and change the MID as well. with ENG-hboot. super cid is just doing half the job. no fc's ever converted AT&T to HTC__001 and changed MID to PN0710000. full wipe and RUU install

ATT htc one with supercid from fstbvoot and bs_us001 hexeditied and no google keyboard issues. I am on android revoluition hd 10.3.

tjsooley said:
ATT htc one with supercid from fstbvoot and bs_us001 hexeditied and no google keyboard issues. I am on android revoluition hd 10.3.
Click to expand...
Click to collapse
Its only HTC__001.
Sent from my Nexus 7 using XDA Premium HD app

daddioj said:
just go ahead and change the MID as well. with ENG-hboot. super cid is just doing half the job. no fc's ever converted AT&T to HTC__001 and changed MID to PN0710000. full wipe and RUU install
Click to expand...
Click to collapse
I did it says that in the OP.
Sent from my Nexus 7 using XDA Premium HD app

Off topic: I have HTC_001 and haven't changed my CID but I have noticed if I use any other theme apart from the stock AOSP theme the keyboard becomes transparent. Am using rootbox

I don't know I don't have any of these issues. when I did have ENG hboot. I wiped the phone completely from the radio to the recovery then flashed RUU

daddioj said:
I don't know I don't have any of these issues. when I did have ENG hboot. I wiped the phone completely from the radio to the recovery then flashed RUU
Click to expand...
Click to collapse
Have you switched your CID to HTC__001, downloaded the Official Google Keyboard, and tried to open it?
If you haven't done exactly that then please don't post saying it's not happening to you.
Sent from my HTC One using xda app-developers app

Related

[Q] Restoring stock ROM / factory reset

I just got a new Xperia X10 (yay!) and am happily enjoying a mod on it. Now it's time to send back the old clunky Magic. Head office is going to use it as a spare device and I'd like to restore it to a stock ROM as I'd prefer not to have to answer questions about "what is this crazy things you've downloaded a virus and it's eating the intertubes etc etc.
I've looked around but I can't find much info about restoring it to stock. A few posts talk about either restoring original nandroid backup or flashing a new SPL? Unfortunately I really screwed up my original rooting and flashing processes, and wasn't able to get a nandroid backup of the stock rom, though I did end up getting it working.
And I'm not sure what SPL I need to flash, or other details. I really just want to run the factory reset from this page but it can't detect the phone.
Any advice?
It's a Magic from Rogers (Canada), running CM6.0 with the following information in fastboot:
Code:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP50000)
CPLD-12
RADIO-3.22.20.17
Jun 2 2009,17:27:03
Thanks!
-aaziz
you could choose one of the ROMS on this link
http://forum.xda-developers.com/showthread.php?t=659403
frequenzy21 said:
you could choose one of the ROMS on this link
http://forum.xda-developers.com/showthread.php?t=659403
Click to expand...
Click to collapse
Thanks - I tried both of the Rogers RUU programs but both tell me the cannot detect the device. I've tried when it was on, in fastboot, and in recovery image.
Advice?
Don't flash anything....
First, post here the outcome of these commands:
Code:
fastboot getvar version-main
fastboot getvar cid
Then i will give you the right sappimg.zip to flash...
Again, don't flash anything.. you got eng spl and it a VERY good thing to have until you get the right image files..
mumilover said:
Don't flash anything....
First, post here the outcome of these commands:
Code:
fastboot getvar version-main
fastboot getvar cid
Then i will give you the right sappimg.zip to flash...
Again, don't flash anything.. you got eng spl and it a VERY good thing to have until you get the right image files..
Click to expand...
Click to collapse
version-main: 2.17.631.2
cid: ROGER001****"
Where **** is a bunch of non-ASCII characters, and I can't seem to copy anything in my console window :S
Download my fastboot command from my signature.
Also do this:
Code:
fastboot oem rebootRUU
Then try one of the official RUU.
If it does not work, then i'll have a solution within 5 min...
But give it a try.
No luck with that. I assume I was supposed to run the RUU when the "RUU USB" text was displayed on the phone?
Did you download the fastboot commander?
Download this image:
https://rapidshare.com/files/458228220/2.17.631.2.zip
Use the "Full zip" tab in fastboot commander.
Navigate to where you downloaded the above image and select it.
Then just flash and KEEP patient.
If you want, take a look at the "Actual tab" or look at your device..
Once this has finished, you should have STOCK rom, recovery, radio and spl.
Yes sir, I have it open now... ("magic" version, correct?)
EDIT: Thanks... waiting for slow as hell Rapidshare now.
EDIT: double post
It worked now! Thanks, Sir!
Oh, man, it's all the way back to 1.5. It's like a punch of nostalgia.
I cannot, however, use the RUU flashers from Rogers to update the OS. Not a big deal, actually, since it's now stock and they can worry about updating it, but it would be nice.
aaziz said:
I cannot, however, use the RUU flashers from Rogers to update the OS. Not a big deal, actually, since it's now stock and they can worry about updating it, but it would be nice.
Click to expand...
Click to collapse
Just do *#*#checkin#*#* then go to the Update option in the settings menu. Should be able to just do the regular update process.
Sent from my HTC Glacier using Tapatalk
DonJuan692006 said:
Just do *#*#checkin#*#* then go to the Update option in the settings menu. Should be able to just do the regular update process.
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
I... I don't know this *#*#checkin#*#* bit perhaps you could enlighten me?
EDIT: I assumed that this was a dialer type code... research verifies this. Now do I type that in with the keyboard, or use the phone dialpad to type those characters? (so 2 for a, b, or c, etc)
aaziz said:
I... I don't know this *#*#checkin#*#* bit perhaps you could enlighten me?
EDIT: I assumed that this was a dialer type code... research verifies this. Now do I type that in with the keyboard, or use the phone dialpad to type those characters? (so 2 for a, b, or c, etc)
Click to expand...
Click to collapse
Yep you do it using the phones dialer. Just like calling 1800geico or something.
Sent from my HTC Glacier using Tapatalk
DonJuan692006 said:
Just do *#*#checkin#*#* then go to the Update option in the settings menu. Should be able to just do the regular update process.
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
I've just followed the procedure outlined in this thread. I also can't update using RUU, and there's no 'Update' option in the settings menu in 1.5 (not even in the 'About Phone').
Is there a more recent image I could flash that would have OTA Update abilities?
Tried Fastboot Commander Method - Bricked
mumilover said:
Use the "Full zip" tab in fastboot commander.
Navigate to where you downloaded the above image and select it.
Then just flash and KEEP patient.
If you want, take a look at the "Actual tab" or look at your device..
Once this has finished, you should have STOCK rom, recovery, radio and spl.
Click to expand...
Click to collapse
I tried the Fastboot Commander method as per mumilover's instructions. Everything worked fine until it was flashing the zip. The bootloader showed that some sections ie. /system didn't flash properly. Now the phone won't even turn on. No bootloader, no recovery, not even Rogers splash screen. Any advice?

Having trouble getting s-off

I have rooted my G2. I installed Cyanogen 7, but then decided I should get s-off. So I followed the tutorial here http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Unlock_the_Phone.2C_Set_SuperCID.2C_and_Turn_Radio_S-OFF
But I get the following output
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.35.10-gb351ce5
New .modinfo section size: 204
Attempting to power cycle eMMC... Failed.
Module failed to load: No such file or directory
And when I try to verify, it hasn't worked. I know the tutorial said that some kernels didn't work, so I tried it with xboarders pure/stock mix and I get the same result.
Any help would be greatly appreciated.
May be wrong but I think you needed to get s-off before changing roms?
Sent from my T-Mobile G2 using XDA Premium App
Do you mean I have to have a stock os? I hope not cause I don't feel like resetting everything and doing it all over again.
Maybe plain old root is good enough.
I think he means to flash roms you need s-off, so chances are you may already have it. check by turning off your phone,hold volume down and click power and it should load into the bootloader and say either s-off or s-on
Sent from my HTC Desire Z using XDA App
gfree does not work with CM's kernel.
Guess I do have S-Off
xT4Z1N4TRx said:
I think he means to flash roms you need s-off, so chances are you may already have it. check by turning off your phone,hold volume down and click power and it should load into the bootloader and say either s-off or s-on
Sent from my HTC Desire Z using XDA App
Click to expand...
Click to collapse
Hmmm...you seem to have found something there. I did boot into Hboot and at the top it actually does say "Vision PVT ENG S-Off"
I guess that means I have S-off, right? But do I have the CID off and the SIMlock off as well? This is all so complicated.
Techngro said:
Hmmm...you seem to have found something there. I did boot into Hboot and at the top it actually does say "Vision PVT ENG S-Off"
I guess that means I have S-off, right? But do I have the CID off and the SIMlock off as well? This is all so complicated.
Click to expand...
Click to collapse
Honestly I'm not sure. Don't take my word for it, let someone else confirm, but u might be best just installing the tmobile stock RUU NOT JUST ROM, reset everything and start over. Most people do all these steps with gfree and such on the stock rom. That is the way it was written to be done anyway. At this point it seems you have a hodge podge of some stuff unlocked some stuff not. Just put it back to 100% stock with an ruu that will take EVERYTHING back. But NOT A NEWER RUU. We will have to get clarification on which one u should use. Someone with more knowledge may be able to help you without backtracking so much, but that is my idea.
Sent from my T-Mobile G2 using XDA Premium App

[Q] Rooted MT3G with CyanogenMod almost bricked

Sorry for creating new thread if there is some solution available on this. But I have searched everywhere and tried lot of things nothing works
Here is my hboot info
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0007 (SAPP30000)
CPLD-10
RADIO-2.22.23.02
JUL 31 2009, 15:49:25
I had CyanogenMod 6 which became slow so I tried to reboot in recovery while USB was connected it didnt get into recovery mode and after reboot its stuck on CyanogenMod boot logo. When I try home + power it boots without going into recover mode and gets stuck in boot loop of CyanogenMod screen. I kept it on till the battery drained (almost 8 hrs 2-3 times) so dont think its issue with keeping it on for longer time.
So far I have tried all possible spamming.zip and spamming.nbh none of them work either get wrong model ID or update failed. I am not able to log in through ADB. adb devices doesnt show me any devices. But when i try fastboot devices i see my phone. But i can not push anything it says remote not allowed.
I tried goldcard but I cant get to the system files so cant swap the hex digits to create goldcard. I know someone would have a better idea.
Need some help from the experts .. please. Its been more than 2 weeks trying out all possible solutions but no luck.
Can you still boot into the rom you had installed?
Sent from my shad0w's sapphire using XDA Premium App
tvall said:
Can you still boot into the rom you had installed?
Sent from my shad0w's sapphire using XDA Premium App
Click to expand...
Click to collapse
If you mean boot and start the phone no I am not able to do that it gets stuck on cyanogen boot screen. I am able to boot in HBOOT and FASTBOOT though.
Have u tried fastboot flashing a new recovery? Just to see if u lost it somehow then try to boot into it.
Sent from my HTC Magic using XDA App
johnson8cyl said:
Have u tried fastboot flashing a new recovery? Just to see if u lost it somehow then try to boot into it.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
He has s-on. If he could do that then this would be easy to fix
Sent from my shad0w's sapphire using XDA Premium App
Oh yeah. You're correct....... duh. Can he use someone else's gold card?
Sent from my HTC Magic using XDA App
happened to my mytouch 3g
it happened to me last week like that, the only thing that saves my was run the 1.5 SAPPIMG.nbh so i'm back to stock again then re-do everything allover
danxtian said:
it happened to me last week like that, the only thing that saves my was run the 1.5 SAPPIMG.nbh so i'm back to stock again then re-do everything allover
Click to expand...
Click to collapse
Can you point me to the file? I have used lots of sappimg.nbh so far none worked so dont mind trying this one. Hope thats the solution for me.
johnson8cyl said:
Have u tried fastboot flashing a new recovery? Just to see if u lost it somehow then try to boot into it.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
No it says remote not allowed.
Rambad said:
Can you point me to the file? I have used lots of sappimg.nbh so far none worked so dont mind trying this one. Hope thats the solution for me.
Click to expand...
Click to collapse
for the old mytouch 3g
http://www.megaupload.com/?d=DQWW0Y9N
for mytouch 1.2
http://www.4shared.com/file/E2zhvzIr/SAPPIMG_Sapphire_T-Mobile_US_2.html
i got them from theunlockr website, hope they works for you..
danxtian said:
for the old mytouch 3g
http://www.megaupload.com/?d=DQWW0Y9N
for mytouch 1.2
http://www.4shared.com/file/E2zhvzIr/SAPPIMG_Sapphire_T-Mobile_US_2.html
i got them from theunlockr website, hope they works for you..
Click to expand...
Click to collapse
Tried again I get Main version older for original and model ID incorrect with mytouch 1.2
ooow sorry to hear that, well i guess you will need to get a goldcard..
danxtian said:
ooow sorry to hear that, well i guess you will need to get a goldcard..
Click to expand...
Click to collapse
I am unable to do that because I cant see my device in adb. Is there some way I can send my phone to t-mobile or htc and they can reset to factory setting? I am surprised that there is not a way to just flash rom with factory settings.
do you know anybody that have a HTC phone? i'm pretty sure some of your friends have one coz HTC phone are almost everywhere nowadays
Simple.... run these commands to establish your current status.
Based on your answers, i can properly asses your situation.
Code:
fastboot getvar version-main
fastboot getvar cid
Maybe we can fix this without the use of goldcard.
mumilover said:
Simple.... run these commands to establish your current status.
Based on your answers, i can properly asses your situation.
Code:
fastboot getvar version-main
fastboot getvar cid
Maybe we can fix this without the use of goldcard.
Click to expand...
Click to collapse
Thanks for your help, this is what I see. Fingers crossed
version-main: 1.92.531.1
cid: T-MOB010_Y∞²
Please recheck that version nr... you are sure its 1.92 or is it 1.94?
Download this:
https://rapidshare.com/files/433519738/1.94.531.1.nbh
rename it to sappimg.nbh
But it on the sdcard and flash it using hboot mode (hold volume - and power together. The "-" sign symbolize decrease of volume).
It should get you back to stock :0)
mumilover said:
Download this:
https://rapidshare.com/files/433519738/1.94.531.1.nbh
rename it to sappimg.nbh
But it on the sdcard and flash it using hboot mode (hold volume - and power together. The "-" sign symbolize decrease of volume).
It should get you back to stock :0)
Click to expand...
Click to collapse
You are the man (or Women) it worked smooth I am now back on 2.2 with official t-mobile update. I hope this helps others who are still looking for a solution.

Update hboot

Hello,
I want only to update my hboot from 0.80.0007 to 1.01.0001
Nothing else, only hboot so i can s-off
Im currently rooted with cwm and cm7
Does anyone know if it is posibel to only update my hboot?
Sent from my HTC Wildfire using Tapatalk
I thought about this as well as I have the same hboot but I s-offed with xtc clip. But you would need to run a ruu man. And then run revolutionary and then restore your nandroid back up of your cyanogenmod. I didn't as the update hboot did nothing for me but I'm pretty sure that's how you would do it. No guarantees though :-/
Sent from my HTC Wildfire using XDA App
Is there not a way to extract the hboot from the ruu and then update it?
Sent from my HTC Wildfire using Tapatalk
i dont think so. the ruu only signs the hboot for use when its running so if its not in the ruu the phone wont accept it. :/ i dont know of any other method than using a ruu, but would love to see if anyone else knew a way to do it
Can you delete the rest other then de hboot from the ruu then?
Sent from my HTC Wildfire using Tapatalk
I suppose you could try but I don't know how the ruu would react to it, or even if it does that first. lf you were to delete the rest of it and say the ruu wiped your phone before doing the hboot you could end up stuck with s-on with no rom on your phone....
sent from my steroid powered, cyanogenmod filled wrecking machine! using xda app.
ok I have now extracted the rom.zip out of the ruu.exe
and unpacked the zip,
the folowing files are interesting in it:
hboot_7225_1.01.0001_101117.nb0
splash1.nb0
, what should i do now,
how do i flash it??
Delete what you don't want and rename the zip to PC49IMG.zip drop it on your SD card and reboot into hboot, volume down and power wait for it to load up press volume up wait again and press power to reboot and it should be done.
Sent from my HTC Wildfire using xda premium
Ok thanks, was a little thinking about that already. My brain was thinking aaa because of the extention of the hboot file,
Going to try that Tomorrow or at the end of the week
Sent from my HTC Wildfire using Tapatalk
i was thinking about 2 things
first, the signing (its still s-on so it should be signed (with the key from htc witch noone knows) does the zip also needs to be signed? or just the files within it?(hboot)
second, does the hboot image also format my other partitions (could be posible if you think about this, there are roms in .nb0 format)
Scratch0805 said:
Delete what you don't want and rename the zip to PC49IMG.zip drop it on your SD card and reboot into hboot, volume down and power wait for it to load up press volume up wait again and press power to reboot and it should be done.
Click to expand...
Click to collapse
uh delete from the orginal rom.zip wont work, it gives me an error (winrar: unrecovereble archive, 7-zip: not implemented)(i guess the rom.zip has to be signed or secured but have unpacked it so i can repack what i need but still those 2 questions
topjor said:
i was thinking about 2 things
first, the signing (its still s-on so it should be signed (with the key from htc witch noone knows) does the zip also needs to be signed? or just the files within it?(hboot)
second, does the hboot image also format my other partitions (could be posible if you think about this, there are roms in .nb0 format)
Click to expand...
Click to collapse
i see there is a file: android_info.txt
Code:
modelid: PC4910000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
mainver: 2.22.405.1
hbootpreupdate:12
DelCache: 1
i think i also need to delete some lines of the cidnum's but there are 10 cidnum's and 9 files in the zip
topjor said:
uh delete from the orginal rom.zip wont work, it gives me an error (winrar: unrecovereble archive, 7-zip: not implemented)(i guess the rom.zip has to be signed or secured but have unpacked it so i can repack what i need but still those 2 questions
i see there is a file: android_info.txt
Code:
modelid: PC4910000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
mainver: 2.22.405.1
hbootpreupdate:12
DelCache: 1
i think i also need to delete some lines of the cidnum's but there are 10 cidnum's and 9 files in the zip
Click to expand...
Click to collapse
Extract, delete what you don't want, leave the txt file completely alone then rezip and call it PC49IMG.zip. it doesn't need signing.
Sent from my HTC Wildfire using xda premium
u can use this to update http://forum.xda-developers.com/showthread.php?t=1160251 u can change to any hboot if you want. but if you have s on and want s off just flash froyo ruu, and then rev.
rolks said:
u can use this to update http://forum.xda-developers.com/showthread.php?t=1160251 u can change to any hboot if you want. but if you have s on and want s off just flash froyo ruu, and then rev.
Click to expand...
Click to collapse
Read the op I ONLY WANT TO UPDATE HBOOT so i can s-off
Sent from my HTC Wildfire using Tapatalk
hello again man. did you have any luck? oh btw htcdev have released a bootloader unlock for the wildfire, im not sure if you`ll need to update the whole rom but it says it just needs a hboot update. might be worth a look.
Scratch0805 said:
Extract, delete what you don't want, leave the txt file completely alone then rezip and call it PC49IMG.zip. it doesn't need signing.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
No signing neded would mean that you could flash every rom with s-on
Sent from my HTC Wildfire using Tapatalk
heavy_metal_man said:
hello again man. did you have any luck? oh btw htcdev have released a bootloader unlock for the wildfire, im not sure if you`ll need to update the whole rom but it says it just needs a hboot update. might be worth a look.
Click to expand...
Click to collapse
That's what I want, only update hboot, but I only have one problem now, wil the hboot.nb0 format the rest of the partitions because that would brick my phone
Edit:
Ps I want revolutionary hboot
And the official unlocker wil notify HTC I beleave
Sent from my HTC Wildfire using Tapatalk
topjor said:
No signing neded would mean that you could flash every rom with s-on
Sent from my HTC Wildfire using Tapatalk
Click to expand...
Click to collapse
No custom roms are different to ruu's, they need signing and flashing through cwm, I've used the PC49IMG method to update hboot plenty of times just delete what you don't want i.e radio, recovery, rom splash etc so you're left with hboot and the txt file then zip it up as I've said above after you reboot go back to hboot and you will have the upgraded one.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
No custom roms are different to ruu's, they need signing and flashing through cwm, I've used the PC49IMG method to update hboot plenty of times just delete what you don't want i.e radio, recovery, rom splash etc so you're left with hboot and the txt file then zip it up as I've said above after you reboot go back to hboot and you will have the upgraded one.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Does that work on s-on.
Just to br sure
Sent from my HTC Wildfire using Tapatalk
topjor said:
Does that work on s-on.
Just to br sure
Sent from my HTC Wildfire using Tapatalk
Click to expand...
Click to collapse
Oh.....maybe not as the partitions will be locked it wouldn't have harmed your phone though as the partition is locked, I never thought of that.
In that case you should try simply running the ruu instead of PC49IMG method.
Sent from my HTC Wildfire using xda premium

Trouble returning to S-On/stock... (and I've really tried!)

Hiya,
Hope somebody can help… I’ve spent the last few hours searching these forums and trying various methods but I just can’t change the CID in my Wildfire .
Basically I want to return my phone to complete stock. I couldn’t change the CID at all (ever) and was on HBOOT 0.80 so upgraded that to 1.01.0001 and used the Revolutionary package to get S-OFF (and I thought SuperCID or other CID).
I have successfully got S-OFF and flashed the stock ROM that I want (RUU_Buzz_Froyo_HTC_WWE_2_22_405_1_Radio_13_55_55_24H_3_35_20_10_release_160191_signed.exe) but for the life of me I can’t change the CID to HTC__001.
I’ve tried everything but for some reason am having trouble writing from fastboot command. Here’s what I’m doing/getting:
C:\adb>adb devices
List of devices attached
HT06GPY07353 device
C:\adb>adb reboot bootloader
C:\adb>fastboot oem writecid HTC__001
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
Honestly, I’d be massively grateful for some pointers in getting S-ON back and returning to complete stock.
Thanks
How did you change your Cid? Did the phone come unlocked? Revolutionary doesn't change your Cid only s-off. If you use a ruu to get back to hboot 1.01.0001 then you will be back at stock, but your Cid is difficult to change without a xtc clip to give true s-off. So how did you change yours???
sent from my android powered. tank using xda premium B-)
I havent managed to change the CID because I can't seem to write adb/fastboot commands to the phone.
The phone came unlocked but with Vodafone branding.
Want I want to do is return to S-ON as well as stock ROM but apparently I need to issue the command "fastboot oem writesecureflag 3" to do that.
Thanks.
MrGansburg said:
I havent managed to change the CID because I can't seem to write adb/fastboot commands to the phone.
The phone came unlocked but with Vodafone branding.
Want I want to do is return to S-ON as well as stock ROM but apparently I need to issue the command "fastboot oem writesecureflag 3" to do that.
Thanks.
Click to expand...
Click to collapse
try this.
http://forum.xda-developers.com/showthread.php?t=1160251
no write secure flag command is need and neither should be a change of cid
good luck
Thanks very much, that did the trick
Glad to help,
sent from my android powered. tank using xda premium B-)

Categories

Resources