Database Info

[How to] Restore a semi-bricked Epic or any software issue. Restores BML from MTD too

PLEASE READ THIS FULL POST BEFORE FLASHING
I continue to put a lot of effort into making this post to help YOU so please help YOURSELF by reading it all!​
If this solves your problem please consider donating as I continue to put a lot of effort into keeping this current and up-to-date! Thank you!
These instructions should fix your semi-bricked or broken phone as long as you can get it into download mode. Make sure you have drivers already installed on your Windows computer before starting.
A NON-STOCK microUSB CABLE IS REQUIRED AS STOCK FAILS THE MAJORITY OF THE TIME
If you need drivers or the ones you have don't work you can use these:
32-bit drivers 64-bit drivers
Things you will need to restore your phone are below.
BY PERFORMING THESE STEPS ALL DATA ON YOUR PHONE WILL BE WIPED AND IT WILL BE RESTORED TO FACTORY STATE. I ASSUME NO RESPONSIBILITY IF THIS DAMAGES YOUR PHONE OR DOESN'T FIX IT. DO AT YOUR OWN RISK
A Windows Machine is required for using Odin. If you don't have a Windows machine see second post.
Download and use this version of Odin: Odin 1.85 and pit file Thanks to iNsAn|tY for hosting1
Download this tar: SPH-D700-EL30-8Gb-REL.tar.md5 Provided by K0nane
Mirror 2 Provided by iNsAn|tY
or
SPH-D700-FC09-8Gb-REL.tar hosted by kennyg123
MD5 sum:6426b89638df4e3dcf6e19b8f79cdcf0
Set up the software:
Extract the Odin3 v1.85.zip
Run odin3 v1.85.exe
Make sure the following boxes are checked (they should already be checked):
Re-Partiton, Auto-reboot, F. Reset Time
Click PIT and select the victory_8G_100528.pit that you extracted from the Odin zip.
Click PDA and select SPH-D700-EL30-8Gb-REL.tar.md5
Put your phone in Download Mode:
Make sure the USB cord is unplugged
Remove the battery and microSD card
Plug the phone into Computer (the phone may display a battery on the display this is normal just ignore it and go to the next step)
Hold down the "1" key and the power button.
The phone should now be displaying a Yellow Triangle with Downloading... (see end of post for image of download mode)
Under ID:COM, the box should turn yellow and contain the com port. If it doesn't see Troubleshooting at the end.
Odin should now look like this (screenshot shows EB13 but is the same for EL30):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Full-size Image
Now you should be able to click Start.
Your phone should try and auto-reboot when finished.
The phone can't boot normally without the battery but you can safely unplug it from the computer install the battery and turn it on.
You phone should be working 100%!
This has worked on numerous phone that have partition issues, intermittent booting issues, and many other file system issues. This also fixes the Samsung Logo disappearing from boot.
While some people claim that the re-partition and time reset should not be checked, this guide is designed to fix ALL problems. While using Odin on your phone has some inherent risk and is slightly less risky to not re-partition the phone some phones will not be fixed without this and that's why it is included. You can try following the above steps and only checking "reboot" but you may have to reflash and check the boxes in the instructions if you phone still has problems.
Troubleshooting:
Phone not getting in download mode
While holding down 1 and power insert the battery before trying to connect the USB cable​Odin isn't detecting the phone?!
Try a different USB PORT on the computer.
Normally only the USB port the drivers were installed to and the phone was plugged into when they were installed will work (easily anyway)​Try a different USB cable
If you are using the stock cable it is almost certainly NOT going to work. You can get a cheap BlackBerry USB cable off of Amazon for a couple bucks and works like a charm.​Uninstall the drivers, reboot, and reinstall the drivers​Try Odin v1.61​It seems frozen and hasn't made any progress for 15 minutes
factoryfs.rfs takes awhile but if it stays on that for longer than 15 minutes unplug the phone and start over​It started flashing but part way through the download mode screen went away and it just shows a color (can be different colors each time)
This means that it got disconnected during the transfer. Try again if that doesn't work try a different USB cable.​You get a big red failed and tried the above steps.
Before you try to reflash make sure to copy the log that Odin makes in the bottom left hand portion of the screen so we can help you troubleshoot and then post in this thread.​Still not working?
Try this tar SPH-D700-EC05-8Gb-REL.tar provided by K0nane​
Here is a picture of Download Mode if you aren't sure what it looks like:
This has worked on all phones that were able to get into download mode. If this works for you or if you have issues let me know! You can message me on Irondust formerly Fossnet in #epic my nickname there is Cyc
Click here to chat with me in IRC
Special thanks to K0nane and iNsAn|tY hosting and providing the EL30 tar and Odin.
Even though there are other guides how to do this I wanted something that was a little more concise and easier to follow. If you prefer qbking77 made a How-To Video to restore your phone. He uses different files and such but the end result is hopefully the same so check that out if you prefer or if you are confused and want to see the steps.
Forum Post for other How-ToVideos by qbking77
May need this again but can't remember the URL NO PROBLEM http://tinyurl.com/epicfix directs here!

