Database Users

[Help] My phone can log in to bootloader but can't start.

Few days ago, while charging I found my phone can't load any app. I tried to restart and it stuck at Nexus logo screen. I think I've got boot loop situation, so I rebooted in to bootloader mode and tried to flash it's stock rom following efrant's guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 but it failed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Has anyone faced the same problem and know how to fix it? I'm afraid the main board has crashed but I can still boot in to bootloader so I really confused.

hungtimb said:
Few days ago, while charging I found my phone can't load any app. I tried to restart and it stuck at Nexus logo screen. I think I've got boot loop situation, so I rebooted in to bootloader mode and tried to flash it's stock rom following efrant's guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 but it failed.
Has anyone faced the same problem and know how to fix it? I'm afraid the main board has crashed but I can still boot in to bootloader so I really confused.
Click to expand...
Click to collapse
Recovery to a stock ROM may cause your phone lock again, please ensure you phone is in unlock status first (you may see an unlocked padlock at the bottom of the screen after power on), and try flash the recovery again.

nabor said:
Recovery to a stock ROM may cause your phone lock again, please ensure you phone is in unlock status first (you may see an unlocked padlock at the bottom of the screen after power on), and try flash the recovery again.
Click to expand...
Click to collapse
You mean the bootloader?? yes, I have it unlocked. In fact, i've just locked it back and unlocked again. But it still unable to flash anything.

hungtimb said:
You mean the bootloader?? yes, I have it unlocked. In fact, i've just locked it back and unlocked again. But it still unable to flash anything.
Click to expand...
Click to collapse
Then try to flash the factory image, this will truly reset your phone:
https://developers.google.com/android/nexus/images
Hopping this will help you

nabor said:
Then try to flash the factory image, this will truly reset your phone:
https://developers.google.com/android/nexus/images
Hopping this will help you
Click to expand...
Click to collapse
Thanks, but that won't help either.

hungtimb said:
Thanks, but that won't help either.
Click to expand...
Click to collapse
Doesn't work? uh... I have no idea for now...

hungtimb said:
You mean the bootloader?? yes, I have it unlocked. In fact, i've just locked it back and unlocked again. But it still unable to flash anything.
Click to expand...
Click to collapse
Try to unlock it again,Install CWM and flash the original ROM into the machine.

Having and unlocked bootloader and not being able to flash the stock factory images is a bad sign. Usually it means a corrupted emmc chip. Can you send it to RMA?

Erovia said:
Having and unlocked bootloader and not being able to flash the stock factory images is a bad sign. Usually it means a corrupted emmc chip. Can you send it to RMA?
Click to expand...
Click to collapse
Forgot to remind 1 more thing,Lock before sending to RMA...

androidvillage said:
Forgot to remind 1 more thing,Lock before sending to RMA...
Click to expand...
Click to collapse
Jeez, a month late for that bit of information.
Sent from my Nexus 5 using XDA Free mobile app

Dead nexus 4?

