Related
Hey all, Was wondering if anybody had some time to help me troubleshoot why I cannot for the life of me get this method to work and maybe explain to me a few things that are confusing to me...
Basically my phone is hard bricked:
Samsung Galaxy S3 SGH-i747 (AT&T)
- Began with Stock 4.1.2 (almost %100 positive)
- Attempted flash to 4.4.4 Task650's AOKP ROM (Flashed ok but stuck at boot animation) via CWM
- Attempted reverting back to stock with the file below via Odin but I must have missed a step...
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5
Now I am hard bricked and don't know where to go from here. I've tried several solutions:
- Homemade Jig (didn't work)
- 3 button combo / download mode (doesn't work)
- Odin does not read phone
- Connected to a pc (red power light appears but nothing else)
- SD card method - Using Win32DiskImager to write images to a 16gb class 10 micro sd
- Debrick images used: 4.1.2, 4.1.1, (should i try 4.0.4, 4.3, or even 4.4?)
- How do I tell if the image is writing correctly and partitioning the drive right?
- When the sd card is seen in the computer I see a folder on it named "image" with several files inside it but I don't know how to see partitions
I have screenshots too if you'd like to see them. Let me know if you have any suggestions or have seen anyone with this same issue able to fix it. I'd appreciate it. Thanks.
- Chris
not very knowledgeable about this stuff , but here is a thread (hardbricked 4.1.1) with link to debrick images 4.3/4.4.
http://forum.xda-developers.com/showthread.php?t=2880002
thanks to @DocHoliday77
hopefully someone will come along with some real help.
good luck.
err on the side of kindness
If that firmware was the full firmware, and it appeared to flash, you'll probably need to use the 4.3 debrick.img. also try different sd cards. Many just don't work, where others will.
Look at Tmobiles debrick thread stickied in the development section there. It tells you how to use a Linux liveCD to partition and check the card. The method will work, just use the files from here if you try it.
Chances are, if it doesn't work with the 4.3 image, you'll need a different sd card though.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
If that firmware was the full firmware, and it appeared to flash, you'll probably need to use the 4.3 debrick.img. also try different sd cards. Many just don't work, where others will.
Look at Tmobiles debrick thread stickied in the development section there. It tells you how to use a Linux liveCD to partition and check the card. The method will work, just use the files from here if you try it.
Chances are, if it doesn't work with the 4.3 image, you'll need a different sd card though.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Ok thanks. I'm going to attempt this again tonight using an SD card adapter instead of using another mobile device as the adapter to see if that makes a difference. If that doesn't do the trick I will try the LinuxLiveCD method. I'm using a Lexar 16gb Class 10 micro sd card so I don't think it that is the issue but I guess it wouldn't hurt to try a different brand.
Just curious, has anybody here successfully debricked their phone using another mobile device as the sd card adapter?
Not sure about using the mobile device, but you'd be surprised about the sd cards! I've seen Samsung 16GB Class 10 fail for some people, but work for others. It's really odd as there is no rhyme or reason to it. More of a crap shoot than anything from what I can tell.
I've seen generic 32GB class 4 cards work for people who couldn't get a name brand class 10 one to work at all.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Not sure about using the mobile device, but you'd be surprised about the sd cards! I've seen Samsung 16GB Class 10 fail for some people, but work for others. It's really odd as there is no rhyme or reason to it. More of a crap shoot than anything from what I can tell.
I've seen generic 32GB class 4 cards work for people who couldn't get a name brand class 10 one to work at all.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Good to know, but just to clarify when you say it "fails"... what exactly fails - writing the image file, partitioning the card, or does it write everything to the card ok and then just not boot up? I'm just asking so I know what to look for if it ever happens.
Thanks for the responses as I'm still new to this process and this phone and every little thing helps!
It usually appears to create the debrick sd card just fine. It just doesn't work when you try to boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
It usually appears to create the debrick sd card just fine. It just doesn't work when you try to boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
So, it appears that the issue was using the mobile device as the sd card reader. After writing the debrick file to the same sd card with an actual sd card reader, I am able to boot into the stock recovery. From here, I should just be able to flash a stock ROM to it correct or no?
Ok, which debrick.img did you end up using? If you used 4.3, you must flash the MJB firmware. If it was an older image, you will have a choice.
Either way, if you're ready to update to 4.3, and the recovery you are able to boot into is Twrp or cwm, you can flash this:
https://www.androidfilehost.com/?fid=23269279319197285
It is the full mjb base firmware. does not include recovery or system. After flashing this, you should be able to boot at least recovery and download mode without the sd card. If your rom is intact, you'll be able to boot it as well. If not, choose one and flash it.
If you are not ready to update to 4.3, we will have to find another, older version of what I linked above. Or I can make one if required.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Ok, which debrick.img did you end up using? If you used 4.3, you must flash the MJB firmware. If it was an older image, you will have a choice.
Either way, if you're ready to update to 4.3, and the recovery you are able to boot into is Twrp or cwm, you can flash this:
https://www.androidfilehost.com/?fid=23269279319197285
It is the full mjb base firmware. does not include recovery or system. After flashing this, you should be able to boot at least recovery and download mode without the sd card. If your rom is intact, you'll be able to boot it as well. If not, choose one and flash it.
If you are not ready to update to 4.3, we will have to find another, older version of what I linked above. Or I can make one if required.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Ok, after playing with the phone for awhile I have found out that I can boot into download mode now. After rebooting, I was able to boot into the stock 4.3 ROM but I noticed I lost root access. Now the problem is I cannot enter the recovery to even flash the file you mentioned above (I flashed CWM via Odin but I can't boot into it). The phone can be seen in Odin now as well. I've done a little bit of research on achieving Root access again but I came across a post that mentioned I could ruin my IMEI number by flashing a "CF-Autoroot" file, should I be worried about doing this now that I'm on 4.3 or am I ok since I didn't use the OTA 4.3 ??
Again, thank you so much for the advise! I'm so glad this phone isn't a brick anymore.
Ok. Since you can get download mode, that changes things.
Boot download mode, remove the sdcard and flash the MJB firmware in Odin. Download here:
http://forum.xda-developers.com/showthread.php?t=2722660
Then, use Towelroot to root the device. (I posted a good guide for this. It should be on page 1 in the Tmobile General section: http://forum.xda-developers.com/showthread.php?t=2793071)
Towelroot is by far the easiest root you'll ever use! Just make sure you read the first two posts before starting!
At this point you should be fully recovered and running stock rooted MJB.
Now before anything else, since you mentioned the imei, backup your NV Data. Very easy!
Install and open Terminal Emulator from the store and enter this:
Code:
su
reboot nvbackup
It'll reboot and create a hidden, permanent, on device backup of your NV data. If corruption is ever detected it'll auto restore during boot, so it essentially protects you from ever losing your imei!
After that, you can do as you wish! If you want to update to 4.4.2 though, I recommend doing that before you root. After flashing MJB, reboot and you should be able to get the official OTA. Then continue with the rest if the instructions above.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Ok. Since you can get download mode, that changes things.
Boot download mode, remove the sdcard and flash the MJB firmware in Odin. Download here:
http://forum.xda-developers.com/showthread.php?t=2722660
Then, use Towelroot to root the device. (I posted a good guide for this. It should be on page 1 in the Tmobile General section: http://forum.xda-developers.com/showthread.php?t=2793071)
Towelroot is by far the easiest root you'll ever use! Just make sure you read the first two posts before starting!
At this point you should be fully recovered and running stock rooted MJB.
Now before anything else, since you mentioned the imei, backup your NV Data. Very easy!
Install and open Terminal Emulator from the store and enter this:
Code:
su
reboot nvbackup
It'll reboot and create a hidden, permanent, on device backup of your NV data. If corruption is ever detected it'll auto restore during boot, so it essentially protects you from ever losing your imei!
After that, you can do as you wish! If you want to update to 4.4.2 though, I recommend doing that before you root. After flashing MJB, reboot and you should be able to get the official OTA. Then continue with the rest if the instructions above.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I flashed the files from the link you posted in Odin and now I am golden! I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs. After seeing that, I checked the system status and it says "OFFICIAL" so I don't really understand why I can't upgrade OTA. I noticed that something I've done has tripped the warranty bit But whatever, I am perfectly fine with staying on 4.3 for now - I didn't see too much to really need to upgrade to 4.4.2 quite yet... although I might try to upgrade again tomorrow and see what happens. I don't really need root at the moment but if I attempt to flash to anything else in the future, I'll give towelroot a shot.
Again, thanks for your help - I owe ya one DocHoliday
CornfedChris said:
.... I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs.
... although I might try to upgrade again tomorrow and see what happens.
Click to expand...
Click to collapse
I've seen reports of this more than once where someone going back to stock initially receives the no updates available msg and then after 24 hrs or so it becomes available. So, your plan sounds good.
CornfedChris said:
I flashed the files from the link you posted in Odin and now I am golden! I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs. After seeing that, I checked the system status and it says "OFFICIAL" so I don't really understand why I can't upgrade OTA. I noticed that something I've done has tripped the warranty bit But whatever, I am perfectly fine with staying on 4.3 for now - I didn't see too much to really need to upgrade to 4.4.2 quite yet... although I might try to upgrade again tomorrow and see what happens. I don't really need root at the moment but if I attempt to flash to anything else in the future, I'll give towelroot a shot.
Again, thanks for your help - I owe ya one DocHoliday
Click to expand...
Click to collapse
Right on! Glad to hear you got it all fixed up! If that update does become available later, please let us know. I've been telling several people to wait a day, but I haven't heard if it actually came through for any of them yet.
If you do decide to root in the future, just don't forget about that backup!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
So tonight while I was watching TV I looked down at my phone and noticed it decided to just go ahead and update itself to 4.4.2, haha. So apparently there's an auto-update defaulted in the settings somewhere. I haven't really noticed too many differences yet but I'm liking it so far. :good:
Hello, Since the Board Giag Tool Doesnt work for the D851 and the only way to unbrick the D851 is by sending it to LG Repair or Some Other Repair or Flashing it with either Medusa Box or Octoplus Box. It wasnt long when @Kathik figured out that the LG G3 F460 S/K/L which is also not supported by the Board Diag Tool can be unbricked by creating a debrick image. You can find his thread here.
This debrick image that @Kathik used is just a dump of the bootloaders from a working LG G3 F460. And all we need to do is to find a way to create the debrick image from a working D851 running the firmware version the bricked D851 was on before it got bricked.
Fortunately for all of us, i got my hands on the zip file which creates the dump or debrick image (Thanks to @Anik49) We have the file.
So all we need is volunteers to flash this zip file in TWRP and once done, you should see a file name debrick.img.zip on your Sdcard.
If this work, we wont need to send our devices for repairs or dissasemble them when they get bricked.
Please feel free to ask any questions about the process.
I flashed the zip and it said it created the debrick.img.zip but I am unable to locate it anywhere. I'm assuming this is because I am on Stock LG Marshmallow with the slight research I did with the thread you linked.
Sorry bud, I tried. It was the only G3 I had hands on. I hope someone else will volunteer in our community.
Maybe u need to downgrade to 5.0
I wrote in the other thread, the day that I put to work to upgrade to Marhsmallow, i will make the debrick files in some versions as 10c, 10f and other higher ... Right now I have a lot of work and I can not do today. Greetings
Any updates on this?
I would also like to hear from a kind soul as now I have a bricked D851 too
UP , anyone ? im suffring with my D851
Jyed said:
UP , anyone ? im suffring with my D851
Click to expand...
Click to collapse
I tried creating the unbrick SD this week but failed to do. Seems like the phone was not actually reading from the SD files.
But I have successfuly created the files to unbrick the phone now as long as the phone is in 9008 mode.
http://forum.xda-developers.com/tmo...hard-brick-t2921642/post67988741#post67988741
makiavelo said:
I wrote in the other thread, the day that I put to work to upgrade to Marhsmallow, i will make the debrick files in some versions as 10c, 10f and other higher ... Right now I have a lot of work and I can not do today. Greetings
Click to expand...
Click to collapse
Hi again, this is my debrick file from D851 running Cloudy 1.2 over a fresh V10c instalation. If it's necesary another version or V10c without Cloudy 1.2, tellme... i will upgrade to marshmallow in next weeks.
http://www.mediafire.com/download/fvyz5bgd8xwb13n/debrick.zip
Dear all, my quick story overwiev:
I have G4 H815 10H
Heat sink upgrade due to bootloop was done week ago and was ok
Wanted make software update to Nougat from 5.1 Lolipop and then some problems comes out
For this puprose wanted gain Root access, so
went through out https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765 , but with 1 mistake, I've download T-Mobile H811 10H Version instead of H815 version and run
dd if=/data/media/0/system.rooted.H81110h.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
After this got Security error #11
So went to Stock Frimware flashing KDZ procedure https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I've decided to flash Europe General H81510B_00.kdz file
but..... now this phone doesn't boot. I can see only Qualcomm hs-usb qdloader 9008 in my device manager.
I know that some of you guys (@TheMadScientist @steadfasterX) are able to unbrick this, really please help.
krzakx said:
Dear all, my quick story overwiev:
I have G4 H815 10H
Heat sink upgrade due to bootloop was done week ago and was ok
went through out https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765 , but with 1 mistake, I've download T-Mobile H811 10H Version instead of H815 version and run
dd if=/data/media/0/system.rooted.H81110h.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
So went to Stock Frimware flashing KDZ procedure https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I've decided to flash Europe General H81510B_00.kdz file
but..... now this phone doesn't boot. I can see only Qualcomm hs-usb qdloader 9008 in my device manager.
I know that some of you guys (@TheMadScientist @steadfasterX) are able to unbrick this, really please help.
Click to expand...
Click to collapse
Well.. You have corrupted the partition table as you used the wrong seek value. The procedure there is EXTREMELY risky and that's one reason why.
You need qfil in that mode. Download this file:
http://droid.binbash.it:8008/unbricking/qfil/h815/G4-h815_fullunbrick_working_7a3ae5809224d.zip
Install qpst and the drivers file from the software folder and after that start qfil. Select the prog_emmc_firehose file from the flashing folder in qfil and select the rawprogramm0 and patch0 file before clicking download.
After succeeded try download mode again and flash any h815 kdz again.
If that doesn't work you either have to wait until I'm back from vacation or find someone else with a box (e.g. infinity) to fix the gpt.
Sent from my LG-H815 using XDA Labs
steadfasterX thanks for your effort! Going to try it morning.
By the meantime maybe @TheMadScientist can say something from his experience?
How about SD card unbricking method https://forum.xda-developers.com/g4/help/unbrick-lg-g4-h811-9008-qualcomm-t3456417
I've tried once but it dosen't work.
Thanks in advance.
krzakx said:
steadfasterX thanks for your effort! Going to try it morning.
By the meantime maybe @TheMadScientist can say something from his experience?
How about SD card unbricking method https://forum.xda-developers.com/g4/help/unbrick-lg-g4-h811-9008-qualcomm-t3456417
I've tried once but it dosen't work.
Thanks in advance.
Click to expand...
Click to collapse
Guys I just studied it I ever actually had to unbrick mine. I studied in help for others so I don't know how much help I would exactly be
krzakx said:
steadfasterX thanks for your effort! Going to try it morning.
By the meantime maybe @TheMadScientist can say something from his experience?
How about SD card unbricking method https://forum.xda-developers.com/g4/help/unbrick-lg-g4-h811-9008-qualcomm-t3456417
I've tried once but it dosen't work.
Thanks in advance.
Click to expand...
Click to collapse
Yes that way is possible too. The only way it worked for me is by using dd to flash the gpt to the external sdcard and then flashing the bootloader stack plus laf. Quite easy if you have some Linux experience. But if not... you need a proper guide..
maybe there is a working h815 image out there as well but the one you're referring to is for the h811.... OMG you haven't used that one did you??? H811 has ARB!!! If you don't know what that means read https://bit.do/antirollg4 and ASK before using files not related to your model.
I'm very interested what SALT would tell us about your ARB once the device is working again....
Sent from my LG-H815 using XDA Labs
I have some base linux experience, (Debian) so no "handle follow guide" would be needed.
Yes, I have used H811 file, that was my mistake . I've exactly used this file http://downloads.codefi.re/thecubed/lg_g4/lef/h81110h.tar.gz from this topic https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765 ,
Dear steadfasterX , please take one more time overlook for my situation and think about wright steps. Waiting for yours advices.
Best regards.
krzakx said:
I have some base linux experience, (Debian) so no "handle follow guide" would be needed.
Yes, I have used H811 file, that was my mistake . I've exactly used this file http://downloads.codefi.re/thecubed/lg_g4/lef/h81110h.tar.gz from this topic https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765 ,
Dear steadfasterX , please take one more time overlook for my situation and think about wright steps. Waiting for yours advices.
Best regards.
Click to expand...
Click to collapse
No I was talking about the sdcard files. Flashing the h811 system file will not increase ARB (as said you corrupted the gpt though) but when you flash the h811(which you linked in your second post!) files to write the sdcard and then trying to boot from the sdcard it very likely will increase the ARB.
Ok so you haven't used the sdcard method yet?
Then try that one:
https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853
Again try to boot to download mode with that and flash a h815 kdz. You MAY have luck but it depends. Give it a try.
Sent from my LG-H815 using XDA Labs
krzakx said:
Dear all, my quick story overwiev:
Click to expand...
Click to collapse
In the photo of your phone in download mode, it identifies as an LG-H810 running H81010o.
If I may ask, where did you get this phone from?
terence.tan said:
In the photo of your phone in download mode, it identifies as an LG-H810 running H81010o.
If I may ask, where did you get this phone from?
Click to expand...
Click to collapse
Dear @terence.tan you've asked good question.
So phone is from China seller, additionally I've made some photos of motherboard and got confused as you can see there VS986_MAIN_1.0 oh no... is all so mixed up.
Unfortunately do not have system.img back up eh.... stupid me.
SD Card method doesn't work.
Now I am think if I should go this method
https://forum.xda-developers.com/g4/help/lg-g4-vs986-super-hard-brick-unbrick-fw-t3666784
it's only idea because my motherboard seems to be VS968 labeled, but let me ask you guys as specialists.
Waiting for answer. Thanks.
One more question regarding SD Card method guys,
I've just prepared SD card fallowing this topic https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853 , but it doesn't work.
Just for confirmation here you can se parted print, can you check please If I've burned SD Card image properly?
https://hastebin.com/inimikipux.sql
Thanks
Hi there! So you have a phone with a VS986 main board, which identifies as an H810, which was sold to you as an H815. (Which you have flashed with H811 software.)
The seller of your phone in China has done something strange to make this all work, we don't know what.
I'm sure you will understand, it will be very difficult for anyone to tell you exactly what to do.
The sdcard unbrick you tried didn't work because it has the boot stack files for H815, which require a phone with ARB version 0. I suspect you will need to copy either the VS986 or H810 boot stack files to your sdcard for it to work. (I don't know which, only the seller knows...)
However trying alternate boot stacks has a chance to increment your ARB; you should consider the consequences and not use anything with a high ARB before trying lower ones...
steadfasterX said:
Well.. You have corrupted the partition table as you used the wrong seek value. The procedure there is EXTREMELY risky and that's one reason why.
You need qfil in that mode. Download this file:
http://droid.binbash.it:8008/unbricking/qfil/h815/G4-h815_fullunbrick_working_7a3ae5809224d.zip
Install qpst and the drivers file from the software folder and after that start qfil. Select the prog_emmc_firehose file from the flashing folder in qfil and select the rawprogramm0 and patch0 file before clicking download.
After succeeded try download mode again and flash any h815 kdz again.
If that doesn't work you either have to wait until I'm back from vacation or find someone else with a box (e.g. infinity) to fix the gpt.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I'm literally praying to the Android Gods that this works. If it doesn't then I am truly truly lost...
Wish me luck!
Ugh!
I get this...
Sending NOP
ReadFile last error: 0
Response is NULL
NOP: Fail Code: 14
Unable to send FireHose NOP. Device is not in FireHose mode!
Download Fail:FireHose Fail FireHose Fail: Failed to send FireHose NOP to the phone.
Finish Download
Man, This LG is kicking my ass!
Any suggestions?
donniegalaxy2 said:
Ugh!
I get this...
Sending NOP
ReadFile last error: 0
Response is NULL
NOP: Fail Code: 14
Unable to send FireHose NOP. Device is not in FireHose mode!
Download Fail:FireHose Fail FireHose Fail: Failed to send FireHose NOP to the phone.
Finish Download
Man, This LG is kicking my ass!
Any suggestions?
Click to expand...
Click to collapse
Having just these problems on qfil with my h815 did you found a solution?
sr.arenisca said:
Having just these problems on qfil with my h815 did you found a solution?
Click to expand...
Click to collapse
No solution found by me!!! I gave up and sold the phone to ecoATM!
first of all - great job steadfasterX and cWks! with unlocking LG G4
probably I bought (in China) "Frankenstein" LG G4 phone, because it should be H810, but on mainboard is written VS986. I have unlocked it by SALT and instaled TWRP, but I have not find any ROM which would work
based on the information from the vendor it should have V10o ATT firmawe, but in the LG software it shows that is model H815 with firmware V29a.
subsequently I brick it and unbrick it a try to fash .tot files using LG software, but unsuccessful. Because the LGUp shows, that it is model LS991 finally I flash the LS991ZVD.tot file. during booting, the android will stop, when "configuring your phone", probably LS991 files have wrong modem...
now works the download mode and recovery mode only for this phone (no fastboot) and in SALT shows that is ARB4 which is not possible to unlock
Is there any possibility to:
1. to flash correct modem (possibly for VS986?) - 1.a) how is possible to modify the modem in tot file?
2. erase eMMC or go back to ARB2?
I have the backup prepared in TWRP with ARB2, but how us it to recover the phone?
Many, many, many thanks for help!
Or it is easier to buy in Chine the new motherboard? and which?
Thank you very much for answers!!!
Dedulo said:
first of all - great job steadfasterX and cWks! with unlocking LG G4
probably I bought (in China) "Frankenstein" LG G4 phone, because it should be H810, but on mainboard is written VS986. I have unlocked it by SALT and instaled TWRP, but I have not find any ROM which would work
based on the information from the vendor it should have V10o ATT firmawe, but in the LG software it shows that is model H815 with firmware V29a.
subsequently I brick it and unbrick it a try to fash .tot files using LG software, but unsuccessful. Because the LGUp shows, that it is model LS991 finally I flash the LS991ZVD.tot file. during booting, the android will stop, when "configuring your phone", probably LS991 files have wrong modem...
now works the download mode and recovery mode only for this phone (no fastboot) and in SALT shows that is ARB4 which is not possible to unlock
Is there any possibility to:
1. to flash correct modem (possibly for VS986?) - 1.a) how is possible to modify the modem in tot file?
2. erase eMMC or go back to ARB2?
I have the backup prepared in TWRP with ARB2, but how us it to recover the phone?
Many, many, many thanks for help!
Or it is easier to buy in Chine the new motherboard? and which?
Thank you very much for answers!!!
Click to expand...
Click to collapse
Ok well first of all read my signature about the anti roll back details. It is absolutely impossible to flash lower ARB . That's for what it is made for obviously .
Next is that you have flashed stupid files and besides they're with an arb higher than 2 so you cannot unlock it anymore.
we all know that Frankenstein devices are special in many terms .
one example is nobody knows what they do or flash in the primary boot loader which we cannot read out. That means we don't know which RAM is compatible and we do not know if they make any modifications in the signed boot loader stack which ensure they can load Frankenstein devices.
So even if you flash for example h810 files with an arb of 4 it may not load or working properly the same goes for vs 986 of course .
yeah and I have to repeat myself but flashing that arb of 4 was bad in another way,too. Having that arb you have no way to use qfil anymore as that works only up to arb 3. So you have no way to use it to flash for example other models image files or even more important to unbrick your device if it ever hard bricks.
You can of course use a text editor to modify any kdz file and flash whatever you like .. The other option is to use the SD card unbrick method linked in my signature but it requires to hard brick your device first. I can tell you how but in your situation it is very risky if you can't get the SD card unbrick working . so I would recommend to go the Hex editor way just search XDA for how to use it and flash vs986 files with an ARB of 4
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
Ok well first of all read my signature about the anti roll back details. It is absolutely impossible to flash lower ARB . That's for what it is made for obviously .
Next is that you have flashed stupid files and besides they're with an arb higher than 2 so you cannot unlock it anymore.
we all know that Frankenstein devices are special in many terms .
one example is nobody knows what they do or flash in the primary boot loader which we cannot read out. That means we don't know which RAM is compatible and we do not know if they make any modifications in the signed boot loader stack which ensure they can load Frankenstein devices.
So even if you flash for example h810 files with an arb of 4 it may not load or working properly the same goes for vs 986 of course .
yeah and I have to repeat myself but flashing that arb of 4 was bad in another way,too. Having that arb you have no way to use qfil anymore as that works only up to arb 3. So you have no way to use it to flash for example other models image files or even more important to unbrick your device if it ever hard bricks.
You can of course use a text editor to modify any kdz file and flash whatever you like .. The other option is to use the SD card unbrick method linked in my signature but it requires to hard brick your device first. I can tell you how but in your situation it is very risky if you can't get the SD card unbrick working . so I would recommend to go the Hex editor way just search XDA for how to use it and flash vs986 files with an ARB of 4
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
You are right. I have done some stupid steps, because the method for unlocking my "Frankenstein" phone did not work. I read about the anti roll back, but I hoped that something had changed (also the unlocking process has gradually developed )
I had to take apart the phone first and find out what was written on the motherboard This was a big mistake!
Today I have bricked (hard?) my phone by flashing LS991 ZVB ARB3 tot file, because I don't know, how to work with Hex editor.
Which KDZ file I need to download for SD card unbrick? I suppose that VS986 with ARB4, right?
Thanks for a help and reply!
Dedulo said:
You are right. I have done some stupid steps, because the method for unlocking my "Frankenstein" phone did not work. I read about the anti roll back, but I hoped that something had changed (also the unlocking process has gradually developed )
I had to take apart the phone first and find out what was written on the motherboard This was a big mistake!
Today I have bricked (hard?) my phone by flashing LS991 ZVB ARB3 tot file, because I don't know, how to work with Hex editor.
Which KDZ file I need to download for SD card unbrick? I suppose that VS986 with ARB4, right?
Thanks for a help and reply!
Click to expand...
Click to collapse
well I see. the ARB is (as written in the linked guide) a (extreme likely) physical blown fuse, so a process which can not be reverted..
yes you hard-bricked the phone by flashing a lower ARB then the current one. once you flashed ARB 4 you can't flash ARB lower then 4.
the good is as you have hard-bricked it you may be able to use the sdcard unbrick but that requires the 9008 qdl mode:
connect the device to your PC and view the device manager. does it add something like QHUSB BULK? If yes use the vs986 files + UsU files as written the sdcard thread.
You can also use FWUL from booting on USB and just type: lsusb in a terminal after connecting the phone. paste the output here then. It should show something like "QDL 9008" or "QualComm...". If thats the case use the vs986 files + UsU files as written in the sdcard thread.
If both of the above does not show up the QDL 9008 mode.. well try it without battery in again. If it still failing it is likely gone. sorry. The QFIL files available do not work with ARB >3 so.
You can still read on in the sdcard unbrick thread in the second post to find out how to force the sdcard unbrick mode (that differs from the the QDL mode and so need to disassembling the whole mainboard and doing tricky stuff without a guarantee of that it work at the end.)
.-
steadfasterX said:
well I see. the ARB is (as written in the linked guide) a (extreme likely) physical blown fuse, so a process which can not be reverted..
yes you hard-bricked the phone by flashing a lower ARB then the current one. once you flashed ARB 4 you can't flash ARB lower then 4.
the good is as you have hard-bricked it you may be able to use the sdcard unbrick but that requires the 9008 qdl mode:
connect the device to your PC and view the device manager. does it add something like QHUSB BULK? If yes use the vs986 files + UsU files as written the sdcard thread.
You can also use FWUL from booting on USB and just type: lsusb in a terminal after connecting the phone. paste the output here then. It should show something like "QDL 9008" or "QualComm...". If thats the case use the vs986 files + UsU files as written in the sdcard thread.
If both of the above does not show up the QDL 9008 mode.. well try it without battery in again. If it still failing it is likely gone. sorry. The QFIL files available do not work with ARB >3 so.
You can still read on in the sdcard unbrick thread in the second post to find out how to force the sdcard unbrick mode (that differs from the the QDL mode and so need to disassembling the whole mainboard and doing tricky stuff without a guarantee of that it work at the end.)
.-
Click to expand...
Click to collapse
Yes, Q HS-USB QDLoader 9008 is in the Ports (in DevMan), but now I need to prepare SD card, because the old files (which I have used for unbricking last time) do not work .
Dedulo said:
Yes, Q HS-USB QDLoader 9008 is in the Ports (in DevMan), but now I need to prepare SD card, because the old files (which I have used for unbricking last time) do not work .
Click to expand...
Click to collapse
sure. you need ARB 4 files.
.-
Dedulo said:
Yes, Q HS-USB QDLoader 9008 is in the Ports (in DevMan), but now I need to prepare SD card, because the old files (which I have used for unbricking last time) do not work .
Click to expand...
Click to collapse
I don´t find the right kdz for VS986 with ARB4. Can I use yours? (these two with ARB2: http://leech.binbash.it:8008/stock/LG/vs986/2BA/)
Dedulo said:
I don´t find the right kdz for VS986 with ARB4. Can I use yours? (these two with ARB2: http://leech.binbash.it:8008/stock/LG/vs986/2BA/)
Click to expand...
Click to collapse
well you still do not read my linked guide or understand what ARB is, right? Its IMPOSSIBLE to use an ARB lower then 4 in your case. so NO you can NOT use these.
Well I assumed there would be firmware with ARB 4 for the vs986 but it seems the highest is ARB 2..
keep in mind: everything you do now is extremely risky with maybe no point of return! If it bricks and is not switching to the 9008 mode.. you are lost!
After looking around a bit including in my ARB thread (which I mentioned) the LS991 seems to be the only one with ARB higher then 3 (so 4).
you are stuck with LS991 now. that means even when you may be able to unbrick with the sdcard unbrick it means you may never get cell service.
so try a LS991 kdz with ARB 4 (ZVD as you flashed that one should be fine) for the unbrick files to bring it at least back to life.
.-
steadfasterX said:
well you still do not read my linked guide or understand what ARB is, right? Its IMPOSSIBLE to use an ARB lower then 4 in your case. so NO you can NOT use these.
Well I assumed there would be firmware with ARB 4 for the vs986 but it seems the highest is ARB 2..
keep in mind: everything you do now is extremely risky with maybe no point of return! If it bricks and is not switching to the 9008 mode.. you are lost!
After looking around a bit including in my ARB thread (which I mentioned) the LS991 seems to be the only one with ARB higher then 3 (so 4).
you are stuck with LS991 now. that means even when you may be able to unbrick with the sdcard unbrick it means you may never get cell service.
so try a LS991 kdz with ARB 4 (ZVD as you flashed that one should be fine) for the unbrick files to bring it at least back to life.
.-
Click to expand...
Click to collapse
OK, so we understood each other. Because I flashed wrong file LS991 ZVD, I can't go back - only to the same firmware (because of ARB etc.). There is no way to change it (to VS986) or flash anything else
and, if I will be lucky, then the phone comes back to point during booting, when it stops in "configuring your phone". Never use him anymore for call services? How to go through this (configuration)?
There is only one way - to buy in Chine the new motherboard, but which (H815)?
Dedulo said:
OK, so we understood each other. Because I flashed wrong file LS991 ZVD, I can't go back - only to the same firmware (because of ARB etc.). There is no way to change it (to VS986) or flash anything else
and, if I will be lucky, then the phone comes back to point during booting, when it stops in "configuring your phone". Never use him anymore for call services? How to go through this (configuration)?
There is only one way - to buy in Chine the new motherboard, but which (H815)?
Click to expand...
Click to collapse
buy a h811 one as you can unlock h811 within just fastboot.
if you can't get one: the h815 international (so no h815p, h815tr etc) as it can be unlocked officially by the LG website.
if you can't get one: any h815 model should be fine as you can unlock by UsU and I haven't heard any big issues here.
good luck
.-
steadfasterX said:
buy a h811 one as you can unlock h811 within just fastboot.
if you can't get one: the h815 international (so no h815p, h815tr etc) as it can be unlocked officially by the LG website.
if you can't get one: any h815 model should be fine as you can unlock by UsU and I haven't heard any big issues here.
good luck
.-
Click to expand...
Click to collapse
I will try to unbrict it first and we will see... maybee I will wait for motherboard. this will be ok?
https://www.aliexpress.com/item/For...pm=a2g0s.13010208.99999999.259.88b93c00XlwucM
or is there any issue?
thank you very much for your time and help!
Dedulo said:
I will try to unbrict it first and we will see... maybee I will wait for motherboard. this will be ok?
https://www.aliexpress.com/item/For...pm=a2g0s.13010208.99999999.259.88b93c00XlwucM
or is there any issue?
thank you very much for your time and help!
Click to expand...
Click to collapse
I cannot guide you in where to buy or if that one is valid sorry.
.-
steadfasterX said:
I cannot guide you in where to buy or if that one is valid sorry.
.-
Click to expand...
Click to collapse
OK, I understand.
Could you be so kind and send me a link for kdz file? I don't find it. I have only LS991 ZVD tot file. It is possible to convert it to kdz?
Thank you!
I have prepared the SD card from tot file (not bin but img files) except PrimaryGPT.gpt (I don't fin it in tot file, only the PrimaryGPT_0.bin from another KDZ).
The proper KDZ for LS991 ZVD I could not download from LG support site, because my FR phone has IMEI VS986.
Until now the SD card unbricking method doesn't work for me.
I will try LS991 ZVB, which I used for bricking the phone.
Any idea what to do?
Hello guys, so after spending a lot of time doing research on which partitions to extract to flash. I found out that the partitions on the link did the trick. I have 2 Sprint V50 same model one is rooted, the other is not, made the backup with Qfil from the non rooted and flashed those onto the rooted, that did the trick. Only use Qfil to flash partitions, do not use TWRP, it'll fail and your data will be erased to get it to work again!
The files are the one's I used, so I upload those to you guys! Hope it helps someone, if you have a doubt, just ask I'll be happy to help.
When I have some time I'll try to make a guide of it. If a new update arrives I'll update this post with the new files!
PARTITIONS 20N - Google Drive
drive.google.com
thx bro.
Strange I've never had any issue with flashing these in TWRP as long as I clear data/userdata. Then again I prefer starting fresh on a new OTA.
Thanks
Am I supposed to flash these files on just slot b or both slots
Merlve said:
Am I supposed to flash these files on just slot b or both slots
Click to expand...
Click to collapse
these are to be flashed on your current slot.. so A if you're on A
THANK YOU!
cloud1250000 said:
these are to be flashed on your current slot.. so A if you're on A
Click to expand...
Click to collapse
How can this be viewed on the phone?
i flashed these, but when i reboot to system it gets stuck on the lg logo. any idea?
1maaax said:
i flashed these, but when i reboot to system it gets stuck on the lg logo. any idea?
Click to expand...
Click to collapse
Did you ever figure this out? I can't seem to gain root anymore with magisk flashed images... the system sticks at the lg logo... once I restore boot_a it boots fine
q-killer said:
Did you ever figure this out? I can't seem to gain root anymore with magisk flashed images... the system sticks at the lg logo... once I restore boot_a it boots fine
Click to expand...
Click to collapse
I've never figured it out, sorry
1maaax said:
I've never figured it out, sorry
Click to expand...
Click to collapse
I just got mine fixed by remote unlock service in Ukraine in v50 telegram channel.... He only has internet on tues-wed but its a reasonable $28 to restore this device. Good luck
q-killer said:
I just got mine fixed by remote unlock service in Ukraine in v50 telegram channel.... He only has internet on tues-wed but its a reasonable $28 to restore this device. Good luck
Click to expand...
Click to collapse
I just flashed kdz with lgup to restore original firmware, in case it happens to you again
1maaax said:
I just flashed kdz with lgup to restore original firmware, in case it happens to you again
Click to expand...
Click to collapse
1maaax said:
I just flashed kdz with lgup to restore original firmware, in case it happens to you again
Click to expand...
Click to collapse
But... My phone won't go into download mode any longer. It did prior to the restore service. Also, I was not able to locate a kdz image for this phone.... Only the international version. Any ideas on how to restore download mode and flash a custom rom?
q-killer said:
But... My phone won't go into download mode any longer. It did prior to the restore service. Also, I was not able to locate a kdz image for this phone.... Only the international version. Any ideas on how to restore download mode and flash a custom rom?
Click to expand...
Click to collapse
What happens when you try to boot download mode? I'm not sure which kdz you are looking for. If it is sprint, I recommend looking for the v50 sprint backup files shared on xda. It isn't kdz, but result should be more or less the same.
Since the original link is dead, I've mirrored the files in case anyone needs them:
V450PM20n
C D said:
Since the original link is dead, I've mirrored the files in case anyone needs them:
V450PM20n
Click to expand...
Click to collapse
THX a lot, btw, is your V50 Still working on t-mobile?
rrhhuutt said:
THX a lot, btw, is your V50 Still working on t-mobile?
Click to expand...
Click to collapse
Nowadays, I can only connect via Wi-Fi calling while the cellular connection no longer works, so I'm guessing that T-Mobile is doing some IMEI-based blocking on their end.
Hrhigher said:
Hello guys, so after spending a lot of time doing research on which partitions to extract to flash. I found out that the partitions on the link did the trick. I have 2 Sprint V50 same model one is rooted, the other is not, made the backup with Qfil from the non rooted and flashed those onto the rooted, that did the trick. Only use Qfil to flash partitions, do not use TWRP, it'll fail and your data will be erased to get it to work again!
The files are the one's I used, so I upload those to you guys! Hope it helps someone, if you have a doubt, just ask I'll be happy to help.
When I have some time I'll try to make a guide of it. If a new update arrives I'll update this post with the new files!
PARTITIONS 20N - Google Drive
drive.google.com
Click to expand...
Click to collapse
Hrhigher said:
Hello guys, so after spending a lot of time doing research on which partitions to extract to flash. I found out that the partitions on the link did the trick. I have 2 Sprint V50 same model one is rooted, the other is not, made the backup with Qfil from the non rooted and flashed those onto the rooted, that did the trick. Only use Qfil to flash partitions, do not use TWRP, it'll fail and your data will be erased to get it to work again!
The files are the one's I used, so I upload those to you guys! Hope it helps someone, if you have a doubt, just ask I'll be happy to help.
When I have some time I'll try to make a guide of it. If a new update arrives I'll update this post with the new files!
PARTITIONS 20N - Google Drive
drive.google.com
Click to expand...
Click to collapse
My friend ask me to changer firmware lg v450 to v500 but messed up some files and now phone is just showing logo and i didn't find stock firmware could you please re-upload your rom
i need your help