Database Users

[Q] Fixing Recovery issues with Iconia A500?

Hi there!
I own an Acer Iconia A500. Originally came with HC3x, updated it all the way to ICS. Rooted it at ICS with this method:
http://forum.xda-developers.com/showthread.php?t=1546593
Worked fine. The only issue is accessing Recovery at boot. (Just in case I plan on restoring the Stock version of Android, for warranty).
I first used the Acer Recovery Tool app at the Play Store. I tried one of the Recovery options listed. CWM for start. Backed up as asked, then rebooted into recovery. I was told "recovery verified failed". Did a restore, tried another method, same crap, with a time the bot with the (!) appears. Did some research on the issue, and came up to this thread:
http://forum.xda-developers.com/showthread.php?t=1622425
I did option 1 (Afterota v1.09). And flashed Recovery Twp 2.1.3/Bootloader.
I reseted back to bootloader, it didn't show "Recovery verified failed", but instead I got the bot with the (!) again. Went back to Acer Recovery tool. Bottom shows that its unable to identify the installed recovery. So I tried TWRP 2.1.3, didn't work.
My question is, how can I get this to fix? This is my first time trying to install a bootloader. Please help me step by step to get this situation fixed. I appreciate the help by any!!

i am having the same issue and have tried several different fixes without success... any suggestions would be greatly appreciated!
(the only one I haven't tried yet is 'manual flashing' outline here http://forum.xda-developers.com/showthread.php?t=1622425... will give this a shot when I get a chance and report back... from all the 'automated' or gui methods it always seems to get stuck at the flashing/copying stage...)
thanks!

Same issue...
Glad I'm not the only one with this issue... Used the exact methods you did, same results. Amazing!

i think part of the problem may be that the bootloader was not unlocked when the initial recovery was flashed? when i rooted i thought I had properly unlocked the bootloader as well, but perhaps not....? (... i thought i read somewhere that if the bootloader has not been unlocked when you flash recovery these are the results.. so i am assuming that this might have something to do with the issue?)
the question is, is there a fix?
i have been playing and experimenting more on the tf101 side... all the stuff i'm doing with this is for my wife's a500 because she liked some of the features on my tablet... i'm not all that familiar with the A500 (didn't have to deal with bootloaders separately on the tf101) so any help is greatly appreciated!
thanks!

Alright. I seem to have got it all fixed. What I did was, went back to this page:
http://forum.xda-developers.com/showthread.php?t=1622425
Went to the "Automated flashing tool" / "USING blackthund3r ATX flash tool , It makes it all a little easier !" Method (below Option 2, in the middle). Downloaded V8-TWRP_2.1.3_ICS_recovery.a500apx and APX-FLASH-Tool & Manager, and followed the instructions.
It didn't work with Windows 8 RTM, (driver issue with APX), but Windows 7, worked perfectly, after downloading the Acer driver from a link in the app when prompted. All worked well.

hope u guys got sorted....
for others reading this
to install recovery from ICS you must first flash the unlocked boot loader, after that u can use Acer recovery installer, although once unlocked most of us use fast boot or the auto tools to do it

[dev][apx][nvflash][tegra-note-7][update]

