Database Users

vista doesn't boot !

hey guys,
I got an htc shift and when I power it on, it dosent find the vista and says insert boot media in the selected boot device,
I tried to recover it from the recovery partition but it doesn't work either,
I appreciate if anyone can help me.

Have you tried going into the BIOS to see if the HDD/SDD is enabled? If it's not listed, it could be that your drive is dead.
Restart your device (or turn it on if it is off), Press "Del" at the HTC Splash Screen, press "Right", "Return, "Down", "Return". You should see it in the list if it's still working OK. If it is in the list and enabled, check the other Setting under the "Boot" menu and check that it is selected as your primary boot device.
If none of this works (or at least drive is not visible), I think your drive may be dead.
If it does show your Drive in the list(s), but Windows still says there is no boot media, and recovery partition is not recovering it, you'll need to try to install an OS so it has some valid Boot Media to boot from.

indeed I tried the bios setup and my HDD is ok,
I saw some linux an xp bootable images but I am wondering that if I use them my device gona work properly!!
cuz I saw some issues with drivers!!
THX &
sorry if my english is kinda wonky pal!!!

sahandf said:
indeed I tried the bios setup and my HDD is ok,
I saw some linux an xp bootable images but I am wondering that if I use them my device gona work properly!!
cuz I saw some issues with drivers!!
THX &
sorry if my english is kinda wonky pal!!!
Click to expand...
Click to collapse
It's worth a try. If you can at least get it to boot, you may be able to check the drive for errors etc. Don't worry about things working properly for now. Just get the barebones working.
Another suggestion though, you could have a virus in the boot sector. I'm not sure if these are reversible or salvagable, but if you do get it to boot, try running a thorough virus scan to see if that throws anything up.
Failing all that, the best solution for trying to diagnose the problem would probably be something like this...
SSD-to-USB converter
With this, you could connect it to another computer and at least see if the drive is readable. Obviously this means taking your Shift to pieces to get the SSD out, but I've done it and it's not that difficult really.
And your English is good!

sure I'll give it a shot,
thanks a million!

Can not Mount Phone to PC

I have run into another issue. I can not mount my phone to computer. I think this is happening because of me rooting my phone. I was able to root the phone successfully. But somewhere along the way something happened and I can't mount my phone to my pc. This is as if my pc is not reading/recognizing the phone when plugged in. However, my phone is reading its memory and sd card perfectly.
When I plug the phone to my pc:
With USB Debugging off... I dont even get a notification in the slide down menu asking me to either mount/unmount.
With USB Debugging on... I do get the option in slidedown menu to mount my phone. At the same time the computer shows a pop up message asking me to install driver software for Samsung_Android. In the meantime , I press mount sd card which by the way is still not recognized by the computer.
I dont have the driver for samsung_android to install on the computer.
This thread here describes how I rooted my phone. I thought this background info might be helpful in solving the problem.
Does anyone know a potential fix for this situation.
Thanks.

When this happened to me having it" ask what to do" when connected may have solved the issue. I went through this just yesterday. You also might re-boot your phone and computer a few times...nothing like that can hurt. Until someone who actually knows something finds this thread : P

67 views and just one reply.
**bump... someone gotta know the solution

Reading your post is a little confusing. If you are saying you cannot "mount" the phone the term Mount is replaced with "connect usb storage" in the pull down. If yours is saying mount, then your rooting process may have not worked. It is hard to tell based on how you wrote this up. Use the one-click rooting you can find all you need INCLUDING the Samsung computer drivers (32 or 64bit) @ unlockr.com along with a nice youtube video showing the whole process beginning to end.
Additional thoughts:
If you are really jacked you can always go to the bible (in the top of this general forum) and search for the "ALL in One" zip to flash back to stock...etc. The All in One has the stock kernel, the .pit (used for mapping) the 32 bit driver/64 bit driver for the computer and Odin all in one Zip. You should have this in your computer folder named (unbrick tools) either way you should get all this if you are going to be customizing the phone, along with the Eugene's froyo that does not brick rom. This rom is a lifesaver should you flash in a way where the format will not recognize the stock format. You can flash this 1st then stock right after and that ALWAYS gets you back to stock.
In the future, when you are trying to describe what is going on try to be careful with terminology it is important not to use terms loosely otherwise we are just guessing on how to help......... hope this helps

