Database Develop

[stock rom][3.0.1] P7100BUKDF + bootloader unlock

Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
ODIN download mode
- Turn your device off and unplug it
- Wait 30 seconds (screen off doesn't mean the device has finished turning off)
- Press-and-hold the power button and very shortly after (0.5 seconds, but not simultaneously) press-and-hold the left volume button
- Release the buttons as soon as you see something on screen. You should be looking at a USB icon and a digging Android.
- Make sure the digging Android is flashing. If the USB icon is flashing, press the left volume button to switch to the Android.
- Press the right volume button to select and enter download mode
Bootloader unlock
Flashing this firmware will also unlock the bootloader.
Included languages
Deutsch
English (UK)
English (US)
Espanol
Italiano
Nederlands
Portugues
Instructions (Windows)
- Download and extract the attached Odin zip file
- Download and extract the ROM (you should end up with three .tar.md5 files)
- Go into bootloader mode, as described above
- Start Odin
- Look at the attached Odin screenshot, make sure of the following:
--- Re-Partition: NOT checked
--- Auto Reboot: checked
--- F. Reset Time: checked
--- Flash Lock: NOT checked
--- Phone EFS clear: NOT checked
--- Phone Bootloader Update: NOT checked
- Press the big BOOTLOADER button on the right and select the "BOOTLOADER_P7100BUKC8.tar.md5" file
- Press the big PDA button on the right and select the "PDA_SIGNED_HRI83_BUKDF.tar.md5" file
- Press the big PHONE button on the right and select the "MODEM_HRI83_BUKDF_REV_03.tar.md5" file
- Connect your device with the USB cable
- Wait a few seconds, Odin should say it is now connected
- Hit the Start button, and wait until the device boots
- Press the Thanks button below this post and/or donate
Random notes
"adb reboot recovery", "adb reboot download" and "adb reboot bootloader" now appear to be working, they weren't on the KD9 ROM my device came with.
Download
Here is the link: http://www.multiupload.com/LWN6RHF8WJ
NOTICE: FLASHING ALSO WIPES YOUR SD-CARD !

Chainfire said:
Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
Click to expand...
Click to collapse
Nice gift!
My bootloader was locked before this update, and I did not attempt to unlock it. Download mode tells me the OEM lock is now unlocked. Please confirm! (I may be a dumbass )
Click to expand...
Click to collapse
Do you see the open padlock on the boot logo screen?

bcmobile said:
Nice gift!
Do you see the open padlock on the boot logo screen?
Click to expand...
Click to collapse
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !

Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.

Chainfire said:
Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.
Click to expand...
Click to collapse
Yay! They do work if you do a adb reboot from the shell, but anyway, that's history now.
If you see the open padlock, you're in business. Im guessing that ROM was not meant for general public... in fact, if it came from where I think it came from, it wasn't
EDIT: So it has the stock recovery menu as well? Can you possibly do a system/boot/recovery dump to save us the pain of Odin?
EDIT2:
Chainfire said:
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !
Click to expand...
Click to collapse
fastboot oem unlock
I love Samsung... now

No Chinese at all, what a pity......
is it android 3.0.1 or android 3.1?

My device (bought in a vodafone ita store) has P7100BUKDF ROM and was already unlocked.

Myeah I was able to flash root after flashing this firmware, so it does unlock, it appears.
EDIT: Someone on twitter confirmed this unlocked the bootloader for him as well.

Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method

gjroeleveld said:
Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method
Click to expand...
Click to collapse
If you press enough buttons the menu appears in recovery

Added the SD-CARD wipe notice for ya

How do root this firmware ?
Thanks

http://forum.xda-developers.com/showthread.php?t=1079781 ?

any one know the difference between this one and stock rom? would be interesting to see if samsung changed anything.

Has anyone tried flashing with Heimdall in Linux?

As for the question about the difference with the original ROM I can tell that as mentioned in the first post more languages are supported.
The rest seems about the same as the previous rom.

Yes, it's also the only change I noticed from the stock room, but in my case is great since now it supports Portuguese (my native language).

I just unlocked my bootloader following your steps. It shows unlocked when booting back up but now it is not recognized by my pc when connecting through usb. I tried rebooting both pc and tablet. I also tried uninstalling the drivers from Samsung and reinstalling it but still no go. I have a Galaxy Tab 10.1v from Google I/O and the usb is gone. I cannot even charge from usb now. Are the files posted the correct ones for this device because it is not working. Does anyone have the correct ones? Any help would be appreciated.

The Google I/O Tab as far as I know is not a 10.1v, thus you shouldn't be using these files on it!

Yeah I figured that out now. I was following the root guide and I thought I was supposed to use this. Everything seems to work but the usb. But I can still connect to Odin and reflash. Is there anyway to get it back?

HTC DUAL SIM M7CDWG (INDIA) in bootloop..

Hi
i need help from all the experienced ppl here...
(THE PROBLEM)
i rooted my HTC dual sim running on 4.2.2 it functioned good untill :
- i ran FOTA 4.4.2 update, update failed..
- i performed a factory reset to avoid problems, and that is when the real problem started..
(CURRENT STATUS) Now..
1. phone shows HTC logo and restarts..
2. USB Debugging not enabled, so cannot use fastboot..
the phone goes into android system recovery (image 2).
(TRIAL) From this recovery i tried flashing
1. FIRMWARE_M7C_DWG_JB​_50_S1_hTC_Asia_India_2.37.720 .1.zip - 23.42 MB
& then
2. OTA_M7C_DWG_JB_50_S1_hTC_Asia_India_2.37.720.1-2.23.720.2_release_337572.zip - 316.63 MB
but failed
then
3. M7DWG_CWM_Nandroid_Backup_CID_HTC__038_2.37.720.1. zip - 998.74 MB - failed
Please help.. Thanks in advance..
Phone details are attached

gary84 said:
Hi
i need help from all the experienced ppl here...
(THE PROBLEM)
i rooted my HTC dual sim running on 4.2.2 it functioned good untill :
- i ran FOTA 4.4.2 update, update failed..
- i performed a factory reset to avoid problems, and that is when the real problem started..
(CURRENT STATUS) Now..
1. phone shows HTC logo and restarts..
2. USB Debugging not enabled, so cannot use fastboot..
the phone goes into android system recovery (image 2).
(TRIAL) From this recovery i tried flashing
1. FIRMWARE_M7C_DWG_JB​_50_S1_hTC_Asia_India_2.37.720 .1.zip - 23.42 MB
& then
2. OTA_M7C_DWG_JB_50_S1_hTC_Asia_India_2.37.720.1-2.23.720.2_release_337572.zip - 316.63 MB
but failed
then
3. M7DWG_CWM_Nandroid_Backup_CID_HTC__038_2.37.720.1. zip - 998.74 MB - failed
Please help.. Thanks in advance..
Phone details are attached
Click to expand...
Click to collapse
USB debugging anyway won't work in recovery mode. It works only in a booting OS. So there's NO REASON why fastboot shouldn't work. Have you given it a try ??

raghav kapur said:
USB debugging anyway won't work in recovery mode. It works only in a booting OS. So there's NO REASON why fastboot shouldn't work. Have you given it a try ??
Click to expand...
Click to collapse
i cannot use sdk tools to flash..
i can boot into fastboot & 'andriod system recovery'(second image posted in the previous post)
it has an option of install from sd, install from phone mem....
but it aborts the installation..so i guess i dont have the correct software to install...

raghav kapur said:
USB debugging anyway won't work in recovery mode. It works only in a booting OS. So there's NO REASON why fastboot shouldn't work. Have you given it a try ??
Click to expand...
Click to collapse
Hi raghav, what u said was absolutely correct...
I probably dis not install the drivers properly.. once I re-installed drivers, i could use sdk

your bootloader is unlocked, first lock the bootloader then retry to install RUU.

Moto g 2 gen's display shut downs after locking the phone or after 'screen time out'

I have Moto g 2nd Gen Indian edition phone
I have been experiencing a strange issue with my phone from past week, when I lock down my phone via power button or closing the cover of magnetic flip-shell or whether it locks it down itself after 'screen time out' automatically the display just shut downs.
The phone is actually working in background as I can see LED notification sometimes. And when I connect my phone to PC via USB it even shows the Internal storage folder. I can even feel vibration on Powering off the device.
When I try to reboot the device, it boots up normally with Motorola logo animation and everything works fine until device gets lock down and this scenario continues as I reboot it again.
Sometime I can feel the bottom speaker grill getting hotter until I 'Power Off' the device forcefully.
So far I have tried fast booting the phone it boots up normally but issue is still there.
I even tried to run the phone in the safe mode but the issue persist even in safe mode.
I even wiped cache partition and also performed 'Factory Reset' via hard reset and soft reset but nothing is working.
I want to clarify that my phone isn't under warranty and also I have not even tempered my phone's software it is completely stock with android version 5.0.2 (recently updated via OTA).
I'm not allowed to post the image as a new user that's why I have written some software specific detail as below.
System version: 22.56.3.titan_retaildsds.retaildsdsall.en.03 retin
Build No: LXB22.99-16.3
Base band version: MSM8626BP_1032.3112.96.00R EMEA_DSDS_CUST
Kernel version: 3.4.42-g0bea67a
[email protected] #1
Wed Aug 26 00:26:33 CDT 2015
I don't think the 'Power Button' can be faulty as it's working as intended properly and almost all the time I use the official Motorola 'Magnetic flip-shells' so I rarely use the power button.
I suspect that this issue may have been caused by some virus or malware as I had visited some torrent hosting and too much ad hosting sites before the issue started.
I contacted Motorola support via chat session and they asked me to get it to the service center, but I have read very bad reviews about service center near my location and I'm afraid to go there.
Although I'm a software developer but in the area of 'Android development' I'm totally noob so joined the XDA to solve the issue with the help of experts.
Can I have some suggestion, solution on this issue? Any help of yours is appreciated.
Also I want to know that if 'Hard reset' can't solve the issue, does that mean the software of device has corrupted?

Try a hard reset first
If not solved use an easy installer

vaisakmct said:
Try a hard reset first
If not solved use an easy installer
Click to expand...
Click to collapse
Well Hello sir thanks for the prompt reply, as I said earlier:
So far I have tried fast booting the phone it boots up normally but issue is still there.
I even tried to run the phone in the safe mode but the issue persist even in safe mode.
I even wiped cache partition and also performed 'Factory Reset' via hard reset and soft reset but nothing is working.
So hard reset is not working for me which I have performed 2-3 times, I guess I have to go through your another suggestion.
Ok, so by 'easy installer' did you mean this method described in below link?
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
I think method in #Post 1 is for my phone.
Does anyone have other solution or advise? Your guidance will be appreciated.

smartandcool3 said:
Well Hello sir thanks for the prompt reply, as I said earlier:
So far I have tried fast booting the phone it boots up normally but issue is still there.
I even tried to run the phone in the safe mode but the issue persist even in safe mode.
I even wiped cache partition and also performed 'Factory Reset' via hard reset and soft reset but nothing is working.
So hard reset is not working for me which I have performed 2-3 times, I guess I have to go through your another suggestion.
Ok, so by 'easy installer' did you mean this method described in below link?
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
I think method in #Post 1 is for my phone.
Does anyone have other solution or advise? Your guidance will be appreciated.
Click to expand...
Click to collapse
ya this one will be best for u

vaisakmct said:
ya this one will be best for u
Click to expand...
Click to collapse
Thank you,
The Easy installer method requires 'USB debugging enabled and RSA key Allowed', so I have enabled 'USB debugging' but I never get the 'RSA key allowed' dialogue.
I tried to attach cable to the different USB ports but I never get the 'RSA Key allowed' dialogue, How can I overcome this issue?

Thats not a pblm get in just fastboot mode click installer and select option for locked boot loader

vaisakmct said:
Thats not a pblm get in just fastboot mode click installer and select option for locked boot loader
Click to expand...
Click to collapse
but as suggested by @reefuge in post #13 and #post16 in link below
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612/page2
that 'Phone must have USB debugging enabled and RSA key Allowed, Usb cable plugged in and in normal use mode'
1. I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated please click to disable"
2. if I go into the Device Manager I can see Android Device
3. I changed my USB-Setting to PTP
but nothing works.

smartandcool3 said:
Thank you,
The Easy installer method requires 'USB debugging enabled and RSA key Allowed', so I have enabled 'USB debugging' but I never get the 'RSA key allowed' dialogue.
I tried to attach cable to the different USB ports but I never get the 'RSA Key allowed' dialogue, How can I overcome this issue?
Click to expand...
Click to collapse
no it does NOT require USB debugging anymore (that was version 1) You must be able to put phone manually into AP FASTBOOT mode by correct key combo
read instruction in zip file and attached here

reefuge said:
no it does NOT require USB debugging anymore (that was version 1) You must be able to put phone manually into AP FASTBOOT mode by correct key combo
read instruction in zip file and attached here
Click to expand...
Click to collapse
Thank you @reefuge sir for the reply.
Does that mean I don't need Phone with 'USB debugging with RSA key allowed'?
All I have to do is to run the 'Magical batch file' of yours and watch the magic show in PC?
Ok one more question, I don't want to irritate you but I'm helpless and confused,
I wanted to ask you that after following this step in sequence:
1] ALL needed files are in the zip file you downloaded TO PC (not phone) including stock ROM files
2] Install Motorola device manager 2.5.4.exe for correct Usb drivers (choose repair if already installed) and install minimal ADB /fastboot v 1.31.exe
3] plug in Usb cable and PUT phone into AP Fastboot Flash mode
4] by holding power and volume down ( - ) until phone powers off to blank screen (may vibrate)
5] still holding both buttons count 1,2,3,4,5 and release both same time
6] Hopefully you should be in AP Fastboot Flash mode with USb cable plugged in?
7] if No go back to step [3] if YES continue
8] do not select anything on phone or press any more phone buttons - All done via pc no
9] Now run the EASY INSTALLER.bat file and watch both pc screen and phone screen
I assume that your program will show me following different menu options:
1)Flash stock ROM --- will flash stock rom / Logo / boot & recovery.img / modem files and bootloader -- this DOES NOT wipe phone so can upgrade / dirty flash keeping settings
2)Lock bootloader --- as above but locks boot loader --- tbh always better to use option 1)
3)Flash Fixed Logo -- Fixes the unlocked Boot Loader Warning EVEN if unlocked still
4)Reboot Phone -- Reboots phone --
5)Factory Reset --- wipes DATA and CACHE --- IF phone hangs at BOOT LOGO, do this Action. ALWAYS use if DOWNGRADING or Coming from A CUSTOM ROM
6)Exit --- Closes command prompt window and exits
from above 6 menu options, which options do I have to follow(related to my phone's condition) in sequence to revive my phone?
I have moto g which is unrooted, stock and with locked bootloader.
You valuable reply is appreciated

smartandcool3 said:
Thank you @reefuge sir for the reply.
Does that mean I don't need Phone with 'USB debugging with RSA key allowed'?
All I have to do is to run the 'Magical batch file' of yours and watch the magic show in PC?
Ok one more question, I don't want to irritate you but I'm helpless and confused,
I wanted to ask you that after following this step in sequence:
1] ALL needed files are in the zip file you downloaded TO PC (not phone) including stock ROM files
2] Install Motorola device manager 2.5.4.exe for correct Usb drivers (choose repair if already installed) and install minimal ADB /fastboot v 1.31.exe
3] plug in Usb cable and PUT phone into AP Fastboot Flash mode
4] by holding power and volume down ( - ) until phone powers off to blank screen (may vibrate)
5] still holding both buttons count 1,2,3,4,5 and release both same time
6] Hopefully you should be in AP Fastboot Flash mode with USb cable plugged in?
7] if No go back to step [3] if YES continue
8] do not select anything on phone or press any more phone buttons - All done via pc no
9] Now run the EASY INSTALLER.bat file and watch both pc screen and phone screen
I assume that your program will show me following different menu options:
1)Flash stock ROM --- will flash stock rom / Logo / boot & recovery.img / modem files and bootloader -- this DOES NOT wipe phone so can upgrade / dirty flash keeping settings
2)Lock bootloader --- as above but locks boot loader --- tbh always better to use option 1)
3)Flash Fixed Logo -- Fixes the unlocked Boot Loader Warning EVEN if unlocked still
4)Reboot Phone -- Reboots phone --
5)Factory Reset --- wipes DATA and CACHE --- IF phone hangs at BOOT LOGO, do this Action. ALWAYS use if DOWNGRADING or Coming from A CUSTOM ROM
6)Exit --- Closes command prompt window and exits
from above 6 menu options, which options do I have to follow(related to my phone's condition) in sequence to revive my phone?
I have moto g which is unrooted, stock and with locked bootloader.
You valuable reply is appreciated
Click to expand...
Click to collapse
FORGET USB debugging and developer options, NOT required - thats NO - IGNORE , not needed
simply install mdm 2.54.exe and ADB v1.31
get phone into Fastboot mode with usb cable plugged in
run easyinstaller.bat
from menu
fmenu options choose [1] and reboot phone [4] to upgrade keeping settings
or [1], [5] and [4] to FULLY wipe and reset phone as new

reefuge said:
FORGET USB debugging and developer options, NOT required - thats NO - IGNORE , not needed
simply install mdm 2.54.exe and ADB v1.31
get phone into Fastboot mode with usb cable plugged in
run eastinstaller.bat
from menu
fmenu options choose [1] and reboot phone [4] to upgrade keeping settings
or [1], [5] and [4] to FULLY wipe and reset phone as new
Click to expand...
Click to collapse
Thank you @reefuge sir for the prompt reply and for your guidance, which actually makes the task easier for me many thanks to you sir.
I will try step '[1], [5] and [4] to FULLY wipe and reset phone as new' as mentioned, and pray to god that my days of misery gets over, to revive my phone.
Do I have to place the 'extracted folder' in my PC's root folder(which is C: drive) or I can place that 'extracted folder' anywhere on PC and execute the 'eastinstaller.bat' from there?

smartandcool3 said:
Thank you @reefuge sir for the prompt reply and for your guidance, which actually makes the task easier for me many thanks to you sir.
I will try step '[1], [5] and [4] to FULLY wipe and reset phone as new' as mentioned, and pray to god that my days of misery gets over, to revive my phone.
Do I have to place the 'extracted folder' in my PC's root folder(which is C: drive) or I can place that 'extracted folder' anywhere on PC and execute the 'eastinstaller.bat' from there?
Click to expand...
Click to collapse
anywhere as it includes (in extracted folder) ALL the files required to make it work

reefuge said:
anywhere as it includes (in extracted folder) ALL the files required to make it work
Click to expand...
Click to collapse
Thank you @reefuge sir for the reply, and I will try this 'Easy Method' and I will keep you posted on its progress.
Once again thank you very much @reefuge sir and @vaisakmct sir as your replies helped me a lot, I hope this issue get resolved soon.

smartandcool3 said:
Thank you @reefuge sir for the reply, and I will try this 'Easy Method' and I will keep you posted on its progress.
Once again thank you very much @reefuge sir and @vaisakmct sir as your replies helped me a lot, I hope this issue get resolved soon.
Click to expand...
Click to collapse
Ok, Guys I was able to run the 'EasyInstaller' and it worked perfectly and magically as it should supposed to be.
Unfortunately I was not able to resolve my problem so It might be something else.
@reefuge sir your 'EasyInstaller' was awesome, and I will highly recommend it to everyone for 1-step solution in need, please keep making these kind of awesome tools.
Thank you @reefuge sir and @vaisakmct once again for all your help. If you have anymore suggestion or solution regarding my problem please let me know.

[GUIDE][SM-T510/T515]Unlock/TWRP/Odin HowTo/Root - Tab A 10.1 (2019)

The purpose of this thread is to have one post with links to all of the following guides:
Unlock Bootloader by @mingkee
TWRP Recovery by @Magendanz
Custom ROM Nexus Stock by @Magendanz - current release is SM-T510 only
Custom ROM LineageOS 16.0 by @Magendanz - SM-T510 only
All credit to @Magendanz and @mingkee for those.
Below are my own observations which supplement but do not replace the guides above. The original posts includes important information not quoted below. You need to read the relevant guides above (depending on what you want to do), and you may get some additional benefit from reading my thoughts below before following the guides above.
***​Contents​
Overview
Downloads
Buttons
Unlock Bootloader
Rooting
How to use Odin
***​Overview​To root your device you need to first install the TWRP recovery. @Magendanz includes TWRP in his ROMs, so you have two options, TWRP without custom ROM, or TWRP with custom ROM.
To be able to install a ROM or recovery you first need to unlock your bootloader.
WARNING - take note of the kernel version of the custom ROM or TWRP you intend to use, e.g. T510XXU2ASI4. Newer bootloader releases will sometimes prevent downgrading, so if you flash a firmware/ROM/TWRP with a later kernel version you may not be able to flash your desired custom ROM without problems, or flashing an older version than you are currently running may trigger anti-rollback mechanisms. Magendanz suggests matching the version exactly.
There are then two paths:
Original ROM:
Read the TWRP instructions
Download any zip you plan to flash (install) from TWRP (e.g. Multi-disable and Magisk) and save to your sdcard. Internal memory will be wiped (formatted) as a necessary step in installing TWRP (if you follow the instructions correctly). Note that the folder /sdcard is part of the devices internal memory, your actual sdcard data can be found in something like /storage/ABCD-1234 in Android, or external_sd in TWRP.
Unlock Bootloader - Click to see original post:
Disclaimer: your tablet warranty will void. Proceed with your own risk
Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
Prerequisite:
Host PC installed Samsung Smart Switch
USB C cable
Your tablet battery should be 70% or higher and you have done data backup
OEM Unlock enabled
1. About tablet
2. Software version
3. Hit Build Number few times
4. Enable USB Debugging
5. Allow your host computer
6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
https://www.xda-developers.com/fix-m...galaxy-note-8/
Are you ready? Let's do it.
1. Turn your tablet off and disconnect USB cable
2. Press and hold both volume up and down buttons and connect to host computer
3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
4. If you see a warning screen on boot, the bootloader is unlocked.
Install TWRP recovery .tar.md5 file via Odin by following the TWRP instructions.
Click to see instructions from the TWRP OP -
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, select your update (.zip) file, and then swipe to install
Reboot to system
[Optional] Install Magisk to get root - see Rooting section below
Don't forget to install Multi-disabler before doing Format Data! (as described in the guide) - In TWRP tap Install then select the Multi-disabler zip file.
Custom ROM [Allow several hours for the custom ROM download]:
Read the custom ROM instructions: Nexus Stock / LineageOS 16.0
Download any zip you plan to flash (install) from TWRP (e.g. Magisk) and save to your sdcard. Internal memory will be wiped as a necessary step in installing TWRP (if you follow the instructions correctly). Note that the folder /sdcard is part of the devices internal memory, your actual sdcard data can be found in something like /storage/ABCD-1234 in Android, or external_sd in TWRP.
Unlock Bootloader - Click to see original post:
Disclaimer: your tablet warranty will void. Proceed with your own risk
Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
Prerequisite:
Host PC installed Samsung Smart Switch
USB C cable
Your tablet battery should be 70% or higher and you have done data backup
OEM Unlock enabled
1. About tablet
2. Software version
3. Hit Build Number few times
4. Enable USB Debugging
5. Allow your host computer
6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
https://www.xda-developers.com/fix-m...galaxy-note-8/
Are you ready? Let's do it.
1. Turn your tablet off and disconnect USB cable
2. Press and hold both volume up and down buttons and connect to host computer
3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
4. If you see a warning screen on boot, the bootloader is unlocked.
Install custom ROM .tar.md5 file (which includes TWRP) via Odin, by following the custom ROM instructions.
Click for instructions from OP for Nexus Stock -
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
When TWRP launches, wipe data if installing for first time. (Not necessary for incremental upgrades.)
Reboot to system
Click for instructions from OP for LineageOS 16.0 -
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM to AP with Odin
When TWRP launches, wipe data if installing for first time. (Not necessary for incremental upgrades.)
Reboot to system
Note that "wipe data" means Wipe -> Format Data
[Optional] Install Magisk to get root - see Rooting section below
Dirty flash: If you had installed the custom ROM previously and are now updating to a newer version then all you need to do is use Odin to flash the latest tar.md5 file. It will enter TWRP after the flash, no need to Format Data, just reboot to system. Alternatively if the ROM developer provides a flashable zip, you can update with TWRP.
Some users have reported getting stuck on the boot animation after a dirty flash, I don't know if that still happens with the latest versions of @Magendanz's ROMs. If it does the solution is to boot into recovery and flash Multi-disabler.
For TWRP versions before v3.3.1-5 you MUST format the encrypted data partition after flashing TWRP or TWRP will hang on the splash screen. For later versions of TWRP you should format the encrypted data partition after flashing TWRP so that TWRP can access the data partition.
You can use TWRP to flash zip files, e.g. to install newer versions of TWRP itself, or custom ROM zips, as follows:
1. Download the zip file
2. Boot into Recovery
3. Install -> Select the TWRP zip file
4. Reboot to System
You *cannot* use TWRP to flash tar.md5 files, and you must use Odin at least once to get TWRP installed in the first place.
***​Downloads​You may not need ALL of these downloads, this is just a handy list of some of the downloads mentioned in the guides
Samsung Smart Switch (for USB drivers)
Magisk - Download Latest Stable zip file to flash in TWRP (see Rooting below) and Latest Magisk Manager to install as an app
Odin
Multi-disabler (required by TWRP only tar.md5)
Firmwares SM-T510 SM-T515 - allow several hours, at least, for the firmware downloads to complete
WARNING - take note of the kernel version of the custom ROM you intend to use, e.g. T510XXU2ASI4 and your current version (Settings | About tablet). Newer bootloader releases will sometimes prevent downgrading, so if you flash a firmware with a later kernel version you may not be able to flash your desired custom ROM without problems, or flashing an older version than you are currently running may trigger anti-rollback mechanisms. Magendanz suggests matching the version exactly.
***​Buttons​
Power On: Hold the Power button for 3 seconds
Boot to Recovery (Before unlocking bootloader) Power On and Press and hold Power and Volume Up until you see Recovery running.
Boot to Recovery (After unlocking bootloader) Power On and then press Power and Volume Up as soon as you see the unlocked bootloader warning. No need to hold.
Boot to Download: Press and hold Volume Up and Volume Down and connect to computer with USB cable.
***​Unlock Bootloader​Read the Unlock Bootloader Guide FIRST​Click to see Unlock Bootloader original post...
Disclaimer: your tablet warranty will void. Proceed with your own risk
Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
Prerequisite:
Host PC installed Samsung Smart Switch
USB C cable
Your tablet battery should be 70% or higher and you have done data backup
OEM Unlock enabled
1. About tablet
2. Software version
3. Hit Build Number few times
4. Enable USB Debugging
5. Allow your host computer
6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
https://www.xda-developers.com/fix-m...galaxy-note-8/
Are you ready? Let's do it.
1. Turn your tablet off and disconnect USB cable
2. Press and hold both volume up and down buttons and connect to host computer
3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
4. If you see a warning screen on boot, the bootloader is unlocked.
After unlocking the bootloader every time you turn the device on a warning about the bootloader being unlocked will appear for ten seconds, unless you dismiss it by pressing the power button.
If you are holding the Power button and Volume Up to boot into recovery this warning screen will flash on and off briefly, at which point you can stop holding down the buttons. Recovery will start a few seconds later.
***​Rooting​Root can be achieved by flashing Magisk in TWRP (you also need to install the Magisk Manager app). From Magisk 19.3 onwards there is no longer a need to use Magisk Manager to patch a tar.md5 file or anything like that.
You can even install Magisk the first time TWRP runs after flashing one of @Magendanz's tar.md5 files in Odin.
To do so follow @Magendanz's guide up to the point where you have Factory Reset/Wiped Data in TWRP then:
1. Reboot to Recovery
2. Install -> Select the Magisk zip file
3. Reboot to System
4. Install Magisk Manager
Otherwise you can start by installing the Magisk Manager app at any time.
Note: You will need to re-install Magisk after a TWRP update.
***​How to use Odin​Odin is a Windows tool for firmware flashing on Samsung devices via USB. Odin can be used to flash firmware, kernels, recoveries or ROMs to your device.
* Firmware zip (or rar) files need to be extracted and then install via Odin. Flashable zip files (e.g. new versions of TWRP or custom ROMs) can only be flashed from TWRP, not Odin, though you need to flash a TWRP tar.md5 file using Odin in the first place *
Preparing the device
Charge the device to at least 80%.
Bootloader unlocked
In developer options, turn USB debugging on. Click on Build number in Settings several times until you see the toast notification "You are now a developer". Go to Developer Options and turn on the USB debugging option.
- In the stock ROM Build number can be found here: Settings | About Tablet | Software Information and the "Developer Options" menu item appears below About Tablet in the main Settings screen.
- The locations may be different in custom ROMs. In the Nexus based ROM the locations are Settings | About phone for Build number, and System | Advanced for Developer options
Turn off the phone, hold down the Volumn Up and Volume Down buttons and connect the device to the computer with a USB cable (preferably the cable that came with the device). A warning will appear saying "A custom OS can cause critical problems in phone and installed applications".
Press the Volume Up button briefly to continue.
The device is now in Download mode.
Install Odin version 3.13.3.
When you run it a dialog will pop up in English and Chinese. Click OK.
The Odin window looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Above ID:COM on the left is the progress bar, below ID:COM is the connection indicator which changes colour (and shows the COM id) when your device is connected in Download mode.
Below that is the "Log" tab which gives verbose output showing what's happening. Normally you will not need to go near the Option or Pit tabs.
There are four buttons in the middle of the screen corresponding to the types of file that you can flash: BL (boot loader), AP (Application Processor, PDA), CP (Core Processor, phone/modem), CSC (Consumer Software Customization)
Depending on what you are flashing you will need to load one or more files. To load each file type click on the corresponding button and select the file to be flashed.
Odin will show the following in the "Log" while the file is being processed:
Code:
<OSM> Enter CS for MD5
<OSM> Check MD5... Do not unplug the cable...
<OSM> Please wait...
For AP_ files this can take some time, during which the button will remain greyed out. When the file has loaded the "Log" will say:
Code:
<OSM> Checking MD5 finished Successfully...
<OSM> Leaving CS...
... the button will be enabled again, the text field beside the button will be filled with the fullpath of the selected file, and the checkbox next to the button ticked.
@Magendanz's TWRP and ROM files are both single files flashed to AP, so just click the AP button and the select the tar.md5 file.
If you are flashing firmware ( e.g. https://samfrew.com/model/SM-T510/ ) unzip the download into separate files and load each with the correspong button. The filenames begin with BL_..., AL_... etc so you'll know which is which.
There will be both a CSC_ and HOME_CSC_ file. You could flash HOME_CSC_ to keep your device's settings and data but normally you should use CSC_ for a clean install. If you have an SM-T515 then you'll have a CP_ file too, but if you have a SM-T510 then your firmware will not have a CP_ file because that's for the phone (SM-T510 is wifi only), so just leave CP alone, only load BL, AP and CSC.
Verify that your device is connected in download mode. The box below ID:COM should show the COM id of the connected device and there should be a line in the "log" saying something like <ID:0/008> Added!!
Click Start to flash the selected files. DO NOT UNPLUG THE CABLE UNTIL THE PROCESS IS COMPLETE. You can follow the progress in Odin and on the Download screen on your device. To flash a ROM or firmware will take several minutes.
If you are flashing one of @Magendanz's tar.md5 files then your device will reboot into TWRP once the install is complete. At that point continue following @Magendanz's guide.
Note: You will need to turn on USB debugging again after flashing firmware, or a clean install of a ROM, before you can use Odin to flash again. Also check that OEM unlock is still turned on.

Hi,
Please help, my tablet SM-T515 got stuck at: teamwin Recovery Project 3.3.1-1 ...blue with black/gray screen, at boot. I can't do anything, it keeps on looping to this screen. If I try to do a Power+VolumeDown it resets the tablet but I can't do anything else, nor entering in Download mode or shut it down. I have no idea how to fix it. Can anyone give me some hints, please ?! PS: I wanted to root it...I might have downloaded on the tablet with ODIN some weird TWRP (I didn't found this post before starting the process from some weird site ... ).
Please, help me,
D

@DdDnt The difficulty in rebooting into Download mode is timing. After triggering a reboot by holding Power+VolumeDown for 7 seconds you need to immediately switch to holding Vol Up + Vol Down then connect the cable.
Alternatively you can wait for the battery to run out, then you can press and hold volume buttons and connect. Should get you into Download mode.
The next steps are
Flash stock firmware via Odin
Reboot into system and turn on USB debugging again in Developer options, verify that OEM unlock is still set
Flash TWRP or Custom ROM via Odin

MossyTC said:
@DdDnt The difficulty in rebooting into Download mode is timing. After triggering a reboot by holding Power+VolumeDown for 7 seconds you need to immediately switch to holding Vol Up + Vol Down then connect the cable.
Alternatively you can wait for the battery to run out, then you can press and hold volume buttons and connect. Should get you into Download mode.
The next steps are
Flash stock firmware via Odin
Reboot into system and turn on USB debugging again in Developer options, verify that OEM unlock is still set
Flash TWRP or Custom ROM via Odin
Click to expand...
Click to collapse
Hey, first of all thanks for the nice guide. I followed it to flash Nexus ROM for my T515 but I messed up the tablet and ended up in the emergency recovery mode. No biggie though, I have flashed back to original stock ROM but I can't seem to find OEM unlock option now in my developer settings (the tablet is still unlocked though, I have to use my power key while turning on to skip the warning screen)
So basically, now I can't figure out why I can't flash the nexus rom but was able to flash official firmware and why I don't have OEM unlock option in my developer settings.
Also, I made a clean install of Windows 10, downloaded the good drivers and used my best type C cord and plugged it directly into the motherboard and not into the front I/O panel, and still no luck with the nexus ROM.
P.S. I'm tagging @Magendanz, just in case you find it interesting how odin refuses to flash your Nexus rom. If you want to, I could test the nexus rom on the latest T515 firmware, perhaps the fw refuses to go below the current version I'm on?
P.P.S : added Odin output
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1303)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3048 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> param.bin
<ID:0/003> product.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Download mode screen spits out Only official released binaries are allowed to be flashed so I guess it is a matter of bootloader unlocking after all?

[deleted]

@fpozar There are two problems that I know of that can cause a FAIL on the product.img line in Odin -
USB debugging not turned on
Incomplete boot loader unlock
Looks like option 2.
As Magendanz has said elsewhere -
Did you reboot with the USB cable inserted holding Vol Up & Vol Down to get the light blue Warning screen and then long press Vol Up to finish unlocking bootloader? A short press, rebooting to bootloader from stock recovery, or adb reboot bootloader in debugging mode won't cut it.
Click to expand...
Click to collapse
Update: More from Magendanz, on missing OEM unlock option:
This is what the VaultKeeper "feature" does. You've got to open Developer Options with internet connectivity for it not to automatically undo your efforts to unlock.
Click to expand...
Click to collapse
So connect to wifi before doing the Developer options thing, then try the bootloader thing.

MossyTC said:
@fpozar There are two problems that I know of that can cause a FAIL on the product.img line in Odin -
USB debugging not turned on
Incomplete boot loader unlock
Looks like option 2.
As Magendanz has said elsewhere -
Update: More from Magendanz, on missing OEM unlock option:
So connect to wifi before doing the Developer options thing, then try the bootloader thing.
Click to expand...
Click to collapse
Yes, I have done the light blue screen long press step.
Now I've held vol buttons while starting the tablet and chose the short click step (the long click step only leads me to locking bootloader again) and entered a bit different looking download mode (the same one you get by using recovery to enter bootloader, but with a bit more colorful text on the sides), but to no avail, the flashing didn't go through and only lead me to emergency recovery. And again, flashing stock worked.
Secondly, OEM trick worked for me, it appeared when I connected to my home network and made it that oem unlock was greyed out and said "oem unlocked".
Tommorrow I'll try to lock the bootloader and unlock it again. It's really weird though because the blue screen part was done correctly it seems (because long pressing leads me to locking).
Bootloader screenshot when entered by volume + and - combination

I'm a bit confused on what I've been doing wrong and where to proceed from here. These are the steps I've done on my most recent try:
1) Downloaded:
- Samsung Smart Switch
- TWRP 3.3.1.5 .tar.md5
- Magisk (Latest Magisk Manager)
- Odin
- Firmware T510 (XAR-T510XXU1ASEF-20190605151710.zip)
- Multi-disabler
2) Followed Unlock Bootloader from mingkee
3) Installed TWRP recovery via Odin
4) Rebooted back into stock ROM
5) Installed Magisk.apk
6) Using Magisk Manager > Selected AP_T510XXU1ASEF_CL15874928_QB23938566_REV02_user_low_ship_meta_OS9.tar.md5
7) That gave me magisk_patched.tar which I moved over to my desktop
8) Boot back into download mode
9) Flash the magisk_patched under AP, TWRP under BL, and HOME_CSC under CSC
10) Then Odin said it failed
Honestly I was pretty confused by the steps going from guide to guide so I'm not sure where I went wrong.
Also I'm not sure where I'm suppose to be flashing multi-disabler. The guide just said don't forget to install it but I'm not sure at which step I should be installing it via TWRP.
Any help would be appreciated.
Edit:
I tried again going with just steps from [GUIDE]Comprehensive T510 root guide.
I unlocked bootloader > patched the AP file I downloaded > Tried flashing the AP file only using Odin and it gave me an error:
"Only official released binaries are allowed to be flashed"

