Related
Ok, just like all of you I have rooted, experimented to the limits and pushed them well little did i Know is that you cant reflash the 1.56 ruu so needless to say I ended up with a brick but luckily for us it will still connect in fastboot
so this is a solution to at least get it up and running
Pros-
Reactivate your phone since it will be formated
All functions will work
can still root, install .apk's use wifi etc
camera etc
so the pros are it will operate just like nothing ever happened now to the con's
YOU WILL HAVE TO DO THIS EVERYTIME YOU TURN OFF YOUR DEVICE
Ok here is how to fix it
Connect your phone to your PC
open command and navigate to your android tools folder
type in
fastboot devices
make sure it detects your device
should show the HTC logo on your phone
now simply type
fastboot oem boot
wait a couple minutes while your phone reboots
viola you phone is back to running again...just dont turn it off LOL
can you launch the RUU again and (hopfully) have it restore your phone correctly?
You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet
rayborn said:
You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet
Click to expand...
Click to collapse
hmmmm interesting man. honestly you should be able to rebuild all the / partitions. such as /misc and /radio. we need some linux junkies in this thread to tell us how to rebuild failed / partitions
This is amazing. Sure did work for me. I just wish there was a way to get it flash the original radio. I have only had this thing two weeks and would love to take it back and exchange it, but I am just paranoid since it shows radio 2.41.04.02.03.
wait, what exactly did you do to get your near-bricked phone?
you used the 1.56 RUU on your phone that had a 2.xxxxxx radio?
have you tried both of the RUU's? the original and 1.56?
My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution
did you try the 1.29 RUU?
yeah i tried every sprint hero ruu i promise you i left no stone unturned trying to fix this
BRILLIANT!
I can't tell you how impressed I am that somebody has found what i now consider to be the first step towards getting the RUU 110 error solved.
I still feel that the issue comes down to the lack of ADB that seems to happen once you get 110... maybe a driver issue on the phone vs. driver issue on the computer? after all the RUU starts failing on all the ADB commands when you check out the RUU logs...
sorry i can't help take it from there, i returned my phone to sprint inside of the 30-day window and just told them something i installed form the market "bricked" my phone...
I eagerly await your results though for a final step towards solution, as I am dreading the day i have to RUU my phone for whatever reason that may be, although I've been running a personally customized Pancake ROM for almost a week and totally happy with it so won't be doing anything until 2.1 is official...
R
rayborn said:
My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution
Click to expand...
Click to collapse
Same exact thing for myself. Multiple people said the way to go back to the stock radio was to use the RUU. I tried both RUU's and same results. Now I am just trying to decide what is better.
Live with this and hope for a better option to come or take back a "bricked" hero that shows Radio 2.41.04.02.03 and hope I don't end up getting charged later.
IMHO I think the best thing for you guys to do is wait for our 2.1 update, which will more than likely have a smiliar radio update. Then you can just say the update bricked the phone.
If we get the same radio version, then just take it back, if we get a different version then maybe we can find a file to edit the number to make it say what ever version you want it to say, something like editing Build.prop. Then Sprint has nothing to ask questions about. Should be out in a few weeks if the rumors are right. Maybe you can deal with this soultion until then.
As far as the don't turn your phone off issue, mines been up for 13 days. I hate turning it off, partially because of the missed emails and partially because I worry that it won't come back up.
Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?
SamXp said:
Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?
Click to expand...
Click to collapse
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?
mginther said:
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?
Click to expand...
Click to collapse
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen
tatonka_hero said:
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen
Click to expand...
Click to collapse
True, and if we elect to continue to use either a Fresh or Damageless version of an official 2.1 Sprint ROM, then we should be ok. But if we wanted to go to the Sprint ROM, there are going to be a lot of bricked phones if there isn't a way to understand what is going on when a 1.56 RUU is used over a phone with the 2.x Radio update.
Just wanted to pass along some more information in case anyone else is having this problem. I had reactivated an old phone temporarily since this one was bricked. This morning I reactivated my hero due to this semi fix and immediately I could call and textimg was fine, but i kept getting vision error 67 for data. Sprint reset my data about three times and it never worked. I tried updating my profile multiple times and it never worked. Finally I Ran the RUU again and sure enough after a reboot or an "oem boot" I had error 67again. I went ahead and updated my profile and this time it worked and data started working. Still hoping someing else comes along though.
well I think the issue here might be that it does not have the recovery backup on it after you do an RUU. I could be wrong but who knows? I would say install flashrec-1.1.3-20091107-2.apk on your phone once you are able to get it up and running then flash the recovery backup and restart. That could possibly fix the issue? I have the files if anyone needs them, I'm not sure how to upload them on here...
~Danny
I'm not sure if it's possible boot into recovery console using this method, but if you can, has anyone tried manually flashing the old radio in the same manner they flashed the new one to revert back and then RUU. Perhaps that may do the trick.
My phone isn't bricked so I can't try it out, but seems like it might be worth a shot in theory.
http://forum.androidspin.com/showthread.php?t=2757
The link above is for instructions claimed to work with all HTC 2.1 Android handsets. I've been trying to get this to work on my Hero but I keep getting stuck at step 7 with my phone offline and unplugg/replug USB does not change it from offline to recovery. Anyone else have luck with this?
why not use unrevoked or the the how to here
Won't work for me. I'm not using Sprint and my build number is newer than Sprints so I can't flash it.
navalynt said:
Won't work for me. I'm not using Sprint and my build number is newer than Sprints so I can't flash it.
Click to expand...
Click to collapse
bummer.. well i would ask the op of the root method on that other forum. i haven't got a clue about that root method.
Check out Droiddog.com site, they've posted a video (actually a two parter) on this rooting method... It is not easy.
I'm pretty sure you can just flash the RUU that has test-keys, and then root that.
Use Regaw's
Like mrinehart93 said, just downgrade to the RUU ending in .5, then follow these instructions.
forum.xda-developers.com/showthread.php?t=694572
If you follow them exactly you will end up with rooted stock 2.1 with that same RUU. I actually just rooted for the first time except loaded this ROM, which is stock using the updated RUU.
forum.xda-developers.com/showthread.php?t=703267
Good luck.
dosnt look easy though !!
I appreciate the responses so far but you all still don't understand. I'm not a Sprint customer, and my current software version is 2.36.556.1. I CAN'T downgrade to one of Sprint's RUUs (already tried just for kicks).
sent from divested Alltel hero help Root
Does this work for Alltel gonna give it a look now
allus_drummer said:
sent from divested Alltel hero help Root
Does this work for Alltel gonna give it a look now
Click to expand...
Click to collapse
just tried, step 7 adb devices and nothing i dont get any kind of recovery menu. only the initial white screen recovery, no offline device menu
I'm thinking that the problem is Windows not executing the adb devices command fast enough. I'll have to try this again later booted into OS X or Ubuntu.
UPDATE: With all of the newer rooting and S-Off methods, and new hardware and firmware revisions, this thread may or may not help with your specific case if trying to unroot and go back to unrooted stock. I originally wrote this based of of the very first root methods known for the Launch EVO. There is a good chance that this method will still work, but there could definitely be something unaccounted for in your own specific case, so tread with caution. It is very doubtful that anything in this tutorial will result in your EVO becoming a fancy-schmancy paperweight, but if something goes afoul, you could have a nice headache to deal with...
Ok guys. There is a lot of partial and mis-information floating around out there about how to UN ROOT if you have to send your phone back for replacement, or you want the official unrooted OTA 2.2.
OLD NEWS!!!---> NEWER METHODS AVAILABLE TO ACTUALLY FIX PRI DOWNGRADE> SEARCH!!!! EDIT your PRI to show 1.40, thanks to sturmen for the pointer, and Calkulin for the method: http://forum.xda-developers.com/showpost.php?p=7267559&postcount=66
This assumes you are full root, S-Off. Note, this is not tested with simple root but should work (EDIT, Simple Root is basically Toastcfh's method, so you simple root users should be set), only with Toastchf's root method and nand unlock.
After reading every thread on the forum here, I think I finally found a fool proof way to do it. All the info was out there, but in several places and each one was missing something.
1) Before you start clicking and flashing and running RUUs, Check your HBoot build. You need to have the 0.76.2000 from Toastcfh's method #2. If you have 0.79.0000 (whatever) go to step 2 below. If you're getting Bootloader errors when running an RUU, I can almost guarantee that you don't have the correct HBOOT. If you somehow still have 0.76.2000 from previous modding, proceed to step 3.
2) Toast's Nand Unlock method. Found here: http://forum.xda-developers.com/showthread.php?t=701835
EDIT: The more I think about it, I think you can just run Simple Root to re-attain the .76 HBOOT and engineering build. It would eliminate the need for any adb, and SHOULD produce the same results. Just run the RUU after you run and complete simple root. See notes in BLUE below too!
THIS STEP IS 100% NECESSARY IF YOU HAVE THE .79 HBOOT version!!!...Do step #2 in Toast's thread, just like you did when you originally unlocked NAND (OR YOU SHOULD BE ABLE TO JUST RUN SIMPLE ROOT AGAIN...UNconfirmed, but should work methinks...). Not 100% sure which steps are necessary, but I do know you need to do steps #1 (Well, #1 is Nandroid Backup, so proceed at own risk if you skip) and #2 again. Make sure after you flash the Flash_Image, and the mtd-eng through adb, that you then load the PC36IMG.zip (Engineering Build), onto the root of your SD card, and boot into HBOOT, and let it install (just like you did when rooting). I didn't bother to flash the Recovery image at the end of step 3, but I don't think it would hurt if you're nervous about losing a custom recovery image in case this method for some reason does not work. It has come to my attention that flashing the engineering build (the PC36IMG from Toast's thread)through fastboot, might be as crucial as simply having the .76 HBOOT version. It at least is a surefire way to make sure you can run an RUU on top of it. There are probably other builds/roms that will work and allow you to run the RUU, but this one is confirmed, so don't skip that step!
3) If you have the 0.76.2000 HBOOT (can be checked by powering down, and booting by holding VOL down and Power), then you can go ahead and boot into the rom, and proceed with downloading the RUUs found here: http://shipped-roms.com/shipped/Supersonic/
Go ahead and download the first one (at least). I think the others are optional to "upgrade" but why should we care. We just want to go back to unrooted stock.
4) Make sure you have the latest version of HTC Sync installed, found here: http://www.htc.com/uk/SupportViewNews.aspx?dl_id=933&news_id=627
Install, and let it do it's thing. Will probably have to restart your PC when complete. Not even 100% sure this is necessary, but it won't hurt. It's basically for the HTC drivers from what I understand.
5) Run the RUU from your pc while your evo is in the phone loaded state of the Rom, (not the bootloader) with the phone connected through USB and have HTC sync selected. Even if it doesn't connect to HTC sync on your PC, you should be ok.
If you get a USB error after the screen goes black with the HTC LOGO, don't touch the phone. Exit the RUU via the EXIT button when given the option.
6) Run the RUU again and see what happens. The Error could happen 1 more time, but just exit again, and run RUU one last time.
7) Thank everyone here at XDA that our EVOs are so badass...I'm certinly not a dev, but these devs work hard for us to have the baddest ass phone there is right now.
Any problems, let me know. I assume your errors are the same ones I was getting, and it's all because of the wrong HBOOT.
I really take no credit for this, as I'm just compiling information in a tut....
Thanks op.
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
arozer said:
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
Click to expand...
Click to collapse
You might be correct, but I couldn't get the FROYO OTA to show up in any of the roms I was using.
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
sturmen said:
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
Click to expand...
Click to collapse
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
EDIT: Yess! See below and in OP!
Bang3r said:
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
Click to expand...
Click to collapse
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
sturmen said:
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
Click to expand...
Click to collapse
That would be cool, but I'm not too worried about that part. Phone is going back tomorrow!
Well, worry even less! Special thanks to Calkulin!
thankssssss
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
I'm getting error 155 running Ava Froyo and trying to go back.
blix1337 said:
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
Click to expand...
Click to collapse
Yes, you are correct, but so am I. This is exactly what step 2 in the OP does (which is a link to Toastcfh's thread about the engineering build).
tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
Ok. RE-read the OP. Everything is there. Check your HBOOT version by booting to the bootloader. If you have .79, you need to re-flash the engineering build before the RUU will work (Step 2 in the OP to get HBOOT to .76). You cannot run the RUU on top of AVA froyo or any froyo, or any rooted custom 2.1 for that matter if you don't have the proper HBOOT (Which I believe you cannot have if you are running any custom rom). Flash to the engineering build, then the RUU.
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
joypunk said:
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
Click to expand...
Click to collapse
Yes you can still REroot VIA those methods. As long as you don't do a FROYO OTA or manually flash the UNROOTED Froyo...there is no ROOT method for FROYO yet.
It returns completely to UNROOTED stock, except for the PRI, which there is a fix for on the 1st page.
And incidentally (and I just figured this out last night) Simple Root is Toast's method, just automated...
EDIT: I think that you could even UNROOT and RUU to 1.3x (whatever it is), then use the ROOTING methods that were in place before the official 1.47 OTA rooting methods. But, I just did simpleroot last night on top of 1.47, and it is freaking SIMPLE....1 click for root...1 click to flash recovery.
tpdtopcop said:
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
Click to expand...
Click to collapse
This is what were trying to show you on Androidcentral as well. Glad you are set!
tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
As long as you have .76 HBOOT flash back to an earlier rom...one that has a 1.32 base. Then use the 1.32 RUU or 1.47 RUU. You should be set. Make sure you have completed step 2 in OP.
Yes. I have .79, thanks!
Sent from my PC36100 using XDA App
Okay, here goes the story-
1.Got an Inspire
2.Did the Hack Kit and then installed the Rooted Stock ROM (Discontinued), everything went okay but when trying to reboot into CWM, I got the HTC Screen for a few seconds then blackness, I later determined it was working I just couldn't see it for whatever reason.
3.Okay, I thought I'd try Bubby's One Click and see if that would fix it, it went great too, but CWM still no workie, getting frustated now.
4.I thought I'd try flashing a non-AT&T ROM, since so many have been having issue running one and getting the working, but black screened CWM, I chose CoreDroid's.
5.I put CoreDroid's ZIP on my SD Card, went into ROM Manager and installed it, making sure clear memory and backup current ROM were checked.
6.It rebooted into CWM, which of course I couldn't see, then about 10 minutes later it rebooted, and the beautiful CoreDroid Animation came up, and a few minutes after that I had CoreDroid up and running.
7.Well, I thought, CWM should work fine now, EHHHHH Sorry Johnny (which sounded weird, since my name is Mike ), wrong answer, I rebooted into CWM and there it was again, total blackness.
8.Okay, I noticed in CoreDroid that to be able to flash new Radio's, you had to have Eng S-OFF, so I ran the One Click Eng S-Off Tool found here http://forum.xda-developers.com/showthread.php?t=855403 , making sure to check the box saying I already have S-Off.
9.It ran, and said it was successful, and I now had Eng S-Off, so I rebooted into Hboot to check, and at the top sure enough, it said Eng S-Off, I then hit PowerDown, which it did, but then....well, go to 10
10.It rebooted into...yep, CWM! Clear and beautiful, it looked wonderful! So booted back up, went into ROM Manager and told it to boot into CWM, it did so and it came up again, no problems! I did it again to make sure it wasn't a fluke, nope, all was well now in CWM Land!
So, how's that for a saga? Ahh, now I can kick back, it's Miller Time, or Dr.Pepper Time in my world, I don't drink
Use this at YOUR OWN RISK! I take no responsibility for bricked or ruined phones, I just posted this in hopes it might help out people having CWM issues. DO NOT send me hate mail because this didn't work for you
Good job bro!! I don't personally have the problem, but I've been following tons who have. Well done!
i did step 8 throu 10 and it works great thanks a mill!
No prob, I'm glad I could help you guys out!
congrads!!! i'm gonna try it out, i really wanna try some of these awesome roms available
Thanks Epic, let me know how it goes for you! I can't figure out what it did, other than maybe some files were corrupted or missing, and doing the Eng S-Off pushed and refreshed whatever was corruped or missing, either way I am glad to have it working again
Very nice discovery, I will in cooperate this into the next version of my program. Thanks a ton.
bubby323 said:
Very nice discovery, I will in cooperate this into the next version of my program. Thanks a ton.
Click to expand...
Click to collapse
No Prob Bubby, I'm glad I could help and give something back! I am in full support of you by the way, I think it's pretty slimy how they ganged up on you like that, when all you did was try and make things easier for the community. If I can help out in any way, let me know!
californiarailroader said:
No Prob Bubby, I'm glad I could help and give something back! I am in full support of you by the way, I think it's pretty slimy how they ganged up on you like that, when all you did was try and make things easier for the community. If I can help out in any way, let me know!
Click to expand...
Click to collapse
Will do.
I believe (if I'm not mistaken) that ENG S-OFF is the Engineering bootloader... it's not the best way to S-Off, because it puts the Engineer's Test HBOOT onto your phone, which causes some problems for other things. Also, to get back to complete stock, you'll now need to flash a stock HBOOT as well, if I remember correctly.
For that very reason, I would *NOT* incorporate this into your one-click, bubby... it worked for me perfectly the way it is, WITHOUT an Engineering HBOOT. I'd leave this as a possible solution for the ones that actually have the problem.
ClearD said:
I believe (if I'm not mistaken) that ENG S-OFF is the Engineering bootloader... it's not the best way to S-Off, because it puts the Engineer's Test HBOOT onto your phone, which causes some problems for other things. Also, to get back to complete stock, you'll now need to flash a stock HBOOT as well, if I remember correctly.
Click to expand...
Click to collapse
I haven't had any issues yet, so hopefully I'm good I wouldn't have even ran it except for the fact that to flash other radios, you need to have it on there. I don't mind doing whatever I have to do to go back to Stock, which I don't plan on doing unless I have to send it in for warranty or insurance.
That said, I just posted it so that it might be of help to others, so I guess try it if you are having problems with CWM showing up properly, otherwise leave it alone
californiarailroader said:
I haven't had any issues yet, so hopefully I'm good I wouldn't have even ran it except for the fact that to flash other radios, you need to have it on there. I don't mind doing whatever I have to do to go back to Stock, which I don't plan on doing unless I have to send it in for warranty or insurance.
Click to expand...
Click to collapse
No doubt. I hope I never have to, either... I just remember that with an engineer hboot on the desire, it was a LOT harder to get it back to stock, and had several other issues, and that's why they did away with it in favor of non-ENG HBOOT options. I like how it opens up the phone, though. This is indeed a great find that it works with ours!
EDIT: Ahh, I found it. It's in the G2 Wiki here.
"INSTALLING ENGINEERING HBOOT (DZ/G2/DHD) - OPTIONAL and UNNECESSARY!
Assuming you've backed up your phone with Clockwork's nandroid, you can install the engineering HBOOT (bootloader), which among other things allows you to use fastboot flash (or flashing-over-usb from your computer). This is unnecessary for most users but provides additional functionality for developers.
This is totally optional and dangerous - if the write to the phone partition fails the phone will be bricked. At the moment there is no cure for a phone that has been bricked by a failed hboot install."
That very last line is why Bubby should NOT include this in his one click... you think problems are bad now, wait till someone bricks a device and we can't unbrick it! D:
ClearD said:
No doubt. I hope I never have to, either... I just remember that with an engineer hboot on the desire, it was a LOT harder to get it back to stock, and had several other issues, and that's why they did away with it in favor of non-ENG HBOOT options. I like how it opens up the phone, though. This is indeed a great find that it works with ours!
EDIT: Ahh, I found it. It's in the G2 Wiki here.
"INSTALLING ENGINEERING HBOOT (DZ/G2/DHD) - OPTIONAL and UNNECESSARY!
Assuming you've backed up your phone with Clockwork's nandroid, you can install the engineering HBOOT (bootloader), which among other things allows you to use fastboot flash (or flashing-over-usb from your computer). This is unnecessary for most users but provides additional functionality for developers.
This is totally optional and dangerous - if the write to the phone partition fails the phone will be bricked. At the moment there is no cure for a phone that has been bricked by a failed hboot install."
That very last line is why Bubby should NOT include this in his one click... you think problems are bad now, wait till someone bricks a device and we can't unbrick it! D:
Click to expand...
Click to collapse
Thanks for posting that. I was just going by what they said to do in the CoreDroid thread, and it worked for me, thankfully
"
FAQ:
Again, it's recommended that you flash radio 26.04.02.17_M2 (Orange ES 1.75.75.2 / HTC WWE 1.72.405.3) or radio_26.06.03.24_M2 (TELUS WWE 1.84.661.1) or Radio 26.05.05.27_M3 - (Orange UK 1.84.61.2)
How do I flash a new radio?
In order to flash other radios you need to have ENG S-OFF. Once your device has that read this thread to learn how to flash a radio.img
How to get ENG S-OFF:
Download the attached "easy S-OFF.zip" at the botton of this FAQ.
Extract to a folder of your choice.
Connect your phone to a computer (make sure you have USB Debugging enabled. Connect charge only!)
Open my "Desire HD easy s-off.exe", click "S-OFF it"! Allow possible SuperUser request on your phone.
There could be force closes after the process, just reboot and everything will be fine.
Done. (in bootloader it should now show ENG S-OFF)"
http://forum.xda-developers.com/showthread.php?t=965207
No doubt, still a great find. It's definitely a temp cwm fix, so use as necessary, just be careful and DO NOT unplug your phone while it's flashing!
ClearD said:
No doubt, still a great find. It's definitely a temp cwm fix, so use as necessary, just be careful and DO NOT unplug your phone while it's flashing!
Click to expand...
Click to collapse
For me, it was a permanent CWM fix
Use this at YOUR OWN RISK! I take no responsibility for bricked or ruined phones, I just posted this in hopes it might help out people having CWM issues.
I just put that in my first post, hopefully it will do it's job
I could get into cwm, no black-screen for me though. Still couldnt do radios. Used this and bam new radio....Thanks for the info.
Lol Cali, remind me to "thank" you tomorrow I've been trying all night, but I'm at the 24 hr limit for "thanks". I appreciate the post update, and this really is a great find. I can't stress that enough lol. In the right hands, an engineering HBOOT is great.
btdt13 said:
I could get into cwm, no black-screen for me though. Still couldnt do radios. Used this and bam new radio....Thanks for the info.
Click to expand...
Click to collapse
You are very welcome!
ClearD said:
Lol Cali, remind me to "thank" you tomorrow I've been trying all night, but I'm at the 24 hr limit for "thanks". I appreciate the post update, and this really is a great find. I can't stress that enough lol. In the right hands, an engineering HBOOT is great.
Click to expand...
Click to collapse
No problemo, as the Terminator would say
Well I decided to jump the hoop and go for rooting my mt4g slide. Was doing great and unlocked it using the lovely All-In-One tool kit and couldn't get the phone to show S-off. I figured I needed to get this done before installing a rom's as I tried 2 different ones and neither would work. Tried a few different things and still wouldn't work to get S-off. Long story short, now I'm in a boot loop where the phone automatically goes into the boot loader. It will start up and show the mytouch splash screen before going into the loader. It will scan the sdcard for files and say there isn't a image etc and go back to the main boot loader screen. I can't do anything beyond that. I hit recovery, factory reset, and nothing. Tried putting roms and see if it would out of the blue read one.
It's my fault for taking the risk but adding a bit of insult to my injury is my back up phone, G1, won't even turn on now. So now I'm kind of phone less. Any suggestions on how to restore hboot?
1st of all WRONG FORUM!!!!!! This is for Development, not questions. That's what general is for. Second, there's a couple threads in General about this. Just hit search.
Magical Mods, may we please have this moved. Thanks.
Sent from my MIUI V4
take out your sdcard and use an adapter to put a stock PG59IMG.zip on your sdcard (make sure its named PG59IMG.zip) and go back into the bootloader. It will confirm if you want to install the zip and in 10 mins you'll be back on stock. Oh and ^ plus one please next time post in general as this has nothing to do with developing.
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
fsured said:
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
Click to expand...
Click to collapse
Thread reported just for the use of "take a chill pill."
blackknightavalon said:
Thread reported just for the use of "take a chill pill."
Click to expand...
Click to collapse
Yes, the correct terminology is 'Take a chill pill, Bill.
Can't get chill without the Bill.
fsured said:
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
Click to expand...
Click to collapse
Sorry I wasn't "helpful". I'll do better to assist you next time....or just ignore it
I can't help you and I expect you to get a satisfactory answer.
fsured said:
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
Click to expand...
Click to collapse
XMC, a Dev. He helped you, we where all noobs once. You should check out the "Welcome to XDA Video". Just follow the Rules. That's all, follow the rules.
Sent from my MIUI V4
To supplement what Agent said the appropriate section for this would be the General section.
Additionally the development area is where devs post new roms, tools and hacks. Users can add observations to these threads to further development.
Hastily spouted for your befuddlement
fsured said:
Well I decided to jump the hoop and go for rooting my mt4g slide. Was doing great and unlocked it using the lovely All-In-One tool kit and couldn't get the phone to show S-off. I figured I needed to get this done before installing a rom's as I tried 2 different ones and neither would work. Tried a few different things and still wouldn't work to get S-off. Long story short, now I'm in a boot loop where the phone automatically goes into the boot loader. It will start up and show the mytouch splash screen before going into the loader. It will scan the sdcard for files and say there isn't a image etc and go back to the main boot loader screen. I can't do anything beyond that. I hit recovery, factory reset, and nothing. Tried putting roms and see if it would out of the blue read one.
It's my fault for taking the risk but adding a bit of insult to my injury is my back up phone, G1, won't even turn on now. So now I'm kind of phone less. Any suggestions on how to restore hboot?
Click to expand...
Click to collapse
"tried a few different things" to get S-Off?
There are two ways of getting S-off. One is done with Revolution if your HBOOT is earlier than 1.45. The other is juopunutbear if your HBOOT is 1.45. Did you check your HBOOT version before "trying a few things"?
Did you read the instructions for the all-in-one toolkit? Or possibly just follow the steps in order in the program? It's specifically designed so you don't need s-off.
I'm assuming you must have flashed CWM recovery since you said you did a factory reset. Did you do Juopunutbear or revolution, or are you planning on leaving S-ON? If S-ON, Did you flash a kernel(boot.img) using the toolkit? If you can get into HBOOT and get into recovery, there's no reason you should need to revert to stock. However, if your plan is to continue doing steps before reading the instructions, you should probably revert to stock anyway before you really do brick your device.
This link will provide you everything you need to get your device running. Just follow the spteps from the beginning. If your bootloader is already unlocked from HTCDev, then start at the step directly after unlocking the bootloader.
http://forum.xda-developers.com/showthread.php?t=1532809
The toolkit worked well for me (even though it was my first attempt at anything), so I guess I'd echo that. It also matched with the step-by-step guides on stuff I found elsewhere in the forum. BUT there is a real difference in the method and order of things for the two hboots, hence KarriOn's questions.
However, having rooted and S-Offed, I then got a bit cocky and managed to end up in a not dissimilar position to you! Total panic, but I managed to get out by thinking through what I'd done, researching, and the cause and hence solution became clear. Took a night sleeping on it, and 2 hours.
what HBOOT?
Did you unlock the boot loader?
Did you get recovery on
Did you do a backup before going any further?
Sent from my myTouch_4G_Slide using xda premium
I followed the all in one tool for everything. I've finally been able to get into cwm recovery. For awhile it wouldn't and I gave up for the night. Came back yesterday morning to tinker with it more and it worked. I've tried flashing the superSu.zip file in cwm and after it reboots it still reads s-on. But either way I can't get the phone to do anything other than boot into the bootloader screen. I'm going to check out the link about 2 posts up and tinker with it after work. Thanks for the replies!
http://forum.xda-developers.com/showthread.php?t=1532809[/QUOTE]
Oh yeah, that is the tread I used and the tool. After getting unlocked from HTC I tried flashing a rom and it wouldn't work. Figured I needed to get s-off for roms also. That is where my error started.
fsured said:
http://forum.xda-developers.com/showthread.php?t=1532809
Oh yeah, that is the tread I used and the tool. After getting unlocked from HTC I tried flashing a rom and it wouldn't work. Figured I needed to get s-off for roms also. That is where my error started.
Click to expand...
Click to collapse
You don't need S-Off for ROMs to work. It sounds like you didn't flash a kernel after installing a ROM. The instructions on doing this are listed in the all-in one tool thread, the "flash ics roms with s-on" thread, and even on the all-in one tool interface itself.
fsured said:
I followed the all in one tool for everything. I've finally been able to get into cwm recovery. For awhile it wouldn't and I gave up for the night. Came back yesterday morning to tinker with it more and it worked. I've tried flashing the superSu.zip file in cwm and after it reboots it still reads s-on. But either way I can't get the phone to do anything other than boot into the bootloader screen. I'm going to check out the link about 2 posts up and tinker with it after work. Thanks for the replies!
Click to expand...
Click to collapse
Flashing SuperUser won't get you to S-Off. Hasoon2000 has two different toolkits. One that will guide you through the rooting process and the other on how to gain S-Off using the Juopunutbear method. Having S-Off isn't necessary to root but it will take a few extra steps to flash a different ROM with S-ON. I was too much of a chicken to try the S-Off method since there is some risk involved but several have reported that it worked successfully for them.