Related
Introduction
Since I'm not a ROM developer or Java coder, I thought I could help by donating this little tool, that was origionally written for my personal use, for all to utilize in an attempt to give back to this community.
WinFastboot - Flash Recovery has been renamed to Android Flash Recovery
Requirements
- A PC running Microsoft Windows. 32 or 64 bit.
- Correct Android USB drivers installed for your device
- An Android powered device with debugging enabled
Description
Android Flash Recovery is a Windows GUI front-end for the Windows version of fastboot. This particular tool is designed to simplify flashing an Android device's recovery partition. Android Flash Recovery WILL NOT repair a bricked device. The device must be able to be put in to fastboot mode for Android Flash Recovery to be able to work. Since Android Flash Recovery is just a GUI for fastboot, the same applies for fastboot.
Beware. Android Flash Recovery unfortunately will not work with every single Android device. I am however, attempting to make strides in that direction
Installation
Installing Android Flash Recovery is simple too. Just unzip to a folder of your choice and then execute androidflashrecovery.exe, assuming your device drivers are already installed.
If you haven't installed your drivers yet, then they will need to be installed before using Android Flash Recovery as your device won't be detected.
If you are an LG user, the latest LG United Mobile USB drivers are are in a sub-folder of Android Flash Recovery, titled "USB". If you have attempted to install your USB drivers in the past with no success or with errors, go to Control Panel and uninstall any LG driver setup program you may find. Reboot your computer. Run the driver installation program. Make sure your device is NOT connected to the PC. Reboot your PC once more. Enable USB debugging on your device the power it off, trust me. After your PC has fully booted, plug your device into a USB port. Do not plug in to a USB hub. Windows may detect your device at this point and begin searching for or installing drivers. Power on your phone. Wait for all devices to be installed. For Froyo and GingerBread phones this is normally 5 or 6 devices. For ICS and JB this is 4 devices I believe. The important one is 'Android Single Sooner Interface'. This won't be installed if USB debugging isn't enabled on the device. Now your drivers should be installed and you can use Android Flash Recovery at your leisure.
Using
Using Android Flash Recovery is even easier than installing it. Browse for the recovery you wish to flash and press the 'Flash Recovery' button. NOTE: In order for Android Flash Recovery to flash, your device MUST BE in fastboot mode.
Included with Android Flash Recovery are the adb binaries with support libraries as well as fastboot. Android Flash Recovery is written to use the binaries included in it's package. Also included is the driver setup application for LGE Android Mobile devices ( United Mobile USB Drivers ).
Post questions here. I will try to answer them as I can. I have a regular full-time job so I am not a full-time developer. You may also email me at [email protected]. Set your subject line to "Android Flash Recovery". If the subject line isn't correct your email will be ignored.
Download
Latest version here -> Android Flash Recovery
Reserved...
Removed
Since I have had zero feedback about my previous post, I've decided to rename "WinFastboot - Flash Recovery" to "Android Flash Recovery". I'd also like to mention that it will be updated later this evening. I have a few more minor things to wrap up and then I'll upload and post a new link.
I've had quite a few downloads, so I know my app is being tried. I really need some feedback folks. If you have issues with, a feature request, or even a simpe UI improvement/suggestion. I'm also curious as to the types of devices that my app is being used in conjunction with. What works and what doesn't.
Thanks.
if a device is able to go into recovery mode, does it mean this app is applicable?
oldsap said:
if a device is able to go into recovery mode, does it mean this app is applicable?
Click to expand...
Click to collapse
Unfortunately no. The device must be in fastboot/bootloader mode.
bill.weckel said:
Unfortunately no. The device must be in fastboot/bootloader mode.
Click to expand...
Click to collapse
well there goes every samsung device that isnt a nexus
jamcar said:
well there goes every samsung device that isnt a nexus
Click to expand...
Click to collapse
There is a way to install a ROM with adb so I'd say it may be possible to do a recovery too. I'll do some investigating. Might be able to do something.
Sent from my LG-P506 using xda app-developers app
bill.weckel said:
There is a way to install a ROM with adb so I'd say it may be possible to do a recovery too. I'll do some investigating. Might be able to do something.
Sent from my LG-P506 using xda app-developers app
Click to expand...
Click to collapse
could you keep us posted on you research?
jamcar said:
could you keep us posted on you research?
Click to expand...
Click to collapse
More than happy to. I've have a little more to do as far as completing this piece of software then I'll look into using adb as an alternative for the purpose of this thread and possibly for devices such as yours that do not have access to the bootloader/fastboot mode for whatever reasons.
bill.weckel said:
More than happy to. I've have a little more to do as far as completing this piece of software then I'll look into using adb as an alternative for the purpose of this thread and possibly for devices such as yours that do not have access to the bootloader/fastboot mode for whatever reasons.
Click to expand...
Click to collapse
for samsung phones you would look into using the dd if=[recoveryimg] of=[recovery partition] to copy the recovery image to the recovery partition. this is how you manually do a samsung phone's recovery flash. so a way to implement this into the app for, let's say the GS3 would be
adb push [user selected recovery img] \sdcard\recovery.img ( or some other way of copying the user selected recovery img to the root of the sdcard )
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
and that will flash the recovery to the gs3.
of course the main issue is that the recovery partition is not always the same name of the block so /dev/block/mmcblk0p18 will not always be the name of the recovery block. The way to overcome this ( i think ) would be to program in a part of the app that reads in Build.MODEL which will give you the model device the user has plugged in and then you can determine from there what the block title is by programming in the blocks for each samsung phone model. To make it simpler befoer you do that, filter out stuff that can just be fastbooted...something like...
if(Build.Manufacturer == 'HTC' || Build.Manufacturer == 'Motorola' ||... etc)
// just do fastboot
else
{
switch(Build.MODEL) { // if switching strings is supported in Android ( it was introduced in java se 7 ) otherwise use enums
case GS3:
block = 'mmcblk0p18';
break;
}
//move the file to the SD card if the model is supported
//do the su and dd command here
}
anyways...im bored at work so just figured ide give my 2 cents, not sure how much support you wanna give this haha...hope this helps
For me it's not working i am in Fastboot mode but winfastboot tells me i am not ... it recognized that the device is connected but not in fastboot mode even tough on my phone it says "fastboot usb" :\
Phone : HTC Wildfire
s-off
radio 3.35.15.31
ROM : CM9
Yeah i just saw "ICS( 4.0.* ) and JB( 4.1.1 ) devices are not detected correctly by the driver software. Some devices may not get installed." in the readme ...
Cant you do anything about this to fix it ?
That's strange. I figured there would be some devices that this wouldn't work for. Are your USB drivers installed correctly? All other fastboot screens say "Fastboot mode started\nudc_start()". I will look into it tho.
Sent from my LG-P506 using xda app-developers app
Updated. Check first post for downloads
Yep , USB drivers installed correctly , other things worked everytime i tried to do something ...
Commandox said:
Yep , USB drivers installed correctly , other things worked everytime i tried to do something ...
Click to expand...
Click to collapse
I'm looking into a workaround for your HTC device and from what I've heard I may need one for some Samsung devices as well. I'm sorry the update I posted doesn't contain this workaround. It is something that I will look into. I do have a regular full-time job tho, so it may take a few days for me to figure out what I need to do, how to do it, then writing the code for it.
As for the fixing how device drivers are installed, that's not something that I can fix. I believe it is actually an issue with the ICS and JB ROMs themselves.
For those of you who are having issues with Android Flash Recovery, I really need the names of your recovery mount points. HTC owners and Samsung GS3 owners for sure.
I can't fix these issues without your input folks. I'd really like to be the guy that has the one universal recovery tool that no one can live without. Scratch my back and I'll scratch yours.
bill.weckel said:
More than happy to. I've have a little more to do as far as completing this piece of software then I'll look into using adb as an alternative for the purpose of this thread and possibly for devices such as yours that do not have access to the bootloader/fastboot mode for whatever reasons.
Click to expand...
Click to collapse
we have download mode instead of fastboot/bootloader we can use ODIN, samsungs recovery tool (tool not mode, meaning the program ODIN is on a computer)
EDIT: sprint galaxy s III is /dev/block/mmcblk0p18
I believe I've stumbled upon a universal method to check a device for mount points. I'm going to throw together a little test app and then upload here for y'all to test out if you would. If my suspicions are correct, I will then be most able to write the
universal recovery tool for windows.
@jamcar
Thanks for your response. I've actually heard of ODIN.
bill.weckel said:
For those of you who are having issues with Android Flash Recovery, I really need the names of your recovery mount points. HTC owners and Samsung GS3 owners for sure.
I can't fix these issues without your input folks. I'd really like to be the guy that has the one universal recovery tool that no one can live without. Scratch my back and I'll scratch yours.
Click to expand...
Click to collapse
For Galaxy Note International (GT-N7000) it should be - /dev/block/mmcblk0p6
i just need to confirm that
Greetings,
I've been using these forums silently for quite some time, but now need help with two devices not covered here.
I have a client who has two devices he'll be putting into service that require a custom branded boot animation. I cannot find any documentation on rooting nor patching these devices with the custom animations, and am hoping the fine gurus of this board can help.
The devices are the Motorola MC40 – “Hybrid” Gingerbread (2.3) and the DAP M4305 (2.3)
Does anybody have any experience rooting / patching a boot animation to these devices?
bounty available
If you are capable of overcoming this task, I will award a bounty. Just specify your costs via PM.
mahngiel said:
Greetings,
I've been using these forums silently for quite some time, but now need help with two devices not covered here.
I have a client who has two devices he'll be putting into service that require a custom branded boot animation. I cannot find any documentation on rooting nor patching these devices with the custom animations, and am hoping the fine gurus of this board can help.
The devices are the Motorola MC40 – “Hybrid” Gingerbread (2.3) and the DAP M4305 (2.3)
Does anybody have any experience rooting / patching a boot animation to these devices?
Click to expand...
Click to collapse
mahngiel said:
Greetings,
I've been using these forums silently for quite some time, but now need help with two devices not covered here.
I have a client who has two devices he'll be putting into service that require a custom branded boot animation. I cannot find any documentation on rooting nor patching these devices with the custom animations, and am hoping the fine gurus of this board can help.
The devices are the Motorola MC40 – “Hybrid” Gingerbread (2.3) and the DAP M4305 (2.3)
Does anybody have any experience rooting / patching a boot animation to these devices?
Click to expand...
Click to collapse
i dont know about that other DAP M4305 but for the hybrid you should be able to use gingerbreak with this since its gingerbread, might work with the other device since its gingerbread also, i have never heard of it. heres a link-
http://forum.xda-developers.com/showthread.php?t=1044765 its by chainfire so its safe
dont click on the "GingerBreak_exploit_source_from_APKv1.1.zip" get the apk on the next post
as for your boot animation im not sure what you want. theres a app that i know of on the play store that can change the boot animation if your rooted.
cheers, good luck! (if they possibly work replie back and i should be able to start a thread for other People)
Edit: oh one more methood i forgot about http://forum.xda-developers.com/showthread.php?t=803682
i would use the gingerbreak methood first thought
Thanks for the tips, Trozzul.
I'll give those two methods a shot - should get the devices by end of week.
Regarding the boot ani, I'd like to not rely on a Play app, since these devices will be given to employees who shouldn't have access to this feature once deployed.
We previously used Anbech's method on a batch of S3s, and were hoping to find a similar approach. We're not android devs, but we can follow directions - so don't know if this approach would work across different models / manufacturers.
Again, thanks for the heads up. I'll report back once I've given GingerBreak a shot - but hopefully there will be more suggestions in the interim.
mahngiel said:
Thanks for the tips, Trozzul.
I'll give those two methods a shot - should get the devices by end of week.
Regarding the boot ani, I'd like to not rely on a Play app, since these devices will be given to employees who shouldn't have access to this feature once deployed.
We previously used Anbech's method on a batch of S3s, and were hoping to find a similar approach. We're not android devs, but we can follow directions - so don't know if this approach would work across different models / manufacturers.
Again, thanks for the heads up. I'll report back once I've given GingerBreak a shot - but hopefully there will be more suggestions in the interim.
Click to expand...
Click to collapse
anytime i hope they work! Gingerbreak SHOULD not Brick your phones im not sure how stable to other methood is, please remeber to write back if they work!
I currently managed to root my Motorola MC40 with kitkat installed. I used Kingo Root, and did it from the computer. I have also installed busybox.apk and other APKs using the adb command prompt from my pc.
bigwhat82334 said:
I currently managed to root my Motorola MC40 with kitkat installed. I used Kingo Root, and did it from the computer. I have also installed busybox.apk and other APKs using the adb command prompt from my pc.
Click to expand...
Click to collapse
And how were you able to connect it to your PC?
I bought mine from a friend that used to work at Walmart. I was able to factory reset it but the Walmart information and everything is still on it. When I try to connect it to my laptop it won't even show up. I went to the Motorola website and downloaded the drivers for it but sill no luck.
I'm guessing if I can get it connected to my laptop I might be able to root it using the same method you did, and be able to put TWRP on it so I could boot it up in recovery mode and completely wipe the whole partition.
Any suggestions?
Bump on this thread
Another bump?
Removing Walmart Apps from MC40
I bought an MC40 from Ebay - I used a download of the MC40 Jellybean restore zip and used ADB Sideload to update the firmware - after that I have stock AOSP firmware. - PM me if you need the zip.
I want to be able to use Speech to Text but for that I have to get Google Mobile Services / App Store installed - it is grayed out in the settings.
I do not have a custom boot loader but I just downloaded the zip from opengapps.org - I attempted adb sideload zip after rebooting the device in recovery mode -
That did not work.
Does any one know if a custom boot loader that could sideload the OpenGapps Package to this device?
Thanks!
can i get the .zip file please?
yngdrum said:
I bought an MC40 from Ebay - I used a download of the MC40 Jellybean restore zip and used ADB Sideload to update the firmware - after that I have stock AOSP firmware. - PM me if you need the zip.
I want to be able to use Speech to Text but for that I have to get Google Mobile Services / App Store installed - it is grayed out in the settings.
I do not have a custom boot loader but I just downloaded the zip from opengapps.org - I attempted adb sideload zip after rebooting the device in recovery mode -
That did not work.
Does any one know if a custom boot loader that could sideload the OpenGapps Package to this device?
Thanks!
Click to expand...
Click to collapse
MC40 jellybean restore zip file
I would like a copy of the MC40 Jellybean restore zip file, please.
yngdrum said:
I bought an MC40 from Ebay - I used a download of the MC40 Jellybean restore zip and used ADB Sideload to update the firmware - after that I have stock AOSP firmware. - PM me if you need the zip.
I want to be able to use Speech to Text but for that I have to get Google Mobile Services / App Store installed - it is grayed out in the settings.
I do not have a custom boot loader but I just downloaded the zip from opengapps.org - I attempted adb sideload zip after rebooting the device in recovery mode -
That did not work.
Does any one know if a custom boot loader that could sideload the OpenGapps Package to this device?
Thanks!
Click to expand...
Click to collapse
I ffigured it out. i was able to get rid of walmart stuff and installed Kit Kat 4.4.4
ieatpinktacoz said:
I ffigured it out. i was able to get rid of walmart stuff and installed Kit Kat 4.4.4
Click to expand...
Click to collapse
I have installed 4.4.4, I cannot perform an enterprise format...
Did you also clean the enterprise partition? If so how , please.
try this
.zebra.com/us/en/support-downloads/software/operating-system/mc40-operating-system-for-voice-skus.html
yngdrum said:
Removing Walmart Apps from MC40
I bought an MC40 from Ebay - I used a download of the MC40 Jellybean restore zip and used ADB Sideload to update the firmware - after that I have stock AOSP firmware. - PM me if you need the zip.
I want to be able to use Speech to Text but for that I have to get Google Mobile Services / App Store installed - it is grayed out in the settings.
I do not have a custom boot loader but I just downloaded the zip from opengapps.org - I attempted adb sideload zip after rebooting the device in recovery mode -
That did not work.
Does any one know if a custom boot loader that could sideload the OpenGapps Package to this device?
Thanks!
Click to expand...
Click to collapse
I need the zip file for mc40
I need a copy of the firmware for mc40 if anyone has one please
I am in the same boat.
Needing the recovery image as Zebra is not allowing downloads of them without an active support contract, which I even had quoted and cheapest I could get was $225. This is a $40 device... stupid.
If anyone could share the file it would be greatly appreciated.
Hello all.
FIrst, I am not new to this. Just let me get that out in the open. I've done custom ROMs and recoveries on four devices including two HTCs. However I'm new to Asus and this is my first tablet.
So, what is going on is that I have an Asus Memo Pad ME301T. It is rooted, bootloader is unlocked (confirmation appears in upper left corner at boot). However, it will not install the TWRP recovery when I try to push it from my PC. I try to choose the recovery icon on the bootloader, and it shows the fallen android with an error message when it tries to open. I have followed the directions and executed the proper commands from the platform-tools folder in the Android SDK. I thought maybe I could try downloading the BLOB file directly to the device's emulated sdcard and installing it via a terminal command, however I do not know what commands I should use from a terminal emulator. I'm sure it's something simple I'm missing. I am trying to install the TWRP 2.5.0 recovery because it seems to have the highest success rate, and I am currently on the 10.6.1.15.ww stock ROM.
If someone familiar with these tablets could go through the process with me, step by step, one more time (don't just link me to a thread unless it's clear, concise, and exactly what you would do in this situation) or provide the commands so I can try it from the terminal within the tablet, I would appreciate it. When I've had problems in the past it's been something simple most of the time or an extra step I need to do so hopefully one of you can tell me what I'm missing.
Thanks!
asilaydyingdl said:
Hello all.
FIrst, I am not new to this. Just let me get that out in the open. I've done custom ROMs and recoveries on four devices including two HTCs. However I'm new to Asus and this is my first tablet.
So, what is going on is that I have an Asus Memo Pad ME301T. It is rooted, bootloader is unlocked (confirmation appears in upper left corner at boot). However, it will not install the TWRP recovery when I try to push it from my PC. I try to choose the recovery icon on the bootloader, and it shows the fallen android with an error message when it tries to open. I have followed the directions and executed the proper commands from the platform-tools folder in the Android SDK. I thought maybe I could try downloading the BLOB file directly to the device's emulated sdcard and installing it via a terminal command, however I do not know what commands I should use from a terminal emulator. I'm sure it's something simple I'm missing. I am trying to install the TWRP 2.5.0 recovery because it seems to have the highest success rate, and I am currently on the 10.6.1.15.ww stock ROM.
If someone familiar with these tablets could go through the process with me, step by step, one more time (don't just link me to a thread unless it's clear, concise, and exactly what you would do in this situation) or provide the commands so I can try it from the terminal within the tablet, I would appreciate it. When I've had problems in the past it's been something simple most of the time or an extra step I need to do so hopefully one of you can tell me what I'm missing.
Thanks!
Click to expand...
Click to collapse
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
lj50036 said:
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
Click to expand...
Click to collapse
Exactly. I open a command line on the folder, renamed the file to twrp.blob, and then I I am using the following:
ADB devices
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
I think the problem is really simple though. I think for some reason, the tablet and the computer are not communicating via fastboot. I.e. the info is not actually getting through the USB cable to the tablet when in fastboot. I have android debugging enabled and all that good stuff. So my assumption is this is a driver issue or an extra step needs done on the tablet to get the communication working. All drivers did install properly according to the PC. Maybe it's even the USB port on the tablet itself and I need to exchange it. But I can transfer files like it's a media device, so I doubt that's it.
Any thoughts?
***UPDATE***I checked settings in SuperuserSU and it turns out I did not have root enabled at boot. Enabled it and it connected to the PC as "fastboot". Commands are still not getting sent to the device. Whenever I try to send the blob, it always says "0 KB" and the device just freezes. Perhaps I need a different command or fastboot on the PC isn't initializing correctly? Or maybe there is a setting on my device that needs tweaked yet?
Thoughts?
I think I know what the problem is. Someone using the TF300T tablet had the exact same problem I'm having. Turned out it was their rooting method. I used KingoROOT despite a few murmurs of it causing issues because I was looking for results quickly not a quality job like I should have been. SuperuserSU has been behaving weirdly, as well as my USB android keyboard and a few other quirks in the OS since I did the root, so it makes sense. I will have to use the KingoROOT app and undo the root, and retry with motochopper. KingoROOT must not have rooted all directories. If that doesn't work, I will probably have to do a full restore to stock settings by re-installing a stock Asus ROM and start fresh.
lj50036 said:
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
Click to expand...
Click to collapse
Did more work and research. I did actually have the improper drivers installed. I installed them from Asus, so that is fixed. But the problem remained. After further research, it came down to version builds and numbers. I am using a version of Asus' firmware that isn't compatible with the operations I'm trying to perform. I am using version 10.6.1.15. TWRP 2.5.0.0 and newer can NOT be installed on any Asus tablet running anything less than 10.6.1.27. There is something about the bootloader, encryption or a security setting that prevents data from being pushed via a fastboot command. So I now have a Christmas project, which is update to a newer version of Asus firmware.
I found my solution here, in a thread filled with people having the exact same issue:
http://forum.xda-developers.com/showthread.php?t=2179874&page=3
And directions for the fix here:
http://forum.xda-developers.com/showthread.php?t=2187982
Hope my work helps someone else.
I just bought this tablet on amazon flash sale and I can't find any other development thread so I decided to make one.
Note: All of these are tested on the A7-30F Variant. Only Kingroot is tested and working for all variants.
1. Root
Root 4.4.2 and 5.0.1 (Make sure to use the desktop version):
http://kingroot.net/
Replace Kinguser with Super Su:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
2. Recovery
Thanks to @SpontaneousMixx for finding this
Easy Magic TWRP Installer
Download
ONLY FOR 4.4.2
1. Extract TWRP.zip
2.Run as administrator
3.Select auto mode
4. Let it run until you have to select screen resolution
5. Select a Screen res lower then 600x1024
6. select no for mirrored recovery
7. Finished and you now should be booted in TWRP Recovery
3. Roms
Stock Rom 4.4.2 (Thanks @gmincca )
4.4.2 OTA files
5.0.1 OTA Files
Use ADB sideload to install
Note: Android file host does not have the A7-30 is its database so all files uploaded will say its for the 9770
4. Boot Animations
Google Play bootup and shutdown animations
Note: Android file host does not have the A7-30 is its database so all files uploaded will say its for the 9770
5. Accessories
Fintie Lenovo Tab 2 A7-30 Case (Good build quality for $10 and still holding up after three months)
I will give this a whirl this weekend if I can unlock the bootloader
http://forum.xda-developers.com/showthread.php?t=1943625
Nickco43 said:
I just bought this tablet on amazon flash sale and I can't find any other development thread so I decided to make one.
1. Root
On another thread someone confirmed Kingo root worked for 4.4.2 (EDIT: Confirmed working)
http://www.kingoapp.com/
2. Recovery
No know recoverys
3. Roms
No know Roms
Click to expand...
Click to collapse
Just got this same Tab for my son & have been looking around for the best ways to root. It's actually a nice little tablet. For $65 I'm quite impressed.
Couple questions for you if I may.
-Does this download have any prerequisite downloads, surveys or ads before it's installed on my PC? You know, junk & not just the program.
-Which super user app is installed?
Kingo root comes with all the files you need with no surveys or bloatware. It installs its own super user program but I deleted it wit ha system app remover and installed super su from the play store. If you can, after you root your tablet can you pull the stock lenovo launcherHD and upload it to here. I deleted mine and you need it to change the lock screen wallpaper.
hI guys!
Good to see topic about our tab 2. Small question - any1 of you got lolipop update already? Week ago Lenovo said it's ready... I have so annoying touch bug and hope update gonna fix this.
The update is not out yet but lenovo said late summer so I would think it would come out sometime in august. Once it comes out can someone try kingo root on it, I'm not updating if I can't get root.
Nickco43 said:
The update is not out yet but lenovo said late summer so I would think it would come out sometime in august. Once it comes out can someone try kingo root on it, I'm not updating if I can't get root.
Click to expand...
Click to collapse
Lolipop is out, but not in every region yet. Sadly, not in mine too (Poland).
forums.lenovo.com/t5/Lenovo-Android-based-Tablets/Lenovo-Tab-2-A7-30GC-Touch-Input-Problem/m-p/2117299/highlight/true#M24873
Well I tired to get a recovery on the tablet but failed. Mtk tool and sb flash didn't work since the tablet is write protected and also I don't think is works for media tek 8 series chips like it does with 6 series chips. I was going to build twrp but you need a unlocked bootloader to flash it and when I run fastboot OEM unlock it returns three dots. I think my fastboot drivers got messed up after I unhard bricked my OnePlus and that's causing it to return 3 dots. I will try another pc and report back.
Nope it still returned the three dots. Well I'm out of ideas to unlock the boot loader. Maybe a more experienced dev can do it or we can ask lenovo nicely.
Bootloader
According to a thread on the lenovo community... the device has a mediatek proceesor, which can be flashed without unlocking anything using their SP flash tool. Only downside is any custom roms would have to be built for mediatek and using a "scatter" file.
Thread: forums.lenovo.com/t5/Lenovo-Android-based-Tablets/how-to-unlock-the-Lenovo-A3000-bootloader/m-p/1588718/
Stock Rom: androidxda.com/download-lenovo-stock-rom-models
Flash Instructions: androidxda.com/flash-stock-rom-using-smart-phone-flash-tool
The rom's source is also available on the Lenovo support site.
Unfortunately, I'm not expert at anything to make anything happen with this information.
---------- Post added at 08:48 PM ---------- Previous post was at 08:41 PM ----------
Then again, all that may have nothing to do with the A3300, since it's all based on the A3000... but same processor type? doesn't seem like mediatek has any info on their site about it either.
TWPR Success
Nickco43 said:
Well I tired to get a recovery on the tablet but failed. Mtk tool and sb flash didn't work since the tablet is write protected and also I don't think is works for media tek 8 series chips like it does with 6 series chips. I was going to build twrp but you need a unlocked bootloader to flash it and when I run fastboot OEM unlock it returns three dots. I think my fastboot drivers got messed up after I unhard bricked my OnePlus and that's causing it to return 3 dots. I will try another pc and report back.
Click to expand...
Click to collapse
It was like pulling teeth, but I FINALLY got TWRP running on this tablet. It was EXTRA painful for me because the tool I use asks you to select your device resolution and like a dummy, I actually picked 1024x600 (which is the device's resolution in landscape, but not portrait mode.) When the thing finished installing TWRP and booted up, I was locked out of the tablet because the touch elements for twrp to actually restart or even unlock the device ran off the screen making using them impossible. I had to wait seven hours for the battery to finally die before I could access the thing again, (thanks for skipping the reset button on the a7-30F, Lenovo!)
In a nutshell though, I started with Kingo Root, which was successful, and then used Easy Magic TWRP Installer made specifically for mediatek devices, found on another xda thread. JUST MAKE SURE that when it says "Unable to detect your device resolution" that you choose the highest res below 600x1024 (it was like 546x964 or something like that. I can't remember exactly.) After I had a working TWRP, I switched to chainfire's SuperSU
I hope this helps.
@SpontaneousMixx Nice Adding it to master list
I'm going to try to port cm 12.1
Nickco43 said:
I'm going to try to port cm 12.1
Click to expand...
Click to collapse
Let me know how it works...
The biggest challenge with installing a ROM methinks though, is that you have to use the SP Flash tool to actually upload a rom. I could be wrong... I haven't tried through TWRP. It took me so long just to fix my screw up that I put it down for a while. The SP Flash Tool needs some kind of Android Scatter file, (probably a Lenovo specific MT8127_Android_Scatter.txt), which I have been unable to find or figure out from the source. I'm just not that talented.
It IS entirely possible that just applying a rom via TWRP will work fine, but it's also likely that the system will bark at you. I'm curious to see what happens.:good:
Usually you can get the scatter file for mediatek device with mkt tools but the option is blocked out when I plug the tablet in. I downloaded the cm source but I ran into my first hiccup when I use cat /proc/mtd to extract the boot.img it won't show any of the partitions.
Nickco43 said:
Usually you can get the scatter file for mediatek device with mkt tools but the option is blocked out when I plug the tablet in. I downloaded the cm source but I ran into my first hiccup when I use cat /proc/mtd to extract the boot.img it won't show any of the partitions.
Click to expand...
Click to collapse
Yeah, I think the mtk tools app is unable to access the root shell on the device for some reason, keeping it from being able to grab the scatter. I'm not sure why it's not working though. I got SuperSU installed and running on the tab, but that application still fails to get to the root shell.
I can't find any time to work on porting cm to the A7-30; Can anyone else give it a shot.?
Nickco43 said:
I can't find any time to work on porting cm to the A7-30; Can anyone else give it a shot.?
Click to expand...
Click to collapse
I would love to, since I have downloaded the source... unfortunately I don't have the technical know-how to really work on it.
I've got the scatter file
SpontaneousMixx said:
Yeah, I think the mtk tools app is unable to access the root shell on the device for some reason, keeping it from being able to grab the scatter. I'm not sure why it's not working though. I got SuperSU installed and running on the tab, but that application still fails to get to the root shell.
Click to expand...
Click to collapse
I've got the scatter file...
It was dumped into the 'last_log_r' file from my last update. Then today I downloaded the lollipop OTA and pulled the scatter file from that (this is what I attached here).
ammmze said:
I've got the scatter file...
It was dumped into the 'last_log_r' file from my last update. Then today I downloaded the lollipop OTA and pulled the scatter file from that (this is what I attached here).
Click to expand...
Click to collapse
How is the update? Is it worth it?
Purchased a Shield K1 Tablet
Which will arrive this week, and there are things I would like to know about it, i.e notably on whether or not I should unlock and root it, despite the potential risk of doing so.
What I plan on using this for is primarily emulation (Snes through PSP and maybe Dolphin, no idea how well that works yet) That being said, are there things I should do to it?
Do as in, things I can root or flash to give myself the best possible experience, to get the most out of this? I've seen a lot of custom ROMs, Cyanogenmod (which I have on my
Nexus 7 2012, along with a dual boot OS). I have been thinking about having the stock Android 5.1.1, alongside Android 4.1.2 for the sake of Wii remote support since Google
foolishly broke that part of Bluetooth (and the part that never will be fixed again). The problem is, I don't know how hard or cumbersome it would be to do such a thing
without bricking the Shield tablet and ending up with a pricey paperweight. What tutorials, guides, etc should I look into before I consider such an undertaking? I want
to be sure I pick the right files and OS image(s) to install so I can do this right, if that makes sense.
I just bought it too and was coming from a Nexus 7 2012.
Rooted with the latest CM 12.1 nightly, no issues so far.
Wifi is slowish/buggy and the touchscreen has some issues, but afaik these issues are there on stock, too.
Just get the latest CM12.1 from their site, flash it with TWRP. I had issues with open gapps and ended up using CM's gapps.
koichirose said:
I just bought it too and was coming from a Nexus 7 2012.
Rooted with the latest CM 12.1 nightly, no issues so far.
Wifi is slowish/buggy and the touchscreen has some issues, but afaik these issues are there on stock, too.
Just get the latest CM12.1 from their site, flash it with TWRP. I had issues with open gapps and ended up using CM's gapps.
Click to expand...
Click to collapse
Fair enough, and I know that no device is perfect, everything has their own set of issues, so I don't think I'll regret getting a Shield Tablet, that much I know. I was going to get a Samsung Tab E 9.6, but the specs just didn't figure, esp. for someone who wants more power, you know? What about the Android OS ROM you install it with? Should I go with Android 5.1.1 or dual boot it with 4.1.2 instead so I can have Wii remote support? Thanks.
I don't know, that's your choice. I don't have that requirement, so I went with CM12 (5.1.1), single OS
koichirose said:
I don't know, that's your choice. I don't have that requirement, so I went with CM12 (5.1.1), single OS
Click to expand...
Click to collapse
Fair enough, I'll keep looking around the forums to gauge what I need to do. I can't help but feel a bit nervous on rooting and voiding the warranty on a device I just spend 200 bucks on, maybe that's just me though :laugh:
the_randomizer85 said:
Fair enough, I'll keep looking around the forums to gauge what I need to do. I can't help but feel a bit nervous on rooting and voiding the warranty on a device I just spend 200 bucks on, maybe that's just me though [emoji23]
Click to expand...
Click to collapse
Nvidia has stated that it will still honor the warranty despite it being unlocked or rooted in most cases. I'm just gonna guess that unless you accidentally wipe your bootloader, or use an overclocked kernel that fries it you should be good. What they said is if YOU fubar it that voids the warranty, but if it's anything normally covered by warranty your good.
That said, I rooted, unlocked, and installed an oc kernel as well as recovery within an hour of receiving mine and it runs beautifully. Better than pure stock actually.
Sent from my SM-G386T1 using Tapatalk
Exile1975 said:
Nvidia has stated that it will still honor the warranty despite it being unlocked or rooted in most cases. I'm just gonna guess that unless you accidentally wipe your bootloader, or use an overclocked kernel that fries it you should be good. What they said is if YOU fubar it that voids the warranty, but if it's anything normally covered by warranty your good.
That said, I rooted, unlocked, and installed an oc kernel as well as recovery within an hour of receiving mine and it runs beautifully. Better than pure stock actually.
Sent from my SM-G386T1 using Tapatalk
Click to expand...
Click to collapse
Okay, I wasn't 100% sure, only device ever rooted and unlocked was a Nexus 7 2012, never had a problem with it once I got it up and running. I don't feel comfortable with OC at all, as the power is
definitely more than enough for my needs, if that makes any sense. That being said, I don't know what kernel I need since this is my second time ever doing something like this, a little green in the gills so to speak (sad, I know). Anyways, would you guys advise to having dual boot install on this, or just a better 5.1.1 Android ROM than the stock version? I feel a bit overwhelmed at it all, and I don't know what tutorial I should truly follow, that's why I feel overwhelmed, you know?
Reasons for the tablet:
1 - The specs are insanely powerful for emulator apps, my Nexus 7 struggles with even 2D PSP games and some PSX games, lots of stuttering in the audio department, so my primary use is gaming
2 - Multimedia, movies, YT, music and so on
So really, I don't need anything fancy OS wise, just enough to help get the most out of it without having to overclock the hardware. What order would I need to do everything in? Are there good step by step guides for people like me?
http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
INSTALL DRIVER
-enable Developer Options
-enable Debugging Bridge
-do a 'adb devices' and check the dialog on your mobile and allow it 'every time'
-shutdown
-hold Volume down and Powerbutton at same time
if the bootloader showed up
-do a 'fastboot devices' if it shows your device online then
-do 'fastboot oem unlock'
after that you have flash your recovery
go to the directory where the file is and
-do 'fastboot flash recovery your_file_here'
after that you can reboot to bootloader and go to recovery
copy the SuperSu.zip which you downloaded at chainfires site or on xda and push it to your internal memory (/sdcard)
and flash it over recovery.
reboot enjoy!
the_randomizer85 said:
Okay, I wasn't 100% sure, only device ever rooted and unlocked was a Nexus 7 2012, never had a problem with it once I got it up and running. I don't feel comfortable with OC at all, as the power is
definitely more than enough for my needs, if that makes any sense. That being said, I don't know what kernel I need since this is my second time ever doing something like this, a little green in the gills so to speak (sad, I know). Anyways, would you guys advise to having dual boot install on this, or just a better 5.1.1 Android ROM than the stock version? I feel a bit overwhelmed at it all, and I don't know what tutorial I should truly follow, that's why I feel overwhelmed, you know?
Reasons for the tablet:
1 - The specs are insanely powerful for emulator apps, my Nexus 7 struggles with even 2D PSP games and some PSX games, lots of stuttering in the audio department, so my primary use is gaming
2 - Multimedia, movies, YT, music and so on
So really, I don't need anything fancy OS wise, just enough to help get the most out of it without having to overclock the hardware. What order would I need to do everything in? Are there good step by step guides for people like me?
Click to expand...
Click to collapse
wiQbold said:
http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
INSTALL DRIVER
-enable Developer Options
-enable Debugging Bridge
-do a 'adb devices' and check the dialog on your mobile and allow it 'every time'
-shutdown
-hold Volume down and Powerbutton at same time
if the bootloader showed up
-do a 'fastboot devices' if it shows your device online then
-do 'fastboot oem unlock'
after that you have flash your recovery
go to the directory where the file is and
-do 'fastboot flash recovery your_file_here'
after that you can reboot to bootloader and go to recovery
copy the SuperSu.zip which you downloaded at chainfires site or on xda and push it to your internal memory (/sdcard)
and flash it over recovery.
reboot enjoy!
Click to expand...
Click to collapse
So I just follow the guide on the thread, or do I follow the guide you just posted?. The reason I ask is because in the thread's guide, past the parts where it said to install the ADB driver and then the USB drivers for the device, I'm not sure what "debugging bridge" is, unless you meant enable USB debugging, IDK.
- Enable USB developer mode
- Enable USB debugging
- Copy the recovery image and supersu.zip to where the ADB install folder is
- Open the program to open a CMD window to the install location
- Type "adb reboot bootloader"
- Etc
I mean, because the two guides are confusing me more, the forum guide, the thread, how it's worded...now I don't know. Sorry. Is that thread and your guide the same thing, all leading to ultimate unlock and root the device using ADB and the recovery image? And is it not feasible to install Android 4.1.2 as a dual boot OS image so I can test out the Wii Classic Controller since Google broke that part of the Bluetooth code in 4.2+?
there is another tutorial from SuperPichu I think. this is the best for my understanding but I didn 't find it , up in hurry(?)
http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
and yes. usb-debugging
wiQbold said:
there is another tutorial from SuperPichu I think. this is the best for my understanding but I didn 't find it , up in hurry(?)
http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
and yes. usb-debugging
Click to expand...
Click to collapse
Okay, that thread says flashed to OTA 2.0 already, not entirely sure what that means, to be honest, or of the bootloader is locked on it, haven't gotten it yet. I take it I follow the first thread you posted, then
the one above?
the_randomizer85 said:
Okay, that thread says flashed to OTA 2.0 already, not entirely sure what that means, to be honest, or of the bootloader is locked on it, haven't gotten it yet. I take it I follow the first thread you posted, then
the one above?
Click to expand...
Click to collapse
it is a old thread. It s for kitkat..
I think you go like I said.
be sure. adb drivers are installed
Developer Options
Usb debugging
cmd
'adb devices'
check dialog
'adb reboot-bootloader'
'fastboot devices'
look for output
'fastboot oem unlock`
'fastboot flash recovery /directory/to/your-recovery-file'
'fastboot reboot-bootloader'
go to recovery
flash SuperSU.zip
reboot
wiQbold said:
it is a old thread. It s for kitkat..
I think you go like I said.
be sure. adb drivers are installed
Developer Options
Usb debugging
cmd
'adb devices'
check dialog
'adb reboot-bootloader'
'fastboot devices'
look for output
'fastboot oem unlock`
'fastboot flash recovery /directory/to/your-recovery-file'
'fastboot reboot-bootloader'
go to recovery
flash SuperSU.zip
reboot
Click to expand...
Click to collapse
And I go into recovery mode by holding vol. down and power, right? And in that mode I flash the SuperSu.zip correct? And I did get the recovery.img from nVidia's source, which I assume is the one I use in Command. Okay. Rebooting I assume is well, heh, also by holding down power. I also noticed both of those threads have the OS name Lollipop in the thread title.