[GUIDE][HUAWEI TAG-Lxx] P8 lite smart/GR3/Enjoy 5S Modding (unlock, root ecc...)

[GUIDE][HUAWEI TAG-Lxx] P8 lite smart/GR3/Enjoy 5S Modding (unlock, root ecc...) - Android General

INFO
This device have different names in different countried (TAG-L01/L03/L13/L21/L22/L23 ecc..), but they are the same, everything writed in this post work on every TAG-Lxx device.
DISCLAIMER FOR ANDROID 6.0
A lot of people asked me to port android 6 or 7, so i answer once and for all:
I have alredy tryed but kernel needs some changes, the problem is that kernel source code they provided is simply incomplete! Compiled kernel without any mods don't boot at all
I've checked and i found that the first problem that cause this is missing/wrong lcd driver(this is the first but i think there are a lot of other driver missing)
So this are the options:
-fix it myself and add drivers from other device(already tried, risked to damage my device, i won't do anymore)
-ask huawei for correct source(i will try)
-find a way to bypass this changing android source(if kernel is not compatible by android, i can make android compatible with kernel), but its not easy
STOCK ROM
Single sim version(system dump of TAG-L01)
I can't find it on internet, so i have created a flashable zip that contains system and boot dumped from my device(using TAG-L22 offical one, because this is the only firmware i have found)
update.zip
if something goes wrong place it into your sdcard, reboot into recovery and flash it, your device is now fully working
-build: TAG-L01C212B123
-brand:TIM
-rooted:yes
this is my dump:
https://www.androidfilehost.com/?fid=24591000424961455
This zip contains boot recovery and system image of my device.
Dual sim version(offical TAG-L22, work on every dual sim variant)
official download link
UNLOCKING BOOTLOADER
Unlock bootloader is the same for all huawei devices:
-enable developer options(7 tap on build number)
-enable "oem unlock"
-go into http://emui.huawei.com/en/plugin.php?id=hwdownload and register an account
-select chinese language (is important, otherwise you can't access bootloader unlock page)
-click on the green lock and select first choice
-accept
-you are now into bootloader unlock page
{
"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"
}
-serial number can be found in settings/about phone/state
-IMEI have to be in the phone box
-product id can be found writing *#*#1357946#*#* in phone dialer
-solve captcha and click on the blue button
-you have bootloader unlock code
-MAKE A BACKUP, BECAUSE WHEN YOU UNLOCK YOUR DEVICE WILL BE FACTORY RESET
-put your indevice in bootloader mode(by using "adb reboot bootloader" or by volume up+power and selecting fastboot mode)
-type "fastboot oem unlock yourcode" (i suggest to write code letter by letter, copy-paste has not worker for me)
-type "fastboot oem get-bootinfo" and you have to see unlocked:yes
-type "fastboot reboot" to reboot into android
ROOT
recommender method(need an unlocked bootloader):
-Install twrp(look under for the link)
-download supersu
-reboot into recovery and flash it
phone can be rooted also without unlocking bootloader, but if something goes wrong to fix you need an unlocked bootloader, and i'm receveing a lot of report of people who have bricked, so i won't show how to do it anymore.
Restore huawei bootlogo(for branded devices)
Thanks a lot @ervius !
download
simply run logo_huawei.bat (or, if you are on linux read that and run all commands inside)
If SIM card is not recognised:
Sometimes, if you wipe data or change rom you will face this problem, fix is easy(but need root):
-go into / and delete nvdata folder(you will see a "read-only filesystem" message, ignore it)
-reboot(not soft reboot, normal reboot)
CUSTOM RECOVERY
TWRP 3.0.2-0
CUSTOM ROMS
Cyanogenmod 12.1
XPOSED
Official thread
-download Xposed for EMUI 3.1 Android 5.1.1 arm64 version
-flash it using twrp
-download and install this apk
NOTE:some module won't work because this device have emui

Thanks, I've been waiting weeks for this!
Can confirm TWRP works on my GR3 (TAG-L13) and was able to SuperSU from there.

felzam said:
Thanks, I've been waiting weeks for this!
Can confirm TWRP works on my GR3 (TAG-L13) and was able to SuperSU from there.
Click to expand...
Click to collapse
Good
Now you can also install xposed and other mods, i'm uploading a zip that fully re-stock this device, so if something goes wrong you can easily restore (some kind of "official firmware" but based on my dump, because official does not exist)
edit: ah ok, you have a TAG-L13, so probably with this firmware your sim wont work

what about tag l21

MedNour said:
what about tag l21
Click to expand...
Click to collapse
This guide will work and TWRP also, TAG-L01 and TAG-L21 are identical, the only problem is dual sim(so if i will succed compiling cyanogenmod, you probably can't use your sim)

mac12m99 said:
This guide will work and TWRP also, TAG-L01 and TAG-L21 are identical, the only problem is dual sim(so if i will succed compiling cyanogenmod, you probably can't use your sim)
Click to expand...
Click to collapse
good news then but i will be able to use 1 sim and micro sd ????

mac12m99 said:
This guide will work and TWRP also, TAG-L01 and TAG-L21 are identical, the only problem is dual sim(so if i will succed compiling cyanogenmod, you probably can't use your sim)
Click to expand...
Click to collapse
Cyanogenmod would be wonderful! I have major push notification problems while on WiFi and would love to move away from EMUI. Would it work on different versions though (on any TAG-LXX)?

MedNour said:
good news then but i will be able to use 1 sim and micro sd ????
Click to expand...
Click to collapse
Micro sd not, but probably all sims will not work
felzam said:
Cyanogenmod would be wonderful!
Click to expand...
Click to collapse
Yes
I have compiled succesiful, but don't boot, i need more time...
felzam said:
I have major push notification problems while on WiFi and would love to move away from EMUI.
Click to expand...
Click to collapse
Settings, protected apps, allow all apps that you want notification
felzam said:
Would it work on different versions though (on any TAG-LXX)?
Click to expand...
Click to collapse
Yes, but in dual sim devices proably sim will not work

Just wanted to say i'm also looking forward to see if an update to Android 6 is possible.

TheEversor said:
Just wanted to say i'm also looking forward to see if an update to Android 6 is possible.
Click to expand...
Click to collapse
There is only a stock rom on internet and is android 5.0(for TAG-L22), so for now no 6.0
My goal is compiling cyanogenmod 13(whitch is based on android 6), but it will take a lot of time.

mac12m99 said:
There is only a stock rom on internet and is android 5.0(for TAG-L22), so for now no 6.0
My goal is compiling cyanogenmod 13(whitch is based on android 6), but it will take a lot of time.
Click to expand...
Click to collapse
I'm absolutely new to this kind of things, but would it be theoretically possible to cook the huawei rom for the Honor 5X (also known as GR5) that is Android 6, adding the drivers of the official Android 5 huawei rom of the GR3 or TAG-L01 ?

TheEversor said:
I'm absolutely new to this kind of things, but would it be theoretically possible to cook the huawei rom for the Honor 5X (also known as GR5) that is Android 6, adding the drivers of the official Android 5 huawei rom of the GR3 or TAG-L01 ?
Click to expand...
Click to collapse
No, because has different hardware, i have to found a device that have the same processor whitch have android 6.0, but i will do late, first i have to build cm12.1(based on the same android version that have this device)

Hang on boot and adb driver problem
Dear friends, I made a little mess and I need your help.
I followed the guide by mac12m99, but I did some mistakes. A little recap:
1) I became developer (7 taps on build) -> OK
2) I enabled ADB debug, OEM unlock -> OK
3) Connected the phone while OS was running and did "adb reboot bootloader" -> OK
the phone booted in "fastboot mode". Now I had a problem: I cannot connect the phone anymore: if I tried "adb devices" no device was found. I think this is a driver related problem (I use Win 7 64bit). I googled a lot, but I wasn't able to find a working driver to solve this issue.
And now I made my BIG mistake! Since I couldn't connect the phone correctly to unlock the bootloader, I tried Kingroot -> success. But I don't like Kingroot much, due to many permissions requested. So I switched Kingroot with superSU using a guide from another forum (sorry I cannot post links).
During the process superSU asked for upgrading and I did -> success, but... after reboot the phone hung on boot.
Panic! tried to factory reset it, but after boot still hung.
Now I don't know how to proceed.
So I need your help:
1) Where can I find the correct driver to connect Win7 64 bit to the phone in fastboot mode ?
2) How could I revive the phone ? I thought if I successfully connect the phone in fastboot mode, maybe I could unlock the bootloader and see if the boot proceeds.
Thank you for your help, and sorry form my English and my ignorance.