@Orite I'm sorry that I haven't been clearer, but I did say to read the relevant guides and read my thoughts below.
In the OP I said
Root can be achieved by flashing Magisk in TWRP (you also need to install the Magisk Manager app). There is no longer a need to use Magisk Manager to patch a tar.md5 file or anything like that.
Click to expand...
Click to collapse
Full details in the Rooting section in the OP.
You should have been following the TWRP Recovery guide for installing TWRP which clearly states at what point to install Multi-disabler.
If you can boot into TWRP you can flash the Multi-disabler zip file. Tap Install then select the zip file. That should fix the problem of not being able to flash via Odin, though you don't need Odin to install Magisk.

Update : So today I've reunlocked bootloader again and still got stuck at product.img step. Again, this is all on fresh windows and Odin works on original firmware.
This time, the error message displayed on my tablet is :
SYSTEM REV. CHECK FAIL. DEVICE:2 BINARY:1 (PRODUCT)
I can only assume this is some anti rollback feature similar to what happens on LG devices when you try to flash software older than what you're currently at.
I guess now we wait for dev's confirmation and if anyone else has something smart to say please feel free to join the discussion. I would try and download older official firmware and try to flash nexus while on something older, but my network connection is kinda unstable and it takes hours to download without a paid account.
Just to avoid questions, my method of unlocking followed exactly the link in the OP and method of flashing was following the mini guide on Nexus rom's OP.
EDIT : For all the T515 users, it seems odin isn't allowed (by some security features) to downgrade bootloader, and since Nexus ROM is based on May update for T515, anyone on updates newer than May can't flash the ROM. I found the answer on Galaxy s9 forums so that might be untrue for our device, but I didn't see many of us T515 users talking about custom roms so that might be it, and the error code makes sense.
Thanks again @MossyTC for trying to help

