Database Develop

How to FORCE stop phone from showing up as USB drives in Recovery, still no root :(

Okay I don't know if this will help anyone, but I figured out how to stop Windows from detecting the phone as two USB drives when the phone goes into Recovery mode, and to make it show up as Android Composite ADB device.
I do NOT have HTC installed, rather, I'm using the USB 3 drivers that come down through the SDK, so I'm not sure how to do this if you are using the HTC Sync drivers intead.
At any rate, start with the phone off and disconnected. Open the Device Manager. Boot with your prefered method into Recovery mode, then connect the phone. It should detect as USB Mass Storage Device under Universal Serial Bus Controllers. Right click on USB Mass Storage Device and click Uninstall and then OK. Once this is done, disconnect the phone (you can leave it running in Recovery).
Open My Computer and navigate to C:\Windows\inf. Copy the files usbstor.inf and usbstor.pnf to your desktop or wherever, it doesn't matter, just make sure you put them somewhere you can get them later. Then delete them from the C:\Windows\inf folder. These are the drivers that Windows automatically uses for USB storage devices.
Ok, now bring Device Manager back to the foreground and plug the phone back in in Recovery. It should show up as Android Phone with an exclamation mark. If Device Wizard pops up cancel out of it. Now right click on the Android Phone and click update driver. Click Browse my computer for driver software. Click Let me pick from a list... Click Android Phone and Next. Click Have Disk. Browse to your SDK folder into the USB Drivers folder and you should see android_winusb.inf, select that then click OK. You should now have a list of three items to select, this part I am not sure if there is a 'right' or a 'wrong' but I go with Android Composite ADB Interface.
Select that or whichever one you think and this is what it will install as. Bingo, now whenever you connect the phone into Recovery or boot into Recovery with it already connect it correctly detects as the Composite ADB Interface or whichever you selected, but does NOT show up as any USB drives.
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
At any rate, to get everything back to normal as far as your computer being able to use USB storage devices just copy those two files back to the inf folder before you connect them and you should be fine.

bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
.
Click to expand...
Click to collapse
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.

Or you could try what I've done 7 times and achieved ADB Shell 7 times...
1. Turn the phone off.
2. Start running Loop.bat
3. Unplug USB cable.
4. Turn device on in Fastboot by holding in the optical joystick and power.
5. Plug USB in.
6. Hit power button once to get to HBOOT.
7. Wait two seconds for it to do it's thing.
8. Pull off the back of the phone.
9. Hit Vol - to Recovery then hit power.
10. Immediately after doing this continuously push the sd card in and out (about every .5 - .75 seconds)
11. ?????
12. Profit

@DigitalDementia--
How is what you said relevant in this thread?

bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
Click to expand...
Click to collapse
drtrmiller said:
@DigitalDementia--
How is what you said relevant in this thread?
Click to expand...
Click to collapse
Pretty positive it had everything to do with that section of the first post, he said he still couldn't achieve root I attempted to help him. Why don't you explain to me exactly what it doesn't have to do with this thread?

rynosaur said:
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Click to expand...
Click to collapse
The real bummer here - and I should have known better, really - is that this wipes your phone.
I suppose it should be obvious, but take it from someone who's pretty new to Android phones and just wiped their entire phone after following your steps: Please add a warning to your original post.
It's late, I'm tired and irritated, but I'm sort of bummed to know I went from hero to zero in trying to enter shell (again) during recovery all in an effort to get proper perm. root. Sort of ****ty to know that I just lost everything.

still no root
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App

USB drives are ok in recovery
When I am in recovery with adb and working correctly it still shows the 2 USB drives so this is normal and ok, what you have done is fool yourself into thinking that your phone is in correct mode but it really is not, this is why it still does not work, sorry.

rynosaur said:
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Now that I've scorched the earth, I'm hitting this thing hard with every trick I can think of to get the shell in recovery again.
Thankfully, I at least have my app list on appbrain.

After researching around the different forums, I think this maybe my issue. I will have to make this attempt when I get home.
This is what I posted on a different forum. I am not sure if this is a similar experience you were having:
So, for a little a bit I was having issues with finding and modding the usb.inf file. I got that finally resolved... Now as I go to one of the first parts of the procedure, executing the adb shell command. Well at first it said the 2 lines, about the daemon and whatever the second line was. Anyways, the third line did not say "no device found" it went straight to a shell prompt "$" . The instructions made a point in the instructions for it to say " no device found" .
I went ahead with the rest of the instructions. No Luck. And I did both methods. A co-worker of mine told to run adb devices to see if my phone is recognized. I will also make that attempt tonight.
I wanted to know if any of you had some insight. I made sure I was in the right directory.
I will make another attempt on a different machine tonight.
Thanks. Oh yeah, I do have some UNIX experience if that makes a difference.

I had the same problem, used this method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!

kentoe said:
I had the same problem, used this method here
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
Click to expand...
Click to collapse
I rooted in Windows, rather than linux, simply because I like the look of MejDam's procedure better than the linux script posted here on XDA--and his windows procedure is accompanied by his YouTube video
Long story short: I had ADB Composite Device AND the two storage volumes mounted together, as I got shell, and did the other steps in recovery. NB: they were mounted as Generic Storage Volumes, not writeable partitions. The stock recovery on DI does not allow host to mount either partions, although I'd like to see if
Code:
mount /dev/block/mmcblk0p1
worked for the SDcard on the sdcard, cuz then it would be a cinch to mount sdcard/emnc partition into host OS--windows, linux, Atari 2600, etc Worth a try.
Anyhow, my conclusion: a bad driver setup could be a barrier to catching adb shell, but it is certain not the prevailing problem for most, IMHO.

Was wondering if bast525(the creator of the thread) was ever able to adb shell while in recovery, and if so what did you do thanks.

Heh, I wish.... I've tried just about every method posted on these forums, and five different SD cards from Sandisk, PNY, and Kingston. The only thing I haven't tried is rolling back to the pre OTA update, because I don't want to wipe the phone at this point.

Yet another another WORKING How to root your Incredible

Thanks to everyone and all their post I was finally able to root my Incredible. Since I was having issues getting mine to root I tried pretty much everything that was said on these forums.
The secret to rooting is the timing of inserting your sdcard before the recovery screen is shown.
Here are the steps that I did to root 2 difficult incredibles.
1) Download the google SDK. You need the adb command for the rooting process.
2) Install HTC Sync or google SDK drivers. It doesn't matter which one you use. You just need the drivers installed and working.
3) Put your phone in USB Debugging mode under the applications config section.
4) Plug your usb in your phone while it is booted normally.
5) Select the disk drive option when prompted.
6) Make sure you can sucessfully connect to your phone using "adb shell" command. If this does not work you will not be able to go any further. This means drivers are not installed correctly.
7) Power off your phone. Doesn't matter how. Battery removal, press power off button etc...
8) Remove your SD card.
9) Press Volume down and power at the same time.
10) When the phone is at the Bootloader menu press Volume down and Highlight the Recovery option. Do not select it yet.
This is where the rooting process gets tricky.
11) Make sure your usb is plugged in.
12) Make sure you dont have your SD card in your phone.
You have to insert your SD card in your phone while the recovery mode is loading. There is a specific time window that you must do this. By using different SD cards they take certain time to initialize during the loading. This is why some SD cards work all the time and why others have to be inserted at a certain time
13) Go ahead and get your "adb shell" loop running. It should show "error: device not found"
14) Bring up a clock. You will need this to keep track of when you inserted your SD card during the recovery boot process.
15) Press the power button to select Recovery and start counting the second hand on the clock.
16) Start at 1 second and insert your SD card. You will wait until you hear windows beep when its loading the drivers for the USB device. After the 10 seconds your adb loop screen should show the following if it worked: "exec '/system/bin/sh' failed: No such file or directory (2)"
17) If it does NOT show this you will need to remove the battery and SD card and go back to step 14.
18) Increment your time by a second. So for the 2nd try insert the SD card after 2 seconds have past. So far on my walmart PNY 2gb SD card on 2 incredibles it takes around 5 to 6 seconds of waiting before I can insert my SD card. If you get to 10 seconds you need to restart and try again, but this time try half seconds increments.
When I select the Recovery option and the phone is loading I will see the white splash screen near the bottom kinda flicker a little bit and have a small horizontal line distort across the screen. That's about the same time I insert my SD card.
If you get the "exec '/system/bin/sh' failed: No such file or directory (2)" message looping in your shell prompt, Congrats you have access to the recovery shell. You will need to follow these steps to fully root your phone.
http://www.unrevoked.com/rootwiki/doku.php?id=public:adb_in_recovery
Thanks to everyone in these forums offering their input. Without your input I wouldn't be able to root my phone.

