Hi, I am trying to install the lineage-14.1-20170125-nightly, but I get the following error:
This package supports bootloaders: MSM8226C00B322_Boot; This device has bootloader MSM8226C00B128_Boot. The updated process ended with Error 7. Error installing zip file '/sdcard/lineage-14.1-20170125-nightly-mt2-signed.zip'.
I am not sure if I have the correct bootloader.
c:\adb>fastboot oem get-bootinfo
.
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.016s]
finished. total time: 0.016s[/SIZE]
I have tried to follow the link below, but some of the direct links to the files are not working:
https://forum.xda-developers.com/as...iew-cyanogenmod-mate-2-mt2l03-t3181518/page52
Could anyone help me out with this thanks.
You have to install TWRP, once installed reboot into TWRP, Wipe then install Lineage OS, su(arm) addon, then open Gapps.
Here is a video on how to install TWRP: https://www.youtube.com/watch?v=sjA4F_TzzwQ
You can find the newest TWRP for the MT2 here (its near the bottom of the page, do not download the version of Lineage OS on that page ONLY TWRP): https://android.cmphys.com/lineageos-mt2/
Then download Open Gapps (click on ARM>7.1> then choose which variant, i use PICO, but other variants have more Google Apps): http://opengapps.org/
Download an official Nightly of Lineage: https://download.lineageos.org/mt2
Download "su (arm)" addon for Root access in Lineage, Flash this a long with Lineage: https://download.lineageos.org/extras
here is another useful video of SuperBass installing a different rom on the MT2 to kind of give you an idea on what to do: https://youtu.be/Tq27VfRYKYQ
Good luck!
Thank you for the quick reply.
NightCrayon said:
You have to install TWRP, once installed reboot into TWRP, Wipe then install Lineage OS, su(arm) addon, then open Gapps.
Here is a video on how to install TWRP: https://www.youtube.com/watch?v=sjA4F_TzzwQ
You can find the newest TWRP for the MT2 here (its near the bottom of the page, do not download the version of Lineage OS on that page ONLY TWRP): https://android.cmphys.com/lineageos-mt2/
Then download Open Gapps (click on ARM>7.1> then choose which variant, i use PICO, but other variants have more Google Apps): http://opengapps.org/
Download an official Nightly of Lineage: https://download.lineageos.org/mt2
Download "su (arm)" addon for Root access in Lineage, Flash this a long with Lineage: https://download.lineageos.org/extras
here is another useful video of SuperBass installing a different rom on the MT2 to kind of give you an idea on what to do: https://youtu.be/Tq27VfRYKYQ
Good luck!
Click to expand...
Click to collapse
Hi, I have followed all the above instructions, but i am still getting the same error. Since there is no OS installed, I have performed the following steps:
1 . Downloaded the twrp-3.0.M6-0-mt2.img and renamed it to TWRP.
2 . Rebooted the phone into bootloader mode and flashed the phone with the twrp-3.0.M6-0-mt2.img (twrp).
3. Rebooted the phone into recovery mode.
4. Wiped the phone to factory settings and also wiped the /system, data, cache, except internal storage.
5. Used the adb push command to transfer the rom, extra (su arm), and gapps to the external memory.
6. Upon flashing the rom I get the error below:
This package supports bootloaders: MSM8226C00B322_Boot; This device has bootloader MSM8226C00B128_Boot. The updated process ended with Error 7. Error installing zip file '/sdcard/lineage-14.1-20170125-nightly-mt2-signed.zip'.
Please let me know if I am missing anything. Thanks again
It is a wind Mobile phone that i am trying to flash it to linage 14.1. I don't have stock rom installed because I wiped /system accidentally.. As stated in my first post that I tried to check the bootloader version, but all I get is the following result below:
-----------------------------------------------------------------------------------
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
-----------------------------------------------------------------------------------
I don't know whether ' 001.001.000' means it is an old bootloader or latest. I would also like to mention that I was able to flash the phone to cm13.1 nightly, but the wifi was not working and security under settings was crashing.
I tried to update the bootloader 322 from the link below with B321_stock p19 recovery.zip under B321 folder:
https://drive.google.com/drive/fold...9VZ0ExZmhWS2VSUnNieUc4QTRRUVVZM2dLOHlRTnhNVDg
When I try to flash the phone with B321recovery.img it gives me an error FAILED (remote: size too large). See the result below:
c:\adb>fastboot flash recovery c:\adb\B321recovery.img
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.074s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.087s
Please any help appreciated.
techswy said:
It is a wind Mobile phone that i am trying to flash it to linage 14.1. I don't have stock rom installed because I wiped /system accidentally.. As stated in my first post that I tried to check the bootloader version, but all I get is the following result below:
-----------------------------------------------------------------------------------
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
-----------------------------------------------------------------------------------
I don't know whether ' 001.001.000' means it is an old bootloader or latest. I would also like to mention that I was able to flash the phone to cm13.1 nightly, but the wifi was not working and security under settings was crashing.
I tried to update the bootloader 322 from the link below with B321_stock p19 recovery.zip under B321 folder:
https://drive.google.com/drive/fold...9VZ0ExZmhWS2VSUnNieUc4QTRRUVVZM2dLOHlRTnhNVDg
When I try to flash the phone with B321recovery.img it gives me an error FAILED (remote: size too large). See the result below:
c:\adb>fastboot flash recovery c:\adb\B321recovery.img
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.074s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.087s
Please any help appreciated.
Click to expand...
Click to collapse
The wind Mobile variant of the MT2 has a little bit of a different process for updating the bootloader, follow this guide to install the last official B322 update, then you will have no problems with installing lineage as your bootloader will be up to date.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
Let me know if you have anymore issues. Good luck!
NightCrayon said:
The wind Mobile variant of the MT2 has a little bit of a different process for updating the bootloader, follow this guide to install the last official B322 update, then you will have no problems with installing lineage as your bootloader will be up to date.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
Let me know if you have anymore issues. Good luck!
Click to expand...
Click to collapse
Thank you so much for the link. I will definitely let you know if I run into more issues with the upgrade. Thanks again.
Yes, the newer custom ROMs require you to have flashed B322 (Huawei's final Lollipop ROM) first before flashing the custom ROMs. They have these warnings in the posts.
In the future, if you want to switch from one custom ROM to another, like from Lineage to CM, you won't need to flash B322 again as you would have already done this.
ScoobSTi said:
Yes, the newer custom ROMs require you to have flashed B322 (Huawei's final Lollipop ROM) first before flashing the custom ROMs. They have these warnings in the posts.
In the future, if you want to switch from one custom ROM to another, like from Lineage to CM, you won't need to flash B322 again as you would have already done this.
Click to expand...
Click to collapse
Thanks for the reply. I really appreciate the response. :good:
Thank you xda forum, NightCrayon and ScoobSTi for helping me fix my phone. Thanks again.
You must be from Wind Mobile from Canada
techswy said:
Hi, I am trying to install the lineage-14.1-20170125-nightly, but I get the following error:
This package supports bootloaders: MSM8226C00B322_Boot; This device has bootloader MSM8226C00B128_Boot. The updated process ended with Error 7. Error installing zip file '/sdcard/lineage-14.1-20170125-nightly-mt2-signed.zip'.
I am not sure if I have the correct bootloader.
c:\adb>fastboot oem get-bootinfo
.
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.016s]
finished. total time: 0.016s[/SIZE]
I have tried to follow the link below, but some of the direct links to the files are not working:
https://forum.xda-developers.com/as...iew-cyanogenmod-mate-2-mt2l03-t3181518/page52
Could anyone help me out with this thanks.
Click to expand...
Click to collapse
You must from Canada. You have to change your device from MSM8226C00B128 to MSM8226C00B322. Flow the link blow. This link will guide you to change to B322 and upgrade to Android 5.1.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
vivek76 said:
You must from Canada. You have to change your device from MSM8226C00B128 to MSM8226C00B322. Flow the link blow. This link will guide you to change to B322 and upgrade to Android 5.1.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
Click to expand...
Click to collapse
Hi, I'm having the same issue and I am using firmware B322 Lollipop 5.1. So I think something else is afoot. I'm going to try and update to Marshmallow cm13 first. But, I have to assemble cm13 myself, unless someone can get me a copy I would surely appreciate it.
sevenday4 said:
Hi, I'm having the same issue and I am using firmware B322 Lollipop 5.1. So I think something else is afoot. I'm going to try and update to Marshmallow cm13 first. But, I have to assemble cm13 myself, unless someone can get me a copy I would surely appreciate it.
Click to expand...
Click to collapse
Candy is so much better have you tried that yet?
https://www.androidfilehost.com/?w=files&flid=151179
I was finally able to install Lineage lineage-14.1 awhile back. I figured out where to get the Rom and modify it in order to flash it on my mtl02. But, it's been acting kinda kinky so for grins I'm going to try Candy that divhandyman suggested. ?
divhandyman said:
Candy is so much better have you tried that yet?
https://www.androidfilehost.com/?w=files&flid=151179
Click to expand...
Click to collapse
I have just flashed Candy ? about two weeks ago. Had some issues with substratum and magisk. I guess it was because you need a certain version of TWRP. Then a few days ago I with the LOD (loop of death). Lineage had the same issue
Related
I followed the directions from this post, but every time I try to install the upgrade, it fails because the partition size is not large enough. I had to flash recovery_MT2L03_mmcblk0p19.img because when I tried to use B321 it also gives me an error that says "failed: remote size too large".
How can I fix this? Thank you!
Also, food for thought, when I look at available internal storage within the stock ROM, it says only ~6gb are free out of 8, and I know this phone is a 16gb device. I don't know if that's related, but it's rather odd.
Are you following the B322 Huawei upgrade instructions PDF? What does it say the firmware version needs to be initially? Are you paying attention to that ?
divineBliss said:
Are you following the B322 Huawei upgrade instructions PDF? What does it say the firmware version needs to be initially? Are you paying attention to that ?
Click to expand...
Click to collapse
Yes I've also read those instructions. I successfully got to this screen once, and at about 25% completion, it said the process failed.
Right now I have no installed OS because it fails for all of them, just FYI.
Update: This is the error message I see on cmd...
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.082s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.093s
Is your HAM2 a Consumer Cellular by chance? Have you tried starting over by putting B148 recovery and firmware on the phone? That's what I would do.
divineBliss said:
Is your HAM2 a Consumer Cellular by chance? Have you tried starting over by putting B148 recovery and firmware on the phone? That's what I would do.
Click to expand...
Click to collapse
Completely unlocked L03, brand new. I've tried installing the old OS from the JB downgrade pack, still fails.
You did not answer my questions ....... and what version ROM/recovery is on the phone now?
divineBliss said:
You did not answer my questions ....... and what version ROM/recovery is on the phone now?
Click to expand...
Click to collapse
I figured that was a proper response to both questions... Apologies. It is not CC, and yes I have done both of those things. There is no installed ROM or OS. Recovery is variable, I've tried stock and TWRP 2.8.7.
1. What model # is this phone?
2. What versions of ROMs, recoveries have you had on it?
3. Is the bootloader unlocked? You're going to need in unlocked to put custom ROMs on it.
4. I would try getting it back to stock B148 ROM and recovery if its a non-CC MT2L03. You might have to hunt around the HAM2 forum for threads on how to recover from bricked phones if you're having problems getting to stock B148 or some other stock version that B322 instructions say can be a starting point to upgrade to B322.
divineBliss said:
1. What model # is this phone?
2. What versions of ROMs, recoveries have you had on it?
3. Is the bootloader unlocked? You're going to need in unlocked to put custom ROMs on it.
4. I would try getting it back to stock B148 ROM and recovery if its a non-CC MT2L03. You might have to hunt around the HAM2 forum for threads on how to recover from bricked phones if you're having problems getting to stock B148 or some other stock version that B322 instructions say can be a starting point to upgrade to B322.
Click to expand...
Click to collapse
1. Model is MT2-L03...
2. I have not had any ROMs, just the stock JB out of the box. Stock recovery and TWRP 2.8.7
3. Bootloader is fully and properly unlocked.
4. I said already, I cannot flash ANY ROM, stock or otherwise, because every time it tells me the partition is not large enough...
Again, this is the error message I see on cmd...
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.082s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.093s
Correction: I was able to flash the stock recovery and then the stock B148 ROM. So the only problem I have now is the system partition is only ~1gb in size, not large enough to accommodate for the ~1.6gb for the B322 or B321 update. I'm trying again now tho.
Tried to flash B321, same error. This is what I see.
Just tagging some people more knowledgeable than I who can probably help. @xordos @SHM
ScoobSTi said:
Just tagging some people more knowledgeable than I who can probably help. @xordos @SHM
Click to expand...
Click to collapse
Any and all help is appreciated, thank you! Btw, the storage size issue has self-remedied since I reflashed the B148. It now says 12.5gb free of 16gb. Apparently the ROM they shipped me with had some issues...
Also: I have tried the repair and resize functions from TWRP 2.8.7 on my system partition to no avail. It remains ~1gb.
Why are you trying to install B321 vs B322?
Go back to B148 (ROM + recovery), then try using the Huawei provided instructions to install, B322 and post what happens.
I went from B148 out of box to B322 to custom recovery / custom ROMs.
divineBliss said:
Why are you trying to install B321 vs B322?
Go back to B148 (ROM + recovery), then try using the Huawei provided instructions to install, B322 and post what happens.
I went from B148 out of box to B322 to custom recovery / custom ROMs.
Click to expand...
Click to collapse
Because that's what Nigel's directions say. Both the B321/B322 recovery and ROM fail independently. So regardless which one I try, I still have the partition problem.
chill8888 said:
1. Model is MT2-L03...
2. I have not had any ROMs, just the stock JB out of the box. Stock recovery and TWRP 2.8.7
3. Bootloader is fully and properly unlocked.
4. I said already, I cannot flash ANY ROM, stock or otherwise, because every time it tells me the partition is not large enough...
Again, this is the error message I see on cmd...
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.082s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.093s
Click to expand...
Click to collapse
format internal Sd and try again.
Moody66 said:
format internal Sd and try again.
Click to expand...
Click to collapse
Reformatted to ext4, partition size is still the same. See attached photo.
Tried to do an update from within the B148 ROM update app, same error as the first image I uploaded.
chill8888 said:
Reformatted to ext4, partition size is still the same. See attached photo.
Tried to do an update from within the B148 ROM update app, same error as the first image I uploaded.
Click to expand...
Click to collapse
Try to do the 309 update first. That should clear up the partitions for L to update.
Moody66 said:
Try to do the 309 update first. That should clear up the partitions for L to update.
Click to expand...
Click to collapse
I may need some help tracking that down. I got the MT2L03_B309_withRoot_Orig.zip from Nigel's Gdrive, but it contains the system and boot.img files, not the update.app file...
DISCLAIMER: This is NOT my work. This files I've downloaded from a different site and flashed them to my device with success. I will not take any responsibility for anything wrong happen to your device. Do it at your own risk. Also, I will not update this thread. I just want to share this information.
After searching for hours I found on a site in Taiwan the way to root the ZenFone 3 Ultra on latest update of Android 7.0 (WW_14.1010.1703.42)
Here are the steps I did:
1. Unlock Bootloader with the original program from Asus website.
2. Flash TWRP 3.1.1 recovery with fastboot.
3. Reboot in to Recovery and installed SuperSU-v2.80-201705171619.zip
4. Wipe cache and reboot.
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Both files are in the link below.
Files:
https://drive.google.com/open?id=0B69uFcMh3Eb6QTFSYXF1TzZxX00
Thank you for your share. I am on my 2nd ZF3U and will look to keep this UNROOTED and BOOTLOADER LOCKED until a decent custom rom becomes available but looks like the developer community does not want to touch this device which is really sad as in my opinipn it is the best large screen phablet currently available,?
AWFRONT said:
Thank you for your share. I am on my 2nd ZF3U and will look to keep this UNROOTED and BOOTLOADER LOCKED until a decent custom rom becomes available but looks like the developer community does not want to touch this device which is really sad as in my opinipn it is the best large screen phablet currently available,?
Click to expand...
Click to collapse
I was going to do the same but I got tired of the ads and bloatware, so I needed root to install AdAway and Titanium Backup to clean the preinstalled programs
Any reason for the v2.80 vs the 2.79? I was rooted before with 2.79 and didn't have any issues that I saw.
doctahjeph said:
Any reason for the v2.80 vs the 2.79? I was rooted before with 2.79 and didn't have any issues that I saw.
Click to expand...
Click to collapse
That is what they recommend on the other site. I do not know why.
once you've done this, does it block OTA updates from Asus?
speculatrix said:
once you've done this, does it block OTA updates from Asus?
Click to expand...
Click to collapse
I think so.
speculatrix said:
once you've done this, does it block OTA updates from Asus?
Click to expand...
Click to collapse
Once you unlock the bootloader the OTAs are blocked, even if you aren't rooted. It is okay you can still manually install the firmware easily.
mushufasas said:
[
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Click to expand...
Click to collapse
I updated it & still have root
I have rooted again on latest firmware and used Supersu 2.79. Works as advertised so far.
Gone Looking
mushufasas said:
DISCLAIMER: This is NOT my work. This files I've downloaded from a different site and flashed them to my device with success. I will not take any responsibility for anything wrong happen to your device. Do it at your own risk. Also, I will not update this thread. I just want to share this information.
After searching for hours I found on a site in Taiwan the way to root the ZenFone 3 Ultra on latest update of Android 7.0 (WW_14.1010.1703.42)
Here are the steps I did:
1. Unlock Bootloader with the original program from Asus website.
2. Flash TWRP 3.1.1 recovery with fastboot.
3. Reboot in to Recovery and installed SuperSU-v2.80-201705171619.zip
4. Wipe cache and reboot.
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Both files are in the link below.
Files:
https://drive.google.com/open?id=0B69uFcMh3Eb6QTFSYXF1TzZxX00
Click to expand...
Click to collapse
Currently at WW_14.1010.1703.36 so off to find xxxxxx42.
This process will not work on my Ultra at rev 36.
cheers,
av8or091 said:
Currently at WW_14.1010.1703.36 so off to find xxxxxx42.
This process will not work on my Ultra at rev 36.
cheers,
Click to expand...
Click to collapse
Have now update to rev 46 and this process still defaults to Android recovery on my Ultra.
I have used your files included in the attached zip and it will not install TWRP.
Thoughts?
av8or091 said:
Have now update to rev 46 and this process still defaults to Android recovery on my Ultra.
I have used your files included in the attached zip and it will not install TWRP.
Thoughts?
Click to expand...
Click to collapse
I do not know why, but I had to reinstall the rom on my phone, used the same files for root and it worked with no problem.
I have updated to UL-ASUS_A001-WW-14.1010.1704.46 using the file from ASUS support page and used the same method to root, and it worked without a problem.
Suggested Edit
mushufasas said:
I have updated to UL-ASUS_A001-WW-14.1010.1704.46 using the file from ASUS support page and used the same method to root, and it worked without a problem.
Click to expand...
Click to collapse
As there can be more than one method in which to select 'Recovery Mode' your third line should read as follows;
3. Do not select Recovery Mode from Fastboot Menu, Reboot Phone then select Recovery Mode to install SuperSU-v2.80-201705171619.zip
C:\Users\xxxxxx\>adb reboot bootloader
C:\Users\xxxxxx\>fastboot flash recovery twrp3.1.1.img
target reported max download size of 536870912 bytes
sending 'recovery' (19986 KB)...
OKAY [ 0.772s]
writing 'recovery'...
OKAY [ 0.331s]
finished. total time: 1.109s
C:\Users\xxxxxx\>fastboot reboot
rebooting...
Works like a charm, thanks for the research making this available.
signature verification failed
hi i have 14.1010.1705.49-20170602 verison
twpr flash is ok but when i try to flash supersu
i get signature verification failed
any help please
TH
krcma.cz said:
hi i have 14.1010.1705.49-20170602 verison
twpr flash is ok but when i try to flash supersu
i get signature verification failed
any help please
TH
Click to expand...
Click to collapse
i flash downgrade fw WW-14.1010.1703.42
and flashing of supersu still not working
any idea ?
av8or091 said:
As there can be more than one method in which to select 'Recovery Mode' your third line should read as follows;
3. Do not select Recovery Mode from Fastboot Menu, Reboot Phone then select Recovery Mode to install SuperSU-v2.80-201705171619.zip
C:\Users\xxxxxx\>adb reboot bootloader
C:\Users\xxxxxx\>fastboot flash recovery twrp3.1.1.img
target reported max download size of 536870912 bytes
sending 'recovery' (19986 KB)...
OKAY [ 0.772s]
writing 'recovery'...
OKAY [ 0.331s]
finished. total time: 1.109s
C:\Users\xxxxxx\>fastboot reboot
rebooting...
Works like a charm, thanks for the research making this available.
Click to expand...
Click to collapse
seems like all went well for me . . . unlocked / twrp / superuser / even the upgraded kernel & software upgrade ........ but the system hangs on the start screen ... but upon restart - the zenphon still goes into bootloader & twrp if i want to.
I don't suppose anyone made a twrp backup of a fresh / no added programs? Even one w/ bloat removed?
anybody able to show a bit of love?
thx in advance
Bummer . . . . no one's made a twrp backup yet? That's one of the 1st things i do - just in case.
.
Is it possible to update to new version of SuperSU then 2.80 ?
I try to update SuperSU with TWRP to version 2.82-201705271822.zip but installation failed....
TWRP for the Moto E4 Plus (Qualcomm)
Based heavily on squid2's TWRP device tree for the Moto E4 (Qualcomm) - See here for more information.
Seems to work fine, but use at your own risk, std_disclaimer.h, etc.
Use fastboot to test or boot this recovery.
To test:
Code:
fastboot boot recovery.img
To flash:
Code:
fastboot flash recovery recovery.img
XDA:DevDB Information
TWRP for Moto E4 Plus Qualcomm (owens), Tool/Utility for the Moto E4 Plus
Contributors
ReimuHakurei, squid2
Source Code: https://github.com/ReimuHakurei/twrp_device_motorola_owens
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2017-10-30
Created 2017-10-30
Last Updated 2017-10-30
Has any one tried this? Does that mean it can be rooted as well? I thought the bootloader had to be unlocked which is not available with qualcomm e4 plus?
shezzy83 said:
Has any one tried this? Does that mean it can be rooted as well? I thought the bootloader had to be unlocked which is not available with qualcomm e4 plus?
Click to expand...
Click to collapse
I have a model from Sprint, and it's unlockable, just not on the official list -- I successfully unlocked mine.
Rooting is also possible -- use phh's; SuperSU doesn't seem to work: https://superuser.phh.me/superuser-r259.zip
https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en
Got Root on Qualcomm E4 plus! ( BOOST MOBILE )
Just tried this on my Boost Mobile E4 plus and it worked. I also used the the no-verify zip and Magisk 14.0 to root.
Can use this guide and just swap out the twrp.img with the recovery.img from this thread:
https://forum.xda-developers.com/moto-e4/how-to/moto-e-guide-to-rooting-t3652982
So what will it take to make this TWRP official and available on the TWRP website?
I am willing to help make it go official on their website.
shezzy83 said:
Just tried this on my Boost Mobile E4 plus and it worked. I also used the the no-verify zip and Magisk 14.0 to root.
Can use this guide and just swap out the twrp.img with the recovery.img from this thread:
https://forum.xda-developers.com/moto-e4/how-to/moto-e-guide-to-rooting-t3652982
Click to expand...
Click to collapse
I just followed this guide on my XT1775 and apart from having some minor issues unlocking (had to run fastboot flashing unlock in addition to the fastboot oem unlock) I'm now unlocked, have twrp installed and rooted.
Thanks all! Can't wait to see what comes next
do anyone know where I can get stock boost mobile firmware for this phone
You probably want the Sprint firmware: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The Retail firmware will also work: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Retail firmware has none of the Sprint bloatware. Flash with fastboot.
shezzy83 said:
Just tried this on my Boost Mobile E4 plus and it worked. I also used the the no-verify zip and Magisk 14.0 to root.
Can use this guide and just swap out the twrp.img with the recovery.img from this thread:
https://forum.xda-developers.com/moto-e4/how-to/moto-e-guide-to-rooting-t3652982
Click to expand...
Click to collapse
thinking about buying this phone at it seems to be boosts easiest rootable phone. did network access persist? and do you still have 4g access and such? or any issues in general.
Has anyone had trouble flashing this? I have the owens XT1775 16GB P3A and can test boot into twrp fine but when I try to flash it comes up with the following:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (10258 KB)...
OKAY [ 0.375s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.387s]
finished. total time: 0.762s
I know it says Image not signed or corrupt but the md5 is correct even after DLing it twice.
mdgiest231 said:
thinking about buying this phone at it seems to be boosts easiest rootable phone. did network access persist? and do you still have 4g access and such? or any issues in general.
Click to expand...
Click to collapse
No issues at this point on boost mobile after I rooted. Only issue I had was I made a backup in TWRP but had to put it on a sdcard since the phone stock doesn't have enough room to store it. The problem came with that the backup I made wasn't visible on the card when connecting to my PC unless I was in recovery mode. This may just be a TWRP issue but I don't know. Haven't tried xposed yet. Busy box wouldn't install.
ReimuHakurei said:
You probably want the Sprint firmware: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The Retail firmware will also work: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Retail firmware has none of the Sprint bloatware. Flash with fastboot.
Click to expand...
Click to collapse
I for got how to flash with fastboot can you please help me out thanks I usually use a tool kit when have to do this so I don't mess it up but now that my phone is basically a brick it don't matter
Chad The Pathfinder said:
Has anyone had trouble flashing this? I have the owens XT1775 16GB P3A and can test boot into twrp fine but when I try to flash it comes up with the following:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (10258 KB)...
OKAY [ 0.375s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.387s]
finished. total time: 0.762s
I know it says Image not signed or corrupt but the md5 is correct even after DLing it twice.
Click to expand...
Click to collapse
That message is normal -- as long as your bootloader is unlocked, it should work fine.
Has anyone here tried Xposed on this device? I am interested in gravitybox and maybe xprivacy modules.
just a heads up, unlocking the bootloader, installing TWRP, and then Magisk 14.0(14.3 beta will pass safety net) is enough to root the xt1775
ReimuHakurei said:
You probably want the Sprint firmware: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The Retail firmware will also work: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Retail firmware has none of the Sprint bloatware. Flash with fastboot.
Click to expand...
Click to collapse
Is there any good guide for flashing the stock ROM? I can't seem to find any.
Edit - I found a version of RSD Lite that works on windows 10 and flashed the Retail ROM that way. I've been out of the android world for a while so I'm refreshing myself on stuff.
Bobboman said:
just a heads up, unlocking the bootloader, installing TWRP, and then Magisk 14.0(14.3 beta will pass safety net) is enough to root the xt1775
Click to expand...
Click to collapse
Thanks for the heads up on Magisk 14.3 beta passing safetynet! I love being able to dl things like netflix from the playstore now.
soaringowl2145 said:
Has anyone here tried Xposed on this device? I am interested in gravitybox and maybe xprivacy modules.
Click to expand...
Click to collapse
I just tried and got a soft brick. Have Twrp, magisk and substratum running well. Just no busybox or xposed yet. Perhaps personal error
xhan145 said:
I just tried and got a soft brick. Have Twrp, magisk and substratum running well. Just no busybox or xposed yet. Perhaps personal error
Click to expand...
Click to collapse
How did you get substratum to run?
shezzy83 said:
How did you get substratum to run?
Click to expand...
Click to collapse
With permission I want to post like a compete guide for root, BusyBox etc so it's all in one place. I'm doing a bit of cleaning but I can either pm or make a subject and the compendium! I don't want credit just want it to be easier for us e4+ peeps
Hi, After updated my Moto Z (XT1650-03) to oreo from OTA, I unlocked the bootloader in order to root phone. But I couldn't root the phone. And it did not boot. Then I flashed stock 7.1.1 (GRIFFIN_NPL26.118-20-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) and the phone turned on. The phone does not power up after I try to install OTA updates. No reaction. Is it hardbrick ?
tekin96 said:
Hi, After updated my Moto Z (XT1650-03) to oreo from OTA, I unlocked the bootloader in order to root phone. But I couldn't root the phone. And it did not boot. Then I flashed stock 7.1.1 (GRIFFIN_NPL26.118-20-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) and the phone turned on. The phone does not power up after I try to install OTA updates. No reaction. Is it hardbrick ?
Click to expand...
Click to collapse
hi dude, mmm i have a similar problem, so i think you have a hard bricked device. My moto z doesnt power up and doesnt charge it is dead
I had a similar problem after a failed downgrade from Oreo to Nougat. My phone was bricked over a month but it works now since the factory image of Oreo is out. I had earlier had a working blankflash but due to security limits I wasn't able to flash anything that would downgrade the system (so nothing really).
The blankflash file I found in the unbrick guide a while ago. Erfanoabli posted the Blank flash file but I'm not sure on witch page but it should be the latest version you can find.
The factory image I found in Android Oreo update -chanels- thread on page 37, and should work for every device except RETCN apparently. I unpacked the zip and flashed it in fastboot after I booted up to fastboot with the blank flash file.
Worked like a charm!
It still says RETEU when I go to settings.
Now I can stop using my backup phone!
I can't post any links unfortunately since I'm not a senior member.
PS. If you want to root Oreo you have to be careful! Read the guides. Otherwise you might get a bootloop.
JohanSjogren said:
I had a similar problem after a failed downgrade from Oreo to Nougat. My phone was bricked over a month but it works now since the factory image of Oreo is out. I had earlier had a working blankflash but due to security limits I wasn't able to flash anything that would downgrade the system (so nothing really).
The blankflash file I found in the unbrick guide a while ago. Erfanoabli posted the Blank flash file but I'm not sure on witch page but it should be the latest version you can find.
The factory image I found in Android Oreo update -chanels- thread on page 37, and should work for every device except RETCN apparently. I unpacked the zip and flashed it in fastboot after I booted up to fastboot with the blank flash file.
Worked like a charm!
It still says RETEU when I go to settings.
Now I can stop using my backup phone!
I can't post any links unfortunately since I'm not a senior member.
PS. If you want to root Oreo you have to be careful! Read the guides. Otherwise you might get a bootloop.
Click to expand...
Click to collapse
Hi I have the same problem, I had Nougat 7.1.1 update to version 8.0 and make a drowngrade to 7.1, then I received an update of the security patch, it was then when it was Hard Bricked (no power up no charge) , I thinkneed a blankFash for the version of Oreo. do you think the flash did you used from the message you mention would?.
Thanks in advance
JohanSjogren said:
I had a similar problem after a failed downgrade from Oreo to Nougat. My phone was bricked over a month but it works now since the factory image of Oreo is out. I had earlier had a working blankflash but due to security limits I wasn't able to flash anything that would downgrade the system (so nothing really).
The blankflash file I found in the unbrick guide a while ago. Erfanoabli posted the Blank flash file but I'm not sure on witch page but it should be the latest version you can find.
The factory image I found in Android Oreo update -chanels- thread on page 37, and should work for every device except RETCN apparently. I unpacked the zip and flashed it in fastboot after I booted up to fastboot with the blank flash file.
Worked like a charm!
It still says RETEU when I go to settings.
Now I can stop using my backup phone!
I can't post any links unfortunately since I'm not a senior member.
PS. If you want to root Oreo you have to be careful! Read the guides. Otherwise you might get a bootloop.
Click to expand...
Click to collapse
Erfanoabli's blankflash works for me too. Can you please help me about what Im going to do ? I dont want to do someting wrong.
Edit : Now My phone powers up on Stock Oreo!! Firstly I flashed gpt.zip. After I flashed GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Thank you so much.
tekin96 said:
Erfanoabli's blankflash works for me too. Can you please help me about what Im going to do ? I dont want to do someting wrong.
Edit : Now My phone powers up on Stock Oreo!! Firstly I flashed gpt.zip. After I flashed GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Thank you so much.
Click to expand...
Click to collapse
Hi ,
Im trying to flash back to stock oreo but using the same GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml package i cannot flash the boot.img i keep receiving this message :
C:\Temp\Tools\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.107s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.834s]
finished. total time: 0.943s
any ideas ?
Scugy said:
Hi ,
Im trying to flash back to stock oreo but using the same GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml package i cannot flash the boot.img i keep receiving this message :
C:\Temp\Tools\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.107s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.834s]
finished. total time: 0.943s
any ideas ?
Click to expand...
Click to collapse
Firstly you should flash gpt.zip which is in 15 page of [GUIDE] Unbrick hard bricked Moto Z topic. After that you can flash the stock oreo.
Code:
PS E:\root\GREE> .\fastboot flash recovery twrp-recovery-v1.2.img
target reported max download size of 536870912 bytes
sending 'recovery' (48973 KB)...
OKAY [ 1.089s]
writing 'recovery'...
FAILED (remote: please install correct signature)
finished. total time: 1.114s
I get this error when trying to flash TWRP on my phone, IDK what the signature means here .. ?
The phone defends you from uploading the wrong file. Are you sure you are flashing the right file for your phone model? Did you compare the checksum after downloading the file with the checksum posted on the download page?
More info:
How to install TWRP recovery on Android smartphones
Installing TWRP on an Android device is the first step towards custom development.
www.xda-developers.com
ze7zez said:
The phone defends you from uploading the wrong file. Are you sure you are flashing the right file for your phone model? Did you compare the checksum after downloading the file with the checksum posted on the download page?
More info:
How to install TWRP recovery on Android smartphones
Installing TWRP on an Android device is the first step towards custom development.
www.xda-developers.com
Click to expand...
Click to collapse
Yes, I followed a Chinese forum that says they have flashed the same twrp img for this specific phone (GREE G0215D) but it's preventing me from flashing it on the phone is there any way around it?
Phone specs
Look first for a way to unlock the booloader based on the thread:
Install Google Play Services on Chinese Phone (Gree G0215D)
Hi there, I received a Gree G2015D Phone as a gift from a Chinese friend. (Here is a Russian Site showing the phone) It comes with a 6.0.1 based Rom but without google play services installed. There are a lot of guides how this can be done for...
forum.xda-developers.com
I can't advise anything else. Good luck.
ze7zez said:
Look first for a way to unlock the booloader based on the thread:
Install Google Play Services on Chinese Phone (Gree G0215D)
Hi there, I received a Gree G2015D Phone as a gift from a Chinese friend. (Here is a Russian Site showing the phone) It comes with a 6.0.1 based Rom but without google play services installed. There are a lot of guides how this can be done for...
forum.xda-developers.com
I can't advise anything else. Good luck.
Click to expand...
Click to collapse
Thank you for answering but I already unlocked the bootloader, do you think the error is from the twrp.img ?
Mark Wasfy said:
Thank you for answering but I already unlocked the bootloader, do you think the error is from the twrp.img ?
Click to expand...
Click to collapse
The way I understand it, the message comes from fastboot and is a response from the phone's bootloader to an attempt to upload data to the protected recovery partition.