Develop Bugs

[Q] Broken from update to Lollipop (stuck in fastboot)

I've seen some other people with this problem, but there have been no fixes.
The problem is that the phone was updated to Lollipop. It worked for a little bit, but after a couple of minutes lots of programs started force quitting, and it eventually turned off.
When it turns on, it takes about 20 minutes, and then goes into fastboot mode.
If I try to get into download mode, it stays on download mode for around 15 seconds, and then it continues into fastboot mode. Windows does not recognize the phone in download mode, so I can't restore anything from there.
What I have learned then is that I need to flash the laf.img file, which I got from download the official firmware from LG's website by inserting my IMEI, so it's the right version, and then trying both fastboot flash laf laf.img, as well as fastboot
boot laf.img. The problem is that they both fail writing, but it's not just that command. I can't do fastboot erase recovery, or fastboot erase anything, only thing that works is fastboot reboot.
Does this mean that the internal storage is broken? Is there anything else I can do? I can execute fastboot commands, but it seems like I cannot write anything. The drivers seem to be working, as it's recognized as a fastboot devices, but it only says
? fastboot devices
All commands result in a error(failure or something like that. I've removed the SD card as well, as I heard that might cause problems. As far as I know, I need to flash the laf.img to get into download mode, and from there on can flash via kdz.
Help please? This kind of sucks..

When you write a command, does it show on the phone?
You might need to change the driver in device manager. Look for "Android", update driver, browse my computer..., let me pick from a list, and here you'll see 3 different drivers, what you want is "Android bootloader interface"

hi
Hi dear frends.
Its sad to know that all you guys cant go to download mode or facing security error or stuck in lg logo or in fastboot mode
And some guys stuck qhsuab bulk 9008
So the solution is here.
If you are unable to get into download mode then you need to force your g3 into qhsusb bulk mode by shorting the test point.
I will help u all guys.....
I will help u to unbrick ur any lg model wothout download mode or stuck in 9008 or anytype of problem.
Please let me know your problem in pm.

[Q] Bricked N7 2013 LTE

Hi everybody,
I own a N7 2013 LTE (deb) with Android 5.1.1 installed (build: LMY48P). This morning I've tried to turn on my device and it remains stuck on Google logo.
The device correctly goes into Fastboot mode but from here I cant do anything:
Start: see the Google logo and stuck
Restart bootloader: correctly reopen the bootloader
Recovery mode: see the Google logo and stuck
Power off: correctly power off
These are the informations showed in the Fastboot screen:
FASTBOOT MODE
Product Name: deb
Variant: deb 32G
HW version: rev_e
BOOTLOADER VERSION: FLO-004.05
BASEBAND VERSION: DEB-Z00_2.44.0_0213
CARRIER INFO: None
SIGNING: yes
SECURE BOOT: enabled
LOCK STATE: locked
I've downloaded Nexus Root Toolkit v2.05 by WugFresh and the device is correctly seen from my windows pc and from NRT (I've succesfully installed USB drivers).
From NRT I've tried to "Flash Stock + Unroot" but I cant flash because the bootloader is locked; so I've tried to unlock the bootloader from NRT, the N7 correctly show the "Unlock bootloader?" screen, I move to "YES" with the volume keys but when I push the power button to confirm, nothing happens and the tablet continues to show that screen (I've waited about 30mins and nothing happens).
I dont care about user data and my photos and videos; I'd like to have my tablet working.
Some questions:
1) is there a way to launch a stock recovery or a TWRP recovery from NRT so I can wipe all data and have my tablet back working?
2) is there a way to see from NRT le log? I'd like to see some more specific error details when I try to unlock bootloader and it fails.
3) do you have some advices? thanks in advance
Thanks guys

M9 failed update = lots of trouble....

Hello and thanks for taking a look at my issue,
So a failed update to the firmware from 5.0.2 to 6.0 led to all kinds of frustration these last few days.
Currently download mode reads:
***RELOCKED***
htc_himaulatt PVT S-ON
LK-1.0.0.0000
Radio-01.01_U11440601_72.02.50602A_F
OpenDSP-v29.2.6-00492-M8994_0702
OS-2.11.502.18
Sep 7th 2015, 23:04:14(591203)
then the security warning and then SD NOT Mounted
At one point I was able to get into OEM Android Recovery which enabled me to get TWRP back on and restore a virgin 5.0.2 system.img on but it kept rebooting every time a call came in or went out text seemed to work fine though but then the phone would reboot about every 3-5 min. I gave a shot at an upgrade to 2.11.502.18 ruu.exe via parallels and Win7 it failed but the bootloader recognizes it but the phone itself thinks it's still 1.32.502.32 and on 5.0.2 not 5.1
I currently can't seem to get adb or fastboot to recognize the device on the Mac side, which I prefer working in, but the computer still asks me which side I want to connect the phone to OSX or Win7. I've tried to put the rom.zip, renamed OPJAIMG.zip, in sdcard and boot to download by holding vol down + power but it does not want to read the SDcard. I seem to currently have no recovery as well right now because I get the recovery failed text when booting into recovery.
I've had this phone as an AT&T business line purchase and it shipped about 2 weeks prior to major release date and when the stores started getting them in stock. The phone seems to be a bit more stable now but will randomly reboot upon awakening the screen...
Again thanks for your help and suggestions!

Its not a O in 0PJAIMG.zip. its a 0 as the number. and the sd card needs to be under 32gb.

A-ha, Thanks for that! Unfortunately I do not currently have a chip under 64g. I may get my hands on one though. On an upside though I went in and found that my fastboot needed to be updated on the mac side, as adb was working but fastboot wasn't. So fastboot is up again and now having an issue with flashing a recovery to the phone. Download mode shows that I'm on 2.11.502.18 but the phone when in OS still states that i'm on 1.32.502.32. I guess I'll recovery for 2.11.502.18 next.
Thanks again

S8311 / MT6592 (MT8392 is Fake!) / Hard bricked / SP Flash

Hi All
following history to my question:
-> S8311 rootet
-> Mtk_Droid_Tool_v2.5.3 reports
Hardware : MT6592 (MT8392 is Fake!)
Model : LIFETAB_S831X
-> made full backup with Mtk_Droid_Tool_v2.5.3
-> did CWM Recovery Flash with Mtk_Droid_Tool_v2.5.3 (build-in-feature)
-> hard bricket
The device is now in a boot-loop.
Only the vendor logo appears cyclic.
Holding Vol+ the normal device menü appears (Recovery Boot, Normal Boot, FastBoot Mode, UART boot).
Recovery, Normal, UART does not work anymore -> BootLoop.
FastBoot Mode works, connection to PC is fine. All me tries with
-> fastboot oem unlock
-> fasboot boot ...
-> fastboot flash ...
-> fastboot getvar ...
did not work out - error message points to unlocked bootloader.
Holding Vol-, a chinese system diag menu appeared pre bricking - now it is not available anymore -> bootloop
The MTK Preloader seem to work. Befor vendor logo appear, PC get Preloader device which disappears again after 2 seconds (with is ok from my point of view)
Now my problem: I would like to restore with SP Flash the Mtk_Droid_Tool_v2.5.3 Backup. I loaded the scatter file, for test purpos only ticked recovery and press download.
Inserting the USB cable the preloader gets recognized and process begins - but ends after 1 seconds at 100% DA and the well known 2004 error. I tested following Versions with same result (3.1216, 3.1344, 5.1352, 5.1452, 5.1628). The log file from SP shows that communication takes place, hardwareinfos are retrievied and ends up with the error.
08/05/16 14:50:14.099 BROM_DLL[1360][8396]: DEBUG: BRom_Base::Write8DataWithEcho(): =0, cmd(0xD7) (FlashToolLib/sv5/common/interface/src/brom_base.cpp:1289)
08/05/16 14:50:14.287 BROM_DLL[1360][8396]: ERROR: BRom_MT6276::BRom_WriteBuf(): Read16Data(): Status returns error (0x2001)! (FlashToolLib/sv5/common/generic/src/brom_mt6276.cpp:1153)
Any ideas, tipps or options I could go for?

