Database Info

[ROOT + CWM 6.0.1.5 or 5.5.0.4] Lenovo IdeaPad A2107A (-H)

The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for your actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Windows device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
To avoid any issues turn the flight mode on so no new "data" is received by the device.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
------------------------------------------------- UPDATE 2 ---------------------------------------------------------
Tested (by user: manwithmanypiercings) USB drivers are in this post: http://forum.xda-developers.com/showpost.php?p=34651039&postcount=51
------------------------------------------------- UPDATE 3 ---------------------------------------------------------
I think there is even easier way than the one I originally posted above.
BUT I cannot be sure that it will work with all of you - the reason is that I made so many changes to my A2107A-H that I do not know whether this method works "just because it's universal" or because my tablet was tweaked far enough.
On the other hand when you consider it reasonably it looks like it's quite simple and there is no particular reason why it shouldn't work with a stock A2107A.
So...
What you need:
1 - this package: http://www.mediafire.com/download.php?fbuzi5xjofs7vgf
2 - PC running Windows 7 would be the best (7 gave me no problems at all - takes 1 minute to do it). I made it on Windows 8 as well but there is a lot more fuss to install the proper driver.
What you do:
1 - turn on USB Debugging on your tablet
2 - connect the tablet to your PC (if it's the 1st, some default drivers will install - that's ok)
3 - tap on the notifications area in the "Connect as" change to "MTP" - this is quite important !
4 - from the downloaded package run the "Flash_tool.exe"
- click "Scatter-loading" on the right and find "MT6575_Android_scatter_emmc.txt"
- in the list in the lower part of the window you MUST have the "PRELOADER" (super important) and "RECOVERY" ticked and leading to the correct files. The PRELOADER = "preloader_lenovo75_a2_ics.bin" (in the package) and the RECOVERY is the recovery file of your choice -> there are 3 in the package - pick the one you want. You can flash them over and over so if you don't like one then try the other.
5 - click "Download" above - you will see a prompt saying that not all images were loaded - that is fine - we only want to flash the RECOVERY - so click "Yes"
6 - now the Flash tool is waiting for the tablet - press "reset" on the back - Windows will recognize a new device (and WILL NOT find the driver unless you have done it before) - no worries, you have the correct driver.
7 - open Windows "Device manager" and locate the MT65..... unrecognised device -> update / install driver -> point Windows to "USB VCOM Driver" folder from the package and pick your system. My Windows 7 found the driver on the spot but asked to confirm the install - "insecure" driver - I obviously clicked "install anyway" and so should you.
8 - once the driver is loaded the Flash tool will flash the new recovery file - you will see some colour progress bars in the program - at the end you should see a green circle.
That is it. Unplug the tablet, press reset on the back and you can now enter the recovery mode.
FUN FACT: the "reset" button on the back is not really a reset button, it's more like physical cut off button to temporarily disconnect the battery.

I have the Lenovo A2107A under Vodafone's brand Vodafone Smart Tab II 7
It has Android version 4.0.4 and compilation: A2107A_A404_010_002_120913_VODA
Imanaged to root it and install CWM using this thread. But somehow I was not able to create the CWM modded recovery.img
I used the one provided here and it worked fine.
Thanks for this.

I can't connect tablet to PC
csns said:
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for you actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Window device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
Click to expand...
Click to collapse
csns thanks for your guide
Unfortunately I can't connect my tablet to pc in USB debbuging mode. I tried a lot of drivers from net but without success.. Pls let me know the right way to root my tablet.

optical99 said:
csns thanks for your guide
Unfortunately I can't connect my tablet to pc in USB debbuging mode. I tried a lot of drivers from net but without success.. Pls let me know the right way to root my tablet.
Click to expand...
Click to collapse
Hi there,
Try those drivers: http://www.mediafire.com/?vx2hyv7dpwlmeyy
They come from the current Android SDK but I am running a 64 bit system and I'm not sure if those drivers will work with 32 bit systems.
Fingers crossed!

I tried with yor recommend dirvers and with a lot of others and doesn't work. I have to unrecognised denices in Device Manager - A2107A-H and MTP.
I am very upset about Lenovo because their support doesn't exist.

optical99 said:
I tried with yor recommend dirvers and with a lot of others and doesn't work. I have to unrecognised denices in Device Manager - A2107A-H and MTP.
I am very upset about Lenovo because their support doesn't exist.
Click to expand...
Click to collapse
I had to use the PDANET from this link.
http://forum.xda-developers.com/showthread.php?t=1982334&page=6
Should be the first post.
Sent from my Samsung Galaxy Note running JellyBeer using Xparent ICS Blue Tapatalk 2

First of all, a ton of thanx to csns for posting this detailed procedure along with all required scripts and tools...
I have just one question...Which Modified ROM did you install as I see you have unlocked calling feature in the video you posted???
I asked because the MOD ROM by pemergency in the other thread is for the 16 GB and creates some issues in the device...But your's is 4 GB, as is mine...
Thanx in advance

