I have rooted LG L80 D380 v10d-IND-XX with Purpledrake-lite.
cwm recovery for lg l80 is being tested at below links but it is in russian language. Procedure for unlocking lg l80 bootloader with 'auto unlock script' and installing cwm.img with terminal emulator is mentioned. it would be helpful if anyone can interpret the discussions and answer some queries.
( ____SOLVED____ )
Bootloader unlock link:
http://4pda.ru/forum/index.php?showtopic=576048&st=680#entry37784411.
Cwm recovery installation link:
http://4pda.ru/forum/index.php?showtopic=576048&st=900.
Thanks.
SOLVED:
Bootloader unlock and cwm at above links are working for lg l80 d380 v10d. Originally it is developed for v10c. No data will be erased during the process. Backup and restore is checked working.
Some tips-
1) bootloader unlock script LGL80D380.exe have option for english language but only russian is working. There are 6 executions in russian language, i opted first one to unlock bootloader.
2) cwm 6_0_5.img to be installed with terminal emulator.
3) reboot to system from cwm prompts root fix ---> click yes.
4) to enter cwm recovery ( to be used only after confirming installation of cwm recovery, otherwise all data will be erased)
*press vol.down+power.
*when lg logo is seen release power and press again until factory reset screen is seen.
*click yes.
*again yes.
*cwm recovery will appear.
Note-
To check bootloader lock status adb command 'adb reboot bootloader' is not working. Also service menu code 3845#*380# does not have any option for bootloader lock status. But i think bootloader must have been unlocked.
Any other method for system backup and restore for lg l80 D380 ?
sasays said:
I have rooted LG L80 D380 v10d-IND-XX with Purpledrake-lite.
cwm recovery for lg l80 is being tested at below links but it is in russian language. Procedure for unlocking lg l80 bootloader with 'auto unlock script' and installing cwm.img with terminal emulator is mentioned. it would be helpful if anyone can interpret the discussions and answer some queries.
Click to expand...
Click to collapse
Hey Friend, I am unable to download those tools from 4pda.ru. It says 404 Error - Not Found. Can you please mirror it. Thanks.
---------- Post added at 06:07 AM ---------- Previous post was at 05:26 AM ----------
And also, How may I boot into fastboot mode?
lifehacker69 said:
Hey Friend, I am unable to download those tools from 4pda.ru. It says 404 Error - Not Found. Can you please mirror it. Thanks.
---------- Post added at 06:07 AM ---------- Previous post was at 05:26 AM ----------
And also, How may I boot into fastboot mode?
Click to expand...
Click to collapse
File is attached..
For fastboot mode, i have seen some some lg post at xda that it is hidden behind download mode. For fastboot you will have to disable download mode by editing/deleting some system file.. search for it.. i have not tried that..
sasays said:
File is attached..
For fastboot mode, i have seen some some lg post at xda that it is hidden behind download mode. For fastboot you will have to disable download mode by editing/deleting some system file.. search for it.. i have not tried that..
Click to expand...
Click to collapse
Thanks Friend. Was waiting for this file. The link seems to no longer work. Now the page gives me error 404. Thanks mate. :good:
lifehacker69 said:
Thanks Friend. Was waiting for this file. The link seems to no longer work. Now the page gives me error 404. Thanks mate. :good:
Click to expand...
Click to collapse
Fastboot guide for l90.. not checked for l80..
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
sasays said:
Fastboot guide for l90.. not checked for l80..
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
Click to expand...
Click to collapse
Thanks mate. Will try and report soon.
Fatsboot Worked!
The Method for l90 for obtaining fastboot worked.
Thanks!
lifehacker69 said:
The Method for l90 for obtaining fastboot worked.
Thanks!
Click to expand...
Click to collapse
What is bootloader lock status on fastboot screen?
Unlocked!
sasays said:
What is bootloader lock status on fastboot screen?
Click to expand...
Click to collapse
When I entered 'fastboot oem device-info' , it showed tampered and unlocked status as false.
Then I entered 'fastboot oem unlock'. And again checking device-info it showed unlocked status true.
It might mean Unlocking actually worked by this modified bootloader.
Code:
C:\Users\admin\Desktop>fastboot devices
4a141be fastboot
C:\Users\admin\Desktop>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.013s]
finished. total time: 0.015s
C:\Users\admin\Desktop>fastboot oem unlock
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\admin\Desktop>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.007s]
finished. total time: 0.007s
lifehacker69 said:
When I entered 'fastboot oem device-info' , it showed tampered and unlocked status as false.
Then I entered 'fastboot oem unlock'. And again checking device-info it showed unlocked status true.
It might mean Unlocking actually worked by this modified bootloader.
Click to expand...
Click to collapse
That means we installed cwm.img on a locked bootloader and is working well. So can cwm.img be flashed on original locked bootloader without running .exe script.. have you tried cwm installation before running script..
Thanks
sasays said:
That means we installed cwm.img on a locked bootloader and is working well. So can cwm.img be flashed on original locked bootloader without running .exe script.. have you tried cwm installation before running script..
Thanks
Click to expand...
Click to collapse
No, But I think installation of cwm was only possible when the script cracked the bootloader.
The bootloader got unlocked but the flag of unlocked status was not set.
lifehacker69 said:
No, But I think installation of cwm was only possible when the script cracked the bootloader.
The bootloader got unlocked but the flag of unlocked status was not set.
Click to expand...
Click to collapse
I changed the lock status flag of my device as stated by you. Would like to know something more from you.
I tried rom porting with rom-porter guide as below-
1) port-rom cm11( for L40 with similar chipset,cpu,sdk etc.) and base-rom Lfino(working on L80 with bugs) from 4pda.
2) init.d not supported in stock rom and base-rom, but i copied init.d folder from cm11 to base-rom.
3) updater script in base-rom has set_perm and in port-rom it shows set_metadata. Editing gives error so i kept it unchanged.
4) All other steps were completed as stated.
After flashing the ported zip cm11 booted with a blank screen and again went to boot animation after few seconds. So what must be stopping the rom at blank screen after boot animation..
1) does cm require script to run at startup to boot-in thus requiring init.d which is missing in base-rom..
2) or is it due to the conflict of set_perm and set_metadata in updater script.
3) or something else.
i know its all crap and i dont know anything about development. Your comments please..
set_perm is deprecated since cwm version 6.0.4.5. We have to use set_metadata.
The problem you state might be due to incorrect permissions or unsupported libraries from l40.
Better would be to use ArchiKitchen to port as it takes care of the permissions.
As I know, it is very hard to port cm roms to non cm based roms because cm roms uses various scripts and custom kernel with optimizations.
The nearest device I found with working cm11 was LG L70 (D325 global w3ds version. Our is D380 w6ds.)
I have ported all the device trees and vendor files for L80 and will try to build cm11.
My current status is I am at repo sync and will take some days to complete. (My internet is very slow. )
As of now, I have successfully built cwm recovery and kernel (boot.img) for stock based roms.
Link to the folder : https://drive.google.com/folderview?id=0Byu6dt70FNVkTFhCa0lia2p1cDg&usp=drive_web
Please test and report me whether they are working?
This thread might be useful. Give it a try. :- http://forum.xda-developers.com/showthread.php?t=2532300
Ok
lifehacker69 said:
Please test and report me whether they are working?
Click to expand...
Click to collapse
Ok.. can i flash with flashify? Cwm and boot img both at a time or individually?
sasays said:
Ok.. can i flash with flashify? Cwm and boot img both at a time or individually?
Click to expand...
Click to collapse
You may but better use fastboot to flash.
lifehacker69 said:
You may but better use fastboot to flash.
Click to expand...
Click to collapse
Used flashify.. chkd cwm 6.0.5.1 backup, restore, wipe data, dalvik and all worked. Not sure, but I felt backup of system partition was little slower. Back camera is not working, it shows front cam view on all modes including video recording. Torch (flashlight) not working.
Thanks
___
lifehacker69 said:
You may but better use fastboot to flash.
Click to expand...
Click to collapse
sshots
Related
hey guys,
i have a big problem. i bought a photon q 4g from ebay.
its with sim mod and had a unlocked bootloader (status code: 1)
so i readed some topics about using custom recovery and root for the phone and started
its not the first time i flashed a phone i already had droid2, droid3 and droid4
first i get stuck because fastboot was giving me a message of "variable not supported" & "download size to large"
but i found a mfastboot that flashed the recovery without a error message
so i restart the phone but the recovery not come up.
booting the system is no problem.
but when i wanne go in recovery (power+vol up, from bootloader, adb reboot recovery..) the phone restarts and boot up normal.
Moto boot logo->moto boot logo again->boot animation->system
i tryed to erase recovery and flashed again but the same happen.
tryed with cwm and twrp. maybe someone have the original 3e recovery.img?
and for what is the console option under APfastboot in the boot menu select?
someone know whats the difference between status code 1 & status code 3?
deleting userdata & cache with fastboot only reset the rom i have. :silly:
Status code 3 should be what you need. Maybe you should try unlocking it for yourself to make sure that it actually was unlocked. There are instructions for the full process from unlock to installing recovery to getting root in my signature if you need step-by-step.
Solust said:
Status code 3 should be what you need. Maybe you should try unlocking it for yourself to make sure that it actually was unlocked. There are instructions for the full process from unlock to installing recovery to getting root in my signature if you need step-by-step.
Click to expand...
Click to collapse
that was one of the first things i tryed but it not work. iam not sure what fastboot was saying (i`l look it up when iam at home) something like "no unlock data"
but when i start APfastboot it say "UNLOCKED status code:1" so its not locked.
but cant find information about the difference.
Edit: i see that i have no recovery-from-boot.p. someone know where i can get the correct one?
some more information: the phone run "AP Fastboot Flash Mode (NS) 10.97"
when i typed fastboot getvar all i saw
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) unlocked: notsupported
(bootloader) iswarrantyvoid: notsupported
the phone is running a not released test firmware with some apps that are not made for public i think.
there is a su in system/xbin and one app named TamperDetect(qualcomm app?)( only 2 button "get var" and "set var") say the phone is permanently rooted
but i installed superuser and it not work.
but other app called DockStatus(moto app?) let me make a adb over wifi with [email protected]_c: #
could that help me fixing my problem?
no one knows what wrong?
huhu1312 said:
no one knows what wrong?
Click to expand...
Click to collapse
I would try giving Motorola a call and see if they can help you. I would think they would at least be able to tell you the difference between the status codes, though who knows if they could get it unlocked for you or not.
no here is no good support in germany
and i read status code 1 = developer device
and why should it be locked if the phone say unlocked?
Why don't you go into the Bootloader menu and try it from this point into the recovery?
VOL_UP+VOL_DOWN+POWER
Loader009 said:
Why don't you go into the Bootloader menu and try it from this point into the recovery?
VOL_UP+VOL_DOWN+POWER
Click to expand...
Click to collapse
if u read my first post correct u will see i tryed and it not work..
Argh, sorry, I only read the first (key-combination) and overread the bootloader and adb.
My Bootloader version is 10.9B.
But my first Line shows "AP Fastboot Flash Mode (S)" instead of (NS).
You should try to contact the american Motorola support...
At least you should try to get some help from them.
I think because you got a developer device, it is slightly different with the partition sizes.
edit: What is with OTA updates on Stock ROM?
i found out S stand for secure NS for non secure
Please try "adb shell" and then "su", do you get a "Permission denied"?
If that works, you should be able to remount the /system partition to rw.
This way you should also be able to install superusers su, somehow... (sorry, never installed it that way)
But this won't help you in your situation.
Please backup your /system, before you make a custom firmware on it (if you'll ever have success).
Those test apps might be interesting.
As you already tried to flash a custom recovery, I assume that the "stock" (or test) recovery is already gone.
My thought is to bring your Bootloader up to date. But I'm not sure, if that would brick your device.
I'm also not sure, if Motorola America will be helpfull with a developer device in your hands.
But without a (valid) sbf flash file you won't be able to flash the appropriate firmware. I haven't seen any official sbf file for our Photon Q.
Theoretically I would say, that you could also try to flash a FXZ file, but it could also brick your device. (Please don't forget to backup /system)
http://forum.xda-developers.com/showthread.php?t=2095536
i know that flashing all can brick the phone thats why i not test it for now.
and yes the root via adb work.
i only found 1 guy in the internet with the same problem like me. he said it was fixed when he flashed a older recovery from GB but is there a old recovery img like this? (this guy had an other phone)
I saw somewhere a stock recovery (that's how I made my OTA Updates).
I still got it, but I prefer to find an uploaded one.
recovery.img 10MiB
CRC32 386A247D
MD5 46CB664521F98B1C1987C288A101A5EC
If you (or I) won't find it, I'll upload it.
Edit: Found it -> http://forum.xda-developers.com/showthread.php?t=2333094
Another one -> http://forum.xda-developers.com/showthread.php?t=1856456
thanks but this files i tryed already;/
i only made a copy of /system/ folder for now
i flashed all with rsd lite 6.1.4 now. and it worked
Hello guys, after a long time with the APPLE, i´ve changed to android.. mainly because of OPO. No regrets.
After a few seconds using it i´ve rooted it and was really happy...
But... after the OTA of the version XNPH30O of CyanogenMod i´m unable to root it again...
I can fastboot... but it stay at the fastboot logo...
Reading arond the interwebs, i´ve realized that it could be something related with the bootloader being locked.... so i´ve unlocked (i think) using the OPO toolkit.. I wiped it and still cannot bypass the fastboot screen..
Any sugestion or help would be awesome.
I´m running th OPO on CyaniogenMod XNPH30O, chinese model.
Thanks and cheers from Brazil.
Go into fastboot mode and issue this command:
Code:
fastboot oem device-info
Post the results.
Transmitted via Bacon
ogabriel said:
Hello guys, after a long time with the APPLE, i´ve changed to android.. mainly because of OPO. No regrets.
After a few seconds using it i´ve rooted it and was really happy...
But... after the OTA of the version XNPH30O of CyanogenMod i´m unable to root it again...
I can fastboot... but it stay at the fastboot logo...
Reading arond the interwebs, i´ve realized that it could be something related with the bootloader being locked.... so i´ve unlocked (i think) using the OPO toolkit.. I wiped it and still cannot bypass the fastboot screen..
Any sugestion or help would be awesome.
I´m running th OPO on CyaniogenMod XNPH30O, chinese model.
Thanks and cheers from Brazil.
Click to expand...
Click to collapse
To root you need to unlock the boot loader than you install a customer recovery. After you do this I recommend that you make a nandroid backup for when you want to go back to stock (a nandoid is an exact back up of you phone). Once you have unlocked the boot loader and installed a custom recovery made a backup you would put a flashable root zip on your SD and flash it in recovery. Most will recommend that you do not use a tool kit because it is doing the work for you and you don't really know/understand what is happening. I have not updated to XNPH30O but I'm sure its been rooted.
You need to have ADB and fastboot on your computer. << Google how to get this done.
Use this guide it will help do the following. >> http://forum.xda-developers.com/showthread.php?t=2788632
1. Put phone in fastboot
2. run command "fastboot OEM unlock" < this is what unlocks the bootloader it wipes your phone.
3. You will need to install a customer recovery
4. Flash the flashable Super User.
Hope this helps.
jdh10475 said:
To root you need to unlock the boot loader than you install a customer recovery. After you do this I recommend that you make a nandroid backup for when you want to go back to stock (a nandoid is an exact back up of you phone). Once you have unlocked the boot loader and installed a custom recovery made a backup you would put a flashable root zip on your SD and flash it in recovery. Most will recommend that you do not use a tool kit because it is doing the work for you and you don't really know/understand what is happening. I have not updated to XNPH30O but I'm sure its been rooted.
You need to have ADB and fastboot on your computer. << Google how to get this done.
Use this guide it will help do the following. >> http://forum.xda-developers.com/showthread.php?t=2788632
1. Put phone in fastboot
2. run command "fastboot OEM unlock" < this is what unlocks the bootloader it wipes your phone.
3. You will need to install a customer recovery
4. Flash the flashable Super User.
Hope this helps.
Click to expand...
Click to collapse
That's all good, but we need more information from him before giving advice, hence my post.
Transmitted via Bacon
timmaaa said:
That's all good, but we need more information from him before giving advice, hence my post.
Transmitted via Bacon
Click to expand...
Click to collapse
True
timmaaa said:
Go into fastboot mode and issue this command:
Code:
fastboot oem device-info
Post the results.
Click to expand...
Click to collapse
I am not the original poster, but I seem to have the same problem—no root after flashing the SuperSU zip file. Here is the result of the above command:
Code:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.000s]
finished. total time: 0.000s
Thanks everyone for the help...
i´ve been reading a lot since this post... and, still wraping my head in Android rooting.
But i managed to fix the problema... I needed to install the TWRP.
So... in this particular case after entering fastboot i´ve installed TWRP (with OPO toolkit in Boot a recovery>Boot!>TWRP) and proceeded to root after that.
hgmichna said:
I am not the original poster, but I seem to have the same problem—no root after flashing the SuperSU zip file. Here is the result of the above command:
Code:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
So what exactly is your problem? Your bootloader is unlocked, so just flash TWRP and then flash SuperSU.
Transmitted via Bacon
timmaaa said:
So what exactly is your problem? Your bootloader is unlocked, so just flash TWRP and then flash SuperSU.
Click to expand...
Click to collapse
Had done that at least five times without success, but eventually, after finding a slightly newer version, it worked. Problem solved.
Simple process don't use toolkits
For any newbs reading this, your Oneplus is simple to unlock, add custom recovery and root. Please do not use tool kits follow the simple steps to do it manually. You will be better off in the long run.
jk8260 said:
For any newbs reading this, your Oneplus is simple to unlock, add custom recovery and root. Please do not use tool kits follow the simple steps to do it manually. You will be better off in the long run.
Click to expand...
Click to collapse
What he said. http://forum.xda-developers.com/showthread.php?t=2788632 is a great guide to use. Very easy to follow and doesn't take long.
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
LE: I should probably mention my bootloader is unlocked
n1c00_ said:
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
Click to expand...
Click to collapse
can i use with stock recovery?
thanks.
vbnoob said:
can i use with stock recovery?
thanks.
Click to expand...
Click to collapse
Hi. It's a fastboot command that you run in bootloader mode. And actually the original script runs an OEM unlock command which bypasses your stock recovery.
So it probably doesn't work with stock recovery.
I'm actually on an unlocked bootloader, added that to the OP
ta
n1c00_ said:
Hi. It's a fastboot command that you run in bootloader mode. And actually the original script runs an OEM unlock command which bypasses your stock recovery.
So it probably doesn't work with stock recovery.
I'm actually on an unlocked bootloader, added that to the OP
ta
Click to expand...
Click to collapse
My phone is unlocked bootloader with stock recovery.
Thanks.
vbnoob said:
My phone is unlocked bootloader with stock recovery.
Thanks.
Click to expand...
Click to collapse
Here's what I'd do if I were you
1. I would try it as stated in the OP at first
2. ...if that doesn't work: 'mfastboot oem unlock' (as per original script) followed by 'mfastboot boot *.img'
3. If it still doesn't work I would instal philz recovery - see http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905 - it does work, mind the ripples
...and if it still doesn't work... Oh well...
n1c00_ said:
Here's what I'd do if I were you
1. I would try it as stated in the OP at first
2. ...if that doesn't work: 'mfastboot oem unlock' (as per original script) followed by 'mfastboot boot *.img'
3. If it still doesn't work I would instal philz recovery - see http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905 - it does work, mind the ripples
...and if it still doesn't work... Oh well...
Click to expand...
Click to collapse
I am attaching the files that served to me with this I got root in Moto G 2013 5.0.2 Retail Beazil.
I have the stock recovery.
I climb into three parts that weighs 11 megs, Just extract it and put the phone mode fastboot and execute the bat file root-windows.
enjoy it
Then tell me as if I served them.
I think I screwed phone. Being a noob I didn't realise fastboot and Bootloader screens are different. I went and use chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions link
in fastboot. After error failed now it ADB doesn't detect my phone.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>
Any advise to help me? Tried hard method going to bootload still nothing either or at least I think its nothing since this is first attempt I ever tried root my phone. Everytime I plugin in fastboot or even in normal mode the pc does detect it. But it just won't show up in adb.
Decided to try again using leocuervo1983 method for fastboot it stated as fail as well but somehow I got root even though adb still no longer detect my phone.
Edit:
Just found out fastboot doesn't use adb commands or do they? I feel stupid. I Guess there are no issues then even if failed still got root. Fastboot commands works adb doesn't work.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
TAXXXXXXXX fastboot
The easiest method would be to flash the latest version of philz recovery, boot into the recovery and then just reboot from the recovery. You will be asked to disable recovery flash and then install su binaries. Just choose yes for both the options and download and super user app you like (I personally use superSU).
PS: I have tested this method and it works.
pfufle said:
The easiest method would be to flash the latest version of philz recovery, boot into the recovery and then just reboot from the recovery. You will be asked to disable recovery flash and then install su binaries. Just choose yes for both the options and download and super user app you like (I personally use superSU).
PS: I have tested this method and it works.
Click to expand...
Click to collapse
Screen flicker issue is there if i install this on stock asia retail 5.0.2 with unlocked bootloader on stock recovery?
Xicor Yagami said:
Screen flicker issue is there if i install this on stock asia retail 5.0.2 with unlocked bootloader on stock recovery?
Click to expand...
Click to collapse
Yes since the recovery isn't entirely compatible with the new kernel.
pfufle said:
Yes since the recovery isn't entirely compatible with the new kernel.
Click to expand...
Click to collapse
Tried latest TWRP? same results?
Xicor Yagami said:
Tried latest TWRP? same results?
Click to expand...
Click to collapse
yep.
n1c00_ said:
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
LE: I should probably mention my bootloader is unlocked
Click to expand...
Click to collapse
Thanks a lot! Worked like a charm using mfastboot command.
Works fine
My bootloader was however unlocked...I tried this on CM12....extract the img file from the CF-Auto root File and then flash on the bootloader mode...with mfastboot boot filename.img
The method same as that of kitkat works for lollipop too...you could made some mistake unknowingly somewhere in the middle while following the original procedure
Sent from my Moto G using XDA Free mobile app
is there any method to root moto g?
Any side effects of chainfire method?
leocuervo1983 said:
I am attaching the files that served to me with this I got root in Moto G 2013 5.0.2 Retail Beazil.
I have the stock recovery.
I climb into three parts that weighs 11 megs, Just extract it and put the phone mode fastboot and execute the bat file root-windows.
enjoy it
Then tell me as if I served them.
Click to expand...
Click to collapse
It did'n work for me .... I ran the bat file , and when I pressed a key, it was waiting for the phone and nothing happened.
Edited:
Sorry... I forgot to unlock bootloader first.... worked fine!!! Thanks a lot!!!
I hope you guys can help me, i have been wandering around blogs forums to find a fix to this issue but to no avail. I got my replacement tablet about a few month ago. I decide to keep the old one and install custom rom on it. The old one is still usable now, but the replacement tablet is dead to me. One day i restart the repl tablet and it just stucked at the fastboot menu. When i choose to go into recovery mode. Nothing happened except a blink of message said that cold linux booting failed. So i try to unlock bootloader to flash it using adb command. Now it wont let me unlock boot loader giving me an error same as the guy here ( i cant paste an outside link here, google : Shield Tablet (LTE) won't boot beyond fastboot, fastboot OEM)
Ps : sorry for bad english im from Malaysia and also im tech newbie
flash the official firmware, you shouldn't need the the bootloader unlocked to flash a signed nvidia package.
this should replace your recovery and system and get you up and running again.
if not, perhaps your NAND is corrupted or damaged.
DreadApex said:
flash the official firmware, you shouldn't need the the bootloader unlocked to flash a signed nvidia package.
this should replace your recovery and system and get you up and running again.
if not, perhaps your NAND is corrupted or damaged.
Click to expand...
Click to collapse
I have downloaded the firmware 3.1.1 2.3gb, but it still required me to unlock bootloader to use this command
Fastboot flash recovery recovery. Img
Fastboot flash boot boot. img
Fastboot flash system. Img
........
Would appreciate if you guys can guide me in this matter
RaybenBB said:
I have downloaded the firmware 3.1.1 2.3gb, but it still required me to unlock bootloader to use this command
Fastboot flash recovery recovery. Img
Fastboot flash boot boot. img
Fastboot flash system. Img
........
Would appreciate if you guys can guide me in this matter
Click to expand...
Click to collapse
Hi,
The "fastboot oem unlock" command don't work?
Elpatii said:
Hi,
The "fastboot oem unlock" command don't work?
Click to expand...
Click to collapse
Nope, also cant detect device using adb devices command. Tried same command in the other shield tablet, work just fine. Its not driver problem.
Tried fastboot oem unlock, and somehow it ask me on the shield to unlock or not, choose unlock and this error occured
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 3.736s
Maybe that you can flash the stock image from NVIDIA (https://developer.nvidia.com/shield-open-source)
Elpatii said:
Maybe that you can flash the stock image from NVIDIA
Trying to flash that one, still it require me to unlock bootloader. I think my chipset was damaged or fried. Have escalate this issue to nvdia, and it seems they want to do a replacement
Click to expand...
Click to collapse
RaybenBB said:
Maybe that you can flash the stock image from NVIDIA
Trying to flash that one, still it require me to unlock bootloader. I think my chipset was damaged or fried. Have escalate this issue to nvdia, and it seems they want to do a replacement
Click to expand...
Click to collapse
I think that's the best solution for now!
Hello everyone. Today I'm presenting you the first development for the LG K10 (MTK chipset). As you can see on announcement text this is beta stage yet so be careful and make you sure what are you doing on your device.
Note: This version can't be written over the stock recovery partition as this has further sizes than stock. Only can be used by downloading via fastboot. Check out installation instructions.
Disclaimer:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What’s new in 3.0.0.0:
TWRP 3.0.0-0 is out now for all currently supported devices.
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
BUG LIST
Can't mount /data partition w/o wiping data because of encryption
Battery percentage doesn't show the correct value.
CPU Temp percentage doesn't show the correct value.
No more(?)
Installation Instruction
Warning: After applying these steps, you might lose your data and your device will have been installed some unofficial stuff. So, it'll give you some warnings during boot up. To skip this warning, just wait till device boots up. To remove this warning, you need to flash whole stock partitions (check this thread to do). As I said above, I'm not responsible for anything. You've been warned twice.
Install right usb drivers for your device. You can find them on official LG website.
Go to "Settings->About phone->Software information and click continiously on build number 7-8 times. You'll see a tost with message "You've enabled developer options."
Go back and go into Developer options, and check "Enable OEM unlock" and "Enable Android Debugging"
Download ADB, fastboot and drivers. Run and install/accept everything. When you're done, copy/cut and paste the image file to root directory of adb folder. (Must be like this http://i.hizliresim.com/jnga7r.png)
Connect your phone with your PC, run command promt and type following commands;
adb reboot bootloader
fastboot oem unlock
-Check your device after this command and follow the instructions on your device. Apply the steps to unlock the bootloader. (This will erase all data)
fastboot boot twrp3_k430-berkantkz.img
And after all these steps, you must see TWRP screen on your device. It will ask you for the password. Don't worry, just click on cancel and voila! TWRP is done for your device. You can edit your system or flash anything with it. But it's not possible to make modifications on data partition unless you wipe it. You need to wipe data partition to remove password/encryption.
DOWNLOAD
http://www.mediafire.com/download/udc4l2avvxwjtj6/twrp3_k430-berkantkz.img
For K430DSY:
For K430DSY by @123xdagsm Removed because can't be used with the new firmware
By @Singular777
for K430DS Not suggested anymore.
3.1.0.0 for K430DS Not suggested anymore
3.1.1.1 for K430DS
For K430AR:
By @Bohemio1987
TWRP 3.1.1.1 for K430AR
Recovery that I ported: http://www.needrom.com/download/twrp-3-0-0-recovery-for-mt6735-intex-aqua-ace/
Note: Rooting Marshmallow is not same like older versions of Android. I'll try to root my Marshmallow w/o any errors like boot verification error and I'll share a guide to how-to in upcoming days. Already managed by @gottlasz. Refer to: https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
Note2: Please hit on thanks button guys That makes me happy
Thanks to:
rameshurfrnd1 at needrom.com for his recovery
XDA:DevDB Information
TeamWinRecoveryProject 3.0.0.0 for LG K10 K430xx MTK VARIANT, Tool/Utility for the LG K10
Contributors
berkantkz
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2016-06-23
Created 2016-06-23
Last Updated 2018-08-22
Reserve for changelog
Hızlı resim hmmm
After reset - stock recovery?
Singular777 said:
After reset - stock recovery?
Click to expand...
Click to collapse
What are you asking for?
-------
EDIT: I've flashed over the stock but not able to boot into recovery mode. A warning appears and boots up normally. I'll try to fix.
EDIT2: I've ported a rom. I'll take a risk and flash it. Wish me luck
EDIT3: It's bricked
EDIT4: Successfully unbricked by following my guide. Wish me luck to be luckier in other attempts
berkantkz said:
What are you asking for?
-------
EDIT: I've flashed over the stock but not able to boot into recovery mode. A warning appears and boots up normally. I'll try to fix.
EDIT2: I've ported a rom. I'll take a risk and flash it. Wish me luck
EDIT3: It's bricked
EDIT4: Successfully unbricked by following my guide. Wish me luck to be luckier in other attempts
Click to expand...
Click to collapse
Good luck to you! =)
I mean after the restart TWRP flies?
Singular777 said:
Good luck to you! =)
I mean after the restart TWRP flies?
Click to expand...
Click to collapse
Thanks.
You'll need to do same steps over again.
+1 Thanks for that Disclaimer[emoji14]
And is it "fastboot flash boot recovery.img" or "fastboot boot recovery.img"?
Because you wrote "fastboot boot recovery.img"
Sent from my SM-G350 using XDA-Developers mobile app
TimSchumi said:
+1 Thanks for that Disclaimer[emoji14]
And is it "fastboot flash boot recovery.img" or "fastboot boot recovery.img"?
Because you wrote "fastboot boot recovery.img"
Click to expand...
Click to collapse
I did true. When we type this, TWRP boots up immediately.
berkantkz said:
I did true. When we type this, TWRP boots up immediately.
Click to expand...
Click to collapse
You have idea for root?)
Singular777 said:
You have idea for root?)
Click to expand...
Click to collapse
Yes, I've but scaried to try. I'd prefer try to porting roms rather than rooting the stock.
hello I would root for this k10 model ( gl- k430dsf ) ?
berkantkz said:
Reserve for changelog
Click to expand...
Click to collapse
hello I would root for this k10 model ( gl- k430dsf ) ?
---------- Post added at 01:57 PM ---------- Previous post was at 01:53 PM ----------
hello I would root for this k10 model ( gl- k430dsf ) ?
paivaduarte said:
hello I would root for this k10 model ( gl- k430dsf ) ?
---------- Post added at 01:57 PM ---------- Previous post was at 01:53 PM ----------
hello I would root for this k10 model ( gl- k430dsf ) ?
Click to expand...
Click to collapse
This thread is not for rooting. If you're asking for does this work on K430DSF, must work. It has alos MTK chipset, as far as I know.
About rooting, I couldn't find a right method to root this devices. Actually, I don't need to root my device. Root isn't needed to port new roms. Root can provide you only customizing stock rom. So I'll try to port new roms.
tuturial
berkantkz said:
This thread is not for rooting. If you're asking for does this work on K430DSF, must work. It has alos MTK chipset, as far as I know.
About rooting, I couldn't find a right method to root this devices. Actually, I don't need to root my device. No need to port new roms. Root can provide you only customizing stock rom. So I'll try to port new roms.
Click to expand...
Click to collapse
would have a tuturial as estrous native Andrid ?
already have one available rom for k10 ?
CyanogenMod already have ?
root still no avail?
I tried the systemless root method still no avail..every startup there's a message that says about corrupted but my phone still works well..when would rooting available for this phone?..i love this phone but without root it cant achieve its real potential..thanks for the twrp sir..hopeyl you'll find a way to root this phone
problem
this is what happend...
C:\adb>fastboot boot twrp3_k430-berkantkz.img
downloading 'boot.img'...
OKAY [ 0.549s]
booting...
FAILED (remote: oem unlock is false)
finished. total time: 0.556s
needles to say twrp didnt start after this...
have a solution?
yotam-m said:
this is what happend...
C:\adb>fastboot boot twrp3_k430-berkantkz.img
downloading 'boot.img'...
OKAY [ 0.549s]
booting...
FAILED (remote: oem unlock is false)
finished. total time: 0.556s
needles to say twrp didnt start after this...
have a solution?
Click to expand...
Click to collapse
I've forgotten that say type fastboot oem unlock,
sorry for that. Check up (guide) again.
berkantkz said:
I've forgotten that say type fastboot oem unlock,
sorry for that. Check op (guide) again.
Click to expand...
Click to collapse
OK.
now when i write fastboot oem unlock it says '<waitiong for device>' and nothing happens on my device..
'adb reboot bootloader' goes first? or after oem unlock
thanks
yotam-m said:
OK.
now when i write fastboot oem unlock it says '<waitiong for device>' and nothing happens on my device..
'adb reboot bootloader' goes first? or after oem unlock
thanks
Click to expand...
Click to collapse
God damn it. Check it again. Sorry.
yotam-m said:
OK.
now when i write fastboot oem unlock it says '<waitiong for device>' and nothing happens on my device..
'adb reboot bootloader' goes first? or after oem unlock
thanks
Click to expand...
Click to collapse
1. adb reboot bootloader 2. fastboot oem unlock, but this wipe data!
cmd run as Administrator. OR: On device- Menu-Settings-General-Developer options (if don't have then: about phone-common-software info-tap about 10 time on build number)-enable OEM unlock.
P.S. sorry for my bad english)