Undoing a Full GPE conversion - One (M7) Q&A, Help & Troubleshooting

I did the full rom conversion to my Dev HTC on. But now i need to undo it since its a work phone so i can do some testing on it. I am trying to find a guide but all i am find is how to do it. Anyone have a guide or tios on how to go back to stock? Can i just do a RUU restore or will the sOff and new CID mess it up?
Thanks

Festaman said:
I did the full rom conversion to my Dev HTC on. But now i need to undo it since its a work phone so i can do some testing on it. I am trying to find a guide but all i am find is how to do it. Anyone have a guide or tios on how to go back to stock? Can i just do a RUU restore or will the sOff and new CID mess it up?
Thanks
Click to expand...
Click to collapse
post a "fastboot getvar all" (excluding IMEI and s/n) and what your original MID and CID were.

nkk71 said:
post a "fastboot getvar all" (excluding IMEI and s/n) and what your original MID and CID were.
Click to expand...
Click to collapse
Thats one of my problems now. I dont know my oringal CID. trying to find it. Its an HTC Dev 64gb. I am setting up adb now on this machine.

Festaman said:
Thats one of my problems now. I dont know my oringal CID. trying to find it. Its an HTC Dev 64gb. I am setting up adb now on this machine.
Click to expand...
Click to collapse
Then is should be:
MID = PN0712000
CID = BS_US001
if you need to 101% sure, you could pull the mfg partition and check.

Thanks!
nkk71 said:
Then is should be:
MID = PN0712000
CID = BS_US001
if you need to 101% sure, you could pull the mfg partition and check.
Click to expand...
Click to collapse
Huge help, thanks dude!

Related

Flashing a RUU?

