Related
Hello to all,
This is my first post on this forum. First of all I want to clarify to everyone that I'm spanish and I'll try to explain this in the better way I can. I've searched for similar cases but I don't know how really find a solution to this.
Today I've recivied a HTC Dream from a guy who sold it here in Spain. He said that the phone was crashed the installation of the firmware. What I've is a phone that only shows the boot image (in this case 'Telefonica Movistar', the carrier of the phone).
I can acces to the Recovery Mode by pressing 'Home + Power' and then ALT + L. In the microSD card I've a recovery.zip. It's not mine, I think that the user put on it. I don't really know because its the first Android system I touch.
When I access to the recovery mode, the first message I get is:
Code:
Android system recovery utility
E: Can't open /cache/recovery/command
I wan't to know if there is some way to go a stable version and later update to some modificated ROM with root support and extras.
Thank you in advance.
Sorry for school English.
Isern Palaus
Sorry!! This should go to 'Dream' thread.
Ask here. Read the rules before posting.
http://forum.xda-developers.com/forumdisplay.php?f=507
This post is going to get moved to the Q&A section by the mods shortly, I suspect.
What you need to do is follow the instructions found on this post. They will take you through flashing the old RC9 image (in English), using the SPL rather than recovery mode. You could then, from there, flash a new recovery and ROM. (Can't help you with the language part. Don't know it -- but I'm sure it's out there.)
IConrad01 said:
This post is going to get moved to the Q&A section by the mods shortly, I suspect.
What you need to do is follow the instructions found on this post. They will take you through flashing the old RC9 image (in English), using the SPL rather than recovery mode. You could then, from there, flash a new recovery and ROM. (Can't help you with the language part. Don't know it -- but I'm sure it's out there.)
Click to expand...
Click to collapse
Hello,
First thank to you. And yes, this sould go to Q&A, so if any moderator can move, I tried editting but there is no option.
I'll try it, but I supose that you are saying RC29.
Thank another time.
Isern Palaus
ipalaus said:
Hello,
First thank to you. And yes, this sould go to Q&A, so if any moderator can move, I tried editting but there is no option.
I'll try it, but I supose that you are saying RC29.
Thank another time.
Isern Palaus
Click to expand...
Click to collapse
I think he actually means RC8 for UK versions.
Hello,
I tried to flash it with the RC7 for UK versions and I got: Model ID incorrect! Update fail!
What I see on the top of the screen is:
Code:
DREAM PVT 32B SHIP S-ON
HBOOT-1.38.0000 (DREA20000)
CPLD-4
RADIO-2.22.16.19
Feb 28 2009, 18:40:30
I can try with the RC29... How to know if its US or UK (EU)?
EDIT: The same with RC29.
Thanks in advance,
Isern Palaus
Just noticed your HBoot version. Hopefully you have fastboot. (Press and hold the camera while booting up the phone, with it plugged into your computer via USB cable. Press "back" a few times; you should see "Fastboot USB" in red.)
From there, follow the instructions found here (starting w/ post # 53):
http://forum.xda-developers.com/showthread.php?t=493241&page=6
Has something to do with the fact that the European HTC Dream isn't the same as other Dreams.
From there you should pretty much be able to run any ROM you need. We hope.
As I am in the US and got my G1 during pre-order, I haven't had to go these routes.
Wrong thread
IConrad01 said:
Just noticed your HBoot version. Hopefully you have fastboot. (Press and hold the camera while booting up the phone, with it plugged into your computer via USB cable. Press "back" a few times; you should see "Fastboot USB" in red.)
From there, follow the instructions found here (starting w/ post # 53):
http://forum.xda-developers.com/showthread.php?t=493241&page=6
Has something to do with the fact that the European HTC Dream isn't the same as other Dreams.
From there you should pretty much be able to run any ROM you need. We hope.
As I am in the US and got my G1 during pre-order, I haven't had to go these routes.
Click to expand...
Click to collapse
Thank you! Now I'm in FASBOOT USB, of course.
I've found in this post a link to french site where they're explaining how to install a ROM (cupcake in this case i think): http://wiki.smartphonefrance.info/Default.aspx?Page=firmware-htcdream&AspxAutoDetectCookieSupport=1
In the post the only talk about changing the keys layout. Seems that this link could help, I'll try to understand it.
If you boot up the rooted kernel using fastboot, you //should// be able to run adb remount and then install the flash_image script from elsewhere. (Such as by pulling it out of the CyanogenMod ROM's .zip files)
Drop that script ("flash_image") into your phone's /system/bin folder, and then run (as root) "chmod 755 /system/bin/flash_image"
From there, you /should/ be able to run the "flash_image" script in order to flash a new recovery image (such as the RA-dream-v.1.2.2, or the Cyanogen Recovery 1.4) which would let you, from there, flash a new IPL ("radio") or SPL -- both of which are risky business -- or else you could just flash a new ROM by booting into recovery, as per usual.
The trick is to be able to successfully boot the rooted kernel image via fastboot.
Fact is, if you can do /that/, then you should /also/ be able to simply flash a new recovery image via fastboot (though you'd have to pull it out of the *.zip):
Code:
./fastboot flash recovery /path/to/recovery.img
Hopefully this is all making sense to you.
Now I've my phone full working.
The way to do it was enter with FLASHBOOT USB and use the SDK to boot.
Update with a update.zip (I used a Cupcake 1.5) and update the radios to the latests.
Thanks to all!
HELP!!
my rogers htc dream just bricked on me last night it only goes to the htc logo and the boot loader thing (power key+camera key)
can anyone help me with this
thanks
zerokenshin said:
my rogers htc dream just bricked on me last night it only goes to the htc logo and the boot loader thing (power key+camera key)
can anyone help me with this
thanks
Click to expand...
Click to collapse
What does the bootloader screen sat (power on holding camera )
If it was 1.33.2005 (ie was rooted) install a recovery via fastboot main version if the radio starts with 2, otherwise the -r if it starts with 3
If its 1.33.00?? Go to rogers website and download the january 911 ruu and install it.. if you want root follow the new rogers rooting directions
the bootloader screen says:
DREAM PVT 32B SHIP S-ONd
HBOOT-1.33.0009 (DREA21000)
CPLD-4
RADIO-3.22.20.17
May 12 2009,17:05:58
HBOOT
<SEND>FastBoot Mode
the phone was never rooted it just went out on me after i installed some new apps from the market place
well rooted or not with the perfected spl there is not much choice install the ruu or nbh of the official Rogers 911 rom and follow the new rerooting instructions.
If you follow all of it you will have an engineering split and can get out of this easily if it happens again.
the rogers site has the HTC Dream ROM Update Utility (RUU) January 2010 is that the right thing cause if so its not working for me
zerokenshin said:
the rogers site has the HTC Dream ROM Update Utility (RUU) January 2010 is that the right thing cause if so its not working for me
Click to expand...
Click to collapse
I can't say I've ever made the RUUs work short of extracting the NBH file from your users temp directory and flashing it manually... but I always assumed I just was lazy on making the phone connect to VMWare on a mac.
Try this:
0) install fastboot/adb if you don't already have them (again I'm on a mac search for it if you need help)
1) Download http://www.rogers.com/dream-zip
2) extract DREAIMG.nbh from the zip file and put it into a directory accessible from fastboot
3) enter fastboot mode on the phone
4) run 'fastboot oem rebootRUU' to put the phone into ruu usb mode
5) run 'fastboot flash nbh DREAIMG.nbh' (specifying the rogers nbh)
5b) wait for everything to flash .. this will take a few mins
6) if the phone dosn't reboot its self run 'fastboot oem powerdown' then boot normally
Once installed + running your re-rooting info is here: http://forum.xda-developers.com/showthread.php?t=733128
i dont understand step 2
2) extract DREAIMG.nbh from the zip file and put it into a directory accessible from fastboot
Hello guys,
I know the first thing you may think is this is another moron who bricked his Cell. But please be patient with me and at least let me learn from my loss. Please let me know what I did wrong.
First I read 3 main thing before doing anything,(1) [Guide] One-Click Root for Rogers HTC Dream:, (2) the post by HYKO and and finally CyanogenMod Wiki. Since I cannot post URL I attached them at the end.
So first I tried to get a hboot 1.33.2005 SPL using the source (1) which went ok.
then I used CyanogenMod Wiki (3) to root my HTC DREAM. Every thing went ok till I tried to update the radio. After I flashed the radio my cell hangs on the rogers logo and does not go any further. I can go to the fastboot (camera butt and END). it is S-off and 1.33.2005 SPL. However, I can not reach the recovery menu (Home and END). I tried flashing back to the older radio 3.22.20.17 and 2.22.29.26I (using the haykuro zip file). none of them worked.
First I want ot know what did I do wrong. Second I noticed my SDcard is broken, and the HBOOT looks for deaimg and deardiag on sd. does anyone know if I can unbrick it using this.
Thanks
alrsar
(1)
1. Download Haykuro's root kit here.
2. Extract the recovery.img and update.zip files from the download and copy them to the root of your sdcard's fat32 partition (if you haven't partitioned your card yet for A2SD, then just the root of the card itself).
2. Last time I checked, the one-click root app, flashrec, has been pulled from the Market, so download it here.
3. Install the app and start it, it will look like this:
4. Tap 'Backup Recovery Image', in some cases the app will fail to backup the image. This shouldn't be a problem, but if it works, it's always nice to have a backup.
5. In the blank above the greyed-out button enter '/sdcard/recovery.img' without the quotes. If you were successful in making the backup, the top button should change to white and say 'Flash Custom Recovery Image'. If not, don't worry, there is a hidden button to the right of the backup button that will bypass the backup requirement. Like so:
6. Press 'Flash Custom Recovery Image'. If you get a flash failed message, try flashing with your phone unplugged from USB.
7. Power your phone down.
8. Power up your phone while holding the home button. You should get the older 1.2 Recovery Menu. If your phone hangs at the Rogers logo, remove your battery, re-install or try the 3-finger salute (Phone, menu, and power button together) and try again. If it still hangs on the Rogers logo, reboot without the home key, this will bring you back to normal boot. You won't be rooted but you won't be bricked.
9. Once you're at the recovery menu, choose the second option, apply sdcard:update.zip. In some cases you may get an error something like E: not found. If you choose the second option again, it should find the update.zip alright and then press home to continue.
10. Now click on reboot (Home & Back). Press and hold the camera button and you should boot into the new 1.33.2005 SPL.
11. If all has gone well and you see hboot 1.33.2005, you can safely follow the rest of the rooting instructions in this thread. There's also a great set of instructions for installing Cyanogen's 4.2.X roms in the same thread. The post is here.
Of course, these instructions may be rendered moot if Rogers chooses to fix the vulnerability that allows one-click root at which point we'll have to hope someone manages to find a way around the so-called 'perfect' SPLs.
If after a couple attempts you remain stuck at the Rogers logo, remove the battery, reinstall it and then power up normally. You should then boot back to the unrooted phone and it will restore the default recovery. You may not be rooted, but at least you're not bricked.
(3)
1. You will need fastboot on your computer to run the following commands. Set up ADB and fastboot on your computer.
2. Download exploid & Amon_Ra's Recovery:
* exploid (includes the source): Download
* Amon_Ra 1.7.0: Download
3. Rename Amon_Ra's Recovery Image to simply recovery.img.
4. Put both the exploid file & Amon_Ra's Recovery in the same directory as adb.
5. Turn on USB Debugging (Settings » Applications » Development).
6. Connect the Rogers Dream to the computer.
7. On the computer, open terminal & navigate to the adb folder
cd /path/to/adb/
8. Type in the following commands:
adb push recovery.img /data/local
adb push exploid /sqlite_stmt_journals
adb shell
cd /sqlite_stmt_journals
chmod 777 exploid
./exploid
9. You will see a message come up. The exploit has now been setup. Unplug & re-plug in the USB cable to the computer.
10. Now type in the following commands:
adb shell
rootshell
NOTE: This will prompt for a password, the password is "secretlol".
chmod 666 /dev/mtd/mtd1
flash_image recovery /data/local/recovery.img
NOTE: The first time this command runs, it may return "mtd: read error at 0x00000000 (Out of memory)". Simply run this command again & it should run without error.
11. The Rogers Dream has now been rooted & will have Amon_Ra's Recovery on it.
Flashing Radio
If the Rogers Dream already had the 911 patch, then the phone will already have the latest radio. Follow these instructions if the Rogers Dream did not have the 911 patch.
1. Download the latest version of the radio (3.22.26.17).
2. Rename the radio image to simply radio.img.
3. Power off the Rogers Dream.
4. Boot into bootloader mode. Hold the Camera button while powering on the Rogers Dream.
5. Connect the Rogers Dream to the computer.
6. On the computer, open the command prompt/terminal & navigate to the Android SDK Tools folder.
7. Type in the following command:
fastboot flash radio radio.img
8. Once finished, you can restart the Rogers Dream.
Perhaps try flashing a new recovey via fastboot?(aka screen with android skateboarding) with adb, looks at the rom bible in the dev section for more details. You also need the android sdk installed on your computer to do so, and a working mini usb cord.
ok first, you are not bricked, brick means cannot get into bootloader (camera+power) nor recovery (home+power), and it will be useless like a brick,thats why we call it "bricked" when you messed it up. Unless you use the jtag method, but thats for the super hardware geeks not for the people here in the forum.
Since you are not bricked, you can try to turn on the phone and wait for at least 5 minutes and see if the screen is still stuck on the same logo, because sometimes it takes quite long for the first boot after your new Flash. If it really stuck on the same logo for the damn 10 minutes, then you can try the following ways.
I dont know what version SPL and radio you use, but remember, always flash the radio first, then restart the phone then flash the SPL, because this really can brick your phone (i done it once)
- if your recovery support usb mount, then re-download the roms and double check with MD5, make sure the rom is 100% identical, then reflash it. because defected rom always caused your kinda problems.
-if it still doesnt work, do this also with your SPL and Radio zip files
-if still doesnt work, get the dreaimg.nbh file to sd, then camera+power to bootloader, and downgrade to 1.0. then start to root again carefully this time.
americanxo said:
I dont know what version SPL and radio you use, but remember, always flash the radio first, then restart the phone then flash the SPL, because this really can brick your phone (i done it once)
- if your recovery support usb mount, then re-download the roms and double check with MD5, make sure the rom is 100% identical, then reflash it. because defected rom always caused your kinda problems.
-if it still doesnt work, do this also with your SPL and Radio zip files
-if still doesnt work, get the dreaimg.nbh file to sd, then camera+power to bootloader, and downgrade to 1.0. then start to root again carefully this time.
Click to expand...
Click to collapse
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
my FASTboot command works but ADB cannot connect. I assume you mean I should flash the recovery, right?
alrsar said:
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
Click to expand...
Click to collapse
From where you are flashing fastboot or rom....
If you are able to go to fastboot mode, then flash the recovery from there....using fastboot from your PC....
alrsar said:
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
Click to expand...
Click to collapse
the last option is to downgrade your phone to its stock version which i think it would be RC29, so you can root. I think you done it once before rooting your device right ?
americanxo said:
the last option is to downgrade your phone to its stock version which i think it would be RC29, so you can root. I think you done it once before rooting your device right ?
Click to expand...
Click to collapse
Please please please do not flash rc29 on a rogers dream.. if the flash fails but installs the spl you can be in an annoying position, best unroot to the rogers firmware and root that again..
However op just needs to flash the -r version of the dream recovery.
This thread is a case of the blind leading the blind. Ignore ALL of the nonsense and read the following:
You have fastboot. That's good.
Start by installing a proper radio image. 2.22.23.02. You do this with FASTBOOT.
Go into fastboot mode, type (on your computer) "fastboot flash radio radio.img", ensuring that you have a radio.img with 2.22.23.02 in the current directory, and the fastboot executable somewhere in your path variable.
Next, flash a proper recovery image to it. Again with fastboot. "fastboot flash recovery recovery.img". Use ANY standard EBI0 recovery image that you like.
Now it'll work.
DO NOT INSTALL ANY NBH FILES!!!!!
lbcoder said:
This thread is a case of the blind leading the blind. Ignore ALL of the nonsense and read the following:
You have fastboot. That's good.
Start by installing a proper radio image. 2.22.23.02. You do this with FASTBOOT.
Go into fastboot mode, type (on your computer) "fastboot flash radio radio.img", ensuring that you have a radio.img with 2.22.23.02 in the current directory, and the fastboot executable somewhere in your path variable.
Next, flash a proper recovery image to it. Again with fastboot. "fastboot flash recovery recovery.img". Use ANY standard EBI0 recovery image that you like.
Now it'll work.
DO NOT INSTALL ANY NBH FILES!!!!!
Click to expand...
Click to collapse
Since he's on Rodgers, doesn't he need the 3.22 radio and a special recovery?
billquinn1 said:
Since he's on Rodgers, doesn't he need the 3.22 radio and a special recovery?
Click to expand...
Click to collapse
Shh people don't realize (ignoring carriers that may cause pain if they find a radio without an imei version of 3, only found on the latest 3.x radio) all dreams support 1.x, 2.x, and 3.x radios *if* installed properly.
The only thing to keep in mind is that like installing danger spl on a ebi0 stock dream, switching from ebi1 to ebi0 has a brick risk if done incorrectly.
To switch from 3.X->2.x or 2.X->3.x you need to flash the destination radio img file via fastboot (from hboot-1.33.2005) and *not* via recovery..
also after flashing you need to flash the recovery for the destination radio. (-r if 3.x otherwise the regular non -r)
As for if 2.x or 3.x is better.. they are nearly identical with some minor configuration changes that include some different memory offsets.. one or the other may or may not be better configured for any particular carrier.
Of corse there are many roms where we don't know what the kernel was pulled from for te ebi0 that since I don't know what kernel it has can't be used on ebi1.. I usually write these off however due to me not knowing where the source code is regardless of my target radio.
This only leaves the interesting aspect of lbcoder.. the amount he screams to ebi0 users not to use danger spl due to the dangers, but requests rogers/ebi1 users to switch to ebi0 radios despite the danger.. (note don't take this as you should or shouldn't do either recommendation, but that you need to understand what the approach means and what is your goal.. if you just want to access root to remove some bloat ware all you need is exploid or androot and you can keep the stock firmware.)
Ultimately however I expect people to take lbcoders advice with a grain of salt; and hopefully this will make the user actually read up on his suggestions, and what they where originally planning.. and figure out how to safely go from where they are to where they are going.
ezterry said:
Shh people don't realize (ignoring carriers that may cause pain if they find a radio without an imei version of 3, only found on the latest 3.x radio) all dreams support 1.x, 2.x, and 3.x radios *if* installed properly.
The only thing to keep in mind is that like installing danger spl on a ebi0 stock dream, switching from ebi1 to ebi0 has a brick risk if done incorrectly.
To switch from 3.X->2.x or 2.X->3.x you need to flash the destination radio img file via fastboot (from hboot-1.33.2005) and *not* via recovery..
also after flashing you need to flash the recovery for the destination radio. (-r if 3.x otherwise the regular non -r)
As for if 2.x or 3.x is better.. they are nearly identical with some minor configuration changes that include some different memory offsets.. one or the other may or may not be better configured for any particular carrier.
Of corse there are many roms where we don't know what the kernel was pulled from for te ebi0 that since I don't know what kernel it has can't be used on ebi1.. I usually write these off however due to me not knowing where the source code is regardless of my target radio.
This only leaves the interesting aspect of lbcoder.. the amount he screams to ebi0 users not to use danger spl due to the dangers, but requests rogers/ebi1 users to switch to ebi0 radios despite the danger.. (note don't take this as you should or shouldn't do either recommendation, but that you need to understand what the approach means and what is your goal.. if you just want to access root to remove some bloat ware all you need is exploid or androot and you can keep the stock firmware.)
Ultimately however I expect people to take lbcoders advice with a grain of salt; and hopefully this will make the user actually read up on his suggestions, and what they where originally planning.. and figure out how to safely go from where they are to where they are going.
Click to expand...
Click to collapse
Interesting stuff. I always thought there was a (carrier + hardware) reason for the different radio. Thanks for taking the time to explain.
Hi,
I bought a faulty Nexus one from ebay, thought I can fix it, as I did buy a faulty desire from ebay and was able to fix it. This time im not so lucky I guess.
So here it is:
The phone is stuck at X when booting normally.
I can access HBoot (But not Hboot USB Plug, because USB debugging is not enabled) and Fastboot USB. I unlocked Hboot. Fastboot in PC recognizes the phone but ADB does not as usb debugging is not enabled.
The phone is not Rooted
Here are my ideas so far:
Get somehow debugging on with some commands (No luck from reshearching in google)
Reflash stock rom with PASSIMG.ZIP in sdcard, but my phone does not recognize the file from my sdcard (I'm pretty certain im doing something wrong or my idea is somehow wrong)
Flash new images through FASTBOOT, but every time Signature check fails (Shipped-roms.com).
Root with superboot, but signature check failed here too.
Flash a recovery, signature check fails.
I will reguraly update my tries
Please suggest correction to my ideas or suggest new ones!
Help will be much appreciated!
I admit it, the phone might be briked, but I want to make sure that I have tried everything before I abandon this project.
And ofcourse I have no Warranty.
What file are you using for passimg.zip? Make sure it's not a zip inside a zip.
What images are you using via the fastboot flash command?
Sent from my Nexus One
You didn't unlock the bootloader, it seems - because if you did, it wouldn't be checking signatures, and you'd be able to flash anything.
First of thanks to both of you for helping.
I'm pretty sure that i do not have zip inside zip and I downloaded them from shipped roms.com -> android -> Passion-> PASSIMG_Google .... .ZIP, (Then renamed it ofcourse) Is there a difference what version of android i use?
The issue with this is, it checks the SD CARD and does not find anything. I have seen from google that the most common issue is that it starts to check the .zip file but then aborts. Does the SDCARD have to be a goldcard (I do have a goldcard but it might be faulty, right?)
I tried fastboot flash PASSIMG_Google.... .ZIP; Fastboot Flashall ( With having boot, recovery, system in my fastboot folder)
Maybe I should try to flash everything the .zip has in it seperately because that succeded for boot, system and recovery but I was too afraid to flash every partitation (Like Radio which seems to be the scariest and the most easiest way to brick phone)
For the third answer, I have ***UNLOCKED*** in bootloader in purple and top on the screen.
Once again thanks and keep suggesting!
Unpack the ZIP and flash each image separately.
Leave the radio as is, if it's updated enough (5.08 or 5.12). In any case, fastboot won't allow you to flash bad radio - and the risk of bricking the phone using fastboot is near 0.
For passimg.zip, you need to download the FRG33 shipped ROM from shipped-roms.com then EXTRACT the zip file that is inside the zip that you downloaded. Rename that file to passimg.zip
For fastboot, flash boot and system seperately.
When you boot the device normally, do you see the lock icon below the four colored x?
Sent from my Nexus One
Okay,
Did it one by one (PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip):
Succeeded:
Boot, Recovery, System and Userdata (that was only 3Kb)
Failed with signature check (Remote:Signature check failed):
Splash1, spcustom,
Did not do:
Radio
I'm going to post more details:
When booting up, it displays the X normally with the unlocking badge on the bottom of the screen and vibrates once. Then it goes black for a second or even less, the same images comes on and then it vibrates 6-7 times.
now that you successfully flashed the stock recovery, cam you boot into it?
Sent from my Nexus One
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
http://forum.xda-developers.com/showthread.php?t=710937
Thanks, Well thats it then for now, just have to figure out what to do now
Sounds like you need to get the PASSIMG.zip method to work, or unlock and flash a new recovery like amon ra, and flash a full rom with sig checks off.
siimplangi said:
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
Click to expand...
Click to collapse
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
any solution?
efrant said:
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
Click to expand...
Click to collapse
hi guys.i have exactly same situation.
does anyone have a solution fir this?
kobi_eidelman said:
hi guys.i have exactly same situation.
does anyone have a solution fir this?
Click to expand...
Click to collapse
Did you try all the solutions suggested above (passimg, fastboot flash, etc)? If yes then no I don't think so.
I recently started using the "Froyo Melt" ROM and while it has been better than others, I still have a problem. Whenever I try to turn Wifi on, it gives me an error. This could be due to an incompatible radio or spl but I'm not too knowledgeable on that because I bought the phone rooted and haven't done too much with it.
I'd be grateful for any help I can get, thank you.
well first off power into fastboot by holding the back arrow and power. write down everything on that screen here
then what method did you use to flash your rom --- give us simple step by step
Fastboot says:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005
CPLD-4
RADIO-2.22.23.02
Apr 20 2009, 15:30:43
To flash the rom I put the zip onto an sd card, booted into recovery, wiped data and cache, and then installed it from the zip.
You probably need a different spl/radio for the rom
But you can also try flashing a different kernel
The cm6 one would work with the spl/radio
But then you'd also need to copy all the wifi libs over
Hmmm...you can also try ezgb kernel...it should autodetect your spl/radio
I tried flashing the ezgb kernel but unfortunately it didn't do the trick. How would I go about changing my spl/radio and what should i change it to?
Google "2708+ kernel" or find it in G1 development
Follow the instructions for flashing the spl and radio from fastboot
Then you're gonna probably have to reflash the ROM
i would definitely recommend the 2708+ radio?spl combo, but i dont think it is 100% necessary for froyomelt (but it would make your rom much nicer) if you dont want to bother just do a superwipe and reflash the latest version of your rom, this should fix your wifi issue so long as it is a software not hardware problem.
It sounds like mismatched kernel/radio to me
I had the same problem with my AOSP rom
Had to flash 2708+ spl/radio and ezgb kernel to fix it
And the DreamTeam Froyo post says that it has been tested on the 2708+ spl/radio
So I think that they haven't done anything to enable other spl and radios
If wiping and flashing again does not work, then it probably is spl/radio.
Downloaded the radio and spl stuff but I'm not sure how to install it. I go into fastboot and then Hboot mode and it can't find the images. Is there a certain place I should be putting them and should I leave the radio and spl in a zip?
Download this and unzip it somewhere, like your desktop
http://www.sendspace.com/file/g8rnkq
Copy the img files from inside the dream2708kit zip into the folder
Copy recovery.img to the folder also
Now open command prompt from the shortcut in the folder
Now type the commands you are told to type in the 2708+ thread
Edit: also be careful in downloading
Sendspace has many ads
The file should be adb.zip or similar
After trying to flash the recovery on the command prompt, it gets stuck at "<waiting for device>" and the phone doesn't look like it's doing anything. Did I miss something?
make sure you are booted into fastboot
it will say fastboot usb
you can test by typing in the cmd <fastboot devices>
if you are connected properly you will see your device
Jay67 said:
After trying to flash the recovery on the command prompt, it gets stuck at "<waiting for device>" and the phone doesn't look like it's doing anything. Did I miss something?
Click to expand...
Click to collapse
Go into fastboot usb mode
Do the "fastboot devices" thing
If the phone doesn't show...
Right click on my computer > properties
Go to...I think hardware...then device manager
Find the phone...it most likely will be "android device" or something similar
Right click and do update drivers
Do "no", then "advanced"
Browse to the htc drivers folder and install the fastboot drivers
Thank you, both of you guys. It works perfectly now and runs better than ever! You both deserve trophies.
glad to hear! so you have the 2708+ now and your running froyomelt right?
Yes and it's the fastest version of Froyo i've used yet. Glad to see that my G1 isn't completely obsolete yet.
Jay67 said:
Yes and it's the fastest version of Froyo i've used yet. Glad to see that my G1 isn't completely obsolete yet.
Click to expand...
Click to collapse
Awesome
G1s are pretty awesome no matter what some say
I do so many things from my G1
Even practice some programming!
Hi there!
The RAM hack for the G1 is very popular, and EVERYONE tells fastboot is the best way to flash this. BUT, in this version it is S-On and no fastboot options. Is there a way to get S-Off on this thing? So why is everyone liking fastboot and loving it? So now nobody can use fastboot, only with DangerSPL. Of course I know that it is the standard MT3G HBOOT and SPL, but asking again, is there a way to enable fastboot on this badboy? Thanks in advance!
(I still support Recovery as my PERMANENT flashing tool!)
From what I understand:
Fastboot can only flash if it is a S-Off Hboot.
Our options seem to be to flash a temp Hboot with S-Off, flash with Fastboot, then back to the S-On Hboot. Flash something twice to flash something once. Hmm.
Or, Flash thru recovery.
Personally, I see the "Use Fastboot" method, but I also think it's dang silly to change the engine in your car so you can repaint the body, but the body color doesn't match the engine, so you replace the engine with the original. I'd rather just repaint the car in one step.
Use recovery if you want to. Use Fastboot if you want to. It's YOUR PHONE. What are 'they' going to do? Turn Apple on you, and stop you from using your phone?
What's next? We're not allowed to install and use Linux instead of Windows or OSX?
I say, do whatever method you want. If it works, why not?
Saying "only use this method" is just plain silly. It's about choice. While it may be "preferred" it is NOT the only way.
If you CAN'T flash using Fastboot, flash using recovery. If you look at many of those threads, they also want you to use superwipe. That can only flash thru recovery. And Fastboot can't wipe as well as that.
So, use whatever method works for you.
cwwilson721 said:
From what I understand:
Fastboot can only flash if it is a S-Off Hboot.
Our options seem to be to flash a temp Hboot with S-Off, flash with Fastboot, then back to the S-On Hboot. Flash something twice to flash something once. Hmm.
Or, Flash thru recovery.
Personally, I see the "Use Fastboot" method, but I also think it's dang silly to change the engine in your car so you can repaint the body, but the body color doesn't match the engine, so you replace the engine with the original. I'd rather just repaint the car in one step.
Use recovery if you want to. Use Fastboot if you want to. It's YOUR PHONE. What are 'they' going to do? Turn Apple on you, and stop you from using your phone?
What's next? We're not allowed to install and use Linux instead of Windows or OSX?
I say, do whatever method you want. If it works, why not?
Saying "only use this method" is just plain silly. It's about choice. While it may be "preferred" it is NOT the only way.
If you CAN'T flash using Fastboot, flash using recovery. If you look at many of those threads, they also want you to use superwipe. That can only flash thru recovery. And Fastboot can't wipe as well as that.
So, use whatever method works for you.
Click to expand...
Click to collapse
That's what I am saying: I have made a guide for doing this with recovery and everyone is saying why do you do that and saying just do it with fastboot. I have told them a million times that it is the choice of the user and not me and they are pushing people to do it with fastboot like it is the only option. I think that's enough, lots of people did this with recovery and no one has had a single complaint so far. What was the point of recovery anyway? To flash ROMs if you dont want to set up your computer, plug in your phone and THEN flash stuff. It's actually totally not making sense at all! I am thinkng tp put a poll to decide what is the best to do.
To put it LOUD and CLEAR: FASTBOOT IS NOT YOUR ONLY OPTION!!!!!!!!!!!!!!!!!!!!!!!!!!!!
If you support this, post a reply and just type in 'fastboot' or 'recovery' for what you use the most. Thanks in advance (again)
I use them both.
Whatever works. If I happen to have my phone plugged in to a USB port, I'll try to use Fastboot. If I don't, I'll just flash thru recovery. Sometimes, I HAVE to use Recovery.
Whatever works.
I think the point isn't fully clear.
Fastboot is nice but not the only method
When flashing something to your phone that may cause you to brick it, radio or hboot namely you should use fastboot as it has the proper checks to lessen the chance of a brick.
If you are just flashing roms and so forth recovery and fastboot it won't matter as a brick is so unlikely.
After you flash the .13d hboot you loose out on most fastboot commands due to the base of the spl. Chances are you won't be flashing a new radio or hboot with the .13d hboot so not having things like fastboot flash doesn't matter so much and the extra 14mb of ram is a fair tradeoff for this.
Yes you can flash the 2708+ update with fastboot and and with recovery, and unless you aren't good at following directions chances are you won't brick your phone. But it is much harder to brick it with fastboot.
As for roms I only use recovery to flash because my hboot won't allow fastboot flash
Sent from my HTC Vision using xda premium
Yeah, you are right, AGAIN. My HBOOT is not compatible for fastboot and for others too.
I think fastboot is only good if you want to change Radio/SPL, for other stuff you just can use recovery. I just wanted to say that Fastboot is not so super awesome as other people think, and it's not the only way to go. You can't make any mistakes if you don't follow it. Plain and simple. It all comes to that, don't it?
Probably you should read a bit about the different kinds of SPLs around and their possibilities. Even the 0013d has fastboot capabilities, you can for example flash an .nbh with it, but that's not the main point.
The main reason why you shouldn't use recovery to flash radio/spl is *how* flashing is done by recovery: Flashing happens when re-booting your phone and a flag is set which says "reboot into recovery". This flag prevents the phone from accepting any other keys pressed, i.e. you are no longer able to press the home-button to go to recovery or the back-button to go to fastboot. If you are in this mode and for some reason (incompatible radio / spl / bad flash / ...) your recovery kernel cannot be startet you have a bricked phone. Using fastboot this cannot happen, because of that it's much more secure. That's the reason why everybody is telling not to flash radio/spl using recovery.
Now it's on you to choose.
AndDiSa said:
Probably you should read a bit about the different kinds of SPLs around and their possibilities. Even the 0013d has fastboot capabilities, you can for example flash an .nbh with it, but that's not the main point.
The main reason why you shouldn't use recovery to flash radio/spl is *how* flashing is done by recovery: Flashing happens when re-booting your phone and a flag is set which says "reboot into recovery". This flag prevents the phone from accepting any other keys pressed, i.e. you are no longer able to press the home-button to go to recovery or the back-button to go to fastboot. If you are in this mode and for some reason (incompatible radio / spl / bad flash / ...) your recovery kernel cannot be startet you have a bricked phone. Using fastboot this cannot happen, because of that it's much more secure. That's the reason why everybody is telling not to flash radio/spl using recovery.
Now it's on you to choose.
Click to expand...
Click to collapse
Yeah, but if you check everything and not be so dumb to flash it without knowing what it takes, you won't have any problems. Only for people who are new to this should flash with fastboot. But people who know what they are doing can flash with recovery and both options are still open.
TheShortybro said:
Yeah, but if you check everything and not be so dumb to flash it without knowing what it takes, you won't have any problems. Only for people who are new to this should flash with fastboot. But people who know what they are doing can flash with recovery and both options are still open.
Click to expand...
Click to collapse
If you want to flash those things through recovery do it! But you shouldn't recommend to people to do that, maybe you can be the cause of a brick
Enviado desde mi LG-E730 usando Tapatalk 2
I am not reccomending anything, just naming an option!