Nexus 5 bootloop. Can't access stock recovery - Nexus 5 Q&A, Help & Troubleshooting

My Nexus 5 started bootlooping suddenly. I havent rooted my nexus5. I guess it will get fixed if I root it.
So I went to recovery mode and dead android guy came up with red exclamation and 'no command' shown. I pressed power+volUP but nothing happened. And also that screen doesnt stay for long, it will restart after few seconds and continue with the boot loop.
I tried cmd and entered "fastboot flash recovery recovery.img". The cmd shows
Target reported max download size of 1073741824 bytes
sending recovery <14582 kb> ...
OKAY [0.64S]
writing recovery...
OKAY [1.109s]
finished. total time: 1.754s
After this when I go to recovery mode, it still shows no command and starts bootloop again
PLEASE HELP

Related

CWM flashing not possible

Hey guys,
my bootloader is unlocked - so far, so good. however though, when I want to flash cwm, I'm getting this result:
C:\xyz>fastboot flash recovery cwmrecovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6632 KB)...
OKAY [ 0.558s]
writing 'recovery'...
OKAY [ 1.838s]
finished. total time: 2.397s
so it looks successful. But I still have the stock recovery. When I'm trying the rom manager from the playstore alternatively, I'm getting an error right aways after the cwm download (looks as if nothing happened in between). Error message is simply "An error occurred while flashing your recovery"
Any suggestions?
Thanks!
After you fastboot flash recovery, IMMEDIATELY reboot to recovery. Do not reboot to Android.
Take a backup. Then boot to Android... should stick.
Yeah, I learned that the hard way....
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Yeah, I learned that the hard way....
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Weird! I had the similar issue as described above. I'm able to successfully flash the CWM flash to the SPH-710 for me. However, can't boot INITIALLY to the CWM boot; It's able to successfully go into normal boot; But Volume-UP, Center button Power button, just blinks the custom boot screen once then the screen becomes blank for some time.
Can't get out of the Stock ROM boot up to CWM;

Desire HD, recovery issue, Please help

Got desire HD which has a faulty firmware and most of the process gets killed and im unable to do anything like installing new app, Bluetooth connection or accessing memory through PC.
However, it does lets me connect to the PC
Details of DHD:
2.3.3
S-OFF
Stock recovery
Background:
Since I’m unable to install any app in it, I got hold of iRoot software and it says rooted successfully
now I got few recoveries
Problem:
adb reboot bootloader .. Goes to fastmode usb
fastboot flash recovery recovery.img … CMD says everything went successful
sending 'recovery' (4002 KB)... OKAY [ 0.777s]
writing 'recovery'... OKAY [ 1.372s]
finished. total time: 2.150s
fastboot reboot
Now it reboots and starts again in android. When I go back to bootloader screen it is still the same no custom recovery installed?
I also have tried going to 'recovery' option in bootloader after flashing recovery the phones gets stuck on HTC green logo and white background
hashims said:
Got desire HD which has a faulty firmware and most of the process gets killed and im unable to do anything like installing new app, Bluetooth connection or accessing memory through PC.
However, it does lets me connect to the PC
Details of DHD:
2.3.3
S-OFF
Stock recovery
Background:
Since I’m unable to install any app in it, I got hold of iRoot software and it says rooted successfully
now I got few recoveries
Problem:
adb reboot bootloader .. Goes to fastmode usb
fastboot flash recovery recovery.img … CMD says everything went successful
sending 'recovery' (4002 KB)... OKAY [ 0.777s]
writing 'recovery'... OKAY [ 1.372s]
finished. total time: 2.150s
fastboot reboot
Now it reboots and starts again in android. When I go back to bootloader screen it is still the same no custom recovery installed?
I also have tried going to 'recovery' option in bootloader after flashing recovery the phones gets stuck on HTC green logo and white background
Click to expand...
Click to collapse
I think when you flash a recovery and you boot into android, android overwrites the custom recovery with the stock one. Try to boot to recovery without booting in android.

OTA caused a boot loop?

