I have a Sprint Mogul running DCD 3.3.4, which I've been using for months. I was listening to a podcast (Buzz Out Loud) via BT headset last night. I paused the podcast via the headset and when I tried to restart it found my Mogul to be in Bootloader (Olipro 2.40). hard, soft resets and puled battery did nothing. Since getting home I tried to connect via usb and get a Windows failed device warning, so titan_exitbl is out. I tried to flach DCD 3.3.4 via sd and the grey loading screen comes on briefly then it returns to the bootloader screen. I also tried re flashing the radio and that doesn't even get a loading. Is there anything I'm missing that I haven't already tried? I'm out of warrenty and I don't have insurance. I've had good success with Sprint, getting 2 replacements when the junk usb port in this phone failed, but I fear I'm pushing my luck. I really hoped that this unit would last till at least the TP2 came out! Andy assistance is greatly appreciated!!!
are you trying to flash with an SD card?
You may be able to flash the current stock Rom from Sprint via sd card as it includes bootloader. It would wipe your device clean and you can start from scratch.
Hope something works for you.
jph8tr said:
I have a Sprint Mogul running DCD 3.3.4, which I've been using for months. I was listening to a podcast (Buzz Out Loud) via BT headset last night. I paused the podcast via the headset and when I tried to restart it found my Mogul to be in Bootloader (Olipro 2.40). hard, soft resets and puled battery did nothing. Since getting home I tried to connect via usb and get a Windows failed device warning, so titan_exitbl is out. I tried to flach DCD 3.3.4 via sd and the grey loading screen comes on briefly then it returns to the bootloader screen. I also tried re flashing the radio and that doesn't even get a loading. Is there anything I'm missing that I haven't already tried? I'm out of warrenty and I don't have insurance. I've had good success with Sprint, getting 2 replacements when the junk usb port in this phone failed, but I fear I'm pushing my luck. I really hoped that this unit would last till at least the TP2 came out! Andy assistance is greatly appreciated!!!
Click to expand...
Click to collapse
Make sure the MicroSD card is less than or equal to 2GB, formatted for FAT, and that the file is titled TITAIMG.nbh
My mistake - it should be formatted FAT32.
serfboreds said:
You may be able to flash the current stock Rom from Sprint via sd card as it includes bootloader. It would wipe your device clean and you can start from scratch.
Hope something works for you.
Click to expand...
Click to collapse
Thanks, it got me close but no cigar. I was able to get the update (3.37) to complete, but it reboots to the SPL-2.40 screen. I'm having the sad revilation that this Mogul is a brick and I'll have to throw myself at the mercy of Sprint support. wish me luck! Anyone know how to revert to a stock (2.07?) bootloader without usb or fully functioning device?
Have you tried to flash back to 2.07 bootloader yet?
I've recommended that friends have unlocked their phone and their biggest concern is usually that if the bootloader install bricks the phone then they can't get the stock software on there again so that they can bring it in for repair.
Personally, I suggest that they just bring me their phone if that happens and I'll hook it up to the DC generator in my workshop and the device will experience an electrical problem. I guess with the new insurance changes, that you don't want to just throw it and show any physical damage.
Luckily I've never needed to do this, as we haven't made any bricks. However, there are so many ways to ensure that the carrier doesn't boot the device into some non-stock boot loader.
It sounds to me like your device's memory has failed. I doubt they'll be able to fix it anyway. However, have you tried the TITAIMG.nbh from the nueSPL Relocker on your FAT formatted SD card?
bitserve said:
I've recommended that friends have unlocked their phone and their biggest concern is usually that if the bootloader install bricks the phone then they can't get the stock software on there again so that they can bring it in for repair.
Personally, I suggest that they just bring me their phone if that happens and I'll hook it up to the DC generator in my workshop and the device will experience an electrical problem. I guess with the new insurance changes, that you don't want to just throw it and show any physical damage.
Luckily I've never needed to do this, as we haven't made any bricks. However, there are so many ways to ensure that the carrier doesn't boot the device into some non-stock boot loader.
It sounds to me like your device's memory has failed. I doubt they'll be able to fix it anyway. However, have you tried the TITAIMG.nbh from the nueSPL Relocker on your FAT formatted SD card?
Click to expand...
Click to collapse
I think the problem was caused by the usb port, it had been flaky for over a month, though no bent pins this time. I could get the update via sd to complete, but it would return to the bootloader. I went into a Sprint repair center, they didn't even look too closely at the screen. Unfortunately, they had Moguls so no TP for me. This is now my 4th Mogul, all have had white spots, 1 had a failing keyboard and right now 3 out of 4 have had failed usb ports. I've owned ~8 PDA's and maybe 14 cell phones in my time and the Mogul is officially the worst made electronic device I have ever owned.
Well I'm on my first Mogul and I use it quite a lot, including the USB. Haven't had any problems except for the low memory.
jph8tr said:
Thanks, it got me close but no cigar. I was able to get the update (3.37) to complete, but it reboots to the SPL-2.40 screen. I'm having the sad revilation that this Mogul is a brick and I'll have to throw myself at the mercy of Sprint support. wish me luck! Anyone know how to revert to a stock (2.07?) bootloader without usb or fully functioning device?
Click to expand...
Click to collapse
also, if you have not figured it out already, you MUST set the allocation size to 1024. leaving it on DEFAULT will not work.
In windows XP you might have to go into the disk management settings to do this, as a "quick format" from the right contextual menu will NOT work. I struggled with this several days ago, and located that solution. At that point the TITAIMG in the SD card loaded properly.
At the "Default" allocation size, it would brielfy flash a "loading" screen, then go back to the rainbow flag screen.
anthonyandrews said:
also, if you have not figured it out already, you MUST set the allocation size to 1024. leaving it on DEFAULT will not work.
In windows XP you might have to go into the disk management settings to do this, as a "quick format" from the right contextual menu will NOT work. I struggled with this several days ago, and located that solution. At that point the TITAIMG in the SD card loaded properly.
At the "Default" allocation size, it would brielfy flash a "loading" screen, then go back to the rainbow flag screen.
Click to expand...
Click to collapse
Thank you for your help! For the record, I'm moderately adept at the upgrade thing, I've flashed off this card at least 15-20 times. My best guess (and it is pure guess!) is that the loose USB port dislodged while the phone was charging caused something to fry. I had some indications that all was not right, the phone was hard to sync (had to get the plug inserted just right), it had rebooted a few times for no reason recently and the upper "mail" and "net" button back lights would sometimes stay on even when the phone was off. I was able to get a stock rom to appear to go through a flash, but it would return to the bootloader. I had the Mogul swapped out and used the same card to flash the "new" phone without issue. Fortunately, I use Sprite Backup nightly making restoration a snap, Unlock> radio> ROM> carrier CAB> b/u restore. I did have to re connect my BT devices, for some reason they don't completely reconnect after a b/u restore. My phone was back to normal in less than 15 min. It's nice to have my phone back, but my opinion of it now is that it's a unreliable piece of crap that I can't wait to replace. Thanks again for the assistance!
Related
Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
CCRDude said:
I don't think using bold letters and the clear word "lie" will help you a lot... you just highlight that you ask for illegal help
Maybe you should take a look at the bricked-devices topic for a chance to revive it?
Click to expand...
Click to collapse
I have spent the last 3 days 30 hours orso fixing my phone. Revive is something my dead baby won't do.
vayip said:
I have spent the last 3 days 30 hours orso fixing my phone. Revive is something my dead baby won't do.
Click to expand...
Click to collapse
enter the bootloader; try to flash a regular update from your provider to it.
vayip said:
Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
I did the same with my Vodafone (UK). I just told them I'd hard reset and this is all I can see on the screen (don't get stroppy etc).
Mine will be back Tuesday, warranty repaired.
Vod UK use an outside repair centre so will probably be the same as T-Mobile if you are in UK. Mine needed a new motherboard, but there is a bit of a shortage in the UK (too many bricks???). I guess it depends on the outside service centre contract whether they charge you or T-mobile (and maybe also because I had warranty and Insurance)..
Just go in and plead ignorance, but if they want to charge you, ultimately it was you that ****ed it and not them
Toast it in the microwave for 5 seconds!
boz said:
Toast it in the microwave for 5 seconds!
Click to expand...
Click to collapse
That's a new one - when car radio codes first came out they always said to put them in the freezer then stroke the chips legs to erase the cmos... never worked for me, but I'd probably get away with the microwave thing with 3 kids at home!!!
@ Olipro
If you mean the SD-card flashing, T-Mobile Holland doesn't have an update available. There is an T-Mobile Holland ROM available, but the image is older than the image installed on my phone. When checking the ROM in the white screen, it says not allow. I think i need ROM 1.21.114.3 from T-Mobile if I want to do the SD-card flash.
I only have access to the bootloader, I have bootloader 1.04, and I have access to KITL mode, but the Windows CE Platform Builder fix also doesn't work
@ ach2
I was thinking also something like that. That I hard reset my phone and now it's broke. I was also thinking something like I left my phone on the charger for the weekend, and when I came back I did a soft reset because it wouldn't go on and know I only see a HTC splash screen.
vayip said:
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
Can you think of a good reason whey the boot screen has changed from the normal T-Mobile one... just hope they don't turn on the phone. Did you try Olipro's suggestion?
@ Wam7
The T-Mobile splash screen is in the extended ROM. If the extended ROM is ****ed up like mine is, it probably goes back to its embedded splash screen, and that's the one from HTC. But thats not what I'm going to say, I'm going to say how should I know.
If I remember correctly a guy has managed to dump the ROM from a Hermes and flash it to the phone... saw a thread somewhere here. If that's the case then you should just need a ROM from a fellow dutch T-Mobile owner with the newer ROM. I take it your phone is not SuperCID
vayip said:
@ Olipro
If you mean the SD-card flashing, T-Mobile Holland doesn't have an update available. There is an T-Mobile Holland ROM available, but the image is older than the image installed on my phone. When checking the ROM in the white screen, it says not allow. I think i need ROM 1.21.114.3 from T-Mobile if I want to do the SD-card flash.
I only have access to the bootloader, I have bootloader 1.04, and I have access to KITL mode, but the Windows CE Platform Builder fix also doesn't work
Click to expand...
Click to collapse
if you have 1.04; run the RUU on your computer; you will get a "Vender ID Error" immediately ignore this and run the updater AGAIN (do not touch or unplug your PDA) after doing this a second time it will begin to flash
vayip said:
Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
seriously this is why MS and Carriers HATE us
Olipro said:
if you have 1.04; run the RUU on your computer; you will get a "Vender ID Error" immediately ignore this and run the updater AGAIN (do not touch or unplug your PDA) after doing this a second time it will begin to flash
Click to expand...
Click to collapse
I did what you said. I connected the phone to my laptop in bootloader. I started the RUU from WMXL 0.20. My phone goes to the white screen and at 0% i get a message on my laptop the connection got disconnected. So i start the RUU again, but again the message my connection got disconnected.
So still working on a good lie.
@vayip: sounds like a problem with the USB on your laptop. Try using a different computer. BL1.04 will let you flash any OS provided your NAND isn't full of bad blocks. You're a long way away from returning your device to Tmo IMO.
On the new computer:
direct USB connect to rear port only no usb hubs
pc running windows XP
turn off screensaver/Powersave mode
close all other apps
hands off the computer for the 25 minutes or so that it takes
Sleuth255 said:
@vayip: sounds like a problem with the USB on your laptop. Try using a different computer. BL1.04 will let you flash any OS provided your NAND isn't full of bad blocks. You're a long way away from returning your device to Tmo IMO.[/list]
Click to expand...
Click to collapse
Does it matter if the phone is simlocked or not. My phone is not SuperCID.
The strange thing than is, i have 2 laptops. Doing the upgrade don't work on both.
Will try a normal pc then. Maybe more luck.
Follow Oli's advice about retrying the update if you get an initial vendor ID error. BL1.04 will flash any rom without SuperCID due to a bug.
You might want to jump in with mtty first to see if your NAND is full of bad blocks. If it is then your device is toast fttb.....
spiritofseth said:
seriously this is why MS and Carriers HATE us
Click to expand...
Click to collapse
I completely agree! If you ****ed up your device, than you should have the courage to stand up for it and if it was not your fault, than just tell them the truth! But suggestions like "put it in the microwave for 5secs".... come on
And just a small hint: If you (for example) really put it in the microwave, than you'll better pray that no technician ever analyses your device - if so you could get into serious trouble, mate.
Btw, if you microwave it, you probalby need a new microwave too.
Edit: And i dont think its warranty would cover "I just put my Phone in there"
"So still working on a good lie."
Doesn't breaking your phone through your own actions and then getting it repaired/ replaced for free by telling lies make you a liar and a thief?
I trashed 8525, and that sucks, but it was my fault so I have to pay for it.
In my adventures flashing Roms, I've only bricked 1 Hermes (Cingular 8525). I actually told the local Cingular shop that I broke it 2 weeks after I bought it. The manager told me to bring it in and she replaced it under the 30 day in-store return policy. I was suprised because I had caused the bad NAND Block problem on the device but she said that since I was able to get an official Cingular Rom flashed onto it and it booted into WM5 (just wouldn't do anything because of memory errors).
Now I also have a very good working relationship with this store. I've gotten a phone about every 6 months from them over tha past 2 years and have given them some great info regarding WM5 devices (reccomendations on screen protectors, software & cases etc). I have 3 lines (2 with Data) and even if they don't know me by name eveyone in the store knows me by reputation.
Tomorrow I will have my spare Hermes (also 8525) so we can begin experimenting with getting some additional storage memory without risking bricking my primary phone.
The way I see it, we are taking a chance when we modify our devices.
I've had to return 2 Wizards for Warranty replacement to Cingular, both were CID Unlocked but the problems were unrelated to flashing Roms (One was because the touch screen developed a dead spot the other was because of Radio hardware issues).
Since Monday morning, I have not been able to sync my phone (was dcd v3.0.4 when it stopped working). I have done much research and have tried many different things in an unsuccessful attempt to solve the issue.
When I plug it in, it begins charging but nothing else happens. No windows new device sound or system tray notification, no driver prompt, no windows activesync activity, nor any activesync activity on the phone (that little arrow icon on the top bar).
I have gotten this problem extremely intermittently previously but have always been able to resolve it with either a soft reset and/or a computer reboot. When that solution attempt failed, I tried moving the usb cable to a different port. I tried four or so different ports with no different results. I tried a different cable. I tried disabling advanced networking, deleting my partnerships (lost my contacts and have not yet been able to re-sync them :/), uninstalling activesync, and cleaning all the activesync files and drivers. I even launched device manager with hidden/non-present devices shown to remove the windows mobile devices (which were oddly not present, although this was after my first activesync uninstall/clean).
After not being able to get anything to respond, I thought it may be something not working properly on my workstation, so I tried similar processes of troubleshooting on my laptop with the same results.
At this point, I figured I had isolated the problem to the device, hopefully being just a software issue and not a hardware issue. At the time, I was still running rom dcd v3.0.4 with radio 3.35. I decided to flash to the newest versions in a hopeful attempt to restore my device's functionality. After flashing radio 3.39 and cooking and flashing a dcd v3.1.2 rom, I tried again with no different results.
Finally, I decided to connect it in bootloader mode, just to see what would happen (what is normal behavior for this anyway? does it get detected and drivers installed correctly?). It was detected as a usb device by my workstation but could not install drivers for it.
Needless to say, I have become rather frustrated with my device this week. I am not sure what the problem is exactly, nor what I could possibly do to fix it. I am on the verge of flashing a stock rom and *gasp* going to the Sprint store for support. Perhaps I finally dropped or shocked it one too many times this past weekend, and it does indeed have a physical issue...
Does anyone have any suggestions/ideas/thoughts? I would be very greatful for any input.
Thank you!
See this thread and see if anything in there fixes your problem.
http://forum.xda-developers.com/showthread.php?t=393918
I have been following that thread in hopes that something may prove helpful and have tried everything suggested, including attempting to clean the port (what would be best for this? anything more than just blowing into it?), trying the two Y adapters I have (emu -> emu / mini-usb & emu -> mini-usb / 2.5" stereo), running that batch script and working with the device manager (those devices were not present), and disabling advanced network functionality, all with no results.
VerusMaya said:
running that batch script and working with the device manager (those devices were not present),
Click to expand...
Click to collapse
If you've sync'd in the past then when you display hidden devices those devices should be present (at least faded). It'll be very strange if you don't see them. If not then uninstall the Mobile Device 6.1 upgrade, restart the PC and reinstall it. Then open up the device manager and watch what changes when you plug in your WinMo device.
Keystone said:
If you've sync'd in the past then when you display hidden devices those devices should be present (at least faded). It'll be very strange if you don't see them. If not then uninstall the Mobile Device 6.1 upgrade, restart the PC and reinstall it. Then open up the device manager and watch what changes when you plug in your WinMo device.
Click to expand...
Click to collapse
I also thought it quite strange that I did not see those devices at all at when I displayed hidden/non-present devices in the device manager. I definitely have sync'd on this machine many times, I typically leave it plugged in throughout the day here at work. My machine is part of a corporate domain but I do not see how anything pertaining to that would affect my devices. On my laptop (used to sync here), the devices were present in the device manager, but even after uninstalling them the phone would not be detected when I plugged it in.
When you say uninstall the mobile device 6.1 upgrade, are you talking about the vista mobile device manager? I am on XP with activesync 4.5.
Also, nothing happens when I plug the device in, not even the standard device connected notification sound. Nothing changes in the device manager, nothing is found when I rescan hardware, I even uninstalled all the usb root hub devices and rescanned for them, hoping a complete usb subsystem driver reinstall may help detect something.
I even downloaded and ran two usb tools, one free usbdeview (http://www.nirsoft.net/utils/usb_devices_view.html) which displayed and monitored all usb devices (present and non-) and drivers and a trial of a usbtrace (http://www.sysnucleus.com/) which was a usb protocol traffic capture and analysis program. I experimented with (un)plugging the phone multiple times in multiple ports with two different cables while running these programs, attempting to find something useful. Absolutely nothing at all happened in either program, which makes me believe it is something either on the phone software or hardware.
I have a feeling I may require a device swap :/
VerusMaya said:
When you say uninstall the mobile device 6.1 upgrade, are you talking about the vista mobile device manager? I am on XP with activesync 4.5.
Click to expand...
Click to collapse
Yeah, activesync then... I dunno, I'm at a loss.
Yeah me too, looks like I am going to have to flash the latest stock Sprint rom and take it in hopefully they can do something for me.
Went to sprint, it was a bad port after all, they gave me a brand new device.
VerusMaya said:
Went to sprint, it was a bad port after all, they gave me a brand new device.
Click to expand...
Click to collapse
Are you sure they gave you the brand new device? coz same thing happened to me a week ago and i went to sprint. They gave me the refurbished phone back. Physical condition of the phone is very good tho.
SptMogul said:
Are you sure they gave you the brand new device? coz same thing happened to me a week ago and i went to sprint. They gave me the refurbished phone back. Physical condition of the phone is very good tho.
Click to expand...
Click to collapse
Well I suppose I am not sure it was brand new, but it had the screen protector and the plastic stickers still on it (next to keyboard when you slide it out). I also received an additional 512MB SD card that comes with it.
Did you flash back to a sprint rom via sd card?
arcanecho said:
Did you flash back to a sprint rom via sd card?
Click to expand...
Click to collapse
Yes, I extracted the two NBH files from the latest (3.35 I believe) stock Sprint rom installer and first flashed the smaller image (bootloader/radio I think it was), and then the larger image (os) before I took it in.
The rep I dealt with at first was somewhat of a technical idiot and only served to confuse/delay matters but after I returned, I spoke to someone else and gave them permission to hard-reset, as well as mentioned I had done this multiple times as well as tried multiple computers and multiple cables, just to help them narrow down the possible source of the problem (as well as to block possible common excuses). After waiting around for half an hour or so in-store, a technician brought me a new phone and told me the port was physically bad.
All-in-all, I was quite pleased with Sprint's service and my free swap for an issueless and scratchless new device. I was afraid it was not going to be quite so easy, requiring more time and/or an insurance replacement fee. Not to mention the free 512mb sd card.
I had a similar problem, I was un able to connect to active sync but was able to charge. Everytime I would try to connect to active sync I got the "device is not recognized" error. Then someone on here suggested perhaps my USB port was messed up, sure enough I looked in the port and noticed one of the gold pins was flipped up slightly higher then the rest. My friend took a needle and adjusted the pin and it was good as new. Somehow I had lifted one of the pins.
Anyways IMHO it's good to look in there and just check if your having problems connecting, it saved me a trip to a technician and having to wait or go through reprogramming everything.
I have an htc touch pro and it wont sync. to anything. Even my car stereo, witch has a usb port so u can sync music to it, wont work. once in a while it will but most of the time it wont. i have tried everything, but still no luck. I tied a new cable, different computers, everything. I may have to be forced to brick it and get a new one for free from sprint.(i have an insurance plan that will replace it for free if its bricked). Any ideas?
p.s: i have looked everywhere but i cant find how to flash a ROM from internal storage on a touch pro. only a touch diamond. any help?
I am not positive I am understanding you 100%, but here is my take. If you are having problems with it conecting to Activesync, try going into Settings - Connections - USB to PC and make sure the "Enable faster data synchronization" checkbox is unchecked. Many systems cannot take advantage of this.
As far as syncing from the storage card, simply extract the .nbh file and rename it to Raphimg.nbh put it on the root of your storage card and enter the bootloader mode ( I think it is holding the volume down button and the power button at the same time and using the stylus on the bottom to reset. kepp holding them until the tri-color screen appears.)
Good luck, and if I didn't understand you, sorry.
Rush_man said:
I have an htc touch pro and it wont sync. to anything. Even my car stereo, witch has a usb port so u can sync music to it, wont work. once in a while it will but most of the time it wont. i have tried everything, but still no luck. I tied a new cable, different computers, everything. I may have to be forced to brick it and get a new one for free from sprint.(i have an insurance plan that will replace it for free if its bricked). Any ideas?
p.s: i have looked everywhere but i cant find how to flash a ROM from internal storage on a touch pro. only a touch diamond. any help?
Click to expand...
Click to collapse
Uhmm, I made a full thread on flashing the device, including flashing from a SD card. Also, the other thing is that your USB jack might be broken, which may be the reason for the occasional connection. If you have the insurance, don't mess with the phone any longer. Back up your data and take it to the Sprint store claiming that it does not work.
Good luck!
egzthunder1 said:
Uhmm, I made a full thread on flashing the device, including flashing from a SD card. Also, the other thing is that your USB jack might be broken, which may be the reason for the occasional connection. If you have the insurance, don't mess with the phone any longer. Back up your data and take it to the Sprint store claiming that it does not work.
Good luck!
Click to expand...
Click to collapse
I guess i didn't look well enough. anyway, i have to brick it if i were to take it back. I unlocked it and now im using Energy rom 3.0. Witch sprint wont like, i guarantee you. I cant re-lock it because that requires it to sync, which it wont. If i brick it the third part retailer i would go to(because the sprint store doesn't do insurance claims) would just say screw it and order a new one(this is my third touch pro in less then a year). But i will flash it from main memory i guess. It would be nice if it would sync tho.
Thanks, Rushman
I received a Nook Tablet 8GB from a friend that has it messed up pretty badly.
I have tried option 1 on the thread below and was able to boot into CWR and install the partition zip, then i used MiniTool Partition wizard to setup microsd as described, then place the update zip onto microsd.
http://forum.xda-developers.com/showthread.php?p=36492731
Once i put back into nook and boot up it goes to call customer service.
I also tried the following method here
http://forum.xda-developers.com/show....php?t=1663836
I get the green check mark and after reboot i get call customer service.
Again, im not sure what was done to this device before. Just trying to fix it for a friend. Is there anything else i can do?
Should i be using this method?
http://forum.xda-developers.com/show....php?t=1570022
So im assuming there is no hope since there is no response? I see many threads of bricked NT's so im assuming this sort of this is quite common and thats the reason for the lack of response to this thread.
I have worked with android for 2 years now and never bricked a device. I just find it hard to believe this nook tablet cannot be repaired. But again, i have no idea what was done to it.
"Bricked" is a very loose term: without knowing more what's wrong and/or what was done with a tablet it's hard to suggest how to really fix it. Applying a wrong fix often makes the problem worse rather than better.
But it's not necessarily a total loss: until you can figure how to fix it you might try to run CM10 off an SDcard: see http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/, or http://forum.xda-developers.com/showthread.php?t=2061536.
Not sure how i missed that thread but that worked great!
i was about to throw in the towel and you blessed me with that great info. Thank you so much!
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Try holding the "n" button when you power up. Press power and at that very first flicker after a few seconds, press and hold n.
bignadad said:
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Click to expand...
Click to collapse
Try what Asa suggested above, if it doesn't work then your friend's NT is like mine and many others' -- they only boot into SD with a cold boot and using a powered USB cable. Some people deem this "USB-tethered boot" behavior a manufacturing defect, but it might very well be by design by B&N to discourage people from venturing outside their content wall-garden with easy-to-use 3rd-party ROMs.
Hello ladies and gents,
I am trying to help my fiancee revive her completely dead Amaze. This phone, unlike my own, is completely stock. No recovery or ROM flashing or S-off etc. It's straight from Wind Mobile (though around 22 months old at this point).
What happened: Phone was low on battery, so it was left plugged in to charge. Seemed fine. Going back to it a couple hours later, and it was died, which was odd since it was plugged in. Now it does not turn on at all (no HTC or carrier splash, recovery boot [vol down + pwr] does nothing), and the LED behind the speaker does not illuminate to indicate charging (no flashing, either).
Plugged into my computer, I get the "QHSUSB_DLOAD" device identifier, but using the brickdetect.sh script from the Unbricker thread doesn't detect anything. Likely because this has nothing to do with S-off bricking, but since I found that thread via the QHS string, I figured trying to detect it was worth a shot.
I would really love to be able to revive this device. The fiancee is back in school right now, so my income is the only one. Spending several hundred dollars on a new phone is just a kick in the pants while trying to manage already frightening wedding-related expenses. :/
What I have tried:
- Tried cleaning the battery terminals (battery and phone side) on my device
- Tried charging both on USB and wall charger for several hours (no change, no LED, no boot, no recovery boot)
- At my carriers store, I tested a known-good battery in our device, same behaviour
- Tested our battery in a known-good Amaze, after after a longer initial charge (battery was completely flat), that device booted with our battery.
- Tried booting into recovery, no luck
- Tried following steps in several other XDA Amaze and Sensation threads, and didn't get anywhere.
- I've ordered a new battery and external charger, but I'm not hopeful due to the above testing
What I haven't tried:
- Because I am still trying to get my Credit Card Extended Warranty to cover repair replacement, I have not opened the insides of the device. This thread proposes removing and replacing a battery on the mobo to get it to reset itself. I have not tried this yet.
- Anything to do with JTAG. While I've flashed ROMs and such myself many times on my own devices, I've never ventured into JTAG territory before.
What I want to know:
- Primary: What else can I try to diagnose what is wrong with this Amaze, and if it is recoverable?
- Secondary: Unfortunately we have photos on the internal memory (not SD-card) that are not backed up. If the phone cannot be revived, is there any way for me to get into the internal storage to try to recover those photos? This would be more of a challenge project. We can live without the photos, though she'll be disappointed. I'll be the hero if I can get them back, even if it means destroying the device permanently.
Thanks in advance for anyone who may have suggestions. I'm heading to bed for the night, but I'll check this tomorrow and test out any theories.
Does anybody have any theories I can test out aside from some sort of hardware failure on the mainboard?
What OS are you running on your computer. Try looking for the device in Ubuntu, maybe it'll find it there.
Windows 8 and 8.1 have issues with the drivers and software.
Darin_Ram said:
What OS are you running on your computer. Try looking for the device in Ubuntu, maybe it'll find it there.
Windows 8 and 8.1 have issues with the drivers and software.
Click to expand...
Click to collapse
I'm using Windows 7 (64-bit), but I also tried using the Ubuntu 10.04 based Live CD (PHToolz?) from the Unbricking thread, and it didn't detect anything at all (tried with and without automount enabled).
Reading what you said again, I'd say that it's a manufacture defect. It could be a wide list of things actually, hard to pinpoint.
In regards to recovering your photos and other files on the phone's storage itself, I don't think you can recover it at all.
The best bet right now is to get it exchanged if it's still under warranty (I'm assuming you didn't void the warranty by unlocking bootloader, attaining S-Off or flashing any custom roms/kernels/incompatible zip files e.g. A rom meant for another phone)
If it has warranty, don't give up hope.