So, here's the story: I wanted to root my d850 on LP version D85021R, Tried all methods posted here, including this, this, and this. None worked. So I decided to downgrade to KK using tot/kdz method by hyelton. Downloaded LGD850AT-01-V10d-310-410-JUN-19-2014+0.tot file and LG flash tool 1.8.x and flashed the tot file. Progress went above 85% and then phone rebooted, but never came back to life; super-bricked, no led, no boot screen, no download mode, no recovery mode, NOTHING! except that it identified as QHUSB_BULK in Win7, which upon installation of drivers turned to qhsusb_dload 9008. Tried all unbricking methods including Board Diag, Flashtool ,etc. none worked. So I took it to a repair guy, who probably used octopus box to copy image from another g3 (at least that's what I think, he would not let me see but i sort of glanced over). After copying that image to my g3, it turned back to life, i.e., boot screen appeared and download mode/recovery mode worked, but it was in a boot loop. however, that guy also tried flashing V10D using flashtool, and same thing happened, i.e., super-brick again. After a day of trying he gave up on it but was kind enough to give it back half alive. So now boot screen appears, download mode works, gets recognized as LGE Mobile USB Serial Port, and LGE Android MTP Device with a yellow triangle. I cannot access fastboot mode due to locked bootloader, or else I would have tried flashing partition images through fastboot, as bootloader and boot partitions are intact, so I would not touch them but could try flashing other partitions. LG Flashtool flashes the whole package so the boot sector also gets over written, which somehow is not compatible with stock rom. One thing which I have not mentioned is that I did not buy it new but refurb one, so may be some part was changed, but which one, no idea. I tried to get it recognized it in linux, but does not work; shows up as libmtp-1-1 in /dev, which is not mountable. However I was able to pullout one interesting fact, which might give some hint. dmesgs shows a serial number for this device which starts as LGD855xxxxxxx, whereas the serial number printed on the back is different, where it shows as d850 and serial number is also different, i.e., 406KPXVxxxxxx.
Now I am out of options. Can someone please suggest what else to do. Also, can someone confirm that the serial number shown in dmesgs when connected to USB port, starting with LGD855xxxxxx can be a d850?
Any help is welcome
First off when flashing almost every time it'll fail at 85%. That's normal. Anything after80% is just rebooting of the phone.
Now what your having is not normal. Maybe whatever the repair shop did changed the serial? And your issue usually means your bricked completely sadly.
Before your downgraded, was your phone booting normally or did the root do something to make it originally boot loop before trying to downgrade ?
Sent from my iPhone using Tapatalk
Thanks for replying hyelton. I fully understand that and also that rebooting should bring the phone to blue reset screen, but it didn't. Instead it died.
The serial number and IEMI fortunately are intact, and are read by firmware when present. Sadly I tried to flash the firmware again through Board DL option, but failed again, so back to QLoader 9800 mode. On WinXP, smart boot diagnostics recognized it and proceeded to flash boot/recovery, but sadly the accompanied AP_Chip file neither has D850 nor D855 Smart_Boot.bin files. So I flashed EUR xxxx.xxx version. Phone still dead, but no Qloader 9800 mode, instead Android Phone device started showing up, which had no supported drivers. After some effort, Windows 7 download drivers and it got recognized as AlCatel Android Phone, lol! No adb and fastboot in Windows, and no Serial communication was possible. I tried linux and there fastboot was showing a device without id, like ??????????, but it did allow me to flash individual mbn paritions extracted from D850 tot to their respective partition, but I discovered I cannot flash through fastboot files larger than 2GB, so no system and no userdata; those were erased only. Upon reboot and return to windows, phone is still dead (without any life) and back to Qloader 9800 mode.
So now I'm stuck due to lack of firmware files. I am afraid to flash a boot or recovery partition extracted from any other firmware, but can try D855 since it worked partially to bring download/recovery partitions and LG logo was also displayed upon turning on. I think it even booted basic kernel in download mode, because I was able to send reboot command through Send_Command.exe and it rebooted. So scripting was also a possible option, but not anymore.
Is the partition layout of D850 and D855 available somewhere? I tried to find but could only find for D851. If someone having these variants is willing to help, I'll post the commands to get partitions layout, or even partition images could be created using dd command if phone is rooted.
To your question, no, the rooting methods did nothing. It was working normal. But somehow I came across a lot of threads that suggested hassle-free downgrading to KK for rooting, and pointed to your guide which surely is hassle-free but not for a troubled phone like mine
BTW, I do have Flashtool log files for original downgrade and then reflashing yesterday. If someone wants to take a look...
Further development: Today I visited the main mobile market in my city, and first went to same shop from where I bought this set. They had a number of other sets in the same batch, so I copied partition tables info and prop files from each device. Also, I had to buy the same set for a friend. I have asked him to lend it over to me for weekend. Now, first I'll try to find the rom versions installed on these sets and see what I can do.
Secondly, is there a way I can copy the whole emmc partitions from alive phone to dead phone? The dead phone can be accessed on serial port. I know I can get partition dumps, but how to write them on bricked phone, that is the question. There must be a software that can access emmc through phone ports and clone it. Help please!
unikorn74 said:
Further development: Today I visited the main mobile market in my city, and first went to same shop from where I bought this set. They had a number of other sets in the same batch, so I copied partition tables info and prop files from each device. Also, I had to buy the same set for a friend. I have asked him to lend it over to me for weekend. Now, first I'll try to find the rom versions installed on these sets and see what I can do.
Secondly, is there a way I can copy the whole emmc partitions from alive phone to dead phone? The dead phone can be accessed on serial port. I know I can get partition dumps, but how to write them on bricked phone, that is the question. There must be a software that can access emmc through phone ports and clone it. Help please!
Click to expand...
Click to collapse
Flash it to D855 Lollipop version via octopus than write DUMP
It does work, indeed. We did it together, didn't we, aamszia?
To elaborate further, Aamir helped me out by writing D855 bootloader through octopus box. That was done before but flashing a KK rom again bricked it. Only this time, he flashed a d855 lollipop kdz rom (v20g, if I remember correctly). That made it functional; everything worked, except radio. Flashing a d850 LP radio would not work; flashing a KK radio would brick it. So I took a dump of mmcblk0 from a fully functioning, rooted, recovery flashed LP d850, via terminal using dd command (I chose to write only first 4gb or so due to smaller sdcard I had. That covered all partitions except cache and userdata, which were not needed anyway). Then I wrote back the dump on the bricked d850 using dd command from terminal. I tried flashing TWRP on it first, but somehow it did not work, and gave secure bootloader error. So I had to do it via terminal. I knew once it starts writing, the system would become unstable due to overwriting of partition table, kernel, system, and stuff, but I had to give it a try, and it worked! Screen went off immediately, but I touched it again after half an hour; pulled out and reinserted the battery; tried recovery and there it was. Rest was easy. Just formatted cache and data, and my phone was back to life.
Related
I really need some serious help and advice. Could anybody who is experienced it this filed please help me, or even put me in the right direction.
I am stuck in the qualcomm download mode with my device as QHSUSB_Dloader9008.
Yes it is a hard brick and 99% of the google searches have just confused me.
So here is the story.
I was developing for the Lg Vista D631, and trying to port a rom from the v10lte tablet due to the exact same architecture. The only main difference was the screen size.
Anyhow i was using fastboot to mess arount with the LG Security Error but nothing worked.
I didnt find out that much. So i just flashed back stock and then restored from cwm.
Well i went back to fastboot to try some more and i typed fastboot erase aboot, all went well. Then as i was in the middle of typing fastboot flash aboot my dang phone battery fell out my phone. And this is what i recieved... It Took it off my cmd prompt screen, i now have a nice crack in the screen, and a wonderful bricked phone....
It read up as Android Net USB, and it also came up as a removable disk with 64mb free on it. so i looked and i looked for something just to flash the aboot partiton back to the phone. But nothing came up. I even tried win32 imager.
I googled jtag and read that there are test points which would i could short to reset the devices bootloader to the wualcomm safe bootloader to flash the emmc chip and partition table back to stock. Which would thus repair the partition and open up recovery and or download mode.
I attempted to trace the circut to find out what point to short' and yea i even tried a few which only reset the phone. So i said screw it and formatted the removable disk....... And bam my pc detected a new device and installed the qhsusb dload9008 driver.
So now im in qpst fail safe download mode, i have it set to com41, and qpst detects it too.
And now th issue and question at hand.. I need the files to flash an msm8296. As the mbn, hex, and what nots are all not working with me. Do
When i try to use eMMC downloader I just kept getting the same response from qpst 4.0.2.
"Download failed could not communicate with flash programmer"
then in software download i keep recieving that the hex file is invalid, and could not detect the hex scrambling method. The file is invalid.
I have the lg d631 and have many unofficial kdz files i compiled. I could use the vs88010b for any other ones needed too. As i found out which ones are compatible through my testing phase.
When thia gets fixed though, the development for this phone will skyrocket, as anything will be possible.
So i am stuck. I messed up. And need to fix my mistake.
djacks222 said:
I really need some serious help and advice. Could anybody who is experienced it this filed please help me, or even put me in the right direction.
I am stuck in the qualcomm download mode with my device as QHSUSB_Dloader9008.
Yes it is a hard brick and 99% of the google searches have just confused me.
So here is the story.
I was developing for the Lg Vista D631, and trying to port a rom from the v10lte tablet due to the exact same architecture. The only main difference was the screen size.
Anyhow i was using fastboot to mess arount with the LG Security Error but nothing worked.
I didnt find out that much. So i just flashed back stock and then restored from cwm.
Well i went back to fastboot to try some more and i typed fastboot erase aboot, all went well. Then as i was in the middle of typing fastboot flash aboot my dang phone battery fell out my phone. And this is what i recieved... It Took it off my cmd prompt screen, i now have a nice crack in the screen, and a wonderful bricked phone....
It read up as Android Net USB, and it also came up as a removable disk with 64mb free on it. so i looked and i looked for something just to flash the aboot partiton back to the phone. But nothing came up. I even tried win32 imager.
I googled jtag and read that there are test points which would i could short to reset the devices bootloader to the wualcomm safe bootloader to flash the emmc chip and partition table back to stock. Which would thus repair the partition and open up recovery and or download mode.
I attempted to trace the circut to find out what point to short' and yea i even tried a few which only reset the phone. So i said screw it and formatted the removable disk....... And bam my pc detected a new device and installed the qhsusb dload9008 driver.
So now im in qpst fail safe download mode, i have it set to com41, and qpst detects it too.
And now th issue and question at hand.. I need the files to flash an msm8296. As the mbn, hex, and what nots are all not working with me. Do
When i try to use eMMC downloader I just kept getting the same response from qpst 4.0.2.
"Download failed could not communicate with flash programmer"
then in software download i keep recieving that the hex file is invalid, and could not detect the hex scrambling method. The file is invalid.
I have the lg d631 and have many unofficial kdz files i compiled. I could use the vs88010b for any other ones needed too. As i found out which ones are compatible through my testing phase.
When thia gets fixed though, the development for this phone will skyrocket, as anything will be possible.
So i am stuck. I messed up. And need to fix my mistake.
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
We cannot provide technical support nor can other members reply to your posts here on XDA Assist. There is no forum specifically for the LG Vista at this time but you may want to ask your question with all relevant details in the friendly general Android Q&A, Help & Troubleshooting forum at http://forum.xda-developers.com/android/help where you have already posted several times. Since your device is relatively uncommon, please be patient and give the experts plenty of time to respond. I also see a number of references to your model from a site search at http://forum.xda-developers.com/sitesearch.php?q=lg vista which might be worth reviewing.
Good luck!
This thread is closed.
Hi there,
Today i've received this tablet. All good and dandy until it notified me it has an update so obviously i've gone and do the update. Surprise.. after reboot, update installment and so on the device won't boot anymore at all, and recover mode doesn't work to enter.
I've found official ROM package on their site:
ftp.vonino.org/public/Firmware/Vonino_Tablets/Pluri%20Q8/Orange%20Version/Android%206.0/
Tablet can connect to the PC, but it isn't recognized because "some drivers" missing. How can i install this ROM on the tablet from my pc ?
Thank you.
Hi,
I can't find anything about it on xda or anywhere. You'll need to contact the manufacturer for drivers and instructions on flashing their firmware.
Good luck!
After i tried like almost the entire day i got the tablet in rescue mode or fastboot mode..
I've wiped/data or factory reset and the same happens... it stays in a loop when boot at logo.
I've let it to do so until the battery went dead from 100% and still the same.
I have official ROM but can't install it at all. I think the bootloader is locked?! And it doesnt even unlock it when using some fastboot commands
Also can't install nothing from SD card and when tryin to use ADB the PC can't see the device, but when using fastboot I can work on it.
In rescue mode i've done some root integrity check and at the end of the check some /system files are modified. I believe this is causing the entire problem.
denede said:
After i tried like almost the entire day i got the tablet in rescue mode or fastboot mode..
I've wiped/data or factory reset and the same happens... it stays in a loop when boot at logo.
I've let it to do so until the battery went dead from 100% and still the same.
I have official ROM but can't install it at all. I think the bootloader is locked?! And it doesnt even unlock it when using some fastboot commands
Also can't install nothing from SD card and when tryin to use ADB the PC can't see the device, but when using fastboot I can work on it.
In rescue mode i've done some root integrity check and at the end of the check some /system files are modified. I believe this is causing the entire problem.
Click to expand...
Click to collapse
Typically, on devices I know of, it's fastboot that you would use to flash factory images. So you should be good there. But again, I don't know if that is how your device works too. And it would also typically not matter what's been altered on your device, system wise, you would simply flash the appropriate images with fastboot.
So I'd still say you need to determine the correct procedure to flash the files you got from their site. Perhaps there site has instructions? Or a support number for help of its not working as it should?
I've talked with the support. They gave me a link with an official ROM, a different one that the one that was from the site. But they didn't even told how to use it, LOL.
Have the damn files and don't know what to do with them, OMG.
I've placed the zip archive on SD card and tried to use the option from rescue mode with 'update via sd card". The zip archive is visible but after i select it says Installation aborted :|
I've googled around and maybe my tablet needs to be at over 50% power... but it was plugged into the wall it should've worked.
edit: 100% and no good...
edit2: they sent me another e-mail with a pdf file in which it is explained how to flash their device.
Hello everyone,
let me start off with what I want:
1. I want to know if I understood it correctly and I can save my device by using another device's (of the same make and model) backup.
2. Hopefully, anyone knows where to find a suitable backup.
Device: Lenovo TB-8704f
Device Situation:
I flashed pretty much badly over every storage in my attempts of doing something useful. Boot and system are flashed with non-working software, so for all purposes, we can regard them as empty. Recovery has TWRP on it.
How did I get here?
So, this part is only if you're interested in why I was this stupid. I tried to condense all the relevant information about my problem above. Anyway, I checked if my tablet has custom firmware and I found one. I overlooked that the firmware said 8703 instead of 8704. So I was convinced I had a working ROM. Now, I am very inexperienced with Android flashing, and when I fastbooted the device to run TWRP, the guide said, I could boot it directly from fastboot with
Code:
fastboot boot twrp.img
and I could then flash it if I wanted. Well, I did not read up on it beforehand and so I went in with
Code:
fastboot flash boot twrp.img
. Bye, bye boot partition. After doing it finally right, I got it running and wiped my system, then copied over the zipped custom ROM and after a few attempts, I finally read the error message careful enough to see that it stated that my device wasn't compatible. At this point, I started to figure out how to go back to stock, since I had no backup due to my previous flashing mistake. Well, I found the firmware from some Russian forum and a few guides that described how I could load it onto the system with QFIL. After spending hours trying to do that, I finally understood what my issue was. All the guides were speaking about the 9008 Port for QFIL. And I only saw a diagnostics port. Found a thread about a different Lenovo device in which it was explained that the diagnostics port was a stripped down 9008 protocol. And it couldn't load any data. Well, that explains my failing. Now that other device could be put in the 9008 by unplugging the battery and holding down up and down button while reconnecting, but I don't have the tools to perform surgery on my tablet, so I just decided to leave it bricked until finally hopefully someone brings out a custom ROM. That was two weeks ago and in the meantime, I had the idea of asking you guys if anyone has a TWRP backup and/or if that would help me in my situation.
Code:
Boot failed. Press POWER KEY to retry.
Your device didn't start up successfully.
Follow these instructions if the failure cannot be recovered after retrying.
If this is a Verizon device, please use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant.
If this is not a Verizon device or Software Repair Assistant did not help for any reason, please contact customer care for furthur assistant.
AP Flashboot Flash Mode ( Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
Hi everyone,
I've wanted to root my Android phone for a while now, so I decided to do it these holidays, following instructions on getdroidtips ( How to Install Lineage OS 17.1 for Moto G8 Plus | Android 10 [GSI treble] (getdroidtips.com) ). I couldn't boot into TWRP recovery mode for some reason, (maybe it didn't install properly) so I tried to install Havoc OS using ADB. My phone then rebooted several times and then gave an error message, saying I could either try rebooting again or factory reset. I chose factory reset and went through the whole process again twice, the third time with Lineage OS. It then gave a different error message (in the code block). I can use the volume keys like in the bootloader, but couldn't get it to boot. I also can't access the phone over ADB.
This was my first time messing with Android beyond basic ADB commands, so I didn't really know what I was doing. I might have messed up the instructions or made some other mistake. All of my data is backed up, so all I'm hoping for is to either boot Lineage OS or somehow flash the stock ROM again.
Does anyone know how to solve this issue?
BTW I am not on Verizon.
I've run into a few of these situations. I also tried this version of Android as a Custom Rom and got a Boot Loop
I had to use TWRP to reinstall my TWRP backup.
Just in case you don't have TWRP or TWRP access for some strange reason you could try this:
I have a moto g8 plus xt2019-2
Motorola_Moto_G8_Plus_XT2019-2_DOHA_RETBR_9.0_PPI29.65-43_(MobileGuru4.com)
Motorola Flash File For All Model (Stock ROM) - Mobile Guru4
Download Motorola Flash File for all Motorola models. Here all Stock ROM and firmware files given for Motorola phones are official original files
www.mobileguru4.com
Search for this on google, when you find it download it. Then inside the zip file once you unzip it find the directory that is labeled - firmware
Inside that directory there's a file labeled "flashfile.bat" This setup uses ADB with ADB Fastboot on the phone. I assume you know how to get ADB Fastboot on your phone. When you execute the above file you will see it working in the command prompt on your computer. Let it run. It will not show anything on your phone until your phone reboots. This is what I use as a DISASTER BACKUP in case TWRP is unusable or in any way I'm unable to get to it.
I hope this helps you, it worked on my phone.
Thanks for the reply. Unfortunately, I can't try it because I've already sent the phone away to be repaired. The repair company said they would have to send it away when I originally emailed them. The repair company had a no fix no fee arrangement, so if they can't do it I'll try using fastboot. Hopefully that will happen and I won't have to pay $200.
sorry my english, i have the same problem and already try everything, rsa always fails and rsd lite does not recognize my device in windows 10, i tried to short the motherboard and it didn't work, i am seriously thinking about changing the motherboard or sell the parts
So I have 10 years of experience of rooting phones and flashing roms etc and I think this is the first time I really bricked my phone and until now did not find i solution my self.
So how got it bricked: I was on my work, in a bit of a hurry and wanted to update my phone (dirty flash) through TWRP but the installation hanged at the last 1% or such. I let it sit for 30 min. still hangs so decided to abort and do a clean flash but again the update hangs (maybe bad download?) but along the way (probably because I was at work and didn't take the time) I think I ****ed up switching partitions or something and now I have no OS installed on my.
I can boot in to Fastboot mode, TWRP EDL mode and such
But I can't flash an new OS through TWRP because it says the following: Unable to find Partition for path '/system_root' (will post screenshot when I get home from work )
I tried MSM tool but until now I could not get the tool to see my Phone so now I am calling for the help of the XDA Community!
So do you guys have any suggestions wich wil unbrick my phone?
Try running msm from different port on your pc. Preferably a 2.0 usb if you have. Many times makes a difference. Also make sure your adb drivers are updated to latest. Many threads around talk about it.
Extracted boot file from original oneplus rom, flashed that with fastboot and like magic my problem was solved