Ok first off I have tried searching all day this both here and and on Google, and all I see is "soft brick" or "brick!!!1!!" threads that have access to the bootloader. So either I am being obtuse or it is buried deep in an obscure thread.
Here is my situation, I unrooted my phone by doing the following: I had used DREAIMG.nbh to return my phone to RC29, flashed the cupcake update, and waited for the donut OTA because the .zip would not successfully flash.
All of that was done and everything was running great for a couple of days and I decided that I wanted to go back to rooted.
Well I was using clockworkmod recovery before and I had made a nandroid back-up before unrooting. I figured that would cut the work in half for when I went back to rooted. I didn't know that AndRoot was available for G1 1.6 so I did it the old fashioned way and reflashed the RC29 DREAIMG.nbh. I then regain root via the original 'telnetd' method and proceeded to flash cloworkmod recovery via Telnet. In the nandroid backup that I made I was running Super F test3 so I know that I needed the danger SPL. This is where everything fell apart, I placed the Danger SPL zip on my sdcard and rebooted to check that the recovery had indeed flashed successfully (it did). Seeing that it was working, I then selected to flash any zip update and selected the Danger SPL. It ran and said the operation completed successfully. I then home & backed to reboot and now I am stuck with just the G1 splash screen.
1) Home & Power does not work
2) Camera & Power does not work
3) Trackball & Power does work to get in blue LED mode. Don't know if that helps just laying it out there.
4) I did not flash a radio, I know the dangers there. This occurred immediately after flashing the Danger SPL via clockworkmod recovery.
To summarize: recovery & bootloader button combos don't work, blue LED mode does, phone does power on but I only get the G1 splash screen for all button combos aside from blue LED mode.
Any help is appreciated, an thank you in advance.
I'm going to call this a brick unless you can get JTAG.
When flashing the danger spl, just follow all the instructions including re-flashing any radio.
UberMario said:
I'm going to call this a brick unless you can get JTAG.
When flashing the danger spl, just follow all the instructions including re-flashing any radio.
Click to expand...
Click to collapse
I didn't need to flash a radio yet, I was just trying to get back to the Danger SPL so that I could restore via nandroid and then I was going to flash the 2.22.23.02 radio because: 1) it worked well for me, and 2) it is Danger SPL safe
I think you mixed things: the correct radio is a precondition to flashing DangerSPL. Flashing RC29 you most likely reverted your radio to a 1.x-version.
In addition to that, there is no need to flash DangerSPL. Go with Firerat's custom mtd method and 1.33.2003 and you are fine.
Sent from my Htcclay's Superfly G1 BTX using XDA App
Roadmasta01 said:
I was running Super F test3 so I know that I needed the danger SPL. This is where everything fell apart, I placed the Danger SPL zip on my sdcard and rebooted to check that the recovery had indeed flashed successfully (it did). Seeing that it was working, I then selected to flash any zip update and selected the Danger SPL. It ran and said the operation completed successfully. I then home & backed to reboot and now I am stuck with just the G1 splash screen.
Click to expand...
Click to collapse
YOU DO NOT NEED DEATHSPL FOR ANYTHING!!!!
It has ZERO benefit and introduces the possibility that you may do what you did. You know, there is a REASON why we developed a method of repartitioning the thing!
You're BRICKED.
lbcoder said:
YOU DO NOT NEED DEATHSPL FOR ANYTHING!!!!
It has ZERO benefit and introduces the possibility that you may do what you did. You know, there is a REASON why we developed a method of repartitioning the thing!
You're BRICKED.
Click to expand...
Click to collapse
Really? Yelling at me is going to help or fix my situation? I was simply working off of the limited knowledge that I have. I had not gotten into MTD partitioning. I felt that that was a little above my head and there for the working knowledge that I had was that I needed the Danger SPL to resize the partitions to enable the flashing of ROMs that need a larger /system partition.
And just for back-up here is quote from Cyanogen's thread for CyanogenMod 6
cyanogen said:
CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.
Visit the CHANGELOG for a full list of changes and features!
If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance.
It's important to know that the "DangerSPL" (or DeathSPL or Haykuro's SPL or whatever you prefer) is a prerequisite for Dream/G1 users. Magic (MT3G etc) users do *not* need to do this. Ciwrl has written a guide to installing this bootloader. Flashing this bootloader under the wrong conditions can actually brick your device, so pay attention to the guide. CM releases have always avoided this requirement, but the new bootloader frees up enough space so that no crazy hacks are required for a fully functional system, and it's easier to keep in sync with the N1/Droid releases.
Click to expand...
Click to collapse
All I was asking for is a little help, I came into this post think that I was hard bricked, I was just hoping against hope that I wasn't. I am not, and neither are a lot of people that modify their G1s, an expert at this. I am one of the original G1 preorders; This is my first and only G1, and this is the first time that I have bricked my phone. That fact alone should tell you that I have tried my best to read as much as I can to understand something before I try it. I simply became complacent in my working knowledge, which led to this. I am sorry that I was ignorant of, or apprehensive to try some new developments in partitioning, rendering the Danger SPL irrelevant. Please don't needlessly yell at people for no reason. At least I was able to concisely describe my situation and you all didn't have to play 20 questions to get the real situation out of me. I now know that the mistake that I made was forgetting that the DREAIMG.nbh file restores the radio to a pre 2.xx.xx.xx radio and seeing as how I didn't flash a compatible radio before flashing the Danger SPL, I am now hard bricked. Now that my rant is now over I will again say Thank you again to UberMario, and AndDiSa for their help.
I am now going to investigate the cost effectiveness of JTAG versus a donor motherboard.
Roadmasta01 said:
Really? Yelling at me is going to help or fix my situation? I was simply working off of the limited knowledge that I have. I had not gotten into MTD partitioning. I felt that that was a little above my head and there for the working knowledge that I had was that I needed the Danger SPL to resize the partitions to enable the flashing of ROMs that need a larger /system partition.
And just for back-up here is quote from Cyanogen's thread for CyanogenMod 6
All I was asking for is a little help, I came into this post think that I was hard bricked, I was just hoping against hope that I wasn't. I am not, and neither are a lot of people that modify their G1s, an expert at this. I am one of the original G1 preorders; This is my first and only G1, and this is the first time that I have bricked my phone. That fact alone should tell you that I have tried my best to read as much as I can to understand something before I try it. I simply became complacent in my working knowledge, which led to this. I am sorry that I was ignorant of, or apprehensive to try some new developments in partitioning, rendering the Danger SPL irrelevant. Please don't needlessly yell at people for no reason. At least I was able to concisely describe my situation and you all didn't have to play 20 questions to get the real situation out of me. I now know that the mistake that I made was forgetting that the DREAIMG.nbh file restores the radio to a pre 2.xx.xx.xx radio and seeing as how I didn't flash a compatible radio before flashing the Danger SPL, I am now hard bricked. Now that my rant is now over I will again say Thank you again to UberMario, and AndDiSa for their help.
I am now going to investigate the cost effectiveness of JTAG versus a donor motherboard.
Click to expand...
Click to collapse
When you do something RETARDED and WITHOUT THINKING, you DESERVE TO BE YELLED AT.
You asked for it, YOU GOT IT!
And you DESERVE it.
lbcoder said:
When you do something RETARDED and WITHOUT THINKING, you DESERVE TO BE YELLED AT.
You asked for it, YOU GOT IT!
And you DESERVE it.
Click to expand...
Click to collapse
I actually was thinking when I flashed it, I obviously just forgot about the radio reversion. Also, by your logic, since you are being a complete and total JACKA$$; Don't you deserve a nice left hook to the jaw?
Roadmasta01 said:
I actually was thinking when I flashed it, I obviously just forgot about the radio reversion. Also, by your logic, since you are being a complete and total JACKA$$; Don't you serve a nice left hook the jaw?
Click to expand...
Click to collapse
Try that and you could find yourself with a broken neck.
And IF YOU HAD A BRAIN to begin with, you would realize that REPARTITIONING THE SAFE WAY USING KERNEL ARGUMENTS is designed SPECIFICALLY to keep moron retard newbs like you from doing what YOU DID!!!!
I had not gotten into MTD partitioning. I felt that that was a little above my head
Click to expand...
Click to collapse
So... the easy and safe way is above your head, so you took the dangerous and difficult option instead? Sound intelligent to you?
lbcoder said:
Try that and you could find yourself with a broken neck.
Click to expand...
Click to collapse
You should really calm down, I didn't threaten you. I simply used your logic to state what you deserve.
lbcoder said:
And IF YOU HAD A BRAIN to begin with, you would realize that REPARTITIONING THE SAFE WAY USING KERNEL ARGUMENTS is designed SPECIFICALLY to keep moron retard newbs like you from doing what YOU DID!!!!
So... the easy and safe way is above your head, so you took the dangerous and difficult option instead? Sound intelligent to you?
Click to expand...
Click to collapse
I don't know enough about modding kernels to even know what kernel arguments are, so yes I feel that is a little above my head. I have been using the DangerSPL for quite a long time now and this is the first time that it has biten me in the a$$. Difficult? What is difficult about flashing file in a certain order? I have updated the radio a few times since having the DangerSPL. The first couple of times I had to reflash the HardSPL, flash the radio, and reflash the DangerSPL. The last time all I had to do was flash the 2.22.23.02 radio on top of the DangerSPL because it is supposed to be DangerSPL safe. So considering that I knew the dangers involved with it and it isn't difficult to put three files on my sdcard for all of maybe ten minutes, yes the DangerSPL path was an intelligent choice for me.
Related
hey guys im fairly new to this forum and this is my first post, well let me get to the point, i got my G1 lets say 2 months ago and ive heard a lot about "rooting" and i thought id give it try, i was just nervous about one thing and that is "bricking" so i was just wondering how easily it is to brick my phone? if that happened oh man i dont know what i would do..thanks
If you read a lot and follow directions I think the chances are very slim. It seems like the main cause of a bricked phone is when someone tries to update to the danger SPL (the spl's you need to run a hero rom) before they update to the latest radio.
sakumaxp said:
hey guys im fairly new to this forum and this is my first post, well let me get to the point, i got my G1 lets say 2 months ago and ive heard a lot about "rooting" and i thought id give it try, i was just nervous about one thing and that is "bricking" so i was just wondering how easily it is to brick my phone? if that happened oh man i dont know what i would do..thanks
Click to expand...
Click to collapse
I'm in no way shape or form an expert on any of this stuff but I have my phone running at a high level I believe. So the advice I can offer as a novice is read read read read read search search search search search and read read read read some more and if you can't find the answer ask but make sure in the right forum or u may get "flamed" lol some ppl will but for the most part ppl will point u in the rite direction. also stick 2 the basics when flashing don't get lazy and skip steps they are there for a reason good luck
If by brick you mean having the phone not even go to a recovery screen then it is very hard.
If by brick you mean having android not boot, then very easy.
There are step by step tutorials out for everything now so it is unlikely you will run into problems if you have a bit of sense.
I would first recommend trying to get the JF1.5 rom and then immediatly upgrading to cyogens 1.4 recovery rom. the ums_enable command has saved me numerous times. What it does is enable usb through the recovery terminal so you can load up some different files or another rom and try again.
And really if all you do is follow the directions and don't try to speed ahead thinking you know something everything should work out great
imbonez9 said:
And really if all you do is follow the directions and don't try to speed ahead thinking you know something everything should work out great
Click to expand...
Click to collapse
Exactly!
When I first looked in to rooting I was also worried about bricking. Like others have said the main reason people brick is updating to haykuro's SPL without the cupcake radio (which is doubly stupid as they probably have a cupcake and should have had it already). After you have rooted and have installed the recovery image you can flash ROMs as much as you want, if your phone becomes unbootable because you messed with a file on your phone, you can just reflash. Btw, someone just posted a thread on how to brick their G1 because it seemed unbrickable
Does anyone know what the difference between the 2.22.19.26I and the 3.22.20.17 (came on my Rogers Dream) radio is? Will I brick my phone if flash haykuro's SPL with the 3.22.20.17 radio?
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.
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?
First off I want to say that I know my way around a WinMo flash,reflash, nand breaking and all that jazz pretty well. But Android...not so much.
I ordered a G1 off Ebay recently, it has been shipped, but in the mean time, I was wanting to research the rooting and flashing process..It looks very involved...Very involved..lol
I've read the guides and such but was curious about the rom/radio bricking issues. With WinMo theres alot of radios..How about Android(My phone is an unlocked T-Mobile)?? Are there still known issues?? I like this rom http://lb.vg/fVl3w
Are the guides for rooting on here currently up to date(I think they are, and they probably are)?? Do I have to root to flash a new rom on there(I think I do)??
Sorry for the n00bish questions, but I really don't wanna kill my phone.
Can all bricks be fixed via the user??
Thanks
Edit: What is the situation of Flash?? What is supported??Is Hulu supported??
2.1 and 2.2 Froyo..Whats the difference??
smurfgod said:
First off I want to say that I know my way around a WinMo flash,reflash, nand breaking and all that jazz pretty well. But Android...not so much.
I ordered a G1 off Ebay recently, it has been shipped, but in the mean time, I was wanting to research the rooting and flashing process..It looks very involved...Very involved..lol
I've read the guides and such but was curious about the rom/radio bricking issues. With WinMo theres alot of radios..How about Android(My phone is an unlocked T-Mobile)?? Are there still known issues?? I like this rom http://lb.vg/fVl3w
Are the guides for rooting on here currently up to date(I think they are, and they probably are)?? Do I have to root to flash a new rom on there(I think I do)??
Sorry for the n00bish questions, but I really don't wanna kill my phone.
Can all bricks be fixed via the user??
Thanks
Edit: What is the situation of Flash?? What is supported??Is Hulu supported??
2.1 and 2.2 Froyo..Whats the difference??
Click to expand...
Click to collapse
First root (did it yesterday for the first time, phone was rooted when I got it).
You need root for certain apps, for installing another spl, custom roms.
Root installs recovery (if I remember ok).
Upgrade spl from stock to 1.33.2003 (zip file in recovery). Now you can use fastboot (safer!).Reboot in fastboot and flash first another recovery, then another radio (2.x) radio (needed for spl 1.33.2005), reboot again, go to fastboot and flash the dangerspl 1.33.2005 (or use MTDpartitions, but I got problems with it). Then flash roms.(no need for the old hardspl).
Flash not supported(arm incompatible).
Bricks can only be fixed with an JTAG, so be carefull (always wait) ! ROMS can't brick your device, only the officials can (which contain spl and radio).
Read for flashing the spl's (if you have rogers(canada) it's different).
Idk what this user means by saying that flash isn't compatible with the arm processor.
But yes android 2.2 supports flash all the way to flash 10 but on the g1 I don't think it would be so good on 528mhz because flash is pretty bloated on system resources. But flash videos are fine hulu runs fine for me.
Woops sorry about the double post I refreshed page and it submitted info twice. I did not see a delete function.
Should I do any sort of formatting or partitioning on my SD card or just let the G1 do it??
I've got an 8gig SDHC Class 4 card also.
I've also been reading about J-Tagging the G1..Theres an adapter on here http://miniurl.com/49008 and it's 20USD for the adapter but I think I have to heek it up to an Omnia Repair box..Is that right?? This video http://miniurl.com/49009 shows em hooking one up to a white box..and the only white box on there site is for the Omnia Repair one and it's 229 Euro's(304USD).
Does the first reply have the correct steps for rooting my phone?? Is that for all versions. I'm not sure if mines a R29 or lower.
Sorry for all the questions.
Thanks
~SMurf
Can u root a g1 with super one click application on the computer?
Sent from my x10a flashed 2.1 Brazilian firmware with multitouch xda download Rooted
The G1 is so incredibly easy to root, it takes about 5 minutes. Using an application for it is just plain lazy haha.
aussiehairspray said:
The G1 is so incredibly easy to root, it takes about 5 minutes. Using an application for it is just plain lazy haha.
Click to expand...
Click to collapse
Sorry I have the same question as the first user, but didn't understand your answer...
he's saying you can, but it's the lazy way... the g1 is so easy to root, plus if you root it the traditional way it gives you a little better of an understanding on how things work behind the OS
so if you want to try it, go ahead but im not 100% sure if it works...
Ooooor if you want to grow some fuzz on your balls than try following this guide
http://forum.xda-developers.com/showthread.php?t=1098899
I am glad I did my first root using the RC29 methods, where they left a shell connected to the keyboard, as it is good background for someone who likes to tweak their phone directly from the OS level, instead of having someone else write a script to do it all with "one-click". Cyanogen's Dream root how-to is fairly good also, just stop reading any of them after you get recovery flashed, as the info you'll find here is much more up to date, with newer SPL and radios which you will need for most of the recent ROM builds.
Read this thread too, on ensuring you have a good match of radio/SPL/recovery flashed so you don't get a brick. (i.e., SPL 1.33.2003 seems to be good with 1.x and 2.x radios, and 1.33.2005 for 2.x or 3.x radio)
That being said, by the time I got to rooting my third phone, I did build a goldcard to flash whatever I wanted, just to save some time, but I usually don't care to save anything from the phone, so a full wipe is OK for me.
If you think you are ready to start flashing things, start over and read all of it again. It may not be as expensive anymore to make a mistake and brick your Dream, but it would still be very sad to turn a working phone into a paperweight because of missing a step, or doing something in the wrong order.