makbro said:
First of all, a ton of thanx to csns for posting this detailed procedure along with all required scripts and tools...
I have just one question...Which Modified ROM did you install as I see you have unlocked calling feature in the video you posted???
I asked because the MOD ROM by pemergency in the other thread is for the 16 GB and creates some issues in the device...But your's is 4 GB, as is mine...
Thanx in advance
Click to expand...
Click to collapse
I'm glad you find my post useful.
As for the calling feature - it's not actually working
You see, to have the calling app (in other words "the phone" app) in the app drawer all you need to do is change one tiny value in framework-res.apk.
This value is telling the system weather the whole device is supposed to handle voice calls or not. I just tricked the system to make the Phone.apk visible but there is a lot more do be done in order to make a real call over the cellular network.
I've just had this tablet for a week and I didn't have much time to dig into this topic. Let's see what the weekend brings
Be patient, I think it's just a matter of time when someone posts a user friendly guide... Or search yourself and share what you find with the community.
Take care.

works fine
manwithmanypiercings
I have gained acces to tabled with PDAnet drivers...thanks a lot
csns
I followed all steps and installed CWM 6015. Very nice tutorial...I thought it's simpliest way...respect for your job

optical99 said:
manwithmanypiercings
I have gained acces to tabled with PDAnet drivers...thanks a lot
csns
I followed all steps and installed CWM 6015. Very nice tutorial...I thought it's simpliest way...respect for your job
Click to expand...
Click to collapse
Glad I could help by showing the link. Glad you got everything else taken care of.

This is an awesome post! Thak you very much.

Need help at step 4
csns said:
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for your actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Windows device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
To avoid any issues turn the flight mode on so no new "data" is received by the device.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
------------------------------------------------- UPDATE 2 ---------------------------------------------------------
Tested (by user: manwithmanypiercings) USB drivers are in this post: http://forum.xda-developers.com/showpost.php?p=34651039&postcount=51
Click to expand...
Click to collapse
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance

makbro said:
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
Click to expand...
Click to collapse
Well, this happened to me once and I think the reason was that the path was too long - I guess it may have something to do with the fact that the .bat is a simple "program" and can have some problems with handling long paths.. specially with "national" character in them.
Try finding a location as close to the root of the drive as possible, and make sure you have full R/W access. Or try with a pendrive for example.
Since you made a backup of your ROM I think you are quite safe with using the recovery I uploaded - first post -> UPDATE 1.
They seem to fit all 2107A devices. If not I will tell you how to restore the original recovery from your backup.
You can also read UPDATE 3 I just made - your choice.

Thanx
Hello csns,
Thanx to your help, I have also got CWM recovery working on my device.
BTW I saw these two posts on a forum in Russian (I guess)...I used google translate and am pretty sure these two posts that I provide links for below have two modified ROMs with everything working, including phone and radio !!! The only draw back is that once you flash these ROMs you'll get Russian language, which can be changed to English from the language menu
I plan to fo it myself as well tomorrow,would let you know the outcome
http://4pda.ru/forum/index.php?showtopic=286687&st=920 (go down to the post labelled "A2107_Foxtrot_v100")
and
http://4pda.ru/forum/index.php?showtopic=286687&st=440 (go down to the post labelled "Прошивка Tasemart
MOD 1.1")
and of course you can also try the "Angeleas_Final" modified ROM also that I'll upload and provide links to tomorrow
Thanx again for all your help !!!

I also had many trouble getting the cwm bat file to work. It is very picky about its path and arguments on Win7.
I moved the michfood folder to C: and moved my own recovery.img to C:\michfood\recovery.old
cd C:\michfood
cwmr\ 6015.bat recovery.old
That worked - otherwise it wouldnt finish the cpio stuff.
Reworking that horrible script to work on linux would have probably taken less time -_-
Anyway - thanks!

Permissions problems on Windows7
Hi,
I Had the same problem.
makbro said:
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
Click to expand...
Click to collapse
My solution:
It was required to use a directory not to deep in folder structures, so the best is as short as possible like "C:\michfood".
I had to add "Full Control" permissions for "everyone" to the "michfood"-directory and enable the "replicate permissions to subfolders"-option (I don't know the exact designation because I use it in german ... )
I had to delete an existing "Recovery" folder inside the "michfood"-directory from earlier attempts to create the new file and for this I had to take over the ownership of the "Recovery" folder before I was able to delete it.
The original Recovery.img must be in a different folder than "michfood". This can be on the desktop but for a shorter path it could be in the root directory.
I had success after copying "cwmr 6015.bat" to "go.bat" (it's shorter and does not contain any space in it) and calling it from command line from its directory( C:\>cd C:\michfood ) with: "go C:\Recovery.img" ( I had Recovery.img on C:\ ).
makbro said:
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
Click to expand...
Click to collapse
I hope this helps ...

Thanx
Thanx for the suggestions everyone, appreciate it...I got it working in the mean time on a WinXP desktop without any problem

makbro said:
Thanx for the suggestions everyone, appreciate it...I got it working in the mean time on a WinXP desktop without any problem
Click to expand...
Click to collapse
HOW?
Tell me what you did...

Cristian.Ene said:
HOW?
Tell me what you did...
Click to expand...
Click to collapse
I copied the folder as "C:\michfoods" and recovery image file as "C:\recovery.img" and gave the command "cwmr6015 C:\recovery.img"...Before that, I removed the space from the file name "cwmr 6015.bat" and saved it as "cwmr6015.bat".

Hi, i rooted succesfuly my a2107a device and installed backup Gscript ...loading "back_mt6575_a4_v2c.sh and saving it , but when it comes to run...nothing...only the counter saying how many sec's till stop.Any ideeas why?

Dolby Atmos [ All Android above 4.3]

DOLBY ATMOS​
For Android 4.3x​
Since this is a software, it should work on all android ( 4.3 and above ). Also contains two types of installation 'one with custom recovery and other without custom recovery' . If you have installed other dolby, it may conflict. Links are given at the bottom. .
***WARNING***​1. DO THIS AT YOUR RISK. (I am not responsible for any damage).
2. MAKE A BACKUP OF YOUR ROM/FIRMWARE
3. BACKUP THE AUDIO_ EFFECTS.CONF into your sd card as there is some reason. ( located in the path /system/etc/audio_effects.conf.)
REQUIREMENTS​1. Rooted android device. ( compulsory )
2. Custom recovery if you have. ( not compulsory ).
3. If you dont have custom recovery, then download ES file explorer from playstore open it and given it permission of root with superuser . Steps below.
INSTALLATION STEPS​
Install Without Recovery​
1. Open ES file explorer
2. Go to left top and tap menu.
3. Go to the bottom to the tab 'tools' .
4. In the 'tools' tab, tap on 'Root explorer' and give permission to superuser.
Note:- whatever you paste( the files of dolby) , then you have to change that file's or folder's permission, ( only to be done after you paste each file and make each folders) steps below =
I. ( for the files) keep holding on the file you have pasted and go to 'properties' and tap 'change permission' , now tick all in the first column, in second column only the first to be ticked. Now tap OK ( these are for the files you create or paste).
II. ( for the folder) same steps as above, now in the first column tick all, second column only the first to be ticked. In the third column all to be ticked.
5. Now go to path /system/app
6. Make folders 'As' and 'AsUI' ( only if other apps are in each folders / if all the apps are mixed then skip this step).
7. Paste As and AsUI in apps (if other are mixed. Any doubt means feel free to ask).
OR​
7. Paste 'As.apk' in the folder 'As' and 'AsUI.apk' in the folder 'AsUI' ( if other apps are in each folder).[ Any doubt means feel free to ask.]
8.Change those folders and apps permission as given above.
9. Go to path /system/etc/ and now paste audio_effect.conf (if already exists take a backup of yours and paste there. If you want me to edit your phones original audio.conf, then upload it and I will add dolby to that for you, so that everything in your audio_effect.conf remains same ( I will just add some lines there and it's still your audio_effect.conf.
10. Change permission of that.
11. In the same path, make a folder 'dolby'. Change permission of that folder.
12. In the folder 'dolby' paste the file 'ds-default.xml' and change its permission.
13. Go to path /system/lib and paste the file 'libdlbdapstorage.so' and change its permission.
14. Go to path /system/lib/sounds and paste the file 'libswdap-mod.so' and change its permission.
15. Go to path /system/vendor/etc (if path not available make a folder and change permission).
16. In the above path, paste 'audio_effects.conf' and change the permission.
17. Just reboot your device and you have successfully installed.
Install with Recovery​
1. Just flash it with your custom recovery.
2. Boot your device and have successfully installed.
UNINSTALLATION STEPS​
Uninstall Without Recovery​
1. Just delete the files you have pasted to install dolby atmos with ES File Explorer. ( only the files I gave )
2. Replace the audio_effects.conf with your backup and change permission as defined above. ( delete the one I gave you and paste there with your old one.)
3. Reboot your device and you have successfully uninstalled.
Uninstall with Recovery​
1. Just flash the UNINSTALL.zip with your custom recovery. ( links below)
2. Reboot your device and you have successfully uninstalled.
Links :-​
MOD EDIT: Removed
Enjoy

Thread closed. Please review the forum rules, specifically rules 5 and 12.
Continue discussion in this thread: http://forum.xda-developers.com/android/apps-games/mod-dolby-atmos-t3109446
Nathan
Forum Moderator

Deodexed and install Xposed Galaxy Note3 SCL22 (SM-N900J) Stock/Lollipop 5.0 [How To]

How to Deodexed and install Xposed Samsung Galaxy Note 3 / SCL22 (SM-N900J) stock Lollipop 5.0
----------------------------------------------------------------------------------------------------
I'll explain you step by step how to do this so please read the post very carefully.
--------------------------------------------------------------------------------------------------------------------------
#. Before you say "there is many threads taking about same subject" and start complaining and reporting this thread, please understand the device im taking about SCL22 (SM-N900J), this device different than AT&T or any other models. SCL22 provided by "au KDDI" one of Japanese major network provider. And KDDI specially custom made this devices from SAMSUNG, Korea only for KDDI network. There is some app's only work for stock ROM. If you install custom ROM you can't install or get register with KDDI network (ex- auMail.apk, auoneidsetting.apk,etc..) app's like auMail very important for Japanese users including me. And another there there is some system app's you can't even copy by adb (I'll talk about this later in the post). So if you are not using SCL22 in Japan register and using KDDI network, then you don't know.
----------------------------------------------------------------------------------------------------------------------------
Before start here is some info ---------------------------
Brick -
What is brick. I guess you all seen a brick before, just a man made stone. Staying there do nothing. "Device Brick" also same. When your device get brick it's do nothing. The thing you must know, there is two kind of bricks
1. Soft brick.
2. Hard brick.
Soft brick - happens all the time, easily can happen, less dangerous. And easy to fix. (That's why everyone saying to keep a nandroid backup)
Hard brick - very dangerous, very hard to fix, some devices close to impossible to fix. But silver line is it's happens very rarely, like 2 %. And some new devices it's impossible to get hard brick. (But always be careful about what you do)
TWRP BackUp -
Keeping a recovery back up very important. If you made a mistake, flash a wrong ROM, or mod or something like that and you will get a bootloop (soft brick) then you can use the recovery back up to fix your device very easily. (Always keep a clean nandroid backup)
Odexed or Deodexed -
Odexed - faster loading of apps into memory. Each .apk has a corresponding .odex. When the application is used by either the system or the user.
Deodexed - has only the .apk file. When the application is called into memory from only pulling the data from it’s .apk, this takes longer due to not being optimized for easier retrieval from the system. (just remember ".apk and .odex compressed in to one .apk file")
This is the simplest way to know your ROM is odex or deodex-
*Download and install any Root explorer (ES File Explorer recommend and you need Rooted device)
*Open the File Explorer and navigate to /system/app
*Open any app directory
*If your ROM is Odexed you can see the .apk and .odex file in the app directory
*If you don't see any .odex file then your ROM is most likely deodexed
OK lets get started...
what you need and all the STEPS -
01. Your phone must be pre-rooted and USB debug enabled. Read this - http://forum.xda-developers.com/galaxy-note-3/general/samsung-galaxy-note-3-scl22-au-kddi-t2964801
02. Android SDK with fastboot and ADB working properly with Google USB Driver installed (Or you can find only ADB and fast boot file .zip but i DON'T recommend that) read and download - https://developer.android.com/studio/run/win-usb.html#WinUsbDriver
03. Turned on USB debugging in you device and connect to PC.
04. Create a new folder in your PC to keep your soon to be download system files, you can name "system" or anything you want but make sure there is NO SPACE ex- E:\system or D:\system
05. Open the adb shell (how to open the adb shell- navigate to the folder that SDK installed, open "platform-tools" folder, keyboard Shift key + Right click, click "Open command window here")
06. Now to check everything works fine run this command-
adb devices
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you see "SH16WV8028** device" (it can be any numbers or letters for you) like above picture, then you are clear for next step. if not please make sure you installed SDK, Google latest usb drivers and also your device drivers. if it works fine then let's move to next step...
07. Now run this -
adb pull /system/app /app/
Click to expand...
Click to collapse
It will pull all your system app's in to your PC C:\ drive (Like you will see new folder - C:\app)if you get any "permission errors" make a note witch app's need permissions.
***** For SCL22 users ONLY- when you run (adb pull /system/app /app/) if you get this error messages like - FeliCaWebPluginBoot\arm\MobileFeliCaWebPluginBoot.odex.xz': Permission denied - you need to navigate to that apps folders using ES FileExplorer and change Permission (give all Permission by clicking all check boxes) and then manually copy and paste that file to your SD card and to your PC. You also need to change Permission and copy this folders too "preloadedkiosk, preloadedsso and preloadFactoryResetOnly" to system folder in your PC.
08. Now run this -
adb pull /system/priv-app /priv-app/
Click to expand...
Click to collapse
09. Now run this -
adb pull /system/framework /framework/
Click to expand...
Click to collapse
10. Now run this -
adb pull /system/odex.app.sqsh
adb pull /system/odex.priv-app.sqsh
Click to expand...
Click to collapse
If you don't have ".sqsh" then you get error. But don't worry about that continue to next step -
11. Now you will see 3 folders call "app, priv-app, framework" now copy or those folders to "system" folder before you made.
if you don't have 7-zip download and install it too - http://www.7-zip.org/download.html
12. Now you need to download and extract the - http://forum.xda-developers.com/attachment.php?attachmentid=3268390&d=1429332195
Original form - http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857
13. Now run the "JoelDroidLollipopBatchDeodexer.exe" click on Brows button and select the "system" you early create and copied app, priv-app, framework. And click on "Start process" button.
If process successfully then your apps and framework are now deodexed. One more step to do. replacing all 3 folders. Let's do that ...
14. Now download this zip file - http://forum.xda-developers.com/attachment.php?attachmentid=3231531&d=1427457507
DO OT UNZIP it just open the zip file using 7zip and open the you will find empty system folder inside that. open it, and copy and paste app, priv-app, framework folders that deodexed. and close 7zip. Press "yes" if 7zip asked to save it.
( installer template.zip only made for wipe and replace the three system folders)
15. Copy that InstallerTemplate.zip file to your SD-Card. wipe cache, dalvik cache and install the zip file.
First time boot will take some time. So please be patient....
Hurry.! you got Deodexed ROM
----------------------------------------------------------------------------------------------------------------------
If this work for you, don't just leave, please hit the "Thanks.!" button. It's FREE - And always, always thanks the developers. And if you kind enough to donate, Please donate to the developers first.
------------------------------------------------------------------------------------------------------------------------
===================================================================================================
I want to thanks @joeldroid , @townsenk for those amazing files. Thank you so much for your time and hard work.
===================================================================================================

How to install Xposed framework on your device
How to install Xposed framework on your device
OK, then let's start -
First download this 3 files and copy them to your SD Card.
01. Xposed v75 sdk21 arm arter97 snapdragon requestConcurrentGC.zip - Download
02. XposedInstaller 3.0 alpha4.apk - Download
03. Xposed uninstaller.zip - Download
04. Now install XposedInstaller 3.0 alpha4.apk
05. Boot to your custom recovery (TWRP recommend)
06. Now install Xposed v75 sdk21 arm arter97 snapdragon requestConcurrentGC.zip reboot to system
Remember first time boot will take some time (10 to 20 minutes/ it depend on your ROM size)
How to uninstall Xposed -
Flash the xposed uninstaller 20150831 arm.zip on the custom recovery.
That's it.! Enjoy
----------------------------------------------------------------------------------------------------------------------------------------------
If this work for you, don't just leave, please hit the "Thanks.!" button. It's FREE - Also please thank the awesome developers who spend so much time to make this possible. If you kind enough for Donate please donate to below developers i mention. I just make this post to give you the steps and correct files for SCL22 so you ain't gonna mess up. But below developers did the hardest part and create this thing possible. So please donate to them.
-----------------------------------------------------------------------------------------------------------------------------------------------------
I like to thanks @arter97, @rovo89, @wanam, @_riddle for all your time and hard work, Thank you guys so so much.
-------------------------------------------------------------------------------------------------------------------------------------------
This guide and files only for Samsung Galaxy Note 3 SCL22 (SM-N900J) Japanese device
-------------------------------------------------------------------------------------------------------------------------------------------

#2

#1

DeadCode1 said:
How to Deodexed and install Xposed Samsung Galaxy Note 3 / SCL22 (SM-N900J) stock Lollipop 5.0
----------------------------------------------------------------------------------------------------
I'll explain you step by step how to do this so please read the post very carefully.
--------------------------------------------------------------------------------------------------------------------------
#. Before you say "there is many threads taking about same subject" and start complaining and reporting this thread, please understand the device im taking about SCL22 (SM-N900J), this device different than AT&T or any other models. SCL22 provided by "au KDDI" one of Japanese major network provider. And KDDI specially custom made this devices from SAMSUNG, Korea only for KDDI network. There is some app's only work for stock ROM. If you install custom ROM you can't install or get register with KDDI network (ex- auMail.apk, auoneidsetting.apk,etc..) app's like auMail very important for Japanese users including me. And another there there is some system app's you can't even copy by adb (I'll talk about this later in the post). So if you are not using SCL22 in Japan register and using KDDI network, then you don't know.
----------------------------------------------------------------------------------------------------------------------------
Before start here is some info ---------------------------
Brick -
What is brick. I guess you all seen a brick before, just a man made stone. Staying there do nothing. "Device Brick" also same. When your device get brick it's do nothing. The thing you must know, there is two kind of bricks
1. Soft brick.
2. Hard brick.
Soft brick - happens all the time, easily can happen, less dangerous. And easy to fix. (That's why everyone saying to keep a nandroid backup)
Hard brick - very dangerous, very hard to fix, some devices close to impossible to fix. But silver line is it's happens very rarely, like 2 %. And some new devices it's impossible to get hard brick. (But always be careful about what you do)
TWRP BackUp -
Keeping a recovery back up very important. If you made a mistake, flash a wrong ROM, or mod or something like that and you will get a bootloop (soft brick) then you can use the recovery back up to fix your device very easily. (Always keep a clean nandroid backup)
Odexed or Deodexed -
Odexed - faster loading of apps into memory. Each .apk has a corresponding .odex. When the application is used by either the system or the user.
Deodexed - has only the .apk file. When the application is called into memory from only pulling the data from it’s .apk, this takes longer due to not being optimized for easier retrieval from the system. (just remember ".apk and .odex compressed in to one .apk file")
This is the simplest way to know your ROM is odex or deodex-
*Download and install any Root explorer (ES File Explorer recommend and you need Rooted device)
*Open the File Explorer and navigate to /system/app
*Open any app directory
*If your ROM is Odexed you can see the .apk and .odex file in the app directory
*If you don't see any .odex file then your ROM is most likely deodexed
OK lets get started...
what you need and all the STEPS -
01. Your phone must be pre-rooted and USB debug enabled. Read this - http://forum.xda-developers.com/galaxy-note-3/general/samsung-galaxy-note-3-scl22-au-kddi-t2964801
02. Android SDK with fastboot and ADB working properly with Google USB Driver installed (Or you can find only ADB and fast boot file .zip but i DON'T recommend that) read and download - https://developer.android.com/studio/run/win-usb.html#WinUsbDriver
03. Turned on USB debugging in you device and connect to PC.
04. Create a new folder in your PC to keep your soon to be download system files, you can name "system" or anything you want but make sure there is NO SPACE ex- E:\system or D:\system
05. Open the adb shell (how to open the adb shell- navigate to the folder that SDK installed, open "platform-tools" folder, keyboard Shift key + Right click, click "Open command window here")
06. Now to check everything works fine run this command-
if you see "SH16WV8028** device" (it can be any numbers or letters for you) like above picture, then you are clear for next step. if not please make sure you installed SDK, Google latest usb drivers and also your device drivers. if it works fine then let's move to next step...
07. Now run this -
It will pull all your system app's in to your PC C:\ drive (Like you will see new folder - C:\app)if you get any "permission errors" make a note witch app's need permissions.
***** For SCL22 users ONLY- when you run (adb pull /system/app /app/) if you get this error messages like - FeliCaWebPluginBoot\arm\MobileFeliCaWebPluginBoot.odex.xz': Permission denied - you need to navigate to that apps folders using ES FileExplorer and change Permission (give all Permission by clicking all check boxes) and then manually copy and paste that file to your SD card and to your PC. You also need to change Permission and copy this folders too "preloadedkiosk, preloadedsso and preloadFactoryResetOnly" to system folder in your PC.
08. Now run this -
09. Now run this -
10. Now run this -
If you don't have ".sqsh" then you get error. But don't worry about that continue to next step -
11. Now you will see 3 folders call "app, priv-app, framework" now copy or those folders to "system" folder before you made.
if you don't have 7-zip download and install it too - http://www.7-zip.org/download.html
12. Now you need to download and extract the - http://forum.xda-developers.com/attachment.php?attachmentid=3268390&d=1429332195
Original form - http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857
13. Now run the "JoelDroidLollipopBatchDeodexer.exe" click on Brows button and select the "system" you early create and copied app, priv-app, framework. And click on "Start process" button.
If process successfully then your apps and framework are now deodexed. One more step to do. replacing all 3 folders. Let's do that ...
14. Now download this zip file - http://forum.xda-developers.com/attachment.php?attachmentid=3231531&d=1427457507
DO OT UNZIP it just open the zip file using 7zip and open the you will find empty system folder inside that. open it, and copy and paste app, priv-app, framework folders that deodexed. and close 7zip. Press "yes" if 7zip asked to save it.
( installer template.zip only made for wipe and replace the three system folders)
15. Copy that InstallerTemplate.zip file to your SD-Card. wipe cache, dalvik cache and install the zip file.
First time boot will take some time. So please be patient....
Hurry.! you got Deodexed ROM
----------------------------------------------------------------------------------------------------------------------
If this work for you, don't just leave, please hit the "Thanks.!" button. It's FREE - And always, always thanks the developers. And if you kind enough to donate, Please donate to the developers first.
------------------------------------------------------------------------------------------------------------------------
===================================================================================================
I want to thanks @joeldroid , @townsenk for those amazing files. Thank you so much for your time and hard work.
===================================================================================================
Click to expand...
Click to collapse
wifi issues after deodexing and flashing zip. Now my wifi wont connect to any wifi device. its stuck at obtaining ip address

Did you wipe delvik cache/ cache.?
What is your device model number.?
My wifi working fine.!

Thanks for your tutorial.
Alternatively, there is now an xposed install package that works on stock, odexed TouchWiz ROMS.
You can find more infos here: http://forum.xda-developers.com/showpost.php?p=65373013&postcount=3960
For those that are still looking how to install, read more of the thread there. A good start could be: http://forum.xda-developers.com/showpost.php?p=68456346&postcount=4588

frenchy2k1 said:
Thanks for your tutorial.
Alternatively, there is now an xposed install package that works on stock, odexed TouchWiz ROMS.
Click to expand...
Click to collapse
Thank you for the info.
I made this post about deodexed not only for installing xposed, deodexed can save you some space, and you can use for develop. i just combine both subjects in one post.

MediaTek MT8735B root, custom recovery, firmware help

Hello everyone
I've recently bought a Lenovo Tab4 TB-7504X.
This Tablet has a MT8735B SoC. I absolutely need to have root since i need to edit a few system files.
However everything i've tried so far didn't work.
I tried a few one-click-root apps, like Framaroot. After everything failed i tried kingroot and kingoroot (didn't want to use them because of all the negativity they have regarding sending IMEI to their servers etc.). But even those tools failed. I also tried the pc version of kingroot since they say that it has a higher chance, but it also failed. I have also read that the MT8735 is just a rebranded MT6735, but frankly i'm too scared to try and flash a custom recovery for that chip, considerin i don't have a firmware file in case the tablet bricks.
Has anybody found a method to root this chip? I don't really need a custom recovery (altough it would be nice to have), and i don't need the firmware either since i'm planing to stay on stock (again, would be nice to have to clean flash after all the crap i've installed and tried).
Tl;Dr:
Has anyone a working root method for this chip?

@yewoni
did you manage in the meantime?
I'm planning to buy a TB-7504X and also need root to access some secure settings (air plane mode) via tasker...

@yewoni, @pipipde
any news here?

d1dd1 said:
@yewoni, @pipipde
any news here?
Click to expand...
Click to collapse
Sorry, I decided to buy a different tablet

Root Lenovo Tab 7 TB-7504X Systemlessly
Root Lenovo Tab 4 7 TB-7504X Systemlessly!!
Hello all!!?
Here I will guide you to root Lenovo Tab 4 7 TB-7504X with the chipset MT8735B and Android version 7.0 that also systemlessly!! So let's get tuned into the Step by Step Guide...?
Firstly, I am not responsible for any kind of demage caused to your phone!!
Actually there are two methords of doing so...
Moving on to first one (Simplest),
You need to download latest version of MTK Easy Su v1.0.6 and the Magisk Manager specifically v7.1.1 I will provide link for both of them below...
Install both of them...
Now Firstly open the MTK Easy Su apk and just tap on 'Activate Bootless Root' if it says 'Exit value 0' in the Log section that means you have Root access on your phone...
Note:- Don't try to update Magisk or Magisk Masnager or Set environment for modules to work properly in Magisk Manager, else you will brick your phone
- Don't update Magisk Manager Directly from the apk
- The following process is done on lock bootloader so be carefull.
- You will have to Open the MTK Easy Su apk and tap on 'Activate Bootless Root' each and every time you Reboot your phone...
Pros:-
- Systemless Root
Cons:-
-Will not be able to Update Magisk Manager or Migisk itself
- Will not be able to install Magisk Modules
Second Method:-
For this to work on your phone you need couple of apks and Files...I will provide all the links at the end of this post...
Again, I am not responsible for any kind of demage caused to your phone!!
- Firstly, You need to download an apk named 'init.d Scripts Support' and also need to know your phone's architecture i.e 32 bit or 64 bit if you don't know just download any apk like CPU-Z or anything like that and note your phone's architecture...
- Now, you need to create an folder named 'init.d' in your phone's internal storage and again create another folder named 'bin' inside the 'init.d' folder
Now, you need to move some files in these folders to gain Root access...So let's move on...
- Firstly, Unzip all the Files...
- Open folder named 'magisk-boot' and copy the file named 'magisk-boot.sh' and paste it in 'init.d' folder
- Moving on to next file, then open folder named 'mtk-su_r22' then open the folder based on your phone's architecture i.e 'arm' or 'arm64' (For 32 bit architecture open 'arm' & For 64 bit architecture open 'arm64') and copy the file named 'mtk-su' and just paste the file inside the 'bin' folder of 'init.d' folder
- Moving on to last file to copy, open the folder named 'Magisk-20.4', then open folder named 'arm' there you will find 3 files here, we are just conserned about 2 files named 'magiskinit' & 'magiskinit64'. Just copy one of the two files based on your architecture (If 32 bit then copy 'magiskinit' & if 64 bit just copy 'magiskinit64') and paste it in 'bin' folder of 'init.d' folder. The one who have 64 bit architecture need to make a small change in the file 'magiskinit64' we just copied to 'bin' folder. Just rename the file and remove '64' written behind the file name.
Now your 90% of work has been completed!!
Now install the latest version of 'Magisk Manager' currently v7.5.1 is the latest.
- Now open 'init.d scripts support' apk and check the 'Run scripts at boot time' option.
- Then set 'Execution delay' to 'No delay'
- Now tap on 'Selected folder' and just locate the 'init.d' folder and select it.
Note:- Please let be the option 'Try to acquire root privileges' Uncheked!!
Lastly Reboot your phone and after Rebooting open the 'init.d scripts support' apk and just tap on 'Run scripts now' it will show 1 File selected and then it will Show 1 File Executed'!!
Then just tap 'Show last execution results' (You may need to watch an add every 24 hours) and if it shows 'client: launching new main daemon process' at the very least of the execution results...Congratulations!! Now you have got Systemless Root on your Lenovo Tab 7 TB-7504X successfully!!
Note:-
- Don't Mess around things you don't know on a locked bootloader or you would brick your device.
- Don't update Magisk via the apk itself
- Be Carefull while installing Magisk Madules on a locked bootloader
- You will have to Run the init.d scripts support apk each and every time you reboot your phone to have root access enabled
You can search on YouTube for 'How to root Lenovo Tab 7 TB-7504X' (Second Method) the video is recently made by me
Channel's Name:- Tricky Everything
Sorry For the poor video and audio quality
If You Like the video please Like,Share, Subscribe and Comment...
Important Note:-
You can update the files Needed to have root access (basically Magisk itself) just be sure to place the correct file in the correct location and with the correct name!!
Files Needed to Root (First Method):-
MTK Easy Su v1.0.6 apk
Magisk Manager v7.1.1 apk
Files Needed (Second Method):-
MTK su_r22.zip (latest version)
Latest Magisk-boot.zip
Magisk-20.4.zip
Magisk Manager-v7.5.1 apk
Sorry I can't post links on XDA Right Now
I was supposed to post links but XDA did not allow me to post links
Please do search for the apks and zips needed to root Lenovo Tab 7 TB-7504X on Google You will surely get it
I have listed all the the needed apks and zips name and version for particular Rooting Method.
Thank You
---------- Post added at 08:45 PM ---------- Previous post was at 08:31 PM ----------
I hope Unlocking Bootloader could now be possible after getting Root access
(By understanding system buildup of this Tab)
Eagerly Waiting
Thank You

New Gen Google Assistant on Mi A2 Lite

THIS IS NOT MY GUIDE IT WAS A GUIDE SHARED ON TELEGRAM On Pixel Props Channel WHO HAD MENTIONED THE CREDITS AND I HAVE JUST FORWARDED THE GUIDE HERE SO THAT OTHER PEOPLE CAN USE IT AS I HAVE TESTED THIS ON MY PHONE RUNNING ANDROID 10
Prerequisites:
1. Rooted Via Magisk
2. Bootloader Unlocked Obv
3. Android 10
PLEASE READ FIRST
1. Please follow the guide properly and use root explorer (the one provided inside the zip file) do not use any other explorer to change the permissions or to edit the XML File I followed this guide which was provided in a telegram channel and I faced issues because I didn't do the things I have mentioned above properly and used my own explorer.
Also if you are using this in conjunction with any other majesty modules that interferes with the gesture navigation system make sure to disable that too as it would not allow it to run properly.
Guide:
How i activated NGA ( New Generation Assistant ) on any AOSP rom
1. Download attached file (Google Assistant Zip File ) and extract. Open GEL.GSAPrefs.xml with MT file manager or Root Explorer and search flag named "GSAPrefs.google_account" and change the flag value with your gmail. Save.
2. Spoof your device to Pixel 4 or Pixel 4 XL, I'm using this module @PixelProps or you can edit ro.product.model in build.prop to "Pixel 4" and reboot
3. After reboot, trigger google assistant by using corner gesture. New window will be open asking you to download new assistant. Click download.
4. Copy edited GEL.GSAPrefs.xml to /data/data/com.google.android.googlequicksearchbox/shared_prefs/ and set permission to 0660 (rw-rw----)
5. Put the folder en-US to /system/product/usr/srec/
set permission folder en-US to rwxr-xr-x and set permission all file inside the folder en-US to rw-r-r
6. Put the folder sysconfig to /system/product/etc/
set permission folder sysconfig to rwxr-xr-x and set permission all file inside the folder sysconfig to rw-r-r
7. Install ngaresources.apk like you install other apk and reboot
Credits : Nishant Kumar, Evo X Team, Zelion, atticusfinch
Files Needed: (For some reason I cannot attach the files directly via XDA Labs so I going to attach G-Drive Links)
Google Assistant Zip File:
https://drive.google.com/file/d/11hemDKg2La2S5ulu3CQm6v_sQxiD2W2Q/view?usp=drivesdk
Use the security patch of the month you are currently on for e.g (if you are on the July patch you will flash the July spoof)
July Spoof Pixel 4XL : https://drive.google.com/file/d/11Y_CvvYoJo5wpRNo3dItUqUBaZaJ3UTd/view?usp=drivesdk
August Spoof Pixel 4XL:
https://drive.google.com/file/d/11gcS3nSm7SllxLThBVDQQ4rsrTzkj9-W/view?usp=drivesdk
Flash this If you have a black coloured invisible assistant:
https://drive.google.com/file/d/11kLIBtWm_dUMnwfK0p3OS70iEPByYF7U/view?usp=drivesdk

are there any way for unroot device ?

Reza 7 said:
are there any way for unroot device ?
Click to expand...
Click to collapse
Uninstall Magisk Maybe

Aadil Gillani said:
THIS IS NOT MY GUIDE IT WAS A GUIDE SHARED ON TELEGRAM On Pixel Props Channel WHO HAD MENTIONED THE CREDITS AND I HAVE JUST FORWARDED THE GUIDE HERE SO THAT OTHER PEOPLE CAN USE IT AS I HAVE TESTED THIS ON MY PHONE RUNNING ANDROID 10
Prerequisites:
1. Rooted Via Magisk
2. Bootloader Unlocked Obv
3. Android 10
PLEASE READ FIRST
1. Please follow the guide properly and use root explorer (the one provided inside the zip file) do not use any other explorer to change the permissions or to edit the XML File I followed this guide which was provided in a telegram channel and I faced issues because I didn't do the things I have mentioned above properly and used my own explorer.
Also if you are using this in conjunction with any other majesty modules that interferes with the gesture navigation system make sure to disable that too as it would not allow it to run properly.
Guide:
How i activated NGA ( New Generation Assistant ) on any AOSP rom
1. Download attached file (Google Assistant Zip File ) and extract. Open GEL.GSAPrefs.xml with MT file manager or Root Explorer and search flag named "GSAPrefs.google_account" and change the flag value with your gmail. Save.
2. Spoof your device to Pixel 4 or Pixel 4 XL, I'm using this module @PixelProps or you can edit ro.product.model in build.prop to "Pixel 4" and reboot
3. After reboot, trigger google assistant by using corner gesture. New window will be open asking you to download new assistant. Click download.
4. Copy edited GEL.GSAPrefs.xml to /data/data/com.google.android.googlequicksearchbox/shared_prefs/ and set permission to 0660 (rw-rw----)
5. Put the folder en-US to /system/product/usr/srec/
set permission folder en-US to rwxr-xr-x and set permission all file inside the folder en-US to rw-r-r
6. Put the folder sysconfig to /system/product/etc/
set permission folder sysconfig to rwxr-xr-x and set permission all file inside the folder sysconfig to rw-r-r
7. Install ngaresources.apk like you install other apk and reboot
Credits : Nishant Kumar, Evo X Team, Zelion, atticusfinch
Files Needed: (For some reason I cannot attach the files directly via XDA Labs so I going to attach G-Drive Links)
Google Assistant Zip File:
https://drive.google.com/file/d/11hemDKg2La2S5ulu3CQm6v_sQxiD2W2Q/view?usp=drivesdk
Use the security patch of the month you are currently on for e.g (if you are on the July patch you will flash the July spoof)
July Spoof Pixel 4XL : https://drive.google.com/file/d/11Y_CvvYoJo5wpRNo3dItUqUBaZaJ3UTd/view?usp=drivesdk
August Spoof Pixel 4XL:
https://drive.google.com/file/d/11gcS3nSm7SllxLThBVDQQ4rsrTzkj9-W/view?usp=drivesdk
Flash this If you have a black coloured invisible assistant:
https://drive.google.com/file/d/11kLIBtWm_dUMnwfK0p3OS70iEPByYF7U/view?usp=drivesdk
Click to expand...
Click to collapse
It doesn't work on Android (Pixel Experience for OnePlus 7 Pro). On Android 10 (Pixel Experience Stable) it worked with both "Hey Google" and continued Conversation, but on Android 11 "Hey Google" doesn't work at all and Continued conversation is missing.