Database Users

[GUIDE][ROOT] Xperia SP 4.3 Root + CWM Guide (.266) Unlocked Bootloader ONLY

This guide excists to help you root your phone and only that.If your phone gets hard bricked i will not be held responsible use this guide with care​
This is a guide for Xperia SP users to root 0.266 firmware (Jellybean 4.3) using Doomlords method ! UNLOCKED BOOTLOADER ONLY !!!!!!​
Before proceding with the installation make sure you have the drivers needed for flashtool
First of all you need and unlocked bootloader!!!! THIS IS CRUCIAL IF YOUR BOOTLOADER IS LOCKED THE ROOTING PROCCESS WONT WONRK AND YOUR PHONE WILL GET INTO A BOOTLOOP
Bootloader unlocking guide comming soon!!!
After you have an unlocked bootloader
The first thing you need to do is to back up every important item or app (contacts will be lost if not synched with google account) in your internal SD card
Connect your phone to your PC via usb and transfer the UpdateSuperSU.zip in your External SD card
After the Backup you open flashtool
Power Off the device
Connect it into your PC via usb WHILE PRESSING THE VOLUME UP BUTTON
In flashtool --> Flash device (lightning button) --> fastboot mode
A window will pop up select "Select kernel to flash" under the tag " By Doomlord"
After that another window will pop up
Select the directory where you saved Doomlords kernel file (Number 1 in the download list)
Then it will automaticaly flash the data itself
After finished it should say disconnect the phone in the flashtool log
Disconnect the phone and power it up
When you see the Sony Logo spam the volume up button
After a while it should get into CWM recovery (here you navigate with the volume and power buttons,Volume Up = UP , Volume Down = Down , Power Button = Select)
Once inside the recovery sellect install zip
Then your external sd card (mine is labeled as "sdcard1")
Navigate throught your External Sd till you find the UpdateSuperSU.zip you put in here a few minutes back
After that you will select the zip and go to the "Yes" option to flash it
After the flashing is done you will select "reboot system"
And thats it you are now running 4.3 rooted with CWM Congrats
Now as Doomlord suggests you should probably install busybox.
Thats easy after you boot your phone go to PlayStore and install the installer then open the app select install busybox and you are done.
Sofware you will need :
Sony Update Service (SUS) http://www.sonymobile.com/global-en/tools/update-service/
Flashtool http://www.flashtool.net/index.php
Hardware you will need :
Xperia SP with 4.3 STOCK
USB Cable
Files you will need:
Doomlord's Kernel Including CWM V03(most recent)http://doomlord.xperia-files.com/download.php?dlid=U1BfRG9vTUxvUkRfQWR2U3RrS2VybmVsX0ZXLTI2Nl92MDE=
UpdateSuperSu.zip http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Busybox https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Thanks for your support.
A thumbs up for Doomlord this great Dev.If it was not for him our phones would not be rooted. Original Guide here : http://forum.xda-developers.com/showthread.php?t=2646193

WTF change font color please. my eyes are bleeding