@fpozar
Magendanz doesn't explicitly say so in his OPs, but in some of his posts he does suggest matching the kernel versions.
magendanz said:
Well, TWRP is going to use a custom kernel based on the latest kernel source release, which as of yesterday is T510XXU2ASI4. The custom recovery uses this, but it will also substitute a new boot partition with the custom kernel so that Knox boot security features are disabled and you can still boot to system. I'd think the goal would be to match them as closely as possible. That said, often newer bootloader releases will prevent downgrading, so it's not entirely without risk to use the newest release. The safest bet is to always match the version exactly.
Click to expand...
Click to collapse
Anyway it looks like you're stuck with stock until there's a newer t515 custom ROM.

Thank you. I was finally able to figure it out with your response.

Hi, I have seem to messed up my process somehow, this tutorial seems kind of out of place.
When i try moving the multidisabler to my phone, it looks like all my folders and files are encrypted inside twrp and from the mounted drive on my pc.
I tried installing multidisabler using an OTG which worked on twrps side, i then rebooted and launched into OEM. after restarting from OEM android, i now receive a message when trying to do anything involving turning on my tablet "Only Official Release Binary Aloud" I cant do anything with it now. It just Shows that msg and the samsung logo, and then goes away, never booting, never entering recovery.
I tried to google this and it came up with something about knox, which i know nothing about. I really hope i didn't just brick my device.

