Related
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
adambombz said:
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
Click to expand...
Click to collapse
It's not rooted out-of-the-box. Google doesn't allow this. But apparently, root will be very easy; just plug it into your computer and enter in a few command lines and you're set (so I've heard). Undoubtedly someone will make a one-click script that makes it even easier.
EDIT: Sorry for that one, was posting too fast without thinking first... Actually rooting includes unlocking bootloader and flashing the required binaries via recovery like said below my post.
Sent from my Desire X using XDA Premium 4 mobile app
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Click to expand...
Click to collapse
Really? Sweet!
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Naturally if you want to root the phone, it's only a quick USB cable plug into your computer and a few command line entries away.
Click to expand...
Click to collapse
Good read, BTW.
OnePlus One Review | Android Central
CafeKampuchia said:
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Good read, BTW.
OnePlus One Review | Android Central
Click to expand...
Click to collapse
That's where I heard it. In any case, it'll be simple; that much was promised from the beginning.
What about SuperSU though? I'm honestly not sure how that gets installed to the right place; the only times I've rooted were with programs that did it for me.
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Sent from my Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh really? Absolutely ridiculous.
tiny4579 said:
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Correct - no retail device shipping with Google CTS/GMS can have root enabled, much less the ability to right OUT OF THE BOX. It has to be done manually by the user, at their discretion.
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Chromium said:
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Click to expand...
Click to collapse
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
dmo580 said:
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
Click to expand...
Click to collapse
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
cyanogenmod has been planning to separate root for years. i think they are coming up with a simple method of root. maybe just an app install?
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Cm I think opted to make root removal so they could get cts approval and install Google Apps.
Sent from my HTC One using Tapatalk
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
The Jack of Clubs said:
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
Click to expand...
Click to collapse
I wonder if they're using this recovery.
https://github.com/CyanogenMod/android_bootable_recovery-cm
Simple recovery is the working title.
You are correct that custom recoveries aren't always needed for root; however, in Android 4.3 and later, the two primary root applications need to install a superuser daemon which makes rooting outside of recovery more difficult.
tiny4579 said:
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Click to expand...
Click to collapse
You all guys keep saying that rooting is trivial, but nobody told how to root. I believe you that it's trivial but - anyway -please tell me how to do this step by step.
I'm actually having trouble getting my 64GB production unit to boot into TWRP or have it flash and stick. fastboot says everything is fine, then rebooting into recovery produces the stock simple recovery.
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
I'm sort of at a loss - I've done this to many Nexus devices before, and the idea is the same. My bootloader is unlocked, that went without any issues.
Booting a debug boot.img from https://cyngn.com/products/oneplusone via fastboot just ends up shutting down and showing the battery charging icon.
Volume Up + Power while booting ends up with a black screen - in fact, the only way I can get into recovery is from a booted OS.
Edit: After many tries, trying different cables and unchecking the Settings -> Development -> update recovery with system updates, the TWRP flash succeeded, and the subsequent SuperSU sideload went just fine. Now I'm rooted.
Another tip regarding using Power+VolDn or Power+VolUp - things happen so slowly that if you keep holding Power, it'll actually trip a reboot before it has a chance to load. Just hold the Power button for a few seconds when booting, then let go and keep the VolUp or VolDn pressed.
Chromium said:
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
Click to expand...
Click to collapse
I just did this and it seems to have worked. TiBu just completed..
Used "Fastboot boot TWRP-2.7.1.0.zip" at ADB/Fastboot interface. It booted to TWRP. As I closed, it stated that it looks like "Your device isn't rooted, Do you want to install SuperSU?" To which I said Yes. It rebooted and I was able to open SuperSU, already on the phone, and get root. Then, opened TiBU and performed a full backup.
Archon810 said:
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
Click to expand...
Click to collapse
The first time I did this it hung for a while. it eventually boots into the recovery. I think it took about 2 minutes for it to finally boot into it.
Maybe that helps?
Root One+ fastboot devices hnags "waiting for device"
I amd trying to unlock bootlaoder, and install TWRP on my ONE+. I have tried both android SDK, and TOOLKIT FOR ONEPLUS FROM XDA, and I cannot get fastboot devices to recognize my One+.
What I have do so far:
My PC: windows 7 - 64bit
Installed SDK kit form developer.android.com, and installed the latest composite usb driver from Google.
Installed OnePLus toolkit and tried using that, no dice.
when I execute "fastboot devices" from my fastboot folder, my prompt hangs "waiting for device" FOREVER!!!
"ADB DEVICES" WORKS PERFECTLY, AND ECHOES MY SERIAL NUMBER BACK TO ME."
Hello everyone!
Since I've unlocked and rooted my Pixel 2 it keeps failing the OTA update. I get the notification and the update is downloaded but when it's being installed, there is an undefined error. For all updates I had to sideload the OTA file via ADB. Honestly, I don't really know what could have caused this issue, as the first OTA update when I got the phone with all stock settings and roms it worked fine. Currently I can only instal the OTA.zip updates via ADB.
Things I did so far which could have caused the issue:
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Things I tried to resolve the issue:
Lock the bootloader again
Flash full stock rom with fastboot and official google script (failed "couldn't write bootloader.img" altough I had it unlocked)
Factory reset
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
Does anyone else have similar experiences?
ekalz said:
Things I did so far which could have caused the issue:[/B]
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Click to expand...
Click to collapse
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
ekalz said:
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
?
Click to expand...
Click to collapse
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.
SweetSofie said:
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.
Click to expand...
Click to collapse
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.
Can you root without patching or unlocking the bootloader so you don't fail the integrity check?
robocuff said:
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.
Click to expand...
Click to collapse
Thanks for the clarification! I would love to learn more about that stuff, I'm just not sure where to start learning.
I have the same problem with my pixel 2. I have tried full factory reset by flashing stock image. I have tried the recovery script some user posted in the p2 forum.
I contacted Google support about it and now i am waiting for 2nd line to contact me.
I will post here if/when i get a solution.
With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete
socal87 said:
With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete
Click to expand...
Click to collapse
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?
smorgar said:
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?
Click to expand...
Click to collapse
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread
socal87 said:
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread
Click to expand...
Click to collapse
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)
smorgar said:
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)
Click to expand...
Click to collapse
Did you try to sideload via ADB?
socal87 said:
Did you try to sideload via ADB?
Click to expand...
Click to collapse
No I am waiting to get it resolved by Google so that I can install OTA in the future.
smorgar said:
No I am waiting to get it resolved by Google so that I can install OTA in the future.
Click to expand...
Click to collapse
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.
socal87 said:
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.
Click to expand...
Click to collapse
I was trying to fix the problem permanently so that i dont have to sideload if i dont want to.
**** went to ****... I did factory reset as the Google support person told me. Tried installing OTA again but it did not work. So they left me waiting for second line support to contact me but its now been the whole weekend and no support.
After support told me to do reset the last time the phone began to freeze and crash apps randomly. So i tried to install full factory image via fastboot but that was the last time the phone booted up. Now its completely dead.
When i try to boot the phone nothing happens. If i hold power button for 20-30 sec i sometimes get a short vibration and a line of pixels flashing by on the screen then nothing more happens. Now im waiting for Google support for real. Pray for my dead pixel2
If anyone have some tips for me im willing to try. The phone does not seem to boot and the PC does not recognize it at all.
You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.
davidisflash said:
You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.
Click to expand...
Click to collapse
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
And so how did everything work out for you? Were they able to get you resolved, or are they just RMA'ing your phone?
No resolution. I sent it back to uk for replacement via seller.
smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716
davidisflash said:
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716
Click to expand...
Click to collapse
I have done all the basic and advanced stuff. I had it dead for about a week to play around with. Used to work in a mobile repair shop so this isnt something new for me.
Okay, so my phone is bricked and there's no recovering it. RMA is already ordered and on it's way. Essentially I'm in the same situation as this poor soul (and many others, from the results of searching for this error in the forums).
What I want to know is if I did this or if this was something I couldn't have foreseen. The phone had an unlocked boot loader with the latest OS (Pie) & security updates (November). No custom ROM or kernel - stock everything, though I did have Magisk installed. Today I decided to re-lock my bootloader. While the device was in fastboot mode I issued the command "fastboot flashing lock" and followed the phone's on-screen directions. When it finished and tried to reboot, it would only go the fastboot mode with the message "ERROR: Slot Unbootable: Load Error".
I recognize that locking the bootloader may have been the last straw for some present flaw - like a weak engine finally giving out after long service. Is that the case here or is there some step I missed that would have prevented this from happening? I ask because I don't want to repeat a mistake in the future.
u found any way to unbrick your phone?
yuva_cool said:
u found any way to unbrick your phone?
Click to expand...
Click to collapse
Nope. The RMA was approved and I'm using a new (refurbished) device.
U had an unlocked bootloader and yet your RMA was approved? @computerslayer
yuva_cool said:
U had an unlocked bootloader and yet your RMA was approved? @computerslayer
Click to expand...
Click to collapse
The error showed up when I relocked the bootloader, so it was locked when I submitted the RMA. They approved it (and didn't demand a payment when they received the RMA'd phone), so I suppose they accepted that it was a warrantied issue.
computerslayer said:
The error showed up when I relocked the bootloader, so it was locked when I submitted the RMA. They approved it (and didn't demand a payment when they received the RMA'd phone), so I suppose they accepted that it was a warrantied issue.
Click to expand...
Click to collapse
Did you flash the stock boot image before you relocked? If not, Magisk was still installed and that's where you went wrong. You need to be completely stock when you relock the phone.
If you ever relock the phone you have now, to be on the safe side, I'd flash the factory image and leave the -w in the flashall batch file. Your phone will get wiped when you relock it anyway so you won't be out anything if you do so.
robocuff said:
Did you flash the stock boot image before you relocked? If not, Magisk was still installed and that's where you went wrong. You need to be completely stock when you relock the phone.
If you ever relock the phone you have now, to be on the safe side, I'd flash the factory image and leave the -w in the flashall batch file. Your phone will get wiped when you relock it anyway so you won't be out anything if you do so.
Click to expand...
Click to collapse
I am abashed to have to report that I did not flash the stock boot image. I wondered if Magisk was the cause, but assumed that the wipe caused by relocking would take care of that too.
computerslayer said:
I am abashed to have to report that I did not flash the stock boot image. I wondered if Magisk was the cause, but assumed that the wipe caused by relocking would take care of that too.
Click to expand...
Click to collapse
If that's the case, it's a certainty that that's the cause of your problem. You have to be completely stock when you relock it. Flashing the factory boot image should take care of that if all you have done is installed Magisk. That said, I'd still flash the factory image and let it do the wipe, just to be sure.
computerslayer said:
Okay, so my phone is bricked and there's no recovering it. RMA is already ordered and on it's way. Essentially I'm in the same situation as this poor soul (and many others, from the results of searching for this error in the forums).
What I want to know is if I did this or if this was something I couldn't have foreseen. The phone had an unlocked boot loader with the latest OS (Pie) & security updates (November). No custom ROM or kernel - stock everything, though I did have Magisk installed. Today I decided to re-lock my bootloader. While the device was in fastboot mode I issued the command "fastboot flashing lock" and followed the phone's on-screen directions. When it finished and tried to reboot, it would only go the fastboot mode with the message "ERROR: Slot Unbootable: Load Error".
I recognize that locking the bootloader may have been the last straw for some present flaw - like a weak engine finally giving out after long service. Is that the case here or is there some step I missed that would have prevented this from happening? I ask because I don't want to repeat a mistake in the future.
Click to expand...
Click to collapse
I have this issue and now my pixel 2 cant boot. It stuck. Cant enter fastboot. This is my last experience with pixel series devices. Its expensive phone, but its too sensitive to brick. I dont know why, an update or a flashing stock rom can make your phone totally unuseable. I just cant accept it
I had exactly the same issue. just keep holding the power button with or without the vol- for a good 30~ seconds or so (it will restart several times) but keep holding.
and make sure you are connected to the PC until you hear the ding that the phone got recognized, then the phone will accept fastboot commands.
This worked for me before I was going to throw the phone in the garbage!
Hi could anyone give me instructions on how to root my samsung Galaxy a20e please
Wazzer21 said:
Hi could anyone give me instructions on how to root my samsung Galaxy a20e please
Click to expand...
Click to collapse
This might help. https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Spaceminer said:
This might help. https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Click to expand...
Click to collapse
The third step is doesnt work for me. (Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.)
triumfanto said:
The third step is doesnt work for me. (Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.)
Click to expand...
Click to collapse
You might not have an unlockable bootloader, or it might just be a different key combo. If you got one that was already carrier branded by Verizon or At&t then you're probably out of luck. You might want to try reading this too. (The middle response.) This is how the regular A20 users are unlocking theirs.
Spaceminer said:
You might not have an unlockable bootloader, or it might just be a different key combo. If you got one that was already carrier branded by Verizon or At&t then you're probably out of luck. You might want to try reading this too. (The middle response.) This is how the regular A20 users are unlocking theirs.
Click to expand...
Click to collapse
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
After few hours later I have a rooted a20e phone! (A202FXXU2ASG1)
When bootloader is really open odin can rewrite original boot.img with the magisk patched one.
TWRP is only need for me now.
triumfanto said:
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
Click to expand...
Click to collapse
I love hearing good news! I'm willing to bet that whatever they're doing to get root will also work for you too. You'll have to do a little digging over there. You also have the same chipset as them and they have twrp already! It should be portable to your device without much of an issue. It really sounds like anyone with an A series can rejoice. I'm tempted to get one myself at this point.
Flash failed
Hello,
I have also a Samsung galaxy a20e and I followed the instructions, but the flash at step 7 fails. The firmware that I used is provided by this sammobile. It's works when I use it normaly, but fails when I use the magisk generated file for the AP . The operation stop when Odin reading the recovery image.
I uncheck the Auto Reboot option like specified
Can someone help me please?
Have a look at this:
https://unofficialtwrp.com/galaxy-a20e-sm-a202fd-root-twrp/
this is what i am trying now, seems to be working to get TWRP and root in one go
(You May also need this: https://www.youtube.com/watch?v=mF2Nxck4FtM
because when i tried this the OEM Unlocking option in Developer Options was missing, follow the instructions in this link, get the OEM Unlock Enabled then follow the first link)
The OEM unlocking option was already active for me. Unfortunately the flash with TWRP that you give still doesn't work. Have you succeed on your side ?
smda said:
The OEM unlocking option was already active for me. Unfortunately the flash with TWRP that you give still doesn't work. Have you succeed on your side ?
Click to expand...
Click to collapse
Hi,
No I am still having the same issue as you, OEM Unlocked, but the flash at step 7 fails. The firmware that I used is provided by this sammobile. It's works when I use it normally, but fails when I use the magisk generated file for the AP.
It says "Can only flash official images"
1. extract the boot.img from the firmware of your device
2. unzip with zarchiver
3. download magisk manager and choose install then select the boot.img file
4. flash the patched boot.img in Odin
Done
there is no TWRP yet cause it would need to be build from source.
triumfanto said:
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
After few hours later I have a rooted a20e phone! (A202FXXU2ASG1)
When bootloader is really open odin can rewrite original boot.img with the magisk patched one.
TWRP is only need for me now.
Click to expand...
Click to collapse
Can you post the files for root? matching the AP via magisk doesnt work, Kingroot doesnt work, I have tried everything, please cam someone help me get this phone rooted!!! the phone is useless as it is as i need titanium backup to work!!!
ParadoxLogic said:
Can you post the files for root? matching the AP via magisk doesnt work, Kingroot doesnt work, I have tried everything, please cam someone help me get this phone rooted!!! the phone is useless as it is as i need titanium backup to work!!!
Click to expand...
Click to collapse
I have the same problem please help to root and put my hand I have tried to do things has this mobile to see if we give a little life thanks
Hello,
Sorry for chiming in, but maybe there is a misunderstanding? The original boot.img file (extracted from the stock firmware) needs to be first patched by the Magisk app. Only after it has been patched, the boot.img file should be flashed by Odin. Maybe the guide over there helps to make it clearer: https://www.getdroidtips.com/root-galaxy-a20-a20e/
EDIT1: I see posts about "vbmeta warning", so there might be some further hurdles, see e.g. there:
https://forum.xda-developers.com/galaxy-a20/help/root-method-twrp-samsung-a20e-help-t4017763
EDIT2: You might also want to have a look into the A20 (i.e. without the "e") section:
https://forum.xda-developers.com/showpost.php?p=80021195&postcount=4
EDIT3: vbmeta.tar attached there:
https://forum.xda-developers.com/showpost.php?p=80188834&postcount=237
Good luck!
PS:
I understood that no TWRP or other custom recovery was needed for this, but I assume that by unlocking the bootloader via the developer options (before flashing) or/and by flashing the patched boot.img (and vbmeta.tar?) file via Odin, the Knox counter is triggered, voiding warranty and some apps not working anymore (e.g. Samsung billing etc.), and OTA updates by Samsung not working anymore. Is that correct?
This thread was started by @Wazzer21. Actually, his first post so far remains the only one. And interestingly, I found this website:
https://www.androidinfotech.com/root-samsung-galaxy-a20e-pie/
...
How to Root Samsung Galaxy A20e Pie 9.0 (SM-A202F, SM-A202K)
First of all, thanks to Wazzer21 – XDA developer for TWRP support and topjohnwu – this genius is a one who discovered and maintaining Magisk. Samsung Galaxy A20e International variants come with a flexible bootloader.
...
Click to expand...
Click to collapse
Er, what does this mean?
When you read further through that page and come to the comments, you learn:
Chris says December 1, 2019 at 3:32 am
This does not work…..at all…
once completing, there is an error VBMETA error…..
Click to expand...
Click to collapse
Selva Ganesh says December 1, 2019 at 11:53 am
The problem is Magisk 20.0. Did you use that Magisk version? If so, Try with Patch version 20.1.
Click to expand...
Click to collapse
Can somebody please confirm this? Or is this all a hoax? Sorry for asking so bluntly, but I have mixed feelings (and still do not want to appear rude or something).
PS:
On this website about rooting the Samsung A20e ("SM-A202")...
https://www.flashfilebd.com/2019/07/samsung-a20-root-file.html
... there are several files for download and the following info:
...
Here You Find Samsung A20e Root File With Magisk Manager Apk. Samsung SM-A202/F/FN/S/K Binary U1 And U2 Root File Available Here.
...
Click to expand...
Click to collapse
What do "U1" and "U2" binaries mean, i.e. how do they differ? There is no explanation (unless I have missed something).
According to some hints from @physwizz in the A20 forum, the root methods described for the A20 also work for the A20e as pointed out in several posts there.
However, currently neither TWRP nor custom kernel seem yet to be available/working for the A20e.
triumfanto said:
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
After few hours later I have a rooted a20e phone! (A202FXXU2ASG1)
When bootloader is really open odin can rewrite original boot.img with the magisk patched one.
TWRP is only need for me now.
Click to expand...
Click to collapse
Hello, i read that you have root your phone, i am trying to do the same thing now but i don't know how please can you give me the process that you followed
I'm curious if at least the 20e version can be rooted, thank you all
ninowebs said:
I'm curious if at least the 20e version can be rooted, thank you all
Click to expand...
Click to collapse
Yes it can be rooted, just install TWRP, then dowbload magisk and flash it in TWRP.
which TPWR?
I root my phone before and I found out the most of the app I used doesnt work with rooted phone. I did flashed the original firmware but I am always getting an error prompt every time I restart my phone or turning my phone off. I also found out that all my banking apps doesnt work if the bootloader is open.
So, I am hoping if by any chance I can have my bootloader relocked?
phaw16 said:
I root my phone before and I found out the most of the app I used doesnt work with rooted phone. I did flashed the original firmware but I am always getting an error prompt every time I restart my phone or turning my phone off. I also found out that all my banking apps doesnt work if the bootloader is open.
So, I am hoping if by any chance I can have my bootloader relocked?
Click to expand...
Click to collapse
You can't change your mind later. Are you sure you can't use one of the safetynet fixes to use the apps?
Beyond that, I believe the locking command was never found. There was a post stating the ones for the ROG 3 didn't work, but I'm not sure if that was ever resolved.
You can make your banking apps work with magisk hide - that's an option to hide your root state for certain selected apps.
Anubarak16 said:
You can make your banking apps work with magisk hide - that's an option to hide your root state for certain selected apps.
Click to expand...
Click to collapse
From where I am at its not the root state that's causing the issue, my phone is not rooted at the moment its running on stock ROG5 firmware the latest one still it doesn't work. Its the unlocked boot loader that's causing the issue.
twistedumbrella said:
You can't change your mind later. Are you sure you can't use one of the safetynet fixes to use the apps?
Beyond that, I believe the locking command was never found. There was a post stating the ones for the ROG 3 didn't work, but I'm not sure if that was ever resolved.
Click to expand...
Click to collapse
I tried the safetynet fixes it doesn't work for me for as long as the boot loader is tampered it wont work. The ROG 2 relocking bootloader worked for me before using tool in one but now I'm not sure how to fix it. I may need the latest boot loader IMG it might fix the issue.
Whenever that I boot into fastboot it's showing fastbootd and not fastboot.
phaw16 said:
I tried the safetynet fixes it doesn't work for me for as long as the boot loader is tampered it wont work. The ROG 2 relocking bootloader worked for me before using tool in one but now I'm not sure how to fix it. I may need the latest boot loader IMG it might fix the issue.
Click to expand...
Click to collapse
You're correct about Safetynet fixes and this device. Some (or all?) apps seem to be able to detect the open bootloader on ROG 5 somehow if they want, even if you get a visual pass on Safetynet with fixes. Don't know how and not sure if there are fixes out there that may work - I didn't find one. I use another device for banking apps.
phaw16 said:
Whenever that I boot into fastboot it's showing fastbootd and not fastboot.
Click to expand...
Click to collapse
Try Fastbooting with the physical buttons (Vol Up + Power) instead.
phaw16 said:
From where I am at its not the root state that's causing the issue, my phone is not rooted at the moment its running on stock ROG5 firmware the latest one still it doesn't work. Its the unlocked boot loader that's causing the issue.
Click to expand...
Click to collapse
Continued at https://forum.xda-developers.com/t/how-re-lock-bootloader-asus-rog-5.4285013/
You can continue discussion in the existing thread here
Thread closed
Thanks