I just flashed from eclair to 1.6 (Cyanogen) and my phone is stuck at the bootscreen.
ddms reports that there is no recovery.img, but I can get into the recovery console, any fixes?
edit:
I did a full wipe, and reparitioned Fat + ext + swap, and I am using ext3.
Did you flash the base rom before flashing the cyanogenmod?
It looks like you somehow deleted your recovery image. Flash Amon_RA's recovery through fastboot. I beieve the code is
fastboot flash recovery recovery.img
and
fastboot reboot
That will replace whatever recovery image you have with amon_RA's.
Hi Everyone,
I am been visiting xda since I got my g1/adp1 over a year ago. I have been using it and it has been doing very well for me. Back in January I had flashed a rom and I had ended up with the hardspl. Since then for some odd reason, I was never able to flash the dangerspl or engineering spl. So from what I looked over on the forum, I used the dream.nbh file and went back to the original release and then flashed the cupcake update as advised in one of the posts here. After doing that, I was able to log in and install FlashRec and install the Amon Ra 1.6.2 recovery.
However, after doing that, I tried to flash the updated Radio and the hard spl, and I have been unsuccessful. Prior to installing the radio, I do the wipe/factory reset and then flash the ota-radio-2_22_19_26I.zip. After it complete it and pressing back + home, it even says writing radio image. However, when I boot into android or fastboot, it still shows that radio is 1.22.12.29. And the spl is the original 0.95.0000. I have also followed the procedure in the above link to install the radio then hard spl and then the cyanogen Cyanogen4.2.12.2 installation. I was able to boot into the rom; however the radio is still 1.22.12.29 and the spl is 0.95.0000.
With regards to info on the phone, it is DREA100 PVT 32B. So I would really appreciate anyone’s advice on how I can restore it to the engineering SPL or install the hard spl and then switch to the danger spl; and also update the radio. Thank you
zer003 said:
Hi Everyone,
I am been visiting xda since I got my g1/adp1 over a year ago. I have been using it and it has been doing very well for me. Back in January I had flashed a rom and I had ended up with the hardspl. Since then for some odd reason, I was never able to flash the dangerspl or engineering spl. So from what I looked over on the forum, I used the dream.nbh file and went back to the original release and then flashed the cupcake update as advised in one of the posts here. After doing that, I was able to log in and install FlashRec and install the Amon Ra 1.6.2 recovery.
However, after doing that, I tried to flash the updated Radio and the hard spl, and I have been unsuccessful. Prior to installing the radio, I do the wipe/factory reset and then flash the ota-radio-2_22_19_26I.zip. After it complete it and pressing back + home, it even says writing radio image. However, when I boot into android or fastboot, it still shows that radio is 1.22.12.29. And the spl is the original 0.95.0000. I have also followed the procedure in the above link to install the radio then hard spl and then the cyanogen Cyanogen4.2.12.2 installation. I was able to boot into the rom; however the radio is still 1.22.12.29 and the spl is 0.95.0000.
With regards to info on the phone, it is DREA100 PVT 32B. So I would really appreciate anyone’s advice on how I can restore it to the engineering SPL or install the hard spl and then switch to the danger spl; and also update the radio. Thank you
Click to expand...
Click to collapse
When installing a radio or SPL, you need to follow its instructions.
That means that when you start in recovery mode and flash the "update.zip" matching your radio, its first step is to write it (to the cache partition), then reboot into update-radio mode, then write it AGAIN (to the radio partition), then reboot into recovery and format the cache partition.
You need to follow it the WHOLE WAY THROUGH -- not stop at the first stage and call it good.
Hi,
As mentioned before, I did follow the guide to the T on re-rooting and reflashing. I followed both ttp://forum.xda-developers.com/showthread.php?t=606147 and also ttp://theunlockr.com/2010/04/26/how-to-root-the-htc-g1dream/ + ttp://theunlockr.com/2010/04/26/how-to-load-a-custom-rom-on-the-htc-g1-dream/ . However, neither of these procedures resulted in the installation of the hard spl or the updated radio ota-radio-2_22_19_26I. The adp1 continues to be to have the Original G1 Spl 0.95.0000 and radio 1.22.12.29 from the flashing of the Dream nbh file.
So could anyone please advise on what else I can do to flash and update the spl and the radio. Thank you ^^.
you can try to flash the radio through adb/fastboot its better and safer to do..
oh? can you please tell me the adb commands to use to flash the new radio? I have look at the ADB guide for dummies and ttp://forum.xda-developers.com/showthread.php?t=532719 & ttp://forum.xda-developers.com/showthread.php?t=517874 . I can't seem to figure out how to install radio via adb. When I had the hardspl, I could install radio, system, boot, etc via fastboot. But adb is unfamiliar to me as I have never been successful with it. So can you please guide me with the commands to follow ^^. Thank you in advance.
Thats what i meant was fastboot that was my noobieness to say adb.. flash radio thru fastboot...
Yes, fastboot is where I am trying to get too. However, the original G1 spl is not letting me access fastboot. If have files on the sdcard, in fastboot it shows serial0. But when I wipe it, it shows nothing under the original g1 fastboot mode.
So can someone advice me on what I can do to install hardspl or engineering spl to get fastboot working again T.T.
same problem
hi! am having exactly the same problem. stuck on stock SPL (hboot 0.95.0000) and radio (1.22.12.29). flashing radio via recovery (RA-dream-1.7.0) yields same results (formatting cache...). tried rebooting after reboot by radio but i still end up with old radio.
any thoughts?
i want to update radio so i can flash dangerSPL and be able to flash CM6.
TIA!
Yep, that's exactly how it works. First off, are you using T-Mobile USA?
Remember to NEVER flash DangerSPL on a 1.x, 4.x, or 6.x radio!!
The following are compatible radios that you can safely flash before you flash DangerSPL:
2.22.23.02 (T-Mobile USA)
3.22.26.17 (Rogers CA)
3.22.20.17 (Orange UK)
2.22.19.26I (Non-US)
Sent from my HTC Dream using XDA App
CyanogenMod V6.0.0 Stable / HBOOT-1.33.2005 / Radio 2.22.23.02 T-Mobile USA
using a T-Mobile G1 outside the U.S.
ok, since i can't update radio as it stands, here's my plan.
1. reboot to recovery mode
2. flash HardSPL
3. flash radio
(... if radio update successful)
4. flash DangerSPL
5. flash CyanogenMod6
6. do the funky chicken!
sounds good?
Yes, but I don't think that will make a difference. You should be able to flash the radio successfully on a stock HBOOT. I've never had problems flashing the radio before, so I don't know. But sure, you can update the HBOOT to HardSPL, but I don't think it'll make any difference.
Sent from my HTC Dream using XDA App
CyanogenMod V6.0.0 Stable / HBOOT-1.33.2005 / Radio 2.22.23.02 T-Mobile USA
exact same problem
Having the exact same problem. I have literally spent 2 days trying to do this.
Trying to do the whole CMwiki procedure, unlockr procedure, and various others.
Luckily I didn't brick it.
But I am in the same boat, now matter what I try, after flashing the radio via
recovery amon-ra 1.7 I check on fastbook and it is still 1.22 version of radio.
I have the stock Hboot, etc....
Has anyone had luck with fastboot / adb flashing the radio??
Thanks for any help.
machine*head* said:
Having the exact same problem. I have literally spent 2 days trying to do this.
Trying to do the whole CMwiki procedure, unlockr procedure, and various others.
Luckily I didn't brick it.
But I am in the same boat, now matter what I try, after flashing the radio via
recovery amon-ra 1.7 I check on fastbook and it is still 1.22 version of radio.
I have the stock Hboot, etc....
Has anyone had luck with fastboot / adb flashing the radio??
Thanks for any help.
Click to expand...
Click to collapse
Flash HBOOT 1.33.2003:
http://forum.xda-developers.com/showpost.php?p=6510019&postcount=76
Once 1.33.2003 is installed you can install 1.33.2005 via fastboot as on the post I linked to .. or skip directly to the newer 2708+ radios/SPLs with extra ram:
http://forum.xda-developers.com/showthread.php?t=831139
ok guys hopefully i can solve this problem.. i never had this issue but have had slight problems almost like so here was my solution....
Stage 1 un-rooting (very simple)
1. download update.zip and DREAIMG.nbh files here...
DREAIMG.nbh http://www.4shared.com/file/9izdCbvo/DREAIMG.html
update.zip http://www.4shared.com/file/ePnmmoxA/update.html
2. boot into recovery mode and do complete wipe of everything, also repartition your sd card set 0mb swap and 0mb ext..
3. then either use usb mounting through recovery or power off and place sd card in comp to copy files over.. than put back in phone and boot in recovery.
4. flash update.zip
5. power on in boot loader and flash DREAIMG.nbh
6. reboot and do normal setup just to make sure you are 1.0 firmware
Stage 2 Re-Root device..
1. download update.zip, flashrec, recovery.img, radio and spl files here...
1.5 update http://www.4shared.com/file/EyiKXmTd/update.html
flashrec http://www.4shared.com/file/ABXfQQ1H/flashrec-113-20091107-2.html
radio 2.22.23.02 http://www.4shared.com/file/jGTeRvfs/G1-radio-2_22_23_02.html
SPL http://www.4shared.com/file/nJkB58Qf/Latest_G1_SPL.html
recovery http://www.4shared.com/file/zCVPjMUz/recovery-RA-dream-v170-cyan.html
2. place files on your sd card than boot into recovery
3. flash update.zip (gets you to firmware 1.5)
4. now boot up normal and go to settings, check in applications and check unknown sources and usb debugging.
5. go to market and download "oi file manager" open app and select the flashrec file
6. when finished select open, then press backup recovery, then type in the box sdcard/recovery-RA-dream-v1.0.7-cyan.img then select flash recovery image.
7. when finished power off phone then boot into recovery.. wipe data factory reset, then flash the radio.zip press home+back to complete installation
8. wipe data again, now flash spl.zip, press home+back to complete..
9. now partition sd card.. i use 128mb swap and 1024mb ext4...
Stage 3 advanced rooting
1. download danger spl, fr boot, super wipe, radio and hboot files here...
fr boot http://www.4shared.com/file/gjRmpuh7/FR-boot-v157-CustomMTD_S.html
hboot (0.33.0013d) http://www.4shared.com/file/tfbsSTys/hboot0013d-signed.html
superwipe http://www.4shared.com/file/qm3gl7fQ/Ohsaka-SuperWipe_v2.html
radio (2.22.28.25) http://www.4shared.com/file/tMqoIX3p/update_2222825_S.html
2. place files on root of sd card
3. boot into revovery wipe data cache all that good stuff than flash the spl.zip let finish...
4. flash superwipe, power off than rebbot to recovery then do manual wipe of everything data, cache, battery, sd partition.. then repair sd..
5. flash the fr boot file, then go to console and type reboot recovery
6. flash radio file, let it finish then flash the hboot file.. power off than power on in fastboot mode (camera+power) and check phone stats.. should be on latest radio and hboot and s-on than you are free to flash roms from here...
My G1 randomly froze during operation. So I held down the power button to bring up the power menu and hit restart. After hitting restart nothing happened, so I took out the battery and put it back in and booted the phone up but it's stuck in the first boot (T-Mobile G1). I can boot into fast boot but not recovery.
I was using CM 5.0.8 with Radio 2.22.23.02.
I had some ROMs on the SD card, but fastboot would either say "No image" or "No image or wrong image"
I've formatted my SD back to FAT32 and tried these images, but I get the same messages in fastboot:
gapps-mdpi-FRF91-3-signed.zip
spl-signed.zip
update-cm-6.0.0-DS-RC2-signed.zip (might as well try CM 6 if CM5 from before wasn't being detected)
Can anyone help me?
Thanks in advance for any help
If you can get into fastboot, just flash a recovery back onto your device, then you can wipe and re-flash your rom. Your phone doesn't sound bricked.
tehseano said:
If you can get into fastboot, just flash a recovery back onto your device, then you can wipe and re-flash your rom. Your phone doesn't sound bricked.
Click to expand...
Click to collapse
sorry for calling it bricked. I didn't really know what to call it.
I gave that a try. I put Amon_Ra 1.7.0 recovery image on my SD card and fastboot doesn't recognize it
Don't put it on your sd card. You do it from your computer. Assuming you have your adb/fastboot drivers installed, just type this in console:
Code:
fastboot erase recovery
fastboot flash recovery C:\Path-To\Your-Image\name_of_recovery.img
I would suggest using ClockworkMod for your recovery, you can find it [HERE].
tehseano said:
Don't put it on your sd card. You do it from your computer. Assuming you have your adb/fastboot drivers installed, just type this in console:
Code:
fastboot erase recovery
fastboot flash recovery C:\Path-To\Your-Image\name_of_recovery.img
I would suggest using ClockworkMod for your recovery
Click to expand...
Click to collapse
Thanks for the quick replies. I've never installed/used fastboot on my linux box, but I quickly got that working and erased my recovery and flashed the new recovery you recommended.
I'm currently flashing my ROM!
Thanks for everything! You guys are the best!
Captain Falafel said:
Thanks for the quick replies. I've never installed/used fastboot on my linux box, but I quickly got that working and erased my recovery and flashed the new recovery you recommended.
I'm currently flashing my ROM!
Thanks for everything! You guys are the best!
Click to expand...
Click to collapse
Glad I could help.
Hi,
I've owned and ROM'd two Android phones, but not a G1 and wanted to help out a friend to get her stock 1.6 G1 to CM5. We ran into problems which led me to not want to continue before they are sorted out. I looked for answers to this but couldn't find any, so please don't flame me if I overlooked any. I tried to go by the instructions in the CM wiki.
This is what we did:
- We installed ClockWorkMod Recovery through the ROM Manager app
- We rebooted into that recovery and via adb flashed AmonRA recovery
- we rebooted into the AmonRA recovery which worked (I *think* just regularly holding Home while powering on)
- we flashed the appropriate radio update for her US TMo G1
- the documentation said "phone will reboot during update". I think it did, but it seemed stuck on "formatting cache" in recovery.
- when holding Home on reboot after that, it did from there on NOT reboot into the custom recovery
- instead, it rebooted into what looks like "bootloader" mode on my Moto Milestone, a screen with a phone and an exclamation point. We could get into stock recovery with Alt-L, but I don't think that is what we wanted.
At this point, it seemed to not reliably boot into custom recovery, so I didn't want to continue the process. I assume I could have gone down the same of flashing a custom recovery, but I wasn't sure what would happen with/after installation of the DangerSPL if booting into recovery wouldn't work.
So - is the "booting into bootloader instead of recovery" a known issue? Am I too much of a noob on the G1 and did totally miss something? Could or should we proceed to the DangerSPL / CM5 installation with this going on?
Any help would be much appreciated!
W0nk0
Flashing a new recovery from CM5 or CM6 is not working well. Try flashing the recovery image / radio image / ... from fastboot and you should be fine.
Edit: I did not read well the first time. Now I notice, that you are still on stock SPL, sorry. But re-reading well I've got a question: Are you sure you flashed already successfully a new recovery? For me it seems you are still on a plain stock G1.
Sent from my Htcclay's Superfly G1 using XDA App
Thanks a lot for your help!
We _were_ on a custom recovery twice, after flashing it from ROM manager (Clockworkmod then) and on the AmonRA recovery after that. As the recoveries clearly had non-stock things like nandroid I'm quite positive.
The problem seems to be that they didn't "stick" - we flashed the radio ROM upgrade from Amonra recovery, but after a reboot with Home pressed landed in the exclamation point screen again (which seems to indicate stock recovery as you can get to that with Alt-L from there).
If fastboot is indeed the way to go, where do I get the drivers for the windows/pc side of it? The noob guide I found had no help there :/.
Thanks again,
W0nk0
Sent from my Dell Streak using Tapatalk
Few things;
1) if you have the OEM system image, then, indeed, the recovery will be overwritten by the OEM recovery image upon reboot into the system.
2) You say that you've written a RADIO image.... ***WHAT*** radio image did you write? You should have written a radio with a version number that starts with a "2".
3) Have you written a new SPL? The SPL you should write is 1.33.2003. DO NOT install deathSPL, no matter how many RETARDS suggest it. There is ABSOLUTELY NO USE in it. 1.33.2003 is SAFE to install (unlike 1.33.2005), and the ONLY benefit of 1.33.2005 has been GREATLY EXCEEDED, making that "benefit" entirely pointless.
Note that with the stock SPL (0.95.0000), there IS NO FASTBOOT. 1.33.2003 has a very strong fastboot capable of writing ALL partitions, including the radio image. Fastboot is the safest way to write the radio and SPL, but prior to installing an SPL with a strong fastboot mode, obviously you can't use this feature.
Steps:
1) Reinstall custom recovery,
2) reboot into recovery and write 1.33.2003 SPL.
3) DO NOT let it boot into regular system prior to installing 1.33.2003 SPL, or it will overwrite that custom recovery.
4) After installing the good SPL, it would still overwrite the custom recovery by booting into the regular system, but by this time, you will have FASTBOOT, so it doesn't matter.
5) Now do what you want... but once you have a 2.x radio and 1.33.2003, do NOT write any other radio or SPL, and for F SAKES DO NOT RUN ANY NBH FILES EVER NO MATTER WHAT!!!
My G1 is stuck on Amon RA recovery....I tried to use firerat's method and after i flashed foroyo rom its stuck in the recovery...but it doesnt show any options...
Just
Build : RA-dream-v1.7.0
thats it i cant do anything....
i know i didnt brick my phone...please help...
[Solved]
solution : install fastboot and you can erase the system...
C:\\ .......android-sdk-windows\tools\fastboot devices
C:\\ .......android-sdk-windows\tools\fastboot -w
C:\\ .......android-sdk-windows\tools\fastboot flash recovery [recovery path with ".img"]
walla your recovery is overridden by the new one...
Most likely you did not completely follow the instructions how to install mtd, but nevertheless what SPL do you have installed? If you have 1.33.2003 I suggest to flash recovery again using fastboot and you are rescued.
Otherwise ... I don't know. Even if you are able to connect via adb I do not expect you can flash a new recovery while beeing in recovery. For sure you are able to go into bootloader install dreamimg.nbh, etc. but this would mean to do the hole rooting process again.
AndDiSa said:
Most likely you did not completely follow the instructions how to install mtd, but nevertheless what SPL do you have installed? If you have 1.33.2003 I suggest to flash recovery again using fastboot and you are rescued.
Otherwise ... I don't know. Even if you are able to connect via adb I do not expect you can flash a new recovery while beeing in recovery. For sure you are able to go into bootloader install dreamimg.nbh, etc. but this would mean to do the hole rooting process again.
Click to expand...
Click to collapse
thankx man for replying....i kinda fixed it ...i followed this step
http://forum.xda-developers.com/showthread.php?t=807183&page=13
post number 160
but afte i Flash FR-recovery-v1.5.3-CustomMTD_S.zip and reboot to recovery my amon recovery goes blank...kinda funny....
actually you can do anything with fastboot...erase system...flash recovery...i couldnt flash a rom..but was able to override the recovery....that all i needed...