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.
Related
So, I have just made a couple of changes to my phone. My mistake is that I did it all at the same time. So I dont know what fu***ed it up !
1. I formated the ext2 partition to ext3
2. I added a linux Swap partition (104Mb)
3. I loaded the CN 1.4 Recovery image
3. I installed the SPL 1.33.2005
I have been using JF 1.51 and I was having some issues after a recent corruption so I thought I will try JacHero 1.7 since I was planning on a clean install anyway. So the new SPL was for the Jachero rom.
Anyway, why i think the issue happened while flashing the SPL its because after I flashed the CN Recovery screen came up and it said "Formatting Cache" and it stayed on that screen for like 15 min. and I thought ok, it must be done and the Recovery menu was active so I just scrolled to reboot after which I was never able to boot past T-Mobile G1 screen.
I did eventually update to JacHero 1.7 after a wipe but still didnt seem to work. Still stuck at boot screen.
Any ideas ?
Any help is appreciated !!
Thanks.
If its the spl I know that one if I rem was the tricky one that couldnt be downgraded or so.
http://forum.xda-developers.com/showthread.php?t=517593 is the only thread on top of my head I can link you to. Hopefully it helps.
Sometimes the only way the danger spl will take is if you rename it to update.zip and click on apply sdcard update zip. Try doing that and see, also try a non hero rom and see if it boots, if it does and a hero won't chances are it was the spl
ITS WORKING !!
So I kept on messing around, I went into the SPL settings pressed lots of keys (not much clue wut i was doing) and I tried a couple of restarts and after messing around with everything.......somehow it booted into the new Hero rom (Dont ask me how !) but it was completely screwed up. Meaning, This HTC screen is the only thing I can see. If i turn off the screen and turn it back on, I will see the unlock screen of Hero (which looked really cool) but as soon as I unlock im back to this wierd HTC black screen where nothing happens!!.
Soooo I went back into the recovery mode and tried the nandroid restore option (AGAIN) only this time it went through and completed the recovery ! (It wouldnt do that the last 3 times i tried) and now I back to my JF 1.51
Not really sure if I still want to try Hero anymore
and thanks alot guys for your quick responses......I REALLY Appreciate it.
Thanks again for your help !
It's up to you, cyanogen just came out with donut in his expermental line of roms so now we are gonna be passed cupcake roms soon
Ive got a bit of a problem. I didn't read things over carefully and didn't realize i had HBOOT 1.33.0010 from Rogers in Canada...
So I booted into RA recovery 1.2.3H and loaded cyanogen 4.2.13 onto my magic. Now whenever I startup or go to market i get an error "com.google.process.gapps has stopped working" force quit and im not able to download anything.
Did I screw up by not working around the perfect GPL first and how do I fix this? Thanks in advance for the help
You need to flash the base defanged before you flash the CM build. Read the Cyanogen Wiki
Go to Installing Tutorial, choose your device, and follow the instructions.
What SPL should you have to flash a rom
Cyanogen's roms does not require you to have an engineering spl. So you're good with stock.
This may be a stupid question...but how do you know when you have root? and is it possible to load another rom onto the device without root?
You would know if you have root. You have to go through a process to get it. And no, you can not install another rom without it. Google how to root your phone. Takes 2 mins.
Oh...well I flashed another rom onto my magic and everything works great now. I guess I do have root. Sorry for the bother and thanks all for the responses.
Hi guys, I'm pretty new here so I hope someone can help me.
I am having serious issues trying to load ANY new ROM onto my missus HTC Vodafone Magic 32B Details -
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0004 (SAP10000)
CPLD-10
RADIO-2.22.19.26I
Apr 9 2009,23:30:40
Since getting the phone second hand from eBay it has played up like nothing else, it now will not even boot into the OS, I’m pretty sure the guy I bought it from, who I cannot get in contact with, stuffed something up when he unlocked it for different carriers. But I'm positive it is an OS issue and not a straight hardware fault.
Anyway I have spent about a day and a half mucking about on here trying things and reading a HEAP of stuff and I just can’t seem find a definitive answer to my problem.
I have tried installing many different roms:
Qteknology Hero (WWE Dump) for G2 Magic-Voda 32B v1.7 Swap
Qteknology Hero (WWE Dump) for G2 Magic-Voda 32B v1.6 Swap.zip
st0kes-v1.4.1
HTC_Magic_Vodafone_AU_Original_ROM
and a few others I cannot remember.
I am using Amon RA recovery ROM, I have rooted the phone based on method 2 in the magic rooting wiki (everything went smoothly), I have updated the SPL to version 2005 which are all the apparent pre requisites for performing this kind of operation.
Anyway down to the problem every time I try and apply a ROM, by renaming it to update.zip, copying it to the root of my SD card, then loading up RA recovery ROM and going to flash zip from SDcard I get the following messages:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Install from sdcard...
finding update package...
opening update package...
verifying update package...
E:corrupt file:
<various file names based on which ROM I’m trying to use, always the same one on each ROM though>
E:verification failed
Installation aborted
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This is starting to drive me insane, I really need to get ANY usable ROM on there I don’t care which one, otherwise I have a AU$400 lump of useless technology.
Any help people can provide me with be unbelievably appreciated.
Thanks in advance
i cant guarantee i can help, but i will try to see if i can, or also help wit some research for ya
first, what version of amon ra are you using???
2nd, do you know if you got 1.5 or 1.6 firmware???
idk too much about firmware, all i know is my mytouch was cupcake when i got it (1.5) then updated to 1.6 ota...
also are you making sure that you wipe before you try to load the roms???
Hi mate, thanks for getting back to me so quickly
The version of amon ra i am using is recovery-RA-sapphire-v1.6.2G.img this seemed to be the right one as i have a google branded phone
I am not sure what version of firmware i have, is there an easy way to check? the only real details I have is what i get from the fastboot screen as i posted above
And yes I am definately wiping the phone before I install the roms, every single time
Thanks
well i just did a few searches and i couldn't find out how to check the firmware...
i dont want to tell you to try something and then crash your system, but...lol...
i would try to "Unroot" the device, basically placing it back to 1.5 firmware and then you can "Root" it yourself.
if you want to try this here is the link for the 1.5 software
link for tutorial:
http://theunlockr .com/2009/08/22/how-to-unroot-your-mytouch-3g/
link for file:
http://www.megaupload .com/?d=BLM4EDGE
no space in the url tho...
all you have to do is,
boot into recovery
go to wipe, and wipe the top three options
go back to the main screen and select Usb-Ms toggle
then plug your device in via usb
and drop the file to your sd card. (not in a sub folder)
then safely remove your phone from pc
then press home on your phone to disable usb
then choose power off.
now to turn it back on,
holding Volume "Down" + "Power"
DON'T PRESS ANYTHING YET
after it reads the image it should show at the bottom, Action:yes, and then click trackball,
let that run all the way thru, and make sure you have enough battery juice, for this to run all the way thru.
when it's complete it will ask if you want reboot, then click Action for yes (trackball)
i believe that should unroot your phone but PLEASE PLEASE PLEASE
do as much research as possible and also question others about this method and see if you can come to a conclusion in which you are satisfied.
as always, i am in no way responsible for the Bricking or Exploding of your device...
here is a link that has great tutorials & and also you might want to check youtube, thats where i findout how to alot of things...
Um, you already have amon ra recovery on there. I assume you've already bought it rooted?
You can only check the firmware by booting up your phone and going into settings. Since you've wiped and aren't able to install a rom, you aren't able to use the phone right now, am i correct?
sanman1185, I'm glad you try to help but you gotta get more info from him first. Cause if he's already rooted, doing what you're telling him to do won't make much progress. Edit: Ok, he's already rooted. You're just telling him to do what he's already done? And he doesn't have any firmware because his phone lacks any rom right now.
Anyways, answer some of those and don't be too worried about bricking your phone. The main reason that people brick their phones is when they touch the radio and SPL.
Edit: Ok I just read that you rooted your phone so you don't need to "unroot" and root it again.
You also put on SPL 2005 instead, so post your boot info again. I assume it's an ENG SPL too, if you haven't found a solution, send me a PM and I'll help you on google talk / MSN or something.
Ps. You don't have to rename the roms to update.zip, his new recovery allows you to flash w/e zip you want. Try another SD card as well, maybe that'll help? but if not, yeah just pm me
KAwAtA - def. understand what your sayin, only reason i was thinkin to unroot and start fresh is cuz, when i started flashin roms, i ended up being stuck on the boot screen for over 30mins. pulled the battery, then read somewhere to partition sd card, then that wiped the zip from my card, lol...so what i did instead of placing another rom on the device, is "unrooted" and started fresh from the start. my theory is if you think your "Jack'd" then start from the beginning and find your mistake.
and if he did unroot and it ran Cupcake on device, and actually loaded wouldn't that have been making progress??? since he couldnt get it to load in the first place???
like i said just a thought, theory, or 2centz (sense)...
but again, i'm glad someone actually responded with a diff method or with additional ?'s, so this way he can get answers from all angle's ya kno...
and if you guys do figure this nifty lil'thang out, could you post what you guys did on here, so myself or future ppl'z that may run into this can have it as a ref??? thnx... Pce
starting a couple days ago, my g1 would restart on boot for no reason. It gets into the phone OS and says preparing SD card and then it vibrates and restarts. I've even unrooted my g1 and rerooted just to make sure everything is perfect and nothing is wrong using the cyanogenmod wiki. I have the latest radio/dangerSPL yet this keeps happening. my phone only boots when its not rooted in 1.5 or 1.6. I'd give more info, but I need some help doing that. I even made a useless video for you to watch my problems. http://www.youtube.com/watch?v=kyAOAPAhq2U
I'm assuming you're not overclocked since you haven't got into the os to set anything up. What rom are you trying to use? Prob. be a good idea to post your fastboot info. A useful thread that might help getting into fastboot and learning the commands to flash through fastboot.
http://forum.xda-developers.com/showthread.php?t=532719
Another question: What SPL do you have installed / what is you space on /system? You have to use DangerSPL, or better: 1.33.2003 in combination with the custom-MTD method to get cm6 running. (Links can be found in my signature)
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Undeadllama said:
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Click to expand...
Click to collapse
You'll need a goldcard and an RUU. Look up how to make a goldcard and let me know when you have one
Wow, thanks for the quick reply
I did try creating a goldcard yesterday (using android.modaco.com/content/software/308798/pc-application-goldcardtool/). So assume I DO have one for the time being...
however if it doesn't work and I need to create a new goldcard:
Since I can't get into adb or boot up android and therefore can't access my sd card through my phone I presume il have to go out and buy a cheap card reader tomorrow.
Also, I have to run this command again:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
But if I can't get into adb how would I go about doing this, can I get the CID of the sd card from a card reader?
As for the RUU, there's many to choose from on shipped-roms.com, does this sound about right?
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe
Thank you so much for your help.
This this a decent guide from Paul over at MoDaCo.
Ok disregard my last post about a card reader... I managed to borrow a friends android phone since it appears goldcard's are specific to the sd card, not the phone. So after following the instructions I now definitely have a goldcard.
Also have the RUU mentioned in the previous post.
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35. 15.19_release_130442_signed.exe
Is this right, and what do I do with these now to get them on my phone? Ive tried running the RUU whilst in Hboot and in recovery but it wont recognise my phone, presumably because adb isn't working.
Thanks again for the help.
There is another way to do it when it can only get into hboot. I'll look today for the method and let you know.
Sent from my HTC Wildfire using XDA App
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Undeadllama said:
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Click to expand...
Click to collapse
Yeah that's the method I was going to suggest, glad you sorted it out.
It's the fact that they lock out fastboot and stuff. If we had S-OFF from the factory, fixing these things would be so much easier
Hi,
how were you able to do this?
"Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system. "
Thanks