So I have the h900 currently with the Xposed framework installed. it WAS rooted until I stupidly unrooted it in the SuperSU app. I have SuperSU installed as a system app. so when I factory reset and open SuperSU, it notifies me that I don't have the SU binaries... I figured this wasn't a problem, and I would just flash the stock image... NOPE! invalid TOT. nothing I have tried goes beyond 9% before I get the "invaled TOT" notification on my PC. while it was rooted I changed all sorts of stuff in the build.prop. Ex. Model number, Bluetooth address, Mac address, android version, and IMEI, device ID. all that stuff. I have come to the conclusion that, that is my problem. The model number. Does that sound feasible?
Now, none of this would be an issue if I could use snapchat... snapchat knows I have the xposed framework installed and I cannot sign in. (laugh it up). and without root... I cannot flash the .zip file to uninstall xposed framework. ive been working on this on and off for 3 weeks. ands its done pissed me off. haha.
oh, and and I still have functionality in most of the xposed modules even WITHOUT root. incase anyone was wondering wether or not you need root. I can list which xposed modules I'm currently using and wether or not they work if anyone wants.
I'm goin to attempt to flash it again right meow. ill report back when it is, once again unsuccessful
well. no success. I even deleted every single file that had anything to do with LG. then downloaded everything again and still, I got no luck.
Possibly broken tot?
Try flashing the original tot if your not already. If not, try using Kingroot to at least get you full access, if your granted root access again, change your device detail back to the original status. Especially the model number. I believe your changed model number is whats triggering your invalid tot error. If you are unable to do so, grab the tot of the model you changed your device to show, and see if you can edit any of the model number identifying entities in the tot file its self. You want to try to trick lg flash to think your flashing the tot file of the model you changed your device to. This process has not been done before nor do i know how to do it, but as far as the diagnostic i provided, i believe it to be correct.
---------- Post added 27th May 2016 at 12:05 AM ---------- Previous post was 26th May 2016 at 11:15 PM ----------
I found this on the G3 forums
sgtmedeiros said:
It seems that there is a way to fix it after all! there is a dll file for the lg g2 that skis the check of which model your phone is. I used this dll in combination with the stock .tot file and it worked!
Click to expand...
Click to collapse
If that dll will work for the v10, that might be the easy fix.
Sent from my LG-H900 using XDA-Developers mobile app
I tried Kingroot and I cant regain Root. is there anyway to install the SU binaries??
I'm gonna try the other option tonight. I've read that thread too, Only I'm unsure if i should rename the .zip file before i unzip it? then rename the .tot file that i get from the .zip?
bellcrayyy said:
I tried Kingroot and I cant regain Root. is there anyway to install the SU binaries??
I'm gonna try the other option tonight. I've read that thread too, Only I'm unsure if i should rename the .zip file before i unzip it? then rename the .tot file that i get from the .zip?
Click to expand...
Click to collapse
Better safe than sorry to rename the .dll file. But after looking into it, it was named after the processer the device that file was designed for, or at least its MSM id. So rename it to LGUP_8992.
Another thing i found, was someone talking about doing a full uninstall of super su, then sideloading it with ADB. With the goal being to re-root your device so you can reset all addresses, IDs, and the model number, i do believe the solution will come from sideloading if the dll doesnt work. BTW. I forgot to ask if you had any kind of custom recovery? And did you modify the the model number using build.prop?
Well. I can't get it to flash back. Not really an issue. I still have the xposed framework active. I just cant update to marshmallow or use Snapchat. Lol.
This the last thing I could find. After that, youll probably have to wait for a dev to crack the h900 wide open.
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
Its been awhile. Ive been super busy with work and I'm taking a course for certification in penetration testing.
Never could figure it out. Kinda sucks
I'm limited to what xposed modules I can use, as some require root access.
Does anyone know how close the devs are to unlocking the bootloader?
Sent from my Certainly not another basic ***** like Siri. Can you say Eww?! using XDA-Developers mobile app
Wait. You can flash zips from within the TWRP apk. The app requires root. I know... But what if I select the supersu apk and press "flash now" will it attempt to flash the .zip? Or will it remind me that I haven't granted root privileges.
LG V10
Tried it. Didn't work. Looks like I'm stuck with this for awhile.
LG V10
bellcrayyy said:
Tried it. Didn't work. Looks like I'm stuck with this for awhile.
LG V10
Click to expand...
Click to collapse
The few devs i know of working on the project have hit multiple road blocks but, some files that are availible need either decrypting, converting, or recompiling. Which is not so easy for some file formats that are only used with LG.
Im still working on converting and decrypting one file that is availible. It appears to be an apple file, but im running windows, so conversion is tricky.
I'm building a hackintosh.... Almost finished... I can let you use it as a designated virtual machine if that'll help. Lol
LG V10
bellcrayyy said:
I'm building a hackintosh.... Almost finished... I can let you use it as a designated virtual machine if that'll help. Lol
LG V10
Click to expand...
Click to collapse
Or would you like a crack at it? I think the main thing is that its not compatible with windows.
PM'd
LG V10
Shadow Assassin said:
And did you modify the the model number using build.prop?
Click to expand...
Click to collapse
Oh. I forgot to mention that i did change the model number using the build.prop
bellcrayyy said:
Oh. I forgot to mention that i did change the model number using the build.prop
Click to expand...
Click to collapse
I want to congratulate you. To hard brick a phone is very rare and in some cases difficult. But you might have done it! Lol, but probably not. With the right tot it can be fixed.
Related
Seeing as there isn't a section for the LG P870/LG Escape I'm going to try and get as much info condensed into one thread for now.
Not even sure how popular this phone is but, hopefully this will be of some use to someone.
KDZ:
I know this isn't posted anywhere so here is the v10f KDZ from LG. It is the latest firmware as of 11/6/2012:
http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP870/AATTBK/P87010f_00/P87010f_00.kdz
If you don't know how to flash a KDZ I will make a guide here soon. V10f is rootable using the method below as is v10c
Download Mode:
To get into download mode turn off your phone, press and hold the vol+ and vol- keys, with those held down insert the USB cable while continuing to hold down the keys. After a few seconds phone will enter download mode automatically.
Rooting:
I was able to root my phone that has v10c on it using this tool:
http://forum.xda-developers.com/showpost.php?p=31963526&postcount=532
I used 1.6 of the root script but some say that 1.2 works better for them. I would try 1.6 if that doesn't work try 1.2 if it fails the first time run it a second time and it should work.
Thanks! My wife just got this. I was able to root and update and retain root with OTA rootkeeper. Was looking for a kdz just in case. If there's enough interest i will see if i can port TWRP so we can cook up some custom roms.
I am definitely interested in custom roms, I have this device. Its not bad considering the price and what you get. 1494 on geekbench too! Pretty decent!
---------- Post added at 07:49 PM ---------- Previous post was at 07:44 PM ----------
Thanks for the effort
Aye guys I'm new into rooting and android in general, but I don't really understand how to root this phone. Kinda been looking around for a while and I was wondering if you can write some sort of guide. As of now I'm pretty lost the other threads aren't giving me any general information on exactly how to root the LG P870 or androids in general.
-Thanks
Btw I understand what exactly what rooting does to your device and the purpose of rooting, its just exactly how to root the device.
Well first things first do you have the android SDK installed on your computer
cyclejim said:
Well first things first do you have the android SDK installed on your computer
Click to expand...
Click to collapse
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Urabewe said:
Rooting:
I was able to root my phone that has v10c on it using this tool:
http://forum.xda-developers.com/showpost.php?p=31963526&postcount=532
I used 1.6 of the root script but some say that 1.2 works better for them. I would try 1.6 if that doesn't work try 1.2 if it fails the first time run it a second time and it should work.
Click to expand...
Click to collapse
He
GHazard said:
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Click to expand...
Click to collapse
Download the zip and unzip it to your desktop. Go into your phone's settings and go to developers options. Turn on USB debugging. Go back to settings and go to security. Turn on unknown sources. Now plug your phone in and run the .bat file that you just unzipped. Follow the commands on the and that should be it. Good luck!
Thanks for the effort
GHazard said:
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Click to expand...
Click to collapse
KDZ is the LG format for ROMs which is the built in read only memory that hold the instructions for the phone to run the hardware and features.
But I just rooted my phone with a combination of the above files, and it didnt go exactly as I hoped. First I ran the v1.2 batch file linked above, (the 1.6 batch file archive is invalid and doesnt extract properly. It seemed like it ran properly, i did the restore (no data destructive you shouldnt lost any data) but I didnt have root when completed. Then I tried the v17 of the original thread which can be found here http://forum.xda-developers.com/showthread.php?t=1886460
That one also ran but failed at the end saying something about me not having root on the phone.
I than ran the v1.2 batch file not once, but twice in a row. The second time I found my phone operating in "emulator mode" in other words, it was running laggy as hell and very slow. I then ran the V17 batch file from the link above, and boom it worked. So as you can see it wasnt typical, but I think if you dont have success with the 1.2 the first time, run it again, if it still didnt work, try running v17 like i did. I now have root and my phone is working fine.
Basically, I got the Escape then got the Nexus7 and have been involved in that. Really haven't been doing much with the Escape. I will be looking into more for everyone and hopefully get a custom recovery at the very least. Then at that point we can start thinking about rom. Until then we are stuck with what we have. I will get more info for everyone , till then this is what we have. If you think you can help go for it. If not sorry but this is the best info there is for our phone . I will positively without a doubt post any new info here so if that's what you are looking for this is the right place until then, thank you and you are welcome.
Sent from my Nexus 7 using xda premium
Markyzz said:
He
Download the zip and unzip it to your desktop. Go into your phone's settings and go to developers options. Turn on USB debugging. Go back to settings and go to security. Turn on unknown sources. Now plug your phone in and run the .bat file that you just unzipped. Follow the commands on the and that should be it. Good luck!
Click to expand...
Click to collapse
So when I run the .bat file do I just run it in cmd? I'm kinda knew at this lol.
Also does my phone have to be in download mode?
Sorry for the inconvenience but where exactly do I run the .bat file?
-Thanks
One more thing I never downloaded a .zip or .rar file.. Could you please leave me a link?
Rooted
Thanks people I guess I just needed time to figure it out lol. I ran it in cmd twice(1.2v) but not right after each other and the second time it worked thanks guys.
Well. I tried to install beats audio but now it won't even load up just boot loops when it gets to at&t...
Bricked
Great the first bricked lg p870 lol, anyone know how to fix this. Or is it just a brick?
Sorry for the repititive posts, but so far I have gotten my device to read by my computer. The only thing is I can see it in the Device manager but it never shows up in my computer. It also picks the phone up in cmd, is there sometype of command I can run to flash the device and put it back to normal?
GHazard said:
Sorry for the repititive posts, but so far I have gotten my device to read by my computer. The only thing is I can see it in the Device manager but it never shows up in my computer. It also picks the phone up in cmd, is there sometype of command I can run to flash the device and put it back to normal?
Click to expand...
Click to collapse
No command. You need to flash the kdz using lg flash tool.
Sent from my MB886 using xda premium
Markyzz said:
No command. You need to flash the kdz using lg flash tool.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Is their a guide on how to flash the device using the kdz flash tool? I mean my phone won't turn on though. It goes into the lg logo then just goes black (the back light is still on).
K I have all the tools but
I downloaded every tool from this thread
But in the PDF guides it says to put the phone in Upgrade mode by removing the SIM, battery and SDC(Micro sd card?) so I did that. Then insert the usb while holding the Volume Up button. All that happens on my phone is the home keys on the bottom just flash. And my phone doesn't connect to my computer either.
My Notes on LG P870
Ok I have fixed my device, well twice now. It seems whenever you try to change any file within the root it restarts, then boot loops. I tried too change a font using Rom Toolbox, it restarted then boot looped. I rooted the device using the 1.2v script once, but this time I'll try 1.7v and see if I can change fonts etc.
Are any of you guys having any problem with this?
If you do, and you are soft bricked just:
Download UPK 3.7.1
Then open up LG /mobile Update
Click Install Drivers(Make sure your phone is not connected) Choose your phone and carrier
Let that finish(Gonna take awhile you have to install all of them)
Then click Install updates...Done
Worked
Posting confirmation for an LG Escape (p870). 10f rooted using the tools linked in first post. Used version 1.2 to start and had to use the version 17 of the other rooting kit to finalize like another user encountered as well. Thanks will be given if they haven't been yet.
*******ALL IS FINE NEVERMIND THIS POST******
Do not use any mods unless you know what you are doing. If your phone cannot boot, there is no going back. There is no way to restore at the moment. So again do not modify the system or anything that you are unsure will work, don't end up with a paperweight.
Mods please leave this here until things are sorted out. Or until if/when we are able to restore to stock, or a custom ROM is released.
If you need help getting AdAway working, or changing emojis; feel free to ask I'm sure myself or others will help you in this thread.
Yup i wish this was started earlier lol
So is there something spexial we need to do for adaway? Already done the whole root process
xamius said:
So is there something spexial we need to do for adaway? Already done the whole root process
Click to expand...
Click to collapse
i just installed the apk from f-droid and it worked.
xamius said:
So is there something spexial we need to do for adaway? Already done the whole root process
Click to expand...
Click to collapse
I installed the dev version from here http://forum.xda-developers.com/showthread.php?t=2190753
Just enable system-less from preferences and you're set.
Here's a question. Can you enable multi-user on the V20 through build prop like we could on other phones? Inserting:
Fw.max_users=3
Fw.show_multiuserui=1
I installed the latest ad away from f-droid, and changed the default hosts file from /system to /data before enabling it, and it works fine.
---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------
czerdrill said:
Here's a question. Can you enable multi-user on the V20 through build prop like we could on other phones? Inserting:
Fw.max_users=3
Fw.show_multiuserui=1
Click to expand...
Click to collapse
Yes, you just need to be aware of the limitations on some of the system apps and features.
kibmikey1 said:
I installed the latest ad away from f-droid, and changed the default hosts file from /system to /data before enabling it, and it works fine.
---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------
Yes, you just need to be aware of the limitations on some of the system apps and features.
Click to expand...
Click to collapse
What limitations are there?
This is nothing new, though. Everyone attempting this should know full well that these are early days and using an exploit before we even have stock images to restore with is always risky. My motto is "keep it stock." Aside from ad blocking and a few other tweaks in build.prop, I keep flashing and other more serious mods to a minimum until there are methods to restore. I'm looking into seeing how TWRP handles the new tot's, but it looks like I'm going to have to cobble it together, which will take some time.
Edit: After looking around, it seems like an update of lgup is needed before any v20 firmware can be flashed, which I would bet will be on the way sometime later this month with the release of the unlocked (carrier free) variant.
So whats the scene update here for the V20? Just 1 variant is bootloader unlocked? What's the flash/root method and what models is it confirmed to work with?
RoOSTA
roosta said:
So whats the scene update here for the V20? Just 1 variant is bootloader unlocked? What's the flash/root method and what models is it confirmed to work with?
RoOSTA
Click to expand...
Click to collapse
http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594 & so far T-mobile has the only unlocked bootloader AFAIK.
apps that use build.prop tweaks like l speed work well on my phone and I left kernel and CPU tweaks alone.
2muchspl said:
http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594 & so far T-mobile has the only unlocked bootloader AFAIK.
Click to expand...
Click to collapse
So single SIMs only can be rooted - or this 1 model?
i'm assuming lgup is LG's version of Odin? what twrp repo were you looking at? I heard nandroid backups were screwed up too
I just got my V20 today from T-Mobile. I traded in my note 7 finally (very sad ) i felt i had too because i fly a lot. I didn't want to be on the news as a domestic terrorists lol Anyways can i install viper safely or should i wait? It an ad blocker are my must haves
albinoman887 said:
i'm assuming lgup is LG's version of Odin? what twrp repo were you looking at? I heard nandroid backups were screwed up too
Click to expand...
Click to collapse
Yeah. The little bit I know about it is that it flashes .tot and .kdz files. What I'm understanding is that there's a missing .dll in order to use the .tot files we have now.
Hook up with @jcadduono. He's been the point man with getting root.
The G.O.A.T. said:
I just got my V20 today from T-Mobile. I traded in my note 7 finally (very sad ) i felt i had too because i fly a lot. I didn't want to be on the news as a domestic terrorists lol Anyways can i install viper safely or should i wait? It an ad blocker are my must haves
Click to expand...
Click to collapse
I have can confirm that version of ad blocking works, I had to use ES file explorer to move file to system/bin and followed steps and everything works fine from there. I started using this after they took AdFree down. RIP
http://forum.xda-developers.com/android/software-hacking/ads-adblocker-v1-0-t3283855
Unbrick Method Link Here?
You think unbricking phones like this would work?
http://techxat.com/restore-lg-v20-stock-romfirmware-unroot/
So there's no restore for a bricked device at the moment?
tApPeD fROM mY nExUs 6
So does anyone know if us T-Mobile users are "safe"? Lol I've flashed things like fonts, iOS emojis, Google assistant, dual speaker mod, and changed some UI sounds and everything seems ok but just wondering if there are certain limitations
I had been reading up on the Dirty Cow exploit/root method, and it seemed to be compatible with all Android devices, so I took a little chance with my v10, and it worked perfectly! I was on the stock unrooted 20l update, and followed all the steps here: https://github.com/jcadduono/android_external_dirtycow#running
Notes:
-I put our TWRP image and SuperSu zip on the root of my sdcard
-For the very last command, replace 'twrp.img' with the name of your TWRP image file(or change the name of your TWRP fiile to twrp.img ).
-Like it says in the instructions, the phone did look like maybe it bricked at one point, with a strange backlighting on the Tmobile boot screen. It worked out tho!
-My boot loader was unlocked prior to doing these steps
Info thread, v20: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Got all the files here: https://build.nethunter.com/android-tools/dirtycow/arm64/
YrrchSebor said:
I had been reading up on the Dirty Cow exploit/root method, and it seemed to be compatible with all Android devices, so I took a little chance with my v10, and it worked perfectly! I was on the stock unrooted 20l update, and followed all the steps here: https://github.com/jcadduono/android_external_dirtycow#running
Notes:
-I put our TWRP image and SuperSu zip on the root of my sdcard
-For the very last command, replace 'twrp.img' with the name of your TWRP image file(or change the name of your TWRP fiile to twrp.img ).
-Like it says in the instructions, the phone did look like maybe it bricked at one point, with a strange backlighting on the Tmobile boot screen. It worked out tho!
Info thread, v20: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Got all the files here: https://build.nethunter.com/android-tools/dirtycow/arm64/
Click to expand...
Click to collapse
Great job. You know technically these same instructions should work for ANY of the v10 variants ..verizon...at&t etc....including the ones that up till now didn't have root at all.
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
YrrchSebor said:
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
It requires an unlocked boot loader.
YrrchSebor said:
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes but for example verizon's comes with an unlocked bootloader...they just only had root for the 5.x rom's and none for the 6.0.
famewolf said:
Yes but for example verizon's comes with an unlocked bootloader...they just only had root for the 5.x rom's and none for the 6.0.
Click to expand...
Click to collapse
Gotcha yeah, it seems like good news for all phones with unlockable bootloaders until Google, and then the OEMs, patch the exploit.
Sent from my LG-H901 using XDA-Developers mobile app
will this factory reset my phone?
CrimsonSaber5G said:
will this factory reset my phone?
Click to expand...
Click to collapse
Nope. Unlocking your bootloader will but this won't in itself.
Sent from my LG-H901 using XDA-Developers mobile app
thank you, and i have the tmobile variant, that means my bootloader is already unlocked??
CrimsonSaber5G said:
thank you, and i have the tmobile variant, that means my bootloader is already unlocked??
Click to expand...
Click to collapse
No, it means it's unlockable, but you have to actively unlock it. There should be a thread here somewhere if you haven't done that yet, but it's just boot into bootloader and then 'fastboot oem unlock'
Edit: in case you need it there are great instructions in the v20 thread that I linked in the first post.
Sent from my LG-H901 using XDA-Developers mobile app
YrrchSebor said:
Gotcha yeah, it seems like good news for all phones with unlockable bootloaders until Google, and then the OEMs, patch the exploit.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
The cow method means copy on write...
This means as anything is written it is copied (or flashed or burned; whatever you want to call your desired definition)
You could in theory copy dummy files to a temp location and actually write to a permanent location...
Or am I thinking wrong about it?
If this is a viable option to ALL phones I don't think Google or manufactures could (or would for that matter) actually patch this kind of exploit as it would be super time consuming.
just confirming that Root 20l w/Dirty Cow does work.
Finally got my replacement V10 back, and all is a go again. Stock rooted,
Not sure the novice should try this, as its pretty nerve racking. If you follow the directions correctly it does work great.
Surprised they have closed this backdoor yet,
thanks for being the first to try this on a V10.
je2854 said:
The cow method means copy on write...
This means as anything is written it is copied (or flashed or burned; whatever you want to call your desired definition)
You could in theory copy dummy files to a temp location and actually write to a permanent location...
Or am I thinking wrong about it?
If this is a viable option to ALL phones I don't think Google or manufactures could (or would for that matter) actually patch this kind of exploit as it would be super time consuming.
Click to expand...
Click to collapse
I think it's considered a very serious vulnerability that must and will be patched soon. They can't have root access so easily obtained on any device.
Amd4life said:
just confirming that Root 20l w/Dirty Cow does work.
Finally got my replacement V10 back, and all is a go again. Stock rooted,
Not sure the novice should try this, as its pretty nerve racking. If you follow the directions correctly it does work great.
Surprised they have closed this backdoor yet,
thanks for being the first to try this on a V10.
Click to expand...
Click to collapse
You're welcome, and thanks for confirming. That one step where the screen goes weirdly backlit with the Tmo splash screen is a bit nerve-wracking, and so is writing recovery this way, but I was comforted by the fact that you can just tell it to to write to the recovery partition rather than having to know the more technical name/location(not sure if this was possible a few years back?)
Anyway, if I did brick I was gonna go straight to the store and buy a ZTE Zmax Pro for $180 haha.
Which reminds me, does anyone know if there is a way to simply push su into /system once you have the root shell, instead of writing recovery to flash SuperSu? Just curious. I sorta wanted to do that but then I just went with TWRP.
YrrchSebor said:
Which reminds me, does anyone know if there is a way to simply push su into /system once you have the root shell, instead of writing recovery to flash SuperSu? Just curious. I sorta wanted to do that but then I just went with TWRP.
Click to expand...
Click to collapse
No. The shell has limited access...it has just enough permissions to write recovery and access some things on boot...you need to get it a recovery where you can then flash a zip to install superuser.
Thanks so much for this info, I was actually about to post a new thread to see if root for 20L had been achieved.
But a few questions:
Is there a KDZ/TOT available for 20L? Or is it delivered in update.zip format via OTA?
Is there a way to root 20L without touching system partition? Like, you know, systemless root? I was thinking that maybe it might be possible to flash Magisk from TWRP then install systemless phh Superuser or (less preferable for me) SuperSU. This way I can still take the official Nougat OTA when it hits, without losing root. But the catch is, TWRP needs to be accessible first.
Well, time to sleep for now, it's been a long 3 days, subsisting on Monster and cigs. I'll tackle this when I eventually wake up.
Like the last guy, I've got a million questions on this. I need to find the changelog on 20L to begin with, because if they didn't fix the VoLTE silence on calling, then it's useless to me. I wonder where the OP was with his existing V10.. because I'm currently on 20J rooted with twrp. Seems with the instructions posted, I would have to use LG bridge to go back to 100% stock, then upgrade to 20L then hope this works. Again, the radios are probably modified so there's probably some kind of anti-rollback involved as well.
Great post though! Great work discovering this! Definitely in the right direction!
AnonVendetta said:
Thanks so much for this info, I was actually about to post a new thread to see if root for 20L had been achieved.
But a few questions:
Is there a KDZ/TOT available for 20L? Or is it delivered in update.zip format via OTA?
Is there a way to root 20L without touching system partition? Like, you know, systemless root? I was thinking that maybe it might be possible to flash Magisk from TWRP then install systemless phh Superuser or (less preferable for me) SuperSU. This way I can still take the official Nougat OTA when it hits, without losing root. But the catch is, TWRP needs to be accessible first.
Well, time to sleep for now, it's been a long 3 days, subsisting on Monster and cigs. I'll tackle this when I eventually wake up.
Click to expand...
Click to collapse
There is a 20l KDZ floating around in some other threads. Not sure if there is or will be a systemless root, never even done it myself [emoji4]
Sent from my LG-H901 using XDA-Developers mobile app
joesee said:
Like the last guy, I've got a million questions on this. I need to find the changelog on 20L to begin with, because if they didn't fix the VoLTE silence on calling, then it's useless to me. I wonder where the OP was with his existing V10.. because I'm currently on 20J rooted with twrp. Seems with the instructions posted, I would have to use LG bridge to go back to 100% stock, then upgrade to 20L then hope this works. Again, the radios are probably modified so there's probably some kind of anti-rollback involved as well.
Great post though! Great work discovering this! Definitely in the right direction!
Click to expand...
Click to collapse
The Volte silence bug is fixed in 20l, as many have reported. I had updated officially to 20l and was stock unrooted prior to this. But for people who are rooted on 20j or earlier, I believe Eliminator has released a pre-rooted update, so maybe you'd wanna do that instead.
Sent from my LG-H901 using XDA-Developers mobile app
The Software update is now rolling out for
ZV6 firmware, This WILL BLOCK DIRTY SANTA
Please don't attempt dirty Santa until there is confirmation
that the ZV6 was not fully patched, or if dirty santa can be changed to still root.
Edit:
If anyone gets a notice that the ZV6 update is ready to download and you ARE rooted,
please dont try and install it, but upload it and pm me with the files. Ill be able to get them to the right places and the device prepared
for the next update.
Thank you
Willing to help out the cause, could you send me guide on how to dump those files?
Yes I would love to have a system dump..... I lost all my radios in need of radios.
Sent from my iPhone using Tapatalk
Team DevDigitel said:
The Software update is now rolling out for
ZV6 firmware, This WILL BLOCK DIRTY SANTA
Please don't attempt dirty Santa until there is confirmation
that the ZV6 was not fully patched, or if dirty santa can be changed to still root.
If anyone can get me a full dump of ZV6 unmodified that would be awsome as i need to get my base updated!
This would need to be a full system dump and the boot.img to match please.
Thank you!
Click to expand...
Click to collapse
Once I get the notification I will try to pull it! Check hangouts we will get a base built.
Sent from my LG_LS997 using Classic Rom!
Team DevDigitel said:
The Software update is now rolling out for
ZV6 firmware, This WILL BLOCK DIRTY SANTA
Please don't attempt dirty Santa until there is confirmation
that the ZV6 was not fully patched, or if dirty santa can be changed to still root.
If anyone can get me a full dump of ZV6 unmodified that would be awsome as i need to get my base updated!
This would need to be a full system dump and the boot.img to match please.
Thank you!
Click to expand...
Click to collapse
DirtySanta wont be able to be changed to fix a block. it relies on the dirtyCow exploit and if that gets blocked theres no fixing. When someone WHO IS ROOTED. gets the update notification please pm me that way i can go through the file and install it to my device.(same way i did the zv5 base) and ill get a ZV6 base going.
Word of notice too all. IF you try to install the update while rooted you will get a TWRP loop. The Fix for that is all over so please dont bug me for a fix.....
mr pnut said:
Yes I would love to have a system dump..... I lost all my radios in need of radios.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
can you explain this?
do you mean that your phone number and baseband are showing UNKNOWN after you flashed a rom ?
more then likely a AOSP one?
No I have nothing no imei no base band no radios no Bluetooth address nothing bro..... I need the qcn and radios
Sent from my iPhone using Tapatalk
mr pnut said:
No I have nothing no imei no base band no radios no Bluetooth address nothing bro..... I need the qcn and radios
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I have stock backups using flashfire..
But the baseband issue come from flashing a gsm rom or a aosp rom. Im not sure witch efs partition is radio only but i have them backed up.. If you look for my guide on how to manually program this will get those items to come back without flashing radios.
Flash my stock rom or the one from dirty santa..
Then follow the instructions to get to manual program. Youll need to go to sprint.com and get ur msl or ask care and say you need it to do a full reset using ##786# / you may also need to flash a asop rom again and toggle your network mode back to rusim or ull have to use cdma workshop to change.
As well as for your msid so you can program it.
The nam config got changed from rium to nv only and breaks ur efs connection. The prl probably is 162 also on your phone so you'll need to grab the latea 56021 prl also to flash.
Theres a ton of good info on that post and the adjoining one to it for fixing this issue.
Id need assistance in what parts of my efs backup i can use as parts contain my imei and msid etc and will booloader brick your device trying to restore my esn as well as error code my device for being cloned.
Some has to have the zv6 ota in their fota directory by now.. Humm.. I personally havent seen it but sheesh..
mhmm :/ we all could be enjoying the new version if someone sends me the file soon. Its located in the Cache partition. Exact file is /cache/update.zip
@me2151 Think this is the right file:
LINK REMOVED - THIS WAS THE ZV5 UPDATE, SORRY.
According to Sprint's website, there is no ZV6 available?
bgibson72 said:
@me2151 Think this is the right file:
Link removed.
Click to expand...
Click to collapse
Is this your file? What version are you currently on?
It is my file but I have no idea what version it is. I am on ZV3 somehow. I used dirtysanta and the stock rom you provided (I think?).
bgibson72 said:
It is my file but I have no idea what version it is. I am on ZV3 somehow. I used dirtysanta and the stock rom you provided (I think?).
Click to expand...
Click to collapse
OK. When did you receive the notification for updating?
EDIT: Based on a quick look through the script i believe this is the zv5 update. ill do a more thorough check tomorrow but target id's are matching zv5.
EDIT#2: Also i do appreciate you uploading the file. If it does turn out to be ZV5 i will ask that you remove your link that way we do not get confused, as for right now though it can stay. Ill let you know tomorrow.
me2151 said:
OK. When did you receive the notification for updating?
EDIT: Based on a quick look through the script i believe this is the zv5 update. ill do a more thorough check tomorrow but target id's are matching zv5.
EDIT#2: Also i do appreciate you uploading the file. If it does turn out to be ZV5 i will ask that you remove your link that way we do not get confused, as for right now though it can stay. Ill let you know tomorrow.
Click to expand...
Click to collapse
Sounds good. I did confirm this was the ZV5 update that came out in December 2016. My bad. The link still works in your quoted reply above, even though I removed the file. (Google has it cached?)
I've got the ZV6 file now, I think.
bgibson72 said:
I've got the ZV6 file now, I think.
Click to expand...
Click to collapse
Yeah. They came out this morning ish
fogame said:
Yeah. They came out this morning ish
Click to expand...
Click to collapse
Sounds like it. I shared the file with @Team Dev Digitel and @me2151 via PM, so we'll see...
Is anyone working on getting root on ZV6? If so what help can I contribute?
Sent from my LG V20 using XDA Labs
shadowswittness said:
Is anyone working on getting root on ZV6? If so what help can I contribute?
Click to expand...
Click to collapse
I'm not working on root for zv6.
I just had this thought... Since Samsung is basically on lockdown now.... I wonder what would happen if you install a custom ROM, in order to make the phone not care which android version or security version you currently have, and then tried to flash the downgraded stock rom that you wanted in the first place? Anyone ever tried this?
Sent from my [device_name] using XDA-Developers Legacy app
Try This
Pawprints1986 said:
I just had this thought... Since Samsung is basically on lockdown now.... I wonder what would happen if you install a custom ROM, in order to make the phone not care which android version or security version you currently have, and then tried to flash the downgraded stock rom that you wanted in the first place? Anyone ever tried this?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hi there,
Well I have tried downgrade from firmware 6.0 to 5.0.2 and it did work so it might work for you
You can try and use this website as I Prefer this website than Sam mobile
The website is www.updato.com
Pawprints1986 said:
I just had this thought... Since Samsung is basically on lockdown now.... I wonder what would happen if you install a custom ROM, in order to make the phone not care which android version or security version you currently have, and then tried to flash the downgraded stock rom that you wanted in the first place? Anyone ever tried this?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
First of all, if the bootloader is locked, you can't flash a custom ROM, so that shoots that idea in the head.
Second, a custom ROM is basically only a system.img and kernel. Even if you were able to flash a custom ROM, your stock bootloader is still there. Flashing a custom ROM will not change whether or not you can downgrade the bootloader, the part of your device where bootloader is located is unaffected by any custom ROM or system.img.
Sent from my LGL84VL using Tapatalk
KIBS2173 said:
Hi there,
Well I have tried downgrade from firmware 6.0 to 5.0.2 and it did work so it might work for you
You can try and use this website as I Prefer this website than Sam mobile
The website is www.updato.com
Click to expand...
Click to collapse
What was your software versions before and after the downgrade? Im just curious if you were still on the first bootloader version and thats maybe why it worked?
Ive been doing a little reading on combination roms... but im not sure where a reliable source would be, or if i can make my own combining 2 different firmwares
Try This
Pawprints1986 said:
What was your software versions before and after the downgrade? Im just curious if you were still on the first bootloader version and thats maybe why it worked?
Ive been doing a little reading on combination roms... but im not sure where a reliable source would be, or if i can make my own combining 2 different firmwares
Click to expand...
Click to collapse
Hi there,
well I was using a Samsung A5000 which was the original version of the A5 series and it was the Chinese version of the phone, so therefore it had the HONGKONG VERSION on it in order to get Google PlayStore because playstore is banned in China. However, the HongKong Samsung service only updated the phone up to version 5.0.2 and China had the latest firmware update which was android 6.0
I was however able to update the phone from version 5.0.2 to 6.0 using ODIN
and the phone rebooted with new boot loader, recovery, and even it has a new downloader.
The phone was working alright but it didn't had any playstore.
I tried numerous ways to install playstore which resulted the phone to lag and heat up for some reason
So I had to downgrade it from 6.0 to 5.0.2 and I used ODIN again.
And it was flashed successfully.
And no when I flashed it from 5.0.2 to 6.0 it had the new boot loader and I didn't have to unlock the boot loader at all.
And I think by 2017 THE SAMSUNG KNOX service was discontinued so i don't see a reason why there would not to downgrade your phone.
Combining two roms with different coding can brick your phone. As most custom roms are built by building over the existing rom.
So by concluding you can try to downgrade the firmware or you can change the firmware to another region or you can wait till samsung to release another software update which might fix your problem or just re-install the whole OS with the same version as there might be a missing file when it was updated to that version
KIBS2173 said:
Hi there,
well I was using a Samsung A5000 which was the original version of the A5 series and it was the Chinese version of the phone, so therefore it had the HONGKONG VERSION on it in order to get Google PlayStore because playstore is banned in China. However, the HongKong Samsung service only updated the phone up to version 5.0.2 and China had the latest firmware update which was android 6.0
I was however able to update the phone from version 5.0.2 to 6.0 using ODIN
and the phone rebooted with new boot loader, recovery, and even it has a new downloader.
The phone was working alright but it didn't had any playstore.
I tried numerous ways to install playstore which resulted the phone to lag and heat up for some reason
So I had to downgrade it from 6.0 to 5.0.2 and I used ODIN again.
And it was flashed successfully.
And no when I flashed it from 5.0.2 to 6.0 it had the new boot loader and I didn't have to unlock the boot loader at all.
And I think by 2017 THE SAMSUNG KNOX service was discontinued so i don't see a reason why there would not to downgrade your phone.
Combining two roms with different coding can brick your phone. As most custom roms are built by building over the existing rom.
So by concluding you can try to downgrade the firmware or you can change the firmware to another region or you can wait till samsung to release another software update which might fix your problem or just re-install the whole OS with the same version as there might be a missing file when it was updated to that version
Click to expand...
Click to collapse
Combining 2 firmwares that were made for the exact same model number, does not cause a brick unless it wasn't done correctly. For example, a 5.0 firmware can be mixed and matched with a 6.0 firmware if they are for the same device.
Sent from my LGL84VL using Tapatalk
Try this
Droidriven said:
Combining 2 firmwares that were made for the exact same model number, does not cause a brick unless it wasn't done correctly. For example, a 5.0 firmware can be mixed and matched with a 6.0 firmware if they are for the same device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hi there,
Well I have tried to combine 2 firmwares together which ended up bricking one of my android devices. since it was a mediatek device I just gave up on the SPFLASH TOOL as it just gave out error codes. However if you have tried it and became successful well think i have done something wrong
BUT I THINK IT WILL BE ALRIGHT FOR YOU TO DOWNGRADE THE DEVICE
KIBS2173 said:
Hi there,
Well I have tried to combine 2 firmwares together which ended up bricking one of my android devices. since it was a mediatek device I just gave up on the SPFLASH TOOL as it just gave out error codes. However if you have tried it and became successful well think i have done something wrong
BUT I THINK IT WILL BE ALRIGHT FOR YOU TO DOWNGRADE THE DEVICE
Click to expand...
Click to collapse
Were the two firmwares that you tried to combine for the exact same model number device? Or were they for a different device? That makes a difference.
What I described is basically the same as porting a Samsung firmware from a US variant of a device to work on an international model of the same device(i.e. port stock lollipop for a US variant of Samsung Galaxy S6 to work on an international variant of Samsung Galaxy S6). It's a common procedure.
Sent from my LGL84VL using Tapatalk
TRY THIS
Droidriven said:
Were the two firmwares that you tried to combine for the exact same model number device? Or were they for a different device? That makes a difference.
What I described is basically the same as porting a Samsung firmware from a US variant of a device to work on an international model of the same device(i.e. port stock lollipop for a US variant of Samsung Galaxy S6 to work on an international variant of Samsung Galaxy S6). It's a common procedure.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hi there,
Yeah they were for the exact phone and model. For some reason SpFlash Tool bricks Mediatek Devices. I think someone should create another version of spflash tool just like ODIN. Odin is actually a great software to flash all Samsung devices I Had no problems with it.
But Spflash tools are still in Beta mode. The software is not reliable.
I had to get a new motherboard for my device because of the hard brick however my pc is still able to detect the device but it won't install the firmware. Keeps on giving me error 4032 something like that.
Droidriven said:
Combining 2 firmwares that were made for the exact same model number, does not cause a brick unless it wasn't done correctly. For example, a 5.0 firmware can be mixed and matched with a 6.0 firmware if they are for the same device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Can you lead me to anywhere explaining how to do this in detail?
I'm still researching. I saw somewhere that Oreo had a not as strict security downgrade and there was possibility that upgrading to Oreo and then downgrading to marshmallow might work.... But I tried to no avail. So there goes that theory...
I wasn't concerned about the upgrading as nougat and Oreo are basically the same, I'm not really losing or gaining by varying between those 2.
Still would love to have the best of both worlds though... Appearance of lollipop/marshmallow in all areas but with version either 7 or 8. The leaks of samsungs spin on 9 look a little promising.... A little.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
Can you lead me to anywhere explaining how to do this in detail?
I'm still researching. I saw somewhere that Oreo had a not as strict security downgrade and there was possibility that upgrading to Oreo and then downgrading to marshmallow might work.... But I tried to no avail. So there goes that theory...
I wasn't concerned about the upgrading as nougat and Oreo are basically the same, I'm not really losing or gaining by varying between those 2.
Still would love to have the best of both worlds though... Appearance of lollipop/marshmallow in all areas but with version either 7 or 8. The leaks of samsungs spin on 9 look a little promising.... A little.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Here is a guide to extract the two firmware files.
Extract one firmware in a folder of its own and extract the other in its own folder.
https://www.rwilco12.com/forum/showthread.php?tid=74
You basically only need to switch the system.img from the older firmware, in other words, remove the system.img from the firmware that won't allow downgrading, then, extract the system.img from the older firmware that you want to downgrade to, then put the older system.img into the firmware that won't allow downgrading. Then repackage the file into an Odin flashable .tar.md5 following this guide.
https://forum.xda-developers.com/showthread.php?t=2446269
Or this guide
https://www.rwilco12.com/forum/showthread.php?tid=92
***NOTE***
Some things may have changed since those guides were written. You might need to switch more than just the system.img files from the two firmware files. Do some researching and reading to find out and understand exactly which parts you need to swap around in order for the finished file to flash correctly.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Here is a guide to extract the two firmware files.
Extract one firmware in a folder of its own and extract the other in its own folder.
https://www.rwilco12.com/forum/showthread.php?tid=74
You basically only need to switch the system.img from the older firmware, in other words, remove the system.img from the firmware that won't allow downgrading, then, extract the system.img from the older firmware that you want to downgrade to, then put the older system.img into the firmware that won't allow downgrading. Then repackage the file into an Odin flashable .tar.md5 following this guide.
https://forum.xda-developers.com/showthread.php?t=2446269
Or this guide
https://www.rwilco12.com/forum/showthread.php?tid=92
***NOTE***
Some things may have changed since those guides were written. You might need to switch more than just the system.img files from the two firmware files. Do some researching and reading to find out and understand exactly which parts you need to swap around in order for the finished file to flash correctly.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks! My brain is kinda pooped for tonight, but I will definitely dig into these tomorrow night
I had read a bit about removing the sboot.bin file from the firmware i want to use, but it feels risky to remove it entirely. I like the idea of using it but allowing that other system image to flash, much like youve described! it sounds safer than just leaving components out completely
Pawprints1986 said:
Thanks! My brain is kinda pooped for tonight, but I will definitely dig into these tomorrow night
I had read a bit about removing the sboot.bin file from the firmware i want to use, but it feels risky to remove it entirely. I like the idea of using it but allowing that other system image to flash, much like youve described! it sounds safer than just leaving components out completely
Click to expand...
Click to collapse
Also, do some Google searches for:
"How to port Samsung stock firmware"
Or similarly worded searches to understand what is involved when modifying Samsung stock firmware.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Also, do some Google searches for:
"How to port Samsung stock firmware"
Or similarly worded searches to understand what is involved when modifying Samsung stock firmware.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
So, if I try this, and it doesn't work.... Is the worst case still that I may need to reflash twrp and the official firmware that does work? I had that happen when just regularly trying to flash the marshmallow official firmware, I think it's called "soft brick" cuz it wiped the nougat/oreo but couldn't install anything in its place, but I found my way out of it with no issues. And since I have no personal things on there yet I wasn't worried about wiping and losing anything. I have a twrp backup I also made of nougat after rooting but before messing with anything, so I've got that to fall back on too.
Still reading but just wanted to be sure, that the worst case is just needing to reflash proper working firmware/recovery if needed.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
So, if I try this, and it doesn't work.... Is the worst case still that I may need to reflash twrp and the official firmware that does work? I had that happen when just regularly trying to flash the marshmallow official firmware, I think it's called "soft brick" cuz it wiped the nougat/oreo but couldn't install anything in its place, but I found my way out of it with no issues. And since I have no personal things on there yet I wasn't worried about wiping and losing anything. I have a twrp backup I also made of nougat after rooting but before messing with anything, so I've got that to fall back on too.
Still reading but just wanted to be sure, that the worst case is just needing to reflash proper working firmware/recovery if needed.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
As long as the two firmware are for the same device and as long as you read carefully about what you're doing and you don't do something completely wrong, the worst you should expect is a soft brick or a bootloop, in which case, you'd flash the original stock firmware or you'd flash TWRP then restore the nandroid backup that you created from stock nougat.
Sent from my LGL84VL using Tapatalk
Droidriven said:
As long as the two firmware are for the same device and as long as you read carefully about what you're doing and you don't do something completely wrong, the worst you should expect is a soft brick or a bootloop, in which case, you'd flash the original stock firmware or you'd flash TWRP then restore the nandroid backup that you created from stock nougat.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
New little snag. Oreo uses lz4 compression while Marshmallow uses regular .img disk image compression. I wonder if I'm better off converting the marshmallow one to lz4 or converting the other Oreo files I'll be using into regular img files. Hmm.
I did start to Google that and people have converted the Oreo files to img before Odin could read the lz4 ones. But I wonder if the other way around could work too. Or, do they even need to be the same? Hmm.... Will need to do a bit more reading than expected
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
New little snag. Oreo uses lz4 compression while Marshmallow uses regular .img disk image compression. I wonder if I'm better off converting the marshmallow one to lz4 or converting the other Oreo files I'll be using into regular img files. Hmm.
I did start to Google that and people have converted the Oreo files to img before Odin could read the lz4 ones. But I wonder if the other way around could work too. Or, do they even need to be the same? Hmm.... Will need to do a bit more reading than expected
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Exactly, this isn't the kind of thing that has a clear cut, everything you want to know guide. It's the kind of thing you'll have to figure out and piece together from different sources.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Exactly, this isn't the kind of thing that has a clear cut, everything you want to know guide. It's the kind of thing you'll have to figure out and piece together from different sources.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Okay, so upon some more research, and finding a couple of tools here on xda, heres what ive been able to do.
Before I did anything I made copies of both roms in a separate new folder, so that I wasnt modifying my original downloads.
I decided that since I had read about people doing this successfully before Odin could read lz4 compression, here on xda I found a tool and removed that compression. Since marshmallow uses img but oreo uses bin files, I then found another thread that states that you can simply rename the file with extensions visible to convert them from .bin to a regular .img, like marshmallow uses. I did this for all the oreo files, replacing only the system.img with the marshmallow one, removing the oreo one to another folder for now. (The only thing im still debating is if i should have gone the other way, and renamed the marshmallow system.img into a .bin file instead. If I try and it fails, that may be my next attempt.) I was then able to use another tool I found here on xda to take the new tar files I made and replace the .md5 extension and recompressed my new editions. There were a few folders within these tar files originally (Meta data was one) that I simply left alone but included in the same tar file that they were in before.
The only thing ive yet to do is actually try to flash them. But, if Ive read everything properly, they are ready to flash. Im only nervous to find out if the absolute worst case if it doesnt work is it will give me some kind of error. the only one i didnt bother with was home_CSC since that 1 is only for restoring with your files present, and im looking to start from scratch, so ill keep those removed from the mix.
so basically the only thing i changed was bin files to img files, and removed the oreo system.img and put the marshmallow system.img in its place. Im wondering now if i should go back and change those files back to .bin extensions. Then that way nothing crutial can screw up? hmm.... but im *almost* there.
ETA: So I just decided to go through everything once more, and decided to keep certain files as bin files like original, and the other files as img, as they were originally within the oreo rom. I was mistakenly thinking that all files had to be either img or bin, but upon another check through i did notice that the file type within the same rom can vary. I feel better about that now Still just working on the courage to flash it. I didnt truly edit any of the files. I only either renamed the extension thereby converting types of files. otherwise i only decompressed and then recompressed things. I didnt do any true open notepad and edit type stuff. Just sticking with the basics here
Pawprints1986 said:
Okay, so upon some more research, and finding a couple of tools here on xda, heres what ive been able to do.
Before I did anything I made copies of both roms in a separate new folder, so that I wasnt modifying my original downloads.
I decided that since I had read about people doing this successfully before Odin could read lz4 compression, here on xda I found a tool and removed that compression. Since marshmallow uses img but oreo uses bin files, I then found another thread that states that you can simply rename the file with extensions visible to convert them from .bin to a regular .img, like marshmallow uses. I did this for all the oreo files, replacing only the system.img with the marshmallow one, removing the oreo one to another folder for now. (The only thing im still debating is if i should have gone the other way, and renamed the marshmallow system.img into a .bin file instead. If I try and it fails, that may be my next attempt.) I was then able to use another tool I found here on xda to take the new tar files I made and replace the .md5 extension and recompressed my new editions. There were a few folders within these tar files originally (Meta data was one) that I simply left alone but included in the same tar file that they were in before.
The only thing ive yet to do is actually try to flash them. But, if Ive read everything properly, they are ready to flash. Im only nervous to find out if the absolute worst case if it doesnt work is it will give me some kind of error. the only one i didnt bother with was home_CSC since that 1 is only for restoring with your files present, and im looking to start from scratch, so ill keep those removed from the mix.
so basically the only thing i changed was bin files to img files, and removed the oreo system.img and put the marshmallow system.img in its place. Im wondering now if i should go back and change those files back to .bin extensions. Then that way nothing crutial can screw up? hmm.... but im *almost* there
Click to expand...
Click to collapse
I'm not sure about changing back to bin files or not. You could always make a copy that is not converted and a copy that is converted.
I can't say that I'm 100% certain about this, but..
As long as you are working with stock files and followed instructions, you shouldn't cause any real permanent damage but you might get errors of some kind, those might be correctable. You might cause a soft brick or have to restore the device by some complex processes but it should be restorable, sometimes its tough to restore but can be done.
I would look for information about whether the question about bin vs img is a valid question and what potential problems it can cause.
Sent from my LGL84VL using Tapatalk
Droidriven said:
I'm not sure about changing back to bin files or not. You could always make a copy that is not converted and a copy that is converted.
I can't say that I'm 100% certain about this, but..
As long as you are working with stock files and followed instructions, you shouldn't cause any real permanent damage but you might get errors of some kind, those might be correctable. You might cause a soft brick or have to restore the device by some complex processes but it should be restorable, sometimes its tough to restore but can be done.
I would look for information about whether the question about bin vs img is a valid question and what potential problems it can cause.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
This is becoming so beyond frustrating... I went though tonight, deleted my previously modified files... I wanted to go through and only undo the lz4, without all that renaming I had done. Did that just fine.
Gather up the guts to finally try it in odin though? Well, i dont even know what the error is. In odin 3.13, it gets to "file analysis" and just sits there. I unplugged and was still even able to restart the device back in to the oreo that was still on it, it did nothing at all. So i did a little bit of searching and it seems that an older version of odin fixes this. So i downloaded the recommended 3.09... Odin gets to the same point and then the program straight up shuts down! Ive even tried compatibility mode for windows 7 thinking maybe. I had ran it as administrator each time.
so the phone is fine.... but i cant get the program to even try it let alone give me any kind of error to work with....
ive given up for tonight!
The other idea i had was to check "phone bootloader update" in odin and just try to flash the straight up marshmallow rom, but googling that gets mixed results.