Develop Bugs

Radio Flash POLL

I always flash a new radio with recovery and I have now been told this is not the correct way on doing this, But all radio flash tutorials I have read say to do it this way.
What all your votes on this?

Depends on if you have modified nand partitions. If you have one with a cache partition to small to hold radio you HAVE to flash from fastboot.
Apart from that I believe there is little difference in the risks associated.

superste2201 said:
Depends on if you have modified nand partitions. If you have one with a cache partition to small to hold radio you HAVE to flash from fastboot.
Apart from that I believe there is little difference in the risks associated.
Click to expand...
Click to collapse
I have stock nand, what's the limit cache on that? new radio is out its a 11mb zip
Am worried using recovery now lol this will be my 4th radio flash with recovery and not one single problem?

it is generally safer to flash radio from fastboot.
if it can go wrong, then it is defienietly more probable while doing that trough recovery.

shankly1985 said:
I have stock nand, what's the limit cache on that? new radio is out its a 11mb zip
Am worried using recovery now lol this will be my 4th radio flash with recovery and not one single problem?
Click to expand...
Click to collapse
Stock should have 40 mb cache, if i remember well...sure you can flash it via recovery then, but fastboot is still safer imo.

vnvman said:
Stock should have 40 mb cache, if i remember well...sure you can flash it via recovery then, but fastboot is still safer imo.
Click to expand...
Click to collapse
Think am just going to stick with recovery like I said I not had one problem.

shankly1985 said:
Think am just going to stick with recovery like I said I not had one problem.
Click to expand...
Click to collapse
It's your choice, tho bricking is more frequent with that way: if the archive gets damaged recovery will flash it anyway and eventually brick your device, fastboot instead doesn't allow you to flash a malformed image, afaik...

vnvman said:
It's your choice, tho bricking is more frequent with that way: if the archive gets damaged recovery will flash it anyway and eventually brick your device, fastboot instead doesn't allow you to flash a malformed image, afaik...
Click to expand...
Click to collapse
True I never thought of that
Can I use this fastboot on windows7? Is there a upto data tutorial you can link me to please that would be great thanks.

shankly1985 said:
True I never thought of that
Can I use this fastboot on windows7? Is there a upto data tutorial you can link me to please that would be great thanks.
Click to expand...
Click to collapse
Yep, you can use it (i got the same os), but in order to do that you have to download the android sdk and set up adb properly. There's a lot of tutorials on how to do this, here's the first i stumbled across:
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Imho it's a rule of thumb to have a working adb/fastboot if you wanna be into the rom flashing thing: sooner or later they'll save your arse

vnvman said:
Yep, you can use it (i got the same os), but in order to do that you have to download the android sdk and set up adb properly. There's a lot of tutorials on how to do this, here's the first i stumbled across:
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Imho it's a rule of thumb to have a working adb/fastboot if you wanna be into the rom flashing thing: sooner or later they'll save your arse
Click to expand...
Click to collapse
Thanks yes I already have all that done and installed USB driver's. I did this when first rooting my phone
so it just learning how to use fastboot

So what ive been reading is this true.
As long has the zip file is not damaged you should be ok flashing in recovery. So if I just check zip file befor flashing for error's I will be fine?

modified changes revert back after rebooting the device

my device has been running cm11 unofficial version for quite sometime now.. the 20140921 version.. but recently I've started having a problem that the phone restarts suddenly.. so., i tried doing a fresh flash again.. but i keep getting the assert error. and the phone restarts. I have the recovery image which grarak had posted in the thread. But i donno how to use it. And now the problem has worsened because once I install any new app, the phone restarts on its own and after which it restores it back to the time when the app wasnt there.. I'm not able to make any new nandroid backups too coz the device restarts again.. I thought it might be a CWM error, so I tried flashing TWRP.. but its again an img file which i donno what to do.. sighs. .. and also, if i try to do a fresh flash of the official version of cm11 now, using the recovery i have now, will it show the assert error again?? thanks a lot in advance... hope someone can get me out of this mess..

mids1810 said:
my device has been running cm11 unofficial version for quite sometime now.. the 20140921 version.. but recently I've started having a problem that the phone restarts suddenly.. so., i tried doing a fresh flash again.. but i keep getting the assert error. and the phone restarts. I have the recovery image which grarak had posted in the thread. But i donno how to use it. And now the problem has worsened because once I install any new app, the phone restarts on its own and after which it restores it back to the time when the app wasnt there.. I'm not able to make any new nandroid backups too coz the device restarts again.. I thought it might be a CWM error, so I tried flashing TWRP.. but its again an img file which i donno what to do.. sighs. .. and also, if i try to do a fresh flash of the official version of cm11 now, using the recovery i have now, will it show the assert error again?? thanks a lot in advance... hope someone can get me out of this mess..
Click to expand...
Click to collapse
Download an app called Rashr. It can be used to flash the img file.

