Database Users

[Q] Need Help restoring Nexus 10!!

Hello everybody, this is my first post and I'm kind od a noob on this whole thing, so bare with me here...
Here's the thing, I have a Nexus 10 (my baby), and like a lot of people i was very excited to the update for the infamous 4.4 KitKat.
Yesterday the update downloaded itself automatically and I installed it. So far so good, right?
Wrong! Cause now my nexus won't work. I personally think that the OS got corrupted on the process of update, and now i can't turn it on.
When i try to turn it on normally (power button only), nothing happens.
I can however enter in download mode and on that other mode that shows the options (image below). I can't however enter on recovery mode, when i try to, it only goes dark, as if it doesn't exist (that's where im getting the whole "corrupted OS" idea).
To make matter worse, I'm pretty sure that the option Usb debugging, was turned off before all this happened, and i think that's the reason why the next step didn't work either.
I tried unlocking the bootloader again (even tough it already appears as unlocked) and also tried to flash the stock recovery that i download from the developers page of google itself, but when i try to do it, it show that my device is not connected (actually it says "waiting for device").
I also tried flashing it trough odin3.07 but it also won't work, that's cause when it seems that the process will start, Odin crashes, and i dont know why (skyes wasnt the reason cause I dont even have it on my pc).
Anyway, that's my problem. I really hope someone can shed some light on me and help me. Thanks
{
"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"
}
So I finally figured out the problem... I had to completely flah the stock image from fastboot, but my drivers were not up-to-date... so I guess it was kinda my own fault... sorry.... but let it be a cautionary tale for everyone, DRIVERS DO MATTER!!

Mancini_Rafael said:
Hello everybody, this is my first post and I'm kind od a noob on this whole thing, so bare with me here...
Here's the thing, I have a Nexus 10 (my baby), and like a lot of people i was very excited to the update for the infamous 4.4 KitKat.
Yesterday the update downloaded itself automatically and I installed it. So far so good, right?
Wrong! Cause now my nexus won't work. I personally think that the OS got corrupted on the process of update, and now i can't turn it on.
When i try to turn it on normally (power button only), nothing happens.
I can however enter in download mode and on that other mode that shows the options (image below). I can't however enter on recovery mode, when i try to, it only goes dark, as if it doesn't exist (that's where im getting the whole "corrupted OS" idea).
To make matter worse, I'm pretty sure that the option Usb debugging, was turned off before all this happened, and i think that's the reason why the next step didn't work either.
I tried unlocking the bootloader again (even tough it already appears as unlocked) and also tried to flash the stock recovery that i download from the developers page of google itself, but when i try to do it, it show that my device is not connected (actually it says "waiting for device").
I also tried flashing it trough odin3.07 but it also won't work, that's cause when it seems that the process will start, Odin crashes, and i dont know why (skyes wasnt the reason cause I dont even have it on my pc).
Anyway, that's my problem. I really hope someone can shed some light on me and help me. Thanks
View attachment 2410610
View attachment 2410611
View attachment 2410612
View attachment 2410613
Click to expand...
Click to collapse
Pm'ed you.
Sent from my Galaxy Nexus using XDA Premium HD app

I like wugfresh's Nexus Root Toolkit.

I had the same problem.
As suggested above, get the wugfresh nexus root toolkit. That has the option of flashing a stock rom from a soft-bricked device so long as you can get to the bootloader (which is where you are).

I had the same issue - I'm wondering how many others are getting this too. I'm in no way conversant with this kind of technical challenge so I had a few hours of stress thinking my tablet was knackered.
I tried mskips and wug's toolkits on my bootcamp partition in but couldnt get them to work. I tried following the manual fastboot recovery then ADB sideloading the image but that kept failing too.
In the end, I use the mac toolkits (here: http://forum.xda-developers.com/showthread.php?t=2063042) to get back to android 4.2, then let the device receive OTAs. The 4.4 OTA installed fine this way around.

LG L Fino D290N boot certification verify error, download mode doesn't work

Hi xda!
Today I woke up, ate breakfast, cleaned my teeth and then turned on my LG L Fino. And then.... I saw an error like this:
{
"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"
}
What is going on? Yesterday it was working.....
I can't flash stock .kdz from recovery, because it doesn't work.
I heard about flash using .tot method, but I can't find any .tot file for L Fino.
What should I do now?

And i have same problem
My LG L FINO D290n is show me thats message.
"ERROR: Boot certification verify"
[1110]: Secure booting error.
Can anyone know how to fix iz?

Here is the .tot file: https://drive.google.com/file/d/0BxxUwn_322_KOVhPRjEzb2M0QVk/view
download mode does not work?

Yeah,download mode not work,when i press vol+ then connect usb my screen is show purpple message with text
DBI Apps Watchdog Reset!
DemiGod Crash Handler : DBI Apps Watchdog Reset!
Board Rev.:1.0
Ram dump mode.
Option : SD card ram dump mode.
Push below files to sdcard before test.
rdcookie.txt, rtcookie.txt
Please do following action.
1)Ram dump Mode. Please connect USB.
2)Get the ram dump image using QPST Configuration
3)If sdcard ram dump enabled just wait for reboot
4)Collect ramdump files from your pc or sdcard)
5)Send e-mail to [email protected]

Do you have twrp?
If yes,
does it still work?
PS: I can't help you if you are offline all the time

Yes friend,i have twrp because im try to use all of this solution and nothing happend.
I think this is problem with emmc chip "maybe"...

