Related
I just did the acmeuninstall in prep for ics but when back in webos i cannot enter usb mode... in my computer it shows as a drive but with 0bytes unabke to create any files / folders...
what went wrong?
webos doctor the only answer?
WebOS doctor fails too...
Gets to about 83% then says the phone has been disconnected?
Starting to wish I just left CM7 on...
Can anybody help please
i found this tut that might help you out it sounds like it might be the same issue
http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed.html
hope its ok to post the link
thanks
To get the Doctor to finish, first try rebooting both your TP and PC and connect again. Also try a different usb port.
If the Doctor is still failing, then in WebOS go into Device Info -> Reset Options -> Full Wipe. After Full Wipe, try WebOS Dr. again. If it still fails, then the SD partition will need some more work from the WebOS command line interface. If you Google WebOS Doctor fails at xx%, you will get a good amount of hits.
Hopefully, because it's failing at a high % of completion, you won't have to go the command line route. Good luck!
Mike T
OK - I managed to get WebOS Doctor to work this morning... Left it on charge last night and it just worked first time today...
Now I cannot enter USB mode on the device in WebOS no pop-up appears... I tried the hardware enter USB mode by holding power and vol down while in WebOS... Still it does not work...
I need to create the folder cminstall and put the files in for ICS install...
Anyone got any ideas what's wrong with the device? How to enter USB mode for file transfer?
I've FULL WIPED in WebOS, WebOS Doctored it twice today but still cannot enter USB mode...
Please Help!
I think I found the route cause of my issues... The cable!
Now using the official cable and can get into usb mode every time....
But here's the kicker... The script in cmd come up with an error..
The system cannot find the file specified?
I'm typing novacom boot mem:// <ACMEinstaller
Also tried it like novacom boot mem:// < ACMEinstaller
What is the issue? The files are in both root of touchpad in cminstall folder and also Palm, Inc in program files...
Never had half as many issues with CN7 as I am with this...
Can some one please help??
If you are installing cm9 you need acmeinstaller2
With Classicnerd ICS you ACMEInstall moboot&CWM then flash rom&gapps from Recovery
I'm trying to install the buttah rom which states to use acmeinstaller 1 in the docs?
JayGB2011 said:
I'm trying to install the buttah rom which states to use acmeinstaller 1 in the docs?
Click to expand...
Click to collapse
YES but just acmeinstall moboot & CWM
colin_404 said:
YES but just acmeinstall moboot & CWM
Click to expand...
Click to collapse
That's exactly what I have in the cminstall folder...
acmeinstaller and moboot...
strange? keeps saying that file / folder not recognised?
JayGB2011 said:
I think I found the route cause of my issues... The cable!
Now using the official cable and can get into usb mode every time....
But here's the kicker... The script in cmd come up with an error..
The system cannot find the file specified?
I'm typing novacom boot mem:// <ACMEinstaller
Also tried it like novacom boot mem:// < ACMEinstaller
What is the issue? The files are in both root of touchpad in cminstall folder and also Palm, Inc in program files...
Never had half as many issues with CN7 as I am with this...
Can some one please help??
Click to expand...
Click to collapse
Heres a thought is your folder named ACMEinstaller OR ACMEInstaller
neither.... its named cminstall as normal.
Thanks for your help though... I've wasted a day on this so far with no luck
sorry not your folder , your file in palm, inc
ACMEInstaller... I'll give it a go without the cap for installer
EDIT: still comes up The system cannot find the file specified
ok in cmd window have you navigated to palm, inc directory
IF not open palm, inc folder in program files
then hold shift and right click. from the list open command window then
novacom boot mem:// < ACMEInstaller
I'm in the right place and using the command above but this error doesn't seem to change?
in "cminstall" folder u should have "moboot" and "clockworkmod" recovery
In Palm, inc folder u should have "ACMEInstaller" file
Then when u run the command if u get that error the cmd window cant be linked to the "palm, inc" folder
If the TP wasnt found it would say "unable to find device"
colin_404 said:
in "cminstall" folder u should have "moboot" and "clockworkmod" recovery
In Palm, inc folder u should have "ACMEInstaller" file
Then when u run the command if u get that error the cmd window cant be linked to the "palm, inc" folder
If the TP wasnt found it would say "unable to find device"
Click to expand...
Click to collapse
What he said, it's very important to be in the same folder as ACMEInstaller when you run the command.
I am trying to install the Samsung USB driver from Samsung Galaxy S3 ToolKit but it insists the mobile phone is in use. It says "The mobile phone is in use. To install normally, you need to remove the device and restart the computer. Please run the SAMSUNG USB Driver for Mobile Phones installer again after restarting." I have tried restarting but it still shows that stupid error message. Using Windows XP. How do I install the drivers?
vpwrf said:
I am trying to install the Samsung USB driver from Samsung Galaxy S3 ToolKit but it insists the mobile phone is in use. It says "The mobile phone is in use. To install normally, you need to remove the device and restart the computer. Please run the SAMSUNG USB Driver for Mobile Phones installer again after restarting." I have tried restarting but it still shows that stupid error message. Using Windows XP. How do I install the drivers?
Click to expand...
Click to collapse
You could try this.
Kangburra said:
You could try this.
Click to expand...
Click to collapse
Still the same error.
vpwrf said:
Still the same error.
Click to expand...
Click to collapse
Is the phone stuck in Device manager? Remove it and try again, do not plug the phone in while installing the drivers.
Kangburra said:
Is the phone stuck in Device manager? Remove it and try again, do not plug the phone in while installing the drivers.
Click to expand...
Click to collapse
What does it appear as in the device manager that needs removing? I tried removing a couple of things that appeared when I plugged it in but still shows that error.
Uninstall everything Samsung from the PC.
Reboot the phone and the PC.
Follow the guide in the link above, then when finished plug the phone in.
Kangburra said:
Uninstall everything Samsung from the PC.
Click to expand...
Click to collapse
How do I do that? I have made sure nothing Samsung is in the device manager and restarted again but still can't install the driver.
vpwrf said:
How do I do that? I have made sure nothing Samsung is in the device manager and restarted again but still can't install the driver.
Click to expand...
Click to collapse
You are going to need help with the PC, it is not a phone problem. Take it to a PC shop near you.
It's the stupid mistake I made by plugging the phone in before installing the drivers. It looks like the only way now is by doing a clean Windows installation unless someone can help me properly remove the failed drivers.
vpwrf said:
It's the stupid mistake I made by plugging the phone in before installing the drivers. It looks like the only way now is by doing a clean Windows installation unless someone can help me properly remove the failed drivers.
Click to expand...
Click to collapse
You just need someone who can do remove the device for you. Don't you have computer shops where you live? No need to wipe the whole machine over a single device.
I think it's a waste of money taking it to a computer shop. It will cost at least £20
SOLVED
After several hours I finally have solved this problem.
go to the C:\Documents and Settings\All Users\Application Data\Samsung\Device Error Recovery
open the file: default-0.log
scroll to the end of this file, you will find something like:
"2014/02/01 22:00:26 0625 [setup(dll) ][RemoveAllDriverDeviceKey:656 ] Delete Driver & Device Keys Failed1(-536870396)... USB\Vid_04e8&Pid_6860&Rev_0400"
Now, open regedit and find all keys with "Vid_04e8&Pid_6860" in their names. Delete them all.
If you have a problem with deleting, change the permisions for the key (right-click on key and add yourself to the user group).
And now you can install new USB driver.
Regards
gregorypeck said:
After several hours I finally have solved this problem.
go to the C:\Documents and Settings\All Users\Application Data\Samsung\Device Error Recovery
open the file: default-0.log
scroll to the end of this file, you will find something like:
"2014/02/01 22:00:26 0625 [setup(dll) ][RemoveAllDriverDeviceKey:656 ] Delete Driver & Device Keys Failed1(-536870396)... USB\Vid_04e8&Pid_6860&Rev_0400"
Now, open regedit and find all keys with "Vid_04e8&Pid_6860" in their names. Delete them all.
If you have a problem with deleting, change the permisions for the key (right-click on key and add yourself to the user group).
And now you can install new USB driver.
Regards
Click to expand...
Click to collapse
Thank you very much. I had the same error and your method worked for me
----
Here are my observations:
In my log, the error had been exactly the same.
I searched my registry for the key Vid_04e8&Pid_6860.
I found it in the following locations:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\VID_04E8&PID_6860
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\USB\VID_04E8&PID_6860
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_04E8&PID_6860
I think it is only necessary to modify CurrentControlSet, the other keys are just backups.
I had to right-click VID_04E8&PID_6860, change the permission settings to full access and then I deleted the whole key named VID_04E8&PID_6860.
Finally the driver installer worked.
gregorypeck said:
After several hours I finally have solved this problem.
go to the C:\Documents and Settings\All Users\Application Data\Samsung\Device Error Recovery
open the file: default-0.log
scroll to the end of this file, you will find something like:
"2014/02/01 22:00:26 0625 [setup(dll) ][RemoveAllDriverDeviceKey:656 ] Delete Driver & Device Keys Failed1(-536870396)... USB\Vid_04e8&Pid_6860&Rev_0400"
Now, open regedit and find all keys with "Vid_04e8&Pid_6860" in their names. Delete them all.
If you have a problem with deleting, change the permisions for the key (right-click on key and add yourself to the user group).
And now you can install new USB driver.
Regards
Click to expand...
Click to collapse
Worked perfectly for me too, with one exception - at first I was not able to delete some of the keys. I had to right click on them, click permissions, and then give Everyone full access so I could delete them.
Hello, i have the same problem on windows 7, and cant connect my galaxy s4
- The mobile phone is in use. To install normally, you need to remove the device and restart the computer. Please run the SAMSUNG USB Driver for Mobile Phones installer again after restarting.
that hint will work on win7?
thank you
and i try it, and cant delet key, runs regedit as admin and cant change permision.
ty
Try this one Universal ADB Driver
gregorypeck said:
After several hours I finally have solved this problem.
go to the C:\Documents and Settings\All Users\Application Data\Samsung\Device Error Recovery
open the file: default-0.log
scroll to the end of this file, you will find something like:
"2014/02/01 22:00:26 0625 [setup(dll) ][RemoveAllDriverDeviceKey:656 ] Delete Driver & Device Keys Failed1(-536870396)... USB\Vid_04e8&Pid_6860&Rev_0400"
Now, open regedit and find all keys with "Vid_04e8&Pid_6860" in their names. Delete them all.
If you have a problem with deleting, change the permisions for the key (right-click on key and add yourself to the user group).
And now you can install new USB driver.
Regards
Click to expand...
Click to collapse
Thank you very much, worked for me too
gregorypeck said:
After several hours I finally have solved this problem.
go to the C:\Documents and Settings\All Users\Application Data\Samsung\Device Error Recovery
open the file: default-0.log
scroll to the end of this file, you will find something like:
"2014/02/01 22:00:26 0625 [setup(dll) ][RemoveAllDriverDeviceKey:656 ] Delete Driver & Device Keys Failed1(-536870396)... USB\Vid_04e8&Pid_6860&Rev_0400"
Now, open regedit and find all keys with "Vid_04e8&Pid_6860" in their names. Delete them all.
If you have a problem with deleting, change the permisions for the key (right-click on key and add yourself to the user group).
And now you can install new USB driver.
Regards
Click to expand...
Click to collapse
Works like a charm, thanks for the solution.
gregorypeck said:
After several hours I finally have solved this problem.
go to the C:\Documents and Settings\All Users\Application Data\Samsung\Device Error Recovery
open the file: default-0.log
scroll to the end of this file, you will find something like:
"2014/02/01 22:00:26 0625 [setup(dll) ][RemoveAllDriverDeviceKey:656 ] Delete Driver & Device Keys Failed1(-536870396)... USB\Vid_04e8&Pid_6860&Rev_0400"
Now, open regedit and find all keys with "Vid_04e8&Pid_6860" in their names. Delete them all.
If you have a problem with deleting, change the permisions for the key (right-click on key and add yourself to the user group).
And now you can install new USB driver.
Regards
Click to expand...
Click to collapse
Can't get autorisation to delete, can you help me please ?
samsung usb drivers
question to anyone: hi i am very new to technology and am self learning about android, rooting, and about my devices. i am learning this stuff on my old samsung galaxy s3 gt-i9305t 4g telstra, which rus kitkat 4.4.4. i have been trying to download samsung usb drivers since i am frugal i would like to do all this for free which i am constantly reminded by other members thats the way to go . could anyone point me to a good website for the drivers, also if you know of a good tutorial website or you tube link i ill be forever greatful to you. thank you for your time
Hello everyone,
I have one Sony Experia Sola MT27i whit Android 4.0.4, core version 3.0.8+, Compile version 6.1.1.B.54. I would like to upload the "Pepper" OS on it.
So i download the flashtool-0.9.10.1-windows (have Windows 7 Ultimate 64 bit all updates on it) and install it... then install the drives for Sola and Flashmode, Flashboot from driver directory, but an error appear "DPinst.exe does not execute on your current Operating System". I tray install them running install again in Compatible mode and no luck again. Then i found in the forum a nookcolor-easyADB installation for windows 7 32/64bit tray it -again noting and an exclamation mark in device manager is there like before. On phone i activate the USB debugger and allow Unknown source option, USB connection mode is MSC.
Were i do wrong- is flashtool the needed program for this version of Sola or i need other drivers
Any help would be appreciated! Thank you
Are u sure u r opening the 64bit of flashtool??
drsanket_xperia_u said:
Are u sure u r opening the 64bit of flashtool??
Click to expand...
Click to collapse
Yes, that's right. Can't install the drivers Flashmode, Flashboot from driver directory, an error appear "DPinst.exe does not execute on your current Operating System". Even i go C:\Users\XXX\AppData\Local\Temp\Flashtool traying to run DPinst64.exe -same error?!
I've had the same issue on my Windows 8 laptop. The drivers installed successfully after disabling "Driver Signature Enforcement" on your Windows operating system. Reboot your PC and press F8. Then select " Disable Driver Signature Enforcement". Then install the unsigned driver.
ОК i managed to run all the stuff but on other PC.. now have other problem. I install CWM v6.0.1.2 (recovery) on phone going on whit steps are shown here:
sites.google.com/site/projectfreexperia/download/howto-install , but i download the update on External SD card FXP202-cm-9-20130111-unofficial-pepper.zip (not just the SD -internal), because don't have free memory on internal.. then i tray to run the zip file form the ext SD i see the file every think seems to look OK then a menu appear whit a column of NO answers and one YES then again 3 NO.. after check the YES its says that Finding update package... then E: Can't mount /external_SD/FXP202-cm-9-20130111-unofficial-pepper.zip
Installation aborted.
Any help would be appreciated!
Case can be close! I run all the stuff..
I am new to this,I am running Touchpad toolbox,and did a complete reset then Install Android the touchpad folder opens on the PC i then copied over the following 3 .zip files
recovery-clockwork-6.0.4.7-tenderloin.zip
gapps-kk-20140105.zip
cm-11-20140609-UNOFFICIAL-tenderloin.zip
then eject touchpad from pc and unmount.
I just keep getting the error NO RECOVERY FILE FOUND, ABORTING
Could someone help please,I don't know what to do.
Thanks...
Touchpad Toolbox Install Android, error "No supported recovery file found. Aborting."
coleraine said:
I am new to this,I am running Touchpad toolbox,and did a complete reset then Install Android the touchpad folder opens on the PC i then copied over the following 3 .zip files
recovery-clockwork-6.0.4.7-tenderloin.zip
gapps-kk-20140105.zip
cm-11-20140609-UNOFFICIAL-tenderloin.zip
then eject touchpad from pc and unmount.
I just keep getting the error NO RECOVERY FILE FOUND, ABORTING
Could someone help please,I don't know what to do.
Thanks...
Click to expand...
Click to collapse
TouchPad 32GB using TouchPad Toolbox v40 2014-05-18
similar error with this Syntax:
No supported recovery file found. Aborting.
** It turns out, this is the same message after the Unmount Media Volume step, even if I don't copy any files to HP Touchpad/ttinstall
** Not sure what is causing this, and at this point I don't know what I should do to load KitKat or get a bootable Android
THIS WAS A BAD USB CABLE - It appeared to work fine for TPToolbox load, but that is deceptive,
the zip files copied are never valid!! Once I switch to new mini-usb it was fine....
SOLVED BY THREAD http://forum.xda-developers.com/showthread.php?t=2774779&page=2
which was excellent effort in the debugging process ...Where do these other cables come from?
Hello,
I rooted my Hisense Sountab MA-327 and changed some issues in the builds.prop (before I backup-ed this file first). There was no result for what I was doing after a successful restart, so I copied the backup file back to the system folder. After I restart the device, the system hangs in the boot. I tried to login with ADB to see whats went wrong, but I can can not find a good USB driver for this device. Can some please help me? The device is no useless.
- Is there a good USB driver for the Hisense SoundTab MA-327?
- What do I need the get in the system (ADB tools)?
- Or ... is there a flash/firmware for the Hisense Soundtab MA-327 somewhere available?
I really hope some can help me out.
Thanks in advance
Hans
kameraad759 said:
Hello,
I rooted my Hisense Sountab MA-327 and changed some issues in the builds.prop (before I backup-ed this file first). There was no result for what I was doing after a successful restart, so I copied the backup file back to the system folder. After I restart the device, the system hangs in the boot. I tried to login with ADB to see whats went wrong, but I can can not find a good USB driver for this device. Can some please help me? The device is no useless.
- Is there a good USB driver for the Hisense SoundTab MA-327?
- What do I need the get in the system (ADB tools)?
- Or ... is there a flash/firmware for the Hisense Soundtab MA-327 somewhere available?
I really hope some can help me out.
Thanks in advance
Hans
Click to expand...
Click to collapse
Some please!
What I understood:
You are stuck in a bootloop because you edited the build.prop file, luckily, you made a backup and you know what adb is, and, hopefully, you know how to use it.
How do we solve it?
Well, I need some more information, can you boot into recovery or boot into fastboot mode? If you can, we can make your backup build.prop file active and if that doesn't work, we can just reflash stock ROM, everything will be wiped if you flash stock ROM though.
Hi RAZERZDAHACKER,
Thanks for your help. Yes I can boot into recovery/boot mode (android robot with sign and even can see the menu (Volume + Start). I tried to make an USB connection, but I can not find any driver for this device. Under XP I find a good USB driver, but then ADB want install, in Windows 7 or 10 its the opposite. And even with some not good driver, I see with the command "adb devices": No access, and then 1234567890ABCDEF. Can not find any driver. If possible its no problem to reflash stock ROM, but I do not know how to do this.
I appreciate your help.
Hans
kameraad759 said:
Hi RAZERZDAHACKER,
Thanks for your help. Yes I can boot into recovery/boot mode (android robot with sign and even can see the menu (Volume + Start). I tried to make an USB connection, but I can not find any driver for this device. Under XP I find a good USB driver, but then ADB want install, in Windows 7 or 10 its the opposite. And even with some not good driver, I see with the command "adb devices": No access, and then 1234567890ABCDEF. Can not find any driver. If possible its no problem to reflash stock ROM, but I do not know how to do this.
I appreciate your help.
Hans
Click to expand...
Click to collapse
Thanks for replying, you can boot into recovery which is probebly the most vital thing of this whole process (YaY), in recovery, there should be an option called "apply update from adb", if not, kindly name the options. When you click it, what happens in adb? From my experience you don't need drivers to acces "adb sideload" (as the feature is called).
Yes I see the option.
--------
Now send the package you want to apply
to the device with "adb sideload <filename>" ....
---------
I made the backup build.prop earlier to /sdcard on the device. Maybe that was not a good idea.
Oke whats the next step?
Hans
kameraad759 said:
Yes I see the option.
--------
Now send the package you want to apply
to the device with "adb sideload <filename>" ....
---------
I made the backup build.prop earlier to /sdcard on the device. Maybe that was not a good idea.
Oke whats the next step?
Hans
Click to expand...
Click to collapse
Oh, I thought you had it on the pc, I am not sure but can you do "adb sideload /sdcard/build.prop /system"?
RAZERZDAHACKER said:
Oh, I thought you had it on the pc, I am not sure but can you do "adb sideload /sdcard/build.prop /system"?
Click to expand...
Click to collapse
That don't work. I get the help of adb when I give the command string. Do not know how this will work with a USB connection. How should Windows and adb know when to get the input from?
when i try adb usb, it start the daemon , but then error: closed
adb devices -> 0123456789ABCDEF sideload
Oke maybe a reflash stock ROM. How does this work?
Again I appreciate all your help.
Hans
kameraad759 said:
That don't work. I get the help of adb when I give the command string. Do not know how this will work with a USB connection. How should Windows and adb know when to get the input from?
when i try adb usb, it start the daemon , but then error: closed
adb devices -> 0123456789ABCDEF sideload
Oke maybe a reflash stock ROM. How does this work?
Again I appreciate all your help.
Hans
Click to expand...
Click to collapse
You get error closed because you're in sideload, I realized that you can't move files in adb sideload. If you want to flash stock ROM, download this and move it to the adb folder and type "adb sideload nameoftheimg.img".
Hope that helps
RAZERZDAHACKER said:
You get error closed because you're in sideload, I realized that you can't move files in adb sideload. If you want to flash stock ROM, download this and move it to the adb folder and type "adb sideload nameoftheimg.img".
Hope that helps
Click to expand...
Click to collapse
I will try that of course, but the same image I previously put on SDCARD, inserted it in the bay and dis an update from external drive. Then a message came that hardware was not compatible with the update. I can not find a flash for MA-327 and (again) not for the USB driver. But I will try what you suggest.
I get the error: cannot read 'MA347ENMEG3EV02.img'
Image is 1.744.423.512 size
Hans
kameraad759 said:
I get the error: cannot read 'MA347ENMEG3EV02.img'
Image is 1.744.423.512 size
Hans
Click to expand...
Click to collapse
If you have a sdcard that is large enough for the image (minimum 4gb) you can download win32diskimager. Open win32diskimager and select the .img file. Then, connect your sdcard to your pc and format it to fat32. Then locate it on win32diskimager and write the file. This will take a very long while so please be patient. Once it's done, put it in the hisense and attempt to boot. The android "bios" will go through all the nand memory for a bootable image but since that wont work, it will proceed to check external devices (as far as I know) and once it sees the bootable sdcrad it will, hopefully boot. Once you have booted, don't eject the sdcard, conncect the hisense to your pc and install the necessary adb drivers, then, boot into recovery and hit apply update from adb. Then type adb sideload nameoftheimg.img.
Hopefully that works
Oke. But if it boot from sdcard, then it will not install the img from sdcard?? I though it would.
What are the 'necessary adb drivers'?
And when i give the command "adb sideload nameoftheimg.img, will it get the img from sdcard OR from PC?
So the image is on SDcard AND on the PC? I do not get it (sorry)
kameraad759 said:
Oke. But if it boot from sdcard, then it will not install the img from sdcard?? I though it would.
What are the 'necessary adb drivers'?
And when i give the command "adb sideload nameoftheimg.img, will it get the img from sdcard OR from PC?
So the image is on SDcard AND on the PC? I do not get it (sorry)
Click to expand...
Click to collapse
Not as far as I know, I could be wrong, it could install from it. As far as the adb driver goes this is what I meant, you manually install them. Yes, the image is on both the pc and sdcrad.
RAZERZDAHACKER said:
Not as far as I know, I could be wrong, it could install from it. As far as the adb driver goes this is what I meant, you manually install them. Yes, the image is on both the pc and sdcrad.
Click to expand...
Click to collapse
Hello (again)
It will not boot from the sd card. I formatted it FAT32, used Win32DiskManager to write the .img on it, place the sdcard in the hisense and booted it. Press ON. System will not boot on sdcard. Instead it boot from disk. I see the same logo as before, Hisense Smart. It ignores the sdcard.
Booted it in recovery mode (with inserted SDcard). ADB sideload xxx.img, gave same answer: cannot read MAxxx.img. Other option in the recovery mode like update from external image (i hoped the sdcard) does not work either (can not find any /mnt ect file).
How can I force to boot from sdcard? Is the sdcard now bootable (with win32diskmanager). I used Rockchip Create Upgrade Tool 1.43 also, but this app crash when it want to write to SDcard.
No luck with me till now. Is my device saveable at all? Why does it not see the sdcard?
Hans
kameraad759 said:
Hello (again)
It will not boot from the sd card. I formatted it FAT32, used Win32DiskManager to write the .img on it, place the sdcard in the hisense and booted it. Press ON. System will not boot on sdcard. Instead it boot from disk. I see the same logo as before, Hisense Smart. It ignores the sdcard.
Booted it in recovery mode (with inserted SDcard). ADB sideload xxx.img, gave same answer: cannot read MAxxx.img. Other option in the recovery mode like update from external image (i hoped the sdcard) does not work either (can not find any /mnt ect file).
How can I force to boot from sdcard? Is the sdcard now bootable (with win32diskmanager). I used Rockchip Create Upgrade Tool 1.43 also, but this app crash when it want to write to SDcard.
No luck with me till now. Is my device saveable at all? Why does it not see the sdcard?
Hans
Click to expand...
Click to collapse
It is saveable, can you give me the link to the .img file? The fact that it says "cannot read" might be that the image file is corrupt. Are you sure you are typing the right name? You can do adb sideload then type the first letter (if it is a big letter type it as big for example Achicken, type A, if it is aCHICKEN, type it as a) and hit tap, that will ensure you have the exact name and dont tamper with it as in add .img at the end.
RAZERZDAHACKER said:
It is saveable, can you give me the link to the .img file? The fact that it says "cannot read" might be that the image file is corrupt. Are you sure you are typing the right name? You can do adb sideload then type the first letter (if it is a big letter type it as big for example Achicken, type A, if it is aCHICKEN, type it as a) and hit tap, that will ensure you have the exact name and dont tamper with it as in add .img at the end.
Click to expand...
Click to collapse
Yes I always give first letter tap. This is what I typed
adb sideload M (and then tap) => adb sideload MA347ENMEG3EV02.img
https://docs.google.com/uc?id=0Bwr18Lh81gvJazJXTGFQTnhDSEk&export=download
Its a rar. I unzipped it with 7-zip
I tryed also adb shell. But device is unauthorized and I get eroor $ADB)VENDOR_KEYS not set (even when I deleted .android in my users dir. Do not get any permission question on device also. My hope is still a bootable SDCard and image.
Thanks
kameraad759 said:
Yes I always give first letter tap. This is what I typed
adb sideload M (and then tap) => adb sideload MA347ENMEG3EV02.img
https://docs.google.com/uc?id=0Bwr18Lh81gvJazJXTGFQTnhDSEk&export=download
Its a rar. I unzipped it with 7-zip
I tryed also adb shell. But device is unauthorized and I get eroor $ADB)VENDOR_KEYS not set (even when I deleted .android in my users dir. Do not get any permission question on device also. My hope is still a bootable SDCard and image.
Thanks
Click to expand...
Click to collapse
Might seem crazy but check this out, try with your image then his image(s). Remember, booting from an sdcrad is extremely slow, It can actually take 24hours depending on the speed fo your sdcrad so before trying this I suggest you leave it for a day.
RAZERZDAHACKER said:
Might seem crazy but check this out, try with your image then his image(s). Remember, booting from an sdcrad is extremely slow, It can actually take 24hours depending on the speed fo your sdcrad so before trying this I suggest you leave it for a day.
Click to expand...
Click to collapse
Oke, I will wait for a while. But it seems it just hangs in the normal boot.
Thanks for so far. I will report back after the weekend with hopely good news
Hans
I waited for 48hours but nothing happens. Still the screen Hisense Smart.
So it will not boot from SD card and I can not external mount with adb.
When I go in recover mode I see message:
failed to mount /mnt/external_sd (No such device)
SDCard is raw formatted. Can not browse with Windows SDCard. Maybe it should be wrotten different so I can see /mnt/external_sd
Maybe you have a good idea this week for me.
Hans