Need to be sure which update method - myTouch 3G, Magic Android Development

I have an (unlocked Rogers) Magic. Running latest cynaogenmod, matching bc kernel, RA-sapphire-v1.5.2H, home++ and had been fine through the Rogers 911 'crisis' but have now had data cut. I have another Magic to get back on data in "24-48 hrs" so in the meantime I want to freshen up the unlocked Magic. But I want to be certain before I jump into this again. A radio update worries me as that is where I'm most likely to brick.
currently on the unlocked Magic::
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0010 (SAPP50000)
CPLD-12
RADIO-3.22.20.17
In December I did the one click root, RA recovery and kept up with cyanogenmod.
I don't care if I have Sense or not, just a fast and smoot experience. The SD card is partitioned with 32M swap, 512M ext2, FAT32. The swap helps but so far I'm not pushing apps to SD since I still have room.
So can anyone point me at my safest method or am I at the best already? I ended up with a brick when I tried going to Cursorsense so I'm not sure what I did wrong or if my phone wasn't suitable the way it was at the time. I've bought a new phone and am now back to where I was.

Related

Newb here with a question

Okay guys,
I have my phone rooted and I have the following loaded:
ota-radio-2_22_19_26l.zip
JFv1.50 ADP1.5
I also have my apps going to my sd card via the guide on here.
I was going to load a custom image and I realized that I didn't have the correct bootloader which I THOUGHT I loaded when I loaded JFv1.50...
It says on my bootloader that I have:
DREA100 PVT 32B
HBOOT-0.98.0000
RADIO-2.22.19.26i
The background of it is red,green, blue, and white...
I thought that I loaded the new bootloader(hardspl) when I rooted my phone before, but I guess I didn't ??? I thought the JF build wouldn't install unless it did...
Can I simply just upgrade it to the new bootloader or will I need to do EVVERYTHING starting from rc29 again ?
Perhaps someone will have better advice, but mine would be to reflash the NBH and then reflash JF's ROM
hardSPL can be flashed without otherwise changing your system
just use utmost caution to ensure the checksum of the update file ON YOUR SDCARD is identical to what is says in the SPL thread. Check it inside the terminal on the phone itself.
also, there is always a chance that flashing an SPL could harm your device.
mhsbrian said:
Okay guys,
I have my phone rooted and I have the following loaded:
ota-radio-2_22_19_26l.zip
JFv1.50 ADP1.5
I also have my apps going to my sd card via the guide on here.
I was going to load a custom image and I realized that I didn't have the correct bootloader which I THOUGHT I loaded when I loaded JFv1.50...
It says on my bootloader that I have:
DREA100 PVT 32B
HBOOT-0.98.0000
RADIO-2.22.19.26i
The background of it is red,green, blue, and white...
I thought that I loaded the new bootloader(hardspl) when I rooted my phone before, but I guess I didn't ??? I thought the JF build wouldn't install unless it did...
Can I simply just upgrade it to the new bootloader or will I need to do EVVERYTHING starting from rc29 again ?
Click to expand...
Click to collapse
I think that you need to redo the hardSPL again. Just make sure you read and re-read it before you do it. It's been a long time since I did it but mine read:
Dream PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CLPD-4
RADIO-2.22.19.23 [--I like this radio the best]
Hope this helps
Thanks guys !!!
Got it flashed and everything works great !!!
mhsbrian said:
Thanks guys !!!
Got it flashed and everything works great !!!
Click to expand...
Click to collapse
I was gonna suggest that haykuro just released a new version of the hardspl that almost doubles the system partition. 89mb of internal mem!!! Since you were flashing anyways. U can find it on his blog.

Hboot-1.76.0007(sapp10000)

