Bricked Snapvue, unrecognized device - Shift General

I was flashing the radio but got stuck at 17%, tried several times and the same result. It had Hard SPL installed so I didn't though it would be killed, but after reset, it would only be recognized as some data communication device without drivers that searching the forums I found the drivers for Qualcomm modem 6000 and other two devices would fit, now I can only communicate to it through COM7, but the commands are very restrictive (no cego, no mw) and I could not devise a solution to flash it again.
I tried PM several people here but got no answers (of course they have they own business), so I'm posting as a thread in the hope that some ideas may arise.
I also looked towards JTAG but there is no info about the pinouts (not even commercial solutions) and looking the board you won't have a clue.
I hope that correctly using "radata" I can go somewhere, please tell me if I'm wrong and I'll just drop it and sell the Shift for parts, I never actually used it.

How I bricket it
I had some problems when people called my number, snapvue would freeze completely so I decided to flash radio 1.58, but that wasn't any better then I reverted back to 1.27 and the flash process stopped at 17% and would not finish no matter what. I believe one of these files didn't like the "HSPL_final" or is corrupted.
Now I have no sound on Windows Vista side, and a black screen on WM side.:crying:
If anyone could look into it please help me.

SMI
Could only download part of smi.bin file, here is what I got.

Related

ROM upgrade possible using IR

My Trinity device is not recognized by any of my 3 pc's using any of USB ports. The problem started when I wanted to try a different ROM. I currently have 20070418_RUU_Trinity_LVSW_WWE_1.25.0.8 installed. I wanted to install img-32424-mUn_1_25_AKU3_5 but during the reboot after the ROM transfer the connection failed for the USB connection, after which I gave up and thought well let's try again and soft resetted the device. However I was never able to get a Active Sync session going again. The OS is still booting fine so I feel I am trying to fix something which is not entirely broken. I also tried the suggestion for flashing from SD card, but that did load the TRINIMG.nbh file as I hoped (and read) it would be loading. So I have a IR connection and possibly a bluetooth connection (I left my bluetooth module at work so I cant test this) Will this be my free ticket out of jail? Thanks for your input
You might want to ask this on the upgrading subforum, where all the people who flash their trinity are. This isnt the place for this discussion.
Though personally I'd say no, IR is slow and unreliable, given the length of time it would take to flash a 50mb ROM file, the chances of it breaking halfway through are pretty high, which would brick your device totally.
Try finding a mate's PC that works and doing it from that?
You can't flash using IR or BT because the drivers for those are removed during the flash process.
Post a query in the Upgrading section for info on how to set the device into Bootloader mode, to avoid the need for activesync.
OK will post it in the correct group. Thanks I wont flash it with IR. I already had a suspicion it would not be a happy ending.

Broken GSM, please help

