I need to take my Photon Q back to stock. I'm currently running CM11, cm-11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl.zip. I might need to switch to T-mobile, they would buy my phone from me, but I want it to look like it hasn't been rooted. Is there anyway to take it back to stock and remove the "unlocked bootloader" warning yet? I'm not sure how to use RSD Lite. I didn't find any instructions/tutorials. I did watch a youtube video on using RSD Lite for the Motorola Atrix. I have RSDLite 5.7. Any and all help would be appreciated.
Have you tried using it?
I thought it was pretty straightforward. Just make sure you do the proper adjustments to the XML file in order to get it to flash properly.
As for getting rid of the unlocked bootloader logo, you can just flash another bootloader logo - even the original if you want. Boot Logos (Unlocked Bootloader Warning)
arrrghhh said:
Have you tried using it?
I thought it was pretty straightforward. Just make sure you do the proper adjustments to the XML file in order to get it to flash properly.
As for getting rid of the unlocked bootloader logo, you can just flash another bootloader logo - even the original if you want. Boot Logos (Unlocked Bootloader Warning)
Click to expand...
Click to collapse
I tried RSDLite 5.7 today on another computer running windows 7 and it did not detect my phone in fastboot mode. I just tried connecting my phone to my computer running Windows Vista and it did detect it with both RDSLite 5.3 and 5.7. In RSDLite 5.7 under status it said connected. Model was listed as Fastboot ASANTI_CS, Port No 1, Port Type USB, IMEI/ESN/MEID was listed as N/A. Under Device Properties everything is listed as N/A including: ESN, Technology, Software Version, Flex Version, Bootloader Version, and DRM Version. I downloaded the firmware version Android 4.1.2
Blur_Version.98.10.5.XT897.Sprint.en.US.
I watched this video http://www.youtube.com/watch?v=bu90DEC0Mxg to see how to use RSD Lite. The video shows how to flash the Motorola Atrix. Would the process be basically the same as the Photon Q?
EpicSaga said:
I tried RSDLite 5.7 today on another computer running windows 7 and it did not detect my phone in fastboot mode. I just tried connecting my phone to my computer running Windows Vista and it did detect it with both RDSLite 5.3 and 5.7. In RSDLite 5.7 under status it said connected. Model was listed as Fastboot ASANTI_CS, Port No 1, Port Type USB, IMEI/ESN/MEID was listed as N/A. Under Device Properties everything is listed as N/A including: ESN, Technology, Software Version, Flex Version, Bootloader Version, and DRM Version. I downloaded the firmware version Android 4.1.2
Blur_Version.98.10.5.XT897.Sprint.en.US.
I watched this video http://www.youtube.com/watch?v=bu90DEC0Mxg to see how to use RSD Lite. The video shows how to flash the Motorola Atrix. Would the process be basically the same as the Photon Q?
Click to expand...
Click to collapse
I'm not sure I've never used an Atrix.
As for the version of RSD, try a newer one. I believe I was using 6.1.5 back when I originally got the phone in 2012.
I tried RSDLite 6.1.6 and 6.1.5 with the MTK patch with my phone in fastboot mode, but there was no change. Both times it came up as "connected" under status in RSD Lite, but everything else was listed as N/A in the above box under device properties.
EpicSaga said:
I tried RSDLite 6.1.6 and 6.1.5 with the MTK patch with my phone in fastboot mode, but there was no change. Both times it came up as "connected" under status in RSD Lite, but everything else was listed as N/A in the above box under device properties.
Click to expand...
Click to collapse
Did you try flashing it? Did you make the necessary adjustments to the XML file?
arrrghhh said:
Did you try flashing it? Did you make the necessary adjustments to the XML file?
Click to expand...
Click to collapse
What adjustments do I make to the XML file? With my phone in fastboot flash mode, do I put the file asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml in the filename box in RSD Lite? When I select that it says "This may take a while to decompress. Continue?". The Options are "Decompress Only" and "Decompress And Start Flashing". Once it's in stock mode again, can I put the original stock image on even though it won't be rooted?
EpicSaga said:
What adjustments do I make to the XML file? With my phone in fastboot flash mode, do I put the file asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml in the filename box in RSD Lite? When I select that it says "This may take a while to decompress. Continue?". The Options are "Decompress Only" and "Decompress And Start Flashing". Once it's in stock mode again, can I put the original stock image on even though it won't be rooted?
Click to expand...
Click to collapse
I assume you read the post where you downloaded the FXZ file?
Skrilax_CZ said:
NOTES
- use at least RSD Lite 6.1.5 (maybe 6.1.x will work too) or you get an error on flashing system.img.ext4
- you may have to open the zip and edit the xml, and delete the 2 lines "<step operation="getvar" var="max-download-size" />" if you get unknown command fastboot getvar max-download-size
- do not flash Sprint firmware to phone from Cellular US and vice versa unless you know what are you doing!!!
Click to expand...
Click to collapse
arrrghhh said:
I assume you read the post where you downloaded the FXZ file?
Click to expand...
Click to collapse
I missed that. There was a death in my family a few weeks ago and everything has been hectic. I've been trying to stay on top of this the best that I can. I just don't know what some of these things are when it comes to flashing and what not. I'm not sure how to use RSDLite. I'm going to use 6.1.6. RSDLite 6.1.6 recoqnizes my phone. I saw that 6.1.5 needs an MTK Patch. What is and MTK Patch? I have to give my phone to T-Mobile either today, tomorrow, or Tuesday at the latest. What is the fastest way to take a Photon Q back to stock and get rid of the bootoader unlocked screen so it returns to looking normal.
EpicSaga said:
I missed that. There was a death in my family a few weeks ago and everything has been hectic. I've been trying to stay on top of this the best that I can. I just don't know what some of these things are when it comes to flashing and what not. I'm not sure how to use RSDLite. I'm going to use 6.1.6. RSDLite 6.1.6 recoqnizes my phone. I saw that 6.1.5 needs an MTK Patch. What is and MTK Patch? I have to give my phone to T-Mobile either today, tomorrow, or Tuesday at the latest. What is the fastest way to take a Photon Q back to stock and get rid of the bootoader unlocked screen so it returns to looking normal.
Click to expand...
Click to collapse
I apologize for your loss, but I'm unsure how else to help.
RSD Lite is the easiest way to get back to the stock ROM. The formerly linked thread about boot logos will help you get rid of the 'Unlocked bootloader' warning.
Good luck, let us know where you get stuck.
arrrghhh said:
I apologize for your loss, but I'm unsure how else to help.
RSD Lite is the easiest way to get back to the stock ROM. The formerly linked thread about boot logos will help you get rid of the 'Unlocked bootloader' warning.
Good luck, let us know where you get stuck.
Click to expand...
Click to collapse
I can't remember where I downloaded the FXZ file. Do I need to change any of the settings in RSD Lite or have the MTK Patch? It's version 6.1.6, I did not see that I needed an MTK Patch. If I have this right, the file asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml has to be changed. I unzipped the asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml file on my computer. I opened the unzipped folder. I clicked "Open" on the XML document and got an error. I clicked "edit" and then edited the xml document and deleted the 2 lines "<step operation="getvar" var="max-download-size" />". Now I can open the XML document by clicking "Open". Should I put the new xml document in the filename box in RSD Lite or rezip the whole folder, asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml and then put the zipped folder in the filename box in RSD Lite?
EpicSaga said:
I can't remember where I downloaded the FXZ file. Do I need to change any of the settings in RSD Lite or have the MTK Patch? It's version 6.1.6, I did not see that I needed an MTK Patch. If I have this right, the file asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml has to be changed. I unzipped the asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml file on my computer. I opened the unzipped folder. I clicked "Open" on the XML document and got an error. I clicked "edit" and then edited the xml document and deleted the 2 lines "<step operation="getvar" var="max-download-size" />". Now I can open the XML document by clicking "Open". Should I put the new xml document in the filename box in RSD Lite or rezip the whole folder, asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml and then put the zipped folder in the filename box in RSD Lite?
Click to expand...
Click to collapse
Pull the .xml out, make the changes, put it back in the .zip, feed the .zip into RSD Lite. 6.1.6 should be fine, that seems to be the latest.
I'm not positive what the MTK patch is, but as you stated it only seems to be needed for 6.1.5. If you're using 6.1.6 there shouldn't be anything additional needed.
arrrghhh said:
Pull the .xml out, make the changes, put it back in the .zip, feed the .zip into RSD Lite. 6.1.6 should be fine, that seems to be the latest.
I'm not positive what the MTK patch is, but as you stated it only seems to be needed for 6.1.5. If you're using 6.1.6 there shouldn't be anything additional needed.
Click to expand...
Click to collapse
I think I have the correct changes made to the .xml file. According to your post quoting Skrilax_CZ, it requires deleting the 2 lines "<step operation="getvar" var="max-download-size" />" . I did that. The layout of the .xml document changed. Then I zipped the .xml back to a zipped folder. I fed it into RSD Lite 6.1.6. A box that read "Compressing" came up and read "This may take a while to decompress. Continue?". The options were "Decompress Only", "Decompress And Start Flashing", and Cancel. Does it sound right so far? Which one would I select, and what should happen next? Thank you.
I simply decompressed the whole zip in a folder and modified the xml.
Then I select the .xml file (with changes made by me) in RSD Lite and it flashed.
What I want to say, you don't need to compress etc. again, it's enough to decompress one time, then change and flash.
(Nobody would really archive a modified FXZ file.)
edit: You can choose (in RSD Lite) Decompress and start flashing. Flashing is what you want to do.
EpicSaga said:
I think I have the correct changes made to the .xml file. According to your post quoting Skrilax_CZ, it requires deleting the 2 lines "<step operation="getvar" var="max-download-size" />" . I did that. The layout of the .xml document changed. Then I zipped the .xml back to a zipped folder. I fed it into RSD Lite 6.1.6. A box that read "Compressing" came up and read "This may take a while to decompress. Continue?". The options were "Decompress Only", "Decompress And Start Flashing", and Cancel. Does it sound right so far? Which one would I select, and what should happen next? Thank you.
Click to expand...
Click to collapse
Well if you select "Decompress only" then it would only decompress... it wouldn't flash to the phone. You'd have to then select another option to flash it. May as well just select "Decompress and start flashing"...
I'm not sure what the issue is, it seems like you are on the right track. This software is very straightforward to use, there's not many "wrong" ways you can use it - just let the process finish, do NOT for any reason interrupt it once it has started flashing. That is about the only thing you could do "wrong", is interrupting the process once it has started.
Loader009 said:
I simply decompressed the whole zip in a folder and modified the xml.
Then I select the .xml file (with changes made by me) in RSD Lite and it flashed.
What I want to say, you don't need to compress etc. again, it's enough to decompress one time, then change and flash.
(Nobody would really archive a modified FXZ file.)
Click to expand...
Click to collapse
This method also works, apologies for not mentioning it. I've only used RSD Lite a few times myself, and I usually just extracted the .xml file and put it back in the .zip. Either way if you decompress it or RSD Lite decompresses it, the result is the same.
arrrghhh said:
Well if you select "Decompress only" then it would only decompress... it wouldn't flash to the phone. You'd have to then select another option to flash it. May as well just select "Decompress and start flashing"...
I'm not sure what the issue is, it seems like you are on the right track. This software is very straightforward to use, there's not many "wrong" ways you can use it - just let the process finish, do NOT for any reason interrupt it once it has started flashing. That is about the only thing you could do "wrong", is interrupting the process once it has started.
This method also works, apologies for not mentioning it. I've only used RSD Lite a few times myself, and I usually just extracted the .xml file and put it back in the .zip. Either way if you decompress it or RSD Lite decompresses it, the result is the same.
Click to expand...
Click to collapse
I edited the xml file. I zipped the folder that I unzipped to edit the .xml file. I'm going to put the zipped folder in rsd lite and select "Decompress And Start Flashing".
After this takes it back to stock, is it possible to take the unlocked bootloader warning away with the stock logo? I went to the link you posted http://forum.xda-developers.com/showthread.php?t=1873834 and it says to use fastboot. On the page where the stocklogo file is http://forum.xda-developers.com/showpost.php?p=37631178&postcount=38 it says to open the logo.bin with hex editor. Where is the hex editor? It says to swap the two identifiers and then DL in attachment. Does that mean download in attachment? If so, how do I do that?
EpicSaga said:
I edited the xml file. I zipped the folder that I unzipped to edit the .xml file. I'm going to put the zipped folder in rsd lite and select "Decompress And Start Flashing".
After this takes it back to stock, is it possible to take the unlocked bootloader warning away with the stock logo? I went to the link you posted http://forum.xda-developers.com/showthread.php?t=1873834 and it says to use fastboot. On the page where the stocklogo file is http://forum.xda-developers.com/showpost.php?p=37631178&postcount=38 it says to open the logo.bin with hex editor. Where is the hex editor? It says to swap the two identifiers and then DL in attachment. Does that mean download in attachment? If so, how do I do that?
Click to expand...
Click to collapse
I think you're reading too much into that post.
Just take the .zip file, extract the .bin file and flash the .bin file with fastboot per the post, "fastboot flash logo stocklogo_swapped.bin".
I put the Zipped file in RSD Lite. I selected "Decompress And Start Flashing", but then I got this, "Error!!!!!
Failed to create
Please check if the file path is too long to create or if there is enough free disk space."
I'm not sure if I need to rename the Zipped file to something shorter, or what.
EpicSaga said:
I put the Zipped file in RSD Lite. I selected "Decompress And Start Flashing", but then I got this, "Error!!!!!
Failed to create
Please check if the file path is too long to create or if there is enough free disk space."
I'm not sure if I need to rename the Zipped file to something shorter, or what.
Click to expand...
Click to collapse
Hm not sure I've heard of this error. Try Loader009's method of extracting the .zip to a folder and feeding RSD Lite the .xml file.
arrrghhh said:
Hm not sure I've heard of this error. Try Loader009's method of extracting the .zip to a folder and feeding RSD Lite the .xml file.
Click to expand...
Click to collapse
Success! I used Loader009's method and it worked! Now I only have to flash the stock logo. Should I open up the adt-bundle and use fastboot from there?
Related
The Restore images now don,t have a .bat file to auto flash, now have a .xml file, for what? now this have mess up my tool and i don't know foer wath is the .xml file!! any help is very appreciated..
alonsoch said:
The Restore images now don,t have a .bat file to auto flash, now have a .xml file, for what? now this have mess up my tool and i don't know foer wath is the .xml file!! any help is very appreciated..
Click to expand...
Click to collapse
In this case you must use rsd lite. It works good.
In gpe there is still a bat.
But in the other cases you can make a .bat starting from .xml and .bat of gpe version for example. Look the structure, it's always the same.
If you can't make that .bat then use rsd lite with xml, the official app from motorola.
Here's the direct link for the 20a Oreo OTA update bin file used for LG V20 VS995. Not sure if it's of any use, just wanted to have some fun trying to find it
https://cdn.vzwdm.com/LG_VS995_1CA_20a_03.bin
If anyone finds a way to extract the contents let me know. Can't figure it out :/
If you already have TWRP and want a flashable zip, have a look at NotYetADev's post.
https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
Thank you for posting this!!!
Change the file extension to .up, then the oreo upgrade can be flashed using the LGUP tool!
0) Make sure your phone already has the 1CA update
1) Connect your phone via USB and select the "File Transfer" mode
2) Run LGUP
3) Select the FOTA option and select the LG_VS995_1CA_20a_03.up file
4) Upgrade!
And thank you for that little piece of info. I didn't know LG UP could flash OTA bin files. That is another attack vector
-- Brian
justmike80386 said:
Thank you for posting this!!!
Change the file extension to .up, then the oreo upgrade can be flashed using the LGUP tool!
0) Make sure your phone already has the 1CA update
1) Connect your phone via USB and select the "File Transfer" mode
2) Run LGUP
3) Select the FOTA option and select the LG_VS995_1CA_20a_03.up file
4) Upgrade!
Click to expand...
Click to collapse
I need you to sniff flashing that. Are you at all familiar with USB packet capture? I would flash it, but I have nothing to flash it on.
If not, I can walk you though it.
This file is not signed, it appears to have an unlock key. By unlock key -- I mean a key that unlocks lafd so that it will flash anything.
Now none of this matters on the V20, but for folks that have other LG devices, it will help out a LOT.
-- Brian
runningnak3d said:
I need you to sniff flashing that. Are you at all familiar with USB packet capture? I would flash it, but I have nothing to flash it on.
If not, I can walk you though it.
This file is not signed, it appears to have an unlock key. By unlock key -- I mean a key that unlocks lafd so that it will flash anything.
Now none of this matters on the V20, but for folks that have other LG devices, it will help out a LOT.
-- Brian
Click to expand...
Click to collapse
How do you know the file isn't signed? I assumed it had the same type of validation as the KDZ files.
I'd be happy to share a USB capture, is that something wireshark can do?
---------- Post added at 01:03 AM ---------- Previous post was at 12:05 AM ----------
I'm sure there is some magic hash hidden somewhere in the file. I'll see if it's possible to flash an edited .up file.
I guess I should rephrase that. It isn't signed in the normal way that a KDZ is signed -- with a SIGN payload. There are hashes for the partitions, but there doesn't appear to be anything to check the integrity of the file itself.
I am still tearing it apart, but without seeing a packet capture of LG UP flashing it, it is kinda pointless. If I had to guess, this file is flashed using RSVD IDDD (indirect flashing). If that is the case, having a full dump of exactly how that is done would be awesome.
Maybe I am wrong, and there is some other opcode that I have no idea what it does that sends a signature that I don't recognize -- because I have never seen it.
EDIT: sorry, I guess I should link to the instructions. You actually don't have to install Wireshark (unless you want to look at the capture): link.
If you install USBPcap using those instructions, then you will be left with Wireshark compatible pcap files that you can zip up and send to me (do NOT post them publicly, they will contain info that is specific to your device).
EDIT2: OK, just digging a little more and there is a zip contained within the file that is signed (the same way a normal OTA update.zip is signed). However, lafd doesn't have those keys, and has no way to deal with a signed zip. That only comes into play when flashed through stock recovery -- so the question remains, how does LG UP get this file onto the phone without verifying its integrity? Again, just to be clear, there ARE hashes that verify the partitions being flashed aren't corrupt. However, there doesn't appear to be anything to prevent modifying the file, and then modifying the hashes to match when flashed through laf -- recovery most definitely verifies the integrity of the file.
-- Brian
I'll capture the flash when I got home
here are links for the other OTA updates, in case anyone is interested.
Code:
VS99512A_06 -> VS99513A_04
https://cdn.vzwdm.com/LG_VS995_12A_13A_04.bin
VS99513A_04 -> VS99514B_00
https://cdn.vzwdm.com/LG_VS995_13A_14B_00.bin
VS99514B_00 -> VS99515A_10
https://cdn.vzwdm.com/LG_VS995_14B_15A_10.bin
VS99515A_10 -> VS99516B_00
https://cdn.vzwdm.com/LG_VS995_15A_16B_00.bin
VS99516B_00 -> VS99517A_00
https://cdn.vzwdm.com/LG_VS995_16B_17A_00.bin
VS99517A_00 -> VS99518A_00
https://cdn.vzwdm.com/LG_VS995_17A_18A_00.bin
VS99518A_00 -> VS99519A_10
https://cdn.vzwdm.com/LG_VS995_18A_19A_10.bin
VS99519A_10 -> VS9951AA_01
https://cdn.vzwdm.com/LG_VS995_19A_1AA_01.bin
VS9951AA_01 -> VS9951BA_01
https://cdn.vzwdm.com/LG_VS995_1AA_1BA_01.bin
VS9951BA_01 -> VS9951CA_01
https://cdn.vzwdm.com/LG_VS995_1BA_1CA_01.bin
VS9951CA_01 -> VS99520A_03
https://cdn.vzwdm.com/LG_VS995_1CA_20a_03.bin
runningnak3d said:
I guess I should rephrase that. It isn't signed in the normal way that a KDZ is signed -- with a SIGN payload. There are hashes for the partitions, but there doesn't appear to be anything to check the integrity of the file itself.
I am still tearing it apart, but without seeing a packet capture of LG UP flashing it, it is kinda pointless. If I had to guess, this file is flashed using RSVD IDDD (indirect flashing). If that is the case, having a full dump of exactly how that is done would be awesome.
Maybe I am wrong, and there is some other opcode that I have no idea what it does that sends a signature that I don't recognize -- because I have never seen it.
EDIT: sorry, I guess I should link to the instructions. You actually don't have to install Wireshark (unless you want to look at the capture): link.
If you install USBPcap using those instructions, then you will be left with Wireshark compatible pcap files that you can zip up and send to me (do NOT post them publicly, they will contain info that is specific to your device).
EDIT2: OK, just digging a little more and there is a zip contained within the file that is signed (the same way a normal OTA update.zip is signed). However, lafd doesn't have those keys, and has no way to deal with a signed zip. That only comes into play when flashed through stock recovery -- so the question remains, how does LG UP get this file onto the phone without verifying its integrity? Again, just to be clear, there ARE hashes that verify the partitions being flashed aren't corrupt. However, there doesn't appear to be anything to prevent modifying the file, and then modifying the hashes to match when flashed through laf -- recovery most definitely verifies the integrity of the file.
-- Brian
Click to expand...
Click to collapse
I've got the USB capture for you and any other developers who're interested.
I will download it just as soon as I get to work. Thanks
-- Brian
justmike80386 said:
Thank you for posting this!!!
Change the file extension to .up, then the oreo upgrade can be flashed using the LGUP tool!
0) Make sure your phone already has the 1CA update
1) Connect your phone via USB and select the "File Transfer" mode
2) Run LGUP
3) Select the FOTA option and select the LG_VS995_1CA_20a_03.up file
4) Upgrade!
Click to expand...
Click to collapse
I cannot upgrade this way. It says Error MTP is not running, even if it is in File Transfer mode. I got one time in FOTA Easy Upgrade but noting happened.
scytalemk said:
I cannot upgrade this way. It says Error MTP is not running, even if it is in File Transfer mode. I got one time in FOTA Easy Upgrade but noting happened.
Click to expand...
Click to collapse
I have same error
scytalemk said:
I cannot upgrade this way. It says Error MTP is not running, even if it is in File Transfer mode. I got one time in FOTA Easy Upgrade but noting happened.
Click to expand...
Click to collapse
is this on a rooted or unrooted phone? I was able to do this twice using the stock KDZ files for my base system with no issues.
justmike80386 said:
is this on a rooted or unrooted phone? I was able to do this twice using the stock KDZ files for my base system with no issues.
Click to expand...
Click to collapse
Step by Step
1. Add Extension file .up
2. Install LG UP MOD
3. Turn on USB Debugging in your phone and make sure your phone allow PC adb command via USB (adb devices > enter)
4. Open LG UP Mod, Choose file .up (step 1). Choose OTA Upgrade and START.
Note: backup your data before upgrade, maybe failed to upgrade and lost data
I'm from Viet Nam, sorry for bad English
I want to be able to root after erecovery and update to latest version. I know magisk can patch boot img for reflashing via fastboot.
Question is, how to extract original boot img?
I know there are tutorials, but they reference specific block that seems to be device dependent. Or am I making it too complicated?
papashex said:
I want to be able to root after erecovery and update to latest version. I know magisk can patch boot img for reflashing via fastboot.
Question is, how to extract original boot img?
I know there are tutorials, but they reference specific block that seems to be device dependent. Or am I making it too complicated?
Click to expand...
Click to collapse
You need the UPDATE.APP for the boot img.
You can find in Huawei Firmware Finder for your Version,download the Update.zip and unzip,inside is the UPDATE.APP.
Extract UPDATE.APP with Huawei Extractor https://forum.xda-developers.com/showthread.php?t=2433454
Copy extracted Boot on your Phone and install Magisk and Patch the File
The patched File save Magisk on internal Memory,copy on your Pc and flash via Fastboot.
Your Bootloader must be unlocked!
Thanks for the run down. I'll give it a go.
Looks like I need a note 10 profile for Huawei extractor. Anyone have that available?
papashex said:
Looks like I need a note 10 profile for Huawei extractor. Anyone have that available?
Click to expand...
Click to collapse
Do you have errors while unzipping?
Use this setting!
letschky said:
Do you have errors while unzipping?
Use this setting!
Click to expand...
Click to collapse
Yes, that's what I use with the unknown profile. I receive this error.
EDIT: I downloaded another file 8.2.0.158 and get same error, just different indices. I don't know if it makes a difference but most of the files found in FF are for C00B. My system info shows only C00. Could that be relevant?
papashex said:
Yes, that's what I use with the unknown profile. I receive this error.
EDIT: I downloaded another file 8.2.0.158 and get same error, just different indices. I don't know if it makes a difference but most of the files found in FF are for C00B. My system info shows only C00. Could that be relevant?
Click to expand...
Click to collapse
this generally works with Huawei,i use it with Note 10,Note 8,Honor View 10,Mediapad M3....
is Net Framework 4.6.1 installed on your Pc?
papashex said:
Yes, that's what I use with the unknown profile. I receive this error.
EDIT: I downloaded another file 8.2.0.158 and get same error, just different indices. I don't know if it makes a difference but most of the files found in FF are for C00B. My system info shows only C00. Could that be relevant?
Click to expand...
Click to collapse
Same Problem in 181 ,but in Settings uncheck :
1:Verify header checksum
and
2:Verifiy file checksum
Unchecking the 2 checksum checks you asked me to check opens up the update.app app-ropriately.
(couldn't resist )
Thanks for the help.
Baby stepping is driving me nuts.
I'm able to extract the update.app file but there is no "boot.img" in the several archives I looked at. Does it go by a different name? list attached.
papashex said:
Baby stepping is driving me nuts.
I'm able to extract the update.app file but there is no "boot.img" in the several archives I looked at. Does it go by a different name? list attached.
Click to expand...
Click to collapse
Ramdisk.img
I've finally had a moment to sit down and put it all together. Got my latest stock oreo rom rooted. Feel confident I can do PIE if it ever shows up for me in the US. Thanks for the tutorial Letschky.
As luck would have it, PIE update arrived after tweaking up the rooted Oreo. Ready to root PIE, but there is no "ramdisk.img" in my downloaded 9.0.0.181 archive.
Has the name changed for PIE or is it a bad archive?
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
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.