Related
I was updating my SPL and upon reboot I got the lovely looping T-Mobile G1 screen, camer+power, back+power, and menu+power all work, but I really have no clue what to do as to fix it, I am new to this, no I did not make a recover because I had just upgraded to Cyanogen's backup, wiping didn't seem to work, I think it was possibly because my rom was out of date? I have JFv1.51_CRB43-US, so my question to you guys is, could going out and buying another SD card and dropping a newer rom and putting the new card in my phone fix my problem?
If you were upgrading to the 1.33.2005 SPL, you need to reflash with whatever rom you are using. The SPL effectively wipes the rom out, so you need to put it back.
Yeah, I just read that in the fastboot for noobs thing, thanks for the info!
Edit:
Do I have to reboot with the exact same rom as before the SPL update?
In case you missed the key point, using that hacked SPL has the effect of WIPING ALL YOUR DATA, so how, if the data is shot, could it possibly care that you write the same thing onto it as it had before? Answer is that it DOESN'T. Now go ahead and write whatever you like to it.
Thanks, was just wondering. :x
Gotta learn one way or another.
Ok first off I am really sorry for the stupidity and should have paid more attention. I was flashing the NBH on my Tilt 8925 and I got the wrong one! it was the KAISIMG-PANEL1-428.NBH that I downloaded and now the text is hard to read and it wont install and I cant change it. Right after I did that I found the forum that told you witch one to use. I wanted to cry!!! So what I'm asking is my phone done for? or is there a way to fix this? like through the andboot folder somehow?
Thank you for any help at all!!!
you learn from your mistakes though, I'm sure I wont do that again
Fixed it! :d
After I gave up I remembered someone said to hold the camera and the power button and reset buttons. I did that just to see what it would do and the colored screen came up with usb at the bottom. so I triad the right file and ran it again and it worked! Now I'll have to give it another go!
so this can be deleted now Thanks!
Just for future reference.
If you flash the wrong nbh with android, you should be able to flash the correct one using either the SD method, or the USB method.
Above all, do not panic, panic bricks more devices than bad flashes ever did
Since this is the Android area, I must say we are extremely lucky, since we are able to flash a new nbh without losing anything at all as far as the OS is concerned, your data and system files will remain intact, flashing an android nbh only replaces the zImage and the android bootloader files, unlike WM where you flash the whole OS and lose everything
Android
That's good to know because I thought I lost the phone for good. I didn't have any data on it that I needed, I was trying to install android to nand and just got the wrong NBH.
The only thing now that would keep me with WM 6.5 is cant get the wifi to work right. It connects to the router but the internet cuts out very bad, like it will work for 10 seconds then cant get it to work at all for 20min then it will load a web page then doesn't work again!
I did the same thing to my Tilt. I downloaded the Kaiser for Super Eclair and flashed it and did not not know I did not flashed the HardSPL.nbh.
I finally figured it out and flashed the HardSPL.nbh. It is at 3.29 right now. But I the phone keep getting error after the penguin screen with scrolling text. It said something about unable to read data. How do I fix this problem?
BeenAndroidized said:
I did the same thing to my Tilt. I downloaded the Kaiser for Super Eclair and flashed it and did not not know I did not flashed the HardSPL.nbh.
I finally figured it out and flashed the HardSPL.nbh. It is at 3.29 right now. But I the phone keep getting error after the penguin screen with scrolling text. It said something about unable to read data. How do I fix this problem?
Click to expand...
Click to collapse
Jesus... the last post is more the 1year old.
I know you must search, but if the last post is that old, the probability that everything in it is outdated, is near 100%.
Well, that is the what I found. I hate digging up old post especially when it's that old.
Hi everybody,
I was trying to load the cyanogen mod to my G1
Had Android 1.6 and Radio 2.22.23.02
I downgraded to RC29 successfully
Rooted my phone
Loaded recovery-RA-dream-v1.7.0.img. Flashed successfully
Then started following instructions below:
wiki . cyanogenmod / index.php / DangerSPL_and_CM_5_for_Dream
I got stuck in step 6
It is probably because downgrading to RC29 also downgraded my radio version. I did not check the radio version again after I downgraded
Using danger.spl bricked the phone
I searched online and found some solutions with JTAG, but I am in Turkey and do not have access to purchasing these from ebay or the know-how to apply them (as you can tell from my mistake above!)
1) I found the below solution, but not sure if it will work:
code . google / p / android-roms / wiki / Unbrick
They say it will only work if you have soft-bricked your G1. I'm not sure
2) Others say I need to call T-mobile Customer care (where I purchased the phne from), but that was about a year and a half ago. How long is the warranty on the G1? 1 year or 2 years?
3) And yet others say use it paper-weight
Should I go for option 3?
What do you think?
Wiki Instructions
What is DangerSPL?
This SPL is actually a port of the Magic/MT3G (Sapphire)'s SPL to the Dream/G1. Called danger because not only does it wipe your data in the repartition process (data can be restored with Nandroid restore after flashing DangerSPL), it has a chance of bricking your phone if you would ever choose to downgrade the radio after flashing it (see below for compatible radios). Never flash a 1.x, 4.x, or 6.x radio with DangerSpl
It is not required for CyanogenMod versions 4.X (CM4) and below, but required for the CM5 series on the G1/Dream.
Why is it required for the CM5 series on G1/Dream?
The G1/Dream's /system partition was originally created to take ROMs up to 64MB. The CM5 series for the G1 & Magic/MT3G is currently too big to fit on this partition.
Why don't Magic/MT3G users have to apply it?
The Magic/MT3G (Sapphire)'s /system is set to take ROMs up to 96MB by default, so no SPL change is needed.
Is it dangerous?
While the method of applying it has been perfected over the course of its use, any modification of SPL/Radio/ROM carries with it an inherent risk. That being said, if you pay attention, follow instructions, and plan your approach, it is actually an easy process.
How do I check if I already have DangerSPL?
Boot into fastboot mode by turning the phone on while holding the camera button and pushing the power button. The second line contains your SPL version. If it ends in 2005 (eg 1.33.2005) then you have DangerSPL installed already. The line with RADIO tells the radio version, which is important if you don't have DangerSPL. To leave fastboot mode, press MENU+SEND+END at the same time.
Installation
Warnings
Make sure that you have a full battery during the steps below and at no point remove power from the device (i.e. no battery pulls!). See the first two bullets in troubleshooting regarding battery use after flashing CM5 and fixes for higher-than-expected battery drain.
There has been some development/debate over DVT/PVT and bricks. Optional reading (but still recommended): XDA forum
Prerequisites
A rooted G1/Dream
A compatible radio (IMPORTANT: If you just rooted, the RC29/RC7 install includes a 1.x radio and you MUST install one of the 2.x radios below before DangerSPL)
2.22.23.02 seems to get more bars for T-Mobile US customers, though non-US users might have better luck with 2.22.19.26i.
(HardSPL/Engineering Spl Users) Radio installations can be had by fastboot flash radio radio.img after extracting radio.img from the .zip
Either of the following radio versions is acceptable.
Radio 2.22.19.26I
Radio 2.22.23.02 (G1)
Rogers Dream users: A 3.X radio is Danger compatible (eg 3.22.26.17)
Failure to meet the Prerequisites WILL result in a BRICK!
Files required
Danger Spl
gapps-ds-ERE36B-signed.zip, Mirror1
Latest CM5 for Dream/Sapphire
ONLY Roger's Dream users: EBI1 kernel for 5.0.x
Steps
It has been brought up that Clockwork Recovery struggles with this guide, so Amon_ra is v1.7.0 recommended. If you have CM or older recovery, upgrade to Amon_Ra first.
Please if you need to diverge from these steps for any reason start over from step 1 when you return.
Boot into Fastboot (Power on the phone holding the camera button) This will either show a screen with dancing androids or a "rainbow" splash. Here you will find the hboot/radio version:
radio 1.x: You will need to upgrade this to a 2.x radio before running this process.. please upgrade and re-do this step (Ie. verify you see the updated radio in fastboot before continuing)
radio 2.x: You may press MENU+SEND+END at the same time and proceed (unless hboot-1.33.2005 is installed; indicating you already have dangerSPL)
radio 3.x: You may press MENU+SEND+END at the same time and proceed (unless hboot-1.33.2005 is installed; indicating you already have dangerSPL)
Copy DangerSPL (spl-signed.zip), CM 5.0.x, and gapps-ds-ERE36B (& Ebi1 port if required) to the root of your sdcard.
Reboot/Boot into your custom recovery by holding down the 'home' key before the G1 splash appears.
Make a Nandroid Backup (ext not required) (recommended for upgrading users, not required for freshly-rooted users)
Flash DangerSPL (spl-signed.zip). It will install and then ask you to reboot to finish the installation
Reboot as prompted at the bottom of the screen. This will finish installing DangerSPL and reboot back into recovery so you can flash your ROM.
Once back into recovery Wipe Data/Factory Reset
Flash CM 5.0.x THEN gapps-ds-ERE36B (& Ebi1 port if required); then reboot (Boot may take longer than normal)
Login to Android/Google as per usual
If you want to restore the nandroid backup (to attempt an unrecommended no-wipe upgrade between CM4.2 and CM5)
[Optional] Reboot to recovery, and issue a Nandroid Restore, then follow the regular instructions .
This command will attempt to restore user data.
Restoring will also restore your previous Firmware, so you have to follow the instructions to get 5.0.x again
Note: If this causes undesired consequences (ie bootloops, FC's, etc) then run Fix Permissions/'Fix UID Mismatches'.
***************************************
Instructions for the 'soft-brick' (I think)
How to Un-Brick Your Phone
(Method 1)
Ok so you're trying to put this really cool new custom ROM on your phone and then suddenly, your phone won't start up…well my friends, you have got yourself a bricked phone. The thing you worry about the entire time you're rooting, and flashing your phone, has now become reality. Well, fear no more, for I, CTDroidBeast have found a way to unbrick your device!
It's really easy. It's actually easier then rooting your phone, believe it or not.
Ok, you will need a new SD card, because I bet if you use the one out of your device your computer will not be able to read it. But if it does then HEY, you're in luck. You don't have to spend your money on a new SD card.
So let's get started.
Step 1: Turning Off Your Phone
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to take out the battery.
Step 2: Preparing Our SD card
Take out your SD card and put it into an SD card reader or some type of other adapter so that we can view it from our computer. If you cannot view the SD card on your computer then you're going to need a new SD card.
Download DREAIMG-RC29.zip and unzip the file.
Reformat the SD card to FAT32 and copy the DREAIMG.nbh onto it.
Safely eject the SD card.
Put the SD card into your device.
Step 3: Wipe The Phone
Hold home and press the power button.
When you see the image of an ! mark, open your keyboard and press Alt + L if you cannot see any command options.
Do a factory reset by pressing Alt + W or just using the trackball.
When the reset is done, go ahead and hold the camera button and select the reboot system now option with your trackball.
Step 4: Flashing The Phone
Once the grey screen pops up (or the white screen if your phone was rooted with JesusFreke) it will ask you to hit a button to start installing the image…press that button. DO NOT DO ANYTHING TO STOP THIS PROCCESS. It will take about 8-12 minutes.
When the image has completed the installation (it will say completed), go ahead and press the green, red, and menu buttons at the same time. The phone will reboot.
And your done! Your phone is now unbricked!.
Please help!
YOU FAILED.
If you don't take the time to read and learn what you are doing, why should anyone take the time to help you?
WHY would you EVER install RC29? IDIOTIC MOVE!
WHY would you EVER install deathSPL? IDIOTIC MOVE!
I say you deserve what you got.
lbcoder said:
YOU FAILED.
If you don't take the time to read and learn what you are doing, why should anyone take the time to help you?
WHY would you EVER install RC29? IDIOTIC MOVE!
WHY would you EVER install deathSPL? IDIOTIC MOVE!
I say you deserve what you got.
Click to expand...
Click to collapse
I was just following the Wiki instructions ( Full Update Guide - G1/Dream Firmware to CyanogenMod ) here:
My radio before downgrading was 2.x, so I assumed it would still be the same after the RC29 downgrade, but it turns out the downgrade also dongrades the radio to 1.x
therefore death spl bricked the phone
I should have checked the radio version for a 2nd time before flashing death spl
Is there any way to fix this now??
HEARTBREAKER123 said:
I was just following the Wiki instructions ( Full Update Guide - G1/Dream Firmware to CyanogenMod )
Click to expand...
Click to collapse
You did not follow the instructions.
You deliberately skipped step one on the danger spl instructions. Put there so that those who didn't realize the radio had become downgraded didn't do what you just did. You also ignored the warnings on that page that rc29 installs the 1.x radio.
HEARTBREAKER123 said:
Is there any way to fix this now??
Click to expand...
Click to collapse
What part of not having the right radio will brick your device wasn't understood..
by all means hope your recovery is messed up and that you have access to fastboot when you attatch a USB wire.
Otherwise there is jtag. .. bit more complex than flash spl-signed.zip after being 100% sure a 2.x radio is installed however..
Another option is replace it.. some have found replacing the main board + daughter board of a working phone in bad cosmetic shape (screen cracked) a cheap alternative here than a brand new dream. Still requires reading the service manual to properly disassemble what you need without having a bit of a mess.. particularly if you skip a step.
My recommended solution is to find a phone you can deal with stock firmware buy it and sell the rest of your dream as is.. you want root you need to understand the instructions not just follow them.
Alright, well I think he got the point - he should have followed instruction better
I'll keep it as straight forward as possible, no there is not a way you can unbrick your phone without the JTAG tools. T-Mobile's warranty is only one year, afterwards they will not replace your device for any reason.
The soft brick solution you posted will not work, because you have a hard brick.
I believe you only have a couple of solutions.
a) Get a new G1
b) Buy an old G1, preferably one with a broken screen so its cheaper, and place the motherboard of that G1 into your current one
c) Work with some members of XDA and see if you can work out an arrangement to get you the JTAG tools, though this is unlikely to work and difficult to do.
I'm sorry that you have broken your G1, it's a terrible feeling to break your phone in this way where everything is physically still perfect. I believe your best bets are probably solution "a" or "b", you can shop around locally and see if you can find anything
Best of luck.
Thanks for the help.
I think I will try and get another G1 to see if I can replace the motherboards
HEARTBREAKER123 said:
Thanks for the help.
I think I will try and get another G1 to see if I can replace the motherboards
Click to expand...
Click to collapse
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.
lbcoder said:
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.
Click to expand...
Click to collapse
Like the OP said, he lives in Turkey and is unable to purchase these items on eBay.
SolemnWishing said:
Like the OP said, he lives in Turkey and is unable to purchase these items on eBay.
Click to expand...
Click to collapse
Turkey is NOT a back-woods country and there ARE LOTS of sources besides ebay. In fact, ebay is the LAST place you should look for electronic components.
I GUARANTEE that the required components can be purchased in STORES all over the place in Turkey.
lbcoder said:
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.
Click to expand...
Click to collapse
$2? I thought Jtag cost like 70 bucks
racerxgt said:
$2? I thought Jtag cost like 70 bucks
Click to expand...
Click to collapse
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Being more careful this time, I went through the wiki steps and installed CM 5.0.8 and gapps-ds-ERE36B-signed
Yaay!
But then I noticed that CM6 was out, and that it had flash, so why wait, right?
I flashed CM6 with no problems, rebooted the phone, logged in, everything seemed OK, except that I didn't have google apps
So I flashed gapps-mdpi-FRF91-signed.zip and... I wasn't able to log on to google!
You know the menu that asks you to sign in to your google account at the beginning
It says "touch the android to begin"... And when I touched the android, it wouldn't ask for my username and password.. Right click would go into 'Wireless Settings', and I was able to successfully define an APN and get a 3G connection, however, even after all that, and when the phone had reception,
touching the android would make the android change color, but it wouldn't let me go to the next step!
So I decided to flash the previous google apps
Now the phone does not boot in normal mode
I can access the bootloader and the fastboot menu (both Camera+Power and Home+Power work fine), but I am not sure how to fix the problem I have
I tried downgrading to Android 1.5 and starting over, but when I go into the bootloader menu, I see 3 androids with skateboards and the following options:
CAMERA_STEP2 : Hboot mode
SEND: Reset device (Doesn't reset, it just reboots when you try)
ACTION: Restart to hboot
MENU: Power down
And when you are in hboot mode, you can't click anything
How can I revert to CM 5.0.8??
Also, is it normal for the new gapps to cause this type of an error?
HEARTBREAKER123 said:
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Being more careful this time, I went through the wiki steps and installed CM 5.0.8 and gapps-ds-ERE36B-signed
Yaay!
But then I noticed that CM6 was out, and that it had flash, so why wait, right?
I flashed CM6 with no problems, rebooted the phone, logged in, everything seemed OK, except that I didn't have google apps
So I flashed gapps-mdpi-FRF91-signed.zip and... I wasn't able to log on to google!
You know the menu that asks you to sign in to your google account at the beginning
It says "touch the android to begin"... And when I touched the android, it wouldn't ask for my username and password.. Right click would go into 'Wireless Settings', and I was able to successfully define an APN and get a 3G connection, however, even after all that, and when the phone had reception,
touching the android would make the android change color, but it wouldn't let me go to the next step!
So I decided to flash the previous google apps
Now the phone does not boot in normal mode
I can access the bootloader and the fastboot menu (both Camera+Power and Home+Power work fine), but I am not sure how to fix the problem I have
I tried downgrading to Android 1.5 and starting over, but when I go into the bootloader menu, I see 3 androids with skateboards and the following options:
CAMERA_STEP2 : Hboot mode
SEND: Reset device (Doesn't reset, it just reboots when you try)
ACTION: Restart to hboot
MENU: Power down
And when you are in hboot mode, you can't click anything
How can I revert to CM 5.0.8??
Also, is it normal for the new gapps to cause this type of an error?
Click to expand...
Click to collapse
*FACEPALM*
goldenarmZ said:
*FACEPALM*
Click to expand...
Click to collapse
Don't facepalm just yet
I managed to go back to 5.0.8 after doing everything from scratch
I guess I will use it like that for a while until CM6 / google apps stabilizes
HEARTBREAKER123 said:
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Click to expand...
Click to collapse
I bricked my G1 as well, but I'm not in the US
Do you have an idea what the JTAG adapter looked like ?
wow you guys sound mean to the poor guy when he was just making a newbie mistake. i remember when i was making all of those mistakes...hell im still making those mistakes and even thou i have gotten my fone to freeze on the g1 logo or even just go into a constant reboot im glad iv been able to fix the problem everytime and still dont know what im doing im just learning. but hey isnt that procedure that you have up there an unrooting procedure???? and for those getting the wrong gappss try downloading the tiny mdpi on the dream that one worked for me, the mdpi didnt work at all till i tried that one got it from the cyanogenmod site. by the way i gotta say thanks to all the devs, which i had a brain like yals id love to join in on developing but im kinda an idiot here lol
spike210 said:
wow you guys sound mean to the poor guy when he was just making a newbie mistake. i remember when i was making all of those mistakes...hell im still making those mistakes and even thou i have gotten my fone to freeze on the g1 logo or even just go into a constant reboot im glad iv been able to fix the problem everytime and still dont know what im doing im just learning. but hey isnt that procedure that you have up there an unrooting procedure???? and for those getting the wrong gappss try downloading the tiny mdpi on the dream that one worked for me, the mdpi didnt work at all till i tried that one got it from the cyanogenmod site. by the way i gotta say thanks to all the devs, which i had a brain like yals id love to join in on developing but im kinda an idiot here lol
Click to expand...
Click to collapse
bigest mistake evar was probably buyng tha damn mobo ...you see i have 3 HTC's 1 HTC Dream that work's just fine , 2 T Mobile G1 that it's a piece of **** ( it got's nothing in comon with HTC dream it's just a cheap crap copy of the original ) and 3 it's a HTC with Win Mobile wich i think it's by far the most stable mobile operating sistem for now , all of you will say that it does not work like that , but think about this .... how manny win mobo's hawe ever been bricked?! and how manny android mobos are there bricking every day ? your android will brick eventualy ... oh yeah and i am selling 2 HTC dream Black and white
Thumb's upp if you are born in the rong generation )
ive done a lot of research and still cant find a solution. im sort of a newb, heres the problem my wifes TP2 when she turns it off and turns it back on the phone gets stuck on bootloadr screen, tried to hard reset but wont do anything. but when i plug it with usb to my laptop if i soft reset it will boot up.I read that alot of people had the same problem and just had to install a coocked rom, well i did i installed energys rom but it still had the same issue. Now its back to stock rom. any info on how to fix this is appreciated and thnx in advance.
Get it replaced under warranty
if you were able to flash a cooked rom, you must have installed hard-spl.
when did you do this, after the problem appeared to be able to flash the energy rom, or before? maybe this could be the problem...
http://forum.xda-developers.com/showthread.php?t=606078
here is a thread on the subject already.
Huthus said:
if you were able to flash a cooked rom, you must have installed hard-spl.
when did you do this, after the problem appeared to be able to flash the energy rom, or before? maybe this could be the problem...
Click to expand...
Click to collapse
well the first time her phone did it i googled the problem and it brought me here, a thread that said stuck at bootloader screen and their solution was flashin a cooked rom. well it got the phone to boot after i did that but every time if she turns it off and back on it gets sutck at the tri color screen. i installed hard spl when i was flashin rom.
here is a thread on the subject already.[/QUOTE]yea been at that thread also,but my problem is that when i turn the phone off and when i turn it back on it wont boot up it just gets stuck there, like i stated above i already flashed hard spl and flashed a energy rom but it still does the same thing. i flashed the phone back to the original rom but is still gets stuck, the phone works as long as she dont turn it off but after awhile her ram goes up to like 80 so i have to turn it off, and to turn it back on i have to use my laptop. and thanx for the help guys i really appreciate it. and phone dont have warranty i bought it on craigslist.
Since it's going to the tri-color bootloader screen, seeing as normally to get to that screen you would hold volume down on boot, have you checked inside the back of the case to make sure there isn't dirt/debris jamming the volume down button? If the volume adjusts normally once you do get it booted, that may not be it, or maybe it's just a short in the key.
Also, both the stock ROM and energy ROMs are bad about eating ram, and need to be rebooted regularly. Maybe try one of the ROMs that doesn't, like a Jackos rom, which you can leave running for days without a reset. Might not solve your problem, but might at least take some of the bother out of it.
FL5 said:
Since it's going to the tri-color bootloader screen, seeing as normally to get to that screen you would hold volume down on boot, have you checked inside the back of the case to make sure there isn't dirt/debris jamming the volume down button? If the volume adjusts normally once you do get it booted, that may not be it, or maybe it's just a short in the key.
Also, both the stock ROM and energy ROMs are bad about eating ram, and need to be rebooted regularly. Maybe try one of the ROMs that doesn't, like a Jackos rom, which you can leave running for days without a reset. Might not solve your problem, but might at least take some of the bother out of it.
Click to expand...
Click to collapse
I take it you haven't used the latest NRG ROM. Mine runs for several days.
stevedebi said:
I take it you haven't used the latest NRG ROM. Mine runs for several days.
Click to expand...
Click to collapse
You've got me, there. The last energy rom I tried was a little bit ago, and was a Maxsense version at that. Even still, it soundly failed my Opera Mobile 10 test on a clean flash off of a fresh boot (it would autokill OM 10 to free up ram without any other apps open). Any rom that does that goes straight into the bin as far as I'm concerned.
I have been meaning to drop one of the more recent builds on to see if that was just a bad experience. Maybe try one of the titanium versions, just to make sure I'm giving it a fair shake. Either way, this has now gotten at least a bit off topic. =P
stevedebi said:
I take it you haven't used the latest NRG ROM. Mine runs for several days.
Click to expand...
Click to collapse
yea i have the sep 18 nrg rom on mine wich now runs very good. well after a couple reboots with the phone plugged to my laptop, i unplluged it and tried a soft reset and thank god it booted normal, i then powered the phone off and turnd it back on and it worked. dont know what the problem was but i appreciate everyones help.
There is different things that you can do to try and resolve your problem. Start by finding a rom that you would like to install on your phone and save the file to your SD Card. FL5 Mentioned Jacko's rom and I swear by it as well. I run the showlite version modified to my liking and still have on average about 80 mbs of ram open.
2nd thing to do would be a Task 29 which will pretty much formats your phone. This is important to do because if there is any "debris' left over from any of the roms you have installed, this will take care of that. "Debris" at times cause issues that you cannot pinpoint and interfere with the rom that is currently installed. It is also important that you do this step second because once you do a Task 29 you will not be able to flash through USB. At least, I have not been able to do so. I flash from my SD Card. You can get Task 29 here-->http://forum.xda-developers.com/showthread.php?t=649191
Once you do that, flash your rom from your SD Card by following the directions here-->http://forum.xda-developers.com/showthread.php?t=550540
Hopefully this fixes your problem. If it doesn't, you don't have to soft reset to free up ram. I use software called "cleanram" and usually run it on level 3 which means that it thoroughly finds processes taking up ram and reclaims it. You can also schedule a daily, weekly, hourly clean under the settings menu. You can find that here-->http://forum.xda-developers.com/showthread.php?t=514333
Best of luck.
Oooooooooooo yeah! Task 29 is absolute magic. Completely wipes your NAND before a flash to remove the chance of old ghost files from past ROMs jacking up your system. If you've followed any of the flashing tutorials on the board then you've definitely been doing this step, and thus this shouldn't have been your problem. Not everyone has problems if they skip it, but all sorts of seeminly otherwise random problems can pop up otherwise.
marduk79 said:
2nd thing to do would be a Task 29 which will pretty much formats your phone. This is important to do because if there is any "debris' left over from any of the roms you have installed, this will take care of that. "Debris" at times cause issues that you cannot pinpoint and interfere with the rom that is currently installed. It is also important that you do this step second because once you do a Task 29 you will not be able to flash through USB. At least, I have not been able to do so.
Click to expand...
Click to collapse
Eh ? I don't know what's going wrong for you, but that's completely untrue. After running task29, you need to unplug the phone from the PC, put the phone into the bootloader (e.g. press reset while holding down the Volume Down button), wait for it to come up and say "Serial" at the bottom, then plug it back in and it should say "USB". Then you can flash via USB (which is safer than flashing from SD card, since it does more checking).
FL5 said:
You've got me, there. The last energy rom I tried was a little bit ago, and was a Maxsense version at that. Even still, it soundly failed my Opera Mobile 10 test on a clean flash off of a fresh boot (it would autokill OM 10 to free up ram without any other apps open). Any rom that does that goes straight into the bin as far as I'm concerned.
I have been meaning to drop one of the more recent builds on to see if that was just a bad experience. Maybe try one of the titanium versions, just to make sure I'm giving it a fair shake. Either way, this has now gotten at least a bit off topic. =P
Click to expand...
Click to collapse
The 20 Sep ROMs have the option of using quick menu. With that option, even with Sense 2.5 and CHT (a RAM hog), I have 88 Mb available on a normal basis. I don't use Opera 10 (also a RAM hog), but I think it would work with the new ROM.
You have to manually select the Quickmenu option.
well the problem with her phone is fixed. but now my hardware keys stay on dim but they stay on, im gonna try doin task 29 and reflashing a rom see if that takes care of my issue.
Well just for future references, I had all of the above problems and tried all of them. Issue did not go away until I did the following steps..:
Run Task 29
Flash new ROM (Issue still exist)
Flash New Radio (Issue still exist)
Reflashed Hard-SPL (This somehow fixed the issue....)
starmena said:
Well just for future references, I had all of the above problems and tried all of them. Issue did not go away until I did the following steps..:
Run Task 29
Flash new ROM (Issue still exist)
Flash New Radio (Issue still exist)
Reflashed Hard-SPL (This somehow fixed the issue....)
Click to expand...
Click to collapse
well i just did all of it and the freakin keys wont go off, n e one have any other suggestions? and thanks to every one for their help.
Hi guys and girls,
First of all here's a little bit background:
I always liked Nokia (GSM's!). My first mobile was Alcatel OT Easy db if i'm not mistaken. After that i had several Nokia's. And then for many years i have used Sharp GX25. While i was using it, GSM world has quite changed. The only GSM i saw like perfect (because of the small size) was Modu mobile at the time. But i couldn't get it anywhere. And the iPhone is like cool. But to bulky for a GSM and to expensive for a thing to call with. When the battery of the GS25 died completely i was thinking how am i going to choose now? ^^ The only thing that i liked was Modu mobile but i couldn't get it anywhere. I don't really cared a lot about some features and so on. Because to get into choosing a phone now, to choose wisely, best for the money, is like spending so much time..
I'm often sending sms to a group of like 20 people. So i bought LG Neon. First cheapest full keyboard gsm i came across. I was thinking you know, Nokia is like the best ever, or has been for me, but i have to give something else a chance. Although i liked the full keyboard it was a really bad experience. But i learned something. So after that i remembered, that i was thinking sometimes, if iPhone was a little bit smaller and cheaper i would buy it. But then i accidentally realized. There are so many ideas you can google. Lets try, cheaper iPhone alternative. So i found Nokia Tube (5800, second hand). I pretty liked it - cheap, compact, a lot of features. I discovered mobile email/gps/sip telephony!/calendar/touchscreen and other nice features of a smartphone. Symbian (Nokia) was still good for me. So now i became kind of accustomed to this nice features. But Tubes touchscreen wasn't really great ether. So i was looking out for some other, more advanced, full keyboard/touchscreen smartphone. Not necessary touch screen, but anyway, it would be nice. So for some time i have been looking on a second hand sites to get a second hand blackberry. Because after researching the question of mobile Emailing i came to a conclusion that Blackberry is the best in it. And even that Blackberry is maybe like the best smartphone of all because of user friendliness, design maybe, and a technological advancement. Like the Mac in a PC world. As i see on the video reviews Blackberry's interface looks more text based would i say. What in my eyes is perfect for a smartphone. I don't see a lot of sense in bells and whistles, or how is it said then in actual information. But!
About not mobile experiences:
It's already for a view years that i am using Linux on my desktop. Since the time when i have got the GX25 i guess. Because i have been quite interested in IT from when i was younger. And now later i already became IT professional and run some Linux servers to. And even my Mac Mini at home runs Linux. I find Mac OS X amusingly technologically advanced, easy to use, user friendly and all that. But i cant install it on my workstation and a laptop at work. So that's the practical reason i choose Fedora over any other OS. No fanaticism here. Because i'm Christian and i believe in Jesus Christ. Because from His words in Bible i learned, or got at least some kind of understanding of what is love actually. So i don't have to be religious about Mac or Linux.
The funny thing actually is, i have used Gnome 3 now for a view month already on Fedora. And a view days ago installed Lion on a Mac. Wow, they already put all the Gnome 3's features in Lion, like first Spaces and now Mission control and Launchpad. ^^
Now, closer to the business - CM6? Dream:
So finally i was thinking, what else can i get, then android. I actually nearly bought Blackberry 8520 pretty cheap. But G1 compared to it has GPS and AutoFocus. And it runs Linux *thumbs up* \o/
Now, when i got the package from Netherlands view days ago. The guy have put CyanogenMod 6 on it for me. But after a day of use i discovered that when you call to me you go straight to voice mail. And i pretty liked CyangenMod's interface although i had an idea, from youtube videos that Hero rom would be nicer(visually). Google apps were not installed ether. So i googled a little bit. And At some places they said that you have to install google apps. But it didn't work. I tried installing it, but always got message about making recovery backup. And then after reboot still no Gapps installed. The phone came with a sd card with cyanogenmod rom on it and two hero roms. Off course before buying it, i already searched for some info. And went to CM wiki. And first questions that arised for me were: how do i determine which radio does the phone has? When i emailed this question to a guy from who i bought the phone he said that someone else has put Hero on it for him. So before he sent it to me he had put CM6 on it. This is i think where the trouble with calling is from. So i played a day with CM6. And using the ROM manager have put Hero on it back. Because seeing video reviews i thought it looked cooler. But now i have an impression, while using Hero rom, like CM6 was better. Like more tweaks and so on. So another question: What are actually benefits of CM6 compared to Hero rom, and vice versa? And the other question is: How do i put CM6 back? Because i don't find ROM manager in the menu anymore. Do i have to install it again? And by the way. I have made a recovery backup when rom manager asked me to do it while trying to install gapps. But doesn't matter a lot i guess. Because people couldn't call me there anyway. And here on Hero it works. I ask myself does the firmware for radio sit in the rom or not? (Ohh, and i actually just realised something, rereading the post here, and checking for errors. Would the radio rom be something like phones bios? And ROM like phones os?)
And also i'm confused a little bit about the process of flashing now. On the wiki i read bout installing DangerSPL and so on. But i have put Hero now just using ROM manager. Has it become easier or how does it work today? Also i ask myself which CM version is like optimal for Dream? To get some nice features but not getting to slow? I guess it would be 6 right?
Okay, hopefully someone can share some knowledge with me about all that rom flashing thing. Or point me to the right direction. Where to start reading.
Thanks in advance,
Sincerely yours,
Nikolai
versions info
Ok, i figured something.
Im reading the "HTC Dream: Installing CyanogenMod 5+" wiki page and heres the info i found so far:
DREAM PVT 32B ENG S-OFF
HBOOT-1.22.2005 (DREA11000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009,15:30:43
HBOOT
Parsing...[DREAIMG.nbh]
[1] RADIO_V2
[2] BOOTLOADER
[3] RECOVERY
[4] BOOT
[5] SPLASH1
[6] SYSTEM
[7] USERDATA
Do you want to start update?
<ACTION> Yes
<POWER> No
============================
ClockworkMod Recovery v2.5.0.7 (the version)
============================
ROM's on the SDcard:
update-cm-6.1.0-DS-signed.zip
gapps-mdpi-tiny-20101020-signed.zip
---
zx2.1hero.v1.5.1.zip
update.ZX1.5Hero.v2.0.1.zip
dream_magic.2.22.19.26i.zip
Now i expect that offcourse DangerSPL is already installed so i skip this part. Only the version numbers are different. Wiki says 33 and my phone says 22. Then i see there the line tat says: "Select USB_MS toggle" - what does this suppose to mean?
ok
Ok i figured it. Rebooted into the recovery mode. Flashed CM6.1. Ended up in reboot loop. Googled. Wiped. Reflashed. And now it works. Working CM6.1 with working recieving calls.
THanks you guys.
DangerSPL
Hi agane,
The guy from who i bought the phone told me that i have to flash in this order:
-Wipe cache/data
-Install zip: de gewenste ROM
-Install zip: Google apps tiny
-Install zip: DangerSPL
But i havent done DangerSPL. Does it matter?
given that u already are running danger spl,u neednt flash it again, unless u upgrade ur radio and have to flash the corresponding spl....
ok thanks
Ok thanks, that's what i was thinkig.
Froyo by Lazslo
Hi guys,
im back to hacking ^^
well since i work and do alot other things i just bought a Blackberry 9780 and hapily used it all the time since i last posted here. And device is great. I like it alot. There was just a little issue i tought would be nice if it could be fixed. So i asked the retailer i bought it from to send it to BB. The stuttering keyboard is it. Google if u wanna know.
So now. Since i had blackberry i havent used Dream anymore. But back in the time i last posted here the sales guy who sold me the BB had a Dream to. And he advised me to use the Froyo by Lazslo. So now after a view month im back at Dream. I actually pretty havent used it alot.
So now i took my Dream and flashed the froyo by lazslo on it. The slp and radio numbers u can see in my previous post. So not i got the G1 logo at boot and the phone isnt booting. I suppose i did not good just flashing it. Because spl and radio numbers mentioned in the froyo by lazslo thread are not the same as mine. But i thought ok lets try. Wiped and installed the froyo by lazslo rom. And now have G1 logo. Well if i push camera button when booting i get into fast boot.
But can i push some combination to get into recovery to flash for example atleast cgm that atleast worked for me? TO get back to working state? Or what can i do now further to get froyo by lazslo running on it? Does the G1 logo means its bricked or not? Because dont know really? Have googled and found that theres posibility to do something via cmd. Any more info on this?
I google further, but dont have alot of time,
Thanks in advance,
Nikolai
good found something
i see that i had to have the ecsactly spl and radio mentioned in froyobylazslo thread
now gonna search how i install them,
because i got the phone with them already installed
not brickked - fixed
oh, good, got it fixed,
have pushed power and home button not long enough before,
so now after getting into the recovery flashed cgm 6 back on it. and its working
but i still think and will search more the other day to put froyobylazslo on it
just need to find instructions to get to newer spl and radio on it.
would anyone help thanks,
now gtg to Church,
see yaa
un root?
Hi all again,
So,
Is it so that i have to unroot and reflash all from the beginning now to jusmp from
HBOOT-1.22.2005 (DREA11000)
RADIO-2.22.19.26I
to
SPL: 1.33.0013d (hboot)
RADIO: 2.22.27.08 / 28.25
let me know please. ty.
edit,
ahh yes,
or can i still do something to flash froyobylazslo with my radio and spl and tont end up with g1 boot screen?
Nikolai_D said:
Hi all again,
So,
Is it so that i have to unroot and reflash all from the beginning now to jusmp from
HBOOT-1.22.2005 (DREA11000)
RADIO-2.22.19.26I
to
SPL: 1.33.0013d (hboot)
RADIO: 2.22.27.08 / 28.25
let me know please. ty.
edit,
ahh yes,
or can i still do something to flash froyobylazslo with my radio and spl and tont end up with g1 boot screen?
Click to expand...
Click to collapse
There is no need to unroot and start from the beginning. I suggest you to learn how to use fastboot and then read in Terry's 2708 thread how to do the update.
Another hint: After you are on the "new" SPL/radio combo you should check twice whether the ROM you want to install supports this combo, otherwise you will stuck on the G1 screen ...
this
Hi,
the guy here explains some things,
http://www.youtube.com/watch?v=sYg3UmQd5y4
what if i download the radio and spl that i need for froyobylazslo and update them the same way thee guy in the video did. Is it gonna work?
p.s. it looks the link u gave is definitive place aboout that but its difficult to follow
On the first look it probably looks difficult, but if you want to root your phone, install unsupported radio and SPL on it, then it's worth to invest some time to learn a bit more of this topic. Otherwise, if you do something wrong or you follow a guide which doesn't comply to your current "configuration" of the phone , risks are high, that it will get bricked. Just my 0.02 cents.
Sent from my Gingerbread on Dream using XDA App
back
hi all,
im back to mess with it a littlebit,
I installed Anroid SDK, and now i want to start flashig via fastboot as described in the link posted above.
But i dont get how do i start a CMD. Just starting CMD and writing for example fastboot devices in CMD doesnt do anything.
Any suggestions please?
And yes im googling to.
Thanks,
Nikolai
First you need to connect your phone to your PC by USB and get it recognized. You can check that by opening a command line window on your pc and typing
adb devices
if your phone is in "normal" or in recovery mode. You should also check whether you enabled "USB Debugging" in Menu -> Settings -> Development.
You should get a list with your device.
To check fastboot, your phone needs to be in fastboot mode. Switch off and reboot by back-Button pressed. In this case the phone gets into the hboot screen.
Now you can type
fastboot devices
on the command line and if your phone gets recognized, you will see it in the list printed on the screen. If it is not recognized directly and serial0 is printed on the phone's screen, try to press the back button. Then "fastboot" should be written on the screen and you can re-try whether your phone will be recognized.
figured
ok i figured that i had to download the fastboot file mentioned here
http://wiki.cyanogenmod.com/wiki/Fastboot
And the system variable path needed to be configured right.
now i dont have dll error but fastboot devices doesnt show anything,
adb devices does
AndDiSa said:
First you need to connect your phone to your PC by USB and get it recognized. You can check that by opening a command line window on your pc and typing
adb devices
if your phone is in "normal" or in recovery mode. You should also check whether you enabled "USB Debugging" in Menu -> Settings -> Development.
You should get a list with your device.
To check fastboot, your phone needs to be in fastboot mode. Switch off and reboot by back-Button pressed. In this case the phone gets into the hboot screen.
Now you can type
fastboot devices
on the command line and if your phone gets recognized, you will see it in the list printed on the screen. If it is not recognized directly and serial0 is printed on the phone's screen, try to press the back button. Then "fastboot" should be written on the screen and you can re-try whether your phone will be recognized.
Click to expand...
Click to collapse
thanks
trying further
duplicate post
spoofspl?
Do i have also to do this?
> A Rom (note: many cm6 based roms block install because of the '1.33.0013d' bootloader Please use firerat's SpoofSPL)
http://forum.xda-developers.com/showpost.php?p=9068311&postcount=84
Depends, what you want to do. Normally this spoofing is needed only when you want to install a ROM which officially isn't supported, but you know that it is runnig with your SPL. Especially when using cMTD you change the partition layout and some ROMs check with the SPL whether the ROM fits into the system partition or not.