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
Related
,...........
try using fastboot to reload rom
cbmm said:
try using fastboot to reload rom
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/index.php?title=Fastboot
cbmm said:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
Click to expand...
Click to collapse
you will also need to install correct drivers on your pc, install pdanet on your desktop, that should do it
In order to use fastboot to push any commands the phone must have an ENG. Hboot. When you boot into bootloader what does it say on the top line on the page with the skateboarding andriods on the bottom? If it says VISION PVT SHIP S-ON your pretty much stuck. The phone is a paper weight. HTC is probably the only one who can fix this. It must say VISION PVT ENG S-OFF or at least VISION PVT SHIP S-OFF if there is any chance for fixing it. The only other hopes in fixing it is to flasch the stock PC10IMG to the phone in bootloader but this will only work if the phone did NOT have the OTA 1.22 rom update applyed to it. There is no way to tell this unless you try it out, but if you do have S-OFF do not try this because it will turn S back on and your screwed. If it says S-Off there is a cooked version of the PC10IMG by hot_hands that you can flash that will keep your S-Off and give you root access plus it will flash the ENG Hboot for you, I have a copy of this at home and can post it later for you, if you have S-Off.
Sent from my HTC Vision using XDA App
.............
.............
phone is locked. i would load the original rom with fastboot
I think you can download a pc10.zip and flash it. Worth a try
cbmm said:
phone is locked. i would load the original rom with fastboot
Click to expand...
Click to collapse
He can't use fastboot he doesn't have an ENG. HBoot he has the SHIP Hboot.
He can try the original stock 1.19 PC10IMG thru bootloader, that is his only option.
Sent from my HTC Vision using XDA App
.............
Erickimdmd said:
would someone mind linking the above mentioned file? and do i do it using a microsd?
sorry if i sound like a newbie... i am
thanks guys
Click to expand...
Click to collapse
http://www.megaupload.com/?d=20Y1ELB0
here's what i tried.
.............
Erickimdmd said:
ok so i found what i think was the 1.19 stock rom.
it was 123 MB (129,303,247 bytes) in size
i renamed it PC10IMG.zip and copied on microsd. when bootloader loads, this following screen flashes and nothing else happens, goes back to screen i posted earlier.
Click to expand...
Click to collapse
Did u try the copy i posted ? i have done it with others and have it do the same but this one worked for me
.............
Sometimes it hard to fact the facts but I think your phone is beyond help, at least the help offered here in the forum, I think the only thing that will bring you phone back is HTC or JTAG both of which are not available here. Might call HTC and see if they can do anything for you.
.............
Erickimdmd said:
if no other methods can be suggested i have one final question:
how much is a bricked G2 worth. heh.
Click to expand...
Click to collapse
For parts? I'm just guessing, $100.00, but you definitely dont want to pass it onto someone else with false hopes of somehow restoring it to working order. Bad Karma.
Are you sure you copied it to the root of your sdcard? With the right file name? It seems as if it isn't picking it up at all.
Sent from my HTC Vision using Tapatalk
.............
You could give this method a try. Follow the instructions carefully. The links to the files you'll need are there too.
http://www.talkandroid.com/20232-tutorial-manually-update-t-mobile-g2-remove-google-goggles/
My HBOOT ver is 0.80 ,how i can change it to 1.01.0001 for s-oof'ing???
I flashed my phone with one of RUU ROM but NOTHING happened
Thanks in advance
change h-boot.
the only way to do it is with ruu man.
did you run a ruu with the same hboot??
if you go to shipped roms.com and then buzz it gives you a list of shipped ruus, select one from your area and give it a go.
remember that using a ruu will wipe the phone entirely. (i dont think the sd card is affected.)
i dont know what ruu to suggest to you but maby someone else on here will know
WWE 2.22.405.1 Froyo RUU from shipped ROMs. Don't attempt flashing any other RUU
3xeno said:
WWE 2.22.405.1 Froyo RUU from shipped ROMs. Don't attempt flashing any other RUU
Click to expand...
Click to collapse
I flashed mentioned ROM but HBOOT version is still the same and nothing happend
Are you sure it flashed completely and properly? You didn't get any error codes or anything? Anyway, try one more way (Using the same WWE 2.22.405.1 RUU)
- Extract the ROM.zip from the RUU. Guide here:
http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html
- Once you get that file, rename it to PC49IMG.zip. Place this file on your SDCard (Not in any folder / sub-folder)
- Turn off your phone, turn on in HBoot mode. It will scan your SDCard and attempt to install the ROM. Confirm it, and see if it installs this time.
3xeno said:
Are you sure it flashed completely and properly? You didn't get any error codes or anything? Anyway, try one more way (Using the same WWE 2.22.405.1 RUU)
- Extract the ROM.zip from the RUU. Guide here:
http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html
- Once you get that file, rename it to PC49IMG.zip. Place this file on your SDCard (Not in any folder / sub-folder)
- Turn off your phone, turn on in HBoot mode. It will scan your SDCard and attempt to install the ROM. Confirm it, and see if it installs this time.
Click to expand...
Click to collapse
I flashed RUU ROM (WWE 2.22.405) like other ROMs and i received no error during the process....should i do somthing else for flashing ????
RUU's are EXE Files. I hope till now you were not talking about the Safe Flash Zips that are located in the Dev Zone?
Anyways, download the RUU from here, and try again. It's not to be installed via Clockworkmod Recovery. Connect your Wildfire to your PC, run the EXE.
http://shipped-roms.com/index.php?category=android&model=Buzz
3xeno said:
RUU's are EXE Files. I hope till now you were not talking about the Safe Flash Zips that are located in the Dev Zone?
Anyways, download the RUU from here, and try again. It's not to be installed via Clockworkmod Recovery. Connect your Wildfire to your PC, run the EXE.
http://shipped-roms.com/index.php?category=android&model=Buzz
Click to expand...
Click to collapse
Yes,you are right i have downloaded Safe_Buzz_Froyo_HTC_WWE_2.22.405.1_Rooted instead of that file which not include any .exe file at all and also i din'nt know RUU is .EXE file that should be installed via pc,anyway i a'm downloading the right one
THANKS
I receive customer id error # 131 ,what is it for???
Create a goldcard from your SDCard:
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
Then flash the RUU again.
Hey Guys, after using an RUU can i root my phone again so i can install a custom ROM??
shico80 said:
Hey Guys, after using an RUU can i root my phone again so i can install a custom ROM??
Click to expand...
Click to collapse
This is what I did with my ruu, first on PC click start then type %temp% to open the temp folder as this is where the ruu unpacks the files when running, then start the ruu while watching the temp folder for the new files to appear.
When they do search through them for rom.zip and copy and paste this to your desktop then extract the rom.zip and remove the hboot, recovery, splash and radio images.
After this is done i zipped it back up with winrar making sure to tick the .zip and selecting store only also renamed it to PC49IMG.zip then dropped the new zip onto the root of my sdcard and rebooted into hboot by pressing volume down and power, hboot found the zip and asked if i wanted to update so i chose yes and let it run.
After it booted I was on a stock unrooted rom but still had clockworkmod recovery and was able to reboot into recovery and flash the superuser zip and a new kernel to get root etc on the stock rom.
Or I could have just flashed a new rom from recovery.
Sent from my HTC Wildfire using xda premium
Oh the memories
3xeno - lol getting deja-vu, glad it wasn't just me who took the safe ruu method mistake. I thought I was reading our old conversations for one moment lol.
Scratch - excellent explaination mate,exactly how I managed it in the end.
Follow the instructions posted by 3xeno (Yoda) and scratch and you'll be s-off in no time buddy.goodluck.
P.s I gained my superuser at end of revolution by just flashing my cm7 nandroid backup.
"sent from me2u"
slymobi said:
Scratch - excellent explaination mate,exactly how I managed it in the end.
Click to expand...
Click to collapse
I know I told you how to do it too I think.........
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
I know I told you how to do it too I think.........
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Afraid not mucca,all credit goes to Yoda for my s-offing.
You have helped with so many other things though.cheers.
"sent from me2u"
You're right I didn't, just scanned through my messages and I have told a lot of people how to do that though!!
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
You're right I didn't, just scanned through my messages and I have told a lot of people how to do that though!!
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
You sure have a lot of patience. I can't ever see myself scanning my PM Box with it's 1500+ msgs.
3xeno said:
You sure have a lot of patience. I can't ever see myself scanning my PM Box with it's 1500+ msgs.
Click to expand...
Click to collapse
Lol...... Billy no mates here doesn't get as many pm's as the master!!
Sent from my HTC Wildfire using xda premium
Is there already a tool for Rooting the HTC Magic automatically?
I'm looking at making a tool that will do everything needed to get HTC Magic rooting with minimal knowledge needed by the user.
This was my first Android Phone and I rooted it no problems the 2nd time around. My first attempt resulted in a hard brick. I was lucky and the phone was replaced. My second attempt went better and I was able to sucessfully root, install Amon_RA recovery, flash Eng SPL, Custom ROM.
I was hoping to help make the process a little more "foolproof" for first timers.
I searched the forums here and have yet to find such a tool.
With help and suggestions I would like to make this program support multiple phone models both HTC and beyond.
Superoneclick. Roots in... well... one click
superoneclick seems to work pretty well, not sure if there others like it.
Yeah. SuperOneClick is the best and easy.
SuperOneClick is good for rooting but it doesn't flash an Engineering SPL or ROM.
SithLord2K said:
SuperOneClick is good for rooting but it doesn't flash an Engineering SPL or ROM.
Click to expand...
Click to collapse
Yeah, but MT3G, MT3G v1.2 and Magic 32B do not need ENG SPL...
Ok. Thank you for your feedback
Sent from my LG-P925g using XDA
Oh I see what you're talking about. A program that will root and flash a recovery in as few clicks as possible. that's a good idea. Make it easier for the noobs.
tvall said:
Oh I see what you're talking about. A program that will root and flash a recovery in as few clicks as possible. that's a good idea. Make it easier for the noobs.
Click to expand...
Click to collapse
Pretty much. Just trying to figure out how to get it to detect the phone type as well. Once I can get that I can make it useful for a broad range of phones.
Sent from my LG-P925g using XDA
SithLord2K said:
Pretty much. Just trying to figure out how to get it to detect the phone type as well. Once I can get that I can make it useful for a broad range of phones.
Sent from my LG-P925g using XDA
Click to expand...
Click to collapse
I would suggest a drop down menu where you select device at the beginning and then root and flash with proper files
Good idea. But I also want it to be able to detect the phone type to ensure someone isn't trying to flash the wrong things. Would hate to see brick posts because someone tried to flash the recovery for the wrong phone.
Sent from my LG-P925g using XDA
SithLord2K said:
Good idea. But I also want it to be able to detect the phone type to ensure someone isn't trying to flash the wrong things. Would hate to see brick posts because someone tried to flash the recovery for the wrong phone.
Sent from my LG-P925g using XDA
Click to expand...
Click to collapse
In theory there are following differences between types:
Magic 32A: hboot 1.33.xxxx / radio 3.22.xx.xx OR hboot: 1.76.xxxx / radio 6.35.xx.xx; MID: SAPPxxxxx
Magic 32B / MT3G: hboot 1.33.xxxx / radio 2.22.xx.xx; MID: SAPPxxxxx
MT3G v1.2: hboot 1.33.xxxx / radio 2.22.xx.xx; MID: SAPP31000 (only); 3.5" audiojack
You can query hboot, radio and modeild from fastboot commands:
Code:
fastboot getvar version-bootloader
fastboot getvar version-baseband
fastboot getvar modelid
But it is not enough. In some cases there are exceptions like this: http://forum.xda-developers.com/showpost.php?p=23595971&postcount=1
User wrote about Magic 32B, but device changed to 32A via inappropriate radio
Just note: it is a "brick" (half or full). If phone has 1.33.xxxx hboot, then it can not have radio 6.35.xx.xx - it will not work normally.
Case #2 - modelid can return sapp*****
http://forum.xda-developers.com/showpost.php?p=23314205&postcount=3
http://forum.xda-developers.com/showpost.php?p=14486530&postcount=3
http://forum.xda-developers.com/showpost.php?p=13186681&postcount=1
And there are some troubles to detect what is type...
Thank you so much I will be working on this. Will be a while but I will eventually get a release out
Sent from my LG-P925g using XDA
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
Friends, please tell me the way to HBOOT version slide runs on HTC ONE M9 Plus HTC__A07
Problem solved so:
1. Get S-OFF, Sunshine
2. Change to the CID HTC__J15
3. Make installer of ARUWizard and 0PK7IMG_1.85.401.6.zip rom
4. flashed without problems
5. Install all updates in order
got android 6
root
enjoy
I need to do the same "Downgrade HBOOT from 2.27.401.1 to 1.90.401.3". How can I do it with S-ON? Phone is not booting to OS therefore i can't make S-OFF with sunshine. Please help...
starmex said:
I need to do the same "Downgrade HBOOT from 2.27.401.1 to 1.90.401.3". How can I do it with S-ON? Phone is not booting to OS therefore i can't make S-OFF with sunshine. Please help...
Click to expand...
Click to collapse
If your phone is bricked you can flash this http://forum.xda-developers.com/showpost.php?p=69147695&postcount=353 from TWRP.
greenapple88 said:
If your phone is bricked you can flash this http://.xda-.com/showpost.php?p=69147695&postcount=353 from TWRP.
Click to expand...
Click to collapse
Thank you very much! Finally I succeed to boot the android. I've done as you said and it works.
starmex said:
Thank you very much! Finally I succeed to boot the android. I've done as you said and it works.
Click to expand...
Click to collapse
Glad that it helped.
If I have s off. Can I just Downgrade it simply with an older Ruu and put it to SD card?
What are the consequences off having s off.
Flashing Roms and something like that in future?
Is any one here to help me for Hboot?? my phone is getting bricked after incomplete flash. its update hboot thn comes lots of error and flash incomplete. after that my htc one m9 plus didnt boot. is any one there to help me how to solve that? i tried lots of ruu file but it didnt get flash. im so upset with this phone now is there any one can help me for hboot? my os version - 2.30.401.1, S-on, Unlocked.