mac12m99 said:
INFO
...
I can't find it on internet, so i have created a flashable zip that contains system and boot dumped from my device(using TAG-L22 offical one, because this is the only firmware i have found)
[ mediafire URL ]
if something goes wrong place it into your sdcard, reboot into recovery and flash it, your device is now fully working
-build: TAG-L01C212B123
-brand:TIM
-rooted:yes
Click to expand...
Click to collapse
Sorry but this content has been removed from Mediafire. Could you upload it again? Thankyou

Hang on boot and adb driver problem - update
OK I solved the first problem: it was a driver related problem as suspected. I succeeded to flash recovery and from there superSU, but after reboot still hang. So I need the stock image to revert the situation. I didn't understand well which image I should use: the first one from Mediafire (not available) or the second one: dumped from your device ? If I should use the second one: what is the procedure? Thank you

Triglia said:
OK I solved the first problem: it was a driver related problem as suspected. I succeeded to flash recovery and from there superSU, but after reboot still hang.
Click to expand...
Click to collapse
Did you unlocked the bootloader?(i guess yes, because twrp booted)
If yes, you have done a factory reset, so it needs 3-4 minutes to re-create cache and then will be working
Triglia said:
So I need the stock image to revert the situation. I didn't understand well which image I should use: the first one from Mediafire (not available) or the second one: dumped from your device ? If I should use the second one: what is the procedure? Thank you
Click to expand...
Click to collapse
They have blocked it
If waiting don't work, for now do this:
-go here
-search for gr3
-download firmware
-flash it using twrp
If you have a TAG-L01 SIM will not work, but device is usable.
If you use the second one you can only flash stock recovery, because system partition is refused by bootloader , but i think you can flash it using adb and twrp(an advanced method, i you want i can explain )

mac12m99 said:
Did you unlocked the bootloader?(i guess yes, because twrp booted)
If yes, you have done a factory reset, so it needs 3-4 minutes to re-create cache and then will be working
They have blocked it
If waiting don't work, for now do this:
-go here
-search for gr3
-download firmware
-flash it using twrp
If you have a TAG-L01 SIM will not work, but device is usable.
If you use the second one you can only flash stock recovery, because system partition is refused by bootloader , but i think you can flash it using adb and twrp(an advanced method, i you want i can explain )
Click to expand...
Click to collapse
Since I'm using TAG-L01 TIM branded, I think I should use your dump. Please explain me how to do. Meanwhile I'm downloading your image.
What do you mean that the SIM won't work? I cannot use it as a telephone anymore???!!!
Thank you.

Triglia said:
Since I'm using TAG-L01 TIM branded, I think I should use your dump.
Click to expand...
Click to collapse
So waiting have not worked?
Triglia said:
Please explain me how to do. Meanwhile I'm downloading your image.
Click to expand...
Click to collapse
-boot into twrp
-place system.img in internal sdcard
-type this:
Code:
adb shell
dd of=/sdcard/system.img if=/dev/block/mmcblk0p22
-flash boot.img using the recovery method(install-install image ecc..)
-reboot and wait 3-4 minutes
But if my firmware wasn't deleted, you can restore by easily flash the zip
Triglia said:
What do you mean that the SIM won't work? I cannot use it as a telephone anymore???!!!
Click to expand...
Click to collapse
Because my firmware was deleted, i've linked to you the only "official firmware", that is for the TAG-L22, i've tested it on TAG-L01 and everything work but SIM not(this firmware is not branded), it means that using this will not work, but if you install another that work, SIM will work
Triglia said:
Thank you.
Click to expand...
Click to collapse
Welcome

mac12m99 said:
So waiting have not worked?
-boot into twrp
-place system.img in internal sdcard
-type this:
Code:
adb shell
dd of=/sdcard/system.img if=/dev/block/mmcblk0p22
-flash boot.img using the recovery method(install-install image ecc..)
-reboot and wait 3-4 minutes
But if my firmware wasn't deleted, you can restore by easily flash the zip
Because my firmware was deleted, i've linked to you the only "official firmware", that is for the TAG-L22, i've tested it on TAG-L01 and everything work but SIM not(this firmware is not branded), it means that using this will not work, but if you install another that work, SIM will work
Welcome
Click to expand...
Click to collapse
Waited for about 15 min. but still hang.
In the file image "zt...G-L01_stock.gz", there is only 1 file "HUAWEI TAG-L01 stock" about 3.8Gb uncompressed. There is no "system.img " file.
I cannot restore a different ROM, I need to use the phone. Please could you send me the correct file? I sent you a private message with my direct contacts.

[SOLVED] hang at boot after Kingroot to superSU switch
After 2 days of test, and with the essential help of mac12m99 :highfive:,
I succeeded to revive my phone. It was necessary to flash the "update.zip" from the first post (but unavailable in the last days) and my phone was back, then I started again from scratch.
A suggestion: DO NOT try to switch from Kingroot to superSU using "superSUME", because you'll end in soft brick as I did.
If you gained root access through Kingroot and you want to switch to superSU, you should do the following:
1) Be sure that Kingroot is installed and working
2) Disable root from Kingroot itself, and uninstall Kingroot (you can do everything within Kingroot's options)
3) reboot in recovery (TWRP)
4) install superSU from TWRP
5) reboot: you are rooted again but with superSU and the phone is still working :good:
So, a big THANK YOU to mac12m99, for his precious help and patience and happy modding to everyone.

Related

[Q] HTC One E8 - root guide help

Can anyone give a step by step root guide of this phone on lollipop version 5.0.2? i wanna try rooting

nisekoi said:
Can anyone give a step by step root guide of this phone on lollipop version 5.0.2? i wanna try rooting
Click to expand...
Click to collapse
May i know what is the varient of your phone? Because the method i followed is to root my E8 M8sX single sim. Im not sure if daul sim will cause a problem or not.
Firstly, you need an unlocked bootloader which can be unlocked through htcdev. You will need to create an account and follow the steps on the website. By unlocking the bootloader, it will wipe away all your data(messages, contacts, Apps etc.) on your phone so do a BACKUP before proceeding on the website.
Next, you will need a TWRP (which is a custom recovery to flash custom ROMs and root). TWRP can be found here. Finally, you need a flashable SuperSU to install through TWRP from here. Save the TWRP and SuperSU zip files on your sd card.
Then, follow the steps in this link. Download Minimal ADB and fastboot. Skip step 2 on the page after the one to download adb and fastboot. Just go straight to command without turning off your phone. Also, there is no need to download TWRP and SuperSU again from the page.
If you encounter any errors during the rooting process, just stop and get back to the state where the device is still bootable and for daily use. Ask me and i will try to reply ASAP.
**Disclaimer: I am in no way responsible if your device becomes unusable after the rooting process. Btw, Nisekoi is quite fun to watch but becomes draggy in the manga

