641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever Техника

Что такое Root-права? Root-права (или Root-доступ, или права суперпользователя) — аналог прав администратора на ПК в Windows. Получить можно на любом устройстве под Android (смартфон, планшет).

По умолчанию операционная система не дает пользоваться рут-доступом, чтобы случайно не удалить важный файл. Для опытного пользователя такие права — это возможность более широко использовать свое устройство.

Рассмотрим, как включить права суперпользователя на Андроид.

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Magisk is currently the most popular Android rooting solution and is also the most widely used one as well. SuperSU has enjoyed a monopoly in the world of Android rooting for a significant time period until Magisk made its debut. Magisk has quickly become the preferred choice for those who are looking to root their Android devices. There are many advantages of rooting Android with Magisk and we shall discuss the same in a short while. One of the most important among them is that Magisk also offers several other functionalities such as hiding root from apps that will not work on rooted Android devices.

In this article, we will show you how to install Magisk Zip along with Magisk Manager APK. which will help you manage root access on your Android.

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Rooting an Android is a complex task and not for everyone. Even if you get it right, there is a good chance that something goes wrong down the line. One such issue is that the root access suddenly goes missing. As weird as it may sound, it does happen to a lot of folks. After all, Android is still software and they tend to misbehave for various reasons.

In this guide, I have listed out the possible ways to fix the lost root access issue on Android devices. No matter what rooting solution you use, either SuperSU or Magisk, you can try the below steps.

Check the Root Access

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Before proceeding, let us make sure if you are having issues with root access on your device. The easiest way to do this using the Root Checker app. You can download the app from Google Play Store by clicking below:

Once you have downloaded the app, open it, and click on the ‘VERIFY ROOT’ button on the app’s main page.

Once you have done the above, there are two possible outcomes and we have shown them both below:

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

1. Root Access is fine.

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

2. Issues with Root Access.

If your device has root properly working, you would see the first image as above and if it’s not, you will see the second image.

⚠️ The value that you should set to root varies, depending on which partition on your hard drive you installed your operating system on.

In my case, I cut up my hard drive into 5 parts, and I used parts 3, 4, and 5 for my Ubuntu machine. Part 3 had the operating system, Part 4 had my swap files, and Part 5 had my hard drive data. (If you were in the desktop session already, you can check this using lsblk to see how the files were partitioned and what sizes they were assigned).

I used sdd3 because the partition that held my OS is on the third partition of my drive sdd. This appears to be the missing part which caused me to get brought to initramfs with root not being specified.

If there are other unix/linux/ubuntu specialists there who could give more clarity on what I may not have explained clearly, please feel free to edit this message.

Как проверить наличие root(рут) прав на андроид

Root-права на устройстве с операционной системой андроид могут понадобиться вам для установки каких-либо приложений, которые работают только в этом режиме или для удаления системных приложений. Если вы купили поддержанный смартфон или производили какие-либо действия по получению рут прав, можно легко проверить есть ли root-права на вашем устройстве.

Установка приложения Root Checker из Google Play

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

После нажатия на кнопку Установить приложение будет установлено на вашем андроид устройстве.

Проверка наличия рут прав на андроид

Откройте приложение через список приложений в меню или через главный экран, если на нем был создан ярлык.

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

При первом запуске приложение отобразит окно с условиями его использования. Соглашаемся с этими условиям путем нажатия кнопки Agree.

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Далее вы увидите по центру экрана строку с названием вашего устройства и под ней большую кнопку Verify Root Access. Нажмите на нее и начнется процесс проверки рут прав.

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Как видно на скриншоте выше устройство в данном примере не имеет рут прав, поэтому в сроке результатов проверки отобразилось сообщение : “Sorry! This device does not have proper root access.”

Если ваше устройство имеет рут права, тогда должно появиться сообщение следующего содержания: “Congratulations! This device has root access!”

В завершении статьи хотелось бы напомнить, что при получении root-прав прекращается действие гарантии на андроид-устройство.

