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/
Related
I did a search, and dont see anything to answer this specific question.
Ive got my new Dev 1, and have the latest JF update. I want to install some cool themes, however, I know its a possibility to brick my phone.
Exactly how easy is it to brick your phone while installing a theme? I plan on following the directions step by step, but I will be very upset if something happens.
Any advice would be much appreciated. I suppose I just need some reassurance...
Thanks in advance.
Not too easy but if you Flash a corrupted SPL your toast
not very easy, just remember, if it boots to the SPL or recovery mode you are fine, it's not a true brick. if it doesn't boot at all then you may have an issue. i have had many times where the phone decided it didn't want to boot past the boot screen, or the flashing android and yet i am able to post this now using my phone as a tether. if you get stuck on one of those screens then you need to either flash the dreaimg.nbh or a new update.zip including the full JF build
Dredge said:
I did a search, and dont see anything to answer this specific question.
Ive got my new Dev 1, and have the latest JF update. I want to install some cool themes, however, I know its a possibility to brick my phone.
Exactly how easy is it to brick your phone while installing a theme? I plan on following the directions step by step, but I will be very upset if something happens.
Any advice would be much appreciated. I suppose I just need some reassurance...
Thanks in advance.
Click to expand...
Click to collapse
Why are you so worry about brink your phone? If you want to brink your phone pour some concrete on the phone and make a customize brink G1.
tubaking182 said:
not very easy, just remember, if it boots to the SPL or recovery mode you are fine, it's not a true brick. if it doesn't boot at all then you may have an issue. i have had many times where the phone decided it didn't want to boot past the boot screen, or the flashing android and yet i am able to post this now using my phone as a tether. if you get stuck on one of those screens then you need to either flash the dreaimg.nbh or a new update.zip including the full JF build
Click to expand...
Click to collapse
whatever he said....^^
I've flashed themes that were designed for RC3xx on my ADP1.1 and managed to "bricked" it. All i did was go to bootstrap and reload the SPL with RC29 and re-flash ADP1.1 to the phone.
As long the hard-SPL on the bootstrap remain untouched, there's always a way to recover your phone...it may be long, boring, and redundant...but it will safe your G1 from truly becoming a brick...or paper weight...or both
This makes me feel a bit better. I will just back up the latest JF update and keep it in case something happens. I will probably just hold off at tleast for a little while before I try doing much. I need to get a feel for the phone before I try to mod it. I found some cool wallpapers that should tide me over for at least a little while. But the clock is u-g-l-y. Im use to having TouchFlo, with HHC, and all the neat custom clocks.
Well, thats why I am probably not going to update my SPL...
I own an ADP1 and so already got the engineering SPL... and as the SPL update seems for me to be the only way to brick my phone... well, I am a coward...
It may be a little offtopic, but i am planning to update to JF1.43, or perhaps even messing around with Ubuntu MID (if ever possible).
Is there a really good reason I should update to HardSPL?
HELP I CAN'T GET DREAIMG.NBH Installed!
I just tried to downgrade my G1 from RC33 v1.42 + Radio Update 1.22.14.11!!!
I think I made the mistake and downgraded my bootloader from SPL_Hard to Original RC29_ SPL, because I was having trouble getting the file Dreaimg.nbh, recognized after booting holding camera + power buttons.
After downgrading from SPL_Hard to Orig RC29, I was able to boot holding the camera + power buttons, and the process started, but just before completing I got an error, FAILED TO UPDATE TERMINATING, and now my phone only reboots to the SPL screen with this showing:
DREA100 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.14.11
SEP 2 2008
I believe it's has to due with the Radio Update 1.22.14.11...
I'm going to try using QMAT and follow the Inst from that same thread. If that doesn't help can some offer some help???
Follow UP!
QMAT WORKED:
http://forum.xda-developers.com/showthread.php?t=490960
Sorry about the double posts!
Many people complain that they have "bricked" their phones when they really haven't. This thread will hopefully help reduce the questions on all of our useful threads.
How to tell if your phone is bricked:
1.) When you try to turn it on, nothing happens?
2.) Camera+Power does nothing.
3.) Home+Power does nothing.
4.) You flashed the SPL BEFORE the radio
If you answered yes to any of the above 4, you are bricked. You probably need a new board in the phone. Read more here: http://forum.xda-developers.com/showthread.php?t=516440 It has been confirmed that you WILL brick your phone if you attempt to downgrade your radio after flashing the new SPL. Not sure why you would want to anyways...
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
2.) Your phone is stuck in a boot loop
3.) Home+Power boots into recovery
If you answered yes to the above then you are NOT bricked. You have the G1 Night Light. This is (usually) a very easy fix.
The usual scenario is: You just upgraded your radio and/or the SPL on your phone and now you are trying to turn it on with no luck.
How to fix: After you upgrade your radio and/or SPL, you need to wipe a rom on the phone. For a plain almost stock feeling rom, checkout http://jf.andblogs.net/2009/05/24/jfv151-images-are-out/ if you are looking for hero, checkout the tutorial at g1upgrade.com.
I have also noticed when you flash hero, it will stay on the g1 logo for 5 or 6 minutes and then it'll finally start loading. Make sure your not being impatient and give it several minutes if you have just flashed a rom.
Last step:
If you have installed a new radio, then spl, then a new rom and you STILL get the g1 screen. Try it all over again. You probably didn't do something right. You don't need to ask questions in 30 different threads, your issue is not unique. You just need to search for some answers.
*Saved for future posts*
Edit:
Thanks! Updated.
I flashed the SPL before the radio whenever Haykuro released the Hero ROM and I didn't brick my device. Guess that I just got lucky. Thank goodness I know better now. haha
it's possible you flashed the radio prior to the SPL, only a loooong ways back.
Another thing to try if you are having issues is:
su
rm -r /system/sd/*
I was stuck in a boot loop and a quick ext3 wipe did the trick. The command should be able to be ran from console or terminal. You may need to mount /system with:
mount -t -rw,remount -o yaffs2 /dev/block/mtdblock3 /system
You would need to type that in between the commands above . I ran across this in another post but i think this is a good spot for it too .
Duplicate post...
thanx
At least I know now how to tell if I bricked my phone or just flashed it badly thanks for this.
youneek said:
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
Click to expand...
Click to collapse
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
alapapa said:
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
Click to expand...
Click to collapse
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Good Job
Sorry this is off topic. But...
Thank you for this thread!
Ok,
By the way, has anyone figured out what The difference in the baseband is?? I have a U in mine...
youneek said:
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Click to expand...
Click to collapse
really? if it can't get to recovery / fastboot mode nobody has published a fix w/o a hardware swap.
what's your method?
I will buy a bricked one off ebay and post the steps I do to get it back. I can only fix the "Night Light", I can't fix a truly bricked phone (yet).
digital006 said:
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
Click to expand...
Click to collapse
How and where did you sent for repair and how much does it cost? I have a bricked MyTouch3G at this moment. Did HTC took it?
not bricked just weird!
ok been reading on here ,not sure if i need to just reflash everything or sd issuse?i put the new raidio,then spl on !then put jacxrom on my phone worked great!then ran for a day.then tryed cyanogenmod 4.0 and loaded fine but got force closed issues at the google sign in so i wipe and went to jachero 1.2 loaded fine went to logo android and then htc ,but then the screen went to blank .like the as said g1 night light .so i went back to jacxrom 1.3 it loaded fine got stuck in t mobile g1 screen .ok i flashed again same thing. but this is the part if i take my memory card out it will boot up just fine!then put memory card back in but lol all apps are missing have reinstall them. i wipe every time.i have the latest raidio 22.19.26I).,spl 1.33.2005 .also the jacxrom is running fine when phones on .so any help please thanks .also when i put the spl on it loaded then said reboot so i did. after went back to recovery at the bottom it said formatting cach... but was setting there for a while so took battery out then booted phone .was it suposse to say done or not ! hope dont make any mad thanks for the info
bump
hey help me plz i have big problem
i forget hit alt+w when i install SPL then i press alt+s when SPL install i out battery then i put it my mobile don’t want open and when i holding down the Home and Power button don’t open recovery mode and i holding the End key and the Camera button don’t open boot loader plz help me plz
You aren't going to get any help with sentences that atrocious. Can you be more clear?
So i think i know what i did wrong, but is there anyway to fix it? I have a 32b which i rooted with the "recovery-RA-sapphirev1.5.2H", then i tried to update the radio with the "update-radio-32A-6.35.08.29-signed" (i didnt read the "32A"). Then i tried to reboot the phone and it got stuck on the "Mytouch 3g" green start up screen, i cant get to the recovery image by holding home+end.
My understanding (please correct me if im wrong) to get the new Nexus ROM was that i had to;
1) Go the the 1.5.2 recovery image & wipe
2) Partition the card (and convert Ext2 to Ext3 or Ext4 depending on the ROM), reboot
3) Flash the new Radio, then reboot
4) Wipe, Flash the new SPL, then reboot
5) Wipe, flash the new ROM, and reboot
Im sure what i did was noobish...
Previously i had been using the 1.3.2 immage and had loaded Hero ROM's and tweeked Cupcake ROM's just fine, it was only when i had to update the radio and SPL was it that i found difficulty, mostly because i found too many and didnt know which one to use.
PLEASE HELP!!!
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
My first guess is that you are f**ked!
Only 2 "Nexus" roms I know that require new radio are for the 32A. And only new radio I know is for the 32A Magic!
Don't know where you got the instructions to upgrade your radio, but the ones I read stated that you have to flash radio, hboot, recovery in this sequence, and THEN reboot. Also, your recovery should be for 32B, dunno how you missed that one.
Try this: find your old radio image, your old hboot and recovery, boot in fastboot mode (back+power) and type in the following commands from the Android SDK tool directory:
Code:
fastboot flash radio your_radio.img <enter>
fastboot flash hboot your_hboot.img <enter>
fastboot flash recovery your_recovery.img <enter>
fastboot erase system -w <enter>
fastboot reboot-bootloader <enter>
You should now have rebooted back in fastboot mode. If that worked, try to reboot into recovery and see that works.
Once in recovery you can restore or flash another 32B rom.
See here for Engineering hboot images.
Download recovery for 32B
I found the link on theunlockr.com
developers.com/showthread.php?t=598973
And found instructions on youtube "ECLAIR 2.1 ROM REVIEW AND TUTORIAL !!!" and tweaked it slightly because i found a recovery image for my sapphire which didn't support either the spl or the radio, i forget... I've been up since 3am on Wednesday because of work and school, and now its 9am Thursday.
I was reading that 32b ROMs were working for the 32a, so i thought i might try a 32a since none of the links on Amon_RA's page developers.com/showthread.php?t=529019 were working for me.
I cant get to the fast boot menu... so that way doesnt work
Some_Biker_Guy said:
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
Click to expand...
Click to collapse
I think you are rather screwed. I believe the phone boots up the radio image before the bootloader and therefore you can't even get to flash a new recovery or radio image as the boot process is halted because of the defective radio image.
The only salvation I know if is a JTAG connection. This involves open up and soldering stuff to the mainboard of your phone. Since you're asking you probably not familiar with it I wouldn't recommend it to you.
you have a mytouch 3g right? if so, you flashed the wrong radio image. you flashed the ra(blahblahblah)H! not the ra(blah)G! "H" IS FOR HTC BRANDED "G" IS FOR GOOGLE BRANDED (THE MT3G). so that is your first issue. try to boot into fastboot and flash the RIGHT RECOVERY IMAGE.
wow as soon as I looked at this thread, you made so many mistakes on the first sentence lol. I hope you learn to read and not rush things next time ^^ Recovery H = 32A, Radio says 32A, and you have a 32B and now you can't get into fastboot? I'm 99.9999% sure it's bricked, but correct me if I'm wrong! 32B roms work for 32A when you port them over. Seems like you did almost no research at all.
You're understanding of what to do is right, but you didnt pick ANY of the right files
KAwAtA said:
wow as soon as I looked at this thread, you made so many mistakes on the first sentence lol. I hope you learn to read and not rush things next time ^^ Recovery H = 32A, Radio says 32A, and you have a 32B and now you can't get into fastboot? I'm 99.9999% sure it's bricked, but correct me if I'm wrong! 32B roms work for 32A when you port them over. Seems like you did almost no research at all.
You're understanding of what to do is right, but you didnt pick ANY of the right files
Click to expand...
Click to collapse
I agree with KAwAtA. You pretty much did the right steps (kinda) but you got the wrong files and now you got a nice brick. You should do research and know how to tell if your phone is 32A or 32B, why you should never flash the wrong radio/spl for your type of phone, and what ROMs are compatible with your hardware and why you should never flash the ROMs for another piece of hardware.
Well look on the bright side, since you bricked your magic, instead of trying out the "Nexus" ROMs, you can now buy a Nexus One for real but do not ROOt it because you might flash a 32B radio on it and make that a fancy brick.
damn sorry bro. does sound like everything that could have gone wrong went wrong for you. i also went to theunlockr to root my phone and add roms to it but i read those instructions like 3 times and watched the videos a few times when i first did it. oh well, you'll learn from this at any rate.
AndroidNoobie said:
Well look on the bright side, since you bricked your magic, instead of trying out the "Nexus" ROMs, you can now buy a Nexus One for real
Click to expand...
Click to collapse
that lucky SOB!
you can't get into recovery, that's fine, but can you boot into hboot and fastboot mode? if so, your phone will be fine, just have to fastboot flash the right junk on
Some_Biker_Guy said:
So i think i know what i did wrong, but is there anyway to fix it? I have a 32b which i rooted with the "recovery-RA-sapphirev1.5.2H", then i tried to update the radio with the "update-radio-32A-6.35.08.29-signed" (i didnt read the "32A"). Then i tried to reboot the phone and it got stuck on the "Mytouch 3g" green start up screen, i cant get to the recovery image by holding home+end.
My understanding (please correct me if im wrong) to get the new Nexus ROM was that i had to;
1) Go the the 1.5.2 recovery image & wipe
2) Partition the card (and convert Ext2 to Ext3 or Ext4 depending on the ROM), reboot
3) Flash the new Radio, then reboot
4) Wipe, Flash the new SPL, then reboot
5) Wipe, flash the new ROM, and reboot
Im sure what i did was noobish...
Previously i had been using the 1.3.2 immage and had loaded Hero ROM's and tweeked Cupcake ROM's just fine, it was only when i had to update the radio and SPL was it that i found difficulty, mostly because i found too many and didnt know which one to use.
PLEASE HELP!!!
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
Click to expand...
Click to collapse
Well, I BRICKED BRICKED BRICKED my other mytouch. Im talking where the computer wouldn't recognize it, wouldn't charge, turn on, splash screen, NOTHING. Wasn't the battery. If you can get to the screen (where you hold down volume and power) you can probably recover it. DON'T know if this would work but it may be worth a try read this link to get it un-rooted and then retry. http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
iluvmymytouch said:
Well, I BRICKED BRICKED BRICKED my other mytouch. Im talking where the computer wouldn't recognize it, wouldn't charge, turn on, splash screen, NOTHING. Wasn't the battery. If you can get to the screen (where you hold down volume and power) you can probably recover it. DON'T know if this would work but it may be worth a try read this link to get it un-rooted and then retry. http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Click to expand...
Click to collapse
maybe u already tried.
dan-htc-touch said:
you can't get into recovery, that's fine, but can you boot into hboot and fastboot mode? if so, your phone will be fine, just have to fastboot flash the right junk on
Click to expand...
Click to collapse
he already said that he couldnt get into fastboot mode. most likely its a brick..
oshizzle1991 said:
you have a mytouch 3g right? if so, you flashed the wrong radio image. you flashed the ra(blahblahblah)H! not the ra(blah)G! "H" IS FOR HTC BRANDED "G" IS FOR GOOGLE BRANDED (THE MT3G). so that is your first issue. try to boot into fastboot and flash the RIGHT RECOVERY IMAGE.
Click to expand...
Click to collapse
I tried the "G" and it didn't work, so i tried the "H" and it worked. Fastboot didn't work...
Thanks everyone for you input... this is my reply to everyone since i cant reply to one/ a few at a time.
1) I knew how to root my phone, and did it multiple times. I also unrooted it a few times as well (just to get a fresh start and make sure i knew how to). I also loaded many different ROM's onto it including Hero and tweaked cupcake ROM's
2) Fast boot did not work, and the computer would not recognize the phone at any point.
3) The unlockr did a good job with instructions on how to root and unroot then loading the hero and cupcake rom's onto it but it had no explanation for loading the nexus rom onto it, although it did feature a link on where to get it. therefore i tried to piece together ways to update the radio and spl (this is where it all went to hell). i figured out that that is what i needed to do to run the nexus rom.
ok, ok now i know, wait for a full set of instructions for my specific phone to try to put the newest and coolest rom onto my phone... :/
4) i got it all taken care of, got "new" phone for free! so glad it worked out.
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.
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
sunster00 said:
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
Click to expand...
Click to collapse
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
jags_the1 said:
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
Click to expand...
Click to collapse
Hi mate thanks for offering advice and help. I have not had to use your method as I decided to give the HTC bootloader unlock code one final try before proceeding to your rescue plan and all of a sudden it was successful again. I got into recovery and did a nandroid restore so am back online again, but have nevertheless made note of your method in case I become stuck again in the future. Thanks anyway for your reply! :good: