So today i finally get the gusto mod my phone Android Dev 1. After downloading all the files and following the instructions here i can't get past the black g1 screen (#8). note i can also get the the rgb screen. thats it, but with so many different posts with similar issues, my brain is pounding. At this point if i can get beack to factory, ill live. what i'll hate is the fact that bricked my phone. i'll most likely get screamed on for not searching, but i think i may be searched out. any help would be appreciated.
thanks.
docfu.
first of all dont freak out lol. Download the dreaming.nbh or w/e file from the rooting instructions and place it at the root of the sdcard. Then get into the rgb screen (Camera + Power) and flash it. That should get you back to factory settings. If not, download the update.zip for w/e region you are in place it on your sd card. Enter recovery (Home + Power) and flash the update.
ok...so i tried the DREAMING file and it kept turning up no image found, alternatively i'm not sure what you mean by w/e region update. i ihavent come across that in my searches.
ok dreaming file did infact work. i feel better knowing that the phone isnt bricked. however after running the update when it prompts for action, i hit the trackball and i'm right back at the rgb screen..AGGGHHHH! sorry. i've been at this since 3pm this afternoon.
Chill. Don't freak. You can't just jump in and do something as soon as your read it. Read the whole thing and if you don't have the patients for this work on that before you work on this. bbreath.
I must say start by saying thanks guys. i stepped back, and actually took my [email protected]@ to bed. Rest does wonders. That said. I've accomplished the factory reset. so i back to a stock g1, and boy does it suck. As stated my phone WAS a dev 1. i've already started the upgrade process, my question at this point is where do you recommend i go from here. back to dev 1 or try one of the other roms. i've already installed the spl, and right now im stuck at the telnetd part of the root process. and this too may have me screaming by the end of the day...
any thoughts would be appreciated.
After the recovery image is installed you need to update the radio if you want to install a cupcake 1.5 ROM. You can get it here, rename 'update.zip', place on the SD card and boot in to recovery and flash. Then flash a ROM of your choice. You should be able to do that on RC 30, but I'm not sure if you need to install a rooted image first, so I'd wait for someone else's input before trying that.
I played it extra safe and used the rc29. as far as i know the proper radio is installed. i'll wait around before i do something stupid. thanks for the input tho. i'm trying to learn everything.
ok...so i went back to the original method for obtaining root. i was so frustrated last nite that i ended up trying to combine 2 slightly diff methods. at this point i call them the telnetd method and root.apk method. correct me if im wrong but niether one mentions the other. so i make it to the bootloader running the root.apk it runs thru the list and the fails at radio_v2. now im on the white screen wuth the skateboarders, the radio #says 1.22.12.29. so i run it again i
now im on the rgb screen at proceeds to attept the update again. this time the dreaimg.nbh fails. i'm not freaking out. im good. because i know im almost there. feedback appreciated. thanks in advance.
y'know i never thought about this..but if i reverted a dev phone to factory settings...did i relock everything? and for the record, i only have a mac. if that matters at all.
Future reference ^-^
In case you encounter this problem in the future, cause it can happen with flashing new roms if you skip a step:
You're only bricked if you are stuck at the G1 boot screen but can't get into recovery or fastboot, adb or anything. In cases where you can still get to other phone options to start over, rest assured your phone does still work, just need to step back and figure it out, which you did in this case with a little help ^-^ First few times doing anything to my phone, I went into panic mode a couple of times thinking I bricked until I read around and found out otherwise.
Just in case you didn't know these things, if you did, well, hope it was a nice read? ^-^
doctorfugazi said:
ok...so i went back to the original method for obtaining root. i was so frustrated last nite that i ended up trying to combine 2 slightly diff methods. at this point i call them the telnetd method and root.apk method. correct me if im wrong but niether one mentions the other. so i make it to the bootloader running the root.apk it runs thru the list and the fails at radio_v2. now im on the white screen wuth the skateboarders, the radio #says 1.22.12.29. so i run it again i
now im on the rgb screen at proceeds to attept the update again. this time the dreaimg.nbh fails. i'm not freaking out. im good. because i know im almost there. feedback appreciated. thanks in advance.
y'know i never thought about this..but if i reverted a dev phone to factory settings...did i relock everything? and for the record, i only have a mac. if that matters at all.
Click to expand...
Click to collapse
Well... if you actually purchased a dev phone it should not be sim locked.
Technically... after the rooting process, we all have dev phones with the exception of the sim lock.
So... what SPL are you using?
What ROM are you trying to install? Some roms you should consider partitioning your sdcard.
What radio do you have?
First thing is first.
Get the 1.4 recovery if you haven't done so already. 1.4 Recovery
Because this allows you to select any .zip file without having to rename it to update.zip. This saves on confusion so you don't try flashing a spl (like danger spl )before a radio (could brick your phone).
Second
You need the 1.5 radio to use cupcake. 2.22.19.26I
Third
Consider an spl. You have 4 choices. HARDSPL (Recommended), Eng SPL (what the dev phone defaults with.. skateboarding androids), the standard spl (nondev) and Danger SPL (risk bricking but worth it because you have more memory for your ROMs and can try HERO builds).
Fouth
Find your rom. NOTE: Read each post carefully! If it says you need a specific spl then get it! Otherwise it won't work. Some require the Danger SPL. If you chose a JF rom then you should be alright and don't even need to partition your card and it will work just like the OTA release. Some (such as Cyanogens 3.9.7) are experiemental and are not recommended for noobs.
Fifth (and probably the most important)
ALWAYS BACKUP WITH NANDROID!!!
In the event that you think that you've bricked your phone. I would say that there is a 90% chance that you didn't. As long as you have a nandroid backup and can get to the bootloader then you still have a phone. Just make sure the fastboot.exe file is in your sytem32 directory of your computer. Open CMD and cd to your fastboot backups saved on your computer. Simply
fastboot flash boot boot.img <enter>,
fastboot flash system system.img <enter>,
fastboot flash userdata data.img <enter>
fastboot reboot <enter>
and you should be back to where you were immediately after the point you backed up. Think of it as a system restore for Windows. It couldn't hurt to have a few backups stored.
If you have any questions or problems include information for us to read in a single post and edit as necessary.
Example:
AT&T
Cyanogen 3.9.7 Rom
Recovery 1.4
HARD SPL
Radio 2.22.19.26l
8GB class 4 sd card (7gb fat32/900mb ext3/100mb swap)
Theme version if any.
That way we know what we are working with.
Happy flashing.
rest assured i was in panic mode yesterday. but honestly the only thing i could really do was just step back for a while, meaning get some rest tackle it with a clean head. its frustrating for sure. this one guy tho who posted in the brick think tank thread...just cuz he couldnt figure things out in an hour he got pissed and started screaming waste of time this that and the other. total BI$CH! I was like whoa. I was at that point too. but Im not tryna be that guy.
Now, if could just figure out if i have to start from scratch, i just might be able to get my phone working again in time fro me to go to work tmrw morning.
So... what SPL are you using?
the hard SPL found here
What ROM are you trying to install?
Well i was trying to follow suggestion on something simple, like one of the early jesusfreke's. if i can step it up sure why not. but i'll pass on the partitioned sdcard setup for now.
actually I'll run with JesusFreke JFv1.51 US CRB43
What radio do you have?
radio number listed in my previous post.
Hey thanks by the way for taking the time out of your day to respond to this. i know u guys get your fair share of spazmiesters, so i appreciate it totally.
after doing research it seems that all the current roms require partitioning. or is that optional just for running apps to sd?
partitioning is optional of apps2sd for preformance. some like myself have three partitions, the third being for a linux swap
Ok ive final decided on the dudes cupcake 101. the ? i have now is do i start from scratch. im kind of in limbo as i'm stuck on the bootloader. if remember correctly i got half way thru the root process and it went down hill from there.
TMobile
RC29 / previously Dev 1
Recovery 1.4
HARD SPL
Radio currently 1.22.12.29 / trying to get to 2.22.19.26l
4gb card
(hope i did that right)
doctorfugazi said:
Ok ive final decided on the dudes cupcake 101. the ? i have now is do i start from scratch. im kind of in limbo as i'm stuck on the bootloader. if remember correctly i got half way thru the root process and it went down hill from there.
TMobile
RC29 / previously Dev 1
Recovery 1.4
HARD SPL
Radio currently 1.22.12.29 / trying to get to 2.22.19.26l
4gb card
(hope i did that right)
Click to expand...
Click to collapse
Okay... you have the recommended recovery and spl.
So all you need to do is get your rom and radio and store the zip files to the root of your sdcard. You don't need to rename them.
Just boot in recovery (power+home) and scroll down to:
[Alt+A] apply any zip from sd
And then you should see the zip files.
Upgrade your radio first.
Then your rom.
Another note... make sure you have a data plan once you've installed your rom. Depending on your rom version, you may not be able to sign in without one. If you can't sign in, you can't use your phone which is why most would recommend a custom rom or an adp rom.
Now... if I'm not mistaken... you do NOT have to partition your sdcard to install a rom (unless it's a HERO rom).
You may want to consider doing so however.
The advantages are that you can have virtually unlimited storage for apps and it's much easier to restore them after a wipe because they are still on your sdcard. Some apps will recognize the partitioned sdcard and automatically do all the apps2sd work for you by default. It is also recommended that you use at least a 2gb class4 card at MINIMUM. Any slower then a class 4 may result in system crashes and errors. Any less then a 2gb card is almost not worth all the effort since you'll likely be using at least a quarter of it for the apps2sd. I would suggest buying at least a 8gb class 6 card for less then $50 online. It's both fast and plenty of storage. With apps to sd, if you do need to wipe you still have all of your apps installed. A great advantage of having apps2sd.
Also... try different roms! There are DOZENS out there! Some have the htc music installed, some have myfaves, some have special cameras, etc. Don't be afraid to experiment. As long as you have a backup and can get to the bootloader (skateboarding androids) and a pc, you can't go wrong! If fact... with the 1.4 recovery you can store several different roms on your sdcard, backup your current rom, wipe, flash a new rom to try it, wipe, flash a different rom to try that one, etc. If you decide that you didn't like any of those... just restore back to your previous backup. Simple as that. No pc needed. However having a pc is handy to get logcat information if it's not booting for some reason.
Speaking of roms not booting... while your experimenting with various roms... you MUST have patience. Sometimes (based on my personal experience with about 10+ different roms) they can take up to 15 minutes to boot up. You can literally be staring at the ANDROID or HTC logo this entire time. Unless you are using ddms.bat or adb shell logcat, you will be clueless of whats going on. DO NOT do anything unless you get the infamous "boot loop". This will be obvious. It will stick at the ANDROID or HTC screen for a while and then blink and go back to the logo. If you see it blink and go back to the logo then try pressing power + talk + menu to restart it and then immediately press the home button to bo back to recovery. Wipe... try again. This time it should work. If it doesn't then restore your backup while you research on that partitcular rom. You may have skipped a step or not have the proper requirements (partitioned card, spl, etc).
With all of that said... good luck and you'll be posting help to other users like yourself before you know it.
Hey Doc, if I'm not mistaken (other guys correct me if I'm wrong), if all, and I mean ALL you have is a boot loader (AKA SPL. ie// skating androids or colored bars) you need to reflash dreaimg.nbh to get a system back.
This ALSO flashes your SPL and RADIO back to default so reflash your radio and SPL afterward. (IN THAT ORDER I HOPE)
Binary100100 is a gentleman and a scholar
nicely written response binary.
I can't stress enough how helpful it is to have the sdk working on a computer when flashing new roms. Get ADB working, it'll save you a ton of headaches.
innerspace said:
nicely written response binary.
I can't stress enough how helpful it is to have the sdk working on a computer when flashing new roms. Get ADB working, it'll save you a ton of headaches.
Click to expand...
Click to collapse
Thank you! I do what I can.
Related
ok - i have a G1 ... fully functional etc
anyway - i started looking into putting SenseUI on it - and then about 15mins ago came across the cyanogen thread and became very intrigured....
i have a couple questions
1. with the latest release of the ROM, is the phone fully functional?? - no restrictions etc? tmo doesnt mind or restrict you etc? - i still want all features working
2. is there a step by step on installing the rom? - i looked around a bit but found multiple conflicting instructions/recommendations -
3. WORST case scenario, can i always go right back to where im at now? - official tmo/google release, fully functional, normal g1? - or am i stuck
my biggest concern is ruining the phone - im just getting in to G1 editing etc - ive always been too nervous because its my main phone and only phone - but i used to do all kinds of crazy things with my old blackberry - beta releases from overseas etc etc - just havent gotten the balls to mess with my g1
but ill be honest, i hate the iphone (not sure why) - but im getting kind of fed up with the G1 - i love it, dont get me wrong - but the add-ons/functions i read in cyans rom intrigured me a lot
so with all this being said - please answer my questions listed above
i dont care so much about the files/apps - i can always re-download the apps i use etc... and the pics/vids i can back up to my pc
thanks in advance!!!!
the current stable release of cyanogen's rom in 4.0.1 and it is very stable and much faster than stock cupcake. the only thing missing as far as i can tell is the myfaves app. but i do not care bc i can update that online. everything in market works. plus many extras from donut.
are you rooted? if not, go to the market.
search for recovery flasher.
download it.
then go to cyanogen's thread and download 4.0.1.
put it on the root of your sdcard (upmost folder).
use the recovery flasher app to apply cyanogen's recovery image 1.4 on your phone.
power off your phone.
hold home and power to boot into recovery.
it should have a green android with text in front of it.
go to flash any .zip.
select the 4.0.1 file you put on your sdcard from above.
hit home to apply it.
after it finishes and tells you to reboot the phone then select reboot phone on the menu.
let the phone boot up.
may take 5 to 10 minutes.
then look into partitioning your sdcard for apps2sd and a linux-swap partition if you want those options.
yes you can easily revert the phone to stock rom like you never rooted it.
when you boot the phone up the first time, if you get a lot of force closes then boot into recovery.
go to the recovery console
hit enter
type fix_permissions
then type reboot
if that does not work then you will have to wipe the phone from the recovery menu and re-flash the rom
any other questions
trying it now - (crosses fingers)
its been on the NEW adroid splash screen ( the one with the android on a skateboard) for a while now... it stops highlighting once in a while and flashes off - then starts again... its been about 7-8mins i think..... is this normal?
got it!
thanks!!!
your welcome. did you have root or did you use the recovery flasher app? because if you used the recovery flasher app there is a quick question i have
i didnt have root at all prior to me trying this tonight
something i would try. power your phone down. hold the camera button and power button (this boots up into bootloader) if you get a rainbow screen then you will want to flash the hard spl(androids on skateboards with a white background). so you can you use fastboot. here is where you can get the hard spl. just boot into recovery and flash it. i do not know if flashing the hard spl will wipe your phone like flashing haykuro's spl will, but you would much rather have the hard spl than not having it so the pros far outweigh the cons. welcome to your newly rooted phone. if you have any questions feel free to pm me and i will do my best to answer them.
david1171 said:
something i would try. power your phone down. hold the camera button and power button (this boots up into bootloader) if you get a rainbow screen then you will want to flash the hard spl(androids on skateboards with a white background). so you can you use fastboot. here is where you can get the hard spl. just boot into recovery and flash it. i do not know if flashing the hard spl will wipe your phone like flashing haykuro's spl will, but you would much rather have the hard spl than not having it so the pros far outweigh the cons. welcome to your newly rooted phone. if you have any questions feel free to pm me and i will do my best to answer them.
Click to expand...
Click to collapse
Thanks for the step by step guide David...
I would like to ask a question on ROM types. I am currently using JF's 1.51. I have no problem with this (occasional force closes, which I suspect is from the SetCPU app). I have hearing lots of updates from CyanogenMod's ROM. What are the main differences? From your experience, what do you think are the disadvantages of CyanogenMod's ROM versus JF's 1.51? Would appreciate any help you can give. Thanks
erlern said:
From your experience, what do you think are the disadvantages of CyanogenMod's ROM versus JF's 1.51? Would appreciate any help you can give. Thanks
Click to expand...
Click to collapse
sorry i almost cried when i saw disadvantages lol.
1 you do not have to overclock bc the phone is set up to overclock when it needs it and to underclock when it doesn't need it.
2 apps2sd is automatic if you have a second partition. there's a great guide for easily partition your phone with cyanogen's 1.31+ recovery image.
3 many cool things from donut.
4 a lot of themes are made for cm roms
5 a lot of stuff too much for me to list
if you really want to try it just get his latest recovery image. download 4.0.1 or whatever the latest stable release is. make a nandroid back up. flash the rom, and if you don't like it, or want to go back to JF then you can easily
David, Thanks for this. Just for kicks. If i want to reset to the factory defaults all I need to select is the "wipe data/factory reset" from recovery?
I think my post just disappeared...anyway... David, Just for kicks, If I need the phone back to original settings, I need to select the "wipe data/factory default" option in recovery? This will keep the new recovery method, just deletes the rom?
You will keep the recovery image. Yes it will just clear you data and stuff off the phone. Things like recovery image, SPL, and radio do not get wiped. If you do wipe just reflash a rom and you will be good to go.
PHP:
david1171 said:
sorry i almost cried when i saw disadvantages lol.
1 you do not have to overclock bc the phone is set up to overclock when it needs it and to underclock when it doesn't need it.
2 apps2sd is automatic if you have a second partition. there's a great guide for easily partition your phone with cyanogen's 1.31+ recovery image.
3 many cool things from donut.
4 a lot of themes are made for cm roms
5 a lot of stuff too much for me to list
if you really want to try it just get his latest recovery image. download 4.0.1 or whatever the latest stable release is. make a nandroid back up. flash the rom, and if you don't like it, or want to go back to JF then you can easily
Click to expand...
Click to collapse
I like your SPL on your signiture. Im guessing its the danger SPL
Yeah it references the danger spl lol. I think thats the feeling that anyone gets when flashing it. I know i was like i really hope this works or i'm going to be sad.
Original question(s) seem to be solved.
Closing thread
I apparently screwed some things up in my attempt to upgrade to Cyanogenmod 4.1.99 so I can move to 4.2.3. . . anyway, I now have the HTC bootloader up with fastboot, the standard Android recovery, and HTC ADP 1.6 DRC83 firmware installed, and its up and running. I don't have root, and I am completely lost as to how to get root back, get cm-recovery 1.4 back, and from there, I should be ok...
I do have DREAMING.nbh on my sd, and when i go into fastboot(pwr+camera) It gives me a list:
Parsing. . .[DREAMING.nbh]
[1] BOOTLOADER
[2] RECOVERY
[3] BOOT
[4] SPLASH1
[5] SYSTEM
[6] USERDATA
[7] RADIO_V2
Do you want to start update?
<ACTION> Yes
<Power> No
This is where I don't know if I should do anything without advice, as I don't want to brick my G1 any further
Anyone care to help out?
if you messed up like i did a few months back , and lost root because you flashed the htc recovery image and didn't flash cyan's rom on top of it then...i can help. i'm assuming you lost root on your rom because of that, and when you rebooted it took out cyan's recovery image as well, so you can no longer flash anything else into your phone. Alright! first thing's first, is we need to have a look at what spl you're using, take out that dreaming.nbh file from your sd, you won't need it, instead, put on a recovery image like cyanogen's 1.4 or amon ra's 1.2.3 (i suggest the latter)
anyways , you're gonna have to have the hard spl/ engineering spl/ or the haykuro "death/danger" spl installed on your phone. I'm going to assume you have at least one of these, because if you don't and you have the stock spl that's a different story. If you have the stock spl for some reason, you are gonna have to downgrade your phone like you did when you first got root. Research the forums , there are loads of guides on how to downgrade your phone, go to the section that specifically talks about using the bootloader to restore the dreaming.nbh file.
if you do have either the hardspl, death, or engineering's spl,
you need to search the forums on how to use fastboot and adb
you're gonna need to push the recovery image file (cyan's or amon_ra's)
into your phone and wahpow!
you're in the green, once you have the recovery image back in the phone, you can boot into it and flash w.e the hell you want
phamous said:
if you messed up like i did a few months back , and lost root because you flashed the htc recovery image and didn't flash cyan's rom on top of it then...i can help. i'm assuming you lost root on your rom because of that, and when you rebooted it took out cyan's recovery image as well, so you can no longer flash anything else into your phone. Alright! first thing's first, is we need to have a look at what spl you're using, take out that dreaming.nbh file from your sd, you won't need it, instead, put on a recovery image like cyanogen's 1.4 or amon ra's 1.2.3 (i suggest the latter)
Click to expand...
Click to collapse
You hit the nail on the head!
phamous said:
anyways , you're gonna have to have the hard spl/ engineering spl/ or the haykuro "death/danger" spl installed on your phone. I'm going to assume you have at least one of these, because if you don't and you have the stock spl that's a different story. If you have the stock spl for some reason, you are gonna have to downgrade your phone like you did when you first got root. Research the forums , there are loads of guides on how to downgrade your phone, go to the section that specifically talks about using the bootloader to restore the dreaming.nbh file.
if you do have either the hardspl, death, or engineering's spl,
you need to search the forums on how to use fastboot and adb
you're gonna need to push the recovery image file (cyan's or amon_ra's)
into your phone and wahpow!
you're in the green, once you have the recovery image back in the phone, you can boot into it and flash w.e the hell you want
Click to expand...
Click to collapse
I know that I had HardSPL on at one time, would everything that has happened somehow remove it, and how can I check if its still there?
I will likely use Cyanogen's recovery. If possible, link me to a good "howto" on loading Cyanogen from Fastboot.
alright, to check what spl you have, turn off your phone and hold camera and the power on button,
you'll go into your bootloader, and it will display what spl you're running
it's been a while since i remember what numbers belong to what spl, but as long as you don't see the multicolored spl, and you see like three little android bugs on the bottom, you're good to go
uhm i kinda saved random links to things that i used, you're gonna have to read all these documents and learn all about adb, it's worth it in the long run, and there's no better time to learn it now since it's your only hope of getting root back.
http://androidcommunity.com/forums/f10/adb-fastboot-for-rookies-18124/
http://forum.xda-developers.com/showthread.php?t=502010
BUT ANYWAYS
OMG i just found the best guide to your problem right here
http://wiki.cyanogenmod.com/index.php/RE-recovery-img
^^ that is GOLD!
hope this helps buddy!
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.261
Apr 20 2009, 15:30:43
Thats all it gives me, but there are 3 Androids on skateboards at the bottom, and its a all white screen.
I cant seem to get the SDK to work, let alone install on my PC here(Damnit Vista, I can't wait for my copy of Win7 Pro to get here!!!!) so I might just let it charge up overnight, check here in the morning and give it a whirl on my laptop with XP. Hopefully, I can get this all taken care of. You have been a world of help so far. Just keep an eye out for some updates here tomorrow.
SAME HERE wow, couldn't get the damn sdk to work on vista either
GO XP
that's what i did, worked instantly, find someone with xp and ask them to let you borrow it for about an hour
----
you have an appropriate spl btw, it'll be able to fastboot correctly
in the meantime, i'd read up on those links i sent you, especially the last one,
and you'll be good!
goodluck!
ok, looks like I got the SDK to work on here, and I have it updating right now. Its first update was the USB driver. If anyone has some time, and wants to send me a IM over AIM to help me out with this, please IM me.
I am going to let this update, and then hope that I can get it to flash cm-recovery back onto the phone.
cm-recovery 1.4 is BACK! OK! AWESOME
god this had me abit scared.
Ok, back to the prior task at hand. at this point, can I update to CyanogenMod 4.1.99 then update to 4.2.3, or can I update this directly to 4.2.3?
ok, you cant update directly to 4.2.3 XD
Ok, awesome, ive got cm-recovery 1.4, and Cyanogenmod 4.2.3.1 up and running. Time to give Cyanogen some credit. this firmware is FAST!
Also, I want to thank everyone that has helped out with my issue. you are all worthy of a beer...I just aint got any money to pay for a beer for you all right now XD
Every time I try to flash a Hero ROM, I get an error of sorts during the copy file portion saying that a "xbin" file of sorts is missing. I had JACxROM on the phone, and tried to go from that to a Hero ROM, with no avail. I just flashed to the newest CyanogenMOD no problem(I did flash the HTC ADP 1.6 recovery img first)
I have the newest radio, deathSPL, as well I have the RA1.2.3 recovery image. Is there something I am missing here?
Do I need to downgrade to 1.5, since as it stands I am running 1.6 ROMs?
Or is it likely something else was a "bad flash" and I should just go back to R29, and work my way forward from there?
are you sure you have the "death/danger" spl installed on your phone? make sure, but even if you don't, why not just install it again, it repartitions the phone memory, and makes it clean when you flash things on top of it.
that's the most common problem for xbin errors when flashing a hero rom , it's too big to fit in the stock system memory alone. Try re-doing everything. Make sure your ext partition is clean (format that) , do a wipe to clear cache/data, repair ext partition,
and if all else fails, maybe you might just wanna repartition your sd card, might have broken/corrupted partitions.
maybe you might even have a broken sd card. and you might have to get a new one
lotta maybe's , but try trouble shooting random things.
hope you can find your answer, noone can exactly help you with this one with any sorta direct guide or how two since they're not there to deal with your phone on site
goodluck flashing!
Thank you! I figured it could be one of many things... I am starting fresh, doing RC29 forward.
I am certain I had death, et al, I have been a bit of a lurker for a while on the Android end, and finally got a G1 about a week ago, so I don't have a lot of experience with it, but I have over a year with a Kaiser, and for several months I ran Android on it.
I tried a couple differnt SD cards, and unless both are dead, I think it is just a bad flash somewhere along the way that didn't show up until that broken file system got tested with a Hero flash.
Anyways, I am confident I will get it sorted out eventually. I am smart enough to not brick the damn thing...fingers crossed... not really, I should be all good.
YAY!!!!!!!!!!!!!!!1
I think my first time through I didn't wipe at some point I should have.
I bought a G1 2 days ago and i've been reading a lots of tutorials on how to root the phone, i have hacked/Modified every phone i've had so far (Motorola/Sony Ericsson/Nokia) and i would like to do the same with my G1 (That;s why i bought it for) the problem is that every tutorial i see wants me to downgrade to RC29 which isn't complicated but the problem is that it has the DMD64 update.
1- Is the rooting process the same for DMD64 or do i need something special to downgrade? i read about the goldcard but i also heard it was not necessary all the time.
2- Since this is my first time rooting , is there a way to make sure i don't brick my phone? like making a backup of the OS or whatever i need to fix it in case i brick it.
3-What are the latest/best files to root it things like Recovery, ROM, SPL (i don't fully understand what this is and how it is different from the recovery)
Thank You.
Frodcord said:
I bought a G1 2 days ago and i've been reading a lots of tutorials on how to root the phone, i have hacked/Modified every phone i've had so far (Motorola/Sony Ericsson/Nokia) and i would like to do the same with my G1 (That;s why i bought it for) the problem is that every tutorial i see wants me to downgrade to RC29 which isn't complicated but the problem is that it has the DMD64 update.
1- Is the rooting process the same for DMD64 or do i need something special to downgrade? i read about the goldcard but i also heard it was not necessary all the time.
2- Since this is my first time rooting , is there a way to make sure i don't brick my phone? like making a backup of the OS or whatever i need to fix it in case i brick it.
3-What are the latest/best files to root it things like Recovery, ROM, SPL (i don't fully understand what this is and how it is different from the recovery)
Thank You.
Click to expand...
Click to collapse
1: I have no idea if the rooting process is the same for DMD64 or not, but I do not see why it would be any different. But, I could be wrong. I was lucky enough to have RC29 when I purchased mine.
2: The only thing that you can do to make sure you do not brick your phone is to FOLLOW EACH STEP CAREFULLY! Do not skip steps, or add your own. This mainly applies to flashing the Radio and SPL. If you f*ck that up, you're bricked, heh.
3: This confused me at first as well.
What is a SPL? The SPL, or Second Program Loader, in conjunction with the IPL comprise a device's bootloader. Aside from bootstrapping Android, the bootloader also fulfills various diagnostic functions. One of these functions is the manipulation of data in the device's internal flash ram. Depending on the SPL installed, the user can apply a signed NBH file, flash nand images, and more. Note that the SPL is installed and operates independently of the Android build that runs atop it.
Click to expand...
Click to collapse
The recovery is kind of like pressing F8 when you are booting into Windows. It lets you make changes to your system, w/o booting the the complete Operating System (The Android OS in this case). Using the recovery menu, you can flash new ROMs, format your SD card, enable the USB Mass Storage so you can see the SD card within windows, do a factory reset on the device, open up a terminal to manually input commands, perform a backup of your device (you can back up most everything on it) which allows you to restore from that backup if you mess something up.
But, then there is your FastBoot screen as well. FastBoot is where you need to be to flash your SPL and Radio. I am not 100% sure as to the correct order of the flashing off the top of my head, but google around (or simply search this forum), and you will find all the info you need.
Not all ROMs require you to have the "Danger/Haykuro/Death SPL" though. Many of them will work on a stock SPL. However, if you do feel the need to try one of the ROMs that require you to use the Death SPL, you can find all the information about it here: http://code.google.com/p/android-roms/wiki/SPL.
Good luck with your new G1, and do NOT be afraid to ask for help if you need it. Nobody likes to see one of these devices get bricked
Thanks a lot for helping me I thought that the recovery was the f8 in a computer too but I still have my doubts about the spl and the radio. I'll try to root my phone tomorrow i'll give you guys an update after I get to 1.5.
Wish me luck xD.
Frodcord said:
Thanks a lot for helping me I thought that the recovery was the f8 in a computer too but I still have my doubts about the spl and the radio. I'll try to root my phone tomorrow i'll give you guys an update after I get to 1.5.
Wish me luck xD.
Click to expand...
Click to collapse
Remember, always RADIO BEFORE THE SPL. If you do decide to mess with SPL, make sure to flash engineering (or hard) first, and then flash Danger/Death SPL thru fastboot. This eliminates 99% chance of the brick.
Good luck.
borodin1 said:
Remember, always RADIO BEFORE THE SPL. If you do decide to mess with SPL, make sure to flash engineering (or hard) first, and then flash Danger/Death SPL thru fastboot. This eliminates 99% chance of the brick.
Good luck.
Click to expand...
Click to collapse
Lol how is he going to know what fastboot/adb is? OP, don't mess with the SPL and radio until you know what your doing. Flash a rom like cyanogen or Enom's AOSP if you don't want to mess with them.
Ok I've done it i am running 1.5 now so if a person comes asking about DMD64 (G1) now you know what to say. You don't need a goldcard or something else just the dreaimg.nbh and there is nothing to worry about.
I still don't fully understand the SPL and Radio part so i'll keep reading until i am ready to use a custom ROM.
so just root DMD64 the normal way?
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
grins1 said:
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
Click to expand...
Click to collapse
I *think* your error, in general, was using a bunch of "easy" one click methods and not properly learning (READING) about what the proper steps are. Here is my advice (assuming you are still rooted) -
1.boot into recovery (power off phone, hold home button, press power)
2.wipe data/factory reset
3.mounts/storage - wipe system and boot
4.restore nand backup OR flash ROM/gapps (from the same thread)
5.reboot, and be patient, bootup could take 5-10 minutes.
Good Luck.
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
grins1 said:
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
Click to expand...
Click to collapse
It is important, as Il Duce said, that you definitely do a good amount of reading when you want to get involved in rooting your phone. You are opening yourself up to some great innovation and fun, but you can also cause yourself a lot of headaches.
Recovery is your friend. If you can get into that, at least you know things are ok. I like to wipe (or format) system, data, cache, and boot 3x just to make sure that clockwork recovery cleaned everything and there are no dingleberries from the last rom I was using.
Flashing the correct type of rom is even more important. Don't flash a gsm rom to a cdma phone and NEVER flash a gsm radio to a cdma phone. Once you delve into the reading aspect of XDA, you will see that is the sure way to brick your phone.
Some roms take longer than others to boot up. Let it run its course. Sometimes it will reboot right after installing. At some point, you might want to make a nandroid of the new rom you are running and go back to your stock (2.1 update 1) and update your PRL, baseband, etc. (if you haven't done an update in a while).
Have fun, that is the most important part and we seem to have a lot of it here in HeroC XDA land.
You know, I put in a fair share of reading about how to update the ROM on my phone and I was under the impression that it would be fairly simple. I figured that since this has been done for quite a while and all these tools have been developed, I wouldnt need to know what happens on the back end during a root or ROM install.
But I did get myself into a bind that I wasnt able to figure out on my own. And with the help of this forum, I was able to get past my problem. Im glad to say I now have a phone that is functioning very smoothly with CM7 and the apps I need.
Next step for me is figuring out how to save my apps to the SD card so that I can install from there if/when I update my ROM in the future.
Thanks again for the help!
Get titanium backup FTW.
BANG! from my shooter...