Develop Bugs

551ml can't unlock bootloader and can't install twrp.

I'm trying flash trwp so I can back up the stock mm that I'm on and I wanted to flash the cm13 with mm blobs.
After flashing twrp and I try to go into recovery it just shows the android guy with a ! Icon above him.
I tried using Asus unlock tool apk but it fails and closes.
The for reading.

Look for the modder tool by giovix in general section , easy as pie

timbernot said:
Look for the modder tool by giovix in general section , easy as pie
Click to expand...
Click to collapse
Thx, I'll take a looksie!

timbernot said:
Look for the modder tool by giovix in general section , easy as pie
Click to expand...
Click to collapse
I just tried it and it seemed everything worked ok and flashed twrp. when i get in to bootloader and try to load into recovery it restarts and shows this https://www.google.ca/search?q=reco...hWFWh4KHW0rDPAQ_AUIBygC#imgrc=P6Av23J5FPR39M:

Hmmm, boot back to bootloader and try again ?
Mine work first time.
You did put the unzipped folder straight in C/: drive like advised? And run as admin ?

timbernot said:
Hmmm, boot back to bootloader and try again ?
Mine work first time.
You did put the unzipped folder straight in C/: drive like advised? And run as admin ?
Click to expand...
Click to collapse
Everything flashed fine the first time. I'll give it another shot.

timbernot said:
Hmmm, boot back to bootloader and try again ?
Mine work first time.
You did put the unzipped folder straight in C/: drive like advised? And run as admin ?
Click to expand...
Click to collapse
I just tried that and I get the same error. The fastboot verify shows my phone is connected.
For some reason I don't think its fully unlocking my bootloader.
It will start to flash but at the end it says failed https://gyazo.com/2025260de02c9ffa6c3a5b9f1663c5a2
I then can proceed to install the splash screen to turn it back to black and exit. When I try to boot in bootloader and goto recovery I then get https://www.google.ca/search?q=reco...hWFWh4KHW0rDPAQ_AUIBygC#imgrc=P6Av23J5FPR39M:

Not too sure what's going on here , relating to your initial problem maybe ?
Drivers installed correctly etc..
This tool just works for me..
You got "minimal adb and fastboot" installed before this tool and working fine ???
Can u power off from bootloader ...Then use hard buttons to get to recovery ?
Just a thought.
Flash stock mm recovery back first if not got and try again.

timbernot said:
Not too sure what's going on here , relating to your initial problem maybe ?
Drivers installed correctly etc..
This tool just works for me..
You got "minimal adb and fastboot" installed before this tool and working fine ???
Can u power off from bootloader ...Then use hard buttons to get to recovery ?
Just a thought.
Flash stock mm recovery back first if not got and try again.
Click to expand...
Click to collapse
Yup I can do all that, I'm on stock mm atm also.

quarterbreed said:
Yup I can do all that, I'm on stock mm atm also.
Click to expand...
Click to collapse
Good news that
Be done with it then by flashing stock recovery then sideload another fresh copy of firmware.
Then , use the modder

timbernot said:
Good news that
Be done with it then by flashing stock recovery then sideload another fresh copy of firmware.
Then , use the modder
Click to expand...
Click to collapse
I'm not sure what you mean. How do I flash stock recovery. And why would I have to reflash stock mm?

To start from fresh
Just in case you damaged any sectors flashing earlier what caused the initial problem you posted.
You need to fastboot flash stock recovery from boot loader screen . Boot into stock recovery then select 'update over adb'
Then sideload from PC which sends firmware to phone.
Then you will be back to clean factory settings.
Fastboot commands is >
fastboot flash recovery recovery.img
Putting stock recovery in adb/fastboot folder first and renaming it to 'recovery'
adb commands in stock recovery is >
adb sideload MOFD_SDUPDATE.zip
Renaming , stock ASUS firmware .134 to MOFD_SDUPDATE
and putting it in adb/ fastboot folder first.
Refresh this page later I will add some more info as I am stuck for time at the min ...
Or someone might come along and help further ?