Heimdall Section for users having trouble with Odin or do not have Windows PC will be added shortly. Below is mordant23's post that I am putting here in the mean time. My post will feature the gui as the main interface and give options for all supported operating systems. Until then thank you mordant23 for allowing me to use this in the opener:
mordant23 said:
I had to flash back to stock after I switched to Linux. I couldn't find an easy guide. In case this helps someone else, below are the steps I took. If this is useful, could this be added to the original post or would it be better if I start a new thread?
The steps should be adaptable to OS X, but since I don't use OS X I can't really write instructions with confidence. Perhaps someone else can?
Note: Everyone's linux distributions are different. For the instructions I'll use generalized descriptions of steps. The only specific instructions I'll give is for using Heimdall. I am not a linux guru nor am I an Epic 4G expert. The only wisdom I have is 42 is the answer to life, the universe, and everything else.
The steps are pretty easy. I'll give more detailed explanation afterwards.
0. Download tar and pit files listed in the original post
1. Install Heimdall
2. Understand how Heimdall linux process differs from Odin windows process
3. Boot phone into download mode and connect to computer
4. Push files to phone with Heimdall
Step 0: Download tar and pit files
Pretty simple. Unpack those bad boys. Put them all into one folder nice and cozy neat like. That's right. The pit, modem, and completely unzipped files all in one folder.
Step 1: Heimdall is your friend
There is no Odin without Windows. We must turn to another Norse god, Heimdall to help us out. Heimdall is an open source project to replace Odin. There are ports to Windows and Mac OS X. The Epic 4G is not officially supported but many people have used it with no problem. I personally used linux mint 11 with an almost bricked phone with no problem. Use at your own risk.
Install Heimdall
The latest version at this time is a command line only version 1.2.0. The GUI for previous version 1.1.1 looks easy enough if you want to use them, although according to reports it may not work as well as command line. For the instructions I'll use the command line because I think it makes it easier to understand how to match files up to the different fields.
Since your linux distros are different, I will not go into any specifics on how to install.
Step 2: Understand how Heimdall differs from Odin
Difference 1: Don't need no stinkin' Samsung drivers (unless you're using Heimdall in Windows). "But what about those drivers..." Zip it! You don't need 'em.
Difference 2: Unpack the tarball and unzip the pit. The individual files in the tar, the pit file, and the modem.bin file should all be in one folder. The major difference with Heimdall and Odin is that with Heimdall, you specify how the files match the partitions. In some respects this is easier because if you don't need to repartition, or if you only need to push a particular file, e.g. the modem, you can do that. The trick with the command line is to know which files match the command line switches, e.g. --modem modem.bin, --factoryfs factoryfs.rfs, etc.
Step 3: Boot phone in download mode and connect to computer
Open up keyboard and hold 1 while hitting power.
Connect phone to computer.
Step 4: Push files to phone
Open terminal window in the directory with all the files. Use cd if necessary to get to the folder.
The general structure for the heimdall command is:
Specifically for the SPH-D700-EC05-8gb-REL.tar and victory_8G_100528.pit listed in the original post on this thread:
Capitalization is important. I don't know how many times I messed up because I didn't type Sbl.bin with a capital "S".
If you use the gui, just make sure you specify which files go in which fields. I don't have the gui front end so I have not tested it, but it looks simple enough.
If everything works, then you'll see the progress as heimdell copies everything. If something is not right, then you'll get an error message.
Heimdall reboots the phone when it's done.
Please let me know what you think. Suggestions always welcome.
Sources:
http://www.glassechidna.com.au/products/heimdall/
http://wmarkito.wordpress.com/2011/02/11/flashing-android-froyo-in-a-galaxy-s-with-ubuntu-and-heimdall/
Click to expand...
Click to collapse

Important to note this will take a very long time I've been sitting waiting for mine to finish for a while. Been about 30 minutes and still not done.

krisman said:
Important to note this will take a very long time I've been sitting waiting for mine to finish for a while. Been about 30 minutes and still not done.
Click to expand...
Click to collapse
What is it saying? It shouldn't take that long. Do you see the blue progress bar on your phone?
I was going to mention that it froze once when I was trying to do it and I just unplugged my phone and took out the battery and restarted and it went through.
You can chat with me on Fossnet
http://webirc.fossnet.info/?channels=epic
Just say my name "Cyc" in channel and I will respond.

dyehya said:
What is it saying? It shouldn't take that long. Do you see the blue progress bar on your phone?
I was going to mention that it froze once when I was trying to do it and I just unplugged my phone and took out the battery and restarted and it went through.
Click to expand...
Click to collapse
Yea still has the blue progress bar odin says factoryfs. I actually thought it might be frozen. But i started to ask how long it would take and it jumped forward some more. And now it just finished as I'm typing this. Which it won't boot stuck on the samsung boot screen just keeps vibrating gonna try again.

krisman said:
Yea still has the blue progress bar odin says factoryfs. I actually thought it might be frozen. But i started to ask how long it would take and it jumped forward some more. And now it just finished as I'm typing this. Which it won't boot stuck on the samsung boot screen just keeps vibrating gonna try again.
Click to expand...
Click to collapse
Yeah try again. It takes a few minutes of factoryfs due to it pushing 258MB to the phone but shouldn't have taken 30 minutes.
Now this can't fix your phone if it has hardware problems but should fix everything else. Let me know how it goes. My problem with it freezing was before it started push stuff to the phone.
The only other thing I could think of and didn't even question was your computer using a USB 2.0 port. That's the only reason I could see it taking so long to transfer data to the phone if it was Using usb 1.0 or 1.1

Finally gave up on eb13 after redownloading the tarball and still not getting anything. Tried a di18 tar and it worked first try. Trying to odin from there to eb13 seems to be slow flash and then not working right still.

krisman said:
Finally gave up on eb13 after redownloading the tarball and still not getting anything. Tried a di18 tar and it worked first try. Trying to odin from there to eb13 seems to be slow flash and then not working right still.
Click to expand...
Click to collapse
IF DI18 works you can let it OTA update to EC05 the same way EB13 would. I used EB13 because there is no OFFICIAL EC05 tar available presently but any of the full tars should work. Any reason you are trying to tar to EB13 in particular if you got DI18 working?
I don't remember where I downloaded EB13 from I just looked for a link when I was posting this How-To. You might want to try finding an EB13 tar from another source and see if that resolves the issue or redownload the EB13 tar. My EB13 tar has an md5 of b9b14611dcde5fbe586fdc242315b92b and I know it works on my Epic. You can use HashCalc or some other program to calculate the EB13 hash.

I updated the EB13 tar link in my original post. You may have to refresh your browser to see it http://www.multiupload.com/3YPCROH00T
You can try that.

No reason in particular for wanting to go to eb13 just thought it strange that it wouldn't work and wanted to keep trying.
Sent from my SPH-D700 using XDA App

krisman said:
No reason in particular for wanting to go to eb13 just thought it strange that it wouldn't work and wanted to keep trying.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I appreciate you trying. If you want you can try the new link of EB13 I posted and see if that works. I am downloading it now myself to see if the hash check matches what I have or not.

I made a video showing how to do this. You might want to link it in the OP:
http://www.youtube.com/watch?v=YQ2g6J1JgjU
Also, a link to my other how to video thread:
http://forum.xda-developers.com/showthread.php?t=1009997
Oh and just for future reference, a post like this doesn't belong in the development section. It goes in to the general section.

Yeah I am going ask impaler to move it for me b/c I didn't mean to post it in dev just had a few too many windows going when I was putting it together. Thanks for the video link I'll add to OP with credit of course

I verified the new link has the correct md5 so it should work.

Very good directions.... should be added to the Other thread we have about ODIN though...

This will also bring back your samsung logo if you repaired your epic after a visionkernel brick but lost the samsung logo..
Sent from my SPH-D700 using XDA App

This thread sponsored by k0nane.info.

@DYEHYA
IM having my first issue with my epic .. SEMI BRICK ... i see in ur picture of ODIN n description u have everything checked but from video n past ODIN tries ive only had reboot checked is this only for semi bricked or should i do what i know worked from previous odin use and that is only keep the auto reboot checked ....

djgallis said:
and that is only keep the auto reboot checked ....
Click to expand...
Click to collapse
I would suggest you continue as you have been - check ONLY 'auto reboot'.

k0nane said:
I would suggest you continue as you have been - check ONLY 'auto reboot'.
Click to expand...
Click to collapse
thank you will do ..

[HOW TO] Root Nextbook8 Premium (and install market app) [UPDATED 1-17-12]

PLEASE BE ADVISED: THE AUTHOR OF THIS POST NO LONGER PROVIDES SUPPORT FOR THIS THREAD. HOWEVER YOU ARE MORE THAN WELCOMED TO CONTINUE USING THE FILES AND METHODS AT YOUR OWN DISCRETION. GOOD LUCK!!
INTRO: For all those searching the internet trying to find answers as to how to gain root on your Nextbook8 Premium and also gain access to the wonderful android market from which we were greatly deprived (as is the case with many low-priced tablets these days), the wait is over thanks to a certain someone who goes by the name of DEVMONKEY. Of course I take absolutely NO CREDIT for this and only took the liberty to re-write it thus adding a little more detail to the process. Enjoy!!!
DISCLAIMER​***I HAVE NOT TESTED THIS PARTICULAR ROM WITH MY N8 WHEN I HAD IT BUT AS THE PROCEDURE TO FLASH IS STILL THE SAME ALL SHOULD GO WELL. HOWEVER, I AM NOT RESPONSIBLE FOR WHAT MAY OR MAY NOT HAPPEN IF YOU USE THIS AND DAMAGE YOUR DEVICE. PLEASE FOLLOW ALL STEPS CAREFULLY***​
[HOW TO] Root and install Market on your Nextbook8 Premium​
UPDATE: This is post has been updated with a new rom to replace old one. Method of flashing is still the same so no worries. All those who want to upgrade to this rom from the one I previously posted in this guide when I first wrote it can just repeat the steps over again with the new rom package.​
This rom is based on Samhain's release: SamDroid v1.13
Modifications (mostly GUI / cosmetic tweaks):
1.) cifs.ko / slow-work.ko / nls_utf8.ko are in /system/lib/modules and can be loaded using Mount Manager app from the market. This will let you mount CIFS/SMB shares to the device.
2.) Honeycomb-like launcher and updated GUI icons. (you can change it to any Launcher you want)
A couple of things to note once you have installed the rom:
- It starts up in Italian, so open Android settings "Impostazioni" and go to the "Lingua e tastiera" setting, and change the "Seleziona lingua" to your preffered language.
- I've put a few wallpapers in /system/media that you can set full screen by going into Live Wallpapers and using the "Multipicture Live Wallpaper" set them to the screen.
- There are a few things (widgets) on the homescreen that don't work after initial boot, just remove them and add back whatever you want to the homescreen.
- Sleep of death issues seem to be fixed, and the camera works (Camera app works, but Skype and Fring don't work yet...).
- You can also grab Adobe Flash 11 from the market and it'll work correctly.
- This release boots MUCH faster, and is even more responsive than before.
- There is a cell standby issue that drains the battery more in theory so if you feel like that is happening with you just delete the Phone.apk and TelephonyProvider.apk from /system/app. You can use ADB or you can use Root Explorer to do so. You will likely have to force a reboot because you'll start getting repetitive force closes once you do so, but it won't hurt anything. Once you reboot, all is well.
VERY IMPORTANT: After installing custom roms that also flash a custom recovery your N8 may reboot into the custom recovery. If this happens hit reboot system and only reboot system.
​Download new rom from HERE and extract (using winRAR preferably) to your desktop or anywhere you choose. Location doesn't really matter for this guide to work.
NOTE: If you have anything you care about (like apps, notes etc.) on your N8 make sure you back it up now.
Step 1: Turn your N8 off.
Step 2: Press both Volume buttons down and plug the USB cord into the N8.
NOTE: On your screen you should see a bubble pop up in the lower-right corner saying "Installing drivers". Most likely it will say it can't find the drivers. This is normal. Continue following the steps to install the missing drivers.
Step 3: Open the Device manager by typing mmc devmgmt.msc into your "Run" box on XP or search box in start menu on Windows 7 and hitting enter (you can also find Device Manager in your Control Panel options in Windows 7).
Step 4: With your N8 still in an off state and plugged in via USB you should see a yellow exclamation symbol somewhere next to "Unknown Device" in the list of devices in the Device Manager. Right click on it and select "Update driver software".
Step 5: Now it will prompt you to choose how you want to search for it. Select "Browse my computer for driver software" and it will bring up a window for you to navigate manually to the driver location which is in the "drivers" sub-folder in the NEXTBOOK8ROOT folder. Select which ever system you have (32bit or 64bit) and then hit "OK". You might go thru one or two prompts before it actually installs. Just "OK" everything and you should be fine.
Step 6: Once the drivers are installed you are ready to flash. Go into the root of the NEXTBOOK8ROOT folder and select RK29update.exe (right-click for Win7 users and Run as Admin).
Step 7: Now you should be at the interface of the program and at the bottom in bold words it should say "FOUND RKAndroid rock usb" (if it doesn't then it mean the drivers probably weren't installed correctly). This part is VERY IMPORTANT!! Make sure all of the boxes on the left are checked (should look like the pic below). The one at top is the one usually missing a check and would need to be checked by you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 8: Once all boxes on the left are checked you are going to click on "EraseIDB" at the bottom and let it complete. Once that finishes click on "Run" and you will see a series of commands running in the right window pane (see pics below). Give it some time as it will probably take a few minutes. When it's done it should look like the second pic below.
Once the process is finished your NEXTBOOK should reboot into the recovery and reflash the OS. Congratulations!!! You now have an affordable rooted tablet with access to the Android Market!!
OTHER ROMS YOU CAN FLASH INSTEAD OF THE ONE IN THE ABOVE GUIDE:
Pisteone - [SDK 2.1] EXT4 Bluetooth 3G Root [Basic FW 1.0.21] ICS Style - LINK
Fintadroid - [FULL ROOT & EXT4] [BT & 3G] [FW.1.0.21 PRESTIGE] - LINK
ALL ROMS FOR NEXTBOOK8 - LINK (Be very careful and read before you flash)

Thanks! worked great.

I signed up, so i can say thank you. this worked perfectly.. i was skeptical and scared i'd ruin this tablet, as i got it as a gift, and was obviously disappointed to see no market on it, but this worked. thank you.

How about Nextbook Premium 7?

Thank you!
This worked great, I was able to get the android market installed and working.

Android version?
What version of Android does this install?
Cheers, Greg.

It's work, your are wonderful,thank you Sunnyboy167

Great job! Good to have root and Market working. But anyone else get FC when opening Camera app?

Perfect! I have rooted many Android devices and this is one of the easiest ones. Just read the directions carefully and you'll do fine.
Hopefully someone will release an ICS update for this device soon..after using my Galaxy Nexus, Gingerbread seems so...obsolete.

I'm glad you enjoyed this info just as much as i did
To everyone YOU ARE WELCOME but please....the best way to thank me is by hitting the thank button at the bottom right of my post. Thanks!
@xxProphecyxx - here is a link for the nextbook7 http://gunnersbarn.wordpress.com/2011/11/04/how-to-install-android-market-to-nextbook-premium-7/ I don't see any root method listed on the site but im sure there is one out there if you want to root it too. Or you can even take a chance if youre brave and use a one click root based on the android version you have.
@ghi07 - All this method does is re-install the OS (which is Gingerbread to answer your question) with market and superuser.
@dalerious - I'm sorry but I don't have a Nextbook anymore but if I did I would definitely try my best to help you. Try doing the entire process over and see if that works. Good luck!

THANK YOU!!!!
I was about to throw this tablet out the window!!! Followed the instructions and it works perfectly!!!! Thanks SO SO much!!!

Thanks to you I had a very Merry Christmas haha thank button has been pushed repeatedly!

Hi Sunnyboy,
Just want to say a big thank you for the detail post. I was about to give up on on this tablet when I came across your post.
Chris

help help!!!
hi sunny boy,
i just got my nextbook8 yesterday... come across this website and trying to root my nextbook last night at home...
I encounter this problem...when i plug in my nextbook into the PC USB ..it turn on from the off mode. and the pc started to scan the driver and it actually install successfully. I am running on win7. after that i cant install the driver required.. can anyone help me out here cos i try to run exe. file. it cant root my nextbook... i am helpless now...

I am also having problem with the camera. I'll have this error:
The application Camera (process com.android.camera) has stopped unexpectedly. Please try again.

HELP HELP HELP...not able to on the device after updated the driver....PC shows device found after plug in USB, which shows the device is working but just cannot on it.. a total IT dummy and not sure what's going on..someone said the ROM is damaged which cause this.....any way to recover the tablet..i just bought it for less than a week. HELP HELP HELP!!!!!! (tried reset but still no response)

Sunnyboy167 said:
To everyone YOU ARE WELCOME but please....the best way to thank me is by hitting the thank button at the bottom right of my post. Thanks!
@xxProphecyxx - here is a link for the nextbook7 http://gunnersbarn.wordpress.com/2011/11/04/how-to-install-android-market-to-nextbook-premium-7/ I don't see any root method listed on the site but im sure there is one out there if you want to root it too. Or you can even take a chance if youre brave and use a one click root based on the android version you have.
@ghi07 - All this method does is re-install the OS (which is Gingerbread to answer your question) with market and superuser.
@dalerious - I'm sorry but I don't have a Nextbook anymore but if I did I would definitely try my best to help you. Try doing the entire process over and see if that works. Good luck!
Click to expand...
Click to collapse
I have already been to this website and successfully added the market to my Next7. I do want to root it and flash a custom ROM, but I have not found anything useful. Thanks though.

Rooted fine, thx a mil. Installed GOLAUNCHER EX and the icons were too big. Dl'd LCD resolution from market and decreased res from 160 to 140. To apply changes app reboots tablet. When it came back up, nextbook stuck on launch screen and I can't even turn it off!! This was my gf's xmas present from her parents!!! Any suggestions??

eybarra2 said:
Rooted fine, thx a mil. Installed GOLAUNCHER EX and the icons were too big. Dl'd LCD resolution from market and decreased res from 160 to 140. To apply changes app reboots tablet. When it came back up, nextbook stuck on launch screen and I can't even turn it off!! This was my gf's xmas present from her parents!!! Any suggestions??
Click to expand...
Click to collapse
u can reboot the device by using a paperclip and press in the reset button.
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
Thanks for the detailed guide Sunnyboy167~ Anyway devmonkey just release a newer mod which works better than the previous. Do check it out

hi all,
I rooted my new nextbook8 ...and it works just nice...
just need some help on whether possible to use my iphone as a modem for my nextbook? as i realized it cant detect my wifi network from my iphone. While my colleague 's motorola zoom works fine with my iphone...any solution on this?
Caduser from singapore...

[Q] Unbrickable Mod Help - Won't complete?

Problem solved -- lessons learned posted on page 2 - in short, use Linux to do this and do the soldering right the first time. Still this experience may be helpful to some who try and come across similar hurdles. Thanks to all who helped.
So I was successful last year rooting and putting a new firmware on this phone. I cam back to try something new but made the bonehead move of grabbing a GB loader for the Vibrant and hard bricked the phone. Nothing worked of course so I got brave and tried the Unbrickable mod. I've worked under a microscope before and after some trial and error modified my tools to manage the task (I think!?).
Up front I want to thank Adam and everyone else who put effort into the Unbrickable mod - that's simply amazing work and I wAs so fascinated I had to try it too.
So I now nothing about linux so all around this has been a huge learning experience and I'm hoping my problem is software but I fear not. I'm running Ubuntu over VirtualBox and used the links provided in Adam's Development thread for the the T959V - of course I'm new here so couldn't comment there. There was no Detector download so I just downloaded the Resurrector. Upon hooking up the phone I got a huge smile because the phone was recognnized by the computer and finally by the resurrector when I figured out how to get Ubuntu to see the USB. I ran the device and everything went apparently well HOWEVER I could not follow on with Heimdall One-click as it would not recognize the phone.
Here's the Output from the ReSurrrector
**********************************************************
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 004
=> loaded 24576 bytes from /tmp/TempHeimdallOneClick99719EDC/UnBrickPack/HIBL.bin
=> Downloading 24586 bytes to 0xd0020000
=> Data checksum d8dc
=> usb_bulk_write() returned 0
failed to write 24586 bytes
Interceptor Injection Complete. Injecting modified SBL
*****************************************************************
I assumed all was good and went forward. I got no display from the phone but the navigation lights did come on. However as said, Heimdall said phone disconnected. The phone is recognized in Windows as well however Odin does not recognize it. I tried Resurrector again and again. In looking at the Resurrector output I noticed there is a fail to write so I'm not sure where to go from here.... is there something wrong wtih my solder job? is one of the adjacent resistors disturbed?
I feel so close and yet so far... any direction is appreciated

sounds like a driver issue. here's a link for heimdall suite 1.3.2 for windows. unzip and make sure your phone is connected to a usb port in back of your pc first. front side usb ports can cause some problems. when phone is plugged into pc via usb, run the zadig.exe in the drivers folder. when open, options>list all devices. then from the drop down menu, select the one for samsung (mine now says galaxy s 4g) and then click install drivers. should be good to go with heimdall after that is done.
http://cdgfx.me/hEiMdaLL

Yep. Driver issue. Its better to use a Heimdall one-click if you can find one for your device. Linux also requires no drivers.

Again - please let me thank all in advance for looking at this problem.
So I've cleared all instances of USB installation before and the result is that I can now see "SCE S5PC110 Test B/D" show up in Zadig however - The drop down box shows only "USB Input Device (Interface 0) and another for (Interface 1)" and of course the S5PC110. I have "list all devices selected" however this devices only shows as the S5PC110 and thus Samsung is not selectable in the drop down box.
Driver reads as (NONE)
WInUSB (v6.1.7600.16385)
USB ID 04E8 1234
WCID shows a red "X"
There is no option to select Samung s4sg I suspect because the bootloaders are still not corrected and the Unbrickable mod is present?
Anyway, I pressed the install drivers button and indeed a usb driver installed with the following output.
******************************************
ini file 'zadig.ini' not found - default parameters will be used
default driver set to 'WinUSB'
0 devices found.
libwdi:info [detect_version] Windows 7
1 device found.
1 device found.
3 devices found.
Using inf name: SEC_S5PC110_Test_BD.inf
Succesfully extracted driver files.
Installing driver. Please wait...
libwdi:info [extract_binaries] successfully extracted driver files to C:\usb_driver
libwdi:info [wdi_prepare_driver] succesfully created 'C:\usb_driver\SEC_S5PC110_Test_BD.inf'
libwdi:info [wdi_prepare_driver] Vista or later detected - creating and self-signing a .cat file...
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\amd64\wdfcoinstaller01009.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\amd64\winusbcoinstaller2.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\sec_s5pc110_test_bd.inf'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\x86\wdfcoinstaller01009.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\x86\winusbcoinstaller2.dll'
libwdi:info [CreateCat] successfully created file 'C:\usb_driver\SEC_S5PC110_Test_BD.cat'
libwdi:info [CreateSelfSignedCert] created new self-signed certificate 'CN=USB\VID_04E8&PID_1234 (libwdi autogenerated)'
libwdi:info [SelfSignFile] added certificate 'CN=USB\VID_04E8&PID_1234 (libwdi autogenerated)' to 'Root' and 'TrustedPublisher' stores
libwdi:info [SelfSignFile] successfully signed file 'C:\usb_driver\SEC_S5PC110_Test_BD.cat'
libwdi:info [SelfSignFile] successfully deleted private key
Driver Installation: SUCCESS
3 devices found.
*********************************************
I have the Heimdall One Click for this device but as seen previously in both linux and windows - Heimdall does not detect this device as a Samsung and shows Disconnected... Similarly Odin does not detect this device.
So I switched back over to VM Virtual Box running Ubuntu 12.04 and no difference there either. I further made the USB permanent and took off automount from windows so that I could ensure the device interfaced directly into linux in the short period of time I assume is the download period - that is to be able to enter password for Resurrector, then plug in phone, and then press OK in a short period of time. The result is the same.
Summary - in Linux, Resurrector recognizes the device but Fails to write 24586 bytes as before. I can now also be in Windows and have the S5PC110 device recognized however nothing can write to it in Windows as far as I know.
*********************
One last try with a different method - held Vol +&- & power before connecting to computer. The following output from Resurrector in Linux appears the same as previous except for the questionable write. After the usb_bulk_write however I heard the device disconnect and again the progress stopped here
----------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 002
=> loaded 24576 bytes from /tmp/TempHeimdallOneClick14WD41A3/UnBrickPack/HIBL.bin
=> Downloading 24586 bytes to 0xd0020000
=> Data checksum d8dc
=> usb_bulk_write() returned 24586
Interceptor Injection Complete. Injecting modified SBL
************************************************** **************
there is no display on the phone and nothing progresses. The usb bulk write happens only on occassion and is immediately followed by the usb disconnect sound.

Lumin30 has a file called usbdeview in his fresh out of the box thread. Use that to remove all samsung drivers. It sounds like a residual driver is causing a problem.

eollie said:
Lumin30 has a file called usbdeview in his fresh out of the box thread. Use that to remove all samsung drivers. It sounds like a residual driver is causing a problem.
Click to expand...
Click to collapse
Thanks eollie but I did that already. I had to delete all previous Samsung and S5PC installations as I've tried so many things to date which involved using almost every usb port. It did make a difference in that now the device is recognized but as the test board and not as Samsung. I have gone through the route of installing the samsung drivers previously from the various Samsung Driver files that are around however none resulted in this phone being recognized as a Samsung again.

On the windows pc go to device manager and delete all USB drivers not just the ones related to phone then reboot and then try a heimdall one-click and only use zadig to install drivers??

OK - so I wanted to remove Windows from the equation as the experts suggested it's a driver issue and despite all my efforts I was having no success. I installed Ubuntu (dual boot) and voila Resurrector now completes and for the first time I actually get into download mode with a graphic on the screen. Using bhundven's One click The T959V Heimdall One-Click Collection I finally saw "connected" and was able to follow the steps twice to flash bootloaders. All operations completed successfully before disconnecting the phone however the phone did not reboot. SO I repeated the whole process again without any change.
current state - I cannot get the phone into download mode without using Resurrector. While I know a ton of progress has been made here thanks to the tools provided by Adam, bhundven, and others my phone still behaves as it did before - no display except for button lights on some methods to get to download mode. My jig does nothing either. Battery is fully charged and I remain stumped.

Did you make sure you flashed with bootloaders cus Ive had tthat happen with an older phone
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol

erikmm said:
Did you make sure you flashed with bootloaders cus Ive had tthat happen with an older phone
Click to expand...
Click to collapse
Yes twice with UVKJ6 package and subsequently tried AntonX-Basic_with_a_twist-v1.1.0-OC_UV.jar with double cycle to get the bootloaders flashed...
each time the process now gets to the point where it tries to reboot the phone and disconnects. The bottom status screen still maintains a rolling circle with statement of it's last step but the phone is powered down and nothing else will happen. No combination of buttons or jig or usb to computer will get the phone to boot or enter download mode.
On going back to windows (and Zadig) the device is still only seen as S5PC110 -- so I guess there is an improvement in but the phone is still not recognized as Samsung, Heimdall or Odin won't see it, and I have no idea what to try next.

You do have a SGH-T959V and not a 959W right? Have you tried to use heimdall frontend and flash everything except the modem? The 959W people that have been stuck in a bootloop got out of is by flashing everything except the modem. Then once sucessful they reboot to recovery and flash the modem of choice for the rom you are using.
I would pm getochkn and get the exact steps he uses and try it.

eollie said:
You do have a SGH-T959V and not a 959W right? Have you tried to use heimdall frontend and flash everything except the modem? The 959W people that have been stuck in a bootloop got out of is by flashing everything except the modem. Then once sucessful they reboot to recovery and flash the modem of choice for the rom you are using.
I would pm getochkn and get the exact steps he uses and try it.
Click to expand...
Click to collapse
This. Are you in Canada? A quick google search of "drsilicone" shows people with that same name on Canadian forums like redhotdeals, etc, so if that's you and you have a "W" phone, I may be able to help. 99% of the phone is the same as the "V" but small differences make a big deal sometimes and I have a pretty much complete dump now of a "W" phone with great help from bhundven and other team acid members. PM if you do have the "W" phone and we'll see what we can do. I've helped fix 2 other "W" peoples phones in the past 2 days. If you don't have a "W", then I can't help much. lol.
EVen if you see nothing on the screen, try the download button combo anyways. I did that to my phone yesterday, looked dead, but holding the buttons and putting the cable in, it still went into DL mode and Heimdall saw it, flashed back my dumps and was going again.

100% T959V -- it's a T-mobile phone that yes I previously rooted and unlocked. Worked fine for a year until my idiocy with the boot loader a few days ago.
and thanks for the advice but as I've noted above I've tried every key, button, jig, usb combination with no luck. The Unbrickable mod, resurrector, and Heimdall one-click with boot loader flash sequence appears to have worked except for the very last event expected - that is for the phone to reboot -- it does not reboot however.
The ONLY thing that produces any recognition or response in the phone is Adam's Resurrector. True the phone is now recognized in the window's environment as S5PC110 Test BD but it has never again been recognized as a Samsung so Heimdall simply won't find, connect, or otherwise allow command line flashing of this device. Similarly, Odin does not show any ID:Com open so that doesn't work either.
I can only hypothesize that the boot loaders were NOT actually written to the device as it would then show up as a Samsung no?? The only other thing to note is that after resurrector puts the device into Download mode (and I now see the yellow triangle graphic) I cannot disconnect the device and move to another port - the phone shuts right down and it's not responsive to ANYTHING I've tried..... and I think I've tried all sorts of combinations with battery in and out.
Edit:
Reading the Unbrickable Captivate thread again FredWorrell wrote on2nd September 2011, 04:31 AM #24
... a tip the size of a human hair. Although, if you screw up and you remove both resistors instead of just one, the phone can now be put into download mode and will accept a download. Unfortunately, it still won't boot normally.
Click to expand...
Click to collapse
This is the situation I guess I face but as I'm not certain what resistors he was referring to nor what those comparable resistors are on the T959V I'm still stumped -- unless Adam or someone knowledgeable can offer input...
I've borrowed this picture from Tablador for the magnification and clarity (Thank you Tablador) to highlight one resistor I have my questions about. I'm not sure how I can test it's function right now and my magnification is at 6X so I can't truly see the solder joints. I did disturb it but fixed it - could that explain this symptom?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Problems SOLVED
Thanks for everyone's help - it turns out that it was the resistor pictured above. The picture above shows solder shoulders on these resistors - without equal magnification I would swear there was none and with the landing pads located underneath it looks like an impossible task but with the right technique I was able to correct my previous mistake.
Funny story goes along with this - I bought a Vibrant last year from a kid who said it was bricked by Kies and he didn't know what to do. I'm up for an adventure and bought it from him. I ended up getting the T959V right after with a broken screen so didn't really try too hard to fix the vibrant. Anyway, with this challenge I set out tonight to do the unbrickable mod on the Vibrant as the T959V wasn't working. On opening up I found quite the mess -- this kid obviously tried the unbrickable mod and the whole bank of high and low resistors was gone with 4 chips spread off to the sides -- A complete disaster indeed and made me realized I had been taken in buying it... Oh well, I was able to harvest a resistor (I guessed one near the cpu that looked similar to the one I wrecked on the T959V) and my only choice now was to go back to the T959V and try again.\
I added some magnification and was able to install the new resistor in place of the questionable one pictured. Happy simply with the new soldering skills I've gained over the past week I resigned myself to the result of this final attempt. Imagine my surprise when I pressed the power button and it booted into CWM -- I couldn't complete the boot sequence so I had to run Resurrector again followed by Heimdall One CLick and I'm overjoyed - This time it all worked as expected.
Thanks to Adam, bhundven, and all others who've contributed to these magnificent technical lessons.
If this thread will serve anyone else in trying the Unbrickable mod I would summarize my lessons --
#This is very difficult and technical work trying to solder these things - don't try it without the right tools, knowledge (which can be gained by reading and watching videos), and a steady hand. Seriously, if you shake under a microscope don't bother - pay someone.
#Don't bother trying to do this in Windows - not worth the headache -- Ubuntu provides a very easy way to install dual boot to your computer and it was so intuitive that I regret not doing it sooner.
# and I guess I'll just testify as one more person that this mod really does work exactly as described -- if it's not working as described you may have USB driver issues or soldering issues as I had. If it's not working - do the mod again and make sure all the connections are as they should be.

[Solved] Noob here: Bricked?

Phone info:
SGH-t959v
Updated to: Gingerbread 2.3.6
Rooted using ZergRushv3
Kernel: sms-T959V-KJ6-antsvx.v1.1.3
I am pretty new to this, but was able to update my phone with the above with no problems so I decided to take the leap and install a custom ROM.
I installed ROM Manager. I downloaded a custom ROM, CyanogenMod9. Then it asked me if I wanted to backup my current ROM and clean up Dalvik cache. Ok'd on both. My phone then re-started and the phone was frozen at the Galaxy S 4G Samsung splash screen. I pulled the battery and have tried the three button combo to get to recovery, but it just keeps restarting and freezes on the splash screen.
Reading the awesome Q&A section I was finally able to to get to download mode using the below directions:
1) Power phone off
2) Pull battery out
3) Hold vol up + vol down
4) While holding vol up + vol down, plug in USB cable into the phone
5) While still holding vol up + vol down, put battery back in
6) Yellow /_\ (triangle, Downloading, Andy shoveling, Do not turn off Target!!! symbol)
I've been @ #6 Downloading for about 20 minutes. Am i on the correct path? Should it take this long? Any insight/advise would be greatly appreciated. Thanks!

