Database Info

[Q] Nexus 5 Soft-Bricked ! Please Help :( (Locked Bootloader, Stock Recovery)

Hello Guys,
I'm now in deep deep trouble as my Nexus 5 has got soft bricked and now stuck in a bootloop. Yesterday evening i unrooted my device, flashed everything to stock and locked the bootloader back because i was getting a really awful battery life upon rooting. Hence thought of reverting to stock. So flashed the stock image of 4.4.2 and setup my phone just like it came from a factory. Only thing i did this time was disable some Google Apps i.e Play News, Games & Magazines, Movies etc. Till midnight it was working too good with only a marginal battery drain on idle i.e 1% in 2 hrs or so.
Today morning when i woke up, i just entered the PIN code and unlocked the homescreen and then it just got stuck. I restarted my device and since then, its just stuck in a bootloop and whenever the phone tries to restart the OS, its gives numerous errors all related to Play sErvices and something like android.process.acore and Media.
I tried to factory reset by going through the stock recovery but even in that it gives the errors " Failed to mount /cache" and "Failed to mount /cache/recovery" with invalid arguments in the brackets.
Now i can't even flash stock as the Bootloader is in Locked State. I'm able to flash unlock Bootloader but when it asks to restart "fastboot reboot", it again gets stuck on the Google Play services error resulting again in locked state. That leaves me with a LOCKED BOOTLOADER, STOCK RECOVERY & NO USB DEBUGGING ENABLED.
What can i do now to get my device working people ? Feel like :crying: since its happened. Moreover, i can't RMA it as I'm now in a different country from where the phone wasn't purchased.

BBThumbHealer said:
Hello Guys,
I'm now in deep deep trouble as my Nexus 5 has got soft bricked and now stuck in a bootloop. Yesterday evening i unrooted my device, flashed everything to stock and locked the bootloader back because i was getting a really awful battery life upon rooting. Hence thought of reverting to stock. So flashed the stock image of 4.4.2 and setup my phone just like it came from a factory. Only thing i did this time was disable some Google Apps i.e Play News, Games & Magazines, Movies etc. Till midnight it was working too good with only a marginal battery drain on idle i.e 1% in 2 hrs or so.
Today morning when i woke up, i just entered the PIN code and unlocked the homescreen and then it just got stuck. I restarted my device and since then, its just stuck in a bootloop and whenever the phone tries to restart the OS, its gives numerous errors all related to Play sErvices and something like android.process.acore and Media.
I tried to factory reset by going through the stock recovery but even in that it gives the errors " Failed to mount /cache" and "Failed to mount /cache/recovery" with invalid arguments in the brackets.
Now i can't even flash stock as the Bootloader is in Locked State. I'm able to flash unlock Bootloader but when it asks to restart "fastboot reboot", it again gets stuck on the Google Play services error resulting again in locked state. That leaves me with a LOCKED BOOTLOADER, STOCK RECOVERY & NO USB DEBUGGING ENABLED.
What can i do now to get my device working people ? Feel like :crying: since its happened. Moreover, i can't RMA it as I'm now in a different country from where the phone wasn't purchased.
Click to expand...
Click to collapse
I had the same problem.
just download this :
http://liciousroms.com/nexus5_restore.html
and do this instructions :
INSTRUCTIONS::
1) Download and install DRIVERS
2) Download and extract Nexus_5_KOT49H_Restore.zip,
3) Turn on your phone, and connect your phone to the computer (make sure you have USB Debugging enabled on the tablet)
4) Open up folder where you extracted the Nexus_5_KOT49H_Restore.zip
5) Double Click on the "Recovery_Nexus7.bat" and follow the instructions,,,,it really is that easy! (watch video and follow along)
6) If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power) and click the "Dead_Nexus5.bat" file found in the folder
2) Download and extract Nexus_5_KOT49H_Restore.zip,
3) Turn on your phone, and connect your phone to the computer (make sure you have USB Debugging enabled on the tablet)
4) Open up folder where you extracted the Nexus_5_KOT49H_Restore.zip
5) Double Click on the "Recovery_Nexus7.bat" and follow the instructions,,,,it really is that easy! (watch video and follow along)
6) If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power) and click the "Dead_Nexus5.bat" file found in the folder

^ I can't enable USB debugging as i'm unable to boot into OS.

Guys please HELP ! I'm only looking upto XDA to rescue me out. :crying:

BBThumbHealer said:
Guys please HELP ! I'm only looking upto XDA to rescue me out. :crying:
Click to expand...
Click to collapse
Hi! Check this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833.
Tapatalk-kal küldve az én Nexus 5-el