LOL
I guess great minds think alike:
http://forum.xda-developers.com/showthread.php?t=703589
^ I posted that this morning.

At first I thought it was you reposting or someone poking fun at these types of threads.
You guys say like the same thing. Hopefully that means this is a good "update" to the process and people will have a slightly easier time.
I have Froyo on my Droid so am not too eager to get my Incredble rooted, but I have been following along.

I'm going to get my timings down tonight and post a 3rd thread on this!!!1

dreamersipaq said:
I guess great minds think alike:
http://forum.xda-developers.com/showthread.php?t=703589
^ I posted that this morning.
Click to expand...
Click to collapse
lol yeah, I guess the method works

seanmcd72 said:
I'm going to get my timings down tonight and post a 3rd thread on this!!!1
Click to expand...
Click to collapse
I'm going to use an atomic clock to time and root my DI and report back on the decay rates of Polonium!
I appreciate users' attempts to refine this process, but I'm sticking with the old: insert the card right before white-switches-to-black . . . I tried timing and found myself slamming the sdcard card into the slot trying to make my targets, and that ain't not good for the DI.

rynosaur said:
I'm going to use an atomic clock to time and root my DI and report back on the decay rates of Polonium!
I appreciate users' attempts to refine this process, but I'm sticking with the old: insert the card right before white-switches-to-black . . . I tried timing and found myself slamming the sdcard card into the slot trying to make my targets, and that ain't not good for the DI.
Click to expand...
Click to collapse
LOL, well that's your own fault
Don't be so rough with her.... Abuser! Gentle, there is no reason to slam.
And it's still better then the click in and out method.

