Database Info

[Request] somebody that can create update.zip for cwm

can someone create a update.zip for cwm with this old firmware v08 , i just badly need it , i have a prototype o3d and i updated it to v10d and after that my battery is always 0%.. the old firmware that is ok with my o3d is v08.
this is the link of the 1st rom that i need.
http://www.multiupload.com/UQPQO1SJ0S
i am hoping that someone can help. thanks

isaias19 said:
can someone create a update.zip for cwm with this old firmware v08 , i just badly need it , i have a prototype o3d and i updated it to v10d and after that my battery is always 0%.. the old firmware that is ok with my o3d is v08.
this is the link of the 1st rom that i need.
http://www.multiupload.com/UQPQO1SJ0S
i am hoping that someone can help. thanks
Click to expand...
Click to collapse
If that's the firmware you need, just download it and put in a zip file.
right click on the folder then add to archive. use the compression method store.
That should work but do a backup before hand just in case.

I tried to zip it and rename it to update.zip and install it via cwm recovery but the recovery said that it failed on signature.. Something.,,

isaias19 said:
I tried to zip it and rename it to update.zip and install it via cwm recovery but the recovery said that it failed on signature.. Something.,,
Click to expand...
Click to collapse
The file is already a zip file, it's just in the wrong compression method...
using winrar, open the zip file, then tools, then convert archive.
A box should appear, change the archive format to zip, and compression method to store.

Hi, isaias19, I also have a prototype o3d. I can not use it after rom(v10d, v10e) upgrade. If possible, could you post your v08 rom backup file using cmw?? Thanks.

@ modernbruce
we have the same problem , i did not backup my stock rom thats why iam searching for the v08 firmware. =C

Hi ,
For your case update.zip will not solve your problem.
you need dump your system and replace by another one:
To see your partition :
adb shell cat /proc/partitions
After try use these command to put your new system :
http://www.omappedia.org/wiki/Android_eMMC_Booting
++

[Q] Please help me step by step for a custom ROM?

Hi guys,
I really need help on this, and i am hoping very much someone can be patient with me as i try to install a custom ROM on my HTC Desire S.
The BIGGEST problem i am facing is getting command text correct in the command window, i am using Windows 7 home premium on a laptop, the previous posts i read and followed were all saying put this in the command and put that in the command but none of them were correct and my computer kept saying wrong!
I am currently at the stage where i have visited HTC Dev and i have sucessfully gone through the procedure for unlocking the bootloader, i found this difficult to do, command prompts they gave were wrong i had to change paths, and i was missing certain .dll files on my computer too, which HTC did not mention i would need, but here i am after days of messing about and trying all sorts of commands, with a unlocked bootloader, with S-ON and running a Vodafone stock rom of Gingerbread Android version 2.5.3.
My phone is Vodafone branded i wish to remove all of their branding and apps, and install a plain unbranded ROM.
However, i need step by step instruction, i can not do this from threads that say "follow this here (link to another thread) which then links to another and another, i ended up with i think 15 tabs in the browser open, with conflicting advice, conflicting information, mistakes, and a whole lot of jargon that i did not understand, so what i really am hoping for is firstly links to all the software or downloads that i will need first, direct link to the rom, the backup, and anything else, if anyone needs info from my phone to pinpoint a specific rom i am happy to give it, i do not mind another HTC rom as long as its plain with no carrier apps or branding on it, then once i have got all the downloads sorted out i can start from there.
Please help me out i have been at this for days and getting nothing except confused.
Many thanks! :good:

3324536
I have found this quite up to date guide which is very easy to follow, are the rom and all the downloads OK for a UK phone?
I have hboot 200. 0002 as well as S-ON so i believe its the same, i can follow this one quite easy is it ok to do??
Also, while flashing this rom and recovery image, should i have SDK tools open on my computer??
And another thing, i noticed while extracting the recovery image that it just says recovery, should i rename it to recovery.img or leave it as it is? Because the command prompts are saying "recovery.img" and not just "recovery"?????
Thanks.
http://forum.xda-developers.com/showthread.php?t=1525100

