Database Develop

[Q] No OS Nexus 6 on 5.1 update

I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!

How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ

lostnthought said:
I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!
Click to expand...
Click to collapse
Please provide more info. Stock or custom recovery?

Evolution_Freak said:
Please provide more info. Stock or custom recovery?
Click to expand...
Click to collapse
Custom Recovery.. TWRP v2.8.2

lostnthought said:
Custom Recovery.. TWRP v2.8.2
Click to expand...
Click to collapse
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.

DebianDog said:
How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
This may sound silly but I'm not 100% sure. A system notification had been on my screen for over two weeks saying that I had a system update to 5.1 and I finally decided to download and install said update and then it sent me to recovery mode. I don't know why I did but I hit fix permissions.. Just fiddling trying to figure everything out and this is where we are.

Evolution_Freak said:
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.
Click to expand...
Click to collapse
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock

lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
I'm not asking you to boot to recovery. Boot to bootloader.

lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
move a rom via a computer to your phone. either connect the recovery to your computer and move it, or connect to a computer and adb push it to your phone.

Sorry, I guess I misread your post. I thought you said can't get to recovery. From TWRP you should be able to enable MTP transfer. Then your PC should see it and you can transfer files as @simms22 suggested.

lostnthought said:
"No OS found."
Click to expand...
Click to collapse
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)

vormund said:
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)
Click to expand...
Click to collapse
you dont need adb to move anything to your phone when using twrp. just connect to twrp using the mtp option.

[Q] moto g 014 soft bricked

iam very sad to say you that my phone is bricked.i will change roms in my phone frequently.u always very careful but today when i was out for a work my brother tried to install the new hyperdrive rom but he had not taken any backup and he wiped all the memory including rom zip files so he stucked the phone in recovery(he dont know about ADB side load) then he ( he observed me when updating from kk to lp) searched the files in my computer then just tried to instal stock kitkat using command prompt Nd succced but when he found lollipop update file in the computer and he placed it in phone but when the phone is updating into lollipop the low battery in the phone made the phone dead.
when i came back home i saw all the mess he does now the phone whn switched on only shows android logo with error frequently but when i went into recovery mode to sideload the rom the the fastbot devices command shows device connected but msg displays error msg showing device not found when i tried to sideload the rom.
in TWRP it displays unable to mount data :crying:
unable to mount cache
when i tired to install using external sd card the installation completes but when rebbot the phone stucks on android exclamation logo showing errror msg
please help i dont my phone to be bricked:crying::crying:

Have you tried mounting from a usb otg ?

the problem is solved partially
oisink2014 said:
Have you tried mounting from a usb otg ?
Click to expand...
Click to collapse
i used TWRP and repaired the filesystems and installed the custom rom microkatv1.zip but the rom is installed succcessfully and i wipe cache/dalvik cache and reboot the phone it will shows motorola logo and automatically moves into TWRP.can anyone help me how to boot the phone normally is there any software or any commands to solve this please lead me to solution:crying:

i saved my phone
at last i had done some file repairs in TWRP and i got installed stock kk rom by ADB then i got my moto g back

sagaremperor said:
at last i had done some file repairs in TWRP and i got installed stock kk rom by ADB then i got my moto g back
Click to expand...
Click to collapse
I'm having a similar problem. Can you elaborate on what you mean by file repairs?

solution may work for you
Eogram said:
I'm having a similar problem. Can you elaborate on what you mean by file repairs?
Click to expand...
Click to collapse
Weird, even though for me it wasn't mountable either, reformatting worked.
I don't think adb will be able to mount it if it doesn't work in CWM. I guess one thing you could try is flash TWRP via sideload and then go to wipe, check all of the partitions, and then hit "repair filesystem". Might work, :fingers-crossed:
if not worked can you tell me whats actual is your problem:silly:

