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

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.

Related

12 Step Root Guide

I just got mine working using some legacy WinMo tricks for the HTC Installer... and I am a n00b at this Droid thingy, so hopefully this is useful and not dangerous or misleading info - use at your own risk!!! Please test and let me know if you have success or if there are better methods for installation. I removed the http preface from the links, FYI...
1. Root the device using the unrevoked.com/m/ method (Steps 1-8 forum.xda-developers.com/showthread.php?t=701004)
2. Installed MyBackup and created a full backup of Apps and Data to my SD card (should say you are root, and enable the additional backup features)
3. Downloaded the new PC36IMG.zip, renamed it to rom.zip (forum.xda-developers.com/showthread.php?t=701835 - under File Needed)
4. Downloaded the RUU Restore Application
(forum.xda-developers.com/showthread.php?t=685835 - Green Text at bottom of Thread)
5. Run the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe downloaded from #4 and contiue with the installer until it asks you to select the ROM - then STOP
6. Navigate to C:\Documents and Settings\USERNAME\Local Settings\Temp and look for the new folders created by the RUU installer
7. Copy the rom.zip from your downloaded PC36IMG.zip (renamed to rom.zip) and overwrite the existing rom.zip file
8. Back to the RUU installer, click the Select ROM, and finish out the installer.
9. I held down the Volume Down button once the phone started rebooting, not sure if it is required or not
10. Wait till it is done installing to release the Volume Down button, tired fingers... ugh, but may be optional
11. Upon reboot, it will take a bit longer than usual, but once it loads, link your account back to Google and download the MyBackup app from your Downloads section, and run the app once installed to restore your Apps, then Data (I use Google for contacts and calendar, so I unchecked those in the restore). Again, you should be informed you are root by MyBackup...
12. Reboot
I haven't tried to finish Step 3 from forum.xda-developers.com/showthread.php?t=701835, but I will asap to assure it is complete.
wow, very interesting!
in simple terms you're essentially tricking the RUU into loading a different rom.zip . since PC36IMG.zip (both the userdebug and eng build versions posted by toast for his root methods) seem to be interchangeable with the rom.zip payload of the RUU .exe installers, they are all swappable ....
unfortunately all these .zip files, rom.zip and PC36IMG.zip seems to have the same special HTC encoding which we can't seem to duplicate or we could make our own PC36IMG.zip files.
this seems like a great method and perhaps can get us one step closer! thanks for posting this! the more little tricks the better!