Does unlocking Bootloader on the T510 change Widevine from L1 to L3? This is my only hestitation to bootloader unlock and root

trashbag1 said:
this tutorial seems kind of out of place.
Click to expand...
Click to collapse
This isn't really a tutorial, more like additional information to help you follow the guides linked in the OP.
When i try moving the multidisabler to my phone, it looks like all my folders and files are encrypted inside twrp and from the mounted drive on my pc.
Click to expand...
Click to collapse
You're internal data is encrypted by default by Android, but the version of TWRP we're using can't handle encryption. We get around that by disabling encryption by wiping the data partition as one of the first things we do when TWRP starts up, as per the instructions in Magendanz's threads. Ideally you should have the Multi-disabler zip on your sdcard before flashing TWRP. I have amended the instructions above to suggest as much.
I tried installing multidisabler using an OTG which worked on twrps side, i then rebooted and launched into OEM. after restarting from OEM android, i now receive a message when trying to do anything involving turning on my tablet "Only Official Release Binary Aloud" I cant do anything with it now. It just Shows that msg and the samsung logo, and then goes away, never booting, never entering recovery.
I tried to google this and it came up with something about knox, which i know nothing about. I really hope i didn't just brick my device.
Click to expand...
Click to collapse
Is your device an SM-T515? You may be having the same problem as @fpozar.
Can you get into Download mode again?

