I'm hoping someone can provide some guidance,
I rooted my Droid Incredible 4G LTE when it was at RUU 1.43.605.3. Then, I wanted to update to RUU 2.17.605.2. But, it wasn't working. I guess the SuperCID from Team fireballas was causing the problem. Anyway, I ended up finding the full RUU 2.17.605.2 ROM in this thread:
http://forum.xda-developers.com/showthread.php?t=1947600
So I flashed the ROM and my phone appeared to be updated to RUU 2.17.605.2. I then did the whole bootloader unlock, SuperCID, TWRP Recovery thing again. As a note, I did not revert back to VZW_001.
Today, my phone asked me to update again. I went into preferences and my phone seemingly had reverted back to 1.43.605.3. I'm not sure what happened. In any case, I can't apply the udpate. And when I try to run Team fireballas it does not seem to reset to VZW_001. I checked and I still have root.
Here's what the script says:
Root access verified, continuing...
========================
= Step 2: Revert CID =
========================
Your phone's CID is being reverted to its original state. Once complete, your phone will reboot to the bootloader.
/sdcard/mmcblk0p4: cannot open for write: Read-only file system remote object '/sdcard/mmcblk0p4' does not exist
cannot stat 'mmcblk0p4': No such file or directory
/sdcard/mmcblk0p4MOD: cannot open for read: No such file or directory
rm failed for /sdcard/mmcblk0p4MOD, Permission denied
Could Not Find C:\Users\lev44063\Desktop\Inc4GUnlockV41\mmcblk0p4
< waiting for device >
...
(bootloader) cid: 11111111
So....Any ideas? I can go through the whole thing again but I don't want the RUU to be reset back to the original.
blevin said:
I'm hoping someone can provide some guidance,
I rooted my Droid Incredible 4G LTE when it was at RUU 1.43.605.3. Then, I wanted to update to RUU 2.17.605.2. But, it wasn't working. I guess the SuperCID from Team fireballas was causing the problem. Anyway, I ended up finding the full RUU 2.17.605.2 ROM in this thread:
http://forum.xda-developers.com/showthread.php?t=1947600
So I flashed the ROM and my phone appeared to be updated to RUU 2.17.605.2. I then did the whole bootloader unlock, SuperCID, TWRP Recovery thing again. As a note, I did not revert back to VZW_001.
Today, my phone asked me to update again. I went into preferences and my phone seemingly had reverted back to 1.43.605.3. I'm not sure what happened. In any case, I can't apply the udpate. And when I try to run Team fireballas it does not seem to reset to VZW_001. I checked and I still have root.
Here's what the script says:
Root access verified, continuing...
========================
= Step 2: Revert CID =
========================
Your phone's CID is being reverted to its original state. Once complete, your phone will reboot to the bootloader.
/sdcard/mmcblk0p4: cannot open for write: Read-only file system remote object '/sdcard/mmcblk0p4' does not exist
cannot stat 'mmcblk0p4': No such file or directory
/sdcard/mmcblk0p4MOD: cannot open for read: No such file or directory
rm failed for /sdcard/mmcblk0p4MOD, Permission denied
Could Not Find C:\Users\lev44063\Desktop\Inc4GUnlockV41\mmcblk0p4
< waiting for device >
...
(bootloader) cid: 11111111
So....Any ideas? I can go through the whole thing again but I don't want the RUU to be reset back to the original.
Click to expand...
Click to collapse
you may get more help posting in the thread of the superCID, but hopefully someone can help you out.
blevin said:
I'm hoping someone can provide some guidance,
I rooted my Droid Incredible 4G LTE when it was at RUU 1.43.605.3. Then, I wanted to update to RUU 2.17.605.2. But, it wasn't working. I guess the SuperCID from Team fireballas was causing the problem. Anyway, I ended up finding the full RUU 2.17.605.2 ROM in this thread:
http://forum.xda-developers.com/showthread.php?t=1947600
So I flashed the ROM and my phone appeared to be updated to RUU 2.17.605.2. I then did the whole bootloader unlock, SuperCID, TWRP Recovery thing again. As a note, I did not revert back to VZW_001.
Today, my phone asked me to update again. I went into preferences and my phone seemingly had reverted back to 1.43.605.3. I'm not sure what happened. In any case, I can't apply the udpate. And when I try to run Team fireballas it does not seem to reset to VZW_001. I checked and I still have root.
Here's what the script says:
Root access verified, continuing...
========================
= Step 2: Revert CID =
========================
Your phone's CID is being reverted to its original state. Once complete, your phone will reboot to the bootloader.
/sdcard/mmcblk0p4: cannot open for write: Read-only file system remote object '/sdcard/mmcblk0p4' does not exist
cannot stat 'mmcblk0p4': No such file or directory
/sdcard/mmcblk0p4MOD: cannot open for read: No such file or directory
rm failed for /sdcard/mmcblk0p4MOD, Permission denied
Could Not Find C:\Users\lev44063\Desktop\Inc4GUnlockV41\mmcblk0p4
< waiting for device >
...
(bootloader) cid: 11111111
So....Any ideas? I can go through the whole thing again but I don't want the RUU to be reset back to the original.
Click to expand...
Click to collapse
andybones said:
you may get more help posting in the thread of the superCID, but hopefully someone can help you out.
Click to expand...
Click to collapse
+1 I would try posting your issue here http://forum.xda-developers.com/showthread.php?t=1986346
Not Quite Enough Postings Yet
AMSPOWER said:
+1 I would try posting your issue here http://forum.xda-developers.com/showthread.php?t=1986346
Click to expand...
Click to collapse
Well, I would except I don't have 10 total postings yet and you can;t post in the development section without 10. But, I guess I will get there soon enough!.
blevin said:
Well, I would except I don't have 10 total postings yet and you can;t post in the development section without 10. But, I guess I will get there soon enough!.
Click to expand...
Click to collapse
ahh yes, I happen to be hindered by that XDA rule but I'll be free soon as well lol Good luck!
blevin said:
I'm hoping someone can provide some guidance,
I rooted my Droid Incredible 4G LTE when it was at RUU 1.43.605.3...
Click to expand...
Click to collapse
If you unlocked your phone way back then, your unlock token that your received by e-mail from HTC should still work. You didn't need to go through the unlock script. From that unlock package, you really only need: fastboot.exe, AdbWinApi.dll, and adb.exe. Put Unlock_code.bin in the same directory as those files, reboot your phone to fastboot, then run
Code:
fastboot flash unlocktoken Unlock_code.bin
from a command prompt.
EDIT: I read a bit more of your post and see that first and foremost, you need to get your cid back to normal. Check that your internal /sdcard is not full before running procedure 3 from the script (also make sure you're using the latest version of the script).
As far as reverting your CID, I had the same problem, but I did a full reboot of everything and started over again, and it worked the second time. I don't know if that will help, but it can't hurt.
Related
I CAN'T RELOCK THE BOOTLOADER!!!
This only reverts your SPL/HBOOT back to 0.33.0012 after you've installed the Korean FRF91 files and ended up stuck with 0.35.0017 SPL.
Thanks to the guys in the Desire forums and help from the Nexus Q&A, I have reverted my phone to the original HBOOT so I can apply custom roms again.
First you need to root the Korean FRF91 that's on your phone using Paul's instructions for superboot FRF83.
If you are rooted already, skip this step.
http://android.modaco.com/content/g...-erd79-frf83-superboot-rooting-the-nexus-one/
You need to download the EPF30 update, save it to your SD card as PASSIMG.zip.
http://shipped-roms.com/shipped/Passion%20(Nexus%20One)/PASSIMG_Passion_Google_WWE_1.14.1700.1_EPF30_release_signed.zip
Create a new mtd0.img file through this site
http://ks33673.kimsufi.com/misc/
I used the values, CID: 11111111 and Rom version: 0.22.997.0
Save the mtd0.img file to you PC.
Download the flash_image binary (right click, save as)
http://benocharm.lensworks.org/flash_image
Make sure it's saved as flash_image, and not flash_image.txt
If it has a Notepad icon, then it's not saved right.
With mtd0.img and flash_image in the same folder, type these commands from within that directory:
Code:
adb push flash_image /data/flash_image
adb push mtd0.img /data/mtd0.img
adb shell
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
NOTE: After flashing the MISC partition with the MTD0 from the Desire, you will notice that you have an HTC logo on your phone.
No worries, this goes away after reflashing the EPF30 Nexus One PASSIMG.zip package.
Power off your phone, then turn it on by holding VolDown and pressing Power.
It will start up in HBOOT mode and will prompt you to flash the EPF30 PASSIMG.zip update.
Once this is finished you can root the EPF30 system through Paul's superboot instructions above, then use Rom Manager from the market to apply a custom recovery again.
Now, remember not to flash the new HBOOT again.
I'd recommend flashing the 5.08 radio for the N1 through other means. Search the forum to find the instructions.
Reserved.
Thanks a lot cursordroid.
Finally I managed to downgrade my hboot.
I could save several steps as my phone is unlocked.
So I just needed to:
- make a nandroid backup
- Go through the steps of flashing mtd0.img
- Apply PASSIMG.zip file
- Through fastboot re-install a custome recovery image
- Nandroid restore
Thanks!
rommelin said:
Thanks a lot cursordroid.
Finally I managed to downgrade my hboot.
I could save several steps as my phone is unlocked.
So I just needed to:
- make a nandroid backup
- Go through the steps of flashing mtd0.img
- Apply PASSIMG.zip file
- Through fastboot re-install a custome recovery image
- Nandroid restore
Thanks!
Click to expand...
Click to collapse
That sounds like it should work, except I'm not sure fastboot accepts unsigned recovery images, you might still need to use Rom Manager to flash one.
YMMV
WTF! This can relock the bootloader?
Where is the link to the latest HBOOT?????????????
cursordroid said:
That sounds like it should work, except I'm not sure fastboot accepts unsigned recovery images, you might still need to use Rom Manager to flash one.
YMMV
Click to expand...
Click to collapse
Just did it
You can definitely flash the recovery directly from bootloader when the phone is unlocked.
I forgot to mention one extra step I took.
Delete through adb the PASSIMG.zip file from the sdcard before trying to enter in bootloader and flash the recovery.
For that, I just needed to boot the stock firmware, enable usb debugging mode and:
#adb shell rm /sdcard/PASSIMG.zip
So if I upgrade I loose root? then i root and reflash stock PASSIMG.zip with original HBOOT after flashing Desire hboot I can get stock bootloader meaning? Security gets disabled when using HTC HBoot? so i can relock my bootloader then update using PASSIMG??????????????
I dont think youve realized how happy you made everyone on this forum is you figured out you can relock the bootloader lol!
I CAN'T RELOCK THE BOOTLOADER!!!
This only reverts your SPL/HBOOT back to 0.33.0012 after you've installed the Korean FRF91 files and ended up stuck with 0.35.0017 SPL.
cursordroid said:
This only reverts your SPL/HBOOT back to 0.33.0012
Click to expand...
Click to collapse
And that's already a lot
Not being able to install or upgrade to any signed build (like recent CM 6.0) including official ones... is not funny. It's really annoying.
Going back to normal is lik
e having a new phone again
Then, what does 0.35.0017 do, if not locking the Nexus?
i'm getting an error saying incorrect cid. i actually have korean nexus one. i've been following all the steps but stuck when i try to flash the rom with passimg. big error msg saying incorrect cid. what to do now?
I can also confirm that this method worked with me. Initially screwed by the Korean ROM, but now back to the old bootloader. Thanks!!
i have tried all the method there and followed all the stuff, but it just won't let me flash passimg.zip. i keep getting cid incorrect. any solution people?
evank418 said:
i have tried all the method there and followed all the stuff, but it just won't let me flash passimg.zip. i keep getting cid incorrect. any solution people?
Click to expand...
Click to collapse
Are you using CID value: 11111111?
Yes and it didn't work. Also tried Googl001 but didn't work either. I actually do have Korean nexus one maybe that's why???? Any solution?
Sent from my HTC Legend using XDA App
@cursordroid help me
i'm a newbie, i don't know much about these, but i have installed Korean FRF91
After seeing u'r post i was happy that i could revert back now, but i don't know how to do
i have followed u'r post but i'm stuck in the middle.................
i have created that two files and downloaded EPF30 update.............
where to enter these commands
adb push flash_image /data/flash_image
adb push mtd0.img /data/mtd0.img
adb shell
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
i have windows 7..............
please help me
my emailid [email protected]
thank you
No need for the help!
I'm back to erd79
evank418 said:
Yes and it didn't work. Also tried Googl001 but didn't work either. I actually do have Korean nexus one maybe that's why???? Any solution?
Sent from my HTC Legend using XDA App
Click to expand...
Click to collapse
Well, if you have a korean one, i'm not sure if there is anything different in that version.
Can you write down all the details from the bootloader screen?
What's the problem with the newer bootloader? Why even downgrade?
rommelin said:
Well, if you have a korean one, i'm not sure if there is anything different in that version.
Can you write down all the details from the bootloader screen?
Click to expand...
Click to collapse
nexusone pvt ship s-on
hboot-0.35.0017
microp-0b15
touch panel-synt0103
radio-5.00.00.04
june 14 2010,12:02:27
If there's further discussion of this elsewhere that I've missed, please point me to it.
I'm trying to root my INC4G, but neither the manual nor scripted Fireballas method is successful.
-I have re-flashed the stock RUU, I am using a USB 2.0 port. All the basic ADB commands are fuctional in and out of fastboot, etc.
When I run the manual version, all is well up through restoring the fakebackup.ab file. When I enter the "while" command (without accepting restore yet on phone) I get the endlessly repeating error message mentioned by Aldo101t on the fireballas thread (post #54 and others). Accepting the restore on the phone handset does NOT stop the endless error loop in the Command line, and a prompt never becomes available again. I'm working on a Vista machine and I've tried the process through both the default 64-bit Command.exe and what I believe is the 32-bit version CMD.exe in the C:\Windows\SysWow64\ directory.
When I run the script version, all is well until I get the following:
----------------------------------------------------------------------------------------------------------------------
= Step 2: SuperCID =
========================
Your phone's CID is being modified to SuperCID. Once complete, your
phone will reboot to the bootloader.
/dev/block/mmcblk0p4: cannot open for read: Permission denied
remote object '/sdcard/mmcblk0p4' does not exist
The system cannot find the file specified.
cannot stat 'mmcblk0p4': No such file or directory
/sdcard/mmcblk0p4MOD: cannot open for read: Permission denied
rm failed for /data/local.prop, No such file or directory
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.012s]
finished. total time: 0.013s
Just above, you should see (bootloader) cid: 11111111
1) Yes, my cid is 11111111. Keep going.
2) No, my cid is VZW__001. Factory reset and try again.
3) No, my cid is VZW__001. Exit the script.
Select an option:
----------------------------------------------------------------------------------------------------------------------
Hitting option 2 to factory reset and repeat brings the same result each time.
Is there a specific permissions problem that I could resolve manually with a file manager? Or do I need to manually create a dummy file that can then be overwritten?
Any suggestions very welcome. I'd have posted this to the Fireballas forum, but I don't have posting privileges.
Thanks!
D
drenkin said:
If there's further discussion of this elsewhere that I've missed, please point me to it.
I'm trying to root my INC4G, but neither the manual nor scripted Fireballas method is successful.
-I have re-flashed the stock RUU, I am using a USB 2.0 port. All the basic ADB commands are fuctional in and out of fastboot, etc.
When I run the manual version, all is well up through restoring the fakebackup.ab file. When I enter the "while" command (without accepting restore yet on phone) I get the endlessly repeating error message mentioned by Aldo101t on the fireballas thread (post #54 and others). Accepting the restore on the phone handset does NOT stop the endless error loop in the Command line, and a prompt never becomes available again. I'm working on a Vista machine and I've tried the process through both the default 64-bit Command.exe and what I believe is the 32-bit version CMD.exe in the C:\Windows\SysWow64\ directory.
When I run the script version, all is well until I get the following:
----------------------------------------------------------------------------------------------------------------------
= Step 2: SuperCID =
========================
Your phone's CID is being modified to SuperCID. Once complete, your
phone will reboot to the bootloader.
/dev/block/mmcblk0p4: cannot open for read: Permission denied
remote object '/sdcard/mmcblk0p4' does not exist
The system cannot find the file specified.
cannot stat 'mmcblk0p4': No such file or directory
/sdcard/mmcblk0p4MOD: cannot open for read: Permission denied
rm failed for /data/local.prop, No such file or directory
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.012s]
finished. total time: 0.013s
Just above, you should see (bootloader) cid: 11111111
1) Yes, my cid is 11111111. Keep going.
2) No, my cid is VZW__001. Factory reset and try again.
3) No, my cid is VZW__001. Exit the script.
Select an option:
----------------------------------------------------------------------------------------------------------------------
Hitting option 2 to factory reset and repeat brings the same result each time.
Is there a specific permissions problem that I could resolve manually with a file manager? Or do I need to manually create a dummy file that can then be overwritten?
Any suggestions very welcome. I'd have posted this to the Fireballas forum, but I don't have posting privileges.
Thanks!
D
Click to expand...
Click to collapse
why not go to unlimited.io and s-off it. DONE
Aldo101t said:
why not go to unlimited.io and s-off it. DONE
Click to expand...
Click to collapse
I'd love to. But their step 12, "get temproot somehow-" appears to be the same part of the Fireballas process that won't work for me. If there's some other way to manage temproot--or if the Fireballas script is actually succeeding at temproot if only I knew to rip the cables out of the phone at the correct instant before the script crashes--please let me know what to try. I've never seen the shell prompt change from $ to #.
Did the unlimited.io process work for you, despite the same endless-error symptom through Fireballas? If so, can I ask how you achieved temproot?
Thanks for responding, above! : )
?
Sent from my ADR6410LVW using xda app-developers app
drenkin said:
I'd love to. But their step 12, "get temproot somehow-" appears to be the same part of the Fireballas process that won't work for me. If there's some other way to manage temproot--or if the Fireballas script is actually succeeding at temproot if only I knew to rip the cables out of the phone at the correct instant before the script crashes--please let me know what to try. I've never seen the shell prompt change from $ to #.
Did the unlimited.io process work for you, despite the same endless-error symptom through Fireballas? If so, can I ask how you achieved temproot?
Thanks for responding, above! : )
Click to expand...
Click to collapse
I USED THE AUTOMATED script in a different cmd window, you need to factory reset first then run it til the scrolling starts then accept restore, if it works properly the scroll stops. then adb reboot. when the phone has a screen with the droid eye on it and no icons(your done with this cmd window). it is in tempt root, then go back to the first cmd window you ruued on and finish the process. make sure usb debugging is on, after the ruu, you have to boot the rom (stock)to turn it on.
are you on a 32bit windows 7 and the enviornmental variables set. and the sdcard will get wiped s-offing so use a spare 8bg to 16gb no larger,and has to have an sdcard installed inthe phone to work. you can also go to unlimited.io for support and help. except the temp root deal they won't support that
Do you have a different machine you could use with a different OS? If so you may want to try that. 64 bit Windows 7 worked for me as far as temp root.
Good Luck
Interesting!
Aldo101t, thanks for mentioning using separate Command prompt windows, it led me to back up even further from a single instruction set and try the original root script by Bin4ry: it got me to a # prompt, and proper temproot...from which I could continue with the manual version of the Fireballas instructions and change out my VZW_001 id...and get the unlock code from HTCDev.
Currently have TWRP recovery installed, and about to flash ViperLTE Rom.
Thanks to Aldo101t and DavDoc for nudges and moral support. : )
drenkin said:
Interesting!
Aldo101t, thanks for mentioning using separate Command prompt windows, it led me to back up even further from a single instruction set and try the original root script by Bin4ry: it got me to a # prompt, and proper temproot...from which I could continue with the manual version of the Fireballas instructions and change out my VZW_001 id...and get the unlock code from HTCDev.
Currently have TWRP recovery installed, and about to flash ViperLTE Rom.
Thanks to Aldo101t and DavDoc for nudges and moral support. : )
Click to expand...
Click to collapse
your welcome, glad you got root.
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.
Hello Everyone,
I know this probably isn't the best place to post this question. I'm limited to not posting in the dev section.
I'm going to post my question and hope someone can help anyway.
I have an HTC One (M7) that seemed to have reception problems. I always thought I just needed to flash a new radio. So I went ahead and S-OFF'd my phone as well as Super CID. I then flashed a new radio & my reception problem seemed to go away. (or so i thought).
I then went ahead and turned my AT&T One into a Google Edition.
I have noticed that my reception problems never really went away. (When I am at home I have full bars. The conversation starts out fine, but about 10 seconds in, the person at the other end can no longer hear me.)
I now suspect this is a problem with the antenna & I have to get my phone back to stock so that I can hopefully switch out for a new one.
I'm just wondering which step I should do first. S-On again (I used REVONE to S-OFF) , CID back to AT&T, or switch back from the GE rom?
Any help would be appreciated.
Thank you,
Dan
demayod said:
Hello Everyone,
I know this probably isn't the best place to post this question. I'm limited to not posting in the dev section.
I'm going to post my question and hope someone can help anyway.
I have an HTC One (M7) that seemed to have reception problems. I always thought I just needed to flash a new radio. So I went ahead and S-OFF'd my phone as well as Super CID. I then flashed a new radio & my reception problem seemed to go away. (or so i thought).
I then went ahead and turned my AT&T One into a Google Edition.
I have noticed that my reception problems never really went away. (When I am at home I have full bars. The conversation starts out fine, but about 10 seconds in, the person at the other end can no longer hear me.)
I now suspect this is a problem with the antenna & I have to get my phone back to stock so that I can hopefully switch out for a new one.
I'm just wondering which step I should do first. S-On again (I used REVONE to S-OFF) , CID back to AT&T, or switch back from the GE rom?
Any help would be appreciated.
Thank you,
Dan
Click to expand...
Click to collapse
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Thanks so much for the response! I appreciate the help. Very informative. I'll read through & hopefully I report back with good news tomorrow morning. :cyclops:
Yay! All done!
Thanks so much for the guide! and the help!
-Dan
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I guess I spoke too soon. After completion, I realized that TWRP was still installed, so I flashed the stock recovery. At this point everything seemed fine, but I noticed that the supersu icon was still there. I also noticed that wifi will no longer turn on. Clearly I've done something wrong.
The first time I had used a nandroid backup to restore to stock, then lock, s-on, remove tampered. That is when I realized TWRP was still installed and SuperSu was still there.
This is when I downloaded an RUU that matched my phone, but it errors saying something like "wrong boot version" (I'm not near my home pc to look)
I tried the process again & somehow SuperSu lost binaries. So I unlocked my bootloader again through HTCDev.com This gave me working SuperSu again. And this is where I am stuck.
I wonder if the GE rom changed something so that this process wont work?
demayod said:
I guess I spoke too soon. After completion, I realized that TWRP was still installed, so I flashed the stock recovery. At this point everything seemed fine, but I noticed that the supersu icon was still there. I also noticed that wifi will no longer turn on. Clearly I've done something wrong.
The first time I had used a nandroid backup to restore to stock, then lock, s-on, remove tampered. That is when I realized TWRP was still installed and SuperSu was still there.
This is when I downloaded an RUU that matched my phone, but it errors saying something like "wrong boot version" (I'm not near my home pc to look)
I tried the process again & somehow SuperSu lost binaries. So I unlocked my bootloader again through HTCDev.com This gave me working SuperSu again. And this is where I am stuck.
I wonder if the GE rom changed something so that this process wont work?
Click to expand...
Click to collapse
when you run the RUU did you use the exe or Rom.zip /?
I use the rom.zip and flash in fastboot...
clsA said:
when you run the RUU did you use the exe or Rom.zip /?
I use the rom.zip and flash in fastboot...
Click to expand...
Click to collapse
I used the ruu. I didn't realize you can access a Rom.zip. how can I try that? Thanks!
demayod said:
I used the ruu. I didn't realize you can access a Rom.zip. how can I try that? Thanks!
Click to expand...
Click to collapse
This is the instructions posted by Scotty85
I'm just re-posting it for you
http://androidforums.com/t-one-all-things-root/723061-t-ruu-1-26-502-12-a.html#post5864243
Click to expand...
Click to collapse
here is how you extract rom.zip:
Quote:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,youre done with it.
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
here are some directions to flash "rom.zip"
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.
Click to expand...
Click to collapse
clsA said:
This is the instructions posted by Scotty85
I'm just re-posting it for you
Click to expand...
Click to collapse
Thank you for the help, but still no good. I end up with FAILED (remote: 43 main version check fail) after I try to flash the zip.
demayod said:
Thank you for the help, but still no good. I end up with FAILED (remote: 43 main version check fail) after I try to flash the zip.
Click to expand...
Click to collapse
change your CID back to 11111111 and try again
Did you change you MID ?
What is the name of the RUU your using ?
My mid is PN0712000. I think that was always my mid. Don't recall changing it.
My cid is currently CW__001
I've tried: RUU_M7_UL_JB_50_Cingular_1.26.502.12.exe
also tried: RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2.exe
I'm currently S-On (could that be an issue?)
I'm unlocked.
clsA said:
change your CID back to 11111111 and try again
Did you change you MID ?
What is the name of the RUU your using ?
Click to expand...
Click to collapse
It worked once I set CID to 11111111 !!
So now I just have to change CID back, reverse S-Off again and change the unlocked and tampered flags?
Yep that should do it
Sent from my HTC One using Tapatalk 4
It did! I'm completely back to stock. I decided to update to the latest RUU that AT&T has released. Just to avoid AT&T wanting me to update to see if it fixes the problem. I know for a fact that it wouldn't fix the problem anyway.
Oddly, my phone told me I was up to date while on the .12 RUU even though I knew the .15 RUU exists. I downloaded the RUU for .15 and it ran fine once I went back to stock after running the .12 rom.zip.
In summary, you saved me from a huge headache! Thanks so much for all the help & kindness.
demayod said:
It worked once I set CID to 11111111 !!
So now I just have to change CID back, reverse S-Off again and change the unlocked and tampered flags?
Click to expand...
Click to collapse
How did you change our CID if you were S-On?
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Hi guys this might be the wrong platform for this question ...but can anyone pls help me with the stock cidnum for sprint htc one M8..thanks
larrydadz said:
Hi guys this might be the wrong platform for this question ...but can anyone pls help me with the stock cidnum for sprint htc one M8..thanks
Click to expand...
Click to collapse
Comments: Sprint
modelid:
cid: SPCS_001
Hey, I am trying to root my HTC evo 3d phone with hboot 1.58. I followed all 12 steps on htcdev.com, except on the final step I punch in: fastboot flash unlocktoken Unlock_code.bin and enter, then noting happens. The phone is supposed to reboot with the unlock option..but nothing happens
Also, the phone is Sprint CDMA if that makes any difference, so no sim card
....................................................................................................................................................................
THREAD SUMMARY
K finally got th phone rooted so here is what you have to do. The following applied to my ***locked*** S-ON Sprint HTC Evo3d with hboot 1.58 but should work with any other version higher than hboot 1.40.
The purpose is to get S-OFF(ROOT the phone) and also continue to use your factory HbOOT 1.58 and main version in the end.
1. Brick the phone carefully following steps outlined in unknownforce's [TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset). Scroll down to the "Downgrade/Unbrick" section and begin the bricking process with the PG86IMG.zip he mentions in "things you'll need".(place the zip on SD card in the main directory and name it PG86IMG)
2. Once phone is bricked(indicated by SOLID and very dimly lit charge light with the AC charger connected. Also the phone will not turn on or boot), download latest version of URT 3.1(first link in [TOOL] thread), continue to the second step 2 which involves booting up with Linux live boot CD on your PC, OR you can use URTLiveCD 1.0 and you will not need Linux
I did it the hard way an used latest version of URT with Ubuntu v12.04 LiveCD. I would recommend URTLiveCD 1.0 as you will boot straight to the tool and will not need the Ubuntu terminal.
3. After successfully completing downgrade with URT 3.1 downgrade, boot up to your new HBOOT 1.40 bootloader screen and enter fastboot USB mode. CHECK THAT THE MAIN VERSION HAS BEEN LOWERED ALONG WITH THE HBOOT.
Log back into windows
3.(A) If you haven't done this yet, get a fastboot PC command directory to retrieve all phone identification info from the bootloader. I used ROOTEVO3DNEW to check my phone's identity info at this point(though there are many programs that do the same thing). Create a new folder in C:\ and name it rootevo3dnew. Unzip all rootevo3dnew.zip contents into that folder.
Now open the command prompt with the phone connected to PC in fastboot USB. Type cd \rootevo3dnew and enter. Now type the following: "fastboot getvar all" (without quotations) and enter. A list should appear. Check that you have: (bootloader) version-main: 0.01.651.1. If this number is still 2.95.XXX.XXX or something close to it, then YOU MUST BRICK THE PHONE AGAIN. See posts starting at #35 of this thread for a more detailed guide through the second brick. It may be very tricky but very much the same process!!!!!
4. After successfully lowering HBoot to 1.40 and the main-version to 0.01.651.1 you can run the 1.13 RUU.exe found HERE: http://d-h.st/h1p . Connect the phone to fastboot USB and RUN the .exe....after the 1.13 .exe successfully runs, your main version should now be 1.13.651.7...again, checking using your rootevo3dnew tool from 3.(A) above....
5. REVOLUTIONARY S-OFF. Very simple, download for windows(or Linux) and fill in your info and retrieve you BETA key. Run REVOLUTIONARY application (which will run in the command prompt) and after successfully completely revolutionary S-off, YOU ARE ROOTED...continue to step 6
6. RESTORE your main version to 2.95(from 1.13) by running the 2.89 zip (HERE . Place this .zip in your main directory(RENAME IT PG86IMG) on the SD card and let it unzip and install it from the bootloader.
After that, you are pretty much finished!! boot up to android(main version 2.89) and let system updates detect and bring you back to 2.95.xxx.xxx..
....
Download and Install a custom recovery. Rename that .zip PG86IMG and install from bootloader as you did with the 2.89 zip. Now you have a custom recovery where you can backup and restore, install ROMS or other software without having to rename it PG86IMG every time, wipe partitions and lots of other stuff...
Now, download this and place it on your SD main directory. Then, using your new recovery(by selecting "recovery" in bootloader menu), select "install from sdcard" and "choose zip from sdcard", select the SuperSU zip and let it install. Reboot, get to homepage, and install SuperSU from the play store. You now hae an administrative super APP that will let you choose which apps are given root access.
Custom ROMS can be installed the same way from the custom recovery. I am currently using Negalite BluRom and loving it
...
THE 6 STEPS OUTLINED HERE PRETTY MUCH COVER EVERYTHING FROM THIS THREAD
HUGE THANKS TO USERS MPGRIMM2 AND BRIAN706 FOR NEARLY 3 DAYS OF HARD WORK !!
Did you get your motherboard replaced at some point of time?
Can't think of a good sig
donkeykong1 said:
Did you get your motherboard replaced at some point of time?
Can't think of a good sig
Click to expand...
Click to collapse
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?
otto325 said:
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?
Click to expand...
Click to collapse
On the phone?
Can't think of a good sig
donkeykong1 said:
On the phone?
Can't think of a good sig
Click to expand...
Click to collapse
Oh ok, what the hell..No, I just got the phone on ebay for $30, currently locked and I am trying to root it. Some Brittney girl owned according to phone identity info left on the phone
Do I need to downgrade the hboot from 1.58 to 1.4? Sorry I'm really new to smartphones, any help is really appreciated
Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.
Brian706 said:
Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.
Click to expand...
Click to collapse
THANKS
main version 2.95.651.5. If I factory reset the phone and discard updates, will the main version reset to 2.89 making the RUU possible?
EDIT: factory reset and no updates did not bring main version down to 2.89
***LOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
Also check most recent post (#508) in the guide thread.
http://forum.xda-developers.com/showthread.php?t=1889438&page=51
Factory reset won't affect your main version
As DK mentioned, a factory reset only resets your current build. It would only take you back to the point of the last OTA update.
Unfortunately, you can't lower the mainversion without the bootloader unlocked, so it's a catch 22 there.
As a long shot, you might look into the new towelroot, thought I really don't think it will work for this phone because HTC locks down the /system partition. It would at least be worth looking in to.
As far as the hboot downgrade method (I assume you mean THIS) it was intended to downgrade from 1.50 Gingerbread to 1.40 Gingerbread. I have no idea if it will work to downgrade from 1.58 ICS?? You might want to ask around a little about that.
Okay... I just saw your posts in the other thread, have you actually received the unlock token from HTC?
IE, you received a file via email named Unlock_Code.bin that you placed in your fastboot directory and then typed the command: fastboot flash unlocktoken Unlock_code.bin ??
Also, when you say nothing happens after running the command, something must happen whether it's the intended results or not. Can you tell us what the command prompt returns after running the command? Maybe just copy/paste it here.
There will either be an error or a confirmation after running the command.
Comes up as successful on the command prompt. But the phone does not reboot or direct to the unlock screen. I just remains on the fastboot USB screen and does nothing.
C:\rootevo3dnew>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.153s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.163s
Thanks for that... That's a bummer. Looks to me like you have the motherboard swap issue. It really sucks that you can't RUU.
It looks like someone answered the question in the other thread though about the hboot downgrade method.
So I got the HBOOT downgrade(0.8.2) boot for a disk but it says the phone needs to be bricked before the downgrade..
That's where I'm at now basically, I'm going to do a little more reading on bricking...
Also would be good to have confirmed that this downgrade will work starting with hboot 1.58, so I don't mess anything up
mpgrimm2 may have found found his way over here from from the [Guide] thread
Also I hope I am downloading the correct RUU's. I had to fish them from various searches because the link supplied in Unknownforce's thread is invalid:
2.17 RUU:
http://d-h.st/ru0ow8ps0i01/PG86IMG_2.17.651.5.zip
1.13 RUU:
http://d-h.st/Xrp
mpgrimm2 said:
Well. Post that in Unknownforce's Ultimate Recovery Tool thread so you are not "off topic" here.
I haven't used the Evo3d in a while but you should probably look over my ...
Post 781 in Unknownforce's thread and the follow up posts right after.
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself)
Click to expand...
Click to collapse
Fyi, I think Unknownforce indicated in one of his first 3 posts that u can brick with the last 2.95 PG86IMG.zip file he linked and then downgrade to 1.13 for s-off. Have to go check...
Keep in mind that you may want to considering posting any issues with the URT/Downgrade tool in Unknownforce's thread if you want any chance of assistance from him.
Bad link in his op but this post has it...
Unknownforce said:
Well, with the 2.95 OTA, they included the HBOOT in the firmware, so it's now much faster of a load time for PG86IMG when doing the brick.
I pulled the new PG86IMG.zip from the OTA update, and it's only 19MB, which takes only 15-20 seconds to fully load and be ready to press volume up to update... this will significantly cut down on the time it takes to downgrade, as you can re-try over and over very quickly now.
Here's the PG86IMG file -> http://d-h.st/3p8
Click to expand...
Click to collapse
And just as a reference for you later I will quote myself from Ramjet73's 2.95 ota update thread
mpgrimm2 said:
ramjet73 and others. I see we still don't have any source for the 2.95.651.6 RUU's. Since I just went ahead and reset my 2 Evo3d's back to stock/S-off as a backup here are the files I had to step through if you want to add or host them directly:
- PG86IMG 2.89.651.2.zip - 449.18 MB
Full RUU.zip for use in bootloader (rename to PG86IMG.zip & place on /sdcard)
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.5-2.89.651.2_release_307948lagg6bmccb9c63ip.zip - 51.11 MB
2.89.651.2 update to 2.95.651.5 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
This is the last official update that just downloaded to my phone after the other Ruu's/updates that were posted previously
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z.zip - 10.59 MB
2.95.651.5 update to 2.95.651.6 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
Wish someone with HTC/Sprint access would post up the latest full RUU. It was a bit of a pain stepping through the updates, but definitely easier being s-Off. Seems that if someone is S-On with the 2.95.651.6 update and can't get past step 13 of the HTC Unlock or needs to RUU back, their only option is Unknownforce's Hboot Downgrade Ultimate Toolkit and "Brick it Twice" to get back to an earlier version for Revolutionary S-Off and then go through the updates from 2.89 on up.
Hope this helps others.
EDIT:
I may be too tired at the moment to figure this out, but for some darn reason both the official OTA Updates would not flash from the bootloader on a stock 2.89.651.2 phone with S-Off (both phones actually). Didn't matter if it was renamed PG86IMG.zip or left as officially downloaded to sdcard/download and booting into the stock recovery. The MD5 of my 651.5 update file matches Ramjet73's as well. But If I connect to wifi, do a system update, let it download (how I got the files) and reboot automatically, it works fine and updates without issue.
Click to expand...
Click to collapse
Forgive me for being such a noob with this stuff.
I'm reading about hboot 1.58 needing to be bricked twice to be able to run the 1.13 RUU.
So to start, do I place the 18.7mb PG86IMG .zip (from the second quote in your last post) in the "download" folder of the sd card?
The stock
(OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z)
Click to expand...
Click to collapse
is there, so do I remove that one and replace it?
I don't think so but just to be sure, I drop the 18.7 PG86IMG zip folder in downloads and begin the brick process, then run the hboot 0.8.2 to downgrade?
*EDIT* ok, place in the MAIN directory. It's working and is unloading the .zip in bootloader
I need a new data sync cable, mine has started intermittently losing connection off and on...going to wait until I have a new one before I go any further.
Also, the latest version of ubuntu that Linux offers did not work. I found an earlier version(12.04) and the boot disk works so I am good to go on that
What is Hboot 0.8.2 ? Are you using Unknownforce's URT 3.1 Tool and following the "Downgrade/Unbrick" section?
This one:
http://forum.xda-developers.com/showthread.php?t=1563342
Yep, that is an outdated/earlier version. You need to use the Ultimate Recovery Tool from Unknownforce's thread as I linked earlier (URT v3.1) and use the LiveCd link.
see here
Sent from my "Up All Night Sleep All Day" Nexus 5!
THANKS
Well I just did a dry run with the Linux boot disk and terminal. Extracted downgrade.zip to HOME folder, ran the commands. I'm getting the correct code returns in the terminal. I got up to the:
Code:
Step 1... Plug in Device while holding down Volume Down key...
Waiting for device...
Just a matter of getting a new data sync cable now and I can do this...
Again thanks for your help, I'm pretty new to this process I've never altered a devices firmware manually before so it's an awesome experience as well..
Will report back in a couple days, hopefully with a newly rooted phone
--------
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?
otto325 said:
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?
Click to expand...
Click to collapse
Yep. Previously...
mpgrimm2 said:
....
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself) <<<--- HERE
Click to expand...
Click to collapse
Sent from my "Up All Night Sleep All Day" Nexus 5!