^ I can't enable USB debugging as i'm unable to boot into OS.
Click to expand...
Click to collapse
Read this:
6) If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power) and click the "Dead_Nexus5.bat" file found in the folder
Click to expand...
Click to collapse
And try suggested instruction. You don't even need to boot into OS.

Rip95 said:
Read this:
And try suggested instruction. You don't even need to boot into OS.
Click to expand...
Click to collapse
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?

BBThumbHealer said:
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
Click to expand...
Click to collapse
Go to the stock recovery and format cache.. Do it a couple of times till the /cache errors go away and then go to the bootloader and flash the stock factory images again. After flashing the stock images, don't boot it up, head over to the stock recovery and perform a factory reset and then reboot!

The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Click to expand...
Click to collapse
You can use command in fastboot "fastboot oem unlock" to unlock then reboot in fastboot again, and try this instruction (since you unlocked you should be able to do this).

BBThumbHealer said:
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
Click to expand...
Click to collapse
Here:
bitdomo said:
Hi! Check this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
(BTW you dont have to reboot after bl unlock.
fastboot oem unlock
then flash stock images iwhtout reboot)

What? USB Debugging doesn't have to be enabled. Bootloader unlocking is done from fastboot via 'fastboot oem unlock'.

bitdomo said:
Here:
(BTW you dont have to reboot after bl unlock.
fastboot oem unlock
then flash stock images iwhtout reboot)
Click to expand...
Click to collapse
Bitdomo tried you awesome tool which gave me a slight hope that could revive my Nexus but sadly it didn't :crying: Memory size is matched 32G but userdata erase fails and at last the Download FAIL error is there I just don't know what is preventing the Cache and User Data to erase. Same is the case in Stock Recovery as well.
Can you please get me a solution on this. Would be highly obliged :good:
GldRush98 said:
What? USB Debugging doesn't have to be enabled. Bootloader unlocking is done from fastboot via 'fastboot oem unlock'.
Click to expand...
Click to collapse

BBThumbHealer said:
Bitdomo tried you awesome tool which gave me a slight hope that could revive my Nexus but sadly it didn't :crying: Memory size is matched 32G but userdata erase fails and at last the Download FAIL error is there I just don't know what is preventing the Cache and User Data to erase. Same is the case in Stock Recovery as well.
Can you please get me a solution on this. Would be highly obliged :good:
Click to expand...
Click to collapse
unlock bootloader: fastboot oem unlock DONT restart
download twrp recovery
boot twrp recovery: fastboot boot path_to_twrp_recovery.img
wait until it boots up, if the phone restarts try again.
in wipe settings select format data type yes then ok, if it winished slide the bar to factory reset.
and in cmd terminal type: adb shell then cat /proc/partitions and post the a screenshot about that.

bitdomo said:
unlock bootloader: fastboot oem unlock DONT restart
download twrp recovery
boot twrp recovery: fastboot boot path_to_twrp_recovery.img
wait until it boots up, if the phone restarts try again.
in wipe settings select format data type yes then ok, if it winished slide the bar to factory reset.
and in cmd terminal type: adb shell then cat /proc/partitions and post the a screenshot about that.
Click to expand...
Click to collapse
Successfully unlocked bootloader finally and installed TWRP. Booted in TWRP and performed Data Wipe and it failed. Again unable to mount /cache /persist /data etc commands showed. Then it tried formatting using make_ext4fs function but it failed. Swiped for a factory reset and it failed.
Used your ADB command afterwards and it displayed first daemon started successfully on port 5037 and then error in cmd : device not found.
What next ?
EDIT : Just noticed on the TWRP screen that my internal storage space is being shown as Zero (0) MB Now does this means my flash storage has died ? If that's the case and i need to RMA it, how to relock the bootloader , reset tamper flag and load stock recovery so that google doesn't cause any warranty issues. Please help me in that case as well.
EDIT 2 : Using fastboot, tried flash stock cache.img and userdata.img, it failed. When i flash system.img it went through perfectly. Also, got to know that the steps which you mentioned earlier, TWRP was booted temporarily and bootloader was unlocked temporarily. So does this means i don't need to relock or flash back something ? And, if i've unlocked and relocked the bootloader numerous times, how do i reset tamper flag ?

BBThumbHealer said:
Successfully unlocked bootloader finally and installed TWRP. Booted in TWRP and performed Data Wipe and it failed. Again unable to mount /cache /persist /data etc commands showed. Then it tried formatting using make_ext4fs function but it failed. Swiped for a factory reset and it failed.
Used your ADB command afterwards and it displayed first daemon started successfully on port 5037 and then error in cmd : device not found.
What next ?
EDIT : Just noticed on the TWRP screen that my internal storage space is being shown as Zero (0) MB Now does this means my flash storage has died ? If that's the case and i need to RMA it, how to relock the bootloader , reset tamper flag and load stock recovery so that google doesn't cause any warranty issues. Please help me in that case as well.
EDIT 2 : Using fastboot, tried flash stock cache.img and userdata.img, it failed. When i flash system.img it went through perfectly. Also, got to know that the steps which you mentioned earlier, TWRP was booted temporarily and bootloader was unlocked temporarily. So does this means i don't need to relock or flash back something ? And, if i've unlocked and relocked the bootloader numerous times, how do i reset tamper flag ?
Click to expand...
Click to collapse
Read the stickies in the general section.. It will tell you how to reset the tamper flag.
- Sent from an IceCold Hammerhead!