tomdot said:
Does unlocking Bootloader on the T510 change Widevine from L1 to L3? This is my only hestitation to bootloader unlock and root
Click to expand...
Click to collapse
I don't know what will affect Widevine.
I think the bootloader can be relocked, but I can't check right now.

The bootloader *can* be locked, I know as I've done it yesterday. In fact, it can be relocked and renlocked as many times as you want. To lock it follow the guide to unlocking but when you enter the light blue menu, holding vol up will lead you to locking and reseting your tab

another guide? lol pretty soon will b only guide threads in here lol

fpozar said:
The bootloader *can* be locked, I know as I've done it yesterday. In fact, it can be relocked and renlocked as many times as you want. To lock it follow the guide to unlocking but when you enter the light blue menu, holding vol up will lead you to locking and reseting your tab
Click to expand...
Click to collapse
"And resetting". That's the problem. You can't relock without resetting and having to start over from scratch.

elliwigy said:
another guide? lol pretty soon will b only guide threads in here lol
Click to expand...
Click to collapse
Yeah, well there are about twelve Galaxy Series A models and the geniuses at xda put them all in one bucket, so lots of Guides in the Guides, News & Discussion section, lots of ROMs in ROMs, Kernels & Recoveries, etc.

Lg g6 bootloop i cant do anything

