Database Develop

Strange issue after lates OTA update 7.4.1 and root - settings menu disappeared

Hi all,
I have a very strange issue after the latest official OTA update to version 7.4.1.
I recognized that my KFHD updated the firmware and after this, I had no root anymore. I used Root_with_Restore_by_Bin4ry_v30 and my KFHD was rooted again (confirmed with root checker). Now I see that I am no longer able to user the settings menu at the top, for wireless network connection, brightness, etc., because it is no longer available. From time to time it appears for a very short period, but disappeared at the same time and I have no chance to drop down this menu.
Anyone here with the same problem or who can help me?
Cheers,
Ingo

Guys, no one, who can help me?

arnakin said:
Guys, no one, who can help me?
Click to expand...
Click to collapse
If you have a recovery installed, I would say just grab the rooted 7.4.1 from the development section and flash that after full wiping. That should solve your issues.

arnakin said:
Hi all,
I have a very strange issue after the latest official OTA update to version 7.4.1.
I recognized that my KFHD updated the firmware and after this, I had no root anymore. I used Root_with_Restore_by_Bin4ry_v30 and my KFHD was rooted again (confirmed with root checker). Now I see that I am no longer able to user the settings menu at the top, for wireless network connection, brightness, etc., because it is no longer available. From time to time it appears for a very short period, but disappeared at the same time and I have no chance to drop down this menu.
Anyone here with the same problem or who can help me?
Cheers,
Ingo
Click to expand...
Click to collapse
When (if) Kinology gets updated (for 7.4.1 support), flash that and your problem will be solved. Unless you don't care about what software version you are on. In that case just flash it now.

A similar problem
-a- said:
When (if) Kinology gets updated (for 7.4.1 support), flash that and your problem will be solved. Unless you don't care about what software version you are on. In that case just flash it now.
Click to expand...
Click to collapse
The OTA updated to 7.4.1 and i tried flashing a custom ROM by Hashcode but, recovery isn't working and with a force recovery in FireFire Flash. It shows a yellow triangle with an explanation point. Also, my audio has stopped working but, i may have found a solution.
To keep in mind: Already Rooted with B4NARY's root, and Google Play Installed.
All Help is appreciated!

CVanB said:
The OTA updated to 7.4.1 and i tried flashing a custom ROM by Hashcode but, recovery isn't working and with a force recovery in FireFire Flash. It shows a yellow triangle with an explanation point. Also, my audio has stopped working but, i may have found a solution.
To keep in mind: Already Rooted with B4NARY's root, and Google Play Installed.
All Help is appreciated!
Click to expand...
Click to collapse
Personally the only tool I've ever used because I got myself in so deep at one point I had no options was the Kindle SRTool, the others seem to create problems, not because the tools were written bad or anything, but because amazon seems to like pushing out updates that don't really update much, but change things just enough to mess with the functionality of the tools. If you can get back to fast boot, you should just use the SRTool and start fresh. Then go to prokkenexxusa's rooting thread and use the manual root method not the automatic.

Solved
DroidIt! said:
Personally the only tool I've ever used because I got myself in so deep at one point I had no options was the Kindle SRTool, the others seem to create problems, not because the tools were written bad or anything, but because amazon seems to like pushing out updates that don't really update much, but change things just enough to mess with the functionality of the tools. If you can get back to fast boot, you should just use the SRTool and start fresh. Then go to prokkenexxusa's rooting thread and use the manual root method not the automatic.
Click to expand...
Click to collapse
I didn't click flash script when I rebooted into recovery from fire flash. In fire flash you have a couple options, two mandatory, using a older bootloader as the 2nd. flash a boot partition image, apply stack override, flash a recovery partition image, disable auto recovery auto update, then wipe cache wipe data wipe system install zip files, flash and install script. Lastly reboot and reboot into recovery. :victory:

So did you get your issues sorted OK, or are you still having problems?

[Q] Having problems when trying to ROOT Moto G LTE x1040

