Comprehensive guide on unbricking the ASUS transformer pad 103c (TF103C)

Comprehensive guide on unbricking the ASUS transformer pad 103c (TF103C) - Android Q&A, Help & Troubleshooting

Welcome to the comprehensive guide on rooting and unbricking your precious TF103C!
Some words of wisdom and truth
You will most likely be here because, you know, your device is bricked.
First of all, I would like to say that none of the downloadable links are made by me. I happened to find them laying around XDA after looking for a solution for a long time.
Skip this if you don't want to know the reason behind this thread
I got this device a while back (my guess is 4 months), and loved it from the start. Rooted it, of course, and soon after, it didn't want to boot anymore.
As there isn't much development going on (due to the locked bootloader), it's hard to find a solution for bricking. While scrolling, I came upon a post from member gouster3, which came to the solution below. I myself have used this successfully, and have my tablet back. In my opinion, also on rooting, there was no dedicated thread available that really explained the steps to root the device, so as a thank you to the guys who got my tablet fixed, here it is!
The rooting process
The rooting of this tablet is quite easy, really! I'll explain in a few simple steps.
Head into settings > security > then turn on unknown sources
Download the Rootzenfone .apk file. get it here
Install the app (if it is still in your notification bar you can just press the downloaded file, or you can navigate to it's location to install from there)
Turn on airplane mode before you open the app
Open the app, and hit "OK, I know, please root!" (when you press this, a number of screens and a popup will show, ignore those)
5 seconds after pressing, restart your tablet.
Hooray! You are now rooted!
Unbricking your device
Luckily, unbricking is almost as easy as rooting the phone, if you know the steps you have to follow. Here's what you could do (it worked for me) if you still have acces to DROIDboot.
As always, install the adb drivers first! get it here
# You can also make sure the correct driver is installed when plugging in the device in DROIDboot mode. In you device manager it should show up as Android Debug Bridge#
Download these files, containing a clean system. get it here
Make sure the device is turned off, and the battery is at least 50% (just to ensure a complete flash before your battery runs out)
Hold volume+ and power untill the asus screen pops up, then release the power button.
Plug in the tablet to your pc (usb cable) when DROIDboot has been loaded.
Open the downloaded folder, and find 'update_image.bat'
Right click the .bat file, and choose 'run as administrator'
A CMD screen should open on your PC indicating the flashing status. All you have to do now (assuming that it works as intended) is wait untill the process is completed.
Your tablet will reboot automatically when the process is done.
That's it! the 2 things that keep this tablet alive. I would like to send a thanks to the members who were so kind to help me out on this.
gouster3, for providing the link to the unbrick solution
Eclipse00, for giving the link to the rootzenfone apk
Monki, for giving me a clean system.img and putting effort into getting my tablet running again
To all of you, thanks!

It works on my TF103CX too. (it is same hardware).
When i bricked my TF103CX, i had around 80% of battery, but i was not able to charge,
so be careful when bricking. Always do interventions to system with full battery.
//I think, we need add our TF103C to xda device list. it will be nice.
I heared that using Intel Manufacting Tool we can get UEFI instead of Droidboot, and boot Ubuntu/Windows on IntelBay tablets. I found guide for Teclast: http://forum.xda-developers.com/android/general/teclast-x98-air-3g-tablet-9-7-2048x1536-t2913035 But i cannot find any UEFI fot TF103C. I dont want to full brick m device with trying flash it.

Here is original thread in russian language.

Thanks
Thanks for helping me rescue my tablet. Much appreciated

Could anyone please confirm if the rooting method may be used on the TF103CG (K018) model? Or in general is the app able to root any device that is anyhow Zen-related?

this don´t work if you have lillipop on tf103c, the droidboot don´t load, You only get Fasboot starting and nothing more...

i want the raw lollipop image ( system.img ) for tf103c

will this essentially work as a factory reset? mine touch isn't working; and i just want to nuke all my data off the device

Hello all, I just ordered a TF0310C (Best Buy exclusive) from woot.com which will be here tomorrow and the closest thing I can find information on is the TF103C (both are Intel processors), and just trying to find as much info on it as I can. I was unable to find any roms or anything for the TF0310c, will things from the TF103C work on the TF0310C such as rooting or custom recovery at least?
http://computers.woot.com/offers/asus-transformer-pad-10-1-android-tablet-1

Unbrick not working on tf103c running KK. It looked like it was doing something, but no luck. Any common troubleshooting tips?

m374llic4 said:
Will things from the TF103C work on the TF0310C such as rooting or custom recovery at least?
http://computers.woot.com/offers/asus-transformer-pad-10-1-android-tablet-1
Click to expand...
Click to collapse
I know its a bit late, but perhaps better than never. I'd say those devices are identical, but somehow there is a weird naming mixup. Here are the official ASUS pages for them:
http://www.asus.com/supportonly/ASUS Transformer Pad TF0310C/HelpDesk/
https://www.asus.com/Tablets/ASUS_Transformer_Pad_TF103C/specifications/
Whatever you do on the first link, it will be eventually redirected to somewhere that belongs to the second. Their specifications are also basically the same. This is still a guessing game tough, so the best would be to compare 2 build properties, partition tables etc. of those devices to know more.
Rooting will most likely work, Zenroot should do it regardless of device type.

hello,
i have tried different way to unbrick my tf103c, but none is working
i have access to fastboot
i successfully run your bat file to copy the image, but after it reboot and stays on the "asus" logo
if i launch the command after modified the name of the "AS-TF103C-v67.43-capsule.bin" into "capsule.bin", it reboot then a blue progress bar is showing, when the bar is complete the tab reboots, but again it stays on the "asus" logo :'(
do you have any advise ?

Same issue
Hello,
I have the same issue with my tf103c ; i was trying to apply a new update from asus support (to get android 5).
It didn't work and in addition to that, my device results to be bricked.
I have successfully run the bat file, but then i get stuck at Asus logo and device never boot...
Icarolo did you manage to solve your issue ? Is someone really succeed in unbrick tf103c device ?
Thank you in advance

Dead
Hi! I have an asus tf103c and i rooted it with the rootzenfone.apk but now it doesn't turn on at all. after i pressed okay, waited about 15 sec and then i restarted it, but it just turned off. And now it's dead. What should i do?

ASUS K010 (TF103C). I forgot how to enter Recovery
Hello everyone, I have an ASUS K010 (TF103C). The complete model is TF103C-MB1-BLK-DK.
I forgot how to enter Recovery. My Asus is bricked. I know it is possible to enter the recovery because a few months ago I entered and also enter droidboot mode. On that occasion I discovered pressing the buttons energy, volume +, volume - somehow, because I did not work the methods that were in different sites websites, but now I do not remember the exact way of pressing the buttons. I tried many methods but they do not work, only the "Asus looking for incredible" logo appears. The battery has a charge (I charge it manually).
If someone has this same model and knows how to enter the recovery would greatly appreciate it.:good:

I think you can enter the droidboot menu by pressing Volume Up + Power for several secondes.

i dont have acces to DROIDboot.
How can unbrick my tf103c.. thanks

i dont have acces to DROIDboot.
How can unbrick my tf103c.. thanks

Brick3d said:
Welcome to the comprehensive guide on rooting and unbricking your precious TF103C!
Some words of wisdom and truth
You will most likely be here because, you know, your device is bricked.
First of all, I would like to say that none of the downloadable links are made by me. I happened to find them laying around XDA after looking for a solution for a long time.
Skip this if you don't want to know the reason behind this thread
I got this device a while back (my guess is 4 months), and loved it from the start. Rooted it, of course, and soon after, it didn't want to boot anymore.
As there isn't much development going on (due to the locked bootloader), it's hard to find a solution for bricking. While scrolling, I came upon a post from member gouster3, which came to the solution below. I myself have used this successfully, and have my tablet back. In my opinion, also on rooting, there was no dedicated thread available that really explained the steps to root the device, so as a thank you to the guys who got my tablet fixed, here it is!
The rooting process
The rooting of this tablet is quite easy, really! I'll explain in a few simple steps.
Head into settings > security > then turn on unknown sources
Download the Rootzenfone .apk file. get it here
Install the app (if it is still in your notification bar you can just press the downloaded file, or you can navigate to it's location to install from there)
Turn on airplane mode before you open the app
Open the app, and hit "OK, I know, please root!" (when you press this, a number of screens and a popup will show, ignore those)
5 seconds after pressing, restart your tablet.
Hooray! You are now rooted!
Unbricking your device
Luckily, unbricking is almost as easy as rooting the phone, if you know the steps you have to follow. Here's what you could do (it worked for me) if you still have acces to DROIDboot.
As always, install the adb drivers first! get it here
# You can also make sure the correct driver is installed when plugging in the device in DROIDboot mode. In you device manager it should show up as Android Debug Bridge#
Download these files, containing a clean system. get it here
Make sure the device is turned off, and the battery is at least 50% (just to ensure a complete flash before your battery runs out)
Hold volume+ and power untill the asus screen pops up, then release the power button.
Plug in the tablet to your pc (usb cable) when DROIDboot has been loaded.
Open the downloaded folder, and find 'update_image.bat'
Right click the .bat file, and choose 'run as administrator'
A CMD screen should open on your PC indicating the flashing status. All you have to do now (assuming that it works as intended) is wait untill the process is completed.
Your tablet will reboot automatically when the process is done.
That's it! the 2 things that keep this tablet alive. I would like to send a thanks to the members who were so kind to help me out on this.
gouster3, for providing the link to the unbrick solution
Eclipse00, for giving the link to the rootzenfone apk
Monki, for giving me a clean system.img and putting effort into getting my tablet running again
To all of you, thanks!
Click to expand...
Click to collapse
Hi, I see that the thread is old, but I need to fix my old pad. I can do all the steps, but the problem is that I can not find a clean system I can install. I will really appreciate if someone could give me a link to one.

Unbricking tf103c
Hello,
Is it possible to unbrick somehow a device like mine. I dont have either bootloader or recovery or anything (I have two same tablets) and I mess one up. After new update touch screen stopped working so I installed something (I dont remember) i installed new recovery and then tried to install new rom...Every time I power it on (doesnt matter standar od with combos it just show asus logo in search of incredible and that's it. I managed if I press both VOL - and VOL + AND PWRBTN I get something in device manager "Unknown USB Device (Device Descriptor Request Failed)"! Is there anything I can do?

Related

Rooting MTK6589 KVD Apollo One

Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys

Potentional Tutorial
philipkroberts said:
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Click to expand...
Click to collapse
philipkroberts said:
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Click to expand...
Click to collapse
Also looks like im getting the Star N9589 just due to the more support available.
Anyhow until then, failing any answers from here, another chinese forum a spanish one and Yahoo answers I am going to go with the following method, If it dies, It dies this was my own fault for not doing enough research and at least it lets others know. I would send it back to DX But cba with postage fees and the hassle;
THIS IS DONE AT YOUR OWN RISK! -
APOLLO ONE - MTK 6589 K6589
Please note all tools and zip files mentioned I cant link to yet should you feel you want them please post in this thread and I will PM you, Gotta get my post count up first!
Guide by philipkroberts Twitter @philipkroberts
Revision 1 - People to be added to credits for leehed source, currently untested, concept only
Before anything try and boot into any form of recovery mode and backup if possible!
DISABLE UAC in WINDOWS 7
RIGHT CLICK RUN AS ADMIN ON ALL FILES
ALLOW NON TRUSTED DRIVER INSTALLATION (Google this if unsure)
On the phone install anububu on pc phone. - See what model it detects as and note it down.
Run MTK DROID TOOLS and connect phone see if drivers After a few seconds, the box should turn blue, and it should say "Apollo ONE or Other Name " besides it. The drivers are working.
If not try the other drivers in the drivers folder using device manager, there are many tutorials for this I cba typing one im so tired! and make sure you have the only trusted drivers thing turned off, if you constantly get unknown driver then your out of look and wil have to try and source some yourself.
Win7 (This method has not been tested by myself. Confirmation required.)
HOW TO MANUALLY INSTALL ANY DRIVERS IF NEEDED
a - Downloading This tool Called EASYBCD
b - Use it to restart your computer in advanced boot mode. (PRESSING F8 WHILST BOOTING UNTIL YOU GET THE OPTION FOR Disable signed driver enforcement)-Must be done everytime you wanna root a phone with this method.
c - Follow instructions and disable SDE.
d Manually install drivers, if above did not work (Yellow sign issue)
e Navigate to control panel - > Hardware and Sound - > Device Manager
f You should see a driver notice with a yellow warning sign next to it.
g Right click on it and choose "Update driver..".
h- Manually assign drivers, usually the choice furthest down.
i- In the window which should have appeared, navigate to the preload/Mt6590 folder and press OK.
j- If SDE is turned off, you should see a red warning window. This is normal, just accept the message prompted.
k- The drivers should now be successfully installed.
l - Once this is done open C:\Users\Hate\Desktop\Chinese Droid Rooting\MTKROOT TOOLS\Root_with_Restore_by_Bin4ry_v28\runme.bat Hope it ****ing works if so your rooted, If not try this next few steps, AGAIN at your own risk, no need to format just continue from here.
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
0 - Use PC to copy UPDATE-SuperSU-v.1.25.zip to the root of SD CARD, do not unpack just leave whole zip there.
1 - Turn off your phone, remove your battery. (Do not connect your phone to the computer yet!)
2 - Navigate to the "SP Flash Tool" folder, and run the tool.
3 - On the right side of the tool, there should be a button, iconed with a folder, named "Scatter-Loading". Click this.
4 - Navigate to the "Yulypis Recovery" folder, and double-click on the "Mt6589_Android_scatter-emmc.txt".
5 - You should be back at the SP Flash Tool start-screen, and there should have appeared a list of text and hex-codes.
6 - The "Recovery" line, should be ticked off, and preloader should be red.
7 - Now, click on the button named "Download", with a blue arrow on it. Press "YES" on the NOT ALL images has been correctly loaded warning.
8 - Connect your phone to a USB 2.0, with removed battery. The program should now work, and if drivers is set up correctly, the 0% will turn 100% and a green circle will appear in the middle of the screen. If your phone disconnects before the flashing tool is able to recognize your device, try putting the battery back into the phone before running SP Flash tool. Additionally, if this doesn't work, try using different drivers in the drivers folder
9 - Disconnect your K6589 from the computer when you see the green circle, insert the battery and boot the phone. Wait for it to get to the start screen.
11 - Installing SuperSU through Yulypis recovery
12 - Run "MtkDroidTools.exe" from the folder.
13 - Connect your device, and after a few seconds, information about your device should appear.
14 - Click on reboot, on the mtkDroidTools start-screen, and choose "..recovery".
15 - If recovery has been properly flashed, your device will now enter Yulypis recovery. Blue, with english text.
16 - Controllers: "Power = Enter, Initialize", "Volume down = Scrolling down". (Don't remember if volume up was bugged or not)
17 - Enter "Install zip from SDcard" - > Navigate to the earlier copied "UPDATE-SuperSU-v.1.25.zip and initialize it by pressing the power button.
18 - Follow the on-screen instructions, and it should be prompted to install after 1-2 more screens.
19 - Reboot the device by clicking on "+++++back+++++" and "Reboot now / Reboot Device".
Either way I am going to smash this in a week or so when the phone arrives from DX and will keep people update.
Peace

Please I want to buy this phone. Can you answer me a few doubts I have?
- How is the viewing angle? Cause i purchased a tablet from china and the angle is very bad.
- Has proximity sensor?
Are you ok with the phone?
thank you.

cabrote said:
Please I want to buy this phone. Can you answer me a few doubts I have?
- How is the viewing angle? Cause i purchased a tablet from china and the angle is very bad.
- Has proximity sensor?
Are you ok with the phone?
thank you.
Click to expand...
Click to collapse
I'm still awaiting the phone, hence why that guide is at your own risk.
However from what I have been told and gather that should root the phone no problems.
As for custom roms, I wouldn't even bother trying!
Once the phone gets here I will test my tutorial and re-write it into a more easy on the eyes fashion.
Thanks

http://www.fastcardtech.com/APOLLO-ONE-K6589?u=37825
They sell the phone, for an extra $3 they root before sending.
It cant be that hard, I'd love to know someone in that factory!

I'm looking for a link to download the full stock firmware for this device.
Anyone, please?
...or at least a firmware dump from a non-modified working phone.
One could use MTK Droid Tools and SPFlash to perform this task easily.
PM me for assistance if you need it.
Thank you.

TF201 stop at ASUS logo - after a firmware update

Hello,
I download from the ASUS website the firmware with version "V10.4.2.18 Only for WW SKU (Android 4.1)" and the pop-up for update de firmware appear normally to me.
Then, the TF201 restarted and since then does not passes through the ASUS Logo.
I Was on 4.0.0.3, firmware 9.4.2.28 and tried to upgrade to a superior version (my mistake as I can see now).
Even when restarting with Power + VOL DOWN the only thing that appears is :
----......................
The Device is Unlocked.
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.2.28-20120525" A03
Checking for android ota recovery
Booting recovery kernel image
-----------
And stays here forever... No option with the 3 icons, so I can choose USB... And neither the VOL UP during this process does nothing...
Anyone can help?
Thanks in advance

Looks like you updated to an incompatible version. The first thing you needed to do was to unlock the bootloader. Volume up will not work unless you specifically enable nvflash, which is the second thing you needed to do. Considering that you still have usb, you may be able to use fastboot to replace your recovery. From there you may still be able install an older rom. If you can get at least some kind of rom running, you'll want to enable nvflash first thing so that you can make your tablet bricksafe. Let us know if you get that far...

sl0mar said:
Looks like you updated to an incompatible version. The first thing you needed to do was to unlock the bootloader. Volume up will not work unless you specifically enable nvflash, which is the second thing you needed to do. Considering that you still have usb, you may be able to use fastboot to replace your recovery. From there you may still be able install an older rom. If you can get at least some kind of rom running, you'll want to enable nvflash first thing so that you can make your tablet bricksafe. Let us know if you get that far...
Click to expand...
Click to collapse
I installed the drives and the PC recognizes the TF-201.
But it seems that fastboot can't recognize the tablet.
Well, I didn't get so far...
But I still want to try, but I'm a little lost...
Any help?

what you see when u run fastboot devices ?

inbg said:
what you see when u run fastboot devices ?
Click to expand...
Click to collapse
From my PC device manager I can see the asus transformer Prime APX Interface and is saying that "This device is working properly.".
However, every command that I sent from fastboot the result is always the same:
< waiting for device >
I'm completely out of ideas to get this back to work...

THATS BAD do u have working adb ?

No i don't...

HOW to Reserruct from APX mode^
HI all,
I have been searching for months how to unbrick the tf201 after trying to load the official update from Asus.
I see so many users stuck like myself in APX mode with the "unlocked" message and Asus Logo.
I have tried in all described ways on the forums to get it to fastboot mode but nothing is helping.
Asus as many have written, are charging a lot for repair, I even bought another used one hoping I could upload the saved blob file from it but it is device related as I read. Is there any solution that will help?
I see a lot of advanced users creating roms and upgrades but never proposing how to unbrick this device in APX mode.
Thank you for all developers here who take the time to push things forward. :angel:

logicmate said:
HI all,
I have been searching for months how to unbrick the tf201 after trying to load the official update from Asus.
I see so many users stuck like myself in APX mode with the "unlocked" message and Asus Logo.
I have tried in all described ways on the forums to get it to fastboot mode but nothing is helping.
Asus as many have written, are charging a lot for repair, I even bought another used one hoping I could upload the saved blob file from it but it is device related as I read. Is there any solution that will help?
I see a lot of advanced users creating roms and upgrades but never proposing how to unbrick this device in APX mode.
Thank you for all developers here who take the time to push things forward. :angel:
Click to expand...
Click to collapse
Logicmate, seems there is no help how to unbrick the tf201 in APX mode...
Did you get lucky meanwhile?

Hard bricked Motorola G7 - Need help

Hello everyone! I am in dire need of help.
So I recently decided to acquire a regular Motorola G7 because I had heard its battery is fantastic. This far, I have been loving it.
But silly me decided I wanted to explore OEM boot unlocking to eventually root the device. After successfully completing theses tasks, I installed the TWRP recovery. Sadly, something (must have) went wrong because when I tried to reboot, the phone went into hard brick. Completely unresponsive, holding both power and vol. down button for 2+ minutes did nothing. I basically have exhausted every Internet recommendations thus far and nothing has been fruitful.
I have been able to get the Qualcomm Port 9008 (COM3) to show up in device manager when I hold power and vol. down. Also, the program QPST also recognizes a phone in Sahara download mode (although I have no idea what it means nor what to do with that, if anything).
So here I am, asking for your help. I have read somewhere that a blankflash zip file could allow me to restore my phone but alas, I wasn't able to find any nor would I know what to do with it.
I would greatly appreciate any help.
Regards,
Afireblood.
Edit: I have managed to find a way to potentially salvage my bricked phone, using QIFL tool to flash a stock rom. However, to do so I need some files (which are proper to the Moto G7 - any other would not do). They are:
programmer (firehose?).mbn
rawprogram.xml
patch.xml
If anyone has any clue where I could find that (except everywhere on Google - it hasn't been helpful), I would very much appreciate it!

afireblood said:
Hello everyone! I am in dire need of help.
So I recently decided to acquire a regular Motorola G7 because I had heard its battery is fantastic. This far, I have been loving it.
But silly me decided I wanted to explore OEM boot unlocking to eventually root the device. After successfully completing theses tasks, I installed the TWRP recovery. Sadly, something (must have) went wrong because when I tried to reboot, the phone went into hard brick. Completely unresponsive, holding both power and vol. down button for 2+ minutes did nothing. I basically have exhausted every Internet recommendations thus far and nothing has been fruitful.
I have been able to get the Qualcomm Port 9008 (COM3) to show up in device manager when I hold power and vol. down. Also, the program QPST also recognizes a phone in Sahara download mode (although I have no idea what it means nor what to do with that, if anything).
So here I am, asking for your help. I have read somewhere that a blankflash zip file could allow me to restore my phone but alas, I wasn't able to find any nor would I know what to do with it.
I would greatly appreciate any help.
Regards,
Afireblood.
Edit: I have managed to find a way to potentially salvage my bricked phone, using QIFL tool to flash a stock rom. However, to do so I need some files (which are proper to the Moto G7 - any other would not do). They are:
programmer (firehose?).mbn
rawprogram.xml
patch.xml
If anyone has any clue where I could find that (except everywhere on Google - it hasn't been helpful), I would very much appreciate it!
Click to expand...
Click to collapse
Update: Now in search of the Moto G7 specific blankflash.zip
If anyone knows where I can find that I would really appreciate it!!

I am not familiar with the g7. (I own a G5+). I believe the G7 code name is "river". You can look at https://mirrors.lolinet.com/firmware/moto/river/ and they show a blank flash - but let me say something - a blank flash must be exact for your phone. Its basically the main disk partition with other partitions inside. My phone has 64GB/4GB, and 32GB/3GB-2GB models - so you see a problem. But if all the G7s are the same, then this blank flash should be OK.
Also you can download the phones original firmware at https://mirrors.lolinet.com/firmware/moto/river/official/RETUS/ , if its a US model. If its not, back up 1 directory and you can find it by either carrier or country. You can fastboot the firmware - which I would do before a blankflash,
Hope that helps.

Need Tablet to Boot Up When Plugged In

I need to run a tablet in a type of kiosk mode. For this to work, the tablet needs to boot up automatically when power is received.
I have MediaTek K107, with Android 7.0.
I have done a lot of googling, and found a number of sources that looked like they might help, but (a) some of them were device specific (b) all of them seemed to be dated, and (c) the one that looked like it might be doable just dumped me into a menu that was all in Chinese. (turn off device, turn on by holding VolDn + Pwr....should enter fastboot mode. )
Honestly I would be happy to at least get some general advice on this. What would be the big picture steps I need to take to accomplish this?
(This is a question that was posted 7 years ago and was never answered. Hope it is okay that I am starting a new thread under this circumstance.)

Try this
fritz.barnes said:
I need to run a tablet in a type of kiosk mode. For this to work, the tablet needs to boot up automatically when power is received.
I have MediaTek K107, with Android 7.0.
I have done a lot of googling, and found a number of sources that looked like they might help, but (a) some of them were device specific (b) all of them seemed to be dated, and (c) the one that looked like it might be doable just dumped me into a menu that was all in Chinese. (turn off device, turn on by holding VolDn + Pwr....should enter fastboot mode. )
Honestly I would be happy to at least get some general advice on this. What would be the big picture steps I need to take to accomplish this?
(This is a question that was posted 7 years ago and was never answered. Hope it is okay that I am starting a new thread under this circumstance.)
Click to expand...
Click to collapse
Hi there,
Try this
You can install this app called GOKIOSK from the google play store but this will not boot up your device when plugged in you have boot up manually by pressing the power button
SETTING UP GOKIOSK
Download GoKiosk
If you want instructions on GoKiosk visit this webiste : https://www.bosstab.com/resources/android-tablet-kiosk-mode/
But there is a trick to shut down your device remotely with a text.
If your device have SIM slot then this method will work.
In order to do so you have to ROOT your tablet first.
You can use KINGOROOT or any method you prefer
After rooting install this app from Google Play Store
https://play.google.com/store/apps/details?id=AutomateIt.mainPackage&hl=en
STEPS
Install and open the AutomateIt app. Provide root permission.
Tap My Rules > + icon.
Hit SMS With Text Trigger.
Provide SMS permission.
In the field, enter the text as per your wish. enter the text turnoff.
Tap Next.
Choose Shutdown Device Action.
Provide a name for the rule and then hit the Save icon at the top.
Regards
KIBS2173

[Hisense A9] Root - How easy? (Snapdragon 662)

Hisense just released a new device called the A9. Since this phone has Snapdragon 662 I was wondering how easy it would be to root this device. I know there is an EDL for this CPU. The Hisense A5 series was also rootable. Not sure what method was used.
The Onyx Boox Note Air 2 (a 10.3" tablet), which I have, also runs on the same Snapdragon 662 and can be rooted via Magisk. I used the EDL to dump the boot.img on the Note Air 2 to root it via Magisk.
Disclaimer: I'm not a developer or super technical guy, but have rooted a few devices by following guides.
Does anyone know how easy or fast a root would be available? I'm assuming they didn't lock the bootloader on this device as most Chinese devices.

Hello, could you share with us how to root boox device please?

It would be great if GAPPS could be used.

Replying to bump this thread. I have the Hisense A9 and would love to be able to root. It has an option to unlock the bootloader in the developer options if that is helpful.

formeriphoneuser said:
Does anyone know how easy or fast a root would be available? I'm assuming they didn't lock the bootloader on this device as most Chinese devices.
Click to expand...
Click to collapse
Hello and good morning, @formeriphoneuser
I hope you'll always find and get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator

I recently good a Hisense A9, and I've been trying to extract the boot.img and / or recovery.img from it (since I can't find either of those online yet). So far I've been trying to get boot.img from EDL mode using this EDL tool. I can boot into EDL mode fine, but when I try to run an EDL command there are lots of errors. It's possible I'm using the wrong Firehose file, but I think it's right. (I'll post a link to the logs below). I've been following this guide mainly. Is anyone else working on this?
*Edit* the firehose file I'm using is 0014d0e100000000_d40eee56f3194665_FHPRG.bin.
Anyway, OP - hopefully I, or someone, can get the boot image or recovery image soon, then we should be able to patch it with Magisk fairly easily and install Google Services etc.
A word of warning to anyone who wants to try working on this - every time I restart after being in EDL mode, the phone goes into a boot loop of sorts. I enter the 6-digit pin at boot-up, and the phone says something in Chinese (which Google translates as something like "optimising the system, please wait", from memory), and then keeps showing the desktop screen for a second, then looping back to the pin code input, then showing the message, and then repeat. If you hold down volume down, it'll go into safe mode, but then the same thing happens when you restart. I've always managed to get out of it, but I'm not 100% sure how! Something like holding the power key down for about 10 seconds while it's looping... The phone vibrates, but doesn't turn off, and then the loop stops and you can enter your 6-digit pin again and it's back to normal. If that doesn't work, then try turning the phone off, then back on again, but holding the power key down so it keeps restarting without fully booting. Last time I made it restart ~5 times, and then it was back to normal. Maybe it cleared some kind of system cache...?
These are the errors I get from the EDL tool when I try to extract the boot image.
https://pastebin.com/ejXfCJs9
https://pastebin.com/5CqUPB0a
https://pastebin.com/LMmEmm6v

RunnyYolk said:
I recently good a Hisense A9, and I've been trying to extract the boot.img and / or recovery.img from it (since I can't find either of those online yet). So far I've been trying to get boot.img from EDL mode using this EDL tool. I can boot into EDL mode fine, but when I try to run an EDL command there are lots of errors. It's possible I'm using the wrong Firehose file, but I think it's right. (I'll post a link to the logs below). I've been following this guide mainly. Is anyone else working on this?
Anyway, OP - hopefully I, or someone, can get the boot image or recovery image soon, then we should be able to patch it with Magisk fairly easily and install Google Services etc.
A word of warning to anyone who wants to try working on this - every time I restart after being in EDL mode, the phone goes into a boot loop of sorts. I enter the 6-digit pin at boot-up, and the phone says something in Chinese (which Google translates as something like "optimising the system, please wait", from memory), and then keeps showing the desktop screen for a second, then looping back to the pin code input, then showing the message, and then repeat. If you hold down volume down, it'll go into safe mode, but then the same thing happens when you restart. I've always managed to get out of it, but I'm not 100% sure how! Something like holding the power key down for about 10 seconds while it's looping... The phone vibrates, but doesn't turn off, and then the loop stops and you can enter your 6-digit pin again and it's back to normal. If that doesn't work, then try turning the phone off, then back on again, but holding the power key down so it keeps restarting without fully booting. Last time I made it restart ~5 times, and then it was back to normal. Maybe it cleared some kind of system cache...?
These are the errors I get from the EDL tool when I try to extract the boot image.
https://pastebin.com/ejXfCJs9
https://pastebin.com/5CqUPB0a
https://pastebin.com/LMmEmm6v
Click to expand...
Click to collapse
Maybe try this loader. This is for sure the one I used for my NA2. Otherwise, you have quite some errors that relate to python. Not sure what the issue is there.

formeriphoneuser said:
Maybe try this loader. This is for sure the one I used for my NA2. Otherwise, you have quite some errors that relate to python. Not sure what the issue is there.
Click to expand...
Click to collapse
Awesome, thanks! I should have mentioned which loader I was using (different to the one you linked). I'll edit my post to say what I used before.

I tried the loader that @formeriphoneuser suggested, but with a similar result. (https://pastebin.com/ucMkEkeW). I also tried with the flag --memory="ufs" in case the device has UFS memory, but similar result.
But the good new is, I've just discovered a reliable way to avoid the boot loop after leaving EDL mode. So to leave EDL mode, make sure any running commands have ended, unplug the device from the computer, and press and hold the eink button (on the left of the phone), volume-up, and power button. Keep them all pressed until the first vibration (after about 15 seconds or so, then release the power button only). Keep the other two pressed while the phone boots, and even while you're entering your 6 digit pin code. When you see the main screen you can release the buttons and your phone shouldn't enter the boot loop. I have no idea how much of that is necessary, but something in there works for me.
I've added an Issue to the github repo for the EDL tool I'm using. Other than that, I think I've hit a brick wall and won't be able to do any more for now. Unless anyone knows how to check that the firehose file is correct for my device, and update it if it's not. Hopefully Hisense will release the stock firmware, or send us an OTA update or something.

Does this work? if the Bootloader could be unlocked.

Arthurliao said:
Does this work? if the Bootloader could be unlocked.
Click to expand...
Click to collapse
The problem with a GSI is that Android doesn't have partial refresh support for the eInk display, which means a driver has to be written from scratch, otherwise the display will be verrrrrry slow.

RunnyYolk said:
I tried the loader that @formeriphoneuser suggested, but with a similar result. (https://pastebin.com/ucMkEkeW). I also tried with the flag --memory="ufs" in case the device has UFS memory, but similar result.
But the good new is, I've just discovered a reliable way to avoid the boot loop after leaving EDL mode. So to leave EDL mode, make sure any running commands have ended, unplug the device from the computer, and press and hold the eink button (on the left of the phone), volume-up, and power button. Keep them all pressed until the first vibration (after about 15 seconds or so, then release the power button only). Keep the other two pressed while the phone boots, and even while you're entering your 6 digit pin code. When you see the main screen you can release the buttons and your phone shouldn't enter the boot loop. I have no idea how much of that is necessary, but something in there works for me.
I've added an Issue to the github repo for the EDL tool I'm using. Other than that, I think I've hit a brick wall and won't be able to do any more for now. Unless anyone knows how to check that the firehose file is correct for my device, and update it if it's not. Hopefully Hisense will release the stock firmware, or send us an OTA update or something.
Click to expand...
Click to collapse
Bit of a long shot here, but I vaguely remember having trouble with EDL on my Oneplus 6T and I think the solution was to use a USB2 port instead of USB3.

RunnyYolk said:
I tried the loader that @formeriphoneuser suggested, but with a similar result. (https://pastebin.com/ucMkEkeW). I also tried with the flag --memory="ufs" in case the device has UFS memory, but similar result.
But the good new is, I've just discovered a reliable way to avoid the boot loop after leaving EDL mode. So to leave EDL mode, make sure any running commands have ended, unplug the device from the computer, and press and hold the eink button (on the left of the phone), volume-up, and power button. Keep them all pressed until the first vibration (after about 15 seconds or so, then release the power button only). Keep the other two pressed while the phone boots, and even while you're entering your 6 digit pin code. When you see the main screen you can release the buttons and your phone shouldn't enter the boot loop. I have no idea how much of that is necessary, but something in there works for me.
I've added an Issue to the github repo for the EDL tool I'm using. Other than that, I think I've hit a brick wall and won't be able to do any more for now. Unless anyone knows how to check that the firehose file is correct for my device, and update it if it's not. Hopefully Hisense will release the stock firmware, or send us an OTA update or something.
Click to expand...
Click to collapse
Also, looking at your pastebins, It seems you are running Ubuntu via a Parallels Virtual Machine. I would suggest using the LiveDVD from the EDL github repo and running it on bare metal to rule out any system related issues. Given that the pastebins show errors relating to libusb1.py, there is a good chance your issues are due to the emulated USB controller provided by Parallels.

matteqa said:
Also, looking at your pastebins, It seems you are running Ubuntu via a Parallels Virtual Machine. I would suggest using the LiveDVD from the EDL github repo and running it on bare metal to rule out any system related issues. Given that the pastebins show errors relating to libusb1.py, there is a good chance your issues are due to the emulated USB controller provided by Parallels.
Click to expand...
Click to collapse
I tried booting the liveDVD from the repo in Parallels, but it wouldn't boot, saying something like Ubuntu was missing. But I'll try it as a bootable USD drive. I won't be able to do it until next weekend at the earliest, but I'll report back when I've tried that method. Thanks for your suggestions!

So I bought a USB drive and flashed the liveDVD from the repo to it, but my only computers are Macs and will recognise the USB drive as bootable - I've tried Fat32 / HFS+ file systems, made sure it's a GUID partition table, and used both Etcher GUI and terminal's `dd` to burn the image to the drive, but still the USB never shows up in the startup utility. Anyway, I've hit a roadblock on this for now - I think my next options are to either pick up a cheap Windows laptop, or put a bounty out for boot.img (or preferably full root! )

RunnyYolk said:
So I bought a USB drive and flashed the liveDVD from the repo to it, but my only computers are Macs and will recognise the USB drive as bootable - I've tried Fat32 / HFS+ file systems, made sure it's a GUID partition table, and used both Etcher GUI and terminal's `dd` to burn the image to the drive, but still the USB never shows up in the startup utility. Anyway, I've hit a roadblock on this for now - I think my next options are to either pick up a cheap Windows laptop, or put a bounty out for boot.img (or preferably full root! )
Click to expand...
Click to collapse
Just checking, have you tried the macOS version of the EDL tool? All of your pastebins are from ubuntu parallels, however there is also a native macOS version in the github repo.

matteqa said:
Just checking, have you tried the macOS version of the EDL tool? All of your pastebins are from ubuntu parallels, however there is also a native macOS version in the github repo.
Click to expand...
Click to collapse
Ah, that's a good call! I did try the native Mac version on one machine, but it wasn't able to find libusb library, so I started using parallels / ubuntu, and then basically forgot that the native mac version existed! So thanks for the reminder - I tried it yesterday on an older Mac, and the native EDL client seems to be working properly. Unfortunately I think the firehose / loader files I have aren't correct. When I ran it with a loader I get sahara - [LIB]: Unexpected error on uploading, maybe signature of loader wasn't accepted ?
type object 'req' has no attribute 'image_id', and then I tried running it without any loader and got sahara - [LIB]: Couldn't find a loader for given hwid and pkhash (0014d0e100430000_56d3f3c74a52172b_[FHPRG/ENPRG].bin) :(.
So I guess we need the correct loader for the A9. I'm pretty clueless about how these files come to exist in the first place (do they have to come from the manufacturer, or can we build them ourselves?), but anyway I'll open a new issue on Github and see if the developer of the client can help.
For completeness' sake, here are logs from each attempt at reading boot_a (I tried three different loaders, each one with and without --skipresponse, and then once with no loader).
https://pastebin.com/AA9d5Tdh
https://pastebin.com/gXHS9pYN
https://pastebin.com/6e5FeWDc
https://pastebin.com/8dGWFNau
https://pastebin.com/iTd8ZsVH
https://pastebin.com/2esPvxyX
https://pastebin.com/Pvz9YxfE
https://pastebin.com/D47mPKt6
*edit* This is the issue on Github: https://github.com/bkerler/edl/issues/303

RunnyYolk said:
Ah, that's a good call! I did try the native Mac version on one machine, but it wasn't able to find libusb library, so I started using parallels / ubuntu, and then basically forgot that the native mac version existed! So thanks for the reminder - I tried it yesterday on an older Mac, and the native EDL client seems to be working properly. Unfortunately I think the firehose / loader files I have aren't correct. When I ran it with a loader I get sahara - [LIB]: Unexpected error on uploading, maybe signature of loader wasn't accepted ?
type object 'req' has no attribute 'image_id', and then I tried running it without any loader and got sahara - [LIB]: Couldn't find a loader for given hwid and pkhash (0014d0e100430000_56d3f3c74a52172b_[FHPRG/ENPRG].bin) :(.
So I guess we need the correct loader for the A9. I'm pretty clueless about how these files come to exist in the first place (do they have to come from the manufacturer, or can we build them ourselves?), but anyway I'll open a new issue on Github and see if the developer of the client can help.
For completeness' sake, here are logs from each attempt at reading boot_a (I tried three different loaders, each one with and without --skipresponse, and then once with no loader).
https://pastebin.com/AA9d5Tdh
https://pastebin.com/gXHS9pYN
https://pastebin.com/6e5FeWDc
https://pastebin.com/8dGWFNau
https://pastebin.com/iTd8ZsVH
https://pastebin.com/2esPvxyX
https://pastebin.com/Pvz9YxfE
https://pastebin.com/D47mPKt6
*edit* This is the issue on Github: https://github.com/bkerler/edl/issues/303
Click to expand...
Click to collapse
Have you tried to read from "boot" instead of "boot_a". Maybe hisense isn't using A/B partitions since they don't care about google play certification. Also, have you tried using --memory=ufs.
Otherwise, it may be that the loader has a custom signature. As far as I know, the loader is proprietary and you have to get it from the manufacturer.

@RunnyYolk
I've also just found a patched version of a SDM662 loader on another forum that might work.
I've reuploaded it here: https://cloud.matteqa.com/index.php/s/M6MxgPFDsYwaKP6

matteqa said:
@RunnyYolk
I've also just found a patched version of a SDM662 loader on another forum that might work.
I've reuploaded it here: https://cloud.matteqa.com/index.php/s/M6MxgPFDsYwaKP6
Click to expand...
Click to collapse
Thanks! I tried this loader, and also the --memory=ufs flag / "boot" alternatives as you suggested, but had the same errors as before. I'm pretty sure I saw boot_a and boot_b directories somewhere when I was exploring the filesystem in adb shell, but I'll double check again when I have time.
Are there any other avenues I could try to root this device? I wonder if there's any point trying to boot TWRP from an A7? Am I right in thinking I can `fastboot boot recover.img` without risk of bricking the phone? (Ie just booting rather than flashing.)... Maybe I'm clutching at straws...

Better Mobile App

welcome