Database Users

Nexus 4 dead on 4.4.3 official

Hello, i whant to put 4.4.3 on N4 and with normal flash-all.bat(did it many times before on 4.4.2) and then phone was flashing booloader..waiting devices...and nothing.Phone screen is black only a sound on windows when i connect it.
How can i fix my nexus?
Edit: 1)if i shutdown with pwrbutton 10 sec and turn on via pwr+volume i hear as i connected the phone
2)if turn on normal red light a few sec..
Bricked???

Are you able to get to bootloader? Was it unlocked before you flashed the 4.4 3 image
Sent from my HTC One using Tapatalk

mrao said:
Are you able to get to bootloader? Was it unlocked before you flashed the 4.4 3 image
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
1)I had PA before on it
2)Yes i was unlocked
3)Black screen...nothing.Just a beep like i connect it to pc....and a red dot a few seconds.

krystyuc said:
1)I had PA before on it
2)Yes i was unlocked
3)Black screen...nothing.Just a beep like i connect it to pc....and a red dot a few seconds.
Click to expand...
Click to collapse
Just a wag, but have you tried letting it charge first?
Sent with my Nexus® 10 minus 3

Berrydroidcafe said:
Just a wag, but have you tried letting it charge first?
Sent with my Nexus® 10 minus 3
Click to expand...
Click to collapse
Yes.
Edit: If i plugit into a new pc it shows me
{
"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"
}
After some serch i think it's bricked....only Jtag can fix it

Don't think its bricked. Try type "fastboot devices" in a command prompt in your fastboot folder. If it shows up under listed devices its not bricked. I've had this happen where just the file that makes the screen light up didn't get installed. Just have to reinstall the bootloader. No big deal.
Scratch that!
I'll buy it from you for $5

M3drvr said:
Don't think its bricked. Try type "fastboot devices" in a command prompt in your fastboot folder. If it shows up under listed devices its not bricked. I've had this happen where just the file that makes the screen light up didn't get installed. Just have to reinstall the bootloader. No big deal.
Scratch that!
I'll buy it from you for $5
Click to expand...
Click to collapse
1)Already tryed that and the adb devices...no luck
2)Nothing is displayed on my n4 screen,absolutly black,but it's still on
3)my pc dose a sound when i connect/disconnect the phone
I found something
"Seems that while flashing that ROM you have managed to destroy parts of the Bootloader, wich finaly results in the device doing nothing. (Black Screen etc)
Partitialy you are right yes "QHS-USB Mode" means your device is hard bricked an in the so called QHS-USB Download Mode
but this mode is meant for vendors to flash bootloaders etc on the devices.
To access the device in a propper way u need some "non-public" tools wich QCOM usaly only supplies to vendors not to endusers!
Without thoose programs u will be not able to access the device in any way, even with thoose tools without the expierience and knowledge and files u need, i guess u will not be able to recover it yourself.
I do not want to risk some trouble with QCom at all so i do not can point u to the propper tools to use but i'm sure when using google u will be able to find out what tools i'm talking about.
In my mind the best way for you to recover that device is a JTAG
So my suggestion is to search for a JTAG in your region a JTAG in europe usaly is arround 30 euro but price can differ in your country"

So.....no luck till now,the phone is hardbricked.I'll send it monday to warranty,maybe they will fix it for free if not....then this is an excuse to buy N5

LG G2 D802 Unidentified device Unknown device

I'm connecting the LG G2 D802 to the Windows 7 in download mode, with LGMobileDriver_WHQL_Ver_4.0.4.exe drivers installed, however the drivers fail to install.
{
"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"
}
Unknown device
Unidentified device

Install drivers manually and disable windows update to override whatever windows wants to install from there...

The issue was happened when trying to flash some LG G5 adapted rom on the LG G2, so the bootloader or the recovery got damaged. What I finally did was to force qhsusb_bulk short circuiting the capacitor and then using SRKtool_2.1_droidth.zip to use the unbrick method.
Then, you can reboot to download mode to use LG Flash Tool or reboot to recovery to flash the partition of your particular rom using dd (once you upload the partition images to the smartphone sdcard).
http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
http://forum.xda-developers.com/showthread.php?t=2582142
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404