Hi, I'm relatively new to this forum and I've been trying almost all day to root my phone...
First, I had problems trying to get a working recovery (they just crashed to random colors/or loaded fine and then rebooted like nothing happened). Tried with CWM Recovery but it seems this model is not supported atm, tried with TWRP v2.8.3.0 and also crashes... ATM the only custom recovery that has started without going haywire is TWRP v2.8.0.0 (at least for my phone).
I prefered using 'fastboot boot recovery.img' before 'flash' since it's the first time I'm trying to root a phone. The recovery mode starts okay and I also placed the UPDATE-SuperSU-v2.46.zip in the internal storage before hand. I try to install the .zip file and all goes well, no errors and a blue 'Successful' message. This is where the 'root' procedure fails. Since you can reboot or go home to check other stuff I just tried rebooting the first time and it asked me that I had a SuperSU in the device and that if I wanted to install it to have root. I obviously swiped to install it and it displayed for a split of a second the window from before and just shut down and rebooted...
I tried several other methods to try and root my phone after this failure, but none worked. I checked again if trying this procedure would serve a purpose but I got the same thing always. But since I saw the process so many times I could see for a moment a red line saying something like 'E: failed to copy su binary to /system/bin (...)' but couldn't read more because it was a split of a second there xD. I googled this weird error and I found that my /system is in read only state and not writtable... But to change it to writtable I need root too it seems <_<)
So, any help? I'm sorry if this long text makes someone just look away but I don't really know how to explain my problem in more simple words xD. Any help will be appreciated .
EDIT: Forgot to say that my phone has its bootloader unlocked already and it has USB Debugging enabled.
Moto G LTE x1040
System version (as my phone says) 21.31.1.peregrine.retla.retla.en.01 entcl
Build: KXB21.14-L1.56-1
OS: KitKat 4.4.4

Any help ?
Bump.

Bump. Tried with CF Root by Chainfire but no root gained =/ .

Wait you are in the wrong forum, this is for the second generation search for moto g 2013 all recoveries here are for different device

fburgos said:
Wait you are in the wrong forum, this is for the second generation search for moto g 2013 all recoveries here are for different device
Click to expand...
Click to collapse
I suppose that would be this one then? http://forum.xda-developers.com/moto-g
Thank you for the response, I'm going to repost this in that section, sorry for the mistake >.<

Help, moto x 2014 stuck in 'MOTO' logo

Hey, I have a moto X 2014 (xt1097)(brazil), unlocked bootloader,previously had root.
I updated to marshmallow about a month ago and had no problems whatsoever with it aside from the fact that root didn't already work for it.So yesterday I saw a post about a user that flashed the "SuperSU 2.62 v3" and got root, so I did the same but without flashing twrp(I just booted it)... It worked (sort of) but it was having some problem about a super su binary not working(I lost the screenshot).
With that I started searching for a way to make it work correctly, until I saw someone in a post saying that they wiped the phone and re-flashed the root file and it worked correctly, and that was what I did.. with one little difference I flashed the latest superSU file released (SuperSU-v2.64),but it didn't work, it initiated but there were notifications all the time about something not working(a lot of things).
With that in mind I started the same process I had done to flash the first superSU,wiped the data and cache, turned it on so that I could enable debug mode to start flashing the superSU but this time the phone didn't get out of the big `M` (powered by android) logo.
I seached a fix for it, on other posts people said that wiping everything(except system) and rebooting worked for them, but for me it didn't.
So I need help with this, if anyone can help please do so, thank you.
UPDATE: I just remembered that before that I didn't use the "unroot" function in the superSU version that didn't work, so I think that I got bootloop because of that, but I still don't know what to do.

Moto X always boots into recovery unless I manually choose normal startup each time