23/029/2014 19:29:57 - INFO - <- This level is successfully initialized
23/029/2014 19:29:57 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
23/030/2014 19:30:01 - INFO - Device connected in fastboot mode
23/030/2014 19:30:06 - INFO - Selected kernel (boot.img or kernel.sin): D:\Programas\Flashtool\Xperia SP\ROOT 4.3\SP_DooMLoRD_AdvStkKernel_FW-266_v01.elf
23/030/2014 19:30:06 - INFO - Flashing selected kernel
23/030/2014 19:30:06 - INFO - sending 'boot' (11009 KB)...
23/030/2014 19:30:06 - INFO - FAILED (remote: The Device must be rooted first)
23/030/2014 19:30:06 - INFO - finished. total time: 0.007s
23/030/2014 19:30:06 - INFO - FASTBOOT Output:
sending 'boot' (11009 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.007s
23/030/2014 19:30:06 - INFO - Please check the log before rebooting into system
But this is for rooting the device...
Someone know why this happen?
EDIT: I did not open the BL... now this work fine

rvjaywaks said:
WTF change font color please. my eyes are bleeding
Click to expand...
Click to collapse
Sorry ill do that now.

maxomen said:
23/029/2014 19:29:57 - INFO - <- This level is successfully initialized
23/029/2014 19:29:57 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
23/030/2014 19:30:01 - INFO - Device connected in fastboot mode
23/030/2014 19:30:06 - INFO - Selected kernel (boot.img or kernel.sin): D:\Programas\Flashtool\Xperia SP\ROOT 4.3\SP_DooMLoRD_AdvStkKernel_FW-266_v01.elf
23/030/2014 19:30:06 - INFO - Flashing selected kernel
23/030/2014 19:30:06 - INFO - sending 'boot' (11009 KB)...
23/030/2014 19:30:06 - INFO - FAILED (remote: The Device must be rooted first)
23/030/2014 19:30:06 - INFO - finished. total time: 0.007s
23/030/2014 19:30:06 - INFO - FASTBOOT Output:
sending 'boot' (11009 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.007s
23/030/2014 19:30:06 - INFO - Please check the log before rebooting into system
But this is for rooting the device...
Someone know why this happen?
EDIT: I did not open the BL... now this work fine
Click to expand...
Click to collapse
Happy to see your problem solved thanks for submitting it

Hi, I'm testing the firmware for a couple of days but I notice a strange thing in there. Crazy touches, wifi problems, app crashes, among other things. I can tell if is problem with the firmware or kernel because I install the two at same time. Someone else has had these problems?
I'm thinking test with stock kernel but I'm not sure if keep the root.

Hi,
i have seen many people having issue regarding the ram management too poor after rooting. So from where i should get the stock kernel to flash ? currently i have 4.3 Stock room and bootloader unlocked. Before Rooting how can i backup kernel ?
Thanks.

maxomen said:
Hi, I'm testing the firmware for a couple of days but I notice a strange thing in there. Crazy touches, wifi problems, app crashes, among other things. I can tell if is problem with the firmware or kernel because I install the two at same time. Someone else has had these problems?
I'm thinking test with stock kernel but I'm not sure if keep the root.
Click to expand...
Click to collapse
Thanks for submitting the problem.
I am not currently running on this kernel but when i was running on it i had no problems.Check if its the rom of the installation process of your Rom

asking said:
Hi,
i have seen many people having issue regarding the ram management too poor after rooting. So from where i should get the stock kernel to flash ? currently i have 4.3 Stock room and bootloader unlocked. Before Rooting how can i backup kernel ?
Thanks.
Click to expand...
Click to collapse
You can extract the kernel but for me it has been kinda tricky.(i am NOT an advanced user i just know some basic things)
But you can find stock kernel files from the forum (http://forum.xda-developers.com/showthread.php?t=2311964)

This tutorial it's useful for sony xperia sp c3506

Waiting for tutorial "How to unlock bootloader"...
So you can't root unless you have Locked BL?

bero1608 said:
Waiting for tutorial "How to unlock bootloader"...
So you can't root unless you have Locked BL?
Click to expand...
Click to collapse
You can but you have at first have root and be on .254.
And about tutorial. 20 tutorial points for unlocked bootloader?? LOL!!!!!
1. Flash .266 via flashtool
2. Flash cutsom kernel with cwm (DoomLord advanced kernel)
3. Run supersu fix from cwm
4. Done.

smogf said:
You can but you have at first have root and be on .254.
And about tutorial. 20 tutorial points for unlocked bootloader?? LOL!!!!!
1. Flash .266 via flashtool
2. Flash cutsom kernel with cwm (DoomLord advanced kernel)
3. Run supersu fix from cwm
4. Done.
Click to expand...
Click to collapse
Oh what I've done :facepalm:
Well I was on rooted .254. Flashed DooMLoRD-s kernel and then rooted with his easy root exploit. And then I updated to .266
So I have to downgrade, do everything again, root, then flash .266 kernel?
God.........

bero1608 said:
Oh what I've done :facepalm:
Well I was on rooted .254. Flashed DooMLoRD-s kernel and then rooted with his easy root exploit. And then I updated to .266
So I have to downgrade, do everything again, root, then flash .266 kernel?
God.........
Click to expand...
Click to collapse
When you have unlocked bootloader just flash Advanced Kernel and install supersufix. Done. Eventually after that flash stock kernel (when you want to lock your BL in future)
For locked bootloader its other method really good explained in one of thread. It was also soon mentioned many many many times in many many many threads. Just search.

MrChicken148 said:
This tutorial it's useful for sony xperia sp c3506
Click to expand...
Click to collapse
Why not . This kernel is developed for the Xperia SP that includes C3502 , C3503 and C3506

Okay gonna search for that one. I just don'y wanna destroy my phone that's why I wait if DooM releases easy root exploit

jackaros said:
Why not . This kernel is developed for the Xperia SP that includes C3502 , C3503 and C3506
Click to expand...
Click to collapse
Thank you for the information... I'll check thus process
Enviado desde mi C5306 mediante Tapatalk

MrChicken148 said:
Thank you for the information... I'll check thus process
Enviado desde mi C5306 mediante Tapatalk
Click to expand...
Click to collapse
Glad i helped

Hi I'm back
I have the same problem of maxomen, you may me explain better please... I don't know very well make this process.
The error message is this:
09/011/2014 18:11:22 - INFO - Please check the log before rebooting into system
09/015/2014 18:15:15 - INFO - Selected null
09/015/2014 18:15:15 - INFO - Flash canceled
09/015/2014 18:15:33 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\AlvaroJeanpier\Downloads\SP_DooMLoRD_AdvStkKernel_FW-266_v01.elf
09/015/2014 18:15:33 - INFO - Flashing selected kernel
09/015/2014 18:15:33 - INFO - sending 'boot' (11009 KB)...
09/015/2014 18:15:33 - INFO - FAILED (remote: The Device must be rooted first)
09/015/2014 18:15:33 - INFO - finished. total time: 0.007s
09/015/2014 18:15:33 - INFO - FASTBOOT Output:
sending 'boot' (11009 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.007s
09/015/2014 18:15:33 - INFO - Please check the log before rebooting into system

bero1608 said:
Waiting for tutorial "How to unlock bootloader"...
So you can't root unless you have Locked BL?
Click to expand...
Click to collapse
You cant using this tutorial.But i think you can not generaly as for the BL unlocking guide comming today

HTC Desire 820s , No Bootloader

Is this real ? i really cant access boot loader , just the recovery with the no command screen
can you confirm ??
if so then what i think that this device is already dead

It has a fasboot mode, for now I can only access it via adb (adb reboot bootloader). It shows a black screen with fastboot mode at the bottom.
It also has a stock recovery mode, shows 'no command' but can be activated by pressing power button.
After you've activated it:
Vol+ to select
Vol- navigate down
Power to go back

Adb No devices found , idk why my Laptop doesn't detect my desire 820s

wil try now just installed htc sync manager

okay it worked and i went to fastboot mode , when i give a cmd order it says waiting for device
eg..... fastboot oem info

Same here
fastboot oem unlock
FAILED (remote: unknown command)
fastboot oem get_identifier_token
FAILED (remote: unknown command)
any idea ?

Nc.netcat said:
Same here
fastboot oem unlock
FAILED (remote: unknown command)
fastboot oem get_identifier_token
FAILED (remote: unknown command)
any idea ?
Click to expand...
Click to collapse
Mediatek Htc devices do not need bootloader unlocking, you can flash anything from fastboot mode
---------- Post added at 04:16 PM ---------- Previous post was at 04:10 PM ----------
Mohamed Yaser said:
Is this real ? i really cant access boot loader , just the recovery with the no command screen
can you confirm ??
if so then what i think that this device is already dead
Click to expand...
Click to collapse
You are right, Mediatek HTC devices dont have bootloader. Infact mediatek htc phones can be flashed with SP Flash tool just like micromax phones. I know this is true for htc 816g.

sziraqui said:
Mediatek Htc devices do not need bootloader unlocking, you can flash anything from fastboot mode
.
Click to expand...
Click to collapse
hhmm
fastboot flash recovery recovery.img => partition 'recovery' not support flash

but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader

sziraqui said:
but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader
Click to expand...
Click to collapse
It works. How about flashing a RUU?

Gibz97 said:
It works. How about flashing a RUU?
Click to expand...
Click to collapse
Can mention on which device you have checked it, does it has locked bootloder (if exists)?
RUU in mediatek? i dont think mediatek phones have RUU, (try "fastboot oem rebootRUU" to check)
But if it does, you can extract rom.zip from the RUU THEN EXTRACT system.img, boot.img and recovery.img
Then keep copy this to your firmware folder (containg scatter file)
load scatter file
Uncheck everything except system,boot and recovery in sp flash tool
Click download and connect your powered off device to pc holding vol down

sziraqui said:
Can mention on which device you have checked it, does it has locked bootloder (if exists)?
RUU in mediatek? i dont think mediatek phones have RUU, (try "fastboot oem rebootRUU" to check)
But if it does, you can extract rom.zip from the RUU THEN EXTRACT system.img, boot.img and recovery.img
Then keep copy this to your firmware folder (containg scatter file)
load scatter file
Uncheck everything except system,boot and recovery in sp flash tool
Click download and connect your powered off device to pc holding vol down
Click to expand...
Click to collapse
I've done that but the phone usually cannot boot into the system.
BTW I am on Kitkat 4.4.4 without Sense and I want to flash Lollipop 5.0.2 Sense 7.
The RUU is from a Taiwanese variant 820ys which runs Lollipop 5.0.2 and Sense 7 out of the box, same models(htc_a50ml_dtul)
The problem is that the Kitkat Firmware has smaller partitions compared to the lollipop one. An example is the Kitkat system partition which is about 1.4Gbs while Lollipop has about 4.9Gbs, so I cannot flash with the same scatter file.
So I edit the scatter file to inflate the partitions in order to accommodate the big Lollipop files (sytem.img,recovery.img and boot.img) and perform firmware upgrade.
What could be stopping it from booting? Is it due the fact that the Lollipop boot and recovery are verified? Thanks in advance
Screenshots for Kitkat and Lollipop firmware files below

Gibz97 said:
I've done that but the phone usually cannot boot into the system.
BTW I am on Kitkat 4.4.4 without Sense and I want to flash Lollipop 5.0.2 Sense 7.
The RUU is from a Taiwanese variant 820ys which runs Lollipop 5.0.2 and Sense 7 out of the box, same models(htc_a50ml_dtul)
The problem is that the Kitkat Firmware has smaller partitions compared to the lollipop one. An example is the Kitkat system partition which is about 1.4Gbs while Lollipop has about 4.9Gbs, so I cannot flash with the same scatter file.
So I edit the scatter file to inflate the partitions in order to accommodate the big Lollipop files (sytem.img,recovery.img and boot.img) and perform firmware upgrade.
What could be stopping it from booting? Is it due the fact that the Lollipop boot and recovery are verified? Thanks in advance
Screenshots for Kitkat and Lollipop firmware files below
Click to expand...
Click to collapse
well this question will take the thread off topic. I would request you to create a new thread regarding this issue under "q&a,help and troubleshooting". Chances of your problem getting solved are higher if you do so. I will post my views regarding your issue in that thread. And i apologize to OP, because i only started answering questions irrelevant to his thread.

i totally accept off topics if they are helpful

sziraqui said:
but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader
Click to expand...
Click to collapse
Hi.
It worked, but pressing Vol UP, not down. Anyway i've installed Recovery but when i try to access it from bootloader the device stopped me tellig that is for Android developers. I think that is because at the top of bootloader screen it tell "LOCKED". Any solution?

htc desire 820 softbrick not connecting with fastboot

[SHARE][RECOVERY][UNOFFICIAL] TWRP 3.0.0.0 + Root for Honor 7i/ShotX

Heres TWRP 3.0.0.0
https://dl.twrp.me/rio/twrp-3.0.0-0-rio.img.html
or
https://mega.nz/#!91ZnAaYA!htGK6PknbEd4twDPCsHQ31ZsmDAdKZ7qP_kFWsfSwC4
Since Huawei G8 is so similar to this phone it works
Remember this is for Honor 7i / ShotX and NOT for the regular Honor 7
Ive flashed it on my ShotX but if you are uncertain, please first try and boot it before you flash it onto your device.
Just type make sure adb developer is activated and you also need to check the setting that allows bootloader unlocking or else you cant flash it. Also remember to move the twrp-3.0.0-0-rio.img file into your adb directory, preferably just use minimal adb which is excellent for this type of job
Code:
adb reboot bootloader
Code:
fastboot boot twrp-3.0.0-0-rio.img
If it boots and everything works then you can reboot in bootloader again
Code:
adb reboot bootloader
and then type
Code:
fastboot flash recovery twrp-3.0.0-0-rio.img
to flash the recovery permanently
And if you want root, simply flash this file (superSU.zip)
https://mega.nz/#!F05GXBoI!abpEgAI4WLuu0nraCpEpB5E2rXkIOIlHbepke5SH0cg
Now we just need some tweaked/alternative roms and preferably a nice kernel along with it

Flashed to my Honor 7 and can confirm it works fine

james194zt said:
Flashed to my Honor 7 and can confirm it works fine
Click to expand...
Click to collapse
@ james194zt: Disagree- not flashable on my Honor7 -> as the topic already described... What's your secret to flash it on a H7
fastboot flash recovery twrp-3.0.0-0-rio.img
target reported max download size of 471859200 bytes
sending 'recovery' (43210 KB)...
OKAY [ 1.291s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 1.309s
Click to expand...
Click to collapse
ByTheWay: is there any reason for the behaviour that "fastboot boot AnyRecoveryImage.img" responses with a "<remote: command not allowed>" for me?

So basically I flashed this and now my phone bootloops. Any solution guys?

this trwp works fine, but mayby you have the stock recovery for huawei shotx?

Is unlocking bootloader required?

sajgon338 said:
Is unlocking bootloader required?
Click to expand...
Click to collapse
every times you want to change something like this on your Honor 7, you must unlock your bootloader if it was not unlocked until now!!! But be careful!!!
You should use the minimalADB tool too.

When i boot it it boots and reboot fine but now when i flashed i am stuck in it anyone help me ;(

I got it fixed by just flashing the stock recovery instead of full ROM.
Stock Recovery here :
https://forum.xda-developers.com/honor-7/development/recovery-huawei-shot-x-aka-honor-7i-t3548163

musamaashraf said:
I got it fixed by just flashing the stock recovery instead of full ROM.
Stock Recovery here :
https://forum.xda-developers.com/honor-7/development/recovery-huawei-shot-x-aka-honor-7i-t3548163
Click to expand...
Click to collapse
oh thank you sooo much, you saved the day - it helped the poor ShotX regain access to dload mode after twrp loop )

silver2004 said:
oh thank you sooo much, you saved the day - it helped the poor ShotX regain access to dload mode after twrp loop )
Click to expand...
Click to collapse
Happy to help
Don't forget to hit thanks

Bootloader-Relock LG G4 (H815) No Wipe, No Backups, All Versions

Relock LG G4 Bootloader easily
First of all, I'm new here. So please tell me if I broke any rules or if I made any english mistakes.
Warning:
This guide will show you how to easily Re-Lock your Bootloader. Your Bootloader is then Locked! So, it's not really clever to lock the Bootloader when a Non-Stock-Rom is installed...
Requirements:
- LG G4 (H815) [This probably works with other LG's too]
- TWRP-Recovery installed or temporary booted using "fastboot boot"
- Stock-Android installed (Any Version)
- Flashable Bootloader/Boot Zip's for your Android-Version
For Android 6.0 you can get them here: https://forum.xda-developers.com/g4/development/stock-h815-20g-images-kdz-flashable-t3450503
How to Relock:
Step 1: Boot into TWRP
Step 2: Copy the Zip-Files to internal storage
Step 3: Go to Advanced/Terminal
Step 4: Perform this command:
Code:
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
Your bootloader is Non-Functional now... Don't reboot until the next steps are completed!
Step 5: Flash both Zip-Files using TWRP
Step 6: Reboot
You now have a G4 with stock ROM and locked bootloader. If you wish to uninstall TWRP (Its no longer working) just Flash a Stock kdz-File using LGUP
Hope I was able to help someone...

Reserved

in dd command are 2x //, is the corect command ? or just one / ?
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
to
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
for me misc is /dev/block/mmcblk0p22

ghepardus said:
in dd command are 2x //, is the corect command ? or just one / ?
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
to
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
for me misc is /dev/block/mmcblk0p22
Click to expand...
Click to collapse
The command is correct... If you perform it, it will make the bootloader crash. If you flash a clean bootloader now ur device is locked again.
Mathias

MathiasR33 said:
Relock LG G4 Bootloader easily
I ...
Click to expand...
Click to collapse
... Thx for your thread even if it is known that the unlock state is handled by misc partition but it's good to have an own thread for it now. Latest TWRP beta can save the unlock state since a while.
Just wanted to add: if you made a misc backup before unlock you can just restore your backup. You can even flash a misc of an extracted kdz.
And another thing: if you zero out it like described you may loose your WiFi Mac and you can loose your imei. So before using this it's better to backup your current unlocked misc e.g. with the latest TWRP beta (select BL unlock state).
Backup before unlock is possible with SALT DLM backup ( https://tinyurl.com/dlbackup )
Sent from my LG-H815 using XDA Labs

MathiasR33 said:
Relock LG G4 Bootloader easily
First of all, I'm new here. So please tell me if I broke any rules or if I made any english mistakes.
Warning:
This guide will show you how to easily Re-Lock your Bootloader. Your Bootloader is then Locked! So, it's not really clever to lock the Bootloader when a Non-Stock-Rom is installed...
Requirements:
- LG G4 (H815) [This probably works with other LG's too]
- TWRP-Recovery installed or temporary booted using "fastboot boot"
- Stock-Android installed (Any Version)
- Flashable Bootloader/Boot Zip's for your Android-Version
For Android 6.0 you can get them here: https://forum.xda-developers.com/g4/development/stock-h815-20g-images-kdz-flashable-t3450503
How to Relock:
Step 1: Boot into TWRP
Step 2: Copy the Zip-Files to internal storage
Step 3: Go to Advanced/Terminal
Step 4: Perform this command:
Code:
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
Your bootloader is Non-Functional now... Don't reboot until the next steps are completed!
Step 5: Flash both Zip-Files using TWRP
Step 6: Reboot
You now have a G4 with stock ROM and locked bootloader. If you wish to uninstall TWRP (Its no longer working) just Flash a Stock kdz-File using LGUP
Hope I was able to help someone...
Click to expand...
Click to collapse
you said temporary booted using "fastboot boot", which is the method with just fastboot? and second thing the command :
Code:
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
need any substitution?

freno25 said:
you said temporary booted using "fastboot boot", which is the method with just fastboot? and second thing the command :
Code:
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
need any substitution?
Click to expand...
Click to collapse
u can now re-lock your device with fastboot
important: you device must be FULLY STOCK BEFORE you lock it again! That means no TWRP, no custom ROM etc! otherwise you will brick the device
if you still want to use that method mentioned here:
Make a backup with SALT (basic mode is enough)
boot into fastboot:
Code:
[B]fastboot erase misc[/B]
is doing the same then the above mentioned way.
the misc partition contains also your IMEI, your MAC (wifi) and Bluetooth address. Those SHOULD be re-generated once you boot Android again but if not you will have the backup you created with SALT before.
.

steadfasterX said:
u can now re-lock your device with fastboot
important: you device must be FULLY STOCK BEFORE you lock it again! That means no TWRP, no custom ROM etc! otherwise you will brick the device
if you still want to use that method mentioned here:
Make a backup with SALT (basic mode is enough)
boot into fastboot:
Code:
[B]fastboot erase misc[/B]
is doing the same then the above mentioned way.
the misc partition contains also your IMEI, your MAC (wifi) and Bluetooth address. Those SHOULD be re-generated once you boot Android again but if not you will have the backup you created with SALT before.
.
Click to expand...
Click to collapse
wow perfect you was very clear, and OMG I didn't saw your projects man, you rock! another and last questions(after the cmd "fastboot erase misc" I should use the cmd mentioned in your first link? so "fastboot oem lock" (because i tried this cmd with fastboot and my phone is recognized I checked with "fastboot devices" but my try failed maybe I miss something? I unlocked bootloader 1 year ago now I want to relock it so I refurbished the stock kdz with lgup and try the cmd but the console said to me FAIL (unknown command remote) somethings like that)? otherwise What I should do? just flash bootloader and boot zips?
EDIT:
What I've done:
-Refurbished with LGUP last version of KDZ STOCK of my country
-Now I have my device STOCK but with bootloader to relock
-I downloaded your os
-I downloaded the zip bootloader and boot of my KDZ from this site
-I made a backup basic with your software SALT (just in case)
-I have just to erase misc part (don't reboot before I haven't done last flash for rebuild misc partition)
-But my last doubt is which cmd I have to do with SALT for reflash the two zip and if this zip containg the misc partition (because inside I did found misc bin or img)

freno25 said:
wow perfect you was very clear, and OMG I didn't saw your projects man, you rock! another and last questions(after the cmd "fastboot erase misc" I should use the cmd mentioned in your first link? so "fastboot oem lock" (because i tried this cmd with fastboot and my phone is recognized I checked with "fastboot devices" but my try failed maybe I miss something? I unlocked bootloader 1 year ago now I want to relock it so I refurbished the stock kdz with lgup and try the cmd but the console said to me FAIL (unknown command remote) somethings like that)? otherwise What I should do? just flash bootloader and boot zips?
EDIT:
What I've done:
-Refurbished with LGUP last version of KDZ STOCK of my country
-Now I have my device STOCK but with bootloader to relock
-I downloaded your os
-I downloaded the zip bootloader and boot of my KDZ from this site
-I made a backup basic with your software SALT (just in case)
-I have just to erase misc part (don't reboot before I haven't done last flash for rebuild misc partition)
-But my last doubt is which cmd I have to do with SALT for reflash the two zip and if this zip containg the misc partition (because inside I did found misc bin or img)
Click to expand...
Click to collapse
I meant that you can also go the new way which is less risky by flashing the nougat bootloader in my mentioned link. Then you don't need to erase anything.

So I can just flash the v29a bootloader over my v20g or I should flash the entire stock with lgup?

freno25 said:
So I can just flash the v29a bootloader over my v20g or I should flash the entire stock with lgup?
Click to expand...
Click to collapse
Flash the TOT available is the easiest way.
Sent from my LG-H815 using XDA Labs

Hello,
thanks for the tuto.
With this method, will the message on the top left corner "bootloader unlocked" no longer appear?

steadfasterX said:
Backup before unlock is possible with SALT DLM backup ( https://tinyurl.com/dlbackup )
Click to expand...
Click to collapse
how do I restore the backup created with salt? Unfortunately my IMEI & MAC won't restore >.<

Koile said:
how do I restore the backup created with salt? Unfortunately my IMEI & MAC won't restore >.<
Click to expand...
Click to collapse
manually with fastboot or in TWRP. Both require an unlocked device though.
SALT will allow restore in a future release in download mode too.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
manually with fastboot or in TWRP. Both require an unlocked device though.
Click to expand...
Click to collapse
bootloader is unlocked again, but TWRP won't show the bin-files created and fastboot just returns:
Code:
> .\fastboot flash misc E:\salt_backup\misc.bin
target reported max download size of 536870912 bytes
sending 'misc' (16384 KB)...
OKAY [ 0.375s]
writing 'misc'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.406s

Can I restore a stock image i backed up with with twrp and go from there or will I need to reflash a tot/kdz and reflash twrp first?

steadfasterX said:
u can now re-lock your device with fastboot
important: you device must be FULLY STOCK BEFORE you lock it again! That means no TWRP, no custom ROM etc! otherwise you will brick the device
if you still want to use that method mentioned here:
Make a backup with SALT (basic mode is enough)
boot into fastboot:
Code:
[B]fastboot erase misc[/B]
is doing the same then the above mentioned way.
the misc partition contains also your IMEI, your MAC (wifi) and Bluetooth address. Those SHOULD be re-generated once you boot Android again but if not you will have the backup you created with SALT before.
.
Click to expand...
Click to collapse
C:\Windows\system32>fastboot erase misc
erasing 'misc'...
FAILED (remote: cannot erase this partition in unlocked state)
finished. total time: 0.031s

Koile said:
bootloader is unlocked again, but TWRP won't show the bin-files created and fastboot just returns:
Code:
> .\fastboot flash misc E:\salt_backup\misc.bin
target reported max download size of 536870912 bytes
sending 'misc' (16384 KB)...
OKAY [ 0.375s]
writing 'misc'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.406s
Click to expand...
Click to collapse
in twrp:
Code:
adb push misc.bin /tmp/
adb shell
dd if=/tmp/misc.bin of=/dev/block/bootdevice/by-name/misc
sync
Spaceboy60 said:
Can I restore a stock image i backed up with with twrp and go from there or will I need to reflash a tot/kdz and reflash twrp first?
Click to expand...
Click to collapse
really reflashing a kdz is your best option. everything must be stock (no twrp or other mods are in place) so flashing a kdz ensures you are good.
Spaceboy60 said:
C:\Windows\system32>fastboot erase misc
erasing 'misc'...
FAILED (remote: cannot erase this partition in unlocked state)
finished. total time: 0.031s
Click to expand...
Click to collapse
that happens when you are on v29a.
on v29a its just a fastboot cmd to lock again: https://forum.xda-developers.com/g4/general/managed-to-relock-bootloader-t3660282
keep in mind that your phone is better pure stock before doing this and it will 100% brick your phone when you have UsU'd your device.
.

steadfasterX said:
u can now re-lock your device with fastboot
important: you device must be FULLY STOCK BEFORE you lock it again! That means no TWRP, no custom ROM etc! otherwise you will brick the device
if you still want to use that method mentioned here:
Make a backup with SALT (basic mode is enough)
boot into fastboot:
Code:
[B]fastboot erase misc[/B]
is doing the same then the above mentioned way.
the misc partition contains also your IMEI, your MAC (wifi) and Bluetooth address. Those SHOULD be re-generated once you boot Android again but if not you will have the backup you created with SALT before.
.
Click to expand...
Click to collapse
steadfasterX said:
in twrp:
Code:
adb push misc.bin /tmp/
adb shell
dd if=/tmp/misc.bin of=/dev/block/bootdevice/by-name/misc
sync
really reflashing a kdz is your best option. everything must be stock (no twrp or other mods are in place) so flashing a kdz ensures you are good.
that happens when you are on v29a.
on v29a its just a fastboot cmd to lock again: https://forum.xda-developers.com/g4/general/managed-to-relock-bootloader-t3660282
keep in mind that your phone is better pure stock before doing this and it will 100% brick your phone when you have UsU'd your device.
.
Click to expand...
Click to collapse
I'm on marshmallow, not 29a
EDIT:reflashed back to stock, but command fastboot erase misc still comes up with an error about not being able to flash in an unlocked state.

MathiasR33 said:
Relock LG G4 Bootloader easily
First of all, I'm new here. So please tell me if I broke any rules or if I made any english mistakes.
Warning:
This guide will show you how to easily Re-Lock your Bootloader. Your Bootloader is then Locked! So, it's not really clever to lock the Bootloader when a Non-Stock-Rom is installed...
Requirements:
- LG G4 (H815) [This probably works with other LG's too]
- TWRP-Recovery installed or temporary booted using "fastboot boot"
- Stock-Android installed (Any Version)
- Flashable Bootloader/Boot Zip's for your Android-Version
For Android 6.0 you can get them here: https://forum.xda-developers.com/g4/development/stock-h815-20g-images-kdz-flashable-t3450503
How to Relock:
Step 1: Boot into TWRP
Step 2: Copy the Zip-Files to internal storage
Step 3: Go to Advanced/Terminal
Step 4: Perform this command:
Code:
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
Your bootloader is Non-Functional now... Don't reboot until the next steps are completed!
Step 5: Flash both Zip-Files using TWRP
Step 6: Reboot
You now have a G4 with stock ROM and locked bootloader. If you wish to uninstall TWRP (Its no longer working) just Flash a Stock kdz-File using LGUP
Hope I was able to help someone...
Click to expand...
Click to collapse
Hello, dear MathiasR33
I am asking you with a very polite request for technical support. I upgraded after OTA Wi-Fi to the latest version of Android MarshMallow 6.0.
Please help me in the next steps.
The fastboot devices command does not work for me.
I post a screen showing the version of my Firmeware in the LGUP.
And Screen from the CMD console saying that the fastboot devices command does not work.
Please, help me, I am waiting for your answer.

Updating Huawei P9 Lite h3g/it to Nougat

Hi everyone. I've already rooted my Huawei P9 lite and now I'd like to update it to Android Nougat.
I tried to install different versions of firmware through OTA, but none of them worked out well. I'm starting to think that this is due to the firmware which are not compatible with my device, and considering that my build number is quite uncommon, that could also be the case. I read from some threads that I have to unroot and lock the bootloader again in order to perform the update, but honestly I'm too lazy right now and I'd prefer to keep my device rooted if it's possible.
Does anybody know what could I do in this case?
OEM Build Number: VNS-L31ITAC555B160
OEM Product Model: HUAWEI VNS-L31
Vendor Country: h3g/it

xXRobyXx said:
Hi everyone. I've already rooted my Huawei P9 lite and now I'd like to update it to Android Nougat.
I tried to install different versions of firmware through OTA, but none of them worked out well. I'm starting to think that this is due to the firmware which are not compatible with my device, and considering that my build number is quite uncommon, that could also be the case. I read from some threads that I have to unroot and lock the bootloader again in order to perform the update, but honestly I'm too lazy right now and I'd prefer to keep my device rooted if it's possible.
Does anybody know what could I do in this case?
OEM Build Number: VNS-L31ITAC555B160
OEM Product Model: HUAWEI VNS-L31
Vendor Country: h3g/it
Click to expand...
Click to collapse
Hi,
you have to rebrand to the Global version (IMO) :
1. install TWRP 3.0.2.0 , Link
2. In TWRP flash C432 oeminfo.zip Link
3. Go back to TWRP's menu without reboot
4. Follow instructions (from step 3.).

-Alf- said:
Hi,
you have to rebrand to the Global version (IMO) :
1. install TWRP 3.0.2.0 , Link
2. In TWRP flash C432 oeminfo.zip Link
3. Go back to TWRP's menu without reboot
4. Follow instructions (from step 3.).
Click to expand...
Click to collapse
Thanks for your help. Is the VNS-L31C432B370 firmware compatible with single sim?

xXRobyXx said:
Is the VNS-L31C432B370 firmware compatible with single sim?
Click to expand...
Click to collapse
No, that's why I gave you the link to oeminfo dual Sim. If that's a problem for you, try looking for the B371, I didn't find one.

-Alf- said:
No, that's why I gave you the link to oeminfo dual Sim. If that's a problem for you, try looking for the B371, I didn't find one.
Click to expand...
Click to collapse
It's not a problem for me. What problems could I encounter if I use a dual sim firmware?

M
xXRobyXx said:
It's not a problem for me. What problems could I encounter if I use a dual sim firmware?
Click to expand...
Click to collapse
It has no effect on the phone's functionality.
Btw, there's B371 Link ,but it may be password protected . For Single SIM firmware use this Oeminfo.zip

-Alf- said:
M
It has no effect on the phone's functionality.
Btw, there's B371 Link ,but it may be password protected . For Single SIM firmware use this Oeminfo.zip
Click to expand...
Click to collapse
I tried to flash the C432 oeminfo, but after rebooting a black screen with red text appears and I can't unlock my phone because it's unable to decrypt the internal archive. Same thing with the singlesim oem info.
Also I can't mount the Internal Storage from TWRP because it results as 0 MB.
The only way I found to solve this issue is by restoring the original oeminfo from a previous backup.

xXRobyXx said:
tried to flash the C432 oeminfo, but after rebooting a black screen with red text appears
Click to expand...
Click to collapse
-Alf- said:
Go back to TWRP's menu without reboot
Click to expand...
Click to collapse

-Alf- said:
4. Follow instructions (from step 3.).
Click to expand...
Click to collapse
I've installed the с432b370 update correctly, but I can't flash the data package (update_data_full_VNS-L31_hw_eu.zip).

xXRobyXx said:
I've installed the с432b370 update correctly, but I can't flash the data package (update_data_full_VNS-L31_hw_eu.zip).
Click to expand...
Click to collapse
it happens sometimes...
Just to be sure - reboot to fastboot mode and run command:
fastboot oem get-build-number
and post result.

-Alf- said:
it happens sometimes...
Just to be sure - reboot to fastboot mode and run command:
fastboot oem get-build-number
and post result.
Click to expand...
Click to collapse
Now it is NRD90M test-keys, before it was VNS-L31ITAC555B160

xXRobyXx said:
Now it is NRD90M test-keys, before it was VNS-L31ITAC555B160
Click to expand...
Click to collapse
Okay, now read carefully:
1. Download TWRP for Nougat Link
2. Flash it over eRecovery (!)
using command:
fastboot flash recovery2 twrp3102.img (recovery2 , not recovery!)
3. Flash stock Recovery Nougat
Link use:
fastboot flash recovery xxxxx.img
4. Reboot, when yellow warning appears, press and hold Volume Up for 3-4 seconds, you should boot into TWRP
5. In TWRP select Wipe - Format data - yes - confirm. Go back - Reboot - System
6. And again, after yellow warning Volume Up and reboot TWRP. Now you can try install second .zip file hw_eu.
7. Reboot into Recovery and do factory reset.
Good luck!

-Alf- said:
Okay, now read carefully:
1. Download TWRP for Nougat Link
2. Flash it over eRecovery (!)
using command:
fastboot flash recovery2 twrp3102.img (recovery2 , not recovery!)
3. Flash stock Recovery Nougat
Link use:
fastboot flash recovery xxxxx.img
4. Reboot, when yellow warning appears, press and hold Volume Up for 3-4 seconds, you should boot into TWRP
5. In TWRP select Wipe - Format data - yes - confirm. Go back - Reboot - System
6. And again, after yellow warning Volume Up and reboot TWRP. Now you can try install second .zip file hw_eu.
7. Reboot into Recovery and do factory reset.
Good luck!
Click to expand...
Click to collapse
Code:
target reported max download size of 471859200 bytes
sending 'recovery2' (24462 KB)...
OKAY [ 0.713s]
writing 'recovery2'...
FAILED (remote: Command not allowed)
finished. total time: 0.713s
I'm sure that Phone and FRP are unlocked.

xXRobyXx said:
Code:
target reported max download size of 471859200 bytes
sending 'recovery2' (24462 KB)...
OKAY [ 0.713s]
writing 'recovery2'...
FAILED (remote: Command not allowed)
finished. total time: 0.713s
I'm sure that Phone and FRP are unlocked.
Click to expand...
Click to collapse
In other words, my instructions are wrong?
Okay, have a nice evening!

-Alf- said:
In other words, my instructions are wrong?
Okay, have a nice evening!
Click to expand...
Click to collapse
Hey, I'm not doubting your instructions! Hahaha.
I'm just asking, what should I do now? I can't flash TWRP to recovery2 if it doesn't allow me to commit any command.

xXRobyXx said:
doesn't allow me to commit any command.
Click to expand...
Click to collapse
And you are sure that Phone and FRP are unlocked? Hahaha.

-Alf- said:
And you are sure that Phone and FRP are unlocked? Hahaha.
Click to expand...
Click to collapse
Yeah

xXRobyXx said:
Yeah
Click to expand...
Click to collapse
Restart your phone, if the BL is really unlocked, after restart appears on screen yellow warning. Fastboot sometimes lies...

-Alf- said:
Restart your phone, if the BL is really unlocked, after restart appears on screen yellow warning. Fastboot sometimes lies...
Click to expand...
Click to collapse
Okay, finally I flashed TWRP. After restart, I pressed Volume Up key but it remains on the yellow warning screen with the text "Your device is booting now...".
Edit:
I solved this by installing Venus TWRP for P9 lite. Then, I followed all the instructions and updated to B416 through dlaod, and later to B418 through OTA. Additionally, I had to unlock the bootloader again and root.
Now I have a fully-functional P9 lite updated to Android Nougat

xXRobyXx said:
Hi everyone. I've already rooted my Huawei P9 lite and now I'd like to update it to Android Nougat.
I tried to install different versions of firmware through OTA, but none of them worked out well. I'm starting to think that this is due to the firmware which are not compatible with my device, and considering that my build number is quite uncommon, that could also be the case. I read from some threads that I have to unroot and lock the bootloader again in order to perform the update, but honestly I'm too lazy right now and I'd prefer to keep my device rooted if it's possible.
Does anybody know what could I do in this case?
OEM Build Number: VNS-L31ITAC555B160
OEM Product Model: HUAWEI VNS-L31
Vendor Country: h3g/it
Click to expand...
Click to collapse
Which process did you follow for the root?