My boot loader is unlocked and am rooted with the stock recovery. My model is XT1550 (dual sim variant in India). I received the OTA updates today.. I downloaded them and installed.. The installation looked like it went fine.. after the installation the phone restarted.. but it kind of went to a boot loop after that.. I can power off the phone pressing the power button for some time.. bu the phone powers off and restarts automatically... it does not progress beyond the few initial screens after which it just displays a blank display...
I am able to get into flashmode.. however, my pc does not recognize the device.. adb terminal shows no devices when I give "adb devices" command.. can someone help? Can I do a factory reset from the flashboot menu? what does the factory mode do? what else can be done to salvage the situation? Thanks.
Update: I went into the stock recovery and did a factory reset. It wiped the user data and did a factory reset. After this I tried rebooting the system. But again the same problem. The phone starts and after the first two -three screens of a boot animation it simply gives me a blank screen display. Really worried now.. Any help?
Flash STOCK FIRMWARE
coolmalayalee said:
My boot loader is unlocked and am rooted with the stock recovery. My model is XT1550 (dual sim variant in India). I received the OTA updates today.. I downloaded them and installed.. The installation looked like it went fine.. after the installation the phone restarted.. but it kind of went to a boot loop after that.. I can power off the phone pressing the power button for some time.. bu the phone powers off and restarts automatically... it does not progress beyond the few initial screens after which it just displays a blank display...
I am able to get into flashmode.. however, my pc does not recognize the device.. adb terminal shows no devices when I give "adb devices" command.. can someone help? Can I do a factory reset from the flashboot menu? what does the factory mode do? what else can be done to salvage the situation? Thanks.
Update: I went into the stock recovery and did a factory reset. It wiped the user data and did a factory reset. After this I tried rebooting the system. But again the same problem. The phone starts and after the first two -three screens of a boot animation it simply gives me a blank screen display. Really worried now.. Any help?
Click to expand...
Click to collapse
Hi, I have faced the same issue that you have faced. I will be resorting to flashing original STOCK ROM using the ADB commands.
There are other threads in this forum explaining the procedure.
Don't worry. If you follow the procedure correctly you will be able to reinstall the system and use your phone again.
After flashing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. Other wise you will face similar issue.
To go to fastboot mode from the blank screen mode you may follow the steps below:
1. Keep the power key pressed for a few seconds till you can see that the screen has gone completely black (otherwise you will see the screen dimly lit)
2. Immediately after this step press the volume down button first followed by power button and hold for a second or two and release the buttons, you would be in the fastboot mode
3. You can connect your phone to the PC in this mode to flash the STOCK ROM using the flash boot commands
4. You will find the STOCK ROM in the following link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
5. For installation procedure and fastboot commands refer this link:
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Hope this helps
arunhebbare; said:
Hi, I have faced the same issue that you have faced. I will be resorting to flashing original STOCK ROM using the ADB commands.
There are other threads in this forum explaining the procedure.
Don't worry. If you follow the procedure correctly you will be able to reinstall the system and use your phone again.
After flashing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. Other wise you will face similar issue.
To go to fastboot mode from the blank screen mode you may follow the steps below:
1. Keep the power key pressed for a few seconds till you can see that the screen has gone completely black (otherwise you will see the screen dimly lit)
2. Immediately after this step press the volume down button first followed by power button and hold for a second or two and release the buttons, you would be in the fastboot mode
3. You can connect your phone to the PC in this mode to flash the STOCK ROM using the flash boot commands
4. You will find the STOCK ROM in the following link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
5. For installation procedure and fastboot commands refer this link:
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Hope this helps
Click to expand...
Click to collapse
Thanks a lot. I can get into fastbot mod. However, when I type adb devices from the command prompt it doesnt list any devices. Will I be able to flash anything in such a situation? I already have the stock firmware extracted to my adb folder.
Update: I have flashed the stock firmware successfully. The device is back up and running now.. thanks a lot..
coolmalayalee said:
Thanks a lot. I can get into fastbot mod. However, when I type adb devices from the command prompt it doesnt list any devices. Will I be able to flash anything in such a situation? I already have the stock firmware extracted to my adb folder.
Update: I have flashed the stock firmware successfully. The device is back up and running now.. thanks a lot..
Click to expand...
Click to collapse
Can you please let us know what you did to over come the problem of your device not being able to be recognized by ADB fastboot?
Also which STOCK firmware did you use (there are two in the link)?
Could you download and update via the OTA?
Your reply would help others. Thanks
arunhebbare said:
Can you please let us know what you did to over come the problem of your device not being able to be recognized by ADB fastboot?
Also which STOCK firmware did you use (there are two in the link)?
Could you download and update via the OTA?
Your reply would help others. Thanks
Click to expand...
Click to collapse
Well, after getting into fastboot when I use the command "adb devices" it did not show anything under the list of devices. However, when I started giving the commands for flashing the stock firmware it was accepting the adb commands. I followed the commands here.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
and I used the stock firmware XT1550_OSPREY_RETASIA-INDIA_DS_2GB_5.1.1_LPI23.72-47_cid7 for this purpose downloaded from
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 things were alright. But I need to say that the first command "fastboot flash partition gpt.bin" did fail in fastboot. But I went ahead and gave all the subsequent commands all of which were successful and in the end I was able to restart with the new factory image.
However, all my data lost, root lost, and my boot loader is still in unlocked status.
About OTAs, I don't know. I went to the system updates to see if there is an OTA.. it says my software is up to date.
Thanks
That was a fast reply. Thanks for elaborating.
Don't know what the consequences of not being able to flash the gpt.bin are...
I will post update after flashing stock rom after reaching home. Stuck in office still...
Hello,
A little info about adb/fastboot :
adb works only after boot.
fastboot works in fastboot mode.
When you boot to fastboot mode and try commands such as "adb devices" you won't see any output or may get an error as the device is connected in fastboot mode.
So using "fastboot devices" will return all device ids connected in fastboot mode.
Hope this helps other new users.
arunhebbare said:
That was a fast reply. Thanks for elaborating.
Don't know what the consequences of not being able to flash the gpt.bin are...
I will post update after flashing stock rom after reaching home. Stuck in office still...
Click to expand...
Click to collapse
This is the message I get after gpt.bin flashing.
sending 'partition' (32 KB)...
OKAY [ 0.059s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Below is a response I saw in reddit on this error. Looks like it should be fine.
That normally happens when you try to downgrade. GPT.bin and motoboot should fail to flash if you're trying to downgrade; prevent a hardbrick. As long as all the other commands are flashing successfully you'll be fine.
Click to expand...
Click to collapse
https://www.reddit.com/r/MotoG/comments/3dxmso/xt_1032_mfastboot_preflash_validation_failed/
Edit: Deleted
Flashed Stock rom. up and about
I flashed the stock 23.72.47 version using fastboot commands.
The flashing of gpt.bin failed but all the other commands were successful.
I had unlocked my bootloader previously which is still showing as unlocked.
Yes, I made a mistake of using adb commands in fastboot. In bootloader we got to use fastboot commands and adb does not work.
I respect this forum for these exact reasons that things are no nonsense here and this is the place for really knowledgeable people.
Thanks for bearing noobs like me.
Lastly my beloved moto g3 is up and about and doing fine.
Oh BTW I too checked for updates and found that the the stock rom 23.72.47 seems to be the updated version with the Ota incorporated. Earlier I was on the 23.72.33 rom.
Thank you members.
boot loupe due to an update
i was used all commands in cmd prompt but in in cmd prompt it was saying like that
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
error: cannot load 'gpt.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash motoboot motoboot.img
target reported max download size of 268435456 bytes
error: cannot load 'motoboot.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
error: cannot load 'logo.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
error: cannot load 'boot.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
error: cannot load 'recovery.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
sechunk1
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk1': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
echunk2
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparechunk2': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
sechunk3
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk3': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
error: cannot load 'NON-HLOS.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.085s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
error: cannot load 'fsg.mbn': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.119s]
finished. total time: 0.120s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.975s]
finished. total time: 0.976s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot reboot
< waiting for device >
rebooting...
finished. total time: 0.007s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>
i was tried a lot in my motog3 device after rebooting also it was showing blank dimly light it was not turning on my device had got a ota update so i was updated after that update i was installed then restarted the mobile after that it was no starting at all showing blank in that case also i was factory data reset my phone in recovery mode but still also it was restating with moto logo and then showing blank please help
Out of curiosity I flashed the 23.72.33 and updated via ota. The version it shows is 23.72-47.4.
Observing the ota results.
pranaykumar3318 said:
i was used all commands in cmd prompt but in in cmd prompt it was saying like that
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
error: cannot load 'gpt.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash motoboot motoboot.img
target reported max download size of 268435456 bytes
error: cannot load 'motoboot.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
error: cannot load 'logo.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
error: cannot load 'boot.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
error: cannot load 'recovery.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
sechunk1
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk1': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
echunk2
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparechunk2': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
sechunk3
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk3': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
error: cannot load 'NON-HLOS.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.085s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
error: cannot load 'fsg.mbn': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.119s]
finished. total time: 0.120s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.975s]
finished. total time: 0.976s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot reboot
< waiting for device >
rebooting...
finished. total time: 0.007s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>
i was tried a lot in my motog3 device after rebooting also it was showing blank dimly light it was not turning on my device had got a ota update so i was updated after that update i was installed then restarted the mobile after that it was no starting at all showing blank in that case also i was factory data reset my phone in recovery mode but still also it was restating with moto logo and then showing blank please help
Click to expand...
Click to collapse
Try it again using fastboot not mfastboot
i was done
thanks friend i was done finally i was installed stock firmwere thanks to xda developers
---------- Post added at 02:14 PM ---------- Previous post was at 02:00 PM ----------
arunhebbare said:
Hi, I have faced the same issue that you have faced. I will be resorting to flashing original STOCK ROM using the ADB commands.
There are other threads in this forum explaining the procedure.
Don't worry. If you follow After flashthe procedure correctly you will be able to reinstall the system and use your phone again.
after installing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. Other wise you will face similar issue.
To go to fastboot mode from the blank screen mode you may follow the steps below:
1. Keep the power key pressed for a few seconds till you can see that the screen has gone completely black (otherwise you will see the screen dimly lit)
2. Immediately after this step press the volume down button first followed by power button and hold for a second or two and release the buttons, you would be in the fastboot mode
3. You can connect your phone to the PC in this mode to flash the STOCK ROM using the flash boot commands
4. You will find the STOCK ROM in the following link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
5. For installation procedure and fastboot commands refer this link:
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Hope this helps
Click to expand...
Click to collapse
i was successfully installed stockfirmwere in my motog3 but still the bootloader is unlocked will you please say that if i unlock the bootloader and then update my device without root will i face the bootloupe problem?? and again i dont want to face bootloupe problems after an otp update will you please say that what type of rules i have to follow to not face this type of problem
and you said that the after installing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. will you please say that how to ensure that my phone has stock recovery
my thought
coolmalayalee said:
My boot loader is unlocked and am rooted with the stock recovery. My model is XT1550 (dual sim variant in India). I received the OTA updates today.. I downloaded them and installed.. The installation looked like it went fine.. after the installation the phone restarted.. but it kind of went to a boot loop after that.. I can power off the phone pressing the power button for some time.. bu the phone powers off and restarts automatically... it does not progress beyond the few initial screens after which it just displays a blank display...
I am able to get into flashmode.. however, my pc does not recognize the device.. adb terminal shows no devices when I give "adb devices" command.. can someone help? Can I do a factory reset from the flashboot menu? what does the factory mode do? what else can be done to salvage the situation? Thanks.
Update: I went into the stock recovery and did a factory reset. It wiped the user data and did a factory reset. After this I tried rebooting the system. But again the same problem. The phone starts and after the first two -three screens of a boot animation it simply gives me a blank screen display. Really worried now.. Any help?
Click to expand...
Click to collapse
so far i have learned that before applying official ota one must have bootloader relock and everything official like recovery etc etc and may be no root (do not remember no root thing well)
i may be wrong but sharing is caring right?
umo4u said:
so far i have learned that before applying official ota one must have bootloader relock and everything official like recovery etc etc and may be no root (do not remember no root thing well)
i may be wrong but sharing is caring right?
Click to expand...
Click to collapse
It doesn't need bootloader relocked but you need stock rom(no Mods or root) and stock recovery to do ota
---------- Post added at 15:56 ---------- Previous post was at 15:53 ----------
pranaykumar3318 said:
thanks friend i was done finally i was installed stock firmwere thanks to xda developers
---------- Post added at 02:14 PM ---------- Previous post was at 02:00 PM ----------
i was successfully installed stockfirmwere in my motog3 but still the bootloader is unlocked will you please say that if i unlock the bootloader and then update my device without root will i face the bootloupe problem?? and again i dont want to face bootloupe problems after an otp update will you please say that what type of rules i have to follow to not face this type of problem
and you said that the after installing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. will you please say that how to ensure that my phone has stock recovery
Click to expand...
Click to collapse
If you reflashed stock firmware then you will have stock recovery and not twrp to find out reboot into your bootloader then use arrow keys until get to option saying recovery then select if its stock it will look abit like cwm but call android 3e recovery or something close to that if not it will boot into twrp
minidude2012 said:
It doesn't need bootloader relocked but you need stock rom(no Mods or root) and stock recovery to do ota
---------- Post added at 15:56 ---------- Previous post was at 15:53 ----------
If you reflashed stock firmware then you will have stock recovery and not twrp to find out reboot into your bootloader then use arrow keys until get to option saying recovery then select if its stock it will look abit like cwm but call android 3e recovery or something close to that if not it will boot into twrp
Click to expand...
Click to collapse
once upon a time I used to have HTC phone and I landed in same problem and learned things from there so what I shared is half true though
minidude2012 said:
It doesn't need bootloader relocked but you need stock rom(no Mods or root) and stock recovery to do ota
---------- Post added at 15:56 ---------- Previous post was at 15:53 ----------
If you reflashed stock firmware then you will have stock recovery and not twrp to find out reboot into your bootloader then use arrow keys until get to option saying recovery then select if its stock it will look abit like cwm but call android 3e recovery or something close to that if not it will boot into twrp
Click to expand...
Click to collapse
thanks for your fast replay
Thanks
arunhebbare said:
Hi, I have faced the same issue that you have faced. I will be resorting to flashing original STOCK ROM using the ADB commands.
There are other threads in this forum explaining the procedure.
Don't worry. If you follow the procedure correctly you will be able to reinstall the system and use your phone again.
After flashing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. Other wise you will face similar issue.
To go to fastboot mode from the blank screen mode you may follow the steps below:
1. Keep the power key pressed for a few seconds till you can see that the screen has gone completely black (otherwise you will see the screen dimly lit)
2. Immediately after this step press the volume down button first followed by power button and hold for a second or two and release the buttons, you would be in the fastboot mode
3. You can connect your phone to the PC in this mode to flash the STOCK ROM using the flash boot commands
4. You will find the STOCK ROM in the following link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
5. For installation procedure and fastboot commands refer this link:
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Hope this helps
Click to expand...
Click to collapse
Thanks bro.

