Database Develop

how did i make my g1 into an adp?/bootloader instead of recovery

Well, I've been browsing around here for a few months ago, and rooted my phone the day I registered. Today I decided to try and install the CyanogenMod. The thing is, i guess i got scared while it was booting because i was coming from JF 1.5, so i installed CyanogenRecovery. Then i decided to try a wipe. However, when i held Home+End or Home+Back, it loaded into the bootloader! I thought this was weird, and ended up restoring my phone from the bootloader. When my phone turned on, it said, Welcome to Android Dev Phone 1. Please press the android to continue.
also, i think this is amazing and all, but i cant install any themes.
Now, whenever i try to go to recovery to install the Hero theme, it just goes into bootloader.
any suggestions?

You sure you're pressing the right buttons? Recovery is home+power. Also, you made your phone into an ADP isn't something new. ADP is just a software version without extras like IM I believe and amazon mp3. Nothing really different.

anakin908 said:
Well, I've been browsing around here for a few months ago, and rooted my phone the day I registered. Today I decided to try and install the CyanogenMod. The thing is, i guess i got scared while it was booting because i was coming from JF 1.5, so i installed CyanogenRecovery. Then i decided to try a wipe. However, when i held Home+End or Home+Back, it loaded into the bootloader! I thought this was weird, and ended up restoring my phone from the bootloader. When my phone turned on, it said, Welcome to Android Dev Phone 1. Please press the android to continue.
also, i think this is amazing and all, but i cant install any themes.
Now, whenever i try to go to recovery to install the Hero theme, it just goes into bootloader.
any suggestions?
Click to expand...
Click to collapse
Its ADP because thats the what firmware Cyanogen uses.
Your recovery image isn't installed properly. Download and reinstall Cyan's recovery image through adb/fastboot or terminal as per his thread

[RESOLVED] G1 hangs on boot, with lots of extra info

I have a G1 with CyanogenMod 1.4 recovery and the original SPL. It boots into either of those just fine.
When I select to apply any zip, I get the list of possibilities. I have tried wiping many times.
Whenever I choose an option from the recovery or flash something, a message appears that says
Code:
E: Can't read MISC:
(No space left on device)
This occurs even after a wipe. Also, I know that the SD card is not full or corrupted (I generally use it in a different G1).
After I have flashed something and reboot, it simply hangs at the G1 boot screen. I left it for half an hour, and it stayed that way.
Any thoughts?

what are you trying to flash? rom might require danger spl. i don't have a g1, so i'm not positive, but i'm willing to bet on it.

I actually tried flashing the danger SPL. In spite of saying "reboot to complete installation," I know it does not work. if I hold Camera as I turn on, it is still the original SPL.
Next bet?

tal82k said:
I actually tried flashing the danger SPL. In spite of saying "reboot to complete installation," I know it does not work. if I hold Camera as I turn on, it is still the original SPL.
Next bet?
Click to expand...
Click to collapse
1.33.2005 is what the danger spl shows up as, which i believe is your "stock" spl. if you installed it and rebooted without any errors it works. simple and plain.

Does the danger SPL look like the original (RGB color testing)? That is what shows up when I boot with camera pressed.
I was trying to flash either Super D or CyanogenMod, when I follow the instructions for either of them and do the final reboot, it never leaves the G1 logo screen. Yes I know that it is a while for the dalvik-cache to be reworked.
I have flashed roms successfully many times on my other G1.
I am very curious what the error message that I posted earlier means. Thanks for your suggestions!

Sorry for the double post. I have an update. I am pretty sure there is a problem with the NAND chip or something similar. I flashed the Amon_RA recovery, and it worked. I used Amon_RA to wipe, and re-partition the SD card. I then tried flashing the HTC 1.6 image for ADP1. And it worked. It booted into 1.6 with no problem (except that I no longer had root). So I tried to get root again. First I tried the Recovery Flasher app. It said that it failed. So I downloaded the DREAIMG.nbh to get back to RC29. When I ran it, I got
Code:
DREAIMG.nbh - FAIL
Update Terminate
UPDATE FAIL
Any thoughts are appreciated. Thanks!

[RESOLVED]
UPDATE: Apparently that last bit ended with bricking the phone. I took out the SD, put DREAIMG.nbh back on it. Put it back in the phone. Re-flashed from the SPL (holding camera while pressing power). It worked. I then went through with regular rooting, putting Amon_RA on there, with Super D 1.8. Everything smooth. I have no idea what really fixed it, but everything works fine.

tal82k said:
UPDATE: Apparently that last bit ended with bricking the phone.
Click to expand...
Click to collapse
i still lol every time i hear that. phixed my brick.

Yeah.... I wish my brick would go into SPL.

*sorry double post, browser messed up*

Stuck on G1 Splash Screen after 1st Root to v. 4.2.15.1

