Related
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.
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'm as green as it gets when it comes to Andriod and all of these custom roms for it and the phones. I am extremely technical, senior dev for 10 years. I know a bit of *nix as well, so command shells aren't new to me and the concept of mounting. I've loaded lots of ROMs (and donated!) on my Windows Mobile device (Touch Pro), so that I have licked fine. Just, now I have an andriod device...
But for the like of me, I am having a hard time finding simple basic instructions on how to load a ROM. All I see are things like "boot to RA". Yes, I've searched and searched with VBulletin's limited forum search (used google to crawl the site too, nada).
What does "RA" mean, and how to do I get to it? LOL See my delima! Does it mean "Root Access", and does that mean I have to root my phone (I am assuming that?). Just don't want to brick my brand new phone!
I just picked up a Sprint Hero and want to load Fresh ROM on it. I have not even activated it!
OS is: 2.27.651.5 I assume this is the "2.1" that people are talking about?
So, if this is the 2.1... Does that mean I cannot root it? And therefore, I cannot load any custom ROM on it?
For example, here are the instructions to load Fresh ROM (and my questions):
•Download and copy the zip to the root of your sdcard
Ok, no problem. The zip is on my flash card. But, do I need to expand it?
•Reboot to RA and do a data wipe / factory reset (REQUIRED)
Again, Reboot to... "RA" what? Root Access?
Also, in the rooting instructions, I don't see anything about "data wipe / factory reset" from whatever this "RA" is.
•You may also need to wipe sd:ext if you are having troubles booting.
How do I do that?
•If you are running Fresh Toast and ext4 then you’ll need to partition back to ext3 if you want to use apps2sd
Say what? How do partition, ext3? ext4? What are those? apps2sd?
Yeah, very new...
The rest of the instructions seem easy enough.
Thanks in advance guys!
You need to root your phone first.
After that the RA everyone is talking about is rebooting into recovery. If you have the android sdk loaded you can send a command like adb reboot recovery or you could also turn on the phone while holding the home button. Then you can do all the wiping and loading of ROMS(just make sure they are for a CDMA hero)
You will need to go into settings -> About phone -> Software Information and look at your firmware version. If it is 2.1 then you can't do anything until an exploit is found. If you are 1.5 then you can root your phone. The easiest way is with fresh kitchen. http://forum.xda-developers.com/showthread.php?t=655225
Thank you centran! Fresh Kitchen looks super clean. I'll give that a shot (when I can...).
Humm. The phone came with 2.1-update1 as the firmware.
So I guess that means I am SOL?
yep. sorry
Is there a way to use the normal HTC Utility and flash the ROM to an older version? Sprint has pulled the older versions of the ROM from the site. But, I am sure there's one floating around here somewhere.
Thanks again!
Nope, HBOOT fails to flash, and even though we maanged to bypass HBOOT, main version check still fails.
Looking forward to the hack when it's accomplished! Thanks!
Hahahaha... And as soon as I give up hope, handed it to the wife and said, "Sorry, we can't hack it at this time", I see on xda's homepage that the Hero 2.1-update1 has been rooted!!!
http://forum.xda-developers.com/showthread.php?t=694572
Now, does this mean I can snag any of the custom ROMs here and slap it on it? Or, do I need to/should wait for an RUU-hacked version?
Yep, just Root it and then flash away. No need to wait for anything.
Thanks again for the reply!
I have a rooted cdma sprint hero and i hear every once in a while that there are some left over stuff that may cause problems with new roms. Now i was wondering what would be the best way to wipe to make sure that there is nothing left over from previous roms.
This is what i do;
1 back up pics and music from sd card
2 format sd card
3 put new rom on sd
4 flash into recovery
5 wipe all that i can cache devalk (sp) etc
6 Run moduler remover
7 Falsh rom
8 Flash kernal
I was also wondering if doing this removes any kernal that i have put on there or am i just adding them on top of each other?
Sorry for such a noob question but i would really like to make sure that my phone is running how the guys making these roms intend them to run
You're being real thorough for sure! LOL! I just boot into recovery and wipe dalvik, cache and ext. I t really depends on how different the new ROM is, as incompatible files are the problem.
Sorry for putting in the wrong thread i wasn't where i thought i was and im not sure i am where i thunk i am. if this needs to be moved feel free
Switching between ROMs all you have to do is wipe data/factory reset and wipe dalvik cache. That's it. No need to reformat your SD card..
what about if you use ap2sd?
Looks as if wiping/resetting the device directly from Fastboot is starting to become fairly popular as well. May want to give that a go...
-Reboot to Fastboot
-Wipe/reset
-Reboot to Recovery
-Flash ROM/Kernel
-Reboot device
Neo31697 said:
what about if you use ap2sd?
Click to expand...
Click to collapse
If you use apps2sd, that's what wipe ext is for. I actually forgot to include that in my previous post.
wow didn't know that thanks
Just making sure, you're talking about apps2ext, right? Not the built-in froyo version aka apps2fat?
Yes I am not running froyo ... yet
Sent from my NFX-HERO
Since the topic is up I have a question on my own. Are all the wipes necessary when I flash one rom and then nand restore to another?
I just Nandroid, flash and pray the new ROM works I may do a Dalvik wipe now and again. Fingers crossed I have had no problems so far, except when I figured there would be one
Krazy_Talk said:
Since the topic is up I have a question on my own. Are all the wipes necessary when I flash one rom and then nand restore to another?
Click to expand...
Click to collapse
See my post above...Some do, I don't, and the last few days I have flashed, Nand, reflashed new ROMS, themes, etc while messing with CM6.1 and have not even done a Dalvik wipe...that's just my style though Is it necessary? I would say no, others would say yes...
However, I do have a collection of working ROMS on my SD from Nand all set up the same way that were done correctly (i.e. proper wipe, etc.) with different themes I can go back to if need be.
hey guys i just got my nexus one 2.3.3
im confused what 2 do first
root, unlock bootloader
what 2 do first?
and i preffer to do all these things WITHOUT adb, bcoz adb never works with me
You can't unlock bootloader without ADB (or actually without fastboot, but if you can't get ADB to work, then you probably won't be able to get fastboot to work - since they work the same way).
My suggestion is - do nothing. At least until you'll be able to follow one of the guides and get ADB and fastboot to work. Then you can decide yourself, whether you want the bootloader unlocked or not, and how will rooting benefit you.
what are the benefits of unlocked bootloader?
i just wanted it to get it rooted and flash CM7 on it
It has been discussed a lot, please search to get A LOT of answers.
In a very short version, the benefits are:
Safe radio updates (using fastboot)
Ability to flash whatever you want whenever you want - which is, permanent ability to have root access, regardless of the currently used OS.
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
shiyou said:
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
Click to expand...
Click to collapse
If there's lock icon at the bottom of boot splash screen, it means the bootloader is already unlocked. Is it used one?
yes its used, i guess that guy alrdy unlocked it for me
another problem
i have serius wifi issue, its different from the other wifi problem
if i connect to my wifi its authenticating, then disabled
i dont even go to sleep its just says disabled after authenticating, i tried reconecctint but same things happens again...
i installed wifi fixer but that doesnt work either
also, my 3g drops after 4 sec and i cant get it to work afterwards
Flash a new ROM, wipe your data, and try.
Repeat.
If the problems will still persist - they're in HW and you can't do anything about them.
i tried factory reset but didnt work...
This is exactly the reason why I suggest not touching your phone.
You either don't understand what exactly I'm guiding you to do, or don't understand the difference between various maintenance/repair operations. Flashing a new ROM and wiping user data from custom recovery ISN'T the same as doing "factory reset" from within already-installed ROM. Flashing 2 ROMs with different base (for example, lightly modified stock and CM7, or CM7 and MIUI, etc) introduces enough difference on the SW size to (almost) make sure that any problem which persists in both new ROMs, is coming from HW.
In any case, I suggest either waiting for someone with much more patience than myself (which isn't hard - patience isn't one of my strengths) to explain you some basics that you're not willing to learn yourself by reading, reading and some more reading, or to give your phone to someone who knows what he's doing.
dude....
i rooted and flashed many roms b4, this isnt my first android phone
i just got confused data wipe with factory reset....
Ok well now I need to know if you have a custom recovery, if so then just 5X wipe plus 3X system wipe and flash a new ROM, if not then do you have root access if not I'll walk you through the process.
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
i know how 2 root,flash,wipe, nandroid and all
i did it many times b4
i think i wont use nightly builds, but a stable? or RC?
which should i take?
How about cm7.1 RC1 that is the latest version of cyanogen mod.
rugmankc said:
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
Click to expand...
Click to collapse
why not clockwork recovery 3? the cyanogenmod rc1 states that i need that?
should i use gingerbeak? im on 2.2.3 and install the recovery afterwards?
ok i rooted it with gingerbreak and flashed clockworkmod recovery on it
after that i went into recovery and couldnt find nandroid backup so i rebooted again
i tried to make a backup via rom manager and it ended up with a "!" icon
i tried to go into recovery again and again i got the "!" icon
I don't know anything about Gingerbreak
But, on CWMod 3.+, it has been unstable for a lot of people--I don't recommend it
If you have Rom Manager--flash something like 2.5.1.4??
Still recommend Amon_Ra
I am not sure, but if you get the exclamation, you may not be rooted
If you are experienced at flashing, I would as another poster suggested--get to know your phone and study hard info from the Rom threads you want to try before trying.
What color was recovery--did it say ClockWork
I don't think you will see the name Nandroid in Clockwork--just Clockwork backups
A couple more suggestions, if you want
Back up sd card regularly--you will lose it on occasion--if you need to reformat it, use sdformatter outside of phone
Partition sdcard with zero swap
Wipe all (data/caches) multiple times before flashing new rom, including System