Related
Hi everyone,
So it would appear that the current builds of CWM and TWRP for the retail XT1032 Moto G won't boot on the Google Play Edition, at least not while booting from memory.
I've tried using fastboot boot recovery.img and it simply reboots and boots into the stock ROM normally.
Since factory images aren't available, I won't attempt to do a perm flash (fastboot flash recovery recovery.img) because I don't want to overwrite stock recovery without dumping it first (for archival purposes).
So, I guess my question here is twofold.
1. Has anyone else with a Moto G GPE had luck booting CWM or TWRP?
2. If not, is someone willing to try to get a version of one or both that WILL boot?
Any insight and help would be appreciated!
Sent from my Moto G Google Play Edition using Tapatalk
Have you tried the Supervboot method? That may allow you to root without modifying the recovery.
Maybe it sounds dumb, but did you unlocked the bootloader first? maybe you just can flash the recovery safely since the GPE its Android 4.4.2, you can flash the same stock recovery from the US Retail 4.4.2... I don't see why the recovery must be updated on the GPE since it has the same Android version as the other 4.4.2 firmwares...
Beegee7730 said:
Have you tried the Supervboot method? That may allow you to root without modifying the recovery.
Click to expand...
Click to collapse
I'll check into that.
EDIT: Not going to work. It would involve changes to the boot image, which I also don't want to do. I want raw, untouched dumps of system, boot, and recovery. I get the feeling that the only way to get that right now is going to be booting CWM or TWRP from memory using "fastboot boot," but that method doesn't currently work with the currently available Moto G builds of TWRP or CWM.
joel_sinbad said:
Maybe it sounds dumb, but did you unlocked the bootloader first? maybe you just can flash the recovery safely since the GPE its Android 4.4.2, you can flash the same stock recovery from the US Retail 4.4.2... I don't see why the recovery must be updated on the GPE since it has the same Android version as the other 4.4.2 firmwares...
Click to expand...
Click to collapse
The recovery is different between each and every Android ROM. The stock recovery from the retail ROM would probably boot but you wouldn't be able to flash GPE OTAs with it. And yeah, I unlocked the bootloader before I booted it for the first time.
Sent from my Galaxy Note 3 using Tapatalk
I saw this from a post from XDA but maybe you can try it:
conect via adb shell or in terminal emulator type: cat/proc/mtd and press enter
you will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
after that you will have recovery.img on your sd card
OK so I downloaded the stock XT1032 US falcon_umts images for Android 4.4.2. I did fastboot boot recovery.img on the stock recovery from those images. It worked, so the bootloader is definitely capable of booting a recovery from memory. I think this is more an issue with the actual custom recoveries available. With that said, anyone up for trying to get this working? I'll happily be the guinea pig for any test builds.
joel_sinbad said:
I saw this from a post from XDA but maybe you can try it:
conect via adb shell or in terminal emulator type: cat/proc/mtd and press enter
you will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
after that you will have recovery.img on your sd card
Click to expand...
Click to collapse
Unfortunately, that only works if you're rooted. That's why I'm looking to boot a custom recovery from memory. I'll have root access via adb shell and be able to dump to my heart's content without overwriting the stock recovery or the stock boot image. Thanks for the suggestion, though.
Beegee7730 said:
Have you tried the Supervboot method? That may allow you to root without modifying the recovery.
Click to expand...
Click to collapse
@oldblue910 I don't think this method changes boot.img. it just boots a custom boot.img from your PC and roots phone. On next boot it boots boot.img from the phone as normal.
BTW I'm on non-GPE 4.3 stock recovery and can issue
fastboot boot recovery.img
to boot into a custom recovery.
However I believe on nexus devices the option to boot a recovery from PC was removed but you can still do it using some weird parameters on the command - maybe the same type of thing on moto g GPE when booting just a custom recovery??
See following link for the parameters on nexus 7 (which is most likely just for nexus 7 but you get the idea)
http://forum.xda-developers.com/showthread.php?t=2380675
scott_doyland said:
@oldblue910 I don't think this method changes boot.img. it just boots a custom boot.img from your PC and roots phone. On next boot it boots boot.img from the phone as normal.
BTW I'm on non-GPE 4.3 stock recovery and can issue
fastboot boot recovery.img
to boot into a custom recovery.
However I believe on nexus devices the option to boot a recovery from PC was removed but you can still do it using some weird parameters on the command - maybe the same type of thing on moto g GPE when booting just a custom recovery??
See following link for the parameters on nexus 7 (which is most likely just for nexus 7 but you get the idea)
http://forum.xda-developers.com/showthread.php?t=2380675
Click to expand...
Click to collapse
Thanks for clarifying about the boot.img. I'll look into it some more.
As for "fastboot boot", every Nexus and GPE can do it as long as the bootloader is unlocked. I've never had any issue booting recoveries from memory except on the GS4 GPE. Not to get off topic, but touch recoveries are useless if booted from memory on the GS4 GPE. That's not so much of a problem for CWM since you can navigate with the volume and power keys, but TWRP, forget it. If you perm flash, everything is fine.
EDIT: That's interesting about the Nexus 4. Apparently that was a bootloader change beginning with Android 4.3. I can confirm that more modern Nexus devices do not have this issue. Weird.
Anyway, I'm going to look into that root method some more. I'll report with success or failure.
OK, just an update. Superboot doesn't work with the Play Edition ROM. If you fastboot boot it (I tried using normal Android fastboot and the Moto fastboot that comes in the zip file), it just boots to a blank screen and hangs. No boot animation, no nothing.
Obviously there's something different somewhere between the GPE and the retail US XT1032. Not sure what it is...but yeah, right now none of the custom recovery kangs work and superboot doesn't work. The only thing I've managed to boot successfully using fastboot boot was the 4.4.2 stock recovery for the retail US XT1032.
At this point I'm going to loop @a1Pha into this thread and ask if he has any thoughts, since he created the working kangs of CWM and TWRP that people seem to be using.
oldblue910 said:
OK, just an update. Superboot doesn't work with the Play Edition ROM. If you fastboot boot it (I tried using normal Android fastboot and the Moto fastboot that comes in the zip file), it just boots to a blank screen and hangs. No boot animation, no nothing.
Obviously there's something different somewhere between the GPE and the retail US XT1032. Not sure what it is...but yeah, right now none of the custom recovery kangs work and superboot doesn't work. The only thing I've managed to boot successfully using fastboot boot was the 4.4.2 stock recovery for the retail US XT1032.
Click to expand...
Click to collapse
I just rooted my XT1032 US Retail 4.4.2 with Superboot, it booted a weird purple screen and then went black screen, but after Hard Rebooting, the phone was rooted, did you checked that?
joel_sinbad said:
I just rooted my XT1032 US Retail 4.4.2 with Superboot, it booted a weird purple screen and then went black screen, but after Hard Rebooting, the phone was rooted, did you checked that?
Click to expand...
Click to collapse
Just checked. There is no su binary in /system/xbin or /system/bin/.ext and there is no Superuser.apk file either.
Sent from my Moto G Google Play Edition using Tapatalk
oldblue910 said:
At this point I'm going to loop @a1Pha into this thread and ask if he has any thoughts, since he created the working kangs of CWM and TWRP that people seem to be using.
Click to expand...
Click to collapse
Interesting. So did I understand this correctly, that flashing a stock recovery from non-GPE Moto G does work?
Which version does your bootloader show? Which kernel version shows up in phone settings?
a1Pha said:
Interesting. So did I understand this correctly, that flashing a stock recovery from non-GPE Moto G does work?
Which version does your bootloader show? Which kernel version shows up in phone settings?
Click to expand...
Click to collapse
You understand correctly, yes. The bootloader version is 41.05 and the kernel version in settings is 3.4.0.
Sent from my Galaxy S4 Google Play Edition using Tapatalk
oldblue910 said:
You understand correctly, yes. The bootloader version is 41.05 and the kernel version in settings is 3.4.0.
Sent from my Galaxy S4 Google Play Edition using Tapatalk
Click to expand...
Click to collapse
Looks like we have to wait for GPE sources to be released to adapt the kernel to the new bootloader. They should release the sources quite soon, so said a source of @dhacker29
a1Pha said:
Looks like we have to wait for GPE sources to be released to adapt the kernel to the new bootloader. They should release the sources quite soon, so said a source of @dhacker29
Click to expand...
Click to collapse
Sounds good. Thank you very much for your help! Let's keep this thread open for continuing discussion once the sources are released. Once we have kernel source, I'll be happy to test any recovery builds on my GPE device if you need testers.
Sent from my Galaxy S4 Google Play Edition using Tapatalk
oldblue910 said:
Sounds good. Thank you very much for your help! Let's keep this thread open for continuing discussion once the sources are released. Once we have kernel source, I'll be happy to test any recovery builds on my GPE device if you need testers.
Sent from my Galaxy S4 Google Play Edition using Tapatalk
Click to expand...
Click to collapse
The GPE Moto G uses ext4 data partition vs f2fs data partition for the Retail version so it's just a matter of having the right fstab in the recovery.
Try with this build
https://mega.co.nz/#!P8BQGYKK!StnnD0z91KLFxAgxQvSMUVWGC-A-4tcqiv9sgh1yXcw
alternate link
https://drive.google.com/file/d/0BxD_8WtIEc3SZnY2al9ZM0VTOFE/edit?usp=sharing
install with flashify app from phone booted in normal mode and then go to recovery
oldblue910 said:
Hi everyone,
So it would appear that the current builds of CWM and TWRP for the retail XT1032 Moto G won't boot on the Google Play Edition, at least not while booting from memory.
I've tried using fastboot boot recovery.img and it simply reboots and boots into the stock ROM normally.
Since factory images aren't available, I won't attempt to do a perm flash (fastboot flash recovery recovery.img) because I don't want to overwrite stock recovery without dumping it first (for archival purposes).
So, I guess my question here is twofold.
1. Has anyone else with a Moto G GPE had luck booting CWM or TWRP?
2. If not, is someone willing to try to get a version of one or both that WILL boot?
Any insight and help would be appreciated!
Sent from my Moto G Google Play Edition using Tapatalk
Click to expand...
Click to collapse
If you go through a1pha's thread, you'll find a TWRP repack from me that was based on a stock 4.4 kernel. Can you try that with "fastboot boot"? (In fact, that particular release from me is ONLY compatible with fastboot boot as it's too big to fit into the recovery partition...) That particular build has a lot of flaws, but should at least let you flash SuperSU on your device so you can back up the stock recovery and kernel partitions.
My observations on Monday are that a lot of recoveries that work properly when flashed to the device fail when attempting to boot them using "fastboot boot" - even on the non-GPe variants! None of the recoveries in dhacker's CM11 thread work with "fastboot boot" and neither does any one I build from Omni sources.
Many non-Nexus devices often have weird issues where "fastboot boot" doesn't work properly. I know Omni lost at least two weeks on the Oppo N1 due to the fact that "fastboot boot" is broken on that device.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD : https://dl.twrp.me/thea/
BUGS:
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY][THEA] TWRP 3.2.3-0 Touch Recovery [OFFICIAL], ROM for the Moto G 2014 LTE
Contributors
luca020400, LuK1337
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2016-02-07
Last Updated 2018-08-07
Reserved
Reserved
Source code : motog2014devteam
Source code : CyanogenMod
ok and how can we install it?
javierutxo said:
ok and how can we install it?
Click to expand...
Click to collapse
fastboot flash recovery file.img
LuK1337 said:
fastboot flash recovery file.img
Click to expand...
Click to collapse
aja, and what about unlock bootloader and rooting? the same process than moto g 2014?
javierutxo said:
aja, and what about unlock bootloader and rooting? the same process than moto g 2014?
Click to expand...
Click to collapse
Yes
javierutxo said:
ok and how can we install it?
Click to expand...
Click to collapse
Take the steps from here http://forum.xda-developers.com/moto-g-2015/general/rooting-moto-g-2015-lte-xt1078-t3086069
Just change the twrp.mg for the one in this post.
Good Luck!
Thank you!! Its worked for me on XT1072
Hello, It worked just fine on my XT1078
Thanks!
Is it possible to make this an "official" release ?
551790 said:
Is it possible to make this an "official" release ?
Click to expand...
Click to collapse
Yes , but I'm not going to do that
luca020400 said:
Yes , but I'm not going to do that
Click to expand...
Click to collapse
Hi Luca! Can you explain shortly how you built this image? Any manual that you can point me to?
I'm asking because I'd like to build it also for peregrine...
New build up
Download
idk whats happening. i unlocked my phone and installed this recovery and when i try to enter in recovery mode it shows and android with the exclamation sign and never continues to the actual recovery. it just stays there forever and then reboots by itself. can anyone tell me what is wrong?
Maledroid said:
idk whats happening. i unlocked my phone and installed this recovery and when i try to enter in recovery mode it shows and android with the exclamation sign and never continues to the actual recovery. it just stays there forever and then reboots by itself. can anyone tell me what is wrong?
Click to expand...
Click to collapse
You haven't flashed twrp
Reboot to bootloader
By pc
fastboot flash recovery twrp-thea.img
( with admin/sudo )
Then reboot to recovery
luca020400 said:
New build up
Download
Click to expand...
Click to collapse
Hi Luca, thank you very much for your hard work on this device.
About this new release of TWRP, I'd like to know, if possible, what are the main differences with the previuos one.
cgb.spender said:
Hi Luca, thank you very much for your hard work on this device.
About this new release of TWRP, I'd like to know, if possible, what are the main differences with the previuos one.
Click to expand...
Click to collapse
TWRP fixes
The TWRP version still 2.8.6 but it's 2.8.7
My encrypted TWRP nandroid backups fail with the following error message:
E:createTarFork() process ended with ERROR=255
Click to expand...
Click to collapse
This only happens when I use encryption, and it always happens right near the end of backing up the Data partition (the System partition backup completes successfully).
N.B. The percentage of files and MB processed do not increase in-step, like with an unencrypted backup. The MB percentage increases to 90%+ far quicker than the percentage of files processed. When the percentages come in-line with each other near the end of the Data partition backup, it fails, and the above error message is given.
I was using a Titan build of TWRP to create nandroid backups on my Thea device previously, and had no issues with encrypted backups.
This is an issue, as there are sensitive security details stored in the backup, which must be encrypted with a strong password.
Internal Storage failure?
sunka1 said:
My encrypted TWRP nandroid backups fail with the following error message:
....
Click to expand...
Click to collapse
This happens to me all the time all of a sudden. I did not change anything at all, except for flashing a new CM version.
I also get a strange stat error, something with google.photo cache.
Yesterday, I have then flashed the new 2.8.6(7). from a few posts above and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
UPDATE:
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Keep it up!
If I install this rom on my phone and it will not work Can I install firmware rom with lg up, but I need dll file(from .kdz file) to replace in lg up folder. I don't want to have bricked device. (Sorry for bad english)
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP.
Click to expand...
Click to collapse
I'm glad to see there is development on K10 but why the heck would you make this when on mtk devices can't be flashed anything not even recovery because of "check function" on Qualcomm it was on aboot partition on Mediatek it's probably on lk. Please announce that before someone screw their phone for no reason.
Also if you make a rom thread make it to look like something like pvineth Lineage thread, add some info and device tree and such things with this info it could be tampered bomb inside..
Why u can't?
---------- Post added at 03:43 AM ---------- Previous post was at 03:42 AM ----------
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. Download
Click to expand...
Click to collapse
Why u can't test?
it's not working :/
i booted in TWRP then wiped data, installed LineageOS and Gapps and rebooted.
and phone booted to lg logo and showed message device is corrupt and powered off
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Click to expand...
Click to collapse
Hello,
Kindly check, confirm if this is useful and safe for other users. Please mention what are the RISKS AND REPERCUSSIONS if the flash is not successful.
It is most important
Thanks
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Click to expand...
Click to collapse
I believe that lg's security system from the 2017 febr. update prevents flashing/loading any modified boot image. So you need your stock firmware to be older than 2017 febr. to flash this OS (if i'm not mistaken it only flashes the boot, the recovery and the system partition). On the other hand you cannot modify the recovery partition at all, no matter the security patch date so before flashing this mod you need to backup your recovery partition and restore it after installing this zip - otherwise you will naturaly get shut off after the device corrupt message.
If you could build it for the k8 (k350n) i could give it a try. Please confirm that it only flashes the boot, recovery and system partition and it's not messing with lk, laf and preloader - so we can recover with lg up if anything goes wrong.
Thanks anyways!
PS. do you think its enough if i just exchange the "boot.img-kernel" file in the boot image in you're zip to mine from k8? all other necessery files looks the same (like fstab and init files). I'm also not sure if i should change the .m253. files to .mm1v. files (like ueventd.m253.rc -> ueventd.mm1v.rc and init.m253.rc -> init.mm1v.rc, etc... all files that are m253 in your boot image are mm1v in my boot image but their contents are the same). So should i exchange them or leave them untouched?
So to test it i must downgrade ROM to earlier version than 2017 feb?
a_lewicki said:
So to test it i must downgrade ROM to earlier version than 2017 feb?
Click to expand...
Click to collapse
Exactly. Also i believe that it has to be ported (not built) for each type (or some) of the k10 variants (https://forum.xda-developers.com/lg-k10/development/stock-versions-model-lg-k10-t3457319) since there might be some difference in the hardware.
Another thing is the recovery partition. The zip itself does not contain any recovery related parts. However the OS might check the recovery during boot up and it might change the recovery partition which means it will fail to boot up again. But i didn't find anything in the zip that would change the most important partitions like lk, bootloader and laf so i'm 99% sure that we can use lg up or lg brigde to recover if we get soft bricked.
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Click to expand...
Click to collapse
I can confirm that it's not hard bricking the device so the stock firmware can be easily reflashed by lg up (i tested three times). However i tried to port it to my k8 but i didn't succeed (never booted up).
So would you be so kind as building one for the k8? More specifically k8 - k350n. I believe you need the source (i guess it's LGK350N):
http://opensource.lge.com/osSch/list?types=ALL&search=k350n
and maybe device tree (if it is really the device tree):
https://forum.xda-developers.com/lg-k8/development/device-tree-device-tree-lg-k350xxx-t3549783
the firmwares you can find here: https://lg-firmwares.com/lg-k350n-firmwares/
Let me know if you need anything else and thanks in advance.
Naturally i don't expect you to make it, i understand if you don't. It would be just nice if you did and you'd probably make many k8 users happy...
gottlasz said:
I can confirm that it's not hard bricking the device so the stock firmware can be easily reflashed by lg up (i tested three times). However i tried to port it to my k8 but i didn't succeed (never booted up).
So would you be so kind as building one for the k8? More specifically k8 - k350n. I believe you need the source (i guess it's LGK350N):
http://opensource.lge.com/osSch/list?types=ALL&search=k350n
and maybe device tree (if it is really the device tree):
https://forum.xda-developers.com/lg-k8/development/device-tree-device-tree-lg-k350xxx-t3549783
the firmwares you can find here: https://lg-firmwares.com/lg-k350n-firmwares/
Let me know if you need anything else and thanks in advance.
Naturally i don't expect you to make it, i understand if you don't. It would be just nice if you did and you'd probably make many k8 users happy...
Click to expand...
Click to collapse
Hi, I'll try to collect the firmware for K8
Singular777 said:
Hi, I'll try to collect the firmware for K8
Click to expand...
Click to collapse
Thank you for your time and efforts! Let me know if i can help!
This'll not work as long as bootloader acts as if it's not unlocked even though we applied the steps to unlock it.
a_lewicki said:
it's not working :/
i booted in TWRP then wiped data, installed LineageOS and Gapps and rebooted.
and phone booted to lg logo and showed message device is corrupt and powered off
Click to expand...
Click to collapse
And it's this what'll happen.
gottlasz said:
I believe that lg's security system from the 2017 febr. update prevents flashing/loading any modified boot image. So you need your stock firmware to be older than 2017 febr. to flash this OS (if i'm not mistaken it only flashes the boot, the recovery and the system partition). On the other hand you cannot modify the recovery partition at all, no matter the security patch date so before flashing this mod you need to backup your recovery partition and restore it after installing this zip - otherwise you will naturaly get shut off after the device corrupt message.
If you could build it for the k8 (k350n) i could give it a try. Please confirm that it only flashes the boot, recovery and system partition and it's not messing with lk, laf and preloader - so we can recover with lg up if anything goes wrong.
Thanks anyways!
PS. do you think its enough if i just exchange the "boot.img-kernel" file in the boot image in you're zip to mine from k8? all other necessery files looks the same (like fstab and init files). I'm also not sure if i should change the .m253. files to .mm1v. files (like ueventd.m253.rc -> ueventd.mm1v.rc and init.m253.rc -> init.mm1v.rc, etc... all files that are m253 in your boot image are mm1v in my boot image but their contents are the same). So should i exchange them or leave them untouched?
Click to expand...
Click to collapse
@berkantkz
Hey what do you think, is it possible that mtk versions of K10/K8 are using this ?
To your "p.s." It's not enough to replace kernel image and it's files if the rom is built from source it is built for different chipset (still mediatek tho but different) so it probably won't work at all.
Professor Woland said:
@berkantkz
Hey what do you think, is it possible that mtk versions of K10/K8 are using this ?
To your "p.s." It's not enough to replace kernel image and it's files if the rom is built from source it is built for different chipset (still mediatek tho but different) so it probably won't work at all.
Click to expand...
Click to collapse
I didn't understand what you've asked for on that link. It's only a guide.
Chipset model doesn't matter. If the configurations are OK to work on our model, there will be no problem or very little which aren't major.
We need to achieve unlocked bootloader. It can be unlocked by oem unlock command but it isn't actually. We have to manage to fix this. Then everything will be fine that our devices are MTK and easy to port rom stuff.
Sent from my LG K10 using XDA Labs
berkantkz said:
I didn't understand what you've asked for on that link. It's only a guide.
Chipset model doesn't matter. If the configurations are OK to work on our model, there will be no problem or very little which aren't major.
We need to achieve unlocked bootloader. It can be unlocked by oem unlock command but it isn't actually. We have to manage to fix this. Then everything will be fine that our devices are MTK and easy to port rom stuff.
Sent from my LG K10 using XDA Labs
Click to expand...
Click to collapse
Sorry for badly explained question. The link I posted talk about "verified boot" it's used to verify system, kernel and other images, so I thought maybe our phones use this too. But errors are different a little bit here take a look on this too
Professor Woland said:
Sorry for badly explained question. The link I posted talk about "verified boot" it's used to verify system, kernel and other images, so I thought maybe our phones use this too. But errors are different a little bit here take a look on this too
Click to expand...
Click to collapse
Both links regard to the same thing.
You're right, it's used on our devices that's why we can't flash anything over the stocks.
As usual, this warn should gone after bootloader unlock but as I told before, it doesn't act like unlocked, still thinks locked so the warn doesn't go away.
Sent from my LG K10 using XDA Labs
berkantkz said:
Both links regard to the same thing.
You're right, it's used on our devices that's why we can't flash anything over the stocks.
As usual, this warn should gone after bootloader unlock but as I told before, it doesn't act like unlocked, still thinks locked so the warn doesn't go away.
Sent from my LG K10 using XDA Labs
Click to expand...
Click to collapse
It's not the same link, but it doesn't matter, however if this is same thing as on our phones this should be able to help us https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't think that bootloader stay locked but that there is some verification and if it fails device won't boot.
Professor Woland said:
It's not the same link, but it doesn't matter, however if this is same thing as on our phones this should be able to help us https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't think that bootloader stay locked but that there is some verification and if it fails device won't boot.
Click to expand...
Click to collapse
Well, actually, I didn't mention links as the same. They're different links. I meant talks about the same thing. Well, this is not matter.
That thread you linked seems useful. I'll look on it. And your p.s. seems sensible.
Sent from my LG K10 using XDA Labs
This rom is compiled from source from cm-13 tree by me. https://github.com/LineageOS/android/tree/cm-13.0
This rom is built for BLU Life One X2 Mini (L0130UU)
This rom allows adb to run as root, but mounting system rw will cause kernel panic and forced shutdown.
I don't use any root other than adb root.
This rom is my daily driver, I have used Lineageos on my phone since my first build, I have no problems with rom, however your mileage may vary.
What works
Camera
Fingerprint
SIM
Data
GPS
Audio
Video Playback
Sensors
Led
known issue
FM radio doesn't work
ideals are welcome.
below are two roms, main difference is toolchain stock toolchain verses UBERTC toolchain, you decide which you prefer.
download rom
https://www.androidfilehost.com/?fid=889964283620760376
Current Rom
Rom is built using GCC: (UBERTC-4.9.x) toolchain
Kernel is built using (UBERTC-5.4.1) toolchain
Older rom version
this version using google stock toolchain
download rom
https://androidfilehost.com/?fid=889964283620759752
device tree
https://github.com/vampirefo/android_device_blu_Life_One_X2_Mini
vendor tree
https://github.com/vampirefo/android_vendor_blu_Life_One_X2_Mini
kernel source
works great so far - what version of gapps do you use?
I installed the arm64 6.0 micro version from http://opengapps.org/ and have been getting crashes now randomly thru-out on menu's in the settings and on the first app I installed "spotify" Have you had any better luck?
cyrusharding said:
works great so far - what version of gapps do you use?
Click to expand...
Click to collapse
open_gapps-arm64-6.0-nano-20171005.zip
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
When I install the ROM with gapps I get errors in the set up process - it says "google services stopped" and then when I try to install software from playstore it gives another error and the apps wont install.
I am using the upside down TWRP 3.1, it seems when I wipe and even format there is still data on the drive - any ideas, do you think its an error because I'm not doing it from adb sideload?
cyrusharding said:
When I install the ROM with gapps I get errors in the set up process - it says "google services stopped" and then when I try to install software from playstore it gives another error and the apps wont install.
I am using the upside down TWRP 3.1, it seems when I wipe and even format there is still data on the drive - any ideas, do you think its an error because I'm not doing it from adb sideload?
Click to expand...
Click to collapse
No ideal, might be wrong TWRP.
Sent from my Life One X2 Mini using Tapatalk
vampirefo said:
No ideal, might be wrong TWRP.
Sent from my Life One X2 Mini using Tapatalk
Click to expand...
Click to collapse
What process do you use for wiping / formatting prior to install?
cyrusharding said:
What process do you use for wiping / formatting prior to install?
Click to expand...
Click to collapse
My device isn't encrypted, I use fastboot to format data, system, cache the first time, then use TWRP from then on.
I use my own version of TWRP, I am not familiar with the version you use, from reading that is an earlier version later version are better.
Sent from my Life One X2 Mini using Tapatalk
vampirefo said:
My device isn't encrypted, I use fastboot to format data, system, cache the first time, then use TWRP from then on.
I use my own version of TWRP, I am not familiar with the version you use, from reading that is an earlier version later version are better.
Sent from my Life One X2 Mini using Tapatalk
Click to expand...
Click to collapse
what adb command do you use for format? thanks for following (updated to the newest recovery that is "right side up"
Edit: I am thinking my root is not working for some reason... Unsure how to fix. I flash magisk from TWRP but it doesnt look like it takes when I run a rootchecker
Looks very promising, I will attempt to flash this tonight. I ran the ported version of lineage OS for a good 6 months before it one day started boot looping (which others have reported as well for that version) . Been running the latest Drax for the mini since then (thank goodness for backups) but am starting to miss a lot of the features from Lineage. Have you had any luck getting the FM radio app to work? If not I would be happy to take a look at it when I flash it later on.
cyrusharding said:
what adb command do you use for format? thanks for following (updated to the newest recovery that is "right side up"
Edit: I am thinking my root is not working for some reason... Unsure how to fix. I flash magisk from TWRP but it doesnt look like it takes when I run a rootchecker
Click to expand...
Click to collapse
I only use SuperSU for root, no ideal about other root method.
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
ieatgravity said:
Looks very promising, I will attempt to flash this tonight. I ran the ported version of lineage OS for a good 6 months before it one day started boot looping (which others have reported as well for that version) . Been running the latest Drax for the mini since then (thank goodness for backups) but am starting to miss a lot of the features from Lineage. Have you had any luck getting the FM radio app to work? If not I would be happy to take a look at it when I flash it later on.
Click to expand...
Click to collapse
I haven't looked at FM radio, I would say it doesn't work, On mtk devices source had to be patched for radio to work, I am using unpatched LineageOS source.
The source takes so long to download and sync, I won't patch it just for FM radio.
If you want to work on FM radio, that's up to you, just isn't important to me.
Anyway good luck.
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
vampirefo said:
I only use SuperSU for root, no ideal about other root method.
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
Click to expand...
Click to collapse
how do you do supersu for root instead of magisk?
cyrusharding said:
how do you do supersu for root instead of magisk?
Click to expand...
Click to collapse
i got it working, but had to install supersu instead of magisk from @ http://www.supersu.com/download
seems like quickcharge isnt working with my 2.0 adapter, otherwise running smoothly.
spotify install crashes and causes a boot loop....
anyway I can help with version testing of updates?
cyrusharding said:
anyway I can help with version testing of updates?
Click to expand...
Click to collapse
I ordered a different phone today, blue tank phone, water is killing my phones, plus the battery life isn't enough to last all day, I have no way to charge phone at work.
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
Thanks for building this! Just wondering if builds are actively being maintained for Life One X2 Mini.
Also wondering if there are any plans to maintain this ROM? Thanks!!
Is it possible to post a link to the kernel sources you used?
Thanks
srgrusso said:
Is it possible to post a link to the kernel sources you used?
Thanks
Click to expand...
Click to collapse
The source is from Blu ftp server, I don't currently have the source as I removed it from my computer to make room for kernel source for tank, that's my current phone.
https://forum.xda-developers.com/showthread.php?t=3716454
Sent from my Tank Xtreme Pro using Tapatalk
this is a great device but its pretty new. Will we be getting TWRP for it? Is there at least an unofficial version yet?
My understanding is it won't work on Android 10.
androiddiego said:
My understanding is it won't work on Android 10.
Click to expand...
Click to collapse
You are correct! Here is the official blog post I just found:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
This is super bogus and especially since this phone (at least mine) does not seem to have a stock recovery (I get a no command dead android). I think I am going to return this phone. Shame. It's pretty slick, but no way I am going to have one that has no viable recovery!
It sounds like they'll get there, just not quickly. If you read that link closely, this seems to apply to all phones shipped with android 10. So jumping to another phone is not necessarily a solution.
does anyone with a Moto G Stylus have a working stock recovery?
fronto said:
this is a great device but its pretty new. Will we be getting TWRP for it? Is there at least an unofficial version yet?
Click to expand...
Click to collapse
Did u unlock the bootloader
Sent from my moto g stylus using Tapatalk
When you go into recovery hit the + and - volume buttons together and it will pop up.
Yes their is recovery software. It's rescue mode.
fronto said:
You are correct! Here is the official blog post I just found:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
This is super bogus and especially since this phone (at least mine) does not seem to have a stock recovery (I get a no command dead android). I think I am going to return this phone. Shame. It's pretty slick, but no way I am going to have one that has no viable recovery!
Click to expand...
Click to collapse
https://motorola-global-portal.custhelp.com/app/mcp/service
twrp
why do you need a recovery when you can unlock the bootloader and use the factory recovery to flash what ever you want and they have a nice recovery option using the rescue and smart assistant software for pc mac or lin. i fail to see why you would want a custom recovery.
Has anyone tried flashing a system image yet, just rooted my Metro Stylus and wondering what's good to flash
DMedina559 said:
Has anyone tried flashing a system image yet, just rooted my Metro Stylus and wondering what's good to flash
Click to expand...
Click to collapse
How did you root? Are there instructions somewhere for Android 10 root?
cyrusalmighty said:
How did you root? Are there instructions somewhere for Android 10 root?
Click to expand...
Click to collapse
I unlocked my bootloader through Motorola then flashed a magisk patched boot.img through fastboot
DMedina559 said:
I unlocked my bootloader through Motorola then flashed a magisk patched boot.img through fastboot
Click to expand...
Click to collapse
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
cyrusalmighty said:
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
Click to expand...
Click to collapse
I haven't kept up with the android modding scene for years so I'm kinda out of the loop, but the general rule of thumb is to not do ota updates unless you're flashing full images with fastboot or using an OEM recovery software (Lenovo\Moto have one here)
As for the patch, I got the boot.img from the recovery software I linked above and installed magisk manager on my phone to patch the img which I then moved to my laptop to flash in fastboot
cyrusalmighty said:
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
Click to expand...
Click to collapse
Hi,
First download Rescue and Smart Assistant from Motorola website, make sure activate the developer options and usb debugging and download your phone's software with Rescue and Smart Assistant (it will find it automatically), find boot.img from inside the downloaded zip file and copy it to your phone, download Magisk Manager to your phone, and patch the boot.img with Magisk Manager, copy patched boot.img to your computer and flash it with adb.
If you have a desire to get TWRP, you should write to Telegram @mauronofrio and raise some donate to develop TWRP for this device.
Root Moto g stylus
fronto said:
does anyone with a Moto G Stylus have a working stock recovery?
Click to expand...
Click to collapse
My moto G stylus if it has an active recovery, when I buy it at 2 hours I unlock the bootloader and root with magisk, I put Xposed and BusyBox, the Xposed does not seem to work very well android 10, Aceves if and sometimes it turns off, buxybox is necessary reinstall again and again every time you turn the phone off and on, and Xposed works 60%, my Motorola G Stylus is from Metro
Luiszipatla said:
My moto G stylus if it has an active recovery, when I buy it at 2 hours I unlock the bootloader and root with magisk, I put Xposed and BusyBox, the Xposed does not seem to work very well android 10, Aceves if and sometimes it turns off, buxybox is necessary reinstall again and again every time you turn the phone off and on, and Xposed works 60%, my Motorola G Stylus is from Metro
Click to expand...
Click to collapse
Same issue, I've had the same provoking anger problem with this phone and previously a Moto e5 plus. It's rooted yet no Magisk module seems to work. This phone I can't even get lucky patcher to work. Android 10 sucks, I miss the good old days of Android 6 and 7.
Anyone else notice the modules not working at all but it's rooted?
Also to do a backup, adb backup and adb restore are your friends.
Rooted you can clone the device at least with adb commands. Slower but it's an exact copy at least.
Anyone with a rooted phone who could grab kernel logs after a fresh boot and post them here ?
vache said:
Anyone with a rooted phone who could grab kernel logs after a fresh boot and post them here ?
Click to expand...
Click to collapse
Going to flash the patched boot IMG once the firmware is done. Is there an app to catch the log or an adb command?