I rooted my XT1052 straight after updating to 5.1, a few years back. As a result I have never been able to install the OTA update (the one which fixed Stagefright, so far as I'm aware it's the only OTA Moto did after the 5.1 update.)
I've been unable to install a few apps recently due to SafetyCheck failing on the rooted phone, so yesterday I decided I would unroot and return to stock, which would also enable me to install the bugfix OTA. (And with Magisk, nowadays we can keep root access without a modified system partition.)
I didn't have a stock image (or I had an image of some sort on a hard drive but couldn't remember its provenance). Moto's download page has images for the XT1053 but not the XT1052… Eventually I found firmware.center, where (I thought) I found the right image.
However, when flashed it (following the step-by-step guides which are the same on various pages, including Moto's own instructions), it failed to flash the `system` image. I got messages about invalid block sizes (IIRC) and then an error saying the image was corrupt (it wasn't; I checked the MD5).
This left me unable to boot. So I downloaded LineageOS (I'd been considering switching to LineageOS anyway to get Android 6), and was able to flash it from TWRP without any issues (other than the fact that a newer version of TWRP is required than the one published on their website…)
All well and good – except that now, when I turn my phone on it goes straight into Recovery (TWRP). Initially I could only get System to boot by starting the bootloader (Pwr+VolDn) and selecting 'BP Tools', which would cause it to boot normally. (I found this by trial and error.) Now, after re-flashing the boot image, It also works if I select Standard Boot from the bootloader. But I still have to select it manually. If I just turn the phone on normally, with the power button, it always boots into Recovery. Also, all the 'reboot' options from fastboot/adb or TWRP all boot to Recovery.
Now, I think I know what I did wrong. The stock image I downloaded was 'XT1052_GHOST_RETGB_5.1_LPAS23.12-15.5-1_cid7_CFC.xml.zip', but my system version before was 5.1_LPA23.12-15.5. I just assumed that the 5.1_LPAS23.12-15.5-1 version was a minor update – likely with the Stagefright OTA installed – so I went for that. But probably I should have gone for the exact version I already had installed.
Searching these forums and the wider web, I haven't found anyone with the exact same issue. But from similar issues, I decided I needed to re-flash the partition table (gpt.bin). I took the gpt.bin image from an older 5.1 ghost ROM I had saved, but I'm not able to flash it – the bootloader shows security warnings when I try.
So I'm stuck now – I have tried pretty much everything I can think of.
If anyone has any ideas I'd be very grateful!

I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?

Alexjrbr said:
I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?
Click to expand...
Click to collapse
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.

cmjs said:
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.
Click to expand...
Click to collapse
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done

Alexjrbr said:
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done
Click to expand...
Click to collapse
Woohoo! Well done!
Look forward to seeing your solution

cmjs said:
Woohoo! Well done!
Look forward to seeing your solution
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644

Moto X 2014 XT1092
Alexjrbr said:
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644
Click to expand...
Click to collapse
Can this solution be used in my case. I have the same problem of the phone booting to recovery on start up...

Struggling to root SM-G780G

Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?

tonyboy_23 said:
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
Click to expand...
Click to collapse
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/

tonyboy_23 said:
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
Click to expand...
Click to collapse
there is only one method that is going to work for you, that method is linked above.
the problem with instructions can be when you don't know what they mean and the way they're written assumes you should.
there are many steps and they are all crucial (like unlocking the bootloader first).
if you don't understand what something means paste it here and ask, people will help you.

bininga59 said:
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
Click to expand...
Click to collapse
Thank you. I have followed the guide to the letter. My screen (in dl mode) is showing OEM bootloader thingy lock is OFF... but I am still getting the 'only official...' error message when trying to flash the boot tar file made in the guide

3mel said:
there is only one method that is going to work for you, that method is linked above.
the problem with instructions can be when you don't know what they mean and the way they're written assumes you should.
there are many steps and they are all crucial (like unlocking the bootloader first).
if you don't understand what something means paste it here and ask, people will help you.
Click to expand...
Click to collapse
Thank you. I feel i understood what I was supposed to do in each step, but i still get the only official... message. The lock is showing as 'OFF' on the DL screen, but it still blocks me.

tonyboy_23 said:
Thank you. I feel i understood what I was supposed to do in each step, but i still get the only official... message. The lock is showing as 'OFF' on the DL screen, but it still blocks me.
Click to expand...
Click to collapse
The switch in developer mode MUST be like this (picture), otherwise you cannot flash or root custom roms, custom kernels, etc.

I've read that sometimes you have to wait a few days for it to show up as unlocked finally. also you can't lock a brand new phone instantly, you've got use it a few days too.

bininga59 said:
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
Click to expand...
Click to collapse
this guide is for SM-G780F, the model is SM-G780G, the guide is for exynos version, i have the snapdragon version but without 5g(SM-G780G), since the chipset is different, i cant see how it works

leokratos17 said:
this guide is for SM-G780F, the model is SM-G780G, the guide is for exynos version, i have the snapdragon version but without 5g(SM-G780G), since the chipset is different, i cant see how it works
Click to expand...
Click to collapse
rooting is pretty universal at the moment barring a couple OEM specifics. pretty much all Samsung phones root the same way.

thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless

leokratos17 said:
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
Click to expand...
Click to collapse
I have the same version, sm g 780g without the 5g (Brazilian version) can you help me to root?

leokratos17 said:
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
Click to expand...
Click to collapse
I also have this s20fe G780G 4g model I'm from Brazil, make a Tutorial help and...

The "OEM unlock" option I missed first but suddenly, after updates of the pre-installed apps and reboots, I got it.
I haven't tried to root as far and directly on front of my vacation.

Hit a wall trying to unlock BL, enabled in dev options and adb into DL mode but LONG PRESS VOL UP is not working! So there is no way to actually unlock BL!??!!?
WTF?