OGPackin said:
Phone info:
SGH-t959v
Updated to: Gingerbread 2.3.6
Rooted using ZergRushv3
Kernel: sms-T959V-KJ6-antsvx.v1.1.3
I am pretty new to this, but was able to update my phone with the above with no problems so I decided to take the leap and install a custom ROM.
I installed ROM Manager.
Click to expand...
Click to collapse
This is where you went wrong. Rom Manager does not support our device.
OGPackin said:
I downloaded a custom ROM, CyanogenMod9. Then it asked me if I wanted to backup my current ROM and clean up Dalvik cache. Ok'd on both. My phone then re-started and the phone was frozen at the Galaxy S 4G Samsung splash screen. I pulled the battery and have tried the three button combo to get to recovery, but it just keeps restarting and freezes on the splash screen.
Reading the awesome Q&A section I was finally able to to get to download mode using the below directions:
1) Power phone off
2) Pull battery out
3) Hold vol up + vol down
4) While holding vol up + vol down, plug in USB cable into the phone
5) While still holding vol up + vol down, put battery back in
6) Yellow /_\ (triangle, Downloading, Andy shoveling, Do not turn off Target!!! symbol)
I've been @ #6 Downloading for about 20 minutes. Am i on the correct path? Should it take this long? Any insight/advise would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Make sure you follow the directions to correctly install heimdall:
https://github.com/Benjamin-Dobell/Heimdall/blob/master/Win32/README.txt

