Related
Everything you ever needed to know about "unbricking" your Excalibur but were afraid to ask is in this guide. I've put together this guide for those of you who either intentionally or unintentionally "bricked" or think you've "bricked" your Excalibur.
It is not easy to brick an Excalibur if you actually read and follow all of the steps and guidelines before a flash. In fact, not many things can go wrong unless a USB cables disconnects during a flash, your PC crashes in the middle of a flash, or you flash a corrupt image file to your device. Statistically, most of the time people only think their Excalibur is "bricked" when actually it's not.
There are three methods you can use depending of the severity of the "bricking". The first method will unbrick 50% of all Excalibur's that have simply "locked up" and won't reboot properly. The second method will unbrick 95% of all Excalibur's that encountered flashing problems or flash failures. The third and final method, and the most involved, is a "last resort" for those who have tried method's one and two numerous times unsuccessfully.
** Please perform these steps and methods at your own risk. I am not responsible for any damage you cause your device using this guide.
If you're new to the Excalibur or SmartPhones in general, please take the time to read the WiKi and this post by Stylez for valuable info before you post or try any of these steps.
http://forum.xda-developers.com/showthread.php?t=397583
http://forum.xda-developers.com/showthread.php?t=537151
But, before I even get into unbricking, if your phone is in fact working right now, I highly recommend you flash HardSPL to avoid even having to follow these steps anytime in the future. The steps and info for HardSPL and JumpSPL can be found in this thread by jockyw2001:
http://forum.xda-developers.com/showthread.php?t=329605
HardSPL basically flashes your phone with an "unlocked" security partition so all security checks are bypassed when you try to flash a cooked ROM or a ROM designed for another variation of the Excalibur such as Dopod, HTC, TMO Dash, etc. Makes life much easier when trying different ROMS or cooking and testing your own! Thanks jockyw2001!!
Ok, so onto the fun stuff... Your phone won't boot... Either it's locked up and simply stopped booting or you flashed your phone and it won't boot. What do you do??
Method 1: Assuming you didn't get "bricked" from a flash problem, the first and easiest method for "unbricking" your Excalibur is (this will erase ALL data in your Excalibur):
(This method works for 50% of supposedly "bricked" Excaliburs)
Remove your SIM and SD card
Remove and reinsert your battery
While holding the two softkeys with your thumbs, press the power button
Continue holding the softkeys until a black screen appears saying "This operation will delete all your..."
Press "'send"' to restore to hard reset your phone
Let the phone cold boot and restore
That didn't work!! . This next method will reflash your phone to the factory ROM.
Method 2: Second way to the path of unbricking is:
(This method will unbrick 95% of all Excaliburs)
Get a hold of your Shipped ROM. You can find these ROMS either in Dopod's site, HTC's site (with a valid serial #), TMO's site (http://www.t-mobile.com/wmupgrade/ with a valid IMEI), or right here at XDA at this post (http://forum.xda-developers.com/showthread.php?t=381726)
Download one of these factory ROMS and unpack it. **Remember, if your phone is a TMO Dash, you MUST use a TMO Dash ROM. If your phone is HTC Branded, you MUST use an HTC ROM, etc., etc., etc...
Remove the SD card if one is inserted in the phone
Remove the battery from your phone for a few seconds. I found this step to be essential to reset the device. Put the battery back in.
While holding the camera button on the right side, press the power button. The phone will enter "bootloader" mode and you will see a tricolor bootscreen.
While in this mode, plug in your USB cable and you will hear the "ba-bing" USB sounds as the device connects
Unpack the ROM package you just downloaded and run RomUpdateUtility.exe. Follow the steps, check the appropriate boxes, and start the flash
Assuming all goes well, your phone will flash to the factory ROM and you can then troubleshoot what went wrong the first time that bricked your phone.
Oh no!! That still didn't work!? Or it worked but the flash failed with Error 270 or another error......... Never fear!! XDA-Developers is here! This next method is a bit more intense. It creates a "goldcard" which is used to SuperCID the Excalibur so that it doesn't care about what factory ROM you flash. Please have the factory (not a cooked) ROM ready to go.
** (This method is not intended for Newbie's and some enhanced knowledge of HTC devices and Windows is required to successfully work.)
** (Retry the second method several times with a few different factory ROMS before attemting the below)
Method 3: The third "goldcard" method is a bit more intensive and should be used as a "last resort" so follow closely:
(should unbrick ANY bricked Excalibur if performed correctly)
Get a cup of coffee or tea
You will need a working Donor HTC device with a microSD slot and a microSD card that is smaller than 1GB (will be formatted) to create "goldcard" image using QMAT tools as described below
You will need QMAT. Get it from http://revskills.de/index.html.
Go to the Download link and download the latest version and unpack QMAT
Have some coffee
Use a SD card reader (either USB for microSD adapter) in your PC to access the SD card through Windows. Format the SD card with FAT32.
* Insert the SD card into the donor HTC device and boot up the device. Connect the USB cable and establish an Activesync connection.
Open QMAT and go to the "Hardware Forensics" menu and select "Generate HTC Goldcard"
In "Select device key:" select the Excalibur
You will need the serial number fro the inserted SD card so click the "Get SD Card Serial from WINCE Device" button
Once the Serial number appears in the box, click the "Save Goldcard Image to WINCE SD" button below
If no errors pop up and all goes well, skip the next step
If you get an error or a popup saying "Goldcard for newer devices isn't implemented in newer devices", you must buy and register the software. Believe me, it's worth the small amount of $ you will spend to bring your expensive device back to life!
Now remove the SD card with the newly written Goldcard image from the Donor HTC device
Insert the SD card back into your PC using the microSD card reader adapter. Browse to the drive letter assigned to it. You will see no files on the SD card, this is normal.
(If, for some reason your PC sees the SD card as unformatted, something went wrong. Remove it and reinsert it into the Donor HTC device. The device should see the card as unformatted and ask you to format it, say yes. Now go back to the "* Insert the SD card into the donor HTC device" step above and repeat the steps)
Unpack your Dopod or other factory ROM and copy RUU_Signed.nbh to the SD card. Once it had finished copying, rename the file to EXCAIMG.nbh. Remove the SD card from the PC.
Make sure the Excalibur is off and insert the SD card
Enter bootloader mode as mentioned earlier (hold the camera button while pressing the power button). No need to connect the USB cable.
You will see a gray screen that says "loading". It will then find the EXCAIMG.nbh file and ask if you would like to start the update process. Follow the instructions and let the phone flash.
It will take 10-15 mins but your phone should boot fine and be back in action!
QMAT is a VERY powerful tool written by viperbjk that allows for full low level manipulation of HTC and WINCE tasks. Read all about it here http://revskills.de/index.html.
Many thanks to jockyw2001 for his amazing HTC device knowledge! Also thanks to all who contributed to this post.
Hope this tutorial helps!
Updates and more info will be here.
What if the phone will not enter bootloader mode?
ookba said:
Updates and more info will be here.
Click to expand...
Click to collapse
Hi OOkba,
This happened to a friend in the office's Dash. It simply froze up while operating. I actually got on the phone with HTC support. We couldn't get it to do anything. It does power up but then freezes.
The HTC guy was of the opinion that it is hardware related.
You ever solved that one?
BTW - I am running the 7.18 6.5 - love it - thank you so much
all steamed out said:
Hi OOkba,
This happened to a friend in the office's Dash. It simply froze up while operating. I actually got on the phone with HTC support. We couldn't get it to do anything. It does power up but then freezes.
The HTC guy was of the opinion that it is hardware related.
You ever solved that one?
BTW - I am running the 7.18 6.5 - love it - thank you so much
Click to expand...
Click to collapse
Thanks, glad you like it. Try this guide for your friend. Sounds like an easy fix unless it is indeed hardware related.
HI OOKBA. I can't find my shipped rom. I have a HTC Excalibur from Digitel, Venezuela. The serial number is SZ702FJ05879. I try all roms and not working. Please, help me. (sorry my bad english)
thank. I formated SD card and insert SD card in to my phone.But Do I need turn on my phone when connect with computer? because when I run QMAT software is error. " could not open connection? Device connected?". Help me. I need help from you
mydreamisrich said:
thank. I formated SD card and insert SD card in to my phone.But Do I need turn on my phone when connect with computer? because when I run QMAT software is error. " could not open connection? Device connected?". Help me. I need help from you
Click to expand...
Click to collapse
Yes, you have to have a spare working phone to create a "goldcard". The phone must be powered on and sync'd via USB so QMAT can access the storage card.
alfatech said:
HI OOKBA. I can't find my shipped rom. I have a HTC Excalibur from Digitel, Venezuela. The serial number is SZ702FJ05879. I try all roms and not working. Please, help me. (sorry my bad english)
Click to expand...
Click to collapse
English is good!! Who is your Carrier? Maybe your carrier has a ROM UPdate on their website? You should be able to use the TMO or Brightpoint ROM. You tried all the factory ROMS and they fail to flash?
ookba said:
Yes, you have to have a spare working phone to create a "goldcard". The phone must be powered on and sync'd via USB so QMAT can access the storage card.
Click to expand...
Click to collapse
I tried turn on my phone. And connect computer by USB but the same error. QMAT can't access the storage card. What does I do?
Sup ookba!
I really want to flash my TMobile Dash using your rom, looks pretty cool but I'm deadly afraid of bricking my phone so first, I took a look on my System Info and it says
ROM Version: 1.33.422.1 (tho its a TMobile Dash, I think the seller flashed it with this international rom).
Model Name: HTC S621
So I got 3 questions
1) Can i flash 3VO rom on this phone?
2) If the flashing fails, can i just use another 1.33.422.1 ROM and reflash it?
3) Will the flashing process (both ways) will bring the SIM Lock back?
Greetings from Brazil and sorry about my glass-cracking, horrible and ultra-bad english.
aletkd said:
Sup ookba!
I really want to flash my TMobile Dash using your rom, looks pretty cool but I'm deadly afraid of bricking my phone so first, I took a look on my System Info and it says
ROM Version: 1.33.422.1 (tho its a TMobile Dash, I think the seller flashed it with this international rom).
Model Name: HTC S621
So I got 3 questions
1) Can i flash 3VO rom on this phone?
2) If the flashing fails, can i just use another 1.33.422.1 ROM and reflash it?
3) Will the flashing process (both ways) will bring the SIM Lock back?
Greetings from Brazil and sorry about my glass-cracking, horrible and ultra-bad english.
Click to expand...
Click to collapse
Yes, your phone is fine. Make sure you follow all of the flashing instructions. Make sure you remove your SD card, connect your phone, run SDA Application Unlock, and run auto.bat from the update package.
mydreamisrich said:
I tried turn on my phone. And connect computer by USB but the same error. QMAT can't access the storage card. What does I do?
Click to expand...
Click to collapse
I dont know what you're doing wrong. Sounds like you're not establishing an Activesync connection properly.
Ok, Ookba. My carrier is DIGITEL and don't have support in the website. The phone comes originally with WM5 in spanish. I try all the factory roms and not working. Please, tell me if there is any solution or I forget the phone.
Thank you any help.
alfatech said:
Ok, Ookba. My carrier is DIGITEL and don't have support in the website. The phone comes originally with WM5 in spanish. I try all the factory roms and not working. Please, tell me if there is any solution or I forget the phone.
Thank you any help.
Click to expand...
Click to collapse
Try the "Goldcard"' method. This should SuperCID your phone and allow you to flash ANY shipped factory ROM. Please follow the tutorial closely. You will need a spare phone with a microSD slot.
Ok, Ookba. But the spare phone must be a same model than mine? (HTC S620)
alfatech said:
Ok, Ookba. But the spare phone must be a same model than mine? (HTC S620)
Click to expand...
Click to collapse
No, just has to Windows Mobile based and have a SDHC slot.
OK. I try with 3rd method and when run Qmat and select "Get SD Card serial from WINCE Device" appears the message "You need to set rigth registry permissions. See QMAT manual for more info." and not recognizes the sd card.
What is the problem?
Thanks, Ookba. You're great, man. Finally someone offers solutions to my problem. Thank you very much. My Phone came back to life again. I make a donation soon.
alfatech said:
Thanks, Ookba. You're great, man. Finally someone offers solutions to my problem. Thank you very much. My Phone came back to life again. I make a donation soon.
Click to expand...
Click to collapse
GREAT!!!!! Congratulations!
I tried but when I click Get SD Card Serial from WINCE Device in the box none found and click Save Goldcard Image to WINCE SD is card ID isn't 16 bit (32 charter) long. I isn't succesful. help me???????
Alright I'm finally going to throw a post up, go ahead and get all your "use search" "it's on search" "it was in a thread" out of the way now, cause I've gone through 76 thread pages of reading and searches and I can't find an answer that works.
I am continually getting the ERROR 262 in RUU everytime I attempt to use it to flash.
- I am running Vista 64bit (not sure if that is the problem or not)
- Using WMDC 6.1
- I have uninstalled and reinstalled WMDC 6.1 a total of 7 times
- I have used every single USB port on my computer.
- I have restarted a total of 15 times, both the computer and hard resets of the phone.
- I have tried both the Unlocker (I'm not sure if I have to unlock a second time or not after my WM 6.1 update) and just the ROM Update.
- I have tried doing the forced bootloader mode (Power+Camera+Reset) and simply allowing the program to do it on it's own.
Everytime it drops into Bootloader (3 color) mode, it drops Activesync and then obviously errors out because of lost connection. I've tried simply running the program and never unplugging the USB cable, I've also tried unplugging the USB cable when the DOSprompt part of the batch tells me to. Everything I've read says to do this, but I don't remember doing this for the 6.1 WM Update. It also doesn't make sense.... if you unplug the device, it's going to drop activesync everytime....
I've just updated every program, reinstalled everything more then 5 times, done countless resets, tried every USB plug and nothing is working. Hopefully this is something easy I'm just overlooking -- or something easy like "It doesn't work with Vista 64" so I can at least get an answer.
Again, I apologize if this was answered somewhere previously. I genuinely tried for 3 hours using search, on and off XDA, so that I wouldn't have to post a question thread but never found a "fix" that worked.
Thanks in advance.
Traumatique said:
Alright I'm finally going to throw a post up, go ahead and get all your "use search" "it's on search" "it was in a thread" out of the way now, cause I've gone through 76 thread pages of reading and searches and I can't find an answer that works.
I am continually getting the ERROR 262 in RUU everytime I attempt to use it to flash.
- I am running Vista 64bit (not sure if that is the problem or not)
- Using WMDC 6.1
- I have uninstalled and reinstalled WMDC 6.1 a total of 7 times
- I have used every single USB port on my computer.
- I have restarted a total of 15 times, both the computer and hard resets of the phone.
- I have tried both the Unlocker (I'm not sure if I have to unlock a second time or not after my WM 6.1 update) and just the ROM Update.
- I have tried doing the forced bootloader mode (Power+Camera+Reset) and simply allowing the program to do it on it's own.
Everytime it drops into Bootloader (3 color) mode, it drops Activesync and then obviously errors out because of lost connection. I've tried simply running the program and never unplugging the USB cable, I've also tried unplugging the USB cable when the DOSprompt part of the batch tells me to. Everything I've read says to do this, but I don't remember doing this for the 6.1 WM Update. It also doesn't make sense.... if you unplug the device, it's going to drop activesync everytime....
I've just updated every program, reinstalled everything more then 5 times, done countless resets, tried every USB plug and nothing is working. Hopefully this is something easy I'm just overlooking -- or something easy like "It doesn't work with Vista 64" so I can at least get an answer.
Again, I apologize if this was answered somewhere previously. I genuinely tried for 3 hours using search, on and off XDA, so that I wouldn't have to post a question thread but never found a "fix" that worked.
Thanks in advance.
Click to expand...
Click to collapse
Try another computer. It does work with Vista 64 (I've done it many times), but there's no point in beating your head against the wall for this. There are so many things that it could be you might as well try another computer so that you at least now it is the computer and not your Vogue.
-GT
You phone is not unlocked and you are trying to flash a custom ROM.
Try following the instructions in this thread found about halfway down the first page of the forum.
http://forum.xda-developers.com/showthread.php?t=508544
atoz350 said:
You phone is not unlocked and you are trying to flash a custom ROM.
Try following the instructions in this thread found about halfway down the first page of the forum.
http://forum.xda-developers.com/showthread.php?t=508544
Click to expand...
Click to collapse
Be it locked or unlocked is beside the point. As I stated before, I unlocked it once for the WM 6.1 upgrade and being as I wasn't sure if I had to do it again, I attempted to do it again.
Regardless of if it's trying to flash the ROM, or use the Unlocker, the same thing always happens. Windows Mobile Device Center (ActiveSync) drops connection once the phone goes to the Bootloader (3 color screen), and it errors out 262 (Connection Lost).
I have attempted to give as much information as possible so I can get input on if I'm missing a step or if it's simple bugging out. I will try what gt! suggested and attempt this on a different computer. However, from the information I've given can anyone confirm that I'm at least doing the correct steps -- there's just some gremlin popping up keeping me from completing it?
Thanks again.
Flash via SD card. There are instructions in CodyBear's FAQ thread.
From experience...use a blank or backed up card.
Traumatique said:
Be it locked or unlocked is beside the point. As I stated before, I unlocked it once for the WM 6.1 upgrade and being as I wasn't sure if I had to do it again, I attempted to do it again.
Regardless of if it's trying to flash the ROM, or use the Unlocker, the same thing always happens. Windows Mobile Device Center (ActiveSync) drops connection once the phone goes to the Bootloader (3 color screen), and it errors out 262 (Connection Lost).
I have attempted to give as much information as possible so I can get input on if I'm missing a step or if it's simple bugging out. I will try what gt! suggested and attempt this on a different computer. However, from the information I've given can anyone confirm that I'm at least doing the correct steps -- there's just some gremlin popping up keeping me from completing it?
Thanks again.
Click to expand...
Click to collapse
CONNECTION DROPS BUT............ it should be installing new drivers.
When i flash my phone on windows 7 it loses connection when it enter bootloader just like you.
And by the time the drivers for the qualcomm chip on my htc touch vogue gets installed (this is the recognized driver when your phone is in bootloader)
the RUU rom updater/installer times out.
After it times out for me i make sure that the driver for the qualcomm chip (the driver that is seen by windows when your phone is in bootloader) is installed, i run the updater again.
Now it should run through smoothly again.
Alternate method:
Flash by ur sd card.
or
Try a different computer.
start it up on serial mode then plug it in to USB, go to device manager make it search for new devices. Driver should start loading and start RRU, if all else fails use the SD CARD for The Flash
Alright, well now I guess a second question looms. I was going to take everyones advice and attempt to flash with the MicroSD Card, but now I'm having problems with that one as well.
Yes it has to be 2GB or less and formatted FAT32
I always find my original 512MB works perfect for flashing from
as to how to get it to your card...
Extract the ROM you want to use
Find the largest *.NBH file and copy it to your desktop
at the desktop rename it to VOGUIMG.NBH (I believe the caps in naming is important)
Copy that file to the root of your formatted FAT32 2GB or less SD Card
enter bootloader mode and it should go from there.
Click to expand...
Click to collapse
Those are the directions on the FAQ. I have the original 512mb card, formated to FAT32. I went into the Unlocker RAR, found the Voguimg2.nbh, renamed it to VOGUIMG.NBH as instructed in the FAQ. Placed the file on the freshly formatted MicroSD Card, put it in the phone and went to bootloader mode and... nothing.
I attempted putting the card in, then going to Bootloader. I tried going to bootloader, then putting in the card. I tried putting it from USB to Serial and vica versa. Tried hitting all the buttons. Nothing happens, it just hangs out on the 3 Color Screen.
Am I missing something, or am I just cursed to not flash my phone more then once? Heh. Thanks again for all the help.
[EDIT] For clarification, since I don't know if I have to unlock before every flash or not, I'm just attempting to unlock it again and hense only using the Unlocker ROM. It was previously flashed for the 6.1 update, but I figured it couldn't hurt to try the unlocker again so that's been the ROM I've been trying to run currently.
Traumatique said:
Alright, well now I guess a second question looms. I was going to take everyones advice and attempt to flash with the MicroSD Card, but now I'm having problems with that one as well.
Those are the directions on the FAQ. I have the original 512mb card, formated to FAT32. I went into the Unlocker RAR, found the Voguimg2.nbh, renamed it to VOGUIMG.NBH as instructed in the FAQ. Placed the file on the freshly formatted MicroSD Card, put it in the phone and went to bootloader mode and... nothing.
I attempted putting the card in, then going to Bootloader. I tried going to bootloader, then putting in the card. I tried putting it from USB to Serial and vica versa. Tried hitting all the buttons. Nothing happens, it just hangs out on the 3 Color Screen.
Am I missing something, or am I just cursed to not flash my phone more then once? Heh. Thanks again for all the help.
[EDIT] For clarification, since I don't know if I have to unlock before every flash or not, I'm just attempting to unlock it again and hense only using the Unlocker ROM. It was previously flashed for the 6.1 update, but I figured it couldn't hurt to try the unlocker again so that's been the ROM I've been trying to run currently.
Click to expand...
Click to collapse
As explained in Cody's FAQ, once your phone is unlocked to flash, it stays unlocked. The only thing you MIGHT want to do other than just flash the new ROM is to flash a stock ROM, then the new ROM.
Go ahead and try putting the VOGUIMG.NBH from the ROM on the card and see what happens. From what I remember, you should have the card in the phone then put it into boot mode. I believe that was what I did for my first flash ever.
What method did you follow when you flashed to 6.1? Has anything changed about what you are doing now?
Also it might be important to know that when flashing via USB on a 64-bit machine the RUU program will give you an error about not working on a 64-bit computer. Just ignore the error and click ok, it will pop up a few times just keep hitting ok and it will work. That error pops up even though it's false.
when i first tried flashing a custom rom, i extracted the downloaded file and when i clicked on the ruu i had the same error... i then tried just running the downloaded file without extraction and it worked fine.
same thing happend 2 me Just run the RUU do not extract files!!!!!!!((-;
Barogi44, JFive1182 -- You are both princes among men.
The Unlocker will only run on the first auto-extract of the file. You cannot run the batch from the extraction folder afterwards, eventhough all it does is auto-extract the contents and then auto-run the batch file.
Out of curiosity... and being infuriated I went and tested this again just to see. On 3 other computers the same thing happened. I have no clue why it would bug out that way... or if it was written that way that's a pretty bad design.
In any case, someone should put that in the FAQ. You have to let it start the process from the auto-decompressing RAR, you can't start it again after the fact by running the batch file from the extracted folder. If it said this anywhere, the 3 guides I read never mentioned that (nore the unlocker's thread at ppcgeeks) so I didn't catch it.
Thanks again for everyone's input, and obviously JFive1182 & Barogi44 for actually letting me know how to make it work!
your welcome
Traumatique said:
[..]The Unlocker will only run on the first auto-extract of the file.
[...]someone should put that in the FAQ. You have to let it start the process from the auto-decompressing RAR, you can't start it again after the fact by running the batch file from the extracted folder. If it said this anywhere, the 3 guides I read never mentioned that (nore the unlocker's thread at ppcgeeks) so I didn't catch it.[..]
Click to expand...
Click to collapse
Bump for emphasis. I had the same problem.
Tutorial said this: "Use WinRAR and extract both the files into separate folders,"
ONLY extract the NFSFAN rar.
I was un the middle of rooting my Droid inc. and I couldn't get the error message needed in my command prompt to install superuser. I tried this both with adb shell and loop.bat but I'm getting no luck. I need the error message to continue the rooting process. Does any one recommend an alternative method ?? I also herd you can swap SD cards or insert it during a certain time. Please pm me for any answers. Thanks !!!!
There are so many different methods, one might work everytime for one phone but never work on another phone, all u can do is keep trying each and every method till u get in. Sorry, I hope your able to crack it soon, good luck!
Sent from my ADR6300 using Tapatalk
Sticky thread "Unrevoked team: Incredible Root process" contains > 1100 replies about getting su on the incredible. Inserting the sd card that came with the phone just after hearing the usb connect sound worked for me.
Ok before anyone asks, Yes I did read the linux threads. Problem is my windows box no longer works. I had to take my slide back to stock before i carried it to tmobile. I had it rooted. Now I am trying to re-root it in ubuntu 10 and im not having any luck getting ADB to connect to the slide while in recovery. I am a complete newb to linux. I do have ADB working because I can adb to the device while it is booted into its normal state(OS loaded).
Was wondering if anybody can lend me a point in the right direction so to speak.
So ADB is working but only while booted into the normal OS.
Crap. Time to see if I can fix my winblows Box then!
Thank's
sultan.of.swing said:
Crap. Time to see if I can fix my winblows Box then!
Click to expand...
Click to collapse
You do realize that there are a lot of other distributions out there other than Ubuntu? Ubuntu is easy, yes, but almost too easy. You're not going to learn anything about Linux with that disguise around it. Besides, openSUSE 11.3 was just released and it has YaST: the best system configuration tool ever. It's almost as easy as Ubuntu. Try it out: http://software.opensuse.org/113/en.
More specifically though, I personally use openSUSE 11.3 and it plays nicely with ADB and rooting with the ADB race exploit (which, for the record, is what you're trying to do).
Ok say I install openSUSE 11.3. Will I have to do any hackery to get adb running? I'm not well trained on linux. But from last nights experience I know how to work with the terminal and nautilus
Sent from my T-Mobile myTouch 3G Slide using XDA App
sultan.of.swing said:
Ok say I install openSUSE 11.3. Will I have to do any hackery to get adb running? I'm not well trained on linux. But from last nights experience I know how to work with the terminal and nautilus
Click to expand...
Click to collapse
No, nothing other than what you did on Ubuntu. Just install ADB using the Android SDK from their website and plug in your phone to your computer. Done.
Also of note, when you install openSUSE it defaults to KDE as your desktop environment. If you want Gnome, select it during install. Nautilus isn't present in KDE, but it has Konqueror (which is arguably better). Personally I use KDE, but I have a bias towards it since I was a developer for it long ago. Flamewars rage, have raged, and will always continue to rage about what is better: KDE or Gnome. There's no clear answers, but most of KDE's recent bad publicity was due to its 4.0 and 4.1 releases. 4.2 is much better and it can be greatly appreciated.
That being said, you can use Nautilus in KDE if you want as well as Pidgin (Kopete is dieing and doesn't really work anymore).
nbetcher said:
No, nothing other than what you did on Ubuntu. Just install ADB using the Android SDK from their website and plug in your phone to your computer. Done.
Also of note, when you install openSUSE it defaults to KDE as your desktop environment. If you want Gnome, select it during install. Nautilus isn't present in KDE, but it has Konqueror (which is arguably better). Personally I use KDE, but I have a bias towards it since I was a developer for it long ago. Flamewars rage, have raged, and will always continue to rage about what is better: KDE or Gnome. There's no clear answers, but most of KDE's recent bad publicity was due to its 4.0 and 4.1 releases. 4.2 is much better and it can be greatly appreciated.
That being said, you can use Nautilus in KDE if you want as well as Pidgin (Kopete is dieing and doesn't really work anymore).
Click to expand...
Click to collapse
To get ADB installed and running on Ubuntu I had to follow the guide posted here on XDA which involved some editing here and there. If its the same in openSUSE then I should be able to get it running. Thank's for your help and I am going to probably go ahead and download and install openSUSE. I need to learn linux anyway.
EDIT- Whew, 4gb. Guess I will let this download tonight and come back tomorrow night and install and try it again.
sultan.of.swing said:
To get ADB installed and running on Ubuntu I had to follow the guide posted here on XDA which involved some editing here and there. If its the same in openSUSE then I should be able to get it running. Thank's for your help and I am going to probably go ahead and download and install openSUSE. I need to learn linux anyway.
EDIT- Whew, 4gb. Guess I will let this download tonight and come back tomorrow night and install and try it again.
Click to expand...
Click to collapse
Strange, the SDK worked out-of-the-box for me on openSUSE 11.3 - no editing of anything required.
And yeah, it's 4GB - that is the entire repository. Ubuntu gives you a smaller CD (as opposed to a DVD) then allows you to download anything else you want later. Personally I prefer the DVD, but I also have a 20mbit connection.
nbetcher said:
Strange, the SDK worked out-of-the-box for me on openSUSE 11.3 - no editing of anything required.
And yeah, it's 4GB - that is the entire repository. Ubuntu gives you a smaller CD (as opposed to a DVD) then allows you to download anything else you want later. Personally I prefer the DVD, but I also have a 20mbit connection.
Click to expand...
Click to collapse
Well hopefully I wont have to do any editing to get it to work either.
It's downloading at 400kb/s about 3 hours to download so it aint gonna take that long.
Thank's for your help. If I didn't have work tomorrow I would be up late setting all this up because my slide without root just plain suck's. LOL
sultan.of.swing said:
Well hopefully I wont have to do any editing to get it to work either.
It's downloading at 400kb/s about 3 hours to download so it aint gonna take that long.
Thank's for your help. If I didn't have work tomorrow I would be up late setting all this up because my slide without root just plain suck's. LOL
Click to expand...
Click to collapse
i hear ya. I'll be on late tomorrow on IRC (irc.fredenode.net #teamslide) and i can help you with anything Linux related.
nbetcher said:
i hear ya. I'll be on late tomorrow on IRC (irc.fredenode.net #teamslide) and i can help you with anything Linux related.
Click to expand...
Click to collapse
Awesome. I'm gonna try to do everything by myself and if all that fails then I'm sure I will need some help. I hate having to ask for help. I usually search and find the answers I am looking for so hopefully that will be the case once all this is up and running.
P.S.-- If the Mod's would like to move this thread to the Q&A/General section then feel free. I only posted it here because no one ever seems to look at the linux thread over in Q&A.
Well I'm sitting here trying to install openSUSE and its not working. It goes though all its checks at the beginning and then just goes to a black screen and stays there.
Sent from my T-Mobile myTouch 3G Slide using XDA App
sultan.of.swing said:
Well I'm sitting here trying to install openSUSE and its not working. It goes though all its checks at the beginning and then just goes to a black screen and stays there.
Click to expand...
Click to collapse
It sounds like it's an X display issue which is surprising in all honesty. What kind of computer do you have? If it's a custom built what is the video card (or if you know the video card and it is a pre-built)?
nbetcher said:
It sounds like it's an X display issue which is surprising in all honesty. What kind of computer do you have? If it's a custom built what is the video card (or if you know the video card and it is a pre-built)?
Click to expand...
Click to collapse
Its an older prebuilt hewlett crappard. I got out of building custom computers a while ago.
Anyway I got installing now using text mode. Its at 83 percent right now. Will see what happens.
Ok wtf. It finished installing, then rebooted and says something about hard disk not found or something.
Sent from my T-Mobile myTouch 3G Slide using XDA App
sultan.of.swing said:
Ok wtf. It finished installing, then rebooted and says something about hard disk not found or something.
Click to expand...
Click to collapse
Do you have two hard drives? Like, one Windows and one Linux? Also, check your boot order in your BIOS (especially if you have two hard drives).
nbetcher said:
Do you have two hard drives? Like, one Windows and one Linux? Also, check your boot order in your BIOS (especially if you have two hard drives).
Click to expand...
Click to collapse
Nope just one drive and I set it up as the first boot device. Guess its time to see if I can find my windows disk.
Sent from my T-Mobile myTouch 3G Slide using XDA App
sultan.of.swing said:
Nope just one drive and I set it up as the first boot device. Guess its time to see if I can find my windows disk.
Click to expand...
Click to collapse
*shrug* I won't stop you from running Windows if you want.
Sometimes certain drivers can interfere with the proper tagging of the drives - most of the has been eliminated which is why I'm surprised to see that issue at all anymore. What I would try first though is making sure that you're NOT booting from the openSUSE DVD when you reboot after that install. Remove the DVD, then boot from your hard drive directly.
If that doesn't fix it then if you're interested you can do this:
Boot into 'Rescue' from the DVD.
Once loaded and at login type 'root' (it won't ask for a password).
Type 'dmesg |more' and look for your hard drive (press 'Space' to go down one-by-one page - it will take a few pages before you get to what you're looking for) immediately followed by something like "sda sda1 sda2 sda3". (The 'a' may be different for you and THAT is what we're looking for).
Once you have that changed letter (e.g. instead of 'sda' you have 'sdb' or 'sdc') type: 'fdisk /dev/sdX' where 'X' is the changed letter.
Then look for the first line that says 'Linux' to the right of it - it will most likely be THE first line. Make note of that number next to '/dev/sdXN' (where 'N' is the number).
Reboot (you can hard reset if you want) and make sure your openSUSE DVD isn't in the drive. Once the boot menu comes up press ESC, then Enter.
In that menu press 'e', then change where it says change 'root=/dev/blahblahblah' to 'root=/dev/sdXN' (where X and N are what you recorded earlier).
Press 'Enter' then 'b'
See if that works.
Otherwise, enjoy the next several hours of installing Windows, Windows patches, applications, and configuration of everything.
EDIT: keep in mind that all of those instructions are from memory, so YMMV
EDIT2: Eh, I had the dmesg grep wrong. Updated to make it a bit more painful, but actually work
An example of the lines in the dmesg you're looking for is something like:
[ 2.640793] scsi 3:0:0:0: Direct-Access ATA HDS728080PLAT20 PF2O PQ: 0 ANSI: 5
[ 2.641334] sd 3:0:0:0: [sdb] 160836480 512-byte logical blocks: (82.3 GB/76.6 GiB)
[ 2.641459] sd 3:0:0:0: [sdb] Write Protect is off
[ 2.641465] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 2.641523] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or F
UA
[ 2.641901] sdb: sdb1 sdb2 sdb3
I'm trying a different install this time. Set up the formatting to see if it will make a difference. If not I will try your method. I was booting without the dvd in the drive as well. I booted into recovery before and tried a bunch of different passwords and what not and decided to try root and that brought up a bunch of stuff I couldn't comprehend. now I know. Lol
Let's see what doesn't happen!
Sent from my T-Mobile myTouch 3G Slide using XDA App
Well it got farther this time. Now its at the yast2 installation screen. Getting somewhere now.
Got a green from now! And bam I'm on the desktop!!!!
NICE!
Ok how the F do I get my internet working? I went through the network settings but it still don't work
Sent from my T-Mobile myTouch 3G Slide using XDA App
razr315 said:
I completed the installation, but of course my wireless card isnt working. Normally on ubuntu it has an option to enable them. I cant seem to find it in Suse.
Click to expand...
Click to collapse
Same here can't seem to get my internet working. With ubuntu it worked automagically. I'm wired too
Sent from my T-Mobile myTouch 3G Slide using XDA App
razr315 said:
Im wired and on the net now. I just cant be wired up on my laptop the whole time. Id much rather get wireless working.
Click to expand...
Click to collapse
How did u get your wired connection working if u don't mind me asking
Sent from my T-Mobile myTouch 3G Slide using XDA App
Hi guys and girls.
New to XDA but not to Android.
I need some help big time as I'm totally stuck and I'm about to send my phone to "will it blend".
Long story short my memory card will not read when inside the phone all I get under phone storage is "unavailable" with mount being greyed out.
HTC DESIRE HD 2.3.3 (Not Rooted)
Things I have tried:
Factory reset soft/hard both through phone and through power + vol down.
Tried two different mem cards both coming up in storage as "unavailable" the general fix seems to be formatting in fat32 on desktop pc I have done that for both cards (which are both readable on PC) and have even tried formatting through command prompt still no luck.
read alot in ADB/fastboot as it is something I'm abit unfamiliar with saw that users where able to restore sd card function by installing adb then running command prompt: "fastboot oem enableqxdm 0" I get a message saying it was successful I reboot guess what...same problem. One thing I have noticed is if I type "adb shell" I get "Daemon started on port 5079". (I have enable debugging) followed by device not found. have tried two diff usb cables both work with my S2 on either media faceplate or backplate usb ports still no luck. Trust me on this one guys I have searched far and wide and I'm just about read to quit on this. I'm at a dead end any advice would be awesome.
I've tried to resolve the adb method by installing various drivers (running windows 7pro 64bit) the issue I seem to get is that windows doesnt like the drivers Im trying to assign so im forced into have to update them manually through "let me choose a driver from location" blah blah blah...
There is a system update available which may possibly fix my issue however suprise suprise I can't download the update without having an sd card. I have even tried downloading a HTC sdmount widget whether Im downloading the wrong one I dont know? I have got HTC sync installed as others claimed this helped windows detect the correct drivers but then technically speaking its not an ADB interface?? just like to point out that both of the sd cards work flawlessly in my s2. anyone who can help me will get paypal'd a beer!
Thanks
Seb.
OK, I had same problem with my Desire S. I'm running Win7 64bit as well. I un-installed HTC sync, including the drivers. Control Panel>Programs & Features. I then download the latest HTC sync. Went back to Programs & Features and un-installed HTC sync but, left the drivers. Rebooted PC and Win7 picked up Desire S.
Hope this helps
How old is your phone? Depending in which country you are in you may still be under warranty.
Try cleaning the contacts?
Not too sure if you can mount the sd card on phones that are not rooted, or if you have the hboot option/recovery. Fastboot turned off, phone off, then press and hold the down volume button and while pressing it down, press the power button.
If you are not sure what you are looking at do not play around with those options, and it may not work. Not sure if you get those options if you are not rooted.
Do not root your phone, it is improbable it will help, and chances are, it may cause more problems than help.
First option, find out about the warranty.
Edit: just noticed you can boot into hboot. Not too sure if you have the option for recovery and even less if you get the option to mount sd card through there.
2nd edit: I'm not responsible for bad advice. I still haven't had my second cup of coffee
3rd edit: to find out if the adb is working properly and you got the htc sync installed type in whatever the command is in adb to see if it detects your device.
However, try cleaning the contacts and find out about the warranty.
Sent from a dream.
eloquence intshe
Thanks for the reply.
Hehe dont worry you can have some of mine I'm on the 4th cup thats how stressed I am getting with this. Just trying Taysider's method for trying to re-enable the sd card function. I have disabled fastboot using your method so is there a way of mouting sd in recovery? because Im sure I may have tried that already and all I got was an icon of a phone with a red exclamation mark infront of it?
thanks
3rd edit: to find out if the adb is working properly and you got the htc sync installed type in whatever the command is in adb to see if it detects your device.
However, try cleaning the contacts and find out about the warranty.
Sent from a dream.[/QUOTE]
How do I clean the contacts on the sd reader? it doesnt look very accessible unless I remove part of the housing? also what command prompt do you recommend I try first? like I said I tried "adb shell" and got no device found I'll update in a second as soon as I have tried this I have just uninstalled htc sync now all I need to do is assign driver to "android 1.0" in device manager then I'll take it for a spin.
Thanks dude
Ironman MarkV said:
Thanks for the reply.
Hehe dont worry you can have some of mine I'm on the 4th cup thats how stressed I am getting with this. Just trying Taysider's method for trying to re-enable the sd card function. I have disabled fastboot using your method so is there a way of mouting sd in recovery? because Im sure I may have tried that already and all I got was an icon of a phone with a red exclamation mark infront of it?
thanks
Click to expand...
Click to collapse
Re-read my previous post, there' another edit.
Thing is, Im not too sure what options you get nor l, well, anything related to non rooted phones. Do not root your phone as I mentioned previously. Mainly because first you ought to find out if you are still under warranty. If you are, send it to them.
Exclamation mark? Do a search, there were a few threads talking about that a few weeks back, but I believe it was about something else entirely, people effen up their phones trying to root.
From here on, the best advice I can give you is step back, take a break, continue later. There is probably too much info in your head right now.
1- see if adb can detect your phone.
2- try cleaning the contacts, do a search cause I can't remember if the cleaning of contacts was also for the sd card or only the wifi antenna.
3- Check your warranty, I can't stress this enough.
4- Coffee is kicking in
5- Check if you can detect the sd card through recovery. My assumption is that recovery works something like safe mode in windows, only an assumption.
6- Wait till someone more knowledgable than myself joins in. Chances are it would either be darunion, gleviatan or some chap who's nick I cant remember but starts with an M.
@guyinthecorner: you can skip this one - and I'm still waiting for that flashable zip.
Sent from a dream.
Teichopsia said:
Re-read my previous post, there' another edit.
Thing is, Im not too sure what options you get nor l, well, anything related to non rooted phones. Do not root your phone as I mentioned previously. Mainly because first you ought to find out if you are still under warranty. If you are, send it to them.
Exclamation mark? Do a search, there were a few threads talking about that a few weeks back, but I believe it was about something else entirely, people effen up their phones trying to root.
From here on, the best advice I can give you is step back, take a break, continue later. There is probably too much info in your head right now.
1- see if adb can detect your phone.
2- try cleaning the contacts, do a search cause I can't remember if the cleaning of contacts was also for the sd card or only the wifi antenna.
3- Check your warranty, I can't stress this enough.
4- Coffee is kicking in
5- Check if you can detect the sd card through recovery. My assumption is that recovery works something like safe mode in windows, only an assumption.
6- Wait till someone more knowledgable than myself joins in. Chances are it would either be darunion, gleviatan or some chap who's nick I cant remember but starts with an M.
@guyinthecorner: you can skip this one - and I'm still waiting for that flashable zip.
Sent from a dream.
Click to expand...
Click to collapse
Lol, already saw your username and was like 'Yup, problem solved ;-)'
Flashable zip is being a pain in the rear, should have it soon (reading a crap-ton of tutorials to help me)
Sent from my Desire HD using Swype beta for Android!