Related
Hi all,
I had a nice, long, detailed post typed out but then my browser at work crashed, so here is the revised edition:
I recently (three days ago) bought a TF300T tablet. Absolutely love it. As any android fan does, I immediately wanted to root it to get the full benefit of the device. I followed the step-by-step guide on the cyanogenmod wiki and have been successful (after a few hours of figuring things out) in unlocking the device. I am aware at this point that my device is unlocked and my Asus warranty is voided. I am also aware I may have to follow different steps to root it, and am willing to do so accordingly.
I'm not set on using cyanogenmod, but that seems to be the most popular and well-known one so I'd like to use one that is established.
So, up until now I have followed that guide but I am having an issue with flashboot. When I go to do the 'fastboot devices' command, I get nothing. It just jumps to the next line, as if I sent a blank command. When I type 'adb devices' it works fine and shows some letters&numbers so I know my device is recognized.
With all that being said, can anyone advise me on which step I'm doing wrong, if any?
Also, I'm -really- cautious about potentially bricking this thing. I still have 30 days at Best Buy but I'm also an employee there and my co-workers know I'm trying to root so if I brick it, it may not be as easy to return it as with a normal customer. I also have the Accidental Damage & Handling plan so if I DO brick it, I can smash it and get a new one without too much incident, if it comes down to it (which obviously is a LAST resort)
My device is as following:
Asus Transformer Pad TF300T unlocked, firmware .29.
I' have about 15 tabs open in Google Chrome right now after SEARCHing the forums, specifically the TF300 forum, and I'm filtering through all the posts right now. If I find a solution I will post asking for this thread to be deleted.
I'm very tech-savvy, but completely new to android. I don't own a smartphone, and this is my first android device, so this is an incredible learning experience. If anyone feels so kind, could you please explain the different terminiologies used in the rooting scene? I hear stuff about blobs, .build files, DE, WW, US stuff. What's what? And what does it all mean?
Thanks so much, and here's to hoping my computer doesn't crash as soon as I press "post"!!
-Opethfan89
*edit* Forgot to add that when I use the command
fastboot flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
the command prompt just stays stuck on "waiting for device", while my device is stuck on "Starting fastboot USB download protocol"
Slight resolution
So I am just posting with a slight update to what I've been trying to get this working. I uninstalled the ADK, all drivers, and started over from scratch. I installed ADB using the method listed on the CyanogenMod wiki, and it works fine (I can use all ADB commands from command prompt and it lists my device when I use the 'adb devices' command.
So I'm continuing to follow the steps on the CyanogenMod wiki page and I get back to the part about Fastboot. I boot into fastboot mode, plug the device in, and the new development is that my computer DOES recognize fastboot only in device manager. I do have a yellow exclamation mark near it meaning I don't have the proper driver installed.
So now my newest question is, how do I install the driver for -just- fastboot, or where can I find the .inf file so I'm able to install it myself?
I'm SO close to rooting this device I can just taste it!! Any device is very much appreciated
Thanks!
Opethfan89
Are you following this guide?
http://forum.xda-developers.com/showthread.php?t=1668173
Pretty easy to follow and the easiest way to install recovery and root device.
Yes I have followed that guide and like I said I get to the step where fastboot SHOULD be recognized by my computer but it isn't. It shows up in my device manager with a yellow exclamation point so I literally just need the driver to make things work and I should be rooted.
This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.
Have you tried to see the index on tf300t development?
Hope you have all you need and all process.
For Fastboot : [GUIDE] Help for flash more faster when you use Fastboot Line Command
And for Drivers:
ASUS Android USB Drivers.zip - 2012/04/13 - MD5 Sum: 43af8f39ed421caabecd6c4a2de17212 - Size: 8.28 MB (8687221 bytes)
ASUS Pad PC Suite (PC version V1.0.41) - MD5 Sum: 02d7661affefeb0ae05f577b6b24b37a - Size: 145.09 KB (148570 bytes)
ASUS Sync V1.0.82 - MD5 Sum: a7d229ee2f2678819e6a99711d1f572d - Size: 62.18 MB (65195236 bytes)
You will find all you need for your TF300t in this index
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop
philos64 said:
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop
Click to expand...
Click to collapse
I think you do need to install android sdk because of the fastboot files are in there and need it to use fastboot that could be the reason why his computer does not recognize the tablet when he is in fastboot mode. If you look at your android manager you will see a file under android tools that fastboot files are installed.
you need to specify device id
fastboot -i 0x0b05 flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
try that op
IT WORKED!!!!
EndlessDissent said:
This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.
Click to expand...
Click to collapse
See, I think that's where I messed up. None of the guides say to download ASUS' drivers, and in my anxiousness to root I must have overlooked that step. I will try this today and post my results accordingly!! Also, no offense taken by the linux comment, and I've used linux in the past, but I've had quite a few times where it doesn't "just work" (Like using a broadcom wireless card on my old laptop. I had to learn how to use ndiswrapper and whatnot, not a pleasant experience for a linux newb at that time!!)
I recently removed my Linux partition (was using ubuntu 10.10 because I hate unity!!) and can re-install it if it will make my rooting process easier?
vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
Yea I didn't download the asus pad suite drivers, and I think that is what is causing my issue. I wish I could post links to the guides I am following but none of them specify that. They just say to download the android SDK and all drivers are included.
FlyingPoo said:
you need to specify device id
try that op
Click to expand...
Click to collapse
I did do that, flyingpoo. At one point my cmd line showed "Sending file recovery.img (5***kb)" but the tablet never picked it up, so I know there is just some miscommunication between the tablet and the PC. When I typed adb devices in cmd line, I see the device listed, but when I type fastboot devices in cmd line, it just goes to a blank line.
I will try the above listed solutions and hope that something works. Thank you all so much for your help!
*edit* This guy, right here? Yea, he's freakin ecstatic! I installed the drivers from EndlessDissents' post, and it worked!! As soon as I booted into fastboot mode, my computer recognized the device. I then used the command that FlyingPoo used (which I tried in the past), and it showed:
Code:
c:\recovery1>fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' <5306 KB>...
OKAY [2.417s]
writing 'recovery'...
OKAY [2.053s]
finished. total time: 4.473s
So now I'm following the next few steps to root it. I've backed up my apps using Astro as well as the ASUS backup suite, and I'm using CWM for a backup of my entire system at the moment.
Thank you again to everyone who responded. I always get hung up on the simplest step, but once that is overcome everything else is a smooth ride downhill
One last noobish question to ask, and then I think I'll be done:
I've downloaded the root-signed.zip file, as well as the latest CyanogenMod file I could find (The official wiki didn't have one listed for any asus products, for some reason?) as well as a google apps for cyanogenmod. I put the files on my SD card but nothing on there is detected within CWM. So the noobish question is which directory do I need to put the files in for CWM to detect it?
That being said, I'm also wanting to backup my system to my external SD card and I selected the option in CWM to backup but it said no sd\ext was detected. Any thoughts?
Thanks again everyone for your responses.
*EDIT* For anyone following this thread, I did figure it out. Another guide I referenced specifies that you copy the files to the INTERNAL SD card (which is kind of confusing, as SD card explicitly refers to an external memory card) and then choose it from CWM. So for me, I downloaded the files on my computer, copied them to my SD card, put the SD card in my tablet, and copied the files to the root directory of the internal storage on my tablet.
Thanks again everyone, I now have root (at least, I'm pretty sure I do?)
Mod, please feel free to close this thread as necessary.
Phone: Alcatel One touch POP 5036x
PC OS: Windows 8.1
Hello, I am Nick from Holland and I am 13 years old. My first post is a request for help, for which I apologize.
I recently bought my second mobile phone, which is my first smartphone/android device.
Quickly after I purchased it, I decided to root the apparatus and got into sudo-ing and that kind of stuff.
Now my phone is in a boot loop and I am unable to recover from it.
I have been searching and reading this forum for days now, and I just cannot figure out what to do.
I' m having trouble finding the right files ( Stock image, CWM and such ) for my particular model.
What happened before this mess:
I installed an anti-theft program called ' Prey'
To see how this worked, I flagged my device as missing. Nothing happened though, so I reverted its status to OK.
Later on I decided to delete some bloatware, and eventually I accidentally erased a file called ' Android System' or something like that.
I am not 100% sure about this particular name though, but I do know it sounded important.
My phone froze during the deletion process and I decided to take the battery out and do a reset.
Phone OFF
Power + Volume up
wipe cache partition
wipe data/factory reset
After which I ended up[ in this boot loop.
The phone boots past the android logo, and restarts during the blue Alcatel POP-C5 animation.
To make things worse, I looked in the ' Prey Control panel, and noticed my phone was still flagged as missing.
I remember I read something, somewhere about a security measure that involves being unable to simply remove Prey
by resetting the phone to its factory defaults.
My current status:
I installed the necessary USB drivers on my Windows 8.1 machine, and I am able to connect to my phone using ADB.
I am able to reboot into fastboot. (
Code:
ADB reboot-bootloader
)
I am able to transfer files and such using ADB
I have collected and properly configured the paths within windows to use the command line and downloaded (I think) all the necessary software. like Flash Tool, MTK Droid, the Android SDK, etc.
Code:
fastboot devices
resolves mt6572v1_phone fastboot
Some discrepancies:
Code:
adb devices
resolves the following data:
List of devices attached
0123456789ABCDEF sideload
Notice 1-to-9 and A-to-F. This seems weird to me.
Code:
get-state
and
Code:
get-devseria
l both resolve 'unknown'
Is there anyone willing/able to help me resolve my issues?
In return I can eventually make a new tutorial or Alcatel OT-5036x recovery thread.
I will try pulling the debug info and produce a logfile later on and upload them to my Google Drive.
Regards,
p011i3 said:
Phone: Alcatel One touch POP 5036x
PC OS: Windows 8.1
Hello, I am Nick from Holland and I am 13 years old. My first post is a request for help, for which I apologize.
I recently bought my second mobile phone, which is my first smartphone/android device.
Quickly after I purchased it, I decided to root the apparatus and got into sudo-ing and that kind of stuff.
Now my phone is in a boot loop and I am unable to recover from it.
I have been searching and reading this forum for days now, and I just cannot figure out what to do.
I' m having trouble finding the right files ( Stock image, CWM and such ) for my particular model.
What happened before this mess:
I installed an anti-theft program called ' Prey'
To see how this worked, I flagged my device as missing. Nothing happened though, so I reverted its status to OK.
Later on I decided to delete some bloatware, and eventually I accidentally erased a file called ' Android System' or something like that.
I am not 100% sure about this particular name though, but I do know it sounded important.
My phone froze during the deletion process and I decided to take the battery out and do a reset.
Phone OFF
Power + Volume up
wipe cache partition
wipe data/factory reset
After which I ended up[ in this boot loop.
The phone boots past the android logo, and restarts during the blue Alcatel POP-C5 animation.
To make things worse, I looked in the ' Prey Control panel, and noticed my phone was still flagged as missing.
I remember I read something, somewhere about a security measure that involves being unable to simply remove Prey
by resetting the phone to its factory defaults.
My current status:
I installed the necessary USB drivers on my Windows 8.1 machine, and I am able to connect to my phone using ADB.
I am able to reboot into fastboot. (
Code:
ADB reboot-bootloader
)
I am able to transfer files and such using ADB
I have collected and properly configured the paths within windows to use the command line and downloaded (I think) all the necessary software. like Flash Tool, MTK Droid, the Android SDK, etc.
Code:
fastboot devices
resolves mt6572v1_phone fastboot
Some discrepancies:
Code:
adb devices
resolves the following data:
List of devices attached
0123456789ABCDEF sideload
Notice 1-to-9 and A-to-F. This seems weird to me.
Code:
get-state
and
Code:
get-devseria
l both resolve 'unknown'
Is there anyone willing/able to help me resolve my issues?
In return I can eventually make a new tutorial or Alcatel OT-5036x recovery thread.
I will try pulling the debug info and produce a logfile later on and upload them to my Google Drive.
Regards,
Click to expand...
Click to collapse
You mention cwm.
Don't you have a backup?
Try google translating this thread: http://www.phonandroid.com/forum/carliv-recovery-cwm-6-0-4-4-pop-c5-et-x-pop-t81752.html
Lgrootnoob;50489116]You mention cwm.
Don't you have a backup?
Try google translating this thread: *link removed due restrictions*
Click to expand...
Click to collapse
I thank you for your kind answer.
No, I do not have a backup prior to my problem.
I have one now though, before things get worse.
I actually made some progress - I managed to correctly install and boot CWM.
I already stumbled upon and downloaded the files mentioned in your link.
The teXt translates as:
-put mobileuncle tools and recovery on your SD
mobileuncle-install and granted him the rights superSU
-click recovery update
-then recovery.img
clicked OK
-then it will ask to restart a recovery click OK
I downloaded the file called ' recovery.img' but I am unsure how to transfer it to my device and implement it.
Also, how do I install and run mobileuncle without being able to boot?
Regards,
EDIT:
Code:
C:\Users\Maya\Desktop>fastboot flash recovery recovery.img
sending 'recovery' (5522 KB)...
OKAY [ 0.217s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.242s
Install stock firmware anf stock rom and ur phone via Odin.... and ur phone will start as it was when u purchased it...
DeathNotice said:
Install stock firmware anf stock rom and ur phone via Odin.... and ur phone will start as it was when u purchased it...
Click to expand...
Click to collapse
Were do I find these for my Alcatel 5036x?
I searched for like four days without any definitive result.
p011i3 said:
Were do I find these for my Alcatel 5036x?
I searched for like four days without any definitive result.
Click to expand...
Click to collapse
Either try:
Code:
fastboot oem unlock
Or talk to the manufacturer.
They should actually provide source code since it is an android/linux OS.
Once you try these things we will move forward.
Lgrootnoob said:
They should actually provide source code since it is an android/linux OS.
Once you try these things we will move forward.
Click to expand...
Click to collapse
This is wrong. They are not required to provide the source code for the OS. Only the kernel is licensed under the gpl. The rest is closed sourced.
You will need to track down the default software for the device. Which maybe hard if not impossible as clone devices/MTK devices are based out of China and few if any have any after market support.
p011i3 said:
Were do I find these for my Alcatel 5036x?
I searched for like four days without any definitive result.
Click to expand...
Click to collapse
Search it on www.SamMobile.com......U may get ur stock rom and firmware on it
Lgrootnoob said:
Either try:
Code:
fastboot oem unlock
Or talk to the manufacturer.
They should actually provide source code since it is an android/linux OS.
Once you try these things we will move forward.
Click to expand...
Click to collapse
Code:
Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
PS C:\Windows\system32> adb start-server
PS C:\Windows\system32> adb reboot-bootloader
PS C:\Windows\system32> fastboot oem unlock
...
And it just hangs there. (Tried 3 times and waited ~10minutes each.)
The cause of this is that I made things worse - yesterday I formatted the /system partition using CWM.
I did make a backup using Android Toolkiot first though, but again I am unsure how to recover it.
Also, I downloaded the files mentioned in the French I briefly discussed above.
I consists of almost all files listed in Flash Tool, except MOBILE_INFO, CACHE and USERDATA
The Alcatel Source code is hosted at Sourceforge under project name ' Alcatel'
zelendel said:
This is wrong. They are not required to provide the source code for the OS. Only the kernel is licensed under the gpl. The rest is closed sourced.
You will need to track down the default software for the device. Which maybe hard if not impossible as clone devices/MTK devices are based out of China and few if any have any after market support.
Click to expand...
Click to collapse
You are probably right. However, Alcatel actually does provide source code. See the ' Open Source' link at the bottom of the Alcatel website.
It is hosted at Sourceforge. Project name:: ' Alcatel'
I downloaded the the tar.gz archive earlier this week and extracted it, but I have no idea how to use this.
I am somewhat familiar with Linux though. I could set something up if I need to.
DeathNotice said:
Search it on SamMobile.com......U may get ur stock rom and firmware on it
Click to expand...
Click to collapse
I searched for ' 5036x' : " No entries found."
p011i3 said:
Code:
Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
PS C:\Windows\system32> adb start-server
PS C:\Windows\system32> adb reboot-bootloader
PS C:\Windows\system32> fastboot oem unlock
...
And it just hangs there. (Tried 3 times and waited ~10minutes each.)
The cause of this is that I made things worse - yesterday I formatted the /system partition using CWM.
I did make a backup using Android Toolkiot first though, but again I am unsure how to recover it.
Also, I downloaded the files mentioned in the French I briefly discussed above.
I consists of almost all files listed in Flash Tool, except MOBILE_INFO, CACHE and USERDATA
The Alcatel Source code is hosted at Sourceforge under project name ' Alcatel'
You are probably right. However, Alcatel actually does provide source code. See the ' Open Source' link at the bottom of the Alcatel website.
It is hosted at Sourceforge. Project name:: ' Alcatel'
I downloaded the the tar.gz archive earlier this week and extracted it, but I have no idea how to use this.
I am somewhat familiar with Linux though. I could set something up if I need to.
I searched for ' 5036x' : " No entries found."
Click to expand...
Click to collapse
I did look at it and it is the part of the source code for the kernel and that's it
Bat cave One
zelendel said:
This is wrong. They are not required to provide the source code for the OS. Only the kernel is licensed under the gpl. The rest is closed sourced.
You will need to track down the default software for the device. Which maybe hard if not impossible as clone devices/MTK devices are based out of China and few if any have any after market support.
Click to expand...
Click to collapse
The kernel should be good enough though. (With modules)
---------- Post added at 10:41 AM ---------- Previous post was at 10:36 AM ----------
@p011i3 Hey, what version of android do you have.
YOu might be able to make a flashable zip if you have a working system img.
Or we could make a false cwm backup and just restore system only from that.
I managed to fully recover my Alcatel One Touch POP C5 5036X without having a backup for my own. I did this by formatting the entire device using Flash Tool and downloading the files from the French Website discussed earlier in this thread.
I'll post a 5036X recovery topic including all files later this weekend.
Again, I thank everyone for their kind help.
Hello
Is there any simple boot loader so I can just boot my device from it,and just inspect the partitions on its flash?
I dont want to flash or hack my devices without a previous inspection. I mean, something similar to Linux "rescue" mode.
I have a MTK6575 based Zhou Xing phone and it has no "Backup & Recovery" option, so i can´t root it because I can´t boot from it.
I can see all my device filesystems with adb from my Linux.But filesystems are all read only.
A simple buybox tool just to tell adb "boot from sd" would be great !!
This is my first post here, i never registered and posted so far because im aware that my english sucks and my skill are really poor.
But now this is my last chance to recover my new tablet (2 days lifetime!)
I will try to explain the problem in the best way possible.
I have a Chuwi vi8 dual boot, and i needed root access to fix the sd card write restriction of 4.4.
After some search i was able to root it. Then i screwed up when i edited the build.prop to change the dpi from 160 to 200. I have touched the permission not knowing it would screw up the boot.
Now my chuwi is stuck on the android boot logo.
Im able to enter the recovery mode (power + volume -)
In the recovery menu (stock recovery menu) i have the following option:
reboot droidboot
reboot
recovery
power off
and this message in the lower part of the screen:
FASTBOOT INIT...
E:installer device ignored
E:failed to mount device '/dev/block/sda1 as installer partition using fs_type..
E:installed device ignored
E:installed device ignored
E:No valid installer medium found
FASTBOOT CMD waiting...
Then i enter recovery:
reboot system now:
apply update from ADB
wipe data/factory reset
wipe cache partition
apply update from internal storage
offcourse wiping everything doesnt solve the problem as the issue is in build.prop
then i try to use ADB:
i have the driver of this device installed in windows, im sure that USB debug was on on the device.
I tested various version of ADB from my pc but no one was able to let me use the vairous command (pull,push etc etc)
Im only able to "ADB devices" and see the name of the device + sideload, any other command will result in error: closed
Im trying to find someone whit a working build.prop, but while doing that i really like to try to pull,edit and push back mine.
I dont even know if there is a way to manual boot windows and try to do something from that side because i dont know if there is a manual way to boot into that.
Any help is appreciated, and again please forgive me if my first post is like this.
Thank you
Im going to reply to my own post
i abandoned the ADB method and went whit another strategy.
I was able to boot windows bios, change boot priority back to windows.
From windows i installed a tool to mount and browse android partition. Edited back build.prop.
Quick reboot and back in android!
Lesson learned. Thank you anyway and please forgive me for this post!
arkh01droid said:
Im going to reply to my own post
i abandoned the ADB method and went whit another strategy.
I was able to boot windows bios, change boot priority back to windows.
From windows i installed a tool to mount and browse android partition. Edited back build.prop.
Quick reboot and back in android!
Lesson learned. Thank you anyway and please forgive me for this post!
Click to expand...
Click to collapse
Hi,
Sorry for bothering, I have the same tablet, and would like to root it. Can you help me in this with a link to the right method or something? The reason is the same, to use the sdcard normally, and maybe ntfs.
Thank you in advance!
asteck said:
Hi,
Sorry for bothering, I have the same tablet, and would like to root it. Can you help me in this with a link to the right method or something? The reason is the same, to use the sdcard normally, and maybe ntfs.
Thank you in advance!
Click to expand...
Click to collapse
Hi,
Finally no need for help, made it with KingoRoot.
asteck said:
Hi,
Finally no need for help, made it with KingoRoot.
Click to expand...
Click to collapse
Hey there
I am trying to root my chuwi vi8 dual boot too
Could use some help
I tried KingoRoot but it does not work
Please help me
arkh01droid said:
This is my first post here, i never registered and posted so far because im aware that my english sucks and my skill are really poor.
But now this is my last chance to recover my new tablet (2 days lifetime!)
I will try to explain the problem in the best way possible.
I have a Chuwi vi8 dual boot, and i needed root access to fix the sd card write restriction of 4.4.
After some search i was able to root it. Then i screwed up when i edited the build.prop to change the dpi from 160 to 200. I have touched the permission not knowing it would screw up the boot.
Now my chuwi is stuck on the android boot logo.
Im able to enter the recovery mode (power + volume -)
In the recovery menu (stock recovery menu) i have the following option:
reboot droidboot
reboot
recovery
power off
and this message in the lower part of the screen:
FASTBOOT INIT...
E:installer device ignored
E:failed to mount device '/dev/block/sda1 as installer partition using fs_type..
E:installed device ignored
E:installed device ignored
E:No valid installer medium found
FASTBOOT CMD waiting...
Then i enter recovery:
reboot system now:
apply update from ADB
wipe data/factory reset
wipe cache partition
apply update from internal storage
offcourse wiping everything doesnt solve the problem as the issue is in build.prop
then i try to use ADB:
i have the driver of this device installed in windows, im sure that USB debug was on on the device.
I tested various version of ADB from my pc but no one was able to let me use the vairous command (pull,push etc etc)
Im only able to "ADB devices" and see the name of the device + sideload, any other command will result in error: closed
Im trying to find someone whit a working build.prop, but while doing that i really like to try to pull,edit and push back mine.
I dont even know if there is a way to manual boot windows and try to do something from that side because i dont know if there is a manual way to boot into that.
Any help is appreciated, and again please forgive me if my first post is like this.
Thank you
Click to expand...
Click to collapse
Hi man could you please tell me how to root this device
Does shifting the dpi make a difference?
Thanks in advance
[email protected] said:
Hi man could you please tell me how to root this device
Does shifting the dpi make a difference?
Thanks in advance
Click to expand...
Click to collapse
Changing DPI is for display scaling, but on your device hard editing the build.prop makes the device not booting!
Make sure to enable "USB debugging" before you try to root your device.
If Kingo still fails, you can try iROOT (former VRoot)
LS.xD said:
Changing DPI is for display scaling, but on your device hard editing the build.prop makes the device not booting!
Make sure to enable "USB debugging" before you try to root your device.
If Kingo still fails, you can try
Click to expand...
Click to collapse
Thanks a lot
Iroot did the trick
But I am unable to use the microsdcard tried link2sd
Partitioned the card for linking but link2sd cannot mount the ext3 partition
[email protected] said:
Thanks a lot
Iroot did the trick
But I am unable to use the microsdcard tried link2sd
Partitioned the card for linking but link2sd cannot mount the ext3 partition
Click to expand...
Click to collapse
Make sure that both partitions are "primary" 1. Partition "fat32" 2. Partition ext4 (MUST BE PRIMARY NOT LOGICAL!!!)
Aha... Finally found a place to discuss this chuwi vi8, a super cheap but amazing tablet LOL ?
Ok this is what've done to my vi8 tablet [emoji111]
A. Root
1. Install pdanet+ from pdanet.co, when it asking to choose phone manufacturer
choose "Others" then it will waiting your tablet to connect
2. Before you connect the tablet make sure that you have the developer menu enabled so you can make usb debugging mode enabled, then connect your tablet.. Wait until the device installation finish, then it will asking to choose after installation... Choose usb mode ignore other option then press finish, then you'll see that your device connected the taskbar
3. Install KingoRoot, launch it, wait until the KingoRoot appear on the tablet, on the computer choose remove root, wait till it succeeded
4. Install iRoot (VRoot), launch it, then root it... On the tablet you'll see a blue lion logo written Superuser
5. If you don't mind with Chinese root app then rooting finish on step 4, but if you do you can replace the root using another root app, in my case I use SuperSU from chainfire.
B. Xposed Framework
1. Download/Install Terminal Emulator from play store
2. Download/Install Root Explorer from anywhere LOL ?
3. Download/install Xposed Framework 2.6.1, install the framework but don't reboot
4. With root explorer go to /system/bin/ rename app_process to app_process.xposed-bak, then rename rename app_process.orig to app_process
5. Open Terminal Emulator
type "su" without quote then execute
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
type "chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
6. Reinstall the framework then reboot
C. Link2SD
1. Prepare the micro SD partition (I'm using mini tool partition), 1st Partition is FAT32 (Primary), 2nd Partition is ext4 (Primary and make it active)
2. Download/Install Link2SD from play store
3. Choose ext4 wait until it success and ask for reboot, then reboot.
Credit goes to... I forgot [emoji33]
Sorry for my bad English [emoji1] [emoji1] [emoji1]
resize patition
Hi is it possible resize android partition and use more space on windows partition? is it possible installing only windows or only android?
thanks
Possible...
Can anyone please provide me a copy of the recovery.img file for the Android partition?
god damn it
DhaniBaho said:
Aha... Finally found a place to discuss this chuwi vi8, a super cheap but amazing tablet LOL
Ok this is what've done to my vi8 tablet [emoji111]
A. Root
1. Install pdanet+ from pdanet.co, when it asking to choose phone manufacturer
choose "Others" then it will waiting your tablet to connect
2. Before you connect the tablet make sure that you have the developer menu enabled so you can make usb debugging mode enabled, then connect your tablet.. Wait until the device installation finish, then it will asking to choose after installation... Choose usb mode ignore other option then press finish, then you'll see that your device connected the taskbar
3. Install KingoRoot, launch it, wait until the KingoRoot appear on the tablet, on the computer choose remove root, wait till it succeeded
4. Install iRoot (VRoot), launch it, then root it... On the tablet you'll see a blue lion logo written Superuser
5. If you don't mind with Chinese root app then rooting finish on step 4, but if you do you can replace the root using another root app, in my case I use SuperSU from chainfire.
B. Xposed Framework
1. Download/Install Terminal Emulator from play store
2. Download/Install Root Explorer from anywhere LOL
3. Download/install Xposed Framework 2.6.1, install the framework but don't reboot
4. With root explorer go to /system/bin/ rename app_process to app_process.xposed-bak, then rename rename app_process.orig to app_process
5. Open Terminal Emulator
type "su" without quote then execute
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
type "chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
6. Reinstall the framework then reboot
C. Link2SD
1. Prepare the micro SD partition (I'm using mini tool partition), 1st Partition is FAT32 (Primary), 2nd Partition is ext4 (Primary and make it active)
2. Download/Install Link2SD from play store
3. Choose ext4 wait until it success and ask for reboot, then reboot.
Credit goes to... I forgot [emoji33]
Sorry for my bad English [emoji1] [emoji1] [emoji1]
Click to expand...
Click to collapse
ok my dear friend, I change the app_process to app_process.xposed-bak and then no more root, so no more rename, so have a brick, can u help me please?
---------- Post added at 01:25 AM ---------- Previous post was at 01:09 AM ----------
arkh01droid said:
Im going to reply to my own post
i abandoned the ADB method and went whit another strategy.
I was able to boot windows bios, change boot priority back to windows.
From windows i installed a tool to mount and browse android partition. Edited back build.prop.
Quick reboot and back in android!
Lesson learned. Thank you anyway and please forgive me for this post!
Click to expand...
Click to collapse
frieeeeeend please tell me the tool to do that, please please !!!!!!
gomexpeed said:
ok my dear friend, I change the app_process to app_process.xposed-bak and then no more root, so no more rename, so have a brick, can u help me please?
---------- Post added at 01:25 AM ---------- Previous post was at 01:09 AM ----------
frieeeeeend please tell me the tool to do that, please please !!!!!!
Click to expand...
Click to collapse
Hi,
There is several tool for this, personaly I'm using this one:
Paragon ExtFS for Windows
It is free for personal usage.
I wan to buy this tablet and install xposed and xmultiwindow on it... does it work? is it easy to factory reset the android rom if something goes wrong?
DhaniBaho said:
Aha... Finally found a place to discuss this chuwi vi8, a super cheap but amazing tablet LOL
B. Xposed Framework
1. Download/Install Terminal Emulator from play store
2. Download/Install Root Explorer from anywhere LOL
3. Download/install Xposed Framework 2.6.1, install the framework but don't reboot
4. With root explorer go to /system/bin/ rename app_process to app_process.xposed-bak, then rename rename app_process.orig to app_process
5. Open Terminal Emulator
type "su" without quote then execute
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
type "chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset" without quote then execute
6. Reinstall the framework then reboot
Sorry for my bad English [emoji1] [emoji1] [emoji1]
Click to expand...
Click to collapse
Hi, looking at the above and had a question. That seems like a longer process than on "normal" devices, ie the Terminal Emulator steps. What is the purpose of those steps? Does this mean I will have to repeat this any time I upgrade Xposed? I am curious as to why it differs from a normal install on a rooted device.
arkh01droid said:
Im going to reply to my own post
i abandoned the ADB method and went whit another strategy.
I was able to boot windows bios, change boot priority back to windows.
From windows i installed a tool to mount and browse android partition. Edited back build.prop.
Quick reboot and back in android!
Lesson learned. Thank you anyway and please forgive me for this post!
Click to expand...
Click to collapse
what did you install in windows to mount and browse android partition. Thanks
bindassever said:
what did you install in windows to mount and browse android partition. Thanks
Click to expand...
Click to collapse
Try this... http://www.paragon-software.com/home/extfs-windows/
Sent using D-Vi8™
hi
I am moderator of a Chinese tablet french site http://tablette-chinoise.net/chuwi-serie-vi-f240
If you have problems with this tablet and want to help no worries
I perceives that there is still a new bios and also another version of android in Vi8 Dual OS since 201504
Let me explain how I came to realize
s / n q32g22150304xxx
bios D86JUBNR01
you can not install on GooglePlay, or manually
Foursquare Google+ and many other applications
s / n q32g22150401xxx
bios D86JHBNR01
Foursquare Google+ OK !
here installation possible also the splash screen before botanimation android was different
but the person who has met with problems with the windows has to reinstall Android repartitioning
My question is the following
Which link the new bios D86JHBNR01 and new ANDROID !!!
Who has the upper android version 20150123
Check your build.prop please
keep me informed
Hey guys.
I've just bought Lenovo A5000. It's a new device. So i dont know how to root it. Are there any apps to handle this problem? i cant stand to not root my device. i cant make it easy to use.
What about "framaroot"? Can this app do it?
Tkdh1986 said:
Hey guys.
I've just bought Lenovo A5000. It's a new device. So i dont know how to root it. Are there any apps to handle this problem? i cant stand to not root my device. i cant make it easy to use.
What about "framaroot"? Can this app do it?
Click to expand...
Click to collapse
I'm not sure whether or not Framaroot is effective. But I am sure that a good way to root a device is to unlock your bootloader and use ODIN. There are various instructions on how to install it on different devices.
Just got mine too. Love this phone! I can get 24 hours of usage in one full charge! Unfortunately still no tutorials on rooting this device
yes ! still waiting for the root tools ...
This site says it's just done via app? Not sure how legit this is. http://www.how-to-root.club/2015/04/lenovo-a5000-7167.html
Root Lenvo A5000 MTK6582 4.4.2
Root Lenvo A5000 MTK6582 4.4.2
Hi, now i've root my device Lenovo A5000.
I've used this tool with my pc. Success 100%.
h_t_t_p://vrootdownload.com/iRoot/#.VUzGO09839w
h_t_t_p://vrootdownload.com/iRoot/#.VUzGO09839w
use the pc to root your device!
after root success, use CH Play to install SupperSU
Good luck!
sucesfull root
Today managed to sucesfully root the phone so no more ads or camera shutter sounds.
You need to use kingroot apk (framaroot didn't worked). I know, it is chinese stuff filled with all sort of additional apps that are installed during rooting process but you have to bear with them for a few minutes.
I downloaded it from here: arykblog.info/2015/04/how-to-root-lenovo-a5000.___html (remove the ___ from link)
After installing the kingroot app and rooting the phone with it, I followed this tutorial
w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.___html (remove the ___ from link)
you have to extract the Replace_Kingroot_With_SuperSU.zip into your "\sdcard" folder (when browsing phone in windows explorer, you are by default in \sdcard folder)
It will look like this \sdcard\mrw\root.sh
Use the mentioned console app on your android
First start root shell by calling "su"
Then you have to make system read-write, by calling "mount -o remount,rw /system"
Then enter that mrw folder "cd \sdcard\mrw" and run "sh root.sh"
After a few seconds it should start SuperUser app and it will prompt you to replace binaries, use the "normal" way.
After success, reboot the phone and SuperSU should be still working and no kingroot app present.
(reboot also restores mount status of system folder)
PS: make sure you do not have installed the SuperUser app before using this process
PSS: make sure you place the mrw folder is in correct directory and that you succeed in one run, or you have to repeat it again from installing kingroot
Important note: DO NOT INSTALL FIRMWARE UPDATE WITH ROOT. You will brick the phone, tested :crying:
If you brick the phone, you have to flash official ROM.
You will have to install latest SP Flash Tool and drivers for your phone bootloader (that unknown device which appears for a few seconds after connecting you turned off phone to PC)
androidxda.com/smart-phone-flash-tool
mediafire.com/download/g4dn7yh54savq90/Lenovo_A5000_usb_driver.rar
Then download from a russian site the official ROM (warning, it contains additional russian apps that you will have to remove)
Can't post the links, so google "A5000_S025_150121_ROW" and look for lenovo-forums.ru and bymobyle.by (1+GB files)
Then extract the ROM somewhere, open flash tool, click on scatter loading and find the "MT6582_Android_scatter.txt", open it and click Download.
Now connect your phone when turned off via USB and it should flash the ROM. Afterwards your phone should be able to start.
PS: It takes quite a while after the flash to start.
I hope you find this tutorial useful.
There is a very easy and simple way to root your lenovo a5000 By using king root app See here How
what is CH?
great tutorial,have you tried any customs roms?because the official sucks
i have a carrier-modified lenovo a5000 and i want to return it to stock. which files should i check on spflash tool to make it stock?
How to root lenovo a5000 kitkat 4.4.2?Is it kingroot safe?
rastikzzz said:
Today managed to sucesfully root the phone so no more ads or camera shutter sounds.
You need to use kingroot apk (framaroot didn't worked). I know, it is chinese stuff filled with all sort of additional apps that are installed during rooting process but you have to bear with them for a few minutes.
I downloaded it from here: arykblog.info/2015/04/how-to-root-lenovo-a5000.___html (remove the ___ from link)
After installing the kingroot app and rooting the phone with it, I followed this tutorial
w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.___html (remove the ___ from link)
you have to extract the Replace_Kingroot_With_SuperSU.zip into your "\sdcard" folder (when browsing phone in windows explorer, you are by default in \sdcard folder)
It will look like this \sdcard\mrw\root.sh
Use the mentioned console app on your android
First start root shell by calling "su"
Then you have to make system read-write, by calling "mount -o remount,rw /system"
Then enter that mrw folder "cd \sdcard\mrw" and run "sh root.sh"
After a few seconds it should start SuperUser app and it will prompt you to replace binaries, use the "normal" way.
After success, reboot the phone and SuperSU should be still working and no kingroot app present.
(reboot also restores mount status of system folder)
PS: make sure you do not have installed the SuperUser app before using this process
PSS: make sure you place the mrw folder is in correct directory and that you succeed in one run, or you have to repeat it again from installing kingroot
Important note: DO NOT INSTALL FIRMWARE UPDATE WITH ROOT. You will brick the phone, tested :crying:
If you brick the phone, you have to flash official ROM.
You will have to install latest SP Flash Tool and drivers for your phone bootloader (that unknown device which appears for a few seconds after connecting you turned off phone to PC)
androidxda.com/smart-phone-flash-tool
mediafire.com/download/g4dn7yh54savq90/Lenovo_A5000_usb_driver.rar
Then download from a russian site the official ROM (warning, it contains additional russian apps that you will have to remove)
Can't post the links, so google "A5000_S025_150121_ROW" and look for lenovo-forums.ru and bymobyle.by (1+GB files)
Then extract the ROM somewhere, open flash tool, click on scatter loading and find the "MT6582_Android_scatter.txt", open it and click Download.
Now connect your phone when turned off via USB and it should flash the ROM. Afterwards your phone should be able to start.
PS: It takes quite a while after the flash to start.
I hope you find this tutorial useful.
Click to expand...
Click to collapse
THANKS A BUNCH!!!
After i have flashed it back to stock version, do i need to reinstall custom recovery or is it still bootable?