Related
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...
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!!!
Hi,
After successfully rooting a G1 stucked on TIM startup logo without any knowledge of versions with this method :
After downgrading using DREAIMG.NBH to:
Firmware 1.0
Radio 1.22.12.29
Build no. RC7
Amon recovery-RA-dream-v1.5.2.img
and I got old SPL and 1.22.12.29 Radio then I had installed JFv1.41 ADB ROM.
Then I had installed Hard SPL 1.33.2005 & 2.22.19.26I Radio to install CM6.1 or other newer ROMs:
But every time I install new rom via recovery manager (with power + holding home key) and not with fast boot, after restart it stuck in boot logo even I do Wipe data. I have tried with many type of ROMs.
So I reinstall JFv1.5 rom: it works!
Any solution for this issue ?? I want to get newest Rom on G1.
Also my recovery manager become : Android system recovery utility Built: JFv1.41. even I tried to reinstall Amon recovery-RA-dream-v1.5.2.img with terminal and telnet and no chance. (permission denied)
BR
Thanks in Advance.
Assuming you have sdk with fastboot set up properly to run fastboot commands. You should try this. Only if you understand the instructions and dont take shortcuts.
http://forum.xda-developers.com/showthread.php?t=831139
MAKE SURE YOU KNOW WHAT YOU'RE DOING THOUGH. Good luck
I'm not too experienced in flashing roms so please have some patience with me.
I recently installed the ota update from htc and then unlocked the bootloader through the official htcdev site. I then flashed clockworkmod recovery through fastboot and flashed cm7 through CWM. I'm still running cm7 at the moment.
However, I am now not able to restore my phone back to the stock rom. I tried to restore the stock rom through a backup I did on nandroid in CWM. It went through all the steps and told me that the backup has been successfully restored. But after choosing the reboot phone option, the screen shows the white HTC screen, followed by a black screen for a couple of seconds, then the white HTC screen again, and then it finally brings me to CWM.
I'm not sure what I can do to restore my phone to stock rom. I went back to cm7 and tried to restore using ROM manager but it didn't work out too.
Help please!
Hboot 2.00
Radio 3822.10.08.28_M
(I'm not sure what other info might be needed so just let me know and i'll post it on here)
I have the same issue, I have a feeling about the cause but it is just a brainstrom. I could be wrong.
It might have something to do with ext4 vs ext3 file system. Custom roms usually format your phone in ext4 format while the stock rom only supports ext3
I would try and search a a format script that formats in ext3. (zip file format so you can flash it through clockwork or something)
fallenwout said:
I have the same issue, I have a feeling about the cause but it is just a brainstrom. I could be wrong.
It might have something to do with ext4 vs ext3 file system. Custom roms usually format your phone in ext4 format while the stock rom only supports ext3
I would try and search a a format script that formats in ext3. (zip file format so you can flash it through clockwork or something)
Click to expand...
Click to collapse
Awesome if you do manage to find it please post it
crunchyHTC said:
I'm not too experienced in flashing roms so please have some patience with me.
I recently installed the ota update from htc and then unlocked the bootloader through the official htcdev site. I then flashed clockworkmod recovery through fastboot and flashed cm7 through CWM. I'm still running cm7 at the moment.
However, I am now not able to restore my phone back to the stock rom. I tried to restore the stock rom through a backup I did on nandroid in CWM. It went through all the steps and told me that the backup has been successfully restored. But after choosing the reboot phone option, the screen shows the white HTC screen, followed by a black screen for a couple of seconds, then the white HTC screen again, and then it finally brings me to CWM.
I'm not sure what I can do to restore my phone to stock rom. I went back to cm7 and tried to restore using ROM manager but it didn't work out too.
Help please!
Hboot 2.00
Radio 3822.10.08.28_M
(I'm not sure what other info might be needed so just let me know and i'll post it on here)
Click to expand...
Click to collapse
fallenwout said:
I have the same issue, I have a feeling about the cause but it is just a brainstrom. I could be wrong.
It might have something to do with ext4 vs ext3 file system. Custom roms usually format your phone in ext4 format while the stock rom only supports ext3
I would try and search a a format script that formats in ext3. (zip file format so you can flash it through clockwork or something)
Click to expand...
Click to collapse
With the unlocked bootloader, when the device is in recovery mode, it cannot overwrite the boot.img partition. So when you flash a custom ROM in CWM, you must manually extract the boot.img file from the zip file and flash it manually in Fastboot mode using the command:
fastboot flash boot boot.img
In the case when you are attempting to restore a previous backup, the same is true, except in this case you would manually flash the boot.img from the CWM backup folder in Fastboot mode.
This should solve both of the situations you have encountered.
Okay that method worked a charm. Just flashed back the stock rom.
Thanks for much for that!
crunchyHTC said:
Okay that method worked a charm. Just flashed back the stock rom.
Thanks for much for that!
Click to expand...
Click to collapse
Weird, didnt work for me. Dit you manually flashed the boot.img extracted from the nandroid backup?
Yup. So i took the backup from my sd card and put the backup onto my computer. Then I used clockworkmod recovery to restore the backup, and then used fastboot on the computer to manually flash boot.img through usb.
Hope that helps
Cannot restore with the procedure.
I have been trying to restore stock rom but I'm unable to do it.
I flashed boot.img using command prompt.
Restored it via Clockworkmod recovery but after restoring when i reboot the phone, it again takes me to recovery mode.
What should I do?
Maybe it is because you have changed the backup name.. I heard that if you change the stock from backup name you will wreck the md5sum ...
___________________________
Device: HTC Incredible S
Bootloader: S-OFF - ENG
Rom: ARHD 2.2.0
Android for life!
NicOsol said:
Maybe it is because you have changed the backup name.. I heard that if you change the stock from backup name you will wreck the md5sum ...
___________________________
Device: HTC Incredible S
Bootloader: S-OFF - ENG
Rom: ARHD 2.2.0
Android for life!
Click to expand...
Click to collapse
No..I have not changed anything.
I even tried formatting it in ext3 using Touch recovery and then tried to back up..but it didn't work.
It just keeps on taking me to recovery mode when I reboot.
Why don't you guys get s-off? I'll post a link when I'm on my PC on how to do it. That way, you won't have to flash the boot.img each Time you install a new rom...
Sent from my HTC Incredible S using XDA
tpbklake said:
With the unlocked bootloader, when the device is in recovery mode, it cannot overwrite the boot.img partition. So when you flash a custom ROM in CWM, you must manually extract the boot.img file from the zip file and flash it manually in Fastboot mode using the command:
fastboot flash boot boot.img
In the case when you are attempting to restore a previous backup, the same is true, except in this case you would manually flash the boot.img from the CWM backup folder in Fastboot mode.
This should solve both of the situations you have encountered.
Click to expand...
Click to collapse
Hello, I tried with "fastboot flash boot boot.img" took the boot.img from the backup and then I did a restore but it always goes into recovery mode, what else can I do?
Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.
Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'