Related
So I guess it really is easy to brick a MT3G - can't fastboot, can't enter recovery.
Just stays on the MT3G boot screen.
I've tried all the boot key combinations, does anyone have any magic solutions that may work?
It was rooted just fine (from the first day rooting was discovered, using the gold card method). Tried to upgrade to a CyanogenMod, and somehow messed things up. I suspect I screwed up when I flashed the radio.
Hmph.
Why did you flash a "new" radio...?
The radio that comes standard as a packaged feature for the T-Mobile USA version of the HTC Sapphire (MT3G) is 2.22.19.26I - there was NO NEED for that adjustment. I'm not suggesting that flashing a new radio is what corrupted your device, but it certainly could have contributed to the eventual cause.
The One-Click Root Method is the safest way (until patched via Google 1.6 build - also known as Donut) to ROOT your MyTouch. I've used that for three various Android devices, all of which functioned properly immediately after. No flashing of upgraded radios, SPLs, etc.
Finally, from the beginning - as any ROM flasher should know, you SHOULD HAVE backed up your STANDARD, T-MOBILE PROVIDED, Cupcake v1.5 build using NANDROID from the Recovery image. If that is the case, restore those settings and start all over with the "rooting" process using the One-Click method via the Recovery Flasher application.
Good luck.
damn i think i brick my phone after loading a radio ugh it sux
Again.
Tobi87 said:
damn i think i brick my phone after loading a radio ugh it sux
Click to expand...
Click to collapse
Re-read what I posted previously.
The MyTouch comes standard with the latest radio and and SPL (even if considered PERFECT) doesn't prevent you from running any of Cyanogen's latest builds. I don't see why you thought that flashing a "new" radio was going to do something special. As for the "Gold Card" method...I don't see why you didn't think to try the easier, safer, much less work type of method. THE ONE-CLICK ROOT METHOD!
Hi all,
I just updated my Magic (Hutchison/3, Australia) (32A) to the latest official HTC firmware with sense ui (I had cyanogen on there before but it was too buggy for my liking). However, it seems that this firmware has the "perfect" spl (HBOOT-1.76.0008, Radio 6.35.08.29). I was planning to root the phone without flashing a different rom but i of course need write access to /system. My plan was to boot amon-ra's recovery to do this, however when i try and boot it with "fastboot boot recovery-RA-sapphire-v1.6.2H.img", i get told "FAILED (remote: not allow)" (same deal for the hero version).
My idea is to download an old sappimg.nbh and start up the SPL on the phone, which displays some messages about looking for that file when it starts up. I assume this will flash an older SPL; then, i install the system part of the new ROM but not the radio/SPL somehow (is this possible?) then follow my initial plan for rooting the phone
However, from what i've read it seems messing with the SPL is pretty much the only way to brick the phone. Is what i suggest safe/will it work?
Thanks guys
greeklegend said:
Hi all,
I just updated my Magic (Hutchison/3, Australia) (32A) to the latest official HTC firmware with sense ui (I had cyanogen on there before but it was too buggy for my liking). However, it seems that this firmware has the "perfect" spl (HBOOT-1.76.0008, Radio 6.35.08.29). I was planning to root the phone without flashing a different rom but i of course need write access to /system. My plan was to boot amon-ra's recovery to do this, however when i try and boot it with "fastboot boot recovery-RA-sapphire-v1.6.2H.img", i get told "FAILED (remote: not allow)" (same deal for the hero version).
My idea is to download an old sappimg.nbh and start up the SPL on the phone, which displays some messages about looking for that file when it starts up. I assume this will flash an older SPL; then, i install the system part of the new ROM but not the radio/SPL somehow (is this possible?) then follow my initial plan for rooting the phone
However, from what i've read it seems messing with the SPL is pretty much the only way to brick the phone. Is what i suggest safe/will it work?
Thanks guys
Click to expand...
Click to collapse
unfortunately wont work... it wont allow you to flash an older spl...probably will have to wait till an official 2.1 update comes out and hope that it might be rootable..
And THAT will teach me to look before I leap! I guess I can live with this update because its actually a HUGE improvement over what I was using before (radio reception is much better, text correction in the browser,sense is win in general and its much snappier) and I can still do usb tethering. But still, WHY DID YOU DO THIS TO US HTC!!!
EDIT:
I tried taking the rom image from the RUU and using fastboot to boot the boot.img from that but not even that works! I was thinking to do something like init=/system/bin/sh... I don't suppose theres another way to supply cmdline parameters to the kernel?
So I've recently been trying to root my G1 and install Cyanogenmod 6, and now I've finally decided to throw my hands up in defeat. This computer voodoo is way too complicated for me to handle, and I just wanna get my phone back to how it was. How do I upgrade my phone back to the highest available firmware for the G1? I can't seem to do it through Android itsself.
What steps have you been doing to the phone? What version is it at now?
Vanilla unrooted 1.0, as far as I can tell. I don't want to put Cyanogen or anything on here any more, it's way too complicated for me to deal with. Just wanna get back to the current version of Android for the G1.
Root it, install SPL 1.33.2003, then install radio and system image from here: http://developer.htc.com/adp.html
Hi there,
I recently bought a brand new Defy+. For start, some general facts about my phone from Settings -> About phone (which I believe will be important for my questions)
System version: 45.0.1250.MB526.NonEFIGSRetail.en.EU
Android version: 2.3.5
Baseband version: EPU93_U_00.60.00
Kernel version: 2.6.32.9-gbdd614e
Build number: 4.5.1-134_DFP-125
I did not flashed anything to it, it is not rooted (yet).
So now the questions:
1) Should I upgrade to official 2.3.6, even if the system update thing in settings says, that there is no update available for my phone? Will I lost my warranty in that case, without the posibility to go back?
2) I would like to get rid of that Motoblur thing, and I would like to have a Cyanogenmod ROM there (or is there anything better than Cyanogenmod?) What should I do?
I readed the general guides about SBF, flashing CM7 and so on, but I don't completly get it (and most of the info considers only Defy, not Defy+). It is my first Android phone, so please, be patient
2.a) Which one is the official stock ROM that I have? On the site with the SBFs, there are two of them matching my system information, they differs in that strange combination of letters and numbers which begins with UCADEFYEMARAB or USADEFYEMARAB). Which one is mine?
2.b) Do I need to do anything with stocked SBF? Do I need to flash another one to be able to "freely" test new ROMs?
3) I know the steps after I will sort this out, just root, install 2nd init, copy zip files to sdcard, reboot, and then follow the steps that comes with each ROM. Or do I get it wrong?
Thanks for reply and again sorry for my dumb questions
Up to the Defy+, I was stuck with Win Mob. phone, things there were completly different, for Android it seems it is not as easy as booting into a bootloader, starting one-click flash utility on the PC and wait
This is something I stumbled on by accident. The easiest way to recover lost performance is utilizing HTC's RUU to return your system to completely stock, and then reroot your system and flash whatever version of android you like. If your bootloader is unlocked, you will need to relock it in order to use the RUU. There is no need to flash an HTC recovery or OS, just lock the bootloader. If you want to do the S-Off procedure, you may as well get the oldest RUU you can, and flash that.
Once you're back to stock, and you do want to go for S-Off, you will need to unlock your bootloader and gain root access. What worked for me was flashing a 4.4.3 Android Revolution HD build, and using Rum Runner. What I started off trying to do was to update the firmware for my One. One thing led to another, and 8 hours, a sleepless night, and a pot of coffee later, she was done.
The end result is that battery performance is now increased by 25%, boot times have decreased by 35%, and the general responsiveness of my phone with CM12 nightlies is much improved. She feels like a new phone again, not withstanding the new exterior casing I dropped in while I was it, creating a possibly one of a kind black T-Mobile One with absolutely no FCC or model number b.s. on the back.
Were you on older firmware before? Can't say I've felt performance in my phone dropping, aside from a possible slight decrease in battery time because of age.
With that said, I do find some ROMs bogging my phone down, but a good wipe and reflash seems to do the trick.
if you want to s-off with older Firmware/hboot and you are for example on latest Firmware/hboot ýou can't downgrade without s-off, so you Need s-off if you want to downgrade to older Firmware/hboot, also if you have for example the latest hboot 1.57 or so you won't be able to use an older RUU you should add that to your OP
That is unfortunately a limitation of the process, you are stuck with whatever version of HBOOT you have. But, that is why I recommend going with the oldest RUU available, to avoid upgrading the HBOOT to a newer version that might give you issues. I had no trouble using a 4.2.2 RUU despite having a 1.55 HBOOT, as this was the oldest RUU I could find. Far as I have found, any RUU will work with any HBOOT version. To do S-Off for any version other than 1.57, you can use Rum Runner, though you will need to use Sunshine for 1.57. And yes, I was saddled with an older version of the firmware, though I do recommend updating your firmware if at all possible. The difference could be described as akin to a dirty flash as opposed to wiping everything and then flashing. The difference between the older firmware and the most current is quite simply astounding. And the battery performance is the clincher. Initially, I would have trouble making it 6-7 hours. Now, it's anywhere from 8 hours to my record of 12 hours and change. She now has a new lease on life, and it looks like another year on the M7 is in the cards.
doing a factory reset from recovery is jsut as good...
from my expereince wiith dealing wth Windows phones ( windows phone only use RUU to flash custom /stock roms). it is the same as factory reset from settings.