[Q] Changing CID back to original
- Thread starter stanny2k
- Start date
I read your other post http://xdaforums.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://xdaforums.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.
In that case, I take that back
I'm going to follow your guide again tonight.The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
In that case, I take that back
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Also, please follow the instruction properly, no jumping, skipping or adding steps
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
Thanks, I like thoseOh, and have a "thanks"
Ok, I'll grab this!
Will do! Don't worry, word for word!Also, please follow the instruction properly, no jumping, skipping or adding steps
Noted.
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
Appreciate it, thank you
yep, exactly, after the 1st OTA, your phone will be 100% "out-of-the-box"; once the OTA updates successfully it will mean
1- your entire firmware was updated (hboot, recovery, kernel, radio, etc)
2- your ROM will also be updated, proving everything is 100%
otherwise, the OTA would not be able to complete.
Now due to a patch in later hboots (in particular 1.55 as far as i know), going from s-off to s-on, will (after a few reboots) result in "tamper detected - rebooting" and TAMPERED is back.
so in summary, if you really need to go S-On, you do so after first successful OTA (using the command mentioned in my guide), and then you can take any OTAs you like.
hope that makes sense
Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
Sorry to hear you had some troubles
, are you on Windows 8 or 8.1, is that why adb wasn't working.Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
Sorry to hear you had some troubles
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.
Yup, I did fastboot erase cache before and after flashing it, both were successful as well. I didnt check the MD5, I just installed it after I downloaded it.. it was midnight by the time I got that far! I was tired!
Yeah and thanks a lot for your help mate. Really appreciate it.
I'll let you know the outcome with HTC
Hopefully they find nothing untoward!Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!
finger gymnastics :laugh:Well, that was an eventful evening
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it
problem is with the CWM i recommended, works just fine when flashed, but when using "fastboot boot CWM.img" looks like 6.0.3.2 doesnt work properly with adb, 6.0.4.5 on the other hand works with "fastboot boot"
I'll update my guide with some more "visuals" whenever I get a chance....
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
I read your other post http://xdaforums.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://xdaforums.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers1
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.1In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Also, please follow the instruction properly, no jumping, skipping or adding steps
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
Thanks, I like thoseOh, and have a "thanks"
1
yep, exactly, after the 1st OTA, your phone will be 100% "out-of-the-box"; once the OTA updates successfully it will mean
1- your entire firmware was updated (hboot, recovery, kernel, radio, etc)
2- your ROM will also be updated, proving everything is 100%
otherwise, the OTA would not be able to complete.
Now due to a patch in later hboots (in particular 1.55 as far as i know), going from s-off to s-on, will (after a few reboots) result in "tamper detected - rebooting" and TAMPERED is back.
so in summary, if you really need to go S-On, you do so after first successful OTA (using the command mentioned in my guide), and then you can take any OTAs you like.
hope that makes sense1Sorry to hear you had some troubles, are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
New posts
-
[CLOSED] change Imei wifi mac Bluetooth mac android id, gsf without LSPOSED- Latest: Oswald Boelcke
-
