Related
Hey guys, i have my rezound running cleanrom icse 3.1 and want to revert back to stock - no root ect. so much has changed since i did this last so im confused, How do i go back to stock, i did the factory reset but that just puts me back to no data on cleanrom icse 3.1.
Any help would be appreciated.
i have clockwork recovery installed
*unlocked*
s-on
hboot 2.10.000
thabnks
real stock
Do a Google search for:
RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe
Relock your phone with these fastboot commands:
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Then put your phone back into fastboot with power/volume down, then run this exe as Administrator.
You'l unroot it and turn it into 100% stock. If S-0ff, it wont change that.
michaelbsheldon said:
Do a Google search for:
RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe
Relock your phone with these fastboot commands:
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Then put your phone back into fastboot with power/volume down, then run this exe as Administrator.
You'l unroot it and turn it into 100% stock. If S-0ff, it wont change that.
Click to expand...
Click to collapse
Thanks, ill try this and get back to you.
Again thank you.
michaelbsheldon said:
Do a Google search for:
RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe
Relock your phone with these fastboot commands:
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Then put your phone back into fastboot with power/volume down, then run this exe as Administrator.
You'l unroot it and turn it into 100% stock. If S-0ff, it wont change that.
Click to expand...
Click to collapse
im getting an error:
C:\mini-adb_vigor>fastboot oem writesecureflag 3
... INFOvreg_set: request is duplicated id 14
INFO vigor_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
INFOwritesecureflag: Permission denied, value 1
OKAY [ 1.578s]
finished. total time: 1.578s
C:\mini-adb_vigor>
any ideads?
next
Android Police posted a zip file 3.14.605.12PH98IMG.zip.
Its the same info in that RUU.
Download it, rename to just PH98IMG.zip and place in root of sdcard.
Run that, and it'll do the factory restore you want, maybe without those
unrequested comments it made in fastboot.
michaelbsheldon said:
Android Police posted a zip file 3.14.605.12PH98IMG.zip.
Its the same info in that RUU.
Download it, rename to just PH98IMG.zip and place in root of sdcard.
Run that, and it'll do the factory restore you want, maybe without those
unrequested comments it made in fastboot.
Click to expand...
Click to collapse
Tried that, didnt work, hboot/cwm recovery said invalid,
I finally got s-off with the JuopunutBear / wire trick and now it seems to be working.
Thank you for the guidance.:good:
Firstly, the problem why the RUU wasn't working, was that your bootloader was unlocked (fastboot oem lock to relock the bootloader)
This usually gives an "Unknown Error 99" message.
The reason it worked after S-OFF is because JuopunutBear erases the unlock token.
Secondly, when you're trying to do something like this, it's better to search for a reliable source for instructions & not jump at any answers that you can find.
michaelbsheldon said:
Do a Google search for:
RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe
Relock your phone with these fastboot commands:
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Then put your phone back into fastboot with power/volume down, then run this exe as Administrator.
You'l unroot it and turn it into 100% stock. If S-0ff, it wont change that.
Click to expand...
Click to collapse
This answer is so so wrong. How can you provide advice on something that you have no idea about?
This instructions are for S-ON & if your device has JuopunutBear hboot, then this will brick the phone.
Would you ever be willing to try something like this on your own phone?
*
If you'd been bothered to read OP comments, he was S-0n, so JBear Hboot couldn't have been there.
Save your crabby comments.
michaelbsheldon said:
If you'd been bothered to read OP comments, he was S-0n, so JBear Hboot couldn't have been there.
Save your crabby comments.
Click to expand...
Click to collapse
Sure, in which case writesecureflag isn't required at all.
Although these wrong S ON bricks are unbrickable, never in any case tell anyone to do that command unless you fully understand the implications of what you are saying.
If you notice, he later did S-OFF with JuopunutBear:
wohn said:
I finally got s-off with the JuopunutBear / wire trick and now it seems to be working.
Click to expand...
Click to collapse
in which case, his phone would have bricked if he had JB hboot had tried your commands.
The android police RUU you linked to is not an Official RUU, it's made from an OTA. Which is why he was unable to flash it without S-OFF.
The instructions you gave were wrong & I simply called you out on that.
I honestly don't want to argue on this, I just want you to be careful of what you advice people to do.
Although this is a public forum & everyone's input is welcome & I'm nobody to enforce any rules; I'm simply giving you my opinion.
The rest is upto you. Good day.
FactoryROM Presents:
A lot of you are wondering how to get back to Bone Stock in case something happens during your Flashing
Addiction. You must run this RUU from a Windows based machine. You will also want to run this
executable with Windows Administrative Privileges (right click on RUU and Run as Administrator)
(1) Download this Package (Which is the HTC RUU in Executable Form) : Here
(2) If you have unlocked your HTC DNA, you must first lock the system again.
First boot into Bootloader
Code:
adb reboot bootloader
Once in Bootloader
Code:
fastboot oem lock
(3) Boot back into Bootloader
(4) Run the RUU with Administrative Privledges
(5) Follow the prompts, and Profit
While the Software Re-loads, your device will reset several times. Once everything is
said and done, your device will reboot into a freshly installed, bloated OS.
Let me know if you have any issues.
To Re-Unlock your Device:
(1) Flash RUU
(2) Turn Phone Completely Off
(3) Hold Volume Down Key and Power to Restart to Fastboot
(4) Reflash your Unlock Token (the original one sent from HTC during initial Unlock)
(5) Enter "Yes" at Unlock Warning - System will not Restart
(6) After Restart, Shut Phone Down Completely Again
(7) Reboot into Fastboot and Check your Lock Status - Should now say "Unlocked"
(8) Flash Unlocked Kernel & Recovery Again
(9) Profit
Thanks:
football (for the RUU leak)
Does this make the bootloader say "LOCKED" as opposed to "RELOCKED"?
Despyse said:
Does this make the bootloader say "LOCKED" as opposed to "RELOCKED"?
Click to expand...
Click to collapse
It will say relocked.
Unlock
Will you be able to re unlock?
thom2k said:
Will you be able to re unlock?
Click to expand...
Click to collapse
It's my understanding that once you unlocked your device, the CID is permanently cleared. So yes, you can re-unlock using the HTC tool.
Cannot re unlock
Well I installed the ruu and cannot re unlock I've even tried rerunning the unlock process as well still no go. Any ideas?
thom2k said:
Well I installed the ruu and cannot re unlock I've even tried rerunning the unlock process as well still no go. Any ideas?
Click to expand...
Click to collapse
Did you go back to the HTC site? You shouldn't have to just Justin's workaround again, simply go to the htcdev site and select "other devices" and do what you did before.
I'm in the process of re-locking mine right now, unfortunately the bootloader says:
**TAMPERED**
**RELOCKED**
**SECURITY WARNING**
I don't recall the security warning being there before..
EDIT: After flashing the RUU now it only says **RELOCKED**.
I flashed RUU last night, then had to start from square 1 to re-unlock. Since I had my BIN file from HTCDev, I thought I could just start with the "fastboot flash unlocktoken Unlock_code.bin" command, but it kept erroring out on me.
has anyone retried jcase's unlock method first before trying to re-unlock?
Cannot re unlock
nitsuj17 said:
has anyone retried jcase's unlock method first before trying to re-unlock?
Click to expand...
Click to collapse
I made several attempts with my original unlock bin after that failed I then retried jcase's unlock method to regenerate new bin but failed as well. Are you suggesting I should have retried jcase's unlock method first?
thom2k said:
I made several attempts with my original unlock bin after that failed I then retried jcase's unlock method to regenerate new bin but failed as well. Are you suggesting I should have retried jcase's unlock method first?
Click to expand...
Click to collapse
im not suggesting that you do it, was just curious if anyone had tried
WorldOfJohnboy said:
I flashed RUU last night, then had to start from square 1 to re-unlock. Since I had my BIN file from HTCDev, I thought I could just start with the "fastboot flash unlocktoken Unlock_code.bin" command, but it kept erroring out on me.
Click to expand...
Click to collapse
So you had success re unlocking? If so what do you mean by square 1? Square one on htcdev or jcase exploit
Sent from my HTC Droid DNA
thom2k said:
I made several attempts with my original unlock bin after that failed I then retried jcase's unlock method to regenerate new bin but failed as well. Are you suggesting I should have retried jcase's unlock method first?
Click to expand...
Click to collapse
Wow, I'm confused. Here's what I've done:
Ran JCase's unlock method, rooted
re-locked and flashed RUU
Tried using bin file from 1st unlock to re-unlock, FAILED
Ran JCase's exploit to re-unlock and rooted again
I forget what the error message was when I tried using the Bin file from the first (initial) unlock, but I know it didn't like it.
WorldOfJohnboy said:
Wow, I'm confused. Here's what I've done:
Ran JCase's unlock method, rooted
re-locked and flashed RUU
Tried using bin file from 1st unlock to re-unlock, FAILED
Ran JCase's exploit to re-unlock and rooted again
I forget what the error message was when I tried using the Bin file from the first (initial) unlock, but I know it didn't like it.
Click to expand...
Click to collapse
When i ran the exploit to re-unlock it didn't work for me. Are you saying it has worked for you?
WorldOfJohnboy said:
Wow, I'm confused. Here's what I've done:
Ran JCase's unlock method, rooted
re-locked and flashed RUU
Tried using bin file from 1st unlock to re-unlock, FAILED
Ran JCase's exploit to re-unlock and rooted again
I forget what the error message was when I tried using the Bin file from the first (initial) unlock, but I know it didn't like it.
Click to expand...
Click to collapse
WorldOfJohnboy. Thanks in advance for any light you can shed on this for me/us.......Were you successful in re-unlocking after RUU? I have been wanting to flash back to stock but am waiting to see if anyone has been successful in RE-unlocking. Thanks again if you can help me out :good:
Unlock
JCase is looking @ this here https://twitter.com/TeamAndIRC
Unable to find device in fastboot.
I am trying to return to stock, but here's my dilemma: I am unable to detect my device in fastboot after fastboot oem lock. I have tried uninstalling and reinstalling drivers. I have installed the HTC ones and the PDAnet ones.Fastboot even shows "fastboot usb" but it doesn't bring up the same drivers.
A windows popup says Failed to install device drivers.
With the phone relocked, it will not let me boot back into the Android OS. Trying to enter clockwork recovery just boots back into the bootloader. There is literally nothing I can do. Is it bricked?
Edit: AAAANNNNNDDDDDDD once again it randomly installed the drivers and restored. Not sure if I am going to attempt a re-root considering all the problems I have had with it.
delete
for those still having issues, you can re-unlock after flashing the RUU (havent seen anyone else comment recently, so many of you may know this already)
*need to use your original unlock token, there is no need to reuse jcase's unlock again
follow the 5 steps in the op to flash the RUU
boot to hboot after RUU finishes and reboots
navigate to your fastboot directory
fastboot flash unlocktoken Unlock_code.bin
unlock on your phone
***this will most likely *seem* to work, but fail on the 1st, 2nd, or even 3rd attempts***
after phone reboots boot back to hboot
if it still says "relocked", fastboot the unlock token again
unlock on phone
**repeat until successful
Why must you relock bootloader to flash this? You can't just flash it like a normal ROM?
Hey guys, I need to return my phone to verizon because of a simcard/PUK lock error. I'm on the current OTA update (2.06) but still unlocked, rooted and S-off. I need to go back to bone stock if possible. Can I still follow the guide in this thread to go back to stock??
http://forum.xda-developers.com/showthread.php?t=2017525
Anyone?
scheirere said:
Anyone?
Click to expand...
Click to collapse
You don't have to relock your phone all you have to do is flash the ENG Bootloader then you can run the RUU. Make sure you have all the drivers you need installed first or it WILL fail.
ENG Bootloader:
http://forum.xda-developers.com/showthread.php?t=2156713
Also this won't take away your S-Off the only way to get to S-On is by running a special command. Once S-Off always S-Off.
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
scheirere said:
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
Click to expand...
Click to collapse
Yes try here:
http://forum.xda-developers.com/showpost.php?p=37277937&postcount=66
Oh and don't forget to hit thanks on that post.
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
scheirere said:
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
Click to expand...
Click to collapse
This first:
1. adb reboot bootloader
2. fastboot oem rebootRUU
3. fastboot flash zip ModdedPL832IMG.zip
4. Profit
making sure that the .zip is in the same folder as fastboot
then run the RUU after you reboot the phone.
Yes it should be the same drivers you used when rooting.
Looks like I spoke too soon on those downloaded files. The download of the RUU file bombed out on me and I didn't realize it. When I go back to the site in the link, and try to download the file now, it just sits waiting. I guess the site is down? Any other links or locations?
Downloads working now maybe keep trying they say they are under a DDOS attack. Here it is from hotfile but I can't confirm this as real.
HERE
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
scheirere said:
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
Click to expand...
Click to collapse
After step 1, but before step 2, do this:
fastboot devices
If you don't get a device id, then you don't have the proper drivers installed.
If you get a device id, then try step 2 again ...
If that doesn't work, then I don't know
Maybe try a different USB port on your computer also use the OEM cable if you can.
Thanks guys for the suggestions. Unfortunately, still no luck. Same results when flashing the Modded file. I did try adb devices as suggested and got the device ID. So I think the drivers are OK. I also tried another USB port just to see if it helped. No go.
Just because I'm pretty new to this stuff, here's a detailed list of what I'm doing.....
1.) ADB reboot bootloader (from a command prompt)
Phone reboots to bootloader screen with Fastboot USB in red, hightlighted.
The screen no longer displays the "TAMPERED" heading at the top. So it looks like I'm making some progress.
2.) fastboot oem rebootRUU (from a command prompt again)
Phone screen goes from white to black with nothing but a large HTC logo in white.
Nothing else happens at this point. I've let the phone sit for 30 minutes with no apparent change and nothing on the host PC.
I then went thru my computer to the directory were the RUU_DLX.... file resides and executed (double clicked) it. I get an RUU - InstallShield screen and then I go thru the HTC rom update utility steps. After a few steps the utility does it's thing and the phone then reboots.
3.) ADB reboot bootloader again
Phone reboots into bootloader screen
4.) fastboot flash zip ModdedPL832IMG.zip (from a command prompt)
Phone does nothing but the command screen returns:
sending 'zip' (485 KB)...OKAY [ 0.266s]
writing 'zip'...FAILED (remote: not allowed)"
pretty much immediately
Am I doing this correctly?
At this point the bootloader screen no longer says tampered. Can I just relock the bootloader so it's s-on again?
BTW, here's what the bootloader screen shows:
*** UNLOCKED ***
MONARUDO PVT SHP S-OFF
CID-22222222
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
Or can I just send the phone back as it is?
Bootloader uses a different driver than ADB. My advise is to boot into the bootloader then verify in device manager that the driver is loaded. See attached. Flashing the RUU will not get you S-On you need a command to do that and I don't know what it is off the top of my head I have never used it.
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.
I have a black HTC One PN07120 and I bought it used. It came with stock android (kit kat). I am trying to unlock my phone so I can use it with t mobile but when I put my code in it give me an error saying "Network Unlock Request unsuccessful". I was looking around and read that custom roms aren't good with unlocking networks so I have to return to htc one stock sense and then put in the code.
When I boot into bootloader, it shows it is *** RELOCKED ***
I have tried using the RUU but that gives me an "unknown error". I also downloaded the "root checker" app and that says I don't have root access. I went to HTCdev.com and did the unlock bootloader thing. Got the file, when I run the "fastboot flash unlocktoken Unlock_code.bin" command, It says successful but doesn't unlock the bootloader.
How can I get my HTC One back to stock. I have tried a lot of things and nothing seems to work. Any help would be appreciated.
Are you s-off? If not, you may need s-off to flash the ruu that you downloaded.
Solution
Found a simple solution...
Go to google and search "htc one ruu zip" Go to the first link.
And download the RUU that corresponds with you phones original carrier.
(You need to have fastboot and adb and all the drivers setup)
Enable USB debugging.
Go to the home screen on your phone
Open up a command prompt and enter:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip theFileName.zip
after this it will zip and give you an error.You have to enter the previous command again.
fastboot flash zip theFileName.zip
After it says "finished." You are done. the last command is to reboot
fastboot reboot
Hope this helped for the people that are in the same situation.
Ah, you may have had the wrong RUU that didn't match your CID or MID, or a decrypted one, which would have only allowed you to run it if you had s-off.