Hey scandium, I know it's been years since you've posted this,
but I was wondering if your phone symptoms were unknown device on any pc+slow charging with any charger. I currently have a G2 in this situation. It works, but has no USB connectivity whatsoever, and takes ages to charge. Do you think that shorting the capacitor and flashing the phone from scratch would fix it? I'm afraid of trying it and when connecting to the PC still get the unknown device problem and end up with a brick. Thanks in advance.
scandiun said:
The issue was happened when trying to flash some LG G5 adapted rom on the LG G2, so the bootloader or the recovery got damaged. What I finally did was to force qhsusb_bulk short circuiting the capacitor and then using SRKtool_2.1_droidth.zip to use the unbrick method.
Then, you can reboot to download mode to use LG Flash Tool or reboot to recovery to flash the partition of your particular rom using dd (once you upload the partition images to the smartphone sdcard).
http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
http://forum.xda-developers.com/showthread.php?t=2582142
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse

Mrkblo said:
Hey scandium, I know it's been years since you've posted this,
but I was wondering if your phone symptoms were unknown device on any pc+slow charging with any charger. I currently have a G2 in this situation. It works, but has no USB connectivity whatsoever, and takes ages to charge. Do you think that shorting the capacitor and flashing the phone from scratch would fix it? I'm afraid of trying it and when connecting to the PC still get the unknown device problem and end up with a brick. Thanks in advance.
Click to expand...
Click to collapse
I did not have any problem with charging.

Nexus 4 - wiped internal storage & pc wont recognize phone so stuck in recovery mode

Nexus 4 - wiped internal storage & pc wont recognize phone so stuck in recovery mode
before i start, i would like to say that my last experience with android phone, rooting and other stuff related to android was last october 2013. please bear with me
i posted this exact texts below before before i gave up on my nexus 4. now after 2 years, im ready to get frustated again. so here it is
----------
my problem started after i updated to oct 7 cm10.3 nightly. my pc and my mbp cant read my nexus storage.
searched for this problem and found some few n4 users that experienced this but my main problem is there is no android device listed on my device manager.
i checked for all possible solutions:
- uninstall driver on device manager and reconnect the phone to install the driver automatically (but theres no android device listed)
- changed the storage settings as to connect to mtp
- restore factory settings and wipe data
- tried different data cables
- changed my rom from cm to pa
- restart phone
- push adb but device not found (but my pc doesnt recognize my phone)
- turned on/off usb debugging (still cant read)
then out of frustration, i wiped my storage data completely
so now, i cant flash any roms, no files found on system
i cant push adb because my pc cant find my phone even in recovery and device manager, even in USBDeview
but the unit is till charging
i sent it to lg and they said the board was the problem and the replacement was expensive so i gave up and bought another phone
----------
google released pixel and i began to miss my n4 so tried to recover it
the condition is the same 2 years ago. placed it in storage after got frustrated
so anyone has an idea?

If the phone is recognized in fastboot mode, flash TWRP, boot into TRWP, mount storage, copy a custom ROM to the phone, and flash from TWRP.
As an alternative, you can flash a stock Google ROM if fastboot commands are working.

Hey!
Maybe it's just a minor "hardware problem". Did you check if there is any lint between the micro usb connector-plate and the back (see attachment)? Mine caught dirt and lint over time. With a thin but sturdy piece of plastic I could remove the dirt again, and suddenly all my cables started to work again.
{
"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"
}

thank you audit13 and smeee_again for your replies. ill look into both of it!

Phone should be recognized in Bootloader mode anyway, try different drivers, then fastboot flash stock and re-root
Optionally, boot into recovery, connect cable and go to mount options then mount usb storage, put any ROM in storage and flash it, the trick is it shouldn't require specific drivers as storage via recovery shouldn't use MTP but generic USB connection (like pendrive) as far as I know.

If you don't want to root and install a custom recovery just download and fastboot the Fake Nexus ROM which will give you a stock experience really easily and also it will be Nougat . Check out the thread for how to install it, it's really easy.

Need some help for a bricked pure

