DO NOT TRY, THIS WILL NOT WORK FOR NOW.
Hey guys, here's the manual for how to get SuperCID WITHOUT S-OFF.
NOTE: THIS IS NOT FOR BEGINNING USERS, YOU WILL CHANGE THE BOOTLOADER WHICH MIGHT BRICK YOUR DEVICE, BE CAREFUL
Thanks to vogonpoetlaureate for finding where the CID is, he's a great guy so go thank him!
Assuming you have ADB (Android Debugging Bridge) installed, open up your command prompt and type this:
Code:
su
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7
Now you have it dumped on your SD-Card
Next, type "exit" and again, "exit".
Type
Code:
adb pull /sdcard/mmcblk0p7
BE SURE YOU KNOW WHAT SIZE IT IS BEFORE CONTINUING
Open the file with your HEX-Editor, assuming you have one downloaded. I personally use XVI32.
You will see your CID on the fourth line, in my case it's HTC__E11.
Change it to 11111111 and save the file as mmcblk0p7MOD. BE SURE IT'S THE EXACT SAME SIZE AS BEFORE.
When you're back in command prompt, type
Code:
adb push mmcblk0p7MOD /sdcard/mmcblk0p7MOD
Type
Code:
adb shell
su
dd if=/sdcard/mmcblk0p7MOD of=/dev/block/mmcblk0p7
Reboot to bootloader, (adb reboot-bootloader) and go into fastboot.
Type
Code:
fastboot oem readcid
It should read 11111111.
Thanks to grankin01 for the base thread: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
I AM NOT RESPONSIBLE FOR BRICKED DEVICES
It works with me, PLEASE, if it works with you reply here!
Just in case
Re: [BOOTLOADER] SuperCID 11111111
Thanks for the step-by-step Maarten. Very helpful.
Sent from my HTC Desire X using xda premium
Re: [BOOTLOADER] SuperCID 11111111
vogonpoetlaureate said:
Thanks for the step-by-step Maarten. Very helpful.
Sent from my HTC Desire X using xda premium
Click to expand...
Click to collapse
No problem
And thank you for pointing out the location of the CID, must have overlooked it.
Did it work for you?
Sent from my awesome fridge
Just to be sure, I need to be in "normal" system (not fastboot or hboot or recovery) to do this steps right?
I'm asking that because I'm facing this error:
[email protected]:/ # su
[email protected]:/ # dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7: cannot open for write: Read-only file system
I should say I have neXus last kernel and TWRP installed.
Thank you very much!!
Re: [BOOTLOADER] SuperCID 11111111
gbueno6 said:
Just to be sure, I need to be in "normal" system (not fastboot or hboot or recovery) to do this steps right?
I'm asking that because I'm facing this error:
[email protected]:/ # su
[email protected]:/ # dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7: cannot open for write: Read-only file system
I should say I have neXus last kernel and TWRP installed.
Thank you very much!!
Click to expand...
Click to collapse
Try using those commands in recovery, then it'll work.
Sent from my awesome fridge
MaartenXDA said:
Try using those commands in recovery, then it'll work.
Sent from my awesome fridge
Click to expand...
Click to collapse
I found out which was the mistake: I was in Hard Disk mode. In charge only mode it worked. Now I'll transfer the file again, reboot to bootloader and see if it worked!
By the way, did it work for you?
Thank you
Re: [BOOTLOADER] SuperCID 11111111
gbueno6 said:
I found out which was the mistake: I was in Hard Disk mode. In charge only mode it worked. Now I'll transfer the file again, reboot to bootloader and see if it worked!
By the way, did it work for you?
Thank you
Click to expand...
Click to collapse
Yep, worked for me.
But still, please report.
Sent from my awesome fridge
MaartenXDA said:
Yep, worked for me.
But still, please report.
Sent from my awesome fridge
Click to expand...
Click to collapse
Not for me! (
I'll try again later because I don't know what I'm doing wrong!
So, just in case... restoring old CID = changing value to old CID?
Great job, but I don't think I will need this thing. Nevertheless it's great job done, because AFAIK changing CID will help to get rid of sim lock by such operators as Verizon, Orange, Vodafone. Am I thinking the right way?
A huge thanks to all the devs who worked on this.
Re: [BOOTLOADER] SuperCID 11111111
MaartenXDA said:
Just in case
Click to expand...
Click to collapse
Doesn't that mean we can now achieve S-OFF.?
Sent from my HTC Desire X using xda premium
Great work! I have contacted the devs of facepalm to get us S-OFF. They were waiting for us to get superCID .
Klapo said:
So, just in case... restoring old CID = changing value to old CID?
Click to expand...
Click to collapse
Yes, keep a backup of the file handy so you can just restore it if you need to.
Please, to all the guys that have made it, can you tell me what kernel and recovery did you have installed?
Because I've tried it again, every single step, and I'm still with my carrier CID: ORANG309.
Thank you very much!
HT__044
Hello and thank you for the nice info...
I have tried several times on CID HTC__044 and still i'm on the same CID...
is there any comment or solution for this?
anyway thanks a lot...
Edit: Nah that shouldn't matter.
Thanks!
I see "ro" so that's why is not working. It seems strange considering I have flashed neXus V3 kernel which has System Protection Disabled but I've flashed it again and see if I see "rw" instead of "ro".
Thank you again!
EDIT: Tried again with a "fresh" flash of neXus kernel and no way to make it work. I'm getting kind of desperate
I have tried it with system protection off even and still the same...
What I need is just to flash back to the the factory firmware, My phone is Asian (Singapore) and I coudnt find the Asian RUU till now...
I cant flash the European version because of the CID...
I dont know what to do...
Related
I've corrupted my recovery image. I'd be very grateful to anyone who could take a minute to grab the image from their amaze.
Here's the step-by-step on how to do it:
1. Unzip zergRush from the attached zipfile. Place it on your PC
2. Push it to your phone using adb (adb push zergRush /data/local)
3. Adb shell to your phone (adb shell)
4. cd to /data/local (cd /data/local)
4. Run zergRush (./zergRush)
5. It will churn for a bit and then you should have temp root.
6. Adb shell back onto the phone. (adb shell)
7. From the # prompt run (dd if=/dev/block/mmcblk0p23 /sdcard/recovery.img)
8. post the recovery image somewhere I can access.
9. receive my gratitude
tia
-xdadevelopers-user
Here you go....
http://dl.dropbox.com/u/19769336/recovery.img
Thank you!
I feel much better now that I have a working recovery - though I'm not exactly sure why.
-xdadevelopers-user
other than fastboot how would you push it back to the device
Hboot
Sent from my HTC Sensation Z710e using xda premium
crackeyes said:
other than fastboot how would you push it back to the device
Click to expand...
Click to collapse
I guess in theory, if you have root, you could dd it back to the correct partition from the running android os.
Code:
#dd if=recovery.img of=/dev/block/mmcblk0p23
Though I haven't tried that. I just used fastboot.
-xdadevelopers-user
xdadevelopers-user said:
I guess in theory, if you have root, you could dd it back to the correct partition from the running android os.
Code:
#dd if=recovery.img of=/dev/block/mmcblk0p23
Though I haven't tried that. I just used fastboot.
-xdadevelopers-user
Click to expand...
Click to collapse
that worked but it is still f'ed up this phone is a brick LOL oh well lets see how i can fry it and get a new one
crackeyes said:
that worked but it is still f'ed up this phone is a brick LOL oh well lets see how i can fry it and get a new one
Click to expand...
Click to collapse
hey crack eyes could you test something for me?
Code:
dd if=(direcotry path to hboot.img Example: C:\Hboot.img) of=/dev/block/mmcblk0p12
could you trry that with this hboot.img
http://www.multiupload.com/D7HEFK9DH6
exract hboot.img first then place in c:\
xboarder56 said:
hey crack eyes could you test something for me?
Code:
dd if=(direcotry path to hboot.img Example: C:\Hboot.img) of=/dev/block/mmcblk0p12
could you trry that with this hboot.img
http://www.multiupload.com/D7HEFK9DH6
exract hboot.img first then place in c:\
Click to expand...
Click to collapse
That cannot work. The example you provide has the input file on the PC and the output file is a block device on the phone. The dd command, when run from a PC won't be able to see the output file since it doesn't exist on the PC. Or, if you run dd from the phone it won't be able to see the hboot.img because it's on the PC - not the phone.
For it to work you'd need to first get the hboot.img on the phone somewhere. If you have an sd card you could copy it to /sdcard or you could put it on /data/local.
Then the command would be something like:
dd if=/sdcard/hboot.img /dev/block/mmcblk0p12
And, of course for this to work you'd need an unlocked bootloader and a working device that has root. And, even then, I'd guess this would either not work or brick the device. But, if someone's willing to test it then, hey, who am I to say otherwise - go for it!
-xdadevelopers-user
cmenard said:
Here you go....
http://dl.dropbox.com/u/19769336/recovery.img
Click to expand...
Click to collapse
Can anyone verify if the recovery in the above link is the Stock Recovery for T-Mo Amaze? I'm on GB and want to get the ICS OTA update but Hasoon has removed the Stock Recovery from his AIO toolkit. Thanks!
ernieg92 said:
Can anyone verify if the recovery in the above link is the Stock Recovery for T-Mo Amaze? I'm on GB and want to get the ICS OTA update but Hasoon has removed the Stock Recovery from his AIO toolkit. Thanks!
Click to expand...
Click to collapse
You don't need a stock recovery, just repock boot loader and apply update
Sent from my HTC_Amaze_4G using Tapatalk 2
Just do what? Thanks
EclipzeRemix said:
You don't need a stock recovery, just repock boot loader and apply update
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Wrong place to ask questions
Sent from my HTC_Amaze_4G using xda premium
HOW TO Flash T-Mobile USA Radio (Needs More Work)
All credit goes to he_stheone64 and his thread located here: http://forum.xda-developers.com/showthread.php?t=2245615
Credit: The War Horse - for telling me the obvious, how to get the radio was listed in the thread above all along
I apologize that is my first stab at development and for any errors you may or may not run into. This is fully expected to work with he_stheone64 method above as the only thing I changed was the radio.img.
This thread taught me how to extract the T-mobile USA radio from my HTC One. Now its time for those in the community who really want to have T-mobile 3G speeds to test this out!
This is for you and you deserve it. As I promised with no more words....
This is how you can upgrade your RADIO without S-Off
1. Download Radio update.zip below and copy to your SD
2. Only an optional step for those, who want to have a Radio Firmware backup just in case
a) Connect your device via USB in recovery and open cmd in fastboot folder:
adb shell
dd if=/dev/block/mmcblk0p31 of=/sdcard/radio_firmware.img
You will now have current Radio on SD as radio_firmware.img
Expected output:
PHP Code:
PHP Code:
Code:
~ # dd if=/dev/block/mmcblk0p31 of=/sdcard/radio_firmware.img
dd if=/dev/block/mmcblk0p31 of=/sdcard/radio_firmware.img
153601+0 records in
153601+0 records out
78643712 bytes (75.0MB) copied, 11.826523 seconds, 5.4MB/s
3. Now just flash the Radio update.zip as usual in recovery, reboot your device and enjoy latest Radio
In case you want / need to restore your current Radio backup:
Either you adjust updater script to radio_recovery.img or just do it via adb in recovery:
dd if=/sdcard/radio_firmware.img of=/dev/block/mmcblk0p31
Download Radio from:
https://mega.co.nz/#!d9wz0QDA!DF1QoGnkPuDt3ttjpGz1xSqh9U0ZDUtEpPG15vA_61E
MD5: 7BACD1B72F53859A52A3EB6CB3FB5433
Not only would this be better placed in Q&A but there is a thread specifically about this in the dev sub.
http://forum.xda-developers.com/showthread.php?t=2245615
To answer your question though, you will need to get the T-mo radio to be able to flash it.
anit77 said:
Not only would this be better placed in Q&A but there is a thread specifically about this in the dev sub.
http://forum.xda-developers.com/showthread.php?t=2245615
To answer your question though, you will need to get the T-mo radio to be able to flash it.
Click to expand...
Click to collapse
Thanks! However, it was stated in this thread that we first need the T-mobile radios right? so Im asking.
If anyone has the t-mobile radios please offer it here for download. Then we can begin the progress on flashing it over to test on the dev editions. Thanks
Yes! Please help! Thanks in advance *^O^*
If you get the radio, could be used on the att htc one x plus?
I'm currently using the att one x+ on t-mobile.
garmig said:
If you get the radio, could be used on the att htc one x plus?
I'm currently using the att one x+ on t-mobile.
Click to expand...
Click to collapse
Pronably not
Sent from my SGH-T999 using xda app-developers app
EclipzeRemix said:
Pronably not
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
So, I have the t-mobile htc one in hand. However, just how do I go about getting the radios so I can share it with everyone here?
Can anyone please give me a step by step tutorial?
Thanks
Becool0130 said:
So, I have the t-mobile htc one in hand. However, just how do I go about getting the radios so I can share it with everyone here?
Can anyone please give me a step by step tutorial?
Thanks
Click to expand...
Click to collapse
Hi you can follow this thread to save the radio image.
http://forum.xda-developers.com/showthread.php?t=2245615
Becool0130 said:
Title says it. Need a T-Mobile radio dump to get T-Mobile frequencies working for you guys. Thanks so much.
I want to give the community - especially the ones with a developer edition or ATT - a way to flash Tmobile radios
Please post the download link here and we can all test it out and see if it works.
This can be done with S-On too! Please see this thread:
http://forum.xda-developers.com/showthread.php?p=40603094&highlight=t-mobile#post40603094
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Ok just dumped the radio from my phone. Hope it works out.
T-Mobile_Radio1.27.431.7
xdarkfirex said:
Ok just dumped the radio from my phone. Hope it works out.
T-Mobile_Radio1.27.431.7
Click to expand...
Click to collapse
Thanks so much! This thread has been updated and reflects how to flash the t-mobile radio via recovery.
Lets get on with it and let me know if it works out for you!! :good:
Thanks guys for making this possible.
I'm trying to backup the original radio but got the permission denied message.
Did i missed anything?
1. The phone was booted in recovery mode.
2. open CMD and go to phone's adb directory
3. typed the adb shell command and then see the rest command log
J:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ dd if=/dev/block/mmcblk0p31 of=/sdcard/radio_firmware.img
dd if=/dev/block/mmcblk0p31 of=/sdcard/radio_firmware.img
/dev/block/mmcblk0p31: cannot open for read: Permission denied
1|[email protected]:/ $
My one is the developer version
Can anyone confirm that tmobile 1700 AWS is working on dev edition?
I'm on Tmo with a 32gb unlocked One, so I gave it a shot. I have a SGS2 as well so I know I get HSPA+ here and not Edge, which is what I'm getting now on my One.
I backed up the radio, unlocked the bootloader, flashed recovery, flashed supersu, flashed Tmo radio, did factory reset. No luck, still getting Edge on my One.
---------- Post added at 01:45 PM ---------- Previous post was at 01:40 PM ----------
sai0899 said:
Thanks guys for making this possible.
I'm trying to backup the original radio but got the permission denied message.
Did i missed anything?
1. The phone was booted in recovery mode.
2. open CMD and go to phone's adb directory
3. typed the adb shell command and then see the rest command log
J:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ dd if=/dev/block/mmcblk0p31 of=/sdcard/radio_firmware.img
dd if=/dev/block/mmcblk0p31 of=/sdcard/radio_firmware.img
/dev/block/mmcblk0p31: cannot open for read: Permission denied
1|[email protected]:/ $
My one is the developer version
Click to expand...
Click to collapse
You might need to root it first. Then enter the command "su" and grant permissions before the "dd" command.
dksxmks said:
I'm on Tmo with a 32gb unlocked One, so I gave it a shot. I have a SGS2 as well so I know I get HSPA+ here and not Edge, which is what I'm getting now on my One.
I backed up the radio, unlocked the bootloader, flashed recovery, flashed supersu, flashed Tmo radio, did factory reset. No luck, still getting Edge on my One.
---------- Post added at 01:45 PM ---------- Previous post was at 01:40 PM ----------
You might need to root it first. Then enter the command "su" and grant permissions before the "dd" command.
Click to expand...
Click to collapse
I believe his phone is rooted already as he already has recovery. Your log you posted "adb server is out of date. killing..." IS CRUCIAL.
You need to launch adb and update it. How? In windows 7 just press start and type in "sdk manager". Everything is straight forward from there. Then try again
I have a tmobile with 1.27.531.7 Is this of any use to anyone?
Can I flash this radio on my unlocked AT&T HTC One? Using it on T-Mobile now but only get edge
dutchtrumpet said:
I have a tmobile with 1.27.531.7 Is this of any use to anyone?
Click to expand...
Click to collapse
As do I. I'm wondering what the difference is.
Sent from my HTC One using xda premium
jonathan3579 said:
As do I. I'm wondering what the difference is.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Your looking for the BASEBAND in settings not the software version running on the phone. Anyhow, please try it out and let me know how it goes. I believe it needs some more work -_-
Airo18 said:
Can I flash this radio on my unlocked AT&T HTC One? Using it on T-Mobile now but only get edge
Click to expand...
Click to collapse
This is what we're hoping but we need a brave soul to try it out. If it works, it means that we can buy the unlocked / developer editions and bring them to tmobile with full 3g/4g/lte!
advocat3 said:
This is what we're hoping but we need a brave soul to try it out. If it works, it means that we can buy the unlocked / developer editions and bring them to tmobile with full 3g/4g/lte!
Click to expand...
Click to collapse
If I flash this and all goes downhill, can I flash an RUU back to stock? Wouldn't mind testing
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Here is a picture of hboot:
Sent from my ADR6400L using xda app-developers app
cyberkeeper1 said:
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Click to expand...
Click to collapse
Something I don't understand here: how were you able to run fastboot oem writecid while S-ON? Have you since gone S-ON after writing the incorrect CID?
Furthermore, why in the world would you venture from my explicit instructions on how to fix the radio? I can't imagine any reason you would want to re-lock the bootloader or go S-ON. As I keep saying: if you are already unlocked or S-OFF, I almost never see a legitimate reason to run the RUU!
I assume you still can boot into CyanogenMod? If so, follow these instructions (Windows):
Set this in CM: Settings > Developer options > Root access > Apps and ADB
Download the latest unlock script package (we will not run the script, but we do need the files there)
Extract the unlock script package and open a command window in that directory
Type these commands:
Code:
adb root
adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/cid"
adb pull /sdcard/cid
hexalter cid 0x214=0x56,0x5A,0x57,0x5F,0x5F,0x30,0x30,0x31
adb push cid /sdcard/
adb shell "dd if=/sdcard/cid of=/dev/block/mmcblk0p4"
This should revert your CID back to VZW__001.
deleted
cyberkeeper1 said:
See I wish I could boot. I didn't understand why it accepted an oem command while s-on either. But alas, it did. I wrote that command after relocking. I am not s-off. Never was, hence my entire problem. I was afraid to try s-off because of the higher possibility of bricking my phone. It's not like the thunderbolt where it always works. If I was s-off I would know what to do and could flash hotdogs as my Cid if I wanted. My first problem is being stuck in hboot and can't restore. I wiped everything. Boot, data, system, recovery all in prep for stock since I am s-on
Click to expand...
Click to collapse
From the bootloader, what is the output this?
Code:
fastboot getvar cid
deleted
cyberkeeper1 said:
The output is:
VZW_0001
Click to expand...
Click to collapse
I can't even explain the number of ways you shot yourself in the foot. You really wiped recovery and boot too? How did you come to believe this would be a good idea? Or is necessary at all?
I believe the only option you have is to try and flash the stock signed recovery through fastboot (not even sure if it'll work), and then use ruu mode to TRY and fix things up:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ruu.zip
I suspect even that will complain about the incorrect CID though. Perhaps jose has some other ideas.
deleted
deleted
deleted
deleted
deleted
YESSSSSSSSSSSSSS! I GOT IT! I GOT IT! I GOT IT!
When i want something done, i try the impossible...
so... here is the thing... and COMPLETELY unexpected it is. Apparently, you can submit the following cid as an unlock token to HTCdev and get returned a valid unlock code BIN file. with VZW_0001 (obviously incorrect) i STILL received the file and it said token submitted successfully. downloaded, flashed and now unlocked. still s-on, but WAY more room for fixing now. i flashed the CID back to the proper VZW__001 using adb root shell in recovery. worked great! thanks MDMOWER for the codes to revert. now i can flash my custom ROM backup back to the device after flashing just the stock rom (NO RELOCKING THIS TIME FOR ME!) to fix the radios the way i was supposed to. ( being tired = not reading + not using glasses) i don't understand it myself, but i bet this one is going to through you for a loop. the only conclusion i can come up with is the fact that another device actually DOES use the CID of VZW_0001 and is not an officially supported device. that would explain why i was even able to be successful. but its speculation at best until confirmed.
cyberkeeper1 said:
YESSSSSSSSSSSSSS! I GOT IT! I GOT IT! I GOT IT!
When i want something done, i try the impossible...
so... here is the thing... and COMPLETELY unexpected it is. Apparently, you can submit the following cid as an unlock token to HTCdev and get returned a valid unlock code BIN file. with VZW_0001 (obviously incorrect) i STILL received the file and it said token submitted successfully. downloaded, flashed and now unlocked. still s-on, but WAY more room for fixing now. i flashed the CID back to the proper VZW__001 using adb root shell in recovery. worked great! thanks MDMOWER for the codes to revert. now i can flash my custom ROM backup back to the device after flashing just the stock rom (NO RELOCKING THIS TIME FOR ME!) to fix the radios the way i was supposed to. ( being tired = not reading + not using glasses) i don't understand it myself, but i bet this one is going to through you for a loop. the only conclusion i can come up with is the fact that another device actually DOES use the CID of VZW_0001 and is not an officially supported device. that would explain why i was even able to be successful. but its speculation at best until confirmed.
Click to expand...
Click to collapse
moderators, after a few replies from the users, i don't mind if you close my thread because my problem is solved.
EDIT: maybe not yet... bootlooping after fix and restore of last backup before the incident. do i have to have the Super CID written to boot from any custom rom?
cyberkeeper1 said:
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Here is a picture of hboot:
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
are you rooted?
EDIT: got confused and was thinking this was a new thread sorry
jose51197 said:
you rooted?
Click to expand...
Click to collapse
i am now that i fixed everything. well the recovery partition is rooted. i cant get my phone to boot now though. i tried using the backup i made right before returning to stock and it no longer works. i get a boot loop from the first boot screen. loads HTC logo, then legal warning in red. screen turns black and back again. it never loads into the CM10.1. i manually flashed the kernel from my backup since i am still s-on. i am going to try fresh installing a rom.
cyberkeeper1 said:
i am now that i fixed everything. well the recovery partition is rooted. i cant get my phone to boot now though. i tried using the backup i made right before returning to stock and it no longer works. i get a boot loop from the first boot screen. loads HTC logo, then legal warning in red. screen turns black and back again. it never loads into the CM10.1. i manually flashed the kernel from my backup since i am still s-on. i am going to try fresh installing a rom.
Click to expand...
Click to collapse
You messed a lot with you phone man, better install stock rom throught ruu or mdmowers way then s off revert cid and flash cm10
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
You messed a lot with you phone man, better install stock rom throught ruu or mdmowers way then s off revert cid and flash cm10
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
i am inclined to agree based on what its doing, but wanted to be sure. i just didnt want to have to re-re unlock again. lol. i'll see what happens.
I was able to successfully flash cyanogenmod, but my phone only works for data, not for calls or texts. I assume this is because I'm still on Super CID (11111111). When I try to revert to the VZW cid, i receive an error executing the adb shell. It tells me that it's a read only file system. I'm rooted, s off, and bootloader unlocked. Any help would be greatly appreciated as my phone is only half usable right now
Don't use adb shell once you're s-off. Use these commands:
Code:
adb reboot bootloader
Once in fastboot, issue this command to revert to the VZW CID:
Code:
fastboot oem writecid VZW__001
that's it.
Sent from my Incredible 4G LTE using xda app-developers app
Thanks so much for the quick response. I knew I was overthinking it. Just applied the change, rebooting now. I'll follow up with my findings.
---------- Post added at 06:27 PM ---------- Previous post was at 06:16 PM ----------
Well, it changed the CID, but the issue still persists. If I look in about phone > status, it says my mobile phone number is 000-000-0000. I'm definitely preplexed to say the least.
Hey Everybody..
Here a little guide to how to make you T-Mobile HTC One a Developer Edition and receive OTA updates directly from HTC with no carries delays.
after downloading and unzip the revone.zip file do the following:
MAKE SURE YOUR ADB AND FASTBOOT ARE WORKING PROPERLY. AND UNINSTALL HTC SYNC MANAGER BEFORE DOING ANY OF THESE STEPS!!
ONLY DO THIS IF YOU ARE COMFORTABLE IN WHAT YOU DOING.
adb push revone /data/local/tmp
adb shell
cd /data/local/tmp
chmod 755 revone
./revone -P
exit
reboot your phone
adb shell
cd /data/local/tmp
./revone -s 0 -u
exit
adb reboot bootloader
your bootloader should now be S-OFF
to change CID do this:
fastboot oem writecid 11111111
fastboot reboot-bootloader
your bootloader screen should now show the new CID
you can now flash the Original RUU for the HTC One Developer Edition from http://www.htcdev.com/devcenter/downloads
i take no credit for this guide this is just a re-write from the real devs page. i wanted to make it easy for those looking in this section
Is this reversible? Also, do you get everything you get on the Tmo version except wifi calling and Tmo apps? Thanks.
I think links to the revone s-off thread would be more appropriate than just rewriting their instructions and posting their file here, don't you? Those devs deserve proper credit, and the real support for problems is going to be there....
Legaleye3000 said:
Is this reversible? Also, do you get everything you get on the Tmo version except wifi calling and Tmo apps? Thanks.
Click to expand...
Click to collapse
yes and yes
When HTC updates though wouldn't they also be updating the radio? If that's the case won't that affect our 1700 band or will we still keep it? All I care about is stock since I'm already over the whole flashing and rooting stuff. Wish HTC did a dev edition with tmobile bands.
Sent from my HTC One
Gja88 said:
When HTC updates though wouldn't they also be updating the radio? If that's the case won't that affect our 1700 band or will we still keep it? All I care about is stock since I'm already over the whole flashing and rooting stuff. Wish HTC did a dev edition with tmobile bands.
Sent from my HTC One
Click to expand...
Click to collapse
I'm running the Dev edition radio and still have 1700 band.
Gja88 said:
When HTC updates though wouldn't they also be updating the radio? If that's the case won't that affect our 1700 band or will we still keep it? All I care about is stock since I'm already over the whole flashing and rooting stuff. Wish HTC did a dev edition with tmobile bands.
Click to expand...
Click to collapse
That's extact what this guide does.. HTC one dev edition and with pentaband
Sent from my HTC One using xda app-developers app
just want to confirm, it should be this?
One
Brightstar US
USA
RUU
3.4.10
v4.1 984.7 MB
1.29.1540.16 Developer Edition
Gja88 said:
When HTC updates though wouldn't they also be updating the radio? If that's the case won't that affect our 1700 band or will we still keep it? All I care about is stock since I'm already over the whole flashing and rooting stuff. Wish HTC did a dev edition with tmobile bands.
Sent from my HTC One
Click to expand...
Click to collapse
Exactly.
Sent from my HTC One using Tapatalk 2
id10terrordfw said:
I'm running the Dev edition radio and still have 1700 band.
Click to expand...
Click to collapse
Again...
jay661972 said:
just want to confirm, it should be this?
One
Brightstar US
USA
RUU
3.4.10
v4.1 984.7 MB
1.29.1540.16 Developer Edition
Click to expand...
Click to collapse
yup.. i used that one .. everything works flawless.. no t-mobile bloatware
adb says: device not found. I installed everything. From android sdk to fastboot. Hasoon2000's all in one kit works, so it is not my USB connection. I really need to recover with a developer edition RUU. My HTC One is useless right now.
Oh well something strange happend. When I command: fastboot reboot-bootloader my HTC One reboot in to bootloader. It is not working on adb, but on fastboot commands.
YaviSGS said:
adb says: device not found. I installed everything. From android sdk to fastboot. Hasoon2000's all in one kit works, so it is not my USB connection. I really need to recover with a developer edition RUU. My HTC One is useless right now.
Oh well something strange happend. When I command: fastboot reboot-bootloader my HTC One reboot in to bootloader. It is not working on adb, but on fastboot commands.
Click to expand...
Click to collapse
boot your phone into the OS, then try the adb devices see if show up
YaviSGS said:
adb says: device not found. I installed everything. From android sdk to fastboot. Hasoon2000's all in one kit works, so it is not my USB connection. I really need to recover with a developer edition RUU. My HTC One is useless right now.
Oh well something strange happend. When I command: fastboot reboot-bootloader my HTC One reboot in to bootloader. It is not working on adb, but on fastboot commands.
Click to expand...
Click to collapse
i do have issue last night in doing the steps, decided to do it using android terminal and its flawless
---------- Post added at 02:36 PM ---------- Previous post was at 02:01 PM ----------
xitaxuta said:
yup.. i used that one .. everything works flawless.. no t-mobile bloatware
Click to expand...
Click to collapse
i run the RUU this morning but hang in Sending for more than 20 minutes thats why i remove unplug the usb
xitaxuta said:
boot your phone into the OS, then try the adb devices see if show up
Click to expand...
Click to collapse
I do not have OS. Everything on my phone is wiped. I only have a USB kabel, HTC One which is still unlocked. My only hope is S-OFF and then flash developer edition cause there is no T-Mobile RUU available
Edit: I think it works. I see a white screen with HTC logo and text at the bottom: "This is build is for development purposes only etc". So I commanded: adb reboot bootloader and it works. Bit still, when I command: adb devices, there is no device.
Is your phone with super-cid?
Sent from my HTC One using xda app-developers app
xitaxuta said:
Is your phone with super-cid?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I don't know what that means.
This is all I can say about my phone:
***TEMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013, 17:22:59:-1
This is what I got when I command:
C:\Android\adb push revone /data/local/tmp
failed to copy 'revone' to '/data/local/tmp' : No such file or directory
YaviSGS said:
I don't know what that means.
This is all I can say about my phone:
***TEMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013, 17:22:59:-1
Click to expand...
Click to collapse
Your phone is showing
S-ON
You need to s-off using the revone file.. and after that you need change it to super-cid.
Sent from my HTC One using xda app-developers app
xitaxuta said:
Your phone is showing
S-ON
You need to s-off using the revone file.. and after that you need change it to super-cid.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes I try to do that now. I putted the revone file in the map where my adb files are. There I opened cmd and typed this:
C:\Android\adb push revone /data/local/tmp
failed to copy 'revone' to '/data/local/tmp' : No such file or directory
I think its refers to my internal storage? Cause there are no files in my storage right now... Or is it something else?
I'm heading to work right now so won't be able to assist you until I get back home.. what rom are you using? Try to cd\android
adb push revone /data/local/tmp
Sent from my HTC One using xda app-developers app
Here's the Rom.zip I pulled from the AT&T 4.18.502.7 RUU
Encrypted version is Removed until i find another source (file was damaged, sorry for any inconvenience )
This will work if your s-off and your modelid: PN0712000 and CID: CWS__001
or you can EDIT the Android-info.txt to match your MID and CID
Decrypted version is here >> http://www.androidfilehost.com/?fid=23329332407580500
Huge thanks to @nkk71 for decrypting the files
And another Big thanks to @AndroidFileHost for the source RUU
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip
Instructions for flashing
If your s-on be sure the bootloader is locked
fastboot oem lock
Copy your downloaded file to your fastboot / adb folder
Rename the file Rom.zip
open a command prompt in the same folder (shift + right click - command prompt here )
adb reboot-bootloader
fastboot commands:
fastboot oem rebootRUU
wait for the Silver HTC logo
fastboot flash zip Rom.zip
the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip Rom.zip
most times the green status bar does not reach the 100% mark. So when the output in the command window is complete, you can reboot:
fastboot reboot
I find these files much easier to use than the RUU.exe and these can be flashed with a MAC or Linux ....Have Fun !!
:good: :good:
clsA said:
Here's the Rom.zip I pulled from the AT&T 4.18.502.7 RUU
This will work if your s-on and your modelid: PN0712000 and CID: CWS__001
Encrypted version is here >> http://www.androidfilehost.com/?fid=23329332407580207
This will work if you s-off and your modelid: PN0712000 and CID: CWS__001
or you can EDIT the Android-info.txt to match your MID and CID
Decrypted version is here >> http://www.androidfilehost.com/?fid=23329332407580500
Huge thanks to @nkk71 for decrypting the files
And another Big thanks to @AndroidFileHost for the source RUU
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip
Instructions for flashing
Copy your downloaded file to your fastboot / adb folder
Rename the file Rom.zip
open a command prompt in the same folder (shift + right click - command prompt here )
adb reboot-bootloader
fastboot commands:
fastboot oem rebootRUU
wait for the Silver HTC logo
fastboot flash zip Rom.zip
the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip Rom.zip
most times the green status bar does not reach the 100% mark. So when the output in the command window is complete, you can reboot:
fastboot reboot
I find these files much easier to use than the RUU.exe and these can be flashed with a MAC or Linux ....Have Fun !!
Click to expand...
Click to collapse
thanks again, much appreciated! I will give it a few more minutes but I work at 6am!
a little help please
I just put my One back to stock. S-on, relocked, tamper gone, etc When I try to update using the above method i get
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (1519630 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.002s
any ideas? thank you!
gsxrfl1k6 said:
I just put my One back to stock. S-on, relocked, tamper gone, etc When I try to update using the above method i get
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (1519630 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.002s
any ideas? thank you!
Click to expand...
Click to collapse
I just tested it and had the same problem ...I'll update when I get the new file uploaded
clsA said:
I just tested it and had the same problem ...I'll update when I get the new file uploaded
Click to expand...
Click to collapse
I'm also having the same issue. Have you been able to figure out what is wrong?
TaDoey said:
I'm also having the same issue. Have you been able to figure out what is wrong?
Click to expand...
Click to collapse
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
HEllo, friend now i feel very dissapointed thus i was not able to update my phone is a htc one M7 7120 from AT$T running this useless firmware 1.26.502.12, im in Colombia myabe thats why the AT&T system update is not working and i tried to run that RUU 3.X.502... but it still giving me the ERROR 158, any idea how can i update this phone? Thank man hope u can answer me.
Sli2cooL said:
HEllo, friend now i feel very dissapointed thus i was not able to update my phone is a htc one M7 7120 from AT$T running this useless firmware 1.26.502.12, im in Colombia myabe thats why the AT&T system update is not working and i tried to run that RUU 3.X.502... but it still giving me the ERROR 158, any idea how can i update this phone? Thank man hope u can answer me.
Click to expand...
Click to collapse
Is your bootloader locked/relocked?
Are you S-OFF or S-ON?
What is the CID?
Is this the RUU 3.17.502.3 that you are trying to run?
You will not get any AT&T updates if you are not on the AT&T network!
If you are not S-OFF, I would recommend obtaining S-OFF then rebrand your phone to the International (.401) variant. Then you could get the OTA updates and not worry about the AT&T network.
majmoz said:
Is your bootloader locked/relocked?
Are you S-OFF or S-ON?
What is the CID?
Is this the RUU 3.17.502.3 that you are trying to run?
You will not get any AT&T updates if you are not on the AT&T network!
If you are not S-OFF, I would recommend obtaining S-OFF then rebrand your phone to the International (.401) variant. Then you could get the OTA updates and not worry about the AT&T network.
Click to expand...
Click to collapse
Hello mate, thanks for the reply, now that you mention it sounds pretty interesting to rebrand to phone to int. variant, but... How do i ado that? Right now im running 4.18.502.7 Stock for AT&T, i would not liek to bother you so much but is there any way to do that i wouls appreciate the help.
Yes im S-OFF and yes im unlocked, TWRP tho, CWS__001, hboot 1.44.000000 and rooted.
Once again thanks for the help.
Sli2cooL said:
Hello mate, thanks for the reply, now that you mention it sounds pretty interesting to rebrand to phone to int. variant, but... How do i ado that? Right now im running 4.18.502.7 Stock for AT&T, i would not liek to bother you so much but is there any way to do that i wouls appreciate the help.
Yes im S-OFF and yes im unlocked.
Once againm thans for the help.
Click to expand...
Click to collapse
Here is a outline of what you will need to do.
Here are the steps to re-branding your phone to Int'l:
Unlock bootloader if not unlocked already!
Install Custom recovery
Download TWRP 2.6.3.3 from here: http://techerrata.com/browse/twrp2/m7
Achieve S-OFF, if not already!
With your hboot 1.5x use rumrunner or firewater to get S-Off: http://firewater-soff.com/ or http://rumrunner.us/
Try all options!
Change CID to the new code:
Code:
[B][I]adb reboot bootloader
fastboot oem writecid HTC__001[/I][/B] <- (CID is exactly 8 characters)
[B][I]fastboot reboot-bootloader[/I][/B]
Change MID to the new code: PN0710000 using: [TOOL] MID change without ENG HBOOT | Aroma GUI
Remove "Tampered" with the Guru Bootloader Reset Tool
Download and flash 4.19.401.9 firmware; place firmware in your fastboot/adb folder and rename to firmware.zip. Ensure you have moved all of your personal items off of your phone this firmware will wipe your phone. Open a command window in your fastboot/adb folder and type:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Execute http://www.htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe/ which now matches your CID & MID
There is no need to lock/relock bootloader with S-OFF, and do not even THINK about going back to S-ON!!!
Now you can receive the OTAs or flash them manually.
OTA_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.11-4.19.401.9_R_release_355954met8o678uio0omu3.zip
OTA_M7_UL_K44_SENSE60_MR_HTC_Europe_5.11.401.10-4.19.401.11_release_372404wj19h95c0x6oa19n.zip
OTA_M7_UL_K443_SENSE60_MR_HTC_Europe_6.09.401.5-5.11.401.10_release_386803.zip
OTA_M7_UL_K443_SENSE60_MR_HTC_Europe_6.09.401.10-6.09.401.5_release_397712mm1f6dd6rksg0p3s.zip
Click to expand...
Click to collapse
majmoz said:
Here is a outline of what you will need to do.
Click to expand...
Click to collapse
Thansk for the reply mate is it neccesary to change the MID of the phone?
Also the hboot is it good at 1.44?
Sli2cooL said:
Thansk for the reply mate is it neccesary to change the MID of the phone?
Also the hboot is it good at 1.44?
Click to expand...
Click to collapse
Only if it is different. I don't know your MID but if it is different from the Int'l MID then you will not be able to flash the firmware, RUU or OTAs.
Yes, it will change when you flash the firmware & RUU. I would keep a copy of it for future use.
majmoz said:
Only if it is different. I don't know your MID but if it is different from the Int'l MID then you will not be able to flash the firmware, RUU or OTAs.
Click to expand...
Click to collapse
I think it is 712000 from AT&T, quite different right?
Sli2cooL said:
I think it is 712000 from AT&T, quite different right?
Click to expand...
Click to collapse
Yes, just think you should only have to change it once!
majmoz said:
Yes, just think you should only have to change it once!
Click to expand...
Click to collapse
Ho danm , then i cannot get back to 7120? Anyways Int goes better i guess, no malfunction on LTE/4G?
Sli2cooL said:
Ho danm , then i cannot get back to 7120? Anyways Int goes better i guess, no malfunction on LTE/4G?
Click to expand...
Click to collapse
You can go back; just do the same steps for AT&T. If you have LTE/4G now you will still have LTE/4G after this process does not change the bands that are hard coded into the phone. The radio in the software merely enhances the bands that are in the phone but can not replace them.
majmoz said:
You can go back; just do the same steps for AT&T. If you have LTE/4G now you will still have LTE/4G after this process does not change the bands that are hard coded into the phone. The radio in the software merely enhances the bands that are in the phone but can not replace them.
Click to expand...
Click to collapse
Okey buddy thansk again for the help ill be trying it tomorrow and ill be updating the process. :good:
I missed this one, well it went well, now i can recieve the OTAs in auto mode, THX for the help @majmoz.
Sorry but when I type "fastboot flash zip Rom.zip" fastboot stops, Someone, can help me? :crying:
I'm S-ON
hboot 1.57
CID: CWS__001