BBThumbHealer said:
Successfully unlocked bootloader finally and installed TWRP. Booted in TWRP and performed Data Wipe and it failed. Again unable to mount /cache /persist /data etc commands showed. Then it tried formatting using make_ext4fs function but it failed. Swiped for a factory reset and it failed.
Used your ADB command afterwards and it displayed first daemon started successfully on port 5037 and then error in cmd : device not found.
What next ?
EDIT : Just noticed on the TWRP screen that my internal storage space is being shown as Zero (0) MB Now does this means my flash storage has died ? If that's the case and i need to RMA it, how to relock the bootloader , reset tamper flag and load stock recovery so that google doesn't cause any warranty issues. Please help me in that case as well.
EDIT 2 : Using fastboot, tried flash stock cache.img and userdata.img, it failed. When i flash system.img it went through perfectly. Also, got to know that the steps which you mentioned earlier, TWRP was booted temporarily and bootloader was unlocked temporarily. So does this means i don't need to relock or flash back something ? And, if i've unlocked and relocked the bootloader numerous times, how do i reset tamper flag ?
Click to expand...
Click to collapse
You could try one more thing. Format the /presist partition, For some reason it magically fixed other's devices, like for this guy and for an other in that same thread, but if you format it you will lose your wifi and bluetooth mac address, and some kind of DRM stuff. I made a tutorial how to fix wifi and bluetoot mac address problem after the formating, but I cant tell anything about the drm kind of files, because I still didnt get answers form the guys in that thread. That could mean they are experiencing no problems. Here is the zip which formats persist partition.

BBThumbHealer said:
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
Click to expand...
Click to collapse
please quote for me to the next time.
just run "Dead_Nexus" and it's will do all the whole thing though the bootloader...

Aviatar2 said:
please quote for me to the next time.
just run "Dead_Nexus" and it's will do all the whole thing though the bootloader...
Click to expand...
Click to collapse
I tried all sort of things before finally giving up. Ultimately sent the device for RMA. Thanks for your inputs as well
@bitdomo, i have realised it was a case of dead memory chip only. I managed to relock the bootloader and reset the tamper flag (oem device info showed Tamper as "false") but now my only cause of concern is the LG Flash Tool. When i flashed the KOT9H firmware, it changed the original device version as mine came with 4.4 OOTB instead of 4.4.2. Can Google refuse the RMA citing this now ? Rest all, the kernel, recovery, bootloader, tamper flag is all stock. I coudn't even change that back to the original device version as i couldn't transfer any zip to the internal storage as it was dead.

BBThumbHealer said:
I tried all sort of things before finally giving up. Ultimately sent the device for RMA. Thanks for your inputs as well
@bitdomo, i have realised it was a case of dead memory chip only. I managed to relock the bootloader and reset the tamper flag (oem device info showed Tamper as "false") but now my only cause of concern is the LG Flash Tool. When i flashed the KOT9H firmware, it changed the original device version as mine came with 4.4 OOTB instead of 4.4.2. Can Google refuse the RMA citing this now ? Rest all, the kernel, recovery, bootloader, tamper flag is all stock. I coudn't even change that back to the original device version as i couldn't transfer any zip to the internal storage as it was dead.
Click to expand...
Click to collapse
Google can't get your actual device factory version, because it is only visible with lg flashtool, and that tool is an internal lg software. Google has nothing to with that tool.
By the way this lgfalsh tool makes your phone offical, because this is the offical tool used in LG service centres!!!!
Can you imagine a guy at google who takes your phone flashes a custom recovery, reads back the misc partition and search for the factory device version in the hex code. Then he checks your phone serial number and sees 310K then denies your rma request because your device factory version cant be that because in oktober 2013 there were no 4.4.2? I think no.
But if it bothers you then, you can flash krt16m, or if your nexus 5 had to do big update ~150 mb ota update then flash kfs78n if your device is D821 or flash kqs81m if your device is D820. Converted roms work too without problems I have tested them.

