Related
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.
Unable to install MODULE, it says (please view the screen capture I posted in the thread)
Hi guys, I have a problem regarding my A13 android tablet device. It doesn’t matter if I will post the brand name of my tablet or whatever because what I only wanted to fix is this. When I follow every instruction written at this link, and following instructions 1-7, after reaching step 5 execute run.bat.
It displays the following image I screen captured. (And my tablet doesn’t reboot, it’s the sign that the computer can’t access my tablet.
View attachment 2445500
Obviously, my tablet is connected to the computer via USB cable after running the run.bat as administrator.
But what is the problem why it is happening to me. What can I do for this?
(Additional information: I already installed and followed this instruction on this same device with no error at all. But why does it happened to me even I installed this with success before. I don’t know and I know that I don’t change any system file on my tablet before, and I don’t know because, I have no idea why it happened? I didn’t change any file or modify file neither on my tablet nor from my PC.)
I hope there is an expert who can answer my question and give to me a solution. Thank you in advance if there is.
nooffensesite said:
Unable to install MODULE, it says (please view the screen capture I posted in the thread)
Hi guys, I have a problem regarding my A13 android tablet device. It doesn’t matter if I will post the brand name of my tablet or whatever because what I only wanted to fix is this. When I follow every instruction written at this link, and following instructions 1-7, after reaching step 5 execute run.bat.
It displays the following image I screen captured. (And my tablet doesn’t reboot, it’s the sign that the computer can’t access my tablet.
View attachment 2445500
Obviously, my tablet is connected to the computer via USB cable after running the run.bat as administrator.
But what is the problem why it is happening to me. What can I do for this?
(Additional information: I already installed and followed this instruction on this same device with no error at all. But why does it happened to me even I installed this with success before. I don’t know and I know that I don’t change any system file on my tablet before, and I don’t know because, I have no idea why it happened? I didn’t change any file or modify file neither on my tablet nor from my PC.)
I hope there is an expert who can answer my question and give to me a solution. Thank you in advance if there is.
Click to expand...
Click to collapse
You need to install ADB. I'll report the post to the moderators to get this post in the right section.
I will continue searching for that
thewadegeek said:
You need to install ADB. I'll report the post to the moderators to get this post in the right section.
Click to expand...
Click to collapse
Alright then thanks for the clue, it’s almost 3 days now since I nonstop looking for solution for this problem. I know that it’s a harsh to think that even a simple problem like was I don’t know how to search and fix. I hope you understand that I am almost losing my hope to solve this problem. At least when because I have written and shared my question on this forum. At least I found new idea again.
I never expect that the answer is only to install ADB.
That is my next goal now, to search how to enable ADB on my PC. I know that this problem that I need to fix was only from my PC, because the USB debugging mode on my tablet setting is already activated. And I checked that a dozen of times already.
And if you found something about my post was not in a right section. Then it’s a thankful for me if you can help me with that, because this is just the first day of my life that I started using this site, except for reading a thread as a guest.
It didn't work
I already installed adb using this tutorial on the link <--- (I’m sorry I can't provide the link outside of this site because, I am a new user yet.) But still, because my tablet problem is the touch screen that’s why I am trying to install the module to fix my device touch screen. But the most important part was that from what I need is to touch/tap on a notification area on tablet to activate the “usb mass storage” button.
My PC can’t detect my tablet because I didn’t tap the “usb mass storage” button yet.
And I can’t tap it because that’s it, I need to install the module first to fix the Touchscreen to allow me activate the button. Oh God, this is so terrifying event.
:crying: :crying: :crying:
Did you try booting into recovery?
YES,
thewadegeek said:
Did you try booting into recovery?
Click to expand...
Click to collapse
Yeah, my tablet can boot to recovery mode. Everything is okay from my tablet. The only problem was the touch screen and the unable me to install module by running the run.bat file.
The only way that I can boot to recovery is by using a USB laptop mouse. And entering settings>Backup & reset>Recovery Mode.
Tonight is the 4th day of my problem. And still I’m stuck up from Touch Screen Problem.
Is there any other way aside from using that module just to fix my touch screen?
I am not good using Linux, so if incase the other way to fix this was by using linux operating system. Then maybe, I should stick to using this module.
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?
Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden
Bump? Anyone? Still swinging in the breeze on this one. No word back from the manufacturer, as expected. =/
I have the same problem
Shaiden said:
Bump? Anyone? Still swinging in the breeze on this one. No word back from the manufacturer, as expected. =/
Click to expand...
Click to collapse
I know it's been 4 years but did you find any solution to this? I'm asking because I have the same problem. I decided to downgrade to Remix OS 1.5 in order to root (I have tried 5 rooting apps with no success) but my device refuses to enter fastboot protocol. The whole idea was since I can't find a way to root the damn thing in its current state maybe I can manage it with its older OS version. All this just to turn it to android root apps "testing ground" device. Oof.
I am trying to unlock the bootloader so I can root a LG Aristo 4 plus model LMX320MA.
1st off I tried "kingroot", kingoroot" and a few other one step app's. None of them worked.
I type in the cmd window "adb devices" I get the following answer:
"list of devices attached"
"LMX320980e0723 device"
Next I type in "adb reboot bootloader" and I am spouse to get on the phone that is in the screen capture that is in the Dropbox link bellow.
https://www.dropbox.com/s/k1u2r5eudem996w/fastboot.jpg?dl=0
instead of getting the screen that is in the Dropbox link above. The phone just boots up to the normal home screen. See the next Dropbox link bellow.
https://www.dropbox.com/s/fopf8ykyyazq0dt/screen capture.jpg?dl=0
I don't know how to fix this problem in ADB- Fastboot
Power off, connect usb and hold power and vol+ button until it boots
DavidxxxD. The phone powers down ok. But the "hold power and vol+ button" doesn't do a darn thing. The phone boots to the normal home screen.
DavidxxxD said:
Power off, connect usb and hold power and vol+ button until it boots
Click to expand...
Click to collapse
@reble1
Phone's stock boot image has dm-verity, which prevents you from booting if you make system modifications.
I finely figured out the buttons. I found a Metro PCS/T Mobile web page with the info. It is pressing and holding the vol down button plus the power button until the 1st Metro logo comes up on the screen. Keep holding the vol down button in while releasing the power button for a sec then press and hold the power and vol down buttons until the 2nd Metro logo pops up on the screen. Then I am in. BUT it doesn't do me any good. All that screen is good for is to wipe the phone clean in the event of a soft brick and set the phone back to factory default settings. It is like wiping the hard drive clean on my Windows laptop and reinstalling the OS and everything else.
I am still stuck in rooting this phone. I understand the concept of rooting, it is like getting super administrator privileges in Windows. I am still fairly new to Android.
@reble1
Since almost a decade peoples use Chainfire's SuperSu to successfully root an Android device without any sprains.
BTW: To root Android doesn't require device's bootloader is unlocked.
jwoegerbauer. What do you mean by "dm-verity"? I went looking and I found out what "dm-verity" is. there is a few reasons as to why I want to root the phone.
1. it is a learning curve for me, it enhances my understanding of Android.
2. there is 2 annoying popups that pope up when I 1st wake up the phone. 1 is from Metro PCS, advertising, and the other is Google Chrome, the last web page that I was on. One or both pop up before I get to the home page.
3. there is a few programs that I would like to look at that require the phone to be rooted.
PS: What is a good phone or tablet that is easy to root for experimenting on?
jwoegerbauer said:
@reble1
Phone's stock boot image has dm-verity, which prevents you from booting if you make system modifications.
Click to expand...
Click to collapse
JwoegerbauerI am fairly new at Android. My vast knowledge, Starting with a Vick 20 and moving up the Commodore chain, then the MS-Dos chain and finely Windows 3.1 and up. Helps some. But I also know there is a lot of differences between Android and Windows.
Is there anyway around the dm-verity? Or am I just plain stuck with what I got?
jwoegerbauer said:
@reble1
Phone's stock boot image has dm-verity, which prevents you from booting if you make system modifications.
Click to expand...
Click to collapse
@reble1
Compared to Windows OS - what is a proprietary OS - Android OS is an open-source OS, means everybody can offer a modified version of it ( keyword: Lineage OS et. al ). OEMs / Carriers got tired of people trying to change the Android that came with their devices. Especially SuperSU and other one-click root enablers, XPosed Framework & Magisk Framework - 3rd-party Android modding tools that severely change the system part of Android OS - were/are such undesired candidates. Hence starting with Android 4.4.4 Google added the dm-verify ( read: Verify Boot ) - what of course on a rooted Android can get disabled. It's a cat-and-mouse game that's going on. Also Android users must know that a modded / rooted Android always can get detected, even if they think that modding / rooting happened in a hidden manner as claimed. Google, OEMs and Carriers are certainly not as stupid as some people think ....
I am to the point of saying. Leaving it ASIS and put up with the browser popping up just after waking up the phone and before the home screen comes up. That was the whole exercise of this was to stop the browser from popping up between waking up the phone and the home screen coming up. And saving space by dumping blotters.
jwoegerbauer said:
@reble1
Compared to Windows OS - what is a proprietary OS - Android OS is an open-source OS, means everybody can offer a modified version of it ( keyword: Lineage OS et. al ). OEMs / Carriers got tired of people trying to change the Android that came with their devices. Especially SuperSU and other one-click root enablers, XPosed Framework & Magisk Framework - 3rd-party Android modding tools that severely change the system part of Android OS - were/are such undesired candidates. Hence starting with Android 4.4.4 Google added the dm-verify ( read: Verify Boot ) - what of course on a rooted Android can get disabled. It's a cat-and-mouse game that's going on. Also Android users must know that a modded / rooted Android always can get detected, even if they think that modding / rooting happened in a hidden manner as claimed. Google, OEMs and Carriers are certainly not as stupid as some people think ....
Click to expand...
Click to collapse
If it was me, being an lg device I'd try to see if I could get modded lgup (dual mode)
By tchnight or the original one by astr4y4l
I'd then see if I cold get the correct dll files for it to connect to my phone.
I'd try dump option to get my firmware.
If successful
I'd rename boot_com3.mbn to boot.img
Then patch it with magisk,
Then use partitions dl option on lgup to flash that magisk_patched image renamed boot.img back to the phone...
Just my 2 cents and unless you gonna pay me for my time and Info..
I'm off the clock
LgPWN'd. Sorry for the delay in the reply. I had other things to tend to that took up my time.
I am not sure i understand what you mean by "modded". If I understand it right. It would be the same as splitting a PC hard drive into 2 partitions and putting Windows 7 on 1 partition for older programs and games. And on the other partition Windows 10, right? secondly I am not worried if Metro PCS finds out that the phone has been rooted. From what I have been told Metro PCS doesn't care if the phone is rooted. Also I am assuming tchnight and astr4y4l are rooting programs? If so. Are they Android app's or Windows based programs? Also I have the correct Windows USB driver to connect my phone to my laptop.
LgPWN'd said:
If it was me, being an lg device I'd try to see if I could get modded lgup (dual mode)
By tchnight or the original one by astr4y4l
I'd then see if I cold get the correct dll files for it to connect to my phone.
I'd try dump option to get my firmware.
If successful
I'd rename boot_com3.mbn to boot.img
Then patch it with magisk,
Then use partitions dl option on lgup to flash that magisk_patched image renamed boot.img back to the phone...
Just my 2 cents and unless you gonna pay me for my time and Info..
I'm off the clock
Click to expand...
Click to collapse
A PS: I just did a quick internet search for " astr4y4l" and " tchnight" . There isn't anything that I can see that has anything to do with cell phones at all.
reble1 said:
A PS: I just did a quick internet search for " astr4y4l" and " tchnight" . There isn't anything that I can see that has anything to do with cell phones at all.
Click to expand...
Click to collapse
Try searching on xda
Sent from my Willeyfox Swift using Taptalk