Am I still stuck?
I have G1 and Magic, and G1 is running on Android 1.6 ... but the battery life is really not up to standard. On the other hand, Magic has good battery life but I am stuck!
My magic:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0007(SAPP10000)
CPLD-12
RADIO-6.35.07.29
Is there anyway to fix this?
annalee said:
Am I still stuck?
I have G1 and Magic, and G1 is running on Android 1.6 ... but the battery life is really not up to standard. On the other hand, Magic has good battery life but I am stuck!
My magic:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0007(SAPP10000)
CPLD-12
RADIO-6.35.07.29
Is there anyway to fix this?
Click to expand...
Click to collapse
G1 has smaller batt capacity compared to magic in other words the matt holds less.Which explains short life.
sorry, are you looking for a way to solve your poor battery life issues with the g1, or are you trying to revert from the 1.76 SPL and 6.35 radio back to standard?
for the former, you are in the wrong section.
for the latter see this: http://forum.xda-developers.com/showthread.php?t=605239
annalee said:
I am stuck!
My magic:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0007(SAPP10000)
CPLD-12
RADIO-6.35.07.29
Is there anyway to fix this?
Click to expand...
Click to collapse
If you've got to this stage using the RUU there is currently no way to downgrade. That SPL is perfected.
?
Hi, have you tried the gold card method?
i hade perfect spl, but i was able to fix this with this method..
Look in here:
http://forum.xda-developers.com/showthread.php?t=547133
Grimms said:
Hi, have you tried the gold card method?
i hade perfect spl, but i was able to fix this with this method..
Look in here:
http://forum.xda-developers.com/showthread.php?t=547133
Click to expand...
Click to collapse
Gold card method will fail when trying to apply the 2.53.707.2 SAPPIMG with an error stating 'main version is older'
You have to wait until a newer version Engineering ROM is available from HTC. Or maybe a new kernel exploit on 2.6.27 will be found...
cursordroid said:
Gold card method will fail when trying to apply the 2.53.707.2 SAPPIMG with an error stating 'main version is older'
You have to wait until a newer version Engineering ROM is available from HTC. Or maybe a new kernel exploit on 2.6.27 will be found...
Click to expand...
Click to collapse
Oki, it was just a proposal..
Thanks guys...
I guess I will just have to keep checking HTC website... and no I really wasn't looking for a fix for the battery life on G1 coz G1 now mostly resides in my draw .. I only use magic now but very frustrated with being stuck in 1.5 while I see my old G1 can run on 1.6! (or above) : (

htc magic boot loop not rooted HELP PLEASE

hi guys i am at my wits end with my htc magic 32a phone
i had a big package of apps on my phone i installed apps2sd no knowing anything about it i had a we fiddle then closed it down thinkin i didnt know how to work it(which i didnt) my phone then started acting all crazy my sd card couldnt be read nothing would start etc so i uninstalled apps2sd then rebooted phone...
now it gets stuck on the first screen (hami logo on mine) and will not go any further i have done a factory reset but it has made zero difference i have also tried booting with no sd or sim, formatting sd even filling my sd with the folders etc off of a freinds phone nothing has worked ive been researching for a while now and am at a loss on what to do
please if anyone has any suggestions i would love to hear them
reloading rom
hey, have you tried reloading the rom?
if you can put a bit more info up someone might be able to find a rom to suit
Do you remember the version number etc?
sapphire pvt 32a ship s-on h
hboot-1.33.0009 (sapp10000)
cpld-12
radio-3.22.20.17
may 8 2009,21:02:32
that is what it says in the fastboot screen
can you flash a rom without having root access?
has nobody else had an experience like this?

RUU USB boot screen

