Related
Hi every one
wondering if there was any app that would let us browse the Root of the phone in windows ,
Using ADB is quite hard i think ...
just want to remove an app , and add another one to /system/app
tried Root Explorer on the phone , but the deleted program magically reappears after a reboot
any help would be appreciated !
thanks !
SkyWalker1726 said:
Hi every one
wondering if there was any app that would let us browse the Root of the phone in windows ,
Using ADB is quite hard i think ...
just want to remove an app , and add another one to /system/app
tried Root Explorer on the phone , but the deleted program magically reappears after a reboot
any help would be appreciated !
thanks !
Click to expand...
Click to collapse
Were you in Recovery when you attached via Root Explorer?
You can't delete anything from /system whilst the phone is fully booted due to the NAND protection.
Also, take a look at Android Commander.
Regards,
Dave
thanks for the reply , but Adroid Commander Didnt solve my problem , it can't edit /system , since the phone is fully booted ( as u mentioned )
and no , i was not in recovery mode , since ROOT exploerer is installed on my phone , i have to boot it , to use it
thanks !
I thought you said you wanted a Windows app - Android Commander should work fine as long as you boot into Recovery.
There is currently *no* true solution for amending /system whilst the phone is booted, though some people are working on AUFS/UNIONFS workarounds which IMHO, are always going to be a suboptimal solution, and in most cases R/W access via Recovery is the better solution (things like Metamorph not withstanding!).
Regards,
Dave
yes , i need a program to edit /system on windows
i read on their webpage ( androidcommande.com ) that it needed USB Debugging to work correctly so i tried it with the phone on and bootedc , but didn;'t work and didn't change /system .
tried it on recovery , but the files are not displayed correclty , the folders are empty and some doesn't even show up
anyway thanks for ur time and answers
PS : tried ADB command but wthout any success
SkyWalker1726 said:
yes , i need a program to edit /system on windows
i read on their webpage ( androidcommande.com ) that it needed USB Debugging to work correctly so i tried it with the phone on and bootedc , but didn;'t work and didn't change /system .
tried it on recovery , but the files are not displayed correclty , the folders are empty and some doesn't even show up
anyway thanks for ur time and answers
PS : tried ADB command but wthout any success
Click to expand...
Click to collapse
You have to mount the appropriate filesystem(s) from Recovery first!
If you are using ClockworkMod recovery, go into the partitions menu and select mount for any file systems you wish to access. Then connect via AndroidCommander and you'll be able to see the files.
Regards,
Dave
Thanks !
used Clockwork as u suggested , mont /system/ , then adb remount
Searched for some ADB tutorials and got it via the commands
was a bit confused bout "shell" or "not to shell "
but everything worked fine
Thanks again for all ur help !
Warning:I am not responisible for any damage to your phone and rooting usually nullifies the warranty. so please procede with your own risk
I tried to root my karbonn A2 for 2 weeks and finally i got it. so im gonna share the steps involved in rooting and also provoide the tools for it.
NOTE: I do not take credit for any tool since all the tools were already available online, so credit goes to whoever programmed them. only thing i did was to alter the method slightly to get my phone rooted.
Lets begin. Before we start rooting our phone, most important thing is the drivers. so u need two types of drivers one is ADB (android debugging bridge) drivers and the other is preloader drivers. i have attached both of these drivers in the attachments u can download it.
Step1[only for beginners]: Go to setting>applications>development>enable USB debugging in the phone, then connect your phone to ur pc (remove all previous drivers if u have installed) then go to device manager>devices, right click on the usb device and click update driver and browse to folder containing the SPdrvers (u need to extract the folder from the attachment first).If driver is successfully installed then u should see "android phone" in ur device manager. to confirm it just run adb devices from the command line by chagning the directory to where adb.exe is, u should see the list of devices attached to ur pc. (usually adb.exe will be in android sdk tools folder or if u dont have one then check in ADB folder from superoneclick in the attachment).
Step2: ok, now that u have installed adb drivers, u need to install preloader driver (also known as downloading mode in some devices). to do this, disconnect ur phone from the pc, then switch off the phone, remove the battery and then connect ur phone to pc again (without the battery). then u should see windows trying to install drivers and fails. then go to device manager again and browse to folder containing USB VCOM drivers (see attachment). after it successfully installs procede to step 3.
Step3:: download, extract the files MTKROM and SPflash tool to ur pc. then put the battery inside ur phone then switch it on, connect it to pc (enable debugging all the time). then open command line then go to adb folder then type :adb devices- u should see the list of device attached (u will get some long numbers so dont worry). then type "adb shell" (without the quotes). u will get a $ sign, then type "cat proc/mtd > /sdcard/firmware.info" if its successful then a file named firmware.info will be created in ur sdcard root. then copy that file to ur pc.
Step 4: Now open that firmware.info in MTKROM.exe u should see a list tables and address like in the image below. then click save scatter and rename the filename to MT6575 instead of MT6573 (and leave everthing else as it is). so a file named "MT6575_Android_scatter.txt" will be created.
Step 5: Now open Spflash tool and load the scatter file in that. u should see something like this in the image below.
STEPS TO BACKUP ORIGINAL BOOT AND RECOVERY
Step 6: Before we actually begin to root its important to make a backup of current images. so to do that, go to READ BACK tab in sp flash tool. click on Add>double click on the page file and save as "Boot.img" somewhere safe. then click on "Read Page only", this is very important. then look at the address side by side from MTKROM and enter into sptool. the start address is the address in which the boot.img begins and length is the length of boot.img. so final address will be startaddress+length =start address of next image (recovery.img). In MTKROM the start address is given as "PART ADDRESS". after entering those carefully click ok. if u want to be sure then use programmer calculator and add the address.
Note :the address will be in hexadecimal format not decimal.
Step7: In order to read the firmware from the phone, disconnect the phone from your pc, remove the battery, dont connect it yet. now click on "Read back" button in the sptool (its after Add,remove button). now the software starts searching for the device. now connect the device to the pc (without battery ofcourse). now if have installed USB VCOM drivers correctly then the sp tool should detect ur device and start reading from it. u will see Red colour in the
task bar when it detects then blue colour while the tool is reading the phone. wait untill the reading is complete. A green circle will pop up after it successfully reads from the device. (refer the images below)
Step 8: repeat step seven as described above for recovery.img (save the file as recovery.img) then select "read page only" option, enter start address as 0x0980000 and length as 0x0500000. (please enter the address carefully cross check with MTKROM image addresses.)
Note: You have to disconnect the device first then click read back button after entering the addresses then connect the device, otherwise the sptool wont detect your device!.
Actual Rooting Procedure
Step 9: Now that you have backed up both boot and recovery images its time to start the actual rooting. download the boot.img file from the attachment and save to your pc (dont replace it with your backup image that you saved earlier). go to download tab in the sp tool and tick only boot.img and uncheck all others (if any of them has been checked already) and click on Bootimg and browse for the folder where u downloaded boot.img from the attachment and NOT THE BACKUP! after that disconnect your device, then click download button above( after format->upgrade button) or f9 from keyboard. the tool will start searching the usb com ports. now connect your device and wait till it downloads fully. Note: In downloading your will get RED colour first, then YELLOW colour while flashing, and finally a GREEN circle after flashing is complete).
Step 10: The most important and complicates steps are over. now all you have to do is put your battery to your phone and switch it on. now after it sucessfully boots up, open superonclick.exe (you will get this software online and its very popular tool for rooting) and connect the device to your pc (enable debugging of course), then click Root button in superoneclick and Voila! your phone is rooted. enjoy and dont forget to press thanks button if ive helped
Note: u will need .NET framework 3.5 to run superoneclick.
Method To Unroot
For unrooting your mobile all you have to do is flash the original, backup boot image back to your phone. just open sptool and load the scatter file, then click on bootimg then browse to wherever u have stored backup boot.img then click download button then connect your device without the battery and thats it. you will get back original firmware without the root!.
Clockwork mod recovery for A2
There is no official cwm recovery for A2, but i ported cwm for other MT65xx devices to A2. so here are the steps to flash.
step 1: download recovery.img from the attachment.
step 2: open sp flash tool and load scatter.txt (for detailed description refer rooting steps). then tick recoveryimg and browse and set the path of the recovery.img you just downloaded from attachment.
step3: click on download button at the top or press f9. then take out the battery from the phone and connect it to the pc. the tool will detect your phone and start flashing cwm recovery.wait untill the green circle pops up.
step 4: now put in the battery and press power button+volume up and hold it for few seconds and voila!! cwm recovery boots up. And to revert back to original recovery just flash the recovery.img that you backed up during rooting process using the above steps.
Note: Do Not factory reset your phone without backing up the IMEI number. After rooting your device please backup your phones IMEI number which is stored in data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 to a safe place. or there is an application called mobileuncletools (a chinese app) which helps to backup your IMEI to sdcard and restore it back. if u loose your IMEI and reset your phone then you cannot call or recieve sms etc
No service and invalid IMEI solution
explanation:
In case u did factory reset of the phone, then all your data will be wiped including the imei number. it will be reverted to factory imei number, hence you cannot connect to any mobile networks in india or anywhere else because most network operators wont allow to use the network with dupicate or invalid imei numbers. every device has a specific imei number. in this device your original imei numbers (15 digits) will be on the back of your battery.
Restoring is tough very simple procedure, creating the required files is a major headache. At first i thought it was impossible to restore the imei back (trust me i tried all the available solutions that u get in the internet, infact there are 5 different types of solutions, none of which worked for this device). luckily one day i found a chinese software which actually did create a imei file that is compatible with this device (phew !, yeah i know) and so i did successully restored my imei back and i can once again connect to mobile network and make calls..:victory: so here it goes.
How to restore IMEI number? (MUST BE A ROOTED PHONE)
1) if u have made the backup of MP0B_001 file in /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 , then install root explorer and simply replace your current file with the backed up MP0B_001 and set the permissions to rw-rw---- and restart.
2) if u havent backed it up (too bad), then download the chinese software sn_gen.zip from the attachments and enter both imei numbers that is found in the back of your battery (enter the numbers correctly and cross check it again, its 15 digit number). then the software generates a new MP0B_001 file, copy and paste in the above mentioned directory and set the permissions to rw-rw---- and restart.:fingers-crossed:
dont forget to press thanks button if ive helped you :good:
Download Links:
Drivers: http://www.4shared.com/rar/XLiLMsG3/sp_drivers_v14.html?
SP flsah tool: http://www.4shared.com/archive/bjTXvBtd/sp_flash_tool_v3122401.html?
scatter txt: http://www.4shared.com/office/W7Fk6VOm/MT6575_Android_scatter.html?
I need to root my A2 too,can you tell me how?
thanks but I want to put ICS in my device karbonn a2 can u help more
thanx in advance
Sent from my Karbonn A2 using xda app-developers app
vickykeeth said:
thanks but I want to put ICS in my device karbonn a2 can u help more
thanx in advance
Click to expand...
Click to collapse
its not possible to put ICS in A2 (since its officially not supported to our device), although cyanogenmod 9 can be installed but its very difficult to build it since most of the drivers are properitery and they wont release the sources. so its almost impossible to run cm9 and even if someone did build cm9 it wont run smoothly because of very low amount ram in our device (<256MB and ICS needs more than that to work smoothly). however im working to build cm7 (based on gingerbread) for our device and even that is really difficult since there is no device tree in github for this device. so i need build cm7 from scratch and that is not an easy job. so if any developers are working on building cm7 for A2 please pm me so that we can work together..
cm10
abhiatreyas said:
its not possible to put ICS in A2 (since its officially not supported to our device), although cyanogenmod 9 can be installed but its very difficult to build it since most of the drivers are properitery and they wont release the sources. so its almost impossible to run cm9 and even if someone did build cm9 it wont run smoothly because of very low amount ram in our device (<256MB and ICS needs more than that to work smoothly). however im working to build cm7 (based on gingerbread) for our device and even that is really difficult since there is no device tree in github for this device. so i need build cm7 from scratch and that is not an easy job. so if any developers are working on building cm7 for A2 please pm me so that we can work together..
Click to expand...
Click to collapse
if we create any partion sd memory for our internal memory can it run cm10 b'cuz galaxy ace can run cm10 it has just 256MB ram and some wat 800MHZ speed only but our device has 256MD ram with 1GHZ processor speed so i think it can also run cm10 if we create a partition memory from ous sd card thats wat i think so........
waiting for reply from ur side thanks in advance.......
urgent help
i tried to reset my karbonn a2 and done it after reboot it shows no service and also no network wat to do pls tell me thanx in advance..........
vickykeeth said:
if we create any partion sd memory for our internal memory can it run cm10 b'cuz galaxy ace can run cm10 it has just 256MB ram and some wat 800MHZ speed only but our device has 256MD ram with 1GHZ processor speed so i think it can also run cm10 if we create a partition memory from ous sd card thats wat i think so........
waiting for reply from ur side thanks in advance.......
Click to expand...
Click to collapse
lol i was a galaxy ace user untill last dec. (its touch digitizer got broke, so i temporarily bought karbonn). anyway i do know ace can run cm10 and pretty much any device can, even ours can run it. i did not say our device doesnt run at all. i said it wont run smoothly and developing cm other than stock os version is very very difficult since our device is a local device and threre is no lot of support for it. so if anything goes wrong we may permanently brick our devices and may not find solution at all.
on the other hand, since i was a former ace user, i know that even though ace can run cm9 and cm10 there were a lot of problem in getting camera, video recording, and other applications because of unavialablity of their sources. so furthermore most of extra features that arent available in gingerbread cannot be used ex: face recognition, google now,otg usb etc( they are built for high end devices). u wont notice the difference in optimizations and performance of jelly bean in low end devices because they need sufficient hardware to utilize the os to full extent. so only thing u get out of installing cm is user interface (which u can change using of launchers, oh yes there are big bunches of launchers out there) and some features of cm (deodexd rom,custom kernel with overclocking features and some tweaks.)
coming back to our device, ive been trying to build cm7 for our device and its really difficult without a device tree and some good prior experience in building cm for atleast 2 devices. so my advice is that first we will build a fully working cm7 for our device and later if possible we will port cm10.
vickykeeth said:
i tried to reset my karbonn a2 and done it after reboot it shows no service and also no network wat to do pls tell me thanx in advance..........
Click to expand...
Click to collapse
what do u mean by reset? did u do factory reset from recovery or did u clear flash from by holding power+down? (oh btw recovery is power+up in our device).
either way ur imei number has been erased and it will be reset to factory number . i spent 1 week day and night searching for a solution and that is exactly why i told u to backup your MB0P_001 file.
in order to repair it u need to root ur phone. follow above steps and paste ur imei number (dial *#06#).
Nothing in SuperOneClick
I am successful in doing everything, but when I open SuperOneClick, it does not show any device, and clicking "Root" greys off the button for a few seconds, and everything is back to normal again. Nothing happens to the phone.
What is wrong?
shyamsn00 said:
I am successful in doing everything, but when I open SuperOneClick, it does not show any device, and clicking "Root" greys off the button for a few seconds, and everything is back to normal again. Nothing happens to the phone.
What is wrong?
Click to expand...
Click to collapse
ru sure u replaced boot.img which was attached in attachments to your phone? if it was successful then u have unlocked the bootloader. the problem here seems to be like superonclick isnt detecting ur phone when connected to pc. In case if the usb debugging is turned off enable it and check if ur device is listed in adb devices command as explained above. if it does and still rooting doesnt work, then maybe you are using wrong version of superoneclick. because some of the loopholes which is used to root your phone (by gaining temporary access to shell) is not available in older versions. the version must be compatible with gingerbread. try downloading superonclick 2.3.3 version.
also, after u root with superonclick, restart it and please check if u have superuser app in ur phone(it will be automatically installed by superoneclick, dont install it manually since the app should be in /system/app and su command should be in /system/bin directory, which u cannot do by installing it manually). if its installed then u have root access, if u still want to confirm just download root checker app from google play and run it.
CM10 means Jelly Bean Which has minimum Requirement of 512MB ram... device cant even Support Cm9(ics)...And generally cynogenmods are not developed for local Indian Brands.....Instead Try this making your phone look like XPERIA:
http://forum.xda-developers.com/show....php?t=2095956
abhiatreyas said:
ru sure u replaced boot.img which was attached in attachments to your phone? if it was successful then u have unlocked the bootloader. the problem here seems to be like superonclick isnt detecting ur phone when connected to pc. In case if the usb debugging is turned off enable it and check if ur device is listed in adb devices command as explained above. if it does and still rooting doesnt work, then maybe you are using wrong version of superoneclick. because some of the loopholes which is used to root your phone (by gaining temporary access to shell) is not available in older versions. the version must be compatible with gingerbread. try downloading superonclick 2.3.3 version.
Click to expand...
Click to collapse
I have indeed replaced the boot.img file and am using the latest version of S1C [ 2.3.3, I guess ]. Can the problem be because of Win8? Should I try doing this in W7?
hi there thanks for sharing that
But i can't find the way to do anythings that u said .....
i cant updated my phone driver, when i do it says up to date ....
can u please help me
thanks
Mr1010ass said:
hi there thanks for sharing that
But i can't find the way to do anythings that u said .....
i cant updated my phone driver, when i do it says up to date ....
can u please help me
thanks
Click to expand...
Click to collapse
im sorry, im not able to understand your problem. please give more information about your issue.
shyamsn00 said:
I have indeed replaced the boot.img file and am using the latest version of S1C [ 2.3.3, I guess ]. Can the problem be because of Win8? Should I try doing this in W7?
Click to expand...
Click to collapse
ok try it once in win7 and check if the issue is resolved, if not please explain clearly what is the problem and what error message you are getting.
need ua help
hey with your help i rooted my phone successfully.. Thanxx alot,,
Bt please invent custom for karbonn A2.. please
Waiting for your reply..
First 3 steps problem
I already downloaded everything and it seems like even before I started I already encountered a problem. When I try step 2 my KArbonn A2 device cannot be found on the list of devices on the cmd.... No "Android Phone" is found on my device manager but only "Karbonn - A2MS USB Device". When I update the driver it says that it is already the best driver for my device.... I need help pls.....:crying:
BOOTLOOP????????
I cannot boot up after flashing the boot.img,you provides...I've been able to flash cwm recovery successfully and make backups of my recoveries and boot.img...But when I flash the provided boot.img,My phone goess inot a bootloop It shows Karbonn A2 splash and shuts down and restarts,doing the same thing over and over again...Please tell me whether it is a problem with the boot.img or have I done something wrong in the flashing procedure???
Thank you..... finally found out where I went wrong... now my phone is rooted..... A hundred thanks....:victory:
hi!
i installed the regulat 1.6 update to my FP1 and everything was just fine.
then I tried to install the "unified 1.6 update" which worked but the problems begun:
things I noticed:
1. backup ist not really a backup for the apps but just a way to reinstall the apps I had installed without any settings. not a fun way to find that out when reopening your apps.
2. the update to the 1.6 unifyed also messed with my SD card and deleted files and put new ones there. not something I was expecting. luckily I had a backup of the SD card.
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
As all my settings are gone anyway I am open to reinstall the phone from scratch.
fivel_ said:
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
Click to expand...
Click to collapse
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
I am not a mac user but I think you need to install some additional software.
https://www.android.com/filetransfer/
_keesj said:
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
Click to expand...
Click to collapse
thanks a lot, that is what I feared.
hi, i'm also have an upgrade problem: mine is that i can't upgrade at all.
i've repartitioned earlier with the app mentioned in the wiki (wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone).
i've also done the steps _keesj descripes in thread "unified storage setup on re-partitioned FP1" ("Steps for "fiixing" your upgrade").
i'm having Cherry 1.6, and two 7 GB partitions.
does anyone has a solution?
see other (missplaced) post
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Donat.Callens said:
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Click to expand...
Click to collapse
thanks, i've read it again and tried _keesj's solution again, unfortunately it didn't solve my situation.
i'm a layman in this area, so probably i shoudn't haved 'played' with partitions at all (but with the app it was easy).
my previous post wasn't quite complete... i have had an unified partition before...
because of an app that didn't work, i used the repartition app again to see if that could solve the problem.
it did, but later i wondered if a wrong install in the unified sistuation was the problem... so i thought 'let's try the unified partition again'...
i thought i could simply re-use the Fairphone Updater...
so maybe i'm now having a unified partition divided in 2?
and lost the ability to ever upgrade to newer versions of the Fairphone OS?
i hope someone can help me...
jjjanssen said:
i could simply re-use the Fairphone Updater...
Click to expand...
Click to collapse
Make sure you allow it to reinstall the default recovery.
Donat.Callens said:
Make sure you allow it to reinstall the default recovery.
Click to expand...
Click to collapse
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Hi,
jjjanssen said:
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Click to expand...
Click to collapse
Non unified images have a different signature. The moment you use the partition upgrader it will change the accepted signature and will no longer allow older images. If all is as I expected your running image is still the parition upgrader image and it contains the tools to perform the last step of the re-partitioning (e.g. calling the script and performing a recovery with format).
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
_keesj said:
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
Click to expand...
Click to collapse
I couldn't find any (log) files in /cache/recovery, but...
flashing the EBR1 from the FUSE binaries (FP1U) to my FP1 solved it! :victory:
thanks to _keesj, Rick (from Fairphone) and Christian (Fairphone forum)!
here is Rick's tutorial (with a few notes of my own):
You can only fix this by flashing your phone:
For GURU's only! (flashing with ADB). The alternative is to use the windows flasher tool.
1) Download the original image binaries from Fairphone's site (as a new user I, jjjanssen, can't post links yet).
(Download FP1U's zip: Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip)
2) unzip the file
(I chose to unzip to location D:/FP1U.
after that i moved all content from the directory which contained EBR1, to D:/FP1U.)
3) enable usb debugging (on your phone: Settings, Developer options, turn USB debugging on)
4) push EBR1 on the phone: (Open (if you're using Windows) the Command Prompt)
adb push FP1U/EBR1 /mnt/sdcard/
(For instructions on how to use ADB search this site)
5) become root:
adb shell
(after that I also became super user (command su), but maybe that's not necessary; Rick didn't mention it. )
6) override the partition inforation:
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot into recovery:
reboot recovery
8) choose to wipe data and cache
(after that, choose reboot)
Click to expand...
Click to collapse
Hello, as some of you may already know, we can't flash MM kdz on our LG Spirit using LG Flash Tool, so we have to use LG UP, a method which is also used by LG G4c owners. I drew the idea from them, since G4c and Spirit are practically the same devices. I've modified a script from G4c, all credits go to @bender_007.
So here are the steps:
1. Make sure you have USB drivers installed.
2. Download and install LG UP: http://www.filedropper.com/g4 ---- First install LGUP_8994_DLL_Ver_0_0_3_23, then LGUP_Install_Ver_1_14_3.
3. Download the script that makes LG UP recognize our device as H440n(Courtesy of @bender_007, I only modified small parts of it). Link: https://www.dropbox.com/sh/lbxdwloffi75qqg/AABfz5e9AIiSxipsnZQIiikGa?dl=0 (Download as zip)
4. Extract the zip and run h440n.bat
5. Connect your Spirit in MTP mode.
6. Run LG UP and wait for it to load.
7. Leave all settings as they are.
8. Under file path, browse to the kdz file you downloaded. NOTE: It won't show in the directory it is in, because the browse window sees only .tot files, so you have to manually type in the KDZ name in the text field and select it that way.
9. Click Start
10. Wait
11. ???
12. Profit! Enjoy your LG Spirit running Marshmallow!
Thanks, I had to manually copy the dll in the LGUP folder, dunno if it's my fault, or script's fault though.
EDIT: It gives me an error on boot, about CUST not existing... Nothing important, I can continue to use it but it's rather annoying? Fixes? Thanks.
guglicap said:
Thanks, I had to manually copy the dll in the LGUP folder, dunno if it's my fault, or script's fault though.
Click to expand...
Click to collapse
I suppose yours, because it worked for me flawlessly. If someone notices any errors in modifications I made to the script, feel free to correct me.
Fobos531 said:
I suppose yours, because it worked for me flawlessly. If someone notices any errors in modifications I made to the script, feel free to correct me.
Click to expand...
Click to collapse
Depending on OS and security level it can happen, it might need an elevated access- Try: right click - run as administrator
Poslano sa mog SM-G930F koristeći Tapatalk
Had to also copy everything over manually, running as admin didn't help. I haven't done anything to my security settings and am running on the only account that was created with the install. I think it might have something to do with me running on dev mode though.
jonixas said:
Had to also copy everything over manually, running as admin didn't help. I haven't done anything to my security settings and am running on the only account that was created with the install. I think it might have something to do with me running on dev mode though.
Click to expand...
Click to collapse
nah, I also run dev mode. No worries I'll create a desktop app which will then work.
Poslano sa mog SM-G930F koristeći Tapatalk
Afternoon fellas. I have reached the part of runinng the kdz via LGUP however the kdz i have (named H525n20c_00_0321.kdz) brings back an error of invalid kdz. Could someone be so kind as to point out a working link for the kdz if possible?
Thanks
Diarno said:
Afternoon fellas. I have reached the part of runinng the kdz via LGUP however the kdz i have (named H525n20c_00_0321.kdz) brings back an error of invalid kdz. Could someone be so kind as to point out a working link for the kdz if possible?
Thanks
Click to expand...
Click to collapse
Firstly, do you have LG Spirit or LG G4c?
guglicap said:
Thanks, I had to manually copy the dll in the LGUP folder, dunno if it's my fault, or script's fault though.
EDIT: It gives me an error on boot, about CUST not existing... Nothing important, I can continue to use it but it's rather annoying? Fixes? Thanks.
Click to expand...
Click to collapse
I had to manually move dll too. But I made it!
@Fobos531 hello good job . bro I can install MM on lg spirit 4g H440F
Mark XP said:
@Fobos531 hello good job . bro I can install MM on lg spirit 4g H440F
Click to expand...
Click to collapse
Wait until H440F kdz is released.
P.S.: I had to copy all files manually and manually Merge registry script. Probbably some Windows 10 BS with UAC and bat scripts lately.
Another BS, now from phone - MSC error on boot. But that temp root isn't availiable :/
Im stupid, what is MTP mode?
MadjijaHacker said:
Im stupid, what is MTP mode?
Click to expand...
Click to collapse
Regular mode what is enabled by Deafult on KitKat and newer ROM's. It is also known as Media Transfer Protocol and when you connect phone it should look something like this (screenshot from my PC with my current device connected because of copying nandroid backup to PC)
Antoher note: for LG Spirit it looks like Phone Icon, not Media Device.
midzan21 said:
Regular mode what is enabled by Deafult on KitKat and newer ROM's. It is also known as Media Transfer Protocol and when you connect phone it should look something like this (screenshot from my PC with my current device connected because of copying nandroid backup to PC)
Antoher note: for LG Spirit it looks like Phone Icon, not Media Device.
Click to expand...
Click to collapse
I knowed that, but i didnt know what is name of it.
i have a few questions, can i back to lollipop? and the adoptable storage is working?
BrainNotFound said:
i have a few questions, can i back to lollipop? and the adoptable storage is working?
Click to expand...
Click to collapse
Yes, you can get back by flashing kdz using LG Flash Tool and as far I saw there isn't enabled Adoptable Storage.
Can you do the same for the LG Spirit h420?
Can someone upload photos ?? Do you feel any diference ate speed or maneging RAM ??
jopafon said:
Can someone upload photos ?? Do you feel any diference ate speed or maneging RAM ??
Click to expand...
Click to collapse
Just check General Info Therad here (last 2-3 pages) - http://forum.xda-developers.com/android/development/lg-spirit-h440n-thread-t3108435
BrainNotFound said:
i have a few questions, can i back to lollipop? and the adoptable storage is working?
Click to expand...
Click to collapse
To anyone interested:
I got adaptive storage to work! It's pretty simple. Just follow the guide from modaco.com (search for "modaco adaptive storage galaxy s7" on google", I don't think I can post links).
Then go to Settings -> Storage & USB -> Your SD Card -> Merge (in the additional menu).
Hello everyone,
Here are some step by step guides for those of you who need detailed instructions for rooting and un-rooting the T-mobile LG G5.
The guides are short and to the point and are meant to be followed one after the other (STEP#1 --> STEP#2 --> STEP#3).
For the step#3 guide, you must choose one out of the three available guides below:
Guides:
Tmobile-LGG5_pre_flash_MM_6_0_1_requirements_STEP_1
Tmobile-LGG5_pre_flash_MM_6_0_1_requirements_STEP_2
Tmobile-LGG5_flash_root_with_stock_MM_6_0_1_Re-install_STEP_3 <------ If you want to re-install stock MM 6.0.1 with root
Tmobile-LGG5_flash_root_with_stock_MM_6_0_1_Upgrade_only_STEP_3 <------ If you want to root current stock MM 6.0.1
Tmobile-LGG5_flash_Stock_UnRoot_MM_6_0_1_STEP_3 <------ If you want to have stock MM 6.0.1 only (no root, use this if you want to return the phone or sell it)
They will walk you through:
Downloading and Installing the necessary drivers / tools
Unlocking your bootloader
Flashing the stock .kdz file
Flashing the rooted .TOT file
Using TWRP to gain root status
I assume the following:
You are using a Microsoft Windows operating system (Windows 7 or above)
You understand that all data on your phone will be deleted
You understand that your warranty is now gone
You understand that YOU MUST follow the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
You understand that YOU MUST follow the steps in the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
Your phone's USB PC Connection (mode your phone is in when connected to your PC) is on File Transfer mode. ADB and Fastboot commands to the device WILL NOT work if device is not on this mode
You read the Useful tips & information for the T-mobile LG G5 post
You read the Changelog + News & Additions post
***Un-root***
If you want to "un-root" your device (go back to default stock) use the Tmobile-LGG5_flash_Stock_UnRoot_MM_6_0_1_STEP_3 guide.
(Keep in mind that this WILL DELETE all data on the phone)
***Disclaimer***
I take no responsibility in what you do to your phone
The step-by-step guides in this thread were made with the assumption that you will strictly follow them one after the other.
(If you don't, YOU WILL brick your phone!)
If you run into an problem, verify that you have correctly completed all the steps for each guide before posting to this thread. Most problems come from guides / steps that were skipped.
If possible use a laptop that is fully charged and plugged in to an outlet instead of a regular PC (unless it has a UPS attached to it) just in case you lose power during the flashing process.
(If you use a regular PC without a UPS attached to it and you lose power during the flashing process, YOU WILL brick your phone!)
I would like to thank the following people for making all of this possible:
tungkick
wolfu11
arjuna_
Your work and dedication does not go unnoticed, thank you. I would also like to thank anyone else not mentioned here that allowed the rest of us to get root on our beloved LG G5 phones. The android community is awesome!!!
Sections:
Post#1: Main introduction & Files
Post#2: Useful tips & information for the T-mobile LG G5
Post#3: Changelog + New & Additions
Please leave a thank you if you find any of this helpful
**Useful tips & information for the T-mobile LG G5**
How to install xposed: (Keep in mind that versions will change over time)
Download the latest xposed framework currently (xposed-v85-sdk23-arm64.zip):
- Go to the following web address: http://dl-xda.xposed.info/framework/
- Click on the sdk23 link
- Click on the arm64 link
- Download the latest xposed zip file currently xposed-v85-sdk23-arm64.zip
Download the latest xposed installer currently (xposedInstaller_3.0_alpha4.apk):
- Go to the following web address (xda thread): http://forum.xda-developers.com/showthread.php?t=3034811
- Scroll down to the "Attached Files" section and download the latest xposed installer currently (xposedInstaller_3.0_alpha4.apk)
Copy both files to the SD-CARD of your phone
Restart your phone into TWRP
Click on the INSTALL button
Flash the xposed framework file (xposed-v85-sdk23-arm64.zip)
Restart your phone and let it start normally
Go to Settings -> General Tag -> Fingerprints & security, Scroll down to the Phone Administration category and make sure there is a check mark next to Unknown Sources option
Open a file manager
Go to the location of the xposed apk
Install the xposed installer .apk file (xposed Installer 3.0 Alpha 4 apk)
Go to Settings -> General Tag -> Fingerprints & security, Scroll down to the Phone Administration category and remove the check mark next to Unknown Sources option
Start the xposed app
How to enter download mode
Power off the phone
Press and hold the VOLUME UP key
Connect the phone while holding the VOLUME UP key to your PC (use a USB-C cable)
Keep holding the VOLUME UP key until you boot into download mode
How to fix the Fastboot device driver issue (no devices detected)
Visit the following website and follow the instructions: Manually installing Android ADB USB Driver
**Changelog + News & Additions**
Changelog (for the guides only):
7.16.16 - All guides have been updated to reflect the new 10d .kdz and .tot files. All links to tools, .kdz, and .tot files have been updated as well.
News & Additions:
7.16.16 - Multiple updates
A modified H83010d rooted .tot file has been released (thanks to Tungkick & wolfu11)
Guides are safe to use again. All links in all the guides have been updated to reflect the new H83010d files
If TWRP is not showing the internal storage but only the external SD-card take a look at post 24
7.9.16 - There is a new firmware update (H83010d) for the LG G5 (T-mobile) which is not compatible with firmware (H83010a) the .TOT files used in this thread have
If you upgrade to this new firmware, you will lose root.
There is no current way to get root on the new H83010d firmware unless the modified .TOT / KDZ files are released with TWRP included
There is an anti-rollback feature in the LG G5 (t-mobile) phone that prevents you from flashing back the H83010a firmware after you upgrade to the H83010d firmware. Attempting to do this WILL BRICK your phone!
Do not attempt to use the guides which are using H8301a .tot / kdz files if you have updated to H8301d. I will be updating the guides as soon as the H83010d modified .tot / kdz files come out.
5.29.16 - LG G5 & LG V10 possible driver issue: First reported on Post#6
If you own an LG V10 and have used your PC to root it, you most likely installed drivers, tools, and or files specific for the V10. What this means is that you may have to uninstall those drivers, tools, and or files prior to installing anything to be used for rooting the G5. This does not include the ADB program which can work for both.
i just felt the need to post and say thanks for this even though i dont need it. Great effort pulling these together, they look good and are very clear. Thanks! :good:
mallman said:
i just felt the need to post and say thanks for this even though i dont need it. Great effort pulling these together, they look good and are very clear. Thanks! :good:
Click to expand...
Click to collapse
Thank you.
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
Two questions:
1) Does this automatically encrypt the phone? After flashing both the no verity and the SU it boots in to "encrypting" with no other option. I have not had this happen with any other device. Did I mess something up?
2) The password at the beginning of TWRP is requested every time, even after flashing the no verity zip. What did I do wrong?
Click to expand...
Click to collapse
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
skyfox99 said:
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
Click to expand...
Click to collapse
Thank you for your input skyfox99. Your solution to the issues you faced will help others avoid them. You made me think of something I did not anticipate which is what happens when you attempt to root your G5 using the same PC you used to root a V10. I am definitely adding a service announcement to the Changelog (post#3) to address this possible issue.
When I get to step 13: Verify that the LGUP Tool works... the progress frame never shows up, even after restarting my PC. Am I missing something? Please help
bigchuq said:
When I get to step 13: Verify that the LGUP Tool works... the progress frame never shows up, even after restarting my PC. Am I missing something? Please help
Click to expand...
Click to collapse
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
skyfox99 said:
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
Click to expand...
Click to collapse
Your internal storage gets wiped. That's why they weren't there.
mikeyinid said:
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
No I was not, I'll give it a shot. Thanks
mikeyinid said:
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
snowlin said:
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
Click to expand...
Click to collapse
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
thoward3 said:
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
Click to expand...
Click to collapse
I guess I'm having trouble understanding exactly what your issue is. Are you saying that when you boot into TWRP and you go to the INSTALL section to flash the encryption zip and the superSU zip you don't see the files? Can you attach a few screenshots so that I can better understand what you are going through. Thank you.
mikeyinid said:
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
No, I copied after wipe so they were there. Computer recognized them and so does file manager.
jun19inf said:
I guess I'm having trouble understanding exactly what your issue is. Are you saying that when you boot into TWRP and you go to the INSTALL section to flash the encryption zip and the superSU zip you don't see the files? Can you attach a few screenshots so that I can better understand what you are going through. Thank you.
Click to expand...
Click to collapse
TWRP has trouble mounting.
thoward3 said:
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
Click to expand...
Click to collapse
There is a TWRP bootloop set of instructions in another thread, run those commands and see if it resolves it, maybe?
snowlin said:
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
Click to expand...
Click to collapse
I had to reflash no verity a few times, before installing SU. There seems to be a problem with TWRP.
Sent from my LG-H830 using Tapatalk
I didn't have any of the issues you guys are reporting in this thread. TWRP sees both internal storage and SD card. And has since I originally rooted.
Will unlocking the bootloader and rooting my phone or if I install a ROM take away my sim unlock?
Sent from my LG-H830 using XDA-Developers mobile app
shaneg79 said:
Will unlocking the bootloader and rooting my phone or if I install a ROM take away my sim unlock?
Sent from my LG-H830 using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a good question and I unfortunately do not know the answer. I truly don't think your sim will be affected but I am not sure. Sorry.
jun19inf said:
This is a good question and I unfortunately do not know the answer. I truly don't think your sim will be affected but I am not sure. Sorry.
Click to expand...
Click to collapse
It's ok I found out it doesn't affect it thanks for your answer.
Sent from my LG-H830 using XDA-Developers mobile app
I'm having the same issue that some of you had. When I boot into recovery, I can't find the zip files anywhere. Was anybody able to figure it out??
rebelde80 said:
I'm having the same issue that some of you had. When I boot into recovery, I can't find the zip files anywhere. Was anybody able to figure it out??
Click to expand...
Click to collapse
It's a very weird problem and unfortunately the only thing I can think off is that TWRP might not be compatible with the SD-Card you are using.