i can't even go to the Fastboot mode

i have kind of the same issue
HI there how is it going
so here is my problem. my girlfriend purchased one of those tablets on aliexpress and it turns out it is totally not what she should have gotten as per the sellers description, so i decided to root it well not i have a tablet that wont power or boot but it registers with my computer(yes even when completely turned off) so I'm assuming it is a flash F&ckup, i cant find the firm ware anywhere so here are the spec
processor MT6592V
Mother board number make and module are
Lantek-06 E253439 94V-0
K10006P9-MB-V1.0-20B3
there is also a 10-1
with 2023
underneath it
i think it screwed up when i tried flashing twrp recovery on it.
ive looked up many firmwares for MT6592 processor and tried installing them with SP Flash tool as it is for mtk devices
i did successfully unlock the bootloader
i am not sure thought if the root was successful.
sio any help or infomation you can provide would be amazingly helpful
thanks Curtis

Bricked moto g8 ?

Hi all, i have a moto g8 from a little bit more of 2 years (so warranty is expired) and some days ago i found that the phone was constantly rebooting (blue screen with Motorola logo loaded for about 5 seconds, black screen and repeat in a loop).
I don't know if this is the right topic where posting, otherwise I apologize and ask where to write.
First of all, I know that I have been a fool since I didn't activate the develper mode and the USB debugging (I didn't needed on previous phones), blame on me.
Since it seemed a software problem, first of all I went in recovery mode and I found
Code:
AP Fastboot Flash Mode(Secure)
BL: MBM-3.0-rav_reteu-a863e9dc072-220330
Baseband: M6125_43.45.03.49R RAV_EMEADSDS_CUST
Product/Variant: rav XT2045-2 64GB PVT1
Serial Number {i do not put it here}
CPU: SM_NICOBAR 1.0
eMMC: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000000000004 {maybe more or less zeroes, i wasn't able to count exactly}
DRAM: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
Console [NULL]: null
Tools Mode Config: DISABLED
Power OK {it's charging}
oem_locked
Transfer Mode: USB Connected {it's charging}
I found that
- the graphics tests and locale tests appeared fine,
- the /system folder cannot be mounted,
- in the reset option only the factory reset was available (not possible to only wipe the cache)
so I went for a factory reset, but unfortunately this did not solve the issue (still loading the os for some seconds and then rebooting).
So then i tried installing the android sdk on the pc and using adb (not working because missing the usb debugging and developer mode), even in a sideload to push a new image (as an update from adb or SDcard or using fastboot), i tried pushing both a whole image or pieces (as boot.img or bootloader.img), but all these actions failed due to some errore related to the signature.
Then I tried to unlock the bootloader using the online procedure and that was successful, but I found no difference after this action (still errors about the signature)
So I don't know if I'm not pushing the right images or, since I didn't activate the usb debugging, (and the oem_locked) I cannot do anything and the phone is almost bricked.
Consider that I'm not a tecnician (i learned programming but all these things about phones are new and in the last days I tried putting together different pieces of information from internet). Moreover, I'm without internet connection (i was relying on the phone hotspot) so i will be able to check replies about once a day.
Please can you help me?
Thanks a lot in advance

Try doing a hard reset IF that doesnt help Try another os

GrundigGrey said:
Hi all, i have a moto g8 from a little bit more of 2 years (so warranty is expired) and some days ago i found that the phone was constantly rebooting (blue screen with Motorola logo loaded for about 5 seconds, black screen and repeat in a loop).
I don't know if this is the right topic where posting, otherwise I apologize and ask where to write.
First of all, I know that I have been a fool since I didn't activate the develper mode and the USB debugging (I didn't needed on previous phones), blame on me.
Since it seemed a software problem, first of all I went in recovery mode and I found
Code:
AP Fastboot Flash Mode(Secure)
BL: MBM-3.0-rav_reteu-a863e9dc072-220330
Baseband: M6125_43.45.03.49R RAV_EMEADSDS_CUST
Product/Variant: rav XT2045-2 64GB PVT1
Serial Number {i do not put it here}
CPU: SM_NICOBAR 1.0
eMMC: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000000000004 {maybe more or less zeroes, i wasn't able to count exactly}
DRAM: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
Console [NULL]: null
Tools Mode Config: DISABLED
Power OK {it's charging}
oem_locked
Transfer Mode: USB Connected {it's charging}
I found that
- the graphics tests and locale tests appeared fine,
- the /system folder cannot be mounted,
- in the reset option only the factory reset was available (not possible to only wipe the cache)
so I went for a factory reset, but unfortunately this did not solve the issue (still loading the os for some seconds and then rebooting).
So then i tried installing the android sdk on the pc and using adb (not working because missing the usb debugging and developer mode), even in a sideload to push a new image (as an update from adb or SDcard or using fastboot), i tried pushing both a whole image or pieces (as boot.img or bootloader.img), but all these actions failed due to some errore related to the signature.
Then I tried to unlock the bootloader using the online procedure and that was successful, but I found no difference after this action (still errors about the signature)
So I don't know if I'm not pushing the right images or, since I didn't activate the usb debugging, (and the oem_locked) I cannot do anything and the phone is almost bricked.
Consider that I'm not a tecnician (i learned programming but all these things about phones are new and in the last days I tried putting together different pieces of information from internet). Moreover, I'm without internet connection (i was relying on the phone hotspot) so i will be able to check replies about once a day.
Please can you help me?
Thanks a lot in advance
Click to expand...
Click to collapse
The easiest thing to try next is LMSA rescue and reflash firmware.
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

@goginator
I did a hard reset and nothing changed
About installing another OS, the phone is not rooted, TWRP is not installed and USB debugging is not activated, is it possible to install a new OS?
@sd_shadow
I tried the LMSA, using the "Rescue" option, it was executed successfully (from the PC message) but on the phone nothing changed, the phone is booting but after few seconds of the blue screen with yellow motorola logo, it stops and reboots itself
After all that and after some boot trials, I have now the following screen
Code:
Boot Failed, Press POWER KEY to Retry
[some other staff]
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
cmd: getvar:slot.count
cmd: getvar:all
cmd: getvar:slot-count
cmd: oem hw dualsim
The "No bootable A/B slot" does not sound promising

I've had it happen before, it's because the system failed to decrypt your phone at boot, so your phone is just loaded into this empty OS until it crashes and keeps looping
to fix it:
1- download the rescue tool on your windows computer
2- boot the phone into fastboot mode by holding the power & volume down button while the phone is turned off
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3- connect the phone and hit the rescue option, the program will download the firmware for your model and flash it onto your device

GrundigGrey said:
I tried the LMSA, using the "Rescue" option, it was executed successfully (from the PC message) but on the phone nothing changed, the phone is booting but after few seconds of the blue screen with yellow motorola logo, it stops and reboots itself
After all that and after some boot trials, I have now the following screen
Code:
Boot Failed, Press POWER KEY to Retry
[some other staff]
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
cmd: getvar:slot.count
cmd: getvar:all
cmd: getvar:slot-count
cmd: oem hw dualsim
Click to expand...
Click to collapse
This is exactly what I did before, without success: after trying the "Rescue" option, I get
Fastboot Flash single partition
Flash Failed, please try again