First ever attempt at rooting...problem..! - G1 Q&A, Help & Troubleshooting

So I followed a guide on youtube for rooting the g1 (should have followed ones on these forums ).
1. I am from the UK so downgraded to the DREAMIMG-RC7.zip first.
2. Then I installed the hardspl (update) and recovery.img.
3. Then did the telnet commands
4. Then downloaded command emulator and entered the commands
5. Finally I updated with the update.zip.
this is where it went wrong
6. I then tried to install open eclare but got this error :
E:Can't chown/mod /sytem/xbin/su
(no such file or directory) E:Failure at line 240: set_perm 0 0 04755 SYSTEM:xbin/su
Installation aborted
7. I rebooted it by back and home but it now gets stuck at the tombile g1 logo part.
I can press home and power to get to the screen, and camera and power does work.
Question...can I just start again by connecting the sd card to my computer card reader and then putting back the DREAMIMG-RC7 and starting again?

Which recovery image are you using?
You might want to try a different rom before openeclair, it needs the death spl, which you don't want to touch just yet. I recommend superD or htcclay fasttest.
Upgrade your radio as well if you haven't already. If you go near the deathspl with the original radio, you'll find out why it's called death.

You got the error because that rom requires the 1.33.2005 spl. Link for radio and SPL are in my sig.

Related

rooting issues

