[Q] I brick my nexus, need help - Nexus 5 Q&A, Help & Troubleshooting

Hello everyone.
Yesterday I tried to flash my nexus to f2fs. After that I wanted to go back to the stock, but forgot format filesystem to ext4 and run flash_all.bat.
Flashing was stopped on system write with error: "Unknown chunk type". After that i can't open recovery or turn on phone.
On 4pda i read, that bootloader reopen can help fix this problem.
When I flash new boot, nexus was died.
Can you help me?

Hi,
Please provide a link to exactly what you've flashed? Can you access the bootloader?

i flash google original rom
no, i haven't access to bootloader

no-tactic said:
i flash google original rom
no, i haven't access to bootloader
Click to expand...
Click to collapse
you need to put your device in fastboot mode, keep retrying
then to go back to EXT4 :
- Flash back an official custom recovery (CWM or TWRP)
- Format Data from recovery
- Flash a kernel compatible with your ROM
- Reboot.

no-tactic said:
i flash google original rom
no, i haven't access to bootloader
Click to expand...
Click to collapse
What happens when you hold down Power + Vol down keys together? Hold them until you feel a vibration. May be the battery has died? Keep it on charge for an hour and then try to enter bootloader?

vin4yak said:
What happens when you hold down Power + Vol down keys together? Hold them until you feel a vibration. May be the battery has died? Keep it on charge for an hour and then try to enter bootloader?
Click to expand...
Click to collapse
nothing happens. When I put the phone on charge, it starts to warm up a bit in the camera, but even the display does not light up.
when i connect the phone to computer, it is defined as qhsusb_bulk or unknown usb device

no-tactic said:
nothing happens. When I put the phone on charge, it starts to warm up a bit in the camera, but even the display does not light up.
when i connect the phone to computer, it is defined as qhsusb_bulk or unknown usb device
Click to expand...
Click to collapse
Your memory is no longer accessible unfortunately, you most likely need to have it repaired (new motherboard) :crying:

no-tactic said:
nothing happens. When I put the phone on charge, it starts to warm up a bit in the camera, but even the display does not light up.
when i connect the phone to computer, it is defined as qhsusb_bulk or unknown usb device
Click to expand...
Click to collapse
If all the key combinations don't work, them your device is done for! Since it's totally dead there shouldn't be any problem to RMA it! Good Luck

no-tactic said:
nothing happens. When I put the phone on charge, it starts to warm up a bit in the camera, but even the display does not light up.
when i connect the phone to computer, it is defined as qhsusb_bulk or unknown usb device
Click to expand...
Click to collapse
Press and hold volume up while you connect usb cable to pc.
can you see download mode on device screen?
if yes read this thread entirely http://forum.xda-developers.com/showthread.php?t=2515760
Edit: try this also:
connect your phone to the pc, open device manager.
hold your power button until QHSUSB_BULK disappears, then in that split second press and hold both volume key while you still press the power key. it may end up into the second bootloader

thank you all!

Related

Phone died afeter bootloop