bricked due to S3 vs. S4 CPU mixup?

I have an old HTC ONE S (z560e => S3 CPU as I now know).
1) I managed to unlock the boot loader (htcdev)
2) Probably managed to get root access (r3-ville-superboot was fast and error free)
3) However them "recovery install apps" (CWM, TWRP) still clamied they'd need root
access but "superuser or su are not to be found"; weird, considering success of 2)
4) hence I tried to flash twrp recovery manually via
Code:
fastboot.exe flash recovery twrp-3.0.0-0-ville.img
message was
Code:
sending 'recovery' (11896 KB)...
OKAY [ 2.078s]
writing 'recovery'...
OKAY [ 3.845s]
finished. total time: 5.931s
And that's it. won't boot anymore. I apparently got the S4 version of twrp-3.0...
Holding in power button for ~10 secs has it very shortly flash the screen and turn on the oragne LED for ~4 secs, then it's black again.
Any idea what went wrong?
Any chance how to save that situation?

screwed up when flashing twrp :(

wrong category..
see https://forum.xda-developers.com/oneplus-6/help/screwed-flashing-twrp-t3846690
please delete
@moderator. can you move my thread to OnePlus 6 Questions & Answers. I think it's in the wrong place.
R0ttenB4ndit said:
Alright so I screwed Up. I got in a rush and followed some guys advice in a thread for a different phone and not sure how to get back on track. Can someone help?
Heres what I did.....
Code:
G:\Downloads\oneplus 6 root\android p>fastboot flash recovery twrp-3.2.3-0-enchilada.img
target reported max download size of 536870912 bytes
sending 'recovery' (26744 KB)...
OKAY [ 0.569s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.577s
Nothing..... SO I googled and then typed this:
>>fastboot flash boot_b twrp-3.2.3-0-enchilada.img
Phone rebooted and showed twrp, cool. I restarted from there then, sh1t! Now I can't get back to twrp nor the os to follow the correct guide.
I tried holding power for 7 seconds - reboots and shows the red dot with white dots circling eternally
I tried holding volume down + power for 7 seconds - reboots and does the same thing
I tried holding volume up + power for 7 seconds - it goes into this all black recovery mode or something
Click to expand...
Click to collapse
You need to boot into fastboot and fastboot flash the stock boot.img from you PC. This should restore your stock boot and fix your issue.
hey @ajsmsg78. when i do adb devices through usb, it doesn't find it. it will keep booting to the red dot and spinning white dots around it. no recovery option appears on the phone. what mode do I have to be in for the pc to see it at this point?
Duplicate thread closed.

Categories

Resources