Tried twrp, but always says I don't have busybox and says loading, but never does, then on install recov, it DL's, but then comes up with an error: Flashing recovery was unsuccessful.
Gives partition as: /dev/block/bootdevice/by-name/recovery
No such partition on LG Leon LTE (h345, flashed from MPCS to T-Mob h345d, only way to get a working root)
Anyone else having this issue?
SOLVED: had to set "OEM Unlock" to enabled in Developer Options..., DUH!!!
This is off-topic, but as you wrote you've flashed a kdz from other variant: is it safe to try flashing different kdz'd just to try? I have a lot of possibilities, but i have only flashed the one from my country and exact same model and v10a. But it's impossible to root. Thanks!
leandeganis said:
This is off-topic, but as you wrote you've flashed a kdz from other variant: is it safe to try flashing different kdz'd just to try? I have a lot of possibilities, but i have only flashed the one from my country and exact same model and v10a. But it's impossible to root. Thanks!
Click to expand...
Click to collapse
I had to downgrade to an h345d kdz variant in order to get a working root. That worked, but it was a MPCS phone (on Tmo network) flashed to a Tmo kdz. Worked. I'd think if you Sbrick it, you could still re-flash with stock from recov., so not that big a deal.
It's not the only way to get root, I rooted my 10e:
http://forum.xda-developers.com/android/help/android-forums-account-rehost-file-t3211801
zowpow said:
It's not the only way to get root, I rooted my 10e:
http://forum.xda-developers.com/android/help/android-forums-account-rehost-file-t3211801
Click to expand...
Click to collapse
Ive tried that also and didnt work. No root method worked on my rom for h340ar
zowpow said:
It's not the only way to get root, I rooted my 10e:
http://forum.xda-developers.com/android/help/android-forums-account-rehost-file-t3211801
Click to expand...
Click to collapse
I can confirm it works with tmobile lg leon h34510f.
To Tomj2
Can you explain how you got twrp on it? Thanks in advance:good:
Edit: figured it out downloaded the img then used flashify to flash the image. Thanks anyways
http://androidforums.com/threads/twrp-2-8-7-0-ms345-twrp-for-lg-leon-metropcs.922379/
I can confirm this works, I have it on my T-Mobile variant.
bzzybfrm313 said:
I can confirm it works with tmobile lg leon h34510f.
To Tomj2
Can you explain how you got twrp on it? Thanks in advance:good:
Edit: figured it out downloaded the img then used flashify to flash the image. Thanks anyways
Click to expand...
Click to collapse
Yeah, that's how I got it on (the latest "blue" TWRP) to be able to load CM12.1
Working twrp recovery 2.8.7.0 on ms34510f rooted using king root installed twrp with twrp manager and then in terminal emulater command reboot oem-unlock oh and check oem-unlock in developer options but cant seem to install cm12
jmarpel said:
Working twrp recovery 2.8.7.0 on ms34510f rooted using king root installed twrp with twrp manager and then in terminal emulater command reboot oem-unlock oh and check oem-unlock in developer options but cant seem to install cm12
Click to expand...
Click to collapse
Are you using the correct twrp? We've got a basic yellow guy which won't flash cm12 and then we've got a blue guy which does.
Why did you use kingroot though? There are better methods for attaining root on your phone.
ninjasinabag said:
Are you using the correct twrp? We've got a basic yellow guy which won't flash cm12 and then we've got a blue guy which does.
Why did you use kingroot though? There are better methods for attaining root on your phone.
Click to expand...
Click to collapse
I didn't have a working pc and King root worked I tried many others and still it's the only one that works. I think I have the yellow one how do I get the blue?
Rooting LG Leon H34510e
I'm a newbie when it comes to rooting however I successfully rooted my H34510e using KingRoot. I verified root and BusyBox installation using Root Checker Basic. I installed TWRP but found that my device was not supported so, I uninstalled TWRO and installed CWM Rom Manager and that's where I'm at today. I'm looking for a custom rom but am not sure CWM is the right manager for my phone.
leandeganis said:
Ive tried that also and didnt work. No root method worked on my rom for h340ar
Click to expand...
Click to collapse
Take your phone, open your internet browser and go to http://www.kingroot.net/
Download the app, open it, follow the steps and you're root!
I have the same phone H340AR v10a ROM, from Uruguay.
Try that, it worked for me.
About TWRP I tried c50 version of TWRP Team, but it doesn't work.. You install the image and when reboot it shows the android robot opened up and nothing comes up.. I installed the TWRP using the "dd if=/dev/ bla bla bla" command..
Some help it wouldn't be bad.
Thanks!
Can't find OEM unlock
I already activated developer options, but..... CANT FIND IT!
Related
Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.
Danokan said:
Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.
Click to expand...
Click to collapse
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232
Amro90 said:
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232
Click to expand...
Click to collapse
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.
Danokan said:
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.
Click to expand...
Click to collapse
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.
Amro90 said:
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.
Click to expand...
Click to collapse
YIKES.
Well.. it got the TWRP recovery loaded alright.
But it won't boot into anything else...light is flashing but screen is black.
HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP
Danokan said:
HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP
Click to expand...
Click to collapse
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.
Hartendief said:
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.
Click to expand...
Click to collapse
How do you propose I flash it?
SOLVED
FIXED
http://forum.xda-developers.com/showthread.php?t=2448960
So I have converted my Note for to developer and have an unlocked bootloader and installed TWRP through Odin. I have tried a few times to gain root by installing SuperSU through TWRP, but it just manages to keep looping my phone after it installs. Is there a way to install SuperSU without doing it through TWRP as I think that's the problem?
Also I wouldn't be able to install a ROM until I gain root correct?
Thank you for all of your help
adriel161 said:
So I have converted my Note for to developer and have an unlocked bootloader and installed TWRP through Odin. I have tried a few times to gain root by installing SuperSU through TWRP, but it just manages to keep looping my phone after it installs. Is there a way to install SuperSU without doing it through TWRP as I think that's the problem?
Also I wouldn't be able to install a ROM until I gain root correct?
Thank you for all of your help
Click to expand...
Click to collapse
install a prerooted rom of your choice through twrp recocery.. they will come pre rooted..
if not i have a feeling youre not using the correct supersu zip to root the device..
have you flashed cf auto root?
Sent from my SM-G925V using XDA-Developers mobile app
Flash a prerooted rom or flash the Emotion-TW-5.1.1-nightly-r21 kernal + BETA-SuperSU-v2.71-20160331103524
elliwigy said:
install a prerooted rom of your choice through twrp recocery.. they will come pre rooted..
if not i have a feeling youre not using the correct supersu zip to root the device..
have you flashed cf auto root?
Sent from my SM-G925V using XDA-Developers mobile app
Click to expand...
Click to collapse
So yea.I don't mean to hijack this thread or anything, but I'm having thebsane issue. I've converted to Dev edition, installed TWRP, and am currently running CM 13. However, whenever I try to use an app that requires root, it says that I don't have root.
I've tried flashing the latest Super SU in recovery, downloading Super SU from the play store, and I've tried flashing the Emotion kernel (when i try to flash that, my screen goes black and I'm returned to my recovery home)
What pre rooted ROMs are out?
And are my issues rooting because I flashed a 6.0,1 ROM before getting permanent root?
refusedchaos said:
Flash a prerooted rom or flash the Emotion-TW-5.1.1-nightly-r21 kernal + BETA-SuperSU-v2.71-20160331103524
Click to expand...
Click to collapse
Cool, thanks got it to work!
Now my only issue is that once I was rooted and everything I wanted to flash CM13.
I shut down my phone and went into TWRP, I restored and the tried to install CM13+Gapps and it just went into a black screen and started over. I rebooted, but now I'm in a boot loop.
So I am going to start over and regain root, but do you know if I did something incorrectly? How would I go about it? Thank you.
shusuke028 said:
So yea.I don't mean to hijack this thread or anything, but I'm having thebsane issue. I've converted to Dev edition, installed TWRP, and am currently running CM 13. However, whenever I try to use an app that requires root, it says that I don't have root.
I've tried flashing the latest Super SU in recovery, downloading Super SU from the play store, and I've tried flashing the Emotion kernel (when i try to flash that, my screen goes black and I'm returned to my recovery home)
What pre rooted ROMs are out?
And are my issues rooting because I flashed a 6.0,1 ROM before getting permanent root?
Click to expand...
Click to collapse
Settings-/developer options/ enable root
Sent from my SM-N920F using XDA-Developers mobile app
adriel161 said:
Cool, thanks got it to work!
Now my only issue is that once I was rooted and everything I wanted to flash CM13.
I shut down my phone and went into TWRP, I restored and the tried to install CM13+Gapps and it just went into a black screen and started over. I rebooted, but now I'm in a boot loop.
So I am going to start over and regain root, but do you know if I did something incorrectly? How would I go about it? Thank you.
Click to expand...
Click to collapse
Hmm im not sure (i'm running stock + Emotion kernel). But if you want to go CM13, you dont need to flash the Emotion kernel.
EDIT: you did a full factory reset (via recovery) before you flashed CM13 right?
refusedchaos said:
Hmm im not sure (i'm running stock + Emotion kernel). But if you want to go CM13, you dont need to flash the Emotion kernel.
EDIT: you did a full factory reset (via recovery) before you flashed CM13 right?
Click to expand...
Click to collapse
Yes I did, but I had the Emotion Kernal installed. That's probably why, I'm going to attempt right now to flash SuperSu then CM13.
[/COLOR]
shusuke028 said:
So yea.I don't mean to hijack this thread or anything, but I'm having thebsane issue. I've converted to Dev edition, installed TWRP, and am currently running CM 13. However, whenever I try to use an app that requires root, it says that I don't have root.
I've tried flashing the latest Super SU in recovery, downloading Super SU from the play store, and I've tried flashing the Emotion kernel (when i try to flash that, my screen goes black and I'm returned to my recovery home)
What pre rooted ROMs are out?
And are my issues rooting because I flashed a 6.0,1 ROM before getting permanent root?
Click to expand...
Click to collapse
Cm13 is pre-rooted, root is embedded in the rom, superSu isn't needed, you can turn it on in developer settings.
adriel161 said:
Yes I did, but I had the Emotion Kernal installed. That's probably why, I'm going to attempt right now to flash SuperSu then CM13.
Click to expand...
Click to collapse
Yea, try with stock kernal. I don't think you need to flash SS when flashing CM13 though
For me, when I try to flash CM13 through TWRP it'll get to saying "MTP Enabled" in the terminal window, then black screens for a few seconds, and reboots to TWRP. It also doesn't flash CM13, and I'm at a loss for what to do
Orange Offizier said:
For me, when I try to flash CM13 through TWRP it'll get to saying "MTP" in the terminal window, then black screens for a few seconds, and reboots to TWRP. It also doesn't flash CM13, and I'm at a loss for what to do
Click to expand...
Click to collapse
Which version of TWRP do you have? And did you make sure it was a vzw build?
Reminon said:
Which version of TWRP do you have? And did you make sure it was a vzw build?
Click to expand...
Click to collapse
I have TWRP 3.0.2, and it is a vzw build
Has anybody managed to get Android Pay working yet on our device with custom rom?
Tried the new SuHide by Chainfire but still get the unable to verify device is Android compatible message
TheATHEiST said:
Has anybody managed to get Android Pay working yet on our device with custom rom?
Tried the new SuHide by Chainfire but still get the unable to verify device is Android compatible message
Click to expand...
Click to collapse
requirements :
- SuperSU installed in systemless mode
So does not work on our device
xander33 said:
requirements :
- SuperSU installed in systemless mode
So does not work on our device
Click to expand...
Click to collapse
Can you clarify why not with our device?
When you install supersu it lists in output that it's being installed as systemless?
TheATHEiST said:
Can you clarify why not with our device?
When you install supersu it lists in output that it's being installed as systemless?
Click to expand...
Click to collapse
As i know the method for root our phone is system mode, the systemless zip not work
Here the procedure that i followed for rooting my phone and is system mode
What you need:
Unlocked bootloader (see chapter 2).
TWRP installed (see chapter 7).
1.Zip .
2.Zip .
How:
Put 1.zip and 2.zip into your sd card/internal storage.
Boot into TWRP.
Ignore the message from TWRP.
Choose the "install" button.
Locate 1.zip (if on sd card go "up a level" and then "external sdcard" there you should find it).
Install it.
Reboot your phone.
Boot into TWRP again.
Locate 2.zip .
Install it.
Reboot
That's just the initial bootloader unlock and root method.
I used same method but later flashed custom rom witch also comes rooted. I have also unrooted and then rerooted systemless mode with SuperSU zip.
TheATHEiST said:
That's just the initial bootloader unlock and root method.
I used same method but later flashed custom rom witch also comes rooted. I have also unrooted and then rerooted systemless mode with SuperSU zip.
Click to expand...
Click to collapse
You need to use Magisk.
It works for me.
Have a look here...
http://pecholite.blogspot.co.ke/2016/08/magisk-la-interfaz-systemless.html?m=1
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Greetings
Sent from my ALE-L21 using XDA-Developers mobile app
Fedroid said:
You need to use Magisk.
It works for me.
Have a look here...
http://pecholite.blogspot.co.ke/2016/08/magisk-la-interfaz-systemless.html?m=1
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Greetings
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Doesn't seem to work for me. Just keep getting the unable to verify device message in Android Pay app.
TheATHEiST said:
Doesn't seem to work for me. Just keep getting the unable to verify device message in Android Pay app.
Click to expand...
Click to collapse
3 months since your last contact....
Things have changed a lot and android pay is working hard for avoid us pay with rooted phones.
Nowadays magisk is on v9 version and facing v10.
Want a clue?
If your mobile is compatible with multirom go this way. One rom rooted and modified as you want and another stock for doing payments.
Luck!
Tried everything flashing every supersu via twrp and just gets stuck at the moto logo. Tried systemless root and did the same thing. So thinking it was my kernel and flashed elementalx moto kernel ( frankenclark ) then tried to flash supersu once again with the same fail and noticed with that kernel I lost my wifi connection but ran it anyways but failed. After much forum browsing and that supersu just isn't for the MXPE I even went as far as kingroot to achieve root then slap supersu to keep root like I did with my kindle fire. I'm pretty lost for words here. I'm previously running resurection remix and works flawless but I do really like the original setup. Ps tried the stock rooted roms and they was a lil off and kept trying to ota update but failed because my bootloader is unlocked so I had to uninstall it. Just looking to root the original rom so I can keep all the moto apps. Looking forward to hearing the ideas. Thanks in advance.
Wow... So I assume you flashed back to pure stock?
Rooting is not difficult, there is only 2 ways to do it, either flash SuperSU 2.62-3 beta or the latest stable version with the "echo" command for systemless installations. Look at this thread (note the pictures in the OP are of my XT1575, I fudged a little) but the method is identical. If it doesn't work, no offense, but your not doing something right.
I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.
fastjohnson said:
I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.
Click to expand...
Click to collapse
It sounds like the install script for SuperSU is not doing a systemless install...
So you are flashing stock, booting at least once (this is required), the open TWRP and allow changes to system (In mounts make sure Mount System Read-Only is NOT checked), go to Advanced - Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" and press enter, then go to Install and select the SuperSU zip file and install it. It should clearly say it is doing a system-less install, patching boot image, etc. as shown in the first post of the link I shared a couple posts previous.
OK I tried this info word for word and tried multiple times and its still gets stuck on the moto logo, I don't get it.
I don't know... it's a puzzler.
2.62-3 and stop using toolkits.
lafester said:
2.62-3 and stop using toolkits.
Click to expand...
Click to collapse
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.
fastjohnson said:
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.
Click to expand...
Click to collapse
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.
fastjohnson said:
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.
Click to expand...
Click to collapse
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.
acejavelin said:
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.
Click to expand...
Click to collapse
No actually I didn't see it, lol probably would have helped made me not look dumb. Buy who am I kidding you guys love flexing you rooting muscles..
Deleted.
EDIT: First of all, thanks for the responses. Second of all, I messed up. I ran a script that I found online called root.sh (I can't link anything until I get to 10 posts). I used that and it didn't work and unrooted me. I tried rebooting my phone(worst idea every) and now it's in a bootloop. I don't think I have root access and I've tried a factory reset. I didn't get any custom recovery and my phone is stuck in a bootloop. I have no idea how to get out of this. Any help is 100% appreciated.
I'm sorry if this is the wrong section but, I couldn't find a section for the M919V. So I recently rooted my Galaxy S4 SGH-M919V running lollipop 5.0.1 using the PC version of Kingoroot. I've been looking for a way to replace Kingo Superuser with SuperSu. I can only seem to find anything about replacing Kinguser/Kingroot (not Kingo Superuser). I would keep Kingo Superuser but, after a reboot it doesn't allow any apps to use root access even though it says it is. I have to keep uninstalling and reinstalling Kingo Superuser and waiting then it finally fixes by it's self (currently it's broken) . SuperSu-Me says I don't have Kingroot (once again, not Kingoroot). I've also tried a script but, once again, it didn't work. I know next to nothing about the inner workings of android phones so please keep any answers simple please.
Flash custom recovery.
Flash SuperSU.
Can't get any simpler.
The sgh-m919v is basically the same phone as the T-mobile S4. The sgh-m919v was issued by Canadian varriers that run an AWS network: https://www.sammobile.com/firmwares/database/SGH-M919V/
The t-mobile s4 forum is here: http://forum.xda-developers.com/galaxy-s4-tmobile
Here's what I would do: flash a stock ROM via Odin to bring the phone back to a stock state and then root using cfautoroot if you want stock recovery or flash TWRP and flash supersu from TWRP.
First of all, thanks for the responses. Second of all, I messed up. I ran a script that I found online called root.sh (I can't link anything until I get to 10 posts). I used that and it didn't work and unrooted me. I tried rebooting my phone(worst idea every) and now it's in a bootloop. I don't think I have root access and I've tried a factory reset. I didn't get any custom recovery and my phone is stuck in a bootloop. I have no idea how to get out of this. Any help is 100% appreciated.
Flash the stock ROM.
Pwnycorn said:
Flash the stock ROM.
Click to expand...
Click to collapse
Could you link me to a good tutorial to do this?
Pwnycorn said:
Flash the stock ROM.
Click to expand...
Click to collapse
Hey man, I got the flash to work. Thank you so much!
ben3759 said:
Hey man, I got the flash to work. Thank you so much!
Click to expand...
Click to collapse
Now, if you still want SuperSU, flash CF-Auto-Root.