[Q] Trio Stealth G2 - Android Q&A, Help & Troubleshooting

Hey,
Tried as hard as I could not to have to ask, looked everywhere I could think of, searched through dozens of threads and found nothing in regards to my Trio Stealth G2 tablet.
My question is, what method of rooting should I use for my tablet, and once I do root would there be a custom ROM I could use?
I've seen people mention they messed up flashing a custom ROM to the Stealth Pro 7, but I'm not sure if any ROM made for a 7" Cortex A9 tablet would work. Don't want to brick this though so thought I wouldn't chance it.
Thanks

I got the other day an I am to wanting to root it I think bin4ry root method would work but adb won't work cause there's no fastboot on the thing it dose have a recovery but its 3e
Sent from my G2 using xda premium

I think I got some progress today while its pluged into ur computer press pwr+vol- to get off of battery charging screen then hold them till u here ur computer make the sound like something got pluged in an ur tablet will be under m3-chipset in device manager search the internet for aml flash tool I have got it to connect to my pc
Sent from my G2 using xda premium

Not gonna use aml flash tools cause I can't find any good info on it found a safe mode on the thing today an got root with bin4ry to finally pick up the device its using adb still no root cant get a backup made with it an adb in cmd won't pick it up I know the tab has it tho I found the adb file on it after looking forever View attachment 2107849
{
"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"
}
Sent from my G2 using xda premium

here is a method that might work for you
go to my thread: forum.xda-developers.com/showthread.php?p=44294370#post44294370
I would post it here but i would just take up alot of posting space writing it down..the way i did it worked for me and believe me i was going for hours trying to find someway to root my trio stealth g2 until i found out how lmao let me know how it goes

U really got root on it
Sent from my G2 using xda premium

Yeah I did i have it rooted now with the play store mod
Sent from my G2 using xda app-developers app

Trio Stealth G2
Just got this tablet today. I was able to root it using the One Click Root and it has rooted it properly so it would seem so far.

slick97477 said:
Just got this tablet today. I was able to root it using the One Click Root and it has rooted it properly so it would seem so far.
Click to expand...
Click to collapse
Hi, slick97477. Where did you get the One Click Root tool? I didn't see any forums for this (or any other Trio) device on here.
Thank you in advance.

http://forum.xda-developers.com/showthread.php?t=1734365

One click
I got it from here
just google oneclickroot
and just run it. Couldn't believe it worked but it did.
However today went to try and turn it on and nothing, Just hung and the Trio logo. Let it sit for about 10 minutes. Decided maybe battery was dead and plugged it in still nothing. No battery logo nothing. Hit reset button and plugged it in again and nothing. Screen doesnt come on now nothing but however weird thing is it shows up as winusb now under devices which is amlogic driver for flashing firmware which im not sure how this has happened but it has. I have took it apart and took pics of the mainboard and cpu. Would like to see if perhaps there is firmware out for this...Have done quite a bit of research and numerous different things so far..
I have downloaded the firmware installer from amlogic but so far no firmware seems to like my cpu....Hmmm well cannot upload pictures yet for some reason..If anybody is interested in trying to help me figure out which firmware will work on it I would greatly appreciate it. I used it the night before and it worked great. Have not installed anything new or anything so I am a bit baffled in how the firmware got torched but I am pretty sure that is what has happened any ideas I am willing to try. I have recently dived into really messing with the android devices but had not done anything with this tablet yet because I had not found a way to back up the current firmware on it...so was really being nice to it for now....
(Edit) Pics are included just didn't try hard enough

try this
Yea id like to help try turning it on while its pluged in ur computer then hold the power button till u here the sound like something got pluged in ur computer then then hit the power button to turn it on if this dosnt work try turning it on then after the @9 boot logo hold both volume keys that should put it in safe mode only the apps that came on the tab will work

Trio Stealth g2 tablet issues
Hi I was reading your posts about the g2 and I seem to be having a similar issue. The tablet is frozen on the trio stealth g2 loading screen and I have pushed all the buttons including the reset button on back to no success. I got the tablet to recognize as m3 chip on my pc and was able to aml flash tool but every time I try to upload a rom like stock jellybean or some custom rom its asking for a upgrade config file which of course I do not have there has to be a way to just completley wipe this tablet and install a new os any ideas on how I can get this thing to flash, I was hoping I could load a sd card and push some buttons on the tablet to flash from the sd card but I have no clue if thats possible

Stealth G2 9.7"
damncheaptablets said:
Hi I was reading your posts about the g2 and I seem to be having a similar issue. The tablet is frozen on the trio stealth g2 loading screen and I have pushed all the buttons including the reset button on back to no success. I got the tablet to recognize as m3 chip on my pc and was able to aml flash tool but every time I try to upload a rom like stock jellybean or some custom rom its asking for a upgrade config file which of course I do not have there has to be a way to just completley wipe this tablet and install a new os any ideas on how I can get this thing to flash, I was hoping I could load a sd card and push some buttons on the tablet to flash from the sd card but I have no clue if thats possible
Click to expand...
Click to collapse
I too have a g2 with the same issue but i've gotten it into ADB Recovery. When using the AML Flash tool, after you import the upgrade file and it asks you to manually input a config file use the config_progress.xml file that is in the AML flash installation directory possibly under \resource\
This is what got me to ADB recovery but anytime I try to reboot the tablet it reverts back to Worldcup Device in device manager so I'm stuck. Hope this helps.

Issue
spurloc said:
I too have a g2 with the same issue but i've gotten it into ADB Recovery. When using the AML Flash tool, after you import the upgrade file and it asks you to manually input a config file use the config_progress.xml file that is in the AML flash installation directory possibly under \resource\
This is what got me to ADB recovery but anytime I try to reboot the tablet it reverts back to Worldcup Device in device manager so I'm stuck. Hope this helps.
Click to expand...
Click to collapse
Hey I was able to flash the tabley with aml but I used novo 7 fire and now nothing comes up, no boot screen or anything, however when its plugged into my pc I can access the internal storage and Micro sd card storage, but I need to remove the rom and get one that works correctly for the tablet, unlike before It wont let me push the power and vol button to make it go to the m3 chip which then I could use the aml world cup driver so some how I have to flash it from the internal storage or by some means but I have no clue at this point. The driver is Portable media player MID Novo7 I changed the driver to android ADB which it installs but then I cant access the internal storage, is there anyway to re flash this? I tried pushing diffrent buttons on the tablet to see if a diffrent chip is recongized like the m3 was from before but nothing

damncheaptablets said:
I tried pushing diffrent buttons on the tablet to see if a diffrent chip is recongized like the m3 was from before but nothing
Click to expand...
Click to collapse
From my experience with the stealth g2 9.7" if you open up the tablet and use a pin or small screwdriver to short (connect) nand pins 7 & 8 (counting down from top right of chip, yours maybe 5 & 6 or 6 & 7 ) as seen in picture below the circled area, while powering the unit on, should erase the nand and revert to Worldcup device in device manager which will allow the AML flash tool to see the device again.
Image -- freaktab(.)com/attachment.php?attachmentid=3068&d=1377544440

Umm ur awesome
spurloc said:
From my experience with the stealth g2 9.7" if you open up the tablet and use a pin or small screwdriver to short (connect) nand pins 7 & 8 (counting down from top right of chip, yours maybe 5 & 6 or 6 & 7 ) as seen in picture below the circled area, while powering the unit on, should erase the nand and revert to Worldcup device in device manager which will allow the AML flash tool to see the device again.
Image -- freaktab(.)com/attachment.php?attachmentid=3068&d=1377544440
Click to expand...
Click to collapse
Thanks alot, I opened my tablet, found the tf boot and it worked, now if I can just get the right firmware installed

damncheaptablets said:
Thanks alot, I opened my tablet, found the tf boot and it worked, now if I can just get the right firmware installed
Click to expand...
Click to collapse
Nice! Glad it worked. At this point we're in the same boat. I'm not sure how to properly flash a new firmware even though i've got an identical working one. It seem's I've tried everything and the closest i've gotten is just getting the screen to light up blank, which hasn't happened in a long while now. I used the instructions in the PDF file below except i replaced the bootloader.img, boot.img & recovery.img files from a backup I made, ran heroflash.bat and rebooted the device and now the screen comes on blank. Not sure where to go from here though. I'll keep trying
Instructions - PDF Link
svet-tabletu(.)cz/podpora/Ainol_Novo_10_Hero/ENG_NOVO10HERO_Unbrick_Instruction_0_4_RC.pdf
package link
mediafire(.)com/download/nq0ppsle1t662ht/AML_USB_Unbrick_AINOL_HERO_10.rar