Hey,
Right, so in my great wisdom I managed to drop my TyTN on its face on the kitchen floor one day and since then it just doesn't do GSM.
On boot, it says "No GSM" below the boot logo, and anything to do with GSM (opening the phone app) causes the device to run slow for a little while then return back to normal without launching the phone app or throwing any error message. Its stuck in permanent "flight mode" as it were.
Sending the phone back to the provider, they turned around and said "On inspection it was found that 3rd party software was loaded on the unit and damaged the unit. Unit is returned without repairs done to it."
I was using one of the ROMS from the forums here which worked fine for a few weeks up till the drop. (I do know which one but I'd prefer not to give anyone a bad name where its not called for, so prefer not to mention it directly).
I will say that it was a fairly new release in june.
Also currently have on boot.
IPL-1.04
SPL-1.40.Olipro
Have since tried re-installing version roms which have made no difference at all.
So:
1: is it possible that the updated OS and flashing the radio etc could have cause the problem described?
2: How do I return the phone to its original radio version and a generic (officially supported) WM5?
3: Is there anything I can do from my side to fix the problem?
Many thanks
-RobH
Have you tried flashing the original ROM that it came with... Then you can probably take it back to another warranty shop or to HTC for repair... You can also upgrade to Olipro 2.10, you can search for the files, I'm just to lazy to look for it now... If you can't find let me know, and I'll look for it...
Once you upgrade to Oli 2.10, it may make a difference.. Have you tried flashing the radio...? It could very well be a hardware problem that occurred during that sudden stop on the floor...
I'm not to helpful, sorry...
Rob,
Obviously the fall messed up your TyTN, and HTC now refuses to work on it (read save money) because you are running a non-standard firmware. Well, screw that!
Have a look here to start the downgrading process.
Then, go to Leaf's site and download the AKU3 firmware from the Members section.
Flash it to your TyTN.
Then take it back to a different repair centre (not too sure about your options in Grahamstown) and tell them you dropped it, and now it is not working anymore.
Right so trying to get the original (well an club-imate approved) rom installed so that I can try the repair center again...
Based on this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
Image is HERMIMG_CDL_1.31.305.2_SHIP.nbh
(Extracted frin JASJAM_wwe_1.31.305.2_1.31.305.104_1.21.31.10_ship.exe)
I get the following:
<Gray screen with blue txt>
HERMIMG.nbh -
IPL - OK
BOOTLOADER - OK
SPLASH1 - OK
SPLASH2 - OK
EXTROM - OK
GSM -
OS -
Update in Progress...
</End screen>
And thats where it sits.
Even when trying the recommended usb/HardSPL methods, its gets to about 14% and hangs. I presume due to the GSM module being damaged.
I've also tried .nbh's that only have the GSM stuff, and using the microSD method, it gets about 5% along the progress bar and then halts.
EDIT: I've managed to flash it with an original rom excluding the GSM stuff. Will see what happens at the repair center...
-Rob
Excellent, hope you get it sorted!

Possible Brick (8125) G4 - At Bootloader Screen

Resolved. Topic Can be Closed / Deleted.
Hello, I am new to the forums and new to reloading phones but fairly tech savvy otherwise.
I have a Cingular 8125 G4 Phone.
Current IPL/SPL
IPL 2.21.0001
SPL 2.21.0lip
-Can Access Bootloader Screen
-I successfully Unlocked it
-Updated the ROM to WM6
-Come to find it operated much slower then my WM5
-Tried a Different ROM
-Left the Room while it was uploading
-Cat attacked the cord or the phone
-Was Detached during the update process
-Rebooted Phone, stuck at the Basic Splash Screen
-Attempted to do a hard reset. Was able to access this screen, format, but would return back to flash screen and just sit there.
I have spent a couple hours going through the information on the forums but to no avail. I fear I have got a paper weight but was wondering if anyone had any suggestions.
Normally I would keep searching however this may prove to be time sensitive and need all the help
Thank you in Advance
Yours Truely
WTFPWN by Cat
Rick
As Murphy's Law would have it, soons as I post this I come across another post that told me to re-flash and for some reason after attempting to reflash 3-4 times, this time it appears to be taking it. I will keep you folks posted
However The link is broken for the official Cingular 8125 WM5 (What was shipped with the phone). If anyone has a link I would appreciate it if someone could send it to me. I will post once I have received.
Thank you very much.
Phone has recovered. However I would like to restore it back to Factory Defaults for reasons that are my own. I feel I can do it but do not have the Factory Image link.
The Following Link appears to be broken:
http://www.htcamerica.net/support/8125/software-downloads.html
This Topic Can now be closed I found the original Rom at
http://rapidshare.com/files/188635235/RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_cingular.rar
Found it after searching on the board for a while.
Adding Keywords for Search Engine to Pick up on so people having similar issues won't have to look as long as I did
AT&T 8125 G4 IPL&SPL
Version 2.25
Original ROM
it's hard to say what rom it had since i got it with wm6.5.
i found a link on this forum to a file called RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_cingular.rar
it seems to be one of the many originals, so i'll try to flash this one as soon as i can figure out the connection issue with ActiveSync. I tried both 4.0 and 4.5 but they both fail to connect i need to fix the pda's display (or wait until it solves itself, like the previous time) in order to troubleshoot the connection error
hi. I hapened for similar trance.
First download RUU_Wizard_Cingular_8125_WIZCNG01_G3_G4_2006_11_May_225_225_225111_22511102_022511_CWS_WWE_Ship2
(seek in google)
Second quit the battery (100% charged) and put again. Power the 8125.
Third reset your PC wihout the 8125 connected.
Fourth connect the 8125 and execute the file donwloaded.
I hpe to help.
(sorry my ugly english, I spoke espaƱol)

[Q] HP 614c Owner needs help

Helo all - I could really use a hand here. This is the second time I have faced this issue.
When trying to make a call on my 614c when the battery is low, it crashes. Upon reboot, the radio no longer works and I cannot make any calls. It just goes into a permanent "Seaching" mode.
What I've tried:
Reboots - warm and cold
Removing the battery for 30 mins
Reset to defaults
Multiple different ROMs including upgrading and downgrading the Radio
No luck.
Last time (3 months ago) I ended up sending it to ipaqrepair to be fixed.
They said:
"the un-official hacked ROM installed in combination with a corrupt / mismatched GSM Radio ROM, these are the root cause of the issues"
I had actually NOT installed a non-official ROM until after it stopped working in a desperate attempt to fix it. But when they got it, it was a 6.5 ROM.
This time, I had upgraded it to 6.5....but I have since downgraded to the official ROM an installed the. .89 Radio update.
It wont work at all and I can't justify mailing it away for another expensive repair.
Any ideas or assistance would be greatly appreciated. Thanks.....
Any ideas? How can I effectively "blow away" all the software/drivers and set the device up as new? IpaqRepair said it was corrupt software last time....
I've installed different ROMs via flash.dio and I tried the HP radio upgrade RUU_1.8.0_081208_MP_M089_WWE. Are their files or settings that the installs I am doing do not affect - and if so, how do I repair/replace them?
Using Sim Manager, it says the phone is not ready. It's just like the phone radio won't initialize...
This phone originated overseas (Europe) - could that be somehow causing this issue since I'm using it in the USA? Something locking or changing and no longer compatible?
Not sure what else I can do and am missing my phone. Any ideas or assistance would be greatly appreciated.
Still fighting with this....maybe onto something now?
When I get the asset viewer information for the phone it shows the radio is present and the firmware number.
the Stack Version, Bootloader Version, Filesystem Verions and Radio GDFS versions are blank.
It does show the IMEI.
I'm guessing I'm missing file/data for the radio....but reinstalling the Radio ROM HP offers has not helped (maybe not complete - just an upgrade?)
Thoughts?
Anyone have a copy of the original ROM and .81 Radio ROM?
Maybe rolling it all the way back might get it operational again....
Official Drivers/Rom/Radio for 614c
Hi,
You can download official drivers from HP website. The forum does not allow me to post the link. Just search for "official 614c drivers" in google and you wil get the link.
Also note, please install using WINDOWS XP os as installing this using other os such windows 7, windows vista etc is not possible.
Okay - I tried installing the software from the HP Website using XP - but it still isn't working. It's just like the software for the radio is corrupted and it won't replace it (does not list the versions like it should when you look at the software inventory).
Is there any way to manually do this? Any advice or help would be greatly appreciated.
If anyone can help me get this resolved, I'm definitely buying them a beer.
Basically the GSM just seems to be bricked. Last time a software fix resolved it, but I'm not sure what software needs to be installed to get the radio working again.
What is the best way to blow it all away and start over? Is there a way to manually delete the radio files - or to look at them for versions/dates to see what is corrupt or mismatched.
-Alpha- said:
If anyone can help me get this resolved, I'm definitely buying them a beer.
Basically the GSM just seems to be bricked. Last time a software fix resolved it, but I'm not sure what software needs to be installed to get the radio working again.
What is the best way to blow it all away and start over? Is there a way to manually delete the radio files - or to look at them for versions/dates to see what is corrupt or mismatched.
Click to expand...
Click to collapse
Just bumping this thread...would love to have this phone back.
Bumping once again - still in hopes of fixing this phone. Can anyone help?
-Alpha- said:
Bumping once again - still in hopes of fixing this phone. Can anyone help?
Click to expand...
Click to collapse
I guess, you will get enlightenment for the problem on your device at http://forum.xda-developers.com/showthread.php?t=455840
Bump.....
Still hoping for a solution. I have gone to a Glisten now, but do not like it as much as the 614c.
I'm open to any suggestions.

Soft Bricked(Hard Bricked partially) Note4 SM-N910P

Alright, Wow a lot has changed here since I got the Note 4!! I no longer use it since I got the A9 from HTC after this one went kaput. Heres the sitch'.....I am super frustrated since the issue I have is a lot like many others ive read all over the internet with just one difference...the USB is not being recognized so I can't use Odin....yes I have tried many different computers, cables etc....the thing was and is still new bout 6 months old before i messed it up so I cant believe that something would or could have easily fried the USB port already. Nothing I have done comes to mind where that could have occurred and could be bad luck getting bad port from the start but unlikely...SO....making it worse is I can boot to stock recovery and the weirdest thing happens when I try to pick any option other than wipe cache or factory reset....it comes up and says dm verity failed, whatever option i chose is disabled!! WTH??? I have been in this awhile so this isnt my first rodeo by far and I have yet to see this.
My question is....HOW can this be fixed...counting out replacing the USB port(that may not be the major cause), I am not sure JTAG will work....most other options all require some sort of PC to Mobile connection to be working and I can't ever get QPST through QXDM to see it( i may be doing it wrong or missing a step....possible since Ive found most instructions to be missing vital information, especially for some of us who may be more green), AND Ive tried creating bootable sd card to use in download mode. The latter option is also very hard to find complete information on process and files needed to properly do so pertaining to this specific variant. The stock recovery i think woukld be the best bet but HOW CAN I ENABLE the options in recovery that are now disable???
I apologize to anyone annoyed if I am asking a question that is often asked.....bear in mind I have another handset I am working on that is completely different that takes up way more time lol, I have searched for weeks on this issue and nothing substantial can be found thanks to to much incomplete information given out AND no one seems to know how to fixed the recovery issue or even had it. Any help will be totally appreciated.....Thanks

Categories

Resources