Also, after you get hiemdall installed correctly, use the oneclick eollie made. Make sure you download the latest CM9 for SGS4G and read the OP and instructions multiple times to make sure you are ready to go before going forward.

bhundven said:
This is where you went wrong. Rom Manager does not support our device.
Ohh F' me! I can not believe i made that dumb mistake!
Make sure you follow the directions to correctly install heimdall:
https://github.com/Benjamin-Dobell/Heimdall/blob/master/Win32/README.txt
Click to expand...
Click to collapse
Working my way thru now. wish me luck.
Thanks!

I've started at the Driver Installation Instructions. When i get to #4 From the USB Device list chose "Samsung USB Composite DEvice". i dont have the option for "Samsung USB Composite DEvice"

OGPackin said:
I've started at the Driver Installation Instructions. When i get to #4 From the USB Device list chose "Samsung USB Composite DEvice". i dont have the option for "Samsung USB Composite DEvice"
Click to expand...
Click to collapse
If you made a guide please add this!
Thanks lumin, and actually I encountered a minor trouble. So I panicked a little but everything was fine in the end, I don't know how but the SAMSUNG USB composite device wasn't found. So I flipped through the thread and what do you know, I researched a bit and found out, that the USB ID can also determine the device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The number on the USB ID which is "04E8 - 6601" can be your device. My phone was named "Gadget" and I was scared that my phone wasn't found but I guess it did find it.
You should put that as a tip/hint on the guide just in-case other people encounter the problem.

