Hi guys, I want to root my phone and install custom recovery so that I can install custom roms .. are they available yet ?
Pls help me
Thanks in advance
-iNCEPTiON- said:
Hi guys, I want to root my phone and install custom recovery so that I can install custom roms .. are they available yet ?
Pls help me
Thanks in advance
Click to expand...
Click to collapse
Its tricky atm root, and not much in the way of stable roms I would hang fire bit longer
Sent from my BLN-L21 using Tapatalk
DoobyDroid said:
Its tricky atm root, and not much in the way of stable roms I would hang fire bit longer
Click to expand...
Click to collapse
Oh and due to honor 6x processor, nothing we can expect
Answer: How to root Honor 6x
WARNING: I AM NOT RESPONSIBLE FOR WHAT YOU DO TO YOUR DEVICE, YOU ARE THE ONE MAKING CHANGES, NOT ME.
I have rooted and flashed TWRP 3.10 on my Honor 6x BLN-24 with Android 7.0 Beta. Theres a new update 360 and 361 but when I try updating it just takes me to TWRP and gives me an error.
Downloads:
Adb & FastBoot - https://forum.xda-developers.com/showthread.php?t=2588979
Chinese Honor/Huawei program-
TWRP:https://dl.twrp.me/berlin/twrp-3.1.0-0-berlin.img.html (DOWNLOAD 3.1.0)
SuperSU:
How I did it: ( Assuming you know how to unlock your bootloader)
Plug your phone into your pc
tap build number 7 times (developer options)
enable USB debugging and Oem unlock.
(check if your device is connected) type adb devices in cmd
Get bootloader unlock code from Huawei/honor's website
Install Adb and fastboot (just press Y for all)
Use Adb to unlock bootloader with fastboot oem unlock (unlock code) in cmd
then do fastboot reboot in cmd
during reboot, device will factory reset.
setup phone quickly and turn on developer options again, this time oem unlock will be locked enabled, enable usb debugging and wait for the phone to connect to pc.
now, type adb reboot bootloader in cmd (this will bring you to fastboot/bootloader
now to flash (assuming you have twrp downloaded.) type fastboot flash recovery twrp-3.1.0-0-berlin.img in cmd
type fastboot reboot in cmd, and you're done with TWRP.
Done! With TWRP atleast. Restart your phone, download latest SuperSU, then in cmd (still plugged in your phone) type adb reboot recovery
then you are in TWRP! I hope you know how to flash SuperSU in TWRP because I'm not helping you with that.
Good Luck!
Oem unlocking has greyed out after officially updated to emui 5.0
I have officially updated to 7.0 Android i.e emui 5.0 before update i was using marshmallow that time i have unlocked bootloader as well as i have installed twrp recovery and rooted then i have got official nought updatr emui 5.0 i have updated then supersu says uh have to again root your device then i tried root but when i goes to developer option their oem unlocking option is Grey out it is unclickable
Plz help me to resolve my issue.
You must go back to Android 6, relock your Bootloader und deactivate OEM Unlock. Then update to Android 7, unlock bootloader and unlock OEM Unlock. I had the same Problem yesterday After that the OEM unlock is also grayed out but it is activated
How to relock bootloader n rollback to marshmallow
Plz Guide me.
Step by step for relocking bootloader and rolling back to marshmallow i hope uh will help mi
help
Can some one plese tell me how to root and install twrp on honor 6X 7.0 emui 5.0 please
Hi,
I recently got a brand new s6 G920A AT&T version from an authorized reseller. To my surprise the firmware on it is very old - 5.0.2 with sw version G920AUCU1AOCE
I have heard that this firmware was a pre-release/developer/engineering version of s6 and has unlocked bootloader. Is that true?
How do I find if the bootloader is locked or unlocked in my samsung s6 or for that matter in *any Samsung* phone? Is it possible to check using Odin or some other tool on whether the bootloader is unlocked?
Please let me know your thoughts or ideas! If the above is true, I could perhaps extract the unlocked bootloader and share it with everybody else!!
Thanks!
Alright Interesting...
Use ADB:
=========================================
1. Make to go to about device and tap build number 7 times.
2. Go to developer options (Above About Device)
3. Check usb debugging and oem (Just in case)
4. Connect your phone to your computer via usb cable (Of Course)
5. Download ADB Fastboot if you haven't already =====> https://forum.xda-developers.com/showthread.php?t=2317790
6. Install it and after that it should be set-up
6. Type the command fastboot devices
7. Then type fastboot oem device-info (BTW I am sorry for letting you know now but i think you might need to be in downloading mode or something to use the commands)
8. It should tell you if it is unlocked or not
==============================================
Method 2:
1. Boot up the phone normally then open the phone application and go to the dialer
2. *#*#7378423#*#*
3. Then service info --> configuration
4. Then it should say one of the following:
---------------------------------------------------------------------------------------------------------------------------------
1. Bootloader unlock allowed --Yes >> This means that your Bootloader is Locked
2. Bootloader Unlocked - Yes >> This means that your Bootloader is unlocked
I hope i was helpful to you, if not then i'm sorry to have wasted your time.
Thanks @ROOT67! Let me try both options out and get back on this thread.
ROOT67 said:
Use ADB:
=========================================
1. Make to go to about device and tap build number 7 times.
2. Go to developer options (Above About Device)
3. Check usb debugging and oem (Just in case)
4. Connect your phone to your computer via usb cable (Of Course)
5. Download ADB Fastboot if you haven't already =====> https://forum.xda-developers.com/showthread.php?t=2317790
6. Install it and after that it should be set-up
6. Type the command fastboot devices
7. Then type fastboot oem device-info (BTW I am sorry for letting you know now but i think you might need to be in downloading mode or something to use the commands)
8. It should tell you if it is unlocked or not
==============================================
Method 2:
1. Boot up the phone normally then open the phone application and go to the dialer
2. *#*#7378423#*#*
3. Then service info --> configuration
4. Then it should say one of the following:
---------------------------------------------------------------------------------------------------------------------------------
1. Bootloader unlock allowed --Yes >> This means that your Bootloader is Locked
2. Bootloader Unlocked - Yes >> This means that your Bootloader is unlocked
I hope i was helpful to you, if not then i'm sorry to have wasted your time.
Click to expand...
Click to collapse
Both the methods did not work! Please see for details below.
ROOT67 said:
Use ADB:
=========================================
1. Make to go to about device and tap build number 7 times.
2. Go to developer options (Above About Device)
3. Check usb debugging and oem (Just in case)
4. Connect your phone to your computer via usb cable (Of Course)
5. Download ADB Fastboot if you haven't already =====> https://forum.xda-developers.com/showthread.php?t=2317790
6. Install it and after that it should be set-up
6. Type the command fastboot devices
7. Then type fastboot oem device-info (BTW I am sorry for letting you know now but i think you might need to be in downloading mode or something to use the commands)
8. It should tell you if it is unlocked or not
==============================================
Click to expand...
Click to collapse
I could not put it in fastboot mode. Do we know if the Samsung s6 supports fastboot mode? If so, how to put it in fastboot mode?
Also as a side note, in developer mode under settings, I could find check box for USB debugging but not for OEM. There was another post which said that OEM checkbox was added under developer options only after bootloader lock was introduced in 5.1.1 firmware. Not sure if this is true.
Method 2:
1. Boot up the phone normally then open the phone application and go to the dialer
2. *#*#7378423#*#*
3. Then service info --> configuration
4. Then it should say one of the following:
---------------------------------------------------------------------------------------------------------------------------------
1. Bootloader unlock allowed --Yes >> This means that your Bootloader is Locked
2. Bootloader Unlocked - Yes >> This means that your Bootloader is unlocked
Click to expand...
Click to collapse
When I dial this number, nothing happened. Is there a different number for Samsung s6?
It's not a pre-release/developer/engineering firmware. It's just a really old firmware which released for public officially.
jilebi said:
Both the methods did not work! Please see for details below.
I could not put it in fastboot mode. Do we know if the Samsung s6 supports fastboot mode? If so, how to put it in fastboot mode?
Also as a side note, in developer mode under settings, I could find check box for USB debugging but not for OEM. There was another post which said that OEM checkbox was added under developer options only after bootloader lock was introduced in 5.1.1 firmware. Not sure if this is true.
When I dial this number, nothing happened. Is there a different number for Samsung s6?
Click to expand...
Click to collapse
No other number is available that i know of, like the person above stated it is a old firmware version and with that said i would highly try to prevent any updates from installing. I would love to help you out, but since i have no idea as to what would be needed to tell if the bootloader is unlocked, but i do know since Samsung is against us rooting and using our devices the way we want, it is safe to assume the bootloader is locked and because you have at&t variant. Your best bet to get your device bootloader information is to look around on the XDA forums.
Do you have any details on whether the bootloader was locked or unlocked for this old version? How can one test or check if bootloader is locked?
forumber2 said:
It's not a pre-release/developer/engineering firmware. It's just a really old firmware which released for public officially.
Click to expand...
Click to collapse
jilebi said:
Do you have any details on whether the bootloader was locked or unlocked for this old version? How can one test or check if bootloader is locked?
Click to expand...
Click to collapse
All AT&T branded nearly-new (including S6) Samsung devices has a non-unlockable locked bootloader.
There's no way to test that.
here are a couple of test scenario that i can think of. let me know your thoughts on them
- if the device is rooted, load a custom recovery like TWRP. next, try to boot into custom recovery. if it boots into custom recovery, bootloader is unlocked. if not, try to restore factory recovery using odin.
- if the device is rooted, load a custom ROM. next, try to boot into custom ROM. if it boots into custom ROM, bootloader is unlocked. if not, try to restore factory ROM using odin.
Will these test scenarios work? If not, what are the potential issues you see?
forumber2 said:
All AT&T branded nearly-new (including S6) Samsung devices has a non-unlockable locked bootloader.
There's no way to test that.
Click to expand...
Click to collapse
jilebi said:
here are a couple of test scenario that i can think of. let me know your thoughts on them
- if the device is rooted, load a custom recovery like TWRP. next, try to boot into custom recovery. if it boots into custom recovery, bootloader is unlocked. if not, try to restore factory recovery using odin.
- if the device is rooted, load a custom ROM. next, try to boot into custom ROM. if it boots into custom ROM, bootloader is unlocked. if not, try to restore factory ROM using odin.
Will these test scenarios work? If not, what are the potential issues you see?
Click to expand...
Click to collapse
- There's no custom recovery or custom kernel for SM-G920A, because of the reason I've wrote above.
- Installing a custom ROM doesn't require an unlocked bootloader unless the ROM doesn't require custom kernel. (Custom ROMs for SM-G920A don't require custom kernel (except leaked engineering/debugging kernel from Samsung for disabling dm-verity))
forumber2 said:
- There's no custom recovery or custom kernel for SM-G920A, because of the reason I've wrote above.
- Installing a custom ROM doesn't require an unlocked bootloader unless the ROM doesn't require custom kernel. (Custom ROMs for SM-G920A don't require custom kernel (except leaked engineering/debugging kernel from Samsung for disabling dm-verity))
Click to expand...
Click to collapse
Got it. Thanks. That makes sense.
Here is another option. For making custom recovery, my understanding is that partition info is needed. If the device is rooted e.g. using Pingpong (which works for this Android version), then one can get a partition info and compile TWRP for G920A. If so, can one try to install custom recovery like TWRP and verify if bootloader is locked? It feels to me that this may work. Do you see any flaws?
One possible flaw is that if bootloader is locked, it will prevent recovery from loading. So the phone will be without a working recovery. In that case, can factory recovery be re-installed using Odin?
Also, will any of the above steps trigger the KNOX flag?
jilebi said:
Got it. Thanks. That makes sense.
Here is another option. For making custom recovery, my understanding is that partition info is needed. If the device is rooted e.g. using Pingpong (which works for this Android version), then one can get a partition info and compile TWRP for G920A. If so, can one try to install custom recovery like TWRP and verify if bootloader is locked? It feels to me that this may work. Do you see any flaws?
One possible flaw is that if bootloader is locked, it will prevent recovery from loading. So the phone will be without a working recovery. In that case, can factory recovery be re-installed using Odin?
Also, will any of the above steps trigger the KNOX flag?
Click to expand...
Click to collapse
You don't have to get partition info, and compile TWRP. All S6 variants are using same partition name scheme and there are no difference on TWRP builds between S6 variants (except kernel and DTB).
The bootloader won't allow you to flash any custom recovery image (via Odin or in Android OS). If you could flash it, It won't boot it up anyway.
I don't have any idea about the KNOX trigger on AT&T variant devices, but I think it won't increase anyway.
forumber2 said:
You don't have to get partition info, and compile TWRP. All S6 variants are using same partition name scheme and there are no difference on TWRP builds between S6 variants (except kernel and DTB).
The bootloader won't allow you to flash any custom recovery image (via Odin or in Android OS). If you could flash it, It won't boot it up anyway.
I don't have any idea about the KNOX trigger on AT&T variant devices, but I think it won't increase anyway.
Click to expand...
Click to collapse
Sorry, I perhaps misunderstood from your last post that since custom recovery is not available for G920A it implied its partition info was different from other variants. If it is the same partition structure for all variants, then I guess we can use the TWRP for the G920F international version for which bootloader is unlocked.
Now that we agree that TWRP is available for use on G920A, the next question is how to load it. My thought is that if the device is rooted that means one can use dd at root shell prompt to write TWRP to the recovery partition, without using Odin or the current bootloader. Do you agree?
Not sure I understand why you say that if one could flash TWRP it would not boot anyways. If bootloader is unlocked (which is what we are testing here), then it should boot, right?
jilebi said:
Sorry, I perhaps misunderstood from your last post that since custom recovery is not available for G920A it implied its partition info was different from other variants. If it is the same partition structure for all variants, then I guess we can use the TWRP for the G920F international version for which bootloader is unlocked.
Now that we agree that TWRP is available for use on G920A, the next question is how to load it. My thought is that if the device is rooted that means one can use dd at root shell prompt to write TWRP to the recovery partition, without using Odin or the current bootloader. Do you agree?
Not sure I understand why you say that if one could flash TWRP it would not boot anyways. If bootloader is unlocked (which is what we are testing here), then it should boot, right?
Click to expand...
Click to collapse
A custom recovery is not available for G920A, because no one could try any custom recovery on G920A due to locked bootloader.
Yes you can write the recovery image via dd at root shell prompt.
And yes, If bootloader is unlocked, it will boot it up.
Sorry to ressurect this old thread, but can you (or anybody else who is knowledgeable) answer the following?
1. Since custom recovery is not available for G920A, which of the Tmobile/Sprint/International versions of TWRP custom recovery would you recommend to use for testing if bootloader is unlocked, using either ODIN or dd method?
2. If bootloader is unlocked, you are suggesting below that it should boot up. However, if it is locked, then will the phone still boot up? i.e. if one does not go into recovery mode, will it still boot up or does the bootloader check if both recovery and kernel are signed and if it finds that the recovery is unsigned, will it also prevent the signed kernel from booting up?
Thanks!
forumber2 said:
A custom recovery is not available for G920A, because no one could try any custom recovery on G920A due to locked bootloader.
Yes you can write the recovery image via dd at root shell prompt.
And yes, If bootloader is unlocked, it will boot it up.
Click to expand...
Click to collapse
Bricked Pixel 2 - locked bootloader & no access to developer options - please help
Hello guys, I just bought myself a Pixel 2 device today and decided to have a go at some changes: I've unlocked my bootloader of my Pixel 2 to perform TWRP flashing & Magisk installation and afterwards I decided to revert to stock.
The first step that I did when trying to revert to stock was to relock the bootloader via adb because I thought (big mistake) this will also revert everything to the factory image. Problem is right now the device isn't booting anymore (so I cannot change anything in developer settings and the bootloader is locked).
Fastboot does work now (I get an "FA8271A02780 fastboot" message when typing fastboot devices) but I cannot flash anything (it always says FAILED: remote Flashing unlock is not allowed.
I tried the Deuces script and UAF but they don't work (because my bootloader is locked). Given that I cannot unlock it, is there any way of flashing the stock image on my device? Any help is appreciated. Thanks a lot.
Sadly I don't believe so. Google doesn't allow us to flash anything without bootloader being unlocked. Other OEMs either have a program or allow you flash signed roms with a locked bootloader. For the trouble iTunes is at least you flash firmware through in the event of a Brick
I recently bought a Note 7 Pro wich is stuck in bootloop after flashing a rom. The guy couldn't give me that much details ...
What I encountered so far:
- might be chinese device (how can this be verified ?)
- bootloop to recovery with message: ... can't install this version "
- bootloader is locked at the moment / not sure if it was unlocked before
- Fastboot is accessible
- tried some updates via xiaomiadb - but without success.
--> China stable & developer recovery rom lead to errors: network carrier type different
--> Global V11 rom is accepted by tool but, leads again to bootloop with error message ...
Therefore I am not sure how to continue. Any hints ?
Thanks,
Oli
Hi, as u are saying that u stuck in bootloop in note 7 pro Answer - the reason is t
Hi, as u are saying that u stuck in bootloop in note 7 pro
Answer - the reason is that ur phone bootloader needs to be unlocked in order to flash any rom Or OEM image or else fastboot recovery image
Normally when phone stuck in bootloop we do flash via mi flash toot app using fastboot recovery image only.
Otherwise u will get error for sure ?
Now ur phone has a bootlock so u have to go to service centre and they will do recovery by opening back panel of phone and they will charge you around 350 plus tax if it is out of warranty
audischrauber said:
I recently bought a Note 7 Pro wich is stuck in bootloop after flashing a rom. The guy couldn't give me that much details ...
What I encountered so far:
- might be chinese device (how can this be verified ?)
- bootloop to recovery with message: ... can't install this version "
- bootloader is locked at the moment / not sure if it was unlocked before
- Fastboot is accessible
- tried some updates via xiaomiadb - but without success.
--> China stable & developer recovery rom lead to errors: network carrier type different
--> Global V11 rom is accepted by tool but, leads again to bootloop with error message ...
Therefore I am not sure how to continue. Any hints ?
Thanks,
Oli
Click to expand...
Click to collapse
Had you applied for Bootloader unlocking? If you had using MI Unlock tool, then wait for the time being until the time period is over and unlock the bootloader. It may work. Also, if you have stock recovery you may confirm with others and install stable OTA updates for the ROM to see if it fixes the device.
No. I did not try to unlock the bootloader. I received the phone in that bootloop and only did one attempt to recover through xiaomiadb with mentioned error.
Is there no other way to escape except going to a shop ?
Hi guys,
im looking forward to unlock the bootloader on my Cubot P30.
The phone is responding in USB debugging moder over the shell, for example when I´m typing "adb devices" or "fastboot reboot bootloader".
But in fastboot afer restart the device unfortunately doesn´t respond.
I even dont really know if the Bootloader is locked or not. The OEM Unlock slider under developer settings is set.
Furthermore The Recovery menu is in chinese, so i also dont know if there is a chance to doublecheck.
I tried flashing an Image over the Shell in case the booloader is unlocked but without success.
Also I cant´t find TWRP for this device, it seems there is no support for Cubot P30, isn´t it.
Hope there is a chance to update the device to Android 10 or Lineage, thanks in advance.
Update: The device is now unlocked. I flashed the Lineage 17.1 and unfortunately the device is still rebooting. Has somone a working image for this device?
Hello, how do you unlock your phone?
Mine Is P40 and same issue.
So if you tell me the way i really appriciate.
Thank you.
Unlock Bootloader & Root Android
Flashing process
1. Unlock Bootloader on Android Devices:
getdroidtips.com/unlock-bootloader-via-fastboot-on-android
2. Install custom recovery:
twrp.me/Devices
3. Root [Download & install supersu.zip via twrp, or root using magisk]:
getdroidtips.com/root-ulefone-power-6