FoxyDrew said:
Download an app called Rashr. It can be used to flash the img file.
Click to expand...
Click to collapse
actually this problem is much more serious than that.... my device has kinda frozen in the present state... if i uninstall any apps and then restart the device the app remains there itself.. and if I try to install a new app, after restart, the app is nowhere to be seen.. so, in short, i cant install any new apps or make modifications to the previous ones... I'm not even able to install any other recovery due to this... it seems like there is some problem with the R/W rights.

mids1810 said:
actually this problem is much more serious than that.... my device has kinda frozen in the present state... if i uninstall any apps and then restart the device the app remains there itself.. and if I try to install a new app, after restart, the app is nowhere to be seen.. so, in short, i cant install any new apps or make modifications to the previous ones... I'm not even able to install any other recovery due to this... it seems like there is some problem with the R/W rights.
Click to expand...
Click to collapse
Youll have to boot into fastboot and flash the recovery. Press and hold volume up + power until the phone shuts down, then hold volume down + power until you get into Hboot. Then scroll down with the volume keys and select fastboot.
Check this out for how to flash the img files in fastboot http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html

FoxyDrew said:
Youll have to boot into fastboot and flash the recovery. Press and hold volume up + power until the phone shuts down, then hold volume down + power until you get into Hboot. Then scroll down with the volume keys and select fastboot.
Check this out for how to flash the img files in fastboot http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
Click to expand...
Click to collapse
everything went well during the flashing process.. i had flashed a TWRP img.... but even this didnt solve the problem, even now its CWM as it was before.... Its just as it was before
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 1298444288 bytes
sending 'recovery' (10540 KB)...
OKAY [ 1.528s]
writing 'recovery'...
OKAY [ 0.532s]
finished. total time: 2.065s

mids1810 said:
everything went well during the flashing process.. i had flashed a TWRP img.... but even this didnt solve the problem.... Its just as it was before
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 1298444288 bytes
sending 'recovery' (10540 KB)...
OKAY [ 1.528s]
writing 'recovery'...
OKAY [ 0.532s]
finished. total time: 2.065s
Click to expand...
Click to collapse
Try a clean flash of the official CM11. If that doesn't work, tell me which variant your using.

FoxyDrew said:
Try a clean flash of the official CM11. If that doesn't work, tell me which variant your using.
Click to expand...
Click to collapse
tried that too quite many times.. it shows that "assert error thing", tried it with both the unofficial and official ones, and also I cant factory reset the device, if i do a factory reset and restart without flashing the rom, I'm stuck with the same rom, cant modify it whatsoever...
I'm using the a5dwg dual sim Indian variant

mids1810 said:
tried that too quite many times.. it shows that "assert error thing", tried it with both the unofficial and official ones, and also I cant factory reset the device, if i do a factory reset and restart without flashing the rom, I'm stuck with the same rom, cant modify it whatsoever...
I'm using the a5dwg dual sim Indian variant
Click to expand...
Click to collapse
Use THIS recovery.img file. Flash that in fastboot, reboot into recovery, then do a full wipe (factory reset, cache, dalvik cache, /system, /boot) and reflash the newest official CM11 nightly.

FoxyDrew said:
Use THIS recovery.img file. Flash that in fastboot, reboot into recovery, then do a full wipe (factory reset, cache, dalvik cache, /system, /boot) and reflash the newest official CM11 nightly.
Click to expand...
Click to collapse
this is the error which i get:
Installing update.....
assert failed: run_program("/system/bin/makelinks.sh") == 0
E: Error in / sorage/sdcard1/cm-11-20141025-NIGHTLY-a5_2.zip
(Status 7)
Installation aborted.

mids1810 said:
this is the error which i get:
Installing update.....
assert failed: run_program("/system/bin/makelinks.sh") == 0
E: Error in / sorage/sdcard1/cm-11-20141025-NIGHTLY-a5_2.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Are you sure you flashed the recovery I linked you too. That's the EXACT error you get if you don't flash that recovery.

FoxyDrew said:
Are you sure you flashed the recovery I linked you too. That's the EXACT error you get if you don't flash that recovery.
Click to expand...
Click to collapse
Yes... I had tried using the recovery which you linked.. Is this problem in any ways related to this thread?
http://forum.xda-developers.com/showthread.php?t=2707378
I tried to add the wp_mod.ko file too... but there's no folder called as "modules" in the bin folder...
I feel its because of some problem with the read write issue.. since I'm not able to bring about any change in the system whatsoever except for changes made in the sd card.. they all get reverted after the reboot

