Dead nexus 4? - Nexus 4 Q&A, Help & Troubleshooting

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

Related

N7 (3G, 2012) bricked? Boot mode, no recovery. N Toolkit doesn't flash.

Hello there.
I am writing because I need your help on unbricking my Nexus 7 3G (2012). Yesterday night I was trying to upgrade it from 5.1.0 to 5.1.1 (from the OTA) and I couldn't because I had an error produced by Stickmount. It changed a file on system/bin which I tried to push manually (following some thread's intructions on XDA) and it didn't work, showing error Status 7 (unexpected content on file debuggerd).
Because of that, I decided to flash the 5.1.1 system image using Nexus Toolkit. I set it up so it'd download and install it automatically (using the "Flash stock + Unroot" option). Everything went okay and started the flashing process until the command prop window force closed mid flash, thing that never happened to me before (as I had tried many times flashing from zero my N7 before).
I tried to start the Toolkit again and the command prop window says it flashes bootloader and radio img's successfully, but then a line of code appears and the cmd window force closes again (it says "No se esperaba ( en este momento" or roughly translated as "The ( was not expected at this moment" into English) and my N7 turns off.
Next, I try to turn it on and it shows the Google logo and a green arrow saying "start". I press it and the N7 reboots to the same screen, saying "booting failed" at the top of the screen. If I choose recovery, the same thing happens.
{
"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 just can make it to boot to bootloader mode but I cannot flash the firmw (even when this mode must be selected in order to the Toolkit to start flashing). It shows the same line of unexpected code as above.
I tried pushing the files manually using ADB and I cannot may it work either.
What can I do to solve this? I've read that as long as you can get to bootloader mode you can unbrick a device.
I hope you could help me out. Thanks in advance.
Anyone?
Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!
wombat3 said:
Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!
Click to expand...
Click to collapse
Thanks wombat. Actually, the N7 is listed under adb devices. It starts the flashing process but ends automatically without finishing the installation.

[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.

Boot Up Question

Hi, I picked up this phone through a private sale and, while it works fine, I noticed a couple of things during boot up. This first flashed on the screen:
{
"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"
}
Then it went away and the following flashed on the screen:
Then it went to the main screen. Does this mean that something has been loaded onto the phone? What should I do to get it back to factory?
Thanks in advance.
vik123 said:
Hi, I picked up this phone through a private sale and, while it works fine, I noticed a couple of things during boot up. This first flashed on the screen:
Then it went away and the following flashed on the screen:
Then it went to the main screen. Does this mean that something has been loaded onto the phone? What should I do to get it back to factory?
Thanks in advance.
Click to expand...
Click to collapse
The first screen indicates the bootloader is unlocked.
The second means you are not stock but running a custom ROM.
Back to stock -> https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Thank you for the link. I checked it but I am not sure which file to download. Sorry, I am not very familiar with all of this and I am nervous about bricking my phone.
vik123 said:
Thank you for the link. I checked it but I am not sure which file to download. Sorry, I am not very familiar with all of this and I am nervous about bricking my phone.
Click to expand...
Click to collapse
Plug your phone into your PC using a good USB 3.0 cable after you reboot into the bootloader (do this by holding down volume down and power button at once. Also, use a type a to c cable, the essential phone stock USB c to c cable doesn't work that well for flashing stuff).
Then install the drivers for this phone from here on a windows system: https://storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe
Then install minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=745425885120698566
Then, download the latest back to stock zip from here:
https://www.androidfilehost.com/?fid=745425885120698566
Unzip into the folder you installed minimal adb and fastboot into, and then open minimal adb and fastboot. In the command window that pops up, type "flash-all.bat && fastboot -w" and then hit enter. This will reflash all the stock partitions and wipe all data.
After you get the stock essential phone firmware booting, you can reboot into the bootloader and run "fastboot -w" and then "fastboot flashing lock" to relock the boatloader if you plan on keeping the stock unmodified firmware.
Credit goes to @aer0zer0 for the dump of the latest firmware.
Thank you so much. I followed the instructions and, while there were some nervous moments, managed to get it back to stock.
I can't believe the previous owner was such a jerk. I always return phones to full stock and relock the bootloader if I plan to sell a phone.
vik123 said:
Thank you so much. I followed the instructions and, while there were some nervous moments, managed to get it back to stock.
Click to expand...
Click to collapse
Hey no problem, always glad to help, especially since the situation you were in was caused by the previous owner not caring to flash stock and relock the bootloader before he sold you the phone. Seems like a careless thing to do, especially since he could've sold the phone to someone who wouldn't be tech savvy enough to restore stock.
The seller was really nice so I have a hard time calling him a jerk, but yeah, it was a careless thing to do. If it wasn't for this community I would probably have been screwed.
Thanks again everybody.

Nokia X6 Stuck in Download Mode

Hello, hope you can help.
I have a Nokia X6 (TA 1099) that somehow got stuck in Download Mode (see attached pictures)
I have tried the Vol Down plus Power to exit Download Mode, also tried various other combinations, but no luck.
When I plug the phone into USB it does show up as Fastboot Device and I can use the fastboot cmd with reboot to make it restart, but it stays in Download Mode.
I tried installing the OST LA tool and it made the phone display some more details on screen (see attached picture), however it wouldn't get as far as to attempt loading a new image. (says software tool needs update)
Thanks,
Jake
{
"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"
}
imgur dot com/a/xDSs8BJ
imgur dot com/eM5a8ib
Try this fix
paul89rulez said:
Try this fix
Click to expand...
Click to collapse
Very nice guide, thanks.
Unfortunately I get an error message saying: FAILED (remote: 'Flashing is not allowed in Lock State')
Then I tried the fastboot flashing unlock and unlock_critical but that just resulted in error message: FAILED (remote: 'Flashing Unlock is not allowed')
However after trying a fastboot --set-active=b and rebooting it made the phone come back from the Download Mode brick telling me something is corrupted and asking to restore to factory. I chose to restore to factory and it appears the phone is now unbricked and I just need to install everything again.
Thanks for your helpful suggestions.
Jake
JakeJ42 said:
However after trying a fastboot --set-active=b
Jake
Click to expand...
Click to collapse
You mean --set-active=_b?
You have bt unlocked?
paul89rulez said:
You mean --set-active=_b?
You have bt unlocked?
Click to expand...
Click to collapse
Nah, it's my wife's phone, I'm not sure how she managed to get it stuck in Download Mode, but I suspect maybe the case she was using caused the buttons to get stuck or something.
It was --set-active=b I used.
JakeJ42 said:
Nah, it's my wife's phone, I'm not sure how she managed to get it stuck in Download Mode, but I suspect maybe the case she was using caused the buttons to get stuck or something.
It was --set-active=b I used.
Click to expand...
Click to collapse
Sorry if I insist, your x6 is converted to global rom or it have Chinese stock?
Thanks for this
JakeJ42 said:
Very nice guide, thanks.
Unfortunately I get an error message saying: FAILED (remote: 'Flashing is not allowed in Lock State')
Then I tried the fastboot flashing unlock and unlock_critical but that just resulted in error message: FAILED (remote: 'Flashing Unlock is not allowed')
However after trying a fastboot --set-active=b and rebooting it made the phone come back from the Download Mode brick telling me something is corrupted and asking to restore to factory. I chose to restore to factory and it appears the phone is now unbricked and I just need to install everything again.
Thanks for your helpful suggestions.
Jake
Click to expand...
Click to collapse
I had the same issue with my 6.1 plus (TA 1116) when it suddenly showed me the screen asking for a factory wipe & that my data was corrupt. The phone entered download mode and I let the battery discharge overnight. Today after following the steps Jake took, the phone got out of download mode and I did a factory reset, the phone is working ok now.
Thanks @ Jake!
I had the same issue with my 6.1 plus (TA 1116) when it suddenly showed me the screen asking for a factory wipe & that my data was corrupt. The phone entered download mode and I let the battery discharge overnight. Today after following the steps Jake took, the phone got out of download mode and I did a factory reset, the phone is working ok now.

I'm having an issue with my G Pad 7 (LG-LK430)

Heres the problem I started getting after I took the update from Magisk this morning. I did the update through Magisk app using their recommended method of flashing it I believe and I think thats how the problems started.
{
"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"
}
it just boot loops now with that message over and over again. On top of that error I am unable to boot into Download Mode or Recovery, I get this when I try to:
Any one have any ideas on how to fix this, I'm all ears. Thanks for the help
arksoother said:
Heres the problem I started getting after I took the update from Magisk this morning. I did the update through Magisk app using their recommended method of flashing it I believe and I think thats how the problems started.
it just boot loops now with that message over and over again. On top of that error I am unable to boot into Download Mode or Recovery, I get this when I try to:
Any one have any ideas on how to fix this, I'm all ears. Thanks for the help
Click to expand...
Click to collapse
Try flashing Mr. Bump linked here -> https://forum.xda-developers.com/showpost.php?p=68638985&postcount=54
rahimali said:
Try flashing Mr. Bump linked here -> https://forum.xda-developers.com/showpost.php?p=68638985&postcount=54
Click to expand...
Click to collapse
So here's the problem with doing this, I have no way of flashing Mr.Bump at the moment with the stupid tablet looping like it is. When I plug in the tablet I don't get the bepoop from my laptop telling me its plugged in and ready to go unless I press the power button and volume down. But then I get what the second picture showed, at that point then the pc does the bepoop sound but I still can't do anything with the tablet. So I guess my next question is how do I flash or use this with the state my tablets in? Thanks.
arksoother said:
So here's the problem with doing this, I have no way of flashing Mr.Bump at the moment with the stupid tablet looping like it is. When I plug in the tablet I don't get the bepoop from my laptop telling me its plugged in and ready to go unless I press the power button and volume down. But then I get what the second picture showed, at that point then the pc does the bepoop sound but I still can't do anything with the tablet. So I guess my next question is how do I flash or use this with the state my tablets in? Thanks.
Click to expand...
Click to collapse
Can you not even boot into bootloader/fastboot or TWRP/recovery?
You should be able to boot to recovery by following the steps shown here -> https://www.hardreset.info/devices/lg/lg-lk430-g-pad-f-70/recovery-mode/
You could also try and boot into safe mode and try and use the magisk manager to uninstall magisk - howto here -> https://www.hardreset.info/devices/lg/lg-lk430-g-pad-f-70/safe-mode/
okay update, so if you look at the fsecond picture it says fastboot_init() I assume this means its initialised? I have no idea what any of the stuff below that means. when I do the recovery mode it shows the words recovery for like a second then gives me the black screen with white text that you see in picture 2. when I try the other method all the tablet does is bootloop with a new error code of 2250 I think. So I have know idea whats going on with this. I'll try uninstalling Magisk like you said but things are looking bleak I feel?
arksoother said:
okay update, so if you look at the fsecond picture it says fastboot_init() I assume this means its initialised? I have no idea what any of the stuff below that means. when I do the recovery mode it shows the words recovery for like a second then gives me the black screen with white text that you see in picture 2. when I try the other method all the tablet does is bootloop with a new error code of 2250 I think. So I have know idea whats going on with this. I'll try uninstalling Magisk like you said but things are looking bleak I feel?
Click to expand...
Click to collapse
somebody else apparently had the same experience although on a different LG device -> https://forum.xda-developers.com/lg-spirit/help/help-fastboot-error-loading-keystore-t3430163
So it seems that fastboot commands may have been disabled which means you can't interact with the device in fastboot mode whatever you do.
If nothing else works, you could try and re-flash stock ROM if you can manage to get into download mode.
Best of luck!

Categories

Resources