Hi,
I have a S8+, SM-G955F and I cannot have Android Oreo and TWRP (and then root). I only can have Android 7 and TWRP (and then root).
Current situation is: I have Android Oreo, Build G955FXXU1CRB7 is installed. Once I go to Download Mode and flash TWRP, I can boot into TWRP, but my device is not booting into Android anymore. It starts up, shows me the Samsung logo and reboots, then it shows samsung logo again and reboots.
It reboots and reboot and reboots...If I go to TWRP and make a factory reset or format data, it does not help, it only reboots when trying to start Android.
Even if I restore an older backup of boot, systems partition, it does not work...
So what do I do? I flash original Android Oreo firmware once again via Odin and get it back working, but: I loose TWRP again (and cannot flash SuperSU).
Any idea? I would like to have latest Oreo as well as TWRP recovery
Many thanks!
tobyffm said:
Hi,
I have a S8+, SM-G955F and I cannot have Android Oreo and TWRP (and then root). I only can have Android 7 and TWRP (and then root).
Current situation is: I have Android Oreo, Build G955FXXU1CRB7 is installed. Once I go to Download Mode and flash TWRP, I can boot into TWRP, but my device is not booting into Android anymore. It starts up, shows me the Samsung logo and reboots, then it shows samsung logo again and reboots.
It reboots and reboot and reboots...If I go to TWRP and make a factory reset or format data, it does not help, it only reboots when trying to start Android.
Even if I restore an older backup of boot, systems partition, it does not work...
So what do I do? I flash original Android Oreo firmware once again via Odin and get it back working, but: I loose TWRP again (and cannot flash SuperSU).
Any idea? I would like to have latest Oreo as well as TWRP recovery
Many thanks!
Click to expand...
Click to collapse
Hello, which instructions did you follow to flash again the firmware? ( i assume the firmware was the official )
StonebridgeGr said:
Hello, which instructions did you follow to flash again the firmware? ( i assume the firmware was the official )
Click to expand...
Click to collapse
Yes, it was the official one. Just searched the site, but cannot find it anymore. However, flashing the firmware does not need many steps. DOwnload the zip, extract the .tar files in it, open ODIN, load .tar files into Odin and click flash. Then it was flashed and Android was booting again.
tobyffm said:
Yes, it was the official one. Just searched the site, but cannot find it anymore. However, flashing the firmware does not need many steps. DOwnload the zip, extract the .tar files in it, open ODIN, load .tar files into Odin and click flash. Then it was flashed and Android was booting again.
Click to expand...
Click to collapse
you are right, when you flashed the official firmware, on odin did you select the Home_CSC or the CSC ?
StonebridgeGr said:
you are right, when you flashed the official firmware, on odin did you select the Home_CSC or the CSC ?
Click to expand...
Click to collapse
I think it was the CSC, but as far as I remember, I also tried the HOME_CSC in the past (not today) but the behaviour was also the same.
As far as I know difference is that with one of these files internal storage is wiped, with the other one it isn't, correct?
But what could this have to do that I get a restart-loop when flashing TWRP? I dont have a problem to flash original firmware, it works. But once I flash TWRP I cannot start Android anymore and have to reflash Android firmware again.
tobyffm said:
I think it was the CSC, but as far as I remember, I also tried the HOME_CSC in the past (not today) but the behaviour was also the same.
As far as I know difference is that with one of these files internal storage is wiped, with the other one it isn't, correct?
But what could this have to do that I get a restart-loop when flashing TWRP? I dont have a problem to flash original firmware, it works. But once I flash TWRP I cannot start Android anymore and have to reflash Android firmware again.
Click to expand...
Click to collapse
which guide did you follow to flash TWRP?
also yes the CSC not the HOME CSC wipes the internal storage
StonebridgeGr said:
which guide did you follow to flash TWRP?
also yes the CSC not the HOME CSC wipes the internal storage
Click to expand...
Click to collapse
I followed this guide: https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
But also not much to follow...Download correct TWRP for S8+, load into Odin and click flash. TWRP is correct version and it works for me. But at same time, phone is not booting into Android anymore. This is why I end in reflashing original Android firmware again. I am in a loop :silly:
tobyffm said:
I followed this guide: https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
But also not much to follow...Download correct TWRP for S8+, load into Odin and click flash. TWRP is correct version and it works for me. But at same time, phone is not booting into Android anymore. This is why I end in reflashing original Android firmware again. I am in a loop :silly:
Click to expand...
Click to collapse
Dude thats guide to flash and root S8 not S8+.. thats why you get bootloop, make sure to follow the correct guide next time
Here is the best guide i found for you https://www.androidinfotech.com/2018/02/root-samsung-galaxy-s8-plus-sm-g955f-oreo.html
StonebridgeGr said:
Dude thats guide to flash and root S8 not S8+.. thats why you get bootloop, make sure to follow the correct guide next time
Here is the best guide i found for you https://droidfeats.com/root-galaxy-s8-plus-variants-android-8-0-oreo-cf-auto-root/
Click to expand...
Click to collapse
thanks, but I dont think so.
From the thread I mentioned, yes, I can download TWRP for S8, not S8+, but I went to TWRP site and downloaded correct TWRP for my device. Loading into odin and flash is the same, doesnt matter which device I have.
CF Autoroot does not work for me as it is not available for Oreo firmware. I checked all this previously, I am not a that stupid guy :laugh:
tobyffm said:
thanks, but I dont think so.
From the thread I mentioned, yes, I can download TWRP for S8, not S8+, but I went to TWRP site and downloaded correct TWRP for my device. Loading into odin and flash is the same, doesnt matter which device I have.
CF Autoroot does not work for me as it is not available for Oreo firmware. I checked all this previously, I am not a that stupid guy :laugh:
Click to expand...
Click to collapse
then follow this guide, i am sure you did a wrong on the instructions, follow then without stress and do not rush . I never said you a stupid guy
https://androidjungles.com/root-samsung-galaxy-s8-plus-install-twrp-recovery-android-oreo-sm-g955f/
Download this TWRP image for your S8PLUS(twrp-3.2.1-0-dream2lte.img.tar 38.2M 2017-12-09 03:01:59 ES)
https://dl.twrp.me/dream2lte/
StonebridgeGr said:
then follow this guide, i am sure you did a wrong on the instructions, follow then without stress and do not rush . I never said you a stupid guy
https://androidjungles.com/root-samsung-galaxy-s8-plus-install-twrp-recovery-android-oreo-sm-g955f/
Download this TWRP image for your S8PLUS(twrp-3.2.1-0-dream2lte.img.tar 38.2M 2017-12-09 03:01:59 ES)
https://dl.twrp.me/dream2lte/
Click to expand...
Click to collapse
I used exactly that TWRP version today.
The only difference between my steps and the steps mentioned in your mentioned guide is that they use an older Odin version. But I already used different Odin version too
Ok, aynway, I will try it again with this guide tomorrow and will let you know about the result tomorrow. Thx so far
tobyffm said:
I used exactly that TWRP version today.
The only difference between my steps and the steps mentioned in your mentioned guide is that they use an older Odin version. But I already used different Odin version too
Ok, aynway, I will try it again with this guide tomorrow and will let you know about the result tomorrow. Thx so far
Click to expand...
Click to collapse
alright i will be waiting for you reply to my post here !!
StonebridgeGr said:
alright i will be waiting for you reply to my post here !!
Click to expand...
Click to collapse
Hi again,
I got an OTA Update this morning, so current build on phone was G955FXXU1CRC7.
I now downloaded the TWRP file you mentioned and followed the guide you mentioned.
TWRP was installed using latest Odin Version 3.13, then I tried to install SuperSU, but this failed, red error messages like failed to mount /data, unable to mount storage.
same for factory reset, does not work. I formated data, it worked. then I installed Super Su, it was possible. then I rebooted device and what shall I say, it booted into Android
Dont know what I did different now, maybe not trying to boot up Android before installing supersu.zip?
However, Now I have latest Oreo with TWRP and phone is rooted
Now I will go on and install xposed framework :good:
Many thanks for your help.
tobyffm said:
Hi again,
I got an OTA Update this morning, so current build on phone was G955FXXU1CRC7.
I now downloaded the TWRP file you mentioned and followed the guide you mentioned.
TWRP was installed using latest Odin Version 3.13, then I tried to install SuperSU, but this failed, red error messages like failed to mount /data, unable to mount storage.
same for factory reset, does not work. I formated data, it worked. then I installed Super Su, it was possible. then I rebooted device and what shall I say, it booted into Android
Dont know what I did different now, maybe not trying to boot up Android before installing supersu.zip?
However, Now I have latest Oreo with TWRP and phone is rooted
Now I will go on and install xposed framework :good:
Many thanks for your help.
Click to expand...
Click to collapse
Update: Just tried to flöash xposed framework via TWRP but it fails because of unable to mount data. Do you know why this appears?
tobyffm said:
Update: Just tried to flöash xposed framework via TWRP but it fails because of unable to mount data. Do you know why this appears?
Click to expand...
Click to collapse
Hello dude, u are gonna need to flash dm-verity 5.1 find it on google , flash it and then flash immediately flash Xposed , if the error appear again then format data, and there is a option to wipe cache and Data, wipe them too, flash dm-verity and flash immediately the Xposed, if I helped you please press thanks buttons
StonebridgeGr said:
Hello dude, u are gonna need to flash dm-verity 5.1 find it on google , flash it and then flash immediately flash Xposed , if the error appear again then format data, and there is a option to wipe cache and Data, wipe them too, flash dm-verity and flash immediately the Xposed, if I helped you please press thanks buttons
Click to expand...
Click to collapse
Hi,
I had to format data, then I wiped Cache and Data again. Tehn, I flashed dm-verity, directly after that SuperSU again and directly aafter this I flashed xposed.
Finally, all works
Many thanks for your kind help!
tobyffm said:
Hi,
I had to format data, then I wiped Cache and Data again. Tehn, I flashed dm-verity, directly after that SuperSU again and directly aafter this I flashed xposed.
Finally, all works
Many thanks for your kind help!
Click to expand...
Click to collapse
I told you you were missing something with the instructions, I am happy now everything is fine
Related
So I rooted my tablet and flashed it with twrp. But it was a long time ago that I did that. And rit running on Android 4.4.2. But to day I wanted to update it to android 5.0. It gave me an error and it said that I had to try downloading the update with keis and I did. Everything was going smoothly until it rebooted and now I'm stuck on bootloop with no backup. When I tried to boot into recovery I gave me the original samsung recovery can anyone help with this fix
MadMac19 said:
So I rooted my tablet and flashed it with twrp. But it was a long time ago that I did that. And rit running on Android 4.4.2. But to day I wanted to update it to android 5.0. It gave me an error and it said that I had to try downloading the update with keis and I did. Everything was going smoothly until it rebooted and now I'm stuck on bootloop with no backup. When I tried to boot into recovery I gave me the original samsung recovery can anyone help with this fix
Click to expand...
Click to collapse
Don't use Kies, it is literally awful. Use one of the SM-T530NU firmware files from this thread and flash it with Odin v3.10 (I would recommend factory resetting in stock recovery before you use Odin). Then you can root again using TWRP, just follow this method
Note: I have the exact same model as you and everything I just said worked fine for my tablet.
Thank you
thisisapoorusernamechoice said:
Don't use Kies, it is literally awful. Use one of the SM-T530NU firmware files from this thread and flash it with Odin v3.10 (I would recommend factory resetting in stock recovery before you use Odin). Then you can root again using TWRP, just follow this method
Note: I have the exact same model as you and everything I just said worked fine for my tablet.
Click to expand...
Click to collapse
one quick question is Factory Reset the same as data wipe with recovery
MadMac19 said:
one quick question is Factory Reset the same as data wipe with recovery
Click to expand...
Click to collapse
Correct
thisisapoorusernamechoice said:
Correct
Click to expand...
Click to collapse
thanks it worked
thisisapoorusernamechoice said:
Correct
Click to expand...
Click to collapse
is there any good Rom for my device like CM-12.1
MadMac19 said:
is there any good Rom for my device like CM-12.1
Click to expand...
Click to collapse
Go to the development section and check out either BlissPop or Resurrection remix. Both are based off CM12.1. The versions made for the SM-T530 work on our SM-T530NU. I use BlissPop, it's great.
Update: Links, BlissPop and Resurrection Remix. Use TK Gapps (either nano or micro) or jajb's minimal gapps, and whichever you use you might want to check out the debloat script on the minimal gapps thread
After attempt at installing software update to Nexus 10 tablet will not boot. Have wiped Cache and even then did a factory reset. Nothing. Google appears and then twirling colorful dots and nothing. For hours just twirling dots., Samsung and Google and Best Buy geeks says nothing they can do. No longer under warranty but very upset since tablet was working great until update. I am not very tech savvy but can anyone help or do I just have a new paperweight? Thanks for any advice.
I have not made any modifications to the tablet.
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
yes flash the newest image
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Gibbothegreat said:
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
Click to expand...
Click to collapse
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Khaon said:
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Click to expand...
Click to collapse
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
same problem
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
as a newbie .I'm not allowed to reference your link !!
I rooted my nexus 10 using xda instructions., installed CWM. All good. I tried backup and recovery and screwed something up in recovery. Got stuck in recovery mode reboot loop. Many gyrations, no fix, so I tried factory reset. Still no fix.
I decided to install a new version of the OS using the Mantaray tar you reference above. UBS connecting and fastboot. All messages look good. Now I have the problem reported in this thread. Stuck with flying balls and no boot. Very interested in any suggestions you may have.
Click to expand...
Click to collapse
Gibbothegreat said:
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
Click to expand...
Click to collapse
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Khaon said:
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Click to expand...
Click to collapse
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Gibbothegreat said:
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Click to expand...
Click to collapse
Oh I see, well, you should just flash a custom ROM or if you want to stay with official factory images, you should just follow instruction there:
https://developers.google.com/android/nexus/images
What you do need is just have fastboot executable once you are into the bootloader.
You can easily access the bootloader from twrp : shutdown > reboot into booatloader
Cool thx for your continued help :good:
The problem is due to your attempting an OTA update with a custom recovery (TWRP). You can only do OTA with stock recovery. Once you are in this situation, your easiest way out of it is to simply apply the latest factory image using "fastboot", but this will also wipe your user data so backup any photos, music, etc. before you start. You will also have to reload programs from Playstore once the new image is installed.
I have OEM unlocked, TWRP flashed, and yeah.
Trying to flash Resurrection Remix and once it's done and I reboot, I get a yellow screen with a couple lines and it gets much worse.
http: // i. imgur . com/ IZ9o3eX .jpg
Which Android version are you using?
Ragazzza said:
Which Android version are you using?
Click to expand...
Click to collapse
6.0.1.
That is the reason, you need to be on 5.1 Lollipop to flash that ROM
All you can do now is flash stock ROM, and start all over
Ragazzza said:
That is the reason, you need to be on 5.1 Lollipop to flash that ROM
All you can do now is flash stock ROM, and start all over
Click to expand...
Click to collapse
AH, so, can I downgrade to 5.1, then flash it?
iiCarelessness said:
AH, so, can I downgrade to 5.1, then flash it?
Click to expand...
Click to collapse
Sure thing fam, you can, download ODIN, and go to sammobile.com and choose 5.1 Lollipop for your country, and flash it. Root you phone after that and install twrp then flash the RR ROM, it will work, good luck
And next time, read the thread better before flashing ROM, next time it could be worst.
Ragazzza said:
Sure thing fam, you can, download ODIN, and go to sammobile.com and choose 5.1 Lollipop for your country, and flash it. Root you phone after that and install twrp then flash the RR ROM, it will work, good luck
And next time, read the thread better before flashing ROM, next time it could be worst.
Click to expand...
Click to collapse
Thank you so much, I appreciate it.
I just skimmed over aha.
iiCarelessness said:
Thank you so much, I appreciate it.
I just skimmed over aha.
Click to expand...
Click to collapse
np bro, report back results so i can know you suceeded
Ragazzza said:
np bro, report back results so i can know you suceeded
Click to expand...
Click to collapse
"Unfortunately, SystemUI has stopped."
I can boot the phone, just can't do anything with it.
Can't use 5.1.1 on my J500FN at all, which is disappointing.
The ROM just hangs on the boot logo, even after I've cleaned system, cache, and data.
iiCarelessness said:
Can't use 5.1.1 on my J500FN at all, which is disappointing.
The ROM just hangs on the boot logo, even after I've cleaned system, cache, and data.
Click to expand...
Click to collapse
1) Go to recovery and wipe /system , /data , /cache and dalvik-cache
2) Power off the phone (from recovery).
3) Boot in Download mode and flash the Lollipop 5.1.1 firmware you want.
3) Wait until phone boots succesfully. Then you can flash TWRP for Lollipop 5.1.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844 .
Always do the step 1) before upgrading / downgrading Android version, but also when reflashing stock rom with same Android version.
#Henkate said:
1) Go to recovery and wipe /system , /data , /cache and dalvik-cache
2) Power off the phone (from recovery).
3) Boot in Download mode and flash the Lollipop 5.1.1 firmware you want.
3) Wait until phone boots succesfully. Then you can flash TWRP for Lollipop 5.1.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844 .
Always do the step 1) before upgrading / downgrading Android version, but also when reflashing stock rom with same Android version.
Click to expand...
Click to collapse
This worked, but I'm having issues with /system not being found while flashing RR 6.0.1.
iiCarelessness said:
This worked, but I'm having issues with /system not being found while flashing RR 6.0.1.
Click to expand...
Click to collapse
Try to mount /system manually before flashing it.
#Henkate said:
Try to mount /system manually before flashing it.
Click to expand...
Click to collapse
I got it fixed, I wasn't on the right version of TWRP.
Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
EDIT: I forgot to mention, I'm not getting the boot animation as well. I press the power key and nothing at all happens.
d1nesh said:
Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
Click to expand...
Click to collapse
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
avirk said:
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
d1nesh said:
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
Click to expand...
Click to collapse
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
avirk said:
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
==vj== said:
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
Click to expand...
Click to collapse
i'm really sorry about posting in wrong thread.
While trying to flash ElementalX kernel through memory card, I'm getting error: Zip signature verification failed, (in red).
nazim7 said:
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
Click to expand...
Click to collapse
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
d1nesh said:
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
Click to expand...
Click to collapse
What did you mean by your device not being detected in bootloader mode. Did you install the right drivers. Did you install minimal adb and fastboot. Can you do the below steps and tell me the result.
1. Download the drivers from here.
For Windows: http://www.devfiles.co/download/5eEx...ager_2.5.4.exe
2. Download the Minimal ADB and Fastboot = https://www.androidfilehost.com/?fid=745425885120698566
3. Install Minimal ADB and Fastboot = https://forum.xda-developers.com/sho....php?t=2317790
4. Restart the Moto G4 in fastboot mode. (Bootloader mode)
5. Connect the Phone to the computer.
6. In adb fastboot folder shift+right click and then in the pop up click "open command window here"
7. In the command line type: "fastboot devices"
Seeing your serial number means we know all is good and your phone is connected and you can go on flash the stock firmware. If the serial number is not showing, the drivers are not properly installed.
---------- Post added at 01:33 PM ---------- Previous post was at 01:25 PM ----------
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I thought he don't have TWRP installed. If TWRP is installed, then go on with what he said. That is the best solution for you. :good:
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
d1nesh said:
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
Click to expand...
Click to collapse
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
avirk said:
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
Click to expand...
Click to collapse
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
Try with other pc or change the port for data cable. It seems your system partition got corrupted, also you can mount system partition under twrp and then try to format it.
d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
nazim7 said:
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
Click to expand...
Click to collapse
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
As @nazim7 suggested you to flash the latest TWRP and then try to flash the rom again, also you can try to resize the partition and try to format it from twrp from the option in twrp. Just let us know what the result come back.
nazim7 said:
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
Click to expand...
Click to collapse
There's one more problem like I've mentioned previously. I have the latest drivers even then the device is not being detected via adb when in bootloader, but as soon as I boot into recovery, the device shows up on adb after command. How do I flash the recovery if the device doesn't show up in bootloader on adb?
This morning I my phone pesented itself in TWRP.
Maybe this is because over the past days I repeatedly got notifications that a system upgrade wanted to install itself (I have a modified 26s X720 from Tora33).
I rejected those notifications.
Now I am stuck in TWRP and I cannot get around it. What I tried:
Reinstalling previous firmware (Tora33 26s) still on the phone
Restoring a TWRP backup from 6 months ago (TWRP didn't see it, maybe it's from a previous TWRP version, I now have v. 3.1)
Flash via fastbood factory image using Mauro's Tool All In One (error message "can't find file mke2fs.conf")
Wipe data, cache, dalvik cache, system; then install Mauro_V2.2 cleansed 23s firmware which I transferred to the phone
Every time it boots up in TWRP.
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Sent from my LEX720 using xda premium
mchlbenner said:
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Click to expand...
Click to collapse
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Wortelstok said:
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Click to expand...
Click to collapse
Yes, that QFIL guide is for the x720.
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
marik1 said:
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
Click to expand...
Click to collapse
If he was just going back stock that would work he flash 28s ota with twrp so this will not work.
Sent from my LEX720 using xda premium
No brick after OFW push 28s
The pushed (unvoluntary) update didn't brick my phone after all. This may be important for those that have modified stock ROMs with TWRP.
Not being able to restore OFW was a bug in Mauro's All-in-One tool which he fixed last night. After I could easily flash 20S or 26S stock from his repository. I would also recommend this as safest/easiest procedure. Afterwards you can just flash TWRP from the same tool and move from there.
By the way, immediately after flashing 20s the FW notified it wanted to update itself, again!
n my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
Click to expand...
Click to collapse
Might have tried that