th3controller said:
If you made a guide please add this!
Thanks lumin, and actually I encountered a minor trouble. So I panicked a little but everything was fine in the end, I don't know how but the SAMSUNG USB composite device wasn't found. So I flipped through the thread and what do you know, I researched a bit and found out, that the USB ID can also determine the device.
The number on the USB ID which is "04E8 - 6601" can be your device. My phone was named "Gadget" and I was scared that my phone wasn't found but I guess it did find it.
You should put that as a tip/hint on the guide just in-case other people encounter the problem.
Click to expand...
Click to collapse
Thanks for the tip. In Zadig I have two Gadgets listed.
Gadget Serial
Gadget Serial Control ( Interface 0 )

Your not paying attention:
LOOK at the USB ID, it should say 04E8 6601

Wow chill dude! When i pull the USB cable from my phone while having Zadig opened i see the Gadget Serial load. I figured thats got to be it. I installed the driver but i still dont see "Libusb devices" right click on "Samsung USB Composite Device"
th3controller said:
Your not paying attention:
LOOK at the USB ID, it should say 04E8 6601
Click to expand...
Click to collapse

Here's where i am...In Device manager im seeing "Samsung USB Composite Device" under USB Controller not under Libusb. So i tried opening heimdall-frontend> browse to SGH-T959V_T959VUVKJ6_UV_TMB.rar. I then get and error "tar header contained an invalid size." I also tried using "T959VUVKJ6_STOCK-UVKJ6-One-Click.jar" but it shows my devise as disconnected.
At this point im not sure what i should do. Any help more help would be greatly appreciated!