Hi guys !
We had unlocked the bootloader and after that, had installed twrp but it didn't start in a few attempts. The "Your software cannot be checked for corruption" screen appeared. I had read somewhere that it's just a warning about the risk of installing custom OS and I just should go factory reset, so I did (and that was a stupid idea, I know). And then the bootloop started to happen. My PC can't see my phone and I can't turn it off in any way

To turn it off just hold the power button... while its bootlooping, it will shutdown. Connect the phone to the pc and enter the bootloader. type fastboot devices, if the pc sees it with a question mark but cannot apply the driver, download the bootloader interface driver and set it manually, now retype fastboot devices and your pc will see it in fastboot, after that, reflash twrp or your recovery of choice, wipe all, format data and install your rom of choice.

marianodelfino said:
To turn it off just hold the power button... while its bootlooping, it will shutdown. Connect the phone to the pc and enter the bootloader. type fastboot devices, if the pc sees it with a question mark but cannot apply the driver, download the bootloader interface driver and set it manually, now retype fastboot devices and your pc will see it in fastboot, after that, reflash twrp or your recovery of choice, wipe all, format data and install your rom of choice.
Click to expand...
Click to collapse
i cant turn off, is stuck on fastboot... how i can unbrick???

hold the vol- button and connect usb cable to a computer. it will connect in fastboot mode. From there you can flash twrp again.