Description of problem:
used Fedora LiveUSB Creator
and Fedora-14-Beta-x86_64-Live.iso
to make a bootable USB.

Ordinary boot appears to fail, with keyboard becoming partially unresponsive
(Caps lock unresponsive, Cntl-Alt-Delete works for reboot)

Дополнительно:  Юридические права Rot на планшет Samsung Galaxy Tab и юридические права Robo на смартфон от Samsung следующие

Simple graphics boot has the 3 color progress bar advance most of the way to the right. But then screen blanks with message:

no root device found
Boot has failed, sleeping forever

How do I get troubleshoot this system and get it to boot?

The last kernel to boot successfully on this hardware is:
Linux amd.home 2.6.33.3-85.fc13.x86_64 #1 SMP Thu May 6 18:09:49 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

2010-10-11 19:40:39 UTC

changing the boot options to

root=live:LABEL=FEDORA (from the USB’s UUID)

does not seem to help.

2010-10-11 20:22:57 UTC

Low graphics boot without quiet rhgb

proceeds all the way to

Starting HAL daemon
retrigger failed udev events
Adding udev persistent rules
Enabling BLuetooth devices:
Starting sendmail:
Starting sm-client:
Starting abrt daemon: eth0: no IPv6 routers present

after a pause, the screen goes blank and the keyboard is unresponsive.

2010-10-11 20:25:06 UTC