mids1810 said:
Yes... I had tried using the recovery which you linked.. Is this problem in any ways related to this thread?
http://forum.xda-developers.com/showthread.php?t=2707378
I tried to add the wp_mod.ko file too... but there's no folder called as "modules" in the bin folder...
I feel its because of some problem with the read write issue.. since I'm not able to bring about any change in the system whatsoever except for changes made in the sd card.. they all get reverted after the reboot
Click to expand...
Click to collapse
In CM you can read and write to everywhere with no problem. You problem is weird, flash a RUU.

hmm...cant find a RUU for my variant though...

mids1810 said:
hmm...cant find a RUU for my variant though...
Click to expand...
Click to collapse
Well, try this Philz recovery, its the same one I'm using, and flash the newest build, which is the same one I'm using. If that doesn't work I honestly don't know what to tell you.

FoxyDrew said:
Well, try this Philz recovery, its the same one I'm using, and flash the newest build, which is the same one I'm using. If that doesn't work I honestly don't know what to tell you.
Click to expand...
Click to collapse
the same as before... cant get out of CWM..

mids1810 said:
Yes... I had tried using the recovery which you linked.. Is this problem in any ways related to this thread?
http://forum.xda-developers.com/showthread.php?t=2707378
I tried to add the wp_mod.ko file too... but there's no folder called as "modules" in the bin folder...
I feel its because of some problem with the read write issue.. since I'm not able to bring about any change in the system whatsoever except for changes made in the sd card.. they all get reverted after the reboot
Click to expand...
Click to collapse
@mids1810
Ok let's see, so your saying that the device won't allow to read or write, meaning 1 of 2 things.
Either you lost root access by uninstalling or modifying something, or
your device has accumulated too much background information / app data and it won't allow it to make any more changes due to limited or in other words, there's no space.
If you have CWM 6.0.4.7 then you will get the assert error every time. This is just to make sure you do have it flashed.
First thing's first.
-Go into your bootloader and go into fastboot mode. Plug it into the PC and it will say fastboot USB.
-Now download and run this .exe:
https://www.dropbox.com/s/7nn4a5xzx2pw7as/CWM_Recovery_en.exe?dl=1
-This will flash the latest 6.0.5.1 CWM automatically.
1. Now that you have the latest recovery installed,
-Boot into the recovery and wipe the CACHE and go into advanced options and wipe DALVIK CACHE. Do not press factory restore.
-Hit reboot device and test by installing an app to see if this fixes the issue.
2. If it still reboots after installing an app then download this .zip:
http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip?retrieve_file=1
-Put this zip on your SD card/internal storage
-Go into CWM and flash this .zip.
-Reboot the device and test again.
3. If BOTH of these steps failed then you will need to freshly install CM11.
-While the device is still on, put the latest CM11 on your device or recycle the same one that your using if you prefer its stability.
-Boot back into CWM and do a factory restore.
Factory restore is almost ALWAYS necessary for every time you flash CyanogenMod unless it is an update that specifically states it can be "dirty flashed" which is just a way of saying you flashed it without wiping all your information - data/cache/dalvik off of it.
Let me know how this goes for you. :laugh:

jaysoblitzed said:
@mids1810
Ok let's see, so your saying that the device won't allow to read or write, meaning 1 of 2 things.
Either you lost root access by uninstalling or modifying something, or
your device has accumulated too much background information / app data and it won't allow it to make any more changes due to limited or in other words, there's no space.
If you have CWM 6.0.4.7 then you will get the assert error every time. This is just to make sure you do have it flashed.
First thing's first.
-Go into your bootloader and go into fastboot mode.
Yeah i already had the CWM 6.0.5.1 running on my device, but I flashed it again just in case.... That didnt solve the issue.
Next I flashed the Super SU zip from my SD card(since anything I place in my internal storage vanishes once I reboot... even if rebooted in my recovery) That again didnt solve the problem
I did a fresh install of CM11, 20140921 which I am running at present due to the stability issue you mentioned.. (have tried with the official nightly a couple of times to no avail)... It shows the assert error just as before, all the time.
And yes, all the apps I uninstalled came back again, as always Completely out of any more ideas... And also I get quite many error messages often " so and so app stopped responding" and stuff
Click to expand...
Click to collapse