mickmick72 said:
I have found this quite up to date guide which is very easy to follow, are the rom and all the downloads OK for a UK phone?
I have hboot 200. 0002 as well as S-ON so i believe its the same, i can follow this one quite easy is it ok to do??
Also, while flashing this rom and recovery image, should i have SDK tools open on my computer??
And another thing, i noticed while extracting the recovery image that it just says recovery, should i rename it to recovery.img or leave it as it is? Because the command prompts are saying "recovery.img" and not just "recovery"?????
Thanks.
http://forum.xda-developers.com/showthread.php?t=1525100
Click to expand...
Click to collapse
First you need to get in Folder Options in your WIN 7 Control Panel.There's option in View tab called " Hide extension for known file types". Uncheck that option and click ok.Then you will see extensions for all files on you win 7.This will show you extension of recovery.Should be .img.
Then you can follow that guide.I used the same one.
You need to get newest recovery.There are TWRP and 4ext for HTC Desire S.They are up to date.Do a little search and read posts and info.
Check post about panels (Hitachi or Sony)http://forum.xda-developers.com/showthread.php?t=1943524.Again search for that in HTC Desire S forum here.When you check all of that you can try any custom ROM but always backup nandroid.
Little hint : If you want to start CMD window in any folder first open that folder hold SHIFT and right click on empty space.You will get command there named Open command window here.Click on that and you can work.
GL.If you need more help ask here again.

SKENER said:
First you need to get in Folder Options in your WIN 7 Control Panel.There's option in View tab called " Hide extension for known file types". Uncheck that option and click ok.Then you will see extensions for all files on you win 7.This will show you extension of recovery.Should be .img.
Then you can follow that guide.I used the same one.
You need to get newest recovery.There are TWRP and 4ext for HTC Desire S.They are up to date.Do a little search and read posts and info.
Check post about panels (Hitachi or Sony)http://forum.xda-developers.com/showthread.php?t=1943524.Again search for that in HTC Desire S forum here.When you check all of that you can try any custom ROM but always backup nandroid.
Little hint : If you want to start CMD window in any folder first open that folder hold SHIFT and right click on empty space.You will get command there named Open command window here.Click on that and you can work.
GL.If you need more help ask here again.
Click to expand...
Click to collapse
Thanks mate, i will do what you advise, good trick about opening command in a folder
I will ask if i get any questions then cheers

OK i have a question straight away, it says in the tutorial:
Copy the rom onto the SD card, then it says copy the boot.img onto the android C folder - SO -
Do i first extract the boot.img and copy it to the C android folder AND copy the same boot.img onto my SD card, as well as the meta info and other stuff?
OR do i copy the boot.img onto the C drive only, and copy everything else onto the SD card?
A little confused here on what to do.
Thanks for any help.

Copy the rom onto the SD card, then it says copy the boot.img onto the android C folder
Click to expand...
Click to collapse
You do exactly that. You place the rom into the sd card, and you copy the boot.img into the said folder.
This is because you are "unlock s-on", the recovery isn't able to flash the boot.img, so you have to do it manually.
Remember, even after you flash the rom, if you did not flash the boot.img the phone will NOT fully boot.
*also, the guide says to turn the phone off after flashing the rom and boot into the bootloader. I dont think this is necessary, you can just reboot the phone into bootloader from the recovery itself.

