Database Info

[Q] ATTD800 no fastboot no downloadmode no rec

ATTD800 no fastboot no download mode no rec no
Sorry, my English is not good enough. I will descript as simple as possible.
Background:
I flash the wrong laf.img file (D802) into D800, it caused that I cannot enter fastboot and cannot flash laf.img and cannot flash tot & kdz.
No fastboot, no Download mode, no rec
Current situation:

1When I press power button, it showed LG logo always.

2Cannot enter download mode via volume plus during booting.

3Cannot enter fastboot mode via volume plus during booting

4 I can enter default rec -> factory data reset, but there is no effect no matter what I chose.
5 I can enter “Hardware Key control” via press volume “+” & “-“during booting, but there is no effect no matter what I chose.
6 Since I cannot enter Download mode, kdz flashing was failed.
7 Although there is no download mode, I can enter the tot guide except the last step-> result is failed.
Problem:
According to tot flash result, I supposed that my problem is that I flash wrong laf.img.
So phone cannot enter fastboot and download mode.
The tot flashing didn’t continue since the laf.img was not match with DLL and SW.
Here I have both D800 DLL& tot file and D802, they were all failed
Below is the result of tot flashing
1)select the dll and tot file of 800, Report error: the model and SW were different
{
"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"
}

2)select the dll and tot file of 802, Report error:
fota partition was changed.
LAF retrieveGPT() failed
LAF: Bin_User_Mode
Fastboot.exe tool
Since there is no downloading and fastboot mode, the fastboot.exe display message “waiting for device” and no result.
Addition Info:
The post [http://forum.xda-developers.com/showthread.php?t=2582142], I have read and tried, however it’s different.
This step
Code:
ls /dev/sd*
It should return something like this:
Quote:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda5
/dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
/dev/sdb5 .......... /dev/sdb36
My result:
About the next steps I can not continue.
If I can flash correct laf.img file into phone, all the problem will be fixed, how to do it?
Please help and give me some suggest or solution, thanks for your help.
____________________________________________________________
Status Update
Reason: Druing using fastboot reparire, I flashed wrong laf.img file. And then I can not step fastboot mode and download, my D800 became a brick.
Description:
1. SD card has been formated.
2. There is no TWRP and REC beside LG's default REC (this is no effect after used LG's default REC)
3. Power on G2 ,stuck on LG logo
4. Can not enter fastboot mode.
5. Can enter the first step of Download mode, but I could not go to next step which show double arrows. This impact that I can not flash kdz.
5. For the first step of Download mode, it can flash TOT, however the result is always failed.
Solution:
Refer to this thread -> http://forum.xda-developers.com/showthread.php?t=2687768
The difference between my normal TOT flashing and the TOT flashing from referenced thread is that there are 2 DLL replacements.
Hope these info could help someone.

No update
Hope more people to see this post.

Update
I tried all kinds of methods but no superises. The result is the same as before.
I brought my G2 to LG Repaire Center, the serviceman could not solve it. I can not bellieve that. Will my D800 be a brick really?

bluemaplelu said:
I tried all kinds of methods but no superises. The result is the same as before.
I brought my G2 to LG Repaire Center, the serviceman could not solve it. I can not bellieve that. Will my D800 be a brick really?
Click to expand...
Click to collapse
same is the problem with me.
http://forum.xda-developers.com/showthread.php?t=2680150

raahult said:
same is the problem with me.
http://forum.xda-developers.com/showthread.php?t=2680150
Click to expand...
Click to collapse
Hey, thanks for your info. And I will try these methods from your thread. That's what I only can do. Hope that I am lucky engouth

I flash wrong laf.img file, now it's bircked
Any one can help me

latest firmware for CUBOT X19 upgrade 2020-04-21

{
"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"
}
upgrade 2020-04-21
​The ROM: _X19_9021C_1_V12_20191219 android 9.0
The Tool : SP_Flash_Tool_v5.2112_Win
Driver : WIN7-WIN8 _EXE_v5.1453.03 .rar or Mediatek Driver Auto Installer v1.1352 ( How To Install Mediatek Driver Auto Installer )
Flash Instruction
Cubot X19 System Upgrade: from android 8 to android 9
youtube
If your phone uses the Android 8. You must adhere to the explanation in the video
​
Caution : If your phone already uses Android 9, you must adhere to the following changes :
Click to expand...
Click to collapse
​
We do not recommend you to flash the preloader.bin file using the Flash Tool as it may brick the device. Therefore, always untick the preloader.bin option before starting the flashing process.
Select mode Download Only If you only want to flash images
Click to expand...
Click to collapse
NEXT
[GUIDE] CUBOT X19​