bitdomo said:
Google can't get your actual device factory version, because it is only visible with lg flashtool, and that tool is an internal lg software. Google has nothing to with that tool.
By the way this lgfalsh tool makes your phone offical, because this is the offical tool used in LG service centres!!!!
Can you imagine a guy at google who takes your phone flashes a custom recovery, reads back the misc partition and search for the factory device version in the hex code. Then he checks your phone serial number and sees 310K then denies your rma request because your device factory version cant be that because in oktober 2013 there were no 4.4.2? I think no.
But if it bothers you then, you can flash krt16m, or if your nexus 5 had to do big update ~150 mb ota update then flash kfs78n if your device is D821 or flash kqs81m if your device is D820. Converted roms work too without problems I have tested them.
Click to expand...
Click to collapse
I have already sent the defective one for RMA so there's no question of flashing any files now. Google sends the new replacement device and and lieu of that they block temporarily the device's price for a period of 14-21 days in which the service centre ppl check for the issues what got the device in. And i think LG only is handling that as it made the device ? So my question still remains now can the LG guys intimate Google that the phone was flashed. ? But on the positive, the flash tool was of LG and it can't be turned unofficial What say ? I don't wish to pay again for a new device. If the service centre guys gives a thumbs up that phone indeed died as a result of hardware failure like emmc chip, then the card block is removed.
BTW, i am not aware whether Google itself handles the service or asks LG to do the same! Any inputs ?

[Q] Can't boot, recovery keeps dissapearing

I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.

aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
@bitdomo might be able to help you lol
Might be bad eMMC or something?

when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?

aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress

simms22 said:
when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?
Click to expand...
Click to collapse
Hey I'm using "fastboot flash recovery recovery.img" and that's what I've used in the past. I've had a fully functioning rom with fully functioning recovery for a while until yesterday.

bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok thanks I'll try this and check the text in fastboot after work today. Thanks for the responses guys.
After reading some more last night I'm afraid it's an emmc problem but I like to be proven wrong sometimes.

Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447

beekay201 said:
Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447
Click to expand...
Click to collapse
I actually have that thread open on my computer. It was my next attempt of repair before starting the thread late last night. Thanks for the suggestion I will certainly try it.
Update: I tried pushing Philz recovery to the phone which seemed to work fine until I selected go to recovery mode. It just went back to that barely light black screen. I'll try again when I get home. Going to try Bitdomo's advice about locking bootloader first.

bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Out of curiosity what's the reason for using two brands, or were they just available so they were used?

bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Bitdomo I'm trying the Flashtool but it's staying at 0% on the firmware update and nothing is popping up on computer or in Device Manager. Had no connection issues prior to the brick or with adb/fastboot. My Ports aren't evening showing at all in DM even if I select show hidden devices.

aburn95 said:
How do I lock the bootloader without being able to put the .zip on my internal memory?
Click to expand...
Click to collapse
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I honestly wanted to do that but it seemed too easy. I was trying to lock it like I did before when i had to send original back to T-Mobile. Sorry and thanks.

bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok so it stayed locked so that's a start. I'm back in download mode again but it's staying at 0% and nothing on computer.

I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:

Unzip the zip and use manual flash commands. Clikc the link in my signature and read my "adb and fastboot. What is it?" thread of you're unsure of the commands.
Sent from my Nexus 5 using Tapatalk

aburn95 said:
I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:
Click to expand...
Click to collapse
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB

bitdomo said:
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB
Click to expand...
Click to collapse
Sorry I meant to tell you yesterday... D820H 16GB. Should I still be able to toggle the tamper tag so they will take it back with no problems? Or am I screwed?

aburn95 said:
Sorry I meant to tell you yesterday... 820H. Should I still be able to toggle the tamper so they will take it back with no problems? Or am I screwed?
Click to expand...
Click to collapse
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.

bitdomo said:
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.
Click to expand...
Click to collapse
Ok thanks. I haven't quite figured out the adb sideload function yet. I tried doing it through TWRP but it just sits there and does nothing after selecting. Maybe I'm trying the wrong thing. I got my phone from T-Mobile so I'll need to solve this. Thanks for the help.

This phone is being a real a-hole. I'm trying to boot to stock recovery but it just sits on a screen with a really big android with wiggling antennae. I pressed up+power many times but it stayed that way. So I tried booting to TWRP again and it did but went immediately to an "OpenRecoveryScript," had a little bar at the bottom for a while with some other stuff on the screen, then turned off.
I tried stock recovery again and it went to the little dead android this time but still nothing when I press up+power.

Oneplus has no OS installed.

