Related
Back when i first got my phone i did the supercid mod on my phone, everytime i flash a rom i have to do other things just because of it (larger mms, install wifi calling patch etc etc) my girlfriends sensation on the other hand is NOT supercid and she never has to do any of the additional patches i have to do.
So is there any way i can reverse the supercid mod on my phone?
Super CID has nothing to do with patch flashing, but if you want to return to stock cid just fallow the steps to get the super cid and replace "11111111" with your original cid.
If your phone was unbranded your cid should be "HTC__001"
_HTC_DHD_ said:
Super CID has nothing to do with patch flashing, but if you want to return to stock cid just fallow the steps to get the super cid and replace "11111111" with your original cid.
If your phone was unbranded your cid should be "HTC__001"
Click to expand...
Click to collapse
how do i know what my original cid would be?
Hello well if you you know how to use the adb command tool (black window with command line) you just type in "adb getvar cid" and it should show your original cid hope I could help
Edit: use while phone is connected with USB debugging on
I AM M07S said:
Hello well if you you know how to use the adb command tool (black window with command line) you just type in "adb getvar cid" and it should show your original cid hope I could help
Edit: use while phone is connected with USB debugging on
Click to expand...
Click to collapse
That is wrong. If you use that, i'll only show the CURRENT CID of the phone, which would be superCID in this case.
There's a CID database somewhere in the development section. Search for it. It has a comprehensive list of CIDs with your carriers name.
illuminarias said:
That is wrong. If you use that, i'll only show the CURRENT CID of the phone, which would be superCID in this case.
There's a CID database somewhere in the development section. Search for it. It has a comprehensive list of CIDs with your carriers name.
Click to expand...
Click to collapse
Oh well I'm sorry but last time I did this it gave me my original and I know this because I have changed it to SuperCID and last night infact I was playing with the adb commands and it gave me my original CID unless of course it has gone back to the original which in that case i am really sorry for being a noob to the android xda community (but im only 17)
If you are on T-Mobile US, then the CID is T-MOB010.
Sent from my HTC Sensation Coredroid 2.7
Try this...
Hi,
I had problems with WIFI calling not installing, so I decided to remove SuperCID. I followed the instructions in this post:
http://forum.cyanogenmod.com/topic/31756-wifi-calling-missing-you-have-supercid-here-is-a-solution/
I didn't use the file from the post, as it didn't work for me. I found another file and everything worked perfectly, I am attaching the new file.
Please be aware that this will get you ENG S-OFF.
cgjjaf said:
Hi,
I had problems with WIFI calling not installing, so I decided to remove SuperCID. I followed the instructions in this post:
http://forum.cyanogenmod.com/topic/31756-wifi-calling-missing-you-have-supercid-here-is-a-solution/
I didn't use the file from the post, as it didn't work for me. I found another file and everything worked perfectly, I am attaching the new file.
Please be aware that this will get you ENG S-OFF.
Click to expand...
Click to collapse
Thanks for the help, it's ****ing monday morning and i feel dumb, but what is ENG S-OFF?
I unlocked my phone using xda guide, at the moment I have super cid, if I reverse my cid back to original, will I loose my unlock?
raul602 said:
Thanks for the help, it's ****ing monday morning and i feel dumb, but what is ENG S-OFF?
Click to expand...
Click to collapse
engineering bootloader with security off..basically meaning you have read/write permissions for the system and can flash a custom rom..Since you changed your CID, you also should be S-OFF.
However, I don't think you fully understand what CID does, b/c I don't see how this would cause the issues your having. Super CID allows for you to flash a STOCK rom from another carrier, so you could flash an unbranded Sensation RUU or a TMo-US S4G RUU, or whatever, through bootloader. It allows to "debrand" your phone, meaning you're not stuck to your carrier specific rom. This is different than flashing a custom rom thru recovery, which your CID doesn't matter, bc custom roms are not carrier specific roms..
CID is basically just a variable that tells the RUU what carrier your phone is from and what rom can be flashed on it.
Now, to get your CID back to stock, do the following:
Connect to ADB, run "adb reboot-bootloader"
Then enter the command "fastboot oem writecid 11111111", except put your carriers CID in place. If you do not know your CID, refer to this thread http://forum.xda-developers.com/showthread.php?t=1195475
Then run "fastboot reboot-bootloader" and then "fastboot getvar cid" to verify it successfully changed.
Hope that cleared things up some.
bakili said:
I unlocked my phone using xda guide, at the moment I have super cid, if I reverse my cid back to original, will I loose my unlock?
Click to expand...
Click to collapse
No it will not..CID is basically just a variable, you need to have S-OFF to change it, but changing it won't effect S-OFF or SIM unlock..
civicvx94 said:
engineering bootloader with security off..basically meaning you have read/write permissions for the system and can flash a custom rom..Since you changed your CID, you also should be S-OFF.
However, I don't think you fully understand what CID does, b/c I don't see how this would cause the issues your having. Super CID allows for you to flash a STOCK rom from another carrier, so you could flash an unbranded Sensation RUU or a TMo-US S4G RUU, or whatever, through bootloader. It allows to "debrand" your phone, meaning you're not stuck to your carrier specific rom. This is different than flashing a custom rom thru recovery, which your CID doesn't matter, bc custom roms are not carrier specific roms..
CID is basically just a variable that tells the RUU what carrier your phone is from and what rom can be flashed on it.
Now, to get your CID back to stock, do the following:
Connect to ADB, run "adb reboot-bootloader"
Then enter the command "fastboot oem writecid 11111111", except put your carriers CID in place. If you do not know your CID, refer to this thread http://forum.xda-developers.com/showthread.php?t=1195475
Then run "fastboot reboot-bootloader" and then "fastboot getvar cid" to verify it successfully changed.
Hope that cleared things up some.
No it will not..CID is basically just a variable, you need to have S-OFF to change it, but changing it won't effect S-OFF or SIM unlock..
Click to expand...
Click to collapse
First of all, thank you very much for your response, I really didn't know exactly what it was till you explained it, THe reason i want to revert back to stock is simply because there are certain things that never seem to work on my phone that always work perfectly on my girlfriends phone, first one being WIFI(never gets installed and second being small mms pics, the ONLY difference between her and my phone is that i am superCID and she is not, i can get the patches and fix it but i don't really need supercid now that i understand it.
Seriously though, thank you!
No problem at all, glad to help! Hope you get things figured out..
i got a mytouch 4g slide from ebay and it shipped s-off!
one catch though..
the hboot is 1.44.0007 and i tried to fastboot flash recovery
and it said "sending"
but it said "writing" FAILED remote: not allowed
should i pack the img into a PG59IMG.zip and then do it that way through the sd?
or get the Juopunutbear bootloader and pack that into a PPG59IMG instead?
or just run revolutionary?
can i try "fastboot oem unlock"?
i assume that the bootloader just wont accept fastboot commands even though fastboot reads it
i just got it a couple hours ago so im just trying to fumble through all my options i have here
thank ya
This should get you to where you want to be......
http://forum.xda-developers.com/showthread.php?t=1801106
Revolutionary won't work on the HBoot you have & even though 'fastbboot oem lock' IS a command the "unlock" is acquired thru HTCdev & the binary supplied by them. You flash that file and achieve unlock. Juopunutbear & the wire trick have already been run or you wouldn't have S-Off yet.
If you can go to a DOS window and run
ADB reboot bootloader .............to get to the HBoot bootloader screen your commands are being accepted. If not it sounds more to me like a driver issue is holding you back on connecting. The guide I gave a link to should iron things out for you though.
WeekendsR2Short said:
This should get you to where you want to be......
http://forum.xda-developers.com/showthread.php?t=1801106
Revolutionary won't work on the HBoot you have & even though 'fastbboot oem lock' IS a command the "unlock" is acquired thru HTCdev & the binary supplied by them. You flash that file and achieve unlock. Juopunutbear & the wire trick have already been run or you wouldn't have S-Off yet.
If you can go to a DOS window and run
ADB reboot bootloader .............to get to the HBoot bootloader screen your commands are being accepted. If not it sounds more to me like a driver issue is holding you back on connecting. The guide I gave a link to should iron things out for you though.
Click to expand...
Click to collapse
well my fastboot drivers are fine because it has no issue finding the device..
the 1.44.0007 hboot is the only one listed on the the revolutionary.io website because i had gone and checked just to verify
and my adb issworking just fine also as i tested with "adb devices" to get my serial to type into the revolutionary page to make my beta key
i think that the hboot that came after the one thats on my device now is the htcdev one
frickinjerms said:
well my fastboot drivers are fine because it has no issue finding the device..
the 1.44.0007 hboot is the only one listed on the the revolutionary.io website because i had gone and checked just to verify
and my adb issworking just fine also as i tested with "adb devices" to get my serial to type into the revolutionary page to make my beta key
i think that the hboot that came after the one thats on my device now is the htcdev one
Click to expand...
Click to collapse
I apologize. My error. It is the 1.45.xxxx HBoot that requires the 'wire trick' to get S-Off. So when you run "fastboot flash recovery recovery.img" you get the "sending" message & then the "writing" FAILED remote: not allowed? This seems odd to me because it is an error message I've not yet read about. I AM doing some checking around to see if that's been covered somewhere so MAYBE 2 heads will be better than one. Have patience..... :good:
Are you attempting to get superuser prior to flashing the recovery?
Hastily spouted for your befuddlement
Ah HA! GREAT point. :good:
Coug76 said:
Are you attempting to get superuser prior to flashing the recovery?
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
haha no i know i need a custom recovery to get su
i downloaded a radio PC59IMG and swapped out the radio img with the CMW img and it flashed thru the bootloader and it gave me CMW
and then flashed aokp so im good for now
so my guess is that the bootloader in its current state just doesn't support fastboot commands, im still iffy about putting a different bootloader in a PC59IMG and flashing though
When I run fastboot from nix I have to ./fastboot flash blah. Sorry I've been drinking and don't wanna run through the posts right now, but that's how I do it
Sent from my HTC MyTouch 4G Slide running MikXE
strapped365 said:
When I run fastboot from nix I have to ./fastboot flash blah. Sorry I've been drinking and don't wanna run through the posts right now, but that's how I do it
Sent from my HTC MyTouch 4G Slide running MikXE
Click to expand...
Click to collapse
Haven't we all been today
Sent from my myTouch_4G_Slide using Tapatalk 2
I'm glad I wasn't the only one.
so if i pack the juopunutbear hboot into a PG59IMG and flash will i turn my device into a paperweight or will i be updated without a hiccup?
frickinjerms said:
so if i pack the juopunutbear hboot into a PG59IMG and flash will i turn my device into a paperweight or will i be updated without a hiccup?
Click to expand...
Click to collapse
I wouldn't try anything like that. Not saying you will brick, but I'm not saying won't either. Just do the whole process
Sent from my HTC MyTouch 4G Slide running MikXE
haha good enough for me ive successfully used the PG59IMG for a splash screen and recovery so i guess i can live without fastboot for now
just an update, i flashed the pg59img that has all the most recent goodies packed in so im on the latest hboot with radios and yada yada and have still retained s-off, i know i need to unlock with htcdev now, but will this allow me to put the juopunutbear hboot thru a pg59img now?
Sent from my Transformer Prime TF201 using Tapatalk 2
and my problem has been fixed i got the PC58IMG of the latest ruu flashed it and then flash the jb_hboot within the bootloader.. so i have the Juopunutbear Hboot and all my fastboot commands i wanted for writing partitions are working so woohoo!
Smoooth move! Congratulations! :good:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
very simple to fix. The fact that you got to the "ready to unlock?" screen means the unlock token works.
go into settings on the phone go to power. Turn OFF fastboot.
Power off the phone completely.
Boot to bootloader
send the unlock.bin again
this time it will stick.
saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
Sometimes the phone can get confused about its locked state.
To fix:
-Force reboot the phone. Hold the power button for 10+ seconds until bottom lights flash and then stop.
-Boot in to bootloader
Now force the phone to lock even if you think it is locked already.
-fastboot oem lock
-fastboot flash unlocktoken Unlock_code.bin
Sending "fastboot oem lock" tends to get the phone back on the right track so it doesn't just keep rebooting in to a relocked state.
get into bootloader manually volume down + power.
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
yes root will happen.
unlock bootloader. Install twrp recovery. Flash the root package found here http://forum.xda-developers.com/showthread.php?t=1673935
Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?
Ethere said:
Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?
Click to expand...
Click to collapse
I think you may have to use fastboot flash recovery recovery.img because of the new limitations of the new HBOOT. It might be only for boot.imgs though
That worked rohan32 Thanks so much to both of you. Now I have an unlocked bootloader and TWRP installed. Going for root now. Thank you thank you thank you! You guys have saved me from wanting another phone!
[EDIT]Rooted as well. Again, thank you both so much!
thanks everyone i solved my problem.dint except quick replies from you guys.
Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
If you stay away from the AT&T cid you will be fine.
In theory things could change but at the moment so long as you have super cid prior to RUU flashing you will be fine.
OK I just got my AT&T HOX today and from what I've read hear there is no way to root it? Since I have 2.20.502.7 710RD but if I use super cid I can flash roms?
Without root you can't get super Cid
Please update the title and add "Resolved"
Sent from my HTC One XL using xda premium
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
fdavidson said:
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
Click to expand...
Click to collapse
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
ganeshp said:
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
Click to expand...
Click to collapse
Thanks ganeshp for the quick answer. I am pretty confident about the RUU as it is the same one I originally ran to move from custom ICS ROM to stock 2.3.4 ROM.
For Revolutionary, even in fastboot, it is stuck in "Waiting for devices..." I think it is because it issues "adb devices" command and expects some answer before carrying on to the bootloader. I would need it to skip this step. Are there any argument to revolutionary to do that?
Fred
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
fdavidson said:
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
Click to expand...
Click to collapse
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Jonny said:
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Click to expand...
Click to collapse
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly change for my device, i.e. PG5810000), would the CID affect anything?
Fred
fdavidson said:
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly chance for my device, i.e. PG5810000), would the CID affect anything?
Fred
Click to expand...
Click to collapse
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
dublinz said:
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
Click to expand...
Click to collapse
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
fdavidson said:
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
Click to expand...
Click to collapse
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
fdavidson said:
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
Click to expand...
Click to collapse
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
ganeshp said:
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
Click to expand...
Click to collapse
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
edit: i just read your first post
so you can not use revolutionary
fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
ahh even that got stuck huh ...try revolutionary again ..with phone boot-looping or when stuck at splash screen ..if revolutionary finds the device all good ..otherwise all doors closed
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
he tried revolutionary already ..and he currently didnt have a booting rom ..so it might not work
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
That was my original attempt but it looks like revolutionary expects the phone to be fully booted so it can set it himself in bootloader/fastboot through adb command. Since I can get into fastboot myself, If I could skip that part from revolutionary and have it do the next steps, I think I'd get a successful S-OFF. Any idea on how to do that?
Fred
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
ganeshp said:
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
Click to expand...
Click to collapse
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
fdavidson said:
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
Click to expand...
Click to collapse
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
ganeshp said:
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
Click to expand...
Click to collapse
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
fdavidson said:
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
Click to expand...
Click to collapse
then im out of ideas
one last try
try changing cid
fastboot oem writecid HTC__001
then
fastboot reboot-bootloader
then verify it
fastboot getvar cid
EDIT: if this worked then ..immediately flash the european unbranded 3.33 rom
hello guys, im new here.
anybody tried relocking their bootloader by using this command?
fastboot oem lock
and does it work and restores warranty conditions?
That command has been tried since the original Moto G and no, contrary to what some people think you can't reset the internal unlock counter. They will always know you unlocked it. If nothing else, they know because you got the unlock code from them. I'm not sure why people overlook this clearly posted sentence when they request the unlock code from Motorola.
"Unless you have a Developer Edition device, once you get the unlock code, your device is no longer covered by the Motorola warranty; in other words, please don't blame us if things go wrong, even if they appear unrelated to unlocking the bootloader."
Sent from my SM-T530NU using Tapatalk
creative21 said:
hello guys, im new here.
anybody tried relocking their bootloader by using this command?
fastboot oem lock
and does it work and restores warranty conditions?
Click to expand...
Click to collapse
That command will lock your bootloader again. However, locking and unlocking will wipe your device.
Upon receiving your unlock code from Motorola, your warranty is void; regardless if you unlock it or not. The sheer act of asking for and receiving the code voids your warranty.
Of course, if there is a true hardware issue that is not caused by software tinkering, you can still use that piece of the warranty.
Sent from my MotoG3 using Tapatalk
nikon120 said:
That command will lock your bootloader again. However, locking and unlocking will wipe your device.
Upon receiving your unlock code from Motorola, your warranty is void; regardless if you unlock it or not. The sheer act of asking for and receiving the code voids your warranty.
Of course, if there is a true hardware issue that is not caused by software tinkering, you can still use that piece of the warranty.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
after relocking, warning bootlogo is removed or can be replaced?
creative21 said:
after relocking, warning bootlogo is removed or can be replaced?
Click to expand...
Click to collapse
I think I can be replaced !, I'm not sure!
I will test and send feedback!
Jeconias Santos said:
I think I can be replaced !, I'm not sure!
I will test and send feedback!
Click to expand...
Click to collapse
but I think after reflashing stock, boot logo will be return to normal.
I tried that command and relock the bootloader several times as i didnt got the same battery backup as stock... So my question is after relocking and flahing stock rom... Do i get the OTA? and will it get flashed sucessfully?
sagar27691 said:
I tried that command and relock the bootloader several times as i didnt got the same battery backup as stock... So my question is after relocking and flahing stock rom... Do i get the OTA? and will it get flashed sucessfully?
Click to expand...
Click to collapse
Yes you will be able to get over the air updates after relocking bootloader if necessary system apps and files are not modified.
If you are not able to get ota you could also flash stick firmware images.
Thanks man... I flashed the whole stock rom from xda here only...
Even though I've run the commands to re-lock, going into the fastboot (bootloader) mode shows it's unlocked.
Anyone figure out a way to actually re-lock it?
JWhipple said:
Even though I've run the commands to re-lock, going into the fastboot (bootloader) mode shows it's unlocked.
Anyone figure out a way to actually re-lock it?
Click to expand...
Click to collapse
No, once it's unlocked, the counter will always show an unlocked bootloader. Best you can do is hide the opening unlocked bootloader screen.
In the 1st Moto G i have sucessfully relocked the bootloader.
You can use the command 'fastboot oem lock begin', then flash all files from fastboot firmware changing the logo file to logo-mod.bin (File that have removed the unlocked warning image, because flashing custom logo.bin doesn't check crc or hash when relocking the bootloader), then finish with 'fastboot oem lock' command.
Example:
fastboot oem lock begin
fastboot flash partition gpt.bin
- - - rest of commands
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
I don't have tested because i don't have unlocked my g3 bootloader yet.
Just try
jmadotme said:
In the 1st Moto G i have sucessfully relocked the bootloader.
You can use the command 'fastboot oem lock begin', then flash all files from fastboot firmware changing the logo file to logo-mod.bin (File that have removed the unlocked warning image, because flashing custom logo.bin doesn't check crc or hash when relocking the bootloader), then finish with 'fastboot oem lock' command.
Example:
fastboot oem lock begin
fastboot flash partition gpt.bin
- - - rest of commands
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
I don't have tested because i don't have unlocked my g3 bootloader yet.
Just try
Click to expand...
Click to collapse
Been there, done that, got the T-Shirt, doesn't stop the banner from saying the bootloader is unlocked.
JWhipple said:
Been there, done that, got the T-Shirt, doesn't stop the banner from saying the bootloader is unlocked.
Click to expand...
Click to collapse
Have you flashed moded logo.bin?
I still don't understand the point of all this... why are people trying to go through all the work of relocking the bootloader?!?! There is ZERO benefit to it... your warranty is still void (you don't even have to unlock, just agree to the terms and get the unlock token), it doesn't enhance resale value, it doesn't change the performance, so why all the effort to try to do it?!?!
acejavelin said:
I still don't understand the point of all this... why are people trying to go through all the work of relocking the bootloader?!?! There is ZERO benefit to it... your warranty is still void (you don't even have to unlock, just agree to the terms and get the unlock token), it doesn't enhance resale value, it doesn't change the performance, so why all the effort to try to do it?!?!
Click to expand...
Click to collapse
to get the new official OTA... if bootloader is locked and have stock rom we are able to get the OTA and can flash successfully with it... though it shows bootloader unlocked warning.
sagar27691 said:
to get the new official OTA... if bootloader is locked and have stock rom we are able to get the OTA and can flash successfully with it... though it shows bootloader unlocked warning.[emoji14]
Click to expand...
Click to collapse
Hmm... Are you sure? If you are unlocked but otherwise pure stock, you should still get OTAs, if your not then they are most likely blocked server-side not client-side. In other words just accepting the T&C of a Motorola bootloader unlock could not only void your warranty, but also blacklist your IMEI from OTAs as well.
I could be wrong, but I think your "barking up the wrong tree" here... I can tell you for sure that Huawei does it this way since Lollipop, if you unlock the bootloader your IMEI is blacklisted server-side... They are very straightforward about it.
Sent from my MotoG3 using Tapatalk
acejavelin said:
Hmm... Are you sure? If you are unlocked but otherwise pure stock, you should still get OTAs, if your not then they are most likely blocked server-side not client-side. In other words just accepting the T&C of a Motorola bootloader unlock could not only void your warranty, but also blacklist your IMEI from OTAs as well.
I could be wrong, but I think your "barking up the wrong tree" here... I can tell you for sure that Huawei does it this way since Lollipop, if you unlock the bootloader your IMEI is blacklisted server-side... They are very straightforward about it.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
not at all... already flashed official firmware 3 times after experiencing the less battery backup on custom roms. in this 3 times i flashed the modified bootlogo so didnt got the warning of bootloader unstlocked and not able to get the OTA but then again i flashed the official firmware 4th time and without that modified bootlogo in hope to get the latest OTA build no. LPI23.72-65 and it worked i got that update next day... and still its show bootloader unlocked warning... so that warnling doesn't affect the OTA is you have everything stock with locked bootloder.
Can anyone post a modified logo without the unlocked warning? My bootlock is relocked but i wanna get rid of this message. Thanks!
Just to clear up any confusion. There is no need to relock the bootloader. In fact it seems like a waste of time to me...
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/91999/p/1449,8620
After I unlock my device bootloader, am I still eligible to receive software upgrades from Motorola?
Unlocking your bootloader does not affect your eligibility to receive over-the-air (OTA) upgrades from Motorola. Upgrade packages to new versions of Android will be pushed to all eligible devices, regardless of their bootloader locking status.
Click to expand...
Click to collapse