Hi peeps,
you might have seen that i only have about 10 posts, i used to be a "only in need to download a ROM user sometimes"
I've had several devices (iMate SP5, HTC Diamond, HTC Touch Pro 2 [Even to native android])without any problems... Until now... My Sensation...
As you might have seen my last post was regarding a Flash that seemed to have done something wrong and my device is in QHSUSB_DLOAD mode...
As i already surfed the web during almost a full day and night, i am just going to ask for it, cause i didn't found it on my own...
What's the plan?
As i am still able to use QPST, it offers me the possiblity to restore a QCN file...
problem is... i've found none on the internet...
I've seen a post here stating that someone could provide one, but was a bit afraid cause it has the EMEI etc right hardcoded in it...
I can promise this in return of getting a QCN file:
You get my official address + phone number (spare phone in use atm) prior to get in touch with eachother whenever you want (GMT+1 zone here, want to be able to still sleep a bit )
What will i try to do:
I am going to figure out, together with the person who provided me the QCN file, which info is from the phone itself that dumped the file, where can i retrieve that info (is it on the box, or do i need to take notes promptly to flashing before it bricks and so on...)
What will i offer afterwards:
Apart from a smile on my face cause my phone will work once again (still got 1.5 years of warranty, so if it fails, i still be able to send it to HTC support), this might be the sollution that is needed to get bricked phones back towards a heartbeat... If we have a success, we will make history in Android Phone Recovery! This might provide XDA with a tool to get even bricked phones back, towards a basic ROM or so... very small and fast to flash, so there is a way to get rid of bricked phones...
I will write a manual on how to do it, with credits to the peeps who've helped me out with info, files etc...
And prior to the manual, on a daily base a post here so you can all see what progress i am going trough...
Thanks in advance
Youry (this is my real name btw...)
The programs & Drivers
This post is for the people who are already in the "bricked phone" mode: QHSUSB_DLOAD mode named
In attachment you can find the QPST program and the needed drivers.
Greetings
This post is for those willing to help me out
First and for all, THANKS!!!
In attachment you can find every file i will be reffering to in the manual how to get the backup made.
HOW TO SETUP QPST FOR USE WITH YOUR PHONE (credits to fowenati)
disclaimer: I am not responsible for anything that happens to your phone.
Make sure your phone is plugged in, has debugging ON for the whole time of this manual.
1. Temp Root yourself using whichever method you prefer (This seems to work great for lots of people)
2. Get your MSL using MSL Reader from the Market (free) OR Call Sprint to get your MSL OR Get your MSL using CDMA Workshop (which I will not go into as It is a different subject and not as easy as the aforementioned) (Official market page of MSL Reader)
3. Get QPST and install it (found in attachment)
Put your phone in diagnostic mode by punching in *#*#3424#*#* in the dialer through out the whole rest tutorial, if it goes out of diag mode, just put it back into it by going to Dailer and punching in *#*#3424#*#*
4. Download HTC Diag Drivers Both 32and 64 are in the zip (found in attachment)
5. Install the QPST Drivers for your system (32bit or 64bit)
- A. Go into Device manager (from control panel)
- B. Find HTC Diag or HTC Diag Modem (along those lines)
- C. Right Click it and select update driver
- D. Select Browse computer for driver software
- E. Browse to the folder containing the drivers your downloaded in step 4 and then select the folder for your Windows version (32/64, if you don't know go to my computer and select properties)
- F. Click Next, it will install your drivers
6. Once your drivers are installed your device should be recognized and read as HTC Diagnostic Interface, followed by the port it is located on. Exmaple: COM5.
7. Open "QPST Configuration" by Start>All Proggrams>QPST>QPST Configuration
- A. Select "Add New Port"
- B. Input whatever port your phone is connected to (eg. "COM5" as mine was, without the quotes) in both the port, and label boxes.
- C. DESELECT The "Show Serial and USB/QC Diagnostic Ports only"
- D. Click OK
8. You should see the new added port and its state as ENABLED, if it is there, continue
The phone is now ready to make the backup i need
HOW TO DUMP THE BACKUP
1. In the already opened QPST Configurator program you open the "Start Clients"-menu, and choose "SOFTWARE DOWNLOAD".
2. You will notice that it doesn't activate the correct port normally seen, so click the "Browse"-button in order to select the right port and press the "OK"-button.
3. Open the "Backup"-tab.
4. You will notice that the box of QCN File is empty, click the "Browse"-button, give the file a place and a name, in order to find it after it is done.
5. Press the "Start"-button
6. from here on you will contribute i guess, cause i am not in the possition to know what will happen...
Greetings
*bump*
And reserve place for further postings
thx for your work, also check TrevE's thread http://forum.xda-developers.com/showthread.php?t=1188510
and also check http://psas.revskills.de/
Revskills can read/write phone partitions, but currently our CPU is not supported...
Bump
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
pirlano said:
thx for your work, also check TrevE's thread http://forum.xda-developers.com/showthread.php?t=1188510
and also check http://psas.revskills.de/
Revskills can read/write phone partitions, but currently our CPU is not supported...
Click to expand...
Click to collapse
I've used the info of TrevE a bit in order to find the thread wich said how to get a HTC in DIAG MODE connected to QPST...
All we need now is a QCN Dump file... So if anyone would like to help us out? It might help you out when you ever have a situation which is now stated as a bricked phone!
I'm even thinking about buying a second phone in order to do it myself... (and to have a smartphone which works, sold my backup a month ago, so i'm back to a non-touch, non-smartphone atm...)
are you sure it will work? sensation store files, data and partition in 3 chips, baseband chip, nand and emmc, i think QPST it's not enough... (or we need a newer QPST that support emmc phones too)
and actually revskills doesn't support "write" for our chipset
i think we should ask to guys working/near HTC, they can provide us leaked ROMs, with not recovery files?
If everyone is just asking if it will work and never tests it... we'll never know, i am waiting for a dump file so we can try it...
pirlano said:
are you sure it will work? sensation store files, data and partition in 3 chips, baseband chip, nand and emmc, i think QPST it's not enough... (or we need a newer QPST that support emmc phones too)
and actually revskills doesn't support "write" for our chipset
i think we should ask to guys working/near HTC, they can provide us leaked ROMs, with not recovery files?
Click to expand...
Click to collapse
*Bump*
Anyone willing to help us out?
Da_Loony said:
*Bump*
Anyone willing to help us out?
Click to expand...
Click to collapse
So you just need a backup from a working phone?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
Yep that's what i need, a backup of a working phone, so i can see if it gets the phone back to life or not... afterwards if it worked, we can strip the file down to just hboot + CWM or so, so we can get it very fast done when this happens to a phone
dexter93 said:
So you just need a backup from a working phone?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
Click to expand...
Click to collapse
Hello Da_Loony,
i want to ask you if your idea worked out using the backup of a working phone? and if yes can you upload the backup please
Any news about the topic ? I need a QCN file for a bricked Sensation XE.
- A. Go into Device manager (from control panel)
- B. Find HTC Diag or HTC Diag Modem (along those lines)
Click to expand...
Click to collapse
nothing appears in device manager(im running windows 7 32-bit)
and i have to ask,is this completely safe procedure?
im willing to help you if it is
subscribed. i would suggest asking a mod to move this to either development or general sections, since q&a is not getting enough attention.
btw, which sensation do you have, op? xe or regular? would it even matter at that level? mike (the revolution cook) compared partition dumps from xe and reg sensation here: http://forum.xda-developers.com/showthread.php?t=1412618
ill give this a go tonight if i can or if not ill do it on saturday its always good to know theres a way back from a brick. I would also try pm'ing someone like adamoutler to see if this might actually work just an idea
EDIT: can't get into diagnostic mode on my phone because im on a custom rom sorry guys
dmcb123 said:
EDIT: can't get into diagnostic mode on my phone because im on a custom rom sorry guys
Click to expand...
Click to collapse
strange, how would that matter? what's the error you're getting?
Im on insertcoin 4.5.0 (ICS maybe thats the problem?) basically when i type in the code it just returns to the dialer???
Related
Update (October 7, 2010)
Use ngholson's guide to root: http://forum.xda-developers.com/showthread.php?t=581869&page=53#post8358998
Posts in the first 40 or so pages of this thread are old old old. Try browsing through the last 10 or so pages if you have any problems.
I may put a guide for using an App to root in this first post, but I don't have time right now.
OLD OLD OLD Manual Root:
This will still work, but ngholson's guide is a lot easier and you should definitely try it first.
NOTICE / WARNING / READ THESE:
1. I give no guarantees for anything that may or may not result from following these instructions (or any mistakes made).
2. Doing this will probably void your warranty, BUT as long as you don't run some other carrier's RUU (not talking about ROMs here, talking about the official upgrade files. what's important is that your hboot version doesn't change) you can always just flash your carrier's RUU to go back to unrooted completely stock.
Known issues:
NONE! This is a clean procedure that leaves your current rom as is. Any issues you have will be related to whatever ROMs you choose to flash or additional packages you choose to flash to your current rom
Steps:
1. Upgrade to 2.1
We know this works with the initial 2.1 updates, but later updates may patch it. If you have installed additional updates from your carrier, you may have to flash the original RUU to be able to root.
2. Download and extract the Android SDK
http://developer.android.com/sdk/index.html
You really only need this for the adb binary. If anyone can suggest a better way to get it than downloading the entire SDK, let me know.
3. Download and install HTC Sync
Some carriers have specific versions of HTC Sync (I know Cellular South does).
You could also just install the adb drivers.
4. Download the hack and extract it to your SDK tools directory. (or wherever you have adb)
It's attached to this post.
5. Turn on USB Debugging on your phone
Settings -> Applications -> Development -> USB Debugging
6. Plug your phone in USB
7. Run the script
For Windows this is runindos.bat. You should be able to just double click it.
That's it. This will flash the Darch version of AmonRA's recovery.
8. BACKUP
At this point you should probably backup your current stock rom (see Recovery guide below) and backup your PRL. (navalynt has good instructions on this in his root guide).
Now you can flash a custom rom or just flash the provided su.zip (see Recovery guide below) for Superuser Permissions (root) within your current rom.
Recovery
Recovery is where you can backup, restore, and flash ROMs or additional app zips.
To enter Recovery mode on your phone, power the phone off. Then hold home and press the power button. Keep holding home until you get the recovery screen.
You'll see several options, but the first thing you'll want to use is Backup.I've always used the nandroid option, not sure of the differences between it and bart. Backing up does exactly what you'd expect: copies your current ROM to your sd card. It doesn't change anything on the phone. It does take a few minutes so be patient.
Most roms will suggest you wipe first, and there is a menu option for that in recovery also. Just choose wipe, then factory reset. This does nothing to your sd card and only wipes application data (app installed from the market, settings for any app, etc).
After you've backed up, Recovery is also where you flash new ROMs or additions to your current ROM. It's easiest to pick a rom you want on your pc, and transfer it to your phone over usb. you can either do this the normal way, or if you're already in recovery, there is a USB-MS option you can use. Some Recoveries require flashable zips to be in the root of your sd card (not in any directory). After the ZIP is on your sd card, choose "install zip from sdcard" and pick the zip of the ROM you want. That's it. After it's done flashing, reboot your phone. If you wiped and flashed a full ROM, the first will take several minutes.
If you flash a ROM and either get stuck in a boot loop or just don't like it, go back into recovery under the Backup option and choose nandroid restore. Pick the option you get (it's a directory named with your phone's serial number) and you'll see a list of backups named with the date/time they were created. Choose which one you want to restore, wait a few minutes, then reboot and you'll be back to exactly where you were.
I've learned that the exploit used on the Sprint Hero doesn't work on the CS Hero because it uses mmap_min_addr. This means that exploits which rely on a null pointer dereference (like the Sprint exploit) won't work.
So here's what I think I need:
1) I'll be watching bugtraq, etc... for non null pointer dereference local kernel vulnerabilities. (I don't think I know 100% what that means yet.)
2) I also need to learn how to know if a vulnerability is applicable. Like this one http://www.securityfocus.com/bid/36834 . I don't even know really where to begin to see if I can use that.
3) Once I've found a vulnerability, how do I exploit it? I realize there will probably be proof of concept for the exploit, but how will I turn that into something that executes a specified command like asroot2 does. Is the source available for asroot2?
4) I wonder if I need to bother figuring out if the source used to build the kernel for CS is different from Sprint. Is a change in config.gz enough to legally require HTC to provide me with source specific to the CS version?
Keep up the good work
I know there aren't many of us, but I'm really hoping to root my hero sometime soon. I wish I could help but I picked my engineering field because it didn't require learning any computer languages haha
cdiamond333 said:
I know there aren't many of us, but I'm really hoping to root my hero sometime soon. I wish I could help but I picked my engineering field because it didn't require learning any computer languages haha
Click to expand...
Click to collapse
Glad to see at least one person interested enough to join XDA!
Though I'm afraid we're going to end up waiting until someone roots the Droid and/or Droid Eris and hope that works for us as well.
Can anyone give us an idea about where to find the RUU specific to Cellular South? Do those come from HTC, the carrier, or do they just "magically" make their way to the net from whoever happens to have access to them?
Really Like To See a Root
I would also like to see some success to this post as well... I have been with cellular south for years and this is the best phone they have produced! It only needs root access! Im a computer engineer a Miss. State, and I would love to see what I could do with this phone.
Maybe I could find an exploit... but it might take me longer to find it seeing that I am still in the beginning stages of my discipline.
But all I wanted to say is: LETS GET THIS ROOT!!
Root cellular south hero
I agree I have the htc hero from cellular south and would like to share the internet with my computer but cant tether unless phone is rooted
Hey guys!
I, too, am a CellSouth Hero haver... and I'm searching high and low for the procedure as well! I'll be checking back here and also searching round and posting anything I find.
If anyone gets an update, please email me at [email protected]
Help
I too own a CS hero and i am looking all over the net for a way to root this phone. if a way can be found will any roms work on it or will new CS specific roms have to be developed. If that is the case then i am afraid we CS users won't gain access to this for awhile as the customer base is quite small compared to sprint
OBSt4l0n said:
I too own a CS hero and i am looking all over the net for a way to root this phone. if a way can be found will any roms work on it or will new CS specific roms have to be developed. If that is the case then i am afraid we CS users won't gain access to this for awhile as the customer base is quite small compared to sprint
Click to expand...
Click to collapse
Well I've been surprised by the response to this thread, so hopefully there is more interest specific to CS than we may realize.
Ideally, ROMs made with Sprint Hero in mind will work on the CS Hero. I haven't put much effort into it without having root access yet, but when I get a chance I'm going to take the time to compare things like the radio image, etc and see just how much they differ from one to the other. If nothing else, hopefully we can replace the different pieces in the custom ROMs and be able to use them.
I will update this thread with what I find, and hopefully others will contribute as well.
??
Any news??
MrDanger said:
Any news??
Click to expand...
Click to collapse
I know, right? Seriously, is anyone out there?
i have posted treads at various sites, and they all get buried fairly quickly.
Would love to solve this issue... surely someone out there would find this to be a challenge worth taking up...
i hope.
Oh, and happy thanksgiving...
markachee message
Check Ur profile for a message that I left u.
It's just going to be a waiting game.
First someone has to find an exploit, most likely in the Linux kernel. This doesn't have to be something specific to our phone. It's more likely that it will be a generic thing that will work for us, Droid, and Droid Eris (as well as Linux in general).
It's not likely I'd be able to discover one of these exploits, so I'm watching for exploits coming out (bugtraq, etc) that might work for us. There really hasn't been anything at all since the pipe.c vulnerability that worked for the Sprint Hero.
Really one thing we need that we should be able to get now is an RUU specific to Cellular South's Hero. From what I understand, an RUU lets you reset your phone to a factory/updated image in the event something goes wrong. It wouldn't directly help us get root, but it would be a "safety net" for those of us screwing with our phones trying to get root.
Anything you guys could help dig up on where/how to find it would be awesome.
This looks promising. At least have some people in this thread that know enough to be able to compile for the phone:
http://forum.xda-developers.com/showthread.php?p=5034122
Also, realized I never mentioned I was looking at the "enlightenment" exploit set from http://www.grsecurity.com/~spender/
Just chiming in, had my Cell South hero for about a month and have been following this thread with the hope of seeing our phones rooted. I am a technician/admin with some coding and linux experience, but I am unfamiliar with rooting cellphones. anything I can do to help let me know.
tether
you can usb tether useing pda net from the market without root
I have seen pda net, i'm not interested in just tethering but thank you.
mine comes in tuesday
markachee said:
This looks promising. At least have some people in this thread that know enough to be able to compile for the phone:
http://forum.xda-developers.com/showthread.php?p=5034122
Also, realized I never mentioned I was looking at the "enlightenment" exploit set from http://www.grsecurity.com/~spender/
Click to expand...
Click to collapse
Here's the compiled programs within that exploit
Hi guys,
I've been looking but couldn't find an easy answer. Is there a way to screen capture on the Sensation?
Thanks in advance!!!
I got this from the Incredible S forums:
1.Download Android SDK (zip one)
2.Download and Install Java JDK 6
3.Connect phone to PC in debugging mode
4.Where you have extracted Android SDK, go to the tools folder and open ddms.bat
5.Click on the device tab and click screen capture.
6.Capture and save
Any way to do it WITHOUT using a PC?
Toeeknee said:
Any way to do it WITHOUT using a PC?
Click to expand...
Click to collapse
Yes this is what I wanted to know. Isn't there a way to just do a capture and have it saved to your phone without a computer?
Here you go
https://market.android.com/details?....screenshotitfullnoroot&feature=search_result
nothing come for free!!
not without root if you don't want to be tethered to a pc
prateekgujral said:
Here you go
https://market.android.com/details?....screenshotitfullnoroot&feature=search_result
nothing come for free!!
Click to expand...
Click to collapse
i tried the free version of this app , which also stated NO ROOT and it didnt work !!
Dandandroid said:
i tried the free version of this app , which also stated NO ROOT and it didnt work !!
Click to expand...
Click to collapse
u could try this paid one.. maybe it works.. and if it doesnt.. u can always uninstall and claim refund (i think within a certian time frame)
So I go to the HTC Sensation support page and I see that under mechanical I see this issue (sorry I tried to post a link but I guess I'm too new for the forum to let me...something about avoiding spam...).
The second question is my question, is it not? But I can't seem to make is work. Anybody else try this?
*EDIT*
I went to the HTC website's forums and they said that this was some sort of misinformation. This feature currently does not exist even though it came from HTC themselves! Someone did state, though, that there is supposed to be an update soon that MIGHT have this feature...not sure if that also includes unlocking the boot loader!
Introduction: It has come to my attention that many of us windows users are still using odin for upgrading to Ginger bread and recovering from soft bricks. I have found the heimdall one click method is easier to use and more stable for flashing your phone from a computer. I am trying to make this guide as noob proof and simple as possible. Given how simple the one click method is it should not be hard (although if you are new to this device it can prove to be difficult if you don't read and understand everything).
Please be sure to format your sd card if this is the first time you are flashing ginger bread. If you have problems converting to ext4 using one of the rooted one clicks it is suggested you create a 2048 partition in cwm.
The first five steps are to help get heimdall and everything needed to use it installed on your windows computer. If you already have heimdall you can skip to steps 6&7.
Please read everything in this guide before proceeding and be sure to read everything else mentioned in this guide. proceed slowly if this is your first time. I recommend a print out, double check everything, and cross off each step as you go. Slow and methodical = smooth = fast and efficient with perfect results. Remember the best way to gain knowledge and learn to do almost anything is to READ.
If you have used the one click method and have any suggestions for this guide please feel free to comment.
Disclaimer: You are flashing your device at your own risk. No one but you can be held responsible if you make a mistake. Some one click packages contain bootloaders and flashing incorrect bootloaders may hard brick your device. Never flash a one click package that is not clearly labeled for your device by model number.
Warning: if you are on a Mac running osx 10.5 or higher there is a problem with the re partition function in heimdall. since you must flash boot loaders these packaged are designed to re partition automatically. It is recommend you use a windows or Linux parallel to flash.
On to the guide:
1: first you will need to download and unzip the lastest heimdall front end. This package can be found at http://www.glassechidna.com.au/products/heimdall/
Please read and understand everything that this website has to offer about the program before use.
2: after you have unziped the heimdall front end package open the containing folder and click on the "Read Me" text file. This file contains troubleshooting tips, driver installation, installation procedures, and instructions for flashing other heimdall supported files to your device. Oh yeah and they don't call it Read Me for nothing
3: you will also need to download and install the package labeled "Microsoft Visual C++ 2010 redistributables" and get java 1.6 do I have Java?. Simply download and run (double click) the executable files.
4: Once you have downloaded and unziped heimdall front end, installed java 1.6, and installed the C++ packages you will need to install your device drivers (this process is also explained in the read me file you should have read).
A: Place your device into download mode and plug it into your computer. How to get into download mode
B: Open the unziped heimdall folder then open the the "drivers" folder and run (double click) the "zadig" application
C: Click the "options" menu and make sure "list all devices" is checked.
D: from the drop down menu choose "Samsung USB composite device"
E: Click the "install drivers" button and let it do its thing.
Note: if you have trouble installing drivers try again. If "Samsung USB composite device" is not an option unplug your device re run zadig and take note of what options have disappeared.
5: Now it is time for you to choose your one click package. If you would like help choosing the package that is right for you please feel free to ask.The threads I am linking to are only for the Samsung Galaxy S 4G device from T-Mobile, Model# SGH-T959V. If this is not your device do not flash the one click packages I am linking to. If this is your device these are the ONLY one click packages available. Again, never flash a firmware package not clearly labeled with the exact same model number as the device you are flashing to.
Choose and download the one click package of your choice. Remember to read the OP of each thread before making your decision. If you have a question feel free to ask here.
A: kj6 one click collection
This thread contains three one click packages to choose from. All are from the official Galaxy S 4G Ginger Bread Upgrade to 2.3.6 or KJ6. Read the OP to choose the one that is right for you.
B: kf1 one click package
This was the first one click package we obtained for the Samsung Galaxy S 4G. It was from a leaked version of gingerbread 2.3.3 or KF1. I, and Most, do not recommend you use it because the boot loaders change the button mapping for recovery and download modes (this can cause problems trying to revert) ;but, I would like to give credit to the creator of the one click packager and will include his thread and work as such.
6: Now that you have installed heimdall and chosen a one click package its time to flash. Close your heimdall folders and forget about them for now. put your device in download mode and connect it to your computer How to get into download mode
A: Run (double click) your "oneclick.jar" package. Yes, they are supposed to be executable files (be patient it may take a minute to load)
B: Read the "package information" section and ensure you are flashing a one click package designed specifically for your device by model number.
C: do nothing else except click "flash"
D: wait for device to reboot
E: If you are upgrading to GB from froyo do not close your "oneclick.jar". You will need to repeat step 6 a second time with the "flash bootloaders" box checked. Please also ensure you have read the disclaimer.
7: At this point your device will be in one of these three states
A: rebooted and running as factory
B: in the stock Samsung 3E blue recovery in which case you should use the volume buttons to navigate to reboot device and use the power button to select reboot device
C: In a CWM recovery where you should use the volume buttons to navigate to reboot device and use the power button to select reboot device.
That's It! Happy flashing!
Credits
Benjamin Dobell - Creator of heimdall
Adam Outler - creator of the one click packaging system
Bhundven - For assembling the kj6 update packages for the t959v
Fbis251 - wiki links and general support
odin vs. heimdall comparison
Most of us here are used to Odin and can make it work; however, it is an unstable, proprietary, windows only, unsupported program. It often will not recognize your device or you get a better experience with v 1.7 or v 1.85 or maybe it is just picky with your computer or device. I had both the above mentioned versions installed on my desktop in case I had problems with one or the other. This, to me, is totally unacceptable. Now we have heimdall and I encourage you to make the switch. It is an ongoing project that is cross platform, supported, and open source. This means it is based on the same fundamentals as Android proving any developer the opportunity to help make it better, faster, or more user friendly. Take the one click project for example: now, with heimdall installed on your system, you can simply execute a pre programmed flash and your done with your device flashed as the developer intended. I admit it is a few clicks not just one but, it hasn't given me any problems, it tells me exactly what it's doing in a language I understand, and it is super easy. So at least give it a shot, bet you will like it
NICEEEEE!
Sent from my SGH-T959V using xda premium
Choosing the right driver
Hi there,
I don't see the Samsung USB Composite Device in the drop down box when running Zadig. What I have is below:
Samsung_Android
CDC Abstract Control Model (ACM)
Android UMS
S3C6410 Android ADB
Driver failed to install for Samsung_Android. Should I try any of the other options?
Thanks for helping a bricked noob out!
R
mandogand said:
Hi there,
I don't see the Samsung USB Composite Device in the drop down box when running Zadig. What I have is below:
Samsung_Android
CDC Abstract Control Model (ACM)
Android UMS
S3C6410 Android ADB
Driver failed to install for Samsung_Android. Should I try any of the other options?
Thanks for helping a bricked noob out!
R
Click to expand...
Click to collapse
Was your phone in download mode?
Unplug your device and re run zadig. Take note if any options disappear. If so re plug your device and try it. If not report back.
Sent from my SGH-T959V using XDA App
Sticky!
Sent from my SGH-T959V using XDA App
its honestly the far superior option and comeing from a linux based world where i dindt have to deal with odin as much Its great tried odin on windows and really its far superior and alot more stable then odin.. its worth learning tbh
Further adventures in un-bricking with Heimdall
Thanks for your quick replies!
1). I was able to get the driver installed, using the Samsung_Android. When I connect the phone it now shows up in the device manager. Picture 1 attached (libusb - Samsung Android).
2). I'm not sure what mode my phone is in. When I press the power button I get first the startup screen....Picture 2.
Then I get this screen "Android System Recovery 3e" and a range of options. The volume control is flipped i.e pressing down causes the menu to go up. (Picture 3)
There is no way to "select" any of the options. Only one of the buttons at the base of the screen seems to work: the menu button causes the text on the screen to disappear and only leaves the green android with triangle exclamation point. (Picture 4)
Heimdall does not detect that the phone is connected....Picture 5.
Any suggestions what I should try next? This is a Galaxy S 4G t959V.
Thanks so much for all your help! What an introduction to the world of Android!
M
mandogand said:
Thanks for your quick replies!
1). I was able to get the driver installed, using the Samsung_Android. When I connect the phone it now shows up in the device manager. Picture 1 attached (libusb - Samsung Android).
2). I'm not sure what mode my phone is in. When I press the power button I get first the startup screen....Picture 2.
Then I get this screen "Android System Recovery 3e" and a range of options. The volume control is flipped i.e pressing down causes the menu to go up. (Picture 3)
There is no way to "select" any of the options. Only one of the buttons at the base of the screen seems to work: the menu button causes the text on the screen to disappear and only leaves the green android with triangle exclamation point. (Picture 4)
Heimdall does not detect that the phone is connected....Picture 5.
Any suggestions what I should try next? This is a Galaxy S 4G t959V.
Thanks so much for all your help! What an introduction to the world of Android!
M
Click to expand...
Click to collapse
You are currently in recovery mode running whatever bad boot loaders you flashed. Use this method to enter download mode
1 pull out battery
2 hold Vol up Vol down at the same time
3 plug USB cable into phone and computer
4 re insert battery and continue to hold both Vol buttons until your phone displays something.
unfortunately it is possible the bad boot loaders you flashed may have messed up your button mapping. if you try the above mentioned method for download mode multiple times and only end up back in the same recovery screen please direct me to the thread you flashed the bad boot loaders from
Good luck
Sent from my SGH-T959V using XDA App
How to get into download mode
FBis251 said:
How to get into download mode
Click to expand...
Click to collapse
Thanks for that link fb. Will add this to the OP in a bit. Maybe we should edit the wiki to show pictures of download mode since we have found a couple different screens other than the one mentioned. Oh crap taking my own thread off topic
Sent from my SGH-T959V using XDA App
More Heimdall recovery....
Cool. OK followed instructions and now have a screen as below:
What next?
M
More Heimdall recovery....
Hit the up button and now get the digging android icon (Digging)...what next experts! You guys rock by the way!
Thanks!
M
Bassmanjames said:
Thanks for that link fb. Will add this to the OP in a bit. Maybe we should edit the wiki to show pictures of download mode since we have found a couple different screens other than the one mentioned. Oh crap taking my own thread off topic
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Yup, anyone can update the wiki I'm going to add guides little by little into it so we can just link new users to it. I realized after typing for the 20th time how to get into download mode that it'd be easier to just use the wiki.
mandogand said:
Cool. OK followed instructions and now have a screen as below:
What next?
M
Click to expand...
Click to collapse
Is it fine if we use your picture in the wiki? People would really appreciate it.
Now that you're in download mode you can use the one click to recover your phone.
Please feel free to use any or all of the pictures!
My utmost thanks to you guys! The "experts" at tmobile basically told me that i had a paperweight and would need a new phone!
M
mandogand said:
Please feel free to use any or all of the pictures!
My utmost thanks to you guys! The "experts" at tmobile basically told me that i had a paperweight and would need a new phone!
M
Click to expand...
Click to collapse
Well with bad boot loaders you might have.
So success?
Sent from my SGH-T959V using XDA App
Just got back. I just flashed it using the file below and put a check mark on the bootloaders.
The file I'm using is from this thread:
http://forum.xda-developers.com/showthread.php?t=1358498
pics attached. However, now the phone seems to be dead and I can't even turn it on....
I did leave the phone connected to USB and it was showing the downloading screen for the 2 hours while I was away...
What now?
Thanks,
M
mandogand said:
Just got back. I just flashed it using the file below and put a check mark on the bootloaders.
The file I'm using is from this thread:
http://forum.xda-developers.com/showthread.php?t=1358498
pics attached. However, now the phone seems to be dead and I can't even turn it on....
I did leave the phone connected to USB and it was showing the downloading screen for the 2 hours while I was away...
What now?
Thanks,
M
Click to expand...
Click to collapse
Do me a favor and pull your battery. post a pic of the device info but edit out your imei number
Sent from my SGH-T959V using XDA App
Here you go.
Serial end with a W.
Thanks,
M
DISCLAIMER
This tool is only to be used to restore your original MEID/IMEI, this tool is not to be used for anything other then that, by downloading this tool YOU agree that you will only be using it to restore a damaged MEID/IMEI. XDA, FTT, I or anyone else is not held accountable for actions that you might consider doing. Any talk of "Cloning", 'Changing" etc will be reported and immediate ban AS THIS IS YOUR ONLY WARNING. So please avoid this. There should be no reason you don't see this, its the first thing you see when reading the thread.
What this is for
Some users when installing a rom, recovery or unlocking the bootloader experience a lose of there IMEI and or ERI. This tool is designed to help them recover it, specially in the case where they didn't make any prior backups.
PLEASE NOTE
If this does not work for you, you can try to use this code in the dialer *2767*3855# using a stock rom. To see if it will factory reset your device.
You may also try ##RTN# to reset device, this will erase all settings and data from the device. In order for this code to you work you must be on a stock touch wiz rom and enable hidden menu.
Prerequisites
Windows XP, Vista, 7 or 8 64bit or 32bit
Microsoft DotNet 3.5 Installed.
Diagnostic Drivers Installed
How To
You must enable the diagnostic port on your device. If you are on a TouchWiz based rom follow TouchWiz Diag else follow ASOP Diag.
1. Find your IMEI under the battery on the device, you should see a sticker. Copy the IMEI down and power on the device.
2. Connect the device to your computer and open "Device Manger"
3. Check under "Ports" and Look for Samsung and Note the Comport it is on.
4. Open the software and under comports select the comport number you found your device on then click connect.
5. Check the IMEI number of to the left, and note the ERI message. If it is red and says your ERI is missing or not found. Please do both methods.
6. If your ERI is not found, click on "Repair" in the ERI section, if your IMEI is missing, when asked to reboot click "NO" other wise click yes and you are done.
7. Type your IMEI in the IMEI box, Do not worry about MEID it will auto fill once IMEI is typed.
8. You will notice that the last number is added automatically this is done using the Luna Algo and is a checksum number.
9. Once you have typed your IMEI click on "Repair" in the IMEI section, once the repair is done your phone will auto reboot.
10. Please check your ERI and IMEI under Settings/System/About/Status. Your IMEI should appear and ERI version 5 should be there.
Thats it you should not be roaming anymore and your IMEI successfully repaired.
TouchWiz Diag
1.) Bring up the Dial Pad on the phone
2.) Press *#22745927
3.) When the "Enable/Disable Hidden Menu" comes up
tap where it says "Hidden Menu Disabled".
4.) Select "Enable" on the popup.
5.) Select "OK"
6.) Press the "Home" key to return to the home screen.
7.) Bring up the Dial Pad on the phone
8.) Press **87284 (USBUI)
9.) On "PhoneUtil" make sure "PDA" is selected.
10.) Select "Qualcomm USB Settings"
11.) Select "DM+MODEM+ADB"
12.) Select "OK"
Note:You can also use "Casual" and invoke the PhoneUtil menu directly.
AOSP Diag
Using adb. or terminal
Execute DiagMode.sh
Code:
echo 0 > /sys/class/android_usb/android0/enable 0
echo smd,bam > /sys/class/android_usb/android0/f_rmnet/transports
echo diag > /sys/class/android_usb/android0/f_diag/clients
echo 1 > /sys/class/android_usb/android0/f_acm/instances
echo rmnet,acm,diag > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
To return to normal
Execute MTPMode.sh as root
Code:
echo "" > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun_ex/file
echo 0 > /sys/devices/virtual/android_usb/android0/enable
echo "mtp,acm,adb" > /sys/class/android_usb/android0/functions
echo 1 > /sys/devices/virtual/android_usb/android0/enable
vold
Video How To
How To Upload ERI using Revskills
Manual Method / How This Works
The IMEI part is complex and I wont go into detail on that at all. If you dont have access to a windows machine, then I'm sorry but most of the avail tools that will allow you to repair IMEI is going to be Windows based and you can use a virtual machine. Not with my tool but others. This is mostly going to be focused on the ERI it self.
The ERI is binary file that is stored on the QCOM chipset, this is the primary file the "Radio" and the device use in order to determine certain functionality of the device.
This is stored as /nvm/eri_0 on the QCOM's EFS. You can use QPST EFS Explorer all though it will probably crash, or some other EFS explorer for Qualcomm chipset's.
I have uploaded the original eri_0 file to this forum. All you have to do is download it. User QPST or Bitpim, Revskills, and upload the file to /nvm/eri_0 you can leave it's permissions as 666 or chmod the permissions to 777 your choice the phone will read it either way.
The /nvm/eri_0 that is uploaded to this forum comes from a stock s3, although its the same ERI file Verizon has been using forever. Thats all this tool does. Simply fix's the IMEI and uploads a good eri file to the correct directory.
Questions and Answers
Q) Do I need to do anything special first like back up any part of my phone or anything ?
A) No, as long as you can enable diag port you can restore your IMEI, just look on the back of your device under the battery for your original IMEI. I STILL ADVISE YOU TO BACK UP using this method here http://forum.xda-developers.com/showthread.php?t=1852255
Q) Can this change IMEI?
A) Its purpose is not to change IMEI doing so is illegal and any talk about changing the IMEI will be reported and you may be banned. I advise against it as it could cause unknown issues.
Q) Can you share how this works.
A) No, sorry my position, my family and my job comes first and this would put me in a bad position.
Q) Can you just tell me in pm.
A) No so dont bother asking.
Q) My phones says Roaming and show roaming icon will this fix it ?
A) Yes this should be able to fix that issue, it does that by uploading the ERI back to the QCOM chipset.
Q) Should I / Do I have to donate ?
A) No, you don't need to donate, and I don't want you to fell you need to. Your donation could go to something else EFF, Adam Outler, XDA, Poor kids in any country, some other foundation. If you feel you would like to donate to me you can, I wont stop you and I wont ask you to.
Credits
Not sure who all to credit if you feel your name should be here Just tell me and why and Ill post it here. I did not read any of the other forum really, but ill list who i have seen and who as helped me identify it was the ERI
Also no particular order
Adam Outler - For everything he does, I watch a lot of his videos.
WildZontar - For his thread, not sure if its his info or just info collected. - http://forum.xda-developers.com/showthread.php?t=1852255
TrevE - For what he has contributed, looks like a lot very knowledgeable person
Jay Evans - For doing the initial tests
BillBauman - Discovered the missing ERI
GerardAnthony - For the AOSP mode scripts
Again, for these people as well, I didn't read the whole thread etc to see everything they contributed. If someone would or if they would / want me to update it please ask to me to update so I can give credit where its do.
amoamare said:
This tool will help you restore your IMEI back to your device. Its about ready. I'm a little tired but I will have it up shortly
Click to expand...
Click to collapse
waiting
Exe has been added.
I gotta give you props just for making your own IMEI all 9's, i would never do that on purpose.
Have to make sure it works as intended lol. I'm not to worried as I know I can restore from it.
the program force closes on me when i try to open it is there something wrong with it? i tried downloading it again and it does the same.
Whats the error you are receiving and are you sure you have at lest 3.5 Dot net installed ?
amoamare said:
Whats the error you are receiving and are you sure you have at lest 3.5 Dot net installed ?
Click to expand...
Click to collapse
ya it could be just something messed up with my computer. im trying to redownload it again and update .net and see if it helps
Does this have the roaming glitch?
What roaming glitch ? Sorry not familiar with that. This doesn't modify anything other then the IMEI
amoamare said:
Whats the error you are receiving and are you sure you have at lest 3.5 Dot net installed ?
Click to expand...
Click to collapse
i updated to 4.5 and still it says program has stopped working and self quits.
same...heres a pic...windows 7 64bit. Ran in compat mode for xp as admin, same error. I am fully updated.
edit: I looked into the app, and you have problem with kernelbase.dll
Ok one sec ill recompile again, one reason i really hate C# haha i think i know what it is
Please re-download should be v2. I forgot to compile a dll with it, so should work now.
sweet dude...yea looks like a faulty dll. Nice program though...I deleted my esn/meid/iemi to see if I could restore earlier today and figured out how but one program would save a lot of steps. Many thanks.
Edit: works!!
amoamare said:
What roaming glitch ? Sorry not familiar with that. This doesn't modify anything other then the IMEI
Click to expand...
Click to collapse
It is where it shows that your roaming, Its a Graphical Glitch.
fr8cture said:
It is where it shows that your roaming, Its a Graphical Glitch.
Click to expand...
Click to collapse
We sure its just a graphical glitch?
Sorry if this is a stupid question. Flame me if you must.
Is it possible to port this to another device or edit to make it compatible. I personally don't need it, but anyone with a lost imei would find it immensely useful. As you can see from my sig I have an att galaxy s2 skyrocket. Thanks for your time.
In case you were wondering this thread showed up in the unread list when I opened the xda app
------------------------------------------------
Sent from my Skyrocket i727 running AOKP JB
For a one stop shop are Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398
Mike on XDA,
It's possible but it would have to be written for that device, meaning I would have to have test device or some way to check stuff.
Damn, this is legit man. Thanks so much for making this tool. I have yet to lose mine, but I'm sure it'll happen at some point.
Much appreciated, booted up just fine on win8 rtm. This is the stuff legends are made of haha.
Sent from my SCH-I535 using xda premium
Hello,
I'm trying to recover the IMEI for my T869 by following this guide:
http://forum.xda-developers.com/showthread.php?t=1867442
The first step is to put the phone/tablet in diagnostics mode. There are two methods described which do this. The first one ( for TouchWiz devices, which should apply for this device ) involves using codes in the dialer to enable a hidden menu. As my tab doesn't have a dialer, this method doesn't work. I've tried 3rd party software that claim to execute codes on the tablet but they don't work.
The second method involves running a script. This fails because/sys/class/android_usb/android0/f_rmnet/transports doesn't exist on my tablet.
So, any ideas how to put my tablet in diagnostics mode or how to fix the IMEI for it ? I don't have a backup of the efs folder and the current IMEI is the generic 004999010640000.
Thanks.
MichaelIvinov said:
Hello,
I'm trying to recover the IMEI for my T869 by following this guide:
http://forum.xda-developers.com/showthread.php?t=1867442
The first step is to put the phone/tablet in diagnostics mode. There are two methods described which do this. The first one ( for TouchWiz devices, which should apply for this device ) involves using codes in the dialer to enable a hidden menu. As my tab doesn't have a dialer, this method doesn't work. I've tried 3rd party software that claim to execute codes on the tablet but they don't work.
The second method involves running a script. This fails because/sys/class/android_usb/android0/f_rmnet/transports doesn't exist on my tablet.
So, any ideas how to put my tablet in diagnostics mode or how to fix the IMEI for it ? I don't have a backup of the efs folder and the current IMEI is the generic 004999010640000.
Thanks.
Click to expand...
Click to collapse
The Dialer is part of Phone.apk, which won't show up on the T869 normally even if its "installed".
There's a file within framework-res.apk (which is found @ /res/values/bools.xml) which essentially tells the Android OS what features the host device does and does not have. The relevant value is <bool name="config_voice_capable">.
By default the T869 will have:
<bool name="config_voice_capable">false</bool>
Changing that to
<bool name="config_voice_capable">true</bool>
Tells the OS that the device is "voice capable", meaning it can make & receive phone calls. This will then allow the Phone.apk features to show up, provided you have Phone.apk installed.
The process of modifying framework-res.apk is somewhat complicated, and your ROM may or may even have Phone.apk present, depending on what you are using. However, at least now you know why you have no dialer.
DivinityCycle said:
The Dialer is part of Phone.apk, which won't show up on the T869 normally even if its "installed".
There's a file within framework-res.apk (which is found @ /res/values/bools.xml) which essentially tells the Android OS what features the host device does and does not have. The relevant value is <bool name="config_voice_capable">.
By default the T869 will have:
<bool name="config_voice_capable">false</bool>
Changing that to
<bool name="config_voice_capable">true</bool>
Tells the OS that the device is "voice capable", meaning it can make & receive phone calls. This will then allow the Phone.apk features to show up, provided you have Phone.apk installed.
The process of modifying framework-res.apk is somewhat complicated, and your ROM may or may even have Phone.apk present, depending on what you are using. However, at least now you know why you have no dialer.
Click to expand...
Click to collapse
I actually did follow your guide here: http://forum.xda-developers.com/showthread.php?t=1872348 to try to get my native dialer but never got it to work. I know that it should work, but I get endless crashes/reboots if I enable voice capabilities for my tab .. All apps crash seconds from startup. What exact ROM do you have which works for enabling the native dialer? I'm running the official ICS build.
MichaelIvinov said:
I actually did follow your guide here: http://forum.xda-developers.com/showthread.php?t=1872348 to try to get my native dialer but never got it to work. I know that it should work, but I get endless crashes/reboots if I enable voice capabilities for my tab .. All apps crash seconds from startup. What exact ROM do you have which works for enabling the native dialer? I'm running the official ICS build.
Click to expand...
Click to collapse
I pretty much only use CM10. Aorth has nightly builds of it. The last "good" CM10 is cm-10-20130118-UNOFFICIAL-t869.zip, which you can get here: http://goo.im/devs/aorth/roms/t869/
I'm curious, what purpose does retrieving the IMEI serve anyways?
DivinityCycle said:
I pretty much only use CM10. Aorth has nightly builds of it. The last "good" CM10 is cm-10-20130118-UNOFFICIAL-t869.zip, which you can get here: ....
I'm curious, what purpose does retrieving the IMEI serve anyways?
Click to expand...
Click to collapse
Well my tablet has the generic IMEI as stated above. Since about 2 days ago, my tablet hasn't been able to connect to the T-Mobile network. I have had the generic IMEI for some time and it has worked. Now either T-Mobile has decided to start blocking the IMEI from the network or my tablet is physically damaged.
I have bars, I can search for networks and it will find T-Mobile and AT&T, I've tried different SIMs with different plans and also checked the SIMs in other phones and they work. Can you connect to the T-Mobile network with the generic IMEI or do you still have your original IMEI?
MichaelIvinov said:
Well my tablet has the generic IMEI as stated above. Since about 2 days ago, my tablet hasn't been able to connect to the T-Mobile network. I have had the generic IMEI for some time and it has worked. Now either T-Mobile has decided to start blocking the IMEI from the network or my tablet is physically damaged.
I have bars, I can search for networks and it will find T-Mobile and AT&T, I've tried different SIMs with different plans and also checked the SIMs in other phones and they work. Can you connect to the T-Mobile network with the generic IMEI or do you still have your original IMEI?
Click to expand...
Click to collapse
I appear to have my "real" IMEI. I have used CM10 nightlies on this tab pretty much since day 1. Have had no problems connected to the T-Mo data network. I would imagine if the IMEI is messed up you should be able to RMA that device, which sucks
find an app called 'any cut' this will allow you to access all the intents and action your device is capable of.
One of them should be service mode.
be careful....
also , if you really want this I would definetly talk to these guys.. http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-plus-imei-efs-repair/
JTAG'd my GT-P6200. I know yours is the Tmobile variant, but he usually has success with new products, etc.
I would ask him.
He is in Texas US of course..
good luck..
Ok, It's confirmed: T-Mobile has started blocking the generic IMEI from their network. At least that's what I conclude from finding a thread on reddit(can't link but you can google the title) from 3 days ago, exactly when I started having the problem:
Anyone else running a custom ROM and have your IMEI reset to 004999010640000? T-Mobile likely blocked your phone today.
DivinityCycle, Just checked again and your bools.xml edit only works with CM10. I've gotten it successfully going on CM10, but the code that gets entered in the dialer only works on a TouchWiz ROM, as noted in the original thread :facepalm:
When I try the same thing on stock GingerBread / ICS I get endless application crashes / freezes so that basically i can't do anything, even launch an app, not to mention enter a code.
chrisrotolo, AnyCut - Managed to install it and create a shortcut to the ServiceMode action but when I execute that shortcut it crashes and nothing happens.
Any other tips?
you could also try factory mode, which will bring up a calculator.
From there enter the *#*# dialer code to get you into service mode...i forget it off hand but i have posted it numerous times,
also if you try another action shortcut, one that is a submenu of the service,mode main menu, such as network, etc.. and that works, you can usually back all the way up to the main menu in service mode.
also CM ROM may have these .apks removed... should be on stock ROM though.
good luck.
chrisrotolo said:
you could also try factory mode, which will bring up a calculator.
From there enter the *#*# dialer code to get you into service mode...i forget it off hand but i have posted it numerous times,
also if you try another action shortcut, one that is a submenu of the service,mode main menu, such as network, etc.. and that works, you can usually back all the way up to the main menu in service mode.
also CM ROM may have these .apks removed... should be on stock ROM though.
good luck.
Click to expand...
Click to collapse
Factory mode worked for me but did not solve my problem. I managed to put the tablet in "modem" USB mode which from what I understand should be diag mode, what I'm looking for, but Windows( All: 7, XP, 32, 64 ) can't find drivers for it. It's showing up as 7 CDCs.
Anyone have any suggestions or knows what "7 CDCs" is and how do I get to an actual working diag mode from that ?
I dialed *#7284#, got this :
i.imgur.com/5W2HSlN.jpg
for drivers, usually you can dowload heimdall and go to 'zadig' (or something similar), with device in download mode: double click zadig.exe it will install drivers
you should see at least one CDC driver possibly a modem driver as well.
Alternatively another good way to install drivers for me has been PDAnet by june fabrics.
find it download .apk it pretty well walks you through set-up.
Thats the right screen for setting usb to modem, etc..
I've had 2 backup's of my EFS folder since day one.
chrisrotolo said:
for drivers, usually you can dowload heimdall and go to 'zadig' (or something similar), with device in download mode: double click zadig.exe it will install drivers
you should see at least one CDC driver possibly a modem driver as well.
Alternatively another good way to install drivers for me has been PDAnet by june fabrics.
find it download .apk it pretty well walks you through set-up.
Thats the right screen for setting usb to modem, etc..
I've had 2 backup's of my EFS folder since day one.
Click to expand...
Click to collapse
Thanks for the suggestions, but I couldn't get them to work. PDAnet requires that the device be put in regular-ADB mode to install drivers - and does install 'normal' drivers but doesn't install the diag mode drivers. zadig installs a driver for the 7 CDCs device but It's listed as a USB device, not as a COM serial port as required by the application.
chrisrotolo said:
I've had 2 backup's of my EFS folder since day one.
Click to expand...
Click to collapse
Do you really need the extra one or can I have it ? :silly:
Still no success so far.
The only possibility I see Is doing a restore using NsPro, which apparently is the only software that supports the T869.
NsPro v6.5.2 released:
-Added I547, T869, T879 support.
Anybody knows how I can try to fix the tab with NSPro without buying the box + 1 year activation ?
Yeah send it to someone who has one...
Have you contacted mobiletechvideos.com yet? They are US based, but one of the best for these types of things..
chrisrotolo said:
Yeah send it to someone who has one...
Have you contacted mobiletechvideos.com yet? They are US based, but one of the best for these types of things..
Click to expand...
Click to collapse
Thanks, didn't know about them. It seems that they require that the device be shipped.
Has anybody dealt with them before ? How reliable are they / where are they located ?