mids1810 said:
jaysoblitzed said:
@mids1810
Ok let's see, so your saying that the device won't allow to read or write, meaning 1 of 2 things.
Either you lost root access by uninstalling or modifying something, or
your device has accumulated too much background information / app data and it won't allow it to make any more changes due to limited or in other words, there's no space.
If you have CWM 6.0.4.7 then you will get the assert error every time. This is just to make sure you do have it flashed.
First thing's first.
-Go into your bootloader and go into fastboot mode.
Yeah i already had the CWM 6.0.5.1 running on my device, but I flashed it again just in case.... That didnt solve the issue.
Next I flashed the Super SU zip from my SD card(since anything I place in my internal storage vanishes once I reboot... even if rebooted in my recovery) That again didnt solve the problem
I did a fresh install of CM11, 20140921 which I am running at present due to the stability issue you mentioned.. (have tried with the official nightly a couple of times to no avail)... It shows the assert error just as before, all the time.
And yes, all the apps I uninstalled came back again, as always Completely out of any more ideas... And also I get quite many error messages often " so and so app stopped responding" and stuff
Click to expand...
Click to collapse
Did you try wiping JUST the Cache and the Dalvik cache WITHOUT doing a factory restore? These options are in CWMR.
Also, what is your device model? (a5_dug/chl/dwg/ul etc.)
If your not sure it says it at the top when your in the bootloader.
Click to expand...
Click to collapse

jaysoblitzed said:
mids1810 said:
Did you try wiping JUST the Cache and the Dalvik cache WITHOUT doing a factory restore? These options are in CWMR.
Also, what is your device model? (a5_dug/chl/dwg/ul etc.)
If your not sure it says it at the top when your in the bootloader.
Click to expand...
Click to collapse
yeah.. I did try.. without any difference in the results.
My device is the a5dwg dual sim Indian variant
Click to expand...
Click to collapse

jaysoblitzed said:
mids1810 said:
Did you try wiping JUST the Cache and the Dalvik cache WITHOUT doing a factory restore? These options are in CWMR.
Also, what is your device model? (a5_dug/chl/dwg/ul etc.)
If your not sure it says it at the top when your in the bootloader.
Click to expand...
Click to collapse
Follow this guide and restore your phone back to stock.
http://forum.xda-developers.com/desire-816/general/rombackup-t2811252
Its an TWRP nandroid backup of the original software, and if you have an updated version it will be able to update as well if you flash the stock recovery.
Click to expand...
Click to collapse

[Q] Need help ASAP! CWM problem.

Hey guys, this is my first post on XDA forum.
So I've recently bought a nexus 7, I used wugfresh's root kit to root my nexus but then it didn't work... so I've tired the auto root by chainfire. Then I was able to get root. So then I went to playstore and downloaded rom manager to install CWM. I went to recovery then I get this message:
E : Cant mount /cache/recovery/log etc.....
I've tried everything I can do such as researching, changing recovery, and watching a youtube tutorial but nothing helped.
Thanks.

I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.

nhizzat said:
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
Click to expand...
Click to collapse
I tried to format using wugfresh couple times but still not working...

DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- https://developers.google.com/android/nexus/images
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.

_MetalHead_ said:
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- Link Removed
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
Click to expand...
Click to collapse
I tried to flash TWRP but its still the same error code

z3r0c311 said:
I tried to flash TWRP but its still the same error code
Click to expand...
Click to collapse
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.

_MetalHead_ said:
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
Click to expand...
Click to collapse
It would be great if u could tell me the commands, im nubby with this fastboot thing.

z3r0c311 said:
It would be great if u could tell me the commands, im nubby with this fastboot thing.
Click to expand...
Click to collapse
I gave you the commands in my first post in this thread.
Here's a guide to get you started-
http://forum.xda-developers.com/showthread.php?t=2277112

Sorry for another nubby question but how do I get flash_all.bat?

z3r0c311 said:
Sorry for another nubby question but how do I get flash_all.bat?
Click to expand...
Click to collapse
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.

_MetalHead_ said:
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
Click to expand...
Click to collapse
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.

z3r0c311 said:
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
Click to expand...
Click to collapse
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?

_MetalHead_ said:
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
Click to expand...
Click to collapse
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...

z3r0c311 said:
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
Click to expand...
Click to collapse
Did the system image flash successfully?

_MetalHead_ said:
Did the system image flash successfully?
Click to expand...
Click to collapse
using flash-all command, yeah

z3r0c311 said:
using flash-all command, yeah
Click to expand...
Click to collapse
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.

_MetalHead_ said:
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...

z3r0c311 said:
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
Click to expand...
Click to collapse
No, you can only flash custom ROMs if you have a custom recovery.

