Related
My allwinner A10 tablet came pre-rooted or so I thought. I installed CWM v6.1.0.2 via the terminal emulator but wasn't able to reboot back to my OS.
I then wiped cache partition and wiped data, it would not allow me to wipe the dalvik cache.
At the end of each process I see:
E:Can't mount /cache/recovery/log
E:Can't mount/cache/recovery/log
Also for /last-log of the two above.
I have got an A10 cm10 rom which I have tried to install via the external sd but no luck.
Any help would be appreciated as I have no clue what I can do next.
Do you know the model or make of your device? What are all of the specs? If you have that information I can probably lead you to a support forum for your device.
I recently recovered my A10 device flashing a .img of a totally different A10 tablet and most of my tablets features work. I tried flashing 100 other .img files and none of those worked correctly.
Where did you get that CWM file? Was it CWM that was specific for A10 devices? You can't just flash any recovery to your device and expect it to work.
Your issue is likely that the CWM is not for your device or it's just having issues with your device. I'm using CWM 6.0.1.1 for Allwinner A10 ICS. I got it onto my device using a simple one click method, but in order for you to use it you have to be on a rom that at least boots up with the display working.
Once you give me information on your device I can try searching for some .img files for you to flash onto your device with Livesuit. If you're lucky enough you'll get one that is specific for your device, if your not so lucky you're going to be breaking your head trying to find a rom that at least boots up with most features working. It's a lesson learned, don't mess with your device unless you have the necessary resources as a backup in the event that something goes wrong.
Hi, thanks for the reply, unfortunately I don't know the make. When it is connected to the PC it shows as BC1077. It came in a completely unmarked box. Here are the specs:
• 10-inch TFT LCD capacitive touch screen
• 1024 x 800 pixels display resolution
• Android 4.0 operating system
• CPU: Allwinner A10 1.5GHz
• RAM: DDR III 1GB
• WiFi: 54Mbps 802.11B/G
• Lan: 10/100M Ethernet Access
• Built-in Micro-SD card slot up to 32GB
• Built-in G-Sensor
• Supports external 3G devices.
• Built-in 1.3 megapixels digital camera
• Built-in 8GB memory
• Plays AVI,RM/ RMVB,FLV,MPG4 - 1,MPEG – 2 video format files
• Plays MP3,WMA,AAC,AC3,WAV audio format files
• Picture browsing of JPEG,BMP,GIF,PNG,TIFF format files
• Built-in 7000mAh Li-poly battery
• 3.5mm earphone socket
• 1 x USB ports
. 1 x Mini USB port
. 1x HDMI port
. Watt speakers
• Android keyboard and Google keyboard input
• Multi-language support
. Battery Life: 6-8 Hours
I got the CWM 6.0.1.2 from here it was meant to be specific to A10's.
Problem is I have no drivers so I cannot see it in windows either.
karlos65 said:
Hi, thanks for the reply, unfortunately I don't know the make. When it is connected to the PC it shows as BC1077. It came in a completely unmarked box. Here are the specs:
• 10-inch TFT LCD capacitive touch screen
• 1024 x 800 pixels display resolution
• Android 4.0 operating system
• CPU: Allwinner A10 1.5GHz
• RAM: DDR III 1GB
• WiFi: 54Mbps 802.11B/G
• Lan: 10/100M Ethernet Access
• Built-in Micro-SD card slot up to 32GB
• Built-in G-Sensor
• Supports external 3G devices.
• Built-in 1.3 megapixels digital camera
• Built-in 8GB memory
• Plays AVI,RM/ RMVB,FLV,MPG4 - 1,MPEG – 2 video format files
• Plays MP3,WMA,AAC,AC3,WAV audio format files
• Picture browsing of JPEG,BMP,GIF,PNG,TIFF format files
• Built-in 7000mAh Li-poly battery
• 3.5mm earphone socket
• 1 x USB ports
. 1 x Mini USB port
. 1x HDMI port
. Watt speakers
• Android keyboard and Google keyboard input
• Multi-language support
. Battery Life: 6-8 Hours
Problem is I have no drivers so I cannot see it in windows either.
Click to expand...
Click to collapse
Okay, if we both search we'll find the device faster.
Go to the following link and try to find your device or a device with similar specs: http://www.slatedroid.com/forum/274-allwinner-a10-cpu-devices/
Android1993 said:
Okay, if we both search we'll find the device faster.
Go to the following link and try to find your device or a device with similar specs: http://www.slatedroid.com/forum/274-allwinner-a10-cpu-devices/
Click to expand...
Click to collapse
Again thanks for the help, where is the spec for all the models on those pages?
karlos65 said:
Again thanks for the help, where is the spec for all the models on those pages?
Click to expand...
Click to collapse
To be honest it's just a long search through each tablets board to find a post that lists the specs. I'm realizing that's a big headache.
I personally just flashed random A10 images onto my device. Nothing bad seemed to happen to my device, but I'm not sure if the same is going to apply to you. If you feel like taking the chance you can just flash some images and cross your fingers hoping it doesn't do anything to your device. When I did it the worst that happened was that the roms either didn't display anything, displayed a static image, display was off center, touch controls didn't work, or got stuck at boot screen, then one finally worked.
I can try to link you to some A10 firmware images and LiveSuitPack if you want to take the chance.
Android1993 said:
To be honest it's just a long search through each tablets board to find a post that lists the specs. I'm realizing that's a big headache.
I personally just flashed random A10 images onto my device. Nothing bad seemed to happen to my device, but I'm not sure if the same is going to apply to you. If you feel like taking the chance you can just flash some images and cross your fingers hoping it doesn't do anything to your device. When I did it the worst that happened was that the roms either didn't display anything, displayed a static image, display was off center, touch controls didn't work, or got stuck at boot screen, then one finally worked.
I can try to link you to some A10 firmware images and LiveSuitPack if you want to take the chance.
Click to expand...
Click to collapse
If I knew how to do it I could persevere trying different images, how easy is it?
karlos65 said:
If I knew how to do it I could persevere trying different images, how easy is it?
Click to expand...
Click to collapse
It's very simple actually.
Here's the LiveSuitPack tool: http://www.topnotchtablets.com/LivesuiteInstall
Here's the guide for installing firmware: http://www.topnotchtablets.com/A10Firmware
In the guide for installing firmware substitute the menu button for volume down button if you don't have a menu button.
There are two firmwares to download on the firmware installation guide page, although I don't think either of those will work at all to begin with. Try them if you'd like. Give me a few minutes to boot into my other partition so I can get all the links of images I bookmarked.
Android1993 said:
It's very simple actually.
Here's the LiveSuitPack tool: http://www.topnotchtablets.com/LivesuiteInstall
Here's the guide for installing firmware: http://www.topnotchtablets.com/A10Firmware
In the guide for installing firmware substitute the menu button for volume down button if you don't have a menu button.
There are two firmwares to download on the firmware installation guide page, although I don't think either of those will work at all to begin with. Try them if you'd like. Give me a few minutes to boot into my other partition so I can get all the links of images I bookmarked.
Click to expand...
Click to collapse
So the drivers are in the folder? for each particular tablet image.
karlos65 said:
So the drivers are in the folder? for each particular tablet image.
Click to expand...
Click to collapse
No, once you download the Livesuitpack you're going to open the folder and run LiveSuitPack_v1.07. That'll install some drivers, or it'll ask you if you want to install some drivers, click Yes. From there you're going to run the LiveSuit application. Then you follow the steps for getting the new firmware onto your device.
EDIT: The drivers that the Livesuitpack installs onto your computer also make your device recognizable in ADB (if you know what that is and ever have a use for it). I also couldn't find drivers for my device for the longest and these seem to work at making your device recognizable across your computer.
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
Firmware:
This is the one that worked on my tablet, doubt it'll work on yours: http://www.ele-china.com/soft/tablet/7inchA10/
This has a good bunch of them: http://www.tikkitoo.com/Firmware-Downloads
Another one I tried: http://androidtabletfirmware.com/firmware_details=MzE5LTEzMzI5MDkxNzAwNzAxNDkyMDU2
This is a forum thread linking to a bunch of websites with firmware for A10 devices: http://www.techknow.t0xic.nl/forum/index.php?topic=3807.0
That's a huge portion of the places I searched and the ones I tried. I'll update the post if I find anymore.
Android1993 said:
No, once you download the Livesuitpack you're going to open the folder and run LiveSuitPack_v1.07. That'll install some drivers, or it'll ask you if you want to install some drivers, click Yes. From there you're going to run the LiveSuit application. Then you follow the steps for getting the new firmware onto your device.
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
Firmware:
This is the one that worked on my tablet, doubt it'll work on yours: http://www.ele-china.com/soft/tablet/7inchA10/
This has a good bunch of them: http://www.tikkitoo.com/Firmware-Downloads
Another one I tried: http://androidtabletfirmware.com/firmware_details=MzE5LTEzMzI5MDkxNzAwNzAxNDkyMDU2
This is a forum thread linking to a bunch of websites with firmware for A10 devices: http://www.techknow.t0xic.nl/forum/index.php?topic=3807.0
That's a huge portion of the places I searched and the ones I tried. I'll update the post if I find anymore.
Click to expand...
Click to collapse
I can't thank you enough for your help.
I will update here on any progress I make.
Once again many thanks, karma owes you one.
karlos65 said:
I can't thank you enough for your help.
I will update here on any progress I make.
Once again many thanks, karma owes you one.
Click to expand...
Click to collapse
No need to thank anymore than you already have. I've been helped around here plenty of times by some sincere people. It's all about giving back what you receive. I hope everything goes well with your tablet as it did mine, and be careful, don't want anything getting messed up on you. Good luck.
Android1993 said:
No need to thank anymore than you already have. I've been helped around here plenty of times by some sincere people. It's all about giving back what you receive. I hope everything goes well with your tablet as it did mine, and be careful, don't want anything getting messed up on you. Good luck.
Click to expand...
Click to collapse
No luck so far, I flashed one image which gave me a sort of cracked looking screen affect, other images I have tried to flash do not make it to 100%?
I am not sure if I have now completely bricked it?
I am still looking for images that closely match my pad and will try again this evening.
karlos65 said:
No luck so far, I flashed one image which gave me a sort of cracked looking screen affect, other images I have tried to flash do not make it to 100%?
I am not sure if I have now completely bricked it?
I am still looking for images that closely match my pad and will try again this evening.
Click to expand...
Click to collapse
Your device shouldn't brick. I believe A10 devices have all necessary code in the chip itself, or something along those lines. The cracked looking screen effect means that it isn't compatible with your device, I came across plenty of roms that did that to my device, all you do if flash the next image.
I haven't come across any issues with it not getting to 100%. I can only suggest you retry it, or move on to the next image.
karlos65 said:
My allwinner A10 tablet came pre-rooted or so I thought. I installed CWM v6.1.0.2 via the terminal emulator but wasn't able to reboot back to my OS.
I then wiped cache partition and wiped data, it would not allow me to wipe the dalvik cache.
At the end of each process I see:
E:Can't mount /cache/recovery/log
E:Can't mount/cache/recovery/log
Also for /last-log of the two above.
I have got an A10 cm10 rom which I have tried to install via the external sd but no luck.
Any help would be appreciated as I have no clue what I can do next.
Click to expand...
Click to collapse
Iv got similar problems with my BC1077. Iv been trying to fix it for the last few days. Im not 100% sure, but I think the problem Iv quoted above is that CWM does not support jellybean, so it wont work with cm10, which is jellybean.
Over the last few days Iv flashed 40+ A10 firmwares to my tablet, but Iv only found 1 that installs properly and boots for me. It actually works pretty well, only major issue iv noticed is auto rotate doesnt work. But this same working firmware is also jellybean, after I install CWM I get bootloops and have to reflash the firmware again to boot.
Heres a link to the firmware that works for my BC1077 - http://www.ssb-repair.com/Firmwares/Cherry/M1007_20121217.zip
Its for a completly different tablet (Cherry Mobility - M007), but like I said it works on mine.
Heres another firmware it might be worth you trying to flash, its the only BC1007 specific firmware Iv found, but it wont install on my tablet, I always get a 0x162 error from it. Heres the link - http://www.pandawillforum.com/soft/mate sku20314 firmware for May 25 stock.rar
Good luck, let us know if you make any progress.
I think I might have been flashing with a very low battery, if a flash was unsuccessful halfway through would this not brick the tablet.
I am not getting any kind of response from the screen at all and when I try to flash although the drivers appear to load the % bar doesn't go up.
col888 said:
Iv got similar problems with my BC1077. Iv been trying to fix it for the last few days. Im not 100% sure, but I think the problem Iv quoted above is that CWM does not support jellybean, so it wont work with cm10, which is jellybean.
Over the last few days Iv flashed 40+ A10 firmwares to my tablet, but Iv only found 1 that installs properly and boots for me. It actually works pretty well, only major issue iv noticed is auto rotate doesnt work. But this same working firmware is also jellybean, after I install CWM I get bootloops and have to reflash the firmware again to boot.
Heres a link to the firmware that works for my BC1077 - http://www.ssb-repair.com/Firmwares/Cherry/M1007_20121217.zip
Its for a completly different tablet (Cherry Mobility - M007), but like I said it works on mine.
Heres another firmware it might be worth you trying to flash, its the only BC1007 specific firmware Iv found, but it wont install on my tablet, I always get a 0x162 error from it. Heres the link - http://www.pandawillforum.com/soft/mate sku20314 firmware for May 25 stock.rar
Good luck, let us know if you make any progress.
Click to expand...
Click to collapse
Thanks for that, I will try tonight and get back.
OK, regardless of the image I try to flash the livesuit progress bar gets to 3% and then goes back to 0% and then nothing.
Anyone?
If the battery was low and the flashing process didn't finish all you have to do is load up the exact image that didn't finish flashing into LiveSuit and put your tablet into download mode and let it do its thing. I had the same problem and got scared my tablet was bricked, so I just did the process I stated above and it finished. It wouldn't allow me to flash another rom, I'd get the little Livesuit pop up that you get after a rom successfully flashes, so if that's the same pop up you're getting don't be alarmed.
karlos65 said:
I think I might have been flashing with a very low battery, if a flash was unsuccessful halfway through would this not brick the tablet.
I am not getting any kind of response from the screen at all and when I try to flash although the drivers appear to load the % bar doesn't go up.
Click to expand...
Click to collapse
I dont think your tablet is bricked, if it was I doubt it would respond to Live Suite or PheonixUSB pro at all. From what Iv read about the A10 its meant to be unbrickable.
What error codes does live suite/pheonixUSB give you when they stop?
if youre getting 0x120 and 0x162 errors, just keep trying more firmwares out till you find one that will install without errors.
Theres loads of A10 Allwinner firmwares at this link - http://androidtabletfirmware.com/firmware_search/order=2/sort=1
I Pre-Apologize If this Has been asked before My Interest at the current time is about developing a recovery image for my soft-bricked Nextbook Ares A11 Tablet android 5.1 64 bit Atom processor 1gb ddr3 ram if i remember correctly I was experimenting with trying to find a recovery image that i could flash to it and well Bricked I can however boot to some sort of bios hardware settings in it with the ability to boot from file and change manufacturer hardware settings ...I dont believe that is part of the android booting process but somewhere hardcoded! As for the android booting i no longer have the stock recovery<!--go figure--> but i still am able to access fastboot in download mode and i have the update firmware from the manufacturers for my specific device! Sorry if this seems like 2 questions If you could tell me wether i could flash the update to fix it has the boot.img in it also other files looks similar to how to root with file-systems anyways if you have no advice on how to unbrick my advice Here is the real question!! What matters when developing a recovery.img for a specific device what do i have to take into consideration as to hardware specs and software specs any good links to that would be awesome and for the final question how to distinguish my recovery partition type idk if it is MTD or BML I cant find the MTD folder so assuming it is BML I can also get additional info such as last_log or any of that I am able to USB boot the tablet into Kali Linux Sorry for Such a long and drawn out explanation I will revise my question if needed and possibly start two separate posts on this! Thanks in advanced i really appreciate the Help!!! XDA Rules
Update Tried to flash the update firmware boot.img snd now i also have a verity issue I think ive tried everything
maybe my answer is to wait until a flash recovery comes out for this tablet!
I have found a Temporary Solution for my Bricked Nextbook Ares A11 Given it is Buggy and you may need to experiment to get the WIFI working! I didnt yet!
I have read somewhere that you can take these Android_x86.ISO and compile the Kernel I Dont Know How YET but if you cant find one that Supports the Wifi chip then i think you'll have to compile the drivers with the Kernel!
If you can Find an ISO Image for this device that seems to work decent at least the WIFI Let me know please I'll be 4ever Grateful!
Here is my Temporary Fix!
While looking for Android Images to Install on my Nextbook I stumbled upon this webpage It has loads of Android ISO's for running inside a VM
http://www.android-x86.org/download
I used a Bootable usb to test then install the one That worked the best for me
The software on my Device was Buggy One ISO let WIFI work for the first boot then all of a sudden it stopped working.... on this one the touchscreen never worked! heres the ISO name---cm-x86-13.0-rc1.iso--<!--WIFI worked for the first boot-->
The other one is --Android-x86 6.0-- the WIFI never worked but the touchscreen does but not for a real long time!! I think if you get the kernels then custom build them to fit your device that would fix a Soft brick for any device that you could figure out how to boot a USB image on!
NextBook Ares 11a bricked
Grey-Dev said:
I have found a Temporary Solution for my Bricked Nextbook Ares A11 Given it is Buggy and you may need to experiment to get the WIFI working! I didnt yet!
I have read somewhere that you can take these Android_x86.ISO and compile the Kernel I Dont Know How YET but if you cant find one that Supports the Wifi chip then i think you'll have to compile the drivers with the Kernel!
If you can Find an ISO Image for this device that seems to work decent at least the WIFI Let me know please I'll be 4ever Grateful!
Here is my Temporary Fix!
While looking for Android Images to Install on my Nextbook I stumbled upon this webpage It has loads of Android ISO's for running inside a VM
http://www.android-x86.org/download
I used a Bootable usb to test then install the one That worked the best for me
The software on my Device was Buggy One ISO let WIFI work for the first boot then all of a sudden it stopped working.... on this one the touchscreen never worked! heres the ISO name---cm-x86-13.0-rc1.iso--<!--WIFI worked for the first boot-->
The other one is --Android-x86 6.0-- the WIFI never worked but the touchscreen does but not for a real long time!! I think if you get the kernels then custom build them to fit your device that would fix a Soft brick for any device that you could figure out how to boot a USB image on!
Click to expand...
Click to collapse
Hi can you give me the steps? my nextbook ares 11a is bricked OS and stock recovery are gone,I can get to fastboot and even the bios but that's it? Thanks so much for any help you may have..
Grey-Dev said:
I have found a Temporary Solution for my Bricked Nextbook Ares A11 Given it is Buggy and you may need to experiment to get the WIFI working! I didnt yet!
I have read somewhere that you can take these Android_x86.ISO and compile the Kernel I Dont Know How YET but if you cant find one that Supports the Wifi chip then i think you'll have to compile the drivers with the Kernel!
If you can Find an ISO Image for this device that seems to work decent at least the WIFI Let me know please I'll be 4ever Grateful!
Here is my Temporary Fix!
While looking for Android Images to Install on my Nextbook I stumbled upon this webpage It has loads of Android ISO's for running inside a VM
http://www.android-x86.org/download
I used a Bootable usb to test then install the one That worked the best for me
The software on my Device was Buggy One ISO let WIFI work for the first boot then all of a sudden it stopped working.... on this one the touchscreen never worked! heres the ISO name---cm-x86-13.0-rc1.iso--<!--WIFI worked for the first boot-->
The other one is --Android-x86 6.0-- the WIFI never worked but the touchscreen does but not for a real long time!! I think if you get the kernels then custom build them to fit your device that would fix a Soft brick for any device that you could figure out how to boot a USB image on!
Click to expand...
Click to collapse
Why not extract the device's kernel from an update file if possible?
I am currently in communication with Alcatel's U.S. support (which may be outsourced, who knows?), and they have made it clear there is no OTU (OneTouchUpdate) available for the AT&T Alcatel Allura 5056O device. Their current advice is limited to performing a factory reset via the GUI, which of course isn't possible for a softbricked phone.
This means that as of this writing, there is no known way to restore this device from a softbrick.
I am explaining carefully the issue I and and a number of others here on XDA have experienced with this phone to Support, specifically asking for some method to reload the stock ROM, and will report any constructive suggestions they may have. But the OTU I made available at:
https://www.multcloud.com/share/0377ab37-15ed-4bcd-be3b-dbe8c7eb2cc8
...that lists the 5056 simply will not work on the 5056O.
Received this from the Contact Center:
The firmware is information that would only be available at the repair center. We would recommend you to perform a factory reset...
Click to expand...
Click to collapse
Still trying, but it isn't looking very good for those of us with softbricked 5056Os...
Yup I wanted to root the phone, so I did but then it bootlooped and it's bricked lol.
Haven't heard anything else from Alcatel's Customer "Support," so I've resent my questions to see if I can get some answers out of someone. There are enough of us affected by this issue that I'm not going to let them off quite so easily...
More bad news; the most recent reply from Alcatel CS:
At this moment it would be to send in the device into the repair center to get it repaired for you.
Click to expand...
Click to collapse
Clearly they are going to be less than helpful for those of us with the 5056O. Unless some kind soul here who has this phone is willing to image and post a copy of the Allura ROM, or someone knows a tech working for Alcatel who can supply the ROM, those of us with soft-bricked phones are completely screwed.
Am getting same info from Twitter CS...the ROM is only available inside their repair center.
(*sigh*) So unless someone else manages to liberate this device's ROM, guess we all might as well throw the devices in a drawer and move along. Just remember that the next time you're phone shopping, and bypass the Alcatel/TCL offerings.
Friends here I leave a link for you to download a copy I made to the Alcatel Allura 5056O, I did it through the flashfire application, I think if some advanced developer could work it, it would solve the problem we have. Https://mega.nz/#!01NDVR5K!rPPYEd87ndmg5Q9jmQ3qWjm1qGD3Rm7ge83yIsezSSQ
Excuse my bad English, I'm from Venezuela.
sanpuyon said:
Friends here I leave a link for you to download a copy I made to the Alcatel Allura 5056O
Click to expand...
Click to collapse
That is excellent, thank you very much!
Now let me make sure I understand; is this a copy of a softbricked ROM, or a functional one? Is it rooted or non-rooted?
CharlieSummers said:
That is excellent, thank you very much!
Now let me make sure I understand; is this a copy of a softbricked ROM, or a functional one? Is it rooted or non-rooted?
Click to expand...
Click to collapse
It is a copy of a functional rom, has root access and has modifications that I did before the device would damage me, but I have all my data in it.
sanpuyon said:
It is a copy of a functional rom, has root access and has modifications that I did before the device would damage me, but I have all my data in it.
Click to expand...
Click to collapse
So, if we can figure out how the Alcatel OTUs push the ROM to the phone, we might be able to get a softbricked phone to the point of performing a system reset...
Time to start reading up on how...
CharlieSummers said:
So, if we can figure out how the Alcatel OTUs push the ROM to the phone, we might be able to get a softbricked phone to the point of performing a system reset...
Time to start reading up on how...
Click to expand...
Click to collapse
The problem with my phone is that I made a modification to the build prop and upon restart I just showed the logo and then black screen, connect it to the adb and try to carry a custom recovery of a 6040A alcatel I had before and the result was that too Delete the recovery stock, now the phone when I connect it to adb appears to me as unauthorized, so I have not been able to repair it
sanpuyon said:
now the phone when I connect it to adb appears to me as unauthorized, so I have not been able to repair it
Click to expand...
Click to collapse
Keep trying. I've noticed that my 5056O does the same thing, but if I keep trying (restarting the phone, plugging in-and-out, etc.) I can eventually get adb devices to show it as "device" at which point I can acquire a shell, which can be SU'd.
Not guaranteeing this will work for you, but it has worked for me quite a few times so far. Beginning to think this phone is just magic, not science.
Just a quick bump to remind folks there are a bunch of soft-bricked 5056O phones out here in desperate search for a ROM...
Another bump to see if anyone has additional information on 5056O ROMs...hope springs eternal!
Still nothing, eh?
Hoping for someone with info on how to unbrick an Alcatel OneTouch Allura (5056O) - a stock ROM and means for recovery would be great!
Dear friends, after suffering for more than a year with my damaged phone, find a solution, I hope you can also solve it.
Here is a guide and the link to download the tool.
In the completely off phone will press the volume up and down keys at the same time and connect it to the pc so enter the download mode
1) Download the tool from this link https://mega.nz/#!NpkhnCoT!q5LxwJdWfIjcIY2tl99eGbhvRtrSY8bk-GQcDji7Rhs
2) Then unzip it install it on the pc
3) They execute it and they place the user and the password that he left in the attached note, when the update comes out they tell him not to
4) They look for the model of the team and they give to the option of flash and enjoy the magic
The only bad thing is that in the process the network release is lost
sanpuyon said:
Dear friends, after suffering for more than a year with my damaged phone, find a solution, I hope you can also solve it.
Click to expand...
Click to collapse
Um, last time I checked, the 5056O didn't have available ROMs outside AT&T. Is this the phone you repaired?
Also, latest version of SUGAR I found is v11.6.9R, which I placed in the MultCloud shared folder at https://www.multcloud.com/share/0377ab37-15ed-4bcd-be3b-dbe8c7eb2cc8 in the Misc folder. Same credentials as listed in the older README:
Region: All
Username: SU_IN.Panasonic
Password: KoD8naL2
Dongle authorization: unchecked
sanpuyon said:
The only bad thing is that in the process the network release is lost
Click to expand...
Click to collapse
My fault being unfamiliar with this stuff, but can you explain what was lost?
Oh, and I don't suppose this got you any closer to installing a custom recovery to root the phone?
does anyone have a link to the stock firmware? for an ALcatel onetouch Allura 5056O, I've been browsing the thread and seen none of the links provided for the stock firmware are all dead.
Better late than never: https://www.androidfilehost.com/?fid=10620683726822061932
I had hat on a HDD from a while back and never had a way to use it until I found edl. I'm currently flashing it now and I have no idea if it's gonna work or not. I don't think it will but who knows.
Also, its probably gonna take a few days or more to flash...
Edit: It failed at some point just a few hours in. Maybe it was just my device because I have disassembled it in the past looking for test points. I wish everyone else good luck.
RCA 10" Touchscreen Tablet PC/DVD Combo Featuring Android 6.0 (Marshmallow)
*No idea why it says PC/DVD as its Android not Windows.
ASIN/Model numbers: ASIN: B077L4VBHK Model: DRP2091
RCA typical RCT number: RCT6603W47M7
Chipset/CPU: MT8127
Ports: 1x Mirco USB (supports ADB! etc. unlike VikingPRO), 1xUSB A, 1xHDMI (mini i believe), 1xMicroSD slot (supports up to 128GB)
Special: 1xDVD/CD Reader/Drive. has unlockable bootloader via fastboot oem unlock
Root Attempts: (Failed: KingoRoot, SRS, KingRoot, RootMaster)
MTK Droid Root & Tools and SP Flash Tools don't seem to work right with this cant create scatter etc. (i assume because of MT8127)
Links:
Walmart/Wally World
Amazon
if any dev could help me root this and get custom recovery would be great.
UPDATE: Thanks to NepoRood (and my testing) theres now CWM recovery (attached to post extract zip and flash img via fastboot flash recovery command.) unfortunately we were still unable to get root access.. if anyone has this device or wants to help root this pm me.
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
darkensx said:
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
Click to expand...
Click to collapse
I found various firmware downloads, but need to know the exact type of firmware you are running.
Example of one I found: rct6603w47m7-android6.0-v23-v2.15.80 (<-- underlined part is what matters)
If you boot into recovery, it should show you the type of firmware you have.
NepoRood said:
I found various firmware downloads, but need to know the exact type of firmware you are running.
Example of one I found: rct6603w47m7-android6.0-v23-v2.15.80 (<-- underlined part is what matters)
If you boot into recovery, it should show you the type of firmware you have.
Click to expand...
Click to collapse
DRP2091-android6.0-v62-v1.19.90-E02
*also says on very bottom of screen "supported API: 3"
**DRP2091 is rct6603w47m7 not sure why there's so many different model/serial numbers referencing the same exact device...
also i managed to dump the whole device via SP tools readback on linux so if anything beyond recovery or boot img are needed i should have it.
darkensx said:
DRP2091-android6.0-v62-v1.19.90-E02
*also says on very bottom of screen "supported API: 3"
**DRP2091 is rct6603w47m7 not sure why there's so many different model/serial numbers referencing the same exact device...
also i managed to dump the whole device via SP tools readback on linux so if anything beyond recovery or boot img are needed i should have it.
Click to expand...
Click to collapse
That version isn't on the site (or any v1.19.x), I'll download the images from the OP in a bit and see what's inside...
NepoRood said:
That version isn't on the site (or any v1.19.x), I'll download the images from the OP in a bit and see what's inside...
Click to expand...
Click to collapse
Had the same issue also I came across a bunch of ota test files on a Chinese site but links were dead and because no ota update is available i can't grab the ota url or file name. So ended up hitting a dead end.
Would it be possible to bypass the activation code screen with cwm or twrp? Or maybe put a different version of android on the tablet, other than marshmallow.?
darkensx said:
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
Click to expand...
Click to collapse
I'm having same problem could someone help me root this tablet explain as easy as possible and slow and clear directions
I have no idea
johnnymack said:
I'm having same problem could someone help me root this tablet explain as easy as possible and slow and clear directions
Click to expand...
Click to collapse
I've got the RCT6603W47M7 tablet, but here in the UK it goes by the name of RCA Neptune 10.1L.
Problem is I have bricked it and I am now trying to recover it using SP Flash Tools. I have tried 2 different stock ROMs, only to have nothing but errors and interruptions during flashing. (errors 2004 and 4008). My tablet is fully charged yet it will randomly disconnect during flashing. I've tried both the MTKAllInOne.bin and DA_SWSEC.bin but I still get the same problem either way.
I've tried different USB ports, different cables and the two download agents that I just mentioned but I am stumped.
I wanted to try the ROM found here https://www.needrom.com/download/rca-rct6603w47m7/
But as I don't have a premium account I cannot access it.
Any ideas? This is very frustrating.
BP9375 said:
I've got the RCT6603W47M7 tablet, but here in the UK it goes by the name of RCA Neptune 10.1L.
Problem is I have bricked it and I am now trying to recover it using SP Flash Tools. I have tried 2 different stock ROMs, only to have nothing but errors and interruptions during flashing. (errors 2004 and 4008). My tablet is fully charged yet it will randomly disconnect during flashing. I've tried both the MTKAllInOne.bin and DA_SWSEC.bin but I still get the same problem either way.
I've tried different USB ports, different cables and the two download agents that I just mentioned but I am stumped.
I wanted to try the ROM found here https://www.needrom.com/download/rca-rct6603w47m7/
But as I don't have a premium account I cannot access it.
Any ideas? This is very frustrating.
Click to expand...
Click to collapse
problem with the cwm recovery if i remember correctly is any thing flashed by it doesnt take the device will just bootloop
i no longer have the device currently i might pickup another at some point... i cant remember if i used the micro usb port to flash or if i had to use a usb male to male cable..
darkensx said:
problem with the cwm recovery if i remember correctly is any thing flashed by it doesnt take the device will just bootloop
i no longer have the device currently i might pickup another at some point... i cant remember if i used the micro usb port to flash or if i had to use a usb male to male cable..
Click to expand...
Click to collapse
Thank you for your reply, I was worried that this discussion was dead. That's frustrating to say the least! Damn! Well, I don't know if this will work but I found another device that is also a MT8127 and has exactly the same spec of this tablet. My point being is that I found a TWRP image for that device, and because it's the same chip set I assume that it'll work for this device too?
If I can get my bricked tablet to even turn on I shall try it. It also makes me wonder that if we were able to root the device, would we be able to access the internal storage by normal means? By using the micro USB ? Either way it'd be great to have it rooted.
I stayed up all night last night trying to flash this tablet and still no luck, it keeps disconnecting half way through.
These tablets were sold with certain Vizio TVs in mid-2016 into 2017, primarily used for Smartcast to the TV.
They are now obsolete since Vizio released firmware for their TVs turning them into normal Smart TVs, requiring the owners of these TVs to get new remotes and the tablets stopped being useful for this function.
Here in 2019, one can buy these tablets, at the low price end, in working condition, for $25 (for the M series) to $40 (for the P series) shipped.
The specs are as follows:
XR6M10:
Snapdragon 410 1.2GHz quadcore APQ8016
2GB RAM
8GB Storage
1280x720 IPS display
802.11n, Bluetooth 4.0
2740mAh battery
MicroUSB for charging, Qi Charging built-in for bundled charge pad or any compatible charging solution
XR6P10:
Snapdragon 615 1.45GHz octocore APQ8039
2GB RAM
16GB Storage
1920x1080 IPS display
802.11n, Bluetooth 4.0
2740mAh battery
MicroUSB for charging, Qi Charging built-in for bundled charge pad or any compatible charging solution
Both tablets feature side-firing stereo speakers, a headphone jack, and NO cameras. The size of the tablet is comparable to the size of a Galaxy Note 9, give or take.
Both tablets came with Android 5.1.1, and OTA updates upgraded them to 6.0.1. There are ZERO available stock ROM files available for the tablets. I've tried sniffing the updater and they seem to go to a dead website.
The stock ROM is fairly clean, and only has the Vizio Smartcast app which needs disabling upon setting up. Aside from this, there is no other bloatware on the tablet to speak of after running a fine-tooth comb through the system apps. You get a clean and snappy tablet.
The problem:
There's no stock ROM file available, neither for Android 5.1.1 or for 6.0.1. Vizio does not have any sort of download for either on their site, nor did in the past. The updater checked a third-party website affiliated with Vizio to manage the tablet's updates, as it does with their TVs. Since the website is inert, it can be safely said that Vizio is no longer interested in their existence at all, especially since the warranty on every single one of these tablets is now up.
The tablet seems it can have the bootloader unlocked, the developer options has the toggle for that, but there's no way to get into fastboot. Holding VOL UP+DOWN+POWER at boot or sending the "adb reboot bootloader" command sends it into a "Qualcomm HS-USB QDLoader 9008" mode under USB. This, from what I understand, is behavior persistent with the locked bootloader, but I have no idea of how to get it out of this and just into fastboot. Stock recovery does not have a fastboot option either.
The desires list:
Have someone that knows the intricacies of the MSM8916 platform and the APQ8016/APQ8039 get their hands on these tablets
Get a ROM dump of both tablets in stock form so people with bricked tablets can flash them with it
Get Root (Patch level on the 6.0.1 stock ROM is from October 2016, shouldn't be hard)
Get the bootloader unlocked, somehow, and if not, figure a way to get something like Safestrap running on it if the out-of-the-box kernel allows for it
Custom ROMs? LineageOS would be sweet, especially with some of the tablet-specific fixes that have dropped in the past couple months overall.
so I ask: is there any interest in the freeing of these super cheap tablets? The price to spec ratio is not bad (once again, I got my 6M10 for $25 shipped, and the seller has like 7 more as of the time of this writing), and it doesn't seem like it would be all too hard to unlock the bootloader and get it rooted (at least, from my perspective, that of a novice in this specific hardware field). There are plenty of these in the wild in the hands of people that bought the TVs and plenty in the hands that bought them from ebay when the tablets became obsolete.
This link contains screenshots of CPU-Z and the About Tablet settings section from the tablet, uploaded to imgur. If anyone needs more information on this tablet that needs an app or adb command, I can make this happen.
Board Pic of the XR6M10, XR6P10 should be the same inside:
(click for larger image)
Update: I have temp root.
I have temp root!-the latest kingroot (NOT Kingoroot) APK seemed to have done the trick. I was able to fire up adaway and get the hosts file set up with adblocks to keep the thing safer.
The root is still temporary so it goes away after a reboot. The rooting process involves it doing the root process once, then rebooting, then failing, then you reboot once more, and then retry rooting from the app. From here, 80% of the time, it works and you're able to get temporary root for that boot session.
Once you're done with anything you need root for, you should reboot and then uninstall Kingroot, which you then need to deactivate the device administrator priveleges for, before it will allow you to cleanly uninstall it.
I also made a huge discovery that may turn out better for anyone that can help getting this thing properly rooted and the bootloader unlocked... it seems the file manager included in the stock ROM is v3.0.0 from Cyanogenmod 12.1.
This makes me think that the ROM creator either used that since it was opensource and readily available than come up with their own solution, or that this ROM has some cyanogenmod roots.
I also found this post from another Q&A thread in this section:
TheDrive said:
This device have made by Chinese/Indian company Borqs. The code name Bennu-M. Platform is Qualcomm APQ8016 (MSM8916 w/o modem). There should work standard method to bring EDL mode. Hold Vol+ and Vol- at power on (press power). Then connect to the PC. Thus device will stay look dead, however should be detected as Qualcomm QDLoader 9008 on the PC side. This is the factory described method.
You can flash factory firmware from this mode using external bootloader (programmer) for MSM8916 firehose protocol. This procedure is described in the thousands of manuals around the net. Qualcomm tools like QPST or QFIL can be used as good as many 3rd party utils to flash and manage any another available way. Many professional 'box' tools should support this device too but only as 'generic' msm8916 (if applicable).
However I can't find the firmware package for this device anywhere. You should ask and require the manufacturer/distributor to publish firmware, the source code and all the corresponding matherials to be able to flash and rebuild firmware from sources in any manner you want without any limitations as required by GNU/GPL free open source software licenses this firmware is obligated to.
Everyone who have the device working or software dead, can try to dump the current firmware and data, stored on the internal eMMC memory module in part(s) or in whole image using free QTools project utilities and suitable external bootloader with ability to dump eMMC, not only to flash as many factory supplied programmers do. There are programmer(s) for MSM8916 available in the project repo. Read and understand manuals carefully before trying anything!
There is definitely another ways to root, dump, flash, manage the device in any manner YOU WANT, not only the way you are "allowed" to use your own device by manufacturer/distributor. FTA!
You can root the device then dump all the multiple partition images manually (dd if=/dev/block/mmbblk0...... of=/sdcard/......) or using built custom recovery like CWM/TWRP for your device. Please note, kernel sources are important but not mandatory to build e.g. CWM. You can build one using CWM image from the similar device and the kernel (boot/recovery) image binaries from your device. There are good manuals and image repacking utils available around like e.g. AndImgTool.
There are the way to produce factory image from the eMMC/partitions dump(s). Use utils like R-Studio to dump particular partition images from the eMMC dump (it's like whole HDD or UFD image with all the sectors raw, one by one, w/o any modifications/compression/etc) Manuals / utils are avavailable to make e.g. sparse and xml scripts set which is flashable by the programmer in the EDL mode (i.e. from any damaged state, because EDL is built in to the PBL and masked to the internal CPU ROM, thus can not be damaged in any manner, except firing the CPU up).
You can also flash partition images from the more common Fastboot mode, unless eMMC GPT and bootloaders (SBL/RPM/TZ/ABoot) stay intact (logo showed). You can't dump from fastboot, which is common due to the (foolish) 'safety' requirements. It's security by obscurity and is definitely not for your favor, but for the corps control over you and force to send valuable private data to foreign clouds.
Please share eMMC full and/or partitions dumps using reliable 'neverending' file cloud/hosting since there is no factory firmware available yet (ever). I do not own this device and never seen being overseas, so I can't share.
Click to expand...
Click to collapse
This gives a little bit more information but seems to be more waffle than helpful. Still need someone, or some individuals, that can get one of these devices into their hands and work on a way to get the bootloader unlocked, the eMMC dumped, and ROMs going.
Update file?
I THINK I have the update file for 6.0.1. I did a packet sniff on a 5.1.1 tablet using a mitm packet sniffer and I ran the system updater, and was able to get this URL:
http://updatev.vo.llnwd.net/v1/idownload/64821.bin
The filesize is 570MB or so, and it looks like it might be the real deal. since it's a .bin file and 7zip can't read it, I won't be able to see what it really is without going over to the box that has a copy of universal extractor installed.
I'll be doing this momentarily and editing this post once I figure out what the contents are or if it's even readable to that extent. Knowing vizio, it could very well be encrypted and need decrypting by the updater application.
Update: it seems to be encrypted. oh joy.
Update 2: I got together with a friend on discord and we successfully decompiled the updater app to a point.
This MEGA link contains all the files thus far and a copy of the tablet's /system/framework folder for decompiling purposes.
However, it doesn't seem we're getting anywhere. the file is still encrypted and I still can't figure out what's needed to decrypt it. Hopefully someone with more knowledge on this can lend a hand.
Sudosftw said:
I THINK I have the update file for 6.0.1. I did a packet sniff on a 5.1.1 tablet using a mitm packet sniffer and I ran the system updater, and was able to get this URL:
http://updatev.vo.llnwd.net/v1/idownload/64821.bin
The filesize is 570MB or so, and it looks like it might be the real deal. since it's a .bin file and 7zip can't read it, I won't be able to see what it really is without going over to the box that has a copy of universal extractor installed.
I'll be doing this momentarily and editing this post once I figure out what the contents are or if it's even readable to that extent. Knowing vizio, it could very well be encrypted and need decrypting by the updater application.
Update: it seems to be encrypted. oh joy.
Update 2: I got together with a friend on discord and we successfully decompiled the updater app to a point.
This MEGA link contains all the files thus far and a copy of the tablet's /system/framework folder for decompiling purposes.
However, it doesn't seem we're getting anywhere. the file is still encrypted and I still can't figure out what's needed to decrypt it. Hopefully someone with more knowledge on this can lend a hand.
Click to expand...
Click to collapse
Just out of curiosity, with the temp root, have you tried using dd to get the recovery image off? If we can do that, we might be able to work on getting a custom recovery built.
Qiangong2 said:
Just out of curiosity, with the temp root, have you tried using dd to get the recovery image off? If we can do that, we might be able to work on getting a custom recovery built.
Click to expand...
Click to collapse
It's not possible to get a proper recovery image from within the system files so far as I know, but my take so far has been that there is no proper way to get that at this time without decrypting that file grabbed from the update server. I'd do it on a 5.x ROM since that will get me permaroot, but the issue is getting and keeping root on a 6.x ROM.
Although encrypted (so far as I can tell) the image linked above is the real deal, and I've given all I can to get it decrypted. A proper exploit to take care of this tablet's vulnerabilities and get temp root (on 6.x) that isn't kingo is what is really needed at this point so to not hinder going around the system with crudware and shady background apps, shouldn't be hard since the security patch level for the 6.x ROM is 2016-10-01.
Even if the ROM is extracted or a recovery image found, custom recovery won't be possible until the bootloader is unlocked, and this isn't doable until someone figures out how the qualcomm qdloader9008 stuff works with this specific tablet. Fastboot is unreachable and I'm almost sure I'm doing something wrong.
I'll get temp root and see about dd'ing stuff later on. What exactly would be needed for me to dd off? Whole disk and then go through it elsewhere? I could definitely see if rsync exists and dd over rsync to another box.
Sudosftw said:
It's not possible to get a proper recovery image from within the system files so far as I know, but my take so far has been that there is no proper way to get that at this time without decrypting that file grabbed from the update server. I'd do it on a 5.x ROM since that will get me permaroot, but the issue is getting and keeping root on a 6.x ROM.
Although encrypted (so far as I can tell) the image linked above is the real deal, and I've given all I can to get it decrypted. A proper exploit to take care of this tablet's vulnerabilities and get temp root (on 6.x) that isn't kingo is what is really needed at this point so to not hinder going around the system with crudware and shady background apps, shouldn't be hard since the security patch level for the 6.x ROM is 2016-10-01.
Even if the ROM is extracted or a recovery image found, custom recovery won't be possible until the bootloader is unlocked, and this isn't doable until someone figures out how the qualcomm qdloader9008 stuff works with this specific tablet. Fastboot is unreachable and I'm almost sure I'm doing something wrong.
I'll get temp root and see about dd'ing stuff later on. What exactly would be needed for me to dd off? Whole disk and then go through it elsewhere? I could definitely see if rsync exists and dd over rsync to another box.
Click to expand...
Click to collapse
I found this today: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
The miflash tool seems promising (it works with nearly any device)
For the dd stuff, you can usually figure out the partitions easily with the fstab file in /. However, getting a raw dump is always useful.
Really, the big 3 would be the recovery.img, the boot.img, and the system.img. We can work from there
Qiangong2 said:
I found this today: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
The miflash tool seems promising (it works with nearly any device)
For the dd stuff, you can usually figure out the partitions easily with the fstab file in /. However, getting a raw dump is always useful.
Really, the big 3 would be the recovery.img, the boot.img, and the system.img. We can work from there
Click to expand...
Click to collapse
I've had that installed whilst trying to figure the image out and the qdloader stuff, it doesn't do anything for this tablet sadly :/
Sudosftw said:
I've had that installed whilst trying to figure the image out and the qdloader stuff, it doesn't do anything for this tablet sadly :/
Click to expand...
Click to collapse
Hmmm. Which tablet do you have? The M or the P?
Qiangong2 said:
Hmmm. Which tablet do you have? The M or the P?
Click to expand...
Click to collapse
this is the M. the P was out of my price range ($40 shipped over $25 shipped) when I was looking at them, but now the Ms are going for around 25 bucks but 15 shipping from another seller, bringing the price up to 40 bucks where the P was. ended up buying the other Ms from the one seller and gave them out to family members because I was so impressed... but I really should have set some money aside for one of the Ps as well and didn't.
Sudosftw said:
this is the M. the P was out of my price range ($40 shipped over $25 shipped) when I was looking at them, but now the Ms are going for around 25 bucks but 15 shipping from another seller, bringing the price up to 40 bucks where the P was. ended up buying the other Ms from the one seller and gave them out to family members because I was so impressed... but I really should have set some money aside for one of the Ps as well and didn't.
Click to expand...
Click to collapse
Okay. You said miflash doesn't do anything, does the device show up in the application and not function? Or does it not show up at all?
Qiangong2 said:
Okay. You said miflash doesn't do anything, does the device show up in the application and not function? Or does it not show up at all?
Click to expand...
Click to collapse
just doesn't show up at all. and yet installing the qualcomm qdloader drivers says it's connected in device manager, so something's up. tried on two different boxes, different cables, no dice.
Sudosftw said:
just doesn't show up at all. and yet installing the qualcomm qdloader drivers says it's connected in device manager, so something's up. tried on two different boxes, different cables, no dice.
Click to expand...
Click to collapse
Hmmm. That's unusual. Are you running it in win 7 compatibility mode?
It would be nice to see community roms for these devices. I have the XR6P. If you need any info from this device, just tell me what to do.
I'm very interested in this as I have one of these tablets that I would like to use in my vehicle as a display for my piggyback ECU tuner. It doesn't currently support USB OTG, but I read that if I can gain root access I can add the file to give it USB Host functionality. Can anyone confirm this? I have tried several apps to get it rooted including Kingroot as you were able to get a temp root with that. Unfortunately Kingroot, as all the others I have tried, won't even install on the tablet. Again, I'm only looking to get this thing to be OTG capable. If anyone here has any suggestions, I would be very grateful! Thanks all!
I just bought an M remote to replace my broken P remote. My P remote had Android 6. My M remote has Android 5, and the OTA updater says there's no update. Any way to get Android 6 on this?
I have factory firmware for Bennu P and Bennu M , but take some time to upload the file.
ALANCHONG said:
I have factory firmware for Bennu P and Bennu M , but take some time to upload the file.
Click to expand...
Click to collapse
Hey. You can lay out the firmware for XR6M10
XR6M10 and XR6P10 firmware
konog said:
Hey. You can lay out the firmware for XR6M10
Click to expand...
Click to collapse
Mega Link: mega.nz/#F!n65kVYIT!PKH8A1WoD_Nc4DU_-9dbiQ
ALANCHONG said:
Mega Link: mega.nz/#F!n65kVYIT!PKH8A1WoD_Nc4DU_-9dbiQ
Click to expand...
Click to collapse
All the time, an error pops up at 12 seconds
Flash fail (-4002)
Log:
21:59:03.576 Arrival: \\?\USB#VID_05C6&PID_9008#5&13a74b18&0&11#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
21:59:03.591 Thread '_PortDownloadThread' started
21:59:04.610 Get Port ...
21:59:04.610 _GetDevicePortName (0): COM5
21:59:04.630 _ComPort: COM5
21:59:04.640 Get Port (0)
21:59:04.650 Flash ...
21:59:09.668 _Connect (0)
21:59:09.668 Downloading flash programmer: C:\_qcMUP\v8016-SIGNED-VIZIO-user-IMAGES\v8016-SIGNED-VIZIO-user-IMAGES\prog_emmc_firehose_8916.mbn
21:59:14.669 Failed to read the command from the opened port
21:59:14.669 _FlashProgrammer (-4002)
21:59:15.700 Flash (-4002)
21:59:15.700 Flash fail (-4002)
21:59:15.731 Download ended: -4002
21:59:15.763 Thread '_PortDownloadThread' ended
konog said:
All the time, an error pops up at 12 seconds
Flash fail (-4002)
Log:
21:59:03.576 Arrival: \\?\USB#VID_05C6&PID_9008#5&13a74b18&0&11#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
21:59:03.591 Thread '_PortDownloadThread' started
21:59:04.610 Get Port ...
21:59:04.610 _GetDevicePortName (0): COM5
21:59:04.630 _ComPort: COM5
21:59:04.640 Get Port (0)
21:59:04.650 Flash ...
21:59:09.668 _Connect (0)
21:59:09.668 Downloading flash programmer: C:\_qcMUP\v8016-SIGNED-VIZIO-user-IMAGES\v8016-SIGNED-VIZIO-user-IMAGES\prog_emmc_firehose_8916.mbn
21:59:14.669 Failed to read the command from the opened port
21:59:14.669 _FlashProgrammer (-4002)
21:59:15.700 Flash (-4002)
21:59:15.700 Flash fail (-4002)
21:59:15.731 Download ended: -4002
21:59:15.763 Thread '_PortDownloadThread' ended
Click to expand...
Click to collapse
Please check if the driver is installed