First, my palm 750 was having the problem that it got stuck like always, and when it finally started working, i had no signal at all, radio on, turned off and back on, hard reset, soft reset, nothing. So then I saw that there was WM6 and upgrading sounded like a good idea. Started looking for the rom and i found the voda WM6 rom, followed the instructions and when it was upgrading the battery felt cuz I didn't put back the cover (my bad). After that, I tried to turn on the fone and all I got is the Bootloader screen, have read a lot and all the answers are to format the card to fat32, or to switch computers, I've used like 3 different cards, checked on 3 pc's, used another card reader and all I got is the boot screen, if I put the card in it says loading, press the end call botton, start updating and then got stuck after splash1 and bootloader says ok. What I'm wondering is if the it is a hardware problem was before the update I had no signal, and now it got stuck on the gsm part of the update. Any Ideas?? this is a really expensive paperweight!!!!!
A couple thoughts...first, when it gets to the GSM portion of the flash it takes significantly longer than the others, so you might just need to be a bit more patient. Run it again and leave it alone for 10 minutes.
If you can get to the bootloader screen, your device is not bricked. You didn't mention what carrier your device is from..is it a Vodafone device? If so, you might be able to just connect the device to your PC while it's in bootloader mode and run the full Vodafone updater on your PC. There's a chance that this method might not work if a partial flash has left your device in a state that the PC based updater can't identify.
pirulino23 said:
First, my palm 750 was having the problem that it got stuck like always, and when it finally started working, i had no signal at all, radio on, turned off and back on, hard reset, soft reset, nothing. So then I saw that there was WM6 and upgrading sounded like a good idea. Started looking for the rom and i found the voda WM6 rom, followed the instructions and when it was upgrading the battery felt cuz I didn't put back the cover (my bad). After that, I tried to turn on the fone and all I got is the Bootloader screen, have read a lot and all the answers are to format the card to fat32, or to switch computers, I've used like 3 different cards, checked on 3 pc's, used another card reader and all I got is the boot screen, if I put the card in it says loading, press the end call botton, start updating and then got stuck after splash1 and bootloader says ok. What I'm wondering is if the it is a hardware problem was before the update I had no signal, and now it got stuck on the gsm part of the update. Any Ideas?? this is a really expensive paperweight!!!!!
Click to expand...
Click to collapse
Thanks, and well it is a Cingular Treo, and I left the updater running several times for more than 3, 4 hours until the battery run out, and well, keep being stuck at gsm part, tried the tool that is on the update but after some % it got disconnected, any ideas???
im no expert. but if your using it with cingular (att) and you used a voda rom, i dont know how it would work in the first place without some sort of cid unlock? correct me if im wrong.
anyway. I would try that leaked att rom it it were me.
kapster said:
im no expert. but if your using it with cingular (att) and you used a voda rom, i dont know how it would work in the first place without some sort of cid unlock? correct me if im wrong.
anyway. I would try that leaked att rom it it were me.
Click to expand...
Click to collapse
Well First never do a rom update off the battery second I have a att/Cingular 750 had leaked att on it ran fine then moved to the voda rom still fine
If the ATT rom doesnt work search for a WM5 Rom I think someone said it was posted in here. If that doesnt work, the first rom update I screwed up killed my device I called ATT said I tried to install the audio update and it killed my device they sent a new one and then i up'ed the ATT rom GL.
mtty perhaps?
I unbranded my Focus and did the no-do patch a month ago then rebranded it to ATT-US but now zune doesn't tell me that there's an update though I haven't received the Focus Firmware.
I've been searching this forum and didn't find an answer so I'm just making sure I haven't found a way around it and will have to restore my phone.
Are you sure you're rebranded to ATT-US ?
Sent from my SGH-i917 using XDA Windows Phone 7 App
Rebrand it and Zune will notice you.
how do you rebrand it?
I would like to know this as well. I can't run samsungregistry to re-brand the phone. am I forced to do a phone reset?
How did you unbrand it?
Sent from my SGH-i917 using XDA Windows Phone 7 App
I'm very sure I rebranded it for sure. I don't think there is a way to run the registry.xap after nodo is there?
albertleao said:
I'm very sure I rebranded it for sure. I don't think there is a way to run the registry.xap after nodo is there?
Click to expand...
Click to collapse
You can still side-load .xaps (like the registry editor) as long as your device is still dev. unlocked. IF, however, you lost your unlock there isn't a way to "jailbreak" NoDo with the Chevron tool.
One option is to use Zune on your PC to roll back the firmware using the backup Zune created during your first NoDo update. This version (maybe .7004??) will be unlockable with Chevron. Doing this will revert your phone back to the state at the time of the first update (you'll loose new app data, personal data, and have to redownload new apps.)
Once you're dev. unlocked you will be able to go through the update process to NoDo without losing the unlock. So you will have a dev unlocked NoDo. This process will probably restore the ATT-US branding, but now with an unlocked device you can brand it to whatever you want!
I'm sure the update is being released in waves so be patient. I have a device that already had NoDo on it and I received the samsung update immediately, but my buddy with a stock 7004 version still hasn't received the update yet.
Getting error C1010007 ever since my first attempt to upgrade. I got the notification on 4/19 and have tried several times, on 2 different laptops, and it gets to step 7 of 10 of the process and got to 68% the first 4 times, then 72% one time, then 55% the last time before it drops the connection with my phone and stops and throws the error.
I've deleted EVERYTHING on the phone ... music, pics, apps ... and same thing. I've used various USB cables including the original, and no success. About the only thing left is to hard reset and I REALLY hate to do that because most people aren't having issues.
I am really not liking this at all!
If you already deleted everything, What's the hurt to do a hardreset? In fact, a lot ppl spent days even weeks try to get the update working (on a Samsung phone) and still ended up with a hard reset and solves the problem. Re-setting up your phone probably won't take days you spent on experimenting already.
Just wondering if anyone has had this problem. I've resetted the phone and still cant get it to update
The only Focus that hasn't received NoDo update is hardware rev 1.4. AT&T is still testing the new firmware that will work with rev 1.4 hardware.
To check your rev number, power down and take the battery out. It is printed on the label underneath the battery.
Most of us are on older rev 1.3 hardware.
Im on rev 1.3, no firmware update though I'm running the latest software update...
no luck here either
Lol I didn't check update b4 I posted, this was for nodo
I just got the Captivate about a month ago. Had a regular phone for about a year, touch screen went out, bought a replacement digitizer but knew it was a temporary fix anyway and wanted a new phone. Convinced the maternal unit to use her contract extension to get me a new phone, and snagged the Captivate for $30 from RadioShack. My first Android phone, and I have to say I'm horribly disappointed, but I guess I'm doing something wrong here.
First two or three weeks, my mom had the phone and got to play around with it for a while. Wasn't until the 29th that I got the phone, and I just played around with it for a week and got all the apps I deemed useful and worthwhile. Eventually realized I couldn't use Flash in the browser, nor Skype, etc., without upgrading to 2.2.
So, I went through the tutorial Samsung provided, watched videos on Youtube just to be sure, but followed everything Samsung's tutorial said word for word. ... only for my phone to end up completely screwed up. Gallery, Browser, Music Player, Video Player, and many other default applications were missing. Now I'm smart enough with technology to think, okay, something's wrong. I knew about the factory reset, so I went to go to settings to do that, and realized. ... oh wait, the Settings menu is also missing. Wonderful. There was no "Settings" button in the Applications list, and if I tried getting to it from the menu button, it simply did nothing at all.
Found Odin, flashed back to 2.1, and then factory reset and got rid of every application I had and etc., so that absolutely nothing was on it, basically a stock phone. Tried upgrading again fresh, still following the instructions very closely. Same problem occurred, and I was pissed. Gave up on 2.2, tried flashing back to 2.1 /again/ with Odin, only for my phone to decide it didn't want to enter download mode anymore. Forced it using 'adb reboot download', but alas, it locked up in the middle of flashing back to 2.1 and wouldn't do anything. I waited about 30 minutes to see if it'd resume the flashing process at all, but nothing, so I regrettably had to disconnect the USB cable and hard brick the phone (wouldn't turn on or anything).
Still under warranty, so I replaced it from RadioShack, and now have a new Captivate. Went ahead and installed all the applications I needed, used the Sideload Wonder Machine to install a few third-party applications, had no problem doing that for a while. Didn't bother attempting to upgrade. However, my computer got a trojan and deleted the MBR. Repaired using the XP boot disc, but it meant I was back on SP2. After installing every last one of the damn updates all over again, I decided to check up on some new applications to install via sideloading.
Hooked up my phone, it detected all the new hardware again since the drivers seemingly were also lost amongst everything else during the repair, only for it to encounter an error on the "Samsung Android Composite ADB Interface". So, I uninstalled the drivers, tried installing them manually. Hooked up the phone, but it still wanted to try to install that one driver and failed. I've restarted my computer, uninstalled the drivers, attempted manually installing them through device manager, you name it. Still can't get it to work -- it keeps having a fatal error every time. However, it's only when my phone has USB Debugging on. Installs every single driver perfectly fine when it's off, in MTP/Mass Storage/Kies mode. Just has a "fatal error" in USB Debugging on that one driver.
tl;dr, the drivers are broken on my computer and I can't fix them despite actually /not/ being computer illiterate. And, I kind of still want 2.2, but apparently the stock 2.2 update is a pain in the rear end and I no longer have a warranty through RadioShack now, so I can't risk bricking my phone due to a faulty update process. Any suggestions?
err, the only thing you should have needed to do was install the latest version of Kies, plugged the phone in, it would have prompted you to do the update. It's quite painless..
Edit: Sorry irrelevant
sw411 said:
err, the only thing you should have needed to do was install the latest version of Kies, plugged the phone in, it would have prompted you to do the update. It's quite painless..
Click to expand...
Click to collapse
At the time I tried, Kies itself didn't support the Captivate. Only Kies mini. And in order to do that upgrade, I had to install the drivers, then put the phone into download mode to install more drivers for some odd reason, restart the phone (taking out the battery and putting it back in), then hook it up. Kies mini wouldn't detect the phone for several tries at first, finally got it about the 10th time in. Then go to the "Upgrade phone" link, and yeah. I followed the instructions from Samsung's official SGH-i897 Froyo upgrade guide.
I did EXACTLY as the instructions say, down to the wire. Still ended up both times with all those applications missing and the settings panel missing, unable to do a factory reset without flashing back to 2.1 first.
Install z4root and root phone
Install rom manager
Flash clockwordmod recovery from rom manager
Choose a 2.2 rom from the forums
Download and copy to SD card
Install via rom manager
????????
Profit
Hope this helps. Btw I reccomend firefly or serendipity for the rom
Sent from my Captivate running CyanogenMod7 using XDA Premium App
brendanmurphy said:
Install z4root and root phone
Install rom manager
Flash clockwordmod recovery from rom manager
Choose a 2.2 rom from the forums
Download and copy to SD card
Install via rom manager
????????
Profit
Hope this helps. Btw I reccomend firefly or serendipity for the rom
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
Only downside to rooting the phone is the voided warranty. I don't entirely know what I'm doing there when it comes to flashing, and if I manage to do something wrong and brick the phone again, I'm completely wiped. I don't have the money to replace the phone at all. I have no job. ._. Only reason I got the phone was because I managed to get some spare money fixing up a friend's computer, and the maternal unit's contract extension was available. I'm not paying for the phone, still my parents. Damn economy in this state is so broken, and I'm screwed over worse since I have no diploma.
However, I was looking into info on the roms, and while I was tempted to try out CM7 for the fact it was 2.3, I actually considered getting Paragon RC6 from what I had read. Just decided not to because I can't replace the phone if I screwed up. In the slim chance I do opt to risk not having a phone at all if I do something wrong, would you say Paragon's worthwhile or would it be better to go with Serendipity? I do like TouchWiz, and Wifi access is a must (200 MB plan isn't going to cover it with how I use data; I'm frequently using Wifi in as many places as is possible), but I'm pretty sure both of those are fine there. Just not really sure which would be better overall, performance-wise.
I can't do either of them right now anyway until I figure out why the drivers aren't installing. So that's my first issue.
Don't worry about bricking I almost guarantee you will brick your phone once. But that is what Odin is for and it's almost impossible to hard brick a phone these days. Just install paragon with the instructions I gave its really fool proof these days to install rom. You will learn by trying if you mess up so be it that's what xda is here for to help.
Drop me a pm anytime if you need help
Sent from my Captivate running CyanogenMod7 using XDA Premium App
brendanmurphy said:
Don't worry about bricking I almost guarantee you will brick your phone once. But that is what Odin is for and it's almost impossible to hard brick a phone these days. Just install paragon with the instructions I gave its really fool proof these days to install rom. You will learn by trying if you mess up so be it that's what xda is here for to help.
Drop me a pm anytime if you need help
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
Well. Despite it being almost impossible, I've managed it once already within the first month of having one. Kind of why I'm a bit skittish about actually going through with it. I'm definitely all about modding and customizing things to your liking, but not having the funds to fall back on if I /do/ screw up bigtime again, yeeeeah.
After looking at Firefly and Serendipity thoroughly, though, I'm impressed. It's a tough choice between the three (Paragon, Serendipity, and Firefly). I'm leaning towards Serendipity now though after watching a video just to see the interface. Kinda not a huge fan of the GB launcher -- I liked the side-scrolling app launcher more, honestly -- but that's not a big deal.
So, let's see if I've got the details down right before I try anything. Search z4root in Market, install. Subsequently get Rom Manager, install it. Flash ClockworkMod (via Rom Manager). Pick a 2.2 rom (which will be a tough choice), and download it to my microSD card to put in the phone. Install said rom (via Rom Manager). And then, voila, it's done.
Did I miss anything, or am I actually following instructions right here?
Edit: Nope, can't find z4root in the Market anyways. Means I'd have to Sideload it, and until I get this driver issue solved, that's not gonna work either. That's gonna be the first thing necessary to fix since it also means I can't use Odin if I do anything wrong... Downloading Serendipity now though, so if I can get that fixed, I may go ahead and try this out after I get some sleep. But since I'm nocturnal, time for some rest. Hoping for some tips or pointers when I get back on. Definitely looking forward to good experiences with XDA and my Android phone.
Yea those are the exact steps its really simple. http://forum.xda-developers.com/showthread.php?t=944418 try this it will install drivers for you ans sideload apps. This is a useful tool
Sent from my Captivate running CyanogenMod7 using XDA Premium App
The.Se7enth said:
Only downside to rooting the phone is the voided warranty.
Click to expand...
Click to collapse
Quick question. Did you purchase the insurance through AT&T for the phone? If so, you will most likely always be able to get it replaced even if it's been rooted. It's just as simple as calling the help line, and saying that you have no idea what happened, and it won't work now. Of course that is worst case scenario
From my experience, the Captivate is a pretty difficult phone to hard brick compared to some others. For a beginner, all of this can be somewhat overwhelming, we've all been there. But once you get the hang of the whole process, you'll be good to go!
Yeah I've done that once already. Just called in and told them that it seems like a software problem and they replaced it no charge.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Beginner help....
AT&T warranty is for 1 year on new phones, 90 days on phones you purchase as refurbished. (30 day "I just don't like THIS phone" replacement/return in both cases.) If Radio Shack will not replace the phone, AT&T should swap. If neither is willing to help, Samsung will honor their 1 year warranty, but it requires shipping back to Samsung.
Your situation sounds like your Windows PC is the problem. A complete reinstall of Windows & apps (not just a quick MBR repair / install over top of existing stuff) may be your best bet if you can't use a different machine.
Kies Mini should upgrade your phone to 2.2 painlessly - without you having to do anything but plug it in and click the on screen button.
Also if you root and need to return it just flash back to stock which will take away root and at$t is none the wiser, most likely
peypey008 said:
Quick question. Did you purchase the insurance through AT&T for the phone? If so, you will most likely always be able to get it replaced even if it's been rooted. It's just as simple as calling the help line, and saying that you have no idea what happened, and it won't work now. Of course that is worst case scenario
From my experience, the Captivate is a pretty difficult phone to hard brick compared to some others. For a beginner, all of this can be somewhat overwhelming, we've all been there. But once you get the hang of the whole process, you'll be good to go!
Click to expand...
Click to collapse
Nope. Don't feel their insurance policies are worth it. You spend more money on the insurance policy in total, even if it's month-to-month, than you would on a brand new contractless phone. Besides, I had only made $120 from fixing up three ancient computers (so ancient they actually had ISA slots and DIMM SD-RAM memory -- one was even a Pentium II), and only had $50 by the time I bought the phone which was a couple months later. My $50 went towards the phone and a pack of screen protectors, while my mom covered the upgrade fee. Couldn't afford the insurance policy even if we wanted to.
But I do greatly appreciate the encouragement. I'll give it a go in a bit, and try out flashing Serendipity. I'll follow the official instructions from their own website though, because I read this on their FAQ:
"Never use ROM Manager. EVER, EVER, EVER, EVER, EVER!"
pouelle said:
AT&T warranty is for 1 year on new phones, 90 days on phones you purchase as refurbished. (30 day "I just don't like THIS phone" replacement/return in both cases.) If Radio Shack will not replace the phone, AT&T should swap. If neither is willing to help, Samsung will honor their 1 year warranty, but it requires shipping back to Samsung.
Your situation sounds like your Windows PC is the problem. A complete reinstall of Windows & apps (not just a quick MBR repair / install over top of existing stuff) may be your best bet if you can't use a different machine.
Kies Mini should upgrade your phone to 2.2 painlessly - without you having to do anything but plug it in and click the on screen button.
Click to expand...
Click to collapse
RadioShack replaced the phone the first time, but the manager there said after replacing it once, the warranty was thus void. I'm not sure if profanity is allowed here, but you can figure out which word I wanted to reply to him. It's eight letters long, starts with bull.
I've read posts on AT&T forums saying if the phone's bricked or can't be repaired by user methods though, especially if it's rooted, that they won't honor the warranty at all and will consider it user error and that you're out of luck. Even people who tried to upgrade to 2.2 stock had issues with that. But I dunno.
Anyways, my machine works perfectly for everything else. Before the repair, when I tried to upgrade? It was a fresh install. I had just reformatted it because it was performing sluggish before and I decided I wanted a single-boot installation instead of having my old dual-boot of Windows 7 and XP. It's now just XP for the time being, seeing as how the hardware's limited and I want to get the best out of it for gaming (I can run 7 with ease, but it uses more resources than XP, thus games don't run as well).
I realize earlier I may have come off as implying the upgrade to 2.2 process was difficult. I don't mean it was "difficult" by any means necessary. It was simply a plug the phone in, let all the drivers install, unhook and put in download mode, hook up again for more drivers. Restart phone, start up kies, hook up phone, and click "Upgrade phone" button. Accept the terms of service or whatever, and wait. Upgrade starts, phone flips into download mode on it's own, restarts a couple times, and voila, you're on 2.2. I thought it was a piece of cake. My issue is that regardless of how easy it was, it still ended up rather broken because all those applications were missing, on top of the fact the Settings panel was also gone, leaving me unable to perform a factory reset.
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
The.Se7enth said:
At the time I tried, Kies itself didn't support the Captivate. Only Kies mini. And in order to do that upgrade, I had to install the drivers, then put the phone into download mode to install more drivers for some odd reason, restart the phone (taking out the battery and putting it back in), then hook it up. Kies mini wouldn't detect the phone for several tries at first, finally got it about the 10th time in. Then go to the "Upgrade phone" link, and yeah. I followed the instructions from Samsung's official SGH-i897 Froyo upgrade guide.
I did EXACTLY as the instructions say, down to the wire. Still ended up both times with all those applications missing and the settings panel missing, unable to do a factory reset without flashing back to 2.1 first.
Click to expand...
Click to collapse
Fail, Kies Mini works from Kies mode on the phone. It puts the phone into download mode when you start the upgrade from Kies Mini.
Just saying...
The.Se7enth said:
Nope. Don't feel their insurance policies are worth it. You spend more money on the insurance policy in total, even if it's month-to-month, than you would on a brand new contractless phone. Besides, I had only made $120 from fixing up three ancient computers (so ancient they actually had ISA slots and DIMM SD-RAM memory -- one was even a Pentium II), and only had $50 by the time I bought the phone which was a couple months later. My $50 went towards the phone and a pack of screen protectors, while my mom covered the upgrade fee. Couldn't afford the insurance policy even if we wanted to.
But I do greatly appreciate the encouragement. I'll give it a go in a bit, and try out flashing Serendipity. I'll follow the official instructions from their own website though, because I read this on their FAQ:
"Never use ROM Manager. EVER, EVER, EVER, EVER, EVER!"
RadioShack replaced the phone the first time, but the manager there said after replacing it once, the warranty was thus void. I'm not sure if profanity is allowed here, but you can figure out which word I wanted to reply to him. It's eight letters long, starts with bull.
I've read posts on AT&T forums saying if the phone's bricked or can't be repaired by user methods though, especially if it's rooted, that they won't honor the warranty at all and will consider it user error and that you're out of luck. Even people who tried to upgrade to 2.2 stock had issues with that. But I dunno.
Anyways, my machine works perfectly for everything else. Before the repair, when I tried to upgrade? It was a fresh install. I had just reformatted it because it was performing sluggish before and I decided I wanted a single-boot installation instead of having my old dual-boot of Windows 7 and XP. It's now just XP for the time being, seeing as how the hardware's limited and I want to get the best out of it for gaming (I can run 7 with ease, but it uses more resources than XP, thus games don't run as well).
I realize earlier I may have come off as implying the upgrade to 2.2 process was difficult. I don't mean it was "difficult" by any means necessary. It was simply a plug the phone in, let all the drivers install, unhook and put in download mode, hook up again for more drivers. Restart phone, start up kies, hook up phone, and click "Upgrade phone" button. Accept the terms of service or whatever, and wait. Upgrade starts, phone flips into download mode on it's own, restarts a couple times, and voila, you're on 2.2. I thought it was a piece of cake. My issue is that regardless of how easy it was, it still ended up rather broken because all those applications were missing, on top of the fact the Settings panel was also gone, leaving me unable to perform a factory reset.
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
Click to expand...
Click to collapse
Yea once you have serendipity installed don't use rom manager but for initial install your fine
Sent from my Captivate running CyanogenMod7 using XDA Premium App
cappysw10 said:
Fail, Kies Mini works from Kies mode on the phone. It puts the phone into download mode when you start the upgrade from Kies Mini.
Just saying...
Click to expand...
Click to collapse
You can "say" all you want, my good sir, but google the instructions. They tell you clearly to put the phone into download mode TO FINISH INSTALLING DRIVERS. You don't start up Kies mini until after all the drivers are installed, at which point you hook up the phone with USB Debugging, not Kies mode. I appreciate your willingness to help, but be sure to read everything I say before you correct me. I'm not that slow. I read instructions thoroughly and I've read quite a lot of posts on these forums. I work with computers regularly -- just not Android. The issue had nothing to do with that anyway, so that doesn't even matter.
brendanmurphy said:
Yea once you have serendipity installed don't use rom manager but for initial install your fine
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
I'm sure it's possible, and I don't mean to come off disrespectful, but I'm just gonna go with the instructions on their website. Just seems a safer route to install a ROM by the creator's instructions, you know? Only thing I'm not sure about is what they mean by "Flash it in 2e recovery (twice)." on ClockworkMod.
The.Se7enth said:
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
Click to expand...
Click to collapse
These two are still my top questions now. Is it a good idea to have the SIM card out during the upgrade process, and not put it back in until after the update is 100% complete?
Also, I'm really frustrated about this whole driver thing. I know the drivers aren't broken because I used them on this very computer before, and the repair shouldn't have damaged anything because absolutely everything else is working flawlessly. But every time I've uninstalled the drivers completely, and hook up the phone, it keeps getting a fatal error on that. Apparently "S3C6410 Android ADB" is the name of the device that can't install drivers.
Just sent my HTC Sensation off for repair under warranty due to this fault :
Running OpenSensation nightly 20120810 and TamCore 3.0.40 without any issues and updated the nightly every 2-3 days with no issues. had the phone 12 months and had it s-OFF and unlocked about 4 hours after buying it. At that time running CM7 as that's all there was, updated to various ROMs until I settled on OpenSensensation (tried CM9 a couple of times for a few days but prefer OpenSensation). All ROMs installed fine over the past 12 months
Installed Kingdoms and Lords off Google play (huge game 200MB data download via wireless), after first game phone froze and reset. So I reduced the overclock, game running fine. Had another game later on in night playing for about 15 minutes. Phone froze again, switched itself off and didn't come back on again !!!!
Tried charging it thinking battery was flat, no charge. Took battery out as it was an Anker 1900mah just in case it had blown. Put original HTC battery back in, no charge light, nothing. Took battery out and left it out 2-3 hours as suggested on 'net as it 'might' help
No charge, tried another USB lead plugged into desktop. Still no charge .... oh crap
Took to T-Mobile shop I got phone and explained situation, forgetting to mention it was running custom ROM, they tried. Still no charge, no reaction in shop. Zero, zip
They sent it off for inspection/repair yesterday under warranty and said it should take 2-4 weeks
It had been running custom firmware since the day I got it on contract and has never caused me any grief, apart from some roms running better than others while I made a choice which ROM to stick with
Question I'm asking is can HTC still test the phone even though its not taking a charge or I assume not powering and just froze and died, assuming the motherboard is fine does anybody know if they use test points that bypass the USB socket to power it up
And how can just playing a legitimate game downloaded off Google Play freeze the phone and shut it down never to power up again
I'm guessing the possibilities of a faulty USB charge socket, faulty power switch or fried CPU/GPU/motherboard considering it just froze and died
I used it as a phone but did play games quite a lot during the day when I had a few minutes while not working, and had it overclocked to around 1625-1728 which it ran stable at without overheating
If they send it back refusing to touch it due to finding custom firmware on it I'm looking at the Samsung galaxy SIII over the HTC Nexus One simply because the Samsung has a removal battery and additional microsd card slot where for some reason I assume is to make rooting more awkward the HTC has a hardwired battery and NO extra sim card slot. I was looking to replace it when my contract expired in February but if they refuse to fix it citing custom firmware (even though it has been working perfectly for 12 months running various custom firmware) I have no real choice but to buy out my contract and get a new contract. Bummer
Hmmmm,
Reading a few postings it appears there is a possibility that the motherboard is fried somehow, or a 'hard brick' through a bad ROM install ... I wasn't updating and firmware, not updating any ROMs
Just playing a game downloaded and installed off Google Play, but if it means the motherboard is fried then at least it means HTC will have to replace it as 'faulty' so saving me the upfront cost of buying out my contract thas has 6 months to run
Actually if you overclock the device or flash a kernel htc doesn't have to replace anything.. by "playing a game downloaded from google play" you mean "playing a game downloaded from google play on a device controlled by custom drivers which clearly make your device out of warranty". So I'm not sure.. altough it's possible that it's not the fault of the kernel but the mainboard had some issues. They are able to test the charging port and the main board seperately. Let us know abouth the end.
It would interesting to see HTC's response either way so I'll report back once they have a look at the phone
As I don't have a loan phone at present so have no phone until they get one back from customers having their phone repaired, I have to use the 'net to check on the status of the repair via the T-Mobile website
I got my phone back yesterday with a new motherboard, under warranty
Now seriously struggling to get it to S-OFF as its running HBoot 1.27 as teh guys in the shop also said its had "new firmware upgraded for you", or to prevent me from getting S-OFF
Tried the all in one kit, tried the 'official' unlocker method from HTC. Keep getting the same error about token mismatch when trying to unlock the bootloader
Reading postings from here and there it's suggested that as the motherboard has been changed and a new IMEI, the IMEI and hardware serial numbers now don't match so causing a mismatch between number so the unlock obviously fails
Looking at trying the JB_Bear flash wire trick when I have more time to see if that work with replacement motherboards, so any suggestions as I'm stuffed and want S-OFF as well as full root again. Unlocked it when it was running HBOOT 1.18 was a doddle but now its a pain and T-Mobile branding is pants so want to be able to have my phone how I want it without all the crappy restrictions
Unless somebody can S-OFF and root for me in the North-West Lancs area without sending the phone away, I'll have to do a bit more digging to see what I come up with
thescrapyard said:
I got my phone back yesterday with a new motherboard, under warranty
Now seriously struggling to get it to S-OFF as its running HBoot 1.27 as teh guys in the shop also said its had "new firmware upgraded for you", or to prevent me from getting S-OFF
Tried the all in one kit, tried the 'official' unlocker method from HTC. Keep getting the same error about token mismatch when trying to unlock the bootloader
Reading postings from here and there it's suggested that as the motherboard has been changed and a new IMEI, the IMEI and hardware serial numbers now don't match so causing a mismatch between number so the unlock obviously fails
Looking at trying the JB_Bear flash wire trick when I have more time to see if that work with replacement motherboards, so any suggestions as I'm stuffed and want S-OFF as well as full root again. Unlocked it when it was running HBOOT 1.18 was a doddle but now its a pain and T-Mobile branding is pants so want to be able to have my phone how I want it without all the crappy restrictions
Unless somebody can S-OFF and root for me in the North-West Lancs area without sending the phone away, I'll have to do a bit more digging to see what I come up with
Click to expand...
Click to collapse
for replaced mother boards ..there is a different version of jb ..check my soff guide ..link in my signature
Will let you know how it goes, thanks
Managed to get S-OFF using your method after a few tries did nothing so started making me nervous I was about to fry my new replacement motherboard, eventually it beeped and did the S-OFF by following yours steps to the letter
Problem is now, I want to remove the ***LOCKED*** but every recovery.img I try fails with a token error, which reading about it is down to teh bootloader apparently still locked
Also changed the HBOOT to your JB_HBOOT with no difference, still S-OFF but ***LOCKED***, so can't get the next step to get a fully rooted fully unlocked system so I can get back to where I was before the original motherboard died
I'm now looking at installing CM10 JellyBean 4.1 by KANG, I used to run OpenSensation CM9 quite happily and nightlies with zero issues installed a few ROMs over the past 12 months with a couple of minor issues I solved myself with reboot loops and ROMs getting confused and having to wipe the entire phone, plus when I wiped the core by accident during yet another ROM install .... that was fun to solve. Took a couple of days of reading about that one
Anyway, any suggestion as to how to get full unlocked or at least so I can install 4EXT recovery and SuperUser to get a bit further on the custom ROM route and get a phone that's what it should be instead of crippled by T-Mobile UK
Thanks for your help to get where I am so far
thescrapyard said:
Managed to get S-OFF using your method after a few tries did nothing so started making me nervous I was about to fry my new replacement motherboard, eventually it beeped and did the S-OFF by following yours steps to the letter
Problem is now, I want to remove the ***LOCKED*** but every recovery.img I try fails with a token error, which reading about it is down to teh bootloader apparently still locked
Also changed the HBOOT to your JB_HBOOT with no difference, still S-OFF but ***LOCKED***, so can't get the next step to get a fully rooted fully unlocked system so I can get back to where I was before the original motherboard died
I'm now looking at installing CM10 JellyBean 4.1 by KANG, I used to run OpenSensation CM9 quite happily and nightlies with zero issues installed a few ROMs over the past 12 months with a couple of minor issues I solved myself with reboot loops and ROMs getting confused and having to wipe the entire phone, plus when I wiped the core by accident during yet another ROM install .... that was fun to solve. Took a couple of days of reading about that one
Anyway, any suggestion as to how to get full unlocked or at least so I can install 4EXT recovery and SuperUser to get a bit further on the custom ROM route and get a phone that's what it should be instead of crippled by T-Mobile UK
Thanks for your help to get where I am so far
Click to expand...
Click to collapse
for flashing eng-hboot aka changing from LOCKED to Juopunutbear
check the troubleshoot point #3 solution in my soff guide ..its explained there
and for thanks ..there is a button to say that
All sorted, now running the latest nightly of Kanga JellyBean 4.1 and full rooted and back to how it was before the motherboard dies, apart from running Android 4.1
Also feels much smoother and much faster, even though its only running the default slight overclock that Kanga sets as teh default, so might leave it at that as it feels faster than previous when running OpenSensation 4.03
Great stuff