Thanks for your thoughts. It seemed as if my computer was lacking the drivers for samsung vibrant so I installed them from here
and now I can connect my phone to the pc and its working fine. I thought I had downloaded and installed the drivers before when I downloaded on the big download button on the top and installed some fake software from advertisement.

If you ever flash a 2.2 rom and experience the problem again with the drivers already installed, this might fix it...
http://forum.xda-developers.com/showthread.php?t=846384

[Q] need help getting unlocked bootloader(solved)

ive tried doing the tutorial at http://forum.xda-developers.com/showthread.php?t=1622425 but to no avail have got it to work i keep getting stuck at step 5 where im checking my sbk number but whenever i type the commands into cmd it says nvflaSH is not recognized as an internal or external command, operable program or batch file??? sorry cant figure it out i have all the acer drives installed and all files needed any help would be appreciated

gears177 said:
ive tried doing the tutorial at http://forum.xda-developers.com/showthread.php?t=1622425 but to no avail have got it to work i keep getting stuck at step 5 where im checking my sbk number but whenever i type the commands into cmd it says nvflaSH is not recognized as an internal or external command, operable program or batch file??? sorry cant figure it out i have all the acer drives installed and all files needed any help would be appreciated
Click to expand...
Click to collapse
Sounds like either you're not in the correct directory with your CMD window, or you didn't extract the files properly. Try extracting them again to a folder on your c: then open a cmd window there. Nvflash is really a simple app. Also, make sure you are in apx mode. Should see a icon in windows task bar, or you can check device manager.

A little tip, do search for cmd.exe on your pc, and then copy it to the folder where you would like to use it. Much easier than cd (change directory) or any other way that I know short of adding it to your right click menu. I keep a copy of it on my desktop so I can copy/paste it anywhere that I need it.

Make sure you installed the Acer drivers. At first I didn't b/c I had working ADB. You need those Acer drivers for the APX driver in there. I wasted an hour or two on that one!

strongergravity said:
Make sure you installed the Acer drivers. At first I didn't b/c I had working ADB. You need those Acer drivers for the APX driver in there. I wasted an hour or two on that one!
Click to expand...
Click to collapse
I've tried that even tried a reinstall I'm pretty sure I'm typing in the commands wrong or when it says open cmd on V6-Unlocked-ICS-HC-bootloader-MULTI-CWM folder I'm not sure does that mean just open up cmd and input that directory and then the commands or what?

gears177 said:
I've tried that even tried a reinstall I'm pretty sure I'm typing in the commands wrong or when it says open cmd on V6-Unlocked-ICS-HC-bootloader-MULTI-CWM folder I'm not sure does that mean just open up cmd and input that directory and then the commands or what?
Click to expand...
Click to collapse
Connect tablet to pc, make sure you are in apx mode , open the folder V6-unlocked.......... and click on the .bat that you want to run. It should start , no need to open cmd on the folder .

I got stuck but in different way altogether.
if you don't mind going back to 3.2.1 for a few minutes then I suggest doing that. it also installed CWM to which you can install your chosen ROM.
then after this you could just use blackthunders apx tool to flash your chosen bootloader.
I know your problem is totally different to mine and looks like you are just not in the right directory while trying to use nvflash but the way I suggest was very easy and works.
I cant post links right now but if you look in the thread for unlocking bootloader then I posted a link which should help you do it this way. its on page 47.
hope u get it sorted I spent many hours yesterday always getting stuck at various points but after many hours found an easier way.
cheers