so I tried to Root my Dream and choose after a number of failed attempts I have decided to just give up so I want to wipe and restore my phone's OS the factory but when I try though the settings menu the phone restarts then just sits on the "Rodgers" logo for ever so is there anyway to fix that?
Don't give up so soon
I definitely recommend rooting. The rogers firmware sucks by default imo. I did not like my phone at all until I rooted.
Check this guide by HyeProfile, I just used it on a new rogers dream and it worked 100%:
http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
If you really don't want to root, you can follow the steps to try flashing (using the same instructions he gives in that post) with the official rogers radio.img and recovery.img here: http://www.stevebirstok.com/android/losemyroot.zip
well I hate how slow my phone feels so I'm going in for the root again thanks for the push to try again.
ok ran into an issue:
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (No such file of directory)
E:Can't mount SDCARD:update.zip
Installation aborted
when trying to apply update.zip
Loading001 said:
ok ran into an issue:
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (No such file of directory)
E:Can't mount SDCARD:update.zip
Installation aborted
when trying to apply update.zip
Click to expand...
Click to collapse
that means it can't see your sdcard.
see if dropping into the recovery console(alt+x) and typing
Code:
mount /sdcard
recovery
see if that helps anything since that command will mount your sdcard which it appears to be failing to read.
when I try enter the console all the options are removed form the screen then nothing happens all I see is the yellow text.
The yellow text I'm talking about is the error message I posted.
if you are trying to unroot it, use the same rc package that you use to downgrade it in the bootloader (camera and power) and run the .nbh there
Loading001 said:
ok ran into an issue:
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (No such file of directory)
E:Can't mount SDCARD:update.zip
Installation aborted
when trying to apply update.zip
Click to expand...
Click to collapse
Are you sure your sdcard is formatted to FAT32?
I'm going o try that when I get home
ok so it's weird.
E:Multiple firmware images
E:can't store hboot images
E:failure at line 1
write_hboot_image PACKAGE:hboot.img
install aborted
ok so now it just sits on the "Rogers" logo and wont enter any mode (camara+power)
edit: looks like that means I biked the thing hope they will replace it (i'll just blame it on their firmware update thing)
edit2: calling rogers to try get a replacement
will it it read an .nbh in the bootloader?
I don't know how can I test that or see if it will?
I was refering to the dreaimg.nbh from either rc29 or rc7 that you use to downgrade your phone in order to root it, that use the bootloader camera + power
no it wont enter any mode at all just sits on the rogers logo so a new phone should show up in the next 3 to 5 days
this kinda scares me off from trying again but I want to so I might.
got a all new phone and it still wont mount the Sd card like last time
ok so i helped some one root their rogers phone last night. are you trying to flash the radio, or have you followed all of the fastboot commands in the "rogers heres your real root" thread? the guy i was helping couldn't flash the radio but we got it with the fastboot commands
no I'm past loading recovery.img with fastboot and I'm trying to apply the update.zip
thats very odd. so you did all the fastboot commands and still can't get it to work?
is it any rom you try to flash?
well I was following the guide in one of the first posts

stuckked at recovery screen

hi
i installed 1.4CM + JF but i did not update via update.zip
then i wanted to flash a Hero rom,
Fatal1ty-Hero-Full-v1-4-zip (HTC Hero ROM for Magic by Fatal1ty)
but it gave error and stuckked at recovery screen always i start phone.
when i want to update:
"E:can't chown/mod /system/xvin (No such file or directory)
E:failure at line 9:
set_perm_recursive 0 2000 0755 0 6755 system:xvin
Installation aborted"
infos of phone:
"drea110 pvt 32B
Hboot_0.95.0000
cpld_4
radio_2.22.19.26I
Sep 2 2008"
i dont have a Backup
should i install HardSPL?... (HSPL10.95.3000) ?
what is solution?
is this phone rooted? how can i understand it?
thanks
did you even read the OP to almost every single hero rom? you have to have the 1.33.2005 spl to flash most any hero rom, there is one (could be more, haven't checked though) that will fit on the hard spl.
to get a rom back on your phone and the phone to a working state go into the recovery console from the recovery screen and type
Code:
ums_enable
to mount your sdcard to your computer and type
Code:
ums_disable
to unmount it after you put a rom on there that does not require the 1.33.2005 spl. such as cyanogen's or enomther's roms.
thanks a lot, it was not written at Fatal1ty's page, so i thought it's simple
i know tried
#ums_enable
/dev/block/mmcblk/ #
and connected to Pc, installed drivers ((http://dl.google.com/android/android_usb_windows.zip)
it still doesnt show the Mass Storage disk in My computer (windows)
there is a disk F: but when i click it it says put a disk in driver etc..
it seems i need a microsd card reader?... otherwise i dont see sdcard
ok i restarted it and now i can see as Mass Storage.. thanks
i have now HSPL10.95.3000 and RADIO-2.22.19
i think it mean i can flash any rom now
If you haven't rooted your phone, cause you said how do I know if it's rooted, you need to root it in order to flash a custom rom.

Need help loading roms!!!!

I went ahead and rooted my G1 using the flashrec.apk method through linda. When ever the rooting is complete, I go ahead and restart my device in recovery mode to flash a custom ROM, but everytime the rom is copying files, i get the following error message:
E:Cant chown/mod /system/xbin
(No such file or directory)
E:failure at line 80:
set_perm_recursive 0 2000 0755 0
6755 SYSTEM:xbin
Installation aborted.
I followed all the rooting steps precisely and it seems to root fine, but no matter what ROM i try to flash, i continue to get this error. Can somebody please help me out with this???
fyi...I have tried at least 5 different ROMS posted here on XDA and each one gives me the same error above...
Did you take out the battery and the SD card and place them back in before you loaded the rom? Take out the SD card and then take out the battery, put back in the sd then put back in the battery. WIPE EVERYTHING, and try again.
Also see if you partitioned your sd correctly.
If that doesn't work, try un-rooting then re-root your phone.
And start over.
u need to FLASH THE NEWEST RADIO.....then read up on how to flash the DEATH SPL....u didn't search because that is the most common error for people who have hard spl when the nead the 1.33.2005 spl go search
Look in Q&A and ask there, search is your friend. make sure when you find the relevant thread and ask, you tell people which recovery image , radio and all you are using as well as the Rom you're trying to flash. Sounds to me like you're trying to flash a Rom that requires the danger all and you don't have it
Wrong Section, and have you tried this Klick Me
-> Moved to Q&A
the-equinoxe said:
-> Moved to Q&A
Click to expand...
Click to collapse
OT iknow, but Eq, your on the ball tonight bro

Need Help...can't Downgrade To Rc29

So I've had my G1 for a while now on the stock non-rooted OS and I decided to try to get a 2.1 rom installed on it. After looking around and reading quite a bit, I primarily went off of this blog post to get it done. hxxp://www .myhangoutonline.com/component/content/article/342-tutorials/7-root-and-upgrade-your-g1
I got it downgraded to RC29 successfully and went through the rooting process. Once I tried to reboot it into recovery mode, my phone just sat at the G1 screen indefinitely. Waited up to an hour and restarted the entire process about 3 times with the same result. Then I started looking around thinking maybe the DREAIMG.nbh file that was provided was no good and I got one linked off of this site hxxp:// androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
So the next time I tried to start over by restoring to the RC29 image it gets all the way through and fails at the end. It says "Update Terminate UPDATE FAIL". I tried going back to the image that worked a few minutes prior to that and I'm getting the same thing.
Any ideas on what I need to do? I'm stuck without a phone until I get this resolved...
Your post is difficult to understand.
The first question:
WHY did you install an NBH file?
The second question:
WHAT *exactly* did you do to the thing?
The third question:
WHY are you trying again to install an NBH file?
The fourth question:
What is it doing now?
The fifth and final question:
HOW can you possibly justify following a bunch of steps that some retard spewed out on a "blog"?
Note: NEVER NEVER NEVER NEVER write an NBH file to your phone!!! Especially once you have root! NEVER.
Note2: you say its stock tmoble-branded htc dream? That means android 1.6 and I believe susceptible to the 1-click-root bug... why didn't you run the 1-click root?
What happens if you try to boot the phone ***NORMALLY*** (instead of recovery)?
What happens if you plug in the USB and run "adb logcat"?
lbcoder said:
Your post is difficult to understand.
The first question:
WHY did you install an NBH file?
The second question:
WHAT *exactly* did you do to the thing?
The third question:
WHY are you trying again to install an NBH file?
The fourth question:
What is it doing now?
The fifth and final question:
HOW can you possibly justify following a bunch of steps that some retard spewed out on a "blog"?
Note: NEVER NEVER NEVER NEVER write an NBH file to your phone!!! Especially once you have root! NEVER.
Note2: you say its stock tmoble-branded htc dream? That means android 1.6 and I believe susceptible to the 1-click-root bug... why didn't you run the 1-click root?
What happens if you try to boot the phone ***NORMALLY*** (instead of recovery)?
What happens if you plug in the USB and run "adb logcat"?
Click to expand...
Click to collapse
1. I installed the nbh file because that's what was in every single set of instructions I've found said to do. Step 1 is to downgrade your phone to RC29 for US phones, and the DREAIMG.nbh file is the way to do that from everywhere that I've seen, mostly here and the cyanogenmod forums. If there is a better guide to follow, please link me.
2. I've already explained this. I followed the following instructions:
1. Format your phone's SD card to FAT32 mode:
o Hook your phone up to your computer using a USB cable and then wait for the
notification to show up in your title bar of your phone.
o Click the notification, and then click "Mount".
o A new removable disk should show up on your computer. Right click it and select
Format, and select FAT32 as the file system type.
2. Download and unzip the RC29 or RC7 image file. Copy the DREAIMG.nbh file to the SD card.
(RC29 for US, RC7 is for UK)
3. Turn the device power off.
4. Hold Camera button, and press Power button to entry boot loader mode. You should see a
gray/white screen with instructions to flash your phone with the update on your SD card. If you
don't see that, make sure you followed the instructions properly.
5. As per the on-screen instructions, press the Power button to start upgrade procedure. DO NOT
DO ANYTHING TO INTERRUPT THIS PROCESS.
6. After it is finished, perform the restart your phone.
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console
with root permissions. More information regarding that at the bottom of this post. But, to get root access,
do the following:
Instructions:
1. Download recovery.img or the new version by Amon recovery-RA-dream-v1.5.2.img and copy
it to your SD card (see the previous instructions on how to copy from your computer to your
Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it
will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
o mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
o cd sdcard
o flash_image recovery recovery.img
o cat recovery.img > /system/recovery.img
Now you have root!
Click to expand...
Click to collapse
3. Already explained in #1. Again if there is a better, easier guide to follow by all means show me. I am new to this, and from what I've seen if noobs ask "how do I do this" around here, they get flamed for not figuring it out for themselves. Something I'm also sensing from your post.
4. I've gotten past my initial problem. This morning I was shown another DREAIMG.nbh file from another source, and I was able to get it on the phone and get it to boot. I've since gone through the root process (using the guide posted above), but I still can't get it into recovery mode. So that's where I'm now stuck.
5. As opposed to a bunch of steps some retard spewed on a "message board"? All of the guides I've gone through were either on or linked to from this forum or the cyanogenmod forum. Both I assume reputable sources for this type of thing.
Note: I think you need to show me another guide because what you're saying contradicts everything I've seen.
Note2: Don't know. Everything I've seen says I have to go back to 1.4 to be able to root it because the security holes were closed in 1.6.
The phone is again back to the 1.4 image from the nbh file. I've tried to root it and get it to recovery mode without any luck, so I could use some guidance on what to do from here. I'm not really sure what adb logcat is or why I'd want to do it.
TalioGladius said:
1. I installed the nbh file because that's what was in every single set of instructions I've found said to do. Step 1 is to downgrade your phone to RC29 for US phones, and the DREAIMG.nbh file is the way to do that from everywhere that I've seen, mostly here and the cyanogenmod forums. If there is a better guide to follow, please link me.
Click to expand...
Click to collapse
Just because it was written does NOT make it right.
The process of rooting does NOT require an NBH file.
The process of REPAIDING NEVER needs an NBH file.
You should NEVER TOUCH an NBH file. The ONLY thing an NBH file does is it increases the risk that you will brick your phone by a bad flash.
Don't do it!
2. I've already explained this. I followed the following instructions:
Click to expand...
Click to collapse
Reposting that crap doesn't help.
WHAT DID YOU DO? WHERE DID YOU GET TO? WHAT DID YOU SKIP? WHAT BUTTONS DID YOU PRESS?
3. Already explained in #1. Again if there is a better, easier guide to follow by all means show me. I am new to this, and from what I've seen if noobs ask "how do I do this" around here, they get flamed for not figuring it out for themselves. Something I'm also sensing from your post.
Click to expand...
Click to collapse
#1: NEVER do anything without ***UNDERSTANDING THE PROCESS FIRST***. If you don't understand, then how can you possibly adapt to inaccuracies/errors/failures? The answer is that you CAN'T.
4. I've gotten past my initial problem. This morning I was shown another DREAIMG.nbh file from another source, and I was able to get it on the phone and get it to boot. I've since gone through the root process (using the guide posted above), but I still can't get it into recovery mode. So that's where I'm now stuck.
Click to expand...
Click to collapse
Define "can't get it into recovery". WHAT recovery do you have installed? The stock one that came with the NBH? Or some OTHER recovery that you installed? You say that it boots into the OS now? Congratulations. DO NOT INSTALL ANOTHER NBH FILE EVER!
What you need to do is install an engineering SPL, and NOT 1.33.2005! Try 1.33.2003.
You can then flash anything you like using FASTBOOT.
5. As opposed to a bunch of steps some retard spewed on a "message board"? All of the guides I've gone through were either on or linked to from this forum or the cyanogenmod forum. Both I assume reputable sources for this type of thing.
Click to expand...
Click to collapse
A forum filters out the retard posts because 100 different people CALL the retard out! A *BLOG* is TRASH unless you absolutely know that the author REALLY KNOWS what he's doing. And in this case, YOU DON'T.
Note: I think you need to show me another guide because what you're saying contradicts everything I've seen.
Click to expand...
Click to collapse
I don't write guides. I INFORM.
Note2: Don't know. Everything I've seen says I have to go back to 1.4 to be able to root it because the security holes were closed in 1.6.
Click to expand...
Click to collapse
The TELNET-ROOT bug was fixed. That's all!
And FYI: There was never a 1.4. 1.0->1.1->1.5->1.6->2.0->2.0.1->2.1->[future]2.2
The phone is again back to the 1.4 image from the nbh file. I've tried to root it and get it to recovery mode without any luck, so I could use some guidance on what to do from here. I'm not really sure what adb logcat is or why I'd want to do it.
Click to expand...
Click to collapse
Again, what did you do to get there?
I can see that this can quickly escalate into an unnecessary back and forth argument. So to avoid that how about I tell you what I've done and where I'm at currently, and you can inform me on what to do to get to my goal?
From what I've seen I had to essentially do the following things:
1. downgrade to RC29
2. root
3. upgrade radio and SPL
4. Install ROM to get to 2.1
What I've done:
1. Formatted my sdcard to fat32, and put the DREAIMG.nbh file on the root of the sdcard.
2. Shutdown. Start up the phone holding the camera button. Got to the gray screen to update, pressed the power button to update.
3. Update successful. Rebooted by pressing call, menu, and power buttons.
4. Went through the setup wizard to set up the phone with my google account.
5. Installed telnet application from the market.
6. Downloaded recovery.img and spl-signed.zip (Danger SPL) and put them on the root of the sdcard.
7. From home screen, pressed enter twice. Typed telnetd.
8. Opened telnet application. Typed the following commands:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img/CODE]
9. Shut down phone. Held down the home button while powering phone on in attempt to get to recovery mode.
10. Phone did not go into recovery mode, but went to this image on the screen: (can't post links, so fix the url)
hxxp:// www .modmygphone.com/wiki/images/1/1b/Howtofirm1.png
Currently, the phone is showing the following:
Firmware version 1.0
Baseband version 62.33.20.08H_1.22.12.29
kernel version 2.6.25-01843-gfea26b0 [email protected] #6
Build number kkila-user 1.0 TC4-RC29 115247 ota-rel-keys,release-keys
What exactly do I need to do from here to get a 2.1 rom installed?
TalioGladius said:
I can see that this can quickly escalate into an unnecessary back and forth argument. So to avoid that how about I tell you what I've done and where I'm at currently, and you can inform me on what to do to get to my goal?
From what I've seen I had to essentially do the following things:
1. downgrade to RC29
2. root
3. upgrade radio and SPL
4. Install ROM to get to 2.1
What I've done:
1. Formatted my sdcard to fat32, and put the DREAIMG.nbh file on the root of the sdcard.
2. Shutdown. Start up the phone holding the camera button. Got to the gray screen to update, pressed the power button to update.
3. Update successful. Rebooted by pressing call, menu, and power buttons.
4. Went through the setup wizard to set up the phone with my google account.
5. Installed telnet application from the market.
6. Downloaded recovery.img and spl-signed.zip (Danger SPL) and put them on the root of the sdcard.
7. From home screen, pressed enter twice. Typed telnetd.
8. Opened telnet application. Typed the following commands:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img/CODE]
9. Shut down phone. Held down the home button while powering phone on in attempt to get to recovery mode.
10. Phone did not go into recovery mode, but went to this image on the screen: (can't post links, so fix the url)
hxxp:// www .modmygphone.com/wiki/images/1/1b/Howtofirm1.png
Currently, the phone is showing the following:
Firmware version 1.0
Baseband version 62.33.20.08H_1.22.12.29
kernel version 2.6.25-01843-gfea26b0 [email protected] #6
Build number kkila-user 1.0 TC4-RC29 115247 ota-rel-keys,release-keys
What exactly do I need to do from here to get a 2.1 rom installed?[/QUOTE]
First you need to be really carefull with the danger spl (make sure you have the right radio installed before installing that spl or bye bye to your phone). You need to install Amon Ra's new recovery. Put 2.1 on sd card. Wipe and flash.
Click to expand...
Click to collapse
supremeteam256 said:
First you need to be really carefull with the danger spl (make sure you have the right radio installed before installing that spl or bye bye to your phone). You need to install Amon Ra's new recovery. Put 2.1 on sd card. Wipe and flash.
Click to expand...
Click to collapse
I got the radio upgraded to 2.22.29.26I.
Turns out I have to hit alt-l to get past the ! screen in recovery mode. So now I should be able to install the danger spl, and then the rom, right?
The one I'm seeing with the guide is Cyanogenmod 4.2.15.1.
TalioGladius said:
I got the radio upgraded to 2.22.29.26I.
Turns out I have to hit alt-l to get past the ! screen in recovery mode. So now I should be able to install the danger spl, and then the rom, right?
The one I'm seeing with the guide is Cyanogenmod 4.2.15.1.
Click to expand...
Click to collapse
To be honest I would flash Amon Ra's new recovery first so you can flash the danger spl and then the rom without a reboot in between. And if you want to install that version of cyanogen you really don't need the danger spl, but if you want to jump up to his 5.0.7 Test5 you'll need to (thats the 2.1 version).
If you want to avoid bricks, you really should NEVER go straight from 0.95.x000 SPL --> 1.33.2005 SPL. The reason for this is that there is no way to make that jump without using recovery, and since those SPLs are so different from each other, it has to use the cache-->update-hboot-->recovery-wipe-cache approach, which is where bricks come from.
If you have a 0.95.x000 SPL and want to go to 1.33.2005, you FIRST go to 1.33.2003 (that's a THREE) using recovery (since 0.95.x000 and 1.33.2003 have equal compatibility) -- this opens up the door for using FASTBOOT to flash your SPL. The move between ANY pair of engineering SPLs using fastboot is guaranteed safe since it can never get stuck in a failed boot-recovery (brick).

Problem Installing SPL and Updating Radio

Hi Everyone,
I am sorry to bother you guys, but I am writing since I am having a hard time upgrading my g1 to the hardspl or any spl for that matter after downgrading and then re-rooting. As per the directions I have:
1. First reformatted my sd card to fat32 in Windows.
2. Downloaded RC29 DREAIMG.nbh file and placed in main sdcard.
3. Turned off the phone off and rebooted holding the Camera button and the Power button until the phone is in bootloader mode.
4. Followed the directions and installed DREAIMG.nbh; and then rebooted the phone via Call button, Menu button & Power button all at the same time.
5. Used t-mobile sim card with data to log in.
6. Then pressed “enter” and type “telnetd” and then “enter.”
7. Next downloaded telnetd from Market.
8. Gained access via telent and did the following
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
The recovery image that I used was the Cyanogen AmonRa recovery from ttp://wiki.cyanogenmod.com/index.php?title=HTC_Dream:_Rooting
9. Step 8 was not fully successful in adding in the recovery image. So I downloaded AndExplorer from Market and installed it. And then I installed Flash Recovery as well, and used Flash Recovery to install the Amon Ra Recovery.
10. After that I rebooted the phone into recovery and did wipe and factory reset.
11. Then I Partitioned the SDCARD to 512mbs for ext2 and fat32 for the remainder. Then Partition SD Card > SD: ext2 to ext3.
12. Then I did USB toggle and loaded up the radio ota-radio-2_22_19_26I, Hard SPL, update-cm-4.2.15.1-signed, and signed-dream_devphone_userdebug-ota-14721.
13. First I flashed the ota-radio-2_22_19_26I and rebooted to apply.
14. Then Hard SPL and rebooted to apply
15. Then did factory reset/wipe.
16. Then applied signed-dream_devphone_userdebug-ota-14721 followed immediately by update-cm-4.2.15.1-signed.
After doing the above 16 steps, I was able to boot in Cyanogen 4.2 and when I checked the radio, it still shows the original old 1.22.12.29 radio. And when I reboot the phone via “Power” and “Back”, in fastboot it shows the rainbow screen with the info
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
Radio-1.22.12.29
Sep 2 2008
Click to expand...
Click to collapse
So it means that the HardSPL is not installing, neither is the radio.
I have tried repeating the above steps with installing the radio then DangerSPL and then Cyanogen 5, but the phone remained stalled on the loading Android screen for 1 hour. So I pulled the battery and followed the above steps to restore the phone back to Cyanogen 4.2.
So can anyone please give me advise on what I can do to get HardSPL and the latest radio to install. Btw this originally an ADP1 that I got installed with the Tmobile stuff. If there was an ADP1 image, I would definitely restore it to that, but I have not come across one yet T.T
Thank you in advance for your help everyone.
So no one has any idea on what i can do to install the hardSPL? I even went here ttp://android-dls.com/wiki/index.php?title=Main_Page#Dream.2FG1.2FADP1 and rebooted everything. And at this point I am running Android 1.1 with RC30 by jesusfreak with his recovery.img. Yet, I am still unable to install the hardSPL.
When I go through recovery mode and run the hardSPL installation, it the installation bar goes to 50% or so visually and then says everything is complete. And after that it tell me to press "home + back" to continue and it does the reboot and reboots back into recovery as well. So after that I reboot the phone and press "power + back" to enter into fastboot and it still shows the rainbow fastboot.
Sigh. So what is missing or what am i doing wrong. As i said I am still running Android 1.1 RC30 JesusFreak mod and I do not want to go up higher unless I am sure I can install the HardSPL.
Please any help would be much appreciate. Happy Holidays everyone .
I almost said flash the radio via fastboot *facepalm*
Are you sure you're using AmonRa's recovery? If you're using Cyan's you can't flash via 'any update.zip on sdcard' or whatever. It *must* be called update .zip and you must flash using alt-s, *not* using the trackball.

Categories

Resources