Related
Hello I am trying to flash the factory image on to my Nexus 5 with the flash all option in the zip file and it keep going missing boot.img as seen in the picture and I am unsure what to do at this point cause I disconnect my phone and it does boot up in to android 4.4.4 but I need help here
hell I would let some one remote connect if that helps any lol
Buckii said:
Hello I am trying to flash the factory image on to my Nexus 5 with the flash all option in the zip file and it keep going missing boot.img as seen in the picture and I am unsure what to do at this point cause I disconnect my phone and it does boot up in to android 4.4.4 but I need help here
hell I would let some one remote connect if that helps any lol
Click to expand...
Click to collapse
1) "Stuck" is NOT a question. Please use descriptive thread titles
2) You haven't unzipped the image-hammerheadxxx.zip that contains the images :/
but I have I followed the instructions to a T and put all file in the folder under platform tools
Buckii said:
but I have I followed the instructions to a T and put all file in the folder under platform tools
Click to expand...
Click to collapse
Not sure what instructions you've followed. Either they're incomplete or you made a mistake. Like I said, your screenshot shows a zip file. You need to unzip that in the location that it is in now
picture
rootSU said:
Not sure what instructions you've followed. Either they're incomplete or you made a mistake. Like I said, your screenshot shows a zip file. You need to unzip that in the location that it is in now
Click to expand...
Click to collapse
This is now what I have done you were right but still missing boot.img
Buckii said:
This is now what I have done you were right but still missing boot.img
Click to expand...
Click to collapse
Just fastboot flash it then.
Link to guides in my signature.
I have similar issues. Mine complains that the archive doesn't contain boot.sig and recovery.sig, and then it fails to allocate space and the update package missing system.img.
Going to do it manually now to see if it works
Desca said:
I have similar issues. Mine complains that the archive doesn't contain boot.sig and recovery.sig, and then it fails to allocate space and the update package missing system.img.
Going to do it manually now to see if it works
Click to expand...
Click to collapse
Mine shows same as you, but just reboot and it is working
With all the random qhsusb_bulk hardbricks coming around, I've decided to create a thread to share debrick.img files just in case. You do not need to create this, but if you ever need it, you'll be glad you did.
EXPLANATION:
If you ever HARDBRICK your phone, which can be caused by flashing an incompatible ROM, bad bootloader flash, or anything, your processor will fallback into a mode called USB_BULK mode. In this mode, it will await an SD card with a special image flashed to it, called debrick.img, and boot to that. Once booted from the SDcard, it will await a firmware flash from a computer (download mode.)
However, this image needs to be specific to the bootloader version the phone was running before the hardbrick occured. That's why I've created this thread: people on different bootloaders can share their debrick images.
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
HOW TO USE ONE:
If you ever have the unfortunate luck of needing to use a debrick image, here's what to do:
-Download Win32DiskImager
-Put your microsd into your PC (yes you will need an adapter in some cases)
-Use Win32DiskImager to write the debrick.img to the SD card
-Take battery out of phone
-Put the SDcard into the phone and put the battery back in
-Do Vol Dn+Power+Home
-Your device should boot into Download Mode, and you should see "SDCARD MODE" at the top right
-Flash stock firmware using Odin
Downloads will be added to the 2nd post
Downloads
PB1 BOOTLOADER DEBRICK
PD1 BOOTLOADER DEBRICK (thanks @klabit87)
PLEASE SHARE YOUR OWN DEBRICK IMAGES! I WILL ADD THEM HERE
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
al50 said:
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
Click to expand...
Click to collapse
It is completely based on bootloader version. You can use "Phone Info - Samsung" to confirm before creating an image.
This is great would be nice if you could create Bod5 img for us who are still able to downgrade
Sent from my SM-G900V using Tapatalk
When I get a chance I'll make one for the OC4. Just want to be sure to do it correctly. Since I'm on UL OC4 Bootloader, PB1 firmware
Nandr0idC0nsumer said:
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card
Click to expand...
Click to collapse
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
ben_pr said:
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
Click to expand...
Click to collapse
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
[email protected] said:
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
200mb is all thats needed on sd.
Only for samsung devices.
Nandr0idC0nsumer said:
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
Click to expand...
Click to collapse
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
ben_pr said:
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
Click to expand...
Click to collapse
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Nandr0idC0nsumer said:
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Click to expand...
Click to collapse
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
Nandr0idC0nsumer said:
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
Click to expand...
Click to collapse
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
ben_pr said:
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
Click to expand...
Click to collapse
Good point. I will update the OP later. This is not my package btw
Nandr0idC0nsumer said:
Good point. I will update the OP later. This is not my package btw
Click to expand...
Click to collapse
My mistake; I thought you made the zip!
Nandr0idC0nsumer said:
200mb is all thats needed on sd.
Only for samsung devices.
Click to expand...
Click to collapse
Thanks
Sent from my SM-G900V using XDA-Developers mobile app
ben_pr said:
My mistake; I thought you made the zip!
Click to expand...
Click to collapse
Lol nope. Usually I like to have it all in the updater-script so I wouldn't have had a seperate script
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
akaplo said:
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
Click to expand...
Click to collapse
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Nandr0idC0nsumer said:
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Click to expand...
Click to collapse
See my thread. http://forum.xda-developers.com/showpost.php?p=67159556&postcount=14
So I just got the Aristo 3 and wanted to root it. after an extensive search I have come up empty. Does anyone know if there is a method available to use yet or maybe something is in the works? I've unlocked flashing but I cant seem to boot recovery. Any help would be greatly appreciated.
Same ive spent about 6 hours researching this ive never built my own root before however i just dont have the time to do whats needed. From what i researched get the original boot rom from lg bridge and perform a restore to download the factory boot image then use magisk to rebuild the image
Nvitethedark said:
Same ive spent about 6 hours researching this ive never built my own root before however i just dont have the time to do whats needed. From what i researched get the original boot rom from lg bridge and perform a restore to download the factory boot image then use magisk to rebuild the image
Click to expand...
Click to collapse
Hmm I'll give it a try. The phone is still new enough that I don't have much saved to it and if I brick it can take it back
should be able to just get the boot image may be the aristo 2 dev would pick this up since he's familiar with it I see you have a few posts in that forum maybe you can send that dev a message see if they would pick it up.
I eagerly await any progress in this run! My girlfriend cracked her screen on her Aristo 2 and decided that it was time to upgrade. I've never been disappointed in the idea of upgrading my phone...until it meant giving up my Aristoboy Mk.2(which was/is quite formidable)and rooted status along with it. If there is anything I might read about the process online, I would at very least consider the task myself. I am learning, but I have some decent skills and experience behind me. Please let me know if I can assist in any way. If not, I hope to see the first strides towards tackling this latest addition to the Aristo line!
My thanks to all my fellow devs here! You each make up a piece of the whole collection that make this, hands down the best forum/online community available the world over! Keep it up! We are making a difference in so many lives!
Your friend,
~[ProTech]~
So I've been busy as **** lately, but I found that the issue seems to be with the os more than the phone itself. I'm not that proficient with downgrading the os to a earlier version since this phone came stock with Oreo. I will try and talk to some of the devs who did the aristo 2 x210ma. Hopefully they have a solution. I've been using my 2 instead. I never realized how much you can't do with a stock phone and os.
OK here's something you can try...
first get dev-patched LGup {GooGle It}
then use the Dump function of Lgup to dump All partitions from your fone...
look for boot_COM{some#here} and rename it to boot.img
put that file on your fones sdcard and install magisk manager app.
use magisk manager app to patch that boot.img file.
find the new file patched_boot.img whereever magisk put it on your sdcard...
move it to your desktop or a folder etc. on P.C
now try to flash it to your fone...
Code:
adb reboot bootloader
Code:
fastboot oem unlock
if that works your bootloader is now unlocked you'll have to reboot the fone once as it'll erase cache and data...
after that
again do
Code:
adb reboot bootloader
now try
Code:
fastboot flash boot patched_boot.img
if that works....
Code:
fastboot reboot
and you'll have root by magisk.
if fastboot's not working other option is to rename "patched_boot.img" to "boot.img"
and then use Partitions DL option in lgup to flash the "patched"boot.img to the phone...
if that works you'll have root by magisk...
If this helped you feel free to hit thanks and come back to post the results plz.
Thanks
LgPWN'd said:
OK here's something you can try...
first get dev-patched LGup {GooGle It}
then use the Dump function of Lgup to dump All partitions from your fone...
look for boot_COM{some#here} and rename it to boot.img
put that file on your fones sdcard and install magisk manager app.
use magisk manager app to patch that boot.img file.
find the new file patched_boot.img whereever magisk put it on your sdcard...
move it to your desktop or a folder etc. on P.C
now try to flash it to your fone...
Code:
adb reboot bootloader
Code:
fastboot oem unlock
if that works your bootloader is now unlocked you'll have to reboot the fone once as it'll erase cache and data...
after that
again do
Code:
adb reboot bootloader
now try
Code:
fastboot flash boot patched_boot.img
if that works....
Code:
fastboot reboot
and you'll have root by magisk.
if fastboot's not working other option is to rename "patched_boot.img" to "boot.img"
and then use Partitions DL option in lgup to flash the "patched"boot.img to the phone...
if that works you'll have root by magisk...
If this helped you feel free to hit thanks and come back to post the results plz.
Thanks
Click to expand...
Click to collapse
My bootloader is already unlocked I've just not been able to flash anything with fastboot. So I have LGup, is there a difference with the dev patched one? I also have magisk on my phone, but it really doesn't give me any options besides to install a new version. I'm gonna go try your suggestion soon though...it sounds promising...and may open up other options if this doesn't succeed. Thanks I'll keep you posted.
Reckless459 said:
My bootloader is already unlocked I've just not been able to flash anything with fastboot. So I have LGup, is there a difference with the dev patched one? I also have magisk on my phone, but it really doesn't give me any options besides to install a new version. I'm gonna go try your suggestion soon though...it sounds promising...and may open up other options if this doesn't succeed. Thanks I'll keep you posted.
Click to expand...
Click to collapse
PLease let us know how it go's...
I'm trying to port and compile Multi-rom for LG-aristo Lg-m210 at the moment...
So I have LGup, is there a difference with the dev patched one?
.
Click to expand...
Click to collapse
in answer to that YES quite a difference...
devpatched lgup gives you extra options such as Dump and Partitions-DL and Chiperase among others...
you'll NEED that dump and partitions-DL option....
LgPWN'd said:
PLease let us know how it go's...
I'm trying to port and compile Multi-rom for LG-aristo Lg-m210 at the moment...ll
Click to expand...
Click to collapse
So I can't get passed the dump. I keep getting a timed out error. I even tried to format the user data using fastboot and it failed. And I am curious about the boot_COM. I didn't see any file in the partition list matching that. I did see the boot partition and many others that I didn't recognize. So kinda feeling that we are back to
Reckless459 said:
So I can't get passed the dump. I keep getting a timed out error. I even tried to format the user data using fastboot and it failed. And I am curious about the boot_COM. I didn't see any file in the partition list matching that. I did see the boot partition and many others that I didn't recognize. So kinda feeling that we are back to
Click to expand...
Click to collapse
No the file wont say that in lgup, it'll be named that after you create a new folder on desktop call it "Dump" then use the dev-patched lgup and Dump option, select the folder Dump on the desktop and select the little checkbox for all on partitions list and click start...
also you may be haveing issues because of the .dll your useing... will lgup flash a stock .kdz to the device?
if yes, I'd think the dump option would work fine...
for firmware look here : https://www.mylgphones.com/metropcs-lg-aristo-3-lmx220ma-x220ma-firmware.html
for direct download use this link
Code:
http://pkg02.lime.gdms.lge.com/dn/downloader.dev?fileKey=FW88KEQ4C2VSAF0C3D54FH4/X220MA10e_00_MPCS_US_OP_0123.kdz
LgPWN'd said:
No the file wont say that in lgup, it'll be named that after you create a new folder on desktop call it "Dump" then use the dev-patched lgup and Dump option, select the folder Dump on the desktop and select the little checkbox for all on partitions list and click start...
also you may be haveing issues because of the .dll your useing... will lgup flash a stock .kdz to the device?
if yes, I'd think the dump option would work fine...
for firmware look here : https://www.mylgphones.com/metropcs-lg-aristo-3-lmx220ma-x220ma-firmware.html
for direct download use this link
Code:
http://pkg02.lime.gdms.lge.com/dn/downloader.dev?fileKey=FW88KEQ4C2VSAF0C3D54FH4/X220MA10e_00_MPCS_US_OP_0123.kdz
Click to expand...
Click to collapse
So yes it would load a stock formware but no it wouldn't allow me to dump even one partion. And the strange thing was that my list of options would chanhe sometimes. Like it would give me more options i.e. phonesettings. I even tried different cables and ports. It doesnt matter though i somehow hard bricked it so bad that it won't even. Boot to download mode and somehow fried my sim card to the point it wont work in any other phone. Im just waiting for metro to open so i can try again
Reckless459 said:
So yes it would load a stock formware but no it wouldn't allow me to dump even one partion. And the strange thing was that my list of options would chanhe sometimes. Like it would give me more options i.e. phonesettings. I even tried different cables and ports. It doesnt matter though i somehow hard bricked it so bad that it won't even. Boot to download mode and somehow fried my sim card to the point it wont work in any other phone. Im just waiting for metro to open so i can try again
Click to expand...
Click to collapse
OH WOW what a mess...
I would say it's the .dll in the LGUP causing pain here...
something you can try when you're ready to try again....
remove/uninstall devpatched LGUP and install regular store version
use the Common .dll
and add this file{ UI_Config.lgl } to your Common folder in the lgup install location ...
to make it easier I'll just zip up My common folder for you to replace yours
to do this
right click on lgup, select open file location...
navigate to the model subfolder you'll see things like
{ AllinOne } {Common} and {LGUP_LGNPST} folders...
at that point just right click and rename {Common} folder to {Commonbak},
then take my zip file I'm attaching and unzip it and inside will be Common folder...
just Copy / Paste that new Common folder to where the old one is..
set permissions of folder { read-only} and open the folder find file called { UI_Config.lgl }
and set it's permissions to READ ONLY . otherwise it'll be erased once you start LGUP.
and see If that changes anything with being able to Dump...
It's let me dump every LG i've plugged into it...
so I should think it should work for you too...
@Reckless459
is there nothing further?
LgPWN'd said:
@Reckless459
is there nothing further?
Click to expand...
Click to collapse
Dude...
First off let me say MertoPCS has the biggest pile of **** customer care department. I'm still waiting on my new device to comr from the warrenty department. I did however fix the sim issue (again metro sucks leaky bowels). I will definitely post any new developments as soon as the happen.
Oh also i did a dump on another phone (aristo 2) and had no issuses. And i saw what ypu meant with the boot_COM##. Thanks for the help.
LGUP dll
Sorry apparently i haven't reloaded this page in 12 hrs and their has been progressing i have 2 aristos im going to work on this also.
i will step in and help out ill read the updates and post further
---------- Post added at 09:43 PM ---------- Previous post was at 09:35 PM ----------
LgPWN'd said:
@Reckless459
is there nothing further?
Click to expand...
Click to collapse
I had a question i would like to chime in here, can i do an extraction on the KDZ with lg extractor i see a boot image in it and flash that?
Nvitethedark said:
Sorry apparently i haven't reloaded this page in 12 hrs and their has been progressing i have 2 aristos im going to work on this also.
i will step in and help out ill read the updates and post further
---------- Post added at 09:43 PM ---------- Previous post was at 09:35 PM ----------
I had a question i would like to chime in here, can i do an extraction on the KDZ with lg extractor i see a boot image in it and flash that?
Click to expand...
Click to collapse
it may work,
when lgup is being a pain it's worth a try.
I say go for it. but to be certain I'd try flashing the extracted boot.img with partitions DL option in lgup once to make sure it flashes it b4 trying to patch it and flash it again...
Just my 2 cents.
LgPWN'd said:
it may work,
when lgup is being a pain it's worth a try.
I say go for it. but to be certain I'd try flashing the extracted boot.img with partitions DL option in lgup once to make sure it flashes it b4 trying to patch it and flash it again...
Just my 2 cents.
Click to expand...
Click to collapse
Aristo3 FW: X220MA10B "10b" came on the system stock
LGUP V1.14 - patched
DLL v1.0.28.17
The above dll is the only one I have found that will recognize the phone and load LGUP, I have also attempted to use uppercut: Error DLL for X220M10b is invalid install a valid dll
https://imgur.com/1Ptrv3n
however, once i attempt to dump phone reboots into download mode i get: Error: 0x2000, please use latest Dll LAF protocol version is not match dll=0 device 162512928
https://imgur.com/5I7GfOa
I attempted to use the LGUPC DLL from the kdz V 10E firmware and that did not recognize the device i also attempted to use your zipped commons.
any feedback on this?
I feel that i should use LG tool update to 0F then use the 0F kdz to attempt all this?
DOWNGRADE Don't UPGRADE
Nvitethedark said:
Aristo3 FW: X220MA10B "10b" came on the system stock
LGUP V1.14 - patched
DLL v1.0.28.17
The above dll is the only one I have found that will recognize the phone and load LGUP, I have also attempted to use uppercut: Error DLL for X220M10b is invalid install a valid dll
https://imgur.com/1Ptrv3n
however, once i attempt to dump phone reboots into download mode i get: Error: 0x2000, please use latest Dll LAF protocol version is not match dll=0 device 162512928
https://imgur.com/5I7GfOa
I attempted to use the LGUPC DLL from the kdz V 10E firmware and that did not recognize the device i also attempted to use your zipped commons.
any feedback on this?
I feel that i should use LG tool update to 0F then use the 0F kdz to attempt all this?
Click to expand...
Click to collapse
If at all posible find the OLDEST firmware possible in kdz and do a full flash of that .
and try your dll mod with that by extracting the dll from said kdz and renaming to what ever the one in Common folder is and keep the UI_Config.lgl in there to keep the extra options if possible...
It's all trial and error with this stuff, so keep at it.
DO NOT flash a firmware.kdz from a different model of the device as it'll flash aboot sbl etc and you'll end with a brick that can't be fixed.
and I've always liked { in my experiments} to use the partitions DL option even when downgrading etc to be able to NOT CHOOSE the boot-stack partitions...
but give it a shot and tell us how it go's.
we may be able to split a root-bounty if we come up with something working across users
LgPWN'd said:
OH WOW what a mess...
I would say it's the .dll in the LGUP causing pain here...
something you can try when you're ready to try again....
remove/uninstall devpatched LGUP and install regular store version
use the Common .dll
and add this file{ UI_Config.lgl } to your Common folder in the lgup install location ...
to make it easier I'll just zip up My common folder for you to replace yours
to do this
right click on lgup, select open file location...
navigate to the model subfolder you'll see things like
{ AllinOne } {Common} and {LGUP_LGNPST} folders...
at that point just right click and rename {Common} folder to {Commonbak},
then take my zip file I'm attaching and unzip it and inside will be Common folder...
just Copy / Paste that new Common folder to where the old one is..
set permissions of folder { read-only} and open the folder find file called { UI_Config.lgl }
and set it's permissions to READ ONLY . otherwise it'll be erased once you start LGUP.
and see If that changes anything with being able to Dump...
It's let me dump every LG i've plugged into it...
so I should think it should work for you too...
Click to expand...
Click to collapse
reinstalled a non-patched version of lgup and used your common folder and set read-only options attempted a dump got this:
https://imgur.com/FJPMUwv
If you find anyway to fix a G7 Power hard brick please someone let me know my model is XT1955-5 (ocean) Amazon
I just bought the phone but now I can't use it anymore I have no access to the bootloader or recovery mode.
The phone plugged into the computer shows up as Qualcomm HS-USB Loader (9008)
I along with other users with the phone on XDA have tried using a mmcblk0.img but sadly it never worked if you find some other method please let someone know on this thread or make a post about it.
Thank you have a good day.
@sd_shadow
Do you think you could try this please and then upload the file?
I believe we have the same phone model the file shouldn't be very big someone uploaded one for the G7 and it was 165MB.
masonw1999 said:
@sd_shadow
Do you think you could try this please and then upload the file?
I believe we have the same phone model the file shouldn't be very big someone uploaded one for the G7 and it was 165MB.
Click to expand...
Click to collapse
The instructions you posted pull a 16gb file.
The G7 Power is a 32gb device.
I've pulled an mmcblk0.img 3 times, using the twrp method.
Not sure what happened the 1st time, the 2nd and 3rd md5 checksums matched.
I couldn't get the sd card method to work, tried several times.
sd_shadow said:
The instructions you posted pull a 16gb file.
The G7 Power is a 32gb device.
I've pulled an mmcblk0.img 3 times, using the twrp method.
Not sure what happened the 1st time, the 2nd and 3rd md5 checksums matched.
I couldn't get the sd card method to work, tried several times.
Click to expand...
Click to collapse
I would pull it using Linux (not a virtual machine) directly to your hard drive as apposed to using twrp to pull it to an sd card
masonw1999 said:
@sd_shadow
Do you think you could try this please and then upload the file?
I believe we have the same phone model the file shouldn't be very big someone uploaded one for the G7 and it was 165MB.
Click to expand...
Click to collapse
Try this
165mb file
https://mega.nz/#!uOpw3AYI!rDXW5rN9LQ4E7mWglOo-HQZY1AWG5914Jp75ijyY1Fo
edit:
some details
if you use
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
file is saved to internal staorage
command needs to to changed
I used
Code:
dd if=/dev/block/mmcblk0 of=/storage/16F4-E1F2/Loader.img bs=1024 count=168960
but this will be different on every device.
I just used the stock files app to see the details of a file on the external storage to check location.
/storage/16F4-E1F2/
@sd_shadow
Thank you for doing that for me man appreciate it I think I'm just going to throw the phone in the garbage it didn't work.
)':
This blank flash unbricked my phone: https://mega.nz/#!5NtCia6a!epk2yLEqnQBKEwT2QbQaOe8-4675pfj76Hs7pC5kbQE
anyone know how to extract a boot.img file so I can use the contents on the inside in windows please
gigawatt said:
anyone know how to extract a boot.img file so I can use the contents on the inside in windows please
Click to expand...
Click to collapse
Boot.img is in the full firmware
https://mirrors.lolinet.com/firmware/moto
Sent from my mata using XDA Labs
hello does anyone have the blank flash for the february 2020 patch?
https://www.clansoft.net/dl/index.php?a=downloads&b=file&id=9858
hope has just come out, but you have to pay
Hi, i own an Oneplus 8 India Version.
As soon as i purchased the first thing I did was to take the persist.img backup as that seemed to be an important thing to do from my reading through the articles.
After a few months now, I seem to be in need of using this image and realized the image file is not accessible. from the articles and videos I read/seen, everyone is able to EXTRACT the image file using the 7zip or similar tools. However, i am unable to extract using any of the tools.
I took the latest persist.img from the already troubled device and that too is not working. 7zip says "Can not open the file ...."
command i used was this :
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
similarly, i manually copied the file using root file manager aad that too is giving the error
Please help
Fastboot flash persist persist.img
I believe that's how you would restore persist.
I could be very wrong. Proceed with caution and I'm not liable if you break it.
crazynapkinman said:
Fastboot flash persist persist.img
I believe that's how you would restore persist.
I could be very wrong. Proceed with caution and I'm not liable if you break it.
Click to expand...
Click to collapse
Hi thank you. The concern is related to the image not being extracted. From what i have read and seen in YouTube too is they are able to extract the img file. But my files are not readable.
firoz3321 said:
Hi thank you. The concern is related to the image not being extracted. From what i have read and seen in YouTube too is they are able to extract the img file. But my files are not readable.
Click to expand...
Click to collapse
Does anyone know if he can flash someone else's backed up persist.img?
crazynapkinman said:
Does anyone know if he can flash someone else's backed up persist.img?
Click to expand...
Click to collapse
There was a thread in this forum that mentioned the persist cannot be shared or doesn't work with others. Apparantly it contains sensor calibration data which usually will be unique.
Can someone confirm if your persist image is extractable with 7zip or similar. If so what am i doing wrong.
firoz3321 said:
There was a thread in this forum that mentioned the persist cannot be shared or doesn't work with others. Apparantly it contains sensor calibration data which usually will be unique.
Can someone confirm if your persist image is extractable with 7zip or similar. If so what am i doing wrong.
Click to expand...
Click to collapse
You need to be unlocked and rooted. Then you will reboot to fastboot. From there, BOOT twrp (fastboot boot twrp.img)
Once booted, use TWRP to backup persist.img
crazynapkinman said:
You need to be unlocked and rooted. Then you will reboot to fastboot. From there, BOOT twrp (fastboot boot twrp.img)
Once booted, use TWRP to backup persist.img
Click to expand...
Click to collapse
Using root explorer i copied the persist image but that too was un extractable. The persist image that i took backup using the command in OP when i bought the device also doesn't extract.
And one more thing is TWRP doesn't seem to be working with 11 OS yet.
firoz3321 said:
Using root explorer i copied the persist image but that too was un extractable. The persist image that i took backup using the command in OP when i bought the device also doesn't extract.
And one more thing is TWRP doesn't seem to be working with 11 OS yet.
Click to expand...
Click to collapse
Need to downgrade to 10.
I pulled my persist image off of 10.
---------- Post added at 07:20 PM ---------- Previous post was at 07:08 PM ----------
From what I've read there's not reason to unzip the persist.img
If you backed it up with a WORKING persist present, then you simply need to boot to fastboot and flash your persist.img
It will replace the corrupted partition and you're good to go. No one on any forum I read said they actually extracted anything from the persist.img file itself.
They all had to extract (see backup) the WORKING persist.img and flash that with fastboot command.
You can extract working persist.img with the following command in adb:
dd if=/dev/block/by-name/persist of=/sdcard/persist.img
This will save it to your sdcard. Transfer that backup to your adb folder on pc. Reboot into fastboot and use the following command to flash it:
fastboot flash persist persist.img
I do have working persist. There is a youtube video regarding same issue and ye extracted files from working persist. Your steps are clear and thank you for that .
My reason for asking was. If my files are corrupted i may damage more than solving. Hopefully the files i have are good.
firoz3321 said:
I do have working persist. There is a youtube video regarding same issue and ye extracted files from working persist. Your steps are clear and thank you for that .
My reason for asking was. If my files are corrupted i may damage more than solving. Hopefully the files i have are good.
Click to expand...
Click to collapse
Hopefully you're using the good backup you made and not something you downloaded...
GL!
crazynapkinman said:
Hopefully you're using the good backup you made and not something you downloaded...
GL!
Click to expand...
Click to collapse
Today i gave it to service.
Un rooted, locked boatloader and sent to service. Just wasn't daring enough as i wasn't sure if my image backup was safe.
firoz3321 said:
Today i gave it to service.
Un rooted, locked boatloader and sent to service. Just wasn't daring enough as i wasn't sure if my image backup was safe.
Click to expand...
Click to collapse
Received the mobile back and the FP reader is working fine. :angel: