Related
Hi guys,
I've searched the forums and I can't find a solution for a problem I'm having. I have successfully rooted and played around with different flavors of Hero ROM's and optimized kernels. But, I would like to revert back to the original Vodafone UK ROM (I have a nandroid backup of it, done right after rooting the device). I have restored the ROM but for some reason, OTA updates never install. The ROM I have backup'ed is CRB17 and I know the latest is CRC1. Using the System updates menu in Android, I download the update, but it doesn't install, it says that I need to reboot, which I do and nothing happens.
How can I get the original unrooted: HBOOT-1.33.0004 (SAPP10000) : Sapphire PVT 32B SHIP S-ON G : CPLD-10 (Voldafone NL + UK + Australia)? I have a friend that hasn't rooted his Magic, how can I get his SPL?
So far, what I've done:
- installed Engineering SPL HBOOT-1.33.2004 Signed update.zip and restored the original recovery for Sapphire that Haykuro has around (when I nandroided my original ROM, I had already put in the Cyanogen's recovery tool...) - OTA doesn't work.
- installed Modded HBOOT-1.33.2004 by Crios Signed update.zip and restored the original recovery for Sapphire that Haykuro has around - OTA doesn't work.
Another thing I noticed is that although people say that with Crios SPL, I should be able to do the OTA updates, I can't!
Also, the SPL description says "Sapphire PVT 32B SHIP S-OFF H : CPLD-10", and my original description should be "Sapphire PVT 32B SHIP S-ON G : CPLD-10".
Has anyone been able to make OTA updates working again?
Thanks for your help in this matter, I feel like I've tested everything :\
-------------------------------
EDIT:
OK guys, just got my OTA updates back. You should thank RubenFreitas for the dump of his "virgin" HTC Magic Vodafone UK. This is a 32B device, unrooted, which means you can do OTA's again.
How to restore your device to OTA abilities:
- first you need to put Crios SPL (2004/2005) with S-OFF on your device. (look for instructions on the forum, search for "magic hboot spl").
- fastboot into Amon_RA recovery tool. (fastboot boot recovery.img)
- make a backup of your current rom (don't worry, this is just for getting the file structure into the sdcard).
- After it finishes, reboot your device and mount your sdcard.
- In your sdcard, you'll find a "nandroid" folder, open it, until you see boot.img, etc.
- replace the files with the ones on the file here: www.dymsoft.com/rubenfreitas_Vodafone_UK_ORIGINAL.zip
- fastboot again into Amon_RA recovery tool
- recover your backup (which will now be the original ROM from vodafone).
- reboot and enjoy your OTA again
If for any reason, nandroid restoring doesn't work (your phone does not boot after 15 minutes), you can restore the backup manually in fastboot mode:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
I have exactly the same question!
Just 1 question, why do you desperately want OTA updates?
I mean anything we get on here is likely to be one step ahead of any update our carriers give us, even if we do miss out on something good when it's sent out someone will pick it up on here pretty quickly and pull it apart to make sure we dont miss out.
Just my thoughts, I really wouldn't worry.
It's just the idea that I can't get my device working for 100% again that makes me crazy
Going back to the standard rom is hardly working 100% ..
xyzulu said:
Going back to the standard rom is hardly working 100% ..
Click to expand...
Click to collapse
Smartass ... but still nothing on how to fix this?
Roy_Drage said:
Just 1 question, why do you desperately want OTA updates?
I mean anything we get on here is likely to be one step ahead of any update our carriers give us, even if we do miss out on something good when it's sent out someone will pick it up on here pretty quickly and pull it apart to make sure we dont miss out.
Just my thoughts, I really wouldn't worry.
Click to expand...
Click to collapse
The only reason I want OTA working again is for getting "Donut" update automatically when it comes out, rather than having to wait for it to be available here.
From what I can gather, we can only have OTA if the Magic is unrooted, am I right? According to Crios posts, I should be able to do the OTA updates, but his SPL is for HTC devices, and I have a Google one, although it works fine on my Google. Just the OTA doesn't work.
Anyone knows how to dump the original SPL from an HTC Magic that hasn't been rooted?
dferreira said:
The only reason I want OTA working again is for getting "Donut" update automatically when it comes out, rather than having to wait for it to be available here.
Click to expand...
Click to collapse
I'm sure once it's out it won't be long before it's available on here. Wouldn't surprise me if it was posted here the same day.
Malky1903 said:
I'm sure once it's out it won't be long before it's available on here. Wouldn't surprise me if it was posted here the same day.
Click to expand...
Click to collapse
Wouldn't suprise me if we had it here before!!
I mean they already have the code for most of it anyways. From what I've seen and tried of donut it doesn't even look that great! Possible mulit-touch, well they will mange to pull that out and stick it in a cyanogen rom or something, and a widget for the home screen allowing you to toggle things like wifi etc....
You can get those anywhere off the market, check the widgets on jerpeleas cyanogen rom page. They are really nice.
Read this, doesn't even sound like Donut is going to be version 2.0 of android, more like 1.7 or something:
http://www.engadget.com/2009/07/26/android-team-member-says-donut-isnt-2-0-doesnt-have-multitouc/
To me that really doesn't matter! I just want the possibility to restore my Magic to factory settings with OTA updates!
same question here. Snappiness of the vodafone original rom is the best so far. Have tried all different roms. Problem is, there is an update available i can download it but it wont install.
Still no-one who can fix this? Come on, please... I'm sure you genius' can help us out!
i think i shall be ok haven't peremantly flashed anything no spl updates back to stock vodafone uk rom. only thing i did install was a few hero builds so hopfully ive done no damage to my phone
Imho un-rooting the phone should do the trick, but how can that be done? There are a couple of manuals for the Dream, but they ain't working for the Sapphire.
Can someone please upload the original SPL from Vodafone (NL/UK/AUS)? I'm pretty sure that if we can put that one back on our Magic's, we have our OTA Updates back!
It would be appreciated very much!
Tomorrow I have a friend that has a "virgin" HTC Magic from Vodafone UK I'll try to get his "virgin" SPL and boot and everything.
I found out how we can dump it all into .img files (what nandroid uses). Hopefully, it should get us back OTA updates!
http://forum.xda-developers.com/showthread.php?p=4035680#post4035680
That would be awesome! Great!
Hi DFerreira.... did you manage to get the original SPL?
Not yet... my friend couldn't come to my place. I'll try to catch up with him tomorrow.
I also have an untouched magic here (dutch one from my gf). I just dont know what to do
---
hyeprofile requested i link to his rooting for dummies guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
---
edit: almost forgot to include the gr33tz! D:
this hack brought to you by dream_kill, and myself.
---
edit: for those of you that don't know how to get to SPL 1.33.2005 i recommend reading here: http://forum.xda-developers.com/showthread.php?t=532224 (under Rooting Rogers).
---
(note: this is for the dream, the method works for the magic you just need to flash a magic compatible recovery.img)
This requires that you use SPL 1.33.2005. (this is safe on all rogers dream devices.)
so if you don't have that already, go get it here.
once you are at SPL 1.33.2005 (AND ONLY THEN)
download this
(md5: 4a58a5702fdf899547011888d9cc066f .. sha1: 99e38e4f8798e952e67421a42e7b053ea70957b7)
extract both images wherever you'd like.
IMPORTANT: make sure you have the rom you'd like to install in the root of your sd card as update.zip (YOU WILL NOT HAVE A ROM INSTALLED AFTER YOU COMPLETE THE FOLLOWING STEPS, YOU WILL HAVE TO USE THE UPDATE.ZIP TO GET ONE)
boot into spl and fastboot (power off, hold camera button, power on, press the back arrow to get into "fastboot" mode)
type in the following:
Code:
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
POWER OFF (not reboot, power it off) THE DEVICE. (you can do this using the corresponding button [it says it on the screen] or just pull the battery [make sure everything is done flashing of course])
(if you don't boot into recovery or accidentally rebooted, just pull the battery [if you notice top left it should read "FASTBOOT" or "FASTBOOT USB" if it's plugged in] you're not bricked, you just need to access recovery, not standard boot ;P)
now hold down the HOME button and power it on, you should boot into recovery mode now, go ahead and ALT+S to flash your rom, and enjoy! now you can flash anything you see in the forums
EDIT:
So i noticed people were talking about reverting back (not sure why you'd want to )
Regardless, heres the original radio (3.22.20.17) and the original recovery (WARNING: UNROOTED) from rogers dream:
http://www.stevebirstok.com/android/losemyroot.zip
Code:
fastboot flash radio rogersradio.img
fastboot flash recovery rogersrecovery.img
fastboot erase system -w
and flash the update.zip found somewhere on this forum ;P
EDIT 2:
as far as this ram / memory loss goes:
C:\Users\haykuro\Desktop>sha1sum radiog1.img radioion.img
14163559b04ba8c9daead5e34465ebf5bafa7bd1 *radiog1.img
14163559b04ba8c9daead5e34465ebf5bafa7bd1 *radioion.img
radiog1.img is the radio.img i provide in the givemeroot.zip, radioion.img is straight off here there are no specific radios between 32A and 32B boards, so that isn't why you're losing memory. i'm trying to figure it out, so if anyones willing to do some testing and post results, please do so.
nice! a whole new crop of modders inbound
cheers
Trying this right away .. no words ... thanks again H !!
EDIT: well not RIGHT away ... need a rom lol
newbie question................Will this fix the iptables issue to allow for tethering?
Thanks alot, this is awesome, Will I be able to flash 32b roms onto my 32a rogers magic? Anything goes??
RezaREX said:
newbie question................Will this fix the iptables issue to allow for tethering?
Click to expand...
Click to collapse
I believe the ROM image contains everything including kernel. So if the kernel in the ROM is IPtables enabled ... you bet
Awesome job Hay!
Now... What is that radio and where does it come from? Will I still be able to get HDSPA on Rogers Bands with this?
Thanks haykuro.
Anything is good as long as it expands the android community on XDA.
Let's go Roger developers!
and I sold mine for a us g1 haha!"now I feel like an idiot" good Job Haykuro!
what else you releasing today"I now you have something special sitting on your desktop"
Drizzy Drake Rogers said:
and I sold mine for a us g1 haha!"now I feel like an idiot" good Job Haykuro!
what else you releasing today"I now you have something special sitting on your desktop"
Click to expand...
Click to collapse
Oooh I love a good mystery.....
Sounds pretty exciting for our fellow rogers dream owners. Haykuro, have you thought about rooting myTouch yet? Or will this work on myTouch as well?
Now that us lowly Rogers Dream owners are able to flash ROMs, does anyone have any suggestions for a good ROM to flash? I'm thinking something Hero ...
RezaREX said:
newbie question................Will this fix the iptables issue to allow for tethering?
Click to expand...
Click to collapse
yes.
rajeevsudra said:
Thanks alot, this is awesome, Will I be able to flash 32b roms onto my 32a rogers magic? Anything goes??
Click to expand...
Click to collapse
yes.
hellfenix said:
Awesome job Hay!
Now... What is that radio and where does it come from? Will I still be able to get HDSPA on Rogers Bands with this?
Click to expand...
Click to collapse
the radio is 2.22.19.26I (comes with all the new g1 roms, came with the ION, and with some other devices.) and it should have 0 effect on HSDPA or bands (that's at a hardware level and has to do with the crystals on your phone )
jackkerouac said:
Now that us lowly Rogers Dream owners are able to flash ROMs, does anyone have any suggestions for a good ROM to flash? I'm thinking something Hero ...
Click to expand...
Click to collapse
Hero for eye candy, cyan for performance, cyan with hero theme for a good mix of both
I forgot to say thank you! So, THANK YOU!
Success
First of all, Haykuro, thank you for all your work (and those that helped you), this is excellent!
I have just completed all the necessary steps from H's first post. Worked like a breeze, I am up and running now. If only I knew we would get access to new ROMS this early, I would have started downloading them a few days ago.
Haven't had time to test everything yet, I randomly downloaded JackHeroV1.0, and it loaded no problem.
Good luck to all on Rogers, this should bring some new life to our phones now.
Great stuff indeed! Has anyone tried this on a 32a magic ?
Thanks for the awesome work haykuro and dream_kill. I can't wait to try this out tonight.
This is awesome, you guys rock! I can't wait until I get home to flash some cyongen-y goodness on my Dream
This is unbelievable haykuro.
Not only did you give us the ability to do custom ROMs ... they don't need to have special mods.
I always expected that every time a new ROM came out we would need someone to do some kernel hacks to make it Rogers compatible.
Great job.
I flashed the 2.1 RUU that was floating around a couple weeks ago. Well now, I can not get any PC to recognize my Hero. I cant mount or use ADB and I'm stuck with this BS 2.1 RUU..Can anyone help PLEASE!!
I thought all the threads that had the 2.1 RUU said that we couldn't get root on it yet, and that it was really posted for devs only.
Your best bet right now is to find some way to conveniently "break" your phone and get a replacement.
http://forum.xda-developers.com/showthread.php?t=668905
I could be wrong, but I think that was for development only not ready for a phone.
HeroHTC said:
I could be wrong, but I think that was for development only not ready for a phone.
Click to expand...
Click to collapse
No, your right - some people have had a hard time reading all of the threds about what that does to you phone. Research pays dividens in the long run.
Key thing to remember: Don't flash a rom unless it has a funny name.
gbhil tweeted this a few weeks back as a way to restore after using the leaked 2.1 RUU... I think it'll help you out:
http://forum.androidcentral.com/htc...pair-your-bootloader-after-using-2-1-ruu.html
Key advice (as mentioned above): ALWAYS read the warnings before flashing something.
i would never RUU my hero after all of the issues that have been reported. best bet is to make a backup of your stock hero rom before flashing any custom one.
Kcarpenter said:
No, your right - some people have had a hard time reading all of the threds about what that does to you phone. Research pays dividens in the long run.
Key thing to remember: Don't flash a rom unless it has a funny name.
Click to expand...
Click to collapse
And don't use an RUU with the word "test" in it.
tf2d said:
I flashed the 2.1 RUU that was floating around a couple weeks ago. Well now, I can not get any PC to recognize my Hero. I cant mount or use ADB and I'm stuck with this BS 2.1 RUU..Can anyone help PLEASE!!
Click to expand...
Click to collapse
I too ran the RUU running around but was able to root my phone using the info in the links that "Is_907" and "Kcarpenter" provided. Now I'm running DamageControl v2.07.2 ROM on my Sprint HTC Hero.
Hope it helps you as much as it helped me.
Is_907 said:
gbhil tweeted this a few weeks back as a way to restore after using the leaked 2.1 RUU... I think it'll help you out:
http://forum.androidcentral.com/htc...pair-your-bootloader-after-using-2-1-ruu.html
Key advice (as mentioned above): ALWAYS read the warnings before flashing something.
Click to expand...
Click to collapse
I used that method about a week ago, work great in about 5 mins I was back to full root and flashing 2.1 roms again!
Using only an SD card this method will restore your old boot loader >> http://forum.xda-developers.com/showthread.php?t=657086
I ran the ruu for the new PRI version, but I was able to root it the same ol' way and have installed 10 different ROMs in the last two weeks.
Just recently I wanted to revert my PRI and boot loader to single out a problem I was having and used the above method. I was able to return my phone to complete stock without running any ruu as described in the link above.
Glad that link helped some people out...
Basically, if gbhil posts something, I trust it.
thanks a lot..to those who actually helped, I'm trying this out now..Ive flashed RUUs before and test ROMs for over a half a decade..
someone one this forum said the RUU came pre-rooted..
I'm no noob, check my join date before: before kcarpenters..lol no offense
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