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?
My G1 is rooted and I have updated it to RC33. (during the process, I used HARDSPL)
1. If I plan on using a theme from Drizzy (champion V2) do I still need to do the cupcake update AND the radio update?
2. Is installing this theme as simple as renaming the .zip to "update" and dragging it to SD card. THEN, do I Alt+W, or only Alt+S when I get to restore screen?
Please help if I am way off.
stevedawg85 said:
My G1 is rooted and I have updated it to RC33. (during the process, I used HARDSPL)
1. If I plan on using a theme from Drizzy (champion V2) do I still need to do the cupcake update AND the radio update?
2. Is installing this theme as simple as renaming the .zip to "update" and dragging it to SD card. THEN, do I Alt+W, or only Alt+S when I get to restore screen?
Please help if I am way off.
Click to expand...
Click to collapse
If you are going to use a theme, you need to make sure the theme is intended for that specific rom. You should always update your radio, without updating it you will have BT problems and possibly dropped calls. If you have Cyanogens recovery 1.4 you don't have to rename anything to update any more cause it can flash any .zip file. And you don't have to wipe before flashing a theme.
Thanks for the help.
How do I find out which rom I have and which rom's the .zip support?
I followed a youtube tutorial from anthonymoreno24 and these are the files I used:
Recovery image & HARDSPL from:
http://koushikdutta.blurryfox.com/G1RootWalkthrough/
I will update to cupcake during lunch (I have to use friends SIM cuz I have no data plan )
--------------
EDIT:
Just found this, do I follow these instructions after I update to Cupcake?:
Download image (right-click, save as): http://n0rp.chemlab.org/android/cm-recovery-1.4.img
MD5Sum: f5135a878c705215f4012786e4261cfe
To install image: copy it to your sdcard and run:
Code:
flash_image recovery /sdcard/cm-recovery-1.4.img
If you have problems with a "no space on device" error, try using fastboot and erasing first:
Code:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
So have you not even loaded any rom yet? If you go to about phone under settings whats the info say?
Sorry, Im a newb, I'm literally following step by step instructions from the youtube vid
FW: 1.1
baseband: 62.33xxxx_1.22xxxx
kernel:2.6.xx-xxx-gfea
[email protected] #1 (kool!!! just noticed this )
Build: kila-user 1.1 PLAT-RC33 126XXXX-xxxwordsxxx
This help? what specific info you need?
Bud, you are a long way off. Drizzy's is not a theme, it is a hero rom which I would not suggest you try since it needs the danger spl and I can see a brick happening already, download cyanogen 4.02 rom and flash that and stick with it before you consider anything else, read the sticky's at the begining of each forum here to get an idea of how android works instead of relaying on a couple month old out of date video. A lot has changed since that was made. Oh and make sure that your file you want to flash is in the root of your sdcard and not in a sub folder otherwise it won't work, biggest thing make a nandroid backup in cm-recovery 1.4
gridlock32404 said:
Bud, you are a long way off. Drizzy's is not a theme, it is a hero rom which I would not suggest you try since it needs the danger spl and I can see a brick happening already, download cyanogen 4.02 rom and flash that and stick with it before you consider anything else, read the sticky's at the begining of each forum here to get an idea of how android works instead of relaying on a couple month old out of date video. A lot has changed since that was made. Oh and make sure that your file you want to flash is in the root of your sdcard and not in a sub folder otherwise it won't work, biggest thing make a nandroid backup in cm-recovery 1.4
Click to expand...
Click to collapse
Took the words right out of my mouth.
OP: If you want to flash anything hero related you need to read read read, if you are asking questions like this, and are this confused then you shouldn't/aren't ready to go hero. Try cyanogen or jacxrom (if you want a different look, it has a nice theme built into it) and after a week or 2 of studying them give hero a shot.
Has anyone else noticed how many people have been posting sh*t like this lately? It seems like noone can read anything anymore and wants us to give them specialized instructions instead of using the GUIDE's like we all did.
crpercodani said:
Took the words right out of my mouth.
OP: If you want to flash anything hero related you need to read read read, if you are asking questions like this, and are this confused then you shouldn't/aren't ready to go hero. Try cyanogen or jacxrom (if you want a different look, it has a nice theme built into it) and after a week or 2 of studying them give hero a shot.
Has anyone else noticed how many people have been posting sh*t like this lately? It seems like noone can read anything anymore and wants us to give them specialized instructions instead of using the GUIDE's like we all did.
Click to expand...
Click to collapse
Agreed. I've noticed that people are like how to I root!?!? I'm such a n00b. There is plenty of literature out there and should learn how like the rest of us did. If you need to be babied into root maybe you shouldn't have root.. or let someone else do it.
agreed
I rooted my phone a couple months ago without asking any ?s, I have still not asked a ? Yet, before I even got my phone, I studied up on it, there is a ton of info and a lot is in the stickysand has been covered countless times. Now it is even easier to root and flash your phone than ever but the problem is people are following videos and blogs that do not provide enough info. I was lucky to find xda back when I had my wing so I knew right were to go from the begining. If people just took notice to the info here they would have no problem at all
gridlock32404 said:
I rooted my phone a couple months ago without asking any ?s, I have still not asked a ? Yet, before I even got my phone, I studied up on it, there is a ton of info and a lot is in the stickysand has been covered countless times.
Click to expand...
Click to collapse
I completely agree, I too read the tutorials many times before I got my phone !
And when I got the phone, I invested almost 2 days ( around 20 hrs) to try different things (Thanks to all for providing guides to everything) and now I am running a fantastic ROM with root.
It feels much better now that instead of asking "How, Why,etc), I am writing "THANK YOU ALL" for fantastic guides and tutorials !
crpercodani said:
Took the words right out of my mouth.
OP: If you want to flash anything hero related you need to read read read, if you are asking questions like this, and are this confused then you shouldn't/aren't ready to go hero. Try cyanogen or jacxrom (if you want a different look, it has a nice theme built into it) and after a week or 2 of studying them give hero a shot.
Has anyone else noticed how many people have been posting sh*t like this lately? It seems like noone can read anything anymore and wants us to give them specialized instructions instead of using the GUIDE's like we all did.
Click to expand...
Click to collapse
FYI, JACxROM requires Haykuro's SPL to run properly as well. If you're using the HardSPL, then your best choice is Cyan's 4.03 or enomther's rooted version of the stock Cupcake CRC1 build.
my bad, I guess since I flashed haykuros spl and the new radio when I first rooted I never relized you needed it for the xrom.
crpercodani said:
my bad, I guess since I flashed haykuros spl and the new radio when I first rooted I never relized you needed it for the xrom.
Click to expand...
Click to collapse
Yeah, actually even the devs didn't realize this until a couple of us did some experimenting. Fortunately, I had two G1s and the only difference with them were the SPLs... one worked and one didn't.
Hey everyone, I'm new to this forum. So...Hi
Anyways, I've got a problem with my Rogers Htc Dream. I was trying to root it and was following a guide on youtube. Then i realized rooting for T-Mobile G1s and Rogers HTC Dreams were different. Now i notice when i turn on my phone it shows a T-Mobile screen instead of the regular Rogers loading screen. I guess i installed the T-Mobile firmware on my phone. I checked in settings the current firmware im running is now 1.0. So, i'm wondering if anyone can help me put back on rogers firmware on my phone and also link me to a Rogers HTC dream rooting guide. Thanks in advance.
Slaii1030 said:
Hey everyone, I'm new to this forum. So...Hi
Anyways, I've got a problem with my Rogers Htc Dream. I was trying to root it and was following a guide on youtube. Then i realized rooting for T-Mobile G1s and Rogers HTC Dreams were different. Now i notice when i turn on my phone it shows a T-Mobile screen instead of the regular Rogers loading screen. I guess i installed the T-Mobile firmware on my phone. I checked in settings the current firmware im running is now 1.0. So, i'm wondering if anyone can help me put back on rogers firmware on my phone and also link me to a Rogers HTC dream rooting guide. Thanks in advance.
Click to expand...
Click to collapse
Yeah I have that too.
Not really an issue. I just too happy to care when I finally rooted my Dream.
Outblaze said:
Yeah I have that too.
Not really an issue. I just too happy to care when I finally rooted my Dream.
Click to expand...
Click to collapse
Okay so, the root worked for you? Everythings alright its just the start up screen that changed?
To get back to stock rogers firmware apply the update from rogers found here:
http://rogers.com/techsupport/
Then follow this guide to get your phone rooted and install cyanogenmod:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
beav_35 said:
To get back to stock rogers firmware apply the update from rogers found here:
http://rogers.com/techsupport/
Then follow this guide to get your phone rooted and install cyanogenmod:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
Click to expand...
Click to collapse
I'm abit scared to follow that guide because there seems to be some ifs about it, like it says avoid anything that writes to the kernel, otherwise you're dead. And it says you require a EBI1, how do I check if I have EBI1
"The Recovery Flasher utility will only work if you're on a version of Android that Rogers/HTC hasn't yet fixed.
If you are at the recovery screen, move on to the next step."
Well how do I know if they haven't fixed it? And if we can't use fastboot to flash images, as Rogers prevents it, then if this procedure goes south we're stuck? I can verify the MD5 of the SPL update ZIP 20 times, but that's not going to guarantee that when I flash it it's not going to brick my phone
edit: I booted with camera and power and it says hboot is 1.33.0009, does this mean I don't have to risk bricking when I root? The tutorial is for 1.33.0010.
I think that it makes it sound a bit worse than it is. I have never tried it but from what I have read if you boot a EBI0 kernel with a EBI1 radio it will just freeze. You will just have to pull out the battery, boot into recovery and then flash a EBI1 kernel on top.
Rogers is bad for releasing updates for their devices. All their Android devices still run cupcake, even the new LG Eve. This is to our advantage because none of the rogers firmwares are fixed. You can give the Recovery Flasher a try because the worst that will happen if you have a fixed rom is nothing.
If you have a 0009 spl you can follow the guide here to update your spl and recovery then start following the guide at Installing HTC System Image. You could also just use the method on the wiki for 0010, I cant see any reason that wouldn't work.
My phone is perfectly fine after the gaining root. So far not much of a difference, except for the virtual keyboard and two more screens and a few more apps and options.
beav_35 said:
I think that it makes it sound a bit worse than it is. I have never tried it but from what I have read if you boot a EBI0 kernel with a EBI1 radio it will just freeze. You will just have to pull out the battery, boot into recovery and then flash a EBI1 kernel on top.
Rogers is bad for releasing updates for their devices. All their Android devices still run cupcake, even the new LG Eve. This is to our advantage because none of the rogers firmwares are fixed. You can give the Recovery Flasher a try because the worst that will happen if you have a fixed rom is nothing.
If you have a 0009 spl you can follow the guide here to update your spl and recovery then start following the guide at Installing HTC System Image. You could also just use the method on the wiki for 0010, I cant see any reason that wouldn't work.
Click to expand...
Click to collapse
I really want to root so I can install applications to the memory card, and to get 1.6, but I'm really really really scared that it's going to break. I got the phone from ebay, so I'm pretty sure if it breaks I'm out $300 bucks. I'm really at a cross road here!
Ya i was kinda scared the first time too. Then I just bit the bullet and did it. Try to read through the forums as much as you can to learn as much as you can about how your phone works. Also make sure that you understand each step completely and what it is doing to your phone. This is what I did and it made me feel a lot better about the process.
The main risk is flashing the radio and spl once you are done that the chance of bricking is almost none of not none. If you have any questions that you can't find answers to by yourself just ask and me or someone else on the forum will answer them for you.
Yeah, if you're on the Rogers HTC dream, just follow the Rogers heres your real root thread, and all the guides he post. And follow it while filling in the rest with logic.
You'll probably get lost like I did, don't be afraid to ask around.
does anyone know the warranty if it bricks?
Hey everyone, thanks for the help. I went through with the root and everything seems to be working fine. I can make phone calls and everything. I'm running a hero rom. The only thing thats different is it shows a T-Mobile screen instead of Rogers. I don't think thats a big deal, is it?
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
There are several thread, especially one that contains an instruction on howto downgrade the HBOOT version.
Many users are not aware of the difference between an AMOLED and a SLCD Nexus device. The EPF30 ROM, is a special ROM, containing an image that WILL BRICK Nexus One devices that are of the SLCD generation!
The MICROP will be downgraded from 0c15 to 0b15, resulting in an irrecoverable flash, that will let the trackball light up in red, the only solution is to send it back to factory and let them fix it.
A lot of problems people are running into, is when they follow a downgrade instruction made by Nexus One owners, that have an AMOLED device and upgraded to boot version 0.35 by accident.
Wiki updated with a visible warning in the guide and reference to this thread.
Jack_R1 said:
Wiki updated with a visible warning in the guide and reference to this thread.
Click to expand...
Click to collapse
Very cool
Correct me if I'm wrong, but I think the first stock ROM to support SLCD was FRF91. I don't know if *all* versions of FRF91 support it or only the versions that came with said devices. But do *not* ever try to install an older version than FRF91 on your SLCD phone.
Stock FRF91 didn't support SLCD, only Korean and Vodafone versions of it. First Google ROM to support SLCD was unofficial FRG33 and official FRG83.
Jack_R1 said:
Stock FRF91 didn't support SLCD, only Korean and Vodafone versions of it. First Google ROM to support SLCD was unofficial FRG33 and official FRG83.
Click to expand...
Click to collapse
Great thanks. I think also the Mobilicity and Videotron Nexus Ones ship with a version of FRF91 and SLCD.
So if you mis-flash an SLCD phone there's no way out? You couldn't even try and blind-flash PASSIMG.ZIP?
Not if you just mis-flash, but if you downgrade HBOOT, which is not to be confused with flashing ROMs - and flash a very specific old OS build.
cmstlist said:
Great thanks. I think also the Mobilicity and Videotron Nexus Ones ship with a version of FRF91 and SLCD.
So if you mis-flash an SLCD phone there's no way out? You couldn't even try and blind-flash PASSIMG.ZIP?
Click to expand...
Click to collapse
If you look at eh EPF30, you'll find an image that is ment to flash microp code.
So - regardless on how many wipes and PASSIMG flashes you make, you'll never get to fix that, since till this very moment there's no SLCD ROM that contains a similar image to upgrade again.
This is why I opened this thread. the only way - is the hard way - to learn this. Because you'll hardly find that documented, or at least stated very clear. Thats why sticky threads with brick potential are dangerous imo
Okay thanks. For the benefit of the uninitiated, can you clarify exactly what is the function of the "microp" code and why this downgrade makes the N1 unrecoverable?
I saw one history by one guy on another forum.
He got some problems with nexus (something wrong with hboot), so he have flashed Eclair full stock rom on slcd nexus (I wonder what he was thinking about..). After flashing he got a brick with red-trackball.
But he says, that putting passimg.zip (korean one) solved it:
After power-on phone automaticly entered bootloader, founded passimg, checked it and started update procedure without any promt. Now the phone boots and works, but still have some problems with flashing custom roms (stuck on boot). Btw he says that red-trackball lighting didnt gone... so be carefull
cmstlist said:
Okay thanks. For the benefit of the uninitiated, can you clarify exactly what is the function of the "microp" code and why this downgrade makes the N1 unrecoverable?
Click to expand...
Click to collapse
Microp stands for microprocessor i suppose. Amoled have 0b15 version, SLCD do have 0c15. The only impact i know, is that the trackball will constantly light up in red, as there is a system warning.
Microp - microprocessor?
I think microp means microprogram.
For example, low-level driver, bridge between hboot and radio
It is possible to fix the red trackball: http://forum.xda-developers.com/showthread.php?t=847499
Tim4 said:
Microp - microprocessor?
I think microp means microprogram.
For example, low-level driver, bridge between hboot and radio
Click to expand...
Click to collapse
Better bad english than bad knowledge.. as I said, not sure, but your definition makes way more sense than my assumption.
Rusty! said:
It is possible to fix the red trackball: http://forum.xda-developers.com/showthread.php?t=847499
Click to expand...
Click to collapse
Not for everybody... The misc flash does not help in case you included the led image from epf30
Newbie question
Sorry for the newbie question I am a long time winmo user about to make my first jump into an actual android phone after playing with android for a while on my HTC HD so I bought a used Nexus one on ebay the other day and it should be here by the weekend. How do i make sure its AMOLED and not SLCD? Is there a boot-loader code or another way to know based on manufacturing dates etc. or are all N1's AMOLED as I understood them to be till now, though this thread seems to suggest otherwise. Thanks for the help and patience.
If you install an older recovery, that will let you know for sure. It won't harm the phone, but the screen won't work in recovery mode. Installing a newer recovery with fix again.
Amon started supporting SLCD at 1.8.0.1
Clockwork started supporting SLCD at 2.5.1.1
Sent from my Nexus One using XDA App
mo976 said:
Sorry for the newbie question I am a long time winmo user about to make my first jump into an actual android phone after playing with android for a while on my HTC HD so I bought a used Nexus one on ebay the other day and it should be here by the weekend. How do i make sure its AMOLED and not SLCD? Is there a boot-loader code or another way to know based on manufacturing dates etc. or are all N1's AMOLED as I understood them to be till now, though this thread seems to suggest otherwise. Thanks for the help and patience.
Click to expand...
Click to collapse
When you boot into the bootloader (i.e., hold the trackball down and power up the device), check the microp. If it its 0b15, it is AMOLED, if it is 0c15, is is SLCD...
Thanks Ill do that.
So how do I know which screen I have, I have the korean nexus one and since i got it I have never been able to get into the recovery screen. I do have it unlocked.
i234.photobucket.com/albums/ee97/xx_ed_xx/DSC02189.jpg