I have managed to get the 3d max bin files merge them into one and have the baseband also the dll if anyone can get the apk's outta them that would be great..
I am confused to how to do this i will upload them now.. please be patiant..
What if we mixed a p920 baseband and used the P720 AP bin file i will try that when i get back from Birmingham after the weekend..
Meemo23 said:
I have managed to get the 3d max bin files merge them into one and have the baseband also the dll if anyone can get the apk's outta them that would be great..
I am confused to how to do this i will upload them now.. please be patiant..
What if we mixed a p920 baseband and used the P720 AP bin file i will try that when i get back from Birmingham after the weekend..
Click to expand...
Click to collapse
great !
so any possibilities that it would work flawlessly on our thrills/o3ds ?
Meemo23 said:
I have managed to get the 3d max bin files merge them into one and have the baseband also the dll if anyone can get the apk's outta them that would be great..
I am confused to how to do this i will upload them now.. please be patiant..
What if we mixed a p920 baseband and used the P720 AP bin file i will try that when i get back from Birmingham after the weekend..
Click to expand...
Click to collapse
i'm stuck on .bin for now, we need to find correct offset to create system.img
If i don't mistake p920 offset was from 00B80000 to 22ABFFF0
anyone can help us?
For the v20B .bin, the system.img file block was from B80000 all the way to the end of the .bin file. The end block depends on the size of the firmware and as such varies with different firmwares.
Maybe you could dd it in Ubuntu and inject the image into a normal p920 bin??
pandaball said:
For the v20B .bin, the system.img file block was from B80000 all the way to the end of the .bin file. The end block depends on the size of the firmware and as such varies with different firmwares.
Click to expand...
Click to collapse
so we need to know exact size of system.img?
any way to find it?
samno said:
Maybe you could dd it in Ubuntu and inject the image into a normal p920 bin??
Click to expand...
Click to collapse
What I did for the v20B bin was to copy the blocks 00B80000 to the end block and paste them in a new file using Winhex, rename it to system.img, go over to linux and use
sudo mkdir temp
sudo mount -o loop system.img temp
Click to expand...
Click to collapse
That way, I can then extract all the files using Terminal, like for example sudo cp system/app/LGHome.apk LGHome.apk (assuming default folder is pointed at desktop) to extract everything.
More info in the original thread: http://forum.xda-developers.com/showthread.php?t=1517531
Fab985 said:
so we need to know exact size of system.img?
any way to find it?
Click to expand...
Click to collapse
No need. System.img extends from 00B80000 all the way to the end of the file. The end block of the .bin file is also the end block of the system.img file.
I tried that but i get: "you must specify the filesystem type" in terminal when i try to mount. Is 00B80000 start? Can you take a look at that? Or bin is not extracted ok.
I don't have the download link... post it here and I'll take a look when I have time, I'm lazy to look for it
pandaball said:
I don't have the download link... post it here and I'll take a look when I have time, I'm lazy to look for it
Click to expand...
Click to collapse
LGP720 V10A_00
At first glance, so much for a 'lighter and thinner' rom when it's almost a full 100mb larger than the P920's rom
pandaball said:
At first glance, so much for a 'lighter and thinner' rom when it's almost a full 100mb larger than the P920's rom
Click to expand...
Click to collapse
Do you think you can extract everything from the kdz?
i will upload the ap file and stuff later i am tired right now will upload when i can...
Yeah, can extract it fine.
---------- Post added at 10:21 PM ---------- Previous post was at 10:11 PM ----------
My WinHex isn't working for some reason, will debug it tomorrow. In the meantime, try looking for the EXT4 magic number 0xF30A (0A F3 in hex) or 13 00 00 00 which is the compatibility structure between ext3 and ext4. The last file with any of these should be system.img.
If not, try the site here and see if it helps you find the start of the img files.
Well guys im really cheering that you can port that to O3D. Sadly im totally dont know how to do the port therefore i cant help to you, but i wish i could.
Go ahead you will make many ppl really happy if you can success (including me -> my genitalia will be the biggest ever xD)
I might have a hit. Winhex is still broken but someone with a working version of it could help me out with it.
154F2EFB seems to be the starting block if I'm interpreting it correctly. Could someone copy from that offset onwards all the way to the end, save it as an img and see if it mounts fine in Linux? This is a semi-wild guess since 0AF3 in hex brings up 5.3k hits while the text based search brings up 154F2EFB as the only hit which strikes me as odd but we'll see. The file size is approximately 300MB which is about right.
pandaball said:
I might have a hit. Winhex is still broken but someone with a working version of it could help me out with it.
154F2EFB seems to be the starting block if I'm interpreting it correctly. Could someone copy from that offset onwards all the way to the end, save it as an img and see if it mounts fine in Linux? This is a semi-wild guess since 0AF3 in hex brings up 5.3k hits while the text based search brings up 154F2EFB as the only hit which strikes me as odd but we'll see. The file size is approximately 300MB which is about right.
Click to expand...
Click to collapse
Wait I will try.
Sent from my LG-GT540 using XDA
---------- Post added at 04:10 PM ---------- Previous post was at 03:56 PM ----------
154f2efb didnt find. I find 0af3 as text 3 times. I will copy last one it has 373 MB maybe it will mount. I will try now.
sorry 154f2efb is a offset lol
---------- Post added at 04:23 PM ---------- Previous post was at 04:10 PM ----------
I tried from offset 154f2efb it is not working i cant mount it. it is 322mb file. Again: you must specify the filesystem type.
hey guys have you you tried this method from this thread to get the system apks ??? or to put in another way would this work for the 3d max extracted files http://forum.xda-developers.com/showthread.php?t=899580
rezzsha said:
hey guys have you you tried this method from this thread to get the system apks ??? or to put in another way would this work for the 3d max extracted files http://forum.xda-developers.com/showthread.php?t=899580
Click to expand...
Click to collapse
Have you actually read this thread? You would know that we're stuck on the final step of extracting system.img if you did.
only thing that is manage to extract are .png files, there are some interesting icons like cube I did it with win hex. It have options too extract known file tipes. It can also extract zip files and it extract parts off apps with it. If we could know header and footer of apk file it could extract them too. I tried but with no succes, I get only parts of apks. I attached 4 icons:
iodak said:
only thing that is manage to extract are .png files, there are some interesting icons like cube I did it with win hex. It have options too extract known file tipes. It can also extract zip files and it extract parts off apps with it. If we could know header and footer of apk file it could extract them too. I tried but with no succes, I get only parts of apks. I attached 4 icons:
Click to expand...
Click to collapse
haha cool i am still trying to rip the whole system apart to get all the files needed to build and port the whole rom.. Even if i do manage to get it working it won't solve our GC problems as we can't use 3D max's baseband as it corrupts your imei..
Related
Im trying to unpack system.IMG from the ruu and running into.issues.
Unyaffs.exe gives an error. And every other unpack tool I can think of fails.
Any ideas? Has anyone unpacked this yet?
Sent from my ADR6425LVW using XDA App
It doesn't use the yaffs filesystem. you need to unpack with explore2fs.exe on windows or in linux since it is ext4
Serinety said:
Im trying to unpack system.IMG from the ruu and running into.issues.
Unyaffs.exe gives an error. And every other unpack tool I can think of fails.
Any ideas? Has anyone unpacked this yet?
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Its EXT4.
The attached tool "should" do it for you. Its what I used...
I cannot however attrribute credit to the tool because I honestly do not know where it came from but its freeware GNU 3. The license is in the Help -> About.
Enjoy!
con247 said:
It doesn't use the yaffs filesystem. you need to unpack with explore2fs.exe on windows or in linux since it is ext4
Click to expand...
Click to collapse
I dont beleive explore2fs will read ext4. You need to use the one I posted above. Could be wrong as I am at work right now
scrosler said:
I dont beleive explore2fs will read ext4. You need to use the one I posted above. Could be wrong as I am at work right now
Click to expand...
Click to collapse
your the man, that worked I thought it was yaffs and nothing I did worked, it was driving me crazy lol.
2nd thing tho. the img file is 1.2gb, but after i extract it its about 697mb.. are there some hidden files that are not being extracted?
scrosler said:
I dont beleive explore2fs will read ext4. You need to use the one I posted above. Could be wrong as I am at work right now
Click to expand...
Click to collapse
It does I used it to extract the system image a couple weeks ago.
Serinety said:
your the man, that worked I thought it was yaffs and nothing I did worked, it was driving me crazy lol.
2nd thing tho. the img file is 1.2gb, but after i extract it its about 697mb.. are there some hidden files that are not being extracted?
Click to expand...
Click to collapse
Your saying JUST system.img is 1.2GB but extracts to /system/ as 697MB?
Thats some serisous backwards compression
700 Megs sounds about right for /systesm/ image. I can look when I get home. Maybe Con has it close by?
con247 said:
It does I used it to extract the system image a couple weeks ago.
Click to expand...
Click to collapse
What version do you have? I tried with the (what I thought was) latest and it wouldnt read it. I then tried with the other and it was fine. Can you post the version you have that read it?
scrosler said:
Your saying JUST system.img is 1.2GB but extracts to /system/ as 697MB?
Thats some serisous backwards compression
700 Megs sounds about right for /systesm/ image. I can look when I get home. Maybe Con has it close by?
Click to expand...
Click to collapse
File Name: system.img
Type: Disc Image File (.img)
Size on Disk: 1.21 GB (1,308,618,752 bytes)
Folder name: systemimg_upack
Type: Folder
Size on Disk: 697 MB (731,574,272 bytes)
Contains: 1,370 Files, 58 Folders
Serinety said:
File Name: system.img
Type: Disc Image File (.img)
Size on Disk: 1.21 GB (1,308,618,752 bytes)
Folder name: systemimg_upack
Type: Folder
Size on Disk: 697 MB (731,574,272 bytes)
Contains: 1,370 Files, 58 Folders
Click to expand...
Click to collapse
Wow, 500 Megs in slack? Now thats efficency!
But 700 megs sounds right to me for a sys img. I will in a few hours, at work now... Maybe can remopte desktop in... LMS...
Ok, RDP and 4G is AWESOME!
I can confirm what you are seeing is 100% correct.
I never noticed that before....
I also compared this with an Evo 3D ROM and it matches up proportionately....
scrosler said:
Ok, RDP and 4G is AWESOME!
I can confirm what you are seeing is 100% correct.
I never noticed that before....
I also compared this with an Evo 3D ROM and it matches up proportionately....
Click to expand...
Click to collapse
Wonder if its because Windows sees ext4 in a different way.. and mis represents its actual size
Sent from my ADR6425LVW using XDA App
Serinety said:
Wonder if its because Windows sees ext4 in a different way.. and mis represents its actual size
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Windows is not looking at it as a ext4 file system. Its looking at it as a single IMG file that is 1.x GB's big.
After doing some research on the bin format rom, i finally find the system.img offset in the v20 bin rom。
tool we need
winhex other HEX edit tool ,yaffs2img or other ext3 img editor.
Step
1.open the LGP920AT-00-V20b-ESA-XXX-JAN-10-2012+0_AP.bin in winhex or other HEX edit tool.
2. use winhex to dump the content from offset
0XB80000 to the end, and save the dump as system.img .
3. now you can use yaffs2img or other ext3 edit tool to edit the img. add su to bin/ (set permission 6755 ),add supperuser.apk to app/ (set permission 0644).
4,save the changes to the img.
5. write the img back to the bin.
6. flash the bin (you know how to right ?)
test fine on my 3D
Ok,where can we find that bin rom???
great work..
can you share your modified bin ????
it would be great to try .....
actually this is required to have modified and pre-rooted roms, those can be flashed direstly
dclx said:
After doing some research on the bin format rom, i finally find the system.img offset in the v20 bin rom。
tool we need
winhex other HEX edit tool ,yaffs2img or other ext3 img editor.
Step
1.open the LGP920AT-00-V20b-ESA-XXX-JAN-10-2012+0_AP.bin in winhex or other HEX edit tool.
2. use winhex to dump the content from offset
0XB80000 to the end, and save the dump as system.img .
3. now you can use yaffs2img or other ext3 edit tool to edit the img. add su to bin/ (set permission 6755 ),add supperuser.apk to app/ (set permission 0644).
4,save the changes to the img.
5. write the img back to the bin.
6. flash the bin (you know how to right ?)
test fine on my 3D
Click to expand...
Click to collapse
well the original v20b bin + fls is linked in this thread http://forum.xda-developers.com/showthread.php?t=1517531 ( thanks pandaball) , so could someone release a modified version with superuser included for us noobs
The modified file please !
Is there any .bin version for V20e?
pennzoilgtr said:
Is there any .bin version for V20e?
Click to expand...
Click to collapse
+1 for that..
I only have v20B currently. In any case, I'm uploading the modified .bin file now. Please wait while it takes its own sweet time to upload
thanks pandaball, hopefully you "find" other ones aswell
pandaball said:
I only have v20B currently. In any case, I'm uploading the modified .bin file now. Please wait while it takes its own sweet time to upload
Click to expand...
Click to collapse
U got any issue with gb baseband on singtel?? I'm on m1 and I got no ghost call though but my radio would just hang and I can't even turn on airplane mode to rectify fortunenately not everytime
pennzoilgtr said:
U got any issue with gb baseband on singtel?? I'm on m1 and I got no ghost call though but my radio would just hang and I can't even turn on airplane mode to rectify fortunenately not everytime
Click to expand...
Click to collapse
Nope, haven't had any dropped calls/sms or any problems related to basebands. I was surprised too since I read that there were issues with the Gingerbread baseband.
pandaball said:
Nope, haven't had any dropped calls/sms or any problems related to basebands. I was surprised too since I read that there were issues with the Gingerbread baseband.
Click to expand...
Click to collapse
i see, btw how is the video recording for 20b? i experiencing persistent stuttering when recording 1080p on my class 6 sandisk for 21a/b, 20e .. froyo seems smoother. but very bad memory management :/
strange thing is that stutters appear to happen when my sd running very low space. but was very smooth when there is tons of space left.
Haven't tried video recording yet, only had this phone for about 2 weeks
pandaball said:
Haven't tried video recording yet, only had this phone for about 2 weeks
Click to expand...
Click to collapse
only had for it for 2 weeks and gone so hardcore
20b and 20e already available pre-rooted in general forum
exploit for 20C coming soon.
20c
rooted 20c fg trill rom on lg o3d
thx
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
Try the tools in this thread . I used them last week to extract a build prop.
Just load up the system.IMG and drag the file from the system folder to your desktop.
gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
The tar file for Cricket has already been posted in the general section of ATT
Sent from my SAMSUNG-SM-G920AZ
daniel4653 said:
The tar file for Cricket has already been posted in the general section of ATT
Sent from my SAMSUNG-SM-G920AZ
Click to expand...
Click to collapse
I already downloaded that file.... I just need to extract the build.prop from the system.img which I already have. The thing is I am having trouble getting the build.prop
Sent from my SAMSUNG-SM-G920AZ
gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
I got your PM. Sorry for the late reply. I'm posting here in case someone else needs the info.
Download Ext2explore.
Extract to your PC.
Run as administrator.
In app: go to file - open image - (find your system image) and open
It will display your image in tree and folder view
Use either one (depending on your preference) (but your build.prop will be in the first view as its in the root of the system).
Right click the file/s you want to extract
Select save
Save your file.......profit
Hope this helps
tiboric said:
I got your PM. Sorry for the late reply. I'm posting here in case someone else needs the info.
Download Ext2explore.
Extract to your PC.
Run as administrator.
In app: go to file - open image - (find your system image) and open
It will display your image in tree and folder view
Use either one (depending on your preference) (but your build.prop will be in the first view as its in the root of the system).
Right click the file/s you want to extract
Select save
Save your file.......profit
Hope this helps
Click to expand...
Click to collapse
When I try to open the file the program just closes and i go to the log and this is what it says.
Error Opening \\.\PhysicalDrive1. Error Code 2
No of disks 1
Scanning \\.\PhysicalDrive0
index 0 ID 7 size 976769024
Partition Table Error on C:/Users/giovany/Desktop/New folder (2)/system.img
Invalid End of sector markerBad Super Block. The drive is not ext2 formatted.
Drive is not right formatted.
solution for img extraction/fix here
I have Just Repaired my H810 after 6 month dead . Now I have full procedure to recover any LG Phone witch has in this condition ,there is no download mode,no recovery and nothing sign of life..
Now you want *.img from running AT&T /h810v10o/H81020n/ h81021z/h81022b (lolipop/marshmallow baseband ) Firmware because there is no full stock firmware available .
Create Backup.img From Running h810v10o/H81020n/ h81021z/h81022b (lolipop/marshmallow baseband ) rooted system
1.Format external MicroSD card with exFAT system file , ( Most Important thing is SD card more than 32GB (which is size of the whole partition) use 64Gb or 128Gb card
2.Do a full factory reset from CWM TWRP or any recovery
3.Now open ADB shell
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=8192 seek=65536 count=579584
it will take around sone time
Size of the backup.img is arround 32gb
Now You have backup.img in your hands
now same method to unbrick
Steps to Unbrick:
1. Insert your memory card in Card Reader and Format it using Windows Format. While formatting "uncheck Quick Format" and Change Type to "exFat". You can alternatively use SD Card Formatter but make sure that the card is in exFat format.
if exFAT not works than try to format with FAT32
2. Once format is completed, install Win32DiskImager and open it. Add SystemImage.bin file. If it does not show the bin file just rename SystemImage.bin to SystemImage.img and then select it. Select your memory card and Click Write.
(You can alternatively change the file types on the win32diskimage from .img to all types)
Win32diskimage
3. One the Write Completes. Eject Card and insert in your LG G4 H810. Press Volume Up Button while connecting the USB Cable.
4. There you go, it will open the download mode. Now Open LGUP Tool as admin. It will show the device as connected. Select the Original KDZ/TOT Firmware and Click Start. it will complete and your Mobile will reboot.
5. Now its Done. Enjoy!
or u can use eMMC ADB Dumper
dump boot1
and boot2
any of one images works to get download mode
does anyone have download link
mahan2607 said:
I have Just Repaired my H810 after 6 month dead . Now I have full procedure to recover any LG Phone witch has in this condition ,there is no download mode,no recovery and nothing sign of life..
Now i want *.img from running AT&T H81020n Firmware because there is no full stock firmware available .
Create Backup.img From Running H81020n rooted system
1.Format external MicroSD card with exFAT system file , ( Most Important thing is SD card more than 32GB (which is size of the whole partition) use 64Gb or 128Gb card
2.Do a full factory reset from CWM TWRP or any recovery
3.Now open ADB shell
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=8192 seek=65536 count=579584
it will take around sone time
Size of the backup.img is arround 32gb
Now You have backup.img in your hands
I Have Sold my Phone So any member provide this image file here .
Click to expand...
Click to collapse
Hello master, i have the same problem, my h810 at&t is dead since a long time, please what files used?? i tried with many files and write in my sd 32 gb and still dead, i believe the files is wrong and you have the one, please up the file, be my savior .
GENTLEMAN I HAVE JUST SOLD MY PHONE , you need a Running H81020n/ h81021z/h81022b (marshmallow baseband ) (marshmallow ,old baseband not supported)rooted system to create bin file . i ahve already posted to create bin file method , believe me its work 100% . no other files works because h810 have different partition size ( not work 811,812,815,818 bin file ) , important thing is that you need a working marshmallow rooted h810 to create files . one thing is also important that you need to 32 gb microsd or greater to backup the image
Can someone share backup dump please
mahan2607 said:
GENTLEMAN I HAVE JUST SOLD MY PHONE , you need a Running H81020n/ h81021z/h81022b (marshmallow baseband ) (marshmallow ,old baseband not supported)rooted system to create bin file . i ahve already posted to create bin file method , believe me its work 100% . no other files works because h810 have different partition size ( not work 811,812,815,818 bin file ) , important thing is that you need a working marshmallow rooted h810 to create files . one thing is also important that you need to 32 gb microsd or greater to backup the image
Click to expand...
Click to collapse
Didnt you saved the dump ? Plz i am not in the us and i cant get access to another g4 At&t
mahan2607 said:
GENTLEMAN I HAVE JUST SOLD MY PHONE , you need a Running H81020n/ h81021z/h81022b (marshmallow baseband ) (marshmallow ,old baseband not supported)rooted system to create bin file . i ahve already posted to create bin file method , believe me its work 100% . no other files works because h810 have different partition size ( not work 811,812,815,818 bin file ) , important thing is that you need a working marshmallow rooted h810 to create files . one thing is also important that you need to 32 gb microsd or greater to backup the image
Click to expand...
Click to collapse
ok my friend, thanks, is a big step to revive my h810
Create backup.img and upload for other members
Why none of members dont want to share dump files
Its been 7 months since my h810 is sleeping
Amit2310 said:
Why none of members dont want to share dump files
Its been 7 months since my h810 is sleeping
Click to expand...
Click to collapse
We don't have root with marshmallow on H810. So we can't make a dump.
N4cr2k said:
We don't have root with marshmallow on H810. So we can't make a dump.
Click to expand...
Click to collapse
gentleman than create lolipop backup.img for those who have bricked with lolipop
now you an use this tool eMMC ADB Dumper
mahan2607 said:
now you an use this tool eMMC ADB Dumper
Click to expand...
Click to collapse
It looks like that tool requires root?
N4cr2k said:
It looks like that tool requires root?
Click to expand...
Click to collapse
you just upload the lolipop rooted emmc backup for users
Many peoples are still using rooted lollipop for h810, even i was using it , its seems like just they are not interested to upload 1gb of file
---------- Post added at 06:17 PM ---------- Previous post was at 06:09 PM ----------
http://ouo.io/XK4tFF
This file is not gonna work ?
Amit2310 said:
Many peoples are still using rooted lollipop for h810, even i was using it , its seems like just they are not interested to upload 1gb of file
---------- Post added at 06:17 PM ---------- Previous post was at 06:09 PM ----------
http://ouo.io/XK4tFF
This file is not gonna work ?
Click to expand...
Click to collapse
this file is not created by this method so its not work for bootable sd card , its for use any kind of box Z3X or emmc pro
Mr. Amit , please upload this file for members
Amit2310 said:
Many peoples are still using rooted lollipop for h810, even i was using it , its seems like just they are not interested to upload 1gb of file
---------- Post added at 06:17 PM ---------- Previous post was at 06:09 PM ----------
This file is not gonna work ?
Click to expand...
Click to collapse
This file don't work, i tried many times but the result is the same, dead, no response.
Please men, the solution is in your hands, up the file
jasta 11 said:
This file don't work, i tried many times but the result is the same, dead, no response.
Please men, the solution is in your hands, up the file
Click to expand...
Click to collapse
I dont have file bros , my own h810 is dead from many months
---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------
I seen in gsmforum that it can be fixed using medusa box by selecting h811 as product then flashing it with kdz file of h810.
Shops in my city dont have that box , you can go to shop in your city and try if they have that box
---------- Post added at 08:47 AM ---------- Previous post was at 08:42 AM ----------
mahan2607 said:
Mr. Amit , please upload this file for members
Click to expand...
Click to collapse
http://www.mediafire.com/?npkrdqrkz03el2e
This file ?
mahan2607 said:
gentleman than create lolipop backup.img for those who have bricked with lolipop
Click to expand...
Click to collapse
You stated that you made a backup from a working phone that we can use to recover. Do you have this image uploaded somewhere so we can download it to repair our dead h810's?
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