It's for A7600-F version! I didn't test it on other variants.
Also the boot.img is for ...150401_ROW firmware. (the latest one)
TWRP + unsecured boot.img
* You need to be rooted at least for the while to do it. The easiest way is to use KingRoot. You can uninstall it later and/or replace it with SuperSU.
1. Download the images and copy them to internal storage -> Google Drive
2. Turn on USB Debugging, then use Android Emulator or ADB shell to type those commands:
Code:
dd if=/sdcard/TWRP_2.8.7.x_a7600f.img of=/dev/recovery bs=16777216 count=1
dd if=/sdcard/unsecuredboot_a7600f.img of=/dev/bootimg bs=16777216 count=1
Root
1. Just flash SuperSU in TWRP.
Bugs
*Screen sometimes doesn't turn on after it goes to sleep (Workaround: Settings-->Screen->Uncheck screen timeout)
*Reboot doesn't work (Workaround: adb reboot or reboot in Terminal Command)
Also external storage isn't tested.
Source: github
Replaced TWRP image with new version with better interface and it should be more stable in overall.
Anyone tried this? Success?
Gesendet von meinem Lenovo A7600-F mit Tapatalk
smogan said:
Anyone tried this? Success?
Gesendet von meinem Lenovo A7600-F mit Tapatalk
Click to expand...
Click to collapse
I had this device and it works lol
Hello!
Is there a way back to stock revocery? because i need to reflash the whole tablet and smart phone tools dont recognize the tablet anymore.
Could we use flashify?
Sent from my LG-D850 using Tapatalk
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
Also, this is for the regular a10-70f or a7600-f not the tab 2 version of the a10-70 correct?
Sent from my LG-D850 using Tapatalk
Bump
I too want to know if this works. Flashify or terminal dd command? Anyone?
I tried it with the dd command line. It works. But I don't know to get back to stock, because the flash tool for stock firmware now does not recognize my tablet anymore.
Maybe someone can make a backup of the system partition for me?
Gesendet von meinem Lenovo TAB S8-50F mit Tapatalk
smogan said:
I tried it with the dd command line. It works. But I don't know to get back to stock, because the flash tool for stock firmware now does not recognize my tablet anymore.
Maybe someone can make a backup of the system partition for me?
Gesendet von meinem Lenovo TAB S8-50F mit Tapatalk
Click to expand...
Click to collapse
Ouch Yeah I am rooted and have it the way I like and even have xposed running, but feel unsafe without a custom recovery installed yet.
Still no recovery solution
Have tried the guides that are around the net, but when I try them my tablet always wakes and boots when plugging it in to use flash tool. I have noticed that there is a flash boot option on tablet but flashtool did nothing in that mode. So I have been trying the apps like flashify to flash recovery directly and haven't been successful yet. Any suggestions are more than welcome at this point.
Lenovo A10-70F 4.4.4 KitKat Rooted
Installed recovery without a pc
Was finally able to install carliv (google it) up and running after trying every recovery image I could find.
First I backup up the stock recovery with rashr flashing tool then flashed the carliv img and boom a recovery solution. Tried many images from the internet and the non-touch version of carliv is the only one that would run.
spacenut said:
Was finally able to install carliv (google it) up and running after trying every recovery image I could find.
First I backup up the stock recovery with rashr flashing tool then flashed the carliv img and boom a recovery solution. Tried many images from the internet and the non-touch version of carliv is the only one that would run.
Click to expand...
Click to collapse
Would you care to tell us which version worked on your device? Nowhere do I see it compatible with the MTK 8165 that's running in this device. Also, the links I followed on xda only mention a touch version of the recovery. Am I missing something?
I'm hoping not to have to spend weeks experimenting to be able to get functionality that should never have been locked out in the first place. I can see the time in the near future where these software giants will finally be sued for willfully selling products that are essentially, deliberately crippled (like they are now). Unlocking my Galaxy Note 2 to gain full ownership was a piece of cake compared to this.
And if I may, as an old timer, rant a little - I've grown pretty sick and tired of the homeland security-esque computing environment of the last few years. When I get too depressed, I fire up my old Windows 98SE machine, tweaked to run like Windows 95, sit back and smile at how easy efficiently I could do everything with it...
Well, enough ranting for now. I'm sure a lot more people are going to start looking at ways to get this device to actually work for them after Christmas, as more people get it considering its great hardware features for the price and we'll get more input on these threads.
Keep up the good work folks, I'll keep looking on my end.
Well, after reading a lot and trying a few things here's what I discovered, for those who have this tablet:
Fist of all, thank you Lenovo for making a tablet that is designed for productive work! I got an external SD Card and was able to easily enable USB Mass storage mode directly without rooting, scripting or any other shenanigans
Furthermore, although this thing is running Kitkat 4.4.4 and although I wasn't sable to directly write to the SD Card, I was able to copy created content from the internal to the external SD Card without any issues. It's just that one cannot write from an installed app to the external card (at least that's what it seems to be from early testing with the tablet in unrooted, original OEM configuration).
I've been collecting files and information and as soon as I get this tablet fully under my control with root and a custom recovery I'll make a write up on it here if there is any interest.
Now if I could only find a way to turn down those impossibly garish colors in my pictures... For now it will have to wait, got stuff to take care at the house now, mess has been accumulating since I got the tablet a few days ago
Sorry I don't recall where I got the recover from it was some German sight. The non-touch version was all I was able to get to work.Play store has apps to fix the read only external sdcard.
Sent from my Lenovo TAB 2 A10-70F using XDA Free mobile app
spacenut said:
Sorry I don't recall where I got the recover from it was some German sight. The non-touch version was all I was able to get to work.Play store has apps to fix the read only external sdcard.
Sent from my Lenovo TAB 2 A10-70F using XDA Free mobile app
Click to expand...
Click to collapse
No problemo, I found it on the Russian Lenovo Forum, after reading this thread on xda-developers in its entirety (a MUST READ IMO) and a couple of other online postings elsewhere.
Basically, the recovery for kitkat (4.4.4) is here, for Lollipop 5.0.2 you need to use the one in that thread. Use Google Translate if you must, it's in the Russian.
I'm not sure why you couldn't get touch to work, and if you're worried because it's for the L version of the tablet originally (the tablet version with cellular data), although posted for the A10-70L (WiFi and Cellular version), it's been tested to work on the A10-70F by this new guy in this post, who succeded in rooting his Lollipop updated tablet, he's written a very nice summary of the whole procedure, so that's good enough for me.
I'll see how it goes as soon as I get my SD Card, which should be in a few days.
For those who wonder about this recovery, I've checked a few youtube videos, it's based it's based on ClockWorkMod, so if you're familiar with it you'll feel right at home. Just make sure you get the right recovery version for your tablet's android version
Old faithful said:
No problemo, I found it on the Russian Lenovo Forum, after reading this thread on xda-developers in its entirety (a MUST READ IMO) and a couple of other online postings elsewhere.
Basically, the recovery for kitkat (4.4.4) is here, for Lollipop 5.0.2 you need to use the one in that thread. Use Google Translate if you must, it's in the Russian.
I'm not sure why you couldn't get touch to work, and if you're worried because it's for the L version of the tablet originally (the tablet version with cellular data), although posted for the A10-70L (WiFi and Cellular version), it's been tested to work on the A10-70F by this new guy in this post, who succeded in rooting his Lollipop updated tablet, he's written a very nice summary of the whole procedure, so that's good enough for me.
I'll see how it goes as soon as I get my SD Card, which should be in a few days.
For those who wonder about this recovery, I've checked a few youtube videos, it's based it's based on ClockWorkMod, so if you're familiar with it you'll feel right at home. Just make sure you get the right recovery version for your tablet's android version
Click to expand...
Click to collapse
Not sure why the touch won't go. I was aware that the "f" and the "l" are the same with the latter just having data. Thanks for "cleaning up" the thread for us. Merry Christmas.
spacenut said:
Not sure why the touch won't go. I was aware that the "f" and the "l" are the same with the latter just having data. Thanks for "cleaning up" the thread for us. Merry Christmas.
Click to expand...
Click to collapse
Thank you for the good wishes
I found a great video online for backing up your own ROM http://bit.ly/1J6x6ruhere and am doing that next while the turkey is cooking and report back afterwards
Since my ROM is a slightly different version from the one posted before I thought it would ne best to make my own to make sure I don't run into problems should I need to get warranty service.
The instructions make it a very simple process, the only thing that isn't clear is what to do to make the tablet read and writable, since in that video you're supposed to remove the battery, which can't be done on our machines. I presume a simple power off should do. I'll be back when it's done.
Sent from my Note 2 using Tapatalk
Backing up
I just back up in Carlviv. The only issue is it does not see my external sdcard. So it takes up lots of room on the device.
spacenut said:
I just back up in Carlviv. The only issue is it does not see my external sdcard. So it takes up lots of room on the device.
Click to expand...
Click to collapse
Indeed - and it's difficult to understand why considering the SDCard can easily made writable - But you can move the backup later if you so wish. I just don't like the idea having to shuffle everything all the time. It's a huge annoyance.
I guess the only solution for now is to move on to lollipop...
Sent from my Note 2 using Tapatalk
I have this problem too but in a more complex version, I need to install TWRP whilst in a bootloop to gain ADB access because then I can push the stock ROM and fix the problem so I was wondering if you could do this without ADB?
Related
I am starting this thread to hopefully encourage discussion on the Lenovo A2107A-F tablet variant.
I am aware there is an existing thread on the A2107 here:
http://forum.xda-developers.com/showthread.php?t=1982334
but that thread is concentrating on the A-H (dual sim + wifi) variant which is somewhat different from the A-F (wifi only).
So far I have not found any custom rom development, which is disappointing as the stock rom leaves a lot to be desired IMHO. While the current OTA update is fine for web surfing, reading emails etc, HD video playback (particularly YouTube HD) is very poor. Also the recent OTA update forces an optimization of apps on bootup which leads to long boot times
You can root and install CWM by following steps 1-5 from the 1st post here:
http://forum.xda-developers.com/showthread.php?t=2044496
Note that "-Update 3-" mentioned in the post does not appear to work for the A-F model!
So, has anybody any leads on possible development on this tab?
Any tips on improving performance?
My first tip:
If after installing CWM you cannot get to the CWM recovery screen after powering down the device, look for for the file "/system/reboot-from-recovery.p". If it's there, either delete it or move it to some other place. This file restores the default recovery on a system reboot.
I got bitten by this a couple of times
Thanks for starting a separate thread for the A2107A-F. I'm new to Android devices and just got this one two weeks ago. I'd like to get rid of several of the apps that I have no use for and from what I understand that means I have to root it. I got lost in the details of the other thread, but I tried reading all of it. I'm on Vista and somewhere along the line I installed one of the suggested ADB drivers via PDAnet. Device Manager is showing Android Phone and under that Android ADB Interface. I wasn't sure if that matched closely enough with the step-by-step threads since I don't really think of the device as a phone, so I've been holding off on going further. I've tried using a few other drivers that were suggested in the large thread and some other threads, but Vista always tells me the current driver is the most up-to-date one.
Do you know if it's okay for it to say Android Phone rather than something else?
Thanks. I've got some other questions about the specifics of some of the other steps, but this is probably enough to get started.
My apologies in advance if my posts are too long and my questions are too basic for these forums. Feel free to point me somewhere else based on what I'm asking for. I'd honestly appreciate any leads towards my goal of getting rid of the bloat on this device and making it more responsive. (Wow! The portrait to landscape lag is really bugging me now after reading around here).
Anyway, my primary purpose is to remove the seemingly unneeded programs, services and widgets that come with the tablet. Maybe I'm just ignorant about these things, but at this time things like messaging (IMO), mapping, and some of the other default features are of no use to me. They seem to be eating up a lot of resources. I can kill some of the services I think they are associated with, but they keep popping back up.
I did watch the "noob" video (color me a tiny ant to be squashed) and did try to search for an answer to get me even started. I've read the huge main A2107A thread (80+ pages) and tried three of the suggested ADB drivers with my Vista 32 setup for my A2107A-F. The only one that even seemed to connect was ADPnet and it showed the tablet as a Android Phone. Maybe I'm just too paranoid, but after the multiple "brick" posts I'd like to make sure I'm on the right path before trying to "root" the device which appears to be the first step in removing all the extra stuff Lenovo added.
Not that it matters, but I've had the tablet for almost two weeks now and my favorite things are Slacker Radio, Scrabble, Roll It and Zen pinball. I do play Words with Friends with my wife, but I don't like it since some of the words they allow are not valid in Scrabble (which I used to play as an expert competitively face-to-face).
If you are so inclined, feel free to PM me for a Scrabble game. I promise I will not use anything other than my brain and the built in dictionary to make my plays. (I'm a bit rusty since I gave up competitive Scrabble in 2006).
So, long story short... Thanks in advance for any and all advice you can give on slimming down the Lenovo A2107A-F. And if you want an honest Scrabble challenge feel free to PM me.
As far as checking if your drivers are installed properly I would open a dos (command) prompt in window and from within the window change to the directory where you have the 4.03root files. From the command prompt type 'abd.exe shell' and you should see something like "[email protected]:/ $". If you don't see this then you will not be able to root! You need to make that USB debugging is turned on on your device you have an entry in the device manager for ADB Interface (expand on the device which you have showing up).
I am no expert, and I struggled with this on my first go also
Once rooted you can then install Titanium Backup from the play store and use it to get rid of the bloatware! Proceed with caution however as it is possible to remove critical system apps!
degsie said:
As far as checking if your drivers are installed properly I would open a dos (command) prompt in window and from within the window change to the directory where you have the 4.03root files. From the command prompt type 'abd.exe shell' and you should see something like "[email protected]:/ $". If you don't see this then you will not be able to root!
Click to expand...
Click to collapse
Thanks! That's the type of test suggestion I was looking for to make sure I was on the right path with the driver.
So has anyone tried creating a rom for this tab yet? I've been doing some research into porting another rom to work on the A2107A-F, but want to make sure there isn't one already.
I just received a notification of a new firmware update for the A2107A-F. This would be the second available update.
Has anyone else gotten this and taken the plunge yet? I'm curious if this is possibly Jellybean, as some of the larger screen IdeaTab models run this.
Sent from my IdeaTab A2107A-F using xda app-developers app
ssenemosewa said:
I just received a notification of a new firmware update for the A2107A-F. This would be the second available update.
Has anyone else gotten this and taken the plunge yet? I'm curious if this is possibly Jellybean, as some of the larger screen IdeaTab models run this.
Sent from my IdeaTab A2107A-F using xda app-developers app
Click to expand...
Click to collapse
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
Kevin147 said:
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
Click to expand...
Click to collapse
I lost root after applying the first update a while back. That's typical when updating. Afterward, I was able to re-root mine again using the same procedure as before. All was well. So, don't panic...yet.
Can you report on what other changes the update made? Is it Jellybean? Or maybe ICS 4.04?
ssenemosewa said:
I lost root after applying the first update a while back. That's typical when updating. Afterward, I was able to re-root mine again using the same procedure as before. All was well. So, don't panic...yet.
Can you report on what other changes the update made? Is it Jellybean? Or maybe ICS 4.04?
Click to expand...
Click to collapse
Well, I just re-rooted my tablet and everything was successful! There is absolutely no difference AT ALL with that so called "update".
Kevin147 said:
Well, I just re-rooted my tablet and everything was successful! There is absolutely no difference AT ALL with that so called "update".
Click to expand...
Click to collapse
Although I have my A2107A rooted and tweaked to my satisfaction, there are a few lingering issues that I'd hoped an update would correct:
1) The neutered Bluetooth stack. The tablet is supposed to work with Bluetooth keyboards, mice, etc. It doesn't. Although I've gotten it to talk to an external GPS module, other Bluetooth data connections simply will not work. Oh, and Bluetooth audio? Forget about it!
2) Some settings that are present in stock ICS builds are just omitted in this one. As an example, the ability to specify a default TTS voice. It's present under settings in my wife's tablet and every other ICS build I've ever encountered. Not this one!
Sent from my IdeaTab A2107A-F using xda app-developers app
Kevin147 said:
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
Click to expand...
Click to collapse
I was rooted too, lost root access (only with some apps!) after the 130221 update Feb 28. I'll try the same root procedure as before to see if I can get it back. Glad to see a thread on the popular US version A2107A-F. Maybe someone will port Jelly Bean to this tablet! Doesn't appear Lenovo wants to do it...
Rob
I cannot get this 'update' to install after downloading. The tablet reboots to CWM during the install (I am rooted with CWM installed) and when I attempt to manually select the update.zip from /sdcard/googleota/ I get on error (status 7). In desperation I re-loaded the stock rom that I found on another thread and when the tablet attempts to update I get a "assert failed apply_patch_check( /system/app/applicationsprovider.apk)" error Anybody any ideas?
degsie said:
I cannot get this 'update' to install after downloading. The tablet reboots to CWM during the install (I am rooted with CWM installed) and when I attempt to manually select the update.zip from /sdcard/googleota/ I get on error (status 7). In desperation I re-loaded the stock rom that I found on another thread and when the tablet attempts to update I get a "assert failed apply_patch_check( /system/app/applicationsprovider.apk)" error Anybody any ideas?
Click to expand...
Click to collapse
I'm in exactly the same boat as you. I'm getting the same exact error. except that I do not have CWM installed (I am rooted though). Perhaps there's a problem with the update.zip?
Something odd that I noticed however: After the tablet reboots into recovery mode, the update fails, and I go to browse for the update.zip, the sdcard/googleota directory is missing (along with everything that follows it alphabetically). They reappear upon normal boot. I've tried copying it to a directory closer to the beginning of the alphabet and it does show up while in recovery mode. But it still will not install.
Maybe I somehow do not have the available space to perform the update? Is that possible? I show plenty of available space on both sdcards. Could we somehow be below a certain ROM space threshold necessary for an update?
I think in my case because I loaded a 'stock' rom I got from another thread, this rom is failing a verification test the update is doing before install. I do not know how to get around this! I'm continuing my search, but I am not so confident this will be resolved easily...
degsie said:
I think in my case because I loaded a 'stock' rom I got from another thread, this rom is failing a verification test the update is doing before install. I do not know how to get around this! I'm continuing my search, but I am not so confident this will be resolved easily...
Click to expand...
Click to collapse
Well, I am running a stock rom. I am unwilling to "mess with success" until there's a 100% reproducible way of recovering if it fails. And, so far, everything I've read in the other A2107A thread has been hit or miss for the A2107A-F people.
Anyway, If the update is performing a verification test, then it my "virgin stock ROM" should certainly pass it. The only thing that I did is to root it. Hmmm...could the update be testing for that and refusing to install if it detects a rooted device? I would tend to doubt that, since the previous ota update went just fine. I lost root in the process but easily reapplied it afterward.
Thoughts?
Interestingly, I flashed the A2107A-F_S483_121115 rom (again, found in another thread) as I was having verification problems with the OTA update just released from lenovo which was available from the A2107A-F_S484_121211 flashed rom. While the S483_121115 rom appears to be older, I no longer get the option to update via OTA as the tablet is telling me that my s/w is up to date! Go figure.
It's really too bad this device hasn't taken off. If I actually knew how to dev then I would start developng ROMs for it. I'm enjoying it now that I have root and got rid of bloat.
Hey guys. Just wanted to say if someone can send me a stock rom and be willing to test, I'll try to do up a good rom for the -f models. I'd use mine for the stock rom, but I've edited a lot of the system, so no go there. If you have the stock rom or want to be a tester, let me know.
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?
Digiland dl701q stock firmware?
This was a Digiland dl701q tablet handed down to me after it was stuck in a bootloop.
the Device despite attempting using stock and chinese recovery would not start up the OS.
adb did not work with the exception of sideload.
fastboot was operational
After four days on and off of trying to get the tablet to work-
this was the only firmware i could find.
mid713l-lp-lvds-20141226
flashing the system.img
did not work it just booted up to the digiland logo and the bootloop again. tried multiple times.
I flashed this^ firmware onto the tablet-
I was unable to make a backup or setup CWM custom recovery before the flashing took place- However all the other options that were available did not work, could not gain root either.
Looked here as well-
http://forum.xda-developers.com/android/help/digiland-dl701q-looking-stock-recovery-t3005788
Current status-
the rom above was flashed to the device.
The tablet has a UBIFS CWM custom recovery-
The tablet boots up successfully but with some caveats-
the colors are inverted, and the touch is completely inverted "touching the top left clicks the icons on the bottom right"
Any assistance would be appreciated-
I'm just trying to find better answers than what i have right now-Pretty sure im out of luck but-
Thanks for your time and also for reading.
One positive would be, I learned how to use adb and fastboot, so thats kinda nice.
Again* If anyone has a stock rom or could point me in the right direction that would be greatly appreciated.
H
Enviado desde mi HUAWEI Y300-0151 mediante Tapatalk
UPDATE
Have located a stock firmware and successfully rebooted device. Now onto other things.
Link?
Could you post a link of where you found the stock firmware?
I need this too
I need the link of where you found the firmware please, I messed up my tablet and need to re-install the firmware.
Sent from my XT1058 using XDA Free mobile app
I need this too
jackalhoun said:
Have located a stock firmware and successfully rebooted device. Now onto other things.
Click to expand...
Click to collapse
I need the link to the firmware you have found, my tablet barely works now. The System UI app will not work anymore, thus making the tablet useless. I really need the link please.
That fool not going to share. Just throw it away and get an iPad or galaxy tab like I did They are cheap enough now. Not worth the headache.
and still no link
I've been using Gnabo v_7 version for quite a long time, and a very simple and beautiful day when I woke up my Samsung GT-N8000 was stuck on bootscreen. I wasn't able to do much so I got this "Brazil stock rom" that I found in a website, and it flashed all right, except for the detail that there is something at the screen that I haven't got a bloody clue how to remove. hahaha
And still, whenever I try to install another room, I got stuck at bootlogo and so on. I'm kinda lost here, mind a little help?
I traveled around the forum but well, I'm a little dumb so I couldn't find any proper information about, how to solve this. I would like to know if there is a way to remove this thing from the main screen, and post here the image for you guys to see it please.
I tried to post the image here to make it easier understanding, but since I got this login recently I can't =\
Thanks
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
DroidTwe4kz said:
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
Click to expand...
Click to collapse
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
vitortakeda said:
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
Click to expand...
Click to collapse
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
DroidTwe4kz said:
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
Click to expand...
Click to collapse
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
vitortakeda said:
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
Click to expand...
Click to collapse
Here is tutorial about how to install ADB and Fastboot drivers and use them. Unfortunately, I don't know how to use it to restore efs. Sorry.
Hi everybody ! Ill try to keep it simple as I'm sure its covered somewhere but here goes ....
Ive been using my shield portable, rooted, for ages now no problems.
Like many Ive updated it in short ever since nothing whatsoever has worked properly , most annoyingly the screen doing backflips when you go near it and hundreds endless strange updates when rebooting.
Anyway I don't think you or I or any of us want to waste time trying to figure out why its done any of this but I just want to be able to fix it. I guess I'm going to have to start again somehow! its worth noting here that all my backup apps like Helium now don't seem to work.
After the update I of course ReRooted and it appears fine from boot loader , still says unlocked. but upon usage its clearly very confused about whether its rooted or not !
In short its useless. Advice please My kung Fu warriors
May your arrows fly straight and true
I have no idea about the various issues, but I would perform a factory reset, and clear cache and dalvik cache using at least 3 swipes per each function. The method of rooting I recommend is by flashing a zip of SuperSU from a custom recovery menu. CWM or TWRP are both available for the NSP. After flashing SuperSU, when you reboot and go into SuperSu you'll see that it's installed (locked down tighter) as a system app.
Downloads:
SuperSU (latest stable version) v2.65
CWM Recovery Menu (latest version) v6.0.4.4
TWRP (Modified recovery (based on TWRP v2.8.7.0)
Sorry. This is the best I can offer you right now. If this doesn't work I would reflash the stock images of whatever OTA you wanna be on. The images can be found @:
SHIELD Open Source Resources and Drivers. You'll need at least the platform-tools portion of the Android SDK (to use Fastboot to flash from recovery). A user friendly PC app that can basically do all this sort of stuff is Shield Ram v1.1. You might find that easier to use.
Oh and here's the latest Minimal ADB and Fastboot Drivers installer [v1.3.1]
If you need further help, let me know.
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
[/COLOR]
Marrhead said:
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
Click to expand...
Click to collapse
Yeah, pretty much the rule is generally "as long as you can still see the screen, it's probably fixable". Sounds to me like your best bet, would be to download the OTA you wanna be on, and flash a new install to your Shield. It's the quickest way from A-B. I'm about 99% sure that this would solve the problem (as long as you re-root it properly). Though if you have your reasons, you can try some of the other things first. You're welcome and let me know how things go!
So where does one get the latest OTA?
cheers
Marrhead said:
So where does one get the latest OTA?
cheers
Click to expand...
Click to collapse
I did link up the main Nvidia page that would lead to the OTA images, but here's a direct link to DL just the OTAs:
Edit: you can get there through the link I included in my previous post: SHIELD Open Source Resources and Drivers. I'm having issues with editing posts, and all sorts of odd **** with the link trying to post a more direct link. It's an Nvidia site, just scroll down to Shield Portable Recovery OS Images (something like that).
Unfortunately there are only Linux and Windows downloads available. I'm not sure what your best option would be, as you have a Mac. You could contact Nvidia support, and see what they say about it. Sorry, but I don't think I can probably help much more than this.When I contacted Nvidia support about a year ago, they were pretty helpful. Hopefully you get this sorted soon. Oh and the OTAs are flashed via a terminal/command prompt. So if you can emulate DOS on your Mac (which I don't see why not...DOSbox? maybe) then that sounds to me like the solution.
Ok , hit another brick wall. Im using a windows computer now, followed all the instructions i can find, and now the bootloader seems dysfunctional.
Ive got adb and fastboot and its recognising the device but once rebooted into bootloader which loads fine, the commands say no device found and nothing works in this mode.
If i hit recovery mode then a little dead android appears! poor little guy.
I tried shield ram but it had same problems, seems to run fine but cant find shield once its in bootloader...
Ive got the image zip of the update i want to flash but no idea if im doing it right- not sure how to use it.
Help!