I'm guessing you have not done Heimdall packages before, don't worry it looks complicated at first but you'll get it soon.
Download this Eollies Heimdall One-Click
Then head over here to Lumins noob-proof Heimdall guide
Don't forget to thank Lumins, Eollies, and Bhundvens posts

th3controller said:
I'm guessing you have not done Heimdall packages before, don't worry it looks complicated at first but you'll get it soon.
Download this Eollies Heimdall One-Click
Then head over here to Lumins noob-proof Heimdall guide
Don't forget to thank Lumins, Eollies, and Bhundvens posts
Click to expand...
Click to collapse
You can say that again, th3controller! What a nightmare.
Followed the directions and when i get to the Command Prompt window and run java -jar everything load along with Heimdall One-Click opens but im getting "Device not connected" in the Command Prompt. My phone shows downloading_Do not turn off target. I've disconnected/connected USB but i still get the same message. Windows does recognize USB being unplugged/plugged in. Not sure what to do hear?

screen shot
Here is a screen shot of what i am seeing

Update......
After banging my head against a wall to figure out my next step i decided to move to a different computer and start the process all over again and guess what.......? IT WORKED!
I know its not board etiquette to thank you guys in a post but i just want to say it...THANK YOU!! I will also click the Thank you button...:angel:
At this point i am going to pass out from exhaustion...lol and work on the phone later. But i figure my next step is to root the phone and reinstall all my apps?
Thanks again!!