Yeah im stuck now
spurloc said:
Nice! Glad it worked. At this point we're in the same boat. I'm not sure how to properly flash a new firmware even though i've got an identical working one. It seem's I've tried everything and the closest i've gotten is just getting the screen to light up blank, which hasn't happened in a long while now. I used the instructions in the PDF file below except i replaced the bootloader.img, boot.img & recovery.img files from a backup I made, ran heroflash.bat and rebooted the device and now the screen comes on blank. Not sure where to go from here though. I'll keep trying
Instructions - PDF Link
svet-tabletu(.)cz/podpora/Ainol_Novo_10_Hero/ENG_NOVO10HERO_Unbrick_Instruction_0_4_RC.pdf
package link
mediafire(.)com/download/nq0ppsle1t662ht/AML_USB_Unbrick_AINOL_HERO_10.rar
Click to expand...
Click to collapse
Yeah I tried to flash 40D_resque.zip with aml and I would either get W/ Import upgrade file C:\Users\Jy\Desktop\_USB-Burning-Tool\resources
\40D_resque.zip
W/ [P2][19:41:11]Loading spl ...
W/ [P2][19:41:12]Transfer Complete! total size is 18556 Bytes
E/ [P2][19:41:13]Spl code,identy(-1)
E/ [P2][19:41:13]Load uboot failed 1 times
E/ [P2][19:41:14]Spl code,identy(-1)
E/ [P2][19:41:14]Load uboot failed 2 times
E/ [P2][19:41:15]Spl code,identy(-1)
E/ [P2][19:41:15]Load uboot failed 3 times
E/ [P2][19:41:16]Spl code,identy(-1)
E/ [P2][19:41:16]Load uboot failed 4 times
E/ [P2][19:41:16]Load uboot failed 3 times, retry from 0 step
W/ [P2][19:41:17]Loading spl ...
W/ [P2][19:41:17]before loadSpl, identify return -1
and have to use a screwdriver to reboot it in m6 chip, before I was able to get about 80% with flash but then got a boot error about unable to find device and at that time the tablet would change device name from the worldcup driver to portable media device with a drive letter like H:/ but I couldnt access it, man this is making me

damncheaptablets said:
Yeah I tried to flash 40D_resque.zip with aml and I would either get W/ Import upgrade file C:\Users\Jy\Desktop\_USB-Burning-Tool\resources
E/ [P2][19:41:16]Spl code,identy(-1)
E/ [P2][19:41:16]Load uboot failed 4 times
E/ [P2][19:41:16]Load uboot failed 3 times, retry from 0 step
W/ [P2][19:41:17]Loading spl ...
W/ [P2][19:41:17]before loadSpl, identify return -1
and have to use a screwdriver to reboot it in m6 chip, before I was able to get about 80% with flash but then got a boot error about unable to find device and at that time the tablet would change device name from the worldcup driver to portable media device with a drive letter like H:/ but I couldnt access it, man this is making me
Click to expand...
Click to collapse
It looks like there's an issue with that specific u-boot.bin (u-boot-orig.bin) within that package. Although the fact that it shows up in device manager as Portable device means that part of it was written by the flash utility. Have you tried force-ably replacing the drivers from portable device to android adb drivers. This might allow you to access the adb recovery mode.
Alternatively if ADB doesnt show any devices after replacing the drivers, you might want to uninstall the adb drivers that didnt work, once it appears as portable device again, the tablet might be looking for its new firmware on the sdcard. Check out the page in the link and follow the instructions for "Method One - SD Card Method for a "soft" brick". It involves restoring a factory image onto the sdcard using a handy tool "USB Image tool" and then rebooting. It might kick in an update from the sd.
link --
slatedroid(.)com/topic/41478-how-to-unbrick-your-amlogic-aml8726-mx-series-tablet-v20/
Also I could upload the aml flash files that are getting me into adb recovery mode every time

Related

Asus Zenfone C bootloop

