TABLET: Fusion5 Premium+ (Re-branded yuandao N90 II dual core RK3066)
ISSUE: The tablet is now stuck in recovery mode (red triangle black exclamation) Stock 3e recovery after a failed firmware upgrade which I think was due to me selecting 'upgrade' and not 'restore'.
Details:
Before this failure rkbatch tool could see my device.
I have now tried rkbatch tool on 4 different PC's with different OS'es (Win8 x64, Win7 x32, Win XP x32, Linux x32) and at least 5 different USB cables using the latest driver_assist and batch tools or Linux equivalents.
Can not get rktools to see device in flash mode on any of them.
All the PC's can see it in ADB though.
“adb devices” reports device in recovery mode.
There's no fastboot and no shell which reports *“exec*'/system/bin/sh' failed:*No*such file or directory” but sideload appears to work.
“adb ls” of /sys /system /data etc show they are all empty.
I have the found the following firmwares specifically for this device
:LINK withdrawn
:LINK withdrawn
PM for the links
Unfortunately both of these updates are *.img files which as I can't connect using rkbatch
tool, I can't flash.
I have tried zipping them and flashing from sideload or from SDCARD both both fail, from sdcard the error is “no update found”. In sideload mode it reports “installation aborted” after the verifying the update stage. I'm quite sure there is more to creating a working update.zip but unsure of the details.
My question is does anybody no of a way to convert these supplied .img files into a format, prbably update.zip, that I can either install via sideload OR from sdcard?
Thanks
Hi,
XDA has no section for your device, therefore this would be the best place to ask for help....
>*Android Development and Hacking*>*Android Q&A, Help Troubleshooting
Good luck!
Hopefully you'll find help there. It's in the right section. This is not where to get help, only direction. ?
Related
Hi.
I have done something stupid
Some website claimed that rom manager from clockworkmod would not work unless twrp was installed. (I guess they meant "for getting the CWM Recovery Boot Menu to work").
I had already rooted my device (Denver Tablet TAQ-80053 ARMv7 with Android 4.1.1) but I thought why not flash to TWRP with the file: "CWM-based-Recovery-v6.0.3.3-signed.zip" ?? BAD idea
Now "Recovery Mode" is only the "TeamWin Logo" then BLACK SCREEN and nothingness ??
Everything else is somewhat normal:
1) I can boot normally into the start screen of Android 4.1.1 and run applets etc.
2) I can connect to Windows 7 (x64) and get file access to everything.
But: Any flashing tool for windows cannot "see" my device, and I very much doubt that it could be a driver problem since I get full access to drives and files on the tablet (USB-connected to Windows 7 x64).
Do you have any thoughts about that ? Because to me it seems logical that a working windows-driver would also work with ADB or ... ?
I also tried the ADB installation with SDK etc. Everything installs fluently with no errors but when I do the "adb devices" command no devices are listed at all ?? The command "ADB Shell" returns an error.
Since I know about the settings needed on the tablet I have: set USB Debug Mode to ON and everytime I plug it in I select "Mass Storage Mode" to get file access from Windows; and it works fine.
As stated above, everything works except "boot into recovery mode" and ADB being able to "see" my device. Not even CWM Rom Manager can boot into recovery mode ??
I want to be able to flash a new OS but recovery mode seems to be the only way apart from the USB to Windows. I cannott accept the notion that the device is "almost bricked" just from installing the wrong
recovery image and now I cannot go back .....
I have spent too much time already and I have discovered that I am not the only one with this problem but I cannot find any solution (that actually works) anywhere. So writing to you guys must be my last
hope. The alternative is getting an axe and chop it to pieces just to be shure that it's completely dead and my $150 lost forever; gone out the window :\
Can anyone please advise me what to do ??
/Pete
PS: OMG captcha is unreadable 30 times or more . . . and then the session ran out. Great
Hi there,
I'm sorry but I can't find anything related to your question/device.
Please post that in the forum bellow for more answers from the experts but first you must register an account on XDA forum:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck
I'm having some trouble mounting a Kindle Fire in Fastboot mode on my system which is running Ubuntu 14.04.
I am new to any kind of Android development and have been following the excellent guides here by @kinfauns. Specifically I have the 5-scecond boot loop problem related to the power draw issue. The solution I'm pursuing is to swap the stock bootloader for FireFireFire. The guide says to do it with fastboot, since the conventional flash recovery method could be interrupted by the shutdown cycle.
So now, just when I think I have a solution to my real problem, I get out the fastboot cable, connect the kindle to my PC, and I get an error in Nautilus: Unable to open MTP device '[usb:001,006]'. Attempting mtpfs at the terminal returns:
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=1949 and PID=0007) is a Amazon Kindle Fire (ID1).
Found 1 device(s):
Amazon: Kindle Fire (ID1) (1949:0007) @ bus 1, dev 6
Attempting to connect device
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
I tried following a tutorial on Ubuntu forums for getting MTP to work. It involves using lsusb command to get the device id, making entries in /etc/udeb/rules.d and /lib/udev/rules.d, supposedly to allow MTP to access the device with proper credentials. However nothing worked.
Now, on the other hand, when the device is NOT in Fastboot mode, it mounts just fine, both in Nautilus and for purposes of checking with the adb devices command.
Seems to me that what I want is for it to mount in file transfer mode instead of MTP mode when in fastboot. The fix for this exact issue in Windows (as reported on other sites) is to change the driver in Windows Device Manager.
Can anybody help with this problem?
Thanks
Hello and thank you for using XDA Assist,
please create an account and ask your question here:
Kindle Fire Q&A, Help & Troubleshooting
Kind regards
Trafalgar Square
XDA Assist
I'm trying to root my tablet for a couple days now. It became kind of a challenge now to root it.
So here are the things I've tried:
Most famous one click root applications - KingoRoot (also the pc version), OneClickRoot, Framaroot, Zhuanhou (or something like that) , Baidu, Universal Androot, and a couple more. All failed. KingoRoot I tried a couple of times (maybe 10), all failed. First I was trying with a locked bootloader, then I unlcoked it, tried most of the things again, no success.
I tried following this thread to root it manually https://forum.xda-developers.com/showthread.php?t=2684210
Everything went well untill the part when I needed to access the files from nautilus in download mode. I tried both in an ubuntu on a virtual machine, and on a kali linux running on a live usb, but I couldn't see the files in nautilus. I tried fastboot mode also after I unlocked the bootloader, I also tried ADB sideload mode, no success.
I can see my device when I type adb devices when its on, can't see when its in recovery mode, I can see it when I type fastboot devices when it's in fastboot mode, both in windows and linux(es). I can't see it in sideload mode in adb devices (I don't know if it's supposed to be that way)
When I plug it into the PC in MTP mode, I can't see it in Windows and Ubuntu running on a VM (VMWare player), windows fails to install the driver (corrupted inf file or something), in Kali it shows up in MTP mode. I can see it in camera mode though, and it is listed in adb devices. I can connect to it's shell normaly, push files, etc. Can't switch to adb root.
I couldn't find CWM or TWRP recoveries for it either...
In the manufacturer website there are some files to download, including a reflashing manual in polish , a driver, that's actually just CWM universal driver, and their stock os image files, with sp flashing tool.
XDA Visitor said:
I'm trying to root my tablet for a couple days now. It became kind of a challenge now to root it.
So here are the things I've tried:
Most famous one click root applications - KingoRoot (also the pc version), OneClickRoot, Framaroot, Zhuanhou (or something like that) , Baidu, Universal Androot, and a couple more. All failed. KingoRoot I tried a couple of times (maybe 10), all failed. First I was trying with a locked bootloader, then I unlcoked it, tried most of the things again, no success.
I tried following this thread to root it manually https://forum.xda-developers.com/showthread.php?t=2684210
Everything went well untill the part when I needed to access the files from nautilus in download mode. I tried both in an ubuntu on a virtual machine, and on a kali linux running on a live usb, but I couldn't see the files in nautilus. I tried fastboot mode also after I unlocked the bootloader, I also tried ADB sideload mode, no success.
I can see my device when I type adb devices when its on, can't see when its in recovery mode, I can see it when I type fastboot devices when it's in fastboot mode, both in windows and linux(es). I can't see it in sideload mode in adb devices (I don't know if it's supposed to be that way)
When I plug it into the PC in MTP mode, I can't see it in Windows and Ubuntu running on a VM (VMWare player), windows fails to install the driver (corrupted inf file or something), in Kali it shows up in MTP mode. I can see it in camera mode though, and it is listed in adb devices. I can connect to it's shell normaly, push files, etc. Can't switch to adb root.
I couldn't find CWM or TWRP recoveries for it either...
In the manufacturer website there are some files to download, including a reflashing manual in polish , a driver, that's actually just CWM universal driver, and their stock os image files, with sp flashing tool.
Click to expand...
Click to collapse
Greetings and welcome to assist. Unfortunately you have already tried all the methods I would have suggested, you could try this as a last resort
https://forum.xda-developers.com/showthread.php?t=2684210
Good Luck
Sawdoctor
Hi All!
I have a Honda Connect audio system (39100-TB9-G61-M1)
After a navigation issue I updated the firmware on the device. The device updated correctly and rebooted. But, never started again.
I can flash the two file from usb after the device starting (ADA_usbdl_V0C.091.01_TV0X_04.zip and ADA_usbdl_V0E094001123_sec_14ada.zip)
But I can't flashing a file (AUD31CF.bin). The navi wrote: "There was a problem during the update. Please switch off the vehicle then restart to retry."
I restarted many times but nothings happened. the navi wont flash the file (AUD31CF.bin) and won't start.
What can I do whit this navi system?
Can somebody help me to recovering this system?
Rocco said:
Hi All!
I have a Honda Connect audio system (39100-TB9-G61-M1)
After a navigation issue I updated the firmware on the device. The device updated correctly and rebooted. But, never started again.
I can flash the two file from usb after the device starting (ADA_usbdl_V0C.091.01_TV0X_04.zip and ADA_usbdl_V0E094001123_sec_14ada.zip)
But I can't flashing a file (AUD31CF.bin). The navi wrote: "There was a problem during the update. Please switch off the vehicle then restart to retry."
I restarted many times but nothings happened. the navi wont flash the file (AUD31CF.bin) and won't start.
What can I do whit this navi system?
Can somebody help me to recovering this system?
Click to expand...
Click to collapse
!!!Update more information!!!!
I have a Fujistu FT0056A device. This device its a sat-nav in a Honda Civic.
The device is frozen. After a usb firmware flashing won't startet. Its in boot-loop. I tryed many solutions, but not working.
http://oi68.tinypic.com/w9jjvt.jpg
First time I tried to flashing from usb stick. I have thre original Honda flash file to tis device:
- For SH USB1 - AUD31CF.bin - I can't extract the bin file. Maybe this contain the boot and recovery images. - I can't flash with via usb stick. Its a error message... Maybe
this bin file contain the boot and the recovery images.
- For tegra EC/NC USB2 - ADA_usbdl_VL0.FFF.04_EXT_HFT_param02.zip - Flash zip file loaded up correctly to the device via usb stick.
- For Tegra USB3 - ADA_usbdl_V10096001123_sec_14ada.zip - Flash zip file loaded up correctly to the device via usb stick. This zip file contain a
"ADA_usbdl_10.096.00.1123.enc" file. Can't decrypt or extract. Its a password protected file. I not know whats the password...
I tried to downgrade, with older and upgrade with newer wersions, but not working....
Now I tried flashing via OTG USB on the USB-B system port
I can't find any driver to the device. I found many driver (apx ; nvidia shield ; toradex_usbpcdriver_32_64 ; universal naked drivers ; etc.) but the ****usb.inf file not
contains any record of this device, what they call it:
USB_Install, USB\VID_0955&PID_7102
USB_Install, USB\VID_0955&PID_7102&REV_0232
After the inf editing and With forced install, i can connecting the driver to the device with many "name":
NVIDIA USB Boot-recovery driver for Mobile devices"
NVIDIA Android Fastboot Device
NVIDIA Android Composite Device
Android Debug Bridge Interface
etc....
I found thre diferent driver dll version too:
WdfCoInstaller01009.dll
winusbcoinstaller2.dll
WUDFUpdate_01009.dll
-------------------------
WdfCoInstaller01009.dll
winusbcoinstaller2.dll
WUDFUpdate_01007.dll
------------------------
and
WUDFUpdate_01009.dll in another file size....
the device not aswered to the fastboot.
Fastboot devices
Cant find any device
Only the xiaomflash.exe can read a a devise serial:
015e8b67e833fc08
but, cant flash the device....
the virtualbox can read the device informations:
http://oi65.tinypic.com/jsjcys.jpg
After adding the usb and post settings in the virtualbox, i tried flashing the board wint ubuntu.
same as with windows. The device its in the ubuntu usb device list:
http://oi64.tinypic.com/2h2kqhg.jpg
but, if i like to flash the device, nothings happened. The flasher wait for the device...
http://oi63.tinypic.com/zwi52s.jpg
So.....
how can I find a solution for flashing this board?
Its any not public device driver to this device?
How can I flash the SH AUD31.bin?
Becouse i think the Tegra files loaded up correctly via USB stick. Now i must to give a "fastboot -w" command to the device, and then can booting correctly. I tried with
"fastboot -i 0x0955 -w command too". not working.
I think I must flashing the bin file with a eeprom félasher. I have eprom flasher, but the flasher can't flash this eeprom. find any eeprom flasher under 600$ for this
"25C512A" eeprom.
So.....
How can i unbrick tis device?
Any solution?
Thanks for the reply
Kind REgads,
Rocco
Rocco said:
!!!Update more information!!!!
I have a Fujistu FT0056A device. This device its a sat-nav in a Honda Civic.
The device is frozen. After a usb firmware flashing won't startet. Its in boot-loop. I tryed many solutions, but not working.
http://oi68.tinypic.com/w9jjvt.jpg
First time I tried to flashing from usb stick. I have thre original Honda flash file to tis device:
- For SH USB1 - AUD31CF.bin - I can't extract the bin file. Maybe this contain the boot and recovery images. - I can't flash with via usb stick. Its a error message... Maybe
this bin file contain the boot and the recovery images.
- For tegra EC/NC USB2 - ADA_usbdl_VL0.FFF.04_EXT_HFT_param02.zip - Flash zip file loaded up correctly to the device via usb stick.
- For Tegra USB3 - ADA_usbdl_V10096001123_sec_14ada.zip - Flash zip file loaded up correctly to the device via usb stick. This zip file contain a
"ADA_usbdl_10.096.00.1123.enc" file. Can't decrypt or extract. Its a password protected file. I not know whats the password...
I tried to downgrade, with older and upgrade with newer wersions, but not working....
Now I tried flashing via OTG USB on the USB-B system port
I can't find any driver to the device. I found many driver (apx ; nvidia shield ; toradex_usbpcdriver_32_64 ; universal naked drivers ; etc.) but the ****usb.inf file not
contains any record of this device, what they call it:
USB_Install, USB\VID_0955&PID_7102
USB_Install, USB\VID_0955&PID_7102&REV_0232
After the inf editing and With forced install, i can connecting the driver to the device with many "name":
NVIDIA USB Boot-recovery driver for Mobile devices"
NVIDIA Android Fastboot Device
NVIDIA Android Composite Device
Android Debug Bridge Interface
etc....
I found thre diferent driver dll version too:
WdfCoInstaller01009.dll
winusbcoinstaller2.dll
WUDFUpdate_01009.dll
-------------------------
WdfCoInstaller01009.dll
winusbcoinstaller2.dll
WUDFUpdate_01007.dll
------------------------
and
WUDFUpdate_01009.dll in another file size....
the device not aswered to the fastboot.
Fastboot devices
Cant find any device
Only the xiaomflash.exe can read a a devise serial:
015e8b67e833fc08
but, cant flash the device....
the virtualbox can read the device informations:
http://oi65.tinypic.com/jsjcys.jpg
After adding the usb and post settings in the virtualbox, i tried flashing the board wint ubuntu.
same as with windows. The device its in the ubuntu usb device list:
http://oi64.tinypic.com/2h2kqhg.jpg
but, if i like to flash the device, nothings happened. The flasher wait for the device...
http://oi63.tinypic.com/zwi52s.jpg
So.....
how can I find a solution for flashing this board?
Its any not public device driver to this device?
How can I flash the SH AUD31.bin?
Becouse i think the Tegra files loaded up correctly via USB stick. Now i must to give a "fastboot -w" command to the device, and then can booting correctly. I tried with
"fastboot -i 0x0955 -w command too". not working.
I think I must flashing the bin file with a eeprom félasher. I have eprom flasher, but the flasher can't flash this eeprom. find any eeprom flasher under 600$ for this
"25C512A" eeprom.
So.....
How can i unbrick tis device?
Any solution?
Thanks for the reply
Kind REgads,
Rocco
Click to expand...
Click to collapse
Hi there...
Did you ever manage to solve your issue ?
just wondering ^^ (I have a device that has the same issue, and trying to recover it see if I can hack it later... )
Thanks.
Thread Closed Per OP Request
Don't work,
I give up
Thanks in advanced. All comments can help!
I have a tablet I can depure via USB and where I can root the tablet. But if I connect to the internet, the "registration and password" of university program enters and is saved (even after formatting it is stuck on this screen) blocking the tablet, I believe that after the internet loads, it installs this locking program ... What would be the name of this type of application? I'd like to know, how remove this app, to If connect in internet, we can block (and try install TWRP via internet with TWRP Management)...
C.Modica said:
Hello everyone !
I've been trying to resolve this issue for weeks. I have a tablet that I can't unlock (it's super hard, it's like Dark Souls of tablets). Well let's start.
He has a program that blocks asking for password and user (this a old from a university), where you request access via wireless or 2G/3G. without it you can't access it, so I believe I have to change his firmware instaled in, but I'm having a hard time to make it.
• Let's go to basic product information:
The chip is a RK3066 (same from TV BOX based on rockchip).
The model is YPY L1050 from POSITIVO (it's from Brazil).
- Software and Items
I have the drivers installed (correctly);
I have adb installed;
I have SD_Card;
I have acess from PC;
The tablet is unroot;
• Back to the items:
So, the good news is that I have the same tablet model, unlocked (with another type of ROM that I am unaware of). That works normally, without problems. Well, I saw a procedure that basically it is possible to extract this image from the good tablet, to the locked tablet. I did that, I ended up extracting a series of .img files from the unlocked tablet: boot, cache, kernel, system, etc... ok.
• Trying a extract from unlock same tablet:
I try transfer the copied files from "good unlock tablet" (extrated with AndroidTool), and put in (with the same tool) in the lock tablet... There is a problem, even before starting the operation, I have the error "Test Device Fail ", in the last is not possible to transfer files via USB (I can only do commands like" ResetDevice ", or export the images from the blocked tablet via AndroidTool... and yes I have the drivers instaled, commands like adb sideloader in the fastboot works).
• Trying a firmware found in internet:
Well, I tryed to download the firmware found on the internet corresponding to the device model, but unfortunately I have the same error as above. I download the .img firware original and using the RKBatchTool and have the same error (the operation don't start, give "Test Device Fail" in "Upgrade" and "Restore").
I believe that both operations do not accept transferring via USB.
PS: The tablet unlocked the command of "TestDevice" works fine.
• What I was thinking of doing:
1 - I think I need to take the all .img(s) files extracted from the unlocked device, put it in a single image (.img), put it in a SD_Card and in the "fastboot" take the option "update rkimage from external storage". But I don't know how to do this. (I try search for it);
2 - Somehow being able to do "apply update from external storage", maybe doing the same procedure above with an "update.img", but I also don't know how to do that (put all img. files together in the form of a one update.img).
3 - Have anothers options, like "apply update from ADB", the PC response this conection with tablet, (I can see the device with ''adb device'' cmds in sideload mode in PC). The problem is that I don't know how I'm going to send the .img file, if I send it inside a .zip (I even tried that, send all the .img files inside a .zip to see if it works. The tablet arrives to read the files but in the end the operation aborts). So my knowledge is lacking in this part.
4 - Another would be such a "ROM Dump." I'd like to do a "ROM dump" with an SD card, I even researched it on the internet but I didn't find this procedure to rockchip (only for Amlogic).
With SD Card:
There was a youtube that managed to unlock a tablet like that, but it was a previous model that I'd like to unlock (and different version of firmware, android etc). His method was to put a bootable sd_card, but he doesn't explain how he does it (he only gives the file done) and looking at the files internally, I just think they were converted to linux formats (system.tar.gz, userdata.tar.gz, some .sh .so files, and a bootenv.img, uImage etc) and with completely different names from .img... It is a pity that it is not for my Tablet model .
Well, that's it in the end, I need to change the firmware and I don't know how to do it.
PS: I tried other operations/methods as well, but I will not comment so that this post doesn't get big.
Thanks in advanced. All comments can help!
Click to expand...
Click to collapse
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
C.Modica said:
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
Click to expand...
Click to collapse
It isn't going to work via adb unless the device is rooted and then it won't be via adb sideload, it would be done by using dd commands to dd the .img files directly to their partitions.
Sent from my SM-S767VL using Tapatalk
I just found a solution. It requires some tinkering, though.
I had to use a machine running windows 7, because that's the only OS that the drivers worked.
Download the firmware for the Ypy L1050F here: https://www.stockrom.net/2018/07/l1050.html
It comes with the drivers, the ROM, and a tool called RKBatchtool 1.8
You'll have to decompress everything, open RKBatchtool and choose the firmware that is in the ROM folder (Not the DEMO one).
Now comes the tricky part: You gotta undo the 3 screws aroud the tablet, then pry it open with your fingers(remember to remove microSD and SIM first, to avoid breaking stuff!). I recommend startind by the side with the usb, hdmi and power ports to get some leverage. The back cover should pop right off. Then you have to locate the NAND chip in it. Should be a Micron one with 48 pins. The small circle at one of the corners of the chip represents pin 1. Plug your usb cable to the tablet. With the tablet TURNED OFF, use a SIM removal tool or very fine tip metallic screwdriver to short pins 17 and 18 on the NAND chip and plug the power jack into the tablet. RKBatchtool should show that a device was connected. You can release the screwdriver now and just click the "Upgrade" button in RKBatchtool. Now this is very important: DO NOT UNPLUG your tablet until everything is done. It'll tell you when it's done uploading the firmware and checking it. Enjoy your new usable tablet!
I scoured the internet and found this procedure being used for TV Boxes with the same RK3066 SoC. AFAIK, nobody else managed to do it so far, so spread the word.
You are awesome. Broke the internet! I will follow your procedures to try to unlock it. Many thanks again xmas for you.
[edit] don't work