You probably forgot to read this part:
IMPORTANT NOTES BEFORE YOU BEGIN:
* * When using Heimdall or ODIN - Designate USB Ports on your computer for each flashing program. Have one USB Port that you only use Heimdall for. Have one USB Port you only use ODIN for. This does not mean you cannot use the designated USB Ports for other functions NOT related to your phone. This is only for flashing with Heimdall and ODIN.
* * Always use a USB Port that is directly connected to your computer - NO USB Hubs or add-on Ports.
* * If possible - Start with a USB Port you have never plugged your phone in to. By doing this you will reduce your probabilities of running into problems.
* * If you have used your phone on every USB Port and/or have no idea where all you have plugged your phone into or used ODIN or Heimdall with - Download [usbdeview-x32.zip] for 32-bit operating systems or [usbdeview-x64.zip] for 64-bit operating systems. Uninstall anything you see that has Samsung and Android related.
You should have uninstalled drivers for a clean get away. But anyways since your issue is resolve please edit the title with a [Solved]

th3controller said:
You probably forgot to read this part:
IMPORTANT NOTES BEFORE YOU BEGIN:
* * When using Heimdall or ODIN - Designate USB Ports on your computer for each flashing program. Have one USB Port that you only use Heimdall for. Have one USB Port you only use ODIN for. This does not mean you cannot use the designated USB Ports for other functions NOT related to your phone. This is only for flashing with Heimdall and ODIN.
* * Always use a USB Port that is directly connected to your computer - NO USB Hubs or add-on Ports.
* * If possible - Start with a USB Port you have never plugged your phone in to. By doing this you will reduce your probabilities of running into problems.
* * If you have used your phone on every USB Port and/or have no idea where all you have plugged your phone into or used ODIN or Heimdall with - Download [usbdeview-x32.zip] for 32-bit operating systems or [usbdeview-x64.zip] for 64-bit operating systems. Uninstall anything you see that has Samsung and Android related.
You should have uninstalled drivers for a clean get away. But anyways since your issue is resolve please edit the title with a [Solved]
Click to expand...
Click to collapse
Nope, ur are incorrect as i did read that part, but could not get it to work on this computer no matter what i did. I wont go into deals as i am up and running and at this point thats all that counts. Thanks again!

Rooting HP Slate 7. Updated March 16 2014

