TWRP FOR THE LG LEON 3.0.2- r1
This is compiled from c50 TWRP source code I just changed a little line of code for it to handle proper flashing of custom roms.
https://twrp.me/devices/lgleonlte.html
Reserve
How's Everything? Bugs to report? Alot of downloads and no feedback. I am glad that you are enjoying it. Czarsup3rstar
OK!
How can I flash it on Android MM to LG Leon (H340n)?
LG Leon. Ms345 aka c50
papzi57 said:
OK!
How can I flash it on Android MM to LG Leon (H340n)?
Click to expand...
Click to collapse
This is just a modified version of the official TWRP. I don't own your model. You have to get someone with your phone and make a recovery. You can even try it.
TWRP for the LG Leon is going to be updated. So it will now flash the available Roms successfully. The commit was put in.
Twrp is now updated. It will now flash properly
Will it work for Leon 3g (H320)?
Related
Does anyone know if there is a CM 13 coming to H811 soon?
Does anyone know if it's possible to flash the CM 13 from H815 on H811?
No is not possible to flash, we need to be updated first from T-Mobile so developers can use the bootloader and the blobs to build cm13.
The only way around is for developers to hack and mod lollipop bootloader to be use in M and we are falling behind with developers at this time so I doubt it will happen until we get updated first
Sent from my LG-H811 using Tapatalk
I was thinking of flashing TWRP recovery, and then flash CM 13 (H815). I'm curios if it works. I have a H811 Unlocked, and do not use T-mobile as a SIM card.
DAXX said:
I was thinking of flashing TWRP recovery, and then flash CM 13 (H815). I'm curios if it works. I have a H811 Unlocked, and do not use T-mobile as a SIM card.
Click to expand...
Click to collapse
If you do this, you may cause permanent damage to your screen, and if it were to work, you wouldn't have any audio at all.... It is my understanding that the 815 and 811 have different audio blobs and different display drivers.
hmm ok... :/ Thanks for the info!
DAXX said:
hmm ok... :/ Thanks for the info!
Click to expand...
Click to collapse
You will Definitely Hard Bricked your device 9008 COM 3 level stuff, brah
DAXX said:
Does anyone know if there is a CM 13 coming to H811 soon?
Does anyone know if it's possible to flash the CM 13 from H815 on H811?
Click to expand...
Click to collapse
http://download.cyanogenmod.org/?device=h811
Edit : Sorry. 12.1 not 13.
Should be available soon after tmo releases mm for g4
Ok. Is there anyone that can guide me on how to get from stock 10H or 10N to CM 12.1? I'm new with LG G4 on T-Mobile.
Hello all,
I've got an XT1045 with stock 5.1 Lollipop. I know that a 6.0 Marshmallow update is promised, but I haven't gotten it yet. Does anyone have it, or links?
Had a look on google but it seems the Peregrine will not get official MM. There is the MM ported rom from the THEA (xt1072)
http://forum.xda-developers.com/moto-g/4g-development/rom-identity-crisis-6-lte-t3327995/page50
But there is official CM13 (MM) available for the Peregrine, I highly recommend it. It is what I use on my THEA.
https://download.cyanogenmod.org/?device=peregrine
Thanks for the info! I'd like to just stay stock, but if this CM ROM is pretty stable, I'll give it a go. About the only reason I want 6.0 is for that adoptable storage feature. I'm assuming that this ROM is pre rooted, and has the usual CM goodies baked in???
PS, I'm new to this device forum. What is this 'THEA' you mentioned?
Mr_IceSlice said:
Thanks for the info! I'd like to just stay stock, but if this CM ROM is pretty stable, I'll give it a go. About the only reason I want 6.0 is for that adoptable storage feature. I'm assuming that this ROM is pre rooted, and has the usual CM goodies baked in???
PS, I'm new to this device forum. What is this 'THEA' you mentioned?
Click to expand...
Click to collapse
It is definitely stable for daily use and does come with CM goodies and yes has built in root (enabled in developer settings) I find it much better than stock MM. Thea is just the device variant, yours being Peregrine and another being Titan. If you do flash CM13 make sure it is for the Peregrine version.
stonedpsycho said:
It is definitely stable for daily use and does come with CM goodies and yes has built in root (enabled in developer settings) I find it much better than stock MM. Thea is just the device variant, yours being Peregrine and another being Titan. If you do flash CM13 make sure it is for the Peregrine version.
Click to expand...
Click to collapse
Thanks for all the info!
And one last request, can you link me a bootloader unlocking tutorial? Many thanks!!!
Mr_IceSlice said:
Thanks for all the info!
And one last request, can you link me a bootloader unlocking tutorial? Many thanks!!!
Click to expand...
Click to collapse
There is a great guide in the link below, I will assume its the same unlocking technique
http://forum.xda-developers.com/moto-g-lte/general/rooting-moto-g-2015-lte-xt1078-t3086069
Here is a link for TWRP for your device.
https://twrp.me/devices/motorolamotog2013lte.html
stonedpsycho said:
There is a great guide in the link below, I will assume its the same unlocking technique
http://forum.xda-developers.com/moto-g-lte/general/rooting-moto-g-2015-lte-xt1078-t3086069
Here is a link for TWRP for your device.
https://twrp.me/devices/motorolamotog2013lte.html
Click to expand...
Click to collapse
Thanks for getting me rolling!
Moto FTW!!!
Hi everyone, so some mistakes have been made today. While playing around with substratum theme engine on my mix running lineage-os 14.1, i had uninstalled one of the themes and then decided to uninstall the app entirely, however after uninstall it didnt reset the theme, so i rebooted. While attempting to reboot it got stuck in a boot loop. At this point I plugged my phone into my pc and booted into twrp so i could access my files and get them off, however when attempting to boot into twrp i could not use the touch screen which is preventing me from re-flashing my rom. and so after troubleshooting for an hour or soi had all my files off of my device, so i decided to format the system partition. so now i have no rom flashed and a twrp that i cannot use due to lack of touchscreen, its temporarily bricked i guess. So my questions are; A. can i use an otg cable and a mouse to control twrp? B. Is there some way to directly flash a rom from adb or from the connected pc. Then I should also state that I have tried older/newer versions of twrp to try to get the touchscreen working, to no avail (currently running 3.1.1-0 lithium). Ive read that it may be touchscreen drivers or something that are mis-matched from the rom. the onlyt issue is that there is no rom, also ive heard that the touchscreen is at a kernel level so i may need to flash a new kernel to get it working. TBH im not going to do anything else so that i dont completely brick my phone. Thank you all in advance for helping out!
Please try this (older) TWRP by MrRaines: https://www.androidfilehost.com/?fid=673368273298927160
It's TWRP 3.0.2-0 based but has different kernel/driver that is more compatible with a varous bunch of ROMs.
You're a god, this is exactly what I needed, thanks!!!
raupe said:
Please try this (older) TWRP by MrRaines: https://www.androidfilehost.com/?fid=673368273298927160
It's TWRP 3.0.2-0 based but has different kernel/driver that is more compatible with a varous bunch of ROMs.
Click to expand...
Click to collapse
I LOVE you, spent hours trying to get recovery working. This was the only fix!
Thank you so much brother.
kanej2006 said:
I LOVE you, spent hours trying to get recovery working. This was the only fix!
Thank you so much brother.
Click to expand...
Click to collapse
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono
raupe said:
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono
Click to expand...
Click to collapse
Just see the kernel img, ramdisk and boot files/blobs
raupe said:
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono
Click to expand...
Click to collapse
Hmmm. I did try two or even three other versions of TWRP. The first two would not even flash giving me an error. The third worked but touch screen would not work. Final attempt was the one from MrRaines which worked perfect!
"Hey everyone,
Here are the latest open beta builds for OnePlus 3 and 3T.
Release notes
Launcher
Improved search tags in App drawer
Added "New installs" category tag in App drawer
Improved app list for hidden space and toolbox
Camera
Optimized switching between front and rear camera
Multimedia
Added capability to scrub/seek through AAC audio file timelines
Please keep in mind that this is beta software. These builds are sometimes not as stable as our official OTAs generally are. By installing this update, you accept the potential risks.
And please remember to tell us about any bugs you may find using the bug report forums, found here. https://forums.oneplus.com/feedback/
Please note:
If you have already flashed an Open Beta (you are currently running the latest Open Beta) you will receive this new build as an OTA.
If you are not running open beta software and would like to, please refer to the flashing instructions and the full ROM found on the downloads page here: http://downloads.oneplus.com/ (requires full data wipe before updating from stable to open beta)
Once you migrate to the Beta path, you will continue to receive Open Beta OTAs. You will no longer receive the regular Official Stable OTAs.
Moving back to the Official OTA path from the Beta path will require a full install and clean flash (FULL WIPE of all data and cache)
Please note that this is the last open beta for OnePlus 3 and OnePlus 3T, we will provide a stable version of OnePlus 3/3T for beta testers to migrate back to stable version of OxygenOS later this month to ensure beta testers will receive regular Android security patch update and so on.
Make sure to let us know how you feel about the beta builds here in the thread too, we are watching."
Gdrive Link for beta 34 credit to @theduke7 :
https://drive.google.com/file/d/1o8jJPsqAKhjRWJWmv9cymksghAJ7YwrA/view
https://dl.xda-developers.com/4/2/0/0/2/6/2/Screenshot_20170703-141050.png?key=jM3BUdtEIPxZKh7O00c-CQ&ts=1499071824
Ota file anyone?
No kernel source released yet?? or no kernel changes on this beta 19???
G drive link full zip beta 20
https://drive.google.com/file/d/0B9UeupRxu1D_cDRGa1FjczFXQ2M/view?usp=drivesdk
As usual you people are so quick. Thanks a lot.
And Oxygen so slow...
On OnePlus site 04.07.2017. On the zip file 27.06.2017, like ob from Hydrogen OS..
Works Fine!
I did a full wipe, clean flash. Reflash Twrp 3.1.1.38 by eng stk. On a second reboot to system, phone goes back to stock recovery.
I reflash recovery from laptop with ADB in Fastboot. All good.
mysky911 said:
No kernel source released yet?? or no kernel changes on this beta 19???
Click to expand...
Click to collapse
Haven't heard Oneplus releasing kernel source for beta builds. I've only ever heard they release for the stable branch
null0seven said:
And Oxygen so slow...
On OnePlus site 04.07.2017. On the zip file 27.06.2017, like ob from Hydrogen OS..
Click to expand...
Click to collapse
So they're supposed to release immediately without testing the builds, stop being a noob
Does bootloader needs to be unlocked to sideload update from stock recovery ?
Do I have to turn on USB debugging ?
I'm on stock 4.1.6, with locked bootloader, want to go to beta builds.
Don't shoot me for this noob question, I just own a op3 for 2 days....
Renosh said:
Haven't heard Oneplus releasing kernel source for beta builds. I've only ever heard they release for the stable branch
Click to expand...
Click to collapse
OP did released kernel source for OB18 on middle June...
https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996/commits/oneplus/QC8996_N_7.1_Beta
abhi0502 said:
G drive link full zip
https://drive.google.com/file/d/0B9UeupRxu1D_Ukl5Z0FCdlpfQ0U/view?usp=drivesdk
Click to expand...
Click to collapse
Lots of thanks man
abhi0502 said:
G drive link full zip
https://drive.google.com/file/d/0B9UeupRxu1D_Ukl5Z0FCdlpfQ0U/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks man! The official link keeps failing on me and I am currently on FreedomOS so OTA isn't an option. Hopefully this will download.
Anyone having trouble re-rooting op3 after this update? Latest supersu fails to install on twrp after I flashed this update.
genaroneto said:
Anyone having trouble re-rooting op3 after this update? Latest supersu fails to install on twrp after I flashed this update.
Click to expand...
Click to collapse
Hi,
Try magisk, it's fine
Or maybe the latest supersu 2.82 SR1?
Sent from my OnePlus3 using XDA Labs
laupuy said:
Hi,
Try magisk, it's fine
Or maybe the latest supersu 2.82 SR1?
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Thank you, it worked perfectly.
i reflashed TWRP blu spart but after one boot again reverted back to stock. any solution. OB19
Justfarooq said:
i reflashed TWRP blu spart but after one boot again reverted back to stock. any solution. OB19
Click to expand...
Click to collapse
I am not sure how your flashing steps are but what I do when flashing oxygen os is usually flashing twrp img right after flashing oxygen os, then reboot to recovery, finally reboot to system. This way i never lose TWRP.
On a second reboot to system you will loose twrp. Stock recovery takes over.
Yes, after flashing the rom i reflash twrp. This happen on H2o ob16 & Oos ob19
I reflash twrp from laptop. Reboot to recovery, NOT to system !
Hi everyone
Today I'm announcing dot os 6.0 for moto g50.
Development starts Q3 of 2022 , because I need to gather vendor and other files to begin compiling. I don't know it will be GSI based or just straight up with TWRP. I just need some time to start. Also wait for the dotos team to release it, or just get now started on Beta versions.
reserved
reserved
Hi. Do you know guys when TWRP will be ported for this phone? This custom rom will also needs TWRP. Thanks.
IulianBoss25 said:
Hi. Do you know guys when TWRP will be ported for this phone? This custom rom will also needs TWRP
Click to expand...
Click to collapse
It dosen't need to use TWRP. It will use dot os recovery for installing updates and etc. For TWRP you'll need to wait cuz i don't know how to actually port it to g50 because there isn't any vendor images in stock files and needs to be pulled from device it self.