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
Related
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.
Hi, I have a MT3G and a G1 before that. I have experience flashing roms and other stuff. I have had the MT3G for sometime and noticed that I can't flash roms anymore since I get FC errors after the boot up. Even the latest CM mods don't let me sign in, and I have to skip the initial sign in to find the market FCing every time I open it. This is getting really annoying, and some roms won't even get past the boot screen without a fix uid mismatches which allows me to boot up, but still gives me some errors, like no android keyboard to sign in or FC on settings or other important things. Any help would be appreciated!
are you wiping the phone completely... list things in your signature like what recovery image what rom you are using at the time are you using a different SPL the community needs to know these kind of things to help you out...
I had this same problem when trying to flash Cyanogens latest.
Go ahead and find version 4.2.1.8 or 4.2.1.9
Wipe everything, then flash one of those.
Everything should work, I would advise not to upgrade to 4.2.12.2 or whatever because I experience home not responding upon reboot. Have to wait a couple times, then it's ok.
Well, I would put it in my sig, but for some reason, I can't edit it. Here's what I've got.
I had the SPL 1.33.2005 then recently 1.33.2009.
I've had problems like this on my G1 as well and never really understood the problem. I have the latest RA v1.5.2 recovery.
I do perform a full wipe and have tried to follow what someone else posted about installing a fresh rom and to fix the apk uid mismatches and a command in terminal, although neither seem to last long. Sometimes I can wipe and do an install of any rom 10 times and still get FC on startup. I fix the apk uid mismatches in recovery to be able to get further, but will usually start to have problems in other settings and apps.
I have a general idea on what to do, and usually wipe the data and everything else about 2 times. I just don't know if it's something I'm doing that's causing this.
I just searched around for the differences of SPL's and read from Amon_RA that they aren't really different besides being able to allow certain roms to run. I'm wondering if the reason I can't run certain roms is because I don't have Haykuro's Death SPL? Is the Death SPL only .2005?
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.
Hi,
So I wanted to upgrade my CM6.1.1 to the stable CM7.
I went to CyanogenMod's wiki for Nexus one as I always did and it says to install the latest radio 5.08.00.04, However I already updated my ClockworkMod to 3.0.0.5 and when trying to flash the radio zip I get this error:
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
After googling a bit I saw understood that my only solution is to downgrade CWM or to flash Amon_RA instead.
Now here's the real problem:
I can't flash to Amon_RA because I won't be able to boot into it. My power button is not functional.
I'm scared to try and downgrade CWM. After some more googling I saw people that claimed downgrading through rom manager did nothing and they still booted to 3.0.0.5, one guy said he got bricked though I don't see how since it's not a radio flash.
Bottom line, the page http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Nexus_One says the latest radio (without saying which one it is) is required for CM7.
Is this true?
Any ideas, thoughts, help, cookies, would be welcome.
p.s.
My Nexus One is originally an AT&T/Rogers nexus if it makes any difference
p.p.s
How come Cyanogen posts instructions to flash a radio that doesn't work on the most recent CWM, is there another version of this radio update.zip that's using Edify?
Try post in the Q&A section
update:
Got over my fears and tried downgrading CWM.
Now trying to flash the radio... Couple of consecutive reboots, my heart skipping a couple of beats...
ok... looks ok... CM (still on 6) is loading...
Takes a long time...
Got the new radio!
Flashing back to CWM 3.0.0.5.
Everything seems to work fine...
will update after upgrading to CM7
Sorry for not posting in the Q&A section.
CM7 loaded fine, everything seems to be in order...
Damn it:
1. For some unexplained reason, Google talk authentication fails, even though contacts and calendar synced fine (so it's not a wrong password or something)
2. The Market is acting funny:
2.1 It won't download anything (same old "failed downloading..)
2.2 Search auto complete shows a list of java.lang.NullPointerException
update:
Had to download Titanium backup .apk manually from the web, push it to the device with adb, only to wipe the data of the market app.
That seemed to fix the market.
For some reason it looks like Google talk authentication is also fixed.. after the market wipe...
weird.
I've never updated my radio, and I've never had a problem with any custom ROMs. I've been running CM7 for a while now with no issues.
Hi,
I managed to mess up my phone by installing Aurora ICS over CM7, therefore issues with connecting to mobile network etc..
Could someone give me link(s) to various official 2.3.5 as i tried some, but i get "Installation Aborted" in return.
Don' t expect to get serious help with these poor info.
Be more specific and give more info about the state of device before flashing ICS, what you have done, in which state the device is now and what you do to flash official 2.3 roms and get the installation aborting error.
for e.g which CM7 you had. There are several versions, some need 2.2 official rom as base and some 2.3 official. Network connected issues appear when you flash a rom which is built for 2.3 official installed as base, and you have original 2.2.
Also when trying to flash the official rom, the 1step( Unpacking process) is successful, or you get only installation aborted error immediately?
I had a gingerbread CM7, idont remember which one.
I get installation aborted at once, when i try to flash through CWM 5.0.2.7
I`ve also tried 5.5.0.4 i think.
EDIT: Think i had a CM7 based on 2.2 Official even if it was Gingerbread, since i flashed it last year before christmas.
just install official 2.3, since it is the base for most ROM's right now.
follow this link, everything is explicit there.
http://forum.xda-developers.com/showthread.php?t=1369296
hope it helps
BRB gonna test something out!..
Think i fixed it now...
Had to boot into purple screen to transfer the update file to the phone, than unpacked in ICS and rebooted into purple screen again.
Looks like it`s trying to install now.
i hope you solved this.