If anybody bricks his/her device and has only the APX mode available or is trying to get an nvflash utility for a Tegra Note 7, now the solution can be found: the Advent company has published a full package including a nvflash working with the Tegra Note 7. Moreover, the package contains a signed bootloader and bct and all the other parts of the entire storage (including the system partition for a 4.3. JellyBean).
It can be downloaded from their website of adventcomputers.co.uk in the downloads section (I can't post links yet), select Product range: "Advent"; Product type: "Tablet"; and then choose "ADVENT Vega Tegra Note 7", do not be mystified by the "driver" type and download the "Advent Vega Tegra Note Factory Image (4.3)" (about 641 MB package)
Many thanks to the dev and support guys at Advent (Dixons retail plc), because they have put the final cherry on the top of the cake. The Nvidia Tegra Note 7 is now not only a top of the top devices regarding its power, but this package renders it into an unbrickable device.
(note: I'm NOT affiliated with any of the companies, I just bricked my device and had no other mode available than the APX mode. I'm posting this post due to the abovementioned reasons, because I find this quite and important source for further hacking(orig. meaning) of the devices. In fact I regard this as an utlimate source for development on this platform.)
I have tried the package (including the batchfile, that does the automation), it works for me on my Advent Vega Tegra Note 7, however Im not sure if it will work on others (EVBA for example), so please feel free to test and post your experience underneath here.

Link: http://adventcomputers.co.uk/product-download-select/296
Sent from my TegraNote-P1640 using Tapatalk

thx

Thanks for the heads up. I tried it on my bricked dodgy manufactured tablet and I was able to get the device to a new level but it still crashes trying to boot the system partition. Least now I have fastboot.
With the nvflash recovery tools you can replace the images to suit say bat-recovery or latest boot.img with menu options the older version doesn't have.

Wait what?! Why havent I been notified?! And subscription to my own thread has been lost?!?! O__o ill take a look at this!!!!
Edit: I see, this isnt my thread thanks ill reopen my thread

Shaky156 said:
Wait what?! Why havent I been notified?! And subscription to my own thread has been lost?!?! O__o ill take a look at this!!!!
Edit: I see, this isnt my thread thanks ill reopen my thread
Click to expand...
Click to collapse
HEhehee. This nvflash recovery is only new to the scene so I didn't get time to check it out then inform you Shaky.
In my opinion our community can rehash these tools and make a better recovery.

Shaky156 said:
Wait what?! Why havent I been notified?! And subscription to my own thread has been lost?!?! O__o ill take a look at this!!!!
Edit: I see, this isnt my thread thanks ill reopen my thread
Click to expand...
Click to collapse
I have tried to make a request on the admin who locked Your threead and wanted to post it there (see my message to Moscow Desire below), but I did not get any answer, so I did not want to dealy such an important newz anymore, so I have allowed myself to open a new thread with simmilar markings. Sorry for the discomfort, but I do not see any other way of behaving corerctly, if this forum platform and its admins do not provide support for this.
With regards
------ Original message ---------
Reopening a closed thread?
There is a thread I would like you to reopen, since the state of things has heavilly changed. The post I would like to post is an quite important one, while it may contain a link to a commercial site, it also points to an nvflash utility working with Tegra Note 7, including signed bootloader and BCT. Moreover, the (non-purchase and registration free) download package is made by a commercial partner of nVIDIA with (AFAIK from their support) full consent of nVIDIA. For the Tegra Note it is the last missing bit for the full controll of the device starting from APX mode up to the various other run-modes.
Im not affiliated with neither of the abovementioned companies, I just bricked my device and had no way to recover it since APX was the only rescue, so they published the whole package (for 4.3 JB). I think mentioning this as well the link to the package is worthwhile the post, but I do not feel that starting a new thread would be correct.
Thread to be reopened: (link to your original thread)
Would this be possible?
Thanks

rheingold said:
I have tried to make a request on the admin who locked Your threead and wanted to post it there (see my message to Moscow Desire below)., but I did not get any answer, so I did not want to dealy such an important newz anymore, so I have allowed myself to open a new thread with simmilar markings. Sorry for the discomfort, but I do not see any other way of behaving corerctly, if the platform and its admins do not provide support for this.
With regards
------ Original mail ---------
Reopening a closed thread?
There is a thread I would like you to reopen, since the state of things has heavilly changed. The post I would like to post is an quite important one, while it may contain a link to a commercial site, it also points to an nvflash utility working with Tegra Note 7, including signed bootloader and BCT. Moreover, the (non-purchase and registration free) download package is made by a commercial partner of nVIDIA with (AFAIK from their support) full consent of nVIDIA. For the Tegra Note it is the last missing bit for the full controll of the device starting from APX mode up to the various other run-modes.
Im not affiliated with neither of the abovementioned companies, I just bricked my device and had no way to recover it since APX was the only rescue, so they published the whole package (for 4.3 JB). I think mentioning this as well the link to the package is worthwhile the post, but I do not feel that starting a new thread would be correct.
Thread to be reopened: (link to your original thread)
Would this be possible?
Thanks
Click to expand...
Click to collapse
Hi i dont have an issue with this, mistake on my part, I thought this was my thread lol. Ive reopened my thread and its moved to Q&A. Will work on a newer things, I have new files. Will test few things first.

Hi
I try download it but every time when is finish file is corrupted.
Can anybody share Vega Tegra Note Factory Image file?
Best regards

After finding out after a long time about this guide,I managed to reflash the stock firmware and reset the tablet,so hurray and much thanks for sharing this guide
Sent from my HTC One X using XDA Premium 4 mobile app

Ok, I need some help if anyone can.
I erased the boot file on my Nvidia EVGA Tegra Note 7 P1640 tablet and now I'm stuck. I had set usb debugging on in the tablet and as far as I know, it's still on. I have tried everything I can think of and nothing works. First, there are 3 driver_install.bat files in the Vega7\usbpcdriver folder. Being that I'm running windows 7 64bit with an AMD processor, I select driver_install_amd64.bat and it fails wanting $P4ROOT$ to be set. I may be wrong, but I set it to D:\Android\Vega7 (in the install_driver_amd64.bat). Please correct me if I'm wrong. Second, if I set p4root to D:\android\vega7 (where the Vega7 folder is), it fails with "NT DDK at //sw/tools/ddk/nt6/6001.18002/... is not synced" and fails. I have no idea what to do about this. If I goto the vega7 directory and click on flash_signed.bat, it stops at >SN.txt and just sits there. I thought I was fairly computer savy, but apparently I'm not.
I've followed the instructions as written up to the point it freezes up on me, however there is no info on what to do if the batch files fail.
I can get the tablet into APX mode in the device manager, but the drivers are not loaded. I can load the drivers in the usbpcdrivers folder, which installs "Nvidia USB Boot-recovery driver for Mobile devices", but still can't get the flash_signed.bat to go any farther than >SN.txt. (I turned echo on in the bat file so I could see what was happening)
So please, anyone, help. I've only got one hand full of hair left and it's about to go too.

Always use usb without option for power charging.
Change USB port if not try on different computer, I was stuck on my one when I try do flash, go on my girlfriend laptop and done without any problems.
Hiro51 said:
Ok, I need some help if anyone can.
I erased the boot file on my Nvidia Tegra Note 7 P1640 tablet and now I'm stuck. I had set usb debugging on in the tablet and as far as I know, it's still on. I have tried everything I can think of and nothing works. First, there are 3 driver_install.bat files in the Vega7\usbpcdriver folder. Being that I'm running windows 7 64bit with an AMD processor, I select driver_install_amd64.bat and it fails wanting $P4ROOT$ to be set. I may be wrong, but I set it to D:\Android\Vega7 (in the install_driver_amd64.bat). Please correct me if I'm wrong. Second, if I set p4root to D:\android\vega7 (where the Vega7 folder is), it fails with "NT DDK at //sw/tools/ddk/nt6/6001.18002/... is not synced" and fails. I have no idea what to do about this. If I goto the vega7 directory and click on flash_signed.bat, it stops at >SN.txt and just sits there. I thought I was fairly computer savy, but apparently I'm not.
I've followed the instructions as written up to the point it freezes up on me, however there is no info on what to do if the batch files fail.
I can get the tablet into APX mode in the device manager, but the drivers are not loaded. I can load the drivers in the usbpcdrivers folder, which installs "Nvidia USB Boot-recovery driver for Mobile devices", but still can't get the flash_signed.bat to go any farther than >SN.txt. (I turned echo on in the bat file so I could see what was happening)
So please, anyone, help. I've only got one hand full of hair left and it's about to go too.
Click to expand...
Click to collapse

lizard-borys said:
Always use usb without option for power charging.
Change USB port if not try on different computer, I was stuck on my one when I try do flash, go on my girlfriend laptop and done without any problems.
Click to expand...
Click to collapse
Can't use usb without power. The tablet will not stay turned off now and because of that, the battery won't charge enough to usb without power from usb.
I've even plugged in the charger and gone into boot-loader and clicked on shut down, but it still won't stay off or take a decent charge.
I have tried a different computer as well as different ports with the same results.
btw, thanks for replying.
As I reread the posts, I noticed rheingold's post at the bottom says he's not sure if this will work on the (I believe he meant EVGA) model. Can anyone verify it works on EVGA?

Solved. Bad USB cable. Unbelievable! I guess the original cable only works when it wants to. Used usb cable from old kindle with complete success. Fully restored to 4.4.2, rooted, and sd card fixed. I'm back in business. Gotta love those rootjunkys super tools.

Hiro51 said:
Solved. Bad USB cable. Unbelievable! I guess the original cable only works when it wants to. Used usb cable from old kindle with complete success. Fully restored to 4.4.2, rooted, and sd card fixed. I'm back in business. Gotta love those rootjunkys super tools.
Click to expand...
Click to collapse
Nice work mate. I am speaking with Nvidia too see if they will do factory images like the Shield but waiting on a response for that.
Also OTA 2.4 is now Live as of 5 minutes ago.
It seems the USB cables are not of high quality just like the ports.

lizard-borys said:
Hi
I try download it but every time when is finish file is corrupted.
Can anybody share Vega Tegra Note Factory Image file?
Best regards
Click to expand...
Click to collapse
Having the same issue here.. anyone?

I have a copy if its needed still.

Today, panic stations as I thought I had bricked my Advent Vega Tegra Note 7.
I had updated yesterday to KitKat along with additional OTA updates, but decided
to go back to 4.3 to capture the update after main KitKat update (2nd of 6 updates [EDIT: forgot to cap that one]).
I unlocked bootloader via fastboot, then flashed system.img (4.3 from Advent) and then the TWRP
recovery.img EDIT: Also locked bootloader..
On boot, it got itself stuck Powered ON at the TEGRA NOTE (white on black) screen, all was doom and gloom.
I finally figured out that holding down Volume+ then pressing the power button quickly and then
pressing again (whilst still holding the volume+ button down), I could get into the recovery menu
to access TWRP. In TWRP I did a factory reset and hoped for the best.
On reboot, all was still doom and gloom. So I thought maybe it might be necessary to have the
appropriate boot image (rather than the 4.4 boot image), and so flashed that, and Voila,
everything is hunky dory again.
I seem to have lost ability to use nvflash (APX mode) after original 4.3 flashing (which I could access
on the device doing the same dance as above but pressing both volume up and volume down keys before power).
My USB driver Vender ID and Product ID's below, I seem to have two Fastboot Id's, presumably one for stock recovery
and the other for TWRP (I blanked last 5 digits with x's just in case they could be used for nefarious deeds).
Code:
Fastboot Advent Vega Tegra Note 7 Fastboot Vid_0955&Pid_cf01\052101410714600xxxxx
TegraNote-Premium Google Galaxy Nexus ADB Interface Vid_18d1&Pid_d001
Tegra NOTE TegraNote-P1640 Vid_0955&Pid_cf02
Fastboot Advent Vega Tegra Note 7 Fastboot Vid_0955&Pid_cf01\15C4110C904000000100xxxxx
Advent Vega Tegra Note 7 Vid_0955&Pid_cf00&MI_00
Tegra NOTE Advent Vega Tegra Note 7 ADB Vid_0955&Pid_cf00&MI_01
Tegra NOTE USB Composite Device Vid_0955&Pid_cf00
APX NVIDIA USB Boot-recovery driver for Mobile devices Vid_0955&Pid_7535
Anyway, perhaps above is all known to you old salts, but for a newbie like me, is perhaps of use.
Also, thanks for the link

You can access APX by pressing Power plus Volume down and Volume UP at the same time and holding them.

Thanx hacktrix, I could access APX OK (was stuck with power on, ie could not power off, the dance described allowed me the access both fastboot and APX).
The problem was nvflash via flash_signed.bat.

[Q] Unsuccessful reflash of Homecare Fly One Note7

Hello guys.
I would like to ask you for help with my bricked Homecare. I apparently cocked up the flashing process and now I don't know, how to proceed.
What I did:
At first I used the Russian (translated) version of supertool designated for Homecare Note 7. But the process wasn't 100 % successful. The bootloader has been unlocked, CWM recovery has been flashed, ROM 4.3 has been flashed. The tablet was able to boot, but it always froze after a few minutes of operation. Most probably there was a wrong boot flashed. No idea.
So, I checked the forums and RootJnky's videos and decided to use CWM to flash a deodex 4.3 stock ROM.
Flash process was successful, but after restart the tablet remains in boot-loop.
Now, I was NEVER able to enter the Recovery or Bootloader using the button combination. Don't ask me why, but it wasn't possible. I could however access recovery or bootloader using ADB.
Right now the only status except a boot-loop is the APX mode. Is there still a chance how to unbrick the tablet???
Thanks for any advice.
Jaro

jardam.cz said:
Now, I was NEVER able to enter the Recovery or Bootloader using the button combination. Don't ask me why, but it wasn't possible. I could however access recovery or bootloader using ADB...Jaro
Click to expand...
Click to collapse
At worse case scenario you need to use APX mode to reflash. You can get the download references for the APX files, particularly the package from Advent UK. The package is setup for Windows but it's easy to use in Linux with their executables.
The APX mode does reflash your tablet in whole, but the end result may not be perfect, but should allow a stepping stone to fastboot mode.
If you can obtain 'fastboot' mode then your can reflash partitions. The 'adb' mode in recovery level or system level will allow for updates with 'sideload' command.
Hope that helps.

e8hffff said:
At worse case scenario you need to use APX mode to reflash. You can get the download references for the APX files, particularly the package from Advent UK. The package is setup for Windows but it's easy to use in Linux with their executables.
The APX mode does reflash your tablet in whole, but the end result may not be perfect, but should allow a stepping stone to fastboot mode.
If you can obtain 'fastboot' mode then your can reflash partitions. The 'adb' mode in recovery level or system level will allow for updates with 'sideload' command.
Hope that helps.
Click to expand...
Click to collapse
@e8hfff I managed to sort him out yesterday using the APX method the use has now got it working, with no issues at all (WiFi works as well).
The only thing different for him is that his Generic bootanimation which Xolo Tegra Note 7's have is now showing advent.
I will send you a PM in a bit out the bootanimation as i have a idea LOL.

hacktrix2006 said:
@e8hfff I managed to sort him out yesterday using the APX method the use has now got it working, with no issues at all (WiFi works as well).
The only thing different for him is that his Generic bootanimation which Xolo Tegra Note 7's have is now showing advent.
I will send you a PM in a bit out the bootanimation as i have a idea LOL.
Click to expand...
Click to collapse
Hi hacktrix2006.
Thanks for the help again. The tablet is working like dream. All my Chinese colleagues are staring at it. The poor guys know only the products of the fruit company (Apple).
I saw the boot animation is a set of pictures in the flash package from Advent. It is ZIPed.
Is there any way how to make and flash a boot animation without reflashing the whole thing? (I know the answer already, but I don't know how to do it DD)

jardam.cz said:
Hi hacktrix2006.
Thanks for the help again. The tablet is working like dream. All my Chinese colleagues are staring at it. The poor guys know only the products of the fruit company (Apple).
I saw the boot animation is a set of pictures in the flash package from Advent. It is ZIPed.
Is there any way how to make and flash a boot animation without reflashing the whole thing? (I know the answer already, but I don't know how to do it DD)
Click to expand...
Click to collapse
The bootanimation.zip is in /lbh partition under media. Should be a easy enough to copy and paste in if not then i will have a look for a way of doing it without flashing all of it again.

Docs on Homecare Fly One rom update
Hi jardam.cz AND hacktrix2006
I see you guys have a working method to update the Homecare Fly One - do you have any documentation on how to root and update the rom for this model? Jardam mentioned a Russian rom, but it caused problems. I really don't want to brick this, as I live and breathe with this tablet every day! But I can't stand the limitations of no root.
Almost all the YouTube videos show EVGA solutions, and lots of people have Homecare Fly One problems - what's the solution please?

They are all the same base nvidia model which is p1640 the lbh partition is wrote when flashing via apx mode which can be risky. However there is a twrp recovery for our device and a stock 4.4.2 image from tom you can use to flash a generic version if the os.

Bricked Tegra Note 7

EVGA Tegra Note 7
4.3 jelly Bean
Used the Super Tool to flash drivers and unlock bootloader.
Installed TWRP Recovery
Rooted using SU
Everything is working great, at this point.
Failed to back anything up
Flashed Shaky's custom Kernal and I couldn't get past the tegra note 7 screen. - at this point I probably could have saved it but doing anything other than what happens next.
Flashed 4.4 stock Rom which has to have reset the Recovery and Debugging is now off.
Do not do what I did. Brick. Any ideas? I can still get into bootloader which is unlocked but my computer no longer recognizes it. Pretty much lost hope on this one. Surprise me if you feel inclined.

I've been trying to sideload via externalSD, the stock 4.3 ROM from the "Tegra Note Discoveries" thread. It actually gets halfway though installation then fails for reasons I can't begin to understand. Most likely because it's rooted and I'm flashing a stock rom. If anyone can find a way to flash the stock Kernel and 4.3 rom I would be grateful.

share_needles said:
I've been trying to sideload via externalSD, the stock 4.3 ROM from the "Tegra Note Discoveries" thread. It actually gets halfway though installation then fails for reasons I can't begin to understand. Most likely because it's rooted and I'm flashing a stock rom. If anyone can find a way to flash the stock Kernel and 4.3 rom I would be grateful.
Click to expand...
Click to collapse
In the recovery environment , ..... you are inside the ram disk of, whatever recovery you are running and root status of your system ROM doesnt matter .
Since from the 1st post you have recovered it to the point where you can access the recovery, I think its just matter of getting the correct backup re-installed.
You can request someone with same Branding ( there are 6-7 avent, XOLO etc ) to upload their cwm backup ( minus data, cache ).
Lack of developer / geeky user community is what you get when companies lock their bootloader under disguise of Warranty n stuff.
I havnt been able to gather the courage to play with TN7 like i do with my Nexus7, nexus 4 and Xperia J . ( XJ has some great XDA community btw even after closed BL)

kapil.git said:
In the recovery environment , ..... you are inside the ram disk of, whatever recovery you are running and root status of your system ROM doesnt matter .
Since from the 1st post you have recovered it to the point where you can access the recovery, I think its just matter of getting the correct backup re-installed.
You can request someone with same Branding ( there are 6-7 avent, XOLO etc ) to upload their cwm backup ( minus data, cache ).
Lack of developer / geeky user community is what you get when companies lock their bootloader under disguise of Warranty n stuff.
I havnt been able to gather the courage to play with TN7 like i do with my Nexus7, nexus 4 and Xperia J . ( XJ has some great XDA community btw even after closed BL)
Click to expand...
Click to collapse
Yea I jumped in the deep end without doing enough research. I have rooted and installed custom ROMs on my android phone without issue but I've never messed around with kernals or had to dig myself out of a device stuck in boot-mode. Instead of learning about a device then modding it, I forced a situation where I modded now need to learn how to fix it.
As novice as I am, still working on getting the correct drivers installed to sideload a backup. My computer will not recognize the ADB device in the stock bootloader but when I boot into recovery it does recognize it so there is definitely a driver issue there.

By kapil.git
You can request someone with same Branding ( there are 6-7 avent, XOLO etc ) to upload their cwm backup ( minus data, cache ).
Click to expand...
Click to collapse
I think more like a dozen brands of TN7.
You should at least tell your brand, would make it less mysterious.
Advent has a stock 4.3 install install via APX mode (although you seem to be only able to use it once, then it locks
the nvflash stuff).

I apologize I have the EVGA Tegra Note.

share_needles said:
I apologize I have the EVGA Tegra Note.
Click to expand...
Click to collapse
you are lucky ... this thread has many posts of the same branding EVGA..
Top posts & stickies also have a AIO post about recovering a unlocked BL device.. download and do it OP.

Hi Guys. Tablet is working fine now. I used multiple files from multiple sources to get this going. Here were the commands to get me back to stock. Obviously there was a lot of playing with commands etc that I cut out. I truly believe this device is unbrickable. I was just stuck in a bootloop.
in short, the issue was with the boot after a kernel flash. The TWRP recovery was flashed back to stock.
Got the drives from SDK download because I'm not slick enough to be able to do it myself.
In fastboot, make sure you have the fastboot file in the folder with your boot.img , recovery.img
fastboot boot boot.img ----got me out of the bootloop temporarily without flashing anything unnecessary
fastboot flash boot.img, flashed the boot.img from Vega Note 7 source files that are out there, I recommend every download those now.
fastboot boot TWRP_recover.img -----messing around be led me in a good direction
From there, I installed the below file from XDA User e8hffff
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
I believe that was a full backup of a 4.3 Evga Tegra Note 7 stock. This really helped me out a lot.
Thanks everyone for the help. You can see by the very few command that got this device up and running I am a total noob but I'm figuring it out little by little.
If anyone is in a similar circumstance in the future send me a PM and I may be able to assist you.

Seeking advice on rooting Smart Tab M10 FHD Plus 2nd Gen

Dear and knowledgeable readers!
Being a longtime lurker, your tireless work and dedication to the community have enabled me to unlock and root many different android devices over the years and I am deeply grateful this place exists.
Right now, I plan on adding the recently released
Lenovo Smart Tab M10 FHD Plus 2nd Gen [ZA5T0302SE / TB-X606F, I believe]
in the WLAN/4GB/64GB variant to my collection. Having grown accustomed to the luxury of root access, I was wondering if anyone already had some experience with rooting the device and would be willing to share his / her knowledge with me.
Especially, I was wondering if this guide for the TB-X605F, which I have successfully used in the past for my older model, would (in principle) be applicable, as long as I could obtain the corresponding firmware for the newer one, which might be available here (as soon as GD wills it).
Any advice / support would be highly appreciated!
[Sidenote]: To my best ability, I wasn’t able to find an existing thread on the topic of rooting the device in question and I hope to have chosen the right forum to post it in (or if the general Q&A would have been the better fit?). If not, dear mods, please be lenient with me and simply move the thread to the proper subforum.

Brotinger said:
Dear and knowledgeable readers!
Being a longtime lurker, your tireless work and dedication to the community have enabled me to unlock and root many different android devices over the years and I am deeply grateful this place exists.
Right now, I plan on adding the recently released
Lenovo Smart Tab M10 FHD Plus 2nd Gen [ZA5T0302SE / TB-X606F, I believe]
in the WLAN/4GB/64GB variant to my collection. Having grown accustomed to the luxury of root access, I was wondering if anyone already had some experience with rooting the device and would be willing to share his / her knowledge with me.
Especially, I was wondering if this guide for the TB-X605F, which I have successfully used in the past for my older model, would (in principle) be applicable, as long as I could obtain the corresponding firmware for the newer one, which might be available here (as soon as GD wills it).
Any advice / support would be highly appreciated!
[Sidenote]: To my best ability, I wasn’t able to find an existing thread on the topic of rooting the device in question and I hope to have chosen the right forum to post it in (or if the general Q&A would have been the better fit?). If not, dear mods, please be lenient with me and simply move the thread to the proper subforum.
Click to expand...
Click to collapse
If you download the lmsa tool, plug in the tablet and go to recovery it will download the full stock firmware. Then you can find it c/program data/LMSA/downloads.
I did that then downloads magisk manager. Extract the boot.img from firmware and put in storage of tablet. Then used magisk manager and patch the boot.img it will tell where it is stored. Extract from tablet and put it in same folder as adb/fast boot. Then put tablet in fastboot and fastboot flash boot magisk-patched.img. then fastboot reboot. The will be rooted with magisk
I forgot. You must unlock bootloader to do this.

Dear 11mackey11,
thank you so very much for caring enough to share your knowledge with me!
So the guide I mentioned earlier is pretty much applicable for the newer model as well? What a relief!
I am also grateful for the hint on how to obtain the stock firmware. For all the dirty things I did to my devices in the past, it never became necessary to put the LMS-Assistant to use, but I will gladly change that now.
As soon as my device arrives, I will try to root it as you suggested and will report back how I fared.
Again, many thanks!

It took me some time to finally get to it … delivery problems with the device … busy work schedule …
… anyhow, I now took the leap and am happy to report that, thanks to your advice, I was able to add another rooted device to my ever-growing collection. “Worked like a charm”, as they use to say.
To repeat myself, I am very grateful for you taking the time to respond to my question and reassuring me that this was the path to follow.
Honestly, thanks!

Brotinger said:
It took me some time to finally get to it … delivery problems with the device … busy work schedule …
… anyhow, I now took the leap and am happy to report that, thanks to your advice, I was able to add another rooted device to my ever-growing collection. “Worked like a charm”, as they use to say.
To repeat myself, I am very grateful for you taking the time to respond to my question and reassuring me that this was the path to follow.
Honestly, thanks!
Click to expand...
Click to collapse
Hi. I just purchased the same tablet. I would appreciate it if you could write up a guide on this forum. It would be a help for everyone.
I'm not even sure how you unlock the bootloader on this thing!

Hi and congratulations on your purchase! The TB-606F is a solid device in my book.
Although I have by now rooted more than a dozen android devices and guess I have at least somewhat of an idea of what I am doing, I am by far no pro on the issue. Basically, I consider myself more a “guide user” than a “guide creator”, still.
But as I have benefited from the kind- and helpfulness of this community many times before, I can’t leave this call for help unanswered.
The thing is, nonetheless, I would really like to refer anyone poised to root their TB-606F to the guide for the TB-605F which I linked to in my initial post. Rooting the TB-606F, in principle, demands the user to undertake the same steps as for rooting the TB-605F.
There are, from the top of my head, only two noticeable differences or variations from that guide which I discovered:
1) firmware
As I still haven’t found a reliable source to obtain the necessary stock firmware by download from the web, the advice of fellow user 11mackey11 comes in very handy who, in response to my initial post, pointed me to the LSMA to download the firmware from your very own device.
2) unlocking bootloader
At least with my device, the fastboot commands known to me to usually unlock the bootloader (as are “fastboot oem unlock-go”, “fastboot oem unlock” or “fastboot flashing unlock”) did not do the trick. I had to resort to the command line of “fastboot flashing unlock” to finally make some progress. This might be an outlier with me device, though, as 11mackey11 did not mention the issue.
Again, I will gladly provide any assistance I can offer, but as for writing up a guide, I would mostly carbon copy turboperson123’s guide for the TB-605F mentioned above anyhow and it does not seem right to take credit for his contributions.
But if you had any specific question, please don’t hesitate to ask and I will answer it to my best knowledge (which might not be much).

Tutorial
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it

b4nd0ler0 said:
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it
Click to expand...
Click to collapse
I want to apply it to my device, have you tried this method?

Yes, tried and failed miserably. The tablet is not correctly rooted as reported by Root Checker. The su binary is there and shows it's Magisk but no root proper.
Will try again and report back when done.

b4nd0ler0 said:
Yes, tried and failed miserably. The tablet is not correctly rooted as reported by Root Checker. The su binary is there and shows it's Magisk but no root proper.
Will try again and report back when done.
Click to expand...
Click to collapse
thanks, I'm waiting for news from you. The tablet is sold very much in our country. like this in the world. I'm sure the developers will do something about this device.

b4nd0ler0 said:
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it
Click to expand...
Click to collapse
I rooted my device with this method

this method doesn't work
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?

adroid_user said:
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?
Click to expand...
Click to collapse
This method is working!
Use the Official Lenovo website to access your original "rom" file and get the "boot.img" file.
Program: Lenovo Rescue And Smart Assistant https://lnv.gy/3d8FHLi
For an article on how to download the Rom file via the program, see here. (Step 3)
https://bit.ly/2yE1nQf
Good Luck!

adroid_user said:
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?
Click to expand...
Click to collapse
You did not enable Magisk Hide

mingkee said:
You did not enable Magisk Hide
Click to expand...
Click to collapse
That was it! Thanks! You're smarter & more helpful than Google!!! ))

Hi.
After i root the tablet, i tried to delete youtube and gdrive. Then i restart the tablet but it stuck in fastboot mode. Not booting.
i couldn't install stock rom. What i must do

I did this..
i patched the boot img from the lenovo program. and i like to shut down my devices when i dont use them and now i cant make it boot. im stuck in a bootloop and its says orange alert when i boot the device. i can only get into the fastboot menu. when i try to boot with vol + and power nothing happens and when i release it starts up again in a bootloop. i cant shut it down either. it just loops and loops. cant do the rescue thing with the program either.. anybody that knows how i can fix this?

I have an out of topic question regarding this tablet.
Can The Lenovo M10 Plus (2nd Gen) 10.3" TB-X606F Output Display via HDMI to TV ???
I tried using a powered USB-C to HDMI adapter to output/mirror the tablet to a TV, but it didn't work.

Brotinger said:
Hi and congratulations on your purchase! The TB-606F is a solid device in my book.
Although I have by now rooted more than a dozen android devices and guess I have at least somewhat of an idea of what I am doing, I am by far no pro on the issue. Basically, I consider myself more a “guide user” than a “guide creator”, still.
But as I have benefited from the kind- and helpfulness of this community many times before, I can’t leave this call for help unanswered.
The thing is, nonetheless, I would really like to refer anyone poised to root their TB-606F to the guide for the TB-605F which I linked to in my initial post. Rooting the TB-606F, in principle, demands the user to undertake the same steps as for rooting the TB-605F.
There are, from the top of my head, only two noticeable differences or variations from that guide which I discovered:
1) firmware
As I still haven’t found a reliable source to obtain the necessary stock firmware by download from the web, the advice of fellow user 11mackey11 comes in very handy who, in response to my initial post, pointed me to the LSMA to download the firmware from your very own device.
2) unlocking bootloader
At least with my device, the fastboot commands known to me to usually unlock the bootloader (as are “fastboot oem unlock-go”, “fastboot oem unlock” or “fastboot flashing unlock”) did not do the trick. I had to resort to the command line of “fastboot flashing unlock” to finally make some progress. This might be an outlier with me device, though, as 11mackey11 did not mention the issue.
Again, I will gladly provide any assistance I can offer, but as for writing up a guide, I would mostly carbon copy turboperson123’s guide for the TB-605F mentioned above anyhow and it does not seem right to take credit for his contributions.
But if you had any specific question, please don’t hesitate to ask and I will answer it to my best knowledge (which might not be much).
Click to expand...
Click to collapse
Hey, thanks for all this useful info. I'm a noob when it comes to rooting. I have hit an issue, that you guys could probably easily advice me. I have got up to where you enter "fastboot flashing unlock" it comes back with something like "waiting for any device". How do I get past this point? I have tried pressing volum up as I saw on a guide however no luck.

unlock not possible
CMX939 said:
Hey, thanks for all this useful info. I'm a noob when it comes to rooting. I have hit an issue, that you guys could probably easily advice me. I have got up to where you enter "fastboot flashing unlock" it comes back with something like "waiting for any device". How do I get past this point? I have tried pressing volum up as I saw on a guide however no luck.
Click to expand...
Click to collapse
I have the same issue, "waiting for device" and adb dies.
I assume, the latest lenovo updates (Android 9) block unlocking.
The current! LMSA tool does not allow to restore an old separately downloaded firmware