JuzARandomGuy said:
May i know what is the varient of your phone? Because the method i followed is to root my E8 M8sX single sim. Im not sure if daul sim will cause a problem or not.
Firstly, you need an unlocked bootloader which can be unlocked through htcdev. You will need to create an account and follow the steps on the website. By unlocking the bootloader, it will wipe away all your data(messages, contacts, Apps etc.) on your phone so do a BACKUP before proceeding on the website.
Next, you will need a TWRP (which is a custom recovery to flash custom ROMs and root). TWRP can be found here. Finally, you need a flashable SuperSU to install through TWRP from here. Save the TWRP and SuperSU zip files on your sd card.
Then, follow the steps in this link. Download Minimal ADB and fastboot. Skip step 2 on the page after the one to download adb and fastboot. Just go straight to command without turning off your phone. Also, there is no need to download TWRP and SuperSU again from the page.
If you encounter any errors during the rooting process, just stop and get back to the state where the device is still bootable and for daily use. Ask me and i will try to reply ASAP.
**Disclaimer: I am in no way responsible if your device becomes unusable after the rooting process. Btw, Nisekoi is quite fun to watch but becomes draggy in the manga
Click to expand...
Click to collapse
Thanks for your reply. My phone is m8sx single sim just like yours. You mean by "stop and get back to the state where the device is bootable" is restore the phone from it backup?
** i watched the nisekoi anime only. will read the manga later.

nisekoi said:
Thanks for your reply. My phone is m8sx single sim just like yours. You mean by "stop and get back to the state where the device is bootable" is restore the phone from it backup?
** i watched the nisekoi anime only. will read the manga later.
Click to expand...
Click to collapse
Well, yeah thats what i meant. One way just to be safe would be after flashing twrp, boot to homescreen. After that then flash SuperSU. Other than while unlocking the bootloader will wipe away everything, i don't think flashing twrp and supersu will cause your phone to brick. Now knowing that we have the same varient then things should also go smoothly with yours. Do take note that the phone may take longer to boot after factory reset.
Just in case you didn't know, in order to boot the phone to recovery is by pressing power and volume down at the same time while the phone is off.

JuzARandomGuy said:
Well, yeah thats what i meant. One way just to be safe would be after flashing twrp, boot to homescreen. After that then flash SuperSU. Other than while unlocking the bootloader will wipe away everything, i don't think flashing twrp and supersu will cause your phone to brick. Now knowing that we have the same varient then things should also go smoothly with yours. Do take note that the phone may take longer to boot after factory reset.
Just in case you didn't know, in order to boot the phone to recovery is by pressing power and volume down at the same time while the phone is off.
Click to expand...
Click to collapse
I can't find the fast boot option under settings/power.
i can already boot to recovery.

nisekoi said:
I can't find the fast boot option under settings/power.
i can already boot to recovery.
Click to expand...
Click to collapse
They removed the fastboot option for lollipop. I think they set it on by default but it seems to boot slower compared to kitkat.

JuzARandomGuy said:
They removed the fastboot option for lollipop. I think they set it on by default but it seems to boot slower compared to kitkat.
Click to expand...
Click to collapse
I still get stuck at the unlocking the bootloader. In step 5, it asked to enter this command "fastboot oem get_identifier_token" but it says that " the program cants start because AdbWinApi.dll is missing". I did follow the steps correctly.

Download Android sdk and update it

nisekoi said:
I still get stuck at the unlocking the bootloader. In step 5, it asked to enter this command "fastboot oem get_identifier_token" but it says that " the program cants start because AdbWinApi.dll is missing". I did follow the steps correctly.
Click to expand...
Click to collapse
snoopyhaeckers said:
Download Android sdk and update it
Click to expand...
Click to collapse
Did the solution work? On google also says to just update android sdk for htc drivers.

JuzARandomGuy said:
Did the solution work? On google also says to just update android sdk for htc drivers.
Click to expand...
Click to collapse
yup it works for me. but now i can't flash the TWRP recovery. it keep saying " error: can't load twrp.img ". i did change the name of the twrp file to twrp.img in my pc.
i did managed to flash the custom recovery... the instruction is not clear. so i search for other information. it turns out i hve to put the twrp file in the same folder as minimal adb

How to root and update htc e8 android version
Hello,
Please I need steps to root my HTC E8 and upgrade the android version.
HTC E8, M8sn Single SIM, Android 4.4.2

[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM]