While I flashed the firmware there was no progress. The bootloader was unlocked. Can you please tell me the reason why?

chartek1 said:
While I flashed the firmware there was no progress. The bootloader was unlocked. Can you please tell me the reason why?
Click to expand...
Click to collapse
Instructions to Install​Charge the device battery up to 50%​
Make sure you follow and download all the required files and flash tools on your PC.
Open the flash tool exe file to open the SP Flash Tool User Interface
Tap on the Download option and load both the download agent and the scatter text file in the scatter-loading section.
Once you load the file, click the Download button
To start the upgrade process of stock ROM on your Cubot X19, you need to turn off your device and hold the Volume Down and Volume Up key together and Connect your Phone to PC/Laptop using USB Cable (Keep the Volume Down and Volume Up button until your computer detects the phone.)
When the phone connects, your device will start upgrading the stock firmware
Wait for a few minutes, If you see a green button on your flash tool which means the upgrading process has been completed.
That’s it! You can reboot your Cubot X19

Hello guys;
On the official website they indicate using the "firmware upgrade" option instead to "download only" and update the preloader.bin file. How should I proceed? another question: this process unlocks the bootloader and accesses the root?

[resolved] Lenovo Smart Tab M10 TB-X605F bootloop, recovery ok, fastboot ok, ADB nok and EDL nok