I tried to flash latest rom from Asus website to my new Zenfone C because it had a weird issue, it came the user interface in taiwanesse, but when trying to change to english, it stayed in taiwanesse, so I wasnt able to setup it in first place.
Then, it came to my mind to flash the latest rom, and I used this guide in absence of a Zenfone C guide for flashing:
http://en.zenfoneasus.com/zenfone-recovering-returning-stock-rom-downgrade-clean-update-guide/
I did all the steps listed there first, and then tried the steps but with the red marked steps, flashing the dnx and ifwi also, no result.
The problem is that now im stuck in a bootloop, and cant advance from there, the Asus logo stays there forever.
What happened during flashing is this:
When I sideloaded the update.zip containing latest rom from Asus website, it said:
-Installing update
-Device image SKU: ww
OTA image SKU: WW
and suddenly after that it restarted, showed a huge Intel Inside logo that I never saw and then went to the dead android image. After waiting a while, the phone restarts, this time only showing the Asus logo with the Intel Inside logo beneath it (not the Intel Inside logo only that I mentioned earlier), and stays there forever.
I dont know what else to do, I dont know if Im doing something wrong.
Were you ever able to fix the problem?
No, until now, no
Sent from my Nexus 5 using Tapatalk
Solved!!!
Hey Spartan!
I was searching online about nexus 5 to buy one but I found something else randomly in an Indonesian blog and was able fix my phone! Hardly took about 15 minutes
I will be posting the solution soon... I hope you are still in need?
kkdevta said:
Hey Spartan!
I was searching online about nexus 5 to buy one but I found something else randomly in an Indonesian blog and was able fix my phone! Hardly took about 15 minutes
I will be posting the solution soon... I hope you are still in need?
Click to expand...
Click to collapse
I still need the fix man, I will really appreciate the posting of the solution! thanks in advance!
Sent from my Nexus 5 using Tapatalk
The Fix!
First Download: -
USB Drivers: http://www.asus.com/in/Phones/ZenFone_C_ZC451CG/HelpDesk_Download/
Asus Flash Tool v1.0.0.11: https://drive.google.com/file/d/0B7cZB2l2IKlKMENKUWlVaHJ3ZHM/view
Signed Rom zip image: https://drive.google.com/file/d/0B__oiYlSY-brdHFWMy1OWXNrajg/view
The Process: -
Get your phone to boot into fastboot mode by pressing [vol -] button and power button simultaneously for few seconds.
Connect to your PC and install USB drivers if not done already. The phone should show up as an "ASUS Android Composite ADB Interface" in the Device Manager.
Now, open ASUS Flash Tool :-
{
"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"
}
It should detect your phone with serial number and blue orb in front of it.
Select your phone model i.e. ZC451CG
Choose if you want to wipe data or not. I chose "Wipe Data" since I had everything backedup on asus web storage.
Click that box icon and browse for the signed zip image file you downloaded earlier.
Select your device on the ASUS flash Tool by clicking on the serial number like shown in the picture below.
( It had me scratch my head after one failed attempt because I didn't select it the first time! :silly
Click on the green start button, be patient, stay calm and cross your fingers. This could take 10-20minutes or so.:fingers-crossed:
If everything went well your phone should bootup to the welcome screen like the day 1 you got it.
Now, the zip image is quite old so after the initial setup the phone would prompt you with lots of system and app updates. Go with it and enjoy! :victory:
Lastly, don't be shy of pressing that " :good:Thanks! " button if this post helped you.
Thanks man, I will try tonight. Do you know if this works under Windows 8.1 64bits??. I see the screenshots are from windows 7.
Spartan Legionnaire said:
Thanks man, I will try tonight. Do you know if this works under Windows 8.1 64bits??. I see the screenshots are from windows 7.
Click to expand...
Click to collapse
Hopefully it should, I did it on a Windows 7 Professional 64 bit machine.
The USB drivers you download has Windows 8 drivers in it. I think that's all that is needed.
Yeah, I will try it then, and report back, thanks again.
Sent from my Nexus 5 using Tapatalk
kkdevta said:
First Download: -
USB Drivers: http://www.asus.com/in/Phones/ZenFone_C_ZC451CG/HelpDesk_Download/
Asus Flash Tool v1.0.0.11: https://drive.google.com/file/d/0B7cZB2l2IKlKMENKUWlVaHJ3ZHM/view
Signed Rom zip image: https://drive.google.com/file/d/0B__oiYlSY-brdHFWMy1OWXNrajg/view
The Process: -
Get your phone to boot into fastboot mode by pressing [vol -] button and power button simultaneously for few seconds.
Connect to your PC and install USB drivers if not done already. The phone should show up as an "ASUS Android Composite ADB Interface" in the Device Manager.
Now, open ASUS Flash Tool :-
It should detect your phone with serial number and blue orb in front of it.
Select your phone model i.e. ZC451CG
Choose if you want to wipe data or not. I chose "Wipe Data" since I had everything backedup on asus web storage.
Click that box icon and browse for the signed zip image file you downloaded earlier.
Select your device on the ASUS flash Tool by clicking on the serial number like shown in the picture below.
( It had me scratch my head after one failed attempt because I didn't select it the first time! :silly
Click on the green start button, be patient, stay calm and cross your fingers. This could take 10-20minutes or so.:fingers-crossed:
If everything went well your phone should bootup to the welcome screen like the day 1 you got it.
Now, the zip image is quite old so after the initial setup the phone would prompt you with lots of system and app updates. Go with it and enjoy! :victory:
Lastly, don't be shy of pressing that " :good:Thanks! " button if this post helped you.
Click to expand...
Click to collapse
IT WORKEEEED!!!! I dont know how to thank you man!. Thank you so much, I was going to give up on this device!. Its working really well.
The only thing I came into trouble, was to install the USB drivers included in the Asus Flash Tool. I did the following (on Windows 8.1 64bits):
I disabled driver signature check first on windows.
I went to the USB drivers folder inside the ASUS Flash tool folder on Program Files.
I went here C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller\devcon\x64
On that folder, there is a program called devcon.exe, right click on it, and select properties.
On compatibility tab select Run as Administrator, click ok.
After this, reinstall USB drivers by going to C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller and here execute install_drivers.bat
Thats it, the phone now should be recognized by the Asus Flash Tool.
I always failed when downloading Signed Rom zip image.. Someone please provide mirror... Thanks
Tjecing said:
I always failed when downloading Signed Rom zip image.. Someone please provide mirror... Thanks
Click to expand...
Click to collapse
Use a download manager like "free download manager" or something. I am on a slow network to re-upload it else where.
kkdevta said:
Use a download manager like "free download manager" or something. I am on a slow network to re-upload it else where.
Click to expand...
Click to collapse
I don't know how to thank You.. But thanks a lot you safe my days..
Can any one plz give me the link of any custom recovery for asus zenfone c.....i badly need it plz help me...thnks in advance.....plz give me..and tell me how to flash it.....
do you know where i can find the correct .raw file for asus zenfone 5 A501CG ? i use lollipop, i dont know if that's matter =s
Anyone help me When I press volume- and power, it can't enter to fastboot. And when I plug the cable, the flash tool can't detect it
Sent from my Mi 4i using XDA Free mobile app
hello brother...can you help me...
my zenfone 5 a500cg has been softrick and bootloop to...
if i'm turn on my phone
logo asus and then usb logo and then dead again...
i can't log into fastboot(power on+vol up)..
but i can log into cwm philz...
i try flash via adb sideload but always error bla bla bla tmp/updated.zip
if i try other ROM always like this ( please upgrade to image 4.3 first)
i try xftsk but always windriver error( i am use notebook win7)
i try asus flashtool with .raw zip rom but my serial number error just 12345678abcdef...
if i click start always device not detect...
help me bro
disappear3896 said:
Anyone help me When I press volume- and power, it can't enter to fastboot. And when I plug the cable, the flash tool can't detect it
Click to expand...
Click to collapse
power and volume up (+)
Spartan Legionnaire said:
IT WORKEEEED!!!! I dont know how to thank you man!. Thank you so much, I was going to give up on this device!. Its working really well.
The only thing I came into trouble, was to install the USB drivers included in the Asus Flash Tool. I did the following (on Windows 8.1 64bits):
I disabled driver signature check first on windows.
I went to the USB drivers folder inside the ASUS Flash tool folder on Program Files.
I went here C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller\devcon\x64
On that folder, there is a program called devcon.exe, right click on it, and select properties.
On compatibility tab select Run as Administrator, click ok.
After this, reinstall USB drivers by going to C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller and here execute install_drivers.bat
Thats it, the phone now should be recognized by the Asus Flash Tool.
Click to expand...
Click to collapse
First and foremost, follow Spartan about how to deal with the driver install error. Read above. Second, those are the links for the raw images:
ww_A500CG_3.23.40.60_20150630.raw and many other phones. It was posted by thanhthuy. 500CG Lollipop: https://mega.nz/#!jwBDUKzJ!x3VD9VJrMe0CBs353DVnXlHr2dHQXepjcqtrR0gQDdU
500CG kitkat:
https://mega.co.nz/#!H8YkyLba!4Ye52JKAjzogGRVvCx2r9XoJIhou_uY3z6YH1xBges8
400CG 6.6.3 - https://mega.co.nz/#!HoRRnLCL!CV-iCMEUgRd_LwDc4QgNkevxKIGOKtFGDYrytt59EVE
400CG 7.3.3 - https://mega.co.nz/#!G8hRwYqR!Eu_l6r_6QSbhjID-MtYQU3v0q0voQ0GYkFeayy-3MFI
451CG: https://mega.co.nz/#!794U1TpT!rermqclZOpPKcYZY8z2YezUkQE-MWjYJgqyKMUAjYDo
600cg Kitkat: https://mega.co.nz/#!S1wlnYhC!doCPvf7ukeEFStcJPgqaEViE5oiHb_hpGSGnIh3n1IQ
Here for 600cg lollipop: https://mega.co.nz/#!3p4wBQAY!KUx26zaGdCBU6CGa4g68zT_iX9NxmIQCUvHiolfa_Oo
ZE550ML Lollipop 40.23 : https://mega.co.nz/#!HgBSySZA!EOxpsmPvHgCfl-9jUVRAv624Uq9LG4uvxuN83j6-P-k
ZE550ML Lollipop 40.40: https://mega.co.nz/#!P4RmXIwb!-xrDe8AYXdprZgUG4Ehs8fLNHhrdKpXdmaV3FBWPC_0
ZE551ML Lollipop: https://mega.co.nz/#!i4JRAQDR!9DzxtSd1oxDuCV6oc0rEhm-1sF4SA-94YPG9fLVw_lw
Source using Google cache (Vietnamese): http://webcache.googleusercontent.com/search?q=cache:w5AS-N1JrAoJ:zenphoneviet.com/threads/all-zen-stock-rom-firmware-kk-l-update-hang-tuan-chay-bang-asus-flash-tool.7066/+&cd=1
---------- Post added at 07:31 AM ---------- Previous post was at 07:29 AM ----------
Those raw files are extremely difficult to find so if you pretend to have any of those phones i recommend to download. It works easily if you have fastboot. If you only have adb i did not saw working but i am trying.
---------- Post added at 07:38 AM ---------- Previous post was at 07:31 AM ----------
If you try to do that under adb they give a serial number mistake.
4 days trying to solve this bootloop using adb. At least one person here saved his phone with the raw links i found using google webcache in this vietnamese link so it was worth it. Looks like i will need to lose 40 days sending to Asus in Sao Paulo. What a hell folks, those asus firmwares are really crap. Set a great hardware for set poor software.
why my phone does not give any reaction when press power button+vol
I had same problem but different situation....I tried to make an experiment by changing systemui and I had done it with a wrong step .lucky I make a backup and tried to recover it.
But Things get worst when it failed to backupbang now my phone get stuck to Asus logo.I tried to follow the method that your all give in this thread but I can go to fastbootode with it must press power button+col down button.
CAN ANYBODY HELP ME WITH THIS PROBLEM
Sorry for my bad English
And I'm a newbie and try to learn something from pro

Lenovo Tab a10-30 bricked or fixable?

Hello everyone,
I will share my experience with you, and I hope for a solution!
A few days ago I rooted my Lenovo tab 2 A10-30 successfully using Kingroot. Then, I tried to change Kinguser with SuperSU, which I also successfully did. However, I noticed that although the main root app was SuperSU, Kingroot was still on my phone, so I deleted it using a bloatware removal app and restarted the tablet. Now it won't turn on. It gets stuck at the Lenovo loading screen, and that's about it. When I press the power button + volume down button, it gets me to a Chinese menu that is not the recovery mode (there is no MMC, just options about voloume, colors, mic test etc). If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
I tried flashing the stock ROM using the Smart Phone Flash Tool, but the PC does not recognize fully the tablet (it just prompts me to install the Lenovo USB drivers, and I cannot access the tablet's internal storage). Moreover, the Lenovo windows applications do not recognize the tablet when I connect it to the PC.
I really do hope that there is a way I can fix it.. Thank you all in advance.
Hi,
I did almost exactly the same... Kingroot, tried to remove bloatware with another app, and ended up with a bricked tablet I can still access the bootloader, but flashing the tablet from there is to no avail.
I am still looking for the original ROM, which seems nowhere to be found. Did you, by any chance, make a backup first?
Another one here But I'am able to go into recovery and into adb sideload, from there I can view internal memory(/system). And it looks like system is trying to load supersu-daemon which was removed and it can't get past that. I tried to recover paths (to original ones), but it still wont go past loading screen. (it is just restarting the app_process32).
Now if we only could get the hold on original factory firmware... from there one we can sideload it via fastboot.
And for the drivers you need andorid usb drivers https://developer.android.com/studio/run/win-usb.html#top
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
So, I have spent about 5 hours attempting to find a way to dump the firmware without first rooting the device, so that I could share it with you guys (and have a backup for myself in case I attempt to root it myself.) Unfortunately it seems like it needs to be rooted before I can create a nandroid backup through adb. Unfortunately the tablet is not based on mtk, and I cannot find any qualcomm utils that can dump the firmware.
The one Qualcomm util I found (QFIL) seems like it is only for flashing, and for backing up some individual data for the tablet (I assume it may contain such as license keys for the commercial features in the recent phones such as Sony Xperia Z3). I also looked into fastboot, and that too can only flash a new firmware.
So, unless the tablet gets rooted I don't see any way to make a proper backup.
I am unable to post links in messages, so you need to do some manual editing.
dz0ny said:
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
Click to expand...
Click to collapse
This however seems like very valuable information, unfortunately the only places I can find that has this available for download is charging money for access to the file.
50$ at dlgsm,com www DOT dlgsm DOT com/register.php?file=TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip&dir=%2FFLASH-FILES%2FLENOVO%2FT_Series%2FTB2-X30F
or from 10$ at pars-hamrah,com: www DOT pars-hamrah DOT com/%D8%A7%D8%AE%D8%A8%D8%A7%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D8%A7%D8%AE%D8%AA%D8%B5%D8%A7%D8%B5%DB%8C-%D9%BE%D8%A7%D8%B1%D8%B3-%D9%87%D9%85%D8%B1%D8%A7%D9%87/38027-%D8%B1%D8%A7%D9%85-%D8%A7%D9%88%D8%B1%D8%AC%DB%8C%D9%86%D8%A7%D9%84-%D9%84%D9%86%D9%88%D9%88-lenovo-tb2-x30f-%D9%86%D8%B3%D8%AE%D9%87-s000015-%D8%A7%D9%86%D8%AF%D8%B1%D9%88%DB%8C%D8%AF-5-1-1-%D8%AF%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D9%82%D8%B1%D8%A7%D8%B1-%DA%AF%D8%B1%D9%81%D8%AA.html"]Here[/URL]
It might also be available www DOT fars-gsm DOT com/75531-tb2-x30f_usr_s000015_1601151950_q8009_row_qpst-zip.html, at least they list the changelog for the firmware.
Since I have no use for a firmware right now, I will not be buying access to one (unless I at some point manage to brick mine as well). But if anyone decides to do so, please share it so others can enjoy it as well. I also suspect that if the file was available, it would increase the probability of someone attempting to make a custom rom at some point as well, it is a very cheap tablet when on sale, so it should have good potential for a community.
PS: I also stumbled over something called vRoot, that might be an alternative to Kingroot, although I have no idea whether it is as good at rooting and not installing unwanted extra apps. I guess someone who has used it on a tablet/phone that has a backup available might be able to shed some light on that.
---------- Post added at 08:08 PM ---------- Previous post was at 08:02 PM ----------
omrtpsycho said:
If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
Click to expand...
Click to collapse
This is the QFIL (Qualcomm Flash something system) mode, however I do now know whether that helps anything at all. Since it seems to me it probably wont accept the TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip file mentioned in the thread. It seems to expect some xml file, maybe the zip file contains that?
Hi guys i have been strugling with this unit The last 3 days. I have eksakt same problem. I found these files: lenovo-forums.ru/files/category/106-прошивки-lenovo-tab-2-a10-30/
I extracted Them but dont know how to flash Them ?? Hope u guys Can help (sorry for bad english)
To Download files from Lenovo-forums.ru i logged in with my Google account
[PUT ROM TEMPORARILY HERE: https://www.wetransfer.com/download...024ee2974a44f8aa50e3dcd120160615184237/a84735 ]
Wow, suddenly action! With the help of Dead2 and Andersbp I have made some progress. Here are my steps:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
The smaller one is simply an update, which you could install easily:
1) boot into Recovery Mode
2) select "Apply Update from ADB"
3) run: adb sideload TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip
Which works... UNLESS YOU ROOTED THE DEVICE. Then it fails, and does not want to update. Thanks Lenovo
So, the larger one is a different type of ROM. This one will not load with adb sideload (gives footprint and signature error). But it DOES contain all the files to flash with QFIL (Qualcomm Flash something system).
Here I'm stuck. I followed this guide:
http://guidebelajar.blogspot.nl/2016/03/guide-how-to-flash-firmware-lenovo-vibe-p1.html
and tried to install these packages:
1) You must download and install USB Driver for Lenovo on your windows computer or PC.
2) QPST-2.7.422-qfil-qcom-Upgrade-Tool-20140422
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Furthermore, the site suggests to install something on the device itself:
5) Create a folder with the name sdfuse in the root of the SD-card phone
6) Put the qsb-firmware (file with the extension .qsb) in the folder sdfuse.
Here I have 2 problems: First, my device does not boot, so I cannot create/copy files. Seconly: I cannot find qsb-firmware.qsb anywhere...
@ Dead2: How did you go through these steps?
Zwartoog said:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
Click to expand...
Click to collapse
Great, thanks for sharing the firmware, I hope you and everyone else with a softbricked tablet can get it fixed now
I am sure some of those would be willing to donate a couple of bucks to you if they get theirs working again.
Zwartoog said:
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Click to expand...
Click to collapse
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
I got the driver package from here: www DOT teamandroiders DOT com/lenovo-usb-drivers-download/
Zwartoog said:
@ Dead2: How did you go through these steps?
Click to expand...
Click to collapse
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
I will assist in any way I can, but I will not attempt flashing my own tablet until I actually need to
Dead2 said:
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
Click to expand...
Click to collapse
We'll get this working
Dead2 said:
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
Click to expand...
Click to collapse
I tried that one too, but to no avail When I try to execute the executable, it ask for administrator permission, and after that vanishes...
I am running Windows 8, 64 bit. You?
Other question: when is your tablet recognised by Windows? Also in Recovery Mode?
Thanks!
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Andersbp said:
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Click to expand...
Click to collapse
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Zwartoog said:
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Click to expand...
Click to collapse
Sure Will try tomorrow
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
{
"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"
}
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Click to expand...
Click to collapse
Super! Will try this tonight. Just in case: which Windows version are you using?
Zwartoog said:
Super! Will try this tonight. Just in case: which Windows version are you using?
Click to expand...
Click to collapse
I use windows 10
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
Click to expand...
Click to collapse
Great work! I am glad I was able to help you guys get this fixed
Andersbp said:
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Click to expand...
Click to collapse
Yep, its at the bottom of my first post also, found that out by accident while trying to get into the normal recovery.
Now, hopefully someone will want to port TWRP and CM13 or Paranoid to this tablet
Doh i did not see that Dead2
Thanks everybody together we defeated the problem !
SUPER! Succes here as well! The trick was indeed to hold both vol UP and DOWN
Now: brand-new unrooted device
Thanks
Btw: I noticed that the rom from Andersbp is a TB2-X30L rather than the TB2-X30F. I used my F file (paid for it, dammit ), and that one also works well.
I am currently checking if I can modify the stock ROM to enable root / mult-user. Any hints?
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Andersbp said:
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Click to expand...
Click to collapse
Noo, no Kingroot. That's where all the disasters began. It is full of bloatware. Trying to uninstall Kingroot lead to bricking the device
Personally I am only interested in re-enabling the multi-user feature from lollipop. WHICH IS FOR SOME REASON DISABLED BY LENOVO Even when rooted and modifying the system/build.prop did not re-enable it.
I'm giving up now. At least I have a workable device. Restored pride. And more important: 3 happy kids
I think the TB2-X30L is the LTE version of the tablet, while the TB2-X30F is the wifi-only version. If correct, then there should be no problem
when using the LTE on a non-LTE model, but the other way around could potentially cause LTE to not work. The LTE firmware might have some
extra apps and settings enabled to cater to this ability, but it might also be completely identical. Btw, what does the model information say
after being flashed with the L firmware? In any case it is useful to know that they are cross-compatible, since sometimes there can be differences
in chipsets or screens that can cause minor or major problems.
As I mentioned earlier, another root alternative to kingroot seems to be vRoot, but I have not tried it myself. But now that it is possible to
recover a bricked tablet, it is also less risky to test such things.
BTW: Please remember to use the "Thanks!" button on posts you find helpful, I have tried to do so myself on the posts that I find helpful