Hi,
I thought id flash my 32b with the latest rom today, so i downloaded it off here (said it was for a 32b) and flashed my phone...
1: its not for a 32b its for a 32a
2: its now stuck in RUU USB mode
3: i can communicate to it with fastboot but can not load a recovery file as it just hangs where it should have rebooted into the recovery image,
4: its using 1.76.0009 spl which is a perfect one.
5: PLEASE does anyone know how i might be able to UN-Brick my phone ?
6: I cant make a gold card as i can't get the CID for my SD card
PLEASE HELP
EDIT: There is an update on HTCs UK site. Just download and install that and you should be fine.
thanks for the reply,
Unfortunately im from NZL and my serial number doesnt work
and my phone is a 32b and that update is for a 32a
Used Haret to get CID
I also bricked my Magic yesterday, using an official RUU.exe. And I had the same problem in obtaining the CID, but luckily I could get around it as follows:
I still have an old HTC Touch Cruise (aka Polaris 100) and installed an Android version which booted from Haret. Once it was running I could obtain a terminal window and do a cat for the CID file. I tried to access it via ADB, but that did not succeed.
There are several distributions described in the Polaris forums, your mileage might vary with other models.
So if you know somebody with an HTC phone (WM) try to find an Android distribution for it, put it on your SD card and run haret. It is non-destructive and allows you to read the CID. After obtaining the CID, I reformatted the SD card and folowed the instructions here: Create gold card.
After inserting the Gold card, I could continue the RUU update and now I have a Magic with HTC Sense.
thanks for that, im glad to see im not alone, im trying to find a program for linux / mac / windows which will give me my CID for my SD card but can't find one anywhere
When you put the goldcard in and turned your phone on it boot from it automatically ?
gymmy said:
thanks for that, im glad to see im not alone, im trying to find a program for linux / mac / windows which will give me my CID for my SD card but can't find one anywhere
When you put the goldcard in and turned your phone on it boot from it automatically ?
Click to expand...
Click to collapse
If u have a nokia hacked can use the ReadCID aplications.
thanks i have found a friend with a touch HD on android so i am going to get that tomorrow and make up a gold card ,... Ill report back with the results.
Thanks to everyone for your help todate
gymmy said:
thanks i have found a friend with a touch HD on android so i am going to get that tomorrow and make up a gold card ,... Ill report back with the results.
Thanks to everyone for your help todate
Click to expand...
Click to collapse
hello, I had the same problem with the help of my colleagues from the Bulgarian, I fixed it without gold for cadets karta.Chek you just made the phone had such a site where you are setting up your serial number and go to where it e.sled enter the site and the HTC looking for old phone si.Download to update it if you go with the serial number if you do not poke around the net, Russians are brothers powwow original RUU, most important is to find for your original RUU telefon.Shtom find it, you put the USB cable and it puskash.This of me I hope I helped you
Wait... how did you manage to install a RUU for 32A on a 32B without goldcard?
sindrefyrn said:
Wait... how did you manage to install a RUU for 32A on a 32B without goldcard?
Click to expand...
Click to collapse
my platform is 32A end I dont creat cold card just a original RUU from HTC sait
my phone is TIM brandet and i download TIM RUU and my phone downupgade then
Just an update to how the recovery is going
Well i created a goldcard which has fixed my issue with the Custom ID check and i have managed to Down grade my hboot to 1.76.0008 and my radio phone is still having a personalliy issue and thinks its a 32a and its NOT !! when it gets to unzipping the system it just hangs there, in fact it sits there all day until the battery dies and indicator doesnt shift on phone from 0 so with the RUU it makes it to 81% if i can get a sappimg for a 32b which desent flash the system but only the radio and hboot would be great (I think) , issue is that when i try and make one, it comes up with Signature Verfiy Fail
HELP
Not even 32A users can downgrade 1.76.0008 right now except for the SU edition, which you cannot boot. You have a brick.
The same problem
http://www.youtube.com/watch?v=PlH_yhgRiwo
I have found a way around that im now working again, its all about the order that things get flashed to your phone.
I found an RUU that flashed everything 1st apart from the rom which is flashed last. As long as you have a gold card you can do this.
When it gets to flashing the system over its crashes... thats ok, take the battery out of your phone and reflash, your 32a s-on H becomes a 32b s-on H and then the system will flash over ok.
So... I have a skitzo phone at the moment with a saudi rom on it, but at least its working... HOW EVER.... these bloody alarms keep waking me up to do my prays hahahaa i thought that was kinda funny...
SO... now i just need to copy a sappimg onto my gold card and flash off that which ill do tonight
Ill give a full detailed HOWTO with links to the files once im back to normal.
Its taken me about 3 full days and about 3gig of downloads to get this sorted. If you dont have a gold card then your SCREWED... well not totally you need to get another phone eg android or a windows mobile 6.5 with eaRET on it works also
gymmy said:
I have found a way around that im now working again, its all about the order that things get flashed to your phone.
I found an RUU that flashed everything 1st apart from the rom which is flashed last. As long as you have a gold card you can do this.
Here's why I thought you had a definite brick:
When it gets to flashing the system over its crashes... that's ok, take the battery out of your phone and reflash, your 32a s-on H becomes a 32b s-on H and then the system will flash over ok.
So... I have a skitzo phone at the moment with a saudi rom on it, but at least its working... HOW EVER.... these bloody alarms keep waking me up to do my prays hahahaa i thought that was kinda funny...
SO... now i just need to copy a sappimg onto my gold card and flash off that which ill do tonight
Ill give a full detailed HOWTO with links to the files once im back to normal.
Its taken me about 3 full days and about 3gig of downloads to get this sorted. If you dont have a gold card then your SCREWED... well not totally you need to get another phone eg android or a windows mobile 6.5 with eaRET on it works also
Click to expand...
Click to collapse
Now I am very curious. Where did you get this RUU? I still don't see how you fixed it. I'm looking forward to seeing you detail this.
The new RUUs come in 2 zip files - the first with the radio and hboot and the other with the rest of the files. You can rename them as sappimg.zip to try to flash them from RUU, since they are signed by HTC.
However, as far as I know those RUUs are for 32A only. If you had HBOOT 1.76.0008, 0009 or 0010, you can not flash a lower version ROM even with a gold card. The SPL/HBOOT and radio combination actually seems to work on the 32B. However, you would need to be able to boot to a custom recovery somehow to do anything special. The system.img on the 32A RUUs I thought were too big for 32B. So if you were able to flash you must have had enough space on the 32B and I was wrong. I wonder why people are getting stuck though.
The reason I called a brick is because the only available 32B HBOOT have lower ROM version strings (2.x series ROM) than the 32A RUUs (3.x series ROM version string). I still don't know if 32A RUUs actually work on 32B.
You can flash the 3.05 series SPLs all you want, but they are all perfected. The only other option for the 32A Magic was booting to the leaked 3.04 ROM with SU in the system image, but you would not be able to flash that. So are you saying that it actually works?
Anyways please report back
xaueious said:
Now I am very curious. Where did you get this RUU? I still don't see how you fixed it. I'm looking forward to seeing you detail this.
The new RUUs come in 2 zip files - the first with the radio and hboot and the other with the rest of the files. You can rename them as sappimg.zip to try to flash them from RUU, since they are signed by HTC.
However, as far as I know those RUUs are for 32A only. If you had HBOOT 1.76.0008, 0009 or 0010, you can not flash a lower version ROM even with a gold card. The SPL/HBOOT and radio combination actually seems to work on the 32B. However, you would need to be able to boot to a custom recovery somehow to do anything special. The system.img on the 32A RUUs I thought were too big for 32B. So if you were able to flash you must have had enough space on the 32B and I was wrong. I wonder why people are getting stuck though.
The reason I called a brick is because the only available 32B HBOOT have lower ROM version strings (2.x series ROM) than the 32A RUUs (3.x series ROM version string). I still don't know if 32A RUUs actually work on 32B.
You can flash the 3.05 series SPLs all you want, but they are all perfected. The only other option for the 32A Magic was booting to the leaked 3.04 ROM with SU in the system image, but you would not be able to flash that. So are you saying that it actually works?
Anyways please report back
Click to expand...
Click to collapse
No they dont work and hence why it bricked the phone, the good part is that it never flashed the rom so I was sweet with getting the phone back. Prior to flashing it was 32b 1.33.0010 eng s-off G, then 32a 1.33.0009 s-on H and now is a 32b 1.33.0010 s-on H... rom is 2.56.??.? which ill have to look up later when im back home either way its gone from a 32b to a 32a stuck in RUU USB (due to not enough room to flash the rom) back to a 32b which works just is all arabic.
With the GOLD card it allowed me to flash a different Custom ID on to my phone, replaced the Radio and SPL and which then changed the phone from 32a to 32b, I even reversed it and did it again to makesure it wasnt a fluke and it wasnt. if it wasnt for the fact that the order of the flashing occured the way i did i wouldnt have been able to fix it as it would tried and flash the SYSTEM b4 it would flash everything else which would make it hang !
As soon as ive rooted the current rom (which is harder than i expected due to the rom version) ill do a write up on how to fix it as there are a few steps inbetween.
.
Wait so you never flashed 1.76.x did you. You just had 1.33.0009 and you typed it wrong in your first post?
If so we don't need a walk through for that. The one at unlocker.net would have served you perfectly.
what walk through was that, ill re 32a it again and ill let you know that it was.
just an update ,
Yes it was spl 1.76.0009
i have since flashed the phone with 2.56.494.7 and now have to wait until someone gets a rooted version of this rom or releases a later gold card version of sappimg.nbh or sappimg.zip to cut a long story short this is what happened.
1: flashed a Sence-IU for a 32b (but it wasnt it was for a 32a)
2: ended up with 1.76.0009 and the radio which goes along with it.
3: now reads 32a s-on H
4: made a goldcard
5: had to flash with 2.56.494.7
6: first flash of this rom replaced the SPL with 1.33.0010 (perfected)
7: screen now reads 32b s-on H
8: rom failed to flash
9: re-run the update of 2.56.494.7 and the phone flashes and reboots
10: cant root the phone until a newer version of sappimg.nbh is released
11: can use the phone but the arab applications dont allow the market
12: now its a waiting game.
Hope this helps others with bricked phone... If i had to do this again i wouldnt have flashed the 2nd time with 2.56.494.7 but instead a different RUU for the 32B this would have ment i would have been able to root the phone... Live and lean !
.
I have used the guides in this post to fix a friend's 32B Magic, which he had flashed with an RUU for 32A Magic. It works just fine.

