I've spend a lot of time searching the internet and reading to find a sollution for rooting my newly XCover 4 (G390F).
Also found a couple of threads about this here on XDA doing so, but all not realy with a "complete" usable sollution. So I've tried to collect all the info I could find, hoping to combine it in something usefull.
I found some older topics about rooting the G390F on android 7, but this doesn't seemed to work for 8.1 (my current version). And there is verry few or complete topics to be found about rooting this phone for the 8.1 android version.
It seems that it should be able to work using Magisk, but before doing so I first should install TWRP.
Then I've found this TWRP version which seemed to work for this phone for others. But I got stuck installing this.
I've first tried using "15 seconds ADB Installer v1.4.3" for installing this TWRP image, so first installed all the corresponding drivers and USB-drivers from here but I'm not able uploading the TWRP image this way. There's simply no progression to be seen in download modus. And have to remove the battery to restart it then.
So I've tried flashing this TWRP using Odin (v3.13.1), which looked more promissing in the beginning because i was actually getting some feedback of the connection and uploading procedure. But this unfortunately failed in the end and showed me the following error:
"Custom binary blocked by FRP lock" in red.
{
"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"
}
I was hoping being on the right way, but seems I'm doing something wrong or missing something here.
Would really appreciate it if someone knows what I'm doing wrong here. Or even better, someone who knows how to root this G390F with Android 8.1, that would be really awsome! :highfive:
I'm willing to make this post complete as a guide then, so it could be of some help for people who encountering the same problem.
Related
Hi all,
Scoured the forum for a while but, to be honest, I didn't even know how to search for my issue. Please feel free to redirect me to another thread.
Two problems.
1.
Tried to flash Cyanogen to my Xperia Z3. Unlocked bootloader and tried to do something [enter technical word, flash maybe] a root img file. This soft bricked my phone, took it to a shop, they said it's dead, bought another one. Is this salvageable? More details: Followed instructions here, got to "fastboot reboot", (flashed a cyanogen nightly) then phone only made it to the Sony screen on startup. Then followed these instructions to flash moonwalker but the result was a soft brick (try to turn it on, one lifeless vibration and nothing). Didn't root it beforehand (yep, idiot). I've heard you could flash an older ROM, but this leads me to the problem below.
2.
New phone. Looking to root it. Using flashtool and an ftf (D6603_23.0.A.2.93) downloaded here, but when selecting firmware, the file ftf appears to be empty. I imagine flashtool has undergone cosmetic surgery (update) as it appears to be different than other pictures, or perhaps I'm missing something glaringly obvious?
If anybody with a bit of free time has a moment to help me out, I'd be very grateful. Many thanks.
{
"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"
}
Not sure the image is working and not able to post external links. To explain it, the firmware appears (and is the correct model), but all other boxes (content, wipe etc.) are empty and the flash button is greyed out.
Hi folks!!!
I have 2 galaxy note 10.1 (2012).
One of them had already put twrp several times and different roms without problem. Now there is no way to enter the recovery, it stays in the logo. I can not use odin either because it stays in get pit for mapping and from there it does not happen. I already tried to load several pits of this page but nothing. Also download an official rom but neither. There is no way to fix the tablet.
The other was never done anything, it was such a factory but, although it worked, there was no way to enter the recovery until one day did not pass the logo.
I have used windows 7 with the drivers, now there is no way and I have had to use windows 10 and if it recognizes the tablet but it still does not pass the get pit for mapping ...
I've also tried from Linux with fastboot devices but it does not recognize anything.
Any help ?. I know it's an obsolete tablet but my son worked to see the YouTube videos.
Attached 1 capture in case they are useful.
I've spent a lot of time with this problem and trying and reading but there's no way.
Thanks and sorry for bothering.
{
"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"
}
See your identical post .
You need a service center repair .
JJEgan said:
See your identical post .
You need a service center repair .
Click to expand...
Click to collapse
Thanks. is it the only way?.
Hey everyone,
I have this issue with my device hopefully you know something about it: a while ago I rooted it, got Magisk on it all that. The device was just out so updates were still coming strong--or maybe I payed more attention to them than I do now, IDK--the case is that I accepted one of them and it undid the root and updated MIUI to something-something, regardless, since then I'm unable to flash a recovery image.
I thought the partitions got messed up or something and flashed the official system with the official Xiaomi spyware/adware suite "tools" hoping it would rewrite what needed rewriting then I tried flashing the recovery (TWRP) but no luck.
I'm using the XiaomiADBFastbootTools Java applet. It seemingly flashes the thing successfuly then it boots right into the system again, not in recovery. If I use force a recovery reboot through adb or with the buttons (which I've already forgot which were) the recovery the comes up is the official one, not TWRP.
{
"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"
}
Every time finishes "successfully", then the device reboots taking just tiny bit longer then I see the MIUI logo with the sort of paint-spill animation covering it and then I'm back on stupid Mars again (the stock pseudo-interactive wallpaper). Not even my information is lost--not that I'd want to, but at least it'd be something.
Since I removed most bloat the phone became pretty much useless and I wasn't even thorough because there's stuff that just can't be removed. Rooting would allow me to get some utility back out of it. Can it be fixed at all??
If I check for an update it shows there's an update to android 13. I've tried several times to update and it always says there was a problem installing the update. I start the installation and then says it's paused. I resume and it says the installation will continue when the device isn't being used. I again hit resume and it says there was a problem. Rooted on build SD2A.220601.003.B1. I've tried on wifi and mobile data with no change. Restarted the phone several times with no change. I'm coming from a Oneplus 7 pro, is there something Pixel related that I don't know about? I haven't tried anything related to Magisk because I've never had to in the past.
{
"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"
}
Rooted on build SD2A.220601.003.B1. I've tried on wifi and mobile data with no change. Restarted the phone several times with no change. I'm coming from a Oneplus 7 pro, is there something Pixel related that I don't know about? I haven't tried anything related to Magisk because I've never had to in the past.
Rooted is the issue. Flash back the stock kernel or just flash 13 manually
You're trying to take an OTA while rooted and asking why it doesn't work? If you want to run a rooted phone, you have some learning to do before you brick your phone.
If root is the problem, it's not a big deal. Taking the OTA and then using Magisk to flash to the inactive slot has always been the easiest solution. The Oneplus never cared about root. Pixel 2 XL was my last pixel device I used but I always had a rom installed. So this is new to me.
Be careful...if/when you DO get updated and reboot into 13, make sure u flash the new bootloader to the other partition.
Hello everyone,
Some years ago i had an S7 as my phone, but it broke, and i bought an S10e now.
Until now, I didn't have problems with stock fw, but now I want to root the device.
I've read some articles about it, and it seems really really complicated.
I have looked at the Magisk website, why is installing through Custom Recovery not recommended? It's so much more complicated the way they describe it.
{
"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"
}
It also says, this is only possible if i have "boot ramdisk". What is that? Why is it required? And why do i not have it? (according to the Magisk App)
I remember it being as simple as putting TWRP on the phone and flashing Magisk on my S7.
Easy, fast, done with 3 clicks or something. (Same thing with new Operating System).
Why did everything become so complicated?
And is installing TWRP on it's own even possible? And is it even worth it if you can't install anything with it?
Thanks in advance, to anyone kind enough to take their time to explain.
I'm thinking of buying a used S7 again now
I use Lygisk root on my SM-G970F, but I first changed to a custom operating system (LineageOS). With a custom operating system, installation of Lygisk.ZIP is simply done in the Lineage custom recovery (and installing the client app Lygisk.APK to manage it)
If you use Google apps, you might want to try LineageOS+MicroG instead and then root that.
I haven't tried getting root with Samsung's original operating system, but I think it requires patching the boot image and is more complicated like you said.