Hello there
These are the current stats of my device:
ROM: TrickDroid 7.5.0
CID: superCID 11111111
S-OFF
Recovery: TWRP 2.5.0
Bootloader: Unlocked
If I want to flash a RUU, I understand that just about ANY RUU will work because I have Super CID, but I want to know if there certain prerequists to flashing a RUU? Like for instance would I have to relock bootloader, set it to S-ON, flash stock recovery first, etc?
I'll probably be flashing either one of those:
RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A .14.3250.13_10.33.1150.01_release_311678_signed.exe
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Thanks
TarekElsakka said:
Hello there
These are the current stats of my device:
ROM: TrickDroid 7.5.0
CID: superCID 11111111
S-OFF
Recovery: TWRP 2.5.0
Bootloader: Unlocked
If I want to flash a RUU, I understand that just about ANY RUU will work because I have Super CID, but I want to know if there certain prerequists to flashing a RUU? Like for instance would I have to relock bootloader, set it to S-ON, flash stock recovery first, etc?
I'll probably be flashing either one of those:
RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A .14.3250.13_10.33.1150.01_release_311678_signed.exe
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Thanks
Click to expand...
Click to collapse
You should be able to flash the ruu the way you are. The only differences between your phone and mine when I flashed the brightstar ruu is the Rom I was on and I had relocked my bootloader. S-off will be retained after the flash but twrp will be replaced with the stock recovery. If it fails to flash you can try it again after relocking the bootloader but I don't think it's necessary.
Thank you very much. I won't need the bootloader to be unlocked anyhow in order to receive OTA updates so I might as well relock it and not flash a custom recovery. I do not need to be S-ON in order to receive OTA updates, right? Just locked bootloader, RUU, stock recovery and the proper CID (like HTC__001, for instance)? And while S-OFF, is changing CID from 111111 to HTC__001 as easy as using one command like
Code:
fastboot oem writecid 11111111
?
TarekElsakka said:
Thank you very much. I won't need the bootloader to be unlocked anyhow in order to receive OTA updates so I might as well relock it and not flash a custom recovery. I do not need to be S-ON in order to receive OTA updates, right? Just locked bootloader, RUU, stock recovery and the proper CID (like HTC__001, for instance)? And while S-OFF, is changing CID from 111111 to HTC__001 as easy as using one command like
Code:
fastboot oem writecid 11111111
?
Click to expand...
Click to collapse
Your pretty much spot on... Keep in mind that for otas your model id needs to be right for the ruu you flash as well as the cid. For example my phone is a US AT&T model has the same model id for the US dev version. So I just needed to be sure to flash the US dev ruu (brightstar) and then set the correct cid (bs_us001) and life is good. Problem is I don't personally know the model id or cid for the ruus you intend to flash. The good news is you can find your model id as well as change it if you need to. The threads to do this are pretty easy to find I'll get a link if you need me too. And to confirm "fastboot oem writecid ********" is what ya need... The asterisks are of course whatever cid you intend to write.
---------- Post added at 03:35 PM ---------- Previous post was at 03:14 PM ----------
http://forum.xda-developers.com/showthread.php?t=2269317&highlight=+model+id+
You can find your model id by doing this in this thread if you need to
Thank you so much for your reply. So from what I understood, in order to go back to stock, I'd have to flash a RUU that will be compatible with my Model ID, correct? I do know what my model is, and it is PN0711000 if I am not mistaken (I have it saved on a text file somewhere), but the problem is that I will not know which model ID I need and for which RUU. And by the way, if something ever goes wrong with my device after returning it to full stock but with a different Model ID, wouldn't HTC be able to figure that out and void my warranty? Sorry for the 20 questions I am very new to this. I appreciate your help.
TarekElsakka said:
Thank you so much for your reply. So from what I understood, in order to go back to stock, I'd have to flash a RUU that will be compatible with my Model ID, correct? I do know what my model is, and it is PN0711000 if I am not mistaken (I have it saved on a text file somewhere), but the problem is that I will not know which model ID I need and for which RUU. And by the way, if something ever goes wrong with my device after returning it to full stock but with a different Model ID, wouldn't HTC be able to figure that out and void my warranty? Sorry for the 20 questions I am very new to this. I appreciate your help.
Click to expand...
Click to collapse
Just replied to you in another thread lol... Um if that's your model id I believe... Emphasis on believe... That matches the Europe ruu and possibly the Asia one too. Maybe someone who knows for sure will pop in here and confirm. As far as the warranty stuff if there is no ruu for you specific carrier then make a fresh nandroid backup of the stock Rom and with s-off can be made like it was when you bought it.
Yeah I just saw your post there, thank you lol. Unfortunately I was stupid enough not to make a Nandroid Backup of my stock ROM before I went ahead and flashed a custom one.
viperlox said:
Just replied to you in another thread lol... Um if that's your model id I believe... Emphasis on believe... That matches the Europe ruu and possibly the Asia one too. Maybe someone who knows for sure will pop in here and confirm. As far as the warranty stuff if there is no ruu for you specific carrier then make a fresh nandroid backup of the stock Rom and with s-off can be made like it was when you bought it.
Click to expand...
Click to collapse
The MID for UK RUU is PN0710000
Rex2369 said:
The MID for UK RUU is PN0710000
Click to expand...
Click to collapse
Thank you so much. So MID PN0710000 and CID HTC__001. Correct?
TarekElsakka said:
Thank you so much. So MID PN0710000 and CID HTC__001. Correct?
Click to expand...
Click to collapse
Yeah that is correct.

please help

hi everybody i need help i have this problem i need now to come back to stock rom but i dont know any version :crying::crying::crying::crying::crying:
mounsif said:
hi everybody i need help i have this problem i need now to come back to stock rom but i dont know any version :crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
First we need your device's CID number.
The fastboot command is: fastboot getvar cid.
Then search for the stock rom for your CID.
mounsif said:
hi everybody i need help i have this problem i need now to come back to stock rom but i dont know any version :crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Go to revone http://forum.xda-developers.com/showthread.php?t=2314582 and make sure to remove the tampered and relocked messages and get S-Off while you still can with Hboot 1.44.. Then flash the latest Europe RUU from here http://forum.xda-developers.com/showthread.php?t=2207874.
farang4u said:
first we need your device's cid number.
The fastboot command is: Fastboot getvar cid.
Then search for the stock rom for your cid.
Click to expand...
Click to collapse
cid : Htc_j15
mounsif said:
cid : Htc_j15
Click to expand...
Click to collapse
You mean HTC__J15? You have to search google for the RUU for that CID. It's an Arabic rom and I'm having no luck finding it myself.
If none is available, you can follow @gee2012's advise. Carries a bit of risk tho.
Edit: This RUU from here might work. http://forum.xda-developers.com/showpost.php?p=42931982&postcount=1061
Or, try searching this thread: http://forum.xda-developers.com/showthread.php?p=39588860
farang4u said:
You mean HTC__J15? You have to search google for the RUU for that CID. It's an Arabic rom and I'm having no luck finding it myself.
If none is available, you can follow @gee2012's advise. Carries a bit of risk tho.
Edit: This RUU from here might work. http://forum.xda-developers.com/showpost.php?p=42931982&postcount=1061
Or, try searching this thread: http://forum.xda-developers.com/showthread.php?p=39588860
Click to expand...
Click to collapse
downloading......
u think 1.29.401.16 work ?????