Hello all
I have a baaaaad situation going on!
I have been trying to delete me superuser in twrp, but something terrible happened....
1) When i boot my 1+ it just stays black.
2) When i boot into fastboot it just shows a linux penguin logo and noting else.
3) When i go to twrp i can do multiple things like adb sideload, and i can push a rom to my phone.
-> but everytime i do this and try to install it, it just fails and says i have no OS installed when i want to reboot.
I've contacted support from 1+ but nothing yet so far...
Anyone here who can help me? (i'm open for teamviewer and even want to pay the person who can fix my Oneplus)
Hoping one of you can help me!
Greetz
Michel
(I have a picture of the logo but i can't post i due to beiing a new member here )

You can't communicate with your phone through fastboot and ADB? Oh ****...

How did you manage to replace the bootloader with a Linux penguin? When you go into fast boot and type does fast boot devices does the pc recognize the phone?
Sent from my One A0001 using Tapatalk

The thing is, i was rooting my device and after i've done that my rootchecker told me the root was incomplete...
So smart as i was i started a complete unroot, to do it all over again...
In this process my device got stuck... so i booted in TWRP recovery to uninstall everything from the root over there..
Here i managed to delete my complete OS.... 8-|
After reading every tutorial and guide i figured out that on my phone my developper otions were NOT enabled...
So i contacted the oneplus support, who even remotely connected to my computer from Beijing to Belgium.. but never the less my problem was not solved and i was still stuck on the f*cking Linux logo...
So i started searching for a flashable ROM (in this case i found Pacman Nightly Signed) to flash on my phone through command on Windows.
After many hours and even more attempts i managed to go in adb en flash it by the sideload way.
So not through "adb push romname.zip /sdcard...." but by "adb sideload romname.zip /sdcard...."
And the pacman rom started to install and booted my phone to language selection...
PS: i cried :cyclops:

Glad to hear that you fixed your phone. I wouldn't contact oneplus support for things like this, chances are you'll get a reply back from xda faster as well as searching on your own to resolve the issue.
Sent from my One A0001 using Tapatalk

OnePlus One no OS, no Charge and that stupid lunix penguin
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:

Ashleigh.17 said:
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:
Click to expand...
Click to collapse
Fast boot flash a TWRP image. Flash CM12 nightly via OTG. You will be good from there.
Hastily spouted for your befuddlement

Ashleigh.17 said:
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:
Click to expand...
Click to collapse
More info required. What recovery do you have installed? Exactly what error are you getting when flashing the ROMs? You probably just need to flash the right firmware first.
Transmitted via Bacon

timmaaa said:
More info required. What recovery do you have installed? Exactly what error are you getting when flashing the ROMs? You probably just need to flash the right firmware first.
Transmitted via Bacon
Click to expand...
Click to collapse
I'm using TWRP
When I did manage to push some files to the device and tried to install them it failed instantly. I tried Cyan Hacker V2 the new Oxygen os and cm-11 and one of my backups, but all of them had the same issue. I can only vaguely remember the command which I think said 'partitions updating' then under the completed tab at the top of the screen in Red text it said failed.
This isn't my main concern anymore the device has died and won't charge so I can't get it to boot into fast boot or Recovery all its done when connected to the charger is light up with a black screen, vibrate then turn off, it repetats that a couple of times then it goes off again and no life at all, if I leave it of the charger for bit and try plugging it in again I get the same flashing black screen but again no charge.
---------- Post added at 10:09 AM ---------- Previous post was at 09:58 AM ----------
Coug76 said:
Fast boot flash a TWRP image. Flash CM12 nightly via OTG. You will be good from there.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
I'm having an issue gettjngit into fastboot its died and all I'm getting is a black flashing screen!
Any tips on how to get it to charge?

Ashleigh.17 said:
I'm using TWRP
When I did manage to push some files to the device and tried to install them it failed instantly. I tried Cyan Hacker V2 the new Oxygen os and cm-11 and one of my backups, but all of them had the same issue. I can only vaguely remember the command which I think said 'partitions updating' then under the completed tab at the top of the screen in Red text it said failed.
This isn't my main concern anymore the device has died and won't charge so I can't get it to boot into fast boot or Recovery all its done when connected to the charger is light up with a black screen, vibrate then turn off, it repetats that a couple of times then it goes off again and no life at all, if I leave it of the charger for bit and try plugging it in again I get the same flashing black screen but again no charge.
Click to expand...
Click to collapse
Yep, it's almost definitely a case of not having flashed the right firmware after coming from Oxygen. Leave it plugged in for eight hours, don't touch it in that time, then try to power it on again.
Transmitted via Bacon

timmaaa said:
Yep, it's almost definitely a case of not having flashed the right firmware after coming from Oxygen. Leave it plugged in for eight hours, don't touch it in that time, then try to power it on again.
Transmitted via Bacon
Click to expand...
Click to collapse
Okay I'll leave it through the day. After I get it to charge how will I get an OS onto it and how will I ensure that its got the right firmware? And if it all goes caput is this a valid reason for a renewed device from oneplus?

Ashleigh.17 said:
Okay I'll leave it through the day. After I get it to charge how will I get an OS onto it and how will I ensure that its got the right firmware? And if it all goes caput is this a valid reason for a renewed device from oneplus?
Click to expand...
Click to collapse
If you want to flash a Lollipop ROM the best way is to first perform a full wipe (system, data, cache, dalvik cache) in TWRP, then flash this firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFdVgxZ0x5RzNJSE0/edit?usp=docslist_api
Then flash this modem:
https://docs.google.com/file/d/0B98G0KTJwnBFU0Z1TUIyVE50WW8/edit?usp=docslist_api
Then go to the reboot menu and reboot back to recovery. Then flash whatever Lollipop ROM you want to use, and reboot your phone. If you still have no success after doing that then you'll need to try to flash the stock images with fastboot, I have a download and instructions in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
If that gets your phone booting then you can go ahead and try the above steps again to flash a Lollipop ROM.
No, this wouldn't be covered by warranty. Unlocking the bootloader and rooting this device doesn't void the warranty but they've stated that if you brick the phone while flashing (or the like) then it isn't covered. This is a case of user error, you didn't ensure that you had the correct firmware before flashing.
Transmitted via Bacon

timmaaa said:
If you want to flash a Lollipop ROM the best way is to first perform a full wipe (system, data, cache, dalvik cache) in TWRP, then flash this firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFdVgxZ0x5RzNJSE0/edit?usp=docslist_api
Then flash this modem:
https://docs.google.com/file/d/0B98G0KTJwnBFU0Z1TUIyVE50WW8/edit?usp=docslist_api
Then go to the reboot menu and reboot back to recovery. Then flash whatever Lollipop ROM you want to use, and reboot your phone. If you still have no success after doing that then you'll need to try to flash the stock images with fastboot, I have a download and instructions in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
If that gets your phone booting then you can go ahead and try the above steps again to flash a Lollipop ROM.
No, this wouldn't be covered by warranty. Unlocking the bootloader and rooting this device doesn't void the warranty but they've stated that if you brick the phone while flashing (or the like) then it isn't covered. This is a case of user error, you didn't ensure that you had the correct firmware before flashing.
Transmitted via Bacon
Click to expand...
Click to collapse
okay
thank you for all your help hopefully I'll be posting later with some good news

So I have gained access to the device in both TRWP and fastboot mode but I have encountered more problems,
Theirs is no OS, but their is a recovery the logical thing here would be boot it in fast boot and push files to the device and install those using the recovery easy right!!
no the boot loader is locked and so I can't flash anything I've downloaded about 2 or 3 tools kits to get it unlocked, when I use them the device reboots but wont load into fastboot, I can get it to with some tampering it doesn't have an exact method
any ideas guys?

Ashleigh.17 said:
So I have gained access to the device in both TRWP and fastboot mode but I have encountered more problems,
Theirs is no OS, but their is a recovery the logical thing here would be boot it in fast boot and push files to the device and install those using the recovery easy right!!
no the boot loader is locked and so I can't flash anything I've downloaded about 2 or 3 tools kits to get it unlocked, when I use them the device reboots but wont load into fastboot, I can get it to with some tampering it doesn't have an exact method
any ideas guys?
Click to expand...
Click to collapse
Why did you lock your bootloader? You need to go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Flash that through TWRP and your bootloader will be unlocked again.
PS. You can't push files to the device in fastboot mode, only adb can push files and adb doesn't work in fastboot mode. Once you've unlocked your bootloader again you'll need to flash the stock images with fastboot. Download and instructions are in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon

timmaaa said:
Why did you lock your bootloader? You need to go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Flash that through TWRP and your bootloader will be unlocked again.
PS. You can't push files to the device in fastboot mode, only adb can push files and adb doesn't work in fastboot mode. Once you've unlocked your bootloader again you'll need to flash the stock images with fastboot. Download and instructions are in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
You HERO!!!!!!!!!!!!!!!!!!!
I actually love you right now thank you so much

Ashleigh.17 said:
You HERO!!!!!!!!!!!!!!!!!!!
I actually love you right now thank you so much
Click to expand...
Click to collapse
Lol, no worries, glad to help.

timmaaa said:
Lol, no worries, glad to help.
Click to expand...
Click to collapse
This is better than the best soapserie
....
Is he going to make it?
Yes
Great! :good:
Oooooh nooooo!!!
He's got a locked bootloader
Damn F*ING
This will never turn out right
OH, look here comes @timmaaa again
He says what? :silly:Really is it possible
Yes YES YYEEEEESSS
I did it, it's working again
I loooove you
:highfive::highfive::highfive:

I have similar issues at the moment. I tried to flash over Oxygen OS and it kept failing. Upon factory wiping the current OS to put CM 12 Nightly, I accidentally deleted all of my data. Now 54,xxx MB is on my phone, meaning it wiped all internal memory, the system is only 20MB and data is 6MB. I tried to plug in my phone to fast boot mode, and my computer wouldn't read it. I did all I could to maybe get it to read, and not a single thing popped up. I do not believe my bootloader is locked, but there could be a possibility that it could. Any suggestions to get an OS pushed over through ADB or Fastboot??

ElmoRapz said:
I have similar issues at the moment. I tried to flash over Oxygen OS and it kept failing. Upon factory wiping the current OS to put CM 12 Nightly, I accidentally deleted all of my data. Now 54,xxx MB is on my phone, meaning it wiped all internal memory, the system is only 20MB and data is 6MB. I tried to plug in my phone to fast boot mode, and my computer wouldn't read it. I did all I could to maybe get it to read, and not a single thing popped up. I do not believe my bootloader is locked, but there could be a possibility that it could. Any suggestions to get an OS pushed over through ADB or Fastboot??
Click to expand...
Click to collapse
It looks like you did the same thing that I did.
Its a pretty easy fix your going to be able to avoid all of the unlocking boot loader issues I had.
To begin with when your try an turn the device on is the screen flashing black?

Soft bricked shield tablet PLEASE HELP!

So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.

okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?

Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?

Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader

Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"

danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha

Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.

Okay will try that. Thanks man.

Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5

Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?

Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader

Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.

Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.

Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5

Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?

Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.

koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?

Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?

Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.

koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader

Moto G3 boots into recovery every time I power on device

I have unlocked my bootloader. Every time I power on my Motorola Moto G3, it boots into the recovery screen. It isn't really a problem, it's more of an annoyance. I have to use the power / volume buttons to choose start and then it boots into the OS fine.
Any help would be greatly appreciated, thanks.

ItsWoffles said:
I have unlocked my bootloader. Every time I power on my Motorola Moto G3, it boots into the recovery screen. It isn't really a problem, it's more of an annoyance. I have to use the power / volume buttons to choose start and then it boots into the OS fine.
Any help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
Look at this thread
https://forum.xda-developers.com/2015-moto-g/help/reboot-bootloader-mode-t3653547

melp57 said:
Look at this thread
https://forum.xda-developers.com/2015-moto-g/help/reboot-bootloader-mode-t3653547
Click to expand...
Click to collapse
Do I need to type in fastboot oem fb_mode_clear while re flashing stock firmware again like I would to relock the bootloader?

ItsWoffles said:
Do I need to type in fastboot oem fb_mode_clear while re flashing stock firmware again like I would to relock the bootloader?
Click to expand...
Click to collapse
Actually it's not an issue, the command
Code:
fastboot oem fb_mode_set
makes the phone boot into bootloader mode instead of starting android. To undo this, you'll just have to type in-
Code:
fastboot oem fb_mode_clear
. No need to flash the whole firmware again if this is the only problem.
Broadcasted from Zeta Reticuli

Gravemind2015 said:
Actually it's not an issue, the command
Code:
fastboot oem fb_mode_set
makes the phone boot into bootloader mode instead of starting android. To undo this, you'll just have to type in-
Code:
fastboot oem fb_mode_clear
. No need to flash the whole firmware again if this is the only problem.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Where do I type this command in? Using ABD and fastboot? Do I just go into the bootloader and plug my phone into my PC, then open up ABD and fastboot and type in that command or what do I do? Is that the only command I need to type in? Sorry, I'm a noob to this kinda stuff!

ItsWoffles said:
Where do I type this command in? Using ABD and fastboot? Do I just go into the bootloader and plug my phone into my PC, then open up ABD and fastboot and type in that command or what do I do? Is that the only command I need to type in? Sorry, I'm a noob to this kinda stuff!
Click to expand...
Click to collapse
Reboot the phone into bootloader mode. To do this, power off the phone, press and hold power+volume down button till it shows up.
Plug the phone into PC, open command prompt from the folder where adb.exe and fastboot.exe are present, and type that command (only that one is needed). Disconnect the phone and try rebooting to see if it boots correctly.
Broadcasted from Zeta Reticuli

ItsWoffles said:
I have unlocked my bootloader. Every time I power on my Motorola Moto G3, it boots into the recovery screen. It isn't really a problem, it's more of an annoyance. I have to use the power / volume buttons to choose start and then it boots into the OS fine.
Any help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
I think u flashed recovery to boot..

mg_jishad said:
I think u flashed recovery to boot..
Click to expand...
Click to collapse
If that was the case, you could never boot the phone into Android... the OP stated that he can select continue and start the device normally. It is most likely stuck in fastboot fb_mode like @Gravemind2015 stated.

Excuse any possible miss posting of My question.
Moto G 3 factory rom and rooted
Problem: Motorola security update action causes Moto to keep booting into twrp recovery loop.
Have tried to break the looping, but there is something I am missing or not doing correctly any help thanks.....

Uncle Waldo said:
Excuse any possible miss posting of My question.
Moto G 3 factory rom and rooted
Problem: Motorola security update action causes Moto to keep booting into twrp recovery loop.
Have tried to break the looping, but there is something I am missing or not doing correctly any help thanks.....
Click to expand...
Click to collapse
Now this sounds like you flashed TWRP in your boot image... Reflash the stock boot image with fastboot

acejavelin said:
Now this sounds like you flashed TWRP in your boot image... Reflash the stock boot image with fastboot
Click to expand...
Click to collapse
Shouldn't that make the phone stay at bootlogo as the kernel and ramdisk are overwritten by TWRP code? @Uncle Waldo stated that the phone is looping into TWRP after *moto update action*. So what I am able to figure out is that this is a OTA-on-stock-rom-with-custom-recovery situation. I am a litte doubtful though as google says the phone boots into kernel from recovery (which is evident here) instead of kernel from boot partiton (source), so you may be 100% correct here too
@Uncle Waldo : If that is indeed the case (i.e moto issued an update and since rebooting the phone it's just looping into TWRP and giving an error) then I'd recommend that-
Flash stock boot.img as @acejavelin suggested
Flash stock recovery.img (as TWRP can't nstall stock ROM updates)
This is assuming that the /system partition was never modified in any way. If the update still fails in stock revovery, I'd guess that the whole system has to be restored to a non-modified state (i.e flashing the full firmware). You can try flashing all without doing the 'fastboot erase' part though, but i'd recommend you to backup your files using TWRP when you can.
links-
Link to the flashing guide is here
Link to the firmware index is here
command to install recovery -
Code:
fastboot flash recovery recovery.img
command to flash boot.img-
Code:
fastboot flash boot boot.img

Uncle Waldo said:
Excuse any possible miss posting of My question.
Moto G 3 factory rom and rooted
Problem: Motorola security update action causes Moto to keep booting into twrp recovery loop.
Have tried to break the looping, but there is something I am missing or not doing correctly any help thanks.....
Click to expand...
Click to collapse
If it is because of an update, you can't accept it while on TWRP... If you did, try to access the TWRP menu and if you can't boot TWRP from.fadtboot (not flash) and wipe caches... It should boot normally after that.

ACE; moto has been operating for sometime now fine
acejavelin said:
Now this sounds like you flashed TWRP in your boot image... Reflash the stock boot image with fastboot
Click to expand...
Click to collapse
You believe this could be my problem as the moto boots just fine and it's only started this problem when I installed the following update.
Motorola > android security updates version 24.211.14.en.US
After this install and reboot it appears to work just fine and then shortly reboots into TWRP from here the only correcting action that stops the reboot loop is "RESTORE".
After restoring and reboot the moto is back to operating as before and at some point I get the same message to install the security updates and the dance begins anew.
If reflashing the stock boot image via fastboot could correct my problem > then I am all ears Ace, as it's been sometime since I ventured into android ville and any help in this matter thanks...

Uncle Waldo said:
You believe this could be my problem as the moto boots just fine and it's only started this problem when I installed the following update.
Motorola > android security updates version 24.211.14.en.US
After this install and reboot it appears to work just fine and then shortly reboots into TWRP from here the only correcting action that stops the reboot loop is "RESTORE".
After restoring and reboot the moto is back to operating as before and at some point I get the same message to install the security updates and the dance begins anew.
If reflashing the stock boot image via fastboot could correct my problem > then I am all ears Ace, as it's been sometime since I ventured into android ville and any help in this matter thanks...
Click to expand...
Click to collapse
You edited the original question after I replied... Read my follow-up answer. You can't take an OTA with TWRP installed, just start TWRP and wipe caches and then don't accept any further OTA.

Ace; I missed that one
acejavelin said:
You edited the original question after I replied... Read my follow-up answer. You can't take an OTA with TWRP installed, just start TWRP and wipe caches and then don't accept any further OTA.
Click to expand...
Click to collapse
Your correct I missed that one, a BC moment (before coffee) sorry.
Okay in the fog of my memory I do now remember the OTA prohibition as I said it's been a piece of time.
I've done as instructed and all is well again, but will this nag screen appear again as it has done.
Question > How do I shut the motorolia OTA update off, so I don't get their stupid never ending nag screen everytime that I look at phone?
Thanks for your help...
---------- Post added at 05:13 PM ---------- Previous post was at 04:33 PM ----------
Ace I figured it out thanks for all your help...