Hi everybody.
I just flashed PureNexus 6.0 rom from 5.1.1 version, and after flashing and rebooting, the device gets stucked at the boot logo (an animation with 4 dots). This was the updating process (I'm rooted and with unlocked bootloader).
1) wiped all partitions (including system, data, etc...)
2) flashed bootloader from latest factory image via fastboot.
3) rebooted to bootloader
4) flashed vendor image via fastboot
5) flashed latest PureNexus 6.0 rom from recovery (latest twrp)
6) flashed dynamic-gapps from banks from recovery
7) rebooted
Did I do something wrong? Bootloader seems unlocked and I'm able to reboot to recovery but I don't know what else I can do.
ialana said:
Hi everybody.
I just flashed PureNexus 6.0 rom from 5.1.1 version, and after flashing and rebooting, the device gets stucked at the boot logo (an animation with 4 dots). This was the updating process (I'm rooted and with unlocked bootloader).
1) wiped all partitions (including system, data, etc...)
2) flashed bootloader from latest factory image via fastboot.
3) rebooted to bootloader
4) flashed vendor image via fastboot
5) flashed latest PureNexus 6.0 rom from recovery (latest twrp)
6) flashed dynamic-gapps from banks from recovery
7) rebooted
Did I do something wrong? Bootloader seems unlocked and I'm able to reboot to recovery but I don't know what else I can do.
Click to expand...
Click to collapse
Sounds like you did everything correct.
" Bootloader seems unlocked"
--- reboot into bootloader and it will tell you if you are unlocked.
Personally I would flash the volantis-mra58n factory image to get on the latest Marshmallow - boot up make sure all is running well.
Flash TWRP, make a nandroid, then flash the ROM.
No need to flash anything else, or at least that's what I did, here where my steps upon recieving the tablet last week.
unlocked bootloader.
flashed volantis-mra58n factory image, booted up played around for a bit (as Pure Nexus 6.0 wasn't out yet)
flashed TWRP, make a nandroid
flashed Pure Nexus 6.0 + banks gaaps
reboot, profit
sounds like something is going wrong, you should have the Marshmallow boot animation not the LP dots.
you don't need to flash the bootloader or vendor images doing my process as you are already on the latest ones from flashing the volantis-mra58n factory image.
Best of luck.
andybones said:
Sounds like you did everything correct.
" Bootloader seems unlocked"
--- reboot into bootloader and it will tell you if you are unlocked.
Personally I would flash the volantis-mra58n factory image to get on the latest Marshmallow - boot up make sure all is running well.
Flash TWRP, make a nandroid, then flash the ROM.
No need to flash anything else, or at least that's what I did, here where my steps upon recieving the tablet last week.
unlocked bootloader.
flashed volantis-mra58n factory image, booted up played around for a bit (as Pure Nexus 6.0 wasn't out yet)
flashed TWRP, make a nandroid
flashed Pure Nexus 6.0 + banks gaaps
reboot, profit
sounds like something is going wrong, you should have the Marshmallow boot animation not the LP dots.
you don't need to flash the bootloader or vendor images doing my process as you are already on the latest ones from flashing the volantis-mra58n factory image.
Best of luck.
Click to expand...
Click to collapse
Thanks for your answer. The bootloader is unlocked, or that's what it says when I boot on it. I'll try flash to the factory image and see what happens. Thanks!
Problem solved after flashing recovery, boot.img and system.img from factory image, thanks! I'll try flashing a custom rom now.
i've read that there needs to be gapps for 6.0, 5.1 gapps supposedly won't work on 6.0
Related
Ok long story short i'm confused as to what's up with this device. I just picked it up and started messing with it. Looks like it has mako bootloader unlock and cwm 6x recovery installed. The only roms it can flash is cm12.1 and the factory ATT images correctly. I tried to update to the newer version of CWM or TWRP via fastboot and the flash takes but no recovery is present. Things i've tried =
Full factory reset via LGE970AT-01-V20j-310-410-MAR-08-2013 (this leaves me with no bootloader/fastboot/recovery) It boots but black screen on bootanimation.
tinybin (both options) only the altern will boot but. (have fastboot but no recovery.)
So long story... In stock firmware I can install freegee and unlock via mako but there will be no recovery if I choose TWRP and CWM won't install anything bt CM... I'm attempting to install Blisspop btw.
Any help would be great. Thank you
While H2OS was loaded, I flashed TWRP. After that I rebooted to recovery, cleared all the essential things, flashed a ROM followed by a Gapps package. After that, when I chose reboot to system, the phone stays stuck at the OnePlus logo screen. I can't access the recovery either. I flashed 3 different versions of TWRP, but still couldn't boot to recovery. P.S.: Bootloader is unlocked
What can I do now?
UPDATE: BluSpark's modded TWRP works, but after flashing the ROM nothing boots
meraj99 said:
While H2OS was loaded, I flashed TWRP. After that I rebooted to recovery, cleared all the essential things, flashed a ROM followed by a Gapps package. After that, when I chose reboot to system, the phone stays stuck at the OnePlus logo screen. I can't access the recovery either. I flashed 3 different versions of TWRP, but still couldn't boot to recovery. P.S.: Bootloader is unlocked
What can I do now?
UPDATE: BluSpark's modded TWRP works, but after flashing the ROM nothing boots
Click to expand...
Click to collapse
You should fastboot flash old OOS 2 stock recovery, then full OOS 2.2.2 Rom.
Then root and install offical TWRP (not BS V41).
Then install what you want (but not Oxygen or hydrogen on MM)
Kéno40 said:
You should fastboot flash old OOS 2 stock recovery, then full OOS 2.2.2 Rom.
Then root and install offical TWRP (not BS V41).
Then install what you want (but not Oxygen or hydrogen on MM)
Click to expand...
Click to collapse
oh, root access is compulsory?
Just tinking about root, because I used it to install TWRP but you're right, fastboot flash could do it
Hi
First a little history...
I recently got an OPX with the intention of installing Sailfish OS on it. So first I need to get CM 12.1 installed. Following the instructions here I flashed TWRP using fastboot, but the version of TWRP provided at the link would not find any system partitions on my device and therefore could not be used to flash any images. Newer versions of TWRP would simply not load.
Eventually, using the stock OPX recovery, I managed to upgrade Oxygen OS to the latest version. I then flashed the latest version of TWRP (3.1.1-1) again and it worked! It found my devices partitions and I could flash ROMs with it. But, it wouldn't flash CM 12.1. Something about a trustzone incompatibility...
So I got the idea to try and downgrade Oxygen OS, which I did via TWRP. But then TWRP stopped working... and here is my problem.
I'm now stuck in a situation where:
- I can access fastboot
- The only versions of TWRP which work (e.g. 3.0.2-0) fail to find my system partitions, and therefore can't be used to flash ROMs
- The stock recovery also seems to fail to find the system partitions (clicking on "install locally" does nothing), so I can't use that to flash ROMs either
So I really need to get a working image on my phone somehow... but how?? Is it possible to do this via fastboot only?
Cheers!
Is your bootloader unlocked? TWRP cannot see system partitions if so.
I unlocked it originally... but since then I have installed a new ROM (Oxygen OS 2.x). Would this overwrite the bootloader? Do I need to unlock again? I think I must be using the old OOS bootloader now...
I think you can see if it's unlocked if you boot into bootloader, connect to pc and write on cmd "fastboot devices".
Whenever you switch between android 5.0 roms and 6.0 and further you have to first use the correct recovery from oneplus, only then you can flash the correct twrp and the adequate roms
My bootloader is unlocked. I cannot flash a new ROM via recovery, because none of the recovery images (stock, TWRP) can see my system partitions (I don't know why). At this stage I would just like to know if there is a way to flash a stock ROM/recovery/bootloader via some other method (fastboot, or a special tool), so I can restore my phone back to factory state. I don't care about losing data. Thanks.
EDIT: Just to clarify, I believe this is my current situation (please correct me if something doesn't make sense):
- OOS has two different bootloaders, 2.x and 3.x.
- The phone originally had OOS 2.x on it. None of the TWRP images I installed recognized my system partitions, so I couldn't flash with TWRP.
- After re-installing the stock recovery (which happened automatically when I booted to the stock ROM), I was able to upgrade to OOS 3.x via stock recovery. Now recent TWRP versions were working (I assume because upgrading to OOS 3.x updated the bootloader too), and were recognizing my system partitions.
- Using a new version of TWRP (3.1.1-1), I re-flashed an older version of OOS 2.x again. I think this was my mistake, because I think this downgraded the bootloader to 2.x again. Now none of the TWRP versions recognize my system partitions, so I cannot flash ROMs.
- I have re-flashed the stock recovery from the OnePlus website, but not even this allows me to flash ROMs. The symptoms look like in TWRP, i.e. that it fails to recognize my system partitions. So I am stuck with no way to flash ROMs, or upgrade the bootloader.
This is my version of TWRP built for the 2017 Moto G5S. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, turn off your device, hold PWR and VolDn for 3 seconds, then let go.
Differences between upstream TWRP and my fork:
My original green theme
No SuperSU
No TWRP app
No HTC Dumlock cruft
Updated pigz compressor (slightly faster and more tolerant of corruption)
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is available on the downloads tab.
XDA:DevDB Information
TWRP for Moto G5S, Tool/Utility for the Moto G5S
Contributors
squid2
Source Code: https://github.com/moto8937-twrp
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-17
Created 2017-11-05
Last Updated 2018-08-17
Squid TWRP 3.1.1-r3
Initial build for montana is up. I expect it to be fully functional, including encryption support. Special thanks to @lohanbarth for testing.
thank you for your work :good:
Hi,
i just flashed your TWRP. The flash was successful, after booting to recovery twrp came up just fine. I wiped /data to decrypt, then rebooted the phone... Now it seems either bootlooping or bricked.
(Of course i unlocked the bootloader before flashing)
The phone just shows the bootloader-screen (blue background, red M-Logo, white letters "powered by android") with a small text in the middle "bad key).
Nothing happens. I cant even shut it down. Holding the power button for 10 seconds seems to start a reboot (screen goes black) but the bootloader-screen immediately shows back up and stays. Theres nothing i can do, no adb/fastboot access either...
Any suggestions?
Edit1:
AH! Pressing VolDown + Power gets me to fastboot/recovery... Phew. Guess i flash the stock rom first before proceeding any further.
Edit2:
Succeeded, nice!
Hi,
I flashed this TWRP. After flashing I went to recovery mode. Format Data failed as /data unknown. Flashed stock ROM. Again flashed TWRP. This time it just bootloops into TWRP recovery. When I power off and ON again, it bootloops and goes into TWRP recovery again and again. Any idea what could be wrong? My guess is I screwed up partition table. But not sure.
Thanks
KS
I went through flashing stock ROM, TWRP once again. After flashing TWRP, I went to recovery repeatedly and did 'Format Data' every time. I flashed Magisk. System booted fine. I verified by power off/on several times. Seems to be working fine.
Thanks
KS
Thanks for your hard work at bringing TWRP to the MOTO G5s.
It took me a while to install it on my XT1797, as there was some strange message during boot which said
ID: Bad key
But after many many times bricking and unbricking, I am now finally rooted using Magisk.
Hope that we can see some custom Roms for this great device soon.
I tried it with XT1797, but I can not boot and flash twrp.
Is this twrp compatible with XT1797?
hello, your bootloader and unlock it?
did you enable USB debugging?
that you put the fastboot cmd?
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
FAFAŁ said:
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Click to expand...
Click to collapse
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Root and TWRP. And a great phone.
Just need some Roms, pray that they will come!
Thank you!
janhieber said:
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Click to expand...
Click to collapse
Ok .that's all super go to recovery end fire .Thanks
Hello, I compiled the twrp3.2 with the sources of squid2.
thank @squid2 for sources
twrp-montana-3.2.0-r1 > http://www.mediafire.com/file/4443oy6kwiyvm5g/twrp-montana-3.2.0-r1.img
Squid TWRP 3.2.0-r1
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
squid2 said:
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
Click to expand...
Click to collapse
Dear @squid2 please give some ROMs also
... please i know you are busy with work but it is just a request
Unable to Flash twrp recovery
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
dau999 said:
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
Click to expand...
Click to collapse
after the flash of the twrp you select good recovery in the bootloader?
lohanbarth said:
after the flash of the twrp you select good recovery in the bootloader?
Click to expand...
Click to collapse
Select good recovery in the bootloader??!!
Bootloader gives me a notification that the img is not signed or corrupt (squids one)
you tried to download it again and then try again
lohanbarth said:
you tried to download it again and then try again
Click to expand...
Click to collapse
I did, same error.
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Do following, instead of flashing your recovery.
Use this method boot and flash Magisk. Reboot back to your system and install Flashify and install your choosen Recovery with it
jonske said:
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Click to expand...
Click to collapse
in stock rom you need to flash magisk right after flashing twrp else it will get replaced by stock
jonske said:
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Click to expand...
Click to collapse
What the post above says is correct. However, if you don't want Magisk, after flashing TWRP, reboot into recovery and then into system. You may retain TWRP. However, this doesn't work for everyone.
Hi all, I fixed the issue by completely wiping my phone via TWRP and clean flashing pixel experience ROM. After rebooting on pixel rom TWRP persists.
It appears that MIUI rom has something that keeps reverting it to stock MI-recovery.
If you are on MIUI and flashing TWRP, once the recovery is up for the first time, you need to head on to reboot>recovery again in order to overwrite MIUI stock recovery. So the whole process would be like this;
i) Fastboot flash recovery twrp.img (or whatever the name of the image)
ii) Fastboot boot recovery
iii) Once TWRP is up, Swipe to allow modification and then go to Reboot>Recovery and reboot into TWRP once more. That's it! You have just overwritten the stock recovery and are now on TWRP!! Now you can reboot to system and TWRP will remain on your device. There's no need to flash Magisk etc if you want just TWRP and nothing else.
Rowdyy Ronnie said:
If you are on MIUI and flashing TWRP, once the recovery is up for the first time, you need to head on to reboot>recovery again in order to overwrite MIUI stock recovery. So the whole process would be like this;
i) Fastboot flash recovery twrp.img (or whatever the name of the image)
ii) Fastboot boot recovery
iii) Once TWRP is up, Swipe to allow modification and then go to Reboot>Recovery and reboot into TWRP again. That's it! You have just overwritten the stock recovery and are now on TWRP!! There's no need to flash Magisk etc if you just want TWRP and nothing else.
Click to expand...
Click to collapse
I did those exact steps and it didn't work. It ALWAYS kept getting overwritten.
jonske said:
I did those exact steps and it didn't work. It ALWAYS kept getting overwritten.
Click to expand...
Click to collapse
Did you follow step 3? You can't boot into system right after twrp is up for the first time. You need to reboot into twrp twice before you boot into system. This is what I do whenever I flash twrp and it never failed me yet.
Rowdyy Ronnie said:
Did you follow step 3? You can't boot into system right after twrp is up for the first time. You need to reboot into twrp twice before you boot into system. This is what I do whenever I flash twrp and it never failed me yet.
Click to expand...
Click to collapse
Yes, I even flashed the recovery image from within TWRP and rebooted to recovery again. Still didn't work.
Note this was on the new 10.3.6 stable MIUI release that got rolled out recently. Not sure if it has new detection or anything that rolls it back.
Anyway I have resolved my issue now all is good.
jonske said:
Yes, I even flashed the recovery image from within TWRP and rebooted to recovery again. Still didn't work.
Note this was on the new 10.3.6 stable MIUI release that got rolled out recently. Not sure if it has new detection or anything that rolls it back.
Anyway I have resolved my issue now all is good.
Click to expand...
Click to collapse
How did you fix it?