A few days ago, I attempted to root my girlfriend's T-Mobile G1 phone, previously unrooted, by following the CM instructions in the CM Wiki page for G1 users.
Throughout the entire process, I received the expected output from the g1 screen - that is, until finally installing the latest CN stable ROM - 4.2.15.1. After this install completed from recovery mode, I rebooted the phone by pressing home + back, the screen displayed an image of a box and phone, and then proceeded to the recovery screen again; I rebooted the phone again - this is when the phone started to hang on the G1 screen.
There is a chance I may have forgotten to flash the CN ROM 4.2.15.1 before rebooting, and then subsequently flashing the CN ROM. I am not completely sure about this.
Anyways, here are the steps I took: Formatted SD Card to FAT 32; Downgraded my phone to RC29 - DREAIMG.nbh using the bootloader; after saving the recovery image file cm-recovery-1.4.img to my SD root dir, I used telnet to flash that recovery file. Next, I downloaded all the necessary OS files - DRC83 Base Defanged; Updated Radio file; 4.2.15.1 ROM. Next, in recovery mode, I wiped the phone, and proceeded to install those files in that order.
After getting the hang on the G1 splash screen, I tried to repeat the process over, from flashing the old RC29 ROM to flashing the updated ROM files. However, I have gotten the same result. Now, after reading about how to revert rooted G1 phones back to the stock firmware, I have managed to get the phone running on Cupcake - 1.5, through the CRB43 update. The CRC1 Update consistently fails during the installation - something like patch error code - failed update on line 243. I guess I may need to wait for a system update from t-mobile to get the phone up to date again.
I thought the original problem may have been a corrupted file - but I have repeated this rooting process many times, and have downloaded new files each time, and usually tried to confirm the MD5Check hash, so I doubt this is the problem. Also, today, I received a system update from TMO, and even then, the system hung on the G1 screen again. I've tried to fix this problem myself, but man, I'm at a dead end.
Any advice would help.

I have the same issue, although it first happened while I tried to upgrade from superD to CM5.
The only ROM I can get to run is the ADP1.6 from htc (the -ota- one)
I've tried every ROM and I can't even Nand back to my previous backup...
The thing is driving me nuts, but, although I reinstalled DangerSPL (with success), I can't run (because installation goes fine) anything else than stock 1.6 (which is still better than your cupcake my poor friend).
Even Defranged DRC83 won't run.
All ROMs get stuck on G1 screen...
I've opened a thread about this but so far, got no working advice.
If I have some time available, I'll try switching back from Amon_Ra's recovery 1.6.2 to Cyanogen's recovery 1.4 to see if it works (hell, that's the only thing I haven't tried. Spent a whole weekend on this ****...)
Let me know if you manage to run a custom ROM.
Good luck

alou2 said:
I have the same issue, although it first happened while I tried to upgrade from superD to CM5.
The only ROM I can get to run is the ADP1.6 from htc (the -ota- one)
I've tried every ROM and I can't even Nand back to my previous backup...
The thing is driving me nuts, but, although I reinstalled DangerSPL (with success), I can't run (because installation goes fine) anything else than stock 1.6 (which is still better than your cupcake my poor friend).
Even Defranged DRC83 won't run.
All ROMs get stuck on G1 screen...
I've opened a thread about this but so far, got no working advice.
If I have some time available, I'll try switching back from Amon_Ra's recovery 1.6.2 to Cyanogen's recovery 1.4 to see if it works (hell, that's the only thing I haven't tried. Spent a whole weekend on this ****...)
Let me know if you manage to run a custom ROM.
Good luck
Click to expand...
Click to collapse
I have this problem too, first time rooting for me too... I used this guide:
http://forum.xda-developers.com/showthread.php?t=548924&highlight=root
and got stuck on the G1 screen after pressing Back and Home after installing the same version of cyanogenmod

I may have bricked my HERO2000 trying to flash a custom ROM.

I'm new to this whole flashing custom ROMS business. I have a CDMA HTC Hero 2000 and I downgraded to the original 2.1 before the update just fine, rooted my phone just fine. Then I tried to flash Aloysius to it using instructions I found here: [Complete Guide] How To Flash A Custom ROM To Your Android Phone With ROM Manager + Full Backup & Restore | Android News, Reviews, Applications, Games, Phones, Devices, Tips, Mods, Videos, Podcasts - Android Police
After all was said and done, my phone starts to boot with the "HTC quitely brilliant" logo, following by "SPRINT the Now network" logo and after it shows "Now" for many seconds (as it normally does before pulling up the home screen), it reverts back to the HTC logo and repeats this process until I remove the battery.
I removed the microSD and attempted to boot, same thing. Then I held down HOME+BACK+POWER to do a manual hard reset, this took a little longer but again had the same result.
I may just cry now. Please help!!