tigermrk said:
I got stuck but in different way altogether.
if you don't mind going back to 3.2.1 for a few minutes then I suggest doing that. it also installed CWM to which you can install your chosen ROM.
then after this you could just use blackthunders apx tool to flash your chosen bootloader.
I know your problem is totally different to mine and looks like you are just not in the right directory while trying to use nvflash but the way I suggest was very easy and works.
I cant post links right now but if you look in the thread for unlocking bootloader then I posted a link which should help you do it this way. its on page 47.
hope u get it sorted I spent many hours yesterday always getting stuck at various points but after many hours found an easier way.
cheers
Click to expand...
Click to collapse
Sweet I'll try civatos way then if that doesn't work I'll give it a shot I'm still on honeycomb boot loader so why not ;-) thnx again for the help......how does black thunders tool work sorry for incompetence I thought I knew about tech :'( any help would be appreciated

its basically GUI program which installs a bootloader of your choice in a few clicks.
of course u dont need the ICS bootloader if you were to choose to install FLEXREAPER rom after going through my method.
just install it by the recovery menu after going back to 3.2.1.
cheers
EDIT: If your already on the honeycomb bootlaoder (just noticed) you should be able to do it pretty easy and civatos way will work fine

Dug up this old threaad because i didnt feel the need to create a new one and still never solved this :/ no matter what i do it seems i get stuck at entering downoad mode it enters apx mode fine but wont enter download mode im on ics locked bootloader and have tried uninstall reinstall of drivers multiple times also tried switching pc's. Is there any preferred os to do this on? and does 64 bit vs 32bit matter?
Edit.....nevermind guys tried on a whole different comp and worked fine

Advice on "unbricking" a soft-bricked stick