You tried the .tot method 4imb0t mentioned?
Here is a flashable .zip for the D290N: https://drive.google.com/open?id=0B0rYlJ-tfKhNcFRfdnFlbjlMa3c
I created the zip for myself, because my download mode didn't work.
After flashing, TWRP will crash.
Then you simply have to enter the download mode and flash a kdz.
BUT I'm not sure if this is going to work.
DISCLAIMER:
I'M NOT RESPONSIBLE FOR ANY POSSIBLE DAMAGE DONE TO YOUR DEVICE AS A RESULT OF FLASHING.
I WILL NOT TAKE ANY RESPONSIBILITY FOR BRICKED PHONES OR LOST DATA.

Sorry for long absence, I had no time.. But now I have it, so I want to repair this phone and...
now my Fino doesn't power on... I tried:
1) Power On normally using Power Button
2) Go to Download Mode
3) Remove battery and go to Download Mode
Nothing works..
But when I plug it to computer everytime I hear that Windows sound and in Device Manager I see:
But the screen is still off...
When trying to flash using TOT Method I see:
What to do now?

So the recovery doesn't work?

Yes. Recovery doesn't work, I can't boot to recovery, I can't even boot to Android and the screen is all time black.

You tried this guide here, right?

I just tried it and the result was:
But the phone still doesn't boot and still is being detected as Qualcomm HS-USB QDLoader 9008

Maybe you have to do the last step from this tutorial.
Sry that I can't really help you, but I gave my old L Fino to my mom like a month ago.

4imb0t said:
I just tried it and the result was:
But the phone still doesn't boot and still is being detected as Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
Did you try to boot in download mode and flash kdz ? It's the last step from the tutorial.

I own an LG D290n . I had to do a factory restore via buttons after a Google update bug. It was crashing some Google service and couldn't do anything to fix it. Strangely neither factory restore worked giving me the same exactly error. I finally downloaded the latest Rom I could find I think it was 4.4.2. I pushed it using official Lg Utility from fino page and worked like it should be just fine. After about 2 months the problems continued , the phone stucked at boot with the known pink message dbi error demigod crush etc unfortunately I didn't took a photo. After reading a lot found a guide for unbricking my phone. UNTIL THEN couldn't go into dl mode or anything except factory reset giving me the same error. After the guide using qfil the phone stayed black . Boarddiag passes ap but not emmc. The phone is stuck on 9008 or if I play a little in diagnostic 9006. I played with battery and cable only , the buttons don't work tried vol up . Any guy want my teamviewer to check? Thank you in advance

if boarddiag is not passing emmc test it means your emmc is faulty/dead, no fix for this that I know unless you replace eMMC.

LG DM-01G
I am facing same error, for LG DM-01G.
help please

How can i open my LG LFINO. It already dead set. But before that i shown that was a watchdog error in the screen.

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

Huawei p8lite ALE-L21 total hard brick or can fix?Tried all solutionsns..pls help.

Hi.
I tried to update my mother in law Huawei p8 lite,phone in settings showed there is a firmaware update available,so I done a backup then download via wifi android 6.0,after download complete its asked me to procced so i click to yes,phone restart to upgrade mode but was stuck on 0% progress for very long time so I tried to restart the phone via power off button but after that phone doesnt start again any more.
So I readed a lot what to do but nothing work for me.
I download android 6.0 to pc then copy dload folder to sd card,then when card in phone I pressed volume + and - and power the same time but nothing happend,phone just vibrate once for very short time and nothing.
I tried also using adb procedure but phone is not recognized in my laptop with windows 8,all drivers installed I believe,I have mined all internet for proper drivers,all adb and fastboot drivers installed,included huawei drivers and HiSuite softaware and even Handset WinDriver installed and windows 8 only seen device like on picture below:
{
"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 plugged phone to laptop via usb cable,short vibrate and nothing,so I press power off and volume down same time and laptop see something but not properly,please check below:
ADB not seen any adb device after command "adb devices" .
I can manulally choose driver for that like e.g ADB interface device but ADB still not see anything.
Tried also with disconnected battery couse read on this forum its help sometimes but nothing,still same.
After doing all that just realize sometimes red led blinking so its mean battery is down,and wont charge via usb on the phone,so I charged battery via external charger connected straight to the wires on battery,now red led not blinking.
Tried also on another laptop with windows xp,same ,nothing happend,adb not see anything,but sometimes in device manager phone is recognized as below:
On other forum when is recognized like that its possible to fix but need special usb box,which I ovcourse dont have.
What else I can try?
Summary:
phone not recognized in laptop,even with unplugged battery
phone wont start,no logo nothing
wont update from sd card wiht dload
is it totally brick?
pls help/

Hi!
i think your phone board was damage in process, happened to me on a Alcatel Idol... The same thing. I think the phone was already a bit laggi, no?
.

Phone was not worked properly,thats what my mother in law said.
Its sometimes show just white screen after unlock,or camera wont switch on.
And battery draining fast.I thought firmware upgrade will fix it but its brick now(

Update:I have fixed the phone with dc phoenix software-Installed new board firmware and then stock rom and its all ok now.

alsat1 said:
Update:I have fixed the phone with dc phoenix software-Installed new board firmware and then stock rom and its all ok now.
Click to expand...
Click to collapse
It would be useful if you did a little tutorial with links.
Thank you

MARCOSOFT said:
It would be useful if you did a little tutorial with links.
Thank you
Click to expand...
Click to collapse
I found informations and tutorial on xda forum so its all here

alsat1 said:
I found informations and tutorial on xda forum so its all here
Click to expand...
Click to collapse
Did you have to pay for the phoenix software?

MARCOSOFT said:
Did you have to pay for the phoenix software?
Click to expand...
Click to collapse
Yes 15 euro for 72hours.

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