timbernot said:
To start from fresh
Just in case you damaged any sectors flashing earlier what caused the initial problem you posted.
You need to fastboot flash stock recovery from boot loader screen . Boot into stock recovery then select 'update over adb'
Then sideload from PC which sends firmware to phone.
Then you will be back to clean factory settings.
Fastboot commands is >
fastboot flash recovery recovery.img
Putting stock recovery in adb/fastboot folder first and renaming it to 'recovery'
adb commands in stock recovery is >
adb sideload MOFD_SDUPDATE.zip
Renaming , stock ASUS firmware .134 to MOFD_SDUPDATE
and putting it in adb/ fastboot folder first.
Refresh this page later I will add some more info as I am stuck for time at the min ...
Or someone might come along and help further ?
Click to expand...
Click to collapse
Thx Ill have to give it a try when i have some time. So I cant flash twrp with the current stock MM. I should probably wait for the cm14 release to go through all that then.

Adb and fastboot knowledge is usually required when unlocking bootloader and flashing recoveries
Enjoy

timbernot said:
Adb and fastboot knowledge is usually required when unlocking bootloader and flashing recoveries
Enjoy
Click to expand...
Click to collapse
when i do fastboot flash recovery (name of twrp.img) it flashes but when I try to get in to recovery i get that command android picture :[

And ?
What about what you have already been advised ?

My 1+ 3 won´t boot recovery or system

hey guys,
i have a big problem.
i unlocked my one+ 3 2 weeks ago and installed twrp and cm13. all worked fine.
yesterday i read the news from cm the first devices will get offical cm14.
so i donwloaded the first rom and updated my phone (without a wipe!).
the cm14 starts good and all worked fine.
But, i find out, i can´t hear a phone call.
so, i want to go back to the twrp to restore my backup of cm13.
the problems begins....
i can´t boot twrp. i see the bootloader screen and after switching the screen to recovery (normaly) i got a black screen (seems like to shut off the screen).
then i tried to reinstall it, nothing.
after a full evening of trying i wiped it (factory reset) from android 7.
after the reboot i got the same problem. -> black screen after bootscreen Android won´t start, recovery won´t start.
then i downloaded a toolbox and installed the stock recovery -> no change -> black screen.
then i tried to find a stock image als *.img format to flash it with all (kernel and recovery, etc) with fastboot, but i didn´t find an image.
my last try was to make a full wipe with "fastboot -w". but this won´t work too.
so, now my phone will only boot into fastboot and thats it.
i need urgend help.
can anyone tell me what i can do? how can i install any os and wipe via fastboot and with no recovery?
thx a lot for your help.
ravn

ravn83 said:
hey guys,
i have a big problem.
i unlocked my one+ 3 2 weeks ago and installed twrp and cm13. all worked fine.
yesterday i read the news from cm the first devices will get offical cm14.
so i donwloaded the first rom and updated my phone (without a wipe!).
the cm14 starts good and all worked fine.
But, i find out, i can´t hear a phone call.
so, i want to go back to the twrp to restore my backup of cm13.
the problems begins....
i can´t boot twrp. i see the bootloader screen and after switching the screen to recovery (normaly) i got a black screen (seems like to shut off the screen).
then i tried to reinstall it, nothing.
after a full evening of trying i wiped it (factory reset) from android 7.
after the reboot i got the same problem. -> black screen after bootscreen Android won´t start, recovery won´t start.
then i downloaded a toolbox and installed the stock recovery -> no change -> black screen.
then i tried to find a stock image als *.img format to flash it with all (kernel and recovery, etc) with fastboot, but i didn´t find an image.
my last try was to make a full wipe with "fastboot -w". but this won´t work too.
so, now my phone will only boot into fastboot and thats it.
i need urgend help.
can anyone tell me what i can do? how can i install any os and wipe via fastboot and with no recovery?
thx a lot for your help.
ravn
Click to expand...
Click to collapse
Lots off people are getting this problem and trust me for some reason people post steps to fix this that are complicated for people who are just getting to playing around with TWRP.
Look, download the original TWRP recovery from here, https://dl.twrp.me/oneplus3/ the one you need is the 3.0.2-1 . I used it and I got back to MC13 From MC14.1 which by the way is now working pretty good. Once you fastboot flash recovery .this 3.0.2-1 recovery you can actually use it with MC14.1 as am doing right now. In any case. flash recovery >factory reset > adb your MC13 Zip to the phone > reboot...
Remember All Of This Steps Are Always Taken At Your Own Risk !!
Best of luck!!! [emoji6]
Sent from my ONEPLUS A3000 using Tapatalk

DiMatador said:
Lots off people are getting this problem and trust me for some reason people post steps to fix this that are complicated for people who are just getting to playing around with TWRP.
Look, download the original TWRP recovery from here, https://dl.twrp.me/oneplus3/ the one you need is the 3.0.2-1 . I used it and I got back to MC13 From MC14.1 which by the way is now working pretty good. Once you fastboot flash recovery .this 3.0.2-1 recovery you can actually use it with MC14.1 as am doing right now. In any case. flash recovery >factory reset > adb your MC13 Zip to the phone > reboot...
Remember All Of This Steps Are Always Taken At Your Own Risk !!
Best of luck!!! [emoji6]
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply.
to flash only the new recovery will not help.
tomorrow i will try to flash, wipe (with "fastboot -w" and copy the zip file.
Will the copy install the cm13 version? or do u mean sideload to have the cm13 zip for the twrp to flash?

Try to flash the modified twrp. Check the official topic for cm 14, it is linked over there
Edit: this one http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get

superiscch said:
Try to flash the modified twrp. Check the official topic for cm 14, it is linked over there
Edit: this one http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
@superiscch just provided you with the TWRP that works. This is what i did !
Flash the recovery provided on the link >boot to the new recovery, you well see the version at the top left corner as 3.0.2-1 > factory reset > adb sideload the MC 13 ....... Reboot system > than add your choice of google apps to the sdcard root > reboot to recovery > flash google apps from with recovery than reboot, you would be golden. After, if your interested just flash the TWRP from the original twrp team. Cuss the one you just installed is modified, it be your choice !!
Sent from my ONEPLUS A3000 using Tapatalk

Hey guys,
thx for your replay. i will try it after work.
but i have one question ... what do u mean exactly with " adb your MC13 Zip"?
do u mean to transfer the zip to install with twrp or is there a command to install the zip to the systempartition?

ravn83 said:
Hey guys,
thx for your replay. i will try it after work.
but i have one question ... what do u mean exactly with " adb your MC13 Zip"?
do u mean to transfer the zip to install with twrp or is there a command to install the zip to the systempartition?
Click to expand...
Click to collapse
Okay... Look, once you have flash the modified recovery and you reboot. You be able to boot to your OS. Than you have to simple options 1. Load the CM13 ZIP file to your sdcard which you can use for installing with recovery
2. Boot into recovery and side load the MC 13 ZIP file into your phone using adb...sideload would be using adb
ADB... adb sideload <name of file> without the brackets...
Good luck man
Sent from my ONEPLUS A3000 using Tapatalk

Thx a lot guys, now it works and in installed my phone successfully.
it was the wrong twrp version.
now, the weekend is save :silly:

ravn83 said:
Thx a lot guys, now it works and in installed my phone successfully.
it was the wrong twrp version.
now, the weekend is save :silly:
Click to expand...
Click to collapse
Alriiiight !!
Sent from my ONEPLUS A3000 using Tapatalk

NEED HELP

I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!

bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242

1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.

SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.

bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.

Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?

bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1

All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!

You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.

TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!

bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?

have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.

bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.

noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!

[Q]E988 Boot certification verify

I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.

hotmatua.parulian said:
I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.
Click to expand...
Click to collapse
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.

ShadySquirrel said:
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.
Click to expand...
Click to collapse
Thank you very much Shady.. Please be kindly to review steps that i should execute when flashing to Carbon Lollipop with regards to my current state (rooted 4.4.2. stock Kitkat):
Prerequisite:
- LG Flash Tool 2014 installed in PC
- LG United Mobile Driver (i use v3.11.3) installed in PC
- Stock firmware E98810e_00.kdz (Indonesia Jellybean) -- Jellybean stock base is required to cater modem/wakelock issue
- Stock firmware E98820c_00.kdz (Indonesia Kitkat)
- ROM Manager (for current state backup/restore)
- Freegee (to cater LG security issue after success flash)
- Towelroot (to root device after success flash)
- TWRP (for recovery tool after success flash)
- Downloaded ZeKrnl 1.7 Build 11/28 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975
- Downloaded ZeKrnl 1.6 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page4 (to cater camera issue after flashed to Carbon)
1. Flash CWM via ROM Manager
2 Execute Backup Current ROM to sd card via ROM Manager and save copy to PC
3. Backup manual for files, apks, contacts to sd card and save copy to PC
4. Copy ZeKrnl 1.7 zip & ZeKrnl 1.6 zip to sd card
5. Turn off phone, plug usb cable to phone
6. Press & hold Volume keys (Up + Down) then plug the other end of usb into PC to until download mode showned
7. Run LG Flash Tool with administrator privilege
8. Flash E98810e firmware into the device till success
(After Success Flash to Andro 4.1.2 JB):
9. Install towelroot and root the device
10. Install freegee to cater LG security issue
11. Install latest TWRP
12. Reboot into recovery mode
13. wipe system, data, cache, dalvik cache
14. flash ZeKrnl 1.7
--Camera issue
debug.composition. type=dyn --> debug.composition. type=gpu using build prop editor and/or flash ZeKrnl 1.6 kernell
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page8
--Deep Sleep issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page10
-- SD Card issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page12
-- Kernel parameter tuning sampel
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page14
Btw looks like you are the only person that still active in this thread...really appreciate it...thank you very much

You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.

So you are saying i just flash the rom as is without any further change?Noted shady...i will inform you the result

ShadySquirrel said:
You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.
Click to expand...
Click to collapse
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock

hotmatua.parulian said:
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock
Click to expand...
Click to collapse
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device

ShadySquirrel said:
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device
Click to expand...
Click to collapse
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.

hotmatua.parulian said:
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.
Click to expand...
Click to collapse
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...

g0at1 said:
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...
Click to expand...
Click to collapse
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.

Quiet interesting this device...salut to programmers of this device...

hotmatua.parulian said:
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.
Click to expand...
Click to collapse
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
hotmatua.parulian said:
Quiet interesting this device...salut to programmers of this device...
Click to expand...
Click to collapse
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.

ShadySquirrel said:
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.
Click to expand...
Click to collapse
:good::good::good::good: salut to you...the true programmer..never quit..yes im agree with you...i had played with nexus 1,2,3 before but never found something like this...
OK then, i will try g0at1 suggestion, hopefully it works... Like you said its only JB, root, freegee, newer twrp, backup, flash custom

Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"

hotmatua.parulian said:
Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"
Click to expand...
Click to collapse
You forgot to wipe system, data and caches.

ShadySquirrel said:
You forgot to wipe system, data and caches.
Click to expand...
Click to collapse
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...

hotmatua.parulian said:
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...
Click to expand...
Click to collapse
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!

g0at1 said:
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!
Click to expand...
Click to collapse
Finally carbon installed successfully after I repeat the step very carefully including your reminder bout wiping...
Thank you very much, I will consult any bugs I found..

Half Day 1 issue:
- Scrambled screen layout each time booting
- Camera unstable/crash, also with apps camera mx and open camera
- i think batt is draining faster than kitkat stock
- i feel internet via wifi is slower than kitkat stock
- phone call, other person cant hear my voice

Just flashed SlimLP..Gosh its so slim and smooth...thank you very much...there issue bout the camera and scrambled screen each time I reboot the system, which camera apps I should use?

Moto G5 automatically boots into TWRP

Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?

I have the same problem, it comes back to recovery all the time and we can tell you about it, some help please
---------- Post added at 09:59 PM ---------- Previous post was at 09:43 PM ----------
Hi, I've come back, hahaha, I installed resurrection remix 7.1, previous all the wipes and reboot in bootloader I gave start and started, great.

I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings

CypherPotato said:
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
Click to expand...
Click to collapse
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.

SuperUtilisateur said:
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
Click to expand...
Click to collapse
Have you tried to boot from Fastboot?

Yes, it works once...
But if I have to restart it (or turn off and start with the power button), the phone boot always in recovery.
It is then necessary to restart fastboot then press "start".

Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
Try do a full reset through fastboot and then try installing whatever you need through fastboot and recovery. Much more reliable han ota installs/updates

Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings

grosobart said:
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
Click to expand...
Click to collapse
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--

SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
It always says that
As long as it says at the end
Write OK
It flashed successfully

OK,
After flash,
boots automatically into recovery ...
--
I tried with various boot.img. (linéage, AOSP, OctOS, ... )
Does not work ..
I started (into fastboot), I was errors. (Process stopped)
I just restored my phone ( https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/ )
... boot correctly.
Never mind ...
thank you all

SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/how-to/fyi-recovered-g5-xt-1676-to-stock-t3626088
try this first, regards

SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect

Moto G5 boots to TWRP
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??

Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup

rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Backing up Gigs of data is a huge pain. Even if I have to copy to my pc. So, just something that's less cumbersome.

Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Read the faq section (2nd post) - answer is there
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737

grosobart said:
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Click to expand...
Click to collapse
Anyone get the stock for 16gb/2gb version?