Related
Hi,
Rogers released new dream rom with a radio update.
We have 62.50S.20.17H_2.22.19.26I now
This new is:
62.52S.20.18U_3.22.20.17.
Anyone able to get it out so we can flash it on cyan latest mod rom?
Dont know exact radio version but go here for rom:
http://www.htc.com/ca/SupportDownload.aspx?p_id=269&cat=2&dl_id=654
Thanks again.
the whole dump is an nbh file that has to be flashed from the sd. Anybody know how to crack it open?
I bet it contains other fixes as well! The message on Twitter said that they fixed some bugs!
jubeh said:
the whole dump is an nbh file that has to be flashed from the sd. Anybody know how to crack it open?
Click to expand...
Click to collapse
I remember back when I had my Wizard, there was a tool to pick apart nbh images and reassemble them. But this was for Windows Mobile, a completely different platform. Perhaps the basic file formats are similar?
Use qmat. It can unpack nbhs.
Mmmm, new radio.......yummy.....I like new stuff.....wait if it is a new radio, will this be able to work for us, how to we know that this won't jeprodize us with the danger spl. I know I ain't gonna be the first to try this
gridlock32404 said:
Mmmm, new radio.......yummy.....I like new stuff.....wait if it is a new radio, will this be able to work for us, how to we know that this won't jeprodize us with the danger spl. I know I ain't gonna be the first to try this
Click to expand...
Click to collapse
my thoughts exactly...took enough balls to go for the danger SPL in the first place.
my current radio works fine, so I am not going to mess.
then again...never say never. thats what XDA is all about
Well we know the radio calls the spl and that the old radio was not able to call the hayruko spl which cause way too many paperweights so how will we know if this radio will also call it, we can assume that since it is an update would but the word assume means to make an ass out of you and me, so is there any way that this can be checked or tested numerous times before we possibly get another wave of bricks and without a cupcake over the air excuse to fall back on. Just my thoughts.
Never change a running system my father tells. Me all the time.. ;-)
Yeah but I like new stuff, I got so used to it feeling like christmas around with new stuff all the time that I got spoiled. I have had this radio and spl for 3 months now and I am bored off it. I demand something new that could cause some new widespread havoc, can't we get something that causes a self destruct if installed incorrectly, kinda jealous of those iphone 3gs users and their exploding batteries, I want something that explodes and catches fire. I demand a refund what am I paying you dev for, wait I don't pay you, nevermind forget this whole post
P.s. I am just playing
rogers is DREA210
we have mostly DREA100/110
i dont think we r able to flash it...
Hardware is identical.
So it should work OK.
Just give me radio Rom only and i will flash it asap.
drea110 here.
You can go back to default by flashing DREAIMG.nbh and then re-flash with this Rom and all will be OK.BUT YOU WILL LOOSE ROOT!
And that is why i didn't flash it yet
Am waiting for someone to give a proper radio Rom to flash.
There will always be a question about whether any new radio image (IPL) that ships will be compatible with a hacked SPL or other SPL not intended for the specific device. This new IPL could very well brick every device it is installed on when mixed with the deathSPL. I very strongly suggest that nobody tries this IPL unless they switch back to their STOCK SPL. Now that HTC has so kindly provided the kernel source needed to build custom kernels that will boot on a stock dream as provided to rogers, there is absolutely NO NEED to continue using the deathSPL phone killer.
Hey, does this nbh file carry the SPL? (it must, doesn't it?)
If it does, then you could maybe just install this and reroot.
Yes it contains spl and radio rom and os rom on it so it will put back everything on stock.
But you will loose root and as of now there is no way to root on 1.5 version.. yet.
if there is i would flash it.
Re-root leave radio and check spl version.
if newer than deathspl would leave it and flash cyanogen 4.0.4.
If not reflash haykuro new hacked spl back and then wipe and flash cyanogen 4.0.4.
And am back in bussiness with new radio and/or spl.
But rooting on 1.5 cupcake needed to do that so...
demetris_I said:
Yes it contains spl and radio rom and os rom on it so it will put back everything on stock.
But you will loose root and as of now there is no way to root on 1.5 version.. yet.
if there is i would flash it.
Re-root leave radio and check spl version.
if newer than deathspl would leave it and flash cyanogen 4.0.4.
If not reflash haykuro new hacked spl back and then wipe and flash cyanogen 4.0.4.
And am back in bussiness with new radio and/or spl.
But rooting on 1.5 cupcake needed to do that so...
Click to expand...
Click to collapse
Really REALLY WRONG!
As I rank your knowledge about SPLs,Radios and android itself with this post, you shouldn't flash this, except if you wouldn't cry and open up a thread "My G1 is dead" ;-)
maxisma said:
Really REALLY WRONG!
As I rank your knowledge about SPLs,Radios and android itself with this post, you shouldn't flash this, except if you wouldn't cry and open up a thread "My G1 is dead" ;-)
Click to expand...
Click to collapse
And you base that on what?
1.5 is rootable - look for "goldcard"
Second: This update has a different SPL - It's not an Engineering SPL.
It replaces your recovery.
And I think these Recovery and ROM wouldn't boot on a regular T-Mobile G1, because it has a different radio chip.
It's very risky to flash this, because it's from a different phone.
It's NOT the same hardware!
maxisma said:
1.5 is rootable - look for "goldcard"
Click to expand...
Click to collapse
I hope this is not a very stupid question, but why would you need a goldcard. Can't you just revert to RC29 and root you device the old and easy way?
maxisma said:
1.5 is rootable - look for "goldcard"
Second: This update has a different SPL - It's not an Engineering SPL.
It replaces your recovery.
And I think these Recovery and ROM wouldn't boot on a regular T-Mobile G1, because it has a different radio chip.
It's very risky to flash this, because it's from a different phone.
It's NOT the same hardware!
Click to expand...
Click to collapse
Of course i didn't expect it to be engineering spl, this rom are made of normal ppl to use not experiment so normal spl would be on it but maybe the same as g1 or newer.
rogers only modification was on UMTS 850 / 1900 bands the normal g1 only supports UMTS 1700 / 2100 but rogers g1 users did flash radio rom from g1 vanilla see hardspl or even haykuro's hacked spl and they work fine so why not the contrary?
After all they keep the same base versions:
We have 62.50S.20.17H_2.22.19.26I
They have 62.52S.20.18U_3.22.20.17.
If they had: 3.0008 i wouldn't bother smells from miles is not same radio hardware
But as you can see the code is identical to each other, only newer!
The hardware IS the same my friend only they dont have dvt only pvt motherboards and they all be flashed with latest haykuro's spl and radio!
If am wrong the os will load but i wont have cell reception but that is as far as it goes for a brick.
Am 99% this rom will do just fine on any pvt g1 phone out there.
As for goldcard, didnt know there is a way to root on 1.5 please enlighten me.
Is there anything to download to make this happen? ->link
if it is am more than 101% that this rom will go on my phone sweet.
After that i dont know what happens will i be able to flash haykuro spl back or i will have a brick? will it let me flash custom rom?
Over and out.
Hello...
I've been frantically googling and checking the forums, I have a mt3g 1.2 (3.5mm) that needs to be exchanged to t-mobile, I rooted following the stock fender w/ root method, and need to revert it back to the stock settings as shipped. So far, my search has turned up no resolve. I was hoping someone here could provide me with the proper sappimg.nbh to restore. I've got the one for the original MT3G, but it (as expected) damages touch-screen capabilities. Can someone please help?
As far as I know, it's not possible until T-Mobile releases an OTA update for either the Fender or MyTouch 3.5mm. That was explained in the rooting instructions here on XDA...
merlino211 said:
Hello...
I've been frantically googling and checking the forums, I have a mt3g 1.2 (3.5mm) that needs to be exchanged to t-mobile, I rooted following the stock fender w/ root method, and need to revert it back to the stock settings as shipped. So far, my search has turned up no resolve. I was hoping someone here could provide me with the proper sappimg.nbh to restore. I've got the one for the original MT3G, but it (as expected) damages touch-screen capabilities. Can someone please help?
Click to expand...
Click to collapse
If you use the stock rom http://www.theandroidkitchen.com/fileshare/MyTouch3g32A/?download=MT3G32AFender-1.0-fixed-signed.zip and then you should have touchscreen. It's only with custom roms that touchscreen does not work.
Couldn't you just flash the Mytouch splash image and turn in in like that?
It looks pretty stock after that.
shawn1224 said:
Couldn't you just flash the Mytouch splash image and turn in in like that?
It looks pretty stock after that.
Click to expand...
Click to collapse
... you got the splash image handy?
kbeezie said:
... you got the splash image handy?
Click to expand...
Click to collapse
you can find the stock mt3g splash screen if u search on here but not the fender one... i got the stock myt3g splash on my 1.2...
ceas909 said:
you can find the stock mt3g splash screen if u search on here but not the fender one... i got the stock myt3g splash on my 1.2...
Click to expand...
Click to collapse
That's what I'm saying though, no one seems to have the fender one. Far as the op's situation, might have tried flashing one of those "32A" roms, which obviously won't work at this point, probabbly best to just try the rom from my signature (the one linked as Rooted), which is basically the stock rom and touchscreen and all that should work.
kbeezie said:
That's what I'm saying though, no one seems to have the fender one. Far as the op's situation, might have tried flashing one of those "32A" roms, which obviously won't work at this point, probabbly best to just try the rom from my signature (the one linked as Rooted), which is basically the stock rom and touchscreen and all that should work.
Click to expand...
Click to collapse
yea he has a 1.2, so yea i think his best bet is to get the stock mt3g splash screen and the stock fender rom... the only problem is that between the fender and the 1.2 the build number is different..the 1.2 is 2.10.531.4 CL119339 release-keys where the fender is 2.10.531.3 CL111099 release-keys .... but a simple edit of the build prop could make it display the correct buid numbers in the about phone menu..
I've actually attempted to just replace the splash with the original mytouch splash. This can be achieved by applying a proper SPL that will allow it to be replaced... PROBLEM being that after repacing the SPL with the ones linked: theunlockr[.]com/2010/03/10/how-to-change-your-splash-screen/
Once this process is taken, the radio functions and all seems well, EXCEPT that now when I place calls, my speaker does nothing. Phones can receive the calls and hear me, but I hear nothing. the end result is to reflash the phone with the rooted rom, minus the mt3g splash... This part is where my frustration is kicking in as their guide claims this is specific for the fender/mt3g 1.2, but yet bricks the speaker somehow.
UPDATE!!
Click to expand...
Click to collapse
It appears that the guide on unlockr is wrong for this phone. I was successfully able to get the splash back on the phone by implementing the steps of adding the splash DURING the initial radio and recovery image restores, at which point the sappimg used is the engineering 2010. Once the splash was loaded at this point, I was able to continue with the install, install the rom, but a fresh install would *not* boot into the OS, just hung on a black screen after the animated "android" splash. Upon restoring a nandroid back-up, the phone booted to the OS in its formerly operational state, mt3g splash included.... I'm going to attempt a factory reset from the phones main options purely to see if it'll boot or hang on the black screen again.
Update 2.0
Click to expand...
Click to collapse
Methods were all successful, factory reset worked to bring the phone back to the android setup wizard WHILE retaining the splash screen with no blank screen as described earlier... Process was as followed:
Performing the unlockr guide; during the following steps:
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
the phone is currently running the SPL for the Engineering SPL 1.33.2010... I modified the above process to reflect
fastboot flash splash1 splash.nb
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Recovered from the rooted fender stock image, which then took me to a blank screen. Recovered from a nandroid back-up, which restored the phone to my state just prior to (re)flashing. After nandroid backup is restored and successfully making calls, factory reset was done and test calls were successfully made from the freshly reset version of fender/wroot stock.... A bit hackish and unorthodox, but it answered the question I was so valiantly struggling to find resolve to.
It appears the stock fender /w root reverts the hboot version to the non-engineering, which functions fine with the speaker.... Hope this helps someone else who was in the same boat as me.
merlino211 said:
I've actually attempted to just replace the splash with the original mytouch splash. This can be achieved by applying a proper SPL that will allow it to be replaced... PROBLEM being that after repacing the SPL with the ones linked: theunlockr[.]com/2010/03/10/how-to-change-your-splash-screen/
Once this process is taken, the radio functions and all seems well, EXCEPT that now when I place calls, my speaker does nothing. Phones can receive the calls and hear me, but I hear nothing. the end result is to reflash the phone with the rooted rom, minus the mt3g splash... This part is where my frustration is kicking in as their guide claims this is specific for the fender/mt3g 1.2, but yet bricks the speaker somehow.
It appears that the guide on unlockr is wrong for this phone. I was successfully able to get the splash back on the phone by implementing the steps of adding the splash DURING the initial radio and recovery image restores, at which point the sappimg used is the engineering 2010. Once the splash was loaded at this point, I was able to continue with the install, install the rom, but a fresh install would *not* boot into the OS, just hung on a black screen after the animated "android" splash. Upon restoring a nandroid back-up, the phone booted to the OS in its formerly operational state, mt3g splash included.... I'm going to attempt a factory reset from the phones main options purely to see if it'll boot or hang on the black screen again.
Methods were all successful, factory reset worked to bring the phone back to the android setup wizard WHILE retaining the splash screen with no blank screen as described earlier... Process was as followed:
Performing the unlockr guide; during the following steps:
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
the phone is currently running the SPL for the Engineering SPL 1.33.2010... I modified the above process to reflect
fastboot flash splash1 splash.nb
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Recovered from the rooted fender stock image, which then took me to a blank screen. Recovered from a nandroid back-up, which restored the phone to my state just prior to (re)flashing. After nandroid backup is restored and successfully making calls, factory reset was done and test calls were successfully made from the freshly reset version of fender/wroot stock.... A bit hackish and unorthodox, but it answered the question I was so valiantly struggling to find resolve to.
It appears the stock fender /w root reverts the hboot version to the non-engineering, which functions fine with the speaker.... Hope this helps someone else who was in the same boat as me.
Click to expand...
Click to collapse
Or you can just goto the thread in the link of my sig ("rooted"), you want to make sure when you're reading guides that they are for your specific phone, some people have bricked their fenders or 1.2 cuz they got the wrong radio/spl intended for the older MyTouch3G
I made sure to use the right guide on the unlockr, the problem came specifically from where they had the SLP change guide... Either way, problem is fixed now and it'll be in the hands of the t-mobile store tomorrow. If I ever doubtfully get a question about the root from them after it ships back, I'll play dumb and inquire if maybe someone else did it while it was waiting to ship
merlino211 said:
I made sure to use the right guide on the unlockr, the problem came specifically from where they had the SLP change guide... Either way, problem is fixed now and it'll be in the hands of the t-mobile store tomorrow. If I ever doubtfully get a question about the root from them after it ships back, I'll play dumb and inquire if maybe someone else did it while it was waiting to ship
Click to expand...
Click to collapse
i hope they dont catch the build number being different.. as i stated in eairler post the build nmbers in the about phone menu are different from the fender and the 1.2
ceas909 said:
i hope they dont catch the build number being different.. as i stated in eairler post the build nmbers in the about phone menu are different from the fender and the 1.2
Click to expand...
Click to collapse
In my experience most sales reps are completely ignorant of that kind of thing, changing the boot screen may be enough to make em go along with it. IF you're dealing directly with the company on the other hand that may be a different story.
It's being shipped back via the store under the 14 day buyers resource. I have had two of these so far, both have suffered from the screen oddly self-scrolling... Figure maybe a bad lot produced, as t-mobile tech support has not even heard of such a problem before. I finally settled on buying a nexus one, which arrives tomorrow. The store doesn't even check the phones out except to make sure all parts and accessories are contained in the box, there it will sit for (they said, roughly a week) before it's shipped back to T-mobile. By then, I figure liability of the phone is officially out of my hands.
merlino211 said:
It's being shipped back via the store under the 14 day buyers resource. I have had two of these so far, both have suffered from the screen oddly self-scrolling... Figure maybe a bad lot produced, as t-mobile tech support has not even heard of such a problem before. I finally settled on buying a nexus one, which arrives tomorrow. The store doesn't even check the phones out except to make sure all parts and accessories are contained in the box, there it will sit for (they said, roughly a week) before it's shipped back to T-mobile. By then, I figure liability of the phone is officially out of my hands.
Click to expand...
Click to collapse
I think you mean buyer's remorse, also I was under the impression that Limited Editions could not be 'returned' , merely exchanged or serviced.
If you don't have a contract, you could sell the phone once you put the working stock rooted rom onto it.
jesus... some of you really hurt my head over this phone.
So flashing the stock mytouch splash screen doesnt work if youre on a 1.2 or are most of you guys worrying because you have fenders?? Also can someone give me the mytouch splash screen???
You can find it here
http://theunlockr.com/2010/03/10/how-to-change-your-splash-screen/
I noticed that no one has set up a guide in this section on how to un-root and restore to factory for Warranty return/exchange purposes.
Below is a guide for the 1.29 Original:
http://theunlockr.com/2009/10/03/how-to-unroot-the-htc-hero/
Here is the Factory Restore for the 1.56 ROM:
http://forum.xda-developers.com/showthread.php?t=608434
Untested Theory:
Restore original Nandroid that you made after you first rooted your phone, that should put you at
a rooted 1.56
Then RUU to 1.56 and you should be factory.
Do not RUU from 2.1 to 1.56 because you are more likely to have issues.
If you can't deal with the minor bugs that are in the current DamageControl v2.0r2 then you might want to RUU restore, however I would suggest to wait it out because an offical 2.1 update might have to be rooted differently than what we have now. I prefer the Dev route.
I'm lucky that I didn't flash a custom ROM that wasn't a Sprint build, so my PRI didn't get messed up but if you did then go here, from dfbonney:
http://forum.xda-developers.com/showthread.php?t=654119
The posts below should also help understand how all this stuff has been gathered.
Most of us dont need a guide since we know that if we use RUU will restore the phone to un-rooted factory settings...
The Nandroid back up you make after your root will capture Root stuff, since it is done after the fact.. so it restoring the nandroid will not unroot (is that a word?)
Only way to unroot is with RUU, some people have an issue (50/50) after you flash the Flipz Radio update. Though it could be linked to running a 2.1 Rom and trying to RUU with 1.5.
I do belive they found a way to reflash each of the partition images individually and bring the phone back to life.
Let's do this!
Darkshneider said:
Most of us dont need a guide since we know that if we use RUU will restore the phone to un-rooted factory settings...
Click to expand...
Click to collapse
Kcarpenter thanks for pointing out what I asked. The above mentioned by Darkshneider is obvious as a stand alone quote but in the case from 2.1 back to 1.5 there may or may not be issues, how to be certain?
I would like this thread to help people who are having problems revert back to something functional in the event of a failure or a freak development like the PRI mismatches that have been happening. I know people here are supposed to be "DEV" savvy but not everyone is at the same experience level.
Let's try have as little guesswork as possible involved and try to get things in order. I don't think that's too much to hope for.
I'm fairly certain my post can help those who've bricked their devices... it should be stickied or in the same post...
http://forum.xda-developers.com/showthread.php?t=654119
GURUGTS said:
Kcarpenter thanks for pointing out what I asked. The above mentioned by Darkshneider is obvious as a stand alone quote but in the case from 2.1 back to 1.5 there may or may not be issues, how to be certain?
I would like this thread to help people who are having problems revert back to something functional in the event of a failure or a freak development like the PRI mismatches that have been happening. I know people here are supposed to be "DEV" savvy but not everyone is at the same experience level.
Let's try have as little guesswork as possible involved and try to get things in order. I don't think that's too much to hope for.
Click to expand...
Click to collapse
If you are asking what issues are there if you go from 2.1 back to 1.5? Well, the only one I ever had was with the market not letting you see Protected apps. This was a bigger pain than I thought it would be and the fix is a little tedious.
Some people have issues with restoring Nandroid's, but I believe that is usually because they are running low on SD Storage space for the Nandroid to expand as it is copied to the phone.
The PRI Stuff shouldn't be a HUGE issue, unless you want to use Sprint TV and Navigation and those Sprint Apps. Persinally I hate Sprint TV, picture is to fuzzy and the way they break the eppisodes into 5.5 minute clips gets on my nerves. Then they want you to pay for the good cartoons...bastards!
I think Google Navigation is just as good as Sprints...minus the Voice and the interface isn't as pretty...but Ill take it.
Will restoring with RUU also put the original dialer taskbar and anything else you changed back??
redlinethecar said:
Will restoring with RUU also put the original dialer taskbar and anything else you changed back??
Click to expand...
Click to collapse
Si. Oui. Ja. And Yes.
I noticed there is a guide on fixing the 110 error and a guide on how to unroot using your sdcard but not a general one covering the basics of unrooting with the RUU.
This should definitely be written up all in a post and included in the guide wiki.
i agree so users like me won't annoy people with thousands of questions when I need to get it done lol
redlinethecar said:
i agree so users like me won't annoy people with thousands of questions when I need to get it done lol
Click to expand...
Click to collapse
lol, noobs asking questions that are readily availble will never stop, at least the wikis give us a single location to direct them to...
Welcome to XDA redline!!
Please ask away, search first but if you can't find something we are here to help!
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
Hi everyone,
So I updated the stock SPL back to my phone while having a CDMA rom on my device. Looks not like a problem at all, but appearantly it is when your phone is not a CDMA rom After that the phone won't boot anymore.
Since then I am not able to update my device to ANY rom, not even the stock rom. The updater keeps giving me the famous 262 error and hangs at 0% of the update. XDA-user orfeo_b has messaged me a while ago that he had a task29 program for windows 7 to format my phone. But he didn't respond to my message. So my question is: is there anybody who has this program for my phone? and if not, is there any other possibility to empty/format my phone?
Why did you create two threads in the same forum? (THREAD LINK)
You not want to post HERE, did you even bother to do any searching in HERE
You do know the FUZE is GSM, correct?
R^7Z said:
Why did you create two threads in the same forum? (THREAD LINK)
You not want to post HERE, did you even bother to do any searching in HERE
You do know the FUZE is GSM, correct?
Click to expand...
Click to collapse
sorry, a second after saving I realised that my topic was a question so I posted the topic again accidentally.. I searched the whole forum for weeks but didn't find any solution. As I said, I accidentally flashed a CDMA rom to my GSM phone.
User benjamminzIS started the thread HERE
Perhaps give that a once or twice over and see if it works for you. Be sure to leave some feed back if it does!
Additionally, I must confess that I skimmed your post because you posted twice and didn't think anything of it after the fact. So I apologize if I came off slightly rude. Was not my intent!
There's a pretty good chance your phone is dead now. Flashing the stock spl after bricking your phone with a cdma rom is probably the worst thing you could have done. What were you thinking? With the stock spl, you can't flash task 29, or anything, for that matter. I guess you can try flashing hard spl, but you have to keep in mind that this 'stock spl' is not in fact the real stock spl (it's a patched stock spl that is capable of over-writing the hard spl). I'm not sure if it can be over-written with hard spl; I guess you'll find out. If you had read any of the posts on reverting to stock for warranty purposes, you would have seen that the absolute last step is flashing the 'stock spl', because once you do that, the device is locked.
Now, if you also flashed a cdma 'stock spl', then you can definitely throw the phone away.