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.
Related
This procedure applies to both flyers and view
Required downloads
First download the Gingerbread RUU for your device from this thread.
If you don't have adb and fastboot on your PC
Get fastboot and adb tool for windows here
Get Fastboot and adb for linux here
I don't have a simple bundde for Mac, would welcome a link if anyone has one.
Download my universal misc_version and unzip to obtain the misc_version file.
Download tacoroot
Place both the misc_version and tacoroot.bin files in the same directory as adb
Procedure
Check the version number for your gingerbread RUU
In my example I am using this RUU: RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.08 9BU_3809.05.04.10_M_release_194964_signed.exe
The version is the part highlighted in red.
Boot your flyer up to android if it's not already on, with usb debugging enabled and connect it to the PC.
Run the following adb commands
Code:
adb push tacoroot.bin /data/local
adb push misc_version /data/local
adb shell chmod 755 /data/local/tacoroot.bin
adb shell chmod 755 /data/local/misc_version
adb shell /data/local/tacoroot.bin --setup
At this point your device will reboot to recovery
Simultaneously press Volume Up, Volume Down and Power
Reboot your device
Run the following command
Code:
adb shell /data/local/tacoroot.bin --root
Your device will reboot, do not worry if it does not boot fully, it doesn't matter for this procedure, and it is a side effect of this root exploit.
Run the following command:
Code:
adb shell /data/local/misc_version -s [COLOR="Red"]2.00.405.3[/COLOR]
Note that the number in RED is the version number retrieved in step 1.
Reboot to fastboot:
Code:
adb reboot bootloader
Run your RUU ( if on linux or mac, see other similar threads from me on how to RUU on those OSes )
Special Thanks
jcase for providing the tacoroot.
Nice release globatron! I was actually looking at Tacoroot for this last night but didn't really want to go into it too much and decided against using it. Glad to see I wasn't the only one with the idea for it though.
heh, Gave jcase the updated misc_version so he has it on the github radme for tacoroot already but didn't want to release the procedure until I has actually tested misc_version to run on at least a few HTC emmc devices and with multiple version string lengths.
Even if you didn't release this today, I probably would have started on it tonight, I'm a bored teenager with too much time. Still, keep up the good work. If you want me to make a script for you or anything, let me know and I'll get to work on it. (also, you know you can actually have adb from the recovery so you dont need to hit the buttons on it, just have it wait then adb reboot (or even adb shell reboot))
Of course I know that but that's not the what the buttons is about here.
What are the points of the button?
Sent by breaking the sound barrier
To ensure with absolute certainty that a log will be created.
Ah, you want the button presses to be logged to ensure it's done the job. Alright, fair enough.
Glad to TacoRoot in use!
Thanks for the spice jcase, just realized I had a typo in the procedure....jcase *provided*, not tested (well that too), tacoroot.
globatron said:
Thanks for the spice jcase, just realized I had a typo in the procedure....jcase *provided*, not tested (well that too), tacoroot.
Click to expand...
Click to collapse
is the typo msc_version being misc_version
thanks Kevin, fixed that.
yep, didnt notice it until someone tried to do my procedure today lol... copy and paste my friend lol. Plus I just need to know one thing. This brings you down to GB but still keeps you locked right? You still technically have to use HTC unlock to bring it back to 1.13.000 correct?
Part1: correct, you've never unlocked if you do this.
Part2: No, you don't have to unlock at all during this procedure.
so to go from the 1.14 hboot to 1.13 u dont need to htc unlock?
kevinrocksman said:
so to go from the 1.14 hboot to 1.13 u dont need to htc unlock?
Click to expand...
Click to collapse
That's correct.
globatron said:
This procedure applies to both flyers and view
Required downloads
First download the Gingerbread RUU for your device from this thread.
the download link takes me to the flyer RUU, i understand the view & flyer are the same except the 3g/4g network on the View. i just want to make sure i download the correct RUU for my View. what verision do i need? this one "RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.0531_NV_2.28_SPCS_release_198141_signed.exe"
agian thank you for the support
Click to expand...
Click to collapse
That one is fine. Express is the board name or the view so an RUU with express (not expresskt) in the name is what you need.
Hello, thanks for the downgrade help. Upgraded to honeycomb and hated it so I followed your instructions and everything went exactly as described until the middle of the RUU upgrade itself where it stopped and gave me an
ERROR[140]: BOOTLOADER VERSION ERROR
The ROM Update utility cannot update your android phone
Please get the correct ROM update utility and try again.
It won't successfully reboot now. When I go back to bootloader mode the recover screen shows
*** LOCKED ***
express pvt ship s-on rl
hboot-1.14.0005
microp-0656
radio-1.05.01.1006_3
emmc-boot
oct 25 2011, 16:35:13
used RUU_Express_Sprint_WWE_1.22.651.1
Its completely stock, was notified of the new update by htc and installed it over wifi. Thanks in advance for any help
What appears to have happened here is that somewhere along the way something didn't work fully and you failed to set the version to the same as or lower than the RUU you used.
I would need to see the output of :
Code:
fastboot getvar version-main
to be absolutely certain of this. If that is the case then becasue you are completely stock the best course of action would be for you to return it for repair. Tell the technical support people that this happened when you tried to take the OTA update to HoneyComb. The alternative will require you to use the HTC unlock.
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
navenine said:
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
Click to expand...
Click to collapse
Try this, starting over. You shouldnt run into any hiccups.
tailsthecat3 said:
Try this, starting over. You shouldnt run into any hiccups.
Click to expand...
Click to collapse
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
navenine said:
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
Click to expand...
Click to collapse
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
tailsthecat3 said:
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
Click to expand...
Click to collapse
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
hey im trying to use the ruu to get back to stock , just re locked the phone , and im STILL getting errors with ruu, its saying Update Failed : Hboot version is older , im on hboot 1.5000 .........Im losing my mind trying to get this thing back to stock and out of htc screen logo bootlooping.........any ideas?
navenine said:
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
Click to expand...
Click to collapse
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
tailsthecat3 said:
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
Click to expand...
Click to collapse
this just got even worse, I uninstalled the drivers, and now I can't reinstall them. I can't find them. My computer wont recognize my phone at all. I've tried to goto the device manager and find them online automatically, and I've tried the google USB drivers from the extra folder from the SDK Manager...
if you can point me toward the USB drivers that'd be great, but regardless, what your saying is I need to connect my phone while its in the bootloader? not once its booted? or are you saying I need to boot my phone through the bootloader selecting "fastboot" first?
thanks again
-Nave
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
navenine said:
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
Click to expand...
Click to collapse
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I pushed everything over, got it into the fastboot USB and then typed the "fastboot flash recovery recovery.img" command line
my script was:
sending 'recovery' <5068 KB>...
Okay [ 1.207s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote:signature verify fail>
finished. total time: 1.855s
any ideas?
tailsthecat3 said:
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
Click to expand...
Click to collapse
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
navenine said:
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
Click to expand...
Click to collapse
Where were you going wrong? And what'd you do to correct it? So everyone knows, in case they encounter the same issues.
Sent from my Google Nexus S 4G via XDA Premium
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
navenine said:
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
Click to expand...
Click to collapse
I appreciate that, thank you.
Hey guys,
beforehand: I'm totally new to this topic, so please be patient.
I got my HTC Flyer Wifi & 3G [P510e] back from reparation and the guys there also updated my Flyer to Honeycomb (3.2.1). Since I cannot use my touch buttons anymore, I would like to do a downgrade to Gingerbread again.
I've searched here and found this topics:
http://forum.xda-developers.com/showthread.php?t=1428104
http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
Now I'm not sure what to do: do I need to S-OFF my Flyer to make a downgrade, like shown in the following thread?
http://forum.xda-developers.com/showthread.php?t=1358758
Which Gingerbread-Version do I have to use, how can I find that out? And where do I get it from?
And the most important thing: what is the worst thing that could happen if I mess up something?
My Flyer is currently S-ON, my HBOOT-Version is HBOOT-1.11.0011 (see attached file) and it's a german version, if that is important to know.
I would appreciate it if someone would help me with this. Normally I'd ask my ex-boyfriend to do this for me, but since we broke up, I want to manage this kind of stuff on my own. :fingers-crossed:
Katzenmuetze said:
Hey guys,
beforehand: I'm totally new to this topic, so please be patient.
I got my HTC Flyer Wifi & 3G [P510e] back from reparation and the guys there also updated my Flyer to Honeycomb (3.2.1). Since I cannot use my touch buttons anymore, I would like to do a downgrade to Gingerbread again.
I've searched here and found this topics:
http://forum.xda-developers.com/showthread.php?t=1428104
http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
Now I'm not sure what to do: do I need to S-OFF my Flyer to make a downgrade, like shown in the following thread?
http://forum.xda-developers.com/showthread.php?t=1358758
Which Gingerbread-Version do I have to use, how can I find that out? And where do I get it from?
And the most important thing: what is the worst thing that could happen if I mess up something?
My Flyer is currently S-ON, my HBOOT-Version is HBOOT-1.11.0011 (see attached file) and it's a german version, if that is important to know.
I would appreciate it if someone would help me with this. Normally I'd ask my ex-boyfriend to do this for me, but since we broke up, I want to manage this kind of stuff on my own. :fingers-crossed:
Click to expand...
Click to collapse
if you are not s-off now,then your 2nd and third links are not really of any use.
depending on wether you want to use htcdev for root,or a temporary root exploint you need to use either this thread:
http://forum.xda-developers.com/showthread.php?t=1307759 (for htcdev)
or your first link:
http://forum.xda-developers.com/showthread.php?t=1428104
the disadvantage to htcdev for root,is that it will leave a watermark that shows you have unlocked the bootloader,and as the unlock website states,this could void "all or parts of your warranty"
the disadvantage of the other link,is that the root exploit(taco root) is kind of a funky exploit,and while safe, is a little tricky to use if youre not used to doing things like this.
after you have downgraded to gingerbread,you can use revolutionary to s-off( http://revolutionary.io/ ) this leaves the door open to upgrade to honeycomb with s-off later,if you desire. it will also let you install a custom recovery,and add root access so that you can modify the stock gingerbread rom,or flash a custom GB rom, so that you can continue to operate on GB without pesky OTA notifications.
last and not least,if you cannot find a GB ruu that supports your CID (carrier identification) you will need a goldcard to downgrade to a different carrier or unbranded RUU. (directions to make a gold card: http://www.addictivetips.com/mobile...-gold-card-for-htc-desire-without-hex-editing)
just holler if you have further questions.
if you decide to go the htcdev route,i have a guide with some download links that may simplify that process somewhat for you,and can reproduce it here if you desire.
scotty1223 said:
if you decide to go the htcdev route,i have a guide with some download links that may simplify that process somewhat for you,and can reproduce it here if you desire.
Click to expand...
Click to collapse
That would be great, thank you.
TSGM said:
That would be great, thank you.
Click to expand...
Click to collapse
sorry for the delayed reply.
here is my "htcdev" guide:
i sometimes refer folks to my rezound guide in other forums,so i decided to make a slightly more "universal" version that i could replicate in other forums,so everyone has a dedicated guide,and there are not accidents with accidental application of rezound specific details or files. devices i am familiar with i will try and tweak and add device specific recovery downloads/info. whatever device youre working on,please feel free to post in this thread,i will be happy to assist you
before we get started,however,be aware that htcdev does have its limitations. it can be used if you only wish to add root access to delete bloat and run a few root requiring apps,but IMO it is best used as a "steppig stone" to get root for downgrade,or for other exploits to run. if s-off is availble on any "downgradeable to" firmware,i do highly recomend to try and achieve that goal if you wish to activly flash roms. im happy to help with this,as well,if needed.
the basic steps will be:
1)unlock with htcdev
2)temporarily or permanently flash a recovery
3)flash root files
before you start,go ahead and download these files:
-mini-adb.zip: mini-adb.zip
-the latest custom recovery image of your choice, for your device(for the flyer,use http://hyuh.net/files/flyer/downgrade/recovery.img md5 bb366b025dcc454ffe8b21b8bf0c72d0)
-superuser files: for froyo use superuser 3.07 (found on revolutionary public wiki). for GB,HC or ICS,use the latest superSU from this thread on xda (the download link is where is says: CWM installable ZIP: CWM-SuperSU-v0.96.zip )
-go to HTCdev - Unlock Bootloader and register an account
1)unlock with htcdev
first thing you need is drivers for adb to see your phone. if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary
most guides simply say "follow the directions to unlock with htcdev" but im gonna go thru it with ya the mini-adb.zip file is all the files that htcdev is telling you to download and put into a folder,so allready this should be a lil easier
1)prepair ADB
-unzip your mini-adb.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC(sorry, you mac guys will need to develop this for yourself,i dont have a mac). root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "mini-adb_devicename" since youll be putting some device specific files in here. (directions from here forward will assume this folder to be named "mini-adb_vigor",as an example)
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your mini-adb_vigor directory. type the following at the prompt in your cmd window:
cd c:\mini-adb_vigor
your command promt should change to "c:mini-adb_vigor>" provided you: 1)unzipped the miniadb zip 2)put the folder on your c drive 3)entered the name of the folder correctly ("mini-adb_vigor" in this case)
-now make sure usb debugging is checked in settings/apps/development,and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
2)unlock using htcdev
-go to HTCdev - Unlock Bootloader and sign in to your account. chose your device from the "select your device bar"(or "other supported devices" if its not listed) and click the green "begin unlock bootloader" button underneath.
-click yes to procede,then read the warnings before checking the boxes and clicking yes to continue,as they are basically explaining that your warranty is now void,and any repairs that your phone needs that may have been a result of unlocking your bootloader and messing with your phones operating system may no longer be covered under mfgr warranty
*check your hboot screen. if you allready have an htc compatible hboot, then skip ahead to the next step,you dont need this.if you have a pink **locked** at the top of the hboot screen,then it is compatible with htcdev. if you dont have a compatible hboot,then download the RUU for the new hboot. right click it,and run as administrator. plug in your phone when prompted to. it will ugrade your hboot to the htcdev unlock compatible version.
-steps 1-4 are describing how to get your phone into bootloader mode and connect it to your PC,wich we have done above. ignore these steps and simply type in your cmd window:
adb reboot bootloader
it may take several seconds,but this command should boot your phone into the "fastboot" screen wich is white with a bunch of colored writing. once this happens,make sure your phone is still being seen in fastboot. type:
fastboot devices
again,this should return your phones serial number.
-click the green procede to step 5 bubble.
-steps 5-7 are telling you how to find the files and utilities inside your mini-adb folder. you have them,so ignore steps 5-7.
-click the green procede to step 8 bubble.
-heres where steps are important,steps 8-10 are telling you how to get your unlock token,and send it to htc. its phone specific(so they prolly know your serial number,meid,etc) so no,you cant use your buddys unlock token and not have htc know that youve unlocked your bootloader. copy this line either from below,or from step 8,and paste it into the prompt in your cmd window. you have to right click to paste in cmd,you cannot control/v :
fastboot oem get_identifier_token
-after yuo hit enter,you will get a bunch of letters that are your identifier token. not much i can say,other than follow the directions in steps 9 and 10 to copy and submit your identifier token to HTC. make sure you get the characters as shown in the pic,with no extra lines or letters. note that you can also hit the "enter" key on your PC to copy,as well as right clicking.
-click the green submit button. wait patiently for an email containing your unlock code. (dont worry,it should come pretty fast )
-save the unlock_code.bin that htc sends you directly to your mini-adb folder(if your PC automatically downloads somewhere else,no biggie. just move the unlock code to mini-adb folder)
-click the link in your email to get the rest of the unlock instructions
-step 12 is where them magic happens copy from below,or from htc dev:
fastboot flash unlocktoken Unlock_code.bin
-youll see the purdy screen pictured in step 13. use the vol rocker to chose "yes unlock bootloader" and select it with the power button. your phone will reboot,performaing a factory data reset in the process. your data is gone,sorry this boot may take a bit longer than they normally do,dont freak out this is normal
as you can see,once the adb files are put in one place to download,its not hard to use,and the commands are pretty simple. below is what you will see in your command window,the red are my inputs.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:mini-adb_vigor>[COLOR="red"]fastboot oem get_identifier_token[/COLOR]
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO2ADC7C0C0F1BAF92074BAE9B0035CB6A
INFO021839BFA7465CD0788664688DCCFDEA
INFO33A2FD2C96C7308DD3C57A517DBA8E14
INFO8048F98A9FEA06B8F2AD05D4D3497CFE
INFO6FCCC1DC4E31E0C6F54CEA18D9A80C82
INFO27C33E209D472E6C11753E9D7BCBCE6D
INFO90D9F226E827B6C26165A029B6F7DFF2
INFO63E382B4C82F9F6D866C01B9823ED1BC
INFO0EEFA859327E6B5AC4C24533C9DFA7AF
INFODBD70D55E4666B4B41828B76FFBD010C
INFO1B916E350EFF199EA5B096FF3337FE19
INFO40E6CA9E7F1DD5B33D8D4780DD775289
INFO953404686AEC4C3CB6F1BBB9DC69BA13
INFO8738C00DAFF280ECF02D0C7A66E13855
INFO1D756616732FF47915EAD551A6933E08
INFO10C541C7RD02C14991E83CC49FCA4B92
INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.069s]
finished. total time: 0.070s
c:mini-adb_vigor>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
sending 'unlocktoken' (0 KB)... OKAY [ 0.143s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.011s]
finished. total time: 0.156s
c:mini-adb_vigor>
2)flash a recovery
if you want to run stock,do not permanently install your recovery. keeping the stock recovery on the phone will ensure that you recieve OTAs without a hitch,wich i know is important to alot of users. YES,the OTA will break root. its no big deal. one good thing about htcdev is that you will always be able to reroot after,simply by following steps 2 and 3 again to launch recovery,flash superser.
once youve either skipped past all the setup,or have re-set up and are ready to root,chose either of the following options to either permantly or termporarily install a recovery:
1)temporary recovery:
-move the recovery image file you downloaded above and place it into the mini-adb folder.
-put the superuser zip file onto your phones sd card
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb directory:
cd c:\mini-adb_vigor
-make sure youre connected by typing:
adb devices
-should return serial number
-check the md5 of your recovery image:
md5sums <recoveryname>.img
**make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)
-boot to bootloader:
adb reboot bootloader
-check for connectivity:
fastboot devices
-should return serial number
-temporarily launch your recovery to phone memory:
fastboot boot <recoveryname>.img
-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone. youll then see the HTC splash screen,then your recovery.
in your command window you will see(red are my inputs):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:mini-adb_vigor>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img 915d5e3cb662076f36f3d6e54759e951
c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:mini-adb_vigor>[COLOR="red"]fastboot boot recovery-ra-vigor-3.14-gnm.img[/COLOR]
downloading 'boot.img'... OKAY [ 1.518s]
booting... OKAY [ 0.005s]
finished. total time: 1.523s
2)permanently install your recovery
-move the image file you downloaded above and place it into the mini-adb folder.
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb directory:
cd c:\mini-adb_vigor
-make sure youre connected by typing:
adb devices
-should return serial number
-check the md5 of your recovery image:
md5sums <recoveryname>.img
**make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)
-boot to bootloader:
adb reboot bootloader
-check for connectivity:
fastboot devices
-should return serial number
-permanently flash your recovery to phones recovery partition:
fastboot flash recovery <recoveryname>.img
-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone,then a (really,really fast) red bar as it flashes it. amon ra is now permanently on your phone when you need it. be aware that you can no longer accept OTAs,unless you reinstall the stock recovery at some point before the next OTAs are pushed.
-to get to recovery,push the power button to select hboot. once in hboot wait for the green writing to flash and disapear,then select recovery.
*note that you can still launch recovery by using the command from scenario 1 above.
-youll then see the HTC splash screen,then your recovery.
and the code(again,red my inputs):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="red"]cd c:\mini-adb_vigor[/COLOR]
c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img 915d5e3cb662076f36f3d6e54759e951
c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:mini-adb_vigor>[COLOR="red"]fastboot flash recovery recovery-ra-vigor-3.14-gnm.img[/COLOR]
sending 'recovery' (7074 KB)... OKAY [ 1.659s]
writing 'recovery'... OKAY [ 5.179s]
finished. total time: 6.840s
3)flash superuser root files*
there is not much to explain with this one. if booted to recovery from above,use the recovery menu on your phone to:
-make a backup of your stock,unrooted rom. completely optional,but a very good idea,IMO.
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-reboot
*congratulations,youre rooted
if your device has procedures to s-off,or procedures to downgrade to more exploitable firmware,you can procede with that now
for the flyer we can use these directions: http://forum.xda-developers.com/showthread.php?t=1307759
after we downgrade to gingerbread,we can root with revolutionary:
http://forum.xda-developers.com/showthread.php?t=1194709
after yoou have s-off on gingerbread,you can update back to honeycomb:
http://forum.xda-developers.com/showthread.php?t=1358758&highlight=honeycomb+easy+s-off
if youre considering leaving htcdev unlock,read this if you want to flash roms: http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html
s-off is better,and worth whatever extra efforts to achieve if available.
*hope it helps,holler if you have questions
donate to my device fund
Click to expand...
Click to collapse
gave you some links at the end to downgrade,then s-off,then upgrade back to honeycome,as well as a link that may be of some value if youre considering just unlocking via htcdev and leaving it at that. htcdev is a PITA if your intent is to flash different roms,and its even more dificult as there is no other option to chagne roms other than manually installing the boot image(i have verified that fastboot booting the recovery on the flyer does NOT provide the same advantages it does on the rezound,and other htc phones.
i will be happy to help you with any questions you have about htcdev vs s-off,or with the unlock procedure. if you just want to be rooted on the stock HC rom,htcdev unlock works,but thats about it
we can also help you with the downgrade etc. after yovue completed this,but will save that for later so we dont overwhelm you with info
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.
We need a dedicated thread for this. The original thread is far too cluttered already.
I was not able to obtain S-OFF using this combination- CID= 11111111, Running Viper (1.13) and DSB's latest (3.13) cubed kernel.
I was able to get S-OFF by simply flashing the stock/writeable kernel and related modules.
Hope this helps someone. Again, I did not have to move to a stock ROM, relock, or any of that other business.
Anybody that I going to paste their output on here please put it in the
Code:
brackets [/ code][/COLOR]
Error 99 as shows here (below) Either A) Restore an Older Nandroid or B) flash a Stock Rom/Kernel
[code]C:\Users\Family\Desktop\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot fl
ash zip PL8320000-DNA.zip
sending 'zip' (36905 KB)...
OKAY [ 2.958s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
[COLOR="Red"]FAILED (remote: 99 unknown fail)[/COLOR]
finished. total time: 3.188s
Thanks much. All I needed was a different kernel. OP updated
Irieone said:
We need a dedicated thread for this. The original thread is far too cluttered already.
I was not able to obtain S-OFF using this combination- CID= 11111111, Running Viper (1.13) and DSB's latest (3.13) cubed kernel.
I was able to get S-OFF by simply flashing the stock/writeable kernel and related modules.
Hope this helps someone. Again, I did not have to move to a stock ROM, relock, or any of that other business.
Click to expand...
Click to collapse
Strange, I had the exact setup and it worked perfect for me on first try without having to change kernel! ??
Changing Kernels
I originally had Error 99 instead of 92. After flashing back to a stock kernel, I was able to obtain S-OFF. Did some searching through the threads and found that this had worked for other people. Glad to see we have S-OFF now.
Code:
F:\TDDOWNLOAD\adb>fastboot oem boot
< waiting for device >
... INFOmonarudo_vibrate_device_time(): vibrate 200(ms)...
INFOBoot/Recovery signature checking...
INFOTZ_HTC_SVC_HASH ret = 0
INFOsetup_tag addr=0x80600100 cmdline add=0x003147C8
INFOTAG:Ramdisk OK
INFOTAG:skuid 0x32401
INFOTAG:hero panel = 0x94005B
INFOTAG:engineerid = 0x0
INFOTAG: PS ID = 0x0
INFOTAG: Gyro ID = 0x1
INFO[SD_ERR] The project does not support SD card
INFOE0902910 E0902E20
FAILED (status read failed (Too many links))
I have tried many methods, but still the same
so you must have a stock kernel flahed first? can a specific file be linked here/
ADB will not recognize my phone , Developer options are on , USB debugging on , I reinstalled android SDK , I have changed USB ports , and yet still a no go . Any suggestions will be helpful ????
cbrown245 said:
ADB will not recognize my phone , Developer options are on , USB debugging on , I reinstalled android SDK , I have changed USB ports , and yet still a no go . Any suggestions will be helpful ????
Click to expand...
Click to collapse
Some, including me, have had issues with windows 8 and adb-if using win 8. If not try running a command prompt from within the sdk platform-tools folder itself (shift+right click and open command window here) hope that helps
rootntootn said:
Some, including me, have had issues with windows 8 and adb-if using win 8. If not try running a command prompt from within the sdk platform-tools folder itself (shift+right click and open command window here) hope that helps
Click to expand...
Click to collapse
Im on windows 7 but I will give this a try anyways . Thanks
Try toggling off/on debugging while phone is plugged in
you need the device to be recognized while running for adb and from hboot for fastboot commamds
I think the 99 error can be fixed simply by running superCID again after seeing the failed message with 99 in it. I believe I stumbled across this accidentally after updating a backup. Someone said to go back to a back up version prior to doing FacePalm but I had none so I just restored my rom and for the hell of it ran superCID again. I had positive results.Worked immediately...so I'm thinking it was that rather than the backup-either way it worked just fine.
rootntootn said:
I think the 99 error can be fixed simply by running superCID again after seeing the failed message with 99 in it. I believe I stumbled across this accidentally after updating a backup. Someone said to go back to a back up version prior to doing FacePalm but I had none so I just restored my rom and for the hell of it ran superCID again. I had positive results.Worked immediately...so I'm thinking it was that rather than the backup-either way it worked just fine.
Click to expand...
Click to collapse
i have seen 10+ ways to get it to work... so its more of a trial and error kind of deal