Related
Hello XDA, I'm kind of new to ROMs etc. and would appreciate some help. I am trying to install mikegapinski's 2.3.7 ROM (v5) through fastboot and whereas in the past I have seen a boot.img and a system.img, there is a boot.img and a system folder. Is there a way to make the folder into a system.img file that I could flash onto my GT540?
In short, how do you make a system.img file out of a folder with system files in them?
hey there !
(system.img + boot.img) is for fastboot
fastboot flash boot boot.img
fastboot flash system system.img
and the (system folder + boot.img) is for recovery
use any recovery
select zip from sdcard
select the zip
i dont think you can convert the folder to a .img(or the other way around) . and if the rom you are talking about mike's aosp v5 then i wont recommend it as for now there are problems with the ram and so it becomes very laggy. i would recommend mur4iks swiftdroid asis but the choice is yours
I know you can 'extract' images using 'unyaffs' but I never made an image from a folder (except when dumping partitions). I think there is a way though.
If you have Linux on your PC, then you can use the 'yaffs' tool. Search it on Google.
This is how even AOSP compiles system folder into system.img
Sent from my LG GT540 Swift using XDA App
I list found this. Should work!
http://db.tt/ROQSWTW6
Sent from my LG GT540 Swift using Tapatalk
can someone please help me to make system.img from system extraxted folder.
my phone its dead and i can find right rom for it
allway hang on boot logo
Please
link for download
https://www.dropbox.com/s/c99ashouw0fb4hp/system.rar
PS
will if neeed no problem
I got it. If you use Linux, you can create an iso file of the system folder, and then convert it to .img. Just follow it:
In a terminal(CTRL+ALT+T):
Code:
mkisofs -o /path/to/the/system/folder ~/system.iso
dd if=~/system.iso of=~/system.img
rm ~/system.iso
Your system.img will be on your home directory.
and it work's too ? (when you flash it from fastboot)
y2yu said:
can someone please help me to make system.img from system extraxted folder.
my phone its dead and i can find right rom for it
allway hang on boot logo
Please
link for download
https://www.dropbox.com/s/c99ashouw0fb4hp/system.rar
PS
will if neeed no problem
Click to expand...
Click to collapse
pls if you find a solutuon please pm me. And do you think flashing the system.img will solve booting probz?
suggestion
take a look at this url, and examine the zip file contained.
you could boot into cwm and install the zip (not suggesting, its what i did)
if u make a zip file in the same layout you could install your zip and it will update the system partition.
as you have a desire, heres whats required
on phone: place phone into fastboot mode
on computer: unzip to a folder , place the img file in such folder,
open a command prompt, (navigate to folder using the cd command)
and type: fastboot boot bravo-cwm.img
mount sd card, toggle usb storage, place your zip in root of sdcard.
then untoggle, go back, select option to install zip from sdcard.
choose select zip file.
find your zip.
tap on the file, and it will install...
you SHOULD by this point have an updated phone as you desired (lol)
if it does not work as you expected, have a look for a standard system.img for your phone, and put that into a zip
name the zip (i put it in caps, weather needed i dont know) PM99IMG.zip
place it into root of sdcard, and put phone into the first screen of recovery menu, the white screen.
it will analyze your zip and ask you to install, press up to flash and then the required option to reboot when its done to revert your phone back to normal.
hope this helps there buddy,
ill most likley forget to check back, so if u need any help pm me and ill see what i can do,
Is this working
Edu_Renesto said:
I got it. If you use Linux, you can create an iso file of the system folder, and then convert it to .img. Just follow it:
In a terminal(CTRL+ALT+T):
Code:
mkisofs -o /path/to/the/system/folder ~/system.iso
dd if=~/system.iso of=~/system.img
rm ~/system.iso
Your system.img will be on your home directory.
Click to expand...
Click to collapse
HI Bro,
Is the output file system.img after flash into the rom?
phone stuck in usb logo... i have zenfone 4
Yaffey for Windows Might Help
tejasjadhav said:
If you have Linux on your PC, then you can use the 'yaffs' tool. Search it on Google.
This is how even AOSP compiles system folder into system.img
Sent from my LG GT540 Swift using XDA App
Click to expand...
Click to collapse
And if you have Windows on your PC, try Yaffey! http://www.xda-developers.com/yaffey-for-all-your-yaffs2-needs/
Huawei Honor 7
– Complete Guide For Beginners –
Optimized For (PLK-L01)
Updating | Rooting | Tweaking | Fixing
In this guide, you will learn the following:
Part I - How to install the latest full ROM for Huawei Honor (PLK-L01).
Part II - How to root Huawei Honor 7.
Part III - How to fix bootloops if things did not go as expected.
Part IV - The most used adb commands.
Part V - The most used fastboot commands.
Part VI - How to change the default boot animation.
Part VII - How to change the default splash screen.
Appendix A - Honor 7 Key Combinations Summary.
Appendix B - How to update Huawei Honor 7 from (B100) to (B180).
Appendix C - Available Custom ROM(s).
Appendix D - Extra Resources.
Appendix E - All Important Downloads.
Notes & Credits:
This guide is written for the absolute beginners who had hard times reading other tutorials on this forum that explains the same set of topics.
This guide is primary written for Microsoft Windows users. Many sections though can be applied to other operating systems.
There are other great guides on this forum that teaches the same stuff but not in a very detailed beginner-friendly way. Special credits go to @piskr for his guide on this topic.
Additional credits go to @DigiGoon and @sminki for their contribution on fixing and updating this guide.
Special credits go to @Ziolek67 and @Kostyan_nsk for their original posts on the splash screen topics.
Special thanks to the Labinator team for their support throughout this guide.
If you have something to add or improve on this guide, please reply to this post and we will be more than happy to update it.
Warning: No one is responsible for what happens to your device while attempting to follow the below guide. Create backups before every section and know the risks before starting out.
Part I - How To Install The Latest Full ROM For The Model (PLK-L01)
Step 1: Download the latest full ROM for Honor 7 from the below link:
http://www.modaco.com/forums/topic/375942-roms-honor-7-stock-rom-images/
Step 2: Extract the (.zip) file and copy the "UPDATE.app" file to your (dload) folder in your external SD card.
Step 3: Make sure the current recovery that is installed is the default stock one and not a custom recovery like TWRP. If you have TWRP installed, make sure to flash the stock recovery before you attempt the update process.
Step 4: Turn off your phone, then press both the Volume Up + Volume Down + Power Key. Then release the power key as soon as you see the initial splash screen.
Step 5: The Huawei eRecovery will start and will update your device from the "UPDATE.app" file that you had placed in your (dload) folder automatically.
Part II - How To Root Huawei Honor 7
Stage 1 – Unlock The Bootloader
Part 1.1 – Getting The Unlock Password
Step 1: Login by clicking here.
Step 2: Click on “Unlock Bootloader”.
Step 3: Accept the unlocking agreement.
Step 4: Fill up the unlock password form as follows:
Product: Smartphone.
Model: (e.g. PLK-L01)
Product Serial Number: Settings -> Status -> Serial Number - > (e.g. H8WDU15814000010)
Product IMEI/MEID (IMEI 1): Settings -> Status -> IMEI1 -> (e.g. 867898020305536)
Product ID: Open the dial up and type: *#*#1357946#*#* -> (e.g. 88429554)
Verification Code: Type the Captcha.
Step 5: Press submit and obtain the unlocking password in red (e.g. 1078018121593242).
Step 6: Store the code obtained in step 5 somewhere safe.
Part 1.2 – Preparations
Step 6: Download and install the latest version of the "15 Seconds ADB Installer”. You can find the download link at >
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Step 7: Download and install the latest version of “HiSuite – Android Smart Device Manager”.
You can find the download link at >
http://consumer.huawei.com/minisite/HiSuite_en/
Step 8: Enable the “Developer options” by going to:
Settings -> About Phone -> Build Number
Tap on the build number 10 times quickly. A message must appear alerting you that the developer mode has been enabled.
Go to the “Developer options” and enable “USB debugging”.
Part 1.3 – Booting into Fastboot Mode
Step 9: Power the phone off.
Step 10: Boot the phone into “fastboot mode” by pressing the below keys.
[Volume Down] + [Tap on Power Button]. You can release the power button as soon as you see the initial splash screen.
Note 1: You must enter the fastboot mode directly after pressing the above keys.
Note 2: In case (Step 10) did not work, then turn off your phone again then insert the USB cable and connect it with your computer. After that, press the same combination mentioned above for 10 seconds. Note 3: You can also boot into the fastboot mode using the following command >
Code:
adb reboot bootloader
Step 11: Connect your phone with your PC. Use a USB cable to connect your phone with your computer while your phone is in the fastboot mode.
Step 12: Open your “Command Prompt (cmd)” and type >
Code:
fastboot devices
Note: The second command must show that your device is in fastboot mode.
Part 1.4 – Perform The Unlock Command
Step 13: Perform the unlock command > fastboot oem unlock ***, where *** is the 16 characters unlock code.
Code:
fastboot oem unlock 1078018121593242
Note: You need of course to replace "1078018121593242" with your unique 16 characters unlock code.
Step 14: Wait for the phone to get unlocked. It will automatically restart if you have entered the correct code.
Step 15: Test if the phone is successfully unlocked by entering the following command >
Code:
fastboot oem get-bootinfo
Case 1: If you have got the message of “Bootloader Lock State: UNLOCKED”, then your phone has been successfully unlocked.
Case 2: If you have got the message of “Bootloader Lock State: LOCKED”, then your phone is still locked.
Note: if you want to re-lock the phone, please check this thread for more details on that. Thanks to @sminki for posting that up and highlighting this point.
Stage 2 – Install Custom Recovery
Step 16: Open your command prompt, and navigate to the right directory where your recovery image file is located. You can do that using this command:
Navigate to the right directory:
[“Directory Letter”]:
Examples: D:, C:, or E:
Navigate to the right folder:
cd [“Full Path Of Directory”]
Example: cd /Users/User1
Step 17: Test if your device is detected by typing the following command while you are in the bootloader mode:
Code:
fastboot devices
> If you got the right messages that your device is properly connected, then you can proceed to step 18.
Step 18: Type the following command to flash the recovery image (TWRP). The recovery image is in English and you can download it from this link. Make sure to download it and place it in the right directory before typing the below command line.
Code:
fastboot flash recovery recovery.img
After the completion of that, simply reboot your device using the following command >
Code:
fastboot reboot
Note: “recovery.img” is the name of the TWRP recovery image. You need to replace this name with the name of your recovery image (e.g. twrp-3.0.2-0-plank.img).
Stage 3 – Root The Device
Step 19: Download the latest SuperSU version from this link and place it on your hard disk then copy it to your phone. You can copy the file from your computer to your device using this command >
Code:
adb push SuperSU-vX.zip /sdcard/
Note 1: You must be in the right directory of the “SuperSU” file or else the above command will not work.
Note 2: You must replace "SuperSU-vX" with the right name of your SuperSU file (e.g. BETA-SuperSU-v2.71-20160331103524.zip)
Step 20: When the process of flashing the recovery is done, reboot your device into the recovery mode using the following command >
Code:
adb reboot recovery
Step 21: After finishing step 20 successfully, your phone would have been booted into the recovery mode. You will be able to see the TWRP home screen. From there, click on the “Install” option then navigate to your /sdcard/ directory where you have copied or pushed your "SuperSU-vX.zip" file.
Step 22: Find the "SuperSU-vX.zip" file and install it.
Step 23: Navigate back to the home page of TWRP then click on the “Reboot” button in order to boot into the system.
Step 24: Double check if your device has been rooted successfully by testing it using one of those root checker applications. There are many of them around the Google Play store.
Part III - Useful ADB Commands
Code:
adb devices
adb reboot
adb reboot bootloader
adb reboot recovery
adb push [source] [destination]
adb pull [source] [destination]
adb backup
adb shell
Part IV - Useful Fastboot Commands
Code:
fastboot devices
fastboot reboot
fastboot reboot-bootloader
fastboot boot recovery recovery.img
fastboot flash [Partition] [Image]
fastboot oem unlock [Unlock Code]
fastboot oem relock [Relock Code]
Note: Use your favorite search engine to search the above commands and learn more about them.
Part V - How To Fix Bootloops
Breaking out of bootloops depends on your device state and what kind of problem you are having. In this section, we are going to focus on the popular case where you can’t access neither the system nor the recovery partitions.
Step 1: Turn off the phone.
Step 2: Press the following buttons:
[Volume Down] + [Tap on Power Button]. You can release the power button as soon as you see the initial splash screen.
Step 3: Head to your computer and download and install the following tool:
http://forum.xda-developers.com/showthread.php?t=2433454
Step 4: Download the latest complete update file (B121) or (B330b) depending on which system you had installed before the bootloop problem. You can download it from:
http://www.modaco.com/forums/topic/375942-roms-honor-7-stock-rom-images-updates-121115-b140/
Then, extract it and get its UPDATE.app file.
Step 5: Use the Huawei Update Extractor to extract the (BOOT.img), (SYSTEM.img), (RECOVERY.img), (CACHE.img), (CUST.img), and (USERDATA.img) from the UPDATE.app file that you have extracted from Step 4.
Step 6: Open your command prompt, and navigate to the right directory where you have extracted the image files. Use the “cd” and “..” commands to do so.
Step 7: Type the following commands and execute them one by one >
Code:
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
Step 8: You can also erase the user data if you like by typing and executing the following >
Code:
fastboot flash userdata USERDATA.img
Step 9: Reboot your device using the following command >
Code:
fastboot reboot
Step 10: You must be able to boot successfully into the system.
Step 11: After booting successfully, apply again the steps mentioned in Part I.
Important Note 1: If the "fastboot flash" is reporting "FAILED <remote: command not allowed>", you need to unlock your device again even if the bootloader is stating that your device has already been unlocked.
Important Note 2: When breaking out of bootloops or frozen splash screens, you need always to flash the right partitions that match up with the previous partitions that you had installed on your system before the occurrence of the bootloop.
Part VI - How To Change The Boot Animation
Step 1: Root Your Device.
Step 2: Create a full Nandroid backup.
Step 3: Create your own animation or download one online. Note that you need the resolution to be (1080 x 1920 pixels). It should not last more than 10-12 seconds at most.
Step 5: Your animation files must be compressed and renamed as: “bootanimation.zip”.
Step 6: Change the permissions of your .zip file to (rw-r-r).
Step 7' - (In case you are running Android 5.x): Navigate to /Cust/Preinstalled/Public/Media and backup the original “bootanimation.zip” file somewhere safe on your hard drive or sdcard.
Step 7'' - (In case you are running Android 6.x): Navigate to /system/etc/media and backup the original “bootanimation.zip” file somewhere safe on your hard drive or sdcard.
Step 8' - (In case you are running Android 5.x): Copy your newly created bootanimation.zip file to the directory /Cust/Preinstalled/Public/Media and replace the original file.
Step 8'' - (In case you are running Android 6.x): Copy your newly created bootanimation.zip file to the directory /system/etc/media and replace the original file.
Step 9: Reboot and check up your new boot animation.
My original post of this section is available at: http://forum.xda-developers.com/showpost.php?p=63828825&postcount=2
Part VII - How To Change The Splash Screen
Requirements:
Your device must be rooted. Follow the steps in Part II in case you have not rooted your device yet.
You must have downloaded and installed the latest version of the "15 Seconds ADB Installer”.
You can find the download link at: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
You need to make a complete backup or a nandroid backup before starting up. You can create a nandroid backup using the custom recovery of TWRP.
Steps:
Turn on your device and connect it to your computer then open the command prompt or your terminal as an administrator.
Make sure your computer can read the data on your phone and all the drivers are installed properly.
Make sure the following command is returning the name of your device:
Code:
adb devices
Save your "oeminfo" to your SDCard:
Code:
adb shell su -c "dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo"
Download this zip file and extract it to your desktop or any location of your choice.
From your opened command prompt, navigate to the extracted zip folder that you have downloaded in Step 5. Use the "cd" command to do that.
Create your new splash screen logo as follows:
Step 1: Open your Adobe Photoshop and create a new file that has the following parameters
Width: 1080 pixels
Height: 1920 pixels
Resolution: 72 pixels/inch
Color Mode: RGB Color, 8-bit
Step 2: After creating your new image, save it as follows:
Extension: *.bmp
From the "Advanced Options", select R5 G6 B5 from the 16-bit depth options.
Save your newly created image in Step 7, in the same folder that you have extracted in Step 5.
From your command prompt, type the following command:
Code:
OEM_logo.exe oeminfo your_logo.bmp
Replace "your_logo.bmp" with the name of your logo.
The above command will create a new oeminfo for you that has your new logo. It will also replace the old one in the same folder.
Copy your newly created oeminfo to your sdcard by typing the following command:
Code:
adb push oeminfo /sdcard/oeminfo
Copy your oeminfo from your sdcard to the right partition on your device:
Code:
adb shell su -c "dd bs=32768 if=/sdcard/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
Reboot your device and check the new splash screen.
Note: The original post of this section can be found at this link.
Credits: Special credits goes to @DigiGoon, @sminki, @Ziolek67, and @Kostyan_nsk for their amazing contribution in writing, testing, and adjusting on the original post of this section of the guide.
Appendix A - Honor 7 Key Combinations Summary
[Without Plugging The Device]:
Volume Down + Tap Power Button -> Normal Boot.
Volume Up + Tap Power Button -> Recovery Mode (e.g. TWRP).
Both Volume Buttons + Tap Power Button -> Flash (dload) Image From External MicroSD Card.
[While Connecting The Device To Your Computer]
Volume Down + Power On -> Fastboot Mode - (Tip: You can exit from this mode with a long power button press).
Volume Up + Power On -> Huawei eRecovery.
Both Volume Buttons + Power On -> Flash Image via HiSuite.
Appendix B - How To Update From B100 to B180
For The Model (PLK-L01)
Important Note: Please update your device before rooting it. You will lose your root access if you attempt to update after rooting your device.
Step 1: Download the latest stock ROM for Honor 7 from the below link:
http://www.modaco.com/forums/topic/375942-roms-honor-7-stock-rom-images/
Step 2: Download the B121 EMUI 3.1 update package.
Step 3: Download the B180 incremental update package (B121 to B180).
Step 4: Extract the B121 update zip file and get the UPDATE.app file from it.
Step 5: Copy the UPDATE.app file from your computer to the /sdcard/dload/ directory.
Step 6: Launch your device and go to: Settings -> Updater -> Menu -> Local Update and choose the UPDATE.app file.
Step 7: Install the update and wait until it reboots again. Check if the update is working successfully.
Step 8: Copy the B180 (B121 to B180) incremental update zip file from your computer to the /sdcard/dload/ directory.
Step 9: Make sure the name of your update zip file is “update.zip”.
Step 10: Apply the update by going to: Settings -> Updater -> Menu -> Local Update and choosing the update.zip file.
Step 11: Install the update and wait until it reboots again. Check if the update is working successfully.
Step 12: Delete the update.zip file from your /sdcard/dload/ directory.
Appendix C - Available Custom ROM(s)
r3 - Custom Rom Starter Template: http://forum.xda-developers.com/honor-7/development/r1-custom-rom-starter-template-honor-7-t3337901
r2 - MoDaCo Custom Kernel: http://forum.xda-developers.com/honor-7/development/kernel-r1-modaco-custom-kernel-t3365909
MoDaCo Custom Rom: http://forum.xda-developers.com/honor-7/development/r1-custom-rom-starter-template-honor-7-t3337901
YodaRom: http://forum.xda-developers.com/honor-7/development/rom-6-0-x-yodarom-v1-0-mm-rooted-ads-t3338179
DigiRom: http://forum.xda-developers.com/honor-7/development/rom-digirom-gpe-v1-t3365391
H7T Rom: http://forum.xda-developers.com/honor-7/development/rom-codename-h7t-t3396002
You can view all available custom ROM(s) at: http://forum.xda-developers.com/honor-7/development
Appendix D - Extra Resources
How to build your own kernel for Honor 7: http://forum.xda-developers.com/honor-7/general/guide-how-to-build-kernel-honor-7-t3363894
Honor 7 Multi-Tool: http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176
Spectrum Pure Theme: http://forum.xda-developers.com/honor-7/themes-apps/theme-spectrum-pure-base-theme-t3321234
Appendix E - All Important Downloads
All Stock ROMs and OTA Updates: http://www.modaco.com/forums/topic/...ck-rom-images-updated-1st-april-2016-plk-l01/
The Latest Version Of "TWRP": https://dl.twrp.me/plank/
The Latest Version Of "SuperSU": https://download.chainfire.eu/supersu
The Latest Version Of "15 Seconds ADB Installer": http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
The Latest Version Of "Huawei Update Extractor": http://forum.xda-developers.com/showthread.php?t=2433454
Access the "Huawei Bootloader Unlocker": https://hwid5.vmall.com/oauth2/portal/cloud_login.jsp
Awesome and very helpful guide @kenshiwara
Thank you for this guide.
If I understand, we can update if twrp is installed?
Envoyé de mon Nexus 5
No offence but this is just @piskr 's thread re-typed with some serious errors added to it.
Did you try "fastboot oem relock"? I started a thread on that, it doesn't work.
Did you try any of the "fastboot erase" commands? As when I tried it wouldn't - "Command not allowed"
The Huawei extract tool doesn't get the names of the images on the current full ROMS (tested on B121 and a few of the Chinese ROMS) it doesn't have the mappings for these. However it has worked with incremental patches..
Extracting the files and only flashing a few like system will leave you with and inconsistent device (if from different versions). Those 20+ files have a reason - modem, sensorhub, trustfirmware, teeos (whatever that is!), etc.. There are actually something like 40 block devices on the H7 (/dev/block/platform/hi_mci.0/by-name/). To run an official update on that system would almost certainly result in failure. (I have tried)
..and flashing a whole system doesn't fix a boot-loop. That's flashing the whole system, it goes away because whatever was causing it has been deleted/wiped. If that's the idea, better off flashing Huawei's recovery and doing a full UPDATE.APP of B100 / B121 and moving up.
Oh and just one more minor thing - holding the power button isn't required, turn the phone on and hold either down (with usb data connected) for boot-loader, or up for recovery
Sorry... I know you mean well, however posting things in good faith is dangerous. Especially in a guide aimed at beginners.
sminki said:
No offence but this is just @piskr 's thread re-typed with some serious errors added to it.
Did you try "fastboot oem relock"? I started a thread on that, it doesn't work.
Did you try any of the "fastboot erase" commands? As when I tried it wouldn't - "Command not allowed"
The Huawei extract tool doesn't get the names of the images on the current full ROMS (tested on B121 and a few of the Chinese ROMS) it doesn't have the mappings for these. However it has worked with incremental patches..
Extracting the files and only flashing a few like system will leave you with and inconsistent device (if from different versions). Those 20+ files have a reason - modem, sensorhub, trustfirmware, teeos (whatever that is!), etc.. There are actually something like 40 block devices on the H7 (/dev/block/platform/hi_mci.0/by-name/). To run an official update on that system would almost certainly result in failure. (I have tried)
..and flashing a whole system doesn't fix a boot-loop. That's flashing the whole system, it goes away because whatever was causing it has been deleted/wiped. If that's the idea, better off flashing Huawei's recovery and doing a full UPDATE.APP of B100 / B121 and moving up.
Oh and just one more minor thing - holding the power button isn't required, turn the phone on and hold either down (with usb data connected) for boot-loader, or up for recovery
Sorry... I know you mean well, however posting things in good faith is dangerous. Especially in a guide aimed at beginners.
Click to expand...
Click to collapse
Thank you for your comments and notes. It is great to see your contribution up there.
This was actually my personal guide that i wrote to help myself around while operating on this device (PLK-L01). Based on your comments, there are several sections that require fixing. Would you mind taking the time to re-write those sections in a step-by-step fashion in order to update the guide?
You disagree with the section of "How to fix the bootloop when you can't access neither the system nor the recovery partitions". My solution - which worked for me - was to erase and flash the main partitions. Still though, if you have a better method, please share it with the whole community in a step-by-step fashion. Everyone will be grateful.
We mainly need the following:
1. How to re-lock the phone if the command of "fastboot oem relock" is not working on some models?
2. How to break out of bootloops if we can't access the system or the recovery partitions? (and flashing the main partitions from fastboot is not a stable solution in your opinion).
If you can provide a detailed step-by-step guides addressing the above two points, i would surely be more than happy to update them in the guide. Please note that the above guide is mostly tested on PLK-L01. Please, always mention your model number when writing your notes.
Thanks again for sharing your results with the community and hope you can send us a better version on the above sections based on your findings.
Freebob94 said:
Thank you for this guide.
If I understand, we can update if twrp is installed?
Click to expand...
Click to collapse
TWRP is not required at all if you are just updating. You should root your device after applying all the updates rather than before.
Thank you for comment!
sminki said:
Did you try "fastboot oem relock"? I started a thread on that, it doesn't work.
Did you try any of the "fastboot erase" commands? As when I tried it wouldn't - "Command not allowed"
Click to expand...
Click to collapse
Well me and @kenshiwara both tried it after stucking in bootloop and those commands worked like a charm
kenshiwara said:
Thank you for your comments and notes. It is great to see your contribution up there.
Thanks again for sharing your results with the community.
Click to expand...
Click to collapse
I'm glad you too my reply as intended and not just an angry rant!
DigiGoon said:
Well me and @kenshiwara both tried it after stucking in bootloop and those commands worked like a charm
Click to expand...
Click to collapse
Guessing by your location, you have the Indian single sim version?
sminki said:
I'm glad you too my reply as intended and not just an angry rant!
Guessing by your location, you have the Indian single sim version?
Click to expand...
Click to collapse
No, I have European model PLK-L01, thanks to @kenshiwara
---------- Post added at 07:48 PM ---------- Previous post was at 07:46 PM ----------
sminki said:
I'm glad you too my reply as intended and not just an angry rant!
Click to expand...
Click to collapse
LOL, yeah, some people or developers would have taken it as angry rant but we all are here to learn and help each other.
OK, well I also have an EU PLK-L01 with unlocked bootloader. I re-tested the following today to confirm my initial findings:
fastboot oem get-bootinfo
Code:
...
[COLOR="Green"][B](bootloader) unlocked[/B][/COLOR]
OKAY [ 0.000s]
finished. total time: 0.000s
fastboot erase system
Code:
erasing 'system'...
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
finished. total time: 0.000s
fastboot erase userdata
Code:
erasing 'userdata'...
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
finished. total time: 0.000s
fastboot -w
Code:
Erase successful, but not automatically formatting.
[B]Can't determine partition type.[/B]
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
Erase successful, but not automatically formatting.
[B]Can't determine partition type.[/B]
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
erasing 'userdata'...
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
finished. total time: 0.000s
This was the same for any of the B1xx firmwares.
DigiGoon said:
Well me and @kenshiwara both tried it after stucking in bootloop and those commands worked like a charm
Click to expand...
Click to collapse
You locked the bootloader to fix boot-loop? That's a bad idea!
sminki said:
You locked the bootloader to fix boot-loop? That's a bad idea!
Click to expand...
Click to collapse
Never locked it, just flashed SYSTEM.img by executing
Code:
fastboot flash system SYSTEM.IMG
and it worked.
DigiGoon said:
Never locked it, just flashed SYSTEM.img by executing
Code:
fastboot flash system SYSTEM.IMG
and it worked.
Click to expand...
Click to collapse
Well, in post #7 you wrote this:
------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
------------------------------------------
However, your answer above says otherwise. Erase and flash are not the same thing
One of my main criticisms on the original post was that fastboot erase doesn't work, I went a long way to back this up in post #10
sminki said:
Well, in post #7 you wrote this:
------------------------------------------
------------------------------------------
However, your answer above says otherwise. Erase and flash are not the same thing
One of my main criticisms on the original post was that fastboot erase doesn't work, I went a long way to back this up in post #10
Click to expand...
Click to collapse
Sorry, that was my mistake but I never erased the partition, directly flashed it
DigiGoon said:
Sorry, that was my mistake but I never erased the partition, directly flashed it
Click to expand...
Click to collapse
Cool thanks. I can sleep easy now :highfive:
sminki said:
Cool thanks. I can sleep easy now :highfive:
Click to expand...
Click to collapse
I have updated the original thread highlighting your comments while fixing it according to our latest tests. Please read it up again and inform us if you have anything else to improve on it.
Out of 500 views, only you decided to take few minutes and help in improving this guide. Thank you for your time and know that your support will be appreciated by all the community of XDA-Developers.
Hi there beautiful people.
I'm getting some error updating after installing tw recovery.
Code:
Checking MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to start
E:Error executing updater binary in zip '/external_sd/dload/update.zip
E:Error installing zip file '/external_sd/dload/update.zip
Now backupping, i'm going to try to flash the zip (i'ts a stupid thing?).
Edit: Did not work either. Cannot update using twrp; the update app reboots directly in the custom recovery.
Currently on B121, it already had it. PLK-L01 europe.
Also, do you really think Haweii will public codes? I'm not so optimistic.
Smokehrbar88 said:
Hi there beautiful people.
I'm getting some error updating after installing tw recovery.
Code:
Checking MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to start
E:Error executing updater binary in zip '/external_sd/dload/update.zip
E:Error installing zip file '/external_sd/dload/update.zip
Now backupping, i'm going to try to flash the zip (i'ts a stupid thing?).
Currently on B121, it already had it. PLK-L01 europe.
Also, do you really think Haweii will public codes? I'm not so optimistic.
Click to expand...
Click to collapse
If that update.zip is from Huawei it won't work in TWRP.
You need Huawei recovery to install Huawei updates.
sminki said:
If that update.zip is from Huawei it won't work in TWRP.
You need Huawei recovery to install Huawei updates.
Click to expand...
Click to collapse
Indeed, it sounds pretty logic. So i should revert the stock recovery, update and then reinstall twrp.
Can I do it simply pushing trough adb? And where should I find the recovery.img?
Thanks for the help.
Smokehrbar88 said:
Indeed, it sounds pretty logic. So i should revert the stock recovery, update and then reinstall twrp.
Can I do it simply pushing trough adb? And where should I find the recovery.img?
Thanks for the help.
Click to expand...
Click to collapse
You have to extract them from the UPDATE.APP file!
I've done the work for you.. B121 recovery attached
Unizp, then
Code:
fastboot flash recovery B121_recovery.img
(like you did with twrp)
Then put TWRP back on.
I forgot to add - if the system partition is altered (su) then the official update may well fail..
sminki said:
I've done the work for you.. B121 recovery attached
Click to expand...
Click to collapse
I was downloading the full rom myself, but my internet speed is so slow. My savior, thank you. I hope to not bother you again with my low-tier noob problems.
If you are looking to flash stock firmware, custom kernel, custom recovery, root via supersu, and remove bloatware for E6883 model only, you came to the right thread, otherwise, go away. Make sure you have at least 50% battery before proceeding. I'm assuming you are running Microsoft Windows 10 Home x64 and have installed all required Google USB Drivers, Android SDK (for fastboot), and an unlocked bootloader. If you have not done this yet, install them first so that your device will be recognized. Don't forget to enable "USB debugging" and "OEM unlocking" from the "Developer options" menu on your device. Come on, you can't be that noob. If you don't even know what that means, you don't belong here and chances are, you will end up with a bricked phone.
/* YOUR WARRANTY IS NOW VOID */
Download all necessary files, preferably the latest version.
Xperia Firmware Downloader
Sony Mobile Flasher by Androxyde
Custom Kernel - Rename the file as boot.img and move it to "C:\Android\SDK\platform-tools\boot.img"
Custom Recovery - Rename the file as recovery.img and move it to "C:\Android\SDK\platform-tools\recovery.img"
SuperSU Stable - Rename the file as supersu.zip and move it to your external SD card.
[STEP 1] Using the Xperia Firmware Downloader.
1. Run "XperiFirm.exe" as Administrator.
2. Select "Xperia Z5 Premium Satsiki" > "E6883 dual" from the list.
3. Select your preferred firmware and download.
4. DONE.
[STEP 2] Using the Sony Mobile Flasher by Androxyde.
// How to prepare a flashable .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Select "Tools" > "Bundles" > "Create" from the menu.
3. "Select source folder" where your firmware folder is located.
4. Double-click "Device" editbox and select "E68XX Sony Xperia Z5 Premium" > "E6883".
5. Fill in the "Branding" editbox.
6. Fill in the "Version" editbox.
7. Select everything from the "folder list" and move them to "Firmware Content".
8. Click on the "Create" button.
9. DONE.
// How to start flashing a .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Click on the "Thunder toolbar button" and choose "Flashmode".
3. Select your "Firmware".
4. Click on the checkboxes to wipe everything and don't exclude anything except SIMLOCK (you can't touch this).
5. Click on the "Flash" button.
6. DONE.
[STEP 3] Flashing the custom kernel.
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash boot boot.img"
6. DONE.
[STEP 4] Flashing the custom recovery. - Actually, there is no need for this step. The custom kernel provided above already included TWRP 3, so this is just to show you how to flash a custom recovery. Thanks, @YasuHamed
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash recovery recovery.img"
6. DONE.
[STEP 5] Flashing the SuperSU, hence rooting your device.
1. Turn off your device.
2. Turn on your device.
3. As soon as your device is powering on, press on the "volume-up rocker" continuously until you load TWRP.
4. Flash SuperSU from your SD card.
5. Reboot system.
6. DONE.
Congrats! :laugh:
Now that you have root access, the next part is to remove bloatware but I will post this later on because I need to do some more research just to confirm it won't have FCs in the future. Removing bloatware is rather self-explanatory and depends on your personal preferences. Like me, I would delete all of Google and Sony apps to bare minimum but some people prefer leaving Google Maps or Sony Smart Connect on their phone. I'll see you on the next episode, to be continued...
Reserved for battery management, tips and tricks.
cglegion said:
If you are looking to flash stock firmware, custom kernel, custom recovery, root via supersu, and remove bloatware for E6883 model only, you came to the right thread, otherwise, go away. Make sure you have at least 50% battery before proceeding. I'm assuming you are running Microsoft Windows 10 Home x64 and have installed all required Google USB Drivers, Android SDK (for fastboot), and an unlocked bootloader. If you have not done this yet, install them first so that your device will be recognized. Don't forget to enable "USB debugging" and "OEM unlocking" from the "Developer options" menu on your device. Come on, you can't be that noob. If you don't even know what that means, you don't belong here and chances are, you will end up with a bricked phone.
/* YOUR WARRANTY IS NOW VOID */
Download all necessary files, preferably the latest version.
Xperia Firmware Downloader
Sony Mobile Flasher by Androxyde
Custom Kernel - Rename the file as boot.img and move it to "C:\Android\SDK\platform-tools\boot.img"
Custom Recovery - Rename the file as recovery.img and move it to "C:\Android\SDK\platform-tools\recovery.img"
SuperSU Stable - Rename the file as supersu.zip and move it to your external SD card.
[STEP 1] Using the Xperia Firmware Downloader.
1. Run "XperiFirm.exe" as Administrator.
2. Select "Xperia Z5 Premium Satsiki" > "E6883 dual" from the list.
3. Select your preferred firmware and download.
4. DONE.
[STEP 2] Using the Sony Mobile Flasher by Androxyde.
// How to prepare a flashable .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Select "Tools" > "Bundles" > "Create" from the menu.
3. "Select source folder" where your firmware folder is located.
4. Double-click "Device" editbox and select "E68XX Sony Xperia Z5 Premium" > "E6883".
5. Fill in the "Branding" editbox.
6. Fill in the "Version" editbox.
7. Select everything from the "folder list" and move them to "Firmware Content".
8. Click on the "Create" button.
9. DONE.
// How to start flashing a .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Click on the "Thunder toolbar button" and choose "Flashmode".
3. Select your "Firmware".
4. Click on the checkboxes to wipe everything and don't exclude anything except SIMLOCK (you can't touch this).
5. Click on the "Flash" button.
6. DONE.
[STEP 3] Flashing the custom kernel.
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash boot boot.img"
6. DONE.
[STEP 4] Flashing the custom recovery.
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash recovery recovery.img"
6. DONE.
[STEP 5] Flashing the SuperSU, hence rooting your device.
1. Turn off your device.
2. Turn on your device.
3. As soon as your device is powering on, press on the "volume-up rocker" continuously until you load TWRP.
4. Flash SuperSU from your SD card.
5. Reboot system.
6. DONE.
Congrats! :laugh:
Click to expand...
Click to collapse
the customer kernals by @khab.bros already have recovery installed,
Correct @YasuHamed, and it's newer than the one I provided. I just want new people to know the idea of flashing custom recovery on this device. Thanks for the heads up. It's a shame there is so less development going on for Z5 Premium Dual compared to other flagship devices such as Samsung... I hope we see more custom roms port in the near future.
@cglegion
Maybe minimal adb and fastboot tool would be better than installing the entire android SDK package... It's a small utility around 2 mb only , since you're doing a noob friendly guide it might be more appropriate...
cglegion said:
Correct @YasuHamed, and it's newer than the one I provided. I just want new people to know the idea of flashing custom recovery on this device. Thanks for the heads up. It's a shame there is so less development going on for Z5 Premium Dual compared to other flagship devices such as Samsung... I hope we see more custom roms port in the near future.
Click to expand...
Click to collapse
the way sony is behind in specs, I think in upcoming days the development side of xperia will suffer the most as the sales goes down!
in 2016 we have mobiles reaching specs such as 2.2ghz with 6gb ram and the NEWEST xperia X series has 1.5gb ~ 2gb RAM ONLY~
-DM- said:
@cglegion
Maybe minimal adb and fastboot tool would be better than installing the entire android SDK package... It's a small utility around 2 mb only , since you're doing a noob friendly guide it might be more appropriate...
Click to expand...
Click to collapse
You're right @-DM-, the fact that I recommend using Android SDK was the ability to install packages automatically for example the Google USB Driver though the SDK manager and not solely for fastboot functionality. Some newbies might not even have appropriate drivers installed on their machine so their device won't be recognized hence a simple problem will lead to another problem. But of course, using minimal adb and fastboot is another noob-friendly way (which is also less in size) compared to the 100mb + Android SDK. Thanks, for the heads up too and making this thread a more noob-friendly one! :laugh:
Btw, @YasuHamed do you somehow know how to create a build.prop and updater-script for a stock firmware that I've just tweaked (delete bloatware apk and add some mods and third party apks)? I need to make it flashable via twrp but lack example for this device. Thanks!
cglegion said:
Btw, @YasuHamed do you somehow know how to create a build.prop and updater-script for a stock firmware that I've just tweaked (delete bloatware apk and add some mods and third party apks)? I need to make it flashable via twrp but lack example for this device. Thanks!
Click to expand...
Click to collapse
as far as I have studied, there is no DIRECT way doing that in MM
however for sake of argument, lets say you are using your z5 at 5.x.x
the zips can be flashed if you are REPACKING your STOCK KERNAL. (the post of Khab.bros) is actually points out to
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
here if you have original FTF file of your z5, EXTRACT kernel.sin to kernal.els (using flashtool) then by running it through ROOTKERNELv5.0, you can add custom recovery and other flashable zips (after disabling dm-variety / SONYRIC)
but to remove BLOATWARE From your stockROM,
you must EXTRACT SYSTEM.sin, from FTF file, Dump it fully to location, RESAVE it using Ext2Explorer, now u will have APP folder, see which apk you want to remove, when you are done, repack everything to SYSTEM.sin and now MODIFIED STOCKROM has been created.
i remember doing id for my xperia C6603 back in 2013
http://forum.xda-developers.com/showthread.php?t=1931585
the tutorial was also very helpful https://www.youtube.com/watch?v=DpYxMRlBrR8
btw, I did all that just to learn, later i never did all this because some how i love the xperia stockroms and after rooting you can remove many bloatware and change system app to user app and remove them at your ease...
Command Prompt
Hi i successfully flashed the tft file and now im up to using the command prompt so i shift+right clicked and opened a command window in the platform tools folder where the boot.img and recovery.img are and entered the command "flashboot flash boot boot.img" and it comes up saying "error: cannot load boot.img"
I dont know what to do here. please help.
shaxta said:
Hi i successfully flashed the tft file and now im up to using the command prompt so i shift+right clicked and opened a command window in the platform tools folder where the boot.img and recovery.img are and entered the command "flashboot flash boot boot.img" and it comes up saying "error: cannot load boot.img"
I dont know what to do here. please help.
Click to expand...
Click to collapse
Make sure you have unlocked your bootloader before following this guide and just to inform you again this guide is for E6883.
Yeah I figured it out, the only problem was the fastboot drives weren't installed correctly for some reason windows 10 didn't allow it, also it was having trouble finding the boot.img so I just dragged the fastboot.exe and the boot.img into the command instead and it worked.
All in all great guide, thanks.
YasuHamed said:
as far as I have studied, there is no DIRECT way doing that in MM
however for sake of argument, lets say you are using your z5 at 5.x.x
the zips can be flashed if you are REPACKING your STOCK KERNAL. (the post of Khab.bros) is actually points out to
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
here if you have original FTF file of your z5, EXTRACT kernel.sin to kernal.els (using flashtool) then by running it through ROOTKERNELv5.0, you can add custom recovery and other flashable zips (after disabling dm-variety / SONYRIC)
but to remove BLOATWARE From your stockROM,
you must EXTRACT SYSTEM.sin, from FTF file, Dump it fully to location, RESAVE it using Ext2Explorer, now u will have APP folder, see which apk you want to remove, when you are done, repack everything to SYSTEM.sin and now MODIFIED STOCKROM has been created.
i remember doing id for my xperia C6603 back in 2013
http://forum.xda-developers.com/showthread.php?t=1931585
the tutorial was also very helpful https://www.youtube.com/watch?v=DpYxMRlBrR8
btw, I did all that just to learn, later i never did all this because some how i love the xperia stockroms and after rooting you can remove many bloatware and change system app to user app and remove them at your ease...
Click to expand...
Click to collapse
Hey, bro @YasuHamed managed to make an Aroma installer for myself (learned this from scratch) but now I'm having problem making the updater-script file because I'm not sure how to mount and extract the system files also the command to patch (a repacked) boot.img kernel. From my research, dev block for E6883 are as follow:
1. /cache /data / sdcard = mmcblk0p42
2. /external_sd = mmcblk1p1
3. /system = mmcblk0p43
Can you help me? I'm very close to releasing a custom ROM based on stock firmware without bloatware. Where do I go about... I've been searching all over Google and XDA and has not found answers for E6883 specific problems.
shaxta said:
Hi i successfully flashed the tft file and now im up to using the command prompt so i shift+right clicked and opened a command window in the platform tools folder where the boot.img and recovery.img are and entered the command "flashboot flash boot boot.img" and it comes up saying "error: cannot load boot.img"
I dont know what to do here. please help.
Click to expand...
Click to collapse
use flahstool
---------- Post added at 11:15 AM ---------- Previous post was at 11:13 AM ----------
use flashtool
---------- Post added at 11:34 AM ---------- Previous post was at 11:15 AM ----------
cglegion said:
Hey, bro @YasuHamed managed to make an Aroma installer for myself (learned this from scratch) but now I'm having problem making the updater-script file because I'm not sure how to mount and extract the system files also the command to patch (a repacked) boot.img kernel. From my research, dev block for E6883 are as follow:
1. /cache /data / sdcard = mmcblk0p42
2. /external_sd = mmcblk1p1
3. /system = mmcblk0p43
Can you help me? I'm very close to releasing a custom ROM based on stock firmware without bloatware. Where do I go about... I've been searching all over Google and XDA and has not found answers for E6883 specific problems.
Click to expand...
Click to collapse
although i never liked aroma and i won't usually recommend custom roms specially for xperia... but since you have came this far,
lets say under APK foler you removed many bloatware and also updated
you must repack you SYSTEM folder (only) back to ROOM.zip (originally extracted from ftf file using ext2explorer)
then you need to apply mods,
https://www.youtube.com/watch?v=FdhUK_Ds4Fo (part 2, deleting bloatware) / finding MODS and repacking
http://forum.xda-developers.com/showthread.php?t=1363460 (tutorial about updater script modification by notepad++ )
however just remember what ever studies i did, for android 6.0.1 the prf creator wont work,
but you can try (PRF creator)
http://forum.xda-developers.com/showthread.php?t=1363460
convert your boot.img to kernel.sin and recreate your PRF creator (as mentioned above)
OR keep the custom rom ftf and BOOT.img SAPERATE as many custom roms does that
1. cynogenmod 12+
3. Miui 5 onwards
have boot+recovery file saperate and Rom saperate to flash.
the only reason i could understand is because they flash their system via recovery. if your aroma stock has xd recovery you can keep the flashable zip to install as system ORRRR keep it as FTF file to be flash and then kernal to be flashed saperate
Thanks for this guide I just wish to have root on locked BL...
Requirements:
Patched aboot: https://forum.xda-developers.com/lg-k10/how-to/bootloader-unlocked-guys-bootloader-t3558810
TWRP: https://eu.dl.twrp.me/m216/
Python scripts: https://github.com/Lekensteyn/lglaf/archive/master.zip
PyUSB: https://walac.github.io/pyusb/
Instaled python
LINUX
LG UP
Device must be: LG K420ds or LG K420n
Video tutorial: https://www.youtube.com/watch?v=vL14_XPrMzs
Watch with subtitles.
1. Install rom
Download this rom https://lg-firmwares.com/download-file/?fileId=4124
Flash it using LG UP with the refurbish option
2. Unlock Bootloader
Enter into Download Mode
Copy aboot_patched.img into folder with python scripts
Type in terminal "python partitions.py --wipe aboot"
Type in terminal "python partitions.py --restore aboot_patched.img aboot"
Exit from Download Mode and from now your BT is unlocked
3. Install TWRP
Enter into Download Mode
Copy recovery.img into folder with python scripts
Type in terminal "python partitions.py --wipe recovery"
Type in terminal "python partitions.py --restore recovery.img recovery"
Exit from Download Mode and from now your recovery is TWRP
Don't enter to recovery from comand "reboot recovery" because it restore your settings to default
Install SuperSU
Download this file https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip and copy to sdcard
Enter into Recovery
Enter into "Install"
Choose your zip file
Swipe for install
Thanks to @pvineeth97 for twrp and patched aboot.
Thread with a tool then I use https://forum.xda-developers.com/android/software-hacking/tool-lg-download-mode-laf-t3285946
[6.*] ? It is wrong. The patched aboot is only for 5.1.
Yes, it is but it work on android 6.0
Yeah, you extracted all the things from the LAF link I provided. Great job!
I recomment you to add the original XDA link for more details and extra information for the rest of users.
https://forum.xda-developers.com/android/software-hacking/tool-lg-download-mode-laf-t3285946
A video tutorial would not be bad, so that people do not have problems when executing the tutorial
flamenkito34 said:
A video tutorial would not be bad, so that people do not have problems when executing the tutorial
Click to expand...
Click to collapse
Instructions are simple buddy! Just follow them.
pvineeth97 said:
Instructions are simple buddy! Just follow them.
Click to expand...
Click to collapse
Well clear, they are not where we put aboot_parched.img and Twrp.img.
Enviado desde mi LG-K420 mediante Tapatalk
flamenkito34 said:
Well clear, they are not where we put aboot_parched.img and Twrp.img.
Enviado desde mi LG-K420 mediante Tapatalk
Click to expand...
Click to collapse
I added information into guide where copy aboot.img and recovery.img file
Well I try and tell me that quw python is not an executable command, it makes the tutorials to facilitate the work to other users, now if you put this is what it takes and you can look for life, it's like having a cough and scratching The eggs, no good
Enviado desde mi LG-K420 mediante Tapatalk
TWRP Backup!
Somebody please share your TWRP backup of system and boot partitions.
Marshmallow offcourse!
Use TWRP Manager from GooglePlay.
Than i will be able to work with it.
Don't want to waist my time to make work python.
And many other users will appreciate it!
D_Vovan_238 said:
Somebody please share your TWRP backup of system and boot partitions.
Marshmallow offcourse!
Use TWRP Manager from GooglePlay.
Than i will be able to work with it.
Don't want to waist my time to make work python.
And many other users will appreciate it!
Click to expand...
Click to collapse
I have LP's backup if you want
Thanks
Ajshal said:
I have LP's backup if you want
Click to expand...
Click to collapse
Thanks but I also have it ?
I need MarshMallow System backup, not LolliPop.
D_Vovan_238 said:
Thanks but I also have it ?
I need MarshMallow System backup, not LolliPop.
Click to expand...
Click to collapse
Ok cheers mate!
hey..
some things you should add to this guide...
How to enter download Mode: Plug In usb cable while holding volume up
*5. python, libusb etc. all installed at stock ubuntu 15.04
*6. Ubuntu 15.04 this os has everything needed in this guide onboard
create live usb usb stick with this tool and this guide
choose install ubuntu and follopw the next steps
how to set up lg up for k10 420n
Important Info: Reboot Phone (into Download Mode) after Bootloader unlock ... the video tutorial doesnt work on my phone ... Im tryed it like in the video .. dont work
How to enter Twrp:
1. Press and hold Volume Down + Power untill you see the lg logo ..
2. at the first lg logo : release volume down and power, and press volume down and power again quickly
3.confirm factory reset ... If twrp correct installed it doesnt wipe your phone
greetings martin
When I typing console commands on linux PC dont see my phone
szymm3 said:
When I typing console commands on linux PC dont see my phone
Click to expand...
Click to collapse
1. Connect phone in download mode
2. *** under linux *** theres no feedback (download mode) that the phone is connected... (Make sure that python and some other packages are installed) see my post with ubuntu
3.open terminal in folder where you placed aboot_patched.img and recovery.img (twrp)
4. Type sudo -s in terminal... Confirm.
5. Type the commands from first page or the tutorial .. I recommend to make a screenshot ...
6. When entering commands you only will see a "feedback" that your phone is correct connected... You see... Only a cryptic message that a file or partition is changed witg trim etc...
I type:
python partitions.py --wipe aboot
and this is output:
Traceback (most recent call last):
File "partitions.py", line 276, in <module>
main()
File "partitions.py", line 248, in main
comm = lglaf.autodetect_device()
File "/home/szymm3/Pobrane/lglaf-master/lglaf.py", line 318, in autodetect_device
return USBCommunication()
File "/home/szymm3/Pobrane/lglaf-master/lglaf.py", line 206, in __init__
raise RuntimeError("USB device not found")
RuntimeError: USB device not found
Phone is lg k10 (k420ds/n?)
Do you have ubuntu / linux installed or do you using live system (try ubuntu)
Little guide to install ubuntu even on a extern hard disk, usb stick , etc.
1. Boot live usb stick or dvd/cd
2.choose try ubuntu
3. Open gparted (search or download it)
4. Choose your device where linux / ubuntu should be installed
5. I recommend to use a empty disk... Delete the main partition
6. Create follow partitions :
Extended ... Select the whole disk
/ ext4 minimum 10-15gb
Logical
Linux swap ...size: Ca. 20% more then installed ram
/home ext4 size you want ...
Logical
Click here for a guide
7.click apply at gparted
8. Reboot to live usb stick
9. Choose install ubuntu
10. When asked where ubuntu should be installed click something else ... Or what you at the last option
****bootloader installation device****
Choose your device not a partition ...
Example. Dev/sdxyz/your harddisk ... Not
Dev/sdx1
11. You now see your installed / pluged devices /hard disk
12.select your device... There now are your prepared partitions ... Choose your / partition.. Click change ... Now choose as mount ... /
13. Install
click here for more infos
dont know how to show this in english
In the live system there are some tools and packages not installed... Seems like there is an issue with pyusb ...
Check... Python status ... Type
ls /usr/bin | grep python .... There should be now pop up some lines1 with python version installed
Now type in terminal
apt-cache policy libusb-1.0
One of the now showed version has to be installed....
If both packages are installed correct... Make sure pyusb is installed ... (As i post above ... Ubuntu 15.04 has both installed
Install python :
Open terminal in pyusb folder...where setup.py is placed
Type
Sudo python setup.py install
Now pyusb should be installed correct....
These are the requirements to use this guide..
If you received more issues .. Just write... But after i do all steps above it worked...
- martin
ps now im off for some hours... repair 260 hp car and ride with my simson moped yeeeeeeha
When im have the time too .. Im write a detailed guide
I have lg k10 k420n
Im using Ubuntu and when i made every step from this instruction I still have the same error
dom133 said:
Requirements:
Patched aboot: https://forum.xda-developers.com/lg-k10/how-to/bootloader-unlocked-guys-bootloader-t3558810
TWRP: https://eu.dl.twrp.me/m216/
Python scripts: https://github.com/Lekensteyn/lglaf/archive/master.zip
PyUSB: https://walac.github.io/pyusb/
Instaled python
LINUX
LG UP
Device must be: LG K420ds or LG K420n
Video tutorial:
Watch with subtitles.
1. Install rom
Download this rom https://lg-firmwares.com/download-file/?fileId=4124
Flash it using LG UP with the refurbish option
2. Unlock Bootloader
Enter into Download Mode
Copy aboot_patched.img into folder with python scripts
Type in terminal "python partitions.py --wipe aboot"
Type in terminal "python partitions.py --restore aboot_patched.img aboot"
Exit from Download Mode and from now your BT is unlocked
3. Install TWRP
Enter into Download Mode
Copy recovery.img into folder with python scripts
Type in terminal "python partitions.py --wipe recovery"
Type in terminal "python partitions.py --restore recovery.img recovery"
Exit from Download Mode and from now your recovery is TWRP
Don't enter to recovery from comand "reboot recovery" because it restore your settings to default
Install SuperSU
Download this file https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip and copy to sdcard
Enter into Recovery
Enter into "Install"
Choose your zip file
Swipe for install
Thanks to @pvineeth97 for twrp and patched aboot.
Thread with a tool then I use https://forum.xda-developers.com/android/software-hacking/tool-lg-download-mode-laf-t3285946
Click to expand...
Click to collapse
______________________________________
Is Flashing the above Rom Necessary?
I already have 5.1.1 Qualcomm but the security patch is Jan 2017.
I want to do it, without flashing.. will it work?
Any Suggestions..?
--------------------------------------------------------------
Hi,
I would like install at the Samsung SM-A515F the Lineage OS and the TWRP. I found only TWRP for the SM-A50. And the flashing dose not work for this phone.
I has try it with Heimdall and Odin.
The recovery I had downloaed from this Page:
https://www.droidthunder.com/install-twrp-recovery-on-galaxy-a51/
Need help or better information, if there exist an TWRP and lineage for this device.
Regards tiptel170
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
s 10 page? which one is that? can u please provide the link?
Go here for odin flash method without twrp
sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
so does this method work for lineage os on A515F too?
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
Don't pay.Its fake
tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
of course it would be fake
How can I open the img-files in the Linux desktop?
Found here this link, for the Magisk in the A515F:
https://forum.xda-developers.com/ga...w-to-root-samsung-a51-sm-a515f-t4032389/page2
I'll found this:
1. https://www.androlite.com/2020/01/twrp-root-samsung-galaxy-a51.html
2. https://appslova.com/install-twrp-on-samsung-galaxy-a51/
This links look likes good, because, my phone will not start or the heimdall goes into the error (likes in de page one, the screenshots ).
I found this, and I used basic from this page: https://forum.xda-developers.com/showpost.php?p=82241115&postcount=70
My first steps to install the lineage os 17 on the SM-A515F
Lineage: https://sourceforge.net/projects/andyyan-gsi/
All commands in the linux terminal, the path please use your own paths you like it!
Unpack lineage****.xz:
unxz lineage*.xz
1) Extract the AP_file.tar.md5 from your firmware.zip file using 7zip
2) Extract the super.img.lz4 file from the AP_file.tar.md5 file using 7zip
3) Put super.img.lz4 file in LZ4 folder and run in CMD the command
lz4 -d super.img.lz4 superLZ4.img
4) Put superLZ4.img file in Simg2img folder and run in CMD the command
chmod 777 ~/bin/otatools/bin/simg2img
~/bin/otatools/bin/simg2img superLZ4.img superSIMG.img
In Linux OR Bash shell:
1) Put superSIMG.img in otatools/bin folder and extract it in Linux terminal using the command
chomd 777 ~/bin/otatools/bin/lpunpack
~/bin/otatools/bin/lpunpack --slot=0 superSIMG.img ~/1
2) Put, in the folder where you extracted superSIMG.img, the GSI file you downloaded and rename it to system.img. Now you should have odm.img, system.img, vendor.img and product.img files in the same folder.
You may also need to delete/remane the original system.img file before renaming the GSI file.
3) Now you’re going to make a brand new super.img file containing all 4 files of the previous step. This is a critical and tricky step. Run Linux terminal and type:
chomd 777 ~/bin/otatools/bin/lpmake
~/bin/otatools/bin/lpmake ~/bin/otatools/bin/lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:4294967296 --group main:4293513600 --partition system:readonly:1959841792:main --image system=./system.img --partition vendor:readonly:680239104:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
4) Make an tar file:
tar -H ustar -c super.img > lineageos17.1_SMA515F.tar
5) Goto Windows -> Odin -> AP, put the file lineageos17.1_SMA515F.tar in to the AP-slot -> Start
This is what I has done:
But, by the compiling, I got this error:
Code:
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition system will resize from 0 bytes to 1959841792 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition vendor will resize from 0 bytes to 680239104 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition odm will resize from 0 bytes to 4349952 bytes
Invalid sparse file format at header magic
Invalid sparse file format at header magic
And the phone is into the boot-loop, it will not starting the system.
Any help please...
Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
tiptel170 said:
Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
Click to expand...
Click to collapse
It is work ???
GreggBorowski said:
It is work ???
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
sankhauaa said:
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
Don't pay.Its fake
Click to expand...
Click to collapse
sar please send me a51 group
Mehran` said:
sar please send me a51 group
Click to expand...
Click to collapse
Go to s10 page
sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
Not working. I has done step by step in this guide.
ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
No. Withe manipulation from the vbmeta.img, the system is unwilling to start. It gos in to the bootloader, with error-codes. Like in first thread I describe. Olny the SAMSUNG original system works with the kernel modification for the MagiskManager.
I saw black for the future, there will be exist an custom rom for this device.
I have no idea, what can I do for this device. But I use and spend a lot of time for modification, without an good result. Has anyone an idea what can I do? But it look likes, it has an great secure system intern for not using an customer rom. This is my intention.