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 )
Related
Hello everyone,
I have a rooted g1 and I was putting on the 2.1 rom on my phone. I was following a guys instruction off of youtube but it totally messed my phone up. Now its stuck on the pitcure with the open box pointing a yellow arrow on the phone right next to it(the update screen), what do I do??? Thanks for your help.
You dont even have root then...If it shows what i think your taking about....You should follow this simple enough my little brother(7yr) could master it:
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
no i have root access i already had about 5 other roms on there but this guy said that you need a radio update sign. the guys site is http://www.youtube.com/watch?v=QfPI9Qdagd0&feature=related
Sagz326 said:
no i have root access i already had about 5 other roms on there but this guy said that you need a radio update sign. the guys site is http://www.youtube.com/watch?v=QfPI9Qdagd0&feature=related
Click to expand...
Click to collapse
If you had root why did you flash the radio again?
That gives bricks applying radio after having root is pointless.
What are you trying to do?
i dont know im a noob if you dont know by know. well is there anything i can do???
Sagz326 said:
i dont know im a noob if you dont know by know. well is there anything i can do???
Click to expand...
Click to collapse
Just tell me everything you did, step by step.
ok first i put both of his zip files on my sd card then turned off my phone and turned it on with the home key, then i backed up my phone, then a factory wipe/reset, then applied the radio update, then tried to apply the other zip file but couldnt, so i rebooted my phone and now im stuck
Sagz326 said:
ok first i put both of his zip files on my sd card then turned off my phone and turned it on with the home key, then i backed up my phone, then a factory wipe/reset, then applied the radio update, then tried to apply the other zip file but couldnt, so i rebooted my phone and now im stuck
Click to expand...
Click to collapse
radio and spl?'
But you have to have a custom recovery image before you can flash either of those.
i think it was just a radio but not sure. but i followed that guys video step by step and now im in this position
yeah i have amonra
Sagz326 said:
i think it was just a radio but not sure. but i followed that guys video step by step and now im in this position
Click to expand...
Click to collapse
Ahh you might brick, you seem to have flashed the Radio made for HTC hero not G1....Notice the title: "How to get Android 2.1 on HTC Hero"
To use Hero 2.1 on G1 it shows it here @ XDA, you only needed Haykuro SPL and the 26I radio/
If rec mode is working then you arent brick or if you can get into bootloader.
how do i get in rec mode or bootloader
Hold down home when turning on the phone=recovery
Hold down camera button while powering on= bootloader
If you can't get into either one of those, likely bricked. I know with WM devices flashing a radio for another phone is one of the fastest ways to brick your phone, Android seems to be much more forgiving, so hopefully you will be lucky and if recovery and bootloader don't work, you can possibly get ADB to work.
If you don't figure out how to do this BEFORE you do it, you will likely brick your phone, if not sooner, soon enough. Doing it along with a video isn't enough to make sure you won't brick your phone.
Read through the steps of rooting, flashing a basic, stock ROM, do that a time or two, and then get into the more up-to-date stuff.
Your method of going about a new task is going to... well, it isn't going to work, unless you are really, really lucky.
Hi all,
I’m in desperate need of some of your wealth of experience, i have managed to root and flash my g1 with - rc9 JFv1.51_CRB43-EU.zip (Jesus freke), and recovery-RA-dream-v1.6.2.img recovery image!. Now i want to update to a newer rom!
Now for the problem, the recovery program allows me to flash many of the rom's available but none of them work after the flash completes it just loads the g1 screen and stops there i have left it on that screen for about 10 min’s and nothing at all happens, but then it will allow me to flash back to rc9 JFv1.51_CRB43-EU.zip absolutely fine no issues every time?. Do i need to install anything else before updating to Open Eclare 2.1.1 or SuperD1103-blk.? I’m in the UK with a UK g1 mobile if that makes a difference?
crusader0071 said:
Now for the problem, the recovery program allows me to flash many of the rom's available but none of them work after the flash completes it just loads the g1 screen and stops there i have left it on that screen for about 10 min’s and nothing at all happens, but then it will allow me to flash back to rc9 JFv1.51_CRB43-EU.zip absolutely fine no issues every time?.
Click to expand...
Click to collapse
Just use the top three wipes available in Anon's recovery menu: Wipe System/Data (1st), Davilk Cache (2nd), Ext Partition (3rd). If you haven't partitioned your SD card into FAT32, Ext2, 3, or 4 and Linux-Swap, do so now with the Recovery menu. You must backup your fat32 first, because a total repartition will totally blank your data. Good luck!
crusader0071 said:
Hi all,
I’m in desperate need of some of your wealth of experience, i have managed to root and flash my g1 with - rc9 JFv1.51_CRB43-EU.zip (Jesus freke), and recovery-RA-dream-v1.6.2.img recovery image!. Now i want to update to a newer rom!
Now for the problem, the recovery program allows me to flash many of the rom's available but none of them work after the flash completes it just loads the g1 screen and stops there i have left it on that screen for about 10 min’s and nothing at all happens, but then it will allow me to flash back to rc9 JFv1.51_CRB43-EU.zip absolutely fine no issues every time?. Do i need to install anything else before updating to Open Eclare 2.1.1 or SuperD1103-blk.? I’m in the UK with a UK g1 mobile if that makes a difference?
Click to expand...
Click to collapse
Make sure you partition your sd card and then try like the above said....or maybe try flashing death spl.
http://forum.xda-developers.com/showthread.php?t=625886&highlight=Death
thanks for trying to help but....
hi thanks for your help but ...
i have partitioned the card via anons recovery flasher, i have set my 8gb to 96mb swap , 1.5gb ext2 and the rest is used for fat32.
i have also gone throught the menu and deleted / erased the top 3 as requested but when i install a new rom it still freezes on the g1 welcome screen? please help!
G1ForFun said:
Make sure you partition your sd card and then try like the above said....or maybe try flashing death spl.
http://forum.xda-developers.com/showthread.php?t=625886&highlight=Death
Click to expand...
Click to collapse
hi i just noticed im using Hard Spl update at the moment ? how do i update to Haykuro?
i think i have totaly broke my phone? - i downloaded haykuros spl and flashed it via the anons recovers flash image from sd card, and now i can no longer get in to the recover menu? and no fast boot please please help me !
crusader0071 said:
i think i have totaly broke my phone? - i downloaded haykuros spl and flashed it via the anons recovers flash image from sd card, and now i can no longer get in to the recover menu? and no fast boot please please help me !
Click to expand...
Click to collapse
This is YOUR FAULT for NOT READING!!!!
You installed an SPL meant for an HTC MAGIC onto your HTC DREAM. It *CAN* be made to work, HOWEVER, you failed to read and understand what is required to actually do it safely.
SPECIFICALLY, you are stuck in boot mode 3 -- boot to recovery, and because you changed the SPL, your recovery partition is UNABLE TO BOOT.
You are BRICKED, and the only way out is to use a hardware interface called "JTAG", which requires you to disassemble the phone.
SPECIFICALLY:
You missed the part of that thread that says "MOD EDIT PLEASE READ THIS THREAD FOR UP TO DATE INFORMATION".
I have no sympathy for you. That instruction is in big purple letters.
hi thanks for your info, do you know anyone or anywhere i can get my phone jtagged?
How could you mess it up with step by step instructions....lol...I am being dead serious....it doesn't get more clear than this.
IMPORTANT: Before going any further make sure that you have PVT board. You can do this by rebooting your phone and holding the camera button. The first line should say "PVT" if you see "DVT" then DO NOT flash this because odds are you will get a brick but If it says "PVT" then you are good to go.
First you are going to need to download the latest radio and the SPL. both can be found here http://code.google.com/p/sapphire-port-dream/ There is also a new radio that is compatible that can be found here http://forum.xda-developers.com/showthread.php?t=640535
Prior to starting the installation process please make sure that your battery has a good charge. Also DO NOT pull your battery out at anytime during the installation process. I know it seems like common sense but I read a thread where someone had pulled their battery in the middle of the installation process and they ended up with a brick.
Now that all that's out of the way lets get started!
1. Copy "ota-radio-2_22_19_26I.zip" or "G1-radio-2_22_23_02.zip" and "spl-signed.zip" onto the root of your SD card.
2. Reboot into recovery. I suggest using the RA-dream recovery you can download it here http://forum.xda-developers.com/showthread.php?t=566669
3. Wipe your phone "factory data reset" (this step isnt really necessary since your phone is wiped after flashing the SPL but I always like to wipe before flashing anything)
DO NOT SKIP THIS NEXT STEP OR YOU WILL BRICK YOUR PHONE
You must have the latest radio "2_22_19_26I" or "2_22_23_02" to flash this SPL if you already have the latest radio you should not have to flash it again but it will not hurt if you do flash it again. When in doubt flash it anyway.
4. Flash the Radio "ota-radio-2_22_19_26I.zip" or "G1-radio-2_22_23_02.zip" it will install and then it will ask you to reboot to finish the installation, so reboot, it will then finish installing and then reboot back into recovery.
5. Flash the SPL "spl-signed.zip" it will install and then ask you to reboot to finish the installation, so reboot, it will then finish installing and reboot into recovery so you can flash your ROM
i cant get in to fast boot or recovery i just get the g1 screen, if i press camera and power or if i press home and power i just get the g1 nothing else
crusader0071 said:
i cant get in to fast boot or recovery i just get the g1 screen, if i press camera and power or if i press home and power i just get the g1 nothing else
Click to expand...
Click to collapse
Did you follow those steps when flashing the SPL? Did you even flash the radio before flashing the SPL?
It sounds like you have no idea what you did to your phone which is never a good sign (and usually means you shouldn't even be flashing custom radios/spl's/roms)
no i did not, i was asking for help for the last 2 or 3 days? i did what i thought was right but it was not. can i fix it or not?
heres what you do
ive did this too lmao jus go here www*androidhustler*blogspot*com ( THE * ARE REPLACEMENTS FOR . BECAUSE I CANT POST A OUTSIDE LINK SO U GET WUT IM SAYING SWITCH THE * WITH A . ) THEN SCROLL DWN TO A POST CALLED THE 2010 HOW TO GET CYANOGEN LATEST. DO ALL STEPS AND DONT RUSH. IF YOURE G1 DOESNT BOOT UP PROPERLY THEN I QUIT THIS SHYT BRO. LOL FOR REAL AND IF U HAVE ANY QUESTION EMAIL ME AT [email protected]*COM
crusader0071 said:
no i did not, i was asking for help for the last 2 or 3 days? i did what i thought was right but it was not. can i fix it or not?
Click to expand...
Click to collapse
Sigh....I would go buy another phone off Craigslist or something similar.
Next time...please read before flashing....Although I'm sure you will after the last mishap.
the only way to fix your phone is to buy a doner phone with a broken screen or something cheap off of ebay
there is NO KNOWN WAY to fix it without a doner (the jtag method isnt do-able yet)
I know here in town...there are so many G1's up for sale around the $150 mark in really really nice condition.
That's where I'd be looking if I bricked my G1. Well...I'd be replacing it with a HD2 probably...lol
garok89 said:
the only way to fix your phone is to buy a doner phone with a broken screen or something cheap off of ebay
there is NO KNOWN WAY to fix it without a doner (the jtag method isnt do-able yet)
Click to expand...
Click to collapse
What do you mean by jtag method isn't do-able?
ezterry did mine without an issue.
details
Sleeepy2 said:
What do you mean by jtag method isn't do-able?
ezterry did mine without an issue.
Click to expand...
Click to collapse
have you got contact details for ezterry? if so pm me please.
as far as i can see the jtag is still in testing?
This noob is in the UK anyways. Let him figure it out.
Wrong section, soft bricked his own phone and freaking out.
Please READ. You are from the UK so your English isn't bad. You have no excuse for not following instructions.
Ways to fix your phone:
1) motherboard replacement
2) JTAG (experts are not anywhere near you though)
3) buy a new phone
Mods please get this out of here
no adb and no fastboot on pc
i can go into recovery but when phone boots it goes straight to tri color screen a.k.a bootloader with serial0
i tried downgrading it shows down grade on bootloader but not booting to rom what am i not doing
any suggestions
mods close thread solved by reflashing org.spl
ok it happen again and this time flashing stock spl is not working any help any one
Well it's very probable that by flashing your stock spl that youre now running a perfected spl which won't let you get any further, If you do manage to get back into the rom adb erase and flash a new recovery and spl because it sounds as if your recovery is fried. If you want help from others it would be a good idea to include rom, spl, radio, recovery that you're running so we can better assist you. every combination is different and often it's something as simple as a radio/rom mismatch or an overclocking issue
ok im at complete stock everything
rooted or unrooted?
one second thought.. try downgrading and re-rooting your phone via old school rc29 rom versions..
something has obviously gone awry. lets see if flashing an older rom will get you into the phone and then you can flash a new recovery, spl and radio from there.
http://forum.xda-developers.com/showthread.php?t=442480&page=35
Sometimes you just gotta redo everything because of software mismatches and extra crap in your phone that isn't supposed to be there.
i had bought the phone like that stuck on bootloader i fixed it after i tried to flash the org. spl it didnt flash but after reset it booted fine after rooting and using the danger spl and cannon complete eclair my carmera went bugging so i decide to downgrade and reroot i flashed the rc29 but it went back to the first problem again
all eclair roms have problems with cameras.. but this sounds more like there's just something not right.. could be anything from your radio to your recovery.. Full wipe and restart the process I no longer have a g1 but im pretty sure if i downgraded from 2.1 to rc29 my phone would act screwy too.
i did the full wipe formated sd cards i am at a brick wall with out a brick
thatruth132 said:
i did the full wipe formated sd cards i am at a brick wall with out a brick
Click to expand...
Click to collapse
set up sdk/adb and see if your phone is being found or not with the command
Code:
/cd
cd AndroidSDK/tools/
adb devices
i have adb installed correct its not picking up in adb at all no fastboot of course
I don't know i maybe wrong but think you should start all over again
downgrading to v1.0
although i am not that experience
please wait for someone how know
nothing i try is catching
still needing help
And we still don't know what you have installed..
1) make sure your phone is off: boot into the spl by turning on the phone while holding down camera.. tell us all the text on that screen
2) power off your phone again and enter recovery (power on holding home) if it loads do you see any version info? Or just an icon in the center of the screen.. if it dosent load tell us that
3) can you boot into a system (in your case I assume not but if others are reading) tell us the build number and rom if possible in about phone. If it wont boot tell us that.
4) Last what carrier and country is the phone originally from. (This changes what "stock" is)
With all of this information we can find the correct path to solve any issues.. usually without resorting to jtag.
DREA 100 PVT 32B
HBOOT 0.95.0000
CPLD 4
Rado 2.22.19.26I
Sep 2 2008
At this point, I searched around again for 30 minutes or so, and saw the stuck camera button problem and took off the back battery case and performed a restart and still went straight to the SPL with almost no delay. The camera button depresses properly and doesnt seem to be stuck.
After all this, I figured I should just start off fresh, so I flashed the DREAM.nbh for RC29 that is listed everywhere in order to get root. On restart, I held down the camera button, and the white screen comes up to ask if I want to boot image.
I do, and everything goes off without a hitch, I press action key to restart and end up at the SPL screen again, this time, my radio is down to v1.2 instead of v2.2 so I know I changed something. I have done this update twice just to make sure everything is going right but I am still stuck at SPL.
Sorry for the extensive post, but as you can see, I did a bit of trouble shooting before I posted this.
1 did that
2 did that regular recovery
3 can not boot into system on 1.5 cupcake signed-kila-ota-148830.de6a94ca.zip
4 tmobile usa
anything i know its not bricked
OK you have rc29 installed. That is the original android with 1x radio. So software wise you are fine. (Ie not bricked)
The problem is you need to enter normal boot and are always entering the spl instead?
My guess is the camera button is stuck..
The real button is surface mounted on the main board what you press is a user friendly piece of plastic on top of that, attatched to the phone's cover.
If you have any warranty get T-Mobile to take a look.. Otherwise you can try opening it and cleaning it out.
i tired that and i actually switched the mother boards and check the buttons and nothing is stuck when i update to rc29 it lets me when i update to cupcake it lets me the text even changes on bootloader but not actual boot
Hi everyone really sorry for opening a new thread for a G1 brick.
My G1 has stuck at the T-Mobile screen and on pressing Camera+Power i cant get into fastboot to restore using the .nbh file.
I am not able to get into recovery using power+home key also.
There has to be a way to get my dream back....
please please please help
JTAG or go for a replacement. I'm guessing it's a DangerSPL brick, right?
Danger SPL
Yes dude....
i have done this so many time.....
this time i forgot to update the radio first and this is stuck....
Someone should have a solution for this....
I read many thread which say use it as a paperweight...
I am not loosing hope....
XDA Member will have some solution.....
Maybe you should try to keep current on developments.
There is NOT A SINGLE REASON to use the deathspl.
As for your "poll"... what do you expect to learn from something like this? Do you realize that any numbers you get will be completely MEANINGLESS?
lbcoder said:
Maybe you should try to keep current on developments.
There is NOT A SINGLE REASON to use the deathspl.
As for your "poll"... what do you expect to learn from something like this? Do you realize that any numbers you get will be completely MEANINGLESS?
Click to expand...
Click to collapse
By adding the poll I am just trying to avoid post which says hey even i have the same problem.
I was upgrading to cm 5 which needs deathspl.
chinmayfun said:
I was upgrading to cm 5 which needs deathspl.
Click to expand...
Click to collapse
Aaaaannnnnd.... it doesn't need it
http://forum.xda-developers.com/showthread.php?t=704560
lbcoder said:
There is NOT A SINGLE REASON to use the deathspl.
Click to expand...
Click to collapse
Sure there is as its one if the few full engineering spls. And I don't think your latest development will ever be quite as user friendly (however some more configuration it will be very close)
The real user friendly fix/patch for 1.33.2005 (those that know what they are doing can decide if any benifit of the spl exists) is an assertion statement in the recovery script to check the radio version is not one of the two common 1.x ones.
(the evil patch is to make the assertion somehow also autoinstall the lattest Rogers e911 patched rom if the user has the 1.x radio. Because atm the rogers rom appears to be very safe from the user messing up the boot chain.. actually we may need to "perfect" the spl a bit more I think it will let us erase hboot)
I am still a newb to the android scene - and do believe I as well made the same mistake - and have bricked my G1.
If eveything I've read is accurate, I can purchase a donor phone - broken screen, or other issues - so long as the mother board is still good.
Swap out the new mother board for the bricked one, and have a working phone again - right ?
Have an opportunity on a donor phone - have no issues pulling phones apart, and putting them back together
But just want to make sure I understand the basics
Thanks in advance for any replies
Motherboard only option ?
Is replacing the motherboard the only option left ?
I am not sure i would be able to do that
Worst day of my life i screwed up big time
Any help is appreciated.
Some tool to recover back to original.
I can understand there is no way to repair as I am not able to get into recovery nor fastboot so cant adb also...
youtube
i checked the below video bt this is kinda a complicated and nt a solution for me
chinmayfun said:
i checked the below video bt this is kinda a complicated and nt a solution for me
Click to expand...
Click to collapse
There is no tool to get it back except by the options listed above. If you are not going to switch the mobos in the G1 then you won't be able to do the other option either. There is no software that can bring your G1 back after a deathspl.
protomanez said:
There is no tool to get it back except by the options listed above. If you are not going to switch the mobos in the G1 then you won't be able to do the other option either. There is no software that can bring your G1 back after a deathspl.
Click to expand...
Click to collapse
Thanks....
i will have to plan out on buying a new android....
had waited for a long time to get tht android phone from a friend in usa....
now there are many android phones available in india.... will have to start saving some money.... cant live without an android....
hey,
i had the same prob.
only thing,
mine bricke in cause of a radio update,
i tried all which was in my head,
and all i can do
but after some nights spending to my phone i found this:
i copied my nand backup to root of sd,
and connected it to pc
first he told me, device not known
so i tried to boot the modified recovery,
and *tada* i was in recovery mode,
plz try and tell me if it fix your problem,
for mine it did
best regards,
psycho
Mine is also due to radio update dude, before flashing spl the radio has to be flashed i and forgot to do that.
Will try out your suggestion, just hoping that it work and my g1 is back to life.
Ne ways appreciate your suggestion.
Please let me know if you were able to get into recovery mode prior to putting the files on the sd card.
And if you could tell me the list of files (if u had nething other then the nand update) which you put on the sd card, i can replicate the exact process.
Thanks,
Chinmay
Hope
Is there any hope to get the G1 back to life from the Death SPL Brick ?
You should read instructions carefully man. Its not that hard. You should always verify that you have a compatible radio before flashing DangerSPL.
There is a method to recover your device and it involves a lot of time and patience. Google "JTAG".
Sent from my HTC Dream using XDA App
"JTAG".
me too, my G1 Bricked (Not able to fastboot). but i wanna know if the JTAG method work 100%.please.
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.