I've been scouring different forums for nearly a month now and can't find a solution that works for my situation. I resisted posting here, hoping to find the info on my own without any luck. I have a handful (6) of these generic MK809III Rockchip 3188 based sticks, with 4.4.2 KitKat. All identical. I have no idea which Chinese manufacturer assembled them. Four of them work perfectly. Two of them have been corrupted by me. I inadvertently wiped out the build.prop files. The files are there, but they are empty. (I know this because the last one I botched, I could see the file in the open editor with no content, as a read-only. The moment I closed the screen... that was it.
Using the "hold the pin in hole, then power up, wait 5 or 10 seconds, then release the pin" method of recovery (sorry, I don't know the proper name) does boot it into recovery mode, but the screen shows this:
Failed to mount /mnt/external_sd (No such device)
Failed to mount /mnt/external_sd (No such device)
Failed to mount /mnt/external_sd (No such device)
one_data_if_exist->can't find databk partition
Formatting /data...
Formatting /cache...
Booting...
--- then, a stuck boot animation.
My problem, is that I cannot connect to these via USB to do anything to them. My system tools are:
Linux Ubuntu 14.04 LTS workstation
RK_Flashtool_1.7
Android Studio
Latest Android tools sdk
Other tools available to me: A Mac (running Yosemite OSx)
Notes:
- Adb drivers, I assume, are correct, because I can access the working stick computer via ADB
- The RKFlashtool will not recognize any of the corrupted units, or show that it is even connected
- Obviously, I cannot set the "Connect to PC" flag without the OS booted
- In a terminal window, adb does not show the usb device as being connected
- I do not have a back up for any of these. I tried, but both Clockwork and TWRP would not recognize the unit to permit a backup. The working units are recognized as: "gxt_dongle_3188".
I really need some advice. I must be overlooking something, I admit to being somewhat new to Android. I wish it were possible to backup one of the working units, and install it on the corrupt units. But no backup app was installed in the boot loader of the corrupted units (that I'm aware of).
Thanks for your time!

Judging from the lack of responses, this problem must have a lot of people as perplexed as I am. I really thought someone here might have an idea.

How I unbricked my Hard-Bricked Samsung Galaxy Tab 4 SM-T337A...

Hello, my name is Marc-Yvan from Douala, Cameroon and I will tell you the whole story about how I successfully unbrick my Android Tablet. My aim is to share with you some tips about how to recover from a desperate situation of having an unusable tablet.
How I hard-bricked my Tablet:
First of all, let me tell you how I hard-bricked my beloved tablet after trying to unlock it from its original network lock. I got this tablet from a relative who live in USA but it was unfortunately network locked to the AT&T network. So I tried to unlock it by multiple means (by myself). I found a cracked software called “Octopus for Samsung” who was said able to unlock any kind of Samsung phones/tablet. When I tried to unlock my Tablet, the software starts the work and then told me that the device will turn off and turn on after a short time. But the Tablet did not turn on anymore and I spend 02 months trying to bring it back from the grave.
Definition:
Let me explain to you what is called a hard-bricked smartphone/tablet. It’s simply a smartphone/tablet which is unusable, doesn’t turn on (desperate black screen) and doesn’t react to any stimulation. But you have to know that these hard-bricked devices are displayed as unrecognized devices when plugged onto a computer. So a hard-bricked device is not a physically damaged device but is a sort of hardly logically damaged device which cannot boot at all and is not recognized by common flash tools such as Odin, etc.
How I unbricked my tablet:
Lucky Context (GOD’s help):
Fortunately, GOD helps me by guiding me through this situation in order to recover from it in a miraculous manner. I will explain it to you in a couple of points:
1- My Tablet was rooted before the incident. I did it by using an application found in play store: “Kingroot.apk”.
2- My Tablet was equipped with some tools like “Es explorer” and “Terminal Emulator”. You will understand how it fortunately helped me before the incident.
3- The real hand of GOD: In my quest of finding a mean to network unlock my tablet, I tried a method which was asking to save some partitions of the eMMC (A kind of processor memory. Sorry but I’m not an expert ). So I saved it to the memory of my Tablet and then transfered it to a folder in my computer (By using command lines with “Terminal Emulator”). This actually helped me after to revive my tablet.
Advice N° 1 (Prevention)
Before trying to explore the whole abilities of your Tablet by flashing it or trying to network unlock it; Do a backup of the primary boot partition of your eMMC by executing this command in the “Terminal Emulator” of your rooted device:
cat /dev/block/mmcblk0> sdcard/mmcblk0.img
Be careful, this command could save the life of your beloved Tablet. This command will actually copy the primary boot partition of your eMMC in a disk image which has the same name. So you have to keep that disk image in a safe place such as your computer or an external removable disk.
Advice N° 2 (Resolution)
The Story:
In my desperate actions trying to revive my hard-bricked tablet, I read tremendous forum posts and tried countless methods. Which lead me to install a new OS in my computer. It was actually Linux Ubuntu 16.4. I found a method which told me to try to write some kind of partitions images down to an SDCard to boot my Tablet with. But the partitions images proposed by the method didn’t succeed in recovering my Tablet. So some days later, when I turn on my computer, I fortunately found a file opened; it was the primary boot partition image file of my tablet that I saved before the incident (The real hand of GOD). So I decided (Inspired by the Holy Spirit) to try the previous method with the original boot partition image file of my tablet.
The Tip:
You will need an SDCard with a correct format (FAT32) and size (16Gb or 32Gb). You will also need to work in a Linux command line terminal. To write the boot partition image in your SDCard you will have to execute this command line:
sudo dd if=mmcblk0.img of=/dev/sdb bs=1024k status=progress
Note: The sd card may not be sdb though. In order to confirm, before writing, browse to /Dev and look at the properties of sdb to ensure it is in fact there (it might be sda, sdb, sdc, etc...). You can also try to unplug and then plug the SDCard to see the changes.
The Last Step (Eureka!!!)
The last step is just to insert the SDCard into the slot of your Hard-Bricked device, Turn it on and then feel its vibration that will let you know that your mission is completed. Your device is alive again.
Conclusion
The only conclusion that I can give is to NEVER GIVE UP when you are trying to solve a problem. You can be closer to the solution than you think.
Good Luck!

What are the chances you would upload the boot partition for me?
I hard bricked mine also, but unfortunately I didn't make a backup. Would you be kind enough to upload the bin file you dumped? I've looked everywhere and no one seems to have an emmc dump of this thing. lol