first post need help returning to stock

hello every one this is my first post i need some help please.
i bought a htc one preowned and i have since been in settings and its running a custom rom
android revolution hd 12.1 by mike 1986
my phone cid is htc_001
how do i return it to stock htc os
i have read a few posts before posting here i no i have to re lock bootloader then flash the ruu
i was wondering is there an easier way to relock bootloader and flash the ruu could some one also point me in the right direction
to which ruu to download with a link if possible to download.
thanks in advance for any help u may give with some simple instructions that i can understand as this is new to me and do not want to
make a mistake.
thankyou.
Is it S-OFF at the moment?
EddyOS said:
Is it S-OFF at the moment?
Click to expand...
Click to collapse
says m7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4a.18.3263.15
openDSP-v26.120.274.0202
eMMC-boot
so im guessing so
You don't need to relock, if you're s-off you can run whatever RUU you like.
iElvis said:
You don't need to relock, if you're s-off you can run whatever RUU you like.
Click to expand...
Click to collapse
thnks for your help can u link me to the correct ruu if u dont mind been looking not sure which one to download
thanks very much for your help to all.
Infamouslimey said:
thnks for your help can u link me to the correct ruu if u dont mind been looking not sure which one to download
thanks very much for your help to all.
Click to expand...
Click to collapse
Where was the phone purchased and what was the carrier? It's possible your CID was changed.
Assuming htc__001 is correct, the RUU collection is here:
http://forum.xda-developers.com/showthread.php?p=39588860
There are no RUUs for 4.2, so this would mean downgrading. But you should then start getting OTAs.
Note that running a RUU will fully wipe the phone. So back up anything on it you want to keep.
iElvis said:
Where was the phone purchased and what was the carrier? It's possible your CID was changed.
Assuming htc__001 is correct, the RUU collection is here:
http://forum.xda-developers.com/showthread.php?p=39588860
There are no RUUs for 4.2, so this would mean downgrading. But you should then start getting OTAs.
Click to expand...
Click to collapse
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Infamouslimey said:
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Click to expand...
Click to collapse
You have superCID, which means any RUU will run. You have the generic European model. CIDGetter is pulling the original cid from some system file, but it doesn't reflect the actual cid.
Infamouslimey said:
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Click to expand...
Click to collapse
will this ruu work
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Infamouslimey said:
will this ruu work
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Click to expand...
Click to collapse
Yes, that's the one you want. You don't need to relock or anything being s-off. Just plug into your computer and run the ruu.
iElvis said:
Yes, that's the one you want. You don't need to relock or anything being s-off. Just plug into your computer and run the ruu.
Click to expand...
Click to collapse
thank you very much for all your help great site with such helpful members.
will this method re-lock bootloader and put s-off back to s-on or whatever its called ?
Infamouslimey said:
will this method re-lock bootloader and put s-off back to s-on or whatever its called ?
Click to expand...
Click to collapse
No and no. You have to do those manually, and there is no need to here.
if i wanted to re lock bootloader and put s back on how would i do it trying to learn so i dont have to keep asking for help ?
Infamouslimey said:
if i wanted to re lock bootloader and put s back on how would i do it trying to learn so i dont have to keep asking for help ?
Click to expand...
Click to collapse
That is a bit trickier and riskier since you don't know what was done to your phone before you bought it. I don't recommend going back to s-on because of this. However, running the correct RUU should put you back to safe stock.
Once the RUU has run and you've confirmed that the phone boots and is back to a stable stock configuration, you need to reboot and run a series of commands in fastboot:
fastboot oem writecid HTC__001
This will restore your stock CID. Note that there are two underscores there.
fastboot reboot-bootloader
Confirm on your bootloader screen that the CID is correct.
fastboot oem lock
This will relock your bootloader. Reboot again and confirm that it says "LOCKED" on your bootloader (Not "RELOCKED"). Boot up your phone and confirm that everything seems to be running correctly. You may want to give this a few days. Then reboot to bootloader when you're comfortable with it.
fastboot oem writesecureflag 3
This will put you back to s-on. When you reboot from here, your bootloader should say LOCKED and S-ON as if it was out of the box.
iElvis said:
That is a bit trickier and riskier since you don't know what was done to your phone before you bought it. I don't recommend going back to s-on because of this. However, running the correct RUU should put you back to safe stock.
Once the RUU has run and you've confirmed that the phone boots and is back to a stable stock configuration, you need to reboot and run a series of commands in fastboot:
fastboot oem writecid HTC__001
This will restore your stock CID. Note that there are two underscores there.
fastboot reboot-bootloader
Confirm on your bootloader screen that the CID is correct.
fastboot oem lock
This will relock your bootloader. Reboot again and confirm that it says "LOCKED" on your bootloader (Not "RELOCKED"). Boot up your phone and confirm that everything seems to be running correctly. You may want to give this a few days. Then reboot to bootloader when you're comfortable with it.
fastboot oem writesecureflag 3
This will put you back to s-on. When you reboot from here, your bootloader should say LOCKED and S-ON as if it was out of the box.
Click to expand...
Click to collapse
thanks very much for all your help ill install the fastboot files anyway so if need them there there.
many thanks
I too need to put my T-mobile HTC One back to stock somehow, but don't even know where to start, I saw this thread so I didn't want to clutter up the subforum, and thought that maybe I should ask here. I'm at 1.27.531.11, S-ON, rooted w/ unlocked bootloader, and would like to make it look like nothing happened to it when I return it to the store tomorrow. Could you please give me some pointers?
N0wy0ud1e said:
I too need to put my T-mobile HTC One back to stock somehow, but don't even know where to start, I saw this thread so I didn't want to clutter up the subforum, and thought that maybe I should ask here. I'm at 1.27.531.11, S-ON, rooted w/ unlocked bootloader, and would like to make it look like nothing happened to it when I return it to the store tomorrow. Could you please give me some pointers?
Click to expand...
Click to collapse
You need to s-off first or it will say "RELOCKED" on the bootloader. Problem is you may or may not be able to s-off right now. There is a new T-Mo exploit that supposedly works but I know nothing about it.
Once you do that, you can run an older RUU, which will remove the TAMPERED from the bootloader, then relock and s-on as described above.
iElvis said:
You need to s-off first or it will say "RELOCKED" on the bootloader. Problem is you may or may not be able to s-off right now. There is a new T-Mo exploit that supposedly works but I know nothing about it.
Once you do that, you can run an older RUU, which will remove the TAMPERED from the bootloader, then relock and s-on as described above.
Click to expand...
Click to collapse
Crap. Well I know they're not going to check the bootloader lol, just that when you turn on the phone, you'll see the red text at the bottom saying "Developmental purposes" and I can't remember the rest of the message. Can I make that disappear so it just shows nothing on the white background but the green HTC logo? Btw thanks for the reply.
N0wy0ud1e said:
Crap. Well I know they're not going to check the bootloader lol, just that when you turn on the phone, you'll see the red text at the bottom saying "Developmental purposes" and I can't remember the rest of the message. Can I make that disappear so it just shows nothing on the white background but the green HTC logo? Btw thanks for the reply.
Click to expand...
Click to collapse
That goes away when you relock.