unlocked bootloader but stuck on entering recovery

Unlocked my bootloader with ease dont this many times in the past. Problem i have now is after i install ClockWorkMod and try get into recovery it just freezes.
Sticks on htc screen saying entering recovery.
Any help appreciated.
If it helps im still on stock rom Android version 5.0.2

Nevermind i have managed to fix it.

Hi Junior, What do you do to fix it. because I'm with the same problem.
After upload the "twrp3.0.0.1.img" I select the Recovery, but nothing happen the Phone does not restart in TWRP graphic mode.
phone: HTC M8 - Unlocked
C:\>fastboot devices
FA56JYS01352 fastboot
C:\>fastboot erase cache
erasing 'cache'...
OKAY 0.023s
finished. total time: 0.023s
C:\>fastboot flash recovery twrp-3.0.0-1-m8.img
sending 'recovery' (20022 KB)...
OKAY 2.068s
writing 'recovery'...
OKAY 0.586s
finished. total time: 2.655

kruivo said:
After upload the "twrp3.0.0.1.img" I select the Recovery, but nothing happen the Phone does not restart in TWRP graphic mode.
Click to expand...
Click to collapse
Try to wipe cache again, and install TWRP 3.0.0.0. The version 3.0.0.1 is really new, so maybe there are some issues.

I believe it is another issue...
redpoint73 said:
Try to wipe cache again, and install TWRP 3.0.0.0. The version 3.0.0.1 is really new, so maybe there are some issues.
Click to expand...
Click to collapse
I've tried with all the images below:
twrp-2.7.0.1-m8
twrp-2.7.0.2-m8
twrp-2.8.5.0-m8
and the problem is the same... after upload the recover image, I select RECOVERY in my phone but nothing happen

You might want to give HTC-fastboot.exe a try. I've had troubles flashing the recovery as well with the standard ADB toolset.
You should be ablo to find the HTC fastboot utility somewhere around here

kruivo said:
I've tried with all the images below:
twrp-2.7.0.1-m8
twrp-2.7.0.2-m8
twrp-2.8.5.0-m8
and the problem is the same... after upload the recover image, I select RECOVERY in my phone but nothing happen
Click to expand...
Click to collapse
Pretty sure TWRMP version 2.7 are known to cause problems with Android 5 or later; and not booting into recovery is the known result. TWRP 2.8.5 might be okay, but I'm not sure. I'd try 2.8.7 or (as I already mentioned) 3.0.0.0.

redpoint73 said:
Pretty sure TWRMP version 2.7 are known to cause problems with Android 5 or later; and not booting into recovery is the known result. TWRP 2.8.5 might be okay, but I'm not sure. I'd try 2.8.7 or (as I already mentioned) 3.0.0.0.
Click to expand...
Click to collapse
I tried almost everything, now I will try via Linux.
because via adb I did not get hit "device not found" (tried all drives and nothing happened) only via fastboot I got connection. I believe I first need to remove the S-ON.

kruivo said:
I tried almost everything, now
Click to expand...
Click to collapse
But did you try what I told you to? Meaning TWRP 2.8.7 or 3.0.0?
"I tried everything" doesn't tell us what you actually did or did not do.
kruivo said:
because via adb I did not get hit "device not found" (tried all drives and nothing happened) only via fastboot I got connection.
Click to expand...
Click to collapse
Doesn't matter, since fastboot is what you need for installing TWRP.
kruivo said:
I believe I first need to remove the S-ON.
Click to expand...
Click to collapse
Why do you think that? Folks always jump to the conclusion that s-off is the magical answer to all their problems. S-off doesn't have any bearing on the ability to install custom recovery, or whether you can connect to adb or not.
Waste $25 is you want (as sunshine is the only working s-off method), but it won't solve your problem.

redpoint73 said:
But did you try what I told you to? Meaning TWRP 2.8.7 or 3.0.0?
"I tried everything" doesn't tell us what you actually did or did not do.
Doesn't matter, since fastboot is what you need for installing TWRP.
Why do you think that? Folks always jump to the conclusion that s-off is the magical answer to all their problems. S-off doesn't have any bearing on the ability to install custom recovery, or whether you can connect to adb or not.
Waste $25 is you want (as sunshine is the only working s-off method), but it won't solve your problem.
Click to expand...
Click to collapse
Yes, I tryed 2.8.7 and 3.0.0, but dosen't work. After select RECOVEY , the phone vibrates and nothing happens, forcing a physical reboot it gets stuck on the HTC home screen.

Do fastboot getvar all, and post the output (delete IMEI and serial number before posting) so we can see more info about the device.
Something else is going on here.

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?