Verity. said:
hold the vol- button and connect usb cable to a computer. it will connect in fastboot mode. From there you can flash twrp again.
Click to expand...
Click to collapse
I am having a similar issue after flashing the TWRP image - phone when into boot loop - resetting did not help. Now, it continues to reboot at the LG logo.
I was able to get it into the fastboot menu (once in like 50 times) - but am unsure of how to repeat the steps (to get it into fast boot)
Can you list the steps, and at what time do you press the vol- button, and when to connect USB cable?
Many thanks in advance

MrJoker8989 said:
I am having a similar issue after flashing the TWRP image - phone when into boot loop - resetting did not help. Now, it continues to reboot at the LG logo.
I was able to get it into the fastboot menu (once in like 50 times) - but am unsure of how to repeat the steps (to get it into fast boot)
Can you list the steps, and at what time do you press the vol- button, and when to connect USB cable?
Many thanks in advance
Click to expand...
Click to collapse
i have the same issue, cannot enter fast boot mode

Any news?
@Vargrimst @MrJoker8989

xVeenix said:
Any news?
@Vargrimst @MrJoker8989
Click to expand...
Click to collapse
unfortunately not, i believe i'll have to trash the phone

Vargrimst said:
unfortunately not, i believe i'll have to trash the phone
Click to expand...
Click to collapse
Hey! Don't lose your hope yet. I managed to fix my phone!
So first of all just to be clear - my problem was that after trying to flash ROM using Custom Recovery (in my case it was OrangeFox Recovery) my phone was stuck in bootloop and it did turn on by itself after forcing shut down.
What I did to fix it:
1. I've waited for battery to discharge
2. I've downloaded and installed on my PC:
- LG UPPERCUT - Download here - XDA
- LG Mobile Drivers - Download here - LG.COM
- Android Fastboot Drivers (not necessary needed but i wanted them just to be sure) - Download here - drive.google.com
3. After that I went to search for stock KDZ for my model and my region here (lg-firmwares.com)
4. When everything was downloaded and installed I took my phone and while holding Vol+ I've connected USB cable to my phone (make sure the second part is connected to PC before pluging in to phone) and after few seconds my phone booted into Download Mode
5. Now you need to run LG UPPERCUT - if your phone is listed in upper list then you good to go and if not, check your drivers and errors in Device Manager - select your KDZ in "BIN File", change checkbox from "REFUBRISH" to "UPGRADE", click "Start" and wait.
Your phone will reboot few times but after hitting 100% in Uppercut it will take 2-5 min and boot to stock OS!

