Related
after flashing the vendor image, i flashed the latest twrp. tried to reboot but unable to go into recovery and stuck in a black screen. Phone boots as normal but lost root. Phone can still be detected by pc, but when i go into bootloader it cant be detected and i flash back stock image. Any help will be appreciated.
Not entirely sure. I would start from scratch and follow this guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928. I would jump to section 11 and go from there. I'm currently waiting for my cache to build after flashing latest stock image from google (MHC1). I followed section 9. Hopefully all goes well. I came from MMB29Q.
---------- Post added at 01:28 AM ---------- Previous post was at 01:09 AM ----------
well everything went as expected for me. That guide has never let me down. If you're using a toolkit to update I would abandon it. That guide is my bible when it comes to anything regarding modifying the 6p. I have seen multiple threads about TWRP not "sticking" or stuck at boot etc, etc. In order for you obtain root again you're going to need to flash TWRP, boot into it, and flash SU 2.68. There is a test version of TWRP 3.0 floating around that I used with no issues. I'll try to find the link and post it here. If not, maybe another user can post it if they have it handy.
Here
Thanks dude!
thx dude gonna give it a shot
So, while trying to follow the steps given to me to gain root access for data recovery, I stupidly swiped allow system modifications on the signed TWRP. The phone has been unable to boot into system ever since and only gets stuck on ZTE screen. I am able to boot into recovery, bootloader, FTM, and EDL but not system. This suggests that the system image has been corrupted somehow. I downloaded the B15 zip from ZTE's support page and tried to do update via SD card from stock recovery.
After selecting the zip file the phone screen showed the following (I tried with and without renaming the zip to update.zip):
supported api: 3
Install /sdcard/<"filename>".zip
finding update package, opening update package, verifying update package
E: footer is wrong
Update package verification took 1.0 s (result 1).
E: signature verification failed
Installation aborted
This entails that perhaps the official zip is faulty in some way. I chatted with ZTE support, he told me to wipe cache, try redownloading the zip file and retry without renaming, But no dice. Then he suggested a factory reset. I had read that for some others a factory reset had fixed the problem, so with some qualms, I went through with it. Lo and behold, even after 30 min the phone was still stuck on ZTE screen. ZTE support no longer has a B29 zip for downgrading and does not offer a B19 zip. So according to the support guy my last option is sending my phone in for repairs where they'll reformat the phone and reflash Stock ROM free of charge.
While that's all well and dandy, I am still desperately attempting data recovery (all efforts have been futile and I am well aware that I will likely be wholly unsuccessful). So, I was wondering if any of you guys had a backup of the fully stock system image, or had a zip file, or solution that would allow me to boot into system successfully without rooting or unlocking bootloader. A fully stock OS is preferred but am open to alternates such as DrakenFX's fastboot enabled EDL zip if there's absolutely no way to go back to fully stock OS. I am ok with downgrading and then updating later. Just don't want to get the phone reformatted. Thanks in advance.
TLDR: Phone stuck on ZTE screen; factory reset did not help; need to flash fully stock system image and maybe can boot successfully into system; if all else fails will probably submit warranty claim.
Install supersu or dm-verity to bypass the security checks.
tupurl said:
So, while trying to follow the steps given to me to gain root access for data recovery, I stupidly swiped allow system modifications on the signed TWRP. The phone has been unable to boot into system ever since and only gets stuck on ZTE screen. I am able to boot into recovery, bootloader, FTM, and EDL but not system. This suggests that the system image has been corrupted somehow. I downloaded the B15 zip from ZTE's support page and tried to do update via SD card from stock recovery.
After selecting the zip file the phone screen showed the following (I tried with and without renaming the zip to update.zip):
supported api: 3
Install /sdcard/<"filename>".zip
finding update package, opening update package, verifying update package
E: footer is wrong
Update package verification took 1.0 s (result 1).
E: signature verification failed
Installation aborted
This entails that perhaps the official zip is faulty in some way. I chatted with ZTE support, he told me to wipe cache, try redownloading the zip file and retry without renaming, But no dice. Then he suggested a factory reset. I had read that for some others a factory reset had fixed the problem, so with some qualms, I went through with it. Lo and behold, even after 30 min the phone was still stuck on ZTE screen. ZTE support no longer has a B29 zip for downgrading and does not offer a B19 zip. So according to the support guy my last option is sending my phone in for repairs where they'll reformat the phone and reflash Stock ROM free of charge.
While that's all well and dandy, I am still desperately attempting data recovery (all efforts have been futile and I am well aware that I will likely be wholly unsuccessful). So, I was wondering if any of you guys had a backup of the fully stock system image, or had a zip file, or solution that would allow me to boot into system successfully without rooting or unlocking bootloader. A fully stock OS is preferred but am open to alternates such as DrakenFX's fastboot enabled EDL zip if there's absolutely no way to go back to fully stock OS. I am ok with downgrading and then updating later. Just don't want to get the phone reformatted. Thanks in advance.
TLDR: Phone stuck on ZTE screen; factory reset did not help; need to flash fully stock system image and maybe can boot successfully into system; if all else fails will probably submit warranty claim.
Click to expand...
Click to collapse
I think this is B29 stock image DrakenFX has uploaded it on sharing website, give it a try.
https://www.androidfilehost.com/?fid=312968873555009511
romeoh said:
I think this is B29 stock image DrakenFX has uploaded it on sharing website, give it a try.
https://www.androidfilehost.com/?fid=312968873555009511
Click to expand...
Click to collapse
Thanks for the link!
Will this work via the update from sd card option on the stock recovery? Or would you recommend flashing from TWRP? Or via MiFlash in EDL mode?
gpz1100 said:
Install supersu or dm-verity to bypass the security checks.
Click to expand...
Click to collapse
Doesn't that require unlocked bootloader? I want to avoid voiding the warranty.
tupurl said:
Thanks for the link!
Will this work via the update from sd card option on the stock recovery? Or would you recommend flashing from TWRP? Or via MiFlash in EDL mode?
Click to expand...
Click to collapse
This is the zte official B29 package and the only way to used it from the stock recovery from the SD card. It won't work with twrp because it requires the stock recovery. You can also use this method and you don't have to have unlcked bootloader http://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514/page26
romeoh said:
This is the zte official B29 package and the only way to used it from the stock recovery from the SD card. It won't work with twrp because it requires the stock recovery. You can also use this method and you don't have to have unlcked bootloader http://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514/page26
Click to expand...
Click to collapse
So, I just now tried to apply the package you linked to (Draken FX stock Marshmallow) and it gave me the same errors :/
E: footer is wrong and E: signature verification failed. Should I try something else?
Enable OEM unlock and flash zte zip from external SD. Sometimes they zip it twice so check the file.
lafester said:
Enable OEM unlock and flash zte zip from external SD. Sometimes they zip it twice so check the file.
Click to expand...
Click to collapse
I can't boot into system. Is there a way to enable OEM unlock from recovery, EDL, or factory test mode?
Did you check the zip? You could always use miflash b15 full.
lafester said:
Did you check the zip? You could always use miflash b15 full.
Click to expand...
Click to collapse
I've been trying to use MiFlash to flash the B29 stock zip by DrakenFX that the romeroh linked to but I can't see my device in MiFlash :/. I know EDL works cuz the axon7tool is able to detect it and write or read recovery and boot properly. Ideas on how to get MiFlash to detect my phone?
tupurl said:
I've been trying to use MiFlash to flash the B29 stock zip by DrakenFX that the romeroh linked to but I can't see my device in MiFlash :/. I know EDL works cuz the axon7tool is able to detect it and write or read recovery and boot properly. Ideas on how to get MiFlash to detect my phone?
Click to expand...
Click to collapse
axon7tool uses different drivers. install the correct drivers for miflash.
tupurl said:
I've been trying to use MiFlash to flash the B29 stock zip by DrakenFX that the romeroh linked to but I can't see my device in MiFlash :/. I know EDL works cuz the axon7tool is able to detect it and write or read recovery and boot properly. Ideas on how to get MiFlash to detect my phone?
Click to expand...
Click to collapse
Ok, I think there was a little misunderstanding about the B29 link that I sent to you bro. That file can only be flashed in Stock recovery you can't flash it with MiFlash. If you want to use MiFlash the only version that's available to flash in EDL mode is Nougat B15. Just reread the OP of the the link I've sent to you before and If you didn't understand anything let us know there is always someone here will help you.
romeoh said:
Ok, I think there was a little misunderstanding about the B29 link that I sent to you bro. That file can only be flashed in Stock recovery you can't flash it with MiFlash. If you want to use MiFlash the only version that's available to flash in EDL mode is Nougat B15. Just reread the OP of the the link I've sent to you before and If you didn't understand anything let us know there is always someone here will help you.
Click to expand...
Click to collapse
I'm having sort of the same problem except I'm stuck on the bootloader unlocked screen and any rom I flash gets stuck on "patching system image unconditionally"
Fazedyrus said:
I'm having sort of the same problem except I'm stuck on the bootloader unlocked screen and any rom I flash gets stuck on "patching system image unconditionally"
Click to expand...
Click to collapse
Have you tried to use the EDL method?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
It should work on fixing this issue even if you are with Unlocked Bootloader, but you'll end up on Nougat B15 because this is the only full EDL mode package available.
romeoh said:
Have you tried to use the EDL method?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
It should work on fixing this issue even if you are with Unlocked Bootloader, but you'll end up on Nougat B15 because this is the only full EDL mode package available.
Click to expand...
Click to collapse
Did that, the flash is successful but I still have the same problem in that the system won't boot. Should I just relock and rma at this point?
---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------
romeoh said:
Have you tried to use the EDL method?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
It should work on fixing this issue even if you are with Unlocked Bootloader, but you'll end up on Nougat B15 because this is the only full EDL mode package available.
Click to expand...
Click to collapse
Flashing supersu and dmverity zip doesn't work either
Fazedyrus said:
Did that, the flash is successful but I still have the same problem in that the system won't boot. Should I just relock and rma at this point?
---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------
Flashing supersu and dmverity zip doesn't work either
Click to expand...
Click to collapse
You doing a full wipe before flashing? Flashing b15 full (no twrp)? Also try format data instead of wipe.
I've gone through this a few times and always manage to get booting.
lafester said:
You doing a full wipe before flashing? Flashing b15 full (no twrp)? Also try format data instead of wipe.
I've gone through this a few times and always manage to get booting.
Click to expand...
Click to collapse
I've done that several times already with no success. I think somehow my device just doesn't work
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
lafester said:
You doing a full wipe before flashing? Flashing b15 full (no twrp)? Also try format data instead of wipe.
I've gone through this a few times and always manage to get booting.
Click to expand...
Click to collapse
also tried flashing DrakenFX's B29 Stock images but still can't boot into system
---------- Post added at 04:21 PM ---------- Previous post was at 04:14 PM ----------
lafester said:
You doing a full wipe before flashing? Flashing b15 full (no twrp)? Also try format data instead of wipe.
I've gone through this a few times and always manage to get booting.
Click to expand...
Click to collapse
I've tried many things over the past 3 days for over 10 hours so I think I'm gonna return this phone and just get a OP3T
---------- Post added at 04:45 PM ---------- Previous post was at 04:21 PM ----------
Fazedyrus said:
I've done that several times already with no success. I think somehow my device just doesn't work
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
also tried flashing DrakenFX's B29 Stock images but still can't boot into system
---------- Post added at 04:21 PM ---------- Previous post was at 04:14 PM ----------
I've tried many things over the past 3 days for over 10 hours so I think I'm gonna return this phone and just get a OP3T
Click to expand...
Click to collapse
also, not being able to flash any rom with a working twrp makes it look like only I have this problem
---------- Post added at 05:32 PM ---------- Previous post was at 04:45 PM ----------
Fazedyrus said:
I've done that several times already with no success. I think somehow my device just doesn't work
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
also tried flashing DrakenFX's B29 Stock images but still can't boot into system
---------- Post added at 04:21 PM ---------- Previous post was at 04:14 PM ----------
I've tried many things over the past 3 days for over 10 hours so I think I'm gonna return this phone and just get a OP3T
---------- Post added at 04:45 PM ---------- Previous post was at 04:21 PM ----------
also, not being able to flash any rom with a working twrp makes it look like only I have this problem
Click to expand...
Click to collapse
yep, everything is stock yet I am still not able to boot into system
lafester said:
Enable OEM unlock and flash zte zip from external SD. Sometimes they zip it twice so check the file.
Click to expand...
Click to collapse
tupurl said:
So, while trying to follow the steps given to me to gain root access for data recovery, I stupidly swiped allow system modifications on the signed TWRP. The phone has been unable to boot into system ever since and only gets stuck on ZTE screen. I am able to boot into recovery, bootloader, FTM, and EDL but not system. This suggests that the system image has been corrupted somehow. I downloaded the B15 zip from ZTE's support page and tried to do update via SD card from stock recovery.
After selecting the zip file the phone screen showed the following (I tried with and without renaming the zip to update.zip):
supported api: 3
Install /sdcard/<"filename>".zip
finding update package, opening update package, verifying update package
E: footer is wrong
Update package verification took 1.0 s (result 1).
E: signature verification failed
Installation aborted
This entails that perhaps the official zip is faulty in some way. I chatted with ZTE support, he told me to wipe cache, try redownloading the zip file and retry without renaming, But no dice. Then he suggested a factory reset. I had read that for some others a factory reset had fixed the problem, so with some qualms, I went through with it. Lo and behold, even after 30 min the phone was still stuck on ZTE screen. ZTE support no longer has a B29 zip for downgrading and does not offer a B19 zip. So according to the support guy my last option is sending my phone in for repairs where they'll reformat the phone and reflash Stock ROM free of charge.
While that's all well and dandy, I am still desperately attempting data recovery (all efforts have been futile and I am well aware that I will likely be wholly unsuccessful). So, I was wondering if any of you guys had a backup of the fully stock system image, or had a zip file, or solution that would allow me to boot into system successfully without rooting or unlocking bootloader. A fully stock OS is preferred but am open to alternates such as DrakenFX's fastboot enabled EDL zip if there's absolutely no way to go back to fully stock OS. I am ok with downgrading and then updating later. Just don't want to get the phone reformatted. Thanks in advance.
TLDR: Phone stuck on ZTE screen; factory reset did not help; need to flash fully stock system image and maybe can boot successfully into system; if all else fails will probably submit warranty claim.
Click to expand...
Click to collapse
lafester is correct, the B15 file from downloaded from ZTE is zipped twice. There is an actual update.zip inside a folder inside the "America A2017U SD card software package(A2017UV1.1.0B15)SD_W" zip. When I bricked my phone, I extracted the update.zip and I was able to flash it from the SD with the stock recovery. Hope that helps.
Howie Dub said:
lafester is correct, the B15 file from downloaded from ZTE is zipped twice. There is an actual update.zip inside a folder inside the "America A2017U SD card software package(A2017UV1.1.0B15)SD_W" zip. When I bricked my phone, I extracted the update.zip and I was able to flash it from the SD with the stock recovery. Hope that helps.
Click to expand...
Click to collapse
where can I find this zip
Hello all,
I have flashed my p9 lite (VNS-L31C432B390) to the newest B390 firmware using official update routine and therefore flashing stock recovery via fastboot before updating. Now I wanted to reflash TWRP in order to get root back (I had done this before with B380 and B388 update, never having issues), but when I try the flash command in fastboot it says "FAILED (remote: Command not allowed)"
After some research, I found that this normally indicates a locked bootloader, but both on the screen of the phone (when in bootloader) and via fastboot (fastboot oem get-bootinfo) bootloader is shown as unlocked.
I just can't figure out what may have caused flashing not to work anymore... Anyone with similar issues after latest update?
EDIT: The solutionwas to re-unlock the bootloader (just perform "fastboot oem unlock PERSONAL UNLOCK KEY). Thanks to AndreaEl for suggesting the solution.
i have had the same problem some days ago.
Re unlock bootloader and try again
Thank you very much, I'm definetly gonna try, although I really hoped to spare me this factory reset
opal06 said:
Hello all,
I have flashed my p9 lite (VNS-L31C432B390) to the newest B390 firmware using official update routine and therefore flashing stock recovery via fastboot before updating. Now I wanted to reflash TWRP in order to get root back (I had done this before with B380 and B388 update, never having issues), but when I try the flash command in fastboot it says "FAILED (remote: Command not allowed)"
After some research, I found that this normally indicates a locked bootloader, but both on the screen of the phone (when in bootloader) and via fastboot (fastboot oem get-bootinfo) bootloader is shown as unlocked.
I just can't figure out what may have caused flashing not to work anymore... Anyone with similar issues after latest update?
Click to expand...
Click to collapse
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
opal06 said:
Thank you very much, I'm definetly gonna try, although I really hoped to spare me this factory reset
Click to expand...
Click to collapse
Have u tried using the method on this thread?
https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
Neo Markson said:
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
B160 -> B370(TWRP) -> B390(Firmare finder DNS method)
i have do like this
Click to expand...
Click to collapse
Re-unlocking the bootloader did the job for me... Afterwords I was able to flash TWRP again over fastboot... So this can be considered as solved...
As for my update method, I found the easiest way is to get official OTAs (I've got the B390 as official OTA, maybe not yet available in your region) by temporarely switch back to official recovery. As this thread shows, there may be minor problems and root will be lost after update. As always, you are performing these steps at your own risk. These are the steps:
- get an official recovery image from an official Huawei firmware (search here on the forums). Unzip it and use Huawei Extractor to extract recovery.img from update.app
- Flash it in fastboot mode (fastboot flash recovery /Path/to/recovery.img)
- Download update via Huawei's software update application
- Let it perform the OTA. This step is likely gonna fail, no problem though, just reboot.
- Software Updater will state that the update failed and start to download the full firmware package, which is way bigger (~2GB). Update with this one will work though...
- Performing the update will unroot, just flash latest TWRP and SuperSu like shown in many guides on this forum to regain it
AndreaEl said:
Neo Markson said:
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
B160 -> B370(TWRP) -> B390(Firmare finder DNS method)
i have do like this
Click to expand...
Click to collapse
Tried that, it doesn't work. And I'm at B381 by the way. See when I try to send the firmware update to the updater app and install it, nothing changes. The installation completes and after reboot, when I check from about phone I see that I'm still in B381(at least according to it )
---------- Post added at 12:39 AM ---------- Previous post was at 12:32 AM ----------
opal06 said:
Re-unlocking the bootloader did the job for me... Afterwords I was able to flash TWRP again over fastboot... So this can be considered as solved...
As for my update method, I found the easiest way is to get official OTAs (I've got the B390 as official OTA, maybe not yet available in your region) by temporarely switch back to official recovery. As this thread shows, there may be minor problems and root will be lost after update. As always, you are performing these steps at your own risk. These are the steps:
- get an official recovery image from an official Huawei firmware (search here on the forums). Unzip it and use Huawei Extractor to extract recovery.img from update.app
- Flash it in fastboot mode (fastboot flash recovery /Path/to/recovery.img)
- Download update via Huawei's software update application
- Let it perform the OTA. This step is likely gonna fail, no problem though, just reboot.
- Software Updater will state that the update failed and start to download the full firmware package, which is way bigger (~2GB). Update with this one will work though...
- Performing the update will unroot, just flash latest TWRP and SuperSu like shown in many guides on this forum to regain it
Click to expand...
Click to collapse
My boatloader is already locked and I'm not rooted.
Click to expand...
Click to collapse
Has anyone tried or found any unofficial version of linageos os that works for this model?.
I have mine rooted, twrp, xposed, but I would really like to change the stock OS. Linage would be awesome.
https://forum.mantab.me/thread/9412/custom-rom-nougat-71-lenovo-phab-2-unofficial-lineage-os.xhtml
Ifound this. But model is different, may u try search on that site
dlsega said:
Has anyone tried or found any unofficial version of linageos os that works for this model?.
I have mine rooted, twrp, xposed, but I would really like to change the stock OS. Linage would be awesome.
Click to expand...
Click to collapse
broo could u write a thread or link how u rooted it? im looking on the rusian site
i have been unsucess full 5 time gave up hope (havent retried since 4 months)
i would love to ****ing rootthis phone and have leagos thing
btw found this also http://lenovo-forums.ru/topic/21441-lenovo-phab-2-исходный-код-ядра/
source code
sushil888 said:
https://forum.mantab.me/thread/9412/custom-rom-nougat-71-lenovo-phab-2-unofficial-lineage-os.xhtml
Ifound this. But model is different, may u try search on that site
Click to expand...
Click to collapse
i tried, but avast shows the site as a security risk. I supose you found something for the pb2-650M?
reggiexp said:
broo could u write a thread or link how u rooted it? im looking on the rusian site
i have been unsucess full 5 time gave up hope (havent retried since 4 months)
i would love to ****ing rootthis phone and have leagos thing
btw found this also http://lenovo-forums.ru/topic/21441-lenovo-phab-2-исходный-код-ядра/
source code
Click to expand...
Click to collapse
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Idlsega, i m bit Confused!!
U r pointing towards 650 Y model to reggie....
Looking for 650 m model custom rom?
Which is yr model ?
And reggie... Is using which model ??
sushil888 said:
Idlsega, i m bit Confused!!
U r pointing towards 650 Y model to reggie....
Looking for 650 m model custom rom?
Which is yr model ?
And reggie... Is using which model ??
Click to expand...
Click to collapse
M and Y are same? i mean i didnt find any difference. only different country same phone
---------- Post added at 08:45 PM ---------- Previous post was at 08:37 PM ----------
dlsega said:
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Click to expand...
Click to collapse
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:52 PM ---------- Previous post was at 08:45 PM ----------
dlsega said:
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Click to expand...
Click to collapse
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:53 PM ---------- Previous post was at 08:52 PM ----------
dlsega said:
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Click to expand...
Click to collapse
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:53 PM ---------- Previous post was at 08:53 PM ----------
dlsega said:
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Click to expand...
Click to collapse
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
reggiexp said:
M and Y are same? i mean i didnt find any difference. only different country same phone
---------- Post added at 08:45 PM ---------- Previous post was at 08:37 PM ----------
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:52 PM ---------- Previous post was at 08:45 PM ----------
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:53 PM ---------- Previous post was at 08:52 PM ----------
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:53 PM ---------- Previous post was at 08:53 PM ----------
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
Click to expand...
Click to collapse
They're pretty much the same, the difference is on the LTE bands, the M has works with more I think. (besides the retail region).
I had a similiar problem, and the issue was that the bootloader wasn't being unlocked flashing the commands. It turns out that the thing keeping the bootloader from unlocking was that little OEM UNLOCK check in the DEVELOPER OPTIONS. After I checked that one, tried again, and this time it worked, I first noticed it because the phone started wiping to a factory reset automatically. After that I just put it into fastboot mode, flashed TWRP. And done.
I don't know if this is the same issue you're having. But for me it was a little frustrating trying and trying without success, until I noticed that little detail and that was it.
At the moment I have it rooted with xposed working just fine. The only issue (don't know if it's only me), is when recording a video using 3rd party apps like instagram or snapchat, the audio is garbage, like some noise cancellation going wrong.
im sure i had that ticked but i guess not. will retry once i fix my xiaomi redmi note 3 who has a memory failure (same on my mom's phone redmi note 3) both crashed 2weeks apart from each other. they boot but as soon as u download 5apps thr phone bootloops... and now im trying to get mi flash to work but its been a long time and i can't figure it out... so now using this massive phone fr 3months its a good phone but damn that quad core is slow... and apps close way to quick on back ground. anyway i will try and root again some dag and install linea os.
reggiexp said:
im sure i had that ticked but i guess not. will retry once i fix my xiaomi redmi note 3 who has a memory failure (same on my mom's phone redmi note 3) both crashed 2weeks apart from each other. they boot but as soon as u download 5apps thr phone bootloops... and now im trying to get mi flash to work but its been a long time and i can't figure it out... so now using this massive phone fr 3months its a good phone but damn that quad core is slow... and apps close way to quick on back ground. anyway i will try and root again some dag and install linea os.
Click to expand...
Click to collapse
Did you manage to get lineage to run?
Sent from my Lenovo PB2-650Y using Tapatalk
frankbonatelli said:
Did you manage to get lineage to run?
Sent from my Lenovo PB2-650Y using Tapatalk
Click to expand...
Click to collapse
didn't even try.
it's my majn phone still so not really wanna mess with it. still to lazy to flash RR on my redmi note 3
frankbonatelli said:
Did you manage to get lineage to run?
Sent from my Lenovo PB2-650Y using Tapatalk
Click to expand...
Click to collapse
still not switch phone? any one got any updates on the roms??? like this forum is dead.././
Custom rom for lenovo pb2-650m
I request the developers to provide custom rom for lenovo pb2-650m.
subal kumar mahato01 said:
I request the developers to provide custom rom for lenovo pb2-650m.
Click to expand...
Click to collapse
it are the same phones anyway i just cant figur out the unlock and twrp flash
subal kumar mahato01 said:
I request the developers to provide custom rom for lenovo pb2-650m.
Click to expand...
Click to collapse
Were you able to find any custom rom for lenovo pb2-650m?
Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.
Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)
Wolamute said:
Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.
What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
fastboot flashing unlock
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
So I went through and fastboot flashed all those files from your link to Motorola support.
It wouldn't let me relock the bootloader with fastboot oem lock
it did lock with fastboot flashing lock
I was able to reboot, now of course with a verification error boot msg
Connected to wifi and it auto-prompted the Nougat ota update.
Just completed the Nougat install currently on build NPJ25.93-14
Maybe you just need to reflash those files from the Motorola site, and connect to wifi for the 700+MB download?
there's another security update to NPJ25.93-14-4 available after you get back to nougat. Good luck
superceege said:
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Click to expand...
Click to collapse
My xt1625 was boot-unlocked, and I was try the same twrp version you mentioned. I continued researching, and found that, despite the error msg, twrp was flashed correctly. I just needed to go to recovery directly from the bootloader screen. Thanks for your help.
superceege said:
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)
Click to expand...
Click to collapse
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.
Wolamute said:
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.
Click to expand...
Click to collapse
Hmm, what 6.0.1. build do you have (if you scroll down to the bottom of Settings>About Phone, there should be an entry for Build Number)? I recall that for US devices you need to be on MPJ24.139-48/49 or MPJ24.139-64 to be eligible for the OTA update to Nougat. Any other different firmware build may not give you an update as the build's not recognised by the update server for your region/software channel.
However, as you flashed the MM firmware onto your device when you previously had Nougat, I would advise against taking the OTA update route. Depending on what version of Nougat you had before you tried to root, you may hard brick your device if you try to flash the OTA, since flashing MM firmware may not downgrade your bootloader, as such you'd be flashing an old OTA onto a newer Nougat bootloader, which is a really bad idea. If you can remember what stock firmware you had (or at least what security patch it was), we can try to locate the correct firmware for you to flash and safely get you back onto the update path.
As for the recovery, that sounds like the stock recovery you have on your device, which if you re-flashed the stock ROM, will replace TWRP. You may have to re-flash TWRP.
On a related note, on Marshmallow, you do not need to flash a custom kernel - you could flash TWRP and your choice of root manager. On stock Nougat (on the G4/Plus devices), you must flash a custom kernel, else you will likely bootloop as you experienced. Here's a rooting guide for G4/Plus Nougat devices: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
---------- Post added at 04:28 AM ---------- Previous post was at 04:23 AM ----------
Baboon_Red said:
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
That error is normal, as far as I know - the TWRP image is not cryptographically signed by Motorola, so that message seems to be mainly informational and alerting you that you are flashing unsigned images in fastboot (which you are), since fastboot is mainly used to flash signed images. Once you've flashed TWRP, reboot straight to recovery to ensure the TWRP is not overwritten by the stock recovery. Afterwards, you can boot as normal.
Be careful to flash the TWRP version/architecture for what you want to do - e.g. if you wish to flash 64 bit custom ROMs, you must use a 64 bit TWRP version. Attempting to flash 64 bit custom ROMs via 32 bit TWRP may give you an error 255 otherwise.