(In reply to comment #2)

This was using a CD burnt with Fedora-14-Beta-x86_64-Live.iso

2010-10-11 21:12:51 UTC

holding shift down and entering ‘linux0’ at boot also fails.
(Text output scrolls past then screen goes blank and keyboard is unresponsive.)

2010-10-24 04:59:42 UTC

How did you make the usb? In Fedora 13?
Did you use Fedora LiveUSBCreator version 3.9.2.1.fc13 ?

I ask because I think I tried this without success. Then I burned the CD but that didn’t help either.

2010-10-24 05:25:47 UTC

I used liveusb-creator-3.9.2-1.fc12.noarch (note that, for some reason, the version reported by the tool is different:
$ liveusb-creator —version
3.7.3
)

Make sure you specify the right /dev/sdXn device and partition to point to the USB key.

2010-11-04 18:26:05 UTC

I’ve been happy with RedHat/Fedora for many years.

in the absence of advice from experts, I’d recommend:
Plan A: Try the F14 DVD or CD install or live CD.

Plan B: Hold off on F14 for now. Install with F13 which works, and use yum upgrade to keep current until F15 comes out.

Warning: I found the later F13 kernels troublesome for my videocards, so if you have a system which boots before but not after upgrade to 2.6.34 or 2.6.35 kernels, keep the F13original kernel. But 2.6.33 and 2.6.36++ work for me.

Unfortunately rumors are that 2.6.36 won’t be in the F14 updates.

2010-11-04 18:38:03 UTC

2010-11-04 20:47:14 UTC

#10: I was finally able to boot it in low-graphics mode (unrelated issue with my ATI card, I think — but it’s strange because using the opensource ati drivers in Ubuntu don’t give me any problem), and specifying root=/dev/sr0.
It was a little bit difficult to guess, anyway.

2010-11-18 11:54:46 UTC

2010-12-03 10:28:57 UTC

Got the same problem on a new HP laptop so it seems to be hardware independent.

Out of curiosity, is this related to the live-cd (meaning Fedora is stuck with it until that iso is deprecated) or can it be live-usb-creator?

2011-03-03 19:45:57 UTC

Was this problem resolved? I’m seeing this same problem with current (fully updated as of 3rd of March 2011) Fedora 14 running livecd-creator generating f14 livecd image..

2011-03-03 22:12:09 UTC

I did not find a way to boot Fedora 14 successfully.

I am able to boot gfx_test_week_20110221_x86-64.iso but:
only with the low quality graphics ‘vesa’ driver.
on the other hand, I reported in bug 679674 that booting with
‘nomodeset drm.debug=0x04’ results in:

No root device found

No root device found

Dropping to debug shell.

sh: can’t access tty; job control turned off
dracut:/#»

I’ve got the same error with pm-test-day-20110324.iso

2011-04-29 17:34:45 UTC

In my case the problem is buggy virtual cdrom drive firmware, ie. bad «READ TOC» implementation, so udev fails to identify the CD and mount root.

udev version from el6 (udev-147-2.35.el6) works OK, and udev from f14 fails. So clearly something got broken in udev. Earlier versions were able to workaround the issue of buggy cdrom drive.

Patch should be added to udev to workaround the issue.
More info from: https://bugzilla.redhat.com/show_bug.cgi?id=681999

I get «No root device found», «sleeping forever» trying to boot Fedora 14 kernel/initramfs, version 2.6.35.13-91.fc14.x86_64.

Disabled all boot devices at the BIOS level, other than the disk. (Happens to be Intel 82801 SATA RAID Controller.)

Able to boot with Fedora 13 kernel/initramfs, and everything else Fedora 14.

Upgraded from Fedora 13 to Fedora 14 using preupgrade utility.

Any additional info needed?

Fedora End Of Life

2012-08-16 19:15:00 UTC

I have rooted my phone. Now what is Next?

Many people root their devices for the sake of doing it without knowing what are the real output can be done by rooting. Actually rooting means taking the control over your device and making all the aspects control by yourself. You can amend anything as you wish after you rooted your phone. Some are asking what could be done after rooting the phone. They have no idea about rooting. I need to ask them what cannot be done after rooting the Android device, Therefore we intend to show you what can be done after rooting procedure has been completed. Below we have listed some important rooting apps which do not use frequently.  Some apps need to be get paid but It is worth getting them though we have to pay some amount.

Root file explorers

This will allow you to see your all folders on your device, such as valuable data which is normally hidden or protected.

Moving and removing Apps

This means you can move or remove your valuable data, apps or whatever from system apps to data to system. You may do this with a risk attached. Make sure you have enough space on your partitions.

This has some issues and also advantages and you better see whether you have enough space in your SD card. Ideally the SD card should be more than 16GB.

Дополнительно:  Пароль для root в altlinux

You know by now Some devices have Wi-Fi tethering out-of-the-box, example for that is like the Samsung Galaxy S, Therefore this is not such a big deal on them unless otherwise the carrier charges for the feature.

Screen shots & Screen recording

Rooting is needed for screenshots before 4.0-Ice Cream Sandwich devices. And also Most of the pre – lollipop version screen recorders also require rooting.

There are also so many apps that will make a full nandroid backup for your device.

Application/ Network Control

The Xposed framework allows apps with more developed functionality to be installed.

Enable swap file / partition

AlThough rooting is not required for flashing new ROMs, many apps ask for you to root your device so that the work you do is more easier.

CyanogenMod is a very famous Rom that majority of the people put on their devices. It is easy to install it using the ROM Manager application. First you have to do is, install the Clockwork recovery. After that run a backup before you will flash any Roms.

Make sure to check out “From Where can I able to seek stock or custom ROMs for my device” or the XDA forums that will work for the other custom Roms. We know Most devices have a specific or more accurate “Android Development” sub-forum which is the place they are posting about the ROMs.

You had better always do a nandroid backup before you install any Rom or mod for your device. It will reduce the risk you will have to take. Furthermore You may also need to clear all the data and cache memory from your device before installing or upgrading a ROM.

Steps to Install Magisk and Root Android Device

There are two ways to install Magisk on an Android device and we shall see them both in detail below.

Flashing Magisk Zip using TWRP Recovery

Once the device reboots, you should have the Magisk Manager app installed on your device.

Flashing Magisk Patched Boot Image

When the device reboots, go to Magisk Manager and make sure that magisk is properly installed.

These are the two ways by which you can install Magisk on your Android device.

Пошаговая инструкция

Как открыть рут-права на Андроид:

Ниже рассмотрим вопрос: «Root доступ на Андроид – как включить на русском языке разными способами?».

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Со смартфона

Список приложений, предоставляющих Root-права на Android, которые устанавливают на сам гаджет (без подключения к ПК):

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

У каждого приложения свой список моделей гаджетов и версий Android, для которых оно подходит. Перед загрузкой проверяйте, подходит ли программа для вашего устройства.

Самая распространенная программа — Kingo Root (на русском языке). Рассмотрим, как открыть Root права на Android через это приложение.

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Через компьютер

Если интересует, как открыть Root доступ на Android через компьютер, подойдут такие программы (устанавливаются не на смартфон, а на ПК):

Пошаговый план установки (на примере Vroot, остальные приложения — применяются так же).

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Через ADB-терминал (с компьютера)

ADB (Android Debug Bridge, или «отладочный мост») – драйвер для смартфонов, связывающий гаджет с ПК. Разрешает управлять устройством из командной строки.

Способ актуален, если производитель устройства постарался максимально закрыть рут-доступ пользователям.

Что нужно для разблокировки через ADB:

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Как подключить рут-права на Андроид через ADB-терминал?

Универсальных команд для этого нет. Поэтому ищите нужные в инструкции к телефону. Если в бумажной инструкции информации нет, или она утеряна, или нет руководства на русском языке — найдите сведения в Интернете, на сайте производителя смартфона.

Особые случаи

В гаджетах с прошивками MIUI (ставится на гаджеты Xiaomi) и LewaOS (и в некоторых других неоригинальных прошивках) активация рут-прав делается без сторонних приложений. Функция уже встроена в ОС и активируется в настройках.

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Обычно включается в разделе «Безопасность». По умолчанию стоит «Выкл». Ползунок надо перевести на «Вкл», и режим суперпользователя включится.

Если Root-доступ уже не нужен, для отключения удалите файлы:

Затем перезагрузите смартфон.

Другой способ удаления — через приложение, которым открывали доступ. В некоторых программах в настройках есть функция отключения.

Hey, Do you see “Root access missing” message on your rooted android device when you try to open an application that requires root? or If you face “Root Access Possibly Lost” issue while trying to flash a ROM in CWM or TWRP recovery, get backup from device, restore your device? then this guide line for you. We listed all Possible Solutions for you.

Confirm that your Android Device is rooted properly by downloading and installing Root Checker app. If your device rooted properly, then Checker app will display Successfull/Congratulations Messages..If not, try to root again.

Go to “SuperSU”and update SU binary if the app prompts you to update.

If you face “root permission” issue. related to one of  application and it works normally with other applications, then, you might have accidentally denied root “permission” to that  app.

Open SuperSU Application from your menu and go to app’s Settings. Now, Disable app and enable it. Check whether problem is fixed. If not, Try to reroot your android device.

If above solutions didn’t help you. Then try this, Open SuperSU app from menu and go it’s Settings and tap on Re- install. Confirm Reinstalling by tapping Continue.

If your android device have not installed Custom Recovery (CWM or TWRP) then you are able to try this method to solve your problem.

Download and  Chainfire’s latest SuperSU File.

After the extract, go to “Common” Folder and Click it

“Samsung Knox has been detected. This might limit root capabilities and cause annoying popups. Try to disable KNOX.”

If your android Device has installed Custom recovery like CWM or TWRP. then latest version from here and Copy it into device’s SD and Flash it.

Особенности процедуры

Получать доступ можно либо через сам смартфон, либо через компьютер. В обоих случаях придется использовать специальное приложение.

Если хотите знать, как включить рут-права на Андроид, и боитесь не справиться — зря. Процедура простая, активировать Root получится и у неопытного человека.

Дополнительно:  Программа master root

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Что можно сделать со смартфоном, имея рут-права?

Имея полный доступ, пользователь может:

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Solution 3. Reinstall Magisk/SuperSU

If nothing else works out, then this is the last resort. The only option available as of now is to completely remove and re-install the rooting solution you have on your Android device.

Reinstall SuperSU

You can completely and safely remove the SuperSU installation on your Android device by flashing the below zip file via TWRP (or any) custom recovery.

I hope you are already familiar with the process of install SuperSU on your Android device; if you need any help, you can refer the guide here.

If you are planning to re-install Magisk, you do not have to remove it first. You can simply flash the Magisk Zip file via TWRP (or any) custom recovery and you should be good. You can download the latest version of Magisk from the below link:

The above link will also have installation instructions, should you need any help in that area.

Getting to know Magisk

Magisk is a popular Android rooting solution that comes in the form of ZIP file which is used to root Android devices. It was developed by the developer topjohnwu in 2016 as an alternative way to root Android devices other than the famous SuperSU by Chainfire.

The Magisk comes in the form of a zip file that can be flashed via custom recovery such as TWRP in order to achieve root on Android devices. Once you have flashed the Magisk Zip file via TWRP, you can handle the front end activities, including but not limited to manager root access, via an App called Magisk Manager.

Magisk – A Magic Mask to Alter System Systemless-ly

SuperSU is the most popular rooting method for Android by Chainfire, but it lost its popularity after Chainfire sold it to a Chinese company and they stopped the SuperSU development. However, topjohnwu’s started to work on Magisk and it became the most popular rooting method. Magisk popularity is by its massive features.

The main goal of these root methods is to manage which installed apps have root access. Not all apps are made to have access root. System apps like Google, Gmail and others will not have benefits from having root privileges. There are apps which are designed specifically keeping the root in mind.

You can even choose how these apps have the root access either permanently or temporarily. Thus making sure only allow the trusted app to have root access.

All Rooting methods offer very much similar functionality, but Magisk and the way you can use any application without any issues makes it stand out from other root methods. Suppose having SuperSU and want to run a banking app is not possible, unrooting is the only way to use the bank app again.

Every time you want to use the app, it’s not possible to unroot the device. Magisk has a feature that hides the rooting from these apps and no need of unrooting the device by hiding root from your device. Unlike SuperSu it doesn’t modify or alter system partition, which means we are not messing with the system files.

What We Can Do with Magisk and Root?

Magisk a very powerful tool to run modifications (modding Android) without messing with the system. That’s the reason it is referred to as the “systemless” method. Using the Magisk manager you’re going to take advantage of Magisk features.

With the ability to install “modules” from the Magisk manager app we can use handy modifications without the need for root apps. These modules allow you to install different handy modifications. Here are some of the best modules for Magisk.

Few modules which I personally use with Magisk:

Now, I know most of the phones out there have the ability to theme the device, but the substratum is more useful for the stock Android phones. I know most devices support Substratum without root. Phones which are on Android Pie or higher require root to apply the theme. Dolby Atmos is not integrated by every phone manufacturer, by giving root access to the app we can enjoy audio enhancements on our phone.

Not all the kernels of the phones, use the full capacity of the phone. Kernel manager will be able to tune certain parameters or even install custom kernels on the device for improved performance and saving battery life.

So here we go, there are a lot of things we can do with the root access. My examples are just small things that we can do form root access. There is so much more we can do from root access.

Solution 2. Clear the Root Manager App Data

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

This should be able to fix any anomalies that you are having with the root managers.

Последствия использования Root, о которых нужно знать

Получение рут-доступа имеет 3 важных последствия.

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Solution 1. Check the Root Manager App

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Fix Root Issue in SuperSU

Sometimes, when you launch the SuperSU app on your rooted Android device, it will show a popup letting you know that the SuperSu binary needs to be updated. Outdated SuperSU binaries can also be a reason for problematic root functionality on Android devices. Outdated binaries break the root access and it may not grant it for some apps while granting it for other apps. To update the SuperSU binary, simply tap Continue on the pop-up and then select Normal.

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Подготовка к активации Root на Android

Прежде чем разбираться с вопросом: «Root-доступ на Андроид – как включить?»,  устройство надо подготовить.

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Для резервного копирования всей информации из памяти гаджета используйте приложение для резервного копирования. Например:

641770 – Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever

Оцените статью
Master Hi-technology
Добавить комментарий