Related
I have flashed twarp recovery through flashify. But i cant get into recovery mode. Im on H815-10b-SEA.
Please help
Same, I have it installed and Flashed it using Flashify but doing the button combo still goes to LG's recovery
What I did was when already in TWRP (using Flashify/fastboot command) simply install TWRP again, from there.
Choose install, image, recovery and select the TWRP image file. Flash. Now a button-reboot should work :good:
So TWRP now works for locked BL?
Sent from my LG-H815 using Tapatalk
Pfeffernuss said:
What I did was when already in TWRP (using Flashify/fastboot command) simply install TWRP again, from there.
Choose install, image, recovery and select the TWRP image file. Flash. Now a button-reboot should work :good:
Click to expand...
Click to collapse
Just tried it but still not working for button combo, Bit weird, I have an app that i use to get into recovery so not so bad, but still weird
Rehok said:
Just tried it but still not working for button combo, Bit weird, I have an app that i use to get into recovery so not so bad, but still weird
Click to expand...
Click to collapse
Would you please share this app?
pomponazzo said:
Would you please share this app?
Click to expand...
Click to collapse
There are multiple on the Play store, I use https://play.google.com/store/apps/details?id=com.naman14.powermenu&hl=en_GB as its material design so looks nice
imarcel99 said:
So TWRP now works for locked BL?
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
I'd like to know the secrets to this as well...
Rehok said:
Same, I have it installed and Flashed it using Flashify but doing the button combo still goes to LG's recovery
Click to expand...
Click to collapse
Have you attempted to do anything in TWRP such as making/restoring a backup, or flashing something besides TWRP? This is very interesting to me!
Sent from my VS986
Can someone confirm if flashing TWRP is possible with a locked bootloader with root as hinted above by the means of Flashify etc?
Thanks
A few people seem to have had success and I suspect this question is going to get more important with Marshmallow being quite tricky to root without an unlocked bootloader.
interesting... i might give it a try. might backup with LG bridge first
It's not possible to flash TWRP on a locked bootloader because until it's unlocked, the recovery partition is write protected. So TWRP can't be written to the device.
I have flashed twrp on several devices with a locked boot loader. It depends on if the version of twrp has been patched where the boot loader detects it as official lg recovery. .that's what I've heard it was but I have several lg devices with twrp and locked bl
Sent from my LG-VS450PP using Tapatalk
Very much doubt this is possible on the g4. Unless anyone has proof, I don't think it's possible.
I tried.
Flash recovery and reboot.
Reboot to recovery through app gives secure boot error but it boots normally.
Rebooting with button combination takes me to stock recovery, so don't know if it flashed it or not.
Doesn't work even going into recover manually by saying yes when on stock recovery.
Just broke stock recovery but boots fine.
Oh I bet it ain't happening on this g4 lol I'm having that same fastboot/****ed up stock recovery with my gpad 10.1 and it still boots into Android... I just wish I had the same look as everyone else who had success flashing recovery with a locked bootloader on that tablet
Sent from my VS986 using Tapatalk
---------- Post added at 12:11 PM ---------- Previous post was at 12:11 PM ----------
But when it comes to my g4 I want everything to be solid and nothing half assed
Sent from my VS986 using Tapatalk
Hi everyone, I'm in major trouble right now.
I just flashed a modem package from this link
https://www.androidfilehost.com/?fid=23578570567721897
and now I cant get to recovery or fastboot and of course cant boot up. Caan anyone help?
I flash using nameless latest twrp and my rom is Omni 6.0 test build.
Hey I have one problem here..
Im using oppo find7a Android 5.0 color os 2.1.5..
Already root using kingroot..
I want to flash to other os like cyanogen, gummybaer, miui etc
I follow all the step on many video on YouTube using TWRP ..
After I flash twrp recover img and reboot, it stuck on fastboot menu
It cannot enter the recovery menu
How do I solve this problem so I can do wipe cache and flash other os
Some people say I must unlock the bootloader so that I can enter TWRP recovery menu
Shouheng said:
Hi everyone, I'm in major trouble right now.
I just flashed a modem package from this link
https://www.androidfilehost.com/?fid=23578570567721897
and now I cant get to recovery or fastboot and of course cant boot up. Caan anyone help?
I flash using nameless latest twrp and my rom is Omni 6.0 test build.
Click to expand...
Click to collapse
Hello, almost the same happend to me.....flashed modem package on nameless ROM.
After reboot, the phone si completely dead.
No vibration, no fastboot, no recovery.....
Did you manage somehow to solve this????
EDIT: found this guide and it works http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=
tw9 said:
Hello, almost the same happend to me.....flashed modem package on nameless ROM.
After reboot, the phone si completely dead.
No vibration, no fastboot, no recovery.....
Did you manage somehow to solve this????
EDIT: found this guide and it works http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=
Click to expand...
Click to collapse
What's your device model name? After unbrick mobile data working fine?
My device is X9006 and on latest Nameless nightly everything is ok.
tw9 said:
My device is X9006 and on latest Nameless nightly everything is ok.
Click to expand...
Click to collapse
Can you give me like of drivers? I used one in unbrick tool but it is not getting installed
I have no other drivers than those in the unbrick thread.
There is also a process of installing them described, which is tricky, because the drivers are not digitally signed.
If you are on windows 7, you must put them in test mode....don't know how it is with other versions of windows, because I used my older machine with W7 for unbricking.
It is all there, in the unbrick thread.....If I remember correctly....
tw9 said:
I have no other drivers than those in the unbrick thread.
There is also a process of installing them described, which is tricky, because the drivers are not digitally signed.
If you are on windows 7, you must put them in test mode....don't know how it is with other versions of windows, because I used my older machine with W7 for unbricking.
It is all there, in the unbrick thread.....If I remember correctly....
Click to expand...
Click to collapse
Finally unbrciked the device using that guide and after some workarounds got 3g working. But the biggest problem I am facing now is. I am stuck in stock 1.2..5i with twrp 2.7.0 can't old backup are not showing in recovery also can't flash anything. No system update. Flashing nameless Rom latest results in updater script error. Tried flashing latest twrp but it will reboot to system every time I try to boot into recovery. Sorry for my bulky English.
Yes, this exact problem I had also to face.
And I don't remember it exactly, but If I'm not mistaken, I flashed the original ColorOS recovery, did some updates and finally then I ended up with ColorOS 2.1.5i, I think.....
From that point TWRP recoveries worked alright, even the newest versions.
If you managed to unbrick your device, this is piece of cake, just remember - you need original ColorOS recovery firstly.
tw9 said:
Yes, this exact problem I had also to face.
And I don't remember it exactly, but If I'm not mistaken, I flashed the original ColorOS recovery, did some updates and finally then I ended up with ColorOS 2.1.5i, I think.....
From that point TWRP recoveries worked alright, even the newest versions.
If you managed to unbrick your device, this is piece of cake, just remember - you need original ColorOS recovery firstly.
Click to expand...
Click to collapse
Thank you for your reply mate. Now flashed cm13 nightly using 2.8.4 I will be selling this phone ASAP. This fourm is almost inactive.
So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life
Hi! Sorry about my english.
I have a problem with my oneplus 3.
Did the unbrick with msmdownload tool, worked.
Bootloader is unlocked.
Did the fastboot recovery flash of the modified twrp 3.0.2-1.28
When i want to start twrp it stucks at one plus logo screen.
When i flash an older twrp version (don´t know which one, 3.0.2.1) it boot into twrp. but i cant flash any rom. Its getting stucked at installing (tried a view roms).
What did i wrong?
branvan said:
Hi! Sorry about my english.
I have a problem with my oneplus 3.
Did the unbrick with msmdownload tool, worked.
Bootloader is unlocked.
Did the fastboot recovery flash of the modified twrp 3.0.2-1.28
When i want to start twrp it stucks at one plus logo screen.
When i flash an older twrp version (don´t know which one, 3.0.2.1) it boot into twrp. but i cant flash any rom. Its getting stucked at installing (tried a view roms).
What did i wrong?
Click to expand...
Click to collapse
Are you on OOS4? If so try 3.0.2.19 of TWRP or the bluspark version 11 by eng.stk
no, @ stock OOS 3.2.8
ok did the update to oos 4.0 now.
and doestn work...
i have no idea
Try: "fastboot erase recovery" then "fastboot flash recovery recoveryfilename.img".
Otherwise try re-downloading it.
thanks, but no success
when i flash modified twrp, get stuck into booting to twrp.
after rebooting oos4 and reboot to recovery, original recovery is getting started.
Tried everything now for hours. Without getting a working twrp. Has anyone the same problem?
branvan said:
Tried everything now for hours. Without getting a working twrp. Has anyone the same problem?
Click to expand...
Click to collapse
I have the same issue, I'm on OOS4.0.1 and TWRP won't boot, tried the blu sparks one and the one included in the toolkit 3.7
Neither would boot, just stuck at their splash screens. I'm also looking for an answer.
do you have the dm-verity screen too at booting?
xT-g-K said:
I have the same issue, I'm on OOS4.0.1 and TWRP won't boot, tried the blu sparks one and the one included in the toolkit 3.7
Neither would boot, just stuck at their splash screens. I'm also looking for an answer.
Click to expand...
Click to collapse
Did you solved the Problem?
branvan said:
Did you solved the Problem?
Click to expand...
Click to collapse
I flashed the blu_sparks one again, worked that time just has abnormally long boot times.
branvan said:
Hi! Sorry about my english.
I have a problem with my oneplus 3.
Did the unbrick with msmdownload tool, worked.
Bootloader is unlocked.
Did the fastboot recovery flash of the modified twrp 3.0.2-1.28
When i want to start twrp it stucks at one plus logo screen.
When i flash an older twrp version (don´t know which one, 3.0.2.1) it boot into twrp. but i cant flash any rom. Its getting stucked at installing (tried a view roms).
What did i wrong?
Click to expand...
Click to collapse
I recently posted a guide to solves issues like that. Here it is: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
I hope it helps.
There is a lot of reading there. So, read it carefully before proceeding any further.
---------- Post added at 11:37 PM ---------- Previous post was at 11:34 PM ----------
xT-g-K said:
I flashed the blu_sparks one again, worked that time just has abnormally long boot times.
Click to expand...
Click to collapse
Just a little bit.
Check this: https://forum.xda-developers.com/showpost.php?p=70541567&postcount=2522
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?