I have not touched this phone in a year, so forgive me if im rusty.
I embarked on a project of compiling slimroms 7.1.2 for this device a year ago, and made a rom that made it onto the device. Now, Here is my mistake. At the time when i built the rom, the nougat bootloader for this device was not out yet(i think, as my bootloader is on a0.4d aka dated 2016-11-30) Giddy that i had finally built a custom rom that worked, i hurriedly flashed the device through the recovery(twrp at the time) and thats when the issues happened. The device will not charge past 1 percent, and in an effort to fix, without knowing that my outdated bootloader was the issue, i decided that installing stock recovery was the best option. BIG MISTAKE. as i now cannot flash anything in recovery. i keep getting signature verification failures and what not.
With that backstory out of the way, here is my issue. I cannot flash anything in fastboot, because when i connect the device to windows i get
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Yes i have updated the drivers and when i install the motorola drivers manually i get this:
Code:
This device cannot start. (Code 10)
A request for the USB device descriptor failed.
this is the single most thing that is keeping me from reviving this device. I have tried using linux, but the device just doesnt show up. I have tried multiple usb cables. so i know thats not the issue. any help would be very appreciated.
UPDATE: i have done some digging around and no loader files are working. (using a 32gig class 10 microsd). Also, It is on stock recovery so i cannot flash anything other than stock images, which if i am correct, none are recovery flashable, only the otas are. When i try to flash an ota it doesnt work because it is expecting stock apps in system, which are not there since i am on a slimrom rom.
TLDR: i have stock bootloader and recovery, (24.49-18-8/4) but have a non rooted slimrom 7.1.2 which shows up in windows as get device descriptor failed(unknown device). if there was a way to root slimrom 7.1 without usb and with stock recovery that would help alot.

Have you tried the method to revive the phone in Qualcom mode (error 9008)?

mr_5kool said:
Have you tried the method to revive the phone in Qualcom mode (error 9008)?
Click to expand...
Click to collapse
Can you link me to a thread that has that info please?
When I am in bootloader and hit the power button on the qcom option my phone just boots into the slimroms option with no change in the USB side

Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860

mr_5kool said:
Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Click to expand...
Click to collapse
So my issue is worse than that. It shows up on the computer as "device descriptor get failed" so I am unableble to use that method unless I can force it into qdloader mode

Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA

mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
When i try to install this driver, it says that it is incompatable for my device
I will try again when i get home tomorrow though

mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
Alright, When i try to install this driver i get this
View attachment 4594365
And this is the error i have on any machine
View attachment 4594369

{
"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 don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!

mr_5kool said:
I don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!
Click to expand...
Click to collapse
its quite alright. i think that i bricked the phone while trying to use an unsupported bootloader, therefore bricking the mainboard
Its noones fault but my own, so i will chalk this one up to a loss lol

I need help trying to restore my Note 7

My Xiaomi Redmi Note 7 (lavender), gave Brick after formatting the cell phone, which was with a Lineage ROM, but immediately the cell phone would not boot, the ROM corrupted and to make the recovery worse, the TWRP, apparently it ended up corrupting, it does not enter and hangs in the TWRP logo.
Fastboot mode still works, but I can't get any device to recognize it, nothing just happens. I've tried ADB, MI Flash and some other programs, but it ends up not working, My computer can't recognize the Note 7. I switched cables and tried different ways, using my second phone as a command prompt, but it still didn't recognize it. Just need to try another computer
I wanted to know if the problem is reversible, because if not, I have a screened brick
I think the connector may be defective but I think it's unlikely as it worked perfectly before
If any expert can help me, that would be great
Sorry for the robotic English, it's not my mother tongue

1Henryx said:
My Xiaomi Redmi Note 7 (lavender), gave Brick after formatting the cell phone, which was with a Lineage ROM, but immediately the cell phone would not boot, the ROM corrupted and to make the recovery worse, the TWRP, apparently it ended up corrupting, it does not enter and hangs in the TWRP logo.
Fastboot mode still works, but I can't get any device to recognize it, nothing just happens. I've tried ADB, MI Flash and some other programs, but it ends up not working, My computer can't recognize the Note 7. I switched cables and tried different ways, using my second phone as a command prompt, but it still didn't recognize it. Just need to try another computer
I wanted to know if the problem is reversible, because if not, I have a screened brick
I think the connector may be defective but I think it's unlikely as it worked perfectly before
If any expert can help me, that would be great
Sorry for the robotic English, it's not my mother tongue
Click to expand...
Click to collapse
For fastboot you just need to update the drivers, run the same process you did sometime, when it, firstly, worked. Remember that a corrupted device must have the drivers updated, a kind of communication lost, nothing more.
I´ll upload some screenies from the process you need to do:
{
"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"
}
Once you get it, repeat the process, i.e. boot to recovery and flash the ROM.