EDIT: no longer need this. It is possible to make your own...
There is a chance that I may not have fried my V10 by shorting the test point, but to test that I need a full Nougat dump (something I can not believe I didn't make from my own phone -- I only have a full MM dump).
If there is someone that has rooted Nougat AND flashed all the Nougat partitions (v30b_update.zip and full_nougat.zip), and is willing to do a full dump, please let me know.
It is preferable if you have access to Linux because you will need to null out some partitions that have private data, and it is much easier to explain how to do it on Linux.
Lastly, this image will be 64gigs uncompressed, but it compresses very well.
Thanks,
-- Brian
Wish I can help, but mine is not rooted..
Hopefully I can bring my phone back to life (one way or another) so I can continue on. I got my board of eBay, but it was more dead than my current board.
runningnak3d said:
Hopefully I can bring my phone back to life (one way or another) so I can continue on. I got my board of eBay, but it was more dead than my current board.
Click to expand...
Click to collapse
That sounds bad. Hopefully someone will upload it.
if i can downgrade it , ill re upgrade to rooted nougat and get a dump but i dont know how to dump and dont have the image for downgrade.
@runningnak3d There's a guy selling one in General. Perhaps you can get a dump off of him?
@runningnak3d I currently have one V10 that I cannot get past the Checking Updates screen in the setup wizard on Nougat (with TWRP) which I am considering performing a KDZ wipe and another that went black screen after I flashed MM (also with TWRP). If I do a KDZ wipe on the first one, I could do a dump for you but I would have to look up how to. You are also welcome to buy the board from the second V10 from me but I'm unsure if you can revive it.
Thanks all, but everything I needed to make my own was staring me in the face.
-- Brian
i will help if i can , but didnt have root yet
@runningnak3d I'm in a need of a Nougat dump for H901, to make a bootable sdcard. Could you share yours or guide how to make one from nougat kdz?
Due to messing the aboot partition (while trying to shut the "big cores" off) the phone does not boot, nor enter download mode. On powering on, it only vibrates. QPST does not work with the phone put into 9008, it returns "target may be unstable". Before that, the phone was rooted, with bootloader unlocked, updated to nougat via the recovery, with the ZIPs.
Any help would be greatly appreciated
Be glad to, and it is easy, but you need dd. If you use Windows, there may be some program that can do something similar, but I haven't used Windows in years. You can always install a very basic Cygwin environment...
* Insert 64gig SD card
* Dump KDZ
* dd if=PrimaryGPTxxxxxx of=/dev/mmcblk0
The xxxxx above is because I can't remember what it gets dumped as, but it will be obvious.
Once you have the partition table on the sdcard, get a list of the partitons:
* gdisk -l /dev/mmblck0
Then proceed to flash the rest of KDZ onto their individual partitions.
For example, I believe that modem was partition 1, so:
* dd if=modemxxxxx of=/dev/mmcblk0p1
Repeat for every partition from the KDZ except system (unless you want to fully boot from the SD card). Also, you can flash recovery with TWRP, and then you can boot from the SD card to recovery and then you only need to flash your aboot partition, so you don't have to use download mode to flash the entire KDZ.
Let me know if you need me to clarify anything.
EDIT: If you do boot to recovery from the SD card, you will need to make sure to flash the correct device. When you go into an adb shell, you will have two mmcblk devices (mmcblk0 and mmcblk1). I don't remember which will be which, so to be safe flash the aboot partition on both...
-- Brian
@runningnak3d Thank you for your reply! I have Ubuntu 17 as a bootable DVD. Does the sdcard have to be formatted in a specific filesystem before doing this? Another question I have, is that the sdcard shows up as dev/sdd for me but it also shows that dev/sdd1 exists on it, so to which should I dd the GPT table to?
I tried to dev/sdd and wrote the rest of KDZ to the partitions, but the phone has not booted (its 64gb sd hc class 10 card). After dd-ing the PrimaryGPT, the terminal mentions that backupGPT is corrupted and that MBR is protective on the sdcard. Also, GParted shows "unknown" for each partition, and modem partition shows up as fat16 one.
Perhaps I should try different nougat KDZ? the phone's sticker under battery says it's H901, so was written in the phone under settings menu (phone also had t-mobile bloatware) and in LGUP when updating to MM, yet the motherboard has VS990 written on it.
My phone said vs990 on the board as well, so that isn't the issue. You need to flash a few partitions from the phone that aren't in the KDZ ... you will have to get someone to dump them for you.
The only place I had them was on an SD card that I have already wiped since I don't have a v10 anymore.
I will have to look in SBL1 to get you a list that you will have to ask for.
They are all just firmware, and contain nothing specific to a users phone, so anyone with a rooted Nougat phone can safely dump them for you.
Please bear with me. I am currently trying to revive my H910 and I order an H918 that I am going to use to help someone with, but I will try to get you the info ASAP.
H901 VS990 board 9008 brick help
@runningnak3d Hey, you seem like an expert at unbricking V10s. I have a H901 that has vs990 motherboard in it. It bricked while I was updating through LG Bridge. I now only have access to qualcomm 9008 mode.
From my understanding, there are 2 ways to solve this. QFIL or booting from dump image through sdcard. The qfil way didn't work for me, since there aren't any compatible .mbn files and xml for VS990 owners. So my only other option is getting to download mode via sdcard method, and I need the dump files for that. If I do what you've told @Mr_pringle, would my phone enter download mode? What exactly would I have to do? Thanks
@N3XTN3XUS What version were you on, and what version did LG Bridge try to update you to?
runningnak3d said:
@N3XTN3XUS What version were you on, and what version did LG Bridge try to update you to?
Click to expand...
Click to collapse
mm to nougat. Do you have the dump img for mm by any chance?
Unfortunately you are going to have to roll your own with the instructions I gave above.
In order to do that, you need to find out what model you should be flashing. I know you said your board said VS990, I am sitting here looking at my dead board, and it says VS990 on it as well, so H901 Nougat *should* have worked for you. I don't have any idea where you should start looking, but you do need to know that before making an SD card or even if you make a perfectly good card, it won't work
-- Brian
Related
I have the LG v10 from T-Mobile. I bought the phone a few weeks ago and it had Marshmallow installed. Somehow I managed to install TWRP/SuperSU, but then had issues and flashed the official/stock MM image with LGUP. Afterwards I discovered that MM for this device is not currently rootable, and TWRP cant be flashed via fastboot because MM blocks it. So I returned the device to T-Mo store, lied and said it force-upgrade to MM and had began freezing up. They did an in-store trade for an identical model that had 5.1.1 Lollipop.
The device is currently still in factory condition in every way, with the exceptions that I unlocked the bootloader via fastboot and installed TWRP. Nothing else is modified yet and no custom ROMs have been flashed.
I recently became aware that there is no stock LP image for the T-Mo v10, only MM images are available. After all the issues I've had, I'm now paranoid and want to have a complete dump of the phone's entire contents (partitions, bootloader, system, etc) that is in KDZ or TOT format, and can be reflashed with the standard tools available. Since there is nothing official then I would have to do this myself. This would be useful in the event that I run into lots of issues and need to do a emergency stock restore.
I found a thread by XDA user @tungkick, in which he created a modified dump of the device while it was running LP. However, because it was unofficial and he didn't disclose this upfront, his thread was shut down. His file bricked multiple MM users. I assume it would work if one was still on LP and hadn't upgraded to MM. Not to mention that I cant seem to find his file anywhere. So I figure the safest way is to do this myself. I would be willing to make this file available to the community when finished, with full disclosure that it is unofficial. But the problem is, I don't know how.
I know that the Linux dd command can be used to dump images of various things, and I have read that this can be done on PC by connecting to the device via ADB or fastboot. This would hopefully result in an image file that contained the contents of all the device's partitions.
But another issue would be converting it to KDZ or TOT. And it would have to be done in such a way that it would be flashable with the standard tools.
Can someone please give me a technical understanding of the tools and knowledge I would need to undertake this? Would it be too complicated for someone like myself that has little Android/Linux experience (but is generally competent with computers/technology)?
Thanks for any advice!
Noone can help me with this?
To the mods/admins: I think maybe I posted this in an area where it is unlikely to get any useful answers. Can someone move the thread to the Help& Troubleshooting area of the general LG v10 forum (not here in the T-Mobile subforum)? Thanks!
I think it's just that if that could. have been done someone would have done it already. Even tungkick didn't make one for tmobile for some reason. I think because he made his root injected files from official lg files and lg has not released a kdz or tot for tmobile LP.
Just my observation... I could be wrong.
Sent from my pretty nifty brand new LG V10
@ planetbeen: I don't see why it wouldn't be possible. Linux's dd program can dump almost any connected device that it can see. But then it needs to be converted into a standard TOT/KDZ that can be flashed with any standard software. Which is why I want to create an unofficial backup of the entire phone before modifying it further, so I can do an emergency restore if necessary. I just need the right instructions from people who have the technical expertise.
I had trouble with my old LG v10, I had used LG's LGUP program to flash it to Marshmallow from my PC, only to realize that it couldn't be rooted or have a custom recovery. And I also discovered that I couldn't downgrade to Lollipop. So I returned the phone to the store and exchanged it for an identical model that still had LP. I just told them it had auto-upgraded to MM and started crashing. They exchanged, no questions. Before this I had various issues, like GPS crashing randomly when turning it on, Bluetooth also doing the same thing, and the Settings app also crashed sometimes when accessing the Security menu. I had flashed multiple ROMs, but stock-based and CM/AOSP-based, but kept running into issues, oftentimes the same ones. So I figured that something in the phone had become corrupt and figured that flashing stock MM would fix everything. Big mistake. I'll never let this phone upgrade again until MM is solidly hacked, which from what I've read may be a long time away. I paid enough for this phone and I really value hackability. I'm not the average Joe that just uses my phone for Facebook, etc. To me, if a phone cant be hacked, then buying/owning it is a waste of time/money. Same thing with every computer/electronics device I've ever owned.
Thanks again!
It looks like I'm going to have problems getting answers from knowledgable people, so instead of waiting, I'm going to take a little initiative and at least try to do the dump with dd. I found a post by @tungkick that says to enable USB debugging and make a backup file via dd with the 'adb shell' and 'su' commands. Is the following syntax correct?
dd if=/dev/block/mmcblk0 of=/sdcard/H901.bin bs=1024 count=6291456
Do I run these commands from a PC via command line while connected via USB? Or directly on the device in a terminal emulator? Or do I need to run the command while in fastboot/bootloader mode, while Android is powered down?
Thanks again!
Stock use tool extract kdz then choose file dz (use lgup)
remember can not flash if phone update 6.0
Never downgrade because phone brick now.
version 5.1.1
https://drive.google.com/file/d/0B_Hol5T47S-bQkJVemgzMDV0Nzg/view?usp=sharing
@ tungkick: Thanks for the info. I had used the dd command to dump my phone to external SD before, but the file was 6GB! I was unable to use Tool KDZ Extract to extract the *.dz from the *.kdz file you provided. I was able to flash your KDZ with LGUP, but it boots me into TWRP recovery near the end.
Do you mind if I publicly distribute a mirror copy of your file on my Dropbox, so that it will be available to others that need the stock LP firmware for this device?
Thanks again!
I just wanted to say that flashing your KDZ has possibly screwed up my device permanently. Your image has TWRP, not the stock recovery, and is pre-rooted with SuperSU. Normally this would be good but...............
Near the end of LGUP, the device boots into TWRP. System and MicroSD are mounted, but nothing else (data, cache, dalvik, etc). I was able to obtain a stock recovery *.img, then copied it over to my MicroSD while in recovery. Then I flashed it, booted the phone into stock recovery, and performed a factory reset. Afterwards I booted into system, and all looked good, until it got to the "Checking connection" screen, then a lot of apps started force-closing repeatedly. Because of this I can't get to the Home screen, and no amount of factory reset is working. It just keeps happening over and over again.
How to get out of this mess, anyone?
Help please!!!
Still looking for a solution and would really appreciate any help!
My theory is that the /cache and /data partitions somehow got corrupted during the flash. So I tried booting into FastBoot mode and issueing the commands:
fastboot erase cache
fastboot format cache
fastboot erase userdata
fastboot format userdata
It just says something something along the lines of "remote: cant format/erase in an unlocked state". If I relock the bootloader, it says that it cant erase/format in a locked state.
TWRP still cant read those partitions (they won't mount and cant be mounted), and the apps still start force-closing almost immediately after rebooting into system, before I can complete the setup, preventing me from getting to the home screen.
@ tungkick: Is there any possibility we can arrange a TeamViewer meeting to fix this?
Thanks!
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse
Hello everyone.
I know many of you have worked on safe-strap TWRP recovery in light of the inability to unlock the bootloader.
I have been testing on my note 8 and as someone else pointed out if you install the Engineering Rom listed below you will have the oem unlock toggle.
This service rom.
COMBINATION_FA71_N950USQU2AQK3_CL12591988_QB15811772_REV00
As far as everyone believes this option is only for FRP reset.
To tell you anyway the FRP reset is simply ZEROing out the persistence partition.
A persistence partition that is ZERO is default OEM Unlock ON. Meaning the toggle is set to not allow oem unlocking.
Using the mentioned rom above it is possible to set oem unlocking allowed.
This does not mean the bootloader is unlocked.
But i do feel that it is very close to unlocked and leads me down a path that i can unlock the bootloader.
I have a Galaxy Tab E that is allowed to be bootloader unlocked.
By doing a dd dump of all partitions then doing hexdump of the dd dumps the hex dumps can be diffed in terminal effectively.
By doing a comparison of the unlocked and locked state partitions I can Identify the changes being made.
I am still in the process of testing and comparing the dumps.
I need a TWRP build for N950USQU2AQK3 or ver 2 bootloader.
I almost think I have the bootloader set to where it will allow TWRP to Run.
This may not be a full unlock yet but having a good TWRP build would be a good test.
I could build TWRP myself but i do not have a build system setup currently..
So one of you that has compiled twrp for safestrap or other testing please share to save me some time.
I dealt with this same scenario on a HTC Desire 526 that was bootloader locked by verizon.
I did develop a unlock method using this same process i am using now.
So no......This is not a JOKE.
I am making progress on unlocking the note 8 USA Variety. :victory:
Help me out and share your TWRP.
HI, I have a SM-N950U and I'm on Verizon,
My Baseband is:
N950USQU1AQI5
What would you like someone to do for you?
Htc is different then samsung....samsung has checks on every partition in the device if it detects something the phone will not boot ha
pbedard said:
Htc is different then samsung....samsung has checks on every partition in the device if it detects something the phone will not boot ha
Click to expand...
Click to collapse
Bigcountry has been doing all the necessary research which involves how the partitions interact with each other. He is really close to officially unlocking the boot loader apparently. We all are aware of how strict Samsung is but there seems to be a small window of opportunity that WILL enable a true bootloader unlocking method.
JedidroidX said:
Bigcountry has been doing all the necessary research which involves how the partitions interact with each other. He is really close to officially unlocking the boot loader apparently. We all are aware of how strict Samsung is but there seems to be a small window of opportunity that WILL enable a true bootloader unlocking method.
Click to expand...
Click to collapse
ºȯº could it be?
Wow really this would be awesome. Cannot wait. Thanks for the hard work.
I really hope this works
Interesting
I am still making progress on this. I took a step back to make sure I can unbrick my device when I screw something up.
Currently I am working on the unbrick for the V2 bootloader.
Someone got the firehose for the s-8 and s-8 + versions and some people have had luck unbricking s8 and s8+.
I have to rebuild the s8 unbrick rom for the note 8.
This involves getting the GPT tables off the device then decoding the GPT to write the partition.xml. Since we have ufs memory there are 4 primary partitions which means there are 8 GPT tables.
Once I have this all completed we can flash anything we want with the firehose. Even single partitions.
What I was asking for was TWRP that is Built for the Note 8.
So I can see if I can get it to boot.
This would save me from building TWRP myself and leave me more time to work on other stuff.
My Note 8 is currently on V2 bootloader.
We will need a unbrick rom for each bootloader version.
In order for me to make that I will need the GPT tables from each bootloader version. I can provide the commands to do it. Anyone wanting to help just let me know. I will be starting a new thread of how to do this soon.
BigCountry907 said:
I am still making progress on this. I took a step back to make sure I can unbrick my device when I screw something up.
Currently I am working on the unbrick for the V2 bootloader.
Someone got the firehose for the s-8 and s-8 + versions and some people have had luck unbricking s8 and s8+.
I have to rebuild the s8 unbrick rom for the note 8.
This involves getting the GPT tables off the device then decoding the GPT to write the partition.xml. Since we have ufs memory there are 4 primary partitions which means there are 8 GPT tables.
Once I have this all completed we can flash anything we want with the firehose. Even single partitions.
What I was asking for was TWRP that is Built for the Note 8.
So I can see if I can get it to boot.
This would save me from building TWRP myself and leave me more time to work on other stuff.
My Note 8 is currently on V2 bootloader.
We will need a unbrick rom for each bootloader version.
In order for me to make that I will need the GPT tables from each bootloader version. I can provide the commands to do it. Anyone wanting to help just let me know. I will be starting a new thread of how to do this soon.
Click to expand...
Click to collapse
I have a V3. I also am currently learning some arm assembly this semester, so I might be of some (minor) use. Note sure what my schedule will allow, but I will definitley assist how I can.
BigCountry907 said:
I am still making progress on this. I took a step back to make sure I can unbrick my device when I screw something up.
Currently I am working on the unbrick for the V2 bootloader.
Someone got the firehose for the s-8 and s-8 + versions and some people have had luck unbricking s8 and s8+.
I have to rebuild the s8 unbrick rom for the note 8.
This involves getting the GPT tables off the device then decoding the GPT to write the partition.xml. Since we have ufs memory there are 4 primary partitions which means there are 8 GPT tables.
Once I have this all completed we can flash anything we want with the firehose. Even single partitions.
What I was asking for was TWRP that is Built for the Note 8.
So I can see if I can get it to boot.
This would save me from building TWRP myself and leave me more time to work on other stuff.
My Note 8 is currently on V2 bootloader.
We will need a unbrick rom for each bootloader version.
In order for me to make that I will need the GPT tables from each bootloader version. I can provide the commands to do it. Anyone wanting to help just let me know. I will be starting a new thread of how to do this soon.
Click to expand...
Click to collapse
I'm on bootloader 5. I'll be glad to help ya out with what you need.
BigCountry907 said:
I am still making progress on this. I took a step back to make sure I can unbrick my device when I screw something up.
Currently I am working on the unbrick for the V2 bootloader.
Someone got the firehose for the s-8 and s-8 + versions and some people have had luck unbricking s8 and s8+.
I have to rebuild the s8 unbrick rom for the note 8.
This involves getting the GPT tables off the device then decoding the GPT to write the partition.xml. Since we have ufs memory there are 4 primary partitions which means there are 8 GPT tables.
Once I have this all completed we can flash anything we want with the firehose. Even single partitions.
What I was asking for was TWRP that is Built for the Note 8.
So I can see if I can get it to boot.
This would save me from building TWRP myself and leave me more time to work on other stuff.
My Note 8 is currently on V2 bootloader.
We will need a unbrick rom for each bootloader version.
In order for me to make that I will need the GPT tables from each bootloader version. I can provide the commands to do it. Anyone wanting to help just let me know. I will be starting a new thread of how to do this soon.
Click to expand...
Click to collapse
I'm on v3 bootloader...if you need anything I will try my best to help you out and see if we can get this phone unlocked
I'm interested and will get note 8 for this work. Is there any particular bl you'd prefer like rev1 and or 3 or just rev 2. Also I have a Samsung edl tool to aid the firehose process. Now that I think of it I already have firehose Rev2 from when I bricked out on SD.
---------- Post added at 06:10 PM ---------- Previous post was at 06:01 PM ----------
Also what sort of programming knowledge can help you if you don't mind me asking
Vell123 said:
I'm interested and will get note 8 for this work. Is there any particular bl you'd prefer like rev1 and or 3 or just rev 2. Also I have a Samsung edl tool to aid the firehose process. Now that I think of it I already have firehose Rev2 from when I bricked out on SD.
---------- Post added at 06:10 PM ---------- Previous post was at 06:01 PM ----------
Also what sort of programming knowledge can help you if you don't mind me asking
Click to expand...
Click to collapse
Currently I am working on Rev 2. bootloader.
You guys that have other Revisions Can help us all out by getting GPT backups from your devices. Then I can Compare the GPT for differences.
I currently have the UNBRICK for bootloader version 2.
Anyone with a HARD Bricked device that is on samfail V2 possibly samfail V2..5 or the factory AQK2 or the AQK2 factory repair should test this unbrick. I am sure it will work.
If other versions of the bootloader have the same gpt then we can take the bootloaders out of the stock firmware and swap them with the files in the unbrick and it should work. If the gpt is different then new GPT files will need made for the other bootloaders.
@Vell123;77796726
Which Box do you have?
You mention SD / does the sdcard method still work.
Do you put the sdcard into the device to boot download mode?
If that is the case we can run full android off the sd card potentially.
I would love to have a copy of the card if you can dd and image that would be great.
I have been thinking about buying the medusabox pro. It supports firehose and these phone models.
I don't know what box is best but whatever it is i want to buy one.
As far as bootloader unlocking I noticed after the GPT on the beginning of dev/block/sda there is a pretty decent chunk of data that is not the GPT or the PIT and may be a place for us to look into. Its basically a hidden spot in the emmc that samsung is not normaly written to.
@kronickhigh
If you can re-base and disassemble the abl.img that could lead us down the right road. You may be able to locate where the security checks are executed. If you can locate those it could be possible to determine the memory addresses where this data is stored.
I'm going to start a new thread on GPT and I will post there the commands to pull the GPT and what were looking at.
I am also going to start a new thread for the unbrick files.
@Vell123;77796726
If you can share the sdcard image you have that would be superb.
For now here is the v2 unbrick tor the N950U
Which Box do you have? I have the z3x box however i also have a edl repair cable/tool.
You mention SD / does the sdcard method still work.
Do you put the sdcard into the device to boot download mode? I don't have a SD card version. I was told by Me21( that made Samfail ) it wouldn't work so i didn't mind working on anything. However it might work. When i said SD i was referring to Snapdragon processors.
If that is the case we can run full android off the sd card potentially.
I would love to have a copy of the card if you can dd and image that would be great.
I have been thinking about buying the medusabox pro. It supports firehose and these phone models.
I don't know what box is best but whatever it is i want to buy one.
I'm sure your may already know the boxes use AT+COMMANDS but the most support is the best!
As far as bootloader unlocking I noticed after the GPT on the beginning of dev/block/sda there is a pretty decent chunk of data that is not the GPT or the PIT and may be a place for us to look into. Its basically a hidden spot in the emmc that samsung is not normaly written to.
@kronickhigh
If you can re-base and disassemble the abl.img that could lead us down the right road. You may be able to locate where the security checks are executed. If you can locate those it could be possible to determine the memory addresses where this data is stored.
I'm going to start a new thread on GPT and I will post there the commands to pull the GPT and what were looking at.
I am also going to start a new thread for the unbrick files. @Vell123;77796726
If you can share the sdcard image you have that would be superb.
For now here is the v2 unbrick tor the N950U[/QUOTE]
Rip note 8
What Happened
pbedard said:
Rip note 8
Click to expand...
Click to collapse
What happened to your note 8.
The unbrick files are legitimate Samsung Leaked files.
If you are on bootloader rev 2 you should be able to unbrick it.
You need to load the qualcomm edl drivers.
If you are on a different bootloader version we can try to make a unbrick for you.
Also depending on what you were doing.
You may have got the device stuck in sahara mode or something.
I once thought i bricked mine.
It was deader than dead. Only showed up as unrecognized device.
I left it that way overnight until the battery fully died.
Then when i plugged it in the next day it came back to life.
Unless you physically damaged the note 8 it can be recovered. Sooner or later.
Sooner if you are on rev 2
So as this thread first asked.
Who has a halFway decent tree for me to build TWRP.
I going to need it pretty soon.
Were about there. I gotta get me a 64gb sd card tonight and finish up a little more work on my gpt decoder.
Looking at the strings in the elf files I can see that the option to boot from sd card is in there.
Other than that I need to create sparse chunk images of partitions like /system and /data and /persist.
All the big boys gotta get sparsed out to chunks small enough for edl flashing.
I have a very special set of bootloaders and I'm thinking this set will be able to be unlocked.
What needs done is building a complete edl flash using these bootloaders and the standard U2 version /system and other images needed to complete the flash. If this all works as I anticipate it will be RIP Locked Bootloader.
I am on rev 3 i fixed my bricked device myself with a friends help
BigCountry907 said:
So as this thread first asked.
Who has a halFway decent tree for me to build TWRP.
I going to need it pretty soon.
Were about there. I gotta get me a 64gb sd card tonight and finish up a little more work on my gpt decoder.
Looking at the strings in the elf files I can see that the option to boot from sd card is in there.
Other than that I need to create sparse chunk images of partitions like /system and /data and /persist.
All the big boys gotta get sparsed out to chunks small enough for edl flashing.
I have a very special set of bootloaders and I'm thinking this set will be able to be unlocked.
What needs done is building a complete edl flash using these bootloaders and the standard U2 version /system and other images needed to complete the flash. If this all works as I anticipate it will be RIP Locked Bootloader.
Click to expand...
Click to collapse
Fingers crossed and good luck!
Looking to start a discussion on rooting the unlocked version.
I have tried the root for other variants for this phone and does not work
hi would love to see my k8+ rooted. i have the lmx210ulma version mtk and android 7.1.2.
There are recoveries for this phone and i have a full partition dump i nade today using salt on my ubuntu 18.04 machine. when i say full i mean something like 30-50 .img files pulled.
Any way. The problem on my end is booting into fastboot mode or rebooting to the bootloader. i have tried ADB, recovery and key combinations with out ever getting there. I can however get the phone to download into recovery download mode just fine.
any help would be appreciated
https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
Duhjoker said:
hi would love to see my k8+ rooted. i have the lmx210ulma version mtk and android 7.1.2.
There are recoveries for this phone and i have a full partition dump i nade today using salt on my ubuntu 18.04 machine. when i say full i mean something like 30-50 .img files pulled.
Any way. The problem on my end is booting into fastboot mode or rebooting to the bootloader. i have tried ADB, recovery and key combinations with out ever getting there. I can however get the phone to download into recovery download mode just fine.
any help would be appreciated
Click to expand...
Click to collapse
We are now in this forum. Why some dork mod moves these too early?
Why here, why not to the K8 forums instead?
The link I posted should work with your device...
Just got told to go to the k8 forums because im really just trying to get the bootloader unlocked. Temp root is nice but my plans involve a recovery and a fully rooted phone. Im trhing to develop a way to compile apps and operating systems completely on the device but i need full access.
Im looking for firmware for LG K8 2018 X210ULMG. Where can i find it ?
go to google and type in "LG K8 + LMX210ULM stock rom" you will get at least five pages or more.
Duhjoker said:
go to google and type in "LG K8 + LMX210ULM stock rom" you will get at least five pages or more.
Click to expand...
Click to collapse
I can't fin anywhere for X210ULMG. Try and when you will find paste here link because anywhere is this rom.
which android version do y0u have 9n your k8. I also need you to go to settings system software info and tell me the software versiion. And just for SandG no seriously, open up a terminal in terminal emulator and type getprop. im looking fir the value of
ro.lge.swversion_arb
to be of further assistance may i ask what exactly you are using it for? ie reflash stock fix brick or other. i can help you with the best plan of action and any other how to.
If you are still out there the ULMG and ULM are the same device. There is no ULMG stock rom. So you will need to flash your K8+ using the ULM firmware. If you are looking to roll back to get to the bootloader the lowest version you can find is a letter F version. None so far have an ARB value so happy flashing.
I myself own this device and its an easily rootable phone with bootloader unlock. Just flash the kdz with the lowest letter value then adb reboot bootloader and then in fastboot mode use fastboot oem unlock and your free to flash any cv1 device twrp recovery.img to the phone.
Just make sure to use either carliv image kitchen or android image studio to check and make sure that system, syatem.img, are both ext4 in recovery.fstab. System.img will probably be labled emmc which will cause failure to mount. Also cache and data as well. Firmware/modem should be labled as vfat. Just as if they were labled if you looked at original fstab.
To root just extract boot.img from kdz and patch using magisk and flash using fastboot flash boot boit.img then fastboot flash recovery recovery.img When booting into twrp first time flash no verity opt encrypt and make backup. Upon exiting make sure all parts are mounted or twrp loop will occur.
Duhjoker said:
If you are still out there the ULMG and ULM are the same device. There is no ULMG stock rom. So you will need to flash your K8+ using the ULM firmware. If you are looking to roll back to get to the bootloader the lowest version you can find is a letter F version. None so far have an ARB value so happy flashing.
I myself own this device and its an easily rootable phone with bootloader unlock. Just flash the kdz with the lowest letter value then adb reboot bootloader and then in fastboot mode use fastboot oem unlock and your free to flash any cv1 device twrp recovery.img to the phone.
Just make sure to use either carliv image kitchen or android image studio to check and make sure that system, syatem.img, are both ext4 in recovery.fstab. System.img will probably be labled emmc which will cause failure to mount. Also cache and data as well. Firmware/modem should be labled as vfat. Just as if they were labled if you looked at original fstab.
To root just extract boot.img from kdz and patch using magisk and flash using fastboot flash boot boit.img then fastboot flash recovery recovery.img When booting into twrp first time flash no verity opt encrypt and make backup. Upon exiting make sure all parts are mounted or twrp loop will occur.
Click to expand...
Click to collapse
I have problem because one month ago I flashed My K8 ULMG with kdz for Aristo 2 . I downloaded the software from Aristo 2 and made Brick through it.
Now it doesn't turn on, gives no sign of life, nothing. When connected to a laptop, the computer can only see Qualcomm HS-USB QDLoader 9008.
Do you know solution for it ?
There are two versions of the k8+ a qualcomm version and an mtk version. Did you read my post after your last reply. I was trying to help you determine that sort 0f thing.
As for a fix.... no as of currently there is no fix for either the qc or mtk versions once bricked. i am working on possible solutions but those are not going to be any time soon.
Your best bet at this point is to look for a used and damaged phone and replace the board in your phone with a different board. Find a k8+ lm-x210ulm or an aristo 2 board. They are cheap around $20 us and can be found with broken screens. They have no arb values so can be flashed and downgraded to get the boot loader unlocked and reflashed and upgraded after with guidance.
Dont feel to bad it happens. I have 4 boards that are trash but im still gonna try to unbrick them. But please what ever you do dont do it with out guidance. pm if you need and ill help.
Duhjoker said:
There are two versions of the k8+ a qualcomm version and an mtk version. Did you read my post after your last reply. I was trying to help you determine that sort 0f thing.
As for a fix.... no as of currently there is no fix for either the qc or mtk versions once bricked. i am working on possible solutions but those are not going to be any time soon.
Your best bet at this point is to look for a used and damaged phone and replace the board in your phone with a different board. Find a k8+ lm-x210ulm or an aristo 2 board. They are cheap around $20 us and can be found with broken screens. They have no arb values so can be flashed and downgraded to get the boot loader unlocked and reflashed and upgraded after with guidance.
Dont feel to bad it happens. I have 4 boards that are trash but im still gonna try to unbrick them. But please what ever you do dont do it with out guidance. pm if you need and ill help.
Click to expand...
Click to collapse
Did you found some method for unbrick this phone without motherboard change ?
As the title implies , this thread will contain g8x att firmware backs ups for people to use, since we don't have kdz for our version of the g8x, these backups will hopefully help people recover phones.
If you have a backup please pm me or post it here and i will add it to the main OP. Also an easy way to dump your firmware is to use Partition Backup
If you do decide to dump your firmware, only backup slot partitions, mostly only those can be shared. Most others are device unique. (you need Bl unlock and root to dump them with this app, with firehose/qpst you dont.)
Only restore this on a Android 10 slot
Also this vendor parttion is decrypted keep this in mind while restoring it.
Firmware List:
ATT G8X 20e Android 10 (Security patch April 1st 2020)
"People cant have nice things =/. look for me on the blue old app"
If you have issues downloading let me know.
Do you have a AT&T LG G8 Android 10 dump?
Also, how would one go about using the Android 10 dump on their LG G8? (Basically how do you install it?)
wwechampian said:
Do you have a AT&T LG G8 Android 10 dump?
Also, how would one go about using the Android 10 dump on their LG G8? (Basically how do you install it?)
Click to expand...
Click to collapse
Not for att g8, i only have a g8 from sprint, im not sure how you would go about using this to upgrade from 9 to 10, i think it has to be flashed on secondary slot. i would go to the lg v50 telegram group and ask there, so you can be sure 100%
so i can only do this if i have root access on my lg g8x from at & t?
siulmagic said:
ATT G8X 20e Android 10 (Security patch April 1st 2020)
att-20e-firmware-backup-slot.7z
drive.google.com
If you have issues downloading let me know.
Click to expand...
Click to collapse
Forgive my ignorance but how does one go about using this backup to restore a bricked G8X...?
Need a step-by-step primer on this if anyone would be kind enough to teach, as I'm only familiar with KDZ's and using LGUP 1.14 Dev Mode for older LG devices...the G8X will not function with this version, so it's not straightforward
Thanks in advance
HanselCustodio said:
so i can only do this if i have root access on my lg g8x from at & t?
Click to expand...
Click to collapse
no, you can use it without root(use firehose/qpst), though my vendor is decrypted no idea how that will affect it.
siulmagic said:
ATT G8X 20e Android 10 (Security patch April 1st 2020)
att-20e-firmware-backup-slot.7z
drive.google.com
If you have issues downloading let me know.
Click to expand...
Click to collapse
Just want to offer a warning to anything thinking about using the above referenced backup - I used it myself on a soft bricked G8X (AT&T) using QFIL on EDL/9008 mode to upload the unpacked IMG's. I went from soft brick to hard brick.
When I first started off using this I uploaded only the system, boot and abl...when I started seeing a fastboot screen (which I hadn't seen since) I felt like I was moving in the right direction so I uploaded the remaining partitions. After exiting EDL the device refuses to turn on...no LG splash, no android warning, no longer any access to download mode. No amount of button pushing brings EDL mode back while connected via USB. Doesn't charge using wireless charger (which it used to before).
I'm very confident I did not mismatch any partitions, though uploading the OP image did mention that there was data overflow and asked me if I wanted to continue. Further, this backup did not contain all of the img's that would ordinarily be present in a KDZ, but contained imgs that a standard KDZ do not have.
Since I can't get to EDL I can't restore the backups I had made of it's previous soft-bricked state.
It's just really frustrating, and I've learned my lesson never to buy a device from a carrier that doesn't allow access to it's KDZ firmware file (or cannot be crossflashed to one that does).
Your mileage may vary of course but I definitely feel like I'd want to stop someone from trying the attached if they're still in a soft-bricked state.
As an aside I would appreciate anyone who might have any ideas of how to reach EDL mode again. Thanks
cliffswallow said:
Just want to offer a warning to anything thinking about using the above referenced backup - I used it myself on a soft bricked G8X (AT&T) using QFIL on EDL/9008 mode to upload the unpacked IMG's. I went from soft brick to hard brick.
When I first started off using this I uploaded only the system, boot and abl...when I started seeing a fastboot screen (which I hadn't seen since) I felt like I was moving in the right direction so I uploaded the remaining partitions. After exiting EDL the device refuses to turn on...no LG splash, no android warning, no longer any access to download mode. No amount of button pushing brings EDL mode back while connected via USB. Doesn't charge using wireless charger (which it used to before).
I'm very confident I did not mismatch any partitions, though uploading the OP image did mention that there was data overflow and asked me if I wanted to continue. Further, this backup did not contain all of the img's that would ordinarily be present in a KDZ, but contained imgs that a standard KDZ do not have.
Since I can't get to EDL I can't restore the backups I had made of it's previous soft-bricked state.
It's just really frustrating, and I've learned my lesson never to buy a device from a carrier that doesn't allow access to it's KDZ firmware file (or cannot be crossflashed to one that does).
Your mileage may vary of course but I definitely feel like I'd want to stop someone from trying the attached if they're still in a soft-bricked state.
As an aside I would appreciate anyone who might have any ideas of how to reach EDL mode again. Thanks
Click to expand...
Click to collapse
You will have to open the back and short some contacts.
Or give to service center if in warranty.
[QUOTE = "lefttobleed, publicación: 84319395, miembro: 2516025"]
Tendrás que abrir la parte trasera y cortar algunos contactos.
O entréguelo al centro de servicio si está en garantía.
[/CITAR]
Lo hiciste ??
Can anyone dump they're .xml partition data file? I am very desperate as my devices partitions are missing. Please help! Cheers!
cliffswallow said:
Just want to offer a warning to anything thinking about using the above referenced backup - I used it myself on a soft bricked G8X (AT&T) using QFIL on EDL/9008 mode to upload the unpacked IMG's. I went from soft brick to hard brick.
When I first started off using this I uploaded only the system, boot and abl...when I started seeing a fastboot screen (which I hadn't seen since) I felt like I was moving in the right direction so I uploaded the remaining partitions. After exiting EDL the device refuses to turn on...no LG splash, no android warning, no longer any access to download mode. No amount of button pushing brings EDL mode back while connected via USB. Doesn't charge using wireless charger (which it used to before).
I'm very confident I did not mismatch any partitions, though uploading the OP image did mention that there was data overflow and asked me if I wanted to continue. Further, this backup did not contain all of the img's that would ordinarily be present in a KDZ, but contained imgs that a standard KDZ do not have.
Since I can't get to EDL I can't restore the backups I had made of it's previous soft-bricked state.
It's just really frustrating, and I've learned my lesson never to buy a device from a carrier that doesn't allow access to it's KDZ firmware file (or cannot be crossflashed to one that does).
Your mileage may vary of course but I definitely feel like I'd want to stop someone from trying the attached if they're still in a soft-bricked state.
As an aside I would appreciate anyone who might have any ideas of how to reach EDL mode again. Thanks
Click to expand...
Click to collapse
This should only be used mostly to restore certain parttion, not the whole backup in one go, as you said this is not a kdz. Also messing with op partition is never recommended, edl did warn you of the parttion size mismatch. Also depends what you had on your primary slot, i would not recommend flashing this on a pie slot. Sucks that you hard bricked.
Need dump full G8X ATT, thank all, I need all partitions except the userdata partition, please help me, thanks
Hey guys, I'm really needing firmware to G850UM10F AT&T. Any one sees this variant come across their screen on a Telegram group or in their searches let me know please.
#Rooty_Mikes# said:
Hey guys, I'm really needing firmware to G850UM10F AT&T. Any one sees this variant come across their screen on a Telegram group or in their searches let me know please.
Click to expand...
Click to collapse
did you find one? I'm looking for a firmware in android 9 for at&t
siulmagic said:
As the title implies , this thread will contain g8x att firmware backs ups for people to use, since we don't have kdz for our version of the g8x, these backups will hopefully help people recover phones.
If you have a backup please pm me or post it here and i will add it to the main OP. Also an easy way to dump your firmware is to use Partition Backup
If you do decide to dump your firmware, only backup slot partitions, mostly only those can be shared. Most others are device unique. (you need Bl unlock and root to dump them with this app, with firehose/qpst you dont.)
Only restore this on a Android 10 slot
Also this vendor parttion is decrypted keep this in mind while restoring it.
Firmware List:
ATT G8X 20e Android 10 (Security patch April 1st 2020)
att-20e-firmware-backup-slot.7z
drive.google.com
If you have issues downloading let me know.
Click to expand...
Click to collapse
Can you unblock bootleader g8x att android 9?
Duythiem said:
Can you unblock bootleader g8x att android 9?
Click to expand...
Click to collapse
I believe to unlock bootloader for any variant you have to be on 10.
conbak49 said:
I believe to unlock bootloader for any variant you have to be on 10.
Click to expand...
Click to collapse
However, i don't have firmware android 10, because i live outside the USA....
Duythiem said:
However, i don't have firmware android 10, because i live outside the USA....
Click to expand...
Click to collapse
Only thing I know to suggest is ask in this thread: https://forum.xda-developers.com/t/...nlock-and-magisk-root-using-firehose.4221793/
i was able to unlock the bootloader on android 9
yoctan1 said:
did you find one? I'm looking for a firmware in android 9 for at&t
Click to expand...
Click to collapse
I might still have a copy on my drive if you still need it