xVeenix said:
Hey! Don't lose your hope yet. I managed to fix my phone!
So first of all just to be clear - my problem was that after trying to flash ROM using Custom Recovery (in my case it was OrangeFox Recovery) my phone was stuck in bootloop and it did turn on by itself after forcing shut down.
What I did to fix it:
1. I've waited for battery to discharge
2. I've downloaded and installed on my PC:
- LG UPPERCUT - Download here - XDA
- LG Mobile Drivers - Download here - LG.COM
- Android Fastboot Drivers (not necessary needed but i wanted them just to be sure) - Download here - drive.google.com
3. After that I went to search for stock KDZ for my model and my region here (lg-firmwares.com)
4. When everything was downloaded and installed I took my phone and while holding Vol+ I've connected USB cable to my phone (make sure the second part is connected to PC before pluging in to phone) and after few seconds my phone booted into Download Mode
5. Now you need to run LG UPPERCUT - if your phone is listed in upper list then you good to go and if not, check your drivers and errors in Device Manager - select your KDZ in "BIN File", change checkbox from "REFUBRISH" to "UPGRADE", click "Start" and wait.
Your phone will reboot few times but after hitting 100% in Uppercut it will take 2-5 min and boot to stock OS!
Click to expand...
Click to collapse
thanks, i'll try, i'm not sure about booting into download mode, as i've tried everything let's hope this time goes better... but what about the old flashing, like.. i went in a bootloop because i tryied to install Twrp, will lg uppercut overwrite everything to stock?

Yes. It will flash full Stock LG Firmware with Recovery
Vargrimst said:
thanks, i'll try, i'm not sure about booting into download mode, as i've tried everything let's hope this time goes better... but what about the old flashing, like.. i went in a bootloop because i tryied to install Twrp, will lg uppercut overwrite everything to stock?
Click to expand...
Click to collapse