Hi guys, this is my first time posting problems like these as I've never encountered anything I can't fix by myself or with help from fine developers and the community here, but now I'm desperate so I wanted to give it a shot.
Anyways here's what happened. My battery died, along with my USB port (the latter of physical damage - it's not burned just the port got damaged from usage I guess). Anyways, I got original replacement parts, put them in all good. And now when I plug in the charge cable, the LED briefly flashes green and after that nothing happens. However, I found out that if I hold power and volume down and plug in the USB cable then, bootloader turns on. It's interesting how the bootloader was marked as locked even though I unlocked it ages ago. Anyways, when I try to start it normally it shows the Google logo, and after a second or so, it shuts down completely (after the screen goes off, the green LED flashes again). I tried doing rebooting bootloader and recovery, same thing occurs. I tried using factory images and here's the weird/interesting part. When I manually flash the images from the latest 5.1.1 set, everything passes except when I tried doing fastboot flash data userdata.img . It downloads as it should, but it stops after the write part (it says that it can't flash a filesystem with type ' ' - Same goes for fastboot format and fastboot wipe and fastboot erase). However, when I use flash-all batch, it passes as it should (write phase included - or that's at least what it says), but still, the phone won't turn on. I can't do fastboot boot recovery.img as it gives the same result. I should note that I did try fastboot oem unlock, and it pops up the confirmation screen and all, and when I press yes, it works as it should, unlocks the bootloader (I know since when I booted into bootloader again, it showed that it's unlocked, and on the Google logo it shows the little symbol on the bottom), but shuts down on the Google logo again. Flashing any other custom made image (for example this http://dmitry.gr/index.php?r=06.+Thoughts&proj=02.%20Android%20M%20on%20Nexus4 Android M image) gives the same outcome. I really ran out of ideas and could appreciate any help or at least ideas on what could be broken on it so I can let it rest in peace.
Also might be noteworthy that my Ubuntu didn't recognize anything when I attached it in fastboot. As in nothing happened.
Here are screenshots of the fastboot output if someone's interested (ignore the red marking on the screenshot, it was for a friend ):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I think you flash the recovery the wrong way.
To flash via fastboot, this is the command:
fastboot flash recovery twrp-2.8.x.x-xxx.img
Source: http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
You tried to flash a recovery in the kernel location.
To flash a kernel via fastboot:
fastboot flash boot boot_name_img

dcop7 said:
I think you flash the recovery the wrong way.
To flash via fastboot, this is the command:
fastboot flash recovery twrp-2.8.x.x-xxx.img
Source: http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
You tried to flash a recovery in the kernel location.
To flash a kernel via fastboot:
fastboot flash boot boot_name_img
Click to expand...
Click to collapse
Yeah sorry those are typos, I came from work and I was tired as hell while I was posting this. If you are referring to the first screenshot, I wasn't flashing the recovery, I was simply trying to boot it off my PC without actually flashing it. Anyways, the recovery flash that I did afterwards was ok, as well as any other except for /data. I think that's the culprit, but it still wouldn't explain why the phone shuts down as soon as it tries to (at least to my understanding) load the kernel. Boot.img is ok, so that can't be the problem.

Hi,
Have you had any luck? I am having the exact same problem with my new battery and charging port replacement which are all genuine parts.
Thanks

[SOLVED] Can't boot, can't boot recovery, oem locked, usb debugging disabled

Happened when I was updating twrp:
I downloaded the .img from their website, booted into my older version of twrp, went to flashing pressed the butting in the bottom right corner, selected the file and selected 'recovery'
Said it was successful, so I rebooted, then it wouldn't do anything anymore except for fastboot.
1. Can't boot into recovery
2. Can't boot normally
3. USB debugging disabled
4. oem locked
Only thing I can enter is fastboot.
I followed this guide, but no luck on my end.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.

passion8059 said:
Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.
Click to expand...
Click to collapse
It's no use because oem is locked. That means I can't flash anything.

toolbox should still help you unlock bootloader again

Just use the Qualcomm factory restore image to return the phone to original shape of things.

passion8059 said:
toolbox should still help you unlock bootloader again
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pitrus- said:
Just use the Qualcomm factory restore image to return the phone to original shape of things.
Click to expand...
Click to collapse
I have no idea how I would do this without being able to flash anything.

Do you mean that the Qualcomm download program also crashes like fastboot? Sounds like you either have some problems with your windows installation or perhaps you haven't searched for and downloaded the Qualcomm restore if your still trying to flash the ordinary way instead of the emergency way.

Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys

Theevilsocks said:
Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys
Click to expand...
Click to collapse
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc

Redjax said:
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc
Click to expand...
Click to collapse
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.

Theevilsocks said:
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.
Click to expand...
Click to collapse
Literally JUST finished with this guide, and my OP2 is alive again! I was going to come back and post. Thanks for the link.
Anyone trying to use this guide without success:
There's one very important step I somehow missed. You MUST disconnect your phone, hold the power button for ~15-20 seconds until it's off, and hold the Volume+ button, THEN plug it back in. Your computer will make the "device connected" sound, but the screen will stay black. THIS IS OK! That means you're in a special recovery, which is where you need to be for the tool.
I also installed the certificate file in the folder I downloaded, then rebooted (it did not work before a reboot, but did work after).
So, the steps:
1. Download the files, make sure your signature signing for drivers is off.
2. Install the trusted certificate, then the driver.
3. Reboot PC
4. Power off phone (hold power for 15-20 secs), hold volume+, then connect through USB (wait for device connected sound, screen on phone will still be black)
5. Run the tool (I ran as admin, not sure if that's required)
6. Weep with joy that you finally found a solution that works.

Bricked my A2017G

Hello guys,
I tried to update my phone to Nougat and I guess I totally failed.
First I just tried to flash this rom: https://forum.xda-developers.com/axon-7/development/rom-purefusionos-official-t3670580 and it did not work. So I thought I might have to update the firmware first and installed the A2017UV1.1.0B32 NOUGAT Update from this thread: https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484. I found out I had to flash (with TWRP) the firmware's G version so I took the A2017G_N_Modem.zip from this https://androidfilehost.com/?w=files&flid=148464.
Now I only get the "your device software can't be checked for corruption. Please lock the bootloader".
Can somehow help me and tell me if and how I can get a rom working again?
Thanks in advance.

Check forum. There are topics to unbrick your device.

Yes, I read the forums. My Problem is that I cannot enter the EDL mode for example. When I git Power + Vol Up + Vol down nothing happen except a shot red LED.
EDIT: I cannot get into fastboot aswell.. Always that screen with lock your bootloader. Pretty much the only mode I can enter is recovery with TWRP.

multimill said:
Yes, I read the forums. My Problem is that I cannot enter the EDL mode for example. When I git Power + Vol Up + Vol down nothing happen except a shot red LED.
EDIT: I cannot get into fastboot aswell.. Always that screen with lock your bootloader. Pretty much the only mode I can enter is recovery with TWRP.
Click to expand...
Click to collapse
When led blinked you are on EDL mode. Screen is black on edl mode.

Yeah I got that an now i completely **** up -.-
I made it to go back to stock. I saw yeah got that B10 version now so I tried to flash PureFusionOS and Beans GApps. Now the screen is just black when I start the phone and my computer (and one other I tested) cannot flash the the edl version via Miflash because the phone is not recognized.
When I try to enter EDL the led is not blinking anymore. Its just showing red.

multimill said:
Yeah I got that an now i completely **** up -.-
I made it to go back to stock. I saw yeah got that B10 version now so I tried to flash PureFusionOS and Beans GApps. Now the screen is just black when I start the phone and my computer (and one other I tested) cannot flash the the edl version via Miflash because the phone is not recognized.
When I try to enter EDL the led is not blinking anymore. Its just showing red.
Click to expand...
Click to collapse
Do you see your device on Device Management? If yes, it is on edl mode. go on other steps
BTW, use this guide.

WesTD said:
Do you see your device on Device Management? If yes, it is on edl mode. go on other steps
BTW, use this guide.
Click to expand...
Click to collapse
Where should I see in the device manager?
EDIT: I do hear a sound when connecting. But I dont know where to find it in the device manager. In which category.
EDIT2: Well I see one device here, but neither the Axontool nor Miflash regonize it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

multimill said:
Where should I see in the device manager?
EDIT: I do hear a sound when connecting. But I dont know where to find it in the device manager. In which category.
EDIT2: Well I see one device here, but neither the Axontool nor Miflash regonize it.
Click to expand...
Click to collapse
Good luck. Your device on DFU Mode. There another guide about it.

multimill said:
Where should I see in the device manager?
EDIT: I do hear a sound when connecting. But I dont know where to find it in the device manager. In which category.
EDIT2: Well I see one device here, but neither the Axontool nor Miflash regonize it.
Click to expand...
Click to collapse
4th category brick repair manual, google it

POCO M3 System has been Destroyed [Lock State]

How u doing?
So, my Poco M3 was working perfectly until yesterday when I said YES to system update notification for MIUI 12.5 (such a dumb decision), now the system is dead...
I did see a lot of videos and I've already read some posts here, I tried to replicate all common solutions to resolve this problem but nothing works for me, because my bootloader is lock and i can't flash any rom in the locked state. I checked this methods to restore the system:
1 - I Downloaded the Mi flash latest version and the ADB drivers, but doesn't work because my phone is iin Lock State...
"Using Mi Flash this happen:
[09:27:04 57a4c2410720]:info1:$fastboot -s devicename erase boot ||
[09:27:04 57a4c2410720]:info2:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State')
[09:27:04 57a4c2410720]:info2:fastboot: error: Command failed
[09:27:04 57a4c2410720]:info1:"Erase boot error"
[09:27:04 57a4c2410720]:begin FlashDone
[09:27:04 57a4c2410720]:error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State')"
2 - So i tried to use Mi Flash Unlock, it didn't work and was showing "add your account in miui's settings developer options mi unlock status". the problem is that it all requires some prerequisite settings done already in the device (Mobile phone) when the only thing I can do it's acess fastboot screen. (Phone has never been unlocked before)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3 - I found another Mi app = Mi Flash Pro, same thing, it contais Fastboot to EDL Tool, but is no longer available by xiaomi.
4 - I also tried to install OrangeFox recovery and TWRP by CLI but it also failed cause is not allowed in lock state....
So, what can i do to save my phone when it's off and i cant acess anything right now?
(I even tried opening it and removing the battery)
Anyone can help me, pls !?

Unfortunately it doesnt work anymore.... Mi Phone Assistant and Mi PC Suite

DartagnanFS said:
Unfortunately it doesnt work anymore.... Mi Phone Assistant and Mi PC Suite
Click to expand...
Click to collapse
have you tried to erase the data with the recovery?

NOSS8 said:
have you tried to erase the data with the recovery?
Click to expand...
Click to collapse
it died with the system, Fastboot Screen it's the only thing that works.... as that pic shows

Hi all i have the same problem!

Jerri7 said:
Hi all i have the same problem! View attachment 5552511View attachment 5552513
Click to expand...
Click to collapse
You cant use Miflash with a locked bootloader.

NOSS8 said:
have you tried to erase the data with the recovery?
Click to expand...
Click to collapse
recovery not working... i tryied "fastboot reboot recovery"

Jerri7 said:
recovery not working... i tryied "fastboot reboot recovery"
Click to expand...
Click to collapse
and when you press power+volume up button what happen?

NOSS8 said:
and when you press power+volume up button what happen?
Click to expand...
Click to collapse
nothing, the same... show "system has been destroyed" with low vibrate and after 5sec its off and repeat ➜ show "system has been destroyed" with low vibrate and after 5sec its off and repeat... its in loop

Hi, i have this exact same problem, did you find a solution?

I can help you with that problem.

Owshiero said:
I can help you with that problem.
Click to expand...
Click to collapse
hi, how can you help? i still have the same problem

Owshiero said:
I can help you with that problem.
Click to expand...
Click to collapse
i have same issue how to fix this

https://forum.xda-developers.com/t/...en-destroyed-lock-state.4409321/post-86522403