Hello everyone,
after installing TWRP and rooting my device by following this tutorial: TWRP for Lenovo Smart Tab M10 , my daughter did the OTA update without uninstalling Magisk.
Following that the device boot always on TWRP.
Not worried, I thought I had a backup on my pc, but I don't.
On 6 tablets and 4 smartphones, it is the only one for which I don't have a backup!
Not having this backup I tried LMSA, but could not finish the flash.
At best it charge at 84%, then fail.
{
"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 my EDL is corrupted, the device is recognized as QUALCOMM HS-USB Diagnostics 900E (with the error symbol).
And if I force the driver on HS-USB QDLoader 9008, I still have the symbol indicating an error, I manage to pass the EDL verification step of LMSA but next failed.
I have tried directly with QFil but I get the following error: Failed to open com part handle:
Having recovered the stock firmware with LMSA, I tried to restore the aboot partition with fastboot but I get: FAILED (remote: Critical partition flashing is not allowed)
Even if I try to unlock the bootloader.
I have the same error with the sbl1, rpm, tz, fsg and persist partitions.
But I can flash the bak partitions:
As you can see, my device is recognized by fastboot but not by ADB, yet I have the right driver:
I also tried to recompile cache, system and userdata partitions from stock firmware with packsparseimg and imgextractor by following this tutorial: Unpack System_XX.img from Firmware
I can only flash cache, for system and userdata I have the error: Invalid sparse file format at header magi.
But by pressing Enter at the moment of the error, the flash is done:
Despite everything, the device bootloop...
I can no longer, or I don't know anymore install TWRP but I still have access to the recovery mode.
I have spent hours doing all of this to no avail, so I come to ask for your help to help me restore my daughter's tablet.
Thank you.
.

A solution was provided in this thread
Thanks to Yahoo Mike for his help !

ADB Sideload state and error: closed

I have a friend's Nokia 7.1 which got stuck on restarting and is basically bricked right now. I am trying to fix it.
things i have tried:
1. wipe data/ factory data reset from recovery: Kept stuck there and it didn't work out.
2. tried to load stock firmware using SDCARD but it already had the latest firmware so the phone is not accepting any other.
3. Sideload stock firmware but shows error: cannot read zip (no zip- no nothing worked here too)
4. booted to recovery and chose ''apply update from ADB'' :
On checking for adb devices it returns with "Sideload" instead of "Device".
no matter what command i give it returns with Error :closed
{
"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"
}
5. Booted to Download mode/fastboot mode. on giving cmd "fastboot devices" it returns with nothing and on giving any other fastboot cmd it return with <waiting for device> .
******All the adb/fastboot drivers are installed correctly******
6. I tried to get into EDL mode by shorting the EDL points but for some reason it didn't work either, I suspect the points i tried to short it with were wrong and right guide is not available.
8. Nokia OST tool gets stuck at "getting product id" and tried OST tool for every other thing but it doesn't work.
7. Authorized Service center said it cannot be repaired and suggested Motherboard replacement. (Sense-less to do so.)
+++++++++++++++++++++++++++++++++++++++THANK YOU++++++++++++++++++++++++++++++++++++++

while in adb sideload mode: Device manager shows this but not adb driver.

mouryas911 said:
I have a friend's Nokia 7.1 which got stuck on restarting and is basically bricked right now. I am trying to fix it.
things i have tried:
1. wipe data/ factory data reset from recovery: Kept stuck there and it didn't work out.
2. tried to load stock firmware using SDCARD but it already had the latest firmware so the phone is not accepting any other.
3. Sideload stock firmware but shows error: cannot read zip (no zip- no nothing worked here too)
4. booted to recovery and chose ''apply update from ADB'' :
On checking for adb devices it returns with "Sideload" instead of "Device".
no matter what command i give it returns with Error :closed
View attachment 5412847
5. Booted to Download mode/fastboot mode. on giving cmd "fastboot devices" it returns with nothing and on giving any other fastboot cmd it return with <waiting for device> .
View attachment 5412851
******All the adb/fastboot drivers are installed correctly******
6. I tried to get into EDL mode by shorting the EDL points but for some reason it didn't work either, I suspect the points i tried to short it with were wrong and right guide is not available.
8. Nokia OST tool gets stuck at "getting product id" and tried OST tool for every other thing but it doesn't work.
7. Authorized Service center said it cannot be repaired and suggested Motherboard replacement. (Sense-less to do so.)
+++++++++++++++++++++++++++++++++++++++THANK YOU++++++++++++++++++++++++++++++++++++++
Click to expand...
Click to collapse
This forum is for...Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum.
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com

How To Guide Guide to Remove Orange State Error Fix For Realme GT Neo 2 (Android 13 RUI 4.0)

Guide to Remove Orange State Error Fix
Tested on Indian region
(May not work on another region)
NOTE: I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS IS DONE BY YOUR OWN JUDGEMENT IF YOU WANT TO DO THIS OR NOT.
It's possible to flash. Modified partition/image file without a bootloader unlock but I'm not 100% positive. .
Requirements:-
Qfil Tool (QPST)
Qualcomm EDL Mode Drivers
Firehose Programmer SDM870
abl.img (new edited)
Steps:-
Step 1: Download the given files.
Step 2: Install Qfil (QPST)
Step 3: Make sure you go to configuration then firehose settings and change from emmc to ufs and do the same as shown in below image.
{
"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"
}
Step 4: Turn off your phone and boot into edl mode
Step 5: Install the Qualcomm drivers by right clicking on the qbulkhub thing and click properties then the driver tab click update then search automatically.
Step 6: Open Qfil tool then load the firehose file in programmer path
Step 7: don't worry about the XML path and stuff just go on the top click tools and partition manager
(NOTE: if there's no port open or the partition manager won't open, try rebooting into edl mode again)
Step 8: Window should pop up with a list of partitions, right click on the abl that you want to flash and then click on Manage Partition Data option then click on Erase option (abl partition will be erased) then click on load image and select and load the given abl.img file
Step 9: Exit from the Qfil tool
Step 10: Reboot your phone
Enjoy!

@Samyak_05
Will this fix work on European GDPR version rom? Also in step 4, how to boot in EDL mode? Thank you for any help
Edit: I finally managed to boot in EDL mode and completed the process with success. Thanks for a perfect Orange State Error Fix.
​

nikoum said:
@Samyak_05
Will this fix work on European GDPR version rom? Also in step 4, how to boot in EDL mode? Thank you for any help
Edit: I finally managed to boot in EDL mode and completed the process with success. Thanks for a perfect Orange State Error Fix.
​
Click to expand...
Click to collapse
What firmware version were you on before you fixed orange state?

ESD444 said:
What firmware version were you on before you fixed orange state?
Click to expand...
Click to collapse
I got the orange state warning when I upgraded to ui 4.0 android 13 (rmx3370gdpr_11_f.02). I was on ui 3.0 android 12 and if i recall the version was rmx3370gdpr_11_c.07 or c09

nikoum said:
I got the orange state warning when I upgraded to ui 4.0 android 13 (rmx3370gdpr_11_f.02). I was on ui 3.0 android 12 and if i recall the version was rmx3370gdpr_11_c.07 or c09
Click to expand...
Click to collapse
So following this post you got rid of orange state?

ESD444 said:
So following this post you got rid of orange state?
Click to expand...
Click to collapse
He is saying he got orange state after updating to rui 4 Android 13 "not in Android 12"

Just to inform anybody, I received a new update RMX3370_11_F.03 and after the update I got the orange state warning back again. So I had to apply the fix again.

Yes you have to apply it again

hi,
i'm triying to fix this orange state problem but can't find abl partition in partition manager, can you please tell me what is the partition i have to erase and flash?
Edit: Ok in fact i don't have to check "customize fysical partition" in configuration. abl is in LUN 4 but i only seen LUN 0 when this case is check.