Hi,
i've do an error with sense 5 rom flash.
I have rebooted the phone before flashing boot.img. I have try to put the one x in fastboot or recovery mode but nothing (this phone have very **** keys). After I shot down phone but now don't start. If I connect to charger red light works, same at PC. Windows recognize phone as HTC mtp devices and show me unity letter but i can't do nothing.
Battery 70%.
Any ideas?
Thank's
Sv22 said:
Hi,
i've do an error with sense 5 rom flash.
I have rebooted the phone before flashing boot.img. I have try to put the one x in fastboot or recovery mode but nothing (this phone have very **** keys). After I shot down phone but now don't start. If I connect to charger red light works, same at PC. Windows recognize phone as HTC mtp devices and show me unity letter but i can't do nothing.
Battery 70%.
Any ideas?
Thank's
Click to expand...
Click to collapse
If you're phone is read as an mtp device that means it's not dead and the rom is loaded. The screen is black I take it and won't come on?
reboot to bootloader
either using adb (adb reboot bootloader)
or
manually (hold power button until capacitive buttons blink a bunch of times and the phone shuts off then let go of power and press and hold volume until bootloader comes on)
If you still can't see the screen while in bootloader, then your screen is dead.
exad said:
If you're phone is read as an mtp device that means it's not dead and the rom is loaded. The screen is black I take it and won't come on?
reboot to bootloader
either using adb (adb reboot bootloader)
or
manually (hold power button until capacitive buttons blink a bunch of times and the phone shuts off then let go of power and press and hold volume until bootloader comes on.
If you still can't see the screen while in bootloader, then your screen is dead.
Click to expand...
Click to collapse
yes, my phone is read but on the control panel there is a yellow icon on driver. and if I push keys phone do nothing
Sv22 said:
yes, my phone is read but on the control panel there is a yellow icon on driver. and if I push keys phone do nothing
Click to expand...
Click to collapse
ok.. did you try what I posted above?
exad said:
ok.. did you try what I posted above?
Click to expand...
Click to collapse
yes, but nothing. ADB show me list devices blank, fastboot no devices.....mmhhhh....I have no word. This morning was alive...
today I have turned on the phone in bootloop.
I have volume down key was not working. Any ideas?
Sv22 said:
today I have turned on the phone in bootloop.
I have volume down key was not working. Any ideas?
Click to expand...
Click to collapse
Are you saying the buttons are actually not working properly?
MTP mode plays havoc with adb, and sometimes fastboot. Of course, if you are not able to access recovery, adb, or fastboot, you are in a very tough spot.
Is the device S-off or S-on?
redpoint73 said:
Are you saying the buttons are actually not working properly?
MTP mode plays havoc with adb, and sometimes fastboot. Of course, if you are not able to access recovery, adb, or fastboot, you are in a very tough spot.
Is the device S-off or S-on?
Click to expand...
Click to collapse
my devices is s-on.
I hate this kind of situation. Very comic......

[Q] JLo bricked

Hello.
I'm in a bit of a pickle. I installed slimbean on my friends Xperia J and it booted properly and everything. The only problem I had was that the IMEI was blank and the phone could not get the network established. Now I wish that was still the problem. It looks like the phone is totally bricked. I left it on over night and it was fully charged, but in the morning it was turned off. I tried turning it on, taking out the battery, but couldn't get it to turn on. I tried getting into fastboot mode, but to no avail.
When I press the fastboot button (volume down) and connect it, the windows doesn't recognize it and failes to install the drivers. After that, when I plug it in, I can hear the failed usb connect sound. And that is about it. Please guys, work your magic. Thanks.
cikamatko said:
Hello.
I'm in a bit of a pickle. I installed slimbean on my friends Xperia J and it booted properly and everything. The only problem I had was that the IMEI was blank and the phone could not get the network established. Now I wish that was still the problem. It looks like the phone is totally bricked. I left it on over night and it was fully charged, but in the morning it was turned off. I tried turning it on, taking out the battery, but couldn't get it to turn on. I tried getting into fastboot mode, but to no avail.
When I press the fastboot button (volume down) and connect it, the windows doesn't recognize it and failes to install the drivers. After that, when I plug it in, I can hear the failed usb connect sound. And that is about it. Please guys, work your magic. Thanks.
Click to expand...
Click to collapse
Use flashtool and flash Stock ICS, To put your device in flashmode you hold the Volume + and plug the USB in, The LED Light should light up green, The reason your IMEI was gone and you have no network was because you must've flashed straight from Jellybean? The way to solve this is by flashing from ICS to your desired rom, Goodluck!
Hussain_Salam said:
Use flashtool and flash Stock ICS, To put your device in flashmode you hold the Volume + and plug the USB in, The LED Light should light up green, The reason your IMEI was gone and you have no network was because you must've flashed straight from Jellybean? The way to solve this is by flashing from ICS to your desired rom, Goodluck!
Click to expand...
Click to collapse
Thanks for your response, but the biggest problem is that I can't get into flashmode. Windows just makes a failed connect usb sound and that's it. And the device is listed in the device manager as unknown device.
But, really, thanks for the response.
cikamatko said:
Thanks for your response, but the biggest problem is that I can't get into flashmode. Windows just makes a failed connect usb sound and that's it. And the device is listed in the device manager as unknown device.
But, really, thanks for the response.
Click to expand...
Click to collapse
Windows won't detect anything if you get into flashmode, try again, plug the usb and wait 0.001s and press "Volume +"button
[0.001 s means that do not press button and plug usb at the same time,but need fast action]
lhkakex said:
Windows won't detect anything if you get into flashmode, try again, plug the usb and wait 0.001s and press "Volume +"button
[0.001 s means that do not press button and plug usb at the same time,but need fast action]
Click to expand...
Click to collapse
No luck, just keep hearing the usb failed connect sound and that's it.
cikamatko said:
No luck, just keep hearing the usb failed connect sound and that's it.
Click to expand...
Click to collapse
I've been through this before, another method is installing Sony PC Companion have it opened up, and attempt to put your device in flash mode
Hussain_Salam said:
I've been through this before, another method is installing Sony PC Companion have it opened up, and attempt to put your device in flash mode
Click to expand...
Click to collapse
Nope
I guess that's it.
cikamatko said:
Nope
I guess that's it.
Click to expand...
Click to collapse
You said your battery was completely flat right, so what's happened is your phone doesn't have enough power to do anything, What you need to do is leave the phone on charge (Best to do it overnight) One you've done this Take your battery out for 5 minutes, After place your battery back in and use flash tool and Flash Stock ICS (If you want to flash to slimbean again) if not goa head and flash Stock JB, Your device should run normally

D2403 not turning on - red light of death

My D2403 (M2 Aqua) doest turn on when I press the power button, the red light lights on when I connect the charger, and the sony logo loops, the red light blinks like two times, and thats it. What can I do ?
pi4a7a said:
My D2403 (M2 Aqua) doest turn on when I press the power button, the red light lights on when I connect the charger, and the sony logo loops, the red light blinks like two times, and thats it. What can I do ?
Click to expand...
Click to collapse
Hi,
What verison of Android do you have on your M2?
Do you use a stock ROM or have you flashed a custom ROM on your device?
xavinux said:
Hi,
What verison of Android do you have on your M2?
Do you use a stock ROM or have you flashed a custom ROM on your device?
Click to expand...
Click to collapse
I flashed custom - CM 13
pi4a7a said:
I flashed custom - CM 13
Click to expand...
Click to collapse
Ok, can you boot in recovery mode if you press POWER and VOLUME MINUS at the same time or by running adb reboot recovery ?
xavinux said:
Ok, can you boot in recovery mode if you press POWER and VOLUME MINUS at the same time or by running adb reboot recovery ?
Click to expand...
Click to collapse
No, the phone only light the red light indicator, and thats all. I tried charging it all day and all night, but with no success.
pi4a7a said:
No, the phone only light the red light indicator, and thats all
Click to expand...
Click to collapse
Try to flash it using EMMA:
https://talk.sonymobile.com/t5/Andr...ony-Flash-tool-for-Xperia-devices/td-p/307318
and see if the computer detects the device. Also remove SIM and SD cards and try to boot the M2.
xavinux said:
Try to flash it using EMMA:
https://talk.sonymobile.com/t5/Andr...ony-Flash-tool-for-Xperia-devices/td-p/307318
and see if the computer detects the device. Also remove SIM and SD cards and try to boot the M2.
Click to expand...
Click to collapse
When I connect it in the PC, there is a sound when you plug and unplug a device, thats sounds plays seconds after connect i(it connects it, and then dicsonnects it automaticlly) also It only recognize it when I plug it in fastboot mode..
When I try to power on the device while is in the charger, the no battery big white icon shows, and thats it.
pi4a7a said:
When I connect it in the PC, there is a sound when you plug and unplug a device, thats sounds plays seconds after connect i(it connects it, and then dicsonnects it automaticlly) also It only recognize it when I plug it in fastboot mode..
When I try to power on the device while is in the charger, the no battery big white icon shows, and thats it.
Click to expand...
Click to collapse
So you can start your M2 in fastboot mode, the led light should turn into blue.
You can try to flash TWRP recovery and then the ROM again, download twrp.img from here: https://www.androidfilehost.com/?fid=457095661767112082
Then to flash it to the M2 from a command line run:
adb reboot bootloader (to enter in fastboot mode)
fastboot flash recovery /path/to/the/twrp.img
Then try to reboot into recovery mode running:
adb reboot recovery
And then from the TWRP menu -> WIPE -> INSTALL the ROM file again.
When I type the first I get a error - error: device '(null)' not found
The device is connected by the way (I got the blue light).
pi4a7a said:
When I type the first I get a error - error: device '(null)' not found
The device is connected by the way (I got the blue light).
Click to expand...
Click to collapse
Ok, so adb is not recognizing the device.
When you connect the M2 make sure you hold the VOLUME DOWN before connecting the USB-cable and hold it until EMMA detect it., this can take up to 1 minute. If this didn't help, force a shutdown holding the POWER and VOLUME UP buttons at the same time for at least 10 seconds, then connect it to the wall charger and charge the M2 for two or three hours. You can also try by pressing the OFF button on the MICRO SIM slot.
xavinux said:
Ok, so adb is not recognizing the device.
When you connect the M2 make sure you hold the VOLUME DOWN before connecting the USB-cable and hold it until EMMA detect it., this can take up to 1 minute. If this didn't help, force a shutdown holding the POWER and VOLUME UP buttons at the same time for at least 10 seconds, then connect it to the wall charger and charge the M2 for two or three hours. You can also try by pressing the OFF button on the MICRO SIM slot.
Click to expand...
Click to collapse
I tried this with Flashtool, its not working, and by the way I have opened the back panel and I have access to the battery, and I can disconnect it directly, to force shutdown it. I did it, and put it on charge for whole day and night, no success at all... :///
pi4a7a said:
I tried this with Flashtool, its not working, and by the way I have opened the back panel and I have access to the battery, and I can disconnect it directly, to force shutdown it. I did it, and put it on charge for whole day and night, no success at all... :///
Click to expand...
Click to collapse
And have you tried the other suggestions I"ve given above ?

How do I fix my OnePlus One’s bootloop?

Greetings of the day,
Hello everyone, I'm having a oneplus one 64GB phone that is not getting start, everytime i connect it with the charger it goes into a bootloop. Yes the phone was rooted and I was using a custom ROM with the default kernel. The issue started when I tried to reset the phone to battery settings. I think I somehow messed the kernel and now it is stuck in bootloop. The problem is that I can't connect it to my computer or put it in debug mode as it just restarts again. Any idea how to actually boot it so I can install the kernel and ROM again?
Lazy Titan said:
Greetings of the day,
Hello everyone, I'm having a oneplus one 64GB phone that is not getting start, everytime i connect it with the charger it goes into a bootloop. Yes the phone was rooted and I was using a custom ROM with the default kernel. The issue started when I tried to reset the phone to battery settings. I think I somehow messed the kernel and now it is stuck in bootloop. The problem is that I can't connect it to my computer or put it in debug mode as it just restarts again. Any idea how to actually boot it so I can install the kernel and ROM again?
Click to expand...
Click to collapse
Can it go into recovery mode(power+ vol-)?
Mr.Ak said:
Can it go into recovery mode(power+ vol-)?
Click to expand...
Click to collapse
No, My phone is not getting on but whenever i am connecting it with my charger the phones goes in the Bootloop, and when i am connecting it to My PC while pressing Volume Up + Power Button Pc shows that the Unrecognized devices has been connected.
And i think phone is Hard Bricked. I have tried ADB software and one plus 1 drivers manually but it didn't worked too. I have tried minimal ADB too but it also didn't work.
Kindly let me know about it.
Lazy Titan said:
No, My phone is not getting on but whenever i am connecting it with my charger the phones goes in the Bootloop, and when i am connecting it to My PC while pressing Volume Up + Power Button Pc shows that the Unrecognized devices has been connected.
And i think phone is Hard Bricked. I have tried ADB software and one plus 1 drivers manually but it didn't worked too. I have tried minimal ADB too but it also didn't work.
Kindly let me know about it.
Click to expand...
Click to collapse
Volume UP + Power should boot in fastboot mode. Volume Down + Power should boot into recovery. First, try to boot recovery.
giaur said:
Volume UP + Power should boot in fastboot mode. Volume Down + Power should boot into recovery. First, try to boot recovery.
Click to expand...
Click to collapse
I have tried both, but nothing happens with it, Volume UP + Power shows the unrecognizable device is connected and Volume Down + Power does nothing it continues with bootloop .
Have you got Developer Options enabled?
Goto About Phone & Tap Build Number until Developer Options is activated. Goto Developer Options> Advanced Restart & enable the switch.
Press power button->Restart->Recovery.
It will now boot into Recovery.
Also have you tried keeping hold of power button whilst it bootloops. Keep holding the power button until it powers off. Then press Volume Down & Power Button to power back up (you might see a slight flicker onscreen that means it should go into Recovery mode). Keep hold of these buttons until you gain Access to Recovery Mode.
This will allow you to Recover or flash a different ROM.
If you're having issues connecting to a computer (Windows) try downloading Windows Media Center for your version of Windows. This will install media drivers to recognize your phone.. If all went well you will get the pop up with A0001 (Codename of OnePlus One). From there you should be able to enter fastboot mode through ADB.
If this doesn't help you, I'm sure that someone else will untangle the puzzle to get your device in good working order buddy. Good Luck.
bmark240 said:
Have you got Developer Options enabled?
Goto About Phone & Tap Build Number until Developer Options is activated. Goto Developer Options> Advanced Restart & enable the switch.
Press power button->Restart->Recovery.
It will now boot into Recovery.
Also have you tried keeping hold of power button whilst it bootloops. Keep holding the power button until it powers off. Then press Volume Down & Power Button to power back up (you might see a slight flicker onscreen that means it should go into Recovery mode). Keep hold of these buttons until you gain Access to Recovery Mode.
This will allow you to Recover or flash a different ROM.
If you're having issues connecting to a computer (Windows) try downloading Windows Media Center for your version of Windows. This will install media drivers to recognize your phone.. If all went well you will get the pop up with A0001 (Codename of OnePlus One). From there you should be able to enter fastboot mode through ADB.
If this doesn't help you, I'm sure that someone else will untangle the puzzle to get your device in good working order buddy. Good Luck.
Click to expand...
Click to collapse
he said his device is in bootloop. how come he will turn on the developer option then?
akhiarr said:
he said his device is in bootloop. how come he will turn on the developer option then?
Click to expand...
Click to collapse
This has got to be some sort of World Record for resurrecting an old post from over five years ago. Congratulations on that achievement!
Did you just join to post that?
Lol.

Help - my honor 8 was block - No access Fastboot Mode or Debugging Mode

Hello,
I downgraded my Honor 8 via Rollback and installed the Rom FRD-L09C432B131.
But my phone is stuck on the blue Android startup screen.
I can not use the Volume +, Volume - or Power buttons.
All I can do is let it turn off by itself when the battery is at 0%.
When I put it on, it turns on by itself. Arrives on a blue screen. Reboot once and then stays eternally on the blue screen while heating up enormously.
I have no access to the Recovery, erecovery or via the computer (by plugging it into a USB port).
Thanks
gregase said:
Hello,
I downgraded my Honor 8 via Rollback and installed the Rom FRD-L09C432B131.
But my phone is stuck on the blue Android startup screen.
I can not use the Volume +, Volume - or Power buttons.
All I can do is let it turn off by itself when the battery is at 0%.
When I put it on, it turns on by itself. Arrives on a blue screen. Reboot once and then stays eternally on the blue screen while heating up enormously.
I have no access to the Recovery, erecovery or via the computer (by plugging it into a USB port).
Thanks
Click to expand...
Click to collapse
Once your phone turns off, press power button amd volume up button together. This should take you to recovery. Or you can't access this at all?
Sent from my Honor 8 using XDA Labs
I can not turn off my phone. It goes off when the battery is at 0%.
If I put on USB or mains, it recharges and restarts automatically. And I can not stop it ...
When I plug it into a USB port, the Power, Volume + or Volume buttons are ineffective.
And when it's plugged into the PC, it does not show up!
So I do not have access ... except perhaps by a software that would force the connection ... or a manipulation other than Power / Volume ..
When I say reboots, it is a program to display the Android blue screen and hangs on it!
does it say android or honor?
going to dload is kinda tricky sometimes and should be done when connected to wall adapter, not pc
can you keep vol- and power pressed while your phone is connected to pc. keep them pressed even after the phone restarts. dont let go. it might take some time. does it go to fastboot?
gregase said:
I can not turn off my phone. It goes off when the battery is at 0%.
If I put on USB or mains, it recharges and restarts automatically. And I can not stop it ...
When I plug it into a USB port, the Power, Volume + or Volume buttons are ineffective.
And when it's plugged into the PC, it does not show up!
So I do not have access ... except perhaps by a software that would force the connection ... or a manipulation other than Power / Volume ..
Click to expand...
Click to collapse
Is your phone still covered by the warranty?
Sent from my Honor 8 using XDA Labs
Do a factory reset I believe
PalakMi said:
Do a factory reset I believe
Click to expand...
Click to collapse
He can't even boot to recovery.
Sent from my Honor 8 using XDA Labs
Ohhh, sorry my bad
dats prolly because he has mismatched files for the os he's running. he should deffo check if he can go to fastboot. the fact that he cant go to dload doesnt really mean anything because i cant do it either 40% of the time. its a bit iffy. the fact remains, if it boots to honor logo, means some type of os is up there. if he can go to fastboot he can flash stock recovery/recovery2 and try dload again. without proper recovery combo he wont be able to flash anything anyways and warranty prolly wont cover it since its users fault, esp if he has unlocked warning.
Delete
Rommco05 said:
Check first post
Click to expand...
Click to collapse
My bad
Rommco05 said:
No way, Im just want to show you is here too much threads witch similar problems and much information and experiences... I think about one guide/thread where will be all info about rollbacks and nougat firmwares. But is a lot of work about finding info, all is ok
Click to expand...
Click to collapse
Thank you :laugh:
Similar to me, only way is go into bootloader mode, then charge the phone for awhile, you cant do nothing cuz of 0% battery, flash stock recovery, update via dload or direct wifi recovery.
qvnsq said:
Similar to me, only way is go into bootloader mode, then charge the phone for awhile, you cant do nothing cuz of 0% battery, flash stock recovery, update via dload or direct wifi recovery.
Click to expand...
Click to collapse
He can't go to fastboot
if he completely bricked it, he'd be stuck at black screen/android logo, not honor logo. either he's not telling us everything (ran out of juice while upgrading / error while flashing / flashing wrong rom), there is no chance all key partitions got wiped if the process finished successfully. meaning at least he should be able to fastboot cause thats the first thing flashing alongside bootloader. no way any type of system partition is up there, and bl/fb is not, even if they are from a different OS. h8 can be stubborn at times, but keeping the cable in pc and holding vol_down+power for good 20s deffo will force it to at least reboot. thats the only way. if this doesnt work, you should take it to a service center.
I guess it's better if he takes it to the service center
Nothing works. So I have to send it to the service center
Thank you all !
gregase said:
Nothing works. So I have to send it to the service center
Click to expand...
Click to collapse
It's sad but, I hope it gets fixed

Categories

Resources