[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?

[Guide]Rooting, CWM, Roms, Bootanimations, mods, etc. for Cherry Mobile Burst

How to Root.
Please do consider pressing thanks. Thank You.
WARNING: Here's the classic: Do With Your Own Risk.
NOTE:
METHOD1: If this is your first time EVER to root.
METHOD2: If you already have CWM.
METHOD1:
This is the easiest f*cking way EVER! to root since my 1st time on developing. RECOMMENDED for total NOOBS
Credits to Mr. Andrew Casal
Originally Created By: alephzain @ http://forum.xda-developers.com/showthread.php?t=2130276
1. download Framaroot and install it on your phone.
2. Open it and choose Superuser or SuperSU (SuperSU recommended but not required, you can choose whatever you want) then press Gandalf.
3. Reboot and Enjoy a rooted phone. Now wasn't that oh so easy!?
METHOD2:
1. download my RootStock and copy it to your sd card.
2. enter CWM and flash it like any other rom.
3. reboot and enjoy!
This is the work of annson24(annson08). Please, for Christ's sake, don't steal my work, especially Mr. Vipul Verma. Give proper credits to me, better if you press thank too if anyone wants to remake the tut.​
Installing CWM Recovery.
DWYOR.
For now, only chinese version is all we have but the devs are working on translating it to english.
UPDATE: We now have a working english CWM, thanks to Lava XOLO devs.
Installation
NOTE:
METHOD1a: If this is your first time flashing CWM.
METHOD1b: If this is your first time flashing CWM. <~ EASIER METHOD, REQUIRES PC
METHOD2: If you have already flashed Chinese CWM before.
(WARNING: Procede to method 2 if this is your first time flashing CWM)
METHOD1a
Need a Rooted Phone. Root procedure HERE.
1. Download a28.img and copy it to your sd card.
2. Install terminal emulator from Play Store. It's free.
3. Open Terminal Emulator and type the following. Be sure to grant Superuser Permission.
Code:
su
[Press Enter]
dd if=/sdcard/a28.img of=/dev/block/mmcblk0p16
[Press Enter]
4. You now have English CWM Recovery v6.0.1.2. You can enter the recovery by turning off your phone, hold vol.down+power button, release after the phone vibrates or power up.
Enjoy!
Video tutorial by Mr. Keiven Adrian Docos Busita again. Thanks for this awesome video.
METHOD1b
(Thank you sir Andrew Casal for the info)
1. Download a28.img
2. Download Universal Android AIO Flasher Tool
3. Turn off phone
4. hold vol.UP+power button, Download mode should come up
5. Connect phone to PC
6. Open Universal Android AIO Flasher Tool
7. Under "Fastboot Flasher (NANDroid Restorer)" Select Recovery
8. Click "Select File" button then locate the "a28.img".
9. tick/check the checkbox "Erase".
10. Click "Flash".
11. Reboot phone to recovery (NOTE: power button doesn't work on download mode, remove battery first the insert it again and hold vol.DOWN+power button, once the BURST page comes up, release your hold..)
12. You now have English CWM Recovery v6.0.1.2.
Enjoy!
METHOD2
1. Download this flashable zip file
http://d-h.st/3Eb
2. Flash it like any other rom (no need to wipe data)
3. Reboot.
4. You now have English CWM Recovery v6.0.1.2.​
How to Change Bootanimation.
STILL DWYOR
Update: Video tutorial by Mr. Keiven Adrian Docos Busita. Watch it Here. Thanks Keiven.
First of all I will start this thread at changing the bootanimation since it's this thread's first purpose. Rooting, build.prop, init.d, scripts are to follow if ever i feel like adding them. Rooting on the other hand will be added for sure because we need a rooted device to change bootanimation.
Requirements:
1. Cherry Mobule Burst/Lava Xolo A500 (Duh!)
2. Root permission (Guide on rooting at OP)
3. Root Explorer
4. Good Understanding.
Procedures:
Step 1
Install Root Explorer an open it.
{
"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"
}
Step 2
Browse for /system folder, open it up and browse for /media folder open that up too and you should find:
/audio
/video
bootanimation.zip
shutdownanimation.zip
turnoff.mp3 (not sure what's its real name, I forgot, I deleted mine)
turnon.mp3 (not sure what's its real name, I forgot, I deleted mine)
Step 3
Download custom bootanimation you want, any size will fit.
Step 4
Delete(not recommended) or backup(recommended) your stock bootanimation.zip to your PC or micro sd, and copy your downloaded bootanimation.zip to that folder (/system/media).
Note: You can also delete the shutdownanimation.zip to skip shutdown animation.
Step 5
Reboot and Enjoy.
Note: The "BURST" that comes out during turn on cannot be replaced because it's a bootsplash and can only be tweaked inside boot.img which is where our kernel lies. Custom ROM is the only way to replace that. If someone have already replaced that, you can freely share it here.
General Note: If root explorer displays this: "bootanimation.zip cannot be moved/deleted because the file system is read-only." tick first the [Mount R/W] Button on the upper right until it becomes [Mount R/O].
Available ROMs for our device.
Unofficial ICS Stock Rom for Cherry Mobile Burst. Procedures present @ Origina Thread.
AndroTronic Credits to Mr. Jov1N. Original thread HERE.
DWYOR.
Need CWM.
1. Download rom located at the original thread. I won't be mirroring the download to respect the creator.
2. Download THIS. <~~~ it's a fix for lcd density and boot.img, for the rom to fully work on our device.
3. copy both files on your SD card.
4. Enter CWM by pressing vol.down+power button simultaneously. The phone must first be off (duh!)
5. Wipe Data. (Important!)
6. Install the rom.
7. Install the fix.
8. Reboot and enjoy.
MIUI by Mr. Jov1N again.
http://forum.xda-developers.com/showpost.php?p=39960803&postcount=21
Procedure of installing, same as AndroTronic but without the fix.
NOTE: need the cherry burst boot.img to work, replace first before installing. I'll elaborate the procedure later.
Re: [Guide]Rooting, CWM, Bootanimations, mod, etc. for Cherry Mobile Burst/Lava Xolo
This CWM is not quite working.
The partition table is a bit different
kank_fraud said:
This CWM is not quite working.
The partition table is a bit different
Click to expand...
Click to collapse
It's working just fine sir, everyone on our facebook pages are already using it.
Very Useful
Did you modify anything to work properly
Cuz as far as I can see, it works only with the sdcard
it cannot see the emmc and one more partition.
The partition table is a bit different
I corrected and am using it.
Well if you did, well n good
I did post in a couple of sites
dude, bakit iba yung mga pictures ng CWM sa actual na gamit ko ngayon?
annson08 said:
Installing Custom Rom.
DWYOR.
AndroTronic Credits to Mr. Jov1N. Original thread HERE.
Need CWM.
1. Download rom located at the original thread. I won't be mirroring the download to respect the creator.
2. Download THIS. <~~~ it's a fix for lcd density and boot.img, for the rom to fully work on our device.
3. copy both files on your SD card.
4. Enter CWM by pressing vol.down+power button simultaneously. The phone must first be off (duh!)
5. Wipe Data. (Important!)
6. Install the rom.
7. Install the fix.
8. Reboot and enjoy.
NOTE: I'll be providing a slightly slimmed version of the rom for better responsiveness and with the fix already in it.
MIUI by Mr. Jov1N again.
http://forum.xda-developers.com/showpost.php?p=39960803&postcount=21
Procedure of installing, same as AndroTronic but without the fix.
NOTE: need the cherry burst boot.img to work, replace first before installing. I'll elaborate the procedure later.
Click to expand...
Click to collapse
How to Install the fix??
same with me cwm is not permanent
kank_fraud said:
Did you modify anything to work properly
Cuz as far as I can see, it works only with the sdcard
it cannot see the emmc and one more partition.
The partition table is a bit different
I corrected and am using it.
Well if you did, well n good
I did post in a couple of sites
Click to expand...
Click to collapse
Kank, as you can see we now have english cwm, but the table is still messed up, how'd you managed to fix yours?
Well sorry for the extremely late reply
Been out of station and will again soon
well i have flashed the CWM, the latest one, and its perfect.
Before flashing I even checked the partition table and its perfect.
Nothing needs to be changed.
Only thing, emmc support is not there in this one, but otherwise its perfect.
BTW I am talking abt the XOLO A500 not the CM Burst
CM Burst has a slight different partiton
When you flash the cwm select reboot system now
It'll say the system may flash back stock recovery . Do you want to prevent this from happening select yes
sent from my super advanced mini fridge
annson08 said:
How to Change Bootanimation.
STILL DWYOR
Update: Video tutorial by Mr. Keiven Adrian Docos Busita. Watch it Here. Thanks Keiven.
First of all I will start this thread at changing the bootanimation since it's this thread's first purpose. Rooting, build.prop, init.d, scripts are to follow if ever i feel like adding them. Rooting on the other hand will be added for sure because we need a rooted device to change bootanimation.
Requirements:
1. Cherry Mobule Burst/Lava Xolo A500 (Duh!)
2. Root permission (Guide on rooting at OP)
3. Root Explorer
4. Good Understanding.
Procedures:
Step 1
Install Root Explorer an open it.
Step 2
Browse for /system folder, open it up and browse for /media folder open that up too and you should find:
/audio
/video
bootanimation.zip
shutdownanimation.zip
turnoff.mp3 (not sure what's its real name, I forgot, I deleted mine)
turnon.mp3 (not sure what's its real name, I forgot, I deleted mine)
Step 3
Download custom bootanimation you want, any size will fit.
Step 4
Delete(not recommended) or backup(recommended) your stock bootanimation.zip to your PC or micro sd, and copy your downloaded bootanimation.zip to that folder (/system/media).
Note: You can also delete the shutdownanimation.zip to skip shutdown animation.
Step 5
Reboot and Enjoy.
Note: The "BURST" that comes out during turn on cannot be replaced because it's a bootsplash and can only be tweaked inside boot.img which is where our kernel lies. Custom ROM is the only way to replace that. If someone have already replaced that, you can freely share it here.
General Note: If root explorer displays this: "bootanimation.zip cannot be moved/deleted because the file system is read-only." tick first the [Mount R/W] Button on the upper right until it becomes [Mount R/O].
Click to expand...
Click to collapse
Thxxx for the tutorial... Successfully changed the bootanimation
professor_proton said:
When you flash the cwm select reboot system now
It'll say the system may flash back stock recovery . Do you want to prevent this from happening select yes
sent from my super advanced mini fridge
Click to expand...
Click to collapse
select yes sir so it wouldn't bother you anymore
Sagarvaghela said:
Thxxx for the tutorial... Successfully changed the bootanimation
Click to expand...
Click to collapse
anytime sir.
please reupload the fix for androtronic. the link is down. t.i.a
this was not a MIUI in http://forum.xda-developers.com/showpost.php?p=39960803&postcount=21.
Nandroid Backup Not completed
Hey i installed english clockworkmod recovery in xolo a500 & when i run backup all it only make backup of 27 mb....dont know the problem...plz help me
itsgauravjain22 said:
Hey i installed english clockworkmod recovery in xolo a500 & when i run backup all it only make backup of 27 mb....dont know the problem...plz help me
Click to expand...
Click to collapse
Select the default backup format to tar . Might help you.
Sent from my A500 using XDA Premium 4 mobile app

[GUIDE] Beginner's guide - first steps with a MTK phone

DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
This guide may be obsolete now for the new MTK SOC's powered phones, but it will give you some ideeas about how MTK phones world works (especially if you are new to this).
Why this thread?
- Because of all those PMs I receive with questions about how to do this or how to do that.
These things aren't they covered here on XDA?
- Some of them are, some don't, or they are spread over the forum in different sections, different threads. Also I will present here my vision about how to do things, and in some parts is different than the others existent.
I tried to document all steps with images for a better understanding, and to make it easy for people who don't understand well English (also I don't claim that my English is very good, but I'm trying).
1. If you want to use your phone as you buy it, then this thread is not for you, but if you want to use a custom recovery, to install a custom ROM, or some modds, keep reading.
2. First big step in our journey is to root your phone, which most of you know that means to get root (administrator) access to your phone's OS - just a simple definition. With an unrooted phone, you can't do much, and that means you will use it pretty much as you buy it - see first point.
There are multiple methods to root your phone, through an application from your phone, with an executable software from your PC or by flashing a zip modd from recovery (only for custom recoveries).
A. The best rooting application at the moment (in my opinion), is Framaroot.apk, developed by alephzain - please stop by his thread and drop a thanks, or if you can buy his donnation app from Playstore to support his work. You can download this app from official thread.
B. For rooting with a software from PC, I know three big candidates: oneclickroot, kingoroot and srsroot. I know there are more, but I mentioned only the best known.
C. Rooting zip archives are two, to choose from: chainfire's and koush's. Although, these require to have a custom recovery installed.
Any method you choose, be sure to check the phone models reported to work for, and look for your model.
Next, I will present step by step what I call "the beginner's routine":
root the phone;
make a nvram backup;
make a stock ROM backup;
generate a custom CWM and flash it;
patch to unsecure the boot and flash it;
get a Root File explorer;
create a custom recovery by porting one.
Prerequisites:
you must have an account on XDA; if you don't, then create one - and remember, at beginning you will not be allowed to post but you can hit Thanks for people I will mention here.
use a computer with Windows XP or 7 (I don't know if it will be any problem in vista or windows 8, but I didn't tried them, so I can't tell).
a phone with MTK CPU, obviously!
these tools:
MTKDroidTools of rua1's - download it from his thread and hit Thanks or donate to him, please
SPFlashTools or MTKFlashTools.
MTK USB Drivers and your phone manufacturer's USB Drivers if they provide that.
For MTK USB Drivers, there are many sources, but I couldn't find any official source. Few known sources: here and here.
* ADDED: For windows 7 and xp I repacked all MTK needed drivers, bundled with latest google usb drivers and using windows driver installer. Some of the drivers are not digitally signed, so when the prompt window ask you if you want to install unsigned driver (it will be several times) select yes or ok. The advantage is that this method is easier than manual method and also will create an entry in installed programs, and later if you want you can uninstall them in control panel uninstall program. Before installing this you need to remove old drivers installations - use usbdeview (download it x86 or X64), and look for VendorId 0bb4 and 0e8d, and uninstall every device with these Ids. Packed drivers are attached to this post; take what corresponds to your windows version. Unpack the archive, open the folder and run dpinst.exe. More info inside: read info.txt (especially for XP).
Install all needed drivers.
A good text editor (Notepad++ or Geany) installed.
Adb installed in your computer from Android: here, here and here you can learn how.
Credits and Thanks:
@alephzain - Framaroot developer
@rua1 - developer of MTKDroidTools
@Chainfire - SuperSU developer
@Koush - so many things!!!
@michfood - developer of Boot Recovery pack/unpack tool
and, even if it is not presented here, but because I use a lot his tools in Linux:
@bgcngm - for his Unpack/Repack scripts
1. Root the phone.
For this step I choose to use Framaroot.apk, first because I don't like to install unnecessary software on my computer, and second because it supports a very large number of MTK phones. So, go to alephzain's thread and download the apk, then connect your phone to PC with USB debugging enabled, turn on USB Mass storage and copy Framaroot.apk to your sdcard root, or in internal storage if you don't have a sdcard in your phone. Eject phone's USB storages from PC, and turn off USB Mass storage from phone.
{
"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"
}
Go to apps drawer, find File Manager, open it, navigate to location where you placed Framaroot.apk touch on it and install it. After that go back in apps drawer and open the newly appeared Framaroot. In that window you have to specify which exploit to use for getting root access. If you don't know it's not a problem, you can try each one until you see the Success message (for me was Barahir). If none of them works, then you have to find a different method to root. After success patching, reboot the phone and then you will see SuperSU.apk in your apps drawer. Now you have root access!
2. Install a Root Explorer.
I prefer ESFileManager, but you can choose what you like. This can be installed free from Playstore, or if you have it downloaded in your PC, use same steps as in Framaroot case, and install it.
Then open the app and let's activate the Root Explorer in it.
But, here you can choose a different view style instead of default big icons - I like Medium Icon view.
Touch on Globe symbol from upper left corner to open Advanced Tools menu, and select Tools (last one). In the list that opens, scroll down until you see Root Explorer entry and touch "OFF" button to activate it. You will be prompted to Grant Superuser access - Grant it! Then, touch on "Root Explorer" text and in the popup window select Read/Write, and in next window select all radios from RW column.
That's it, ESFileManager is now a powerfull Root Explorer.
3. Make a backup.
This means actually make two backups, one for nvram and one for the whole stock ROM. Why to make a backup for nvram? Because it is very easy in MTK phones to mess up with it, and you may loose IMEI, mac address or to have other connectivity issues. This backup will be your insurance.
For this you need MTKDroidTools. Download it from rua1's thread (link in OP) and unzip it in a folder named "MTKDroidTools" on your primary (system) partition - this is important, and in other locations you may experience errors and malfunction.
Connect your phone in usb debugging mode to PC, then start MTKDroidTools as administrator and wait untill you see that MTKDroidTools recognize it and loads its data. The following pictures will show you how to check if you have usb debugging activated, and how MTKDroidTools looks with loaded phone data. In most of the phones, adb gets root access immediately, but in some "branded" ones that has to be achieved by click on the "ROOT" button next to "Adb Terminal" - Notice that if you don't see that ROOT button, that means you have already "root in shell". Also, if you have chainfire's SuperSU you will be prompted in the phone to grant root access to adbd, but if you have koush's Superuser, adbd gets root access by default.
Now, as I said first thing is to do a nvram backup. Click on "IMEI/NVRAM" button and next select both methods (bin and zip folder) and click on "Backup".
After that, it's time to do a stock ROM backup. This is important if you are going to try different custom ROMs and modds. This will assure you that you always have a way to start from the beginning in a clean state. Also makes easy to unbrick your phone if you have the misfortune to brick it.
Click on "root,backup,recovery" tab, and click on "Backup" button, then wait to finish. Be patient, this will take a while, and you can see progress logs in side window. At the end, a popup will prompt you to pack the backup. Now you know it is finished. I don't pack these backups, but you do what you think.
In this stage first thing I do is to generate a scatter file. You have one in that backup made before, or you can get one from stock firmware archive if the phone's manufacturer provide that, but let's see how to do it as it is, to understand the process, or to learn how to get one if we loose it or we are unsure if the one we have is good for our phone (this is important, because using a wrong scatter file it may damage your phone).
So, return to "Phone Informations" tab and click on "Blocks Map" button. A window opens with your phone partition structure. Click on "Create Scatter File" button and save it somewhere in your computer.
Mission complete for backup; you are assured now.
4. Generate a custom recovery.
This is mandatory if you want to use an easy way to backup, restore, flash or wipe ROMs and modds. Fortunately, rua1 has included in his tool all you need to generate one for your phone. This method is successfull for almost every MTK phone, but not for all. There isn't an universal method for anything.
So, enter again in "root, backup, recovery", select the radio "To choose the boot.img file" - by default is selected "Install already prepared files" - and click on "Recovery and Boot" button.
When prompted, select the boot.img from previous backup folder and click Yes to make CWM recovery automatically. First you will be prompted to flash a patched boot.img in your phone - click Yes to get an unsecured boot, then next message will ask you to install the new created recovery in your phone. Click Yes and Yes to reload the phone in recovery mode.
The phone will shut down and reboot in recovery. Now you can see your custom recovery in place.
GOOD TO KNOW: you can't generate a recovery everytime you want to flash one, to use MTKDroidTools for flashing, and the adb method may not work for many MTK phones.
The most known method to flash a new recovery is by using SPFlashTools or MTKFlashTools, and an alternative method is with MobileUncle application from phone, but I will show detailed the FlashTools method. One thing though: if you want to use MobileUncle application, you have to use it from /system/app folder, not from /data/app. Many users say that the MobileUncle doesn't work to flash recovery: it show success, but rebooting to recovery reveal the old one. The reason? They installed MobileUncle from market, and that place the app in /data/app as a user app. In custom ROMs where the app is placed in system by ROM developer, the problem won't manifest. So, if you want to use MobileUncle, make it a system app not user app.
In order to do that, grab a copy of any of these tools from DR_MOOSAVI's thread (link in OP), unzip it in a folder "MTK_Flash_tool" in your primary(system) partition (C in my case), and notice the name have to not contain any spaces or special characters. In that folder create a new folder "Resources" or ROM or whatever name you want, also without spaces or special characters, and place in it your scatter file and recovery img you want to flash. Open Flash_Tool executable as administrator.
IMPORTANT: Your phone is not connected to the PC now. Swtich it off and wait, you will connect it later.
Continue in next post.
In Flash_Tools program window click on load scatter file, navigate to that folder you created and select your scatter. Now you can see your phone's partition structure. If the recovery you want to flash is named "recovery.img" it will be selected automatically, if not you have to click on recovery row in Location column and select your recovery from that folder.
Then click on "Download" button.
Now connect your phone to PC, just like that in power off. Some models enter automatically in download mode and the flashing process begins, but others don't. For some it is necessary to connect them without battery (battery removed), other need to press briefly Power and Vol Down button at same time and release them immediately. That you have to find for your phone from forums, other users, or by trying. When the phone enter in download mode you will see a red bar down in Flash_Tool window, followed by a yellow or other color one (that means the flashing process is taking place).
At the end a popup with a green circle or green checkmark will let you know that the flash was a success. Deconnect the cable and reboot the phone, or reboot it in recovery to see if the wanted recovery is installed. The most common method to boot in recovery from power off is to press Power and Vol UP at same time, and keep them pressed untill you see the logo, then release Power but keep pressing Vol Up untill the recovery UI appears. If Power and Vol Up doesn't work for you, start the phone normaly and connect the phone to PC, then open a command prompt window, and type " adb reboot recovery", then hit Enter during bootanimation. The phone will stop loading and will boot in recovery.
5. How to port a custom recovery.
Check my new guide.
Check my new guide.
Awesome Tutorial!!! U did it again....
Thanks!!!
Thank you sir I will try to port cwm to my mtk mobile
Sent From MTK-MT6572
---------- Post added at 03:31 PM ---------- Previous post was at 03:01 PM ----------
Sir now my mobile with ext4
Now in your thread about porting carliv cwm.. there is only custpack and ubifs ...!! Where is for ext4
Sent From MTK-MT6572
carliv grt work hope u add this post too http://forum.xda-developers.com/showthread.php?p=49081376
[email protected] said:
carliv grt work hope u add this post too http://forum.xda-developers.com/showthread.php?p=49081376
Click to expand...
Click to collapse
Thanks, but that is not something for begginers. Maybe meteos method with his app will be, but I'm not sure. Though, if someone want to procede to do that, you can edit your post and give more details, for people to know what is about, and to follow your link if they are interested.
Great guide @carliv.
Just a bit confused, as I usually flash custom recovery first before rooting my MTK phones (same goes for all my android devices). So, maybe, rooting and flashing custom recovery is interchangeable as the first step for MTK phones depending on their availability.
iZLeeP said:
Great guide @carliv.
Just a bit confused, as I usually flash custom recovery first before rooting my MTK phones (same goes for all my android devices). So, maybe, rooting and flashing custom recovery is interchangeable as the first step for MTK phones depending on their availability.
Click to expand...
Click to collapse
Yeah, well the next step in my guide is "do a stock ROM backup", and if you flash a custom recovery, that will not be a complete stock backup. With my method, any time, after flashing the stock backup, unroot and you will be in stock initial state.
I hope it's more clear now.
carliv said:
Yeah, well the next step in my guide is "do a stock ROM backup", and if you flash a custom recovery, that will not be a complete stock backup. With my method, any time, after flashing the stock backup, unroot and you will be in stock initial state.
I hope it's more clear now.
Click to expand...
Click to collapse
Got it. So this is more suited for those who do not have the original firmware for restoring their devices in case something goes wrong which is so like MTK phones. In any case, your guide is spot on. Hope the moderators would give this a sticky, if possible, since MTK phones are scattered all over xda.
How to Port to Device that have recovery-from-boot.p
Hello Everyone, and hello to @carliv,
Thanks to this Tutorial I have Manage to port in on a MT6582 and MT6572 Device with ext4 partition, but I just want to share some tips when porting the latest build of the carliv the tutorial here is complete except for one thing just in case you are ending up on a custom recovery not booting up and when you use the MTK Droid Root and Tools you will see this
-->Connect Device<--
there is a file blah blah - recovery-from-boot.p <----
Now that mess up the things but before we dig into that let me first share on how I got my Carliv Custom Recovery to Bootup
on the Tutorial there is a section that you need to use the MTK Unpacked tool right now once you have done that do all the other things that is written in the tutorial it will guide you on the whole process but on my end even though I followed the tutorial and all are correct I still end up on a Bootloop well I discovered that you need to copy the init file from the RUA1 CWMR that you got from the MTK Droid Root and Tools and overwrite the one on the Carliv Recovery after that once you have finish until on the Overwriting of the Kernel and Kernel header pack your Carliv Recovery using the MTK pack tool and now Flash it on your Device it will now boot :highfive:
BUT WAIT!! yes! it will boot but it will boot on the STOCK RECOVERY and that is because like what I said the recovery-from-boot.p is the culprit of the issue now you need to root your device which is on my end I used framaroot and then download the ES file manager and also follow the instruction of carliv on how to have the full ROOT R/W access and on your device, once your have done that got to this folders and delete this 3 files.
Be sure you have the R/W access or else this files will not be deleted
/system/recovery-from-boot.p
/system/etc/recovery-install.sh
/system/etc/recovery-resources.bin <--- I am not just sure if this is the right filename but it is almost the same will check it once again once I got to stock rom again :fingers-crossed:
and now once you have rebooted your smartphone to recovery mode it will now boot to the Carliv Custom Recovery.
But also take note that if you don't have that 3 files on your device your just good to go and it will boot to Carliv Custom Recovery without any issues.
it's just that 3 files makes the custom recovery always boot to stock recovery even though you do something else
hope this tip helps for some people having issue on a bootloop carliv custom recovery on doing the manual porting
and don't forget to hit the thanks button if this helps :victory:
rnovino said:
/system/recovery-from-boot.p
/system/etc/recovery-install.sh
/system/etc/recovery-resources.bin <--- I am not just sure if this is the right filename but it is almost the same will check it once again once I got to stock rom again :fingers-crossed:
Click to expand...
Click to collapse
Removing recovery-from-boot.p is enough, I think. Besides, CTR asks if you want to disable recovery-install.sh. That prevents the ROM from flashing stock recovery.
iZLeeP said:
Removing recovery-from-boot.p is enough, I think. Besides, CTR asks if you want to disable recovery-install.sh. That prevents the ROM from flashing stock recovery.
Click to expand...
Click to collapse
it depends on the unit, I just deleted the recovery-from-boot.p and still it boots up on the stock recovery that's why I needed to trace other files that still makes it boot on stock recovery, but then again not all units will have the same issues as mine
Thanks for your help, it works with my Huawei Honor 3X (mtk6592) !
Thanks Man!
Error
Please help me in porting recovery.I am getting error "the syntax of the command is incorrect " in all four files.
View attachment 2654172
View attachment 2654177

[Lava Magnum X-604][Android Development & Q&A][AIO Thread]

[Lava Magnum X-604][Android Development & Q&A][AIO Thread]​
Key Features:
Lava Magnum X604 is a Smart Phone Powered by 6.00-inch HD 720x1280 pixels with 245 Pixels per inch (PPI) display,Android 4.4 KitKat,8 MP Auto Focus with with BSI Sensor for low light imaging and Broadcom 1.2GHz Quad Core processor coupled with Videocore IV GPU alongside 1GB RAM.
​
Rooting & Unlocking:
Code:
[B][SIZE="4"][COLOR="DarkRed"]Before You Begin[/COLOR][/SIZE][/B]
1. This will void the warranty of your device. We won’t be held responsible if you end-up bricking or damaging your device. Do it at your own risk.
2. This should only work on Windows based PCs Preferably Windows-7
3. There should be at least 65% charge in your
4. Make a Backup of Your Contacts,SMS,And Whats App data in SD Card
Code:
[B][SIZE="5"][COLOR="DarkRed"]Downloading Required Files:[/COLOR][/SIZE][/B]
Download Lava Magnum X-604 Root Toolkit [B][URL="https://drive.google.com/file/d/0B7OdRw3ALPgGdWcxOUx0c0llMGs/edit?usp=sharing"]Click Here To Download[/URL][/B]
Code:
[B][SIZE="5"][COLOR="DarkRed"]Preparing Your Windows PC And Magnum X604 for Rooting:[/COLOR][/SIZE][/B]
Extract Downloaded Lava Magnum X604 Root Tool Kit to your Windows PC Desktop
Go to Settings >> Backup & Reset >> Factory data Reset in your Lava Magnum X-604 and Do a factory data Reset and Complete setups after it re-boots
Enable USB Debugging On your Device You can find this option in Settings >>Developer Option >>USB Debugging.
Enable Allow Installation of Apps from Unknown Sources under Settings >> Security >> Unknown Sources also Disable verify apps bellow Unknown Sources
Now Connect your device via USB cable to windows PC and Start installing programs which is provided in tool kit in same order
1.) Adb Driver Installer 2) BRCM_Driver_Package 3.)For Windows x64 Bit/For Windows x32 Bit 4.)VRoot_1.7.8.7753_Setup
Code:
[SIZE="5"][COLOR="DarkRed"][B]Rooting :[/COLOR][/SIZE][/B]
Open installed V-Root Program and Grant USB Debugging Authorization when a pop-up pops in your device Remember to tick always allow option.
When connection is established between V-Root program and your device it will display your device model and Root Button in Opened V-Root Program
If You See Green Colored Root button in V-Root Program Just click it and Wait silently with out touching your device .After some Times Your
Device will reboot (Remember Don't Disconnect USB cable until and Unless V-Root Program show success in your PC )
When you see Success message in PC remove USB Cable and Reboot Your Phone
Now Your Lava Magnum X604 is Rooted
Code:
[B][SIZE="5"][COLOR="DarkRed"]Installing Super-SU By Chain Fire [/COLOR][/SIZE][/B]
Install Super SU application from Google Market
When you open Super SU it will prompt you to update binary select install binary from normal recovery when option pops
After rebooting it will Ask you to Uninstall V-Root Super User application to Avoid conflicting of 2 Different Root application so you can press yes and uninstall V-Root superuser
Don't forget to Grant Root Permission when application asks
Now Enable Super Su as system application from its options if this step fails copy it to systm/app folder from data/apps folder via any root file managers like Root Explore etc
Now Your Lava Magnum is permanently Rooted.
Code:
[B][SIZE="5"][COLOR="DarkRed"]Installing BusyBox: [/COLOR][/SIZE][/B]
Why Busy Box ??? Busy box is needed to run most of the mods and scripts successfully in your device
Install Busybox installer application from Google Market and Follow the instruction in application to install latest Busy box 1.22 or Custom 1.23 versions
Don't forget to Grant Root Permission when application asks
This Makes your device to run any mods compatibility
Code:
[B][SIZE="5"][COLOR="DarkRed"]Enabling Init.d Support :[/COLOR][/SIZE][/B]
Why Init.d support ??? with out this enabled you cant run any scripts
Download and install Init.d Enabler application from [URL="http://forum.xda-developers.com/showthread.php?t=1933849"]This link[/URL]
Install the apk like any normal app.
Launch the app.
The rest are pretty self-explanatory...
Code:
[B][SIZE="5"][COLOR="DarkRed"]De-bloating and Making Rom More Light:[/COLOR][/SIZE][/B]
De-Bloating means removing unwanted applications which is pre-installed in stock firmware This will increase system storage and Speed up and optimize device speed
Here bellow you can find the list of applications that can safely removed with out any fear of bricking your Device, Use root explorer or any other file manager to delete bellow mentioned applications
[B][U]System/app folder[/U][/B]
CloudPrint.apk
FileManager.apk
Galaxy4.apk
Galaxy4.odex
GoogleHangouts.apk
HoloSpiralWallpaper.apk
HoloSpiralWallpaper.odex
LiveWallpapers.apk
LiveWallpapers.odex
MagicSmokeWallpapers.apk
MagicSmokeWallpapers.odex
Music.apk
Music.odex
NoiseField.apk
NoiseField.odex
PhaseBeam.apk
PhaseBeam.odex
VisualizationWallpapers.apk
VisualizationWallpapers.odex
[B][U]System/Pri-app folder [/U][/B]
Airdroid.apk
DangerDash.apk
Facebook.apk
Gmail.apk
GooglePlus.apk
L-Explorer.apk
Launcher2.apk (Before deleting this install a custom launcher from market)
Launcher2.odex (Before deleting this install a custom launcher from market)
LavaZone.apk
Maps.apk
mlava.apk
NQ_P209391_AV68.apk
NQ_P209391_Vault.apk
operamini.apk
Quickoffice.apk
QuickSearchBoxNew.apk
SaavnPro.apk
viberDroid.apk
WeChat.apk
YouTube.apk
System/Media folder
LAVA_demo_video.mp4
Code:
[B][SIZE="5"][COLOR="DarkRed"]X-Posed Modding & Enabling Features like Heads-Up ,Lock Screen Notification....Etc[/COLOR][/SIZE][/B]
Install X-posed Framework which is core for all x-posed modding from[URL="http://repo.xposed.info/module/de.robv.android.xposed.installer"] Here[/URL]
Heads-Up Notification : [URL="http://repo.xposed.info/module/com.mohammadag.headsupenabler"]Download Here [/URL]
Lock Screen Notification,Advanced Reboot,Peak, etc [URL="http://repo.xposed.info/module/ind.fem.black.xposed.mods"]Install This [/URL]
Pie Control [URL="http://forum.xda-developers.com/showthread.php?t=1330150"]Download Here [/URL]
Un-Rooting And Restoring Stock Status/Firmware (Un-Bricking Also)
Code:
[B][SIZE="5"][COLOR="DarkRed"]Un-Rooting Guide[/COLOR][/SIZE][/B]
If You Installed Super SU as system application move it back to data/apps from system/apps via root file manager
Go to settings inside super su and click full unroot and uninstall
After reboot your device will be fully un-rooted
Restoring Stock Status/Firmware (Un-Bricking)
Code:
[B][SIZE="5"][COLOR="DarkRed"]Downloading Required Files:[/COLOR][/SIZE][/B]
Download Lava Magnum X-604 Stock Firmware Version : Lava_x604_S008_20140612
[B][URL="http://support.moulnisky.com/index.php?dir=Lava/Magnum%20X604/Software%20Versions/S008_12.06.2014/"]Click Here To Download[/URL][/B]
Download Lava Magnum X604 SW DOWNLOAD TOOL [URL="http://support.moulnisky.com/index.php?dir=Lava/Magnum%20X604/Tools/"]Click Here To Download[/URL]
Download Breadcom Driver Package [URL="http://support.moulnisky.com/index.php?dir=Lava/Magnum%20X604/Tools/"]Click Here to Download[/URL]
Code:
[B][SIZE="5"][COLOR="DarkRed"]Installation/Preparation[/COLOR][/SIZE][/B]
Extract all Downloaded package on your Windows PC Desktop
Install Breadcom Driver Package
Open Extracted Lava Magnum X604 SW DOWNLOAD TOOL
Run “vcredist_x86.exe” to install VC Redistributable.
Run Multi Downloader.exe as Administrator
Select “Setting->Configuration” to enter setting dialog.
Click “…” button. Select your image folder. and select the extracted lava magnum x604 stock firmware folder
If an up level folder selected, tool will search all image package contained.
And list all packages for your selection.
Check Reset in after download mode
apply these configurations
[B][SIZE="4"]How to download [/SIZE][/B]
1. Click “start” on main GUI to enable download main process.
2. Take off the phone battery, unplug the USB cable (make sure the phone is fully
power off), then connect the USB cable from the phone to the PC, put back the
battery.
3. A user should see that the tool detects the device and start flashing.
4. Unplug the phone once the DIAG color is green. Please don’t unplug a phone if
the color is still in yellow. This will cause an error.
Now Your Device is Restored to Original condition like when it was opened from new box
Read more explanations from read me file Inside Lava Magnum X604 SW DOWNLOAD TOOL.zip
Note: If You Are able to Produce Mirror links for Stock firmware and Tools feel Free to create and share it here so that i can add Those mirror Links in op to keep Files alive for Future Users
Credits
V-Root Developers
Sujyot GSM Zone
GSM Hosting
Chain fire
Please Don't say thanks in words Simply press Thanks Button Which is more Meaning full?
Enjoy The Power Unleashed
The-Immortal
Stock recovery and kernel
Stock Recovery and Stock Kernel can be download from Below mentioned download links...
Feel Free to Use these files to make a custom Recovery like CWM ,TWRP etc...
Stock Recovery.img
Stock Kernel(boot.img)
Block Details
{
"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"
}
one more in case
Increase space for apps
The-Immortal said:
one more in case
Click to expand...
Click to collapse
Hi, immortal, thanks a ton for the guide. I managed to root my phone as well as remove most of the bloatware. A couple of questions, would be great if you could help me out with
1. In another thread you mentioned installing fly-on mode for some tweaks to make it run smoother. Would be great if you could help with a link or instructions. I tried googling but could only find ones that needed CWM recovery
2. The space for apps is only 800MB. I know link2sd allows you to allocate external sd card memory, but i was wondering if there is a way to increase the internal memory allocation itself for apps, since there is about 6GB or internal memory.
Would appreciate your help in this regard.
boysha8 said:
Hi, immortal, thanks a ton for the guide. I managed to root my phone as well as remove most of the bloatware. A couple of questions, would be great if you could help me out with
1. In another thread you mentioned installing fly-on mode for some tweaks to make it run smoother. Would be great if you could help with a link or instructions. I tried googling but could only find ones that needed CWM recovery
2. The space for apps is only 800MB. I know link2sd allows you to allocate external sd card memory, but i was wondering if there is a way to increase the internal memory allocation itself for apps, since there is about 6GB or internal memory.
Would appreciate your help in this regard.
Click to expand...
Click to collapse
You can find fly-on mod here ....
http://forum.xda-developers.com/showthread.php?t=2226373
Since till now there is no cwm recovery the option to install this mod is manual installation .....
Follow the same folder structure create and paste files with the help of root explore its the best tool also don't forget to set permission as follows
All new folder 0755
Files inside init.d 0755
Files inside xbin and bin 0755
Rest all files 0644
I did this in same way ...now am almost fully customised with gesture supported android L keyboard
Face lock in lock screen option ..which all lava didn't provided us in stock ROM [emoji12]
Regarding internal space we need to do reparation once cwm recovery is done we can do this easily .....
At present I don't have Linux build environment so am not touching that part my net is dam slow
If any one is ready to setup build environment and compile custom recovery then contact me I will definitely guide you and help you to my best of knowledge ....
Further if you need anything just contact me ....never fear to brick your device i already wrote a unbricking guide which is working perfect ....(I have already bricked my device many times )
All the best
The-Immortal
Sent from my x604 using Tapatalk
The-Immortal said:
You can find fly-on mod here ....
http://forum.xda-developers.com/showthread.php?t=2226373
Since till now there is no cwm recovery the option to install this mod is manual installation .....
Follow the same folder structure create and paste files with the help of root explore its the best tool also don't forget to set permission as follows
All new folder 0755
Files inside init.d 0755
Files inside xbin and bin 0755
Rest all files 0644
I did this in same way ...now am almost fully customised with gesture supported android L keyboard
Face lock in lock screen option ..which all lava didn't provided us in stock ROM [emoji12]
Regarding internal space we need to do reparation once cwm recovery is done we can do this easily .....
At present I don't have Linux build environment so am not touching that part my net is dam slow
If any one is ready to setup build environment and compile custom recovery then contact me I will definitely guide you and help you to my best of knowledge ....
Further if you need anything just contact me ....never fear to brick your device i already wrote a unbricking guide which is working perfect ....(I have already bricked my device many times )
All the best
The-Immortal
Sent from my x604 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick response. Apologies for so many questions, but i am not quite sure how to do it manually. I downloaded the zip "Signed_Fly-On_Mod™_sqlite_KK4.4.zip". I understand thats a flashable file, i tried to unzip it and i got the meta-inf and system folders. where exactly should i put these folders?
Also, i am currently using root browser, do you recommend root explorer (its a paid app right?) I did not understand the numbers you assigned to each folder, is that some kind of root permission that you give in root explorer?
boysha8 said:
Thanks for the quick response. Apologies for so many questions, but i am not quite sure how to do it manually. I downloaded the zip "Signed_Fly-On_Mod™_sqlite_KK4.4.zip". I understand thats a flashable file, i tried to unzip it and i got the meta-inf and system folders. where exactly should i put these folders?
Also, i am currently using root browser, do you recommend root explorer (its a paid app right?) I did not understand the numbers you assigned to each folder, is that some kind of root permission that you give in root explorer?
Click to expand...
Click to collapse
You can safely ignore metainfo folder ...
Only need to paste contents of system folder ie contents inside system folder .....to system folder in your device
Simply contents of system folder to system folder of your device ( inside ticked folder in image )
Root explorer is most best root file manager for ever .... ?
Permissions please refer these images with value
0755
0644
I hope its clear now
The-Immortal
Sent from my x604 using Tapatalk
your links to recovery & boot.img are down
katinatez said:
your links to recovery & boot.img are down
Click to expand...
Click to collapse
I think its working now please have a look
Also please check your XDA PM
Sent from my x604 using Tapatalk
I got them
Not sure if you have a locked bootloader, but you could try this command to find out
Command to boot into bootloader:adb reboot bootloader
Command to check bootloader status: fastboot oem device-info
Command to unlock bootloader: fastboot oem unlock
Command to check if recovery works without writing over your stock recovery: fastboot boot recovery.img
if it works then continue with next step
Command to flash cwm recovery: fastboot flash recovery magnum_recovery.img (on linux this has to be on home folder( or fastboot flash recovery C:\magnum_recovery.img on root folder of C:\ on Windows))
next step
Command to reboot: fastboot reboot
Try this CWM 6.0.5.1 and report back
To test recovery I recommend you install aroma file manger first. And post a picture of mounts here.
katinatez said:
Not sure if you have a locked bootloader, but you could try this command to find out
Command to boot into bootloader:adb reboot bootloader
Command to check bootloader status: fastboot oem device-info
Command to unlock bootloader: fastboot oem unlock
Command to check if recovery works without writing over your stock recovery: fastboot boot recovery.img
if it works then continue with next step
Command to flash cwm recovery: fastboot flash recovery magnum_recovery.img (on linux this has to be on home folder( or fastboot flash recovery C:\magnum_recovery.img on root folder of C:\ on Windows))
next step
Command to reboot: fastboot reboot
Try this CWM 6.0.5.1 and report back
Click to expand...
Click to collapse
Thanks a lot bro...
Actually yesterday night shockxx and myself ported philz recovery but it has some issues of mounting external SD card ..
I will download this file and giving a try by the way my device is having unlocked boot loader so no issues here ....
After testing I will get back to you with result ....[emoji1]
Sent from my x604 using Tapatalk
The-Immortal said:
Thanks a lot bro...
Actually yesterday night shockxx and myself ported philz recovery but it has some issues of mounting external SD card ..
I will download this file and giving a try by the way my device is having unlocked boot loader so no issues here ....
After testing I will get back to you with result ....[emoji1]
Sent from my x604 using Tapatalk
Click to expand...
Click to collapse
The answer to mounting extrnal sd card is on post 2 of philz, you need these repos here
https://github.com/PhilZ-cwm6/android_system_vold
https://github.com/PhilZ-cwm6/android_external_sepolicy
follow instructions for extra.fstab
katinatez said:
The answer to mounting extrnal sd card is on post 2 of philz, you need these repos here
https://github.com/PhilZ-cwm6/android_system_vold
https://github.com/PhilZ-cwm6/android_external_sepolicy
follow instructions for extra.fstab
Click to expand...
Click to collapse
Ya gona give a look ...
I tried your file but its unable to mount sdcard ...so totally unable to do any thing .....
I have unpacked IMG file let's try what I can do [emoji1]
Sent from my x604 using Tapatalk
I used a different fstab try this one it's cwm.
katinatez said:
I used a different fstab try this one it's cwm.
Click to expand...
Click to collapse
OK downloading
Edit: same as old one unable to mount storage/sdcard0
Sent from my x604 using Tapatalk
twrp
Here is twrp 2.8.0.0.
If it's not loading the storage sdcard then I have to adjust the fstab or add flags to correct but without the device it's nearly impossible to figure what it's needed. Recovery logs would help.
Done for the night, will respond in the morning.
katinatez said:
Here is twrp 2.8.0.0.
If it's not loading the storage sdcard then I have to adjust the fstab or add flags to correct but without the device it's nearly impossible to figure what it's needed. Recovery logs would help.
Done for the night, will respond in the morning.
Click to expand...
Click to collapse
OK bro....
Will test this if issue comes I will try to experiment with fstab ....let's see what happens
Sent from my x604 using Tapatalk
Aroma
Try this Aroma file manager its compiled together with philz .
also try this philz build
i have to work now
shoxxy said:
Try this Aroma file manager its compiled together with philz .
Click to expand...
Click to collapse
Fest of recovery for magnum ...[emoji1]
Going to try it ....
Sent from my x604 using Tapatalk

Categories

Resources