Related
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?
Hello Buddies,
Today i am here to show you how to root your Swipe MTV_Volt phablet
The phablet comes with a android 4.1 jellybean and 6" screen
MTK 6577 1.2 GHz dual core processor
8 MegaPixel camera and much more
After Googling for hours and wasting time trying many tools i finally found out how to root the swipe MTV_Volt phablet without bricking it
The process is 100% safe
First you need to install the adb drivers for the phablet
Install it via pda net
You can find the download file and instructions here : http://goo.gl/npzlai
Then you have to install the RootMaster Tool on your computer
download root master from here : http://goo.gl/ppezGm
You will also need root explorer on your phone, Either download it on your phone from play store or Grab the .apk from here http://dl.xda-developers.com/attachdl/1fe073cbef763cf3c302a5cd8733d71f/5276196f/2/1/8/3/9/8/0/RootExplorer.apk
And download the Superuser 3.1.3 from here : http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
Make sure that you have installed the drivers of the phablet on your PC using the PDA net and after you have downloaded all the files given above,
1. Download Root Explorer [Google Play]
2. Download Root Master
3. Unpack and install Root Master on your PC
4. Install drivers of your mobile
5. Run RootMaster and press first button on first screen
6. After this click the center button on all windows
7. You mobile is rooted - Reboot your mobile
8. Close the RootMaster
9. Install Root Explorer and delete superuser.apk
10. This release of superuser.apk is not english
11. Delete or replace your superuser.apk in /system/app
12. Unpack Superuser.apk from zip and copy to /system/app folder
13. Reply yes to replace your apk Superuser.apk
14. If you delete superuser.apk reinstall Only superuser from Zip
The RootMaster is in chinese but it is still convenient to use If you need instructions regarding how to use RootMaster check ot the link: http://forum.xda-developers.com/showthread.php?t=2403230
I know i am the first person who has discovered the method To Root the Swipe MTV_Volt so if you appreciate my work please hit the thanks button.
If you do all the steps properly your phone will be rooted without any problems,
Do it properly and follow every step correctly because,
YOU ARE DOING IT ON YOUR OWN RISK..!!
The file is ested and 100% working on Swipe MTV_Volt screenshot provided below
If i helped then press the thanks button
thread moved
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.
Hello
I was wondering if someone found any working root method for this tablet. This is the only new 7" tablet i've found with decent hardware, so i'm kind of surprised this tablet has such a small community.
Anyways, has someone managed to root this tablet? I've tried popular apps like Kingroot, Kingoroot etc. but none of them worked.
Thanks
Please make twrp recovery for my lenovo T- 7504x
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
---------- 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
[/QUOTE]
Hey guys have you tried this? anyone can help with the location to all these files mentioned?
Hey everyone,
UPDATE: WORKS WITH ANDROID 13! You can now use the more stable verison!!
Thanks to the people at github, yujincheng08 , updated one of the github commits and was finally able to root this device.
How to unlock:
Should be the same as any other samsung device. Follow my S6 Lite guide.
How to root:
1. Download the firmware for your your tablet, i dont know if i can link the sites but you can google it. (frija is recommended and is the fastest)
2. Extract only the AP portion of the firmware.
3. Open up the AP portion with 7-zip or winrar
4. extract the boot.img.lz4 out of the AP file
5. Download Lz4 https://github.com/lz4/lz4/releases to your pc corresponding version.
6. Extract the LZ4 to the same area where the boot.img.lz4 is
7. Open command prompt in that folder and then do
Code:
lz4 boot.img.lz4 boot.img
8. Download this magisk version from github
Release Magisk v24.3 · topjohnwu/Magisk
For those coming from v24.1, check the full changelog for changes introduced in v24.2. [General] Stop using getrandom syscall [Zygisk] Update API to v3, adding new fields to AppSpecializeArgs [App...
github.com
9. Extract the app-release.apk
10.. Connect your tablet and put it in your downloads folder
11. Install it via th My Files or use a file explorer.
12. Move the boot.img into the tablet and use the magiks that you just installed and patch it using that .
13. Move the magisk_patched version back to your pc, rename it to boot.img and create a tar version of it (i used 7-zip)
14. Open up odin , put your device to download mode and then patch the AP using the boot.tar you just created.
15. It should reboot, wait a few seconds and it may reboot a couple times. Then it may ask you to factory reset and just reset.
16. Once you setup your tablet again, connect your pc and do all that usb setup agagin and then move that app-release.apk again.
17. Youre gonna have to install the app-release again but uninstall the magisk already installed on your device first then install it via the apk
18. It should say additional setup required so do that, reboot and you should have root!
Has anyone else tried this guide?? Not trying to brick my new tablet so would like to know if it works for anyone! Thanks in advance!
Awesomeslayerg said:
Hey everyone,
Thanks to the people at github, yujincheng08 , updated one of the github commits and was finally able to root this device.
How to unlock:
Should be the same as any other samsung device. Follow my S6 Lite guide.
How to root:
1. Download the firmware for your your tablet, i dont know if i can link the sites but you can google it. (frija is recommended and is the fastest)
2. Extract only the AP portion of the firmware.
3. Open up the AP portion with 7-zip or winrar
4. extract the boot.img.lz4 out of the AP file
5. Download Lz4 https://github.com/lz4/lz4/releases to your pc corresponding version.
6. Extract the LZ4 to the same area where the boot.img.lz4 is
7. Open command prompt in that folder and then do
Code:
lz4 boot.img.lz4 boot.img
8. Download this magisk version from github https://github.com/topjohnwu/Magisk/suites/4781599968/artifacts/133467701
9. Extract the app-release.apk
10.. Connect your tablet and put it in your downloads folder
11. Install it via th My Files or use a file explorer.
12. Move the boot.img into the tablet and use the magiks that you just installed and patch it using that .
13. Move the magisk_patched version back to your pc, rename it to boot.img and create a tar version of it (i used 7-zip)
14. Open up odin , put your device to download mode and then patch the AP using the boot.tar you just created.
15. It should reboot, wait a few seconds and it may reboot a couple times. Then it may ask you to factory reset and just reset.
16. Once you setup your tablet again, connect your pc and do all that usb setup agagin and then move that app-release.apk again.
17. Youre gonna have to install the app-release again but uninstall the magisk already installed on your device first then install it via the apk
18. It should say additional setup required so do that, reboot and you should have root!
Click to expand...
Click to collapse
https://github.com/topjohnwu/Magisk/suites/4781599968/artifacts/133467701
This site is don't work. Can you share this file?
Thanks for the notice. Just rooted my device successfully using the latest Magisk build from the master branch. Works great!
@ahrmakrm1235 The github artifacts link will only work if you are logged into Github (create a new account if need to, it is free).
first time rooter here. do you mind specifying what you mean by opening command prompt in the folder? i extracted the contents of the Lz4 application into the folder containing the boot file. when I open command prompt, i drag that folder there and then enter the code, but it's not doing anything.
Thank you so much. I success to root sm-t733
zriw said:
first time rooter here. do you mind specifying what you mean by opening command prompt in the folder? i extracted the contents of the Lz4 application into the folder containing the boot file. when I open command prompt, i drag that folder there and then enter the code, but it's not doing anything.
Click to expand...
Click to collapse
Use 7zip zs, free and works just like 7zip , easier method than the lz4 extract.
@Flaccthehawk I'm going to try it out now and see if it makes a difference. If not, I'll edit and add pictures or a screen recording of what I'm doing wrong.
Edit: I did everything correctly, but I'm having trouble flashing the tar file. It keeps failing. I've already tried updating to the latest odin version of 3.14 & I know the firmware is correct because I downloaded it using frija. Any suggestions? I've attached what the error looks like below and my tablet in download mode in case there's an issue there.
In step 13 when creating the tar file for the boot image, what did you use for this? Did you use 7-zip? And did you select the tar option in the archive option in 7-zip (or another program)? Note that it must be a proper tar file. If the file created is a zip or 7z file, it won't work even if you rename the output file as a tar file.
Can you open the tar file using 7zip. Provide a screenshot of what is displayed here. Also within 7-zip after opening the tar file, click into File - Properties and provide a screenshot of this also.
FYI: I actually removed root for now. I noticed the battery was draining a lot quicker than before with Magisk (I did a clean format/flash too when rooting the device). Removing root, battery life is back to normal.
I'm new here, do I need to unlock bootloader before process this?
Yes, the bootloader needs to be unlocked. Note that the device will be erased when unlocking the bootloader so backup any data that you need before doing so.
@1987tlz Yes, I used 7zip to to open the boot file and selected tar as you can see here.
Thank you so much, success to root (SM-T735).
Hi again, I have problem about SafetyNet test failed (basicIntegrity -, ctsProfile -, evalType BASIC), also I cannot enable MagiskHide (after I enable and back to Magisk home, it's change back to disable). Does it possible to bypass SafetyNet test and enable MagiskHide?
Many Thanks
@zriw It wasn't clear from the screenshots, but for the file patched by Magisk, did you rename this to boot.img? Once the file is named as boot.img, then you create the tar file as boot.img.7z. Now you should be to flash it again using Odin.
@imjizho It looks like you are not using a recent version of Magisk, as MagiskHide doesn't exist anymore. On the latest release, Zygisk needs to be enabled and then you can enforce and configure the DenyList.
For passing SafetyNet, the latest version of this module will do the job:
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
All done! Thanks a lot @1987tlz
I found that the problem occurred when I try to hide the Magisk app, it will installed previous version and cannot change back when restore.
1987tlz said:
FYI: I actually removed root for now. I noticed the battery was draining a lot quicker than before with Magisk (I did a clean format/flash too when rooting the device). Removing root, battery life is back to normal.
Click to expand...
Click to collapse
Can others confirm the battery drain with root?
Rooting was the first thing i did with the tablet, i have no reference if it is really draining the battery.
//edit:
removing some bloatware (netflix, chrome, and so one) lead me to a bootloop
Im not finding bootloader unlock and am not sure if i have done it correctly on this samsung device.
This is what i have done,
1.Settings>About Tablet>Software Information
2.Tap Build Number repetitively until Developer Settings Enabled
3.Settings>Developer Options
4. Turn OEM Unlocking on
Is this all there is to it? I feel like im missing something.
*** EDIT
Found that if holding both volume down and volume up while plugging the tablet into my PC i was able to find more options to bootloader unlock as well as warnings. After accepting those it did a factory reset. I hope this is all i needed to do.
Thank you, i have successfully achieved root!
Typhoon_Master said:
Can others confirm the battery drain with root?
Rooting was the first thing i did with the tablet, i have no reference if it is really draining the battery.
//edit:
removing some bloatware (netflix, chrome, and so one) lead me to a bootloop
Click to expand...
Click to collapse
Have you tried freezing the bloatware apps with Titanium Backup located in the Play Store?