[Q] How to find out what carrier this phone is?

i got the phone stuck on TWRP so i downloaded the telus ruu and installed it fine, then i noticed there was a rogers one too. is there anyway to tell what carrier this phone is for? i have no sim cards to test it out besides a fido one. its the 801e UL variant. someone must be able to help me i have searched everywhere for answers.
In fastboot: fastboot getvar all
This will display your CID
Marc199 said:
In fastboot: fastboot getvar all
This will display your CID
Click to expand...
Click to collapse
ya but what if the cid was changed to 1111111111 to get s-off?
I don't think it is possible to find out what your original CID was. Where did you buy the phone?
gnome9er said:
ya but what if the cid was changed to 1111111111 to get s-off?
Click to expand...
Click to collapse
that's SuperCID, keep it as is and download CIDGetter from Play Store, when it sees SuperCID it will pull CID from a secondary location, hopefully that wasn't changed and it will show your original CID.

RUU For 4M Radio

Hey Guys. Im looking to unroot yet another HTC One m7. AT&T continues to send me defective devices. This one is a 1.57 Hboot 4M.27.3218.15 radio. I cant find a RUU for this setup. Any help would be greatly appreciated.
sjorge3442 said:
Hey Guys. Im looking to unroot yet another HTC One m7. AT&T continues to send me defective devices. This one is a 1.57 Hboot 4M.27.3218.15 radio. I cant find a RUU for this setup. Any help would be greatly appreciated.
Click to expand...
Click to collapse
radio version is irreverent when searching for a RUU. CID, MID and version-main are the information needed to find one. Best thing is to post your output of "fastboot getvar all' except your imei and serialno. Unfortunately, I don't think there is any AT&T ruu for version on hboot 1.57.
Latest RUU for AT&T (CID: CWS__001 MIDN0712000) is 4.18.502.7 and will require s-off because its a downgrade (hboot 1.56)
alray said:
radio version is irreverent when searching for a RUU. CID, MID and version-main are the information needed to find one. Best thing is to post your output of "fastboot getvar all' except your imei and serialno. Unfortunately, I don't think there is any AT&T ruu for version on hboot 1.57.
Latest RUU for AT&T (CID: CWS__001 MIDN0712000) is 4.18.502.7 and will require s-off because its a downgrade (hboot 1.56)
Click to expand...
Click to collapse
Cool. Never knew that. I will need to S off anyway since that's how to return to stock. I didn't know radio didn't matter. I can flash a 1.56 ruu with no problems?
sjorge3442 said:
Cool. Never knew that. I will need to S off anyway since that's how to return to stock. I didn't know radio didn't matter. I can flash a 1.56 ruu with no problems?
Click to expand...
Click to collapse
If you have to send the phone for warranty I will even recommend you to use the 1.26.501.8 RUU (hboot 1.44) so you can remove the tampered flag from bootloader because it might come back if removed on hboot 1.55 and up.
Take a look at nkk71's guide linked in my signature.
sjorge3442 said:
Cool. Never knew that. I will need to S off anyway since that's how to return to stock. I didn't know radio didn't matter. I can flash a 1.56 ruu with no problems?
Click to expand...
Click to collapse
alray said:
If you have to send the phone for warranty I will even recommend you to use the 1.26.501.8 RUU (hboot 1.44) so you can remove the tampered flag from bootloader because it might come back if removed on hboot 1.55 and up.
Take a look at nkk71's guide linked in my signature.
Click to expand...
Click to collapse
I've done this a few times now so I'm no stranger to thing. Last two times I did the 1.56 update, plus I have those files downloaded already. They keep sending me refurbs and each one they send has build quality issues. Its unreal.
sjorge3442 said:
I've done this a few times now so I'm no stranger to thing. Last two times I did the 1.56 update, plus I have those files downloaded already. They keep sending me refurbs and each one they send has build quality issues. Its unreal.
Click to expand...
Click to collapse
Well return it to stock so you can send it for warranty again and ask for an upgrade to another model. Explain that you are not satisfied with this model because you have experienced issues on each replacement units. Might worth a try...
alray said:
Well return it to stock so you can send it for warranty again and ask for an upgrade to another model. Explain that you are not satisfied with this model because you have experienced issues on each replacement units. Might worth a try...
Click to expand...
Click to collapse
Yeah that's the plan. I tried last time, but they swore they would send me a new. box phone this time. However, I ended up with a "like new" phone. This won't be happening again. Hoping for an M8
sjorge3442 said:
Hoping for an M8
Click to expand...
Click to collapse
That is exactly what I had in mind.
Good luck!

Categories

Resources