98623459
#Fear said:
You do exactly that. You place the rom into the sd card, and you copy the boot.img into the said folder.
This is because you are "unlock s-on", the recovery isn't able to flash the boot.img, so you have to do it manually.
Remember, even after you flash the rom, if you did not flash the boot.img the phone will NOT fully boot.
*also, the guide says to turn the phone off after flashing the rom and boot into the bootloader. I dont think this is necessary, you can just reboot the phone into bootloader from the recovery itself.
Click to expand...
Click to collapse
So, just to clarify, i copy the whole .zip onto the SD card (including boot.img) and then re copy the boot.img into my Android folder on the computer (i will then have boot.img on BOTH the SD card and the C Android folder, this is where i am getting confused, i intend to start flashing today sometime.
OK i am going to flash Reaper V.4 rom and 4EXT as recovery, if anyone has better suggestions on a safe rom please let me know i will flash that instead.
Thanks.

mickmick72 said:
So, just to clarify, i copy the whole .zip onto the SD card (including boot.img) and then re copy the boot.img into my Android folder on the computer (i will then have boot.img on BOTH the SD card and the C Android folder, this is where i am getting confused, i intend to start flashing today sometime.
OK i am going to flash Reaper V.4 rom and 4EXT as recovery, if anyone has better suggestions on a safe rom please let me know i will flash that instead.
Thanks.
Click to expand...
Click to collapse
You can try other roms when you try that.There's a lot of nice and smooth editions. First try reaper you have it now.
With S-ON you have to flash boot.img in fastboot after you install rom from recovery.That's why you need to copy it in android-tools folder.Whole zip goes on sd and you backup old rom from recovery, wipe everything except sd (wipe is recommended) and then install from zip in recovery.After that reboot in bootloader then flash boot.img from fastboot.Reboot and wait.Should be in in few min.No more then 10.Follow the guide.
GL

4325422
SKENER said:
You can try other roms when you try that.There's a lot of nice and smooth editions. First try reaper you have it now.
With S-ON you have to flash boot.img in fastboot after you install rom from recovery.That's why you need to copy it in android-tools folder.Whole zip goes on sd and you backup old rom from recovery, wipe everything except sd (wipe is recommended) and then install from zip in recovery.After that reboot in bootloader then flash boot.img from fastboot.Reboot and wait.Should be in in few min.No more then 10.Follow the guide.
GL
Click to expand...
Click to collapse
Any idea what i am doing wrong here? I do have recovery.img in my Android folder, but its not in the android tools folder, should i be putting it in the adt bundle folder rather than leaving it outside of it?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Michael>cd \Android
C:\Android>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Android>

Yes put the recovery.img inside the fastboot/adb folder

jmcclue said:
Yes put the recovery.img inside the fastboot/adb folder
Click to expand...
Click to collapse
OK going to try again, thanks!

Success!! And all the crap vodafone apps and branding have gone! I did run into problems but i sorted it out. Thanks very much for all the help here i will be installing new roms all the time
On this reaper rom, there is no app for google play store, would anyone know how to install it? Or how do i get to play store from this rom?
And no options for fastboot that i can see, so i may have a few problems installing other roms
Where can i see a list of all the roms i can download for the Desire S??
Thanks!!

mickmick72 said:
Success!! And all the crap vodafone apps and branding have gone! I did run into problems but i sorted it out. Thanks very much for all the help here i will be installing new roms all the time
On this reaper rom, there is no app for google play store, would anyone know how to install it? Or how do i get to play store from this rom?
And no options for fastboot that i can see, so i may have a few problems installing other roms
Where can i see a list of all the roms i can download for the Desire S??
Thanks!!
Click to expand...
Click to collapse
Flash gapps (google apps) in recovery and for everything else ul find below
http://forum.xda-developers.com/showthread.php?t=1146601

jmcclue said:
Flash gapps (google apps) in recovery and for everything else ul find below
http://forum.xda-developers.com/showthread.php?t=1146601
Click to expand...
Click to collapse
jmcclue means you need to download gapps for your android.That will be in zip and you install it through recovery just like rom.Most of custom rom require that step.Copy zip on SD,boot in recovery and flash from zip.Reboot and you will get google apps.
This guide is for HTC Desire S and you can find most of things you need but for roms follow Android Development in HTC Desire S on XDA.
GL

mickmick72 said:
And no options for fastboot that i can see, so i may have a few problems installing other roms
Click to expand...
Click to collapse
fastboot is controlled by the bootloader, the rom can't affect it in any way. The option "fast boot" in HTC Sense roms is something else, that sort of hibernates the phone instead of powering off, so the phone "boots fast".

Thanks guys i will go aheah and do these

SKENER said:
This guide is for HTC Desire S and you can find most of things you need but for roms follow Android Development in HTC Desire S on XDA.
GL
Click to expand...
Click to collapse
That link i posted also has all the roms in it

[Completed] Bricked, only adb sidelog is working nothing else

Interrupted flashing.. System memory null, adb not recognizing device, mtp drivers installing process failing.. No fastboot mode, its snapdragon 415 (micromax e455) phone,
Only firmware available on sites is folder with (.bat) file on top double clicking which alloed me flash firmware earlier.. This folder don't have meta-inf folder.. System.img boot.img are there..
Please tell me.. Is there any possibility of reviving my phone??
Phone is stuck on company logo.. (im assuming not system files are there in phone= blank)
I cant flash twrp/cwm or any thing else.. Fastboot not working.
Please any help will be much appreciated

aalok.kashyap said:
Interrupted flashing.. System memory null, adb not recognizing device, mtp drivers installing process failing.. No fastboot mode, its snapdragon 415 (micromax e455) phone,
Only firmware available on sites is folder with (.bat) file on top double clicking which alloed me flash firmware earlier.. This folder don't have meta-inf folder.. System.img boot.img are there..
Please tell me.. Is there any possibility of reviving my phone??
Phone is stuck on company logo.. (im assuming not system files are there in phone= blank)
I cant flash twrp/cwm or any thing else.. Fastboot not working.
Please any help will be much appreciated
Click to expand...
Click to collapse
Greetings and welcome to assist. Unfortunately I can not find any software for your device. All I have managed to find is there is a nitro and canvas version of the e455, do you have the correct firmware for your variant?
Good Luck
Sawdoctor

Yo.. I too can't find any software assistance for my device.. I have only adb sidelog operational.. Nothing else.. Yes, that firmware i have is the only firmware available on Internet for e455 and it will work once i can make my adb work.. Not "adb sidelog" which is already working.. This phone belongs to my friend.. I borrowed it from him for learning developing..
That firmware worked when i deleted micromax(brand) own app store on phone, deleting which phone bwas not loading 'os'.. Again that firmware folder have .bat file which automatically flash every thing once its double clicked..
Right now.. I think this phone have lost adb and fastboot while i was flashing firmware from that .bat file in that folder after double clicking it..
Now this phone have only "STOCK RECOVERY" AND ONLY ADB SIDEOAD IS WORKING THERE..
In my next reply I'll post ss of yhe files i have in that folder..
Read again.. This is the only firmware we have available for this phone on net ..

Okay? I have left 2 options only..
1. Some how flash this files in this folder using adb sideload.. Which i currently cannot becouse of the the error after zipping this folder on flashing i get.. "signature verification failed"
2. Make my adb working.. Phone memory is empty.. I assume.. Haoe to make adb working on this phone?

Yo

No Screenshot is showing when i trying to upload it from phone app (n9005), switching to website on phone.. Will try ro upload them from there ??

..

link for both 2 photos.. Please read the the tge content carefully.. I've described my problem 100%.. Need help desperately

https://m.facebook.com/story.php?story_fbid=452799381776484&id=100011392778817&_rdr

LG Aristo 3 X220MA Root Search

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

Can I recover Tab3 7.0 Android 4.4.2 WiFi using Haimdall on FWUL and how is it done?

As Odin in Windows does not do the trick for me, flashing stock ROM onto the Tab3, 7.0 WiFi device, I'll now want to try using Haimdall on FWUL.
But to make that happen, I seem need seperate .img files as Haimdall works with seperate files instead of that big tar.md5 file like Odin in Windows does.
So the first question would be:
What tools do I need to get all these seperate .img files out of the stock ROM Odin uses??
In Haimdall I managed to detect the Tab3 device and download and save the PIT file successfully.
But when I try to write into 'recovery' partition using a renamed file (TWRP 3.0.0-0.img) recovery.img, the process failed.
The log shows successfull writing of the PIT file, but it failed on recovery.img with this error 'failed to confirm end file transfer sequence'.
Also, there's no progressbar showing on the Tab3 device, while writing.
I already tried other USB cables, same results.
So the second question would be:
What did I do wrong, or did I miss something?

xdausernl said:
As Odin in Windows does not do the trick for me, flashing stock ROM onto the Tab3, 7.0 WiFi device, I'll now want to try using Haimdall on FWUL.
But to make that happen, I seem need seperate .img files as Haimdall works with seperate files instead of that big tar.md5 file like Odin in Windows does.
So the first question would be:
What tools do I need to get all these seperate .img files out of the stock ROM Odin uses??
In Haimdall I managed to detect the Tab3 device and download and save the PIT file successfully.
But when I try to write into 'recovery' partition using a renamed file (TWRP 3.0.0-0.img) recovery.img, the process failed.
The log shows successfull writing of the PIT file, but it failed on recovery.img with this error 'failed to confirm end file transfer sequence'.
Also, there's no progressbar showing on the Tab3 device, while writing.
I already tried other USB cables, same results.
So the second question would be:
What did I do wrong, or did I miss something?
Click to expand...
Click to collapse
To extract the firmware down to the individual .img files, try this thread, it leads to another guide on another site.
https://forum.xda-developers.com/showthread.php?t=2138885
Keep in mind, this guide is a bit old, the basic process is still valid but some things may have changed in how Samsung firmware is put together, there may be some extra steps required for firmware from newer devices.
Sent from my LGL84VL using Tapatalk

Droidriven said:
To extract the firmware down to the individual .img files, try this thread, it leads to another guide on another site.
https://forum.xda-developers.com/showthread.php?t=2138885
Keep in mind, this guide is a bit old, the basic process is still valid but some things may have changed in how Samsung firmware is put together, there may be some extra steps required for firmware from newer devices.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...

xdausernl said:
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...
Click to expand...
Click to collapse
I have to edit the last post, because I can change the stock ROM file name as mentioned before and that did not cause any problems with the md5 hash.
At this point, I can also download all files (10) succesfully from Heimdall with the Samsung tablet.
The only problem is caused by replacing the 'system.img' file, as the tablet immediatly reboots after Heimdall released the device after download was successfully.
It could mean that after the succesfull download, the downloaded system.img file is deleted at immediate reboot of the tablet, which would also explain why there's no changes after tablet reboot.
With all the other 9 downloaded files from Heimdall, it took several seconds until reboot of the tablet.

xdausernl said:
I have to edit the last post, because I can change the stock ROM file name as mentioned before and that did not cause any problems with the md5 hash.
At this point, I can also download all files (10) succesfully from Heimdall with the Samsung tablet.
The only problem is caused by replacing the 'system.img' file, as the tablet immediatly reboots after Heimdall released the device after download was successfully.
It could mean that after the succesfull download, the downloaded system.img file is deleted at immediate reboot of the tablet, which would also explain why there's no changes after tablet reboot.
With all the other 9 downloaded files from Heimdall, it took several seconds until reboot of the tablet.
Click to expand...
Click to collapse
Try a windows PC and try flashing via Odin, it tends to work better than Heimdall.
Also, if you are trying to use a system.img that is different than the system.img in your firmware, your bootloader may not be allowing the different system to flash or boot on your device.
Sent from my SM-S767VL using Tapatalk

xdausernl said:
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...
Click to expand...
Click to collapse
Droidriven said:
Try a windows PC and try flashing via Odin, it tends to work better than Heimdall.
Also, if you are trying to use a system.img that is different than the system.img in your firmware, your bootloader may not be allowing the different system to flash or boot on your device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply.
But I came to Heimdall because Odin3 in Windows and even JOdin3 in Linux failed.
My guess is that the installed system.img on the system partition the culprit was in this case, because the stock ROM was the correct one for my tablet.
If you don't have the correct software, you either cannot install it or you will get your device bricked.
My device seem to be software bricked, for that matter and that is due to either the root software, anti virus software or an combination of both.

xdausernl said:
Thanks for your reply.
But I came to Heimdall because Odin3 in Windows and even JOdin3 in Linux failed.
My guess is that the installed system.img on the system partition the culprit was in this case, because the stock ROM was the correct one for my tablet.
If you don't have the correct software, you either cannot install it or you will get your device bricked.
My device seem to be software bricked, for that matter and that is due to either the root software, anti virus software or an combination of both.
Click to expand...
Click to collapse
Meanwhile I think I found a possible cause for failure using Heimdall-Frontend.
Heimdall-Frontend uses only extracted content of a stock ROM, in my case that's 10 files.
Although the download of the 'system.img' file completed successfully and Heimdall-Frontend releases the connected device, there's still a slightly different behaviour at reboot of Tab3.
Because after the release of the connected device, Tab3 then immediately goes into reboot.
That's not the case with all other downloaded files.
After releasing the connected device, it then takes a few second until the Tab3 goes into reboot.
So my guess is that at immediate reboot the downloaded 'system.img' file will then be deleted from the Tab3.
That would explain why after reboot nothing has really being changed.