Related
I hope I am not posting where I am not supposed to, but I desperately need help. I am a noob and have managed to brick my inspire, or at least that's my guess. I can still get in to hboot, but when I select recovery, nothing happens. This all started after trying to use the htc boot unlocker. My screen shows the following when in hboot
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MIROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Dec 22 2011,14:28:19
I have tried loading the stock images using the PD98IMG.zip files that I have found throughout the site, but nothing seems to be working. Please help, or if you can point me to someone that can I would greatly appreciate it. I hate to be a pain, but I don't know what else to do.
dalton42503 said:
I hope I am not posting where I am not supposed to, but I desperately need help. I am a noob and have managed to brick my inspire, or at least that's my guess. I can still get in to hboot, but when I select recovery, nothing happens. This all started after trying to use the htc boot unlocker. My screen shows the following when in hboot
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MIROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Dec 22 2011,14:28:19
I have tried loading the stock images using the PD98IMG.zip files that I have found throughout the site, but nothing seems to be working. Please help, or if you can point me to someone that can I would greatly appreciate it. I hate to be a pain, but I don't know what else to do.
Click to expand...
Click to collapse
YOUR PHONE IS NOT BRICKED. The term bricked means that your phone is a useful as a brick, i.e. if you can get into HBOOT, it's not bricked.
Gotta ask though, why did you not use the Hack Kit as its the only reliable method to root, my advice to you sir is when this gets cleared up READ AND EDUCATE YOURSELF before you really do brick your phone.
If you have a SDcard reader, pop out the SDcard and place one of the PD98IMG stock ROMs on your SDcard. From here you can reboot into HBOOT with the sdcard in your phone and HBOOT should pick up the PD98IMG and flash a working stock ROM. From here, you can root with the Hack Kit...
This will help you, read it and do what the stock ROM option...if you can get into HBOOT
I have tried doing that, it says loading image, then parsing, then goes back to the hboot screen, it doesn't say press volume up to update or anything else as I have read in many other posts. Am I doing something wrong? As far as not using the hack kit, I didn't really stumble on that until after it was to late, sure wish I had found it in the first place. Guess if I could just get it back to factory, I would accept that doing this isn't for me and not mess with it again. I am good at following directions, but nothing I have tried seems to work.
dalton42503 said:
I have tried doing that, it says loading image, then parsing, then goes back to the hboot screen, it doesn't say press volume up to update or anything else as I have read in many other posts. Am I doing something wrong? As far as not using the hack kit, I didn't really stumble on that until after it was to late, sure wish I had found it in the first place. Guess if I could just get it back to factory, I would accept that doing this isn't for me and not mess with it again. I am good at following directions, but nothing I have tried seems to work.
Click to expand...
Click to collapse
is the file named exactly "PD98IMG.zip"..you may also want to check the hide extension option to be sure its not hiding the .zip because if it is and you renamed it to "PD98IMG.zip" with the hide extension on, the phone will read it as "PD98IMG.zip.zip" and you would get that error.
haha and yeah man, we've all been there...I don't want to discourage you man, rooting is such an awesome experience and the hack kit is a pretty straight forward process, if you do the research and take the time to understand what you're doing, but lets see if we can help you out here first. I had the same issue you're having when I tried to flash a radio (same PD98IMG method you're trying to use) and it turned out to be the hide extension issue.
I had also verified that as well, I went under tools, folder options, view tab, scrolled down to hide extensions for known file types and unchecked... And, everything was correct, just verified to be on the safe side.
dalton42503 said:
I had also verified that as well, I went under tools, folder options, view tab, scrolled down to hide extensions for known file types and unchecked... And, everything was correct, just verified to be on the safe side.
Click to expand...
Click to collapse
hmm, so its named PD98IMG.zip caps and everything? If its not working you m ay have to get a stock RUU and run it through fastboot..
This is why you should educate yourself first. You do not need to unlock the bootloader from the HTC dev site. Now you could flash the the stock ruu from the PC and then use the hack kit. Check the stickies in the Inspire general section for more help.
Sent from my HTC Inspire 4G using Tapatalk
I understand that I should have been a little more educated first now, but I thought I had everything in order, thats what thinking gets me... I have tried running the stock ruu, but it gives the following error.
ERROR[155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
I did notice the Image version the program shows is on the phone is 3.13.0.0, and it is trying to put 2.47.502.7 on the phone... Is this the problem? If so, whats the solution, I am so lost now its not even funny.... I apologize everyone.
dalton42503 said:
I understand that I should have been a little more educated first now, but I thought I had everything in order, thats what thinking gets me... I have tried running the stock ruu, but it gives the following error.
ERROR[155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
I did notice the Image version the program shows is on the phone is 3.13.0.0, and it is trying to put 2.47.502.7 on the phone... Is this the problem? If so, whats the solution, I am so lost now its not even funny.... I apologize everyone.
Click to expand...
Click to collapse
Dalton, lock your bootloader again. Boot into fastboot and plug the phone. You will see fastboot usb at the top. Then plug your phone and open cmd session. Once there type fastboot oem relock. Once that is done, try flashing the .exe file in the HTC site (original GB update), making sure that you have HTC Sync installed.
If that fails, then I would try using the HACK Kit to gain S-OFF and root. You will then be able to revert to stock or flash a custom rom...
Had a similar problem when using aahk my own fault and I took care of it. Long winded, so short of it, are you trying to install through
1. hboot or 2. on the computer using HTC rom update?
I ended up trying 2. But ended up using aahk to finish.
HTC update errored out and the recovery portion would not work, just in a boot loop on HTC logo
This was good news as aahk could take over on USB during that HTC green letters white background.
I'd suggest reading the effen manual run the tool to get it up and going, figure out what you want to do. I've used it to return to stock with s off before go back into roms.
So look at those options know what you want and then power on the phone USB connected and during HTC screen enter your number the kit should take over and give you what you asked it.
That should give you a working rom image.
--will'm
Sent from my Inspire 4G using XDA Premium HD app
willm98G97B said:
Had a similar problem when using aahk my own fault and I took care of it. Long winded, so short of it, are you trying to install through
1. hboot or 2. on the computer using HTC rom update?
I ended up trying 2. But ended up using aahk to finish.
HTC update errored out and the recovery portion would not work, just in a boot loop on HTC logo
This was good news as aahk could take over on USB during that HTC green letters white background.
I'd suggest reading the effen manual run the tool to get it up and going, figure out what you want to do. I've used it to return to stock with s off before go back into roms.
So look at those options know what you want and then power on the phone USB connected and during HTC screen enter your number the kit should take over and give you what you asked it.
That should give you a working rom image.
--will'm
Sent from my Inspire 4G using XDA Premium HD app
Click to expand...
Click to collapse
He won´t be able to use the Kit if the bootloader is unlocked. HE MUST RELOCK Bootloader...then run the Kit...It´s worth mentioning that...
True, never ran htc s unlock option.
Sent from my Inspire 4G using XDA Premium HD app
Thanks A MILLION!!!
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
dalton42503 said:
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
Click to expand...
Click to collapse
Glad you have it back....yeah you'd better read and make sure what are about to do it and of course what risks are involved before making a move....
Dalton,
I would suggest following glevitan's and willm's assertion of getting s-off and root to use custom roms. Custom roms are WAY better than anything HTC has to offer, and much easier to install, if you have an issue warranty wise, you can always return to stock. Just make sure you know how to flash correctly, search for it and you will find easy instructions, and if memory serves, a youtube video which helped me greatly.
dalton42503 said:
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
Click to expand...
Click to collapse
Can you tell me the which firmware or send me a link.I have a same problem
If you are using AT&T branded cell then go to the htc.com site and in the support section of the inspire you will find it. Otherwise, you will find stock roms in the general section of this forum
Sent from my Inspire 4G using XDA
glevitan said:
If you are using AT&T branded cell then go to the htc.com site and in the support section of the inspire you will find it. Otherwise, you will find stock roms in the general section of this forum
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
I am having a bootloader error with stock ro.(error 140)
How can i fix it
ydnbngl said:
I am having a bootloader error with stock ro.(error 140)
How can i fix it
Click to expand...
Click to collapse
if you have unlocked the bootloader then relock it...then run it again.
glevitan said:
if you have unlocked the bootloader then relock it...then run it again.
Click to expand...
Click to collapse
It is relocked and ship s-on
Folks, I wouldn't call myself a n00b in flashing phones--I've been flashing ROMs since my HTC Wing so I feel like I have a decent amount of experience under my belt. But this Sensation...
From the start, performing S-OFF was tricky in itself, particularly with the paperclip trick. Miraculously, it worked after the third try. Flashing ROMs was a whole different monster. Even with 4ext, I could only flash THREE ROMs from the huge collection in the Development forum. And I honestly don't even know why--I kept on getting Error 0 for every build I tried to load. It was only through luck or magic that I was able to flash HyperNonsense, a MIUI build, and another one that I don't remember. Upgraded 4ext to latest version: nope. Changed SD card: nope. Different sequences of superwipe/no superwipe, clear dalvik, etc.: nope. I'm using HyperNonsense for now since it's pretty legit, but even then, I'm getting reboots all over the place. Stock kernel or different kernels--doesn't matter. I have a hunch it has to do with the bottom row of capacitive buttons running so hot.
Oh well, just holding out for the One X+ on T-Mobile or the next Nexus device. Just wanted to let out my despair and frustration. Thanks, guys. :good:
Long live the HD2. :silly:
Have you tried not using superwipe and using factory reset/wipe from 4ext recovery instead? Never had a problem with that.
Also I've never had to use the wire trick to have S-OFF. Gained it back when I was running GB, and still have it. Even after flashing OTA updates.
Sent from my HTC Sensation using xda developers app
nuron said:
Folks, I wouldn't call myself a n00b in flashing phones--I've been flashing ROMs since my HTC Wing so I feel like I have a decent amount of experience under my belt. But this Sensation...
From the start, performing S-OFF was tricky in itself, particularly with the paperclip trick. Miraculously, it worked after the third try. Flashing ROMs was a whole different monster. Even with 4ext, I could only flash THREE ROMs from the huge collection in the Development forum. And I honestly don't even know why--I kept on getting Error 0 for every build I tried to load. It was only through luck or magic that I was able to flash HyperNonsense, a MIUI build, and another one that I don't remember. Upgraded 4ext to latest version: nope. Changed SD card: nope. Different sequences of superwipe/no superwipe, clear dalvik, etc.: nope. I'm using HyperNonsense for now since it's pretty legit, but even then, I'm getting reboots all over the place. Stock kernel or different kernels--doesn't matter. I have a hunch it has to do with the bottom row of capacitive buttons running so hot.
Oh well, just holding out for the One X+ on T-Mobile or the next Nexus device. Just wanted to let out my despair and frustration. Thanks, guys. :good:
Long live the HD2. :silly:
Click to expand...
Click to collapse
It has nothing todo with the capacitive buttons running hot. Have you tried a different recovery like CWM because this seems like a recovery issue. As a side note, try disabling signature verification in 4EXT or better still, attempt to flash a ROM with aroma installer in and then save the aroma log and post it here
nuron said:
Folks, I wouldn't call myself a n00b in flashing phones--I've been flashing ROMs since my HTC Wing so I feel like I have a decent amount of experience under my belt. But this Sensation...
From the start, performing S-OFF was tricky in itself, particularly with the paperclip trick. Miraculously, it worked after the third try. Flashing ROMs was a whole different monster. Even with 4ext, I could only flash THREE ROMs from the huge collection in the Development forum. And I honestly don't even know why--I kept on getting Error 0 for every build I tried to load. It was only through luck or magic that I was able to flash HyperNonsense, a MIUI build, and another one that I don't remember. Upgraded 4ext to latest version: nope. Changed SD card: nope. Different sequences of superwipe/no superwipe, clear dalvik, etc.: nope. I'm using HyperNonsense for now since it's pretty legit, but even then, I'm getting reboots all over the place. Stock kernel or different kernels--doesn't matter. I have a hunch it has to do with the bottom row of capacitive buttons running so hot.
Oh well, just holding out for the One X+ on T-Mobile or the next Nexus device. Just wanted to let out my despair and frustration. Thanks, guys. :good:
Long live the HD2. :silly:
Click to expand...
Click to collapse
Post combat time. *Puts on Armor*
The wire trick is only necessary if you got screwed out of every other S-OFF method. I used Revolutionary and got S-OFF the day I rooted it. As for your ROM issues, that's pretty odd and unheard of to me. Try to flash one of those error 0 ROMs and Dump your recovery.log here after the flash, I'll look at it. As for the capacitive buttons, it's not the buttons running hot, but the fact that the CPU is literally right behind it. It doesn't run hot for me unless I start a game, and even that varies by ROM. Never gets hot on CM9. HyperNonSense 3.3 always runs hot though, no matter what. hyperNonSense 2.7 was the best :/
Anyway send in the recovery log, I'll try help you with that. PM me as well because I won't remember this thread after 5 minutes.
Thanks very much for all of your replies. I think I'll start with removing 4ext and run regular CWM. How would I go about uninstalling 4ext?
Hypernonsense always reboots for me
Sent from my Sensation using xda premium
nuron said:
Thanks very much for all of your replies. I think I'll start with removing 4ext and run regular CWM. How would I go about uninstalling 4ext?
Click to expand...
Click to collapse
just flash over it. Are you sure you're doing everything right? Have the right firmware for the right roms? Sounds like you're missing something
se1000 said:
just flash over it. Are you sure you're doing everything right? Have the right firmware for the right roms? Sounds like you're missing something
Click to expand...
Click to collapse
Seems like I am. I'm S-OFFed, and before 3.33 FW was required, I wasn't on it. When the cooks started requiring it, I flashed it. How important is Super CID? Will that cause an Error 0?
nuron said:
Seems like I am. I'm S-OFFed, and before 3.33 FW was required, I wasn't on it. When the cooks started requiring it, I flashed it. How important is Super CID? Will that cause an Error 0?
Click to expand...
Click to collapse
Your problem may be that you flashed the wrong FW for your CID - that is why superCID is important because it allows you to flash any variation of the firmware you like (you will have seen there are about 10+ variations of the 3.33 firmware)
So maybe try superCID (its really easy) then reflash the radio
fredcorp6 said:
Your problem may be that you flashed the wrong FW for your CID - that is why superCID is important because it allows you to flash any variation of the firmware you like (you will have seen there are about 10+ variations of the 3.33 firmware)
So maybe try superCID (its really easy) then reflash the radio
Click to expand...
Click to collapse
Yep, this.
It takes a couple of seconds to do, and is super easy.
Like fredcorp6 said, SuperCID will allow you to flash any RUU or firmware from any region.
Sent from my CM9 Stable Sensation using XDA Premium
Alright, so I just performed Super CID and was looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1459767&highlight=3+33
I just flash 3.33 Universal?
nuron said:
Alright, so I just performed Super CID and was looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1459767&highlight=3+33
I just flash 3.33 Universal?
Click to expand...
Click to collapse
I recommend 3.32 fw, flash in fastboot or bootloader can't remember which lol. I don't see any reason for 3.33 fw and 3.33 u can't do fastboot commands
Sent from my Sensation using xda app-developers app
nuron said:
Folks, I wouldn't call myself a n00b in flashing phones--I've been flashing ROMs since my HTC Wing so I feel like I have a decent amount of experience under my belt. But this Sensation...
Click to expand...
Click to collapse
Ever installed linux on a d-box2 (famous settop-box of a german pay-tv provider, anno 1999)? No? Well, shut up, with this thing you're SO happy seeing "u-boot" in the display and having it boot from your tftp server, which of course only works with a properly configured arpd and a dhcpd that speaks the ancient "bootp" ...
Haha, no offense For me, sensation was a piece of cake, didn't even need any hardware hacks, just a nice tool called "revolutionary"
Zirias said:
Ever installed linux on a d-box2 (famous settop-box of a german pay-tv provider, anno 1999)? No? Well, shut up, with this thing you're SO happy seeing "u-boot" in the display and having it boot from your tftp server, which of course only works with a properly configured arpd and a dhcpd that speaks the ancient "bootp" ...
Haha, no offense For me, sensation was a piece of cake, didn't even need any hardware hacks, just a nice tool called "revolutionary"
Click to expand...
Click to collapse
Shut up. No one cares about you. This isn't a one-up contest. With that kind of supposed knowledge, you should be helping others. But nope, you instead add nothing to the thread.
Thanks everyone for all the help so far. uml, I'll flash 3.32 and get back to you.
GazaIan said:
Post combat time. *Puts on Armor*
The wire trick is only necessary if you got screwed out of every other S-OFF method. I used Revolutionary and got S-OFF the day I rooted it. As for your ROM issues, that's pretty odd and unheard of to me. Try to flash one of those error 0 ROMs and Dump your recovery.log here after the flash, I'll look at it. As for the capacitive buttons, it's not the buttons running hot, but the fact that the CPU is literally right behind it. It doesn't run hot for me unless I start a game, and even that varies by ROM. Never gets hot on CM9. HyperNonSense 3.3 always runs hot though, no matter what. hyperNonSense 2.7 was the best :/
Anyway send in the recovery log, I'll try help you with that. PM me as well because I won't remember this thread after 5 minutes.
Click to expand...
Click to collapse
True! i never had to use paperclip to S-OFF mine. Both the official HTC method (on HTC website) AND the non-official method here on XDA worked for me to S-OFF my sensation.
I didn't mind the paperclip method too much. I think I needed to do it because my HBOOT was of a different version than the regular easy-to-root versions.
nuron said:
Just wanted to let out my despair and frustration.
Click to expand...
Click to collapse
nuron said:
Shut up. No one cares about you. This isn't a one-up contest. With that kind of supposed knowledge, you should be helping others. But nope, you instead add nothing to the thread.
Click to expand...
Click to collapse
So ... what actual "addition" were you hoping for? I don't think you'd start a thread like this if you didn't kind of enjoy the "hard way" you obviously took
btw -- whole point was to contradict your title by example, just to say: there are worse, much worse
Don't you understand that the Sensation is one of the most aggravating devices ever FOR ME?
This thread could be useful for other XDA members if they run into the same problems that I did and are searching for solutions. But instead, they have to to read through your useless posts. This clutters up the whole thread and detracts from all the members who have helped with a response and possible solution.
Leave.
nuron said:
Don't you understand that the Sensation is one of the most aggravating devices ever FOR ME?
This thread could be useful for other XDA members if they run into the same problems that I did and are searching for solutions. But instead, they have to to read through your useless posts. This clutters up the whole thread and detracts from all the members who have helped with a response and possible solution.
Leave.
Click to expand...
Click to collapse
There are a LOT of useful threads with lots of useful info here. This isn't one of them. Just re-read your original post and stop being such a moron, thanks.
wow, no ****, Sherlock. But I couldn't find an answer so that's why I created this thread. Thanks for not helping. And thanks for cluttering up this thread. Don't start calling others a moron without evaluating yourself first.
First: Thanks to this great forum of developers and users, I have learned a lot in a short period of time. The HTC One S is my first Android handset, and I love it. All the wonderful tutorials and threads you guys created made learning the basics of rooting/flashing easy.
This is my second HTC One S handset, the previous one died from hardware failure. The previous handset had HBoot 1.06, and so I was able to flash the TWRP recovery and use the Trickdroid 9.1.0 flawlessly. The problem comes with this new handset, and I am not sure exactly what it is to troubleshoot. The current HBoot on the phone is 1.14 (which means I can't flash radios, etc.). After unlocking the bootloader, I flashed the latest TWRP recovery (2.4.1.0). After factory resetting the phone and installing the Trickdroid 9.1.0, the phone won't boot. If I hold the power for 5-10 seconds, the keys flash, that's it. I am able to get into the bootloader using the power + volume down method, and then I have to recover my phone back to factory settings using the RUU avaliable online. I have tried redoing this process 2-3 times now, and everytime I flash the JB rom, the phone won't boot. I am not sure if having a HBoot 1.14 prevents me from upgrading from ICS --> JB, recovery, or anything else. As I said, my knowledge of Android is very limited as I am a new user. I really would like to use the JB rom that is cleaned and optimized. If anyone has any suggestions on what I can do, I would greatly appreciate it. Right now, I just did the perm root to be able to get rid of some of the bloat (T-Mobile comes with so much garbage!). Thank you so much, once again, and any troubleshooting help will be returned with big kiss! :angel:
bombina said:
First: Thanks to this great forum of developers and users, I have learned a lot in a short period of time. The HTC One S is my first Android handset, and I love it. All the wonderful tutorials and threads you guys created made learning the basics of rooting/flashing easy.
This is my second HTC One S handset, the previous one died from hardware failure. The previous handset had HBoot 1.06, and so I was able to flash the TWRP recovery and use the Trickdroid 9.1.0 flawlessly. The problem comes with this new handset, and I am not sure exactly what it is to troubleshoot. The current HBoot on the phone is 1.14 (which means I can't flash radios, etc.). After unlocking the bootloader, I flashed the latest TWRP recovery (2.4.1.0). After factory resetting the phone and installing the Trickdroid 9.1.0, the phone won't boot. If I hold the power for 5-10 seconds, the keys flash, that's it. I am able to get into the bootloader using the power + volume down method, and then I have to recover my phone back to factory settings using the RUU avaliable online. I have tried redoing this process 2-3 times now, and everytime I flash the JB rom, the phone won't boot. I am not sure if having a HBoot 1.14 prevents me from upgrading from ICS --> JB, recovery, or anything else. As I said, my knowledge of Android is very limited as I am a new user. I really would like to use the JB rom that is cleaned and optimized. If anyone has any suggestions on what I can do, I would greatly appreciate it. Right now, I just did the perm root to be able to get rid of some of the bloat (T-Mobile comes with so much garbage!). Thank you so much, once again, and any troubleshooting help will be returned with big kiss! :angel:
Click to expand...
Click to collapse
Did you flash the boot.img via fastboot after flashing the rom?
rustykwak said:
Did you flash the boot.img via fastboot after flashing the rom?
Click to expand...
Click to collapse
That seemed to be the problem this whole time! Argh! Thanks! In the previous phone, I always flashed it after rebooting via FlashGUI. I guess the only looming problem now is that the Wifi doesn't work on this Trickdroid ROM for my HBoot (1.14). Blah.
bombina said:
That seemed to be the problem this whole time! Argh! Thanks! In the previous phone, I always flashed it after rebooting via FlashGUI. I guess the only looming problem now is that the Wifi doesn't work on this Trickdroid ROM for my HBoot (1.14). Blah.
Click to expand...
Click to collapse
theres a thread in dev section wifi partions perhaps that will help you out!
rustykwak said:
theres a thread in dev section wifi partions perhaps that will help you out!
Click to expand...
Click to collapse
Unfortunatly on that hboot I dnt think we can
Sent from my HTC One S using xda app-developers app
siqbudz said:
Unfortunatly on that hboot I dnt think we can
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yes, that is right. I think any HBoot higher than 1.09 (I am 1.14) will not be able to flash WiFi partitions. Any way we can make WiFi work on JB? Would upgrading the HBoot to 2.x fix this Wifi problem? I still don't know why it doesn't work though and not having Wifi is kind of a big deal.
I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!
If I were you I would stay away from toolkits altogether. Not because they are bad, only because you learn absolutely nothing from using them and usually come bomb the threads when **** hits the fan.
The wire trick is a fun little task to handle though so everything should be okay that way.
Sent from my Nexus 4 using Tapatalk 2
Toolkit
ArachnydZ28 said:
I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!
Click to expand...
Click to collapse
His toolkit is still there, just browse around a bit... or go here... http://d-h.st/users/hasoon2000/?fld_id=2818#files
acwest said:
His toolkit is still there, just browse around a bit... or go here...
Click to expand...
Click to collapse
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".
Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium
demkantor said:
Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
unlocked
Doubleshot PVT Ship S-On RL
Hboot- 1.45.0013
Microp-0353
eMMC-Boot
Nov 21 2011, 20:20:47
I do have recovery and hboot. Stock backup won't load though even though the file is there in recovery.
Thanks!
And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium
demkantor said:
And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I was able to reflash a version of CM10 I was using for a while and that works, but I can't find a stock one that will work. I've tried multiple, and they all give me "bad" error and don't finish the install.
I was going to try a different version of CM10, 10.1, or go to a stable release of 9. If none of those worked, I'd be happier with stock. None of the ones I've tried will work, but I'm assuming thats because I'm S-On, but since I can't find hasoon2000s S-Off tool everyone was raving about, and the wire trick requires stock ROM based on what the directions say, I find myself in a pickle.
The CM10 version I have can't do some basic things I need for work- like sync with my bluetooth in the car or not randomly freeze up during the day without me knowing it sending all my calls to voicemail. I tried versions of the others that other people are using (like silverL's 10.1 and the CM-listed stable CM9) and neither would load.
Do I have a different issue? AKA are other people with S-On able to load those Roms? I can try miktouch too.
---
Also trying to load via fastboot and I'm getting this error:
"Whoops: didn't find expected signature
read_central_directory_entry_failed
error: failed to access zipdata in [Whole bunch of non-english characters taking up a few lines]"
----
Update: Just to clarify, when I try to install a stock rom it gives me "Can't open [filename] (bad)
However, when I try to install the CM's, it installs fine and says "Install from sdcard complete" they just won't load when I restart my phone, except for the original version of CM10. (for example, in all the 10.1s I've tried I get "Unfortunately, the process com.android.phone has stopped" but the intro page will load. I figured that came down to an S-On issue when I tried to troubleshoot.
Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium
demkantor said:
Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.
ArachnydZ28 said:
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.
Click to expand...
Click to collapse
negative.
miktouch would go through the install process, and end at the Tmobile mytouch 4g slide screen forever. I know on one install it took a long time to "load" the first time so I left it on this screen for about 15 minutes to no avail. Let me know if there is any chance of it taking longer than that. Reinstalls were the same story.
I got CM9.1 to install by installing it twice on top of itself (not sure why that fixes it) but it was a tiny bit buggy.
Is there any chance this could be bootloader related or recovery related? I can try to reload those too. grrr...
Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium
demkantor said:
Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!
ArachnydZ28 said:
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!
Click to expand...
Click to collapse
You should try CWM 5.0.2.7. Also, since you are S-On you should extract the boot.img from Miktouch and flash it from fastboot, separately from the ROM. Since you have been on an ICS/Jellybean rom, I have to believe your original boot.img was replaced at some point. This is the only way to get back the Gingerbread boot.img. I am not savvy enough to know if this file is the bootloader or the kernel, but this process should get you back to stock-enough to do the wire trick.
Sent from my SGH-T699 using xda app-developers app
It's the kernel.....the boot.img file, I mean. The bootloader is that mostly white screen you see with "Hboot" at the top that will have "S-On" or "S-Off" after the word Radio. Good response.:good:
ArachnydZ28 said:
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".
Click to expand...
Click to collapse
Load the pd15img.zip on your sd card and boot to your bootloader. It should detect the file on your card and ask if you want to flash it. Just follow the directiins it gives you
Edit: actually should be pd59img not 15
Sent from my SGH-T889 using Tapatalk 2
Followed the steps in Hassoon's toolkit, installed recovery, sideloaded CM, and now I have no OS. I can still access fastboot and recovery, see attached image for more info. Any more information needed, please let me know. This is pretty frustrating, no wonder I like Nexus devices.
(sorry for double posting, I also put this in Hassoon's thread, but felt it'd be more appropriate to post here)
first man... you'll only be able to use sense roms most likely, as the newer aosp roms dont mix with the upgraded touchscreen on the 3.18 firmware. so you can head to the original dev section to find the "downgrade touchscreen" thread to use aosp...
second, you have to fastboot flash the boot.img of every rom because the newer hboots dont allow it. easy solution to that is to go to original dev section and follow the s-off thread. if you can s-off you can say bye bye to fastboot for the most part
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
exad said:
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
Click to expand...
Click to collapse
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Dolfan058 said:
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Click to expand...
Click to collapse
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
InflatedTitan said:
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
I feel bad, I see all these people having trouble getting s-off to work, and I did it today without any hassles at all.
Sent from my Evita using XDA Premium
exad said:
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Click to expand...
Click to collapse
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Dolfan058 said:
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Click to expand...
Click to collapse
if a simulated battery pull isnt working for you, you can paste your cmd prompt window in here and i can check if anything weird is going on.
usually it should work by the third try or so if not after the first simulated battery pull.