Updated to March 16th 2014.
General Warning, read before doing anything to your tablet:
Whenever you try to do anything to your system ALWAYS back up everything since there is always the chance that something might go wrong.
If something goes wrong you have to download and install the boot images from HP support, HP Slate 7 2800 restore image and HP Slate 7 4600 restore image, the install instructions are in the same page in "How to install".
Some users have had problems with the alternative rooting method using Bin4ry's tool, since it is some I will asume it is something someone is not doing correctly, because other users with the same slate model have been able to root, if it is your case where you can't actually root post here I'll try to help you in any way I can.
To end this sort of disclaimer, my Slate 7 is the model 4600 so I'm not actually able to try the method with other slate models, anyhow other users have had no problem but as always this could be your case and I'm not responsible in any way if you brick your device.
Cydia's Impactor tool has been updated and it's working with all versions of the roms (Confirmed by users).
Bin4ry's rooting tool has been updated, chances are it's more friendly user and won't throw any errors, up to you to try it out.
Just as a side note, the screenshots below are just for reference, they are not the same drivers/devices, they are only meant for you to know where to click.
Step 1: Download Tool Package (this is an old package, the drivers in the package works but you NEED TO ALSO DOWNLOAD Cydia's Impactor (Link to home page in case you are interested in reading a bit) and Googles ADB Drivers with a little modification in the ini file so it installs the driver for our HP Slate 7 tablet). If your Slate 7 model is 2800, you have to also download Moborobo that will find and install the drivers for you. I've received messages from users who have had both good luck and no luck installing the drivers, this must be dependant on your operative system and administrative rights, I did all this steps on a Windows 8 64bits machine with administrative privileges.
Download latest Cydia's impactor tool from the link above. The one in the package won't help you if you are trying to root v9 and above.
Step 2: Unzip the package anywhere you like, meanwhile go to your tablet and set it to USB Debugging.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YOU MUST SET IT ON USB DEBUGGING MODE, else nothing that you try will work.
Step 3 OPTIONAL: Just in case if your computer doesnt realize there is a device connected you need to copy the file in "\.android\adb_usb.ini" over to your user path "%USERPROFILE%\.android\" and reboot the computer (Just in case it wont recognize a device as connected).
Step 4: Now open the computers Device Manager and you will see something similar to this picture
Step 5: Right click the HP Device and choose to update driver, search for drivers in the computer (2nd option), then "let me pick from a list of device" as follows:
Step 6: Next click in "have disk" and navigate to where you unpacked the file downloaded earlier and choose the ini file.
Pictures for reference only.
Step 7:All you have left is open Cydia's Impactor tool, you will see a small window with a default command on screen which is the following:
Code:
# drop SuperSU su to /system/xbin/su
Just click Start next to it aaaaand you are done!
(PS: If this worked you are done, skip Step 7B. If you were unable to root your device try Step 7B)
Step 7B (ONLY IF Cydia's tool did not work): Warning: I've received messages from some users that this exploit has left them on bootloops, this method is tested on the 4600 model, if you have another and it works please do post your results, if you have problems all you have to do is download your model ROM from HP support and boot it through your microSD card to restore factory settings, also check in Bin4ry's thread for information if it is your case, if you find another method please do let us know . DO THIS ONLY IF STEP 7 FAILED, you will have to download the following rooting tool from Bin4ry's XDA thread, execute "RunMe.bat" and use method 1 and follow the on-screen instructions (This method will reboot your tablet 3 times if I remember correctly, after 2 reboots it will be stuck in a black screen for a couple of minutes (or more, it took me around 10 minutes) this is as it pushes the files for superuser, don't panic).
You can check your build version as it's shown in the following picture.
Just open an app like Titanium Backup which needs root to see if it worked.
This method is simple plus you don't have to download anything chinese or unnecesary software into your computer, the tutorial is really long because I tried to be as detailed as posible but in the end you shouldnt take more than 5 minutes (The downloads might take a bit longer though for the SDK), I would take screenshots of the process but my computer runs on a Spanish version of Windows (The same reason why you might see things with different names I was just trying to guess the device manager label part).
If you have any question feel free to ask (of course... as long as it hasn't been asked again and again in the thread ) and if it worked for you a thanks would be awesome so more users will try
PS: My Slate 7 model is the 4600 but it should work with others slates and for that matters, with any tablet as long as the adb driver is recognized.
PS2: If you could upload the package into a new mirror that might help more people.
PS3: Updated to March 16th 2014.
PS4: I just realized the screenshots facilitated by another user have been deleted, will try to find new ones.
PS5: If this helped you, please do thank, this way more users will benefit from it.

Universal Root
Ok people, I've used pretty much the same method to unlock 2 different tablets, if you see my other guide with rooting MSI Windpad 71 it's almost the same thing.
Once you get ADB running all you have to do is run Cydia's impactor and you are good to go.
If this helped anyone please tell your experience and with which devices you have tried this.

It's working guys!
It works perfectly, even better.
Also does anybody know how to make GT Racing Academy work on it?

My HP its Slate7 2800 your thread its for 4600 its diferent i think? I cant install the driver from device manger.

mastertempo said:
My HP its Slate7 2800 your thread its for 4600 its diferent i think? I cant install the driver from device manger.
Click to expand...
Click to collapse
Please do reply to the questions I asked you earlier, if you don't give out information I don't know what you are not doing right.

Dont wory man,i root my slate 7. How? I told you now. First i intall this: https://www.dropbox.com/s/0jg872o2armnntt/ADBDrivers.exe and strart it and install drivers. Then i run cydia impactor and everyting its done for few seconds. But i have one question now: is the cydia its universal for all android deviceses?

mastertempo said:
Dont wory man,i root my slate 7. How? I told you now. First i intall this: https://www.dropbox.com/s/0jg872o2armnntt/ADBDrivers.exe and strart it and install drivers. Then i run cydia impactor and everyting its done for few seconds. But i have one question now: is the cydia its universal for all android deviceses?
Click to expand...
Click to collapse
Yes, Cydia's main goal is to be a universal rooting tool.
I will check on the drivers you found, it could shorten the guide.
For everyone else I know it looks like a lot of steps, but it's really download software, modify a couple of ini files, install driver and run Cydia Will check on the drivers MasterTempo installed maybe I can make a package for a single small download.

Ok guide updated to v2.0 with single package download.
As long as the computer recognizes the ADB drivers for the phone/tablet Cydia's Impactor tool should root any device.

Worked on my slate. Thank you very much for your help
Sent from my GT-I9100 using XDA Premium 4 mobile app

what about unroot?
hi still i didnt root but i want to know how to unroot it : as my HP Slate is very new

OTA update
kibaruk said:
Ok guide updated to v2.0 with single package download.
As long as the computer recognizes the ADB drivers for the phone/tablet Cydia's Impactor tool should root any device.
Click to expand...
Click to collapse
My tablet is asking to update, if I do the OTA will I lose root?

wasim9283 said:
hi still i didnt root but i want to know how to unroot it : as my HP Slate is very new
Click to expand...
Click to collapse
No idea here mate sorry.
dalethefarmer said:
My tablet is asking to update, if I do the OTA will I lose root?
Click to expand...
Click to collapse
Nope, I've updated mine and it's still rooted.

kibaruk said:
No idea here mate sorry.
Nope, I've updated mine and it's still rooted.
Click to expand...
Click to collapse
I just updated mine and lost root...

dalethefarmer said:
I just updated mine and lost root...
Click to expand...
Click to collapse
Really?? That's odd... well you could always just re-run Cydia and go ahead with the push of files again and voila rooted again.

kibaruk said:
Really?? That's odd... well you could always just re-run Cydia and go ahead with the push of files again and voila rooted again.
Click to expand...
Click to collapse
Doesn't work. When I run Impactor I get an error: Signature bugs unavailable.
I tried updating impactor and I have the latest version.
I can factory reset and root again, but how do I stop the OTA update prompts from popping up?

dalethefarmer said:
Doesn't work. When I run Impactor I get an error: Signature bugs unavailable.
I tried updating impactor and I have the latest version.
I can factory reset and root again, but how do I stop the OTA update prompts from popping up?
Click to expand...
Click to collapse
Ok it seems the latest OTA which was a big one over 250mb changed something, I lost root access too, will have to see how to get this one rooted.
If anyone could confirm before trying to update to big OTA their versions? Mine is after OTA Android Version 4.1.1 compilation numbre v1.05.10_user.

It seems that for version 1.05.10 they have fixed the master key vulnerability of android.
"If you are having problems using Cydia Impactor (it crashes, doesn't work on your device, or simply doesn't make any sense) please join #android on irc.saurik.com and ask a question.
The Android "Master Key" vulnerability was found by Bluebox Security. For more information on how this bug works, I have done an overly-detailed article on the exploit technique.
If that bug is not available, Impactor will instead attempt to use a different signature verification bug. For more information on how that bug works, I have done another article on the new exploit.
It is possible that your device has been patched against both bugs; Impactor will inform you of this. If you'd like to check before spending time working with Impactor, you can try either the Bluebox Security Scanner or the alternative SRT AppScanner (which I have found to provide fewer false positives than Bluebox's tool).
Some devices are also patched against the second stage now used to get root; devices that are patched will show "link failed file exists". (This second stage was made possible due to help from @giantpune.)".

dalethefarmer said:
Doesn't work. When I run Impactor I get an error: Signature bugs unavailable.
I tried updating impactor and I have the latest version.
I can factory reset and root again, but how do I stop the OTA update prompts from popping up?
Click to expand...
Click to collapse
Ok I found a working root for latest 1.05.10 patch you can download here.
Once you download the tool you have to run the "RunMe.bat" file and follow the instructions, the method that worked was method 1 "New Standard-Root", it seems to also come with an unroot option for those who have asked for it, havent tried it though.
PS: Be careful when "press a key to continue now" because you can make it a double tap and miss a step, it won't brick the device but you will take longer.

Guide updated for latest OTA pushed 1.05.10_user that won't accept Cydia's vulnerability. It seems that the alternative rooting tool has the option to unroot for all of those who have asked for it, I havent tried it yet though.

mastertempo said:
My HP its Slate7 2800 your thread its for 4600 its diferent i think? I cant install the driver from device manger.
Click to expand...
Click to collapse
I've found out other HP Slate 7 2800 users are having problems with the drivers I put in the package, they have found Moroboro useful for that matter