Hi All !
Given a TOT file, can we edit it (lets say with any hex editor) to change its Anti Roll-Back i.e. ARB value from, say, 00 to 02 or 03?
rizkhan999 said:
Hi All !
Given a TOT file, can we edit it (lets say with any hex editor) to change its Anti Roll-Back i.e. ARB value from, say, 00 to 02 or 03?
Click to expand...
Click to collapse
100% no this is not possible. Change a single bit the signatures get invalid which will brick your device.
Sent from my LG-H815 using XDA Labs
What about hex-editing .IMG files?
steadfasterX said:
100% no this is not possible. Change a single bit the signatures get invalid which will brick your device.
Click to expand...
Click to collapse
Thanks sir. And what about editing ARB version or anything else in the rooted system image .IMG file? Will the signature hurdle be encountered here as well, or not?
rizkhan999 said:
Thanks sir. And what about editing ARB version or anything else in the rooted system image .IMG file? Will the signature hurdle be encountered here as well, or not?
Click to expand...
Click to collapse
Check my post here: http://tinyurl.com/antirollg4
If you go through the details at the beginning and follow the links you may understand better.
In short: the ARB is implemented in the bootloader and to be more clear in the certificates within. There is 100% no chance to change this other then when you break the signature algo or find a bug in the implementation.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Check my post here: http://tinyurl.com/antirollg4
If you go through the details at the beginning and follow the links you may understand better.
In short: the ARB is implemented in the bootloader and to be more clear in the certificates within. There is 100% no chance to change this other then when you break the signature algo or find a bug in the implementation.
Click to expand...
Click to collapse
Okay sir. But really sorry to take from your precious time, actually what I am trying to do is to change (via hex editor) the echo value of 1 to 0 wherever the following instances occur in the rooted system image .IMG files:
/sys/devices/system/cpu/cpu5/online
/sys/devices/system/cpu/cpu6/online
/sys/devices/system/cpu/cpu7/online
This is in the spirit to disable two big cores.
But I have the following questions regarding this:
1. Would the IMG file still be valid and correctly flashable after changing the above mentioned values from 1 to 0?
2. Would the changes be effective only after the phone has booted into the OS or... from the powering-on of the phone and onwards?
3. What is "cpu7" in IMG files, while G4 is only hex-core (i.e. cpu1 to cpu6)?
rizkhan999 said:
Okay sir. But really sorry to take from your precious time, actually what I am trying to do is to change (via hex editor) the echo value of 1 to 0 wherever the following instances occur in the rooted system image .IMG files:
/sys/devices/system/cpu/cpu5/online
/sys/devices/system/cpu/cpu6/online
/sys/devices/system/cpu/cpu7/online
This is in the spirit to disable two big cores.
But I have the following questions regarding this:
1. Would the IMG file still be valid and correctly flashable after changing the above mentioned values from 1 to 0?
2. Would the changes be effective only after the phone has booted into the OS or... from the powering-on of the phone and onwards?
3. What is "cpu7" in IMG files, while G4 is only hex-core (i.e. cpu1 to cpu6)?
Click to expand...
Click to collapse
sys files are created and changed on boot you can't change them in the system image even if they would be there. Those are created and changed in the ram disk which is part of the boot image.
You can't change the boot image as this makes the signature invalid .
You can change the system image especially on LL when rooted. Here you can implement the disabling of the cores e.g. implemented as an init script.. but it will have an effect after booted only.
The boot process will still use all cpu cores.
You have no cpu7 on a g4. The reason is that it starts from 0 to count. Cpu0 to cpu3 are the first 4 cpus.
there is success reported with many devices to install the unofficial official v29 beta for nougat. This beta contains at least for the boot the disabling of the big cores but I don't know if your device model is supported by it or not but check this maybe.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
sys files are created and changed on boot you can't change them in the system image even if they would be there. Those are created and changed in the ram disk which is part of the boot image.
You can't change the boot image as this makes the signature invalid .
You can change the system image especially on LL when rooted. Here you can implement the disabling of the cores e.g. implemented as an init script.. but it will have an effect after booted only.
The boot process will still use all cpu cores.
You have no cpu7 on a g4. The reason is that it starts from 0 to count. Cpu0 to cpu3 are the first 4 cpus.
there is success reported with many devices to install the unofficial official v29 beta for nougat. This beta contains at least for the boot the disabling of the big cores but I don't know if your device model is supported by it or not but check this maybe.
Click to expand...
Click to collapse
By LL i guess you mean LP (lollipop).
In rooted system image IMG files as well as in the TOT files, there is a mention of seven cpu's from cpu1 through cpu7. And this cpu7 is always mentioned along with cpu5 and cpu6 under the comment of A57 cores. While the rest four are A53 cores. So i wonder what this cpu7 really denotes on a hexcore processor!
I also have h815 (international variant) and using Nougat A29a rom from here. And i have flashed titan kernel with no big cores over it, from the same developer. I recovered this phone from bootloop by initially flashing the 4mb ILAPO FIX TOT file with LGUP. But the traditional TWRP from twrp official website is working fine for me. I didnt have to use custom TWRP that doesnt use two big cores.
Anyways. Thanks alot for all your time and support.
rizkhan999 said:
By LL i guess you mean LP (lollipop).
In rooted system image IMG files as well as in the TOT files, there is a mention of seven cpu's from cpu1 through cpu7. And this cpu7 is always mentioned along with cpu5 and cpu6 under the comment of A57 cores. While the rest four are A53 cores. So i wonder what this cpu7 really denotes on a hexcore processor!
I also have h815 (international variant) and using Nougat A29a rom from here. And i have flashed titan kernel with no big cores over it, from the same developer. I recovered this phone from bootloop by initially flashing the 4mb ILAPO FIX TOT file with LGUP. But the traditional TWRP from twrp official website is working fine for me. I didnt have to use custom TWRP that doesnt use two big cores.
Anyways. Thanks alot for all your time and support.
Click to expand...
Click to collapse
There is no cpu7.. Even no cpu6. The thing is you have to differ between what happens on os site and what on app site.
Some apps like kernel Adiutor starts to count from 1 instead but in the background it's still from 0..5
SoC: Qualcomm Snapdragon 808 MSM8992
CPU: 2x 1.8 GHz ARM Cortex-A57, 4x 1.44 GHz ARM Cortex-A53, Cores: 6
0-3 are a53
4-5 are a57
Sent from my LG-H815 using XDA Labs
steadfasterX said:
There is no cpu7.. Even no cpu6. The thing is you have to differ between what happens on os site and what on app site.
Some apps like kernel Adiutor starts to count from 1 instead but in the background it's still from 0..5
SoC: Qualcomm Snapdragon 808 MSM8992
CPU: 2x 1.8 GHz ARM Cortex-A57, 4x 1.44 GHz ARM Cortex-A53, Cores: 6
0-3 are a53
4-5 are a57
Click to expand...
Click to collapse
Actually the file /etc/dir/init.qcom.post_boot.sh does contain mentions of only six cores from cpu0 through cpu5. However all the IMG and TOT files contain mentions of seven cores from cpu1 through cpu7.
The first screenshot shows one of such mention of all seven cores, as highlighted in it. The second screenshot shows the mention of cpu5, cpu6 and cpu7 under A57 cores which shows that cpu7 is also treated as a big core. That's why I was asking what this seventh core mean in a hex-core device?
rizkhan999 said:
Actually the file /etc/dir/init.qcom.post_boot.sh does contain mentions of only six cores from cpu0 through cpu5. However all the IMG and TOT files contain mentions of seven cores from cpu1 through cpu7.
The first screenshot shows one of such mention of all seven cores, as highlighted in it. The second screenshot shows the mention of cpu5, cpu6 and cpu7 under A57 cores which shows that cpu7 is also treated as a big core. That's why I was asking what this seventh core mean in a hex-core device?
Click to expand...
Click to collapse
Its there but it's useless.
Mount the system image instead of using a hexeditor then grep on the files like this
grep -r cpu7 /path/
I can't verify this atm as I'm on vacation but I strongly believe this is just a leftover from another device made by LG. Keep in mind that developers are lazy and so they copy things which is ok but this also means they may copy too much without verifying . Actually this doesn't harm anything in this case (if cpu6 or 7 are not there an error is thrown and maybe shown in dmesg but that's all) so they may just don't care.
.
steadfasterX said:
100% no this is not possible. Change a single bit the signatures get invalid which will brick your device.
Click to expand...
Click to collapse
I tried flashing my H815 with H810 10o TOT file using LGUP. It gave out the invalid file error as expected. Then I modified the mentioned H810 10o TOT file by replacing all occurances of H810 with H815 and flashed it on H815 using LGUP. The phone got bricked, as also expected and became dead. No display, no download mode.
Then when I long pressed the power and vol down buttons together the phone got detected as QFUSE in Device Manager but it happened only once.
Now when I long press power and vol down buttons, the phone always vibrates but remains undetected.
I have tried this memory card unbrick method as well as tried installing qualcomm drivers after uninstalling all phones drivers using this guide but same status.
Any other unbrick guide that may work?
rizkhan999 said:
I tried flashing my H815 with H810 10o TOT file using LGUP. It gave out the invalid file error as expected. Then I modified the mentioned H810 10o TOT file by replacing all occurances of H810 with H815 and flashed it on H815 using LGUP. The phone got bricked, as also expected and became dead. No display, no download mode.
Then when I long pressed the power and vol down buttons together the phone got detected as QFUSE in Device Manager but it happened only once.
Now when I long press power and vol down buttons, the phone always vibrates but remains undetected.
I have tried this memory card unbrick method as well as tried installing qualcomm drivers after uninstalling all phones drivers using this guide but same status.
Any other unbrick guide that may work?
Click to expand...
Click to collapse
ok you hard bricked (hard not hard-hard which means you can recover).
you can recover from that hard brick by using QFIL and the RIGHT files (beware of the dragons!)
download & install QPST: https://www.androidfilehost.com/?fid=673368273298970431
download & install QPST drivers: https://www.androidfilehost.com/?fid=673368273298970430
download & extract H815 QFIL recover files: https://www.androidfilehost.com/?fid=745425885120762427
Start QFIL.exe within the Qualcomm QPST installation folder
Select Build Type: > Flat <
Browse to > prog_emmc_firehose_8992_lite.mbn <
Click Load XML button and select: > rawprogram0.xml <
then: > patch0.xml <
Take a deep breath......
Click > Download <
Wait until it finishes. Unplug USB, remove battery, put battery back and go into download mode for a full recovery by flashing a h815 KDZ
sfX
steadfasterX said:
ok you hard bricked (hard not hard-hard which means you can recover).
you can recover from that hard brick by using QFIL and the RIGHT files (beware of the dragons!)
download & install QPST: https://www.androidfilehost.com/?fid=673368273298970431
download & install QPST drivers: https://www.androidfilehost.com/?fid=673368273298970430
download & extract H815 QFIL recover files: https://www.androidfilehost.com/?fid=745425885120762427
Start QFIL.exe within the Qualcomm QPST installation folder
Select Build Type: > Flat <
Browse to > prog_emmc_firehose_8992_lite.mbn <
Click Load XML button and select: > rawprogram0.xml <
then: > patch0.xml <
Take a deep breath......
Click > Download <
Wait until it finishes. Unplug USB, remove battery, put battery back and go into download mode for a full recovery by flashing a h815 KDZ
sfX
Click to expand...
Click to collapse
Awesome. There is some progress. The screenshot shows that my phone is properly connected in QDloader 9008 mode but the QFIL during the flash process gives the error that the phone is not in the FireHose mode. Any ideas?
rizkhan999 said:
Awesome. There is some progress. The screenshot shows that my phone is properly connected in QDloader 9008 mode but the QFIL during the flash process gives the error that the phone is not in the FireHose mode. Any ideas?
Click to expand...
Click to collapse
well.. yea the 9008 mode is a PITA. The thing is 9008 is not 9008.. plus that mode is very sensitive: means u need to know some things:
timing: when you wait too long (lets say.. 5 min or longer) the 9008 mode will stop working. The device gets still detected but QFIL will not work.
so best is: prepare QFIL so you just need to click the Download button and before actually doing so pull out battery , unplug USB and plugin again. once detected in QFIL press download.
Usually u have at least 1 min or even more after the device brings up the 9008 mode so no need to hurry that much but if you wait too long it will fail.
second: when you used QFIL once you HAVE to reboot bc otherwise the firehose programmer will not fit into memory anymore and so it will fail as well.
always start the 9008 mode fresh for every try.
third: best is to pull out the battery and just plugin the USB cable. If you device is detected this way in QFIL: perfect! do it like this as this can be different from the result when the battery is in and its recommended to have not the battery in for the 9008 mode actions
fourth: last but not least: the only 100% way to bring up a 100% valid 9008 mode is by either erasing a partition (u cant do that atm) or by shorten 2 PINs on the mainboard.
this will be the last option when all the above wont help you out.
(All the above is the result of a looooong try & error process I've done during my unlocking attempts)
sfX
steadfasterX said:
well.. yea the 9008 mode is a PITA. The thing is 9008 is not 9008.. plus that mode is very sensitive: means u need to know some things: sfX
Click to expand...
Click to collapse
Thanks alot for your detailed reply. My phone has stopped getting detected by computer, as it happened a few days ago as well. And no vibrations either. So I have left it with battery removed. Will try it again after a few days. May be it starts getting detected again.
steadfasterX said:
download & extract H815 QFIL recover files: https://www.androidfilehost.com/?fid=745425885120762427
Click to expand...
Click to collapse
Btw do you also have qfil recover files of h810 and h811 variants? Can u plz upload them too? Thanx in advance.
No success still...
steadfasterX said:
well.. yea the 9008 mode is a PITA. The thing is 9008 is not 9008.. plus that mode is very sensitive: means u need to know some things:
Click to expand...
Click to collapse
Sine the phone was undetected for days, I kept it in the freezer for the night. And it has started getting detected in 9008 mode again . But I have tried it flashing while keeping the mind all the instructions, like connecting it without the battery and with battery as well, and keeping the QFIL ready and pressing the Download button as soon as the device gets detected, but I have received the same error that the phone is not in the firehose mode.
The QFIL version you shared was 2.7 with build 425. I have also tried build 437 as well and got the following error (log attached herewith):
ERROR: OpenPort:4197 It took 160.07800000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
I also tried the build 422 which gave out the same error of phone not being in the firehose mode eventhough I disconnected and connected it afresh. I think the phone is either not in the pure 9008 mode (as you also said) or that it enters the mode for a very short period of time so that the QFIL flashing fails.
Any solutions now?
rizkhan999 said:
Sine the phone was undetected for days, I kept it in the freezer for the night. And it has started getting detected in 9008 mode again . But I have tried it flashing while keeping the mind all the instructions, like connecting it without the battery and with battery as well, and keeping the QFIL ready and pressing the Download button as soon as the device gets detected, but I have received the same error that the phone is not in the firehose mode.
The QFIL version you shared was 2.7 with build 425. I have also tried build 437 as well and got the following error (log attached herewith):
ERROR: OpenPort:4197 It took 160.07800000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
I also tried the build 422 which gave out the same error of phone not being in the firehose mode eventhough I disconnected and connected it afresh. I think the phone is either not in the pure 9008 mode (as you also said) or that it enters the mode for a very short period of time so that the QFIL flashing fails.
Any solutions now?
Click to expand...
Click to collapse
Then your device may is in the R.I.P. 9008 mode. Devices who have the mainboard issue goes through several steps. The last one is being detected as 9008 only without any chance to use qfil anymore.
Only fix known is written in my bootloop fix it list (see signature) and means replacing the mainboard or for the advanced ones doing some soldering.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Then your device may is in the R.I.P. 9008 mode. Devices who have the mainboard issue goes through several steps. The last one is being detected as 9008 only without any chance to use qfil anymore.
Click to expand...
Click to collapse
Yeah thats possible. Because the phone is getting detected in 9008 only with the battery now. While without the battery it either gives the blank battery with ? indication, while sometimes the blue screen as well (similar to G3's Blue Screen of Death).
Only fix known is written in my bootloop fix it list (see signature) and means replacing the mainboard or for the advanced ones doing some soldering.
Click to expand...
Click to collapse
Do you have any link to any of such kind of soldering tutorial? I can have it done from any hardware guy in the market.
rizkhan999 said:
Yeah thats possible. Because the phone is getting detected in 9008 only with the battery now. While without the battery it either gives the blank battery with ? indication, while sometimes the blue screen as well (similar to G3's Blue Screen of Death).
Do you have any link to any of such kind of soldering tutorial? I can have it done from any hardware guy in the market.
Click to expand...
Click to collapse
I have updated my bootloop fix it list. Scroll down to the Advanced disassemble method(s)
Sent from my LG-H815 using XDA Labs
Related
Hello
This is the process that I used to unbrick the LG G Pad 8.3 tablet.
Note 1: The operating system on my PC is Windows XP SP3 x86
Note 2: The same process should also work on LG G Pad 10.1 (With a different .tot file)
1. First of all you should make sure that the G Pad is detected when connected to the PC.
The device should be seen as QHSUSB_DLOAD in Other Devices section in Device Manager.
hxxp://i.imgur.com/IawJZq0.jpg
2. Install the QHSUSB Driver for your operating system.
The driver can be found here:
hxxp://mega.nz/#!HlpViaTJ!NPACjSQtTjGWdYIj3kHO3bGfmAotaSSQindmgRY9VJ4
I have used the driver from the "checked" folder.
Reconnect the tablet and you should now see the device as Qualcomm HS-USB QDLoader 9008 (COMxx) under the Ports section in Device Manager.
Take a note of the COM port number.
hxxp://i.imgur.com/IR7uUCB.png
3. Download the .tot image file for you tablet model.
I have used the one from here (LG G Pad 8.3 V500 4.4.2):
hxxp://androidfilehost.com/?fid=23329332407581518
4. Now you need the LG BoardDiag tool.
Download this one from here:
hxxp://mega.nz/#!XwgkXTAR!JnAAXKBQoezT7CcxRSVkSQlPFr4AXcvfm6oJbw4bht4
Please use only this one even if you have another BoardDiag. I have tried other versions and this was the only one that worked. For the other versions I always got some error:
failed during loading flash programmer
or
device not found in dload trying flash programmer
With this tool we will extract the .tot rom image first.
Unrar the archive and open BoardDiag3.99c application.
Click on the ... button next to BIN from the Image Extraction section on the bottom of the BoardDiag application and browse to the .tot file you downloaded at step 3.
Then click on the ... button next to DIR and browse to a folder to extract the files in.
Click on the Extract button and wait for the files to be extracted.
After the extraction is complete, close the BoardDiag application.
hxxp://i.imgur.com/Kw0ZhUv.jpg
5. Now we will perform some cheks on the tablet.
Open the BoardDiag application again.
Now select the AP check and EMMC TEST checkboxes from the Board Diag Test section on the top-left.
Also choose the G-pro (APQ8064) on the AP Chipset dropdown selection box. Choose the Com Port that you took a note of at step 2. Select as the Target Dir the folder where you extracted the .tot image file at step 4. These settings are in the top-right side of the BoardDiag application. Make no other changes to the settings.
Now Click on the big START button and wait for the checks to be made.
If everything is OK you should see under the Test Results section the green text PASS both under the AP and EMMC. Leave the BoardDiag application open. Now you can proceed to step 6.
6. Now we will Flash the files to the tablet.
Now you will also check the SDRAM TEST checkbox on the left top side of the BoardDiag application. The other settings were already made in step 5. Click the START button again.
After performing the checks you should see that the files from the image (aboot.mbn, boot.mbn, etc.) are written to the tablet.
After that, the BoardDiag tried to reset the tablet, but it failed and it ended with FAIL for SDRAM under the Test Results section. But the files were already written on the tablet.
7. After that I disconnected and reconnected the tablet to the PC. Nothing was detected, or so I thought, because I could see that in Device Manager something was happening. It was like refreshing itself every 5 seconds or so. I disconnected the tablet from the PC and I plugged in the wall charger. It turns out that the battery had no power.
After a few minutes the LG logo appeared on the screen. Nothing else was happening but I could see the LG logo. I left the tablet to charge the battery for at LEAST 3 hours. If your tablet battery is also discharged you should plug your tablet to the charger for at LEAST 3 hours.
After that I reconnected the tablet to the PC and it was detected as G Pad but it couldn't find the driver.
8. Install the LG Mobile Drivers.
You can get them from here:
hxxp://mega.nz/#!j8xikSYC!Njz3E1_PSJanzQEeZCbbEoWfxUz9TfrTVgusqBCJ2qY
After the driver installation reconnect the tablet to the PC.
It should now be connected properly.
9. Download LG Mobile Support Tool. You can use the launcher from here:
hxxp://mega.nz/#!bp5jgBQJ!xqiMyQU7z-ATlYz__0ybz2kM7boeLFNgqsu5XoPPSzo
Open LG Mobile Support Tool. You should now see the tablet is connected correctly and you should see the tablet model on the left side of the LG Mobile Support Tool. You will now go to Options and choose Upgrade Recovery. Wait for the image to be downloaded and flashed to the tablet.
After the process is completed the tablet will boot to life again.
Please write your comments bellow if you succeeded or failed. I will provide further assistance if required.
PS: I think you need to remove the battery and reinsert it after step 6. Or it could also work if you let the battery discharge completely.
Good luck!
I could not post the images and the links.
I will add them later (after I get to 10 posts).
Contact me on skype (cyadron) for the files and for other help.
nice finding.
it can be handy if we try to flash the v510 bootloader on the v500 to see if it fits and "unlocks" the pad
ckret said:
nice finding.
it can be handy if we try to flash the v510 bootloader on the v500 to see if it fits and "unlocks" the pad
Click to expand...
Click to collapse
Actually it was the only way I found that worked to unbrick this tablet.
Bricked LG G Pad
Need your help man with those files. I bricked my device after flashing wrong file. I have tried LG G2 Pro Board Diag tool and everything passes except SDRAM.
Thanks in advance for your assistance.
Links for files
Hi, I bricked my GPad and would be very interested in getting the proper files or links. How can I get them?
I will update this thread as soon as I can post links. Hopefully no more than a few days.
cyadron said:
I will update this thread as soon as I can post links. Hopefully no more than a few days.
Click to expand...
Click to collapse
Can you post links ?
This sounds very promising @cyadron, hopefully you'll be able to edit the links in soon.
@muiriddin this sounds like you should be able to revive your tablet from your science experiment.
@fefifofum posting here instead of the other thread as that would be way off topic for it.
This sounds like we'll be able to do some proper experimenting and still be able to recover if it doesn't work!
Hopefully I will be able to post the links soon. Does anyone know the minimum number of posts required to post links?
cyadron said:
Hopefully I will be able to post the links soon. Does anyone know the minimum number of posts required to post links?
Click to expand...
Click to collapse
Just put hxxp instead of h t t p.
roirraW "edor" ehT said:
Just put hxxp instead of h t t p.
Click to expand...
Click to collapse
Thank you. That worked.
Links have been added.
cyadron said:
Thank you. That worked.
Links have been added.
Click to expand...
Click to collapse
This thread should probably be pinned. You can request the moderators to do so by "reporting" your first post and ask them there. Too bad, as far as I know, there aren't any TOTs available for the VK810, although I haven't needed one yet.
I used the tutorial, but accuses ero Emmec test fails
Any solution?
edsmat said:
I used the tutorial, but accuses ero Emmec test fails
Any solution?
Click to expand...
Click to collapse
Unless there is a hardware problem with the emmc, it should work.
Try and remove the battery and put it back again.
Please also make sure you follow the steps as described.
Cluey said:
This sounds very promising @cyadron, hopefully you'll be able to edit the links in soon.
@muiriddin this sounds like you should be able to revive your tablet from your science experiment.
@fefifofum posting here instead of the other thread as that would be way off topic for it.
This sounds like we'll be able to do some proper experimenting and still be able to recover if it doesn't work!
Click to expand...
Click to collapse
It would be nice to get my science experiment working again... I hopefully will have some time to follow this process this weekend...
hi, i have hardbrack v410 no have screen at all only qualcomm hs_usb 9008 please help me (
lgv410 said:
hi, i have hardbrack v410 no have screen at all only qualcomm hs_usb 9008 please help me (
Click to expand...
Click to collapse
Read everything you can and follow instructions.
I think you'll need to search further than just this thread though. I read about someone recovering an LG device from this state but I think it was a phone.
But you'll need to find it and follow the instructions, I don't remember where I read it.
Cluey said:
Read everything you can and follow instructions.
I think you'll need to search further than just this thread though. I read about someone recovering an LG device from this state but I think it was a phone.
But you'll need to find it and follow the instructions, I don't remember where I read it.
Click to expand...
Click to collapse
thank you for you answer, can you show me where i can found this instructions to fix this problem? :/
lgv410 said:
thank you for you answer, can you show me where i can found this instructions to fix this problem? :/
Click to expand...
Click to collapse
No, I'm not here to do searches for you.
This is my first modern Windows Mobile (I used Windows Mobile 11 years a go) and it seems Microsoft was crippled the operating system.
Model: Bush Eluma, Windows 10 native (rebranded Archos 50 Cesium)
Specification:
Snapdragon 210
Adreno 304
1 GB RAM
16GB ROM
MicroSD support up to 128GB
5" 720x1280 IPS screen
4G LTE
WIFI/Bluetooth/GPS
8MP rear/2MP front with flash
2100mAh battery
Spec. Sheet: archos [dot] com/corporate/press/press_releases/EN_ARCHOS_50Cesium_50eHelium.pdf
What I'm trying to do: Interop-unlock
What I've managed to do: Deploy apps, such as Root Tool and vcREG
Where I'm stuck: Setting the value for my model of phone - I have no idea where to look
I hope I've provided information in a clear format. I'd very much appreciate some help or feedback in order to interop-unlock this model
System\Platform\DeviceTargetingInfo
PhoneManufacturer
Value = "True" (I think this used to just say "ARCHOS")
Thank you for reading.
Was there any progress made with this? Looking to interop unlock phone too so any help would be great
you tried this?
https://forum.xda-developers.com/windows-10-mobile/acer-liquid-jade-primo-upgrade-to-au-cu-t3589156
Worked a treat! Thanks a lot.
user154 said:
Sorry to kinda hijack this thread, but I have this device and struggling to find any other owners. My understanding is that the archos 50 cesium is the windows version of the 50e helium. I have an emmc dump of the 50e helium, if you cant already tell where im going with this, I want to flash this dump to my eluma b2 but cant get qfil or thor2 to do this. Can anyone help? or even know if this is possible?
Click to expand...
Click to collapse
I say just enjoy the W10 phone while you can, or if you really want Android, go buy that model online some where.
It is not as simple as it sounds. You would need at least a flash programmer for the SoC in that phone which usually the manufacturers never release. Depending on the format of the dump you might need other flashers or files to understand how the Archos 50 eMMC is structured or to utilize them in the flashing process. You would also want to be able to put the phone into EDL mode. If you can manage to even boot the flash programmer and initialize a flash of the phone there is also high risk of bricking it. Because you would be flashing partitions that were not signed for that phone/SoC. So I am not sure if you would also need to unlock the boot loader on it or not...sounds like you would. IMO it would be best to unlock the bootloader so you can backup the current layout of the phone. This as far as I know is not possible, so I would just stop there.
I know there are some threads in other forums where they are trying to do this with the IDOL 4s, and maybe a couple devices in the past have worked out to be able to do this. However it pretty much hinges on unlocking the boot loader. Also from what I know once you flash it like that and even if device survives (it boots, the IMEI is in tact, etc.) you cannot revert it back or it is pretty much impossible to go back without bricking it.
user154 said:
It doesnt really matter if the device is rendered unusable, it is quite a long way down the list of backup devices I have, it was more for the fun of trying to do it. The device is the exact same as its android counterpart (hardware wise) this is what made me think it should theoretically be possible. The dump I have was made with infinitybox, I have managed to create the required rawprogram.xml and patch.xml from the gpt binary contained within the dump. I have also found a couple of flash programmers for the soc (prog_emmc_firehose_8909.mbn, and a couple of manufacturer specific ones, pretty sure iv got the filename slightly wrong there). I have been able to boot the device to EDL mode using a cable, however sahara fails to load the flash programmer to the device. I didnt think the bootloader would need to be unlocked to flash the device seeing as the device is in EDL mode and what Im trying to flash is signed as is just the dump from the android counterpart. Maybe this is where im going wrong. Also Im working on the assumption the IMEI will be wiped as I plan to flash persist.img from dump too, I thought trying to keep the partition where it is stored in windows 10 and repartition the rest of the emmc to the same as the android counterpart might make things more complicated than they already are. Also IMEI can sometimes be quite simple to repair on certain devices (A lot more simple than what Im trying to acheieve here anyway). Can you point me in the right direction as to where I can find instructions to unlock the bootloader of this device? for some reason it doesnt get recognised by wpinternals (In any mode, EDL, standard flash mode, no idea what thats called on windows haha, or booted normally)
Click to expand...
Click to collapse
Sounds like you're on the right path. I'm not 100% sure you need to unlock the boot loader, however it would definitely make things easier as you could dump partitions from the phone as it is and even possibly enable mass storage mode. I am unsure where you would look to unlock that phones boot loader other than here. The flash programmers you have may not be built for the Windows Phone eMMC and why they are not booting.
Hi, this is quite interesting for me as I am struggling with 2 Cesium 40 devices stuck in Qualcomm download mode. I thought I managed to extract msimage.mbn and hex binary file from ffu, converted the hex file to hex.hex and added first and last-but-one lines. Although there was no way to escape from Qualcomm mode. Thor recognizes the Qualcomm deveices, but tells me to stop QFIL operations, even if there is no QFIL. Any ideas?
JoachimP said:
Hi, this is quite interesting for me as I am struggling with 2 Cesium 40 devices stuck in Qualcomm download mode. I thought I managed to extract msimage.mbn and hex binary file from ffu, converted the hex file to hex.hex and added first and last-but-one lines. Although there was no way to escape from Qualcomm mode. Thor recognizes the Qualcomm deveices, but tells me to stop QFIL operations, even if there is no QFIL. Any ideas?
Click to expand...
Click to collapse
If you have qpst/qfil installed on your PC, and have used them recently. The services might still be running. Just hunt for them in task manager and kill them and run thor2 again. See if that helps.
Worked a treat! Much obliged.
@nate0
Hi, thanks for your reply. I am nearly sure, I uninstalled QFIL and shutdown my pc after use, but I will check on it.
So I uninstalled QFIL and rebooted. This is the result:
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode list_connections
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode list_connections
Process started Wed Nov 14 08:48:16 2018
Logging to file C:\Users\me\AppData\Local\Temp\thor2_win_20181114084816_ThreadId-4796.log
Debugging enabled for listconnections
WinUSB in use.
Connection list START
0.1A07:0004:0004 {71de994d-8b7c-43db-a27e-2ae7cd579a0c} Emergency mode connected
Connection list END
Exited with success
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode emergency -hexfile cesium\hex.hex -mbnfile cesium\prog_emmc_firehose_8x10.mbn -ffufile cesium\flash_retail.ffu
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode emergency -hexfile cesium\hex.hex -mbnfile cesium\prog_emmc_firehose_8x10.mbn -ffufile cesium\flash_retail.ffu
Process started Wed Nov 14 08:48:52 2018
Logging to file C:\Users\me\AppData\Local\Temp\thor2_win_20181114084852_ThreadId-7500.log
Debugging enabled for emergency
Initiating emergency download
Using default emergency protocol
ALPHA EMERGENCY FLASH START
Emergency Programmer V1 version 2014.10.31.001
Hex download selected
Check if device in Dload
Message send failed with error code -1
Waiting connection to DLOAD: 2 of 2
Check if device in Dload
Message send failed with error code -1
Failed to connect to DLOAD mode
Make sure that the COM port is free. Close QPST.
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 8.00 seconds.
THOR2_EMERGENCYFLASHV1_ERROR_PROGRAMMER_SEND_FAILED
THOR2 1.8.2.18 exited with error code 85030 (0x14C26)
Any suggestions?
It has taken me many days to find a tool to flash KDZ AND TOT since many people show an error at 4% of FlashTool and there is no solution so this is your Post.
LGUP is a tool used by Lg for phones that still have a guarantee such as a system error or a software error.
Compatible with Windows vista/7/8/10 No macOS No Linux
Thanks to DroidTH for giving me a link
ok let's start
Renember: All will be erased in the internal memory.
Your warrantly is now avoid
Visit [How-to] Flash firmware KDZ G2 G3 G4 by LGUP On Youtube to the link
Remember that it is not channel advertising, it's just that I can not add external links
Steps to follow
Make sure you have the drivers installed correctly
Download The KDZ / TOT
Connect Lg g3 to pc (No need to enter download mode manually)
Unzip (LGUP-G2-G3.ZIP)
First install (LGUP_8974_DLL_Ver_0_5_CODEFIRE)
Second Install (LGUP_Install_Ver_1_14_3)
Enter the LGUP program that is probably hosted on your desktop
Select the Upgrade box and select the KDZ / TOT file
Wait for the process to finish (Do not disconnect the phone)
At 80% the phone will restart (not yet to be disconnected)
When you reach 100% the phone must have turned on or starting on the TMO logo
If it does not start
-------------------------------------------------- -------------------------------------------------- ----
If it does not start
---------------------------------------------- -------------------------------------------------- -----
If it restarts constantly and does not enter the system (It restarts before reaching the optimizing application)
Turn off the phone completely and remove the battery
Wait 10 seconds. And put it back
Press Vol- and on when logo is released and press them again.
Give you everything
EYE: all files on the internal SD card will be erased
A factory reset will be made and then it must be turned on normally.
If it still does not start, remove the chip (SIMCARD)
Well that's all if you have any questions please write
Sorry if I needed something, it's just that I'm new and I do not know anything about xda
I hope you understand.
When I run LGUP it says Model is Unknown, then gives an error telling me I have to choose a known Model. Drivers are installed, USB debugging is enabled, not sure what else there is missing. Please help.
my phone: (T-Mobile lg g3 d851 30e)
dricialg said:
error Unknown model.!!
my phone: (g3 d851 30e)
Click to expand...
Click to collapse
sorry you had problems
the error is one of the drivers lg
you should plug it into one of the main USB ports on your PC.
or rather entering device manager and re-assign drivers to ports.
Have you downloaded the lgup for lg g3 and g2?
Drivers are installed, USB debugging is enabled, LG PC Suite OK.not sure what else there is missing.
Download : lgup-g2-g3.zip
Solve it FIX
good after I found the problem LGUP
roms apparently change the model of the device as it changes cm11 to build Cyanogenmod 11 xx
AOSP - to AOSP rom 2 etc.
the solution would be to install a stock rom clean no matter if v10 v30 etc. The important thing is not having changed the model number and manufacturer.
I hope I have helped and sorry
that includes cloudy fa's roms
minicm94123 said:
It has taken me many days to find a tool to flash KDZ AND TOT since many people show an error at 4% of FlashTool and there is no solution so this is your Post.
LGUP is a tool used by Lg for phones that still have a guarantee such as a system error or a software error.
Compatible with Windows vista/7/8/10 No macOS No Linux
Thanks to DroidTH for giving me a link
ok let's start
Renember: All will be erased in the internal memory.
Your warrantly is now avoid
Visit [How-to] Flash firmware KDZ G2 G3 G4 by LGUP On Youtube to the link
Remember that it is not channel advertising, it's just that I can not add external links
Steps to follow
Make sure you have the drivers installed correctly
Download The KDZ / TOT
Connect Lg g3 to pc (No need to enter download mode manually)
Unzip (LGUP-G2-G3.ZIP)
First install (LGUP_8974_DLL_Ver_0_5_CODEFIRE)
Second Install (LGUP_Install_Ver_1_14_3)
Enter the LGUP program that is probably hosted on your desktop
Select the Upgrade box and select the KDZ / TOT file
Wait for the process to finish (Do not disconnect the phone)
At 80% the phone will restart (not yet to be disconnected)
When you reach 100% the phone must have turned on or starting on the TMO logo
If it does not start
-------------------------------------------------- -------------------------------------------------- ----
If it does not start
---------------------------------------------- -------------------------------------------------- -----
If it restarts constantly and does not enter the system (It restarts before reaching the optimizing application)
Turn off the phone completely and remove the battery
Wait 10 seconds. And put it back
Press Vol- and on when logo is released and press them again.
Give you everything
EYE: all files on the internal SD card will be erased
A factory reset will be made and then it must be turned on normally.
If it still does not start, remove the chip (SIMCARD)
Well that's all if you have any questions please write
Sorry if I needed something, it's just that I'm new and I do not know anything about xda
I hope you understand.
Click to expand...
Click to collapse
Where are downloads
minicm94123 said:
good after I found the problem LGUP
roms apparently change the model of the device as it changes cm11 to build Cyanogenmod 11 xx
AOSP - to AOSP rom 2 etc.
the solution would be to install a stock rom clean no matter if v10 v30 etc. The important thing is not having changed the model number and manufacturer.
I hope I have helped and sorry
Click to expand...
Click to collapse
Hi !
How do I do all the above ?
My PC recognize the phone without problem, but LGUp won't start unless I "select a known model"... (LGUp window shows : Model = Unknown ; COM Ports = [COM5, CloudyG3] )
Problem is that my phone is softbricked after installing a new ROM, and I can only enter download mode (not even recovery). I just want to downgrade it and reflash a LG's stock ROM (or whatever ROM that would make my phone actually work !!! )
Can you help me do that ?
raf1978 said:
Hi !
How do I do all the above ?
My PC recognize the phone without problem, but LGUp won't start unless I "select a known model"... (LGUp window shows : Model = Unknown ; COM Ports = [COM5, CloudyG3] )
Problem is that my phone is softbricked after installing a new ROM, and I can only enter download mode (not even recovery). I just want to downgrade it and reflash a LG's stock ROM (or whatever ROM that would make my phone actually work !!! )
Can you help me do that ?
Click to expand...
Click to collapse
Do you still wanting help?
minicm94123 said:
Do you still wanting help?
Click to expand...
Click to collapse
YEEEESSSSSS !!!!
Please.... ?
(My phone is currently used as a toy by my 6 yo daughter ? )
LGUP "UNKNOWN" and FlashTool failure with LG G3 (and possibly others)
When I downloaded and installed LGUP with the DLL installer stated to be for the LG G3, the program did not recognise the phone, reporting it as "UNKNOWN". The LG FlashTool also failed, reporting the IMEI and PID as NULL. After spending a lot of time on this, I twigged that the DLL file in the LGUP model directory was for the 8994 processor; but the G3 has an 8974, quite different and incompatible. I located the DLL installer MSI file for 9874 devices, uninstalled LGUP and the DLLs from Windows add/remove programs, ran the 9874 DLL installer and reinstalled the LGUP program, and everything worked.
The file is, amongst other places, on https://uptoandroid.com/download-lg-up-tool-for-lg-smartphone-latest/. Do not download DLL files for LG G4, LG V10, LG G3, LG Stylo, filename LGUP_Common_DLL_Ver_1_0_28_5 .msi, but instead For LG phones based on Qualcomm Snapdragon 800 MSM8974 SoC, filename LGUP_8974_DLL_Ver_0_5.msi:.
HTH
23 Aug 19: I find that I've rediscovered the wheel. Exactly what I said was posted in 2016 - if I'd found it, it would have saved me a lot of time!
hi..i have hard bricked my asus zenfone 551ml 4gb/32gb.lost bootloader,recovery everything.set was just vibrating and black.then used xSTFS loader and now regained bootloader..but when i try to flash raw image via asus flash tool it shows FAILED(wrong image format).i tried several times but same.it shows my serial no 123456789ABC..now i m really puzzled what to do.as most who bricked their set were succeded by this method here..so what should i do now? i dont have any asus centre here.plz help.thanx
serial number 123456789ABC is normal if you have ever used xFSTK program to reload the entire boot chain.
I gathered from the internet that Asus Flash tool will hang after it reloads the correct serial number. It thinks it is communicating with a phone that has SN 123456789ABC but then at some point the phone switches SN and Asus Flash Tool hangs.
You can get around this hang using several methods
1) restart computer after asus flash tool hangs
2) use second computer to load RAW image after asus flash tool hangs
3) Going into Windows Device Manager and disabling the Android bootloader device then re-enabling it (after asus flash tool hangs)
You can tell Asus flash tool is hanging when you run "fastboot devices" command and you see a device that is not serial number 123456789ABC
RAW image (to my knowledge) is only for xFSTK program.
kaiser4782787890 said:
serial number 123456789ABC is normal if you have ever used xFSTK program to reload the entire boot chain.
I gathered from the internet that Asus Flash tool will hang after it reloads the correct serial number. It thinks it is communicating with a phone that has SN 123456789ABC but then at some point the phone switches SN and Asus Flash Tool hangs.
You can get around this hang using several methods
1) restart computer after asus flash tool hangs
2) use second computer to load RAW image after asus flash tool hangs
3) Going into Windows Device Manager and disabling the Android bootloader device then re-enabling it (after asus flash tool hangs)
You can tell Asus flash tool is hanging when you run "fastboot devices" command and you see a device that is not serial number 123456789ABC
RAW image (to my knowledge) is only for xFSTK program.
Click to expand...
Click to collapse
but it doesnt hang..just shows failed wrong image format
dr.estiack said:
but it doesnt hang..just shows failed wrong image format
Click to expand...
Click to collapse
problem solved...flashed via fastboot
dr.estiack said:
problem solved...flashed via fastboot
Click to expand...
Click to collapse
can you tell us what u have done to fix it??
i am facing something like you, cannot flash using AFT because after i click start on AFT, it always show "Flash image failure (FAILED (wrong image format))"
tried download raw file few time, in case corrupted, different version and different AFT version, run as administrator but still no luck still showing the same error
in fastboot mode, my serial number is looks normal but "bootloader version - unknown"...
i wonder if the phone bootloader have been unlock, so it cannot be flash using AFT.
i am facing some problem with asus zenfone 2 ZE550ML (Z008)
and decided to flash it so maybe the problem will gone...i maybe gonna create my first thread here about it, i hope i can get some help and fix it myself...
kim7tng said:
can you tell us what u have done to fix it??
i am facing something like you, cannot flash using AFT because after i click start on AFT, it always show "Flash image failure (FAILED (wrong image format))"
tried download raw file few time, in case corrupted, different version and different AFT version, run as administrator but still no luck still showing the same error
in fastboot mode, my serial number is looks normal but "bootloader version - unknown"...
i wonder if the phone bootloader have been unlock, so it cannot be flash using AFT.
i am facing some problem with asus zenfone 2 ZE550ML (Z008)
and decided to flash it so maybe the problem will gone...i maybe gonna create my first thread here about it, i hope i can get some help and fix it myself...
Click to expand...
Click to collapse
just send the commands via fastboot...follow the thread
https://forum.xda-developers.com/ze...ked-phone-updating-to-mm-tips-t3452785/page66
dr.estiack said:
just send the commands via fastboot...follow the thread
https://forum.xda-developers.com/ze...ked-phone-updating-to-mm-tips-t3452785/page66
Click to expand...
Click to collapse
you refer to the step "Flashing Firmware Without AFT", right??
because the phone which i wanna flash is not bricked yet, it still can turn ON normally. i just cannot hearing call in and out (not hardware problem since i still can hear and speak if calling using apps like Whatsapp, BBM, IMO or other chat apps). and also the IMEI of SIM 2 is unknown/Null...but the SIM 1 still can be used and the IMEI is there...tried update to latest OTA didnt solved it, so i think maybe need to be flashed using AFT.
so i did not do the steps before it...i wonder if it still OK??...
kim7tng said:
you refer to the step "Flashing Firmware Without AFT", right??
because the phone which i wanna flash is not bricked yet, it still can turn ON normally. i just cannot hearing call in and out (not hardware problem since i still can hear and speak if calling using apps like Whatsapp, BBM, IMO or other chat apps). and also the IMEI of SIM 2 is unknown/Null...but the SIM 1 still can be used and the IMEI is there...tried update to latest OTA didnt solved it, so i think maybe need to be flashed using AFT.
so i did not do the steps before it...i wonder if it still OK??...
Click to expand...
Click to collapse
it was ok for me..my set was hard bricked..even no bootloader..mine is 551ml. i spent 2days searching and found fastboot method other than aft.
This is my universal LG 90 minute method to virtually unbrick the most stubborn of bricks. This dilemma concerning the Verizon varient not getting any unbrick love has been making me ill. Let us, with the VS986_9008's, take the QDloader to the Mortal Combat ring And show it the "9008 Fatality". This takes about 90 minutes and sheds an unbelivable amount of light on a larger scale. I am starting this thread due some "lurkur guilt". I've been silently creeping around XDA since 2012. Not a single THANX button, post, comment, or even regerstering a user name. I have gathered all the things to revive this device here on XDA. So there is no need to go anywhere other than download mirrors provided by authentic XDA members. Well. First. Along over due shout out to the Devs whom I owe appreciation to, and they don't even know it yet. This is a long list. THE Greatest of THANX & PRAISES to GameTheory, PlayfulGod, Mazda, Steve Kondick, ChainFire, LaserWolf, roirrawdaor, RootJunky, Roark 13, and many more. Most importantly the main body of the Xda Developers that work painstakingly consistant on keeping these forums spam and malware free. Thank You for all the patience and for the most part, compassionate and keeping the sarcasm down to a minimal when dealing with noobs' questions at times when all any body ever wanted was a greater understanding of the Android OS. It displays a level of understanding and Professionalism that is so scarce in this technological revolution era. Never a noob joke. Very Cool. So very, very cool. I have never done this before so here goes........ One more thing be fore we start. I will not be providing download mirrors, links, or subsections of instructions on how to use these tools. I am leaving the greater portion of the learning curve to the reader. Big Tip: Search Plus is your greatest friend. Drum Roll Please.......................................................................................................................................................................You will need these 1) VS98627C_00_ARB02.kdz
2) VS98613B_00_ARB02.kdz 3) LGMobileDriver_WHQL_Ver_4.2.0.exe 4) QHUSB drivers (Qualcomm drivers) 5) QFIL (latest version) 6) WindowsLGFirmwareExtract (latest version) 7) LGUP and 8992_dll.msi (LGUP for G4) 8) LS991_ARB_02_RecoveryImage.zip (Yeah. I know it's for sprint. Just trust me.) This is done in stages so maybe a small break to stand up and stretch in between each phase is a protocol to follow. FOR SANITY. PHASE ONE: When all the needed files are chill'in on your desktop create a new file and name it "VS986 Firmware Recovery" extract the LS991 RecoveryImage to it. Now delete these laf, tz, pmic, rpm, hyp, sdi, sbl1. Using WindowsLGFirmwareExtract ; extract the VS98627C.kdz . We now take the VS98627C laf, tz, pmic, rpm, hyp, sdi, and sbl1 files and move them to our "VS986 Firmware Recovery" folder. Last but not least rename the file extensions of those from bin to mbn. But do not rename the laf.img file. Congrats. you just made a recovery image for the verizon varient of the G4. If you didn't Know how to use the kdz extraction tool. You do now. Isnt learning Android a Blast. PHASE ONE COMPLETE PHASE TWO: Like I said in the begining.. I am not giving Tuts on the use of tools or driver installs. - Iinstall the LG drivers / install the Qualcomm drivers / install LGUP and 8992_DLL.msi / Reboot PC / Go Pee PHASE THREE: Open up the back of your G4 but leave the board intact in the chassis. If you have never done this before then I suggest a youtube search to get you up to speed. With the phone open and your PC freshly booted, open up DEVICE MANAGER and force the G4 into QDLOADER 9008 mode using the test points. Again there are more than enough Threads on this topic. Open QFIL Double check the comm port number in device manager compared to comm port connection in QFIL. Make sure they are the same. IF QFIL does not recognize your connected phone than driver installation school should have held you back for that lesson. When you're all good up to this point....... Tick the "FLAT BUILD" box............. load "prog_emmc_firehose_8992_lite" found in the folder you created................. rawprogram0.xml and patch0.xml should load automatically. If they do not then load them manually. Click DOWNLOAD button. This should result in a successful flash of the laf image, except in the case where the device has the dreaded G4 hardware curse. If the logic board has no issues there should not be a problem. Upon success/pass of flash, disconnect the phone from the PC and put back together you device. PHASE 4::: This should be easy. Hold volume up. Plug into PC. Continue to hold volume rocker up untill FIRMWARE UPDATE screen displays. Use LGUP to flash the VS98627C.kdz and if you like downgrade to 13B for root and start all over. What do you mean to tell me you are not familiar with download mode? What in tar nations are you doing here? Did you try the SEARCH PLUS feature?
FILES USED IN THIS POST>https://forum.xda-developers.com/g4/general/vs986-ls991-firehoseprogrammer-raw-t3670375
Having trouble?
gratefuldeaddougie said:
This is my universal LG 90 minute method to virtually unbrick the most stubborn of bricks. This dilemma concerning the Verizon varient not getting any unbrick love has been making me ill. Let us, with the VS986_9008's, take the QDloader to the Mortal Combat ring And show it the "9008 Fatality". This takes about 90 minutes and sheds an unbelivable amount of light on a larger scale. I am starting this thread due some "lurkur guilt". I've been silently creeping around XDA since 2012. Not a single THANX button, post, comment, or even regerstering a user name. I have gathered all the things to revive this device here on XDA. So there is no need to go anywhere other than download mirrors provided by authentic XDA members. Well. First. Along over due shout out to the Devs whom I owe appreciation to, and they don't even know it yet. This is a long list. THE Greatest of THANX & PRAISES to GameTheory, PlayfulGod, Mazda, Steve Kondick, ChainFire, LaserWolf, roirrawdaor, RootJunky, Roark 13, and many more. Most importantly the main body of the Xda Developers that work painstakingly consistant on keeping these forums spam and malware free. Thank You for all the patience and for the most part, compassionate and keeping the sarcasm down to a minimal when dealing with noobs' questions at times when all any body ever wanted was a greater understanding of the Android OS. It displays a level of understanding and Professionalism that is so scarce in this technological revolution era. Never a noob joke. Very Cool. So very, very cool. I have never done this before so here goes........ One more thing be fore we start. I will not be providing download mirrors, links, or subsections of instructions on how to use these tools. I am leaving the greater portion of the learning curve to the reader. Big Tip: Search Plus is your greatest friend. Drum Roll Please.......................................................................................................................................................................You will need these 1) VS98627C_00_ARB02.kdz
2) VS98613B_00_ARB02.kdz 3) LGMobileDriver_WHQL_Ver_4.2.0.exe 4) QHUSB drivers (Qualcomm drivers) 5) QFIL (latest version) 6) WindowsLGFirmwareExtract (latest version) 7) LGUP and 8992_dll.msi (LGUP for G4) 8) LS991_ARB_02_RecoveryImage.zip (Yeah. I know it's for sprint. Just trust me.) This is done in stages so maybe a small break to stand up and stretch in between each phase is a protocol to follow. FOR SANITY. PHASE ONE: When all the needed files are chill'in on your desktop create a new file and name it "VS986 Firmware Recovery" extract the LS991 RecoveryImage to it. Now delete these laf, tz, pmic, rpm, hyp, sdi, sbl1. Using WindowsLGFirmwareExtract ; extract the VS98627C.kdz . We now take the VS98627C laf, tz, pmic, rpm, hyp, sdi, and sbl1 files and move them to our "VS986 Firmware Recovery" folder. Last but not least rename the file extensions of those from bin to mbn. But do not rename the laf.img file. Congrats. you just made a recovery image for the verizon varient of the G4. If you didn't Know how to use the kdz extraction tool. You do now. Isnt learning Android a Blast. PHASE ONE COMPLETE PHASE TWO: Like I said in the begining.. I am not giving Tuts on the use of tools or driver installs. - Iinstall the LG drivers / install the Qualcomm drivers / install LGUP and 8992_DLL.msi / Reboot PC / Go Pee PHASE THREE: Open up the back of your G4 but leave the board intact in the chassis. If you have never done this before then I suggest a youtube search to get you up to speed. With the phone open and your PC freshly booted, open up DEVICE MANAGER and force the G4 into QDLOADER 9008 mode using the test points. Again there are more than enough Threads on this topic. Open QFIL Double check the comm port number in device manager compared to comm port connection in QFIL. Make sure they are the same. IF QFIL does not recognize your connected phone than driver installation school should have held you back for that lesson. When you're all good up to this point....... Tick the "FLAT BUILD" box............. load "prog_emmc_firehose_8992_lite" found in the folder you created................. rawprogram0.xml and patch0.xml should load automatically. If they do not then load them manually. Click DOWNLOAD button. This should result in a successful flash of the laf image, except in the case where the device has the dreaded G4 hardware curse. If the logic board has no issues there should not be a problem. Upon success/pass of flash, disconnect the phone from the PC and put back together you device. PHASE 4::: This should be easy. Hold volume up. Plug into PC. Continue to hold volume rocker up untill FIRMWARE UPDATE screen displays. Use LGUP to flash the VS98627C.kdz and if you like downgrade to 13B for root and start all over. What do you mean to tell me you are not familiar with download mode? What in tar nations are you doing here? Did you try the SEARCH PLUS feature?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B41...ew?usp=sharing Extract folder / Move folder into QFIL folder as a folder not as individual files / load the firehoseprogrammer, patch, & raw / Flash / Remove battery / insert battery / hold volume up and plug in at same time until "download mode" appears on device / wait for drivers to install ? flash vs98627C.kdz with LGUP.
This will only work if the device bricked on 27C or earlier. If you know what FW version you bricked on the extract that FW and replace the appropriate files in the recovery image folder.
It appears as if some body else has stumbled upon this 4 months befor I did, back in May. Here is his Guide> http://forum.gsmdevelopers.com/showthread.php?t=28897&highlight=VS986+REPAIR
I understand the guide, but I'm confused on what you mean by "don't rename the laf.img file" because when I got the needed files from the kdz file, I got a laf.bin file but not a laf.img file. Do you mean rename the laf.bin to laf.img?
gratefuldeaddougie said:
FILES USED IN THIS POST>https://forum.xda-developers.com/g4/general/vs986-ls991-firehoseprogrammer-raw-t3670375
Click to expand...
Click to collapse
I need help with LS991ZVI
gratefuldeaddougie said:
This is my universal LG 90 minute method to virtually unbrick the most stubborn of bricks. This dilemma concerning the Verizon varient not getting any unbrick love has been making me ill. Let us, with the VS986_9008's, take the QDloader to the Mortal Combat ring And show it the "9008 Fatality". This takes about 90 minutes and sheds an unbelivable amount of light on a larger scale. I am starting this thread due some "lurkur guilt". I've been silently creeping around XDA since 2012. Not a single THANX button, post, comment, or even regerstering a user name. I have gathered all the things to revive this device here on XDA. So there is no need to go anywhere other than download mirrors provided by authentic XDA members. Well. First. Along over due shout out to the Devs whom I owe appreciation to, and they don't even know it yet. This is a long list. THE Greatest of THANX & PRAISES to GameTheory, PlayfulGod, Mazda, Steve Kondick, ChainFire, LaserWolf, roirrawdaor, RootJunky, Roark 13, and many more. Most importantly the main body of the Xda Developers that work painstakingly consistant on keeping these forums spam and malware free. Thank You for all the patience and for the most part, compassionate and keeping the sarcasm down to a minimal when dealing with noobs' questions at times when all any body ever wanted was a greater understanding of the Android OS. It displays a level of understanding and Professionalism that is so scarce in this technological revolution era. Never a noob joke. Very Cool. So very, very cool. I have never done this before so here goes........ One more thing be fore we start. I will not be providing download mirrors, links, or subsections of instructions on how to use these tools. I am leaving the greater portion of the learning curve to the reader. Big Tip: Search Plus is your greatest friend. Drum Roll Please.......................................................................................................................................................................You will need these 1) VS98627C_00_ARB02.kdz
2) VS98613B_00_ARB02.kdz 3) LGMobileDriver_WHQL_Ver_4.2.0.exe 4) QHUSB drivers (Qualcomm drivers) 5) QFIL (latest version) 6) WindowsLGFirmwareExtract (latest version) 7) LGUP and 8992_dll.msi (LGUP for G4) 8) LS991_ARB_02_RecoveryImage.zip (Yeah. I know it's for sprint. Just trust me.) This is done in stages so maybe a small break to stand up and stretch in between each phase is a protocol to follow. FOR SANITY. PHASE ONE: When all the needed files are chill'in on your desktop create a new file and name it "VS986 Firmware Recovery" extract the LS991 RecoveryImage to it. Now delete these laf, tz, pmic, rpm, hyp, sdi, sbl1. Using WindowsLGFirmwareExtract ; extract the VS98627C.kdz . We now take the VS98627C laf, tz, pmic, rpm, hyp, sdi, and sbl1 files and move them to our "VS986 Firmware Recovery" folder. Last but not least rename the file extensions of those from bin to mbn. But do not rename the laf.img file. Congrats. you just made a recovery image for the verizon varient of the G4. If you didn't Know how to use the kdz extraction tool. You do now. Isnt learning Android a Blast. PHASE ONE COMPLETE PHASE TWO: Like I said in the begining.. I am not giving Tuts on the use of tools or driver installs. - Iinstall the LG drivers / install the Qualcomm drivers / install LGUP and 8992_DLL.msi / Reboot PC / Go Pee PHASE THREE: Open up the back of your G4 but leave the board intact in the chassis. If you have never done this before then I suggest a youtube search to get you up to speed. With the phone open and your PC freshly booted, open up DEVICE MANAGER and force the G4 into QDLOADER 9008 mode using the test points. Again there are more than enough Threads on this topic. Open QFIL Double check the comm port number in device manager compared to comm port connection in QFIL. Make sure they are the same. IF QFIL does not recognize your connected phone than driver installation school should have held you back for that lesson. When you're all good up to this point....... Tick the "FLAT BUILD" box............. load "prog_emmc_firehose_8992_lite" found in the folder you created................. rawprogram0.xml and patch0.xml should load automatically. If they do not then load them manually. Click DOWNLOAD button. This should result in a successful flash of the laf image, except in the case where the device has the dreaded G4 hardware curse. If the logic board has no issues there should not be a problem. Upon success/pass of flash, disconnect the phone from the PC and put back together you device. PHASE 4::: This should be easy. Hold volume up. Plug into PC. Continue to hold volume rocker up untill FIRMWARE UPDATE screen displays. Use LGUP to flash the VS98627C.kdz and if you like downgrade to 13B for root and start all over. What do you mean to tell me you are not familiar with download mode? What in tar nations are you doing here? Did you try the SEARCH PLUS feature?
Click to expand...
Click to collapse
Hi!
I need to know if I can go back to the original fastboot mode of my lg vs986 because the flashed one is from the ls991, and that's a problem bacause when you plug the device to the pc staying in fastboot mode it won't be visible, I think is a driver problem that cause incompatibility, I've lost my imei after try with other tutorials and that's why I need to restore it, I need to entry on fastboot mode (done), I'm actually using "usu unlock" tutorial, It has unlocked fastboot mode but still being the ls991 one.
the other points are nicely explained but I AM little confused in one point in which you mentioned don't rename the files what is its mean please help me to understand that point.