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.
I have been wondering if I should attempt to root my phone or not. With the new rumor claiming that Google's newest updates (donut eclair flan ect..) will not be distributed out to the G1 users due to hardware issues. It seems if this rumor turned to be true the only way to get the new said updates will be to root my phone. My worry is that i will end up bricking my phone. Now to the Question.
If by some chance i end up bricking my phone is there any way to unbrick it or would i be SOL because rooting voids warranty?
I advise you to read the ultimate noobs guide up and down http://forum.xda-developers.com/showthread.php?t=550710&highlight=ultimate+noob
After you have read that then goto youtube and watch the 3 part series at this link.http://www.youtube.com/watch?v=GgJ2VtSqtJY&feature=channel_page
If you follow these guides, you shouldn't have any problems.
Thanks for the links. The n00b guide i knew about. I was planning on using that when the time came for me to root my phone. I just wanted to know about bricking just as a fail safe. I have read that once a G1 is bricked there is no going back but i have also read with the new updates there is a way to restore a bricked phone. Just wanted some clarity.
A real brick is just that, a paperweight, no coming back. The real only way to brick at this point is the danger spl needed for a hero rom, other than that any boot loops or jam ups as long as you can get into recovery or the bootloader you can be saved with a little bit of reading, and don't worry we will get the updates just our xda versions of them
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
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.