Model ID Error - myTouch 3G, Magic General

Ok, Im sorry if this has been addressed somewhere. Ive searched for everything I can think of and nothing really seems to fix my problem that I can find.
Until recently, I was running Cyanogen 4.6 (I think) on my MT3G. Once I found out about 2.2 coming for my phone, I followed unrooting instructions and got running on the stock 1.5. The update came, I had it install the 2 parts of the update. After 2.2 was supposedly installed, I checked and my system still said it was running 1.5. No repush on the update for 10 days.
At this point, I went through the process of getting my unit more up to date and running 1.6 dmd64. Still no repush for the update.
So now Ive gone and made sure i have sappimg.nhb on my sd card. I try to run the first update for 2.2 manually. When I reboot holding home, all I get is the image of my phone with a triangle and an exclamation point. So I reboot holding down and try the update through hboot. It runs through the process, and when it is verifying signatures at the end, I get an error that says "Model ID Error."
I dont know what to do so that I can start running these updates to get up to 2.2
Thank you so much for your consideration and any help you can offer.

Related

UK OTA for 1.5 on a JF ADP 1.5 Rooted phone?

Ok...
So I woke up this morning to an update request on my UK T-Mobile G1. However, I've been running JF ADP 1.5 rooted build for at least a week!
If you click on details is says that it is a bootloader update, that will then be followed by a further update. This leads me to believe that my bootloader is not up-to-date?
I have had a look around, but am a little confused, as I previous installed the JF RC9 1.43, which included the bootloader (or the version before did).
On going into the recovery utility - it appears to have reverted to a 'standard' bootloader one (e.g. with triangle with !). I have re-installed the Engineering Bootloader, but it doesn't seem to have made a difference (don't know if it didn't install correctly!)
Anyway, anyone got an idea of how to stop the network update message?
The triangle with the ! is the recovery screen, the boot loader is either the rainbow colours or the skating androids.
My phone is running the eu 1.5 gfh firmware and I'm getting the same update. I think it's trying to put back the rainbow boot loader with fastboot support.
n0ahg said:
The triangle with the ! is the recovery screen, the boot loader is either the rainbow colours or the skating androids.
My phone is running the eu 1.5 gfh firmware and I'm getting the same update. I think it's trying to put back the rainbow boot loader with fastboot support.
Click to expand...
Click to collapse
So i'm clearly getting confused...
When I go into recovery mode (e.g. Home + Power) I used to get a JF console, now I get triangle !
I was just trying to guess at what had changed... All I really want is the update message to disappear!
The change would be to the boot loader
see http://forum.xda-developers.com/showthread.php?t=455860
Ok - so I've tried:
1) Re-doing the Bootloader
2) Re-installing the update (JF ADP 1.5)
3) Re-installing (or installing for the first time) the 1.5 radio from HTC website
Still keep getting the update request... I'm out of idea's! Any further suggestions more than welcome...
I have a US G1 but if i was you i would do the whole rooting process over again download the RC7.NBH rename it DREAMIMG.NBH redo the root hack than install JF ADP 1.5.
Thats your best bet
The how to is here
:-(
Unfortunately, that's pretty much the only thing I had thought of too...
But I haven't received any updates since rooting (e.g. since Dec) - so am not convinced that it will solve the problem.
smccaldin said:
:-(
Unfortunately, that's pretty much the only thing I had thought of too...
But I haven't received any updates since rooting (e.g. since Dec) - so am not convinced that it will solve the problem.
Click to expand...
Click to collapse
Well did you try it? It doesn't hurt to try it
Will try @ w/e

recently rooted phone, troubles installing roms

I've been reading these forums for quite some time folowing H's and JF's builds and just seeing what the devolping community has been up to.
I've been wanting to root my g1 for some time but didnt ever make the jump till now. I read through the Helpful Thread / Build Round up started with in the beginning there was root as well as the How-to- Root, Hack, and Flashing your G1/Dream and decided i could do it. i followed all of hte steps with ease. had my phone rooted within 20 minutes the first thing i wanted to do was to get a new rom with cupcake but i also wanted to be sure not to mess it up so i read through nandroid and was a bit confused as to what all was needed so i figured the recovery img that the tutorial gave was fine since everything i had done was no problem. i then went to H's ion thread and saw that i needed a differen spl so i went and read about those and decided with hardspl got that applied no problem. i downloaded the ion rom renamed it to update.zip put it on my card and loaded up recovery mode pressed alt+s to apply it and everything went fine till it hung at the 2nd boot screen. a little disheartened i went into the spl using camera+power and flashed the recovery img. i read around the forums seeing if i did anything wrong and couldnt figure it out so i tried a different rom this time one of Jf's early roms i think it was rc33 i tried to apply that but i got a no signature verication failed at the recovery screen so i tried some others. JF's 1.51 and same problem. i read around some more and thought maybe it was because i didnt do alt+W so i tried that with JF's roms and both of the leaked hero roms (i know hero is extremely unstable but i just wanted to see if something entirely differnt would work.) by this time i go into the spl again and saw that the hard spl wasnt loaded any more (i guess the recovery img changes that) i reloaded the recovery img once more and tried to install a the 2nd Ion rom with H's root apps and still the same problem.
i really try to read and search before posting but after 4 hours of nothing i really just want some help. if someone could help me get a working rom on my phone preferably H's new Ion rom and tell me what im doing wrong i'd be endlessly great full.
Im guessing what happend was you did the switch of releasekeys to testkeys and then later redid the DREAIMG.nbh. If so you need to redo the steps involving testkeys. This is why it gives the no signature verification error.
In fact id suggest redoing the whole root process again. starting with the DREAIMG.nbh.

Gmail / Market not booting after Cyanogen upgrade.

I'm trying to upgrade my brother's MT3G from a 1.5 build of cyanogen to a 1.6 build. the latest one, which is I believe is 4.2.5.
When I upgraded my G1 ages ago, I downloaded this file
"signed-dream_devphone_userdebug-ota-14721.zip"
ran it from the from power + home then upgraded cyanogen rom without a problem.
The sapphire equivalent is this:
signed-google_ion-ota-14721.zip
I just finally got around to my brother's MT3G, and when I try to install it I get this error:
assert failed getprop == "sapphire" (status 7)
some tutorials I read listed this one instead, so I tried it...
HTC_ADP_1.6_DRC83_rooted_base.zip
it installed, then I upgraded to 4.2.5 and it booted no problem. But, I can't get Market or Gmail to open now. I thought the last file I listed was supposed to fix that, but apparently not. I'm at a brickwall, I have zero clue what to do to solve this problem.
just did a wipe and reinstalled both zips.
it works now.
HAHA good job buddy
you did the right process the onlything you might have not done right is a full coplete wipe that is the only thing that could've caused you to not get those things to work properly... try again from recovery wipe evrything do it twice to make sure there arent any "crumbs" left behind and then flash the drc83 image tehn the cyanogen....
P.S. there is cyan 4.2.6 out now just a heads up not much differant but appearently bug fixes even though I never had any bugs with cyan 4.2.5

[Q] Need Help! Rogers streak

Hi i just received a streak (Rogers) with 1.6 7921.
I tried all of the recovery images but they all went to a black screen. The only one that seemed to boot was clockwork 1.8.17 but never did anything.
So i tried to install a super boot that has done something bad as after i tried to goto ATT 1.6 as stated in most of the guides i would always get the "write raw image fail with error 7.
now after installing superboot i cannot get back to the stock rogers 1.6 , all i get now is dell logo screen with the home and menu lights flashing.
updating this device is very confusing to me ive followed most things but i suppose im missing something, maybe cause its rogers? maybe someone with a rogers device can help?
can i remove the superboot at least to get it back to booing into android?
Not Android Development
Please post in th correct forum
Moved to General
Ok my rogers streak has baseband 732-us can someone please let me know how i get this to froyo (current 1.6) ive tired almost everything on this site to get it to work, i get as far as it loading te update.pkg but then i get the status 7 assert failed /tmp/boot.img error message.
im trying to goto O2 1.6 which i think is correct.
re root using androot

[Q] HD2 Running Froyo 3.2; Just got a notification of an OTA upgrade but....

Novice Android user here.
Very interesting. Just got a notification for an OTA update on my T-Mobile US HD2 running Froyo 3.2.
I selected to download the upgrade, which the phone did.
A screen then popped up asking if I wanted to install the system SW update. Upgrade version showing on the screen is 2.29.205.2 (28.87 MB).
Tried to select "Install now" but phone just reboots and ends up in the same place.
And will never complete, darnit!
Here is the filename of the upgrade file that was downloaded to the micro SD card.
OTA_Bravo_Froyo_HTC_WWE_2.29.405.2-2.10.405.2_R_P_release8gn61bgo3rswcw24.zip
Is this something useful or old news?
3.2?? hmmm, idk man, probably was not supposed to happen.
It's old. I have heard people talking about this from Darkstones build. I don't think it's even possible to upgrade anyways.
the same but different Froyo build. When tap instal phone reboot and of course load winmo (energy) when run android & situation repeat and loops. So I did ignore this update that's it.

Categories

Resources