I know that SkyworthDigital is the manufacturer of Mecool KM2 Plus right?
So what is the procedure to start Mecool KM2 Plus in Recovery Mode?
This TV Box does not have a Reset button that allows you to access Recovery Mode in case of a crash on startup.
I already asked this question to Mecool support and they didn't know how to answer it?!
I sent an email to SkyworthDigital support and got no response?!
adb reboot recovery
aIecxs said:
adb reboot recovery
Click to expand...
Click to collapse
Is there a possibility to access Recovery Mode by booting with a file on the pendrive or memory card?
irinho said:
Is there a possibility to access Recovery Mode by booting with a file on the pendrive or memory card?
Click to expand...
Click to collapse
It is possible. The KM2 Plus has a factory mode that looks for a file on USB.
Code:
Starting the controller
USB XHCI 1.10
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
[sk_usb_cfg_init,259]load file "/skyworth/factory_mode/uboot/check_udisk.cfg" from u disk failed!
[sk_boot,108]general boot.
But only Skyworth knows what needs to be in that file.
Make a request to Skyworth that they publish the source code for their u-boot modifications. The GPL requires that they do this. Tell them that you'll sue!
you can sign OTA zip with platform test keys. I own Mecool KII PRO Amlogic S905D shipped with Android 7.1.1 rooted from stock (only su binary, no Superuser)
The Skyworth devices using certified androidtv builds are quite different than the generic aosp builds on Mecool's non-certified devices. The Mecool KII PRO ships with a userdebug build.
BigEmpty said:
It is possible. The KM2 Plus has a factory mode that looks for a file on USB.
Code:
Starting the controller
USB XHCI 1.10
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
[sk_usb_cfg_init,259]load file "/skyworth/factory_mode/uboot/check_udisk.cfg" from u disk failed!
[sk_boot,108]general boot.
But only Skyworth knows what needs to be in that file.
Make a request to Skyworth that they publish the source code for their u-boot modifications. The GPL requires that they do this. Tell them that you'll sue!
Click to expand...
Click to collapse
The problem is that Skyworth does not respond to emails. I sent an email about how to access Recovery Mode when booting the KM2 Plus and I didn't get a response?!
irinho said:
The problem is that Skyworth does not respond to emails. I sent an email about how to access Recovery Mode when booting the KM2 Plus and I didn't get a response?!
Click to expand...
Click to collapse
This works for all Android TV boxes with S905X4 chip.
Method 1:
1. Power off the device.
2. Disconnect power cable.
3. Keep pressing reset button while connecting the power cable.
4. After a few settings the recovery mode should start.
Method 2:
1. Enable developer mode.
2. Enable USB debugging.
3. Connect the device via USB cable to your pc.
4. Download platform-tools (adb) - https://dl.google.com/android/repository/platform-tools-latest-windows.zip
5. Open CMD window in folder with adb.exe file.
6. Execute "adb devices" to check if Windows recognizes the Android TV box.
7. Execute "adb reboot recovey".
8. Device should boot in recovery mode.
Method 3 - if recovery is broken:
1. Download https://disk.yandex.ru/d/dp5RAJJ51gst3Q
2. Format a USB stick to the FAT32 file system .
3. Copy the aml_ autoscript and twrp.img files which you just downloaded to the root of the USB drive.
4. Power off the device and disconnect power cable.
5. Insert the USB stick into the OTG USB port of the device (just try which of the USB ports works).
6. Connect power to the device while pressing the “RESET” button for 5-7 seconds.
7. TWRP (recovery) should start.
Source: https://slimboxtv.ru/twrp-vremennoe/
Hi
there are many ways to do that but the easiest way is to use ADB AppControl
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mazjed said:
Hi
there are many ways to do that but the easiest way is to use ADB AppControl
Click to expand...
Click to collapse
True, but you need a USB A male to USB A male cable to connect which most people don't have:
Or your pc has an USB C port, so you can use a USB A to USB C male cable:
This is probably the easiest method:
1. Download https://disk.yandex.ru/d/dp5RAJJ51gst3Q
2. Format a micro SD card to the FAT32 file system.
3. Copy the aml_ autoscript and twrp.img files which you just downloaded to the root of the micro SD card.
4. Power off the device and disconnect power cable.
5. Insert the micro SD card into the micro SD card slot of the device.
6. Connect power to the device while pressing the “RESET” button for 5-7 seconds.
7. The device should boot from the micro SD card and TWRP (recovery) should start.
If you don't have a micro SD card and/or reader, try it using a USB drive.
This TWRP is loaded from a USB drive or micro SD card into the RAM of your device, you cannot flash it to the recovery partition of your Android TV box.
The custom TWRP recovery can:
- open a terminal window
- browse and edit the files on your device
- factory reset
- format storage
- reboot to fastboot
- reboot to bootloader
- mount USB drives
- flash IMG files from your USB drive or micro SD card
- flash ZIP files from your USB drive or micro SD card
- backup your data to your USB drive or micro SD card
- restore a preciously made backup from your USB drive or micro SD card
- sideload via ADB
If your device is bricked, TWRP is by far the easiest way to fix your Android TV box.
wootje_ said:
True, but you need a USB A male to USB A male cable to connect which most people don't have:
Click to expand...
Click to collapse
Ho said so
you Do wireless adb no wires required
just connect the tv box to the same pc network .
And remember that The custom TWRP recovery won't work with password protected bootladers
mazjed said:
Ho said so
you Do wireless adb no wires required
just connect the tv box to the same pc network .
And remember that The custom TWRP recovery won't work with password protected bootladers
Click to expand...
Click to collapse
Normally wireless adb would be a simple solution. However, my MeCool KM2 Plus doesn't support wireless ADB. The option is missing in the Developer menu. It also requires your device too boot normally, it doesn't work if your device is bricked.
Maybe this app will trigger ADB over the network. On rooted Android it enables ADB over LAN & Wi-Fi. The app also shows which IP and port to connect to.
ADB Manager:
https://f-droid.org/packages/com.matoski.adbm/
Wireless adb method:
1. Download platform-tools (contains adb.exe)
2. Open command prompt
3. Run "cd /d <path to folder containing adb.exe>"
4. Run "adb connect <ip address>:<port>"
5. Run "adb devices"
6. Run "adb reboot recovery"
wootje_ said:
This works for all Android TV boxes with S905X4 chip.
Method 1:
1. Power off the device.
2. Disconnect power cable.
3. Keep pressing reset button while connecting the power cable.
4. After a few settings the recovery mode should start.
Method 2:
1. Enable developer mode.
2. Enable USB debugging.
3. Connect the device via USB cable to your pc.
4. Download platform-tools (adb) - https://dl.google.com/android/repository/platform-tools-latest-windows.zip
5. Open CMD window in folder with adb.exe file.
6. Execute "adb devices" to check if Windows recognizes the Android TV box.
7. Execute "adb reboot recovey".
8. Device should boot in recovery mode.
Method 3 - if recovery is broken:
1. Download https://disk.yandex.ru/d/dp5RAJJ51gst3Q
2. Format a USB stick to the FAT32 file system .
3. Copy the aml_ autoscript and twrp.img files which you just downloaded to the root of the USB drive.
4. Power off the device and disconnect power cable.
5. Insert the USB stick into the OTG USB port of the device (just try which of the USB ports works).
6. Connect power to the device while pressing the “RESET” button for 5-7 seconds.
7. TWRP (recovery) should start.
Source: https://slimboxtv.ru/twrp-vremennoe/
Click to expand...
Click to collapse
There is only one detail, the KM2 Plus does not have the reset button. If there was, it would be easy.
irinho said:
There is only one detail, the KM2 Plus does not have the reset button. If there was, it would be easy.
Click to expand...
Click to collapse
I did some testing and found a way:
1. Enable developer mode (tap "build" several times under device info in the settings).
2. Enable USB debugging in Developer settings.
3. Connect to your network using wifi (disconnect LAN).
4. Install the app I attached to this post.
5. Run the app.
6. Download platform-tools: https://developer.android.com/tools/releases/platform-tools
7. Extract the files
8. On Windows pc open the Start Menu
8. Type "cmd".
9. Open Command Prompt.
10. Navigate to the extracted folder using "cd /d <path to folder>".
11. Run "adb connect <ip address shown in the app>
12. Run "adb reboot recovery".
The device reboots into recovery. When booted into recovery, you can start bootloader, fastboot or rescue mode.
The MeCool KM2 Plus doesn't respond when I connected a USB cable when it was powered off. Other Android TV boxes running on the Amlogic S905X4 chip did start bootloader of fastboot when I pressed the reset button and connected a USB cable. But the reset button is missing, so I have to idea how to flash using a USB cable.
I didn't test booting from a micro SD card. When your device is bricked, it should boot from a micro SD card (it's default setting for Android TV when it cannot boot normally). I'm not planning to brick my device, so I can't test that method.
The KM2/KM2 plus (and most rebranded skyworth devices) use a virtual "reset button" in the form of a configuration file placed on usb (fat32 formatted flash drive) prior to powering up the device.
Using the virtual reset button requires at least the bootloader to be functioning. But a physical hardware reset button also requires a functioning bootloader in order to operate.
Skyworth devices have bootloader fastboot disabled (but not fastbootd), so the only recovery menu options that are likely to be of any use on a skyworth device are the options to factory reset the device and the option to flash an update from ud/sd. Any update zip used with the recovery menu must pass verification. Not just any update file will pass.
Related
Hello everyone,
I have a Samsung Galaxy S II (I9100) with Cyanogenmod 11 (Snapshot M12) installed. Recently I dropped my phone and the screen was completely shattered. The display does not work, neither does the touch. However, the phone works fine as I can turn it on and connect it via USB to my computer and access the data on my internal memory. Although USB debugging is enabled on my phone, I am unable to do anything because the computer isn't authorised i.e. I cannot press "OK" on the authentication prompt that I would have otherwise normally seen on the screen (screenshot attached). Is there any way to bypass this prompt or a workaround for it? I basically need to get a Nandroid backup of my phone and then factory reset it.
P.S.: I tried to access my phone via a program called "Android Control" but apparently it is practically useless without the debugging privileges.
Thanks.
Solved!
This guide assumes that USB debugging was enabled on your device before you broke it. You can enable USB debugging via recovery using:
Code:
adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
After digging through various threads I finally managed to bypass the secure USB prompt on my Galaxy SII with a shattered screen.
For this method to work you need another device running Android 4.4.2 or above with USB debugging enabled and the same computer authorised from that device i.e. connect that device to your computer and press "OK" on the authorisation prompt that appears on screen for secure USB debugging. Let us call this device the "authorised device".
"adb_keys" is the file we need from the authorised device which is located in /data/misc/adb/
Normally you must be rooted to take the adb_keys file from the device using "Root explorer" or "ES File Explorer" but I will assume that the authorised device is unrooted. You don't need to root it. However, if your authorised device is rooted then simply copy the adb_keys file on your computer and jump directly to Step 5.
Steps:
Connect the authorised device to your computer using USB (debugging enabled) and open a command prompt with administrator privileges.
To get the "adb_keys" file, use this command:
adb pull /data/misc/adb/adb_keys <destination path>/adb_keys
For example:
adb pull /data/misc/adb/adb_keys c:/adb_keys
The above command will save the adb_keys file to the root of your C: drive. You can change the destination folder to your liking. Now the job of the authorised device is done. You can disconnect it and disable USB debugging.
Once you get a copy of adb_keys, reboot the phone with the broken screen into recovery.
Now connect the broken phone to the computer using USB.
We need to copy the adb_keys file to the broken device. Use the command below:
adb push <file location> /data/misc/adb
For example:
adb push c:/adb_keys /data/misc/adb
After the file is copied, reboot your device using "adb reboot" and voila! You can now use adb shell.
Special thanks to torankusu for this post which helped me compile this guide.
Check out this thread by k.janku1 if you want to have full control over your device even with a broken screen (requires Java Runtime Environment and Visual C++ redistributable). This tool lets you use your device through your Windows PC even if your touchscreen doesn't work or you can't see anything.
P.S.: My broken device was a Samsung Galaxy SII running Cyanogenmod 11 (M12) and my authorised device was an unrooted Moto G running stock ROM.
Thanks man.
I'm (noob) trying to follow the guide which exactly fits my situation.
Status : Broken SGS7 screen with USB debugging enabled but cannot accept the computer
SGS4 backup phone where i extracted the adb_key
both are not rooted and running stock OS
Unfortunately i get stuck between step 6/7... When i reboot to recovery mode the windows does not recognize neither of the phones when conneted to USB. Therefore i cannot run the ADB command and copy the key on my broken phone (SGS7).
i can choose the "aply update From ADB" and then the computer recognizes the phone and i can find it in ADB devices "sideload" but here i cannot use the command "adb push....."
Ii've tried updating drivers googled alot, but without luck...
what am i missing?
input very appreciated
I too am a noob who was trying to follow this guide, which also exactly fit my situation. My status was a broken Sony Xperia screen with USB debugging enabled, but I was unable to click on the "accept" button whenever I hooked my phone up to my PC. I extracted a working adb_key from my new Asus ZooXS phone; neither phone is rooted, and both are running stock Android OS.
Unfortunately, I got stuck right between Steps 7 & 8; Windows did not allow me to use the ADB Push command to copy the key onto my broken Sony Xperia. I could Pull the key from my Asus using ADB just fine, but not the other way around.
I did eventually find an alternative solution: I used an OTG device & hooked up a mouse to my Sony Xperia so that I could get past the broken screen issues & navigate to Settings > Bluetooth. I then borrowed a Bluetooth Mouse & "discovered" it with my broken Sony Xperia. I could then unplug the OTG device & re-connect my phone to my PC via USB, & then click on the screen using the Bluetooth Mouse to "accept" my computer as always being authorized to perform USB debugging. Afterwards, I was able to use Helium backup to pull off most of my important data from my phone.
Hope this helps others who are running into the same problem....
i don't get it - authorizing adb via adb
The steps maq_ posted helped me rescue my data from my broken OP3. Combined with the information from here: https://stackoverflow.com/questions...b-rsa-key-with-broken-touch-screen-on-android which indicates the files between the computer (running adb) and the key file you copy to /data/misc/adb should "match" with each other. Indeed, you might need to have been bootloader unlocked (with a custom recovery) to use adb push to copy the adb_keys file to your broken phone. For me, since my broken phone was rooted I used a terminal emulator with the 'su' command (after successfully getting the file onto my broken phone) to copy the file over to /data/misc/adb.
Some tips that might help newbs before following maq_'s steps: First, re-install another copy of adb (remember the path you installed to on your PC). Second, erase contents of c:\Users\$name\.android\ (which contains existing keys generated by adb). Third, run adb kill-server to make sure other instances of adb don't confuse things.
maq_ said:
This guide assumes that USB debugging was enabled on your device before you broke it. You can enable USB debugging via recovery using:
After digging through various threads I finally managed to bypass the secure USB prompt on my Galaxy SII with a shattered screen.
For this method to work you need another device running Android 4.4.2 or above with USB debugging enabled and the same computer authorised from that device i.e. connect that device to your computer and press "OK" on the authorisation prompt that appears on screen for secure USB debugging. Let us call this device the "authorised device".
"adb_keys" is the file we need from the authorised device which is located in /data/misc/adb/
Normally you must be rooted to take the adb_keys file from the device using "Root explorer" or "ES File Explorer" but I will assume that the authorised device is unrooted. You don't need to root it. However, if your authorised device is rooted then simply copy the adb_keys file on your computer and jump directly to Step 5.
Steps:
Connect the authorised device to your computer using USB (debugging enabled) and open a command prompt with administrator privileges.
To get the "adb_keys" file, use this command:
adb pull /data/misc/adb/adb_keys <destination path>/adb_keys
For example:
adb pull /data/misc/adb/adb_keys c:/adb_keys
The above command will save the adb_keys file to the root of your C: drive. You can change the destination folder to your liking. Now the job of the authorised device is done. You can disconnect it and disable USB debugging.
Once you get a copy of adb_keys, reboot the phone with the broken screen into recovery.
Now connect the broken phone to the computer using USB.
We need to copy the adb_keys file to the broken device. Use the command below:
adb push <file location> /data/misc/adb
For example:
adb push c:/adb_keys /data/misc/adb
After the file is copied, reboot your device using "adb reboot" and voila! You can now use adb shell.
Special thanks to torankusu for this post which helped me compile this guide.
Check out this thread by k.janku1 if you want to have full control over your device even with a broken screen (requires Java Runtime Environment and Visual C++ redistributable). This tool lets you use your device through your Windows PC even if your touchscreen doesn't work or you can't see anything.
P.S.: My broken device was a Samsung Galaxy SII running Cyanogenmod 11 (M12) and my authorised device was an unrooted Moto G running stock ROM.
Click to expand...
Click to collapse
Thanks for clarifying TWRP and UNLOCKED bootloader is required.
TWRP is not available for some devices. Luckily i found a ported recovery.img for my broken tablet. Unfortunately adb shows device as offline in TWRP, adb does not work in recovery.
I finally managed installing adbkey.pub via script. does not work on dm-verity, KNOX enabled or locked devices!
1. install ODIN (Samsung) or SPFLASH tool (MTK)
2. get the firmware for your device (fw.updato.com)
3. unpack system.img
4. add your own shell script (backdoor) to /system/etc/init.d, /system/etc/install-recovery.sh or whatever
5. repack your custom system.img
6. flash system.img
7. copy RSA Key to /sdcard via MTP
My (backdoor) shell script was a watchdog looking for another shell script on /sdcard. The second shell script was copying adbkey.pub from /sdcard to /data partition. This worked without root because init scripts run with root permissions on boot.
With this method i was able to backup userdata from my broken tablet via adb. TWRP has adb backup option too, in case touch screen is broken.
I will explain in detail on request.
edit: for experts only: instead of flashing whole system.img, you can do slight modification using Tarek Galal inception Utility via ODIN, for example "Place your adb keys, configure USB debugging"
edit2: most recent version of that backdoor script can be found here
https://forum.xda-developers.com/showthread.php?t=4111923
my touch is broken and i cant select usb authorization as ok... device is not rooted...
device name is sony z3...
i have another device with 4.4 and with that device i made a backup of drm keys... now what should i do?
sorry if english is bad... helpwill be really appriciated....
hello, i have te same problem with my huawei p smart. does this work for huawei to?
no, but you can connect OTG keyboard and unlock screen. that should unlock MTP you can at least transfer pictures. even Monitor via MHL/HDMI is possible for some devices
https://dtmedia.tech/list-of-mhl-compatible-phones
speedin said:
I'm (noob) trying to follow the guide which exactly fits my situation.
Status : Broken SGS7 screen with USB debugging enabled but cannot accept the computer
SGS4 backup phone where i extracted the adb_key
both are not rooted and running stock OS
Unfortunately i get stuck between step 6/7... When i reboot to recovery mode the windows does not recognize neither of the phones when conneted to USB. Therefore i cannot run the ADB command and copy the key on my broken phone (SGS7).
i can choose the "aply update From ADB" and then the computer recognizes the phone and i can find it in ADB devices "sideload" but here i cannot use the command "adb push....."
Ii've tried updating drivers googled alot, but without luck...
what am i missing?
input very appreciated
Click to expand...
Click to collapse
Hi
I have the same connection impact when I use adb command too. Is there any solution for this situation?
Thank you.
aIecxs said:
Thanks for clarifying TWRP and UNLOCKED bootloader is required.
TWRP is not available for some devices. Luckily i found a ported recovery.img for my broken tablet. Unfortunately adb shows device as offline in TWRP, adb does not work in recovery.
I finally managed installing adbkey.pub via script. does not work on dm-verity, KNOX enabled or locked devices!
1. install ODIN (Samsung) or SPFLASH tool (MTK)
2. get the firmware for your device (fw.updato.com)
3. unpack system.img
4. add your own shell script (backdoor) to /system/etc/init.d, /system/etc/install-recovery.sh or whatever
5. repack your custom system.img
6. flash system.img
7. copy RSA Key to /sdcard via MTP
My (backdoor) shell script was a watchdog looking for another shell script on /sdcard. The second shell script was copying adbkey.pub from /sdcard to /data partition. This worked without root because init scripts run with root permissions on boot.
With this method i was able to backup userdata from my broken tablet via adb. TWRP has adb backup option too, in case touch screen is broken.
I will explain in detail on request.
edit: for experts only: instead of flashing whole system.img, you can do slight modification using Tarek Galal inception Utility via ODIN, for example "Place your adb keys, configure USB debugging"
Click to expand...
Click to collapse
ThanK You Senior for posting the solution.
Can you please help me in this.
I am using mediatek device
Didn't find /system/etc/init.d
Didn't find /system/etc/install-recovery.sh
But found "" install-recovery.sh "" inside /system/bin folder
Now do i have to only paste the your given rsa_copy.sh scrip in this file?
and paste the pub_keys from authorize device to /sdcard/
That method will most likely fail because dm-verity deny booting if any modifications detected. You can however patch boot.img with Magisk (to disable dm-verity). What android version/mediatek device you have?
Yes you can replace install-recovery.sh or add line
Code:
/system/bin/sh /path/to/rsa_copy
/system/bin/sh /path/to/99userinit_daemon
But I do not recommend this method any longer, modifications in /system should be avoided. Instead you could simply disable RSA authorization and enable usb-debugging in default.prop
https://forum.xda-developers.com/showthread.php?t=1867446
I recommend AIK it is capable of re-signing AVBv1-signed boot.img
I have android 7
mt6753
init.d is n't here
placing code inside install-recovery.sh didn't work because it runs with root privileges
now i am trying to cp /system/adbkey.pub /data/misc/adb/adb_keys
and tring to modify boot.img
aIecxs said:
That method will most likely fail because dm-verity deny booting if any modifications detected. You can however patch boot.img with Magisk (to disable dm-verity). What android version/mediatek device you have?
Yes you can replace install-recovery.sh or add line
Code:
/system/bin/sh /path/to/rsa_copy
/system/bin/sh /path/to/99userinit_daemon
But I do not recommend this method any longer, modifications in /system should be avoided. Instead you could simply disable RSA authorization and enable usb-debugging in default.prop
https://forum.xda-developers.com/showthread.php?t=1867446
I recommend AIK it is capable of re-signing AVBv1-signed boot.img
Click to expand...
Click to collapse
Senior Help. (I am extra noob)
I also noticed data folder inside boot.img can I directly put " adb" folder here?
no. data directory is just mount point. no longer required to place adb_keys, just edit default.prop with Notepad++
aIecxs said:
no. data directory is just mount point. no longer required to place adb_keys, just edit default.prop with Notepad++
Click to expand...
Click to collapse
I attempted this trick with working phone's boot.img (working img) but even after repacking boot.img without edits phone stuck/hangs on boot (without animation)
Recommend me a good tool for unpacking and repacking boot.img with guide.
(I already tried with android kitchen on Linux (This one's boot.img make phone report after boot animation) and unpack/repack Tool on windows ( http://www.mediafire.com/file/nvo2popw26k4mit/IMG_Extractor_2.0.rar/file) and this one's boot.img doesn't boot phone to boot animation and hangs on initial logo)
I tried this on other working phone
@osm0sis may have a look into boot.img can you upload please?
aIecxs said:
no. data directory is just mount point. no longer required to place adb_keys, just edit default.prop with Notepad++
Click to expand...
Click to collapse
I attempted this trick with working phone's boot.img (working img) but even after repacking boot.img without edits phone stuck/hangs on boot (without animation)
Recommend me a good tool for unpacking and repacking boot.img with guide.
(I already tried with android kitchen on Linux (This one's boot.img make phone report after boot animation) and unpack/repack Tool on windows ( http://www.mediafire.com/file/nvo2popw26k4mit/IMG_Extractor_2.0.rar/file) and this one's boot.img doesn't boot phone to boot animation and hangs on initial logo)
aIecxs said:
@osm0sis may have a look into boot.img can you upload please?
Click to expand...
Click to collapse
Yes please,
LT700 is for testing purpose workig phone.
Both phones are almost from the same manufacturer (Note: but different models) Even unmodified repacked file does make phone boot success.
Uploading both stock and magisk patched working images of both phone
I recently got prestigio 3970b duo 7 " tablet that is stuck on the boot . With power on it would remain on the first screen and would not go any way, it was not possible to enter into recovery mode or to get recognized by the computer when it is connected via USB port with the classic combination of pressing vol + and power button at the same time .
Here's how I managed to revive :
Things you need for this:
1. AML tool from this link http://www.mediafire.com/download/y86c6f99irj3nme/AML_Flash.zip
Unzip it!
2. Firmware I found at the following address http://yf.value4it.com/Service_Files/TabletPC/PMP3970B/
I have used PMP3970B_20130505_v1.0.7.zip – unzip it!
3. Mini SD card 1GB minimum
4. Computer win7 64bit
5. Tablet stuck on boot with full battery
So this i what i did. I have downloaded AML tool on my computer and unziped it, downloaded firmware for flashing and unziped it (when unziped you will have 3 files, one is .zip file and you don't need to unzip it) , formated in FAT32 my SD card and copied firmware files on it. Now you are ready for tablet.
I have plugged in my USB cable while holding volume + button and short pressing power button about 10 times and computer finally recognize that some device is plugged in it. It will try to find drivers, but it can't be found.
Now you need to go in Control Panel - Device manager and you will see your tablet as Unknown device - M3-CHIP, now right click on it go to properties – driver – update driver, select browse my computer for drivers.
You will find drivers in unziped files of AML tool directory in AmlogicusbBurningdriver folder win7.
Windows will ask you if you want to do this, answer yes. Now it will install drivers on your tablet.
After that you need to go in your AML tool folder and find ImageBurnTool.exe and start the program, it will go to 62% or 65% and it will stop, saying it can't finish, but no worry, now you can close that program and unplug the tablet.
Leave tablet power off and insert mini SD card with flash files.
Now power on tablet by pressing only power button and it will start to flash the tablet by it self.
When it is done it will boot up and your tablet is alive again!!!
Now you can get your SD card out from tablet.
I hope that this will help someone.
This 100% worked for me, a i hope you understand that i am not going to take any responsibility if you break your tablet by doing this.
yf.value4it. com/Service_Files/TabletPC/PMP3970B/PMP3970B_20130505_v1.0.7.zip
Thank you sir!
its worked perfectly!!! amazing so much problems and find your solution, thank you very much
Thanks, worked like a charm.
So, as the story goes, I accidently bricked by tablet, by rooting it.
Now all I have is.
- EFI Shell
- EFI OS
- my USB Stick
I managed to boot the stock 4.4.4 firmware downloaded from "" and it flashed it's files (system.img boot.img etc.)
However the tablet still refused to boot.
Nevermind Fixed it.
==================================================================================
=======FIXNG you tablet (Onda V919 Air Dual OS in my case ) WITHOUT Fastboot===================
Disclaimer: this WILL completly erase your Tablet and REMOVE THE WINDOWS PARTITION if you had one
It is advised to remove the Micro SD from your TABLET PRIOR USING THIS FIXING PROCESS, it MIGHT GET ERASED
All you need to fix your tablet (as long as you can still access the Bios Screen via USB Keybaord and pressing ESC during boot) is:
- USB OTG Adapter
- USB Hub (preferably self powered over USB)
- USB Keyboard
- USB Stick (formatted FAT 32)
In my case I required the Firmware "V919_Air_DualOS_4.4.4_V1.0.0_v7" (Kernel Version: 3.10.20-00004-gf8a8ae3-dirty).
#00 Fetching the Firmware
##This is the step I cannot help you with: You need to aquire the corresponding FW for your Tablet (it will be a *.rar file with at least 500MB I surmise)
1. Extract the files from the rar to the USB Stick (formatted in FAT32)
2. Connect the USB Keyboard to the Hub
3. Connect the USB Stick to the hub aswell
4. Connect the USB Hub itself to the Tablet (by USB OTG)
5. Turn the Tablet on and press "ESC" immediately & hold it until you enter BIOS (this SHOULD work, even if you tablet refuses to boot into Fastboot via VOL+,VOL- & Power hold)
6. Change the boot order inside "BOOT" to 1. EFI Shell
7. Press F4 and "Save and Exit" (leave everything connected and don't touch the Tablet)
8. The Tablet should now reboot to EFI Shell
9. From here on things should go automatically (startup.nsc should be automatically read from the stick and should autoboot the Recovery files)
[[startup.nsc should contain this line (if you open it in the Editor of your PC): efilinux-eng.efi -f droidboot.img]]
10. If DroidBoot is on...: biggest you are nearly done !
11. wait for Droid Boot to flash all files (system.img will take a REALLLLLY long time... just leave everything as is)
12. Tablet will reboot in Android Mode
I'd love if there was a subcategory called "Onda Tablets" so s.o. could pin this.
It is possible that such guide exists already, but I had spent the last day just fixing my device... so...)
Please report back to tell me if it worked for you.
If I feel lucky I might add some images to this guide sometime...
about The solution.
-Rye- said:
So, as the story goes, I accidently bricked by tablet, by rooting it.
Now all I have is.
- EFI Shell
- EFI OS
- my USB Stick
I managed to boot the stock 4.4.4 firmware downloaded from "" and it flashed it's files (system.img boot.img etc.)
However the tablet still refused to boot.
Nevermind Fixed it.
==================================================================================
=======FIXNG you tablet (Onda V919 Air Dual OS in my case ) WITHOUT Fastboot===================
Disclaimer: this WILL completly erase your Tablet and REMOVE THE WINDOWS PARTITION if you had one
It is advised to remove the Micro SD from your TABLET PRIOR USING THIS FIXING PROCESS, it MIGHT GET ERASED
All you need to fix your tablet (as long as you can still access the Bios Screen via USB Keybaord and pressing ESC during boot) is:
- USB OTG Adapter
- USB Hub (preferably self powered over USB)
- USB Keyboard
- USB Stick (formatted FAT 32)
In my case I required the Firmware "V919_Air_DualOS_4.4.4_V1.0.0_v7" (Kernel Version: 3.10.20-00004-gf8a8ae3-dirty).
#00 Fetching the Firmware
##This is the step I cannot help you with: You need to aquire the corresponding FW for your Tablet (it will be a *.rar file with at least 500MB I surmise)
1. Extract the files from the rar to the USB Stick (formatted in FAT32)
2. Connect the USB Keyboard to the Hub
3. Connect the USB Stick to the hub aswell
4. Connect the USB Hub itself to the Tablet (by USB OTG)
5. Turn the Tablet on and press "ESC" immediately & hold it until you enter BIOS (this SHOULD work, even if you tablet refuses to boot into Fastboot via VOL+,VOL- & Power hold)
6. Change the boot order inside "BOOT" to 1. EFI Shell
7. Press F4 and "Save and Exit" (leave everything connected and don't touch the Tablet)
8. The Tablet should now reboot to EFI Shell
9. From here on things should go automatically (startup.nsc should be automatically read from the stick and should autoboot the Recovery files)
[[startup.nsc should contain this line (if you open it in the Editor of your PC): efilinux-eng.efi -f droidboot.img]]
10. If DroidBoot is on...: biggest you are nearly done !
11. wait for Droid Boot to flash all files (system.img will take a REALLLLLY long time... just leave everything as is)
12. Tablet will reboot in Android Mode
I'd love if there was a subcategory called "Onda Tablets" so s.o. could pin this.
It is possible that such guide exists already, but I had spent the last day just fixing my device... so...)
Please report back to tell me if it worked for you.
If I feel lucky I might add some images to this guide sometime...
Click to expand...
Click to collapse
HI what if you did all of that but it gets to the flash bit, but it say flash failed can't format partition flash failed..... What should i do?
Symptoms
The classic symptoms of the issue are at some point the Nvidia Dreamtab will stop booting and hang at the Dreamworks characters screen and never boot any further. The frequency ranges from once a month to a year. You are able to factory reset and the issue goes away for some periodicity and then returns.
NOTE: If you recently bought a new Nvidia Dreamtab and you have this character freeze right after doing the OTA then this probably isn't the issue, I am working on a different fix for that problem in this thread. If however this solution does fix your issue I'd like to hear about it.
Background
The tablet uses the linux ext4 filesystem. The Dreamtab kernel requests a filesystem check every 20 partition mounts(typically during reboots) or when the files system is marked dirty(the tablet is hard powered off, or some other glitch). The tablet is missing the fsck binary which is the filesystem checker similar to what you might have seen in windows with chkdsk. Without this file the tablet can not check filesystem and the kernel waits indefinitely for that to happen and your tablet sits and the Dreamworks characters.
Solution
Temporarily boot to a program(TWRP) that can install the filesystem file on the tablet. To temporarily boot to TWRP the bootloader must be unlocked. The unlock procedure requires erasing all information on the tablet which isn't an issue if you are currently experiencing the problem as a factory reset was the only way to recover anyway. If you have a working tablet and want to apply this fix you should find a way to backup your files prior to attempting this. To better understand how the low level Nabi functions this should be required reading and will help better understand what you are doing. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Procedure
Only for Nvidia Dreamtab NV08B. Use this at your own risk, your warranty is void. You will lose all personal data on the device
Link to video Youtube video installation
1) Down load the drivers.
-- There are 3 popular options included in the link from above in the driver section of the Nabi General Information thread. Have them handy for the next step.
2) Download TWRP recovery.
-- The file is attached at bottom of post. DTTWRPinstaller300.zip
-- Note: You can automate some of the bootloader unlock and installing TWRP steps below with the install.bat file if you have a working Nabi.
3) Download the fsck patch.
-- The file is attached at bottom of post. NV08B_FSCK_PATCH.zip
4) Reboot to fastboot protocol
-- With Nabi powered off press and hold the power button and the vol + button until a small menu(bootloader menu) appears. Quickly release both buttons or the tablet will start booting normally. Using the vol- button to highlight the fastboot protocol(2nd option from top) and then press the vol+ button to select it. Note: Depending on if the drivers are installed the screen will change or stay the same.
5) Verify drivers installed or install drivers.
-- Open windows device manager. On Windows 10 type "device manager" in to the Cortana search bar. On other versions open run by pressing the "windows key" in lower left of keyboard while also pressing R key. Then type: devmgmt.msc
-- If you have "Android Device" and it's sub menu says bootloader/fastboot then you are set up. If down by "other devices" you have an unknown device then you will need to install the drivers from the selection and download you made from reading the Nabi General Information thread.
6) Unlock the bootloader
-- This step will ERASE ALL information on the tablet.
-- Unzip the DTTWRPinstaller300.zip to a location of your choosing. If you use Windows built in unzip utility make sure you check the box that says to open when unzipping is complete.
-- Hold the shift key on the keyboard while right clicking on the "files" folder. Then select "open command window here"
-- At the prompt type:
Code:
fastboot oem unlock
Note: You need to move quickly to the tablet and do the next step as there is a timeout
-- On the tablet it will ask if you want to unlock. Using the vol- key select "yes" with vol+ or pwr. If you do this properly in the command window on your computer it will tell you it is erasing the device.
7) Temporary boot TWRP
-- I can't remember if after the bootloader unlock if tablet is at fastboot, or if you have to power off the tablet and do step 4 again. I think you can just proceed.
-- At the prompt type
Code:
fastboot boot recovery.img
8) Get the patch file on the tablet
-- Option A: There are a couple options for this. Check the file explorer on your computer. If you see t8400n as a device you can just copy and paste the NV08B_FSCK_PATCH.zip to the internal storage by copy and pasting in windows. Go to step 9.
-- Option B: Insert a microSD card in your computer and copy the NV08B_FSCK_PATCH.zip to your microsd card and insert the sdcard in the tablet.
-- Option C: If the t8400n does not show up on your computer then you will need to transfer via ADB. This will require you to setup the ADB driver like you did for fastboot in step 5. Now in sub Android Device in Device Manager you should see ADB, if you don't install driver.
--Copy the NV08B_FSCK_PATCH.zip to the "files" folder where you extracted DTTWRPinstaller300.zip. It should be in a folder with adb, fastboot, AdbWinAPi, etc
-- At the command prompt type:
Code:
adb push NV08B_FSCK_PATCH.zip /sdcard
9) Install patch
-- In TWRP on tablet click the install tab. Generally you will now see the NV08B_FSCK_PATCH.zip if you picked option A or C. If not navigate to the sdcard folder. If you picked option B navigate up a folder and find external_sdcard folder and look in there.
Note: For external_sdcard it may be necessary to exit to TWRP main menu and select mount tab and make sure Micro SDcard is checked.
-- Once you have found the NV08B_FSCK_PATCH.zip from inside the install tab you can select it and then swipe to install. You should get verification it completed normally.
I know this is rather old, but I have a couple of these tablets I'm trying to get working again to give to a friend's kids, but this doesn't seem to work. Did you have to have USB debugging checked before the tablets stopped booting in order for this to work properly?
Basically I can do all the fastboot stuff without any errors, but when I try to boot to TWRP all the tablets do is pretty much rotate the screen 180° so the bootloader screen is in the opposite corner and the volume buttons no longer work until I hold power for ten seconds to power it off... Any help is greatly appreciated!
Hey xda members,
My name is Pierre, from France and new owner of X820 version 6GB 64GB (from Aliexpress).
I made a big mistake yesterday, wiping from TWRP all data (Sytem, applications etc.)
Now if I put "ON" again, it is just showing "EUI" logo, without end
I have still access to TWRP but no backup, not .img loaded in the phone.
I can't connect and load from USB the ROM, so I am honestly lost.
If you have just any idea,how to solve it! Please let me know
Thank you very much, and good evening,
TWRP has a backup solution for you. I did this same misstake like you.
In Advanced settings you can run ADB SIDELOAD.
I hope you have proper ADB drivers in your PC and command prompt in Windows is your friend.
With ADB SIDELOAD you can install ROM from your PC via USB to your bricked phone. ADB uses whole base of commands to control what you can do.
Follow this steps:
https://forum.xda-developers.com/showthread.php?t=2318497
Twrp also supports MTP so you should also be able to copy a rom on the sdcard when in twrp.
just use:
fastboot boot twrp.img (if TWRP you have in twrp.img file)
mobile boot in TWRP
then
adb push rom_file.zip /sdcard
after OK just install that rom from SDCARD via TWRP...
Thank you Razor, mikey and cr3pt !
If I am not mistaken, you provide me: 2 different solutions (ADB Sileload or abd push ROM).
It does mean, if I select the "one more easy" :
1. I boot in TWRP my phone
2. connect by USB (ADB drivers must be installed). Usually it is written MTP or "Android" but I can't see the external drive in Win10.
3 Then adb push rom_file.zip /sdcard in the Wincommand
4. wait and after disconnect USB
Then I will find the ROM to install in my phone.
Is it correct?
Yes
If you have TWRP, connect the phone to your computer, mount storage in TWRP, copy the rom of your choice, and install it. That simple
Sent from my Le X821 using Tapatalk
I use TWRP and always just drag and drop the ROM zip from PC to the phone's internal storage and it shows up in TWRP under install. It's super easy. As long as you have the correct drivers installed on your PC you shouldn't need to use adb.
kanagawaben said:
I use TWRP and always just drag and drop the ROM zip from PC to the phone's internal storage and it shows up in TWRP under install. It's super easy. As long as you have the correct drivers installed on your PC you shouldn't need to use adb.
Click to expand...
Click to collapse
Hey
My computer (Win 10) does NOT recognized sometimes: MTP, or sometime "Android". So in fact, I never the external storage in my windows.
That is why I can not simply "drop" unfortunately.
Should I maybe install ADB again?
install ADB, all necessary drivers. without that you can only dream about correct fix'a
piyerre said:
Hey
My computer (Win 10) does NOT recognized sometimes: MTP, or sometime "Android". So in fact, I never the external storage in my windows.
That is why I can not simply "drop" unfortunately.
Should I maybe install ADB again?
Click to expand...
Click to collapse
I'd try to start again clean. First completely remove adb and android device drivers from your computer. Then boot your phone into TWRP and connect it by usb to your computer and see if it auto installs the right drivers. If not, I guess you have to find where to download them from to install manually.
cr3pt said:
install ADB, all necessary drivers. without that you can only dream about correct fix'a
Click to expand...
Click to collapse
Can you give me please a link with the correct ADB and the correct drivers.?
I can't see the external drive even if adb devices gives me OK result.
Thank you,
you don't need external drive - correct is adb device. just push file when is visible in device manager
Hello !
It does work perfect, I finally use the "adb push" function!
Thank you very much all
cr3pt said:
just use:
fastboot boot twrp.img (if TWRP you have in twrp.img file)
mobile boot in TWRP
then
adb push rom_file.zip /sdcard
after OK just install that rom from SDCARD via TWRP...
Click to expand...
Click to collapse
It works! Thank you very very much!
Bro Its is new security added in windows 10... U can only install official and signed drivers in windows 10.. U should turn it off.. only then u can access adb and fastboot...
One more thing bro...
If u have lost every thing, but u r able to boot in twrp, then follow me:
1. Download any rom for le max 2 U want to
2. After downloading,copy it in ur pendrive
3.Boot in twrp
4.connect the pendrive to ur device using OTG adapter
5.Mount USB storage
6.wipe every thing again.
7.After installation,reboot
8.first boot may take time and then wgwghrussuwgskaaiiawg (U know the rest??)