Run the official sprint ruu, and see what that does for u. Then read the rooting guide here on xda and try it. I personally recommend amon ra recovery to flash roms, rom manger never seemed to work right. Feel free to pm for more help, dont worry u prob arent bricked unless u flashed a gsm rom (which aloysius isn't)
Sent from my HERO200 using XDA App

That's a bootloop not a brick You could try downloading a different rom and flashing it in recovery, nandroid restoring - if you made one, or flashing the same rom again. just wipe your phone before (data/cache/dalvik)

Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.

chrisdegraw said:
Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.
Click to expand...
Click to collapse
Four key words to remember when trying out any new rom
Nandroid is your friend!
additionally, you should always remember to wipe before loading a new rom!
Enjoy!

Yeah, don't ever panic, that was, as everyone said, a bootloop by textbook definition. I've never seen a brick before, but I'm damn sure it won't get as far as the Sprint logo. The only way to brick a CDMA Hero is to flash a GSM Radio/Bootloader to it.

[Q] Boot loop after installing Danger SPL, Cyanogenmod 6.1 and Google Apps

I'm helping a friend with a hand-me-down G1 upgrade from 1.6 to CyanogenMod 6.1 using the wiki cyanogen links, which basically told me to downgrade to RC29 / RC7 DREAIMG.nbh file after reformatting the sdcard, then root the phone using telnet, flash Amon_Ra's Recovery using telnet, flash 2.22.23.02 radio using recovery, then install dangerspl, cyanogenmod 6.1 and tiny google apps.
As far as I know, I followed every step. I did get stuck a couple of times while installing DangerSPL. I'd fastboot and hit call+menu+end and instead of rebooting, it would install dreaimg.nbh again (since I used fastboot to flash dreaimg.nbh earlier and still had it on the root of the sdcard) and I would have to start over again and re-root, re-flash Amon_Ra's Recovery and the 2.22.23.02 radio. That happened twice before I decided to take dreaimg.nbh off of the sdcard, since I realized that it had already been flashed onto the phone and would probably work. Once I did that, the call+menu+end during fastboot worked and it restarted, which is what it was supposed to do. Kept trying and trying to hit the home button as quickly as possible to get to recovery, like the instructions said, but it wouldn't work. So I took a chance and booted into recovery using home+power and flashed Danger SPL, which seemed to install well, and Cyanogenmod 6.1 and tiny google apps. All seemed to be going well until rebooting the system. The cyanogenmod splash screen popped up after the g1 screen and just sits there, stuck in a boot loop. I waited a good 10 minutes before I pulled the battery and tried again...same thing. Also wiped the dalvik cache and cache, which i saw on the first page of this thread, to no avail. Can anyone tell me where I went wrong and what I can do to pull out of it and successfully install this rom? Really want to get this back to my friend. Also hoping his contacts are still on his sim card after all this... I flashed dreaimg.nbh, per the first step, and noticed that the contacts didn't come up after this. The data on the phone works and the phone number shows up under about phone but since I haven't gotten any further than that OS I can't tell. No where have I seen in the instructions that I had to pull my sim card before flashing... hope it's all good. Any help with any of this would be greatly appreciated.
As you can tell, I'm new to all this. I own a Samsung Moment and flash ROM's on it all the time but that process is much simpler than this one. Have never dealt with a boot loop so I'm a little unsure of what to do.

ejatx said:
I'm helping a friend with a hand-me-down G1 upgrade from 1.6 to CyanogenMod 6.1 using the wiki cyanogen links, which basically told me to downgrade to RC29 / RC7 DREAIMG.nbh file after reformatting the sdcard, then root the phone using telnet, flash Amon_Ra's Recovery using telnet, flash 2.22.23.02 radio using recovery, then install dangerspl, cyanogenmod 6.1 and tiny google apps.
As far as I know, I followed every step. I did get stuck a couple of times while installing DangerSPL. I'd fastboot and hit call+menu+end and instead of rebooting, it would install dreaimg.nbh again (since I used fastboot to flash dreaimg.nbh earlier and still had it on the root of the sdcard) and I would have to start over again and re-root, re-flash Amon_Ra's Recovery and the 2.22.23.02 radio. That happened twice before I decided to take dreaimg.nbh off of the sdcard, since I realized that it had already been flashed onto the phone and would probably work. Once I did that, the call+menu+end during fastboot worked and it restarted, which is what it was supposed to do. Kept trying and trying to hit the home button as quickly as possible to get to recovery, like the instructions said, but it wouldn't work. So I took a chance and booted into recovery using home+power and flashed Danger SPL, which seemed to install well, and Cyanogenmod 6.1 and tiny google apps. All seemed to be going well until rebooting the system. The cyanogenmod splash screen popped up after the g1 screen and just sits there, stuck in a boot loop. I waited a good 10 minutes before I pulled the battery and tried again...same thing. Also wiped the dalvik cache and cache, which i saw on the first page of this thread, to no avail. Can anyone tell me where I went wrong and what I can do to pull out of it and successfully install this rom? Really want to get this back to my friend. Also hoping his contacts are still on his sim card after all this... I flashed dreaimg.nbh, per the first step, and noticed that the contacts didn't come up after this. The data on the phone works and the phone number shows up under about phone but since I haven't gotten any further than that OS I can't tell. No where have I seen in the instructions that I had to pull my sim card before flashing... hope it's all good. Any help with any of this would be greatly appreciated.
As you can tell, I'm new to all this. I own a Samsung Moment and flash ROM's on it all the time but that process is much simpler than this one. Have never dealt with a boot loop so I'm a little unsure of what to do.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=566669 also I just got off that build it's really really slow, try yoshi's gingerbread build.