Copy Android OS (Marshmallow),Flash the OS to another identical device - General Questions and Answers

hello..
i have a Bluewave 8 HD+ tablet running Kitkat 4.4.4,my friend also has Bluewave 8 HD+ tablet running Android Marshmallow.
when trying to check for an update for my Kitkat tablet,it says i am currently running the latest OS,no update available(i am sure they have because my friend's tab is running Marshmallow,we have the same Tablet,just running different OS)
Question:
how do i copy my friend's Android Marshmallow OS and flash it to my Kitkat Bluewave Tablet?(no need copying the files,settings,apps etc.,just the Marshmallow OS).
More power and God bless.
thanks,
Jovi
Update:
i flashed my Bluewave 8 HD+(Kitkat-i flashed my tab several times before but same Stock OS) using Rockchip Batch Tool provided by the manufacturer's website(http://www.wavetablet.com/wave8hd-marshmallow/resources/firmwareupdates) and downloaded the Marshmallow OS.
The flashing went flawless and after it finished flashing and tried to turn ON my Bluewave Tablet(with its new Marshmallow OS),the device will just turn on with the lights but no display.tried to poke the Reset Hole to no avail. I tried to connect said Tablet to my computer and it works as a normal(working)tablet,device drivers installed.From Computer,said Tablet is now connected as a Media Player device(before was Mass Storage,same as a USB Stick inserted to port) and i can see the storage info of the tablet from the computer.
Problem:
i want to reflash my Bluewave Tablet back to its Stock ROM(Kitkat) using the same Rockchip Batch Tool but it will no longer be detected by the said Tool( all drivers were installed).
Additional Info:
Volume Buttons- NO
Home(Physical)Button- NO
thanks in advance,
Jovi

Uhm Hey. I'm a bit too late to reply. I did the same thing as you did. Same result no display. But I've discovered that Marshmallow actually boots. I've plugged a mini hdmi to hdmi adapter and I hooked it up to my TV. Touch screen works, everything works except for the lcd. I'm still looking for a solution to make the lcd work.
---------- Post added at 04:25 PM ---------- Previous post was at 04:18 PM ----------
I don't really know why the lcd doesn't work...Maybe it requires different drivers?

if it requires different driver(if ever we know exactly what driver it is and we have a copy of it),how will you(we) gonna install the said LCD Drivers into the Marshmallow OS?
some people out there might help us?

jovirex said:
if it requires different driver(if ever we know exactly what driver it is and we have a copy of it),how will you(we) gonna install the said LCD Drivers into the Marshmallow OS?
some people out there might help us?
Click to expand...
Click to collapse
Yeah. I hope so. I don't really know what to do with it. Kitkat is a really old OS. I'm planning to experiment with it for a while and try to make the LCD work. I don't really get it though why the LCD doesn't work. They have the same resolution and same size.
Have you tried flashing the lollipop one? Does the LCD work?

Hello. I've finally discovered a way to reflash the old firmware back.
---------- Post added at 04:19 PM ---------- Previous post was at 04:17 PM ----------
You still interested? Sorry for the very late response. I was very busy at school. Y'know 17 yr old stuff. But I had finally time to fix that tablet.

It requires opening the actual device though but don't worry, its only held down by some plastic clips. Then you would have to remove the gray thermal pad and expose the rockchip cpu, nand flash and ram. The Nand flash here is what were after. Right beside the nand flash, there is a flash clk pin along with the ground pin beside it. I've read that the Wave 8 HD+ has volume buttons which enables you to enter the combination in order to reflash the rom. The combination is holding the +Volume while plugging in the micro usb to the computer. The batch tool will then detect the tablet. But in our case, we cannot do that since we do not have volume buttons. So I've researched more and found out that the Rockchip CPU has a MASKROM mode which would temporarily disable the marshmallow rom that we just flashed. Short circuiting the flash clk to ground would enable the Maskrom mode which would then enable us to flash back to the old stock kitkat rom.

Related

[Q] TF101 not recognized by PC (Windows 7/8 x64)

OK. First of all, although I'm using the TF101 for the first time, I'd like to say that I've done a fair bit of rooting, troubleshooting and customizing various Android devices (HD2, Desire, SE x10, SGS2, SGSN, SGSN2...). So I ensure you, any lack of knowledge regarding the TF101 is not caused by ignorance. I'm trying to find out the cause for my problem for few days now, but can't find something to catch on. There are many similar problems with TF101 not being recognized by PC, but they all offer solutions which don't work, I don't understand them, or which make no sense.
Let's start at the beginning.
I have gotten my hands on Asus EEE Pad Transformer TF101. It was really cheap. I was told it came form USA.
It's obviously rooted, has a custom rom and recovery (ClockworkMod Recovery v3.2.0.1. roach2010-tf101-r1)
This is waht it says in Settings>About:
Model Number:
Transformer TF101G (although I think it is actually just a Wi-Fi model - TF101, it has no SIM slot)
Android version:
3.2.1
Baseband version:
Unknown
GPS version:
V5.5.8
Wi-Fi version:
V5.2.65
Bluetooth version
v6.24
Kernel version:
2.6.36.4-g6aa10ba
[email protected] #20111023
Build number
HTK75.prime_epad-2.1.0-20111105
Mobile Dock version:
Not available​
It seems to be working fine, except for being totally filled up with apps, bloatware and data. Natural instinct was to install a clean ROM. I wanted to go with CM, and a newer Recovery, but I got stuck on the first step. I can't get it recognized on any of my computers. Both Windows 7 and 8.
However I plug it in, I get; USB device not recognized. One of the USB devices attached to you computer has malfunctioned... This happens when I connect the USB cable when Android is booted up, when in recovery and also in APX mode, providing I have entered it (I'm not really sure because the display is always black).
In Device Manager, I can see only one exclamation icon (I did enable show hidden devices) in Universal Serious Bus Controllers called Unknown Device, which seems to be from the TF101. I tried uninstalling it. Restarting both the tablet and the computers. I tried to manually override those Unknown Device drivers with ASUS Android USB drivers for Windows and Universal_Naked_Driver_0.72 and ventana apx driver, but it wouldn't take any of them. I also tried installing them manually by right clicking on the INF files, and still nothing.
Then I thought I could mount the sdcard or USB mode in recovery, but that wouldn't work either.
Any solutions?
Do you have the stock USB cable? Are you plugging in to a usb3 slot?
Does the rom have fast charge enabled? I think that's what it's called but it allows USB charge rather than seeing your files and such.
Do you have mtp mode or mass storage mode options on the tablet?
Sent from my SGH-T999 using Tapatalk 2
Yes, I have stock USB cable. At least I think so. I'm not the first owner. How can I be sure? It seems to be charging fine on the wall charger. It doesn't charge thru PC though.
If you are asking me if I tried it on USB 3.0; yes I did. Both 2.0 and 3.0. Not recognized.
I don't know if the ROM has "fast charge". I'm new to the TF101, and Honeycomb in general, and I didn't notice such an option. Where can I look?
I also didn't see any MTP/Mass storage modes in settings. Where would they be?
estugarda said:
Yes, I have stock USB cable. At least I think so. I'm not the first owner. How can I be sure? It seems to be charging fine on the wall charger. It doesn't charge thru PC though.
If you are asking me if I tried it on USB 3.0; yes I did. Both 2.0 and 3.0. Not recognized.
I don't know if the ROM has "fast charge". I'm new to the TF101, and Honeycomb in general, and I didn't notice such an option. Where can I look?
I also didn't see any MTP/Mass storage modes in settings. Where would they be?
Click to expand...
Click to collapse
Lol I don't know on honeycomb. It's been a long time but these threads are filled with fast charge and the other issue as well. Do some more searches it's bound to give you something.
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
Lol I don't know on honeycomb. It's been a long time but these threads are filled with fast charge and the other issue as well. Do some more searches it's bound to give you something.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I did look around. I read a ton of posts here and elsewhere. There is nothing to the point. People at transformer forums are actually advising to just forget about the usb and use wireless transfer instead, since there are so many people with this problem who can't solve it. That would be fine with me, but I'm especially stuck because I can't flash anything since my USB connection is not working, and current CWM recovery doesn't seem to support flashing from internal memory/sd card.
Before you do anything else, install TWRP recovery before you brick your TF with CWM
Install Goo Manager here
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Tap the menu dots at the top right of the app and choose "Install OpenRecoveryScript"
That should flash the latest TWRP recovery for you
estugarda said:
OK. First of all, although I'm using the TF101 for the first time, I'd like to say that I've done a fair bit of rooting, troubleshooting and customizing various Android devices (HD2, Desire, SE x10, SGS2, SGSN, SGSN2...). So I ensure you, any lack of knowledge regarding the TF101 is not caused by ignorance. I'm trying to find out the cause for my problem for few days now, but can't find something to catch on. There are many similar problems with TF101 not being recognized by PC, but they all offer solutions which don't work, I don't understand them, or which make no sense.
Let's start at the beginning.
I have gotten my hands on Asus EEE Pad Transformer TF101. It was really cheap. I was told it came form USA.
It's obviously rooted, has a custom rom and recovery (ClockworkMod Recovery v3.2.0.1. roach2010-tf101-r1)
This is waht it says in Settings>About:
Model Number:
Transformer TF101G (although I think it is actually just a Wi-Fi model - TF101, it has no SIM slot)
Android version:
3.2.1
Baseband version:
Unknown
GPS version:
V5.5.8
Wi-Fi version:
V5.2.65
Bluetooth version
v6.24
Kernel version:
2.6.36.4-g6aa10ba
[email protected] #20111023
Build number
HTK75.prime_epad-2.1.0-20111105
Mobile Dock version:
Not available​
It seems to be working fine, except for being totally filled up with apps, bloatware and data. Natural instinct was to install a clean ROM. I wanted to go with CM, and a newer Recovery, but I got stuck on the first step. I can't get it recognized on any of my computers. Both Windows 7 and 8.
However I plug it in, I get; USB device not recognized. One of the USB devices attached to you computer has malfunctioned... This happens when I connect the USB cable when Android is booted up, when in recovery and also in APX mode, providing I have entered it (I'm not really sure because the display is always black).
In Device Manager, I can see only one exclamation icon (I did enable show hidden devices) in Universal Serious Bus Controllers called Unknown Device, which seems to be from the TF101. I tried uninstalling it. Restarting both the tablet and the computers. I tried to manually override those Unknown Device drivers with ASUS Android USB drivers for Windows and Universal_Naked_Driver_0.72 and ventana apx driver, but it wouldn't take any of them. I also tried installing them manually by right clicking on the INF files, and still nothing.
Then I thought I could mount the sdcard or USB mode in recovery, but that wouldn't work either.
Any solutions?
Click to expand...
Click to collapse
Are those drivers signed? I know 7 will reject an unsigned driver for security reasons.
Nexus 4 CyanogenMod 10.1.0RC2
---------- Post added at 02:04 PM ---------- Previous post was at 02:01 PM ----------
estugarda said:
Yes, I have stock USB cable. At least I think so. I'm not the first owner. How can I be sure? It seems to be charging fine on the wall charger. It doesn't charge thru PC though.
If you are asking me if I tried it on USB 3.0; yes I did. Both 2.0 and 3.0. Not recognized.
I don't know if the ROM has "fast charge". I'm new to the TF101, and Honeycomb in general, and I didn't notice such an option. Where can I look?
I also didn't see any MTP/Mass storage modes in settings. Where would they be?
Click to expand...
Click to collapse
It should be somewhere in "storage" in settings.
Nexus 4 CyanogenMod 10.1.0RC2
Here you go hope it helps
Nexus 4 CyanogenMod 10.1.0RC2
*Detection* said:
Before you do anything else, install TWRP recovery before you brick your TF with CWM
Install Goo Manager here
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Tap the menu dots at the top right of the app and choose "Install OpenRecoveryScript"
That should flash the latest TWRP recovery for you
Click to expand...
Click to collapse
Unfortunately, GO Manager wouldn't install OpenRecoveryScript. It says something along the lines of "No Recoveries were found for your device..."
ryaniskira said:
Are those drivers signed? I know 7 will reject an unsigned driver for security reasons.
Those from Asus websites are signed 100%.
Nexus 4 CyanogenMod 10.1.0RC2
Click to expand...
Click to collapse
estugarda said:
Unfortunately, GO Manager wouldn't install OpenRecoveryScript. It says something along the lines of "No Recoveries were found for your device..."
Click to expand...
Click to collapse
You might need to update to ICS first then, maybe Honeycomb is too old
CWM has a habit of boot looping devices, I would try updating to an ICS ROM and then trying Goo again before going for a Jellybean ROM
EDIT - You might have more luck getting TWRP installed using Easyflasher
http://forum.xda-developers.com/showthread.php?t=1688012
In the same boat
estugarda said:
OK. First of all, although I'm using the TF101 for the first time, I'd like to say that I've done a fair bit of rooting, troubleshooting and customizing various Android devices (HD2, Desire, SE x10, SGS2, SGSN, SGSN2...). So I ensure you, any lack of knowledge regarding the TF101 is not caused by ignorance. I'm trying to find out the cause for my problem for few days now, but can't find something to catch on. There are many similar problems with TF101 not being recognized by PC, but they all offer solutions which don't work, I don't understand them, or which make no sense.
Let's start at the beginning.
I have gotten my hands on Asus EEE Pad Transformer TF101. It was really cheap. I was told it came form USA.
It's obviously rooted, has a custom rom and recovery (ClockworkMod Recovery v3.2.0.1. roach2010-tf101-r1)
This is waht it says in Settings>About:
Model Number:
Transformer TF101G (although I think it is actually just a Wi-Fi model - TF101, it has no SIM slot)
Android version:
3.2.1
Baseband version:
Unknown
GPS version:
V5.5.8
Wi-Fi version:
V5.2.65
Bluetooth version
v6.24
Kernel version:
2.6.36.4-g6aa10ba
[email protected] #20111023
Build number
HTK75.prime_epad-2.1.0-20111105
Mobile Dock version:
Not available​
It seems to be working fine, except for being totally filled up with apps, bloatware and data. Natural instinct was to install a clean ROM. I wanted to go with CM, and a newer Recovery, but I got stuck on the first step. I can't get it recognized on any of my computers. Both Windows 7 and 8.
However I plug it in, I get; USB device not recognized. One of the USB devices attached to you computer has malfunctioned... This happens when I connect the USB cable when Android is booted up, when in recovery and also in APX mode, providing I have entered it (I'm not really sure because the display is always black).
In Device Manager, I can see only one exclamation icon (I did enable show hidden devices) in Universal Serious Bus Controllers called Unknown Device, which seems to be from the TF101. I tried uninstalling it. Restarting both the tablet and the computers. I tried to manually override those Unknown Device drivers with ASUS Android USB drivers for Windows and Universal_Naked_Driver_0.72 and ventana apx driver, but it wouldn't take any of them. I also tried installing them manually by right clicking on the INF files, and still nothing.
Then I thought I could mount the sdcard or USB mode in recovery, but that wouldn't work either.
Any solutions?
Click to expand...
Click to collapse
Have exhausted all resources all so if you find out anything please pm me. In the mean time I am still looking and I will keep you posted if I find out anything.
philseven said:
Have exhausted all resources all so if you find out anything please pm me. In the mean time I am still looking and I will keep you posted if I find out anything.
Click to expand...
Click to collapse
My guess is a bad USB cable. I had my USB cable stop working for ADB/APX/MTP/PTP but it still works with the Asus wall wart for charging. New USB cable fixed it straight away.
Solution
hi. if you cannot enter apx mode. try flashing a new rom of the tf101 or reflashing your current recovery
Soft brick Asus transformer tf101,None boot stuck\no USB
Hello I'm having the same problem with my tf101 but I can't get windows 7 64bit too load a driver for it, tried them all? Mine is soft bricked and there's no recovery file to restore. getting file not found.
Only shows CMW Based recovery v 5.5.0.4 roach-tf101-r2, also won't see SD card to re flash a rom or recovery.img, seems everywhere I turn I hit a wall on getting it back to working again, just hangs on Asus Logo?
please help? do I need to use a terminal program? is there a way to force a driver to load and see it long enough to reimage?
Thanks tons for any help.:crying:
rmontgo3Denver said:
Hello I'm having the same problem with my tf101 but I can't get windows 7 64bit too load a driver for it, tried them all? Mine is soft bricked and there's no recovery file to restore. getting file not found.
Only shows CMW Based recovery v 5.5.0.4 roach-tf101-r2, also won't see SD card to re flash a rom or recovery.img, seems everywhere I turn I hit a wall on getting it back to working again, just hangs on Asus Logo?
please help? do I need to use a terminal program? is there a way to force a driver to load and see it long enough to reimage?
Thanks tons for any help.:crying:
Click to expand...
Click to collapse
Same problem here... Tried Naked Driver and still got nothing. The Tablet just won't get recognized by the computer (Windows 8.1).
Did you have any luck unbricking it?
I've been through soft bricks before but this time, it seems to me that I've hit the bottom... I just can't think of anything else... any help??
had this problem for 2 years now. started off off like that, now it doesnt recognize at all. if it's rooted, flash a recovery using a terminal emulator. (there are instructions on team win's website on how to flash it to the appropriate block). then, just install a ROM with twrp. mine is in a permaloop. wiping data, rebooting, doing it again. if you get it to work, don't tinker with it any more. that's from my experience.
Sent from my LG-LG870 using Xparent Blue Tapatalk 2
tf101
hi, my asus tf101 has a same issue,my laptop don't recognized my asus,i dont know if the problem is in the cable or what,.i tried already what i saw in youtube but nothing happen.,the sdcard slot is not working,i used cwm v5.8.1.8 touch ,.but i want to change it into original stock version..now ,im working on how my device will recognize...is there a solution to bringback the original recovery base without using computer?..thank you..
---------- Post added at 03:08 PM ---------- Previous post was at 03:04 PM ----------
fabioporto said:
Same problem here... Tried Naked Driver and still got nothing. The Tablet just won't get recognized by the computer (Windows 8.1).
Did you have any luck unbricking it?
I've been through soft bricks before but this time, it seems to me that I've hit the bottom... I just can't think of anything else... any help??
Click to expand...
Click to collapse
got a same issue here,with my asus tf101,i regret to changed my recovery base into cwm touch v5.8.1.8.. it didn't show my ext sdcard file to change it again..i want to bring back the old one..but i don't know how..please please please..need help..
---------- Post added at 03:13 PM ---------- Previous post was at 03:08 PM ----------
James130201 said:
hi. if you cannot enter apx mode. try flashing a new rom of the tf101 or reflashing your current recovery
Click to expand...
Click to collapse
hi sir,..i have the same problem above,.my data cable doesn't work ..the cwm i used now doesn't show my ext sd card,.only clockworkmod file,.is it possible to flash the old rom without computer?..how..please reply ,..thanks,
Don't wanna be the bearer of bad news but, I gave up trying to recover that thing a long time ago buddy. My advise to you would be: let go of it. The way I see it, the only way you could do it would be if you could replace the connection port and regain access to you tablet through you computer - considering the problem is being caused by that port.
Another way of doing that would be if you could actually have access to the tablet's internal storage and then place a ROM there so you could flash that using CWM.
Those are the only two options I didn't try, and now I can't, since I gave mine away to someone I thought could try one of those things, but not even an eager 17 year old boy could do it.
So, good luck with that.

can someone help with allwinner boot loop but i have no recovery

hi guys, i bought an allwinner a13 7" tablet online that is stuck in a boot loop. im new to this stuff but i have tried to get into the recovery by holding vol up + vol down + power like everywhere says to but all i get is a pic of the android symbol down with an exclamination mark coming from his guts. i am led to believe that this means there is no recovery on it. the specs of the tablet are:
model: yeahpad pillbox7
7.0" Capacitive multiTouch Tablet PC Resolution 800 * 480 pixels, 16:9
All Winners A13 Cortex A8 .
CPU Boxchip A13 1.5GHz .
Memory 512MB DDR2 ROM
HARD DISK 4GB
Camera 1.3 Mega Pixels
Wi-Fi 802.11 b/g/n supported 3G External 3G (USB 3G Modem)
supported Card type Micro SD/TF Card (Maximum 32GB supported)
USB/3.5mm Headphone
how do i put a recovery on it in order to reset it to stock, or at least get past the boot loop?
any help is appreciated, thanks in advance
RE
666vi6696 said:
hi guys, i bought an allwinner a13 7" tablet online that is stuck in a boot loop. im new to this stuff but i have tried to get into the recovery by holding vol up + vol down + power like everywhere says to but all i get is a pic of the android symbol down with an exclamination mark coming from his guts. i am led to believe that this means there is no recovery on it. the specs of the tablet are:
model: yeahpad pillbox7
7.0" Capacitive multiTouch Tablet PC Resolution 800 * 480 pixels, 16:9
All Winners A13 Cortex A8 .
CPU Boxchip A13 1.5GHz .
Memory 512MB DDR2 ROM
HARD DISK 4GB
Camera 1.3 Mega Pixels
Wi-Fi 802.11 b/g/n supported 3G External 3G (USB 3G Modem)
supported Card type Micro SD/TF Card (Maximum 32GB supported)
USB/3.5mm Headphone
how do i put a recovery on it in order to reset it to stock, or at least get past the boot loop?
any help is appreciated, thanks in advance
Click to expand...
Click to collapse
Okay, first question is whether or not you are able to access the battery for your device? If so sometimes its as simple as removing the battery and then rebooting after 30-60 seconds. If not you will need the drivers for your device and will need to access the device via adb (there are several good forums on here to explain how to use adb). But you may be able to install a recovery via adb push.
---------- Post added at 07:07 PM ---------- Previous post was at 06:58 PM ----------
So it is possible to do this however you will need to download the android SDK to access adb and find a custom recovery.IMG for your device. Hope this helps you. If you need anything else feel free to ask.
O
android_geek_0507 said:
Okay, first question is whether or not you are able to access the battery for your device? If so sometimes its as simple as removing the battery and then rebooting after 30-60 seconds. If not you will need the drivers for your device and will need to access the device via adb (there are several good forums on here to explain how to use adb). But you may be able to install a recovery via adb push.
---------- Post added at 07:07 PM ---------- Previous post was at 06:58 PM ----------
So it is possible to do this however you will need to download the android SDK to access adb and find a custom recovery.IMG for your device. Hope this helps you. If you need anything else feel free to ask.
O
Click to expand...
Click to collapse
not with ease, the battery is glued to the screen and i risk damaging the screen getting it out.
if i can put a recovery on the tablet i will be ok, my wildfire s was rooted when i purchased it and i have flashed a few different roms on it using the recovery, so that much i can do but i cant find the right recovery for the tablet to factory reset it,
i have never herd of adb, is that a program for P.C? to be honest, im new to putting a recovery on a device, sorry for being such a noob and thanks, if someone can help me find the right IMG i should be able to do the rest, but i cant find the correct IMG
I'll look for a recovery image for you... ADB is the Android Debug Bridge and comes.included in the Android SDK.... Its a way to perform operations on your device via a PC.... There are several very good tutorials on here regarding how to push files and flash ROMs and recoveries via ADB to your device.... If I can find a recovery for your device I will let you know on here
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Samsung Galaxy Tab 2 10.1 Help!!

Hi everyone, I am a new person in the forums, so please understand if I'm not good at some stuff and if I'm posting this in the wrong place
Well, story is that I found my old Galaxy Tab 2 in my basement after 3 years, and I got it to turn on (no factory cable, 1€ chinese cable). Android version is 4.0.3.
Found a couple of roms in the forums for 6.0, and yes, I've done it before on my phones.
Computer cannot recognize the tab, only says "Unrecognized device", even though I've tried every driver there is to it. Tried kies, no help. Tried odin, no help.
Neither of those detect the tab either, so I rooted it from the tab itself with KingRoot.
Now the tab is rooted, and I tried to flash TWRP to install 6.0.
It says that the recovery is flashed, but when I try to reboot to recovery, it only restarts, with nothing.
It goes into download mode just perfectly, but when connected to the pc, it still doesn't detect it.
I do not have money to buy a new tablet, so I would really like some advice.
Thanks!
hello
go in download mod ( power & vol+ )
go back to origin
use cfautoroot (all needed in it odin + drivers + cfautoroot)
use a new cable
after that install twrp, os ( first cm12.1 )
regards
Hi, will try!
Don't set auto reboot in Odin.
Once TWRP is flashed wait 1 minute and unplug the tab.
Now directly boot into TWRP, else stock recovery get restored on boot.
You should update over OTA to 4.1 or 4.2 if available first, else you'll have to flash a newer bootloader using Odin to avoid graphics glitches at boot.
Android-Andi said:
Don't set auto reboot in Odin.
Once TWRP is flashed wait 1 minute and unplug the tab.
Now directly boot into TWRP, else stock recovery get restored on boot.
You should update over OTA to 4.1 or 4.2 if available first, else you'll have to flash a newer bootloader using Odin to avoid graphics glitches at boot.
Click to expand...
Click to collapse
Hi, thanks! Got it working!
It was a very good idea to ask xda for help
Can you tell me how you did it? Where to get origin? I have the same problem - please help.
dionex2k said:
Can you tell me how you did it? Where to get origin? I have the same problem - please help.
Click to expand...
Click to collapse
Read above, lol, he quoted it too
I did.... my computer does not even recognize my tab - I tried 3 different cables and 2 different computers.
Use the driver from here http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Android-Andi said:
Use the driver from here http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Click to expand...
Click to collapse
I installed the drivers from the link you provided - my laptop still does not recognize my tablet... any other suggestions?
dionex2k said:
I installed the drivers from the link you provided - my laptop still does not recognize my tablet... any other suggestions?
Click to expand...
Click to collapse
Tired a different cable? Different usb port?
dionex2k said:
I installed the drivers from the link you provided - my laptop still does not recognize my tablet... any other suggestions?
Click to expand...
Click to collapse
I have heard about a tool called "Forget Windows Use Linux (FWUL)" but I have not tried it. Maybe give it a shot
hello
cfautoroute gives odin, drivers, ...
regards
dionex2k said:
I installed the drivers from the link you provided - my laptop still does not recognize my tablet... any other suggestions?
Click to expand...
Click to collapse
Is your cable a data cable or just a charging cable?
UnavailableSurm said:
Is your cable a data cable or just a charging cable?
Click to expand...
Click to collapse
Yes I tried 3 cables they are for data and charging
---------- Post added at 06:55 PM ---------- Previous post was at 06:53 PM ----------
validatus said:
hello
cfautoroute gives odin, drivers, ...
regards
Click to expand...
Click to collapse
I tried that - did not work.
---------- Post added at 06:55 PM ---------- Previous post was at 06:55 PM ----------
Can someone try and help me via teamviewer? It would make me happy because I really want to use this damn tablet again.

my zu680kl hard brick!!! hlp pls

i install twrp after unlock bootloader , i flashed stock rom but i forgot to wipe system , data before flashed
My device's No Fastboot, No recovery, No Display, hard bricked
i's only vibrate when i press power button
red blink when connect usb cable
anyone has same problem? help me pls..
Same here. But i have yet to find anyone to get it past the black screen.
.
when you try to boot into recovery.. try to. hold the vol up button for a sec after it it should have loaded.. that whats mine was doing.. black screening
Any news? My device also bricked.
Me to, I got stuck in updating firmware process or corrupted firmware file. I'm also stuck with black screen no recovery, Fastboot mode, computer won't recognize device, phone just blinks red notification light when cable plugged in, power button vibration, also looking for fix. The phones only week old, had to buy another one. I'm now stuck with the new device can't get into twrp just presented a black screen when booting into twrp, only way to get into twrp is with adb, fastboot/boot/twrp.Img which sucks really like the device
Same problem, I can't acces to bootloader, fastboot, recovery
it's only vibrate when i press power button and the red led blink when I connect the usb cable
Someone found a solution ?
Roxy34 said:
Same problem, I can't acces to bootloader, fastboot, recovery
it's only vibrate when i press power button and the red led blink when I connect the usb cable
Someone found a solution ?
Click to expand...
Click to collapse
I've been working on a similiar issue on a ZU680KL for a friend of mine for a few months now. I ended up buying a USB-C type of an EDL cable. I am able to get some software's to better recognize the phone now including Xiaomi's MiFlash, and have found variations of the files that QPST wants when trying it as a solution, but the raw flash programmer file's I have found, though for right chipset, or probably intended for other devices are the partition tables for example would all be different. This whole project to me as I just recently described it, feels like trying to glue a shattered light bulb back together using liquid glue like the kind they use to have us use in Elementary school on paper projects, and to make it more fun, every time you look away, someone's throwing away more and more of the puzzle pieces on us. lol. Frustrating as all hell. It's as if Asus never wanted or intended for us to restore these phones from an EDL or low level NVRAM status. Wish I had the exact answer. Plan to waste a few hours of today on it again though, being how I found this thread researching it some more. Good luck to all.
solved? I have easy way to fix
regards
grean said:
solved? I have easy way to fix
regards
Click to expand...
Click to collapse
what's easy way to fix? thanks^_^
If you watch YouTube videos, you find virtually nothing. There is one Portugese video, but they never show the phone in a completely dead state of black screen with a couple vibrations & an occasional blinking light. This state is truly bricked. There are a couple fake videos also, wanting you to just look at stuff, but it's just a stupid ad. We have one working Zenfone 3 ultra, & one seriously did one. I've offered 100's of $$ to anyone to bring it back to life, & have received ZERO takers. Anybody who's not insane can understand what that means. In other words, so far, forget it. No one has been able to unbrick this model. Only the other Asus models. This Asus model has relatively few purchasers - & has even fewer people willing to mess with it. What a shame.
.
Hello, if someone has a working zu680kl device we could extract the necessary image and fix it using this tutorial:
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
I think it looks very promising.
I also have a bricked zu680kl device and I don't think about to give it up !!!!
We have a working one, but my better ½ is not about to give it up for an experiment.
.
hillg001 said:
We have a working one, but my better ½ is not about to give it up for an experiment.
.
Click to expand...
Click to collapse
I think there is no risk to brick the device because there will be no installation of any kind of firmware at all. The only thing is to make a backup of all app data because a fresh clean device (factory reset) is necessary. If you like to have a look at the whole procedure search for
Guide, if you are NEW “Qualcomm HS-USB QDLoader 9008” MODE
on the mentioned page
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
If it would be possible to get the eMMC image I would try to go through the rest of the process. Maybe this brings back our dead devices to life.
Buy your better 1/2 some flowers before you ask
I managed to get it fixed tonight
I did the following steps:
1) Enable Qualcomm HS-USB QDLoader 9008 mode with help of an diy EDL cable.
2) Download the zu680kl raw firmware from here - was not easy to find : http://vietmobile.vn/threads/file-raw-asus-zu680kl-asus-zenfone-3-ultra-zu680kl.46825.html
3) Flash the raw firmware with QFIL
4) Reinstall the stock firmware with fastboot and adb sideload
5) Thank God for help !!!
luckychild said:
I managed to get it fixed tonight
I did the following steps:
1) Enable Qualcomm HS-USB QDLoader 9008 mode with help of an diy EDL cable.
2) Download the zu680kl raw firmware from here - was not easy to find : http://vietmobile.vn/threads/file-raw-asus-zu680kl-asus-zenfone-3-ultra-zu680kl.46825.html
3) Flash the raw firmware with QFIL
4) Reinstall the stock firmware with fastboot and adb sideload
5) Thank God for help !!!
Click to expand...
Click to collapse
Hey what files do you use with the qfil out that raw firmware package or do you just flash the whole raw zip
gubbilo144 said:
Hey what files do you use with the qfil out that raw firmware package or do you just flash the whole raw zip
Click to expand...
Click to collapse
I am not sure - but I think Qfil needs to be set as a Flat Build - not Meta - using files:
Code:
Programmer Path = prog_emmc_firehose_8976_lite.mbn
Download Raw Program = rawprogram0.xml
Download Patch = patch0.xml
Now -- When I try this - I still get an error:
Code:
Download Fail:Sahara Fail:QSaharaServer Fail:The Directory name is invalid
Does anyone get past this at all???
---------- Post added at 10:54 AM ---------- Previous post was at 10:37 AM ----------
deadmatrix said:
Now -- When I try this - I still get an error:
Code:
Download Fail:Sahara Fail:QSaharaServer Fail:The Directory name is invalid
Does anyone get past this at all???
Click to expand...
Click to collapse
Success!
Just solved my own issue - must use a much newer version of Qfil! I was successful with version 2.0.1.7 - I had to install it as opposed to downloading a zipped exe and running from an extraction point.
I downloaded my copy from https://www.androidbrick.com/downloads/
Just scroll down a little and watch for it manually.
Will update as I get further!
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
I can confirm luckychild's success. After six months of nothing but a black screen and a flashing red led and some occasional vibrations - I have restored my friend's ZU680KL that she mailed to me half a year ago. And I have made it to a stock Android desktop.
After you flashing using qfil per my prior post - you will still have a black screen - reboot to see Asus - In search of Incredible come up - rejoice - It'll go straight to the bootloader - from there - you want to run "ftm-flashall.cmd" from the zip you downloaded from the Portuguese website luckychild linked too already. Once it runs, your good to go. Continue on with his instructions. All credit to luckychild for putting the pieces together.
deadmatrix said:
I am not sure - but I think Qfil needs to be set as a Flat Build - not Meta - using files:
Code:
Programmer Path = prog_emmc_firehose_8976_lite.mbn
Download Raw Program = rawprogram0.xml
Download Patch = patch0.xml
Now -- When I try this - I still get an error:
Code:
Download Fail:Sahara Fail:QSaharaServer Fail:The Directory name is invalid
Does anyone get past this at all???
---------- Post added at 10:54 AM ---------- Previous post was at 10:37 AM ----------
Success!
Just solved my own issue - must use a much newer version of Qfil! I was successful with version 2.0.1.7 - I had to install it as opposed to downloading a zipped exe and running from an extraction point.
I downloaded my copy from https://www.androidbrick.com/downloads/
Just scroll down a little and watch for it manually.
Will update as I get further!
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
I can confirm luckychild's success. After six months of nothing but a black screen and a flashing red led and some occasional vibrations - I have restored my friend's ZU680KL that she mailed to me half a year ago. And I have made it to a stock Android desktop.
After you flashing using qfil per my prior post - you will still have a black screen - reboot to see Asus - In search of Incredible come up - rejoice - It'll go straight to the bootloader - from there - you want to run "ftm-flashall.cmd" from the zip you downloaded from the Portuguese website luckychild linked too already. Once it runs, your good to go. Continue on with his instructions. All credit to luckychild for putting the pieces together.
Click to expand...
Click to collapse
Good just got my edl cable in the mail, going try to fix my Asus zenfone 3 ultra that's been in my dresser for 6 months bricked.
---------- Post added at 03:45 PM ---------- Previous post was at 03:24 PM ----------
deadmatrix said:
I am not sure - but I think Qfil needs to be set as a Flat Build - not Meta - using files:
Code:
Programmer Path = prog_emmc_firehose_8976_lite.mbn
Download Raw Program = rawprogram0.xml
Download Patch = patch0.xml
Now -- When I try this - I still get an error:
Code:
Download Fail:Sahara Fail:QSaharaServer Fail:The Directory name is invalid
Does anyone get past this at all???
---------- Post added at 10:54 AM ---------- Previous post was at 10:37 AM ----------
Success!
Just solved my own issue - must use a much newer version of Qfil! I was successful with version 2.0.1.7 - I had to install it as opposed to downloading a zipped exe and running from an extraction point.
I downloaded my copy from https://www.androidbrick.com/downloads/
Just scroll down a little and watch for it manually.
Will update as I get further!
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
I can confirm luckychild's success. After six months of nothing but a black screen and a flashing red led and some occasional vibrations - I have restored my friend's ZU680KL that she mailed to me half a year ago. And I have made it to a stock Android desktop.
After you flashing using qfil per my prior post - you will still have a black screen - reboot to see Asus - In search of Incredible come up - rejoice - It'll go straight to the bootloader - from there - you want to run "ftm-flashall.cmd" from the zip you downloaded from the Portuguese website luckychild linked too already. Once it runs, your good to go. Continue on with his instructions. All credit to luckychild for putting the pieces together.
Click to expand...
Click to collapse
Were do run the ftm-flashall.cmd in qfil or adb
gubbilo144 said:
Good just got my edl cable in the mail, going try to fix my Asus zenfone 3 ultra that's been in my dresser for 6 months bricked.
---------- Post added at 03:45 PM ---------- Previous post was at 03:24 PM ----------
Were do run the ftm-flashall.cmd in qfil or adb
Click to expand...
Click to collapse
Run it from a command prompt window. So like at a DOS Prompt. Nothing to do with ADB.
---------- Post added at 01:17 PM ---------- Previous post was at 01:12 PM ----------
After running the command - it'll boot up to a custom Qualcomm rom - it will have no Gapps of any kind on it. That's why we still need to sideload the rom from Asus's website that you can download from them. I have trouble sideloading over here - not sure why. I have to put it onto a microSD card to flash it from the phone's recovery. Also - Don't forget to wipe data and factory reset it before booting up post of the sideloading. Otherwise it'll possibly get stuck trying to optimize apps - it froze on 'Android is Starting' for me and when I power cycled manually - it corrupted the UI. Had to go back and run the ftm-flashall.bat again.
Just realized the ftm-flashall.cmd that i listed earlier - is a typo - the propper file name should end in a .bat I believe. Sorry for the mistake. Not enough Coffee.
deadmatrix said:
Run it from a command prompt window. So like at a DOS Prompt. Nothing to do with ADB.
---------- Post added at 01:17 PM ---------- Previous post was at 01:12 PM ----------
After running the command - it'll boot up to a custom Qualcomm rom - it will have no Gapps of any kind on it. That's why we still need to sideload the rom from Asus's website that you can download from them. I have trouble sideloading over here - not sure why. I have to put it onto a microSD card to flash it from the phone's recovery. Also - Don't forget to wipe data and factory reset it before booting up post of the sideloading. Otherwise it'll possibly get stuck trying to optimize apps - it froze on 'Android is Starting' for me and when I power cycled manually - it corrupted the UI. Had to go back and run the ftm-flashall.bat again.
Just realized the ftm-flashall.cmd that i listed earlier - is a typo - the propper file name should end in a .bat I believe. Sorry for the mistake. Not enough Coffee.
Click to expand...
Click to collapse
i got it thanks so much guys im updating in recovery now,my asus zenfone 3 ultra paperweight is back alive
gubbilo144 said:
i got it thanks so much guys im updating in recovery now,my asus zenfone 3 ultra paperweight is back alive
Click to expand...
Click to collapse
Glad to hear it! So we have a now reproducable cure after years of nothing in the pipe really. I am thinking of writing a start to finish post of how to deal with it for beginners that can be pinned by a mod. If someone else wants to beat me to this, feel free - especially since I don't actually even own this model of phone.. Might maybe pick it up though.

x96 mini - solid red light, undetectable.. Help please.

Purchased new box and was stuck on x96 mini page from start. I pressed pin and powered back up (without sd card in box) to try and get to menu to just simply reboot it but solid red light came on without me even getting to menu that I know of. I have tried all methods found in these forums. For grounding out pins I read that some people successful after trying different pins then in posts but they not post pins they used, may be helpful to others if they did. I don't think world cup drivers works for Windows 10, or I need help making them work as I tried connecting a working box to usb burning tool and was also not recognized but windows itself recognized. Windows does not recognise my bricked box. Any help would be greatly appreciated.
coyotecal said:
Purchased new box and was stuck on x96 mini page from start. I pressed pin and powered back up (without sd card in box) to try and get to menu to just simply reboot it but solid red light came on without me even getting to menu that I know of. I have tried all methods found in these forums. For grounding out pins I read that some people successful after trying different pins then in posts but they not post pins they used, may be helpful to others if they did. I don't think world cup drivers works for Windows 10, or I need help making them work as I tried connecting a working box to usb burning tool and was also not recognized but windows itself recognized. Windows does not recognise my bricked box. Any help would be greatly appreciated.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=fsyS3p5asZs&list=LLxxDotaUFh_I_kB85QpA6Gw&index=2&t=0s
Neekapp said:
https://www.youtube.com/watch?v=fsyS3p5asZs&list=LLxxDotaUFh_I_kB85QpA6Gw&index=2&t=0s
Click to expand...
Click to collapse
That is for x96, not x96 mini...different board.
coyotecal said:
That is for x96, not x96 mini...different board.
Click to expand...
Click to collapse
Just have a look at this:
https://blog.danman.eu/bricking-and-unbricking-vontar-x96-mini/
hi. was this ever solved? were you able to fix your x96 mini?
@claishem
https://blog.danman.eu/bricking-and-unbricking-vontar-x96-mini/
It will Unbrick your X96mini
zusatzmetall said:
@claishem
https://blog.danman.eu/bricking-and-...ntar-x96-mini/
It will Unbrick your X96mini
---------- Post added at 10:25 AM ---------- Previous post was at 10:25 AM ----------
[/COLOR @claishem
https://blog.danman.eu/bricking-and-...ntar-x96-mini/
It will Unbrick your X96mini
Click to expand...
Click to collapse
this is what appears in the link you provided sir
https://blog.danman.eu/bricking-and-unbricking-vontar-x96-mini/
zusatzmetall said:
@claishem
https://blog.danman.eu/bricking-and-...ntar-x96-mini/
It will Unbrick your X96mini
Click to expand...
Click to collapse
@zusatzmetall
or you are referring to the shorting of pins sir?
but i have seen a lot of reports here and and in other forums that they still were not able to fix their x96 minis even if they did the tutorial of danman. any idea?
Trust me, it works
zusatzmetall said:
Trust me, it works
Click to expand...
Click to collapse
thanks for the assurance sir. i really hope so. i had a mibox 3 last year. it also uses amlogic processor, s905x. i was able to play with its os for a few months until i bricked it while trying to downgrade it succesfuly from oreo despite of the warning not to do it. because mibox has this kind of like anti rollback protection that would render your device paperweight if you downgrade. there was one expert also from vietnam named Nguyen Van Dai if you are also familiar with him, who was the author of the modified bootloader of mibox to be able to safely downgrade from Nougat to marshmallow. but when i tried his modified oreo bootloader i bricked my mibox and that's the end of the box.
anyway, what is important to me now is a sure answer if this x96 mini can be revived regardless of anykind of software brick.
---------- Post added at 04:30 PM ---------- Previous post was at 03:47 PM ----------
zusatzmetall said:
Trust me, it works
Click to expand...
Click to collapse
by the way sir, have you already encountered yourself that red light only problem and then you were able to resolve using the method of danman? most or all of those who are saying that danman method does not work for them are those whose boxes only show red light..
It works!!!
So guys. I found a new way to recover our bricked X96 Minis. So I bricked mine with a wrong FW. I had inly red light, no reset through AV switch, no magic SD card, Computer doesn t recognized usw.
First of all: I have a X96 mini with Amilogic S905W CPU, 2/16. My PCB version is x96 Mini Q6X v 2.2 17355 and I have memory from Samsung. They call it k4b4g0446q.
So the method:
1. Short the two point.
2. Connect USB Kabel to PC. Wait until the computer recognize the box.
3. Remove shortcut, connect AC adapter to the box.
4. Flash enjoy
I used a laptop with Windows 7 64 bit and USB Burning tool 2.2.0. The USB 3 kabel is one meter long. I flashed simply an android 9 FW from web.
Q6X v2.3 1/8GB X96 mini
Hi,
Do you have any clues for Q6x v2.3 board X96 mini 1/8gb board? I tried as card flash but after 2s afters flashing started the box turn off itself and of i try to connect box to pc, windows says usb device not recognised and goes to coonect/disconnect loop.
Eh nevermind, i changed usb cable. Pc recognised it, flashed. But sometime freeze itself :/
Kuontol tenan juancokkk frimware tipu led red mulu asuuu juanccokkk anjing wedhuss
Hello,
I had exactly the same problem on my x96mini.
You must have a cable that turns on the red led without the charger, my first cable did not do it I had to change it.
I connect the cable to my pc.
Took out the motherboard, I turned it over.
With a metal object I rubbed it on all the welds (by despair)
By magic I saw Connect succes posted on Burning tool.
Good luck if you have this problem
claishem said:
this is what appears in the link you provided sir
Click to expand...
Click to collapse
I have x88 pro stuck on red light not recognized by pc or tv any help please
I have X96 mini with Q6X V2.3 18186 16/2GB board. I flashed a new firmware in it and it was working fine for one day then it suddenly stopped and now when i plug it in red light stays solid for few seconds then start blinking, it in not turning on or detected by computer. How to fix this.

Categories

Resources