[Q] Help with free phone with half-flash

So I lost my phone this week, and my buddy offered me up his old Inspire for free. He didn't mention the fact that it's like, midway through a failed flash (soft-bricked, I guess?). I've been searching and reading, but I just seem to get further down the rabbit hole with what exactly I'm supposed to do. Really, I haven't run across any threads with this problem yet.
It's currently S-ON, but has CWM installed. There doesn't seem to be a rom installed, because it'll hang on the HTC splash screen on boot (matter of fact, he didn't even give me an SD card with the phone, so I had to scavenge one of my good SanDisk ones) and I'm not entirely sure where to go from here to get it up and running. I don't care much for the Inspire's stock rom, but at this point I'm in dire need of a phone and if it's easier to go back to stock than it is to fix this mess and have a nice ROM, I can live for a little while.
What should I do, and how exactly should I do it? It's been quite a while since I tried this (and even then it was with my lineage of janky huawei handsets).
EDIT: I've got a screencap of the info but the board spam prevention won't let me link it.
***UNLOCKED***
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
burk992 said:
So I lost my phone this week, and my buddy offered me up his old Inspire for free. He didn't mention the fact that it's like, midway through a failed flash (soft-bricked, I guess?). I've been searching and reading, but I just seem to get further down the rabbit hole with what exactly I'm supposed to do. Really, I haven't run across any threads with this problem yet.
It's currently S-ON, but has CWM installed. There doesn't seem to be a rom installed, because it'll hang on the HTC splash screen on boot (matter of fact, he didn't even give me an SD card with the phone, so I had to scavenge one of my good SanDisk ones) and I'm not entirely sure where to go from here to get it up and running. I don't care much for the Inspire's stock rom, but at this point I'm in dire need of a phone and if it's easier to go back to stock than it is to fix this mess and have a nice ROM, I can live for a little while.
What should I do, and how exactly should I do it? It's been quite a while since I tried this (and even then it was with my lineage of janky huawei handsets).
EDIT: I've got a screencap of the info but the board spam prevention won't let me link it.
***UNLOCKED***
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Click to expand...
Click to collapse
My strong hunch is that he didn't flash the boot.img in the ROM zip, which you need to do for S-On Unlocked phones. When you flash a ROM in the recovery, make sure you also fastboot flash the boot.img from the ROM zip. The Ace Think Tank thread in DHD General has links with instructions on how to do that.
bananagranola said:
My strong hunch is that he didn't flash the boot.img in the ROM zip, which you need to do for S-On Unlocked phones. When you flash a ROM in the recovery, make sure you also fastboot flash the boot.img from the ROM zip. The Ace Think Tank thread in DHD General has links with instructions on how to do that.
Click to expand...
Click to collapse
Aha! That did the trick. I just flashed Carbon on this thing, but now the Android keyboard won't work. It's okay, I'm sure I can fix it. Thanks for the help!
Yeah, that'll be an issue for the ROM thread. Though of course, if you didn't full wipe first, try that.

Categories

Resources