Hi All,
I have a HTC ADP1 phone. For a long time I continued with the stock ROM and then later switched to cyanogen 4.x. Over the period of time, I've updated from that all the way to the latest 6.x ROM, changed the SPL and also changed the Radio.
Since the past 1 week I've been a little disappointed with the speed and then decided to switch the ROM (after discovering the many options available). After researching for quite a while I settled on the list of following ROM's.
1. BiffMod v2.0.1
2. Superfly TCBY 1.3 DS
3. SpeedTeam v3.1.1
My initial configuration was the following:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
RADIO-2.22.19.26I
CyanogenMod: 6.0.0 DS
The first ROM I tried was BiffMod, which mentioned that it requred Radio 2.22.23.02. So I went ahead and downloaded that radio and flashed the same (Via recovery. AmonRA 1.7.0). After that I did the necessary wipes/reboots and flashed BiffMod and then BiffModGapps.
It all seemed good, and probably for the about the rest of the day it seemed to be fine. However doing some more research I came across Superfly TCBY 1.3 DS. I decided to flash that and went ahead and did it. Once again wiping and flashing as necessary.
Then in order to try out SpeedTeam I went through the same cycle.
I noticed all throughout though that the signal was weak. So I went ahead and flashed the radio intermittenly, hoping that it would resolve the problem. I've probably flashed the phone 5-6 times that day (hopefully this will not cause any damage).
Now however, I'm on SpeedTeam. I notice that my apps are disappearing between reboots and overall the phone feels very unstable. Places where I never had any issues with the signal (my office/home) there seems to be absolutely no signal.
I read somewhere that flashing the radio via recovery might not be the best idea, so I went ahead and did it via fastboot along with erasing the system via fastboot.
Since the signal issues, I have tried reverting to my old radio (26I) and cyanogen ROM 6. I still face the same network issues.
Steps I've followed during my flashes are the following:
1. Wipe system/cache via fastboot
2. Wipe all others via recovery
3. Flash radio
4. Reboot
5. Wipe all
6. Flash ROM
7. Reboot
8. Flash Gapps
9. Reboot.
Is there any way to figure out what is going on or is there something wrong I am doing?
The only stupid thing I did was take a nandroid backup and then lost it during one of the sdcard re-partitions. So now I don't have a nandroid backup either.
Any help would be greatly appreciated.
Thanks for your time in advance.
Related
First I want to thank everyone on these forums for all the information they've posted and shared.
There's so much information, that I'm afraid I am a little lost. I've followed so many different guides to do this and that and what not, I'm unsure of where I am exactly in the process.
My goal is to have Nandroid installed and working so I can switch and check out different roms/apps/capabilities of my phone.
I have a T-Mobile G1 that I purchased yesterday and unlocked yesterday. It came from T-Mobile already updated to 1.5 cupcake. I have an EDGE data plan and not a 3G Data plan (applies to what I had to do below.)
First thing I did was downgrade to RC29. I attempted to re-activate the phone after, but I was unable to probably due to edge connectivity.
I downloaded the SDK, and using adb I connected the phone to my wifi access.
Once I was in, I followed this guide to update the SPL. I used some utility to do it automatically, but only because I spent so much time trying to get wifi to work and activate the phone.
I then updated to the latest radio version.
I thought I wanted to install a Hero build, so I updated the SPL to the latest version, this caused my phone to freeze at the G1 screen, it wouldn't go any further. Just after this I realized that the Hero build doesn't have bluetooth, and it's essential for me right now.
So as a n00b, I downloaded JesusFreke's latest US Android build "JFV1.51 CRB43 US (11733)" renamed it update.zip and did the update, it worked fine and I've been using my phone ever since (there have been several crashing apps though.)
As I said, I want to install Nandroid to make backups, but I really don't know where in the process I'm at.
If I hold down Back+Power I get the skateboard guys (fastboot I think), if I hold down Home+Power I get the recovery mode, and Camera+Power gets the SPL. I don't really know the difference between Fastboot and Recovery mode, don't they do roughly the same thing?
I believe I'm going to have to partition my SD card (I have a 1GB right now, but I have a 16GB in a photo frame at work I will get on Monday.) in order to save apps onto the SD card and still keep music on the phone and use the phone as a portable drive.
There's so much information out there to do X with Y and run Z that it doesn't take long to figure out where you are lost.
If I go into fastboot I see:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.261
Apr 20 2009, 15:30:43
Then the Menu.
In recovery Mode:
Android system recovery utility E:Can't open /cache/recovery/command
Then the Menu.
Uh oh, just noticed that when I hold the camera down and power, I don't get the SPL anymore. I get the FastBoot Menu:
HBOOT
<BACK> FastBoot Mode
That's not supposed to happen, it should go into the SPL right?
Thanks a lot for the help. I hope to be able to be at the point that I can contribute or answer questions soon.
install cyanogen's recovery image. nanroid backup AND restore is built right in.
Maybe this is where my confusion comes in.
Both recovery images and ROMs are installed by renaming them update.zip?
I guess everything is installed with update.zip. That explains a lot...
Sirchuk said:
Maybe this is where my confusion comes in.
Both recovery images and ROMs are installed by renaming them update.zip?
I guess everything is installed with update.zip. That explains a lot...
Click to expand...
Click to collapse
You only have 2 posts. You need to go and read through everything. There are rules about starting threads, and this one shouldn't have been started and will probably get deleted.
You need to go to the designated thread and ask your questions. Getting to where you understand everything doesn't happen overnight.
You want nandroid backup/restore? Go to the development forum and look for cyanogen's pimped out recovery 1.3.1.
You need help on your spl? Same forum, but look for let's fix that spl.
Please do research before making a new thread.
All your answers have already been posted, just look for them.
I understand you are a noob, I welcome you to the world that is g1 with open arms. But, we all had to start somewhere.
Thank you.
You are well on your way...
You have the newest radio. You have the newest spl... You've successfully flashed a custom rom, so you are well on your way. Listen to temporizer, he's laid it all out for you. And yes, search comrade, search!
I had 3.6.8.1 build, tried to upgrade from modified launcher 7 to 8, got stuck at splash screen. I did (a million times now) RC29, root, RC33, but then when I try to flash JF1.51, 1.5, Cyanogen 3.6.8.1, 3.9.4, or Hero, it takes me to fastboot with Hard SPL and gets stuck on Splash with Special SPL.
Any advice?
P.S. JF1.41 RC33, ADP 1.1 (holiday updates included) and 1.42 RC33 all work, just not Rooted 1.5 ROMs. Flashed back to T-Mobile's 1.5.
Why are you flashing RC33 after you root your phone? This reflash of official release candidates is what is closing your root loophole...its like you never rooted in the first place. You should go rc29, root, then a custom ROM, you can never go back to anything official unless you are willing to loose your root.
Unless I'm misreading or misunderstanding you, that seems like your problem
The official update I flashed to see if it was 1.5 or the rooted ROMs that was having the affect. I re-rooted after to test but when I flash the custom ROMs after rooting I get stuck at fastboot (Hard SPL) or splash screen (Special SPL).
The only Custom ROMs I can flash successfully are the RC33 and ADP1.1. I hope that clears it up.
I just got a new G1 so hopefully this won't be an issue an longer.
Genesis206 said:
The official update I flashed to see if it was 1.5 or the rooted ROMs that was having the affect. I re-rooted after to test but when I flash the custom ROMs after rooting I get stuck at fastboot (Hard SPL) or splash screen (Special SPL).
The only Custom ROMs I can flash successfully are the RC33 and ADP1.1. I hope that clears it up.
I just got a new G1 so hopefully this won't be an issue an longer.
Click to expand...
Click to collapse
I guess I'm just not understanding what your saying.... We may be talking in different jargon because the RC33 that I know of is the name of the release candidate of T-Mobile's official firmware prior to their 1.5 (cupcake) firmware upgrade.
I suspect that you are doing something wrong somewhere in the process because I see in your signature block that you have bricked two phones and it sounds like you are getting a new one again so perhaps we are on a 3rd brick?
You might want to head back to the beginning and read carefully the steps for rooting and installing "custom" roms. Again, there is nothing custom about RC33 or ADP1.1
its not a brick if he can access fastboot. Also he said he flashed Tmo 1.5 official so its not a brick. I suggest trying to root your phone again. You might be doing something wrong...
No one said he had a brick. I was simply commenting on how his signature says he has four phones, 2 bricks, 1 sold, and one presumably that he uses. Then in his response to my first comment, he said
I just got a new G1 so hopefully this won't be an issue an longer.
Click to expand...
Click to collapse
This led me to assume that that would be a fifth phone, ultimately leading me to conclude that he bricked two for sure and possibly a 3rd.
1. dreaimg.nbh
2. root
3. flash recovery 1.4
4. flash radio
5. flash spl
6. if using app2sd you'll need to have that partitioned SD card we all love to gab about
7. wipe your ext2 partition
8. WIPE YOUR PHONE! (most people forget this when they're startin out. use the recovery screen)
9. flash your rom
10. reboot
11. enjoy
(optional)
12. reboot again
13. flash theme
14. enjoy some more
I will start off with the issue is i probably messed up something and more importantly I am probably over my head.
Basically my G1 will not get past the tmobile screen. I have let it sit up to 35 mins in between flashing on this screen.
Before i touched it today, I had a working version of CyanogenMod, and before that the 1.5 of JF. The version of CyanogenMod i had I don't remember, but it did have all the standard google features including work email, but was not able to be updated via the CyanogenMod Updater app if that helps.
What i did.
I went out to CyanogenMod and downloaded update-cm-4.2.3-signed.zip and renamed it to update.zip and placed on the root of my SD card. I deleted the previous version that was there that flashed sucessfully last time.
I then restarted the phone holding Home and Red - did a wipe and applied the image. Nada - did it again. I have attempted to do so 4x's now. I can get into the that mode just fine.
Booting with camera yields the following
DREA100 PVT 32b
HSPL10.95.3000
CPLD-4
RADIO-1.22.12.29
OCT 20 2008
Any help gents? I appreciate it.
White G1 - 4 Gig SD Card - T-Mobile Service -
Thanks!
do u have a nandroid back up? if not once this is resolved u should grab the latest recovery 1.4 i believe that can do back ups and restores with out much work. have u tried flashing a different rom back onto your phone again to try and get that to work?
Thanks for the reply and I will look into the backup.
I did take my SD card out and dump it all to my pc. I started looking around and it appears I made a backup of the original CyanogenMod i did in september. I then took my sd card - wiped it, and put that one on it.
So now im back working again, which i can live with, but I wonder what I did wrong with the last one or why it wont work.
If your cyan was pre-4.1.99, You have to flash the ADP recovery image as the instructions state
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
B-man007 said:
If your cyan was pre-4.1.99, You have to flash the ADP recovery image as the instructions state
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
Click to expand...
Click to collapse
Thus where I failed. Thanks for pointing that out, I ran through this pretty fast assuming it was like the previous install. Again Thanks! I will take sometime and go through it slowly tonight.
Knowledg said:
Thus where I failed. Thanks for pointing that out, I ran through this pretty fast assuming it was like the previous install. Again Thanks! I will take sometime and go through it slowly tonight.
Click to expand...
Click to collapse
Frankly, before you go through upgrading to a more recent ROM, and since you have a working rooted phone at the moment, I'd take the time to upgrade to the latest Radio (you're on the old 1.22.12.29 according to your post), newest SPL (Haykuro's "Danger" SPL), and recovery partition.
First update to a new Recovery... I recommend Amon_RA's latest 1.3.2. It simplifies backing up and flashing immensely. He's built Backup and Restore Tool into the Recovery, so you can essentially make an image of your phone and ext partition and restore within minutes if you screw something up (short of bricking your phone of course).
Next, I would upgrade your Radio and SPL (in that order). Follow the link in my sig for directions. Remember though... RADIO, THEN SPL. If you do SPL then Radio, you'll brick.
About a week ago I updated my post-911 fix Rogers HTC Dream to Cyanogenmod 4. It ran quite slowly, obviously, but it was much better than having Android 1.5 apps and a useless "smartphone". After just recently reading about Froyo and Cyanogenmod 6 I decided that the apparently streamlined update would be a good idea. I heard it was significantly faster. And then the trouble started.
I updated my recovery image to RA-dream-v1.7.0R (R because as I understand it the post-911 fix is EB1I) because the wiki said the cm recovery had troubles with CM6. After looking over the appropriate information that said I did have DangerSPL (fastboot says RADIO-3.22.26.17, and HBOOT-1.33.2005) and so on, I continued. I downloaded CM6 and the appropriate Google Apps package, moved them to the root directory of the SD Card, installed the zips (CM6 first) with Amon_RA and restarted the phone.
When I did so, the phone would not boot past the Rogers logo (which formerly appeared before the HTC and Cyanogen boot screens). After about 15 minutes I had to pull the battery. I went back into the recovery and enabled USB mass storage, when I looked at the SD Card it was completely empty.
Yeah.
So, I've put CM5 and CM6 as well as their corresponding Google Apps packages on the sdcard.
If I haven't bricked my (already useless Rogers Wireless 1.5 and not updating) phone, what should I do next?
Thanks for any help.
Flash CM6, Flash Gapps, Flash EBi1 port (you can get it from here http://briancrook.ca/android/cm-ports/bc-6.0.0-ebi1-signed.zip)
Official instructions found here
http://forum.cyanogenmod.com/topic/5286-cyanogenmod-6-for-ds-shoehorn-sledgehammer-v600-08272010/
Enjoy
Wow. So it was just the radio I misunderstood?
Given that this is my regular phone, you truly made my day. Thanks for taking the time, Sleeepy2.
you have to flash the ebi1 for every Rom
Posted this in the wrong place... so here I go again.
Alright as the Title says I got a problem with Froyo.
First of all, this is the first time i ever tried anything with a cellphone, although so far it went well (took me long though).
First I removed an old version of cyanogenmod from the old user.
Then I followed this guide: http://forum.xda-developers.com/show....php?t=1098899
Then I installed Froyo by Laszlo 5.2
http://forum.xda-developers.com/showthread.php?t=929678
Now to my ultimate surprise, I actually got this all done and it works perfectly, except for one thing. Wifi does not work. When I turn it on it starts scanning for networks, then gives the message "unable to scan for network" and Wifi automaticly gets turned off again. Before installing this I always found 2 networks from the point I'm sitting now.
I simply got no clue what it could be.
Some info. Following the guide for radio and boot I got the correct information in the bootloader as mentioned in step 3:
Dream PVT 32b SHIP S-on
HBOOT 1.33.0013d (drea10000)
CPLD-4
RADIO 2.22.28.25
OCT 21,2009,22:33:27
About Phone:
Android version 2.2.1
Baseband version 62.50SJ.20.17U_2.22.28.25
Kernel version 2.6.34.8-froyobylaszlo [email protected] #1
Mod version FroyoByLaszlo-5.2
If you need more info, just ask.
And thanks in advance,
Greetings,
Noddahead
edit:
Little update here. On some forums I found that a file bcm_supp.conf in /data/wifi caused a problem like mine. When I plug in my phone in my pc I only see the sd card. Therefore I installed sdk/adb thing, connected with my phone (correctly). and I manually tried to remove the file via cmd. This resulted in the notification that the file did not exist.
Hence, back to nothing. Any way I can make my internal memory show up again?
All in all it seems like I got the same problem as many people had with Froyo. But it seemed solved for everyone after a certain patch. My Froyo version is obviously more recent. And no one seems to have this problem with this version of Froyo (in the Froyo by Laszlo thread page 97ish and forth)
Alright. I'm trying my very best but I'm really clueless right now.
After not getting this wifi to work I tried the COS-DS mod. Installing it and everything went fine, except for one thing: the settings menu would not open.
Not being able to do anything on that I went on to the next to the next rom: Cyanogenmod 7 Magpie. Once again, most things work, but some do not. I started out with an input.latin error, which I somehow fixed. I do not have a status bar, and I think I'm missing some other things too... for example, the android market does not appear. Wifi does work now though.
I have no clue what's going on... do I just need to start over from scratch? Trying Froyo again? I could really use some advise.
Noddahead
Have you tried wiping properly before flashing the new roms because I've never had a wi-fi issue unlees it was broken in the kernel which is rare these days.
Thank you for replying.
I am back to Froyo by Laszlo now, seems the best option. Before installing that I wiped cache, wiped data/factory reset, and I used Ohsaka Superwipe. But no Wifi.
Using another Kernel with Froyo by Laszlo did not help.
Well, last update here. Never got it to work, now having succes with GingerYoshi. This topic can be locked.
try everything???? re partition and re format sd card, try ezbifftest 2708 kernel, i had best luck with laszlo rom
First of all, thank you for your guide.
I had not actually partioned before installing froyo, and I did partition before using Ginger right now.
If I would repartion right now, and then reformat... can I then instantly install froyo laszlo and the kernel? And what values for the partioning?
you can flash a rom whenever you want, as long as you wipe all data from previous rom or mod first,so i would repartition to this
96-128mb=swap
512mb=ext
than flash the ohsaka superwipev2, power off device than reboot back to recovery.
flash the rom you want and enjoy!!
re-partitioning/re-formatting does not have to be done everytime.. it's just good to do every once in a while because you never know what could be happening in there... you or a developers rom could have done something somewhere that caused a bug in your sd partitions so its always good to wipe them at some point...
the ohsaka superwipe i do reccomend using everytime!! I also recommend wiping it manually sometimes... also another good known method is a fastboot wipe 'i forget the cmd for it' lol but do these every once in a while...
Did exactly as you said, unfortunately I still get the same problem: Cannot scan for networks.
I will stick to Gingeryoshi for the moment.
Thank you for your time and help.
wow, thats a bummer... i never had that issue with laszlo's rom at all... i wonder what could be wrong. sorry i couldn't help.. just out of curiosity what device do you have? is it a dream or magic?
possibly if you are using a magic, you may need a kernel with wlan.ko modules included for the specific kernel(would be icluded in kernel.zip file)... different kernels wont work with different drivers...
It is a Dream