[Q] Can not ADB my device?!

I have a Verizon Galaxy Tab 7 (SCH-I800) and I can not link up to it in ADB.
I have installed the Android Development Kit, Samsung drivers, and downloaded CM10.1.
I was able to contact the tablet in command prompt through heimdall and push clockworkmod recovery.
I'm following this guide:
http://rootzwiki.com/topic/33743-ext...rd-only-guide/
I've removed the internal memory card.
I've modified the update.sh file and rezipped everything.
I just need to know WHY adb cannot find my device. When I type "adb devices" in the command line NOTHING shows up. I've tried reinstalling the samsung driver, reinstalling the driver that came with heimdall, and updating the samsung driver via windows update.
By the way, this device would bootloop at the verizon loading screen, could not be updated, and could not load its original android OS, therefore I cannot turn on debugging or anything like that. Alls I can do is access the "PC connection" yellow screen and the CWM bootloader I pushed with Heimdall.

By "Internal" Memory ya meant "External" Memory right? as the Internal Memory is the 16GB Flash ROM.
In any case all pedantry aside. Did you remember to check the USB Debug Setting?
I think you can find this under the Wi-Fi Settings (On the Samsung Stock ROMs), IIRC it should be near the "Samsung Kies / Media Player / USB Storage" Settings. On CM10 Builds you'll find it in the "Developer Settings" near the bottom of the List.
Pretty sure you have to check this "Flag" before you can use ADB on your Device...
In that case consider yourself bricked!
In this case I'd recommend you find the Overcome Recovery Package: HERE
Install such Driver that you may need, then fire up Odin3 v1.7
Then set your Device into Download Mode (e.g. Hold Volume Rocker down + Power till you enter the Download Mode Screen)
Pit -> gt-p1000_mr.pit
PDA -> GB_Stock_Safe_v5.tar
Phone -> modem.bin**
Most People would just use the XXJPZ (GSM modem.bin), here but, since you have a CDMA Phablet, you'll have to find and pick the correct modem.bin File that is the best match for your CDMA Device. This is also likely why your now soft-bricked.
Hopefully after all this rigamarole you'll land up on a Stock, non-branded Samsung Gingerbread 2.3.3 ROM.
To which I would just download This, and that should give you Root.
Without all that tedious mucking about with ADB.

The internal chip has failed. I cannot boot the device whatsoever. I removed it as the link states. Therefore i cannot check off debug mode on the tablet. I will try your suggested method and report back

Don't look at Overcome method if you have a CDMA tab.
It will only brick your tab if it ever worked at all.
Regarding bad internal memory, there are two chips. The OneNand 512MB and the MoviNAND 16GB.
If your OneNAND is the one broken, removing the MoviNAND achieved nothing.
The bootloader, modem, (and is it /system too of stock rom?) sits on OneNAND.

If you look at the link I posted, my tablet was doing the same exact thing as pictured in the link. Saying it could not mount any files or anything. No matter what I did, it would just get to the verizon loading screen and keep flashing "verizon".
I haven't tried the "overcome" method as it didn't really seem like it'd work.
I want to ADB my device to push the new ROM to it. I've already formatted the SDcard as suggested in the guide. Since clearly no one is clicking the link and reading the guide, I'll post it:
Summary:
- Open up the device and take internal SD Card out.
- Re-assemble the device.
- Partition the external SD Card (3 partitions, two small ext4 and one big FAT32)
- Modify ICS or later ROM's update.sh to use partition 3 as external SD Card.
- Flash modded ROM via CWM (and Google Apps optional).
- Enjoy
Taking it appart:
Don't panic!, if you can use a screwdriver and build with Legos you are qualified to do this!
iFixit does a wonderful job of showcasing how to open the device up that I rather link to them than try to out-do them.
Follow their guide until step 13 then refer back to this guide. http://www.ifixit.co...Teardown/4103/1
Posted Image
To actually remove the Internal SD Card (that is not soldered to the board but in-fact glued to it), I recommend you take an exacto knife (or other small blade or thin screwdriver) and slide it around the edges gently; once the edges are loose, take your screwdriver under the chip and just pop it up.
Posted Image
There will be adhesive residue on the board, I recommend using some gentle solvent to remove it (I used a cloth with a little paint thinner).
Put everything back together (just follow the iFixit guide on reverse) and feel proud that you are done with the hardware mod.
Partition your external SD Card
I used three partitions (all primary, not logical) , two 500 MB ext4 and a FAT32 with the rest of the space.
Linux users will probably not require much help on deciding what software to use, but for Windows users MiniTool Partition Wizard does a good enough job.
Do note that your device will perform according to your external SD Card, so it's not a bad idea to invest in a category 10 SD Card.
Modifing the ROM:
Download your ICS / JB ROM of choice, unzip it and open update.sh
Edit both line 31 and 35 to be as bellow
SD_PART='/dev/block/mmcblk0p3'Save and zip back.
Loading the Modded ROM to the SD:
Because we messed with the SD Cards, CWM will have a bit of trouble finding the external SD Card (until we flash our ROM).
Go ahead and connect your device to your computer and ADB the following command:
adb shell "echo /dev/block/mmcblk0p3 > /sys/devices/platform/usb_mass_storage/lun0/file"
That will allow you to access your SD Card from your PC, just copy your modded ROM to it.
Now, issude the following command:
adb shell mount /dev/block/mmcblk0p3 /sdcard
This will allow you to install the .zip file from CWM, go ahead and do that.
After checking partition types, your device will reboot and appear on a countdown to find the external SD Card, go ahead and reboot it manually before it does automatically (reboot to recovery with volume up).
Flash the .zip again, this time the installation will go successfully and you will have a working device.
Optionally, flash your desired Google Apps.
Now if we could get back to my original question, does anyone know why this device will not allow me to ADB it even when it's in download mode (a.k.a volume down/power button)
I actually got my tablet to boot up this morning for about 1 minute, then it shut off for no reason and did the "verizon" flash again when restarted.