The S5 Bootloader Unlock is here! Huge thanks to @beaups for the research and sourcecode and tool, @ryanbg for researching this method in the firstplace, @autonomousperson For compiling the source to a app for us all, @haggertk for his CID and aboot! @jrkruse for innovating methods, one click apps, and MM methods @magic_man185 for recompiling the binary to disable SD requirements for MM, and everyone else for being patient for me being slow! Also thank you all for being a great supportive community!
I Have Updated the OP Hoping this is less messy and hopefully neater to deal with
DO NOT ASK ABOUT ROMS, KERNELS, OR OTHER THINGS. THIS IS ONLY FOR UNLOCKING THE BOOTLOADER. WE WILL LAUGH AT YOU IF YOU ASK ANYWAYS!!!EMMC 15 Unlocking Bootloader
2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom . Downloads S5_Root_Tools_2023.7z EMMC_15_Rom.zip -- Stock QL1 6.0 Directions For Unlocking Stock Phone I would...
forum.xda-developers.com
EMMC 15 Updating Unlocked Bootloaders Or Downgrading
2022_VZW_EMMC_15_Chipset For Unlocked Dev BL To Downgrade To LL_KK Or Upgrade To MM_And Keep Unlock Bootloader
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4 Root And Unlock Instructions Can Be Found Here EMMC 15 Rooting And Bootloader Unlocking EMMC 11...
forum.xda-developers.com
For Rooting EMMC 11 Phones
2021_VZW_Locked_Bootloader_EMMC_11_Rooted/NonRooted_Roms_With_Safestrap_MM_LL_KK
This Process Will Install On The EMMC_11 Locked Bootloader Verizon S5 Marshmallow QL1 Stock Rom NonRooted With Safestrap. Lollipop PB1 Stock Rom Rooted With Safestrap. KK Rom Rooted With Safestrap What This Does This gives you the ability to...
forum.xda-developers.com
All the methods below are only preserved for historical purposes!!! Please use the new methods above!
Warnings
READ THE ENTIRE OP AND THE POST BELOW BY @jrkruse BEFORE DOING ANYTHING AT ALL!!!!!!!!!!
THIS IS ONLY FOR THE VERIZON S5. DOES NOT WORK FOR AT&T!!!!!
This is for users with 15' Sasmung eMMC's not users with 11 Toshiba eMMC's. You can check this by reading the file
/sys/block/mmcblk0/device/cid
Just the first 2 15xxxxxxxxxxxxxxxxxxxxxx or 11xxxxxxxxxxxxxxxxxxxxxxx(my number of x's are random, just read the first 2)
We still are unsure if changing the CID causes app store, verification, activation, provision, or other issues, everything you do is at your own risk!(Pretty sure it's safe)
REACTIVATION LOCK MUST BE TURNED OFF. YOU'VE BEEN WARNED
Starting notes
*REQUIRES ROOT*
If you don't have root, please goto @jrkruse thread here
https://forum.xda-developers.com/ve...ot-method-t3561529/post71202995#post71202995/
For Method 4
You must make sure first of all you have authorized your computer in developer options and that USB debugging is on, you could also using adb tools use adb wireless if your device is configured for this!
You also on screen must grant ADB root access, please make sure of this!
Make sure you have a blank sd card, EVERYTHING on it WILL BE WIPED as a backup for the bootloader!
*If you have no root access OR SAFESTRAP you must proceed to the rooting thread, nothing below works without root*
Methods
Method 1: Primary Method (Old thanks @jrkruse) For PB1, PD1, PF4, PG2, PJ2, PL1, QA1 (MARSHMALLOW)*REQUIRES SAFESTRAP
Download these files
Bootloader_Unlock_Safestrap.apk
VZW_BPB1_ODEX_DEODEX_V9.zip
G900V_Firmware_PB1.tar.md5
S5_KLTE_USA_VZW.pit
Download and install VZW_BPB1_ODEX_DEODEX_V9.zip
Reboot to Download Mode
In Odin Under AP slot load G900V_Firmware_PB1.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
After Phone reboots pull battery reboot to download mode (pwr+voldwn+home) and make sure current binary status is official If not In Odin Under AP slot load G900V_Firmware_PB1.tar.md5 and Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
If current binary is official reboot phone and enter Rom Setup. There is no need to setup any accounts unless you plan on running this rom
Download and install Bootloader_Unlock_Safestrap.apk
Open Safestrap app and install the safestrap recovery to the system
Open safetrap app and click Reboot To Recovery Button
Flash: (Choose 1 Whatever One You Choose Is The Firmware And Bootloader Version You Will Be On)
SafeStrap_PB1_Bootloader_Unlock_AIO.zip
SafeStrap_PD1_Bootloader_Unlock_AIO.zip
SafeStrap_PF4_Bootloader_Unlock_AIO.zip
SafeStrap_PG2_Bootloader_Unlock_AIO.zip
SafeStrap_PJ2_Bootloader_Unlock_AIO.zip
SafeStrap_PL1_Bootloader_Unlock_AIO.zip
SafeStrap_QA1_Bootloader_Unlock_AIO.zip
Phone will Power Off.
Pull Battery enter TWRP Recovery (volup+pwr+home) Wipe Data and System and Flash A Rom That matches Firmware For example PB1 would be a 5.0 rom PD1 Or PF4 would be 6.0.1 Rom
Method 2: Unlocker via Safestrap (Old thanks @jrkruse) For OE1, OK3, PB1 (LOLLIPOP)
1. Flash this Samsung_Bootloader_Unlocker.zip in safestrap or flashfire
2. Reboot phone click on SamsungUnlocker app
3. Wait and make sure to grant SuperSu access. This may take a few seconds to come up
4. type yes in the terminal screen when it ask you (Yes/No) Hit enter on the keyboard
5. wait for phone to power off
6. reboot to bootloader and verify it says MODE: Developer
7. Flash Twrp recovery using Odin
8. Your done!
Method 3: ADB For 4.4-5.0 (OLD, OUTDATED)
This Method is old and outdated, Do not use unless the new method isn't working!!!
1. Download https://github.com/beaups/SamsungCID/blob/master/samsung_unlock
2. Download View attachment adb.7z
3. Extract adb to /adb
4. Extract samsung_unlock
5. Put samsung_unlock inside the adb folder
6. Launch adb tools
7. Select push file
8. Source is samsung_unlock
9. Destination is /data/local/tmp/
10. Select the option for Pull
11. Source is /sys/block/mmcblk0/device/cid
12. Destination is cid.txt
13. Select the option for adb shell
14. Continue after the warning
15. type the following
Code:
su
cd /data/local/tmp/
chown root.root samsung_unlock
chmod 777 samsung_unlock
./samsung_unlock
Device will shut down, manually reboot
16. once it reboots, in adb tools connect to the shell again
17. Enter the following commands
Code:
su
cd /data/local/tmp/
./samsung_unlock
18. once this is done, you can type exit twice to return to the menu of adb tools
19. Select reboot
20. Reboot to bootloader
21. Verify you now have a dev edition
Method 4: On Device For 4.4-5.0 (OLD, OUTDATED)
This Method is old and outdated, Do not use unless the new method isn't working!!!
1. On your device download https://github.com/beaups/SamsungCID/blob/master/samsung_unlock
2. Move to your root directory of your internal storage(if you can't figure out where that is, you shouldn't be doing this)
3. Using a root file explorer goto /sys/block/mmcblk0/device
4. Copy the file cid to your internal storage(this is a backup of your old cid, if it fails to copy, just open it as text and copy paste the text)
5. open a terminal emulator app
6. type the following
Code:
su
cd /storage/emulated/0/
chown root.root samsung_unlock
chmod 777 samsung_unlock
./samsung_unlock
7. Device will poweroff, focefully power on
8. Enter the terminal again and enter the following commands
Code:
su
cd /storage/emulated/0/
./samsung_unlock
9. Once completed reboot to bootloader using your favorite way
10. Verify you are a Developer edition phone now
Photo of what your Bootloader should say
{
"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"
}
Working TWRP and International Rom Patch

TWRP 3.0.0 Flashable recovery zip. Can be flashed in safestrap or flashfire if you have not installed it yet
TWRP_3.0.0-0-klte-klte.zip
International Rom Patch For Data And MMS. Flash right after you flash the rom.
VZW_5.0_International_Rom_Patch_No_Boot.zip
VZW_5.0_International_Rom_Patch_VZW_BOOT.zip
Directions To Update Or Downgrade Bootloaders
If you have already Unlocked your bootloader and are running TouchWiz Rom(Stock kernel)
Download this files
PB1_Firmware_Only_NK2_Kernel.tar.md5
TWRP_Prepare.zip
SafeStrap_PB1_Bootloader_Unlock_AIO.zip
SafeStrap_PD1_Bootloader_Unlock_AIO.zip
SafeStrap_PF4_Bootloader_Unlock_AIO.zip
SafeStrap_PG2_Bootloader_Unlock_AIO.zip
SafeStrap_PJ2_Bootloader_Unlock_AIO.zip
SafeStrap_PL1_Bootloader_Unlock_AIO.zip
SafeStrap_QA1_Bootloader_Unlock_AIO.zip
S5_KLTE_USA_VZW.pit
In TWRP Flash TWRP_Prepare.zip
Reboot to Download Mode
In Odin Under AP slot load PB1_Firmware_Only_NK2_Kernel.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
When finished on reboot watch for Safestrap Splash Screen and enter Safestrap
Now goto Power Menu/Reboot Menu and reboot to Download Mode
Make sure in download mode the current binary is Official. If it is not reflash In Odin Under AP slot load PB1_Firmware_Only_NK2_Kernel.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit
Click Start on reboot enter Safestrap reboot back to download mode and make sure binary status is Official
If Binary Status is Official Pull battery restart and enter SafeStrap
Flash: (Choose 1 Whatever One You Choose Is The Firmware And Bootloader Version You Will Be On)
SafeStrap_PB1_Bootloader_Unlock_AIO.zip
SafeStrap_PD1_Bootloader_Unlock_AIO.zip
SafeStrap_PF4_Bootloader_Unlock_AIO.zip
SafeStrap_PG2_Bootloader_Unlock_AIO.zip
SafeStrap_PJ2_Bootloader_Unlock_AIO.zip
SafeStrap_PL1_Bootloader_Unlock_AIO.zip
SafeStrap_QA1_Bootloader_Unlock_AIO.zip
Phone will Power Off.
Pull Battery enter TWRP recovery Wipe Data and System and Flash A Rom That matches Firmware For example PB1 would be a 5.0 rom PD1 Or PF4 would be 6.0.1 Rom
[FIX] MM Users. Wifi not working? Hardkeys not working???

View attachment 3772847
Unzip recover.zip place on internal storage flash in TWRP choose install image then choose recovery.img and flash to recovery
power off device
reboot to bootloader and reflash PD1_Firmware_Modem_HLOS_No_Aboot.tar.md5 in odin uncheck auto reboot when done pull battery reboot back to recovery wipe data and cache and system reinstall rom.
Notes:
If You Bricked Your Device somehow someway

1. Download the following image https://www.androidfilehost.com/?fid=24562946973631519
2. Download https://sourceforge.net/projects/win32diskimager/
3. Attach a micro sdcard(min 16GB class 10, others may work but unsure) to your PC via a reader
4. Backup all data on the micro sdcard, EVERYTHING WILL BE ERASED
5. Extract the image from the zip
6. Select write option, select the img file, select SDcard
7. Now write
8. Pop the Sdcard into the phone, and try and power it up
9. When you do open download mode
10. Goto odin and flash a FULL STOCK TAR
11. Start from scratch
To reuse the card it will need to be formatted using fdisk, diskpart, or android
If you have issues flashing modems, firmware, or anything
jrkruse said:
Ok here is the solution
The Stock Boot.img and Stock Recover.img that match your firmware must be flashed before any firmware can be updated on your phone. What I mean by firmware is the things other than images that are flashed in odin like the modem.bin. If your just wanting to flash a custom boot or recovery image then you can just flash them you and dont need to do any of this.
So after the Stock and Recovery images are flashed the phone needs to return to a power off state. Then a reboot to stock recovery and wipe the cache. Then reboot the phone and the goto bootloader mode from there.
After doing this the phone will allow firmwares to be flashed through odin.
Instructions
Flash the Kernel_Recovery Only either odin package or zip package in custom recovery
If using Odin uncheck reboot now then flash Kernel_Recovery package pull battery Reboot to recovery (Pwr+Hme+VolUp) wipe cache reboot phone then reboot back to bootloader and flash whatever your wanting to upgrade.
Reboot phone make sure your changes applied the you can flash your custom recovery again
If Flashing In recovery, flash the zip then reboot to recovery which will now be stock recovery and wipe cache and then power off Do not reboot, the phone must go to a poweroff state
Reboot phone then reboot to bootloader and use odin to update what ever your needing to do
Reboot Phone make sure your changes took. Then reboot back to odin and flash custom recovery or use flashfire or safestrap to flash the custom recovery zip.
If for some reason the bootloader becomes locked again simply do the unlock procedure again
https://www.androidfilehost.com/?w=files&flid=53300
Click to expand...
Click to collapse
To make the SD card usable again, format using android!
Or keep it as a backup
IF YOU FLASH STOCK BACK TO THE PHONE, IT WILL RELOCK THE BOOTLOADER, Requiring your run the script ONCE and it will be unlocked again
Source Located @ https://github.com/beaups/SamsungCID
beaups said:
its done
If any bounties applicable, please donate to "make a wish foundation" or @ryanbg (he's getting married)
--beaups
Click to expand...
Click to collapse
Sourcecode
https://github.com/beaups/SamsungCID
eMMC 11 is non-exploitable
http://forum.xda-developers.com/ver.../toshiba-11-series-bootloader-unlock-t3349346

Updated 04-08-23!!
2023 EMMC_11 Exploit To Root And Flash Custom Boot And Recovery Images Allowing Custom Roms To Be Used
This process will allow flashing custom boot and recovery images on EMMC11 S5 Yes this will allow the EMMC11 S5 to run custom roms like Lineage Than You ryanbg Summary Of What This Does You must be on G900VVRU2DPD1 bootloader for the exploit too...
forum.xda-developers.com
EMMC_11 S5 phones now have an explot that allows flashing custom boot and recovery images giving the ability to run custom AOSP based roms such as Lineage and root with Magisk root on android 6.0 bootloaders. It is not a bootloader unlock so no custom images can be flashed with odin

jrkruse said:
It doesn't work dev bootloaders are specific to the phone they don't work on other phones even other dev phones
Click to expand...
Click to collapse
I read in another forum somewhere about someone editing a hex value in a kernel to allow it to be loaded by odin (I think by changing some kind of version or product number). I expect if a VZW dev edition bootloader is specific to the phone, it incorporates some kind of IMEI or ESN check. Maybe it's possible to change that in the bootloader? Or perhaps it would work by spoofing the IMEI of the phone?

I think it's some kind of shared key encryption and that won't work

Going to take a peek then, I need a bootloader dump please? Anyone got a Dev Edition GS5?
Knowing verizon it's got a boot signature key probably with Secureboot. Damn
If thats the case, Another dead end?

GeTex said:
Going to take a peek then, I need a bootloader dump please? Anyone got a Dev Edition GS5?
Knowing verizon it's got a boot signature key probably with Secureboot. Damn
If thats the case, Another dead end?
Click to expand...
Click to collapse
Would this help?
https://docs.google.com/file/d/0B8a454A1K5eOSEJFMEZTUmMyeTg/edit
Sent from my Motorola XT912 using XDA Labs

Bobcus Leper said:
Would this help?
https://docs.google.com/file/d/0B8a454A1K5eOSEJFMEZTUmMyeTg/edit
Sent from my Motorola XT912 using XDA Labs
Click to expand...
Click to collapse
Unfortunately, no. That only includes the kernel and ROM itself. What we need is an img of a vzw dev edition aboot.mbn. This can be acquired using the dd command.
I was looking at some of the many long threads regarding attempts at unlocking the galaxy s4 as well as beaups' galaxy s5 developer edition hack, and I've come to think that what beaups did is to edit some unprotected small flag or string somewhere which is accessed by a developer ed. bootloader to check whether the phone matches the bootloader. He ran his program FIRST, then flashed what I suspect to be a signed dev edition bootloader which booted. If we can pick through the dev edition aboot.mbn with IDA pro and see where in memory the bootloader is checking to verify the phone, maybe we can copy his exploit.
If beaups had some kind of other exploit (to bypass security or other checks), there would be no reason for him to flash a new aboot.mbn, or even if so, he would have to edit some kind of string anyways to get the dev edition bl to work.
does anyone have any thoughts or feedback (or dev edition bootloaders)?

I figure I can make this work but I need a bootloader dump.

There's a guy who just posted about selling his dev edition, maybe he'd supply you with the dump??

Hariiiii said:
Unfortunately, no. That only includes the kernel and ROM itself. What we need is an img of a vzw dev edition aboot.mbn. This can be acquired using the dd command.
I was looking at some of the many long threads regarding attempts at unlocking the galaxy s4 as well as beaups' galaxy s5 developer edition hack, and I've come to think that what beaups did is to edit some unprotected small flag or string somewhere which is accessed by a developer ed. bootloader to check whether the phone matches the bootloader. He ran his program FIRST, then flashed what I suspect to be a signed dev edition bootloader which booted. If we can pick through the dev edition aboot.mbn with IDA pro and see where in memory the bootloader is checking to verify the phone, maybe we can copy his exploit.
If beaups had some kind of other exploit (to bypass security or other checks), there would be no reason for him to flash a new aboot.mbn, or even if so, he would have to edit some kind of string anyways to get the dev edition bl to work.
does anyone have any thoughts or feedback (or dev edition bootloaders)?
Click to expand...
Click to collapse
When the mmc card is initialized in aboot, it loads /populates ddi_data and ddi_priv data. These contain info about the product generated from the Cid. It checks a value in qfprom and if a certain value makes it so sw_id or sw_revision isn't checked and/or is ignored. This also happens to correspond with a value of cc_type and determines if the device is a developer edition or not. I'm guessing @beaups has an exploit that writes over the mmc card Cid so the value returns from qfprom in such a way as to register as a developer edition device and this also allows the flashing of a dev edition boot chain. I'm guessing he had to flash the dev edition boot chain because the Cid hack probably wasn't going to remain permanently to whatver he wrote to it.
Maybe he'll chime in and tell me if I'm thinking on the right path/track. I'm not sure, I didn't study the function for very long, it was just something I noticed when I was going through the note 4 aboot.

Surge1223 said:
When the mmc card is initialized in aboot, it loads /populates ddi_data and ddi_priv data. These contain info about the product generated from the Cid. It checks a value in qfprom and if a certain value makes it so sw_id or sw_revision isn't checked and/or is ignored. This also happens to correspond with a value of cc_type and determines if the device is a developer edition or not. I'm guessing @beaups has an exploit that writes over the mmc card Cid so the value returns from qfprom in such a way as to register as a developer edition device and this also allows the flashing of a dev edition boot chain. I'm guessing he had to flash the dev edition boot chain because the Cid hack probably wasn't going to remain permanently to whatver he wrote to it.
Maybe he'll chime in and tell me if I'm thinking on the right path/track. I'm not sure, I didn't study the function for very long, it was just something I noticed when I was going through the note 4 aboot.
Click to expand...
Click to collapse
I'll reply for a change. I didn't do any research on aboot or the lock mechanism, @ryanbg did. There may be other "features", but his research indicated the eMMC cid was hashed, signed, and stored in the dev edition aboot for the device it was targeted for. So in order to flash (and more importantly boot) someone's "borrowed" dev-edition aboot, you need a cid that matches the signed hash. So, yes, I just changed the CID to match that. Then the flash is easy.
--beaups

beaups said:
I'll reply for a change. I didn't do any research on aboot or the lock mechanism, @ryanbg did. There may be other "features", but his research indicated the eMMC cid was hashed, signed, and stored in the dev edition aboot for the device it was targeted for. So in order to flash (and more importantly boot) someone's "borrowed" dev-edition aboot, you need a cid that matches the signed hash. So, yes, I just changed the CID to match that. Then the flash is easy.
--beaups
Click to expand...
Click to collapse
So... This would in theory be possible then? If so, I have more digging to do. THANKYOU for the response. I'm getting a grip on this

Holy **** I was right kind of. We need a dev edition aboot with its corresponding Cid NOW

Hariiiii said:
Holy **** I was right kind of. We need a dev edition aboot with its corresponding Cid NOW
Click to expand...
Click to collapse
You also need a way to change the CID.
Sent from my XT1254 using Tapatalk

beaups said:
You also need a way to change the CID.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
And therein lies the rub

Surge1223 said:
And therein lies the rub
Click to expand...
Click to collapse
Indeed I plan to release details soon, I've been working on and off with documenting it. It won't be a "double click here to unlock", but the details will be sufficient for someone with coding/technical knowledge to turn it into a functioning tool (you seem to fit that description).
--beaups

Hariiiii said:
Holy **** I was right kind of. We need a dev edition aboot with its corresponding Cid NOW
Click to expand...
Click to collapse
GeTex said:
So... This would in theory be possible then? If so, I have more digging to do. THANKYOU for the response. I'm getting a grip on this
Click to expand...
Click to collapse
I would suggest researching how/what the the CID does to effect these values though, fwiw, getting a dev edition aboot would be the least of your problems imho.

@beaups
Yes....i quickly began to realize that this was the issue. I actually have no idea where the CID is on the galaxy s5, but based on reading some of ryanbg's posts, I'm going to guess it's in the rpmb partition at mmcblk0rpmb. This post in particular seems to be the important one:
http://forum.xda-developers.com/showpost.php?p=52454292&postcount=18
I suppose the plan would be then to mount the partition as read/write, then scan through it with a hex editor, find the location of the CID in memory, and then maybe write over it using dd like in the link below? Or maybe I'm just crazy.
http://unix.stackexchange.com/questions/214820/patching-a-binary-with-dd

Hariiiii said:
@beaups
Yes....i quickly began to realize that this was the issue. I actually have no idea where the CID is on the galaxy s5, but based on reading some of ryanbg's posts, I'm going to guess it's in the rpmb partition at mmcblk0rpmb. This post in particular seems to be the important one:
http://forum.xda-developers.com/showpost.php?p=52454292&postcount=18
I suppose the plan would be then to mount the partition as read/write, then scan through it with a hex editor, find the location of the CID in memory, and then maybe write over it using dd like in the link below? Or maybe I'm just crazy.
http://unix.stackexchange.com/questions/214820/patching-a-binary-with-dd
Click to expand...
Click to collapse
No, CID is in the eMMC hardware.

beaups said:
You also need a way to change the CID.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
beaups said:
No, CID is in the eMMC hardware.
Click to expand...
Click to collapse
Ok, so I found a file called CID in /sys/block/mmcblk0/device/
it has a number in it.....
it can't be that easy, can it? this is the number:
11010048313647453208872a30e41200

[Tool][Unbrick][Reset][Fix for bad Signal] Stock Firmware

Unbrick tool by One-Team - EypCnn
First: This tool seems to be from EypCnn, One-Team. All credits to them!
EDIT2: I no longer own this device, so i will leave this thread here for people to use. But don't expect any direct support from me .
What can this tool do?:
Restore phone to Stock(International) Firmware (S048) Marshmallow (Locked & Unlocked bootloader)
Fix Lost or bad Signal / IMEI any software Problem
For who does this work?
Pretty much any Lenovo P2 Variant (Chinese and International)
Phones which can access bootloader(you have to boot into it)
Works on Locked & Unlocked Bootloader
Installation aka. Flashing-Steps
Put your phone into bootloader (which is also fastboot) mode.
Download the folder and unzip it.
Connect your phone to your pc.
Go into the unzipped folder and open "flashall - stock reco.bat"
Wait, for the process to end, your phone will reboot on its own.! A stock lenovo bootlogo will show up !
You can disconnect your phone cable from pc and plug into a wall charger, just to be safe. Once the lockscreen is showing up, you're done.
If you want to flash Custom Roms:
look below:
WHEN MOVING TO CUSTOM ROMS NOW:
1. Boot to twrp. (Make sure it is pietwrp from telegram or the official 3.2.3 or later version)
2. Select WIPE menu option
3. Select data partition
4. Change file format to f2fs or anyother.
5. Go back to Start Menu of TWRP, choose Reboot Menu Option
6.Reboot to Recovery
7. Repeat Steps 2 and 3
8. This time select EXT4 when changing file format
9. Do Step 5 and 6
10. Wipe System,Cache and Dalvik-Cache partitions
( for older twrp versions: 10.1 If you're on official twrp 3.2.3 or lower, you have to flash pietwrp or latest twrp now !)
11. Flash your Custom Rom, Gapps (optional) and latest Magisk(optional)
12. Wipe Cache and Dalvik-Cache
13. Reboot. First Boot might take a few minutes but never longer than 7minutes.
If it takes longer, you're encounter a so called bootloop.
Comment hear if that happens, containing information on your twrp-version, rom, gapps, magisk and mods(if present) you're using.
When you corrupt your internal Storage or geht TWRP Error 1001, Error 7:
1. Repeat steps 2-6
2. Repeat steps 7-8
Download(Official Link)
2nd Link(reuploaded because some couldn't download it from androidfilehost): https://drive.google.com/open?id=1wUOZiTwW8mo0IheAGONyj9-QnjimnY2M
I will help if questions arise.
Credits to One-Team & EypCnn.

Thanks a lot. You literally saved my life!

Works like Magic
Thanks a lot for saving my ass . simplest way to downgrade to mm too. Thanks again

Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?

eried1 said:
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
Click to expand...
Click to collapse
My p2 was bricked and , stuck in boot loop. I followed the above instructions, 10 mins into it , it booted with mm version, the same version when i bought and booted for 1st time. It was like a new phone to me.
So i assume if one has upgraded to noughat and want to downgrade but is worried he might brick his device, one can take a back up and try this tool. It works flawless.
No harm in trying this one if ur p2 can boot up mate. Give it a shot. Good luck
Cheers

This tool has saved my device from multiple over a span of two years soft bricks. Can confirm it to do wonders.

eried1 said:
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
Click to expand...
Click to collapse
THis will solve your problem , Cheers.

I tried but cannot download it - do you where to find it?

can i flash this without pc?? if yes please tell how

@sm00th4f3 bro, i wanna know, does this tool flashes full ROM including modem files etc, even on unlocked bootloader?
What is the state of bootloader after using this tool?

amansehdav said:
@sm00th4f3 bro, i wanna know, does this tool flashes full ROM including modem files etc, even on unlocked bootloader?
What is the state of bootloader after using this tool?
Click to expand...
Click to collapse
It flashed everything you have when you buy a new phone. And no, it doesn't lock your bootloader.
So you can either :
- keep using MM Stock Rom S048
- Update via ota in System like you normally would do.
- Update till latest Firmware, then flash twrp- and then Custom Rom of your Choice.
Bootloader is in the same state it was before you used this tool.

sm00th4f3 said:
It flashed everything you have when you buy a new phone. And no, it doesn't lock your bootloader.
So you can either :
- keep using MM Stock Rom S048
- Update via ota in System like you normally would do.
- Update till latest Firmware, then flash twrp- and then Custom Rom of your Choice.
Bootloader is in the same state it was before you used this tool.
Click to expand...
Click to collapse
So how does it fixes corrupted modems? it cannot be flashed on unlocked P2 right?

amansehdav said:
So how does it fixes corrupted modems? it cannot be flashed on unlocked P2 right?
Click to expand...
Click to collapse
I literally just answered it above somewhere.
(Literally in thread description)
You can flash it on unlocked bootloader or locked as well.

So many thanks for bringing up tis tool for us!
This thread should be stick as the "New user" thread is, they definitely belong together.

Download source
Thanks guys, if this works I can now revive my phone. But can someone please upload the tool to another place like google drive. From android filehost it will take an eternity to download!

HkQc said:
So many thanks for bringing up tis tool for us!
This thread should be stick as the "New user" thread is, they definitely belong together.
Click to expand...
Click to collapse
I didn't bring it up, i just linked it . All Credits belong to ONE TEAM and EypCnn.
ryd3r89 said:
Thanks guys, if this works I can now revive my phone. But can someone please upload the tool to another place like google drive. From android filehost it will take an eternity to download!
Click to expand...
Click to collapse
Link updated, Cheers

Lavesh05 said:
can i flash this without pc?? if yes please tell how
Click to expand...
Click to collapse
Nah you need a Computer for this.

no signal after using "flashall - stock reco.bat", it finished successfully, but after rom setup still no signal

GPSSlovakia said:
no signal after using "flashall - stock reco.bat", it finished successfully, but after rom setup still no signal
Click to expand...
Click to collapse
If you used some other tool for imei. You are pretty much done for.

Using this tool i can go to MM version and can upgrade to S251. However after installing twrp and flashing custom rom, it goes to bootloader

[TOOL][DAISY] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Xiaomi Mi A2 Lite's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.

Yay ^_^ Thanks for the efforts Respected devs. Hope it makes life way easier for people here at the community ^_^

unlock bootloader and root still delete all of my files right?

machine1104 said:
unlock bootloader and root still delete all of my files right?
Click to expand...
Click to collapse
Yes

Xiaomi Mi A2 Lite got messed up
Hi there!
I have just received my new Xiaomi Mi A2 Lite phone and wanted to pass all of my data from my old phone to it in a way that it was required to be rooted.
KingRoot didn't work on this new phone, so I unlocked bootloader and tried to install TWRP recovery on my phone.
Installing to the recovery partition did not work. I searched the error it gave me and found a thread saying that flashing it to the boot partition worked for them. So I did. Next thing that happened is that my phone did not boot into the OS (operating system) ever again. It only booted TWRP.
I have since been able to remove TWRP (though I made a back up of it) but the phone still stays on just the loading part before going to the OS.
I have since been able to get back the fastboot and stock recovery, but the phone will not start into the OS anymore.
How can I fix this?
I have been searching for ways to restore my android to the 8.1 Oreo version that it was.
Can I do it with this Tool All In One? Please help! Thank you in advance!! Much appreciated!!

hello
i have unlocked bootloader and wait for TWRP and want to root my phone.
Can I flash TWRP and root with this tool easy? And will I lost all data if do that?

chillout23 said:
hello
i have unlocked bootloader and wait for TWRP and want to root my phone.
Can I flash TWRP and root with this tool easy? And will I lost all data if do that?
Click to expand...
Click to collapse
If you need to flash twrp and root.no, you will not lose data

Ok. Thank you very much for answer
Then will try

chillout23 said:
Ok. Thank you very much for answer
Then will try
Click to expand...
Click to collapse
I would suggest using the root method mentioned here
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Twrp does not have good results for most people.

With this method I will lost all data on my phone and I do not want to setup phone 1 more time. Twice was just enough
I know that already but thank you anyway

chillout23 said:
With this method I will lost all data on my phone and I do not want to setup phone 1 more time. Twice was just enough
I know that already but thank you anyway
Click to expand...
Click to collapse
If your bootloader is unlocked, you should not lose any data just installing magisk

Yes...my fault. My BL is unlocked already.
But I posted in that thread...because of some reason does not work. But this is not thread about it
Thanks for help

So...Installed TWRP but does not recognize anything in internal storage. Not recognize SD card.
When boot again to TWRP goes to "something"...some kind of empty stock recovery with android logo and nothing more.
Oh man...that will be interesting ride...to put TWRP or root device

chillout23 said:
So...Installed TWRP but does not recognize anything in internal storage. Not recognize SD card.
When boot again to TWRP goes to "something"...some kind of empty stock recovery with android logo and nothing more.
Oh man...that will be interesting ride...to put TWRP or root device
Click to expand...
Click to collapse
Because your not supposed to install the twrp image just boot from it and if you do install it then you have to flash the original boot image for which ever 8.1 update your on to get rid of it.
This is explained on the team win page for daisy wish i had read that first after re flashing my os twice and boot image once trying to install this am just using the phone as is for now until i get the urge to try again

uptowner said:
Because your not supposed to install the twrp image just boot from it and if you do install it then you have to flash the original boot image for which ever 8.1 update your on to get rid of it.
This is explained on the team win page for daisy wish i had read that first after re flashing my os twice and boot image once trying to install this am just using the phone as is for now until i get the urge to try again
Click to expand...
Click to collapse
This tool can only boot the recovery or can boot the recovery and automatic flash the installer, i'm not udnerstanding which is the problem

uptowner said:
Because your not supposed to install the twrp image just boot from it
Click to expand...
Click to collapse
Installed TWRP image. I know what is .img

mauronofrio said:
This tool can only boot the recovery or can boot the recovery and automatic flash the installer, i'm not udnerstanding which is the problem
Click to expand...
Click to collapse
oops sorry i should check what thread this is before trying to answer a question i blame alcohol .
Thing is there are posts out on the net that advices people with the a2 lite to install the twrp image to their inactive slot and not to just boot it and that's where things seem to start going wrong.
This has absolutely nothing to do with this tool and sorry i just dived in here and confused people.
maybe some kind passing mod will get rid of the post apologies again

Hi, I bought this device one weeks ago. I wanna flash new android pie OTA update. I dont know how to use this program exactly and I dont wanna lose my data and deal with brick risk.
I understood only one thing from other websites:I must use sideload method .Can someone guide me?Actually I have experience from my old devices(Note 4, Lg optimus, Xperia P) but this is new. I dont wanna broke it immediately .XD.

mesuahas said:
Hi, I bought this device one weeks ago. I wanna flash new android pie OTA update. I dont know how to use this program exactly and I dont wanna lose my data and deal with brick risk.
I understood only one thing from other websites:I must use sideload method .Can someone guide me?Actually I have experience from my old devices(Note 4, Lg optimus, Xperia P) but this is new. I dont wanna broke it immediately .XD.
Click to expand...
Click to collapse
Read the op follow it exactly how it says if u don't know something research it.i have root with no problems if u do as the op says u shouldn't have no problems

Will this work on pie at all?

Nokia 3 fastboot boot loop

In trying to root my Nokia 3, I installed TWRP custom recovery but realised that I forgot to install magisk manager. Upon rebooting the phone out of TWRP recovery mode my Nokia 3 is now stuck in a boot loop such that whenever I turn the device off or reboot it, either from adb or TWRP, the device inevitably only reboots in fastboot mode. Even using the fastboot reboot command doesn't work and only boots it up again only for it to enter fastboot mode immediately.
This means that I can't access the phone as usual meaning I'm unable to download the magisk.zip file I need to install magisk. I tried cloning the git-master and sideloading that from my computer but it said invalid .zip format.
Any idea what I can do?

Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.

andres_vacal said:
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
Click to expand...
Click to collapse
I don't see how I might have done this seeing as I'd guess such a thing would only be possible if I had root on my device. I haven't rooted it yet.
But if I'm mistaken on that, using the TWRP file manager shows an empty /boot/ directory. Is there any way I can restore normal functionality to my device? I just need to be able to get magisk on there so I can install in through TWRP and then root the phone so I can get a custom ROM

Totalitor said:
I don't see how I might have done this seeing as I'd guess such a thing would only be possible if I had root on my device. I haven't rooted it yet.
But if I'm mistaken on that, using the TWRP file manager shows an empty /boot/ directory. Is there any way I can restore normal functionality to my device? I just need to be able to get magisk on there so I can install in through TWRP and then root the phone so I can get a custom ROM
Click to expand...
Click to collapse
But, in TWRP, when you go to reboot section, does it says "No OS Installed"? ( in the upper side )

andres_vacal said:
But, in TWRP, when you go to reboot section, does it says "No OS Installed"? ( in the upper side )
Click to expand...
Click to collapse
It doesn't. I suppose the contents of /boot just isn't visible because I haven't rooted the phone yet?

Totalitor said:
It doesn't. I suppose the contents of /boot just isn't visible because I haven't rooted the phone yet?
Click to expand...
Click to collapse
idts, have you tried to wipe and install constum ROM again?

andres_vacal said:
idts, have you tried to wipe and install constum ROM again?
Click to expand...
Click to collapse
No. I haven't installed a custom ROM. It was the default android 8.0 OS. I haven't been able to root the phone yet because I don't have magisk manager installed.
The only thing I've installed has been TWRP custom recovery. As I understand it, you can't even install custom ROMS unless the phone is already rooted.

Totalitor said:
No. I haven't installed a custom ROM. It was the default android 8.0 OS. I haven't been able to root the phone yet because I don't have magisk manager installed.
The only thing I've installed has been TWRP custom recovery. As I understand it, you can't even install custom ROMS unless the phone is already rooted.
Click to expand...
Click to collapse
No, you only look for the rom of your specific device, and then just flash it trought TWRP

andres_vacal said:
No, you only look for the rom of your specific device, and then just flash it trought TWRP
Click to expand...
Click to collapse
Ok then. I haven't actually been able to find any ROMS for the Nokia 3 other than the stock ROM.
Do you know of any custom ROMS for the device?

andres_vacal said:
No, you only look for the rom of your specific device, and then just flash it trought TWRP
Click to expand...
Click to collapse
I ran adb sideload on the update.zip file downloaded from here.
It seems to have restored my nokia 3 device's recovery to a stock recovery.
Attempting to reboot the device merely reboots it to the stock recovery mode. I cannot seem to get it to reboot into the phone's normal state.
In addition, adb, even while running under root permissions, can no longer detect the device.
I have tried wiping the device, factory resetting it, but the device refuses to reboot into it's normal mode. I can only reboot it into stock recovery or the bootloader.

Totalitor said:
I ran adb sideload on the update.zip file downloaded from here.
It seems to have restored my nokia 3 device's recovery to a stock recovery.
Attempting to reboot the device merely reboots it to the stock recovery mode. I cannot seem to get it to reboot into the phone's normal state.
In addition, adb, even while running under root permissions, can no longer detect the device.
I have tried wiping the device, factory resetting it, but the device refuses to reboot into it's normal mode. I can only reboot it into stock recovery or the bootloader.
Click to expand...
Click to collapse
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.

andres_vacal said:
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
Click to expand...
Click to collapse
My phone randomly decided it'd revert back to TWRP custom recovery today but I still can't access the main operating mode of the phone. Do you know where I can find either a custom ROM for the Nokia 3 or the stock ROM? All instructions I find online seem to be in broken english so I'm having some difficulty following a lot of the guides as they're rather vague

andres_vacal said:
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
Click to expand...
Click to collapse
As mentioned in my previous post, my phone reverted back to TWRP custom recovery for some reason. I tried sideloading the Magisk.zip file and it said it successfully flashed it, but now my Android system has reverted back to the standard Android recovery, booting into it by default.
it says
"alps/NE1_00WW_FIH/NE1
7.1.1/NMF260/00WW_2_15A
/user/release-keys"
at the top.

Totalitor said:
The bootloader was unlocked at some point but I guess it must have locked itself again at some stage when I reset it. Though now that my phone seems to be stuck in bootloader mode and stock recovery mode exclusively, I'm not able to view the serial number in settings as that's something one may only do when the normal mode of the device can be accessed.
I'd use adb to retrieve the serial number of the device but adb doesn't seem to be able to detect my device. I have the necessary drivers on my computer and am running on root privileges but it seems it can't detect it if it's not in the normal operating mode. Any idea how I can get the serial number?
Click to expand...
Click to collapse
I think before flashing magisk we should make sure the OS is ok, can you write the specific phone model?, "Nokia 3" is not an specific number. Then we should be able to find at least a stock ROM.

andres_vacal said:
I think before flashing magisk we should make sure the OS is ok, can you write the specific phone model?, "Nokia 3" is not an specific number. Then we should be able to find at least a stock ROM.
Click to expand...
Click to collapse
It's a Nokia 3 TA-1032
Sorry, I should've specified.

Totalitor said:
It's a Nokia 3 TA-1032
Sorry, I should've specified.
Click to expand...
Click to collapse
Okay man, I did some research and found out that there is not so much info about the specific model but there is some people with the same problem. Found this thread useful so let's try out that.
Nokia 3 official Firmware India/UAE Region [ Links updated with Flash tool]
Hi All, Nokia 3, 5, 6 & 8 Official Firmware flashing tool is Known as OST ( Online Service Tool) Download link Nokia 3 Firmware :- https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg----- latest for Nokia 3 is v 2.15H Nokia 5 Firmware :-...
forum.xda-developers.com

andres_vacal said:
Okay man, I did some research and found out that there is not so much info about the specific model but there is some people with the same problem. Found this thread useful so let's try out that.
Nokia 3 official Firmware India/UAE Region [ Links updated with Flash tool]
Hi All, Nokia 3, 5, 6 & 8 Official Firmware flashing tool is Known as OST ( Online Service Tool) Download link Nokia 3 Firmware :- https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg----- latest for Nokia 3 is v 2.15H Nokia 5 Firmware :-...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, But all of the links on that thread to nokia 3 firmware are dead. In the meantime I used the adb push command to upload the magisk.zip file to my device as well as the Lineage 14.1 custom ROM which I got from here and tried installing both of them using TWRP. TWRP said both were successful but on reboot, my phone is once again stuck in the orange state at the boot screen.

Totalitor said:
Thanks, But all of the links on that thread to nokia 3 firmware are dead. In the meantime I used the adb push command to upload the magisk.zip file to my device as well as the Lineage 14.1 custom ROM which I got from here and tried installing both of them using TWRP. TWRP said both were successful but on reboot, my phone is once again stuck in the orange state at the boot screen.
Click to expand...
Click to collapse
Ow, I didn't check that, my bad. Have you tried to flash only LOS?, generally the problem with LOS is that you need to have installed the stock ROM for it to function well, if you wipe and then flash LOS it will say "successful" but it won't start.
Or at least at my experience

andres_vacal said:
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
Click to expand...
Click to collapse
we've established that I must have somehow accidentally deleted the ROM in installing TWRP.
You mentioned you accidentally deleted the ROM. How did you go about fixing your problem?
I've looked everywhere online for Nokia 3 TA-1032 stock firmware but all I can find are dead google drive links. How did you fix your issue? Or was yours with a different model of phone?

Totalitor said:
we've established that I must have somehow accidentally deleted the ROM in installing TWRP.
You mentioned you accidentally deleted the ROM. How did you go about fixing your problem?
I've looked everywhere online for Nokia 3 TA-1032 stock firmware but all I can find are dead google drive links. How did you fix your issue? Or was yours with a different model of phone?
Click to expand...
Click to collapse
Mine was with an Asus, and the only way I could fix the horrible bootloop was managing to install the stock un-official ROM made from a well known developer. I just did a short research on this case, and all the solutions on internet say you need the ROM like I just told you, so I think there is no way if we cannot find a ROM for the device.

Database Info

welcome