Locked bootloader and can't boot into ROM or Recovery. (Fixed!)

Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
EDIT: Got it resolved!
In order to get into Recovery I had to use the following commands in the bootloader:
fastboot format cache
fastboot format userdata
After doing this I was able to boot into recovery. However, recovery showed 0MB available storage and wouldn't mount /data, which prevented me from installing anything. It also wouldn't allow me to copy anything to the SD card using Android File Transfer or ADB sideloading.
To solve this I went into "Wipe" while in recovery and did a full format (the one that requires you to type "yes" before proceeding"
After doing this and booting back into recovery, I had full storage space back and recovery was able to mount /data. At this point I just copy/pasted the 5.1.1 ROM onto the sdcard with Android File Transfer. Once installed, I flashed the ROM and it booted right up.
I then skipped through the setup to get to settings and in developer settings I ticked the box to allow OEM unlocking. After doing that, I booted back into the bootloader and used the fastboot command "fastboot oem unlock" to unlock the bootloader again.
Once that was done I was able to use fastboot commands to flash the M preview all over again.
Hopefully you don't find yourself in this mess, but if you do, I'm hoping the above solution works for you.

sn0warmy said:
Well, I really did it this time. In my efforts of messing the the M Preview build and trying to eliminate the verification failed startup message I really locked up the phone. I locked the bootloader and now the phone will not boot into either recovery or the ROM. It won't let me "fastboot OEM unlock" the device either because it requires me to go into settings and check the allow OEM unlock. However, since I can't boot into the ROM, I cannot do that.
I'm really stuck here. Any ideas?
Click to expand...
Click to collapse
Hope you can RMA it

akellar said:
Hope you can RMA it
Click to expand...
Click to collapse
Well.... s**t.

sn0warmy said:
Well.... s**t.
Click to expand...
Click to collapse
Is TWRP installed?

WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?

I did something similar this past weekend while trying to do the 5.1.1 upgrade with the OTA files before the Factory images were available.
Try and use the WugFresh tool to wipe the cache and such, and try some of the other obvious settings in the tool.
It was late and I'm not 100% sure what I did but I do remember reflashing the LRX22C from the factory image using the tool. Everything I did was from the tool minus the 5.1 OTA that came through once I was able to get back into the device. From there I was able to unlock the bootloader again.
I was worried myself that I might have to send the phone back but I just kept trying, don't give up just yet. I've been told many times it's almost impossible to brick an android device now a days.
Good luck!

sn0warmy said:
WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?
Click to expand...
Click to collapse
Enable MTP in TWRP then drag n drop.

rootSU said:
Enable MTP in TWRP then drag n drop.
Click to expand...
Click to collapse
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?

sn0warmy said:
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?
Click to expand...
Click to collapse
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4

rootSU said:
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4
Click to expand...
Click to collapse
Success!
TWRP was also reporting 0mb available storage. I went into Wipe and performed a full format. Booted back into recovery and storage was showingt he full amount again. I was then able to plug the phone in and enable MTP and drag/drop the 5.1.1 ROM onto the SD card. Just flashed it and it booted right up!
I'm going to update the OP with all this info just in case someone else runs into the issue and needs help.
Thanks for your help!

sn0warmy said:
Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
Click to expand...
Click to collapse
Hi,
I faced the same condition like you experienced, with some differences:
- the phone stuck in "Google" logo
- stock recovery is accessible from bootloader
- I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
any ideas what to do next?
================ edited- add below info on how I got stuck
So my N6 was still on 5.0 (has not been updated to 5.1). I decided to try the M preview. I downloaded the preview, and began the process as follows:
1. reboot into bootloader
2. fastboot oem unlock
3. flash-all (success on loading the bootloader and radio, but error on updating the image)
4. hence i followed to flash individually:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
5. and comes the stupid thing ! --> fastboot oem lock (really really regret why I did this)
6. and then once reboot, it stuck in Google logo forever
However, I am still able to access:
- bootloader (fastboot recognize the device, but wouldn't allow me to fastboot oem unlock)
- able to go to stock recovery, and as mentioned above:
I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
I tried to adb sideload the M preview image and 5.1 LMY47I but both showing the above error....
hope you can shed some light on this...

Please does anyone have a solution to this? please help me

Iambenqazy said:
Please does anyone have a solution to this? please help me
Click to expand...
Click to collapse
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.

Strephon Alkhalikoi said:
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.
Click to expand...
Click to collapse
.
OK What i was trying to do was to flash a stock recovery, i start it by running the flash-it all.bat file in the factory image zip, it changed the user interface of the bootloader after first reboot and and had an error for "archive: recovery.sig not found" (something like). the phone status shows Software Version: Modified and fastboot oem unlock dont give the confirmation.
and
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:

If you can't even get into the bootloader (volume down and power) you may have to have the device serviced. Do you get a response when you type "adb devices"?

Iambenqazy said:
.
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:
Click to expand...
Click to collapse
Maybe it just crashed at a black screen? Does a very long press of the power button (over 10 secs) cause it to react?
Or maybe the battery is empty? Try connecting the power supply for some time.

i did that but no response.

Iambenqazy said:
i did that but no response.
Click to expand...
Click to collapse
The very dead battery is a real possibility. The thing is, using the charger that came with the phone isn't going to help. If you think the battery being dead is a possibility, you would need to plug the phone into a USB port on a PC, that is a very slow charge. Leave it on there overnight then unplug and replug. If the led at the top of the screen lights or the battery icon shows on the screen, you have hope. At this point using the original charger should get the battery going again. In this case, plan on replacing the battery.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

LG L Fino D290n makes error on boot.No download mode or recovery,please help!

Yesterday a LG L Fino was brought to me for repair.It makes an error on boot.The error is the boot certificate verify error.I cannot fix this!
I tried booting in recovery,gives me the boot screen,then the error,black screen.
I tried download mode,same.
I even tried flashing it,but LG Flash Tool does not recognize it.When i connect the phone a whole alphabet of drives would appear with LG Logos on them.I was able to only open one of them,the size was 64MB and it stored a image folder.Device manager recognizes the phone as QHSUSB_BULK and a ton of Unknown Devices would appear,after that they disappear and the phone will be recognized as LGE AndroidNet USB Serial Port(COM4).Thank you :angel:

filipkosteski said:
Yesterday a LG L Fino was brought to me for repair.It makes an error on boot.The error is the boot certificate verify error.I cannot fix this!
I tried booting in recovery,gives me the boot screen,then the error,black screen.
I tried download mode,same.
I even tried flashing it,but LG Flash Tool does not recognize it.When i connect the phone a whole alphabet of drives would appear with LG Logos on them.I was able to only open one of them,the size was 64MB and it stored a image folder.Device manager recognizes the phone as QHSUSB_BULK and a ton of Unknown Devices would appear,after that they disappear and the phone will be recognized as LGE AndroidNet USB Serial Port(COM4).Thank you :angel:
Click to expand...
Click to collapse
Will the device boot to fastboot? Does the device respond to adb commands?
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
Will the device boot to fastboot? Does the device respond to adb commands?
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Sorry i was inactive,but the LG L Fino is gone now i do not need help.Thank you

Droidriven said:
Will the device boot to fastboot? Does the device respond to adb commands?
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Hi, I have the same problem, here is the picture of my screen.
I have tried to follow these steps, but my phone cannot enter Secure boot mode.
Any idea what can I do?
thanks

ndr113 said:
Hi, I have the same problem, here is the picture of my screen.
I have tried to follow these steps, but my phone cannot enter Secure boot mode.
Any idea what can I do?
thanks
Click to expand...
Click to collapse
Hey there
I have a LG L90 D410 (Similar Qualcomm Device)
And I faced the same issue after a bad flash.
Did you flash anything?
Does the LG logo show up?
Please answer the above questions so I would be able to solve your problem

Gaptain4 said:
Hey there
I have a LG L90 D410 (Similar Qualcomm Device)
And I faced the same issue after a bad flash.
Did you flash anything?
Does the LG logo show up?
Please answer the above questions so I would be able to solve your problem
Click to expand...
Click to collapse
Hello sir!
I have never flash the phone. The first problem that I have seen was after one restart, it won't boot the os, I have seen the LG logo and after that it keeps reboots again. I have entered in recovery mode and wipe all data, but it didn't help. After that I started to see the message above(error) and that's all. My battery is completely empty and cannot charge it because the phone doesn't charge.

ndr113 said:
Hello sir!
I have never flash the phone. The first problem that I have seen was after one restart, it won't boot the os, I have seen the LG logo and after that it keeps reboots again. I have entered in recovery mode and wipe all data, but it didn't help. After that I started to see the message above(error) and that's all. My battery is completely empty and cannot charge it because the phone doesn't charge.
Click to expand...
Click to collapse
Hey there did you use advanced wipe to clear your data or was it factory reset.
If the LG Logo shows up and then the error comes then you can enter download mode by switching off the phone and then hold volume up key and at the same time insert a usb. You would enter download mode. If you enter the mode you can flash a KDZ
Gaptain4 here at your service :fingers-crossed:

Gaptain4 said:
Hey there did you use advanced wipe to clear your data or was it factory reset.
If the LG Logo shows up and then the error comes then you can enter download mode by switching off the phone and then hold volume up key and at the same time insert a usb. You would enter download mode. If you enter the mode you can flash a KDZ
Or If you want custom rom only,enter into recovery mode.
Then click wipe and then advanced wipe.
Check data
Check System
Check Dalvik/art
Check Cache.
And then Press install and download the suitable rom for you phone.
If you cannot resolve the problem contact me again
Gaptain4 here at your service :fingers-crossed:
Click to expand...
Click to collapse
No, they didn't use advanced wipe because they don't have a custom recovery installed. If you read their post more carefully, you'll see where they said that they never flashed the device, this means they have stock recovery, not custom recovery. None of what you posted helps them.
Sent from my LGL84VL using Tapatalk

Droidriven said:
No, they didn't use advanced wipe because they don't have a custom recovery installed. If you read their post more carefully, you'll see where they said that they never flashed the device, this means they have stock recovery, not custom recovery. None of what you posted helps them.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hey there thank for informing me.
He can still enter into download mode and flash kdz using flash tool
Custom Rom cannot be flashed
But a stock rom can be flashed and can be fixed.
Its a soft brick so he can surely flash a stock rom and recover his phone :fingers-crossed:\
When you try to charge your phone it doesn't show the charging status
But when you completely drain your battery to 0% it will show 0% and shows charging and you can confirm that it is charging

hi everyone
i have a LG L25
and i think i messed up flashing it using TWRP.
it stuck in FIRMWARE UPDATE screen and i cant access its TWRP mode
please help me

Marclance said:
hi everyone
i have a LG L25
and i think i messed up flashing it using TWRP.
it stuck in FIRMWARE UPDATE screen and i cant access its TWRP mode
please help me
Click to expand...
Click to collapse
Did you try to flash a stock update using TWRP?
If so, that is the problem. Stock updates can't be applied to a rooted device or a device that has TWRP installed, any one or both of these will interfere with applying the update. You can only apply stock updates to devices that have an unmodified system partition(no root, no Xposed) and have stock recovery, stock recovery is required for applying stock updates.
If this is what you did, your only option to fix this is to flash your full stock firmware. Do a Google search for:
"Return to stock (your model number)"
If the tools and files exist for your device, that should find it.
Sent from my LGL84VL using Tapatalk

TWRP failed to boot up

Hi guys~
so recently i was trying to flasha custom rom for my moto g5s plus and already unlock the bootloader, but when i flash the new twrp(3.2.0.1) and reboot to recovery mode this error comes up
Start up failed:
Your device didn't start up successfully.
Use the software repair assistant on computer
To repair your device.
Connect your device to your computer to get the software repair assistant.
IN RED - AP Fastboot flash mode (secure)
USB connected
.....
......
In red - failed to load kernel !
Boot up failed
Click to expand...
Click to collapse
so how to fix this guys? i already tried to do some research for my problem but its useless it was still not working
big thanks for you guys~

solved thx!

Could you possibly share how you fixed this?

Hymix said:
Could you possibly share how you fixed this?
Click to expand...
Click to collapse
First make sure you are using the right version for your build.. After you install it via fastboot, from there go to the recovery menu, up, down volume. When in there wipe data.. Some say factory reset, but I wiped data which did the same thing, and now it works.

help
doubledragon5 said:
First make sure you are using the right version for your build.. After you install it via fastboot, from there go to the recovery menu, up, down volume. When in there wipe data.. Some say factory reset, but I wiped data which did the same thing, and now it works.
Click to expand...
Click to collapse
Hello, I have the same problem when trying to start the TWRP, I want to try this solution but the Google Translator is bad and it is not understood. Can you explain it again please?

NelsonFa01 said:
Hello, I have the same problem when trying to start the TWRP, I want to try this solution but the Google Translator is bad and it is not understood. Can you explain it again please?
Click to expand...
Click to collapse
Install the Version of TWRP for your device. Use Fastboot boot twrp-x.x.x-x.img Twrp should boot into recovery automatically.. Once in there go to wipe>advanced wipe and wipe data only reboot.

TWRP recovery not boot
tart up failed:
Your device didn't start up successfully.
Use the software repair assistant on computer
To repair your device.
Connect your device to your computer to get the software repair assistant.
i have Moto 4g Plus please help
TWRP recovery not boot