Related
I have been useing the JF 1.51 build for awile and decided to change to cyanogen's 1.6 tonight. the recovery programs are not identical but seemed similar enough. I got the recovery image and the cyanogen build, put them both on my sd card. Because of the JF recovery module I only had options to install update.zip so I renamed the recovery image to update.zip and installed it. I then restarted the phone so I could change the name of the cyanogen image to update.zip (I now realize I probably could have just taken the SD card out and done that on my computer and put it back in while still in the recovery console) so I could go back and install it but when I restarted it took forever to get into the android os and got force close errors on every possible program and couldn't do anything. I then restarted to get into the recovery console but I now get at picture showing a phone with a error triangle on top of it. if anyone has any suggestions please help
if you can get into bootloader (camera and power) then flash the DREAIMG.nbh file, and re-root your phone.
it went to the bootloader screen instantly, red green blue white stripes and says
drea100 pvt 32b
hboot-0.95.000
cpld-4
radio-2.22.19.261
sep 2 2008
serial0
I havn't messed with anything of this stuff in months so I can't remeber anything of this stuff and can't find anything online, I really dont' want to screw this up. what am I supposed to do from this screen? I know I sound like a moron but I jus don't want to truly brick this phone if its not already lol
you have a stock spl, but you can still flash the DREAIMG.nbh file, it will not brick your phone. if you are in the united states then grab rc29, if in the uk grab rc7, this is a good thread for flashing the file, and re-rooting your phone. also it will get you to the latest cyanogen rom.
thanks alot for your help! I'll try this and let you know but happends, I'm sure this will work from skimming over it.
no problem, you are welcome.
hey guys, i tryed the one clik meth od here:
http://theunlockr.com/2009/08/22/how...-in-one-click/
after everything, when i get to step 12 and reboot my phone (holding home and power) my phone just freezes with the rogers logo up (i need to remove battery to get back).
What can I try next to root my phone? should i first restore my back up image that i made with the program before I do anything else?
I need some help as i really need to root this phone for 2 reasons
1)apps on sd
2)Rogers locked out the touchscreen keyboard
http://forum.xda-developers.com/showthread.php?t=563679
Follow this, if you want CM keep going all the way through, if you want someone else's ROM then flash that instead of CM's.
hey, ok so my latest update is that i got myself to SPL 1.33.2005
i was able to boot into everything that was needed (power + camera) (power + home)
I am now at this step:
http://forum.xda-developers.com/showpost.php?p=4848777&postcount=506
Look at where he posts his info he has:
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.20.17
I have:
DREAM PVT 32B SHIP S-OFF
does it matter that mine says S-OFF
Hold your horses! That isn't the link I gave you to follow... You are in dangerous territory right now... what all have you done, exactly? Flashing that SPL can and will brick your phone if not done right.
I was using the link you gave me, close to the top it says to follow the linked guide for rogers phones as they are done differently(my phone is rogers)
that link leads you to:
http://forum.xda-developers.com/showthread.php?t=558301
once done that it says to go to:
http://forum.xda-developers.com/showpost.php?p=4848777&postcount=506 (never mind i should not use this as his spl is different as well, not the spl gotten from the previous link)
OR
http://forum.xda-developers.com/showthread.php?t=544654
this first one is a relply of the second link (supposedly easyer)
LAST EDIT:
So, should i continue following
http://forum.xda-developers.com/showthread.php?t=544654
Ok, carry on! As long as your reasd twice and do once you should be ok. And don't worry about the 'on' vs 'off', the big concern is what board do you have, and you have the 32b PVT, which is the one you need. I believe that 'on' 'off' is in regards to carrier lock.
like i edited, the first link guy does not have the SPL that I now have, i will be following the final link
http://forum.xda-developers.com/showthread.php?t=544654
When it says:
"once you are at SPL 1.33.2005 (AND ONLY THEN)
download this (it is hyperlinked)
(md5: 4a58a5702fdf899547011888d9cc066f .. sha1: 99e38e4f8798e952e67421a42e7b053ea70957b7)
extract both images wherever you'd like."
does it mean extract whereever on the sd?
I would assume extract and place on the root of the SD card based off the fact you will be doing all this from fastboot, aka the phone itself.
alright so i did that stuff, now when i boot the phone hangs at the rogers logo, what should i try.
did make a nandorid back up in the recovery menu a little while ago, how an i use it to go back? or is there another option to do something?
I can still boot into the recovery menu and camera+ power menu
Can you get into recovery? First boots take a long time as well, how long has it been hung up? But it sounds like you don't have a ROM on the device currently.
I can get into recovery, It was hung for like 4-5 minutes before i reset it. I dont think i did the fastboot stuf right, I pressed send inorder to fastboot, it said fastboot and i started typing the stuff on the link (you cannot see anything i was just typing) i then rebooted to recovery and Alt+s applyed the update (cynogen).
it is hung at the rogers screen. Can you try and translate the link
http://forum.xda-developers.com/showthread.php?t=544654
a bit better and i can try the fast boot part again?
In the guide it says press back arrow to get inot fast boot but on my screen there is only one option for fastboot and it is the send button.
I tryed to use the update.zip file again but this time it said that it could not mount and that the directory does not exist.
It sounds like you did do the fastboot right, actually, since if you didn't it would boot up fully...
I would try this, dl this rom and put it on the root of your sd card, then boot into recovery mode and select "flash any .zip update" or whatever the exact wording is, then select the file named "dwang-v1.15" and follow the onscreen prompts. It is also probably a good idea to get your phone on a charger sometime soon, wouldn't be surprised if the battery is getting close to dead since when in fast boot and recovery and during boot up itself battery drain is pretty quick.
I truly think you did the fastboot stuff right, since when done you should have the SPL and radio, recovery, but no ROM and need to boot into recovery and flash the new ROM.
Forgot to give the link to the ROM, it is dwang's, my personal favorite and a good starting point to work from:
http://forum.xda-developers.com/showthread.php?t=567023
the option is apply update.zip so i should probably change the file name to that. Ill give it a go.
its still hanging on the rogers icon, weird. Perhaps i should use the nandoid backup? if you agree that that is the best option how would i do that?
another note, when i tryed to flash the rom you gave me it did not let me, game a an error about mounting and cannot find a file, I then put the recovery images back onto the sd card and the operation worked this time, it was unpackin na extracting and everything. Now it is still hung.
I would probably just nandroid at this point, yes
can ou guide me on how to do that?
Hmmmmmmm, do this for me as well, boot into boot loader (camera+power) and tell me what it says on the screen.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA21000)
CPLD-4
RADIO-3.22.20.17
Apr 20 2009, 15:30:43
HBOOT
<SEND> Fastboot Mode
Okay, so I know what everyone says, "make sure you know what you're doing before you update to Danger SPL." So I read and re-read all the forums and guides about various problems and how to avoid them and how to flash the radio and SPL, THEN after I was comfortable I decided to go for it.
So here is my issue:
I used the two sd card method. After wiping, I flashed the radio to 2.22.19.26I, then rebooted. I wiped again and flashed the SPL to 1.33.2005, took out the SD card and put the other one in. I rebooted from console (using command "reboot recovery"), wiped again, and flashed CM 4.2.10.1 and rebooted. After this final reboot it sticks at the G1 screen and doesn't do anything beyond here. I also tried reflashing everything and formatting the new SD card, then loaded the CM version with RA's USB-MS mode and flashed it. Same effect, stuck on G1 screen.
I still have access to the recovery image as well as fastboot and the screen with the androids on the scateboards (bootloader? I'm niot sure). WIth those things in mind, I don't think I have bricked anything, but of course that doesn't help the fact that I can't use the phone. Any help here would be AWESOME.
ROM: CM-4.2.10.1
recovery image: RA-dream-v1.5.0
Android screen reads:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
ALSO I hope a thread with an answer doesnt already exist, I did search for quite a while for a solution but couldn't find one. Thanks again to anyone who can help me out.
Just checking cause you didn't mention this step but before flashing Cyanogen 4.2.10.1 did you flash the HTC ADP image??
Have you tried flashing any other ROM's??
Since you still have recovery && bootloader you're not in a terrible position, you're not bricked, just gotta find out where you're going wrong
HamToast said:
Okay, so I know what everyone says, "make sure you know what you're doing before you update to Danger SPL." So I read and re-read all the forums and guides about various problems and how to avoid them and how to flash the radio and SPL, THEN after I was comfortable I decided to go for it.
So here is my issue:
I used the two sd card method. After wiping, I flashed the radio to 2.22.19.26I, then rebooted. I wiped again and flashed the SPL to 1.33.2005, took out the SD card and put the other one in. I rebooted from console (using command "reboot recovery"), wiped again, and flashed CM 4.2.10.1 and rebooted. After this final reboot it sticks at the G1 screen and doesn't do anything beyond here. I also tried reflashing everything and formatting the new SD card, then loaded the CM version with RA's USB-MS mode and flashed it. Same effect, stuck on G1 screen.
I still have access to the recovery image as well as fastboot and the screen with the androids on the scateboards (bootloader? I'm niot sure). WIth those things in mind, I don't think I have bricked anything, but of course that doesn't help the fact that I can't use the phone. Any help here would be AWESOME.
ROM: CM-4.2.10.1
recovery image: RA-dream-v1.5.0
Android screen reads:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
ALSO I hope a thread with an answer doesnt already exist, I did search for quite a while for a solution but couldn't find one. Thanks again to anyone who can help me out.
Click to expand...
Click to collapse
Snab a copy of cyanogen's rom (update.zip) and recovery image (on the forums)
Boot the phone into fastboot (power off, hold camera button and power on)
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
this should insure that you have a proper recovery image.
boot into recovery mode now (you can press the menu button to power off the device from the SPL menu, then hold the HOME button and power on the device)
Code:
adb devices
you may need to do this a couple times until it shows up, once adb reports your device is available
Code:
adb shell mount /sdcard
adb push update.zip /sdcard
then press ALT+S (or select the option from the menu using your wheel)
let the rom flash.
when it's complete, reboot your device (HOME+BACK) or just use the menu again.
it should now boot.. if it takes a bit longer than usual, check if the device is active using:
Code:
adb devices
if your device is listed, see if it's actually doing something using
Code:
adb logcat
if you see a bunch of "E/" followed by text, your phone is erroring out and you may have to report back here for further assistance, if you see a bunch of "apks" and "jars" flying by, your phone is booting it's just checking signatures most likely.
jackslim said:
Just checking cause you didn't mention this step but before flashing Cyanogen 4.2.10.1 did you flash the HTC ADP image??
Have you tried flashing any other ROM's??
Since you still have recovery && bootloader you're not in a terrible position, you're not bricked, just gotta find out where you're going wrong
Click to expand...
Click to collapse
ADP image? I did the steps exactly as I described them. Should I have flashed HTCs ADP image? I guess so, if thats what I did to get CM in the first place. Is that the image that puts all the Google Apps on the phone? Also, if I'm getting CM v4.2.10.1 from the website, and I'm coming from a new radio and SPL, should I have to treat it as though I'm not updating and am coming from a freshly rooted phone?
and @haykuro, I'll try that as soon as I get the time.
Before you flash Cyanogen for the first time you need to flash HTC's ADP image
Check out the Cyanogen's Wiki for a full guide on installing his rom
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Since you've already gotten as far as getting a custom recovery skip down to the section called "File Download" and continue on, that should get you on the right track
Yes that is the image that get's you all the Google Apps
Yes after installing the 1.33.2005 SPL you have to reinstall a fresh ROM
jackslim said:
Before you flash Cyanogen for the first time you need to flash HTC's ADP image
Check out the Cyanogen's Wiki for a full guide on installing his rom
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Since you've already gotten as far as getting a custom recovery skip down to the section called "File Download" and continue on, that should get you on the right track
Yes that is the image that get's you all the Google Apps
Yes after installing the 1.33.2005 SPL you have to reinstall a fresh ROM
Click to expand...
Click to collapse
Worked like a charm! Kinda makes me feel like an idiot though for not thinking about needing to treat it like a fresh install instead of an update, but I'm glad it worked!
Also, thanks for how quick you helped me out! I was only without my G1 for maybe 5 hours!
I LOVE THIS COMMUNITY!!!!
HamToast said:
Worked like a charm! Kinda makes me feel like an idiot though for not thinking about needing to treat it like a fresh install instead of an update, but I'm glad it worked!
Also, thanks for how quick you helped me out! I was only without my G1 for maybe 5 hours!
I LOVE THIS COMMUNITY!!!!
Click to expand...
Click to collapse
Man! 5 hours is 5 hours too long!
So I have this g1 sitting here for a few months- great looking phone, not a scratch on it...total virgin- no water damage or anything... a true spectacle compared to me daily driver (water damaged g1 with cm 5.07 on it... broken camera, broken wifi module <or so i am guessing since its been that way through all of the different roms ive tried... just shuts off> )
Back to the point-
This spectacle of a g1 - has but one issue... the digitizer doesn't work. No clue why- just wont respond... the g1 has been wiped so I have been stuck @ a "touch the android in its naught spot to continue" screen for a while...
Just decided today that I would try and get cm 5.07 on it... I was remembering (correct me if I am wrong) that android 2.1 didnt bother you with that "touch me" screen when you first booted it up.
So I began with a wipe through recovery- ... formated my sd to fat 32, and threw my DREAIMG.NBH (RC29) on it.
hit the boot loader (camera + power) - boots up as normal- grey screen for the update, and continued with it. Got an OK on each item down the list...looking good.
Update done- hit the power button to finish it- goes back to boot loader displaying the rainbow screen with:
DREAM100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
Serial 0
--
So at this point its all looking great to me- I hit call + menu + power and phone begins to reboot.
But gets stuck @ the freaking tMobile G1 Screen...
I can still access the boot loader... but Ive tried 6 different downloads, re formatted the sd card 3 times, tried a second sd card... tried a copy of RC30 ... nothing works... I get stuck at the G1 screen every time.
I cannot access recovery! Just sticks at G1 screen.
What now? Is this G1 a paper weight?
THANKS!
I don't know if this works with a stock rom, but did you try to get a logcat while it hangs at the g1 screen? Might be useful...
Logcat
I cant do anything :/ Only ability I currently have is to boot the phone via fast boot with a DREAIMG.NBH or sit at a boot screen.
Is there a modified DREAIMG.NBH I should try and run?
Thread moved to Q&A.
pcguru000 said:
This spectacle of a g1 - has but one issue... the digitizer doesn't work. No clue why- just wont respond... the g1 has been wiped so I have been stuck @ a "touch the android in its naught spot to continue" screen for a while...
Click to expand...
Click to collapse
I had a G1 refurb from HTC on which the digitizer did not work properly. No matter what ROM I installed, same problem, no accurate touch response. It was a hardware issue with the phone. I know it doesnt help with the phone hanging on boot. As far as that, it's a tough one. If you only have the stock SPL (rainbow screen) and no modded recovery, you can't do much other than use a .nbh (release key signed ROM/stock ROM) to flash a ROM. Unless there another backdoor I'm unaware of. Good luck!
CM roms need danger SPL, if you're on the "rainbow" screen - you don't have it. You shou've not run NBH because that takes away the root and brings you back to RC29. Sound's like you're out of luck on this one. However, now would be a good time to swap out that digitizer for the one out of "mother-of-all-problems" phone.
Good luck.
danger
I know CM roms need Danger- but at the point I was at I had no way of flashing danger, I needed to first root the phone... the way I have rooted all my G1's was using RC29 first (DREAIMG.NBH) and then using the "type anywhere" exploit to give the phone root administrative rights.
After that i load up a good recovery image, do a nandroid back up etc etc...
Im just not sure why it just died half way through the process- its strange that I can still access the stock boot loader and flash an image but yet nothing happens.
Is it possible for me to flash an image OTHER than RC29- and where could I access that image download?
pcguru000 said:
I know CM roms need Danger- but at the point I was at I had no way of flashing danger, I needed to first root the phone... the way I have rooted all my G1's was using RC29 first (DREAIMG.NBH) and then using the "type anywhere" exploit to give the phone root administrative rights.
After that i load up a good recovery image, do a nandroid back up etc etc...
Im just not sure why it just died half way through the process- its strange that I can still access the stock boot loader and flash an image but yet nothing happens.
Is it possible for me to flash an image OTHER than RC29- and where could I access that image download?
Click to expand...
Click to collapse
That all sounds like it should be working but I would try one more thing. You say you have a second G1. I would try formating the sd card in that phone. It may make a difference. If that does not work you may want to search this forum for "gold card" instructions.
Good luck.
Hello, and welcome myself to this wonderful forum.
Let me introduce myself:
My name is Mish , im a 100% dumbass
Also BIG! thanks for sh1tty cyan's wiki about flashing with dangerspl.
Let me tell you my story:
In a cold night, a boy tried to update his G1 to android 2.2 , updated dreaimg.nbh , rooted the device, installed recovery image . that boy was so excited his 1st android, his 1st up mod.
but that boy was upset, didnt wanted to get his update.zip installed because of the status 7 error. well done , he just looked into the cyan's bloody wiki and he found the magic archive called Danger SPL.
flashed it , rebooted it and stucked into G1 T-mobile Splash screen .. he was like . ah , allrite, i'l reboot and enter to recovery mode . but he cannot do that.
He was so anger . he kissed his keyboard with 2 gently strikes. and searched for hours for solutions but nothing found.
I dont have pages to write the whole story. Aka the end.
in other words, can i get my device working or should i give him wings to fly straight on the garbage can ?
Can you get into fastboot mode? Also i think in the instructions it tells you to flash the radio first. I could be wrong but several people have successfully rooted their device with the instructions given here on xda. Welcome to xda btw.
John
Hello John, i can't enter to fastboot mode or i dont know , it shows me just the T-mobile G1 Splash screen and nothing more, tried with Camera + Power, Volume + Power, Home + Power and still nothing . if you have any hints please share, regards.
Can you reboot holding back and power and get into fastboot?
nope , is stucked in G1 splash screen
I did the same thing and had the same problem - had to replace the motherboard. There is NO WAY to fix it except to replace the mainboard. Good Luck
Is my phone a goner?
I wasn't trying to root or modify my phone in any way. It started flickering and then went black. Now...
Phone does not power on. Not with power button or any combo (camera+power; home+power; etc).
No LED notification. Not even orange when charging.
Eventually starts in tri-color/rainbow/RGB Bootloader ON ITS OWN (no keystrokes). Sometimes after 1 min, sometimes after 20+. Once in Bootloader, it stays there. If it's plugged in and charging, the Bootloader stays on even after battery pull.
Bootloader says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLID-4
RADIO-2.22.23.02
Sep 2 2008
Serial0
Reformatted SD card and installed original SPL (renamed install.zip) and DREAIMG.nbh to the SD's root. When my phone eventually started in Bootloader (on its own), it went into the install phase, completed, and asked for reboot. I pressed the trackball (action button), it rebooted, and hasn't done a thing since.
mish12 said:
Also BIG! thanks for sh1tty cyan's wiki about flashing with dangerspl.
Click to expand...
Click to collapse
Cyan's wiki is one of the most well written, organized and constanly updated around. Don't blame wiki for something that you did.
Take a look at http://wiki.cyanogenmod.com/index.php?title=DreamangerSPL#Flashing_DangerSPL, how can anyone miss this?
Congrats on your new paperweight.
DUBsays said:
I wasn't trying to root or modify my phone in any way. It started flickering and then went black. Now...
Phone does not power on. Not with power button or any combo (camera+power; home+power; etc).
No LED notification. Not even orange when charging.
Eventually starts in tri-color/rainbow/RGB Bootloader ON ITS OWN (no keystrokes). Sometimes after 1 min, sometimes after 20+. Once in Bootloader, it stays there. If it's plugged in and charging, the Bootloader stays on even after battery pull.
Bootloader says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLID-4
RADIO-2.22.23.02
Sep 2 2008
Serial0
Reformatted SD card and installed original SPL (renamed install.zip) and DREAIMG.nbh to the SD's root. When my phone eventually started in Bootloader (on its own), it went into the install phase, completed, and asked for reboot. I pressed the trackball (action button), it rebooted, and hasn't done a thing since.
Click to expand...
Click to collapse
Do you have access to another battery? I would try that first. This is not a software issue, if new battery doesn't fix it... you may be better off getting another G1 of CL or Ebay (I hear of folks picking them up for less then $50 nowadays)