priyana said:
Don't look at Overcome method if you have a CDMA tab.
It will only brick your tab if it ever worked at all.
Regarding bad internal memory, there are two chips. The OneNand 512MB and the MoviNAND 16GB.
If your OneNAND is the one broken, removing the MoviNAND achieved nothing.
The bootloader, modem, (and is it /system too of stock rom?) sits on OneNAND.
Click to expand...
Click to collapse
Please correct my but, what other then the modem.bin File could brick such a CDMA Device?
AFAIK as long as he picks the correct CDMA modem.bin it should work alright?
In the case that I am in error, then how does One recover such a CDMA Device then?

I can easily recover this device if I can get the ADB commands to start working. I feel like no one is reading the instructions. If you look at the link where the instructions are, there is a screenshot of his device. All of that "unable to mount" etc is what was happening to my device, hence why I removed the failed chip.
If I could get my device to show up in ADB, I wouldn't be asking this question!
By the way, I'm on an HP DV6. I tried all this in windows 8 and got nothing, so I installed a backup hard drive and put windows 7 on (this is what I'm on now) to see if that'd make a difference. Still nothing. I also tried on my old Gateway desktop but in download mode my old PC (still USB 1.1 1GHz celeron 512mb ram) the PC has no clue what the tablet is.

So I finally got this thing to boot into 2.2. Now the touch screen is unresponsive and the battery goes to 0 as soon as it's unplugged. Going to take it apart in the morning and make sure everythings connected. Might try a new battery but if this thing doesn't show more promising results soon I'm going to just say screw it and get rid of it.
Edit: Touch screen works but is flipped. If I slide my finger side to side nothing happens. If I slide it up and down i can awkwardly unlock the device. I'm guessing reload the factory image?!

the CDMA device is of different hardware. Not just the modem.
I am not technical enough to explain the difference. But I know Overcome method will brick it.
EliteEmerz: can you at least share how you get the PC to detect your device again?

priyana said:
the CDMA device is of different hardware. Not just the modem.
I am not technical enough to explain the difference. But I know Overcome method will brick it.
EliteEmerz: can you at least share how you get the PC to detect your device again?
Click to expand...
Click to collapse
If you put it into download mode it shows right up in my device list, drivers for "samsung USB device" load up. I can contact the tablet through heimdall to load bootloaders, images, etc.
For some reason I got it working pretty good last night except the touch screen issue. I reloaded the stock rom again and am playing with the SD card partitions since that's how I got it to boot up the last 2 times. I dont even care if I can load Jellybean on, I just want a working tablet.

By the way, this is SOLVED.
It will now boot up using a Stock ROM plus the zImage + recovery from clockworkmod
My touch screen is flipped (so I have to slide up and down to get it to swipe side to side) but at least it's on now. Made a new thread to address the flipped touch screen issue!!

[Q] No Option to Update

Hello,
I've already sent my device back to Asus, where they did absolutely nothing and just sent it right back to me. Complete waste of $16 shipping.
anyway, a while back I received a notification to update firmware. It downloaded, but then the install failed. About 2 weeks later, it prompted me again, and once again it downloaded but then failed to install on the restart. I decided to download the latest firmware on the Asus website, but I have no option to install by SD Card once I'm in Droidboot. My only options are:
1. REBOOT
2. REBOOT DROIDBOOT
3. RECOVERY
4. POWER OFF
Can someone please help? Asus has been absolutely no help, as I just spent another hour yesterday "chatting" with the rep who knew absolutely nothing!
Thanks in advance, cheers!

Well, I guess I stumped everyone in here as well. I just sent the device back to Asus for the second time in 2 weeks. Let's see if they do anything more than just power on the device, deem it "working properly" and promptly send it back to me.

Shaundiesel said:
Hello,
I've already sent my device back to Asus, where they did absolutely nothing and just sent it right back to me. Complete waste of $16 shipping.
anyway, a while back I received a notification to update firmware. It downloaded, but then the install failed. About 2 weeks later, it prompted me again, and once again it downloaded but then failed to install on the restart. I decided to download the latest firmware on the Asus website, but I have no option to install by SD Card once I'm in Droidboot. My only options are:
1. REBOOT
2. REBOOT DROIDBOOT
3. RECOVERY
4. POWER OFF
Can someone please help? Asus has been absolutely no help, as I just spent another hour yesterday "chatting" with the rep who knew absolutely nothing!
Thanks in advance, cheers!
Click to expand...
Click to collapse
I have (2) K01A MemoPad 170CX's, less than 30-days old. Both updated to 4.4.2 via OTA method running software Image Version: V11.2.3.27. (2014-12-23)
On one all of the sudden (and it may be a case the camera never worked) is when the camera is activated the cam app comes up for (3) seconds with the still icon lit up, then the video icon lights up as well for a (1) second then app exits to desktop with a "No Camera is found" error message.
I've been all over the net trying to find into on how to manually flash it.
According to the very cryptic info on ASUS website step # states:
"2. Download device software and Update SOP (From “Manual” Item)"
Googling for info on SOP, you download firmware in zip format, then do (1) extraction of the contents to a MicroSD card formated FAT32 to the root of the card. (After extraction there is a zip file named ifwi.zip that contains (4) *.bin files that remain inside the zip, you don't extract that zip.)
According to info on SOP, with device powered fully up inserting the sd card is supposed to bring up a prompt, a icon on the taskbar/, you click the prompt and the update process begins.
I'm not seeing that.
All I see when the SD card is inserted is a notification the SD is being prepared for use.
When trying to update via DROIDBOOT (W Fastboot wording at bottom of screen), with SD card inserted the DROIDBOOT menu isn't coming up, when I fire up DROIDBOOT without the SD card inserted and insert it DROIDBOOT does not recognize any change has occurred.
Wanted to try re-flashing WW_V11.2.3.27 as I've read in cases the camera gets the No camera found error message the camera firmware gets corrupted somehow. when you hit the return to home-screen icon too fast, I guess when app is in process of opening and it's closed before it initializes fully.
If that doesn't work, trying Version WW_V11.2.3.28 as I for sure don't want to have to send the device back to ASUS when a simple reflash of the firmware would get the camera working again.
Q: Are / were you getting the same results?
(I guess you didn't try SOP method?)
Q: I guess "Fastboot" means "neutered"? Is there a way to bypass? /enable all functions ASUS would not be able to detect if I have to send in unit for service?
Tried copying the contents of the removable SD card to the internal SD card folder...
Nada, zip, nothing.
ASUS needs to provide info on how to run the flash, I've never had this much trouble flashing a device.

WeAreNotAlone said:
I have (2) K01A MemoPad 170CX's, less than 30-days old. Both updated to 4.4.2 via OTA method running software Image Version: V11.2.3.27. (2014-12-23)
On one all of the sudden (and it may be a case the camera never worked) is when the camera is activated the cam app comes up for (3) seconds with the still icon lit up, then the video icon lights up as well for a (1) second then app exits to desktop with a "No Camera is found" error message.
I've been all over the net trying to find into on how to manually flash it.
According to the very cryptic info on ASUS website step # states:
"2. Download device software and Update SOP (From “Manual” Item)"
Googling for info on SOP, you download firmware in zip format, then do (1) extraction of the contents to a MicroSD card formated FAT32 to the root of the card. (After extraction there is a zip file named ifwi.zip that contains (4) *.bin files that remain inside the zip, you don't extract that zip.)
According to info on SOP, with device powered fully up inserting the sd card is supposed to bring up a prompt, a icon on the taskbar/, you click the prompt and the update process begins.
I'm not seeing that.
All I see when the SD card is inserted is a notification the SD is being prepared for use.
When trying to update via DROIDBOOT (W Fastboot wording at bottom of screen), with SD card inserted the DROIDBOOT menu isn't coming up, when I fire up DROIDBOOT without the SD card inserted and insert it DROIDBOOT does not recognize any change has occurred.
Wanted to try re-flashing WW_V11.2.3.27 as I've read in cases the camera gets the No camera found error message the camera firmware gets corrupted somehow. when you hit the return to home-screen icon too fast, I guess when app is in process of opening and it's closed before it initializes fully.
If that doesn't work, trying Version WW_V11.2.3.28 as I for sure don't want to have to send the device back to ASUS when a simple reflash of the firmware would get the camera working again.
Q: Are / were you getting the same results?
(I guess you didn't try SOP method?)
Q: I guess "Fastboot" means "neutered"? Is there a way to bypass? /enable all functions ASUS would not be able to detect if I have to send in unit for service?
Tried copying the contents of the removable SD card to the internal SD card folder...
Nada, zip, nothing.
ASUS needs to provide info on how to run the flash, I've never had this much trouble flashing a device.
Click to expand...
Click to collapse
I tried everything under the sun....I extracted the zip, nothing. I left it as a zip, nothing. I went to recovery, nothing. You name it, I did it. So, I sent back to Asus for the second time in 2 weeks. I just checked the status of my RMA with Asus, and it states that "No trouble found." I'm not sure how NO TROUBLE IS FOUND when I can't even update to Asus latest firmware for their device? In addition, I do not get the options to try to manually update (Not that I should even have to go that route when it should be OTA). I will never own another Asus product. I've only had my tablet for 4 months, 2 1/2 months of which it sat in my desk, unused. Asus is garbage.

Did you remove any system files or freeze them? Did you root?

lvnatic said:
Did you remove any system files or freeze them? Did you root?
Click to expand...
Click to collapse
No I did not remove any system files or freeze them, that I know of. I rooted shortly after purchasing this, but unrooted the device about 2 weeks later.
Thoughts?

lvnatic said:
Did you remove any system files or freeze them? Did you root?
Click to expand...
Click to collapse
If you are talking to me in which camera(s) both seem to not be found by the OS ME170 is STOCK, STOCK, STOCK.
Contacted the vendor TigerDirect, noticed that they claim they will NOT do exchanges due to "manufacturers polices". While I realize it costs vendor (TigerDirect) to handle exchanges that wording could also indicate they have run the numbers and don't want to be bothered.
Reading about ASUS service, and my interaction with ASUS when I contacted them does not insipre incidence so I'm hoping to be able to flash the device and cameras will start functioning again.
In regards to the customer being able to flash a device (Which I done numerous times on other brands)
I know ASUS is a Asian based manufacturer and sells worldwide but they really need to have persons who can write in better ENGLISH.. ASUS needs to publish detailed instructions on how to flash device, additionally they need to update support pages with any drivers, tools to do so vs just posting the firmware with vaque reference to SOP.
Q: How long after firmware updates appears on ASUS site does OTA update get pushed?
..

Just an update....
Just received my memo pad back, and it appears to be finally fixed. It took sending it back twice, and escalating to a supervisor, but it looks good now. I've actually received 3 firmware updates in 2 days, so it was REALLY behind! What firmware are you all running right now? I have WW-3.2.23.201.

I think 201 is the latest. Mine is still on 199 though and it won't try to update again since it failed a couple of weeks ago.

Teclast X80 Pro (E3E6) Dual OS (Win10/Android 5.0): Remove Windows

Hey guys. Sorry to bother you in the X98 section, but since there's no section for the X80 yet and maybe the devices have some similarities, I hope it's ok.
The tablet worked fine, but to remove any possible bloatware under Windows or Android, I reset Windows. Somehow the device must have crashed (low battery?) and now I can't boot to Windows anymore (black screen and / or boot loop). Of course I made no backup / recovery disk. Android still works fine and I still get into BIOS / UEFI.
I tried reinstalling Windows via OTG with USB stick. I got to the point where I can choose a partition. Problem is, there are lots of partitions (Android, recovery, System and so on). I located the Windows partition, formatted / deleted it and tried to reinstall Windows on this partition. Just the exact way I would do it on a PC. Somehow it won't install on this partition. The error message says something about "the partitions are not in the recommended order. Further information for installation on GPT-volumes..." (I don't know the exact English phrasing because everything is in German). I chose "continue anyway". Then I get the message that "the EFI-system is not formatted in NTFS. Format the partition to FAT32 and start install procedure again". I press ok and get back to Windows Setup (Install now).
I also tried different repair and recovery options. One time I got error code 0xC0000034. Funny thing is, Windows still seems to be there because while trying to repair / recover I tried to load some drivers and could see the hard drives and folders under Windows.
I tried downloading the original roms here: http://pan.baidu.com/s/1qYEa8gc
You need a Baidu account for the larger files and after days and days I gave up to create such an account as it seems to work only with a mainland China number. There's an option for oversea mobiles but that's not working. I tried a QQ-account, but Baidu wants to link with it and you need that telephone number again. So apparently there's no way to get the original files that way.
I found some stuff here: http://www.needrom.com/download/teclast-x80-pro-dualboot/ but that's only a tutorial file in Chinese and some flash programms / drivers (also got them from Baidu - smaller files are possible to download without an account).
Long story short: I guess recovering Windows 10 is too much effort, so I want to make the tablet Android only and of course want to use the whole capacity for Android. I found a thread on reddit about removing Windows on the X98: https://www.reddit.com/r/teclast/comments/479eua/teclast_x89_how_to_remove_windows_10/
But I have no idea which partitions are definitely needed for Android and which ones I can safely delete. I found a partition map here: http://wheresmykeyboard.com/2015/08/teclast-x98-air-64gb-dual-boot-default-partition-map/ but that doesn't help me that much because they look different.
Attached you will find a photo of all the partitions on my device. I guess there are some which were created during the failed Windows installation because I had about 20 GB free space and now only 17.7 GB.
So is there anybody out there who knows if it's possible to remove Windows completely and which partitions I have to delete?

Did you ever figure this out? I just bought an X80 Pro and was thinking of doing something similar since I plan on making it an android-only tablet.

Deathgazer said:
Did you ever figure this out? I just bought an X80 Pro and was thinking of doing something similar since I plan on making it an android-only tablet.
Click to expand...
Click to collapse
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.

metalaxi said:
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.
Click to expand...
Click to collapse
Please do describe how you achieved Android-only with 32 GB memory
Cheers

metalaxi said:
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.
Click to expand...
Click to collapse
Yes please tell us how metalaxi , it'll be much appreciated.:good:

Ok, guys. Since some of you are asking how I did it, I'm going to try to explain it. It's kinda embarrassing that I don't remember the exact way but I hope it helps somehow. I used the tutorial from this site: http://techtablets.com/forum/topic/x80-plus-android-os-only/#login
Even though it's supposed to be for the Plus model, it also worked on the Pro. Btw, the guy Alex in that thread is me .
You can download all the files from my Google Drive here: https://drive.google.com/open?id=0BxEFqy4Rt9w_cnh3VG9ySk5sOHM
You need
- Android5.1 Upgrade Tool.rar
- X80 Pro (E3E6)- Dual OS - Android5.1-V1.04 Firmware.rar
- gpt.rar (Credit goes to Allember @techtablets-forum; hope it's ok to spread the file)
First you have to install the flash tool. Unrar the firmware and replace the gpt.bin. Then flash the firmware by checking BLANK.
Problem is that when I did all that, my Windows was already crushed and wasn't working anymore. I can't remember anymore if I erased the Windows partitions or any others beforehand. If you're not interested in Windows anymore, just flash it without changing or erasing any of the partitions. I guess by replacing the gpt-file, you do all that automatically.
I hope this somehow helps you. Feel free to ask for more help.
Have a good night!

metalaxi said:
Ok, guys. Since some of you are asking how I did it, I'm going to try to explain it. It's kinda embarrassing that I don't remember the exact way but I hope it helps somehow. I used the tutorial from this site: http://techtablets.com/forum/topic/x80-plus-android-os-only/#login
Even though it's supposed to be for the Plus model, it also worked on the Pro. Btw, the guy Alex in that thread is me .
You can download all the files from my Google Drive here: https://drive.google.com/open?id=0BxEFqy4Rt9w_cnh3VG9ySk5sOHM
You need
- Android5.1 Upgrade Tool.rar
- X80 Pro (E3E6)- Dual OS - Android5.1-V1.04 Firmware.rar
- gpt.rar (Credit goes to Allember @techtablets-forum; hope it's ok to spread the file)
First you have to install the flash tool. Unrar the firmware and replace the gpt.bin. Then flash the firmware by checking BLANK.
Problem is that when I did all that, my Windows was already crushed and wasn't working anymore. I can't remember anymore if I erased the Windows partitions or any others beforehand. If you're not interested in Windows anymore, just flash it without changing or erasing any of the partitions. I guess by replacing the gpt-file, you do all that automatically.
I hope this somehow helps you. Feel free to ask for more help.
Have a good night!
Click to expand...
Click to collapse
Hi @metalaxi. Do you think its possible to like "reverse" and use the same files to remove Android instead and maintain the Windows 10? Appreciate to hear from you. Thanks!

Do we have to change the gpt before doing what you said in your PDF? Or I have just to follow your PDF?

Hi guys, got mine a few months and want to get rid of the Windows part, but the instructions are insufficient for a joker like me.....
1. Download the firmware, its 4 parts of rar being zipped together
2. flash the firmware HOW?!?!?! I have no Idea...... please give us some closer instructions.

reycharlesconrad said:
Hi @metalaxi. Do you think its possible to like "reverse" and use the same files to remove Android instead and maintain the Windows 10? Appreciate to hear from you. Thanks!
Click to expand...
Click to collapse
Sorry, I can't answer that sufficent enough. As far as I know, you can just delete all partitions except the ones from Windows. Then format the unallocated space and merge it with the one from Windows. No guarantee!

dirkzelf said:
Hi guys, got mine a few months and want to get rid of the Windows part, but the instructions are insufficient for a joker like me.....
1. Download the firmware, its 4 parts of rar being zipped together
2. flash the firmware HOW?!?!?! I have no Idea...... please give us some closer instructions.
Click to expand...
Click to collapse
1. Which 4 parts do you mean?
2. To flash any firmware, you need to install all the upgrade tools:
IntelAndroidDrvSetup1.5.0
iSocUSB-Driver-Setup-1.2.0
PhoneFlashTool_5.3.4.0_internal_win32

metalaxi said:
1. Which 4 parts do you mean?
2. To flash any firmware, you need to install all the upgrade tools:
IntelAndroidDrvSetup1.5.0
iSocUSB-Driver-Setup-1.2.0
PhoneFlashTool_5.3.4.0_internal_win32
Click to expand...
Click to collapse
it's too long ago, so I don't know what I exactly did there, but since there was no reply for a long time, I just took a shot and worked out well, now I have an Android only tablet.
I just got lucky I guess....

partition help
Hi, please help.
I have x80pro e3e8
I managed to erase a complete disk partition.
You are trying to revive again, fail.
installed here:
iSocUSB-Driver-Setup-1.2.0
IntelAndroidDrvSetup1.5.0
PhoneFlashTool_5.3.4.0_internal_win32
downloaded here:
Firmware (20161020_SZ)
Tablet joined and tried to flash.
* failed - failed loadet.efi
Please help. I can not download from Baidu
* If I use phoneFlasTool and flash a blank disc - Create Flash partition and dual boot and replace recovery?
What to do with an empty disc?
Thanks for any advice

It is not so hard. By mine it was only trial and error. Installiert all drivers an go in the bootloader with three Finger method. Go two levels up and go into bootloader. Then connect to PC and look in Intel flashing tool if connection is reconiced correctly. Select the downloaded file and select flash. Thats it. Device will reboot and you are ready to go.

theone0987654321 said:
It is not so hard. By mine it was only trial and error. Installiert all drivers an go in the bootloader with three Finger method. Go two levels up and go into bootloader. Then connect to PC and look in Intel flashing tool if connection is reconiced correctly. Select the downloaded file and select flash. Thats it. Device will reboot and you are ready to go.
Click to expand...
Click to collapse
Thank you for the advice. That's right, I did it was marked. I found a reason. rom file was saved on desktop, and had a long name (as I downloaded it) It must copy the file to C've renamed the firmware. Everything went alright. I downloaded and used the GPT files for resizing disk and now goes all right. Thank you for responding to my question.

hi, I have problem while flashing.
Phone flash tool always gives ERROR
Automatic reboot is not supported on this device, please reboot the device manually
ERROR : [Port 0/1/4] Failed to reboot the device
Click to expand...
Click to collapse
Any idea what to do? I followed all the steps, tried many times, still same problem. And it's not possible to reboot device manually, because then it lose connection with PC

Restock OS Without Android
Hi there.
I have to restock my Device, but the Intel Flash Tool does not recognize my Device.
I cannot boot into Android to turn on USB-Debugging or go into fastboot mode
How do i flash my device without any OS installed?
---------- Post added at 04:03 PM ---------- Previous post was at 03:52 PM ----------
affe2000 said:
Hi there.
I have to restock my Device, but the Intel Flash Tool does not recognize my Device.
I cannot boot into Android to turn on USB-Debugging or go into fastboot mode
How do i flash my device without any OS installed?
Click to expand...
Click to collapse
Ok, got it working... dnx fastboot mode is there

....

hello guys by accident i deleted windows 10, how can i reinstall them? i dont have the windows 10 icon in the dual boot select i only see the android icon

mike mike baby said:
hello guys by accident i deleted windows 10, how can i reinstall them? i dont have the windows 10 icon in the dual boot select i only see the android icon
Click to expand...
Click to collapse
Straightforward if you can obtain a USB stick capable of storing over 7GB (some 8GB sticks may not); USB hub (ideally a powered hub); USB keyboard; OTG cable.
1) Obtain the Windows files of the correct firmware. The procedure outlined here is for E6E9 firmware, but other firmware will be similar. Download the circa 6.5GB E6E9 firmware Windows files from https://yadi.sk/d/XEvRsoiD3Q4vKX or https://mega.nz/#F!I0AXGR5C!YiNFkZL9DIvzepH28qAjEQ (or from appropriate source for your firmware version).
Decompress the downloads as required to obtain six folders and two files.
2) Format the stick to FAT32.
3) Name the stick WINPE (five uppercase characters).
4) Copy the previously mentioned folders and files to the USB stick.
5) Plug USB stick and USB keyboard into hub; plug hub into OTG cable; plug OTG cable into tablet whilst the tablet is off.
6) Turn on tablet and immediately start tapping << Delete >> key on USB keyboard. This should open the UEFI config section prior to Android boot option. If the tablet displays the Android boot option, turn off the tablet, wait a few seconds, then turn on and start tapping << Delete >> key on USB keyboard again.
7) When in UEFI, touch the title menu option of << Save and Exit >> and look in the << Boot Override >> section for the name of your USB stick, then touch the name of your USB stick. The screen will immediately go blank as the tablet starts to boot from the USB stick.
8) After a few minutes, a numerically display of progress will be displayed in a CMD window.
9) After reaching 100% and nearing completion of the overall installation, the tablet will prompt for acceptance, so accept that prompt.
10) The setup will run a few final operations for a few seconds, then automatically reboot.
11) Done.
You will be prompted to complete the OOBE on each Windows boot until you complete OOBE.