(Help) Mi-box stuck/bricked - MDZ-16-AB

Need some help with my mi box (MDZ-16-AB) as somehow it got bricked.
Background:
A while ago I tried to connect my Bluetooth headset, connection process froze and I had to hard reboot (plug out/in power). After starting up, the box die not proceed further than the initial MI logo screen (think its the first screen altogether).
I tried already to flash diverse OTA files via recovery, to which I got access, but all ended up having similar error messages as the one attached (Can't mount/open catch etc.).
I am versed in flashing roms etc. and kind of remember seeing those messages when the file system got corrupted, hence my fear that I can't fix the box at all. To my knowledge, there is still no full rom img for the MDZ-16-AB version released!?
Anyone here with further advice?
Screenshot
chrismast said:
Need some help with my mi box (MDZ-16-AB) as somehow it got bricked.
Background:
A while ago I tried to connect my Bluetooth headset, connection process froze and I had to hard reboot (plug out/in power). After starting up, the box die not proceed further than the initial MI logo screen (think its the first screen altogether).
I tried already to flash diverse OTA files via recovery, to which I got access, but all ended up having similar error messages as the one attached (Can't mount/open catch etc.).
I am versed in flashing roms etc. and kind of remember seeing those messages when the file system got corrupted, hence my fear that I can't fix the box at all. To my knowledge, there is still no full rom img for the MDZ-16-AB version released!?
Anyone here with further advice?
Screenshot
Click to expand...
Click to collapse
try a different flash drive, formatted as FAT32
try formatting drive in a different computer
try anothe power supply i had a bootloop problem with my mibox and i replaced the power supply with one i had for a psp and is working now no more reboot or bootloop at all.
maybe is not same problem but you can try
brigantti said:
try anothe power supply i had a bootloop problem with my mibox and i replaced the power supply with one i had for a psp and is working now no more reboot or bootloop at all.
maybe is not same problem but you can try
Click to expand...
Click to collapse
tried that as well with my new mibox power supply, same result though.
bigtalker said:
try a different flash drive, formatted as FAT32
try formatting drive in a different computer
Click to expand...
Click to collapse
tried that, did not help
Found a guy with a similar issue on Reddit but he had also no luck...
I went thru 4 different flash drives until it relented to flash
If you cannot resolve this issue PM me and if your happy to send your device for testing/recovery purposes you can send it to me, if i recover you can have it back, i simply need it for debugging as the one someone already sent had a wipes emmc
I've got similar problem.
I have mdz-16-ab, international version, with 1st Oreo build installed (2167). Full stock, no root access, etc. Suddenly the device stopped booting properly, during boot it displays rotating Android logo for ~5 minutes following by black screen afterwards. I managed to launch recovery, did wipes and tried to flash any of the 3 available Oreo builds to the moment being written to 2 various flash drives I possess (1 gb and 16 Gb, FAT16 and FAT32 formatted accordingly). Every attempt resulted in "Failed to verify whole-file signature" error.
Looks like it could not properly read image file from the flash drive or the image itself is wrong for this model but I'm perfectly sure image is correct.
sergeyouknw said:
I've got similar problem.
I have mdz-16-ab, international version, with 1st Oreo build installed (2167). Full stock, no root access, etc. Suddenly the device stopped booting properly, during boot it displays rotating Android logo for ~5 minutes following by black screen afterwards. I managed to launch recovery, did wipes and tried to flash any of the 3 available Oreo builds to the moment being written to 2 various flash drives I possess (1 gb and 16 Gb, FAT16 and FAT32 formatted accordingly). Every attempt resulted in "Failed to verify whole-file signature" error.
Looks like it could not properly read image file from the flash drive or the image itself is wrong for this model but I'm perfectly sure image is correct.
Click to expand...
Click to collapse
Sounds like you have a flaky USB thumb drive. Try formatting on a different pc and keep trying different usb drives. Current world record holder tried 8 different drives until succeeding with #9!!
Concur with bigtalker. Or a bad download. I followed a procedure that was a cross between https://www.reddit.com/r/AndroidTV/comments/9fo34b/xiaomi_mdz16ab_solution_to_downgrade_from_flaky/ and https://www.reddit.com/r/AndroidTV/comments/97rvqg/mi_box_stuck_in_recovery_mode/e4ct7n0/:
Extracted the 2167 7zip file to a clean 2GB thumb drive (FAT32)
Booted MiBox into recovery and did a data wipe/reset
Shut down the MiBox and inserted thumb drive
Booted MiBox into recovery, again, where it automatically picked up and installed the 2167 update
Shut down the MiBox
Cleared the thumb drive, copied the 2179 .zip over to it as update.zip and restored the xiaomi_update file (from the 2167 7zip file)
Rebooted the MiBox into recovery again. It picked-up and installed the 2179 update
Booted the MiBox into Android and did a Factory Reset
Did minimal new setup configuration on boot and installed the 2396 OTA update
Done!
Just went to update the 2nd of our two MiBox 3's. The light lights but nothing on-screen at all. It's bricked but good. I guess turning off Google Play Services wasn't enough.
Now trying to find a receipt to see if I can persuade Walmart to take it back. It's probably been too long, but it's worth a shot. I have to go back to return the now-unnecessary 2nd IR remote, anyway.
Good job, Xiaomi. You suck
{
"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"
}
I will never buy another Xiaomi product again. Ever. You could not give me a Xiaomi product.
jseymour said:
Just went to update the 2nd of our two MiBox 3's. The light lights but nothing on-screen at all. It's bricked but good. I guess turning off Google Play Services wasn't enough.
Now trying to find a receipt to see if I can persuade Walmart to take it back. It's probably been too long, but it's worth a shot. I have to go back to return the now-unnecessary 2nd IR remote, anyway.
Good job, Xiaomi. You suck
I will never buy another Xiaomi product again. Ever. You could not give me a Xiaomi product.
Click to expand...
Click to collapse
Sorry to hear of your travail...
Did you update 2nd box via OTA or using manual steps as in reddit post?
What version did you start from on box #2?
bigtalker said:
Sorry to hear of your travail...
Click to expand...
Click to collapse
Thanks. I'm not as annoyed as I might otherwise have been, being as I was more-or-less expecting it'd happen eventually. *shrug*
bigtalker said:
Did you update 2nd box via OTA or using manual steps as in reddit post?
What version did you start from on box #2?
Click to expand...
Click to collapse
Each of the two boxes bricked themselves, or Xiaomi bricked them for me, with absolutely no intervention from me whatsoever. Box #1 was bricked to its splash screen. That one I recovered with the aforementioned procedure. Box #2 was bricked to completely dead except its front-panel indicator.
They had both been on the same versions. I don't recall which that was at the time they were bricked. The 1st or 2nd update Xiaomi pushed out for Oreo. IIRC: 2179 created as many problems as it solved, so I didn't apply that OTA when it was available. So perhaps the one before that?
There are reports of Xiaomi MiBox 3's "bricking themselves" on every on-line forum in which I participate, BT. Some to their splash screens. Some to just dead. Just like I experienced. These all started appearing about the time 2396 became available.
hi i have an IMG for MDZ-16-AB to get unbrick
https://drive.google.com/drive/folders/1-fGnIP7iLmpHUNRPhlWyEnEVHuraDc1q?usp=sharing
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
roeer said:
hi i have an IMG for MDZ-16-AB to get unbrick
https://drive.google.com/drive/folders/1-fGnIP7iLmpHUNRPhlWyEnEVHuraDc1q?usp=sharing
Click to expand...
Click to collapse
i got brick after trying to update to version 9. and the device freeze. and now i flash this img and get out of brick. after this img burend. enter to recovery and install version 9 with this link:
https://4pda.ru/pages/go/?u=https:/...c055db0b4f8dee8d49e4b04ecf9100.zip&e=65311772
What is the AndroidTV version of the img file you posted
What is the AndroidTV version of the update.zip file you posted
Curious as to the origin of the img file. Normally such things come from the hardware vendor. Xiaomi has not been forthcoming with img files, mainly staying with flashable zip format updates
hum..
I Use USB_Burning_Tool 2.0.7 and it say Low-Power after 1' ... :'( after, crash burn...
roeer said:
hi i have an IMG for MDZ-16-AB to get unbrick
https://drive.google.com/drive/folders/1-fGnIP7iLmpHUNRPhlWyEnEVHuraDc1q?usp=sharing
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
i got brick after trying to update to version 9. and the device freeze. and now i flash this img and get out of brick. after this img burend. enter to recovery and install version 9 with this link:
https://android.googleapis.com/pack.../2c49569c61c055db0b4f8dee8d49e4b04ecf9100.zip
Click to expand...
Click to collapse
Thank you sooo much! You saved many once working devices from the landfill.
I got it to work following the instructions posted here:
https://forum.xda-developers.com/an...ogic/s905x-xiaomi-mi-box-3-mdz-16-aa-t3502992
Edit: Download for latest USB Burning Tool v2.2.0:
https://mega.nz/file/Hd0CmACT#OPws8xFAPOGR6SmFJKfkVQ4SXjXpetJHmZZZ7nqkRHc
Note: you will need a USB Male to Male cable (2.0 is fine) which can be found for ~$5.
Ex: https://www.amazon.com/dp/B009GUXG92/
The MDZ-16-AB is almost the same as the AA except the pins are a bit more to the right:
For the image burning tool, DO NOT ERASE ALL. Uncheck Erase bootloader and keep it to 'Normal erase', this is to keep DRM keys which allows Netflix to work.
The image linked above works flawlessly!
The image is of Oreo version 2167
Once back in recovery, I was in a recovery loop. To fix this I followed the instructions posted here:
https://www.reddit.com/r/AndroidTV/comments/97rvqg/mi_box_stuck_in_recovery_mode/e4ct7n0/
After that I was able to update to Oreo version 2562 posted above.
I then followed the same procedure to manual update to Android 9 and it succeeded.
Captured the link for MDZ-16-AB Android 9 r2926 for anyone who wants to try manual updating as well:
https://android.googleapis.com/pack.../ed5bdb6aefb2bb6ee3f46a9f4d46026b9df88159.zip
@criscodecookies: I also tried flashing my bricked MDZ-16-AB. However, I'm also getting the low power error. With only the usb connected the device is not detected by the tool when shorting the two pads. Did you connect the power cable?
Thanks in advance
Hitchar said:
@criscodecookies: I also tried flashing my bricked MDZ-16-AB. However, I'm also getting the low power error. With only the usb connected the device is not detected by the tool when shorting the two pads. Did you connect the power cable?
Thanks in advance
Click to expand...
Click to collapse
Yes, power cable must be connected while shorting the two pads. Once USB Burning Tool sees the device you may then let go of shorting the pads but keep power connected.
criscodecookies said:
Yes, power cable must be connected while shorting the two pads. Once USB Burning Tool sees the device you may then let go of shorting the pads but keep power connected.
Click to expand...
Click to collapse
Yeah that seems to work. The USB Burning Tool sees the device and I can start the flash. But after a minute I get the error 'low_voltage'. I've tried all my USB ports (USB2 and USB3) and also tried to use my laptop. So now I'm wondering whether my cable is good (I've soldered it myself). I've tested for continuity so the connections are good. How are the cables inside your USB cable wired?
criscodecookies said:
Thank you sooo much! You saved many once working devices from the landfill.
I got it to work following the instructions posted here:
https://forum.xda-developers.com/an...ogic/s905x-xiaomi-mi-box-3-mdz-16-aa-t3502992
Note: you will need a USB Male to Male cable (2.0 is fine) which can be found for ~$5.
Ex: https://www.amazon.com/dp/B009GUXG92/
The MDZ-16-AB is almost the same as the AA except the pins are a bit more to the right:
For the image burning tool, DO NOT ERASE ALL. Uncheck Erase bootloader and keep it to 'Normal erase', this is to keep DRM keys which allows Netflix to work.
The image linked above works flawlessly!
The image is of Oreo version 2167
Once back in recovery, I was in a recovery loop. To fix this I followed the instructions posted here:
https://www.reddit.com/r/AndroidTV/comments/97rvqg/mi_box_stuck_in_recovery_mode/e4ct7n0/
After that I was able to update to Oreo version 2562 posted above.
I then followed the same procedure to manual update to Android 9 and it succeeded.
Captured the link for MDZ-16-AB Android 9 r2926 for anyone who wants to try manual updating as well:
https://android.googleapis.com/pack.../ed5bdb6aefb2bb6ee3f46a9f4d46026b9df88159.zip
Click to expand...
Click to collapse
i've tryed to flash this oero img16-ab on my bricked mi box 3 mdz 16-ab and the usb burning tool all the time showing me error
low power with this img but when i try to flash any other rom dont showing this error only with this rom, whats the problem?

S905X3 + X96 Max Plus + CoreELEC = very strange troubles. Help?

Hi, I'm having these issues with this box. It was intended to be a small media server, but in trying different things I'm stuck and I'd appreciate it if anyone could help me. These AmLogic boxes are quite similar so any idea is more than welcome.
This is an S905X3 based box with 4GB RAM.
CoreELEC has been installed onto eMMC using their "ceemmc" tool. CoreELEC runs just fine.
Device is now unable to boot Armbian from either SD card nor USB.
Can't restore stock firmware: Burn Card Maker throws an error when writing SD card. Also, manually created SD card gives a black screen.
Can't access recovery. Almost sure RESET button isn't doing anything.
Windows can't detect when connected via male-to-male USB cable: do I need to short pins?
Any way to force recovery mode by shorting pins?
Thanks
Hi, I found this thread while looking for some info on how I could unbrick my X96 Max+.
It has bricked because of the Bl301 injection on CoreELEC and just like you, I can't access recovery and I don't know on which pins I should apply a short-circuit.
If someone knows which pins are the ones to short circuit, that would be much appreciated. Here are two pics of the X96 Max+ PCB:
{
"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"
}
I have higher resolution versions if necessary but I cannot post outside links at the moment.
Cheers.
After bottles my device is the same, nothing works anymore you have found a solution please write thank you
I evntually found out which pin to short thanks to mAtvXk on freaktab.
Please note that this is for the 4/64 version.
The 2/16 is a bit different, here is the pic posted by mAtvXk:
Hope this helps.
ludotaku said:
I evntually found out which pin to short thanks to mAtvXk on freaktab.
Please note that this is for the 4/64 version.
The 2/16 is a bit different, here is the pic posted by mAtvXk:
Hope this helps.
Click to expand...
Click to collapse
Is there a pattern for connection before you short the pins. I'm using USB burning tool, holding button in av port with USB connected then shorting the pins. Still no connection
leefreeman said:
Is there a pattern for connection before you short the pins. I'm using USB burning tool, holding button in av port with USB connected then shorting the pins. Still no connection
Click to expand...
Click to collapse
I didn't manage to make it work with USB Burning Tool. I burned a card with Burn Card Maker then I plugged the AC and HDMI cables with the SD card in the slot, did the short, waited for a few minutes (the screen was black during sometime) and then, the device was as new.
It was the bootloader that was broken on my device so it allowed me to restore it to its initial state.
My solution
ludotaku said:
I didn't manage to make it work with USB Burning Tool...
Click to expand...
Click to collapse
leefreeman said:
Is there a pattern for connection...n
Click to expand...
Click to collapse
ergun37 said:
After bottles my device is the same...
Click to expand...
Click to collapse
I should have posted an update here as soon as I got it resolved but I completely forgot and for that I apologise. :fingers-crossed:
Anyway, I went online and downloaded as many ROM images (aka "firmwares", .img files) for this box as I could find. I then wrote each onto MicroSDs as normal and booted the box with the card in. Eventually one of them worked and after a few minutes I was looking at the original box's AndroidTV skin.
HOWEVER... Although USB Image Tool copies data from these .img files onto cards I don't think it actually formats the card before it does, but just erases all the files instead. It seemed to only work for me after I formatted the card first with a small tool called SD Card Formatter from Tuxera and then used USB Image Tool. I hope this helps anyone.
On a side note: I went to CoreELEC's forum to ask for help and there were a couple of people who were more interested in ranting and giving me lectures than actually helping me. One guy did try and help me but now I'm not sure his suggestions actually helped. You can read the whole exchange here.
with my x96 max plus nothing goes no display allas dark with tv no life picture
ergun37 said:
with my x96 max plus nothing goes no display allas dark with tv no life picture
Click to expand...
Click to collapse
me too. nothing happen when i did short pin, there is no sign that my box would be restored again
iSlaker said:
I should have posted an update here as soon as I got it resolved but I completely forgot and for that I apologise. :fingers-crossed:
Anyway, I went online and downloaded as many ROM images (aka "firmwares", .img files) for this box as I could find. I then wrote each onto MicroSDs as normal and booted the box with the card in. Eventually one of them worked and after a few minutes I was looking at the original box's AndroidTV skin.
HOWEVER... Although USB Image Tool copies data from these .img files onto cards I don't think it actually formats the card before it does, but just erases all the files instead. It seemed to only work for me after I formatted the card first with a small tool called SD Card Formatter from Tuxera and then used USB Image Tool. I hope this helps anyone.
On a side note: I went to CoreELEC's forum to ask for help and there were a couple of people who were more interested in ranting and giving me lectures than actually helping me. One guy did try and help me but now I'm not sure his suggestions actually helped. You can read the whole exchange here.[/URL]
Click to expand...
Click to collapse
did you have 3 files in the card after burned ? or more files ? because i already burned my card, only 3 files there. and there is no response from my box, already short the pin to the ground. nothing happened
Hi ISlakar
having some odd issues with my x96max+ also. i have been unable to get CE on it at all. the box simply will not boot from the SD, infact it wouldn't even boot in to stock rom with the SD inserted, just got stuck at the x96 splash screen (but if i insert after stock is booted i see the SD and CE partition) my reset button appeared to be either broken, or disabled as it has no effect, does not even restart the box. i figured it may be disabled by firmware intentionaly or due to a bug so i tried some custom roms. non worked initially and no longer (or so i thought) was recognised by the AMlogic burning tool. the box appeared bricked however i noticed by chance that after around 4 minutes, it would suddenly ' connect' in the flash tool on my PC and teh clock would light up, and the box would stay connected in the flash tool. i tried same as you - many ROMS, none of the generic s905x3 roms will boot the box, and niether will the 'stock' x96 Max + roms i downloaded (various releases from last year and this). I found i can get the box to boot using slimbox ROMS for x96 AIR p1, p2 and V2. It does not run well with them though and hangs oftern for a few seconds, and still no way to get CE on with re-set button still seemingly broken or disabled. i treid 'reboot update' from terminal emulator but still no CE, it just seems to boot in to the boot loader, i dont get any CE splash screen. ive had loads of cheap boxes before and always have been able to get a decent ROM in them, and then get CE going from SD, but this one has me perplexed...
what ROM did you find that worked on you X96 Max+ ?
Thanks!!
thecubasekid said:
Hi ISlakar
having some odd issues with my x96max+ also. i have been unable to get CE on it at all. the box simply will not boot from the SD, infact it wouldn't even boot in to stock rom with the SD inserted, just got stuck at the x96 splash screen (but if i insert after stock is booted i see the SD and CE partition) my reset button appeared to be either broken, or disabled as it has no effect, does not even restart the box. i figured it may be disabled by firmware intentionaly or due to a bug so i tried some custom roms. non worked initially and no longer (or so i thought) was recognised by the AMlogic burning tool. the box appeared bricked however i noticed by chance that after around 4 minutes, it would suddenly ' connect' in the flash tool on my PC and teh clock would light up, and the box would stay connected in the flash tool. i tried same as you - many ROMS, none of the generic s905x3 roms will boot the box, and niether will the 'stock' x96 Max + roms i downloaded (various releases from last year and this). I found i can get the box to boot using slimbox ROMS for x96 AIR p1, p2 and V2. It does not run well with them though and hangs oftern for a few seconds, and still no way to get CE on with re-set button still seemingly broken or disabled. i treid 'reboot update' from terminal emulator but still no CE, it just seems to boot in to the boot loader, i dont get any CE splash screen. ive had loads of cheap boxes before and always have been able to get a decent ROM in them, and then get CE going from SD, but this one has me perplexed...
what ROM did you find that worked on you X96 Max+ ?
Thanks!!
Click to expand...
Click to collapse
Hey,
It's been a while since I touched this box. Once I got it back working on the original firmware I just threw it in a drawer and decided to wait until some linux based ROM came along as I knew I did not want to use CoreELEC. Their forum is not a very welcoming place.
Did you read my last post above? I think there's something about the way the card is formatted. It only worked once I used this specific tool to format the card BEFORE using USB ImageTool. I don't remember how many files ended up in the card but I still have the .img file. See if it helps.
If you do go down the CoreELEC route and pop in their forums DO NOT mention you installed or even tried to install anything on it other than CoreELEC. They can be a bit nazi-ish about their beloved software.
aml_upgrade_package.img
drive.google.com
[/QUOTE]
[/QUOTE]
Hi,
I have this box too, /q5x3_141 v4.0 20112/
I tried to update the android on it, and got trouble.
The box not starting if I plug in the power.
I have to plug in, and wait about 5 minutes and automatic turn it on, without I touch anything.
But it freeze on the boot loader pic. /clock working/
I tried reinstall rom with pc, same, it not turning on, I have to wait and turn it on itself.
Not help reset, not help that 2 small pin short circuit connect.
Only start itself.
But I can install different rom /I tried 3 different -original 20200901 , nexon x8 q 10 aosp v222, some x96max plus which is not the original/
All of them problem is the same, I have to wait about 5 minutes to start the device, and the boot picture freeze, but clock working /clock first show booting, after clock start as a clock/
I tried different power adapter, different hdmi, different tv, same problem.
Do you have any idea?
----SOLVED-----
This rom fix all the problems.
Now I see, what was the problem.
I bought 4/32 , and it shows on the roriginal system 4/32 version /in the storage I see 25Gb free space/
But in real it is a 2/16 version. And when I updated it updated with 4/32 and crashed the system.
Now with this rom I see the real storage which is 11Gb free, and 2Gb ram
I hope it helps, if somebody walking in my shoes.
hello, I have the same problem, but my box is 2gb / 16gb X96Max + Q5X3_141, I even found their original firmware, which I'm leaving here for you, but I need someone to help me, where can I find the pins for short circuit of the 2gb / 16gb version. below I leave the links to download for both versions:
x96max+ 2gb/16gb: https://mega.nz/file/jlg32KgA#7dVg-5EI9t37YzC4IzDfHiO5bR7tPVzA62c3IRXfohk
x96max+ 4gb/32/64 https://mega.nz/file/P0hzBaiS#8K3DJmhU8OwP8mSCxhW7TcsnCHwDwXFixZVxWjo1G5w
rogerioca said:
hello, I have the same problem, but my box is 2gb / 16gb X96Max + Q5X3_141, I even found their original firmware, which I'm leaving here for you, but I need someone to help me, where can I find the pins for short circuit of the 2gb / 16gb version. below I leave the links to download for both versions:
x96max+ 2gb/16gb: https://mega.nz/file/jlg32KgA#7dVg-5EI9t37YzC4IzDfHiO5bR7tPVzA62c3IRXfohk
x96max+ 4gb/32/64 https://mega.nz/file/P0hzBaiS#8K3DJmhU8OwP8mSCxhW7TcsnCHwDwXFixZVxWjo1G5w
Click to expand...
Click to collapse
I discovered the secret, patience is everything, no need to short circuit, just open the USB BURNING TOOL choose the firmware file and START, then put the hdmi cable, hold the boot recovery pin and connect the usb cable to the pc, release the pin and wait about 5 minutes and it will start to update, mine I discovered by accident, due to the fact that I forgot the cable connected in this way. I hope it helps,
sorry for the english, i'm using google translator
Guys, I strongly discourage opening the box and shorting pins unless 1) you know what you're doing; and 2) you have tried ALL other avenues. Before you go opening the box, please try as many ROMs as possible (there have been two ROMs posted in this thread so far, afaik), also try special formatting tools (like the one I mentioned from Tuxera), and make sure you use MicroSD cards only and if you can, pick a 4GB one.
Best of luck to all having trouble with this godforsaken box and please report back so other people who WILL ALSO have problems can find help in the future.
I have x96 max plus 4gb/64gb board v4.0.Who installed armbian ubuntu on s905x3?
I1V1A1N said:
I have x96 max plus 4gb/64gb board v4.0.Who installed armbian ubuntu on s905x3?
Click to expand...
Click to collapse
This is for H96 max X3 https://forum.armbian.com/topic/13992-h96-max-x3-specifics-only/
ludotaku said:
I evntually found out which pin to short thanks to mAtvXk on freaktab.
Please note that this is for the 4/64 version.
The 2/16 is a bit different, here is the pic posted by mAtvXk:
Hope this helps.
Click to expand...
Click to collapse
its different version the first pic is v4.0 the second pic is v3.0 the short pin location is different.. anyone know where the short pin loaction for the first pic?

Goclever Zoom.me adb connection

Hi Team,
Long story short - I have a problem with adb connection to Android device. And details below.
I've got a Goclever Zoom.me - Android 4.2.2 based photo frame. Really crappy device by the way... but, I really need to install some apk to have a possibility of remote connection to this device (FTP or SMB, or at least just create some network-shared directory). It would be also perfect to have any launcher with android menu and so on...
The issue is that it's impossible to connect to this device via adb. I remember that with old firmware it was actually possible, but long time ago (2015) I upgraded it to newer software, and official instruction to click 8 times a serial number in a device's software to enable USB debugging doesn't work anymore... I thought it had enabled debugging permanently but it seems to be not true, as adb nor fastboot don't see the device. PC recognizes it as a camera allowing to transfer files only.
Device doesn't have any hardware buttons except power and hard reset buttons. I was looking for any possibility to solder volume buttons, but didn't find a spot for them (mainboard is marked as: e351308 topwise-014).
I can connect OTG keyboard and mice instead, which may be helpful... but escaping nor ALT+ESC in the best case moves me to black screen with mouse cursor only...
Can you advice anything to connect to device via adb? What else can I try?
Modify the update perhaps? Seems to work.
GoClever Zoom.me and GApps
I need some help. I own a digital photo frame GoClever Zoom.me which is based on Android 4.2.2. It is rooted and USB debugging is on. I managed to install standard launcher but unfortunately there is no GApps installed on this device. I'm able...
forum.xda-developers.com
Still available
http://downloadfiles.goclever.com/Tablet/Zoom_me/ZOOM.ME_WiFi_Zmiana_Oprogramowania.pdf
80 page manual for a photo frame? LOL!
http://zoom.me/files/manual_en.pdf
Well, some say repetitio est mater studiorum, so they have put it there twice...
LOL! 40 page manual for a photo frame...
CXZa said:
Modify the update perhaps? Seems to work.
Click to expand...
Click to collapse
What do you mean by modifying the update? To modify /system/build.prop ?
I saw that thread, but the issue is that I can't update device again... PhoenixSuit nor adb can see it connected - seems like USB debugging is not enabled anymore and I can't enable it anyhow.
CXZa said:
80 page manual for a photo frame? LOL!
(...)
LOL! 40 page manual for a photo frame...
Click to expand...
Click to collapse
That frame was released with a huge marketing action...but it became a failure as it's a terrible design in total - from housing to software...
matisys said:
Hi Team,
Long story short - I have a problem with adb connection to Android device. And details below.
Can you advice anything to connect to device via adb? What else can I try?
Click to expand...
Click to collapse
That's really weird, because ADB since ever is integral part of every Android distribution. May be in the ROM your device is running on either ADB in fact isn't implemented or USB.debugging isn't allowed or ADB isn't bound to Android's USB-service.
matisys said:
What do you mean by modifying the update? To modify /system/build.prop ?
Click to expand...
Click to collapse
Meant flashing. So, do you have the MTK or Allwinner?
With one button it might be difficult to enter the update mode, but if opened you could possibly connect some pins to make boot to fail thus making it to boot such mode... IDK.
Other possibility is to make your wifi to connect to your own server instead of http://ota.zoom.me/ and let it "update" itself.
Their update zips are signed using test keys so you can make your own. (If recovery keys aren't changed when updated.) Or if you can enter the recovery mode then install it from sdcard.
I have multiple tools, but none can see the device without debugging on.
It's actually easy to open, but I didn't find a proper spot to enforce recovery mode...
CXZa said:
Other possibility is to make your wifi to connect to your own server instead of http://ota.zoom.me/ and let it "update" itself.
Their update zips are signed using test keys so you can make your own
Click to expand...
Click to collapse
How do you know that?
Running an own server is actually an easy part for me, but I'm not sure how to prepare a proper package...
There is actually an update package available to download:
http://downloadfiles.goclever.com/Tablet/Zoom_me/ZM7WIFI_20150717.img
But I couldn't modify it using Dragonface...
matisys said:
How do you know that?
But I couldn't modify it using Dragonface...
Click to expand...
Click to collapse
I checked the recovery in case build.prop lies.
Then again is their update a zip? Might be something exotic.
I also checked their ota apk and tested it.
It didn't download. Sent a lot of info from my tab. Some didn't match (faked what I easily could)... or no updates anymore...
Gave 502...
matisys said:
I didn't find a proper spot
But I couldn't modify it using Dragonface...
Click to expand...
Click to collapse
Another soc and device, but might work.
Entering to Flashing/Adfu mode (and Recovery mode too) - Actions Semi ATM7029 Quad-core ARM CPU devices
Entering to Flashing/Adfu mode (and Recovery mode too) - posted in Actions Semi ATM7029 Quad-core ARM CPU devices: The instructions given in this thread should work, but still as always, you use them at your own risk!If there is a hardware problem then the tablet probably is bricked for good...
www.slatedroid.com
Battery removing might be the safest...
Try imgRePacker...
OK, I managed to unpack the img file and to edit build.prop - Thanks fot that info One small step forward.
I added:
qemu.hw.mainkeys=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=ptp,adb (this one already exists)
Hoping it will allow me to access the system via adb or screen directly after reflash.
I didn't pack it back yet as I still didn't manage to access this device from computer...
I tried to find a spot on mainboard - I've made a connection on two spots:
{
"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"
}
But no luck...
There is more spots however, but none marked as recovery, ADFU, or similar...
And still no USB debugging, nor adb connection...:/
Tried of course some tricks with power button holding, clicking, reseting while hold, etc...
Any further suggestions...?
Maybe some ideas to enforce upgrade via wifi? I can establish a server, but not sure what exactly server should serve...? Just an img file is rather not enough...
Below that E351308 text, or above if other way around, is the target for those pin suggestions. But try battery, you can always solder it back together,.. or just let it go empty - might work...
> what exactly server should serve...?
yeah, there probably is some data exchange before the download..
BTW, this img appears to have adb enabled, so it's not the last one... Or it's disabled by other means...
Data it sent:
{"genderId":-1,"email":"","Locale":{"L":"eng","S":"en_US","C":"USA"},"deviceInfo":{"TIME":1419244414000,"FINGERPRINT":"ZOOM_ME\/ZM7WIFI\/ZM7WIFI:4.2.2\/JDQ39\/20141222:eng\/test-keys","HARDWARE":"gs702a","VERSION.SDK_INT":17,"BOARD":"exdroid","PRODUCT":"ZM7WIFI","DISPLAY":"ZM7WIFI_20141222","VERSION.INCREMENTAL":"20141222","DEVICE":"ZM7WIFI","TAGS":"test-keys","MODEL":"ZM7WIFI","BOOTLOADER":"unknown","CPU_ABI":"armeabi-v7a","CPU_ABI2":"armeabi","VERSION.CODENAME":"REL","MANUFACTURER":"ZOOM_ME","BRAND":"ZOOM_ME"}}
Click to expand...
Click to collapse
That hardware exposed me. It didn't get that from *.prop files.
OK, so currently it's like below.
I already tried some tricks with battery - disconnecting, connecting while booting, and no luck...
I tried with all spots marked below - one by one, and some combinations of few of them...
And the status is like that - spots 2 and 3 - seems to be ignored when connected - device behaves like nothing happened. It's more interesting when I connected 1 or 4. Device didn't start, and in a computer it appeared as unknown winusb device or Billboard device when connected 4 (USB\VID_1F3A&PID_EFE8&REV_02;3).
Universal ADB driver installer doesn't recognize it...
The only driver I managed to install was Allwinner driver and it appeared as USB Device(VID_1f3a_PID_efe8).
But still no luck with adb connection... Phoenix suite also doesn't recognize the device... In this state screen remains black and AXP223 (Power management) quickly becomes hot as hell (battery unplugged)...
Once unsoldered - it went back to life.
I also realized that my device says that it is version ZM7WIFI_20150717... what is confusing a bit because in other place it says it's 2.2 23-5.03.2015 software version...
But still no connection or any option to flash it
Can you tell me how do you run this software/hardware to see what does it send?
I can still use OTG keyboard and mouse - maybe there is some option to enter android settings and simply enable USB debugging?
Those pins that I mentioned at slatedroid are on the sides of that chip.. and don't solder, just place some tool - a needle between them. And if recognized remove it as after error it must function again in order to flash or what ever..
Here is one older post showing pin connecting for Amlogic,
that other was Actions Semi. Both go a mode that enables flashing when device looks dead. I don't know about Allwinner, is it similar...
How To Unbrick Your Amlogic AML8726-MX Series Tablet - v2.0 - Ainol Novo 7 Crystal
Page 1 of 47 - How To Unbrick Your Amlogic AML8726-MX Series Tablet - v2.0 - posted in Ainol Novo 7 Crystal: How To Unbrick Your Amlogic AML8726-MX Series Tablet - v2.0If Ive helped you unbrick your device please consider a donation, even if it is small it will help!My laptop is currently all...
www.slatedroid.com
So it seems that would be all, and the device got bricked...
I started the device with 7 and 8 pin of Flash memory connected - it was connected to PC and PhoenixSuite with original img loaded was running.Phoenix asked me immediately if I want to format the device - I clicked no, and it still started to flash the memory... It finished succesfully, device restarted and...now it freezes on initial logo.
Phoenix and adb recognize the device now, but adb shell doesn't work:
- exec '/system/bin/sh' failed: No such file or directory (2) -
and when I try to repeat flashing, phoenix recognizes device, but once I click upgrade - device resets, and upgrade is not performed...
EDIT: It's not that bad... I managed to make it working again on original software, and after one more reflash - ADB works well
Thanks a lot for all your help!
Did the reset hole fix it?
Maybe you should have formatted it in case the data is the reason to the freeze. But how it recovered?...
This Allwinner seem to be quite good.
Open source and giving info.
FEL - linux-sunxi.org
linux-sunxi.org
Installing to NAND - linux-sunxi.org
linux-sunxi.org
FEL/USBBoot - linux-sunxi.org
linux-sunxi.org
matisys said:
after one more reflash - ADB works well
Thanks a lot for all your help!
Click to expand...
Click to collapse
Great! Now disable that ota updater apk so it doesn't update it again...
It's actually hard to tell how it got fixed... instruction tells to not format the storage to not loose the unique device number - so I didn't, but it seems that it got formatted by itself as I lost all my pictures, but number remained untouched.
Now adb is enabled and I can freely connect to it - seems that something simply went wrong during previous upgrade years ago.
build.prop file gets restored after every reboot, so I can't put and store any changes there...
And OTA is not an issue as this device is not supported for a long time now And I'm not exactly sure how to do it, and feel a bit afraid of touching it when it finally works...
But just to finish entire project - can you recommend some reliable android SSH and FTP server? Or maybe something to share a folder via SMB?
matisys said:
But just to finish entire project - can you recommend some reliable android SSH and FTP server? Or maybe something to share a folder via SMB?
Click to expand...
Click to collapse
Not really but that android version limits the choices nicely...
Here is one saying it's open source.
swiftp
A FTP Server for your Android device.
ppareit.github.io
I think I once tested cifs in that Action Semi but it was long ago and was ready made in that test boot img...
[HOW TO] 2-way network file sharing on Android
Hi everyone, just thought I'd write up some quick instructions on how to set up file sharing between Android and a PC - both mounting Windows shares on Android, and Android on Windows. I was always frustrated by iOS's inability to do this easily, and it was one of the major reasons I switched...
forums.androidcentral.com
Thanks. Finally, after some trials I used SSHDroid and it's quite decent...
Can you also tell me how to permanently edit build.prop file? Mine is reverted to original after reboot. Device is factory rooted.

Categories

Resources