I have a Samsung Galaxy Tab S2 stuck on Android 5.0.2. I wanted to upgrade the software to LineageOS. There is a lot of information out there, but nothing that can help me. A few things first that I need to share. I'm using a Mac. I once unlocked my device and Knox is now void, so it must be unlocked. I can't tell if the bootloader is unlocked. I tried to check using an app, but came back with an error of "Sorry! root access is not properly installed on this device". The tablet is in developer mode, there is no OEM mode or anything like that, and USB debugging is turned on. I have tried several things using Terminal but they didn't work with homebrew and ADB services. These are installed on my Mac. I got as far as trying to add fastboot devices, and it was denied on the terminal, but that probably makes sense if the bootloader is locked. Most instructions imply that you know what to do and don't explain much. Can anyone please assist with step-by-step instructions so I can complete the process of installing LineageOS?

I had a tablet (Alcatel U3A_7_WIFI running Android Go) working alright. In order to root it, first I made (what I thought was) a full backup with mtkclient : python mtk.py rl ./backup After the rooting went wrong, I tried to flash a stock ROM (with SP Flash tool). Found many variants for that model and they all work perfectly while doing black and white output. But as soon as colors are involved I get this stripe pattern (and bluish colors): The battery indicator shown when charging, has the same color problem, so I think it has to be something happening at a very early stage. Does anybody know how to solve it? Or what could be wrong? I tried flashing individual partitions with mtkclient from the backup I had (no way to flash the whole thing back, as far as I know). But half of the time this bricks the tablet (just BROM mode) and the other half nothing changes. Colors are still the same, bluish and striped.

I recently downloaded [this ROM](http://forum.xda-developers.com/showthread.php?t=2480246) for my Allview P5 (Allview P5 is the equivalent of Gionee GN700W/FLY IQ441/QMobile Noir A8). It`s called Primonex ROM and is made for the Gionee version of the phone. - Firstly, I tried to install it as it is but it got stuck at the boot screen. - After some research I found out that it could be a problem with the boot.img file and I don't know how to extract or edit it... Can someone tell me how to do it?

I have an extra phone, i.e., Samsung SGH-i997, at home. A while back, I installed **Clockwork Recovery** and installed CyanogenMod ROM on it. Then somehow, out of stupidity or accident, it went back into recovery mode, and everything on the phone was wiped. It even deleted Clockwork Recovery, and I guess that even the factory firmware isn't there anymore. Now every time I turn on the phone, it automatically goes to the default recovery mode with 4 options - reboot system now - apply update from SD card - wipe data factory reset - wipe cache partition I have tried switching it to **download mode** and connecting it with my laptop, but the drivers are not recognized. I also tried installing kies, which I thought would help with the driver issue, but it didn't. I guess there isn't any firmware inside that the driver would connect to. Now the only way left to somehow copy something to the phone is via an SD card. I tried copying several different Android firmware and mods to the SD card, but I think the default recovery mode doesn't use the external SD card but the phone's internal SD storage, which i why everybody is using Clockwork Recovery instead of default. I am really tired of searching for a solution to this issue. If anyone out there has done something similar or can somehow show me how to go into the shell, I might be able to find my way. Thanks in advance.

Just got a GALAXY A71 sm-a715w. Its in QDLoader Mode 9008. How do I flash it? Where can I get (Loader files) etc.. I haven't found much info, or guides on the subject. Is there someone familiar wit the process

I have a Motorola ROKR E6, which is currently running MontaVista Linux. I was thinking of installing Android on it to make it usable again (and also to clear a lock code previously set on it that I completely forgot). I found how to access the bootloader, and now I'm installing the required drivers and software. But if I flash Android on it, it may brick the phone, so I'm going to be very careful while flashing Android. Do you think that installing Android on a non-Android phone like this old Motorola phone is possible?

I want to have a adbd in debug mode on my Pixel 6a. The easiest way to get it would be to flash a userdebug image as suggested by [f.e. official guides](https://source.android.com/docs/setup/create/new-device#build-variants) . Using the flash.android.com tool does not work because it does not include userdebug builds (anymore?). Is there any place where one can find pre-built userdebug builds? Is there any other way except for building a full AOSP image myself?

Are custom ROMs different for different makes of handsets? Or is there only one CyanogenMod for, say, Android 2.2? Can someone please elaborate why a 'ROM' is called as such? I mean, does it have any similarity to Read-Only Memory?

# Current status ## Device issue I have a Asus Nexus 7, I can't flash anything with fastbootbecause all flash procedures I have read need to unlock (using fastboot oem unlock) or mount /cache partition and for some reason when I try something I get freezed mounting /cache partition. More details about this please read: https://android.stackexchange.com/questions/89892/nexus-7-error-failed-to-mount-cache , which still **UNSOLVED**. ## Asus support I asked to Asus Support Service (in USA and Mexico) and they answer that this device do not have support. # My claim So I want to try to flash using a tool like Odin. Maybe it can solve my problem (now I have an expensive *paperweight*).

So, I'm making a little batch script to be able to automate the whole process of flashing new roms for my Galaxy S6. Since its screen is broke, I have to do everithing manually from the adb shell, and since i'm having so many troubles with all the roms, I decided to make a little script to make my life easier. This is what I got so far: @echo off setlocal enabledelayedexpansion REM Factory settings echo Formatting to Factory Defaults adb reboot recovery adb wait-for-usb-recovery adb shell twrp wipe cache adb shell twrp wipe dalvik adb shell twrp wipe data adb shell umount /sdcard adb shell umount /sdcard adb shell umount /data adb shell umount /data adb shell mke2fs -t ext4 /dev/block/platform/15570000.ufs/by-name/USERDATA adb shell reboot recovery adb wait-for-usb-recovery REM Rom Flashing Section set argCount=0 for %%x in (%*) do ( set /A argCount+=1 set "argVec[!argCount!]=%%~x" ) echo Wiping /system adb shell twrp wipe /system for /L %%i in (1,1,%argCount%) do ( adb wait-for-usb-recovery echo Flashing "!argVec[%%i]!" adb shell twrp sideload adb wait-for-usb-sideload adb sideload "!argVec[%%i]!" echo "!argVec[%%i]!" flashed echo. ) REM Debug enable adb wait-for-usb-recovery echo Enabling USB Debugging adb shell mount system adb shell "echo '' >> /system/system/build.prop" adb shell "echo '# Enable ADB' >> /system/system/build.prop" adb shell "echo 'persist.service.adb.enable=1' >> /system/system/build.prop" adb shell "echo 'persist.service.debuggable=1' >> /system/system/build.prop" adb shell "echo 'persist.sys.usb.config=mtp,adb' >> /system/system/build.prop" adb push C:\Users\ffpp2\.android\adbkey.pub /data/misc/adb/adb_keys REM Booting system echo Rebooting into system... adb shell reboot echo waiting for phone to boot up adb wait-for-usb-device echo Launch scrcpy "D:\Users\ffpp2\Documents\Celus\zeroflte\scrcpy-win64-v1.25\scrcpy.exe" Now, I want to be able to evaluate every adb shell ... return code, so if anything happens mid way I can stop execution and I can get to fix what didn't work. I havent been able to find anything regarding if adb shell forwards error codes back to the windows command prompt. Take a look at this: D:\Users\ffpp2\Documents\Celus\zeroflte>adb shell mount /system mount: mounting /dev/block/sda15 on /system failed: Device or resource busy D:\Users\ffpp2\Documents\Celus\zeroflte>echo %errorlevel% 0 D:\Users\ffpp2\Documents\Celus\zeroflte>adb shell ~ # mount /system mount: mounting /dev/block/sda15 on /system failed: Device or resource busy ~ # echo $? 255 ~ # exit D:\Users\ffpp2\Documents\Celus\zeroflte>adb shell cat asd cat: can't open 'asd': No such file or directory D:\Users\ffpp2\Documents\Celus\zeroflte>echo %errorlevel% 0 D:\Users\ffpp2\Documents\Celus\zeroflte>adb shell ~ # cat asd cat: can't open 'asd': No such file or directory ~ # echo $? 1 ~ # As you can see, no error code was returned. And, in theory, it should be returned, since I didnt used the -x argument: Android Debug Bridge version 1.0.41 Version 34.0.0-9570255 Installed as C:\Program Files (x86)\ADB and Fastboot++\adb.exe ... shell: shell [-e ESCAPE] [-n] [-Tt] [-x] [COMMAND...] run remote shell command (interactive shell if no command given) -e: choose escape character, or "none"; default '~' -n: don't read from stdin -T: disable pty allocation -t: allocate a pty if on a tty (-tt: force pty allocation) -x: disable remote exit codes and stdout/stderr separation emu COMMAND run emulator console command ... Has TWRP anything to do with this?

I have Xiaomi Redmi Note 8T (ginkgo). I was installing a new ROM, wiped the device, and from TWRP, flashed the recommended recovery from the CrDroid device page - SHRP (SkyHawk Recovery Project). After flashing, it said it was going to reboot to recovery, but it didn't, and it seems to be stuck in a loop. - Holding Power and Volume down - Vibrates and just flashes. - Holding Power and Volume down - Orange Fastboot logo flashes on and off. - When the buttons are released, it goes blank, i.e., the phone stays turned off. - If connected by USB to a laptop, it keeps flashing every second. - adb fastboot does not recognize the device: - using adb devices = just says: List of devices attached - adb reboot bootloader = error: no devices / emulators found - fastboot reboot = Any way out of this?

Are there any technical or others reasons why Android is still a firmware and not an OS which can be just installed without a lot of hassle? Why there is no universal image which could detect appropriate drivers (kernel modules), partition NAND in some standard way and configure boot loader to boot updated OS version? What stops Google from making a real (less firmware-like) OS (an OS for small ARM, x86 etc. devices)?

I have a Samsung Galaxy S4 Mini (GT-I9195) and successfully installed CyanogenMod 13 with the CM 13 Recovery on it. Now I am stuck with the installation of GApps by means of TWRP. I have tried to follow this tutorial to install TWRP (3.0.1 or 2.8.7): 1) App Install Method: it tells me that something went wrong and it does not boot the recovery, indeed. What seems wired to me is that when I have to choose an image it shows me the device code **serranolteusc** and **serranoveltexx** for my S4 Mini rather than **serranoltexx**, like on the website of CM 13. Is this normal? (I even tried Flashify instead of the TWRP manager, but it did not function!) 2) Since I am on Linux and have no Windows, I cannot use the Odin method. But I tried Heimdall via heimdall flash --RECOVERY twrp.img --no-reboot to no avail. 3) I tried the dd Install Method via dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery, but it still does not boot into recovery mode. Is it possible that there is an issue with the path in of=/dev/block/platform/msm_sdcc.1/by-name/recovery? Is it possible that there is no TWRP for **serranoltexx** available?

I am trying to fix my Huawei P30 (Android 10) which gets stuck in recovery mode. I tried to fix it by using eRecovery but I get the error "Get Package info failed". Around the internet, I was told to flash a new ROM to solve this problem, but there is no tutorial for flashing stock ROMs for Huawei P30 on the internet. My Huawei P30 does not have an SD Card slot meaning I can't use the method of adding update.app to /dload folder on an SD card. I also cannot use ADB fastboot because the Huawei on Android 10 does not have the image files required (boot.img, recovery.img, etc.) Instead, it has a myriad of images like Super.img, Ramdisk.img, erocovery.img, etc. I don't know which ones to select because I am unable to find a tutorial on the internet that tells me which files to select. I also cannot use the SP Flash Tool because Android 10 stock ROMs do not have scatter file XML or txt (it has update.app) I am unable to use SigmaKey as well because of the "SmartCard resource manager not running" error (I'm on Windows 10) I have exhausted many options with no luck, please help me.

Before we start, just want to make it clear that I am aware how easy it is to brick this device, and have decided to go ahead rooting and installing a custom ROM anyway. My goal currently is to use twrp to install magisk and root the phone, but I cannot get the thing to boot into twrp. In case it matters, I'm running Miui 12.0.8.0 Global with Android 10 (4/01/21 patch) on a Global phone. My device is a 6GB/64GB variant with plenty of storage available. I've grabbed the required twrp image from the link in the XDA developers guide (https://forum.xda-developers.com/t/guide-begonia-unlock-bootloader-flash-twrp-and-root-proper.3995919/) as well as a vbmeta image for a Redmi Note 8 because I couldn't find one for the pro variant. I wouldn't expect that's an issue because they run the same OS, but because mine has a mediatek SOC I won't rule it out; if someone has the right vbmeta for me, it would be appreciated. My procedure is as follows: - Boot phone into fastboot, open minimal fastboot/adb from the guide. - Make sure twrp.img and vbmeta.img are in the fastboot directory - fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img - fastboot erase recovery - fastboot flash recovery twrp.img - Hold power and volume up to try to boot recovery. At this point, as long as I keep holding power+vol up the phone will make it to the "REDMI" splash screen, show me the unlocked bootloader icon, and power off. A few seconds later, it will try again to the same result. This will loop indefinitely until I stop holding volume up, at which point it happily boots into Miui; I've let it loop 5 times to be sure. If I hold just vol up (no power) once the phone turns on, like the guide says, it will pass the splash screen and simply shut off. I've tried multiple twrp and vbmeta images to the same result. The next thing to try was to boot directly to the image. I erased recovery, flashed vbmeta, and ran 'fastboot boot twrp.img." The phone hung on the fastboot screen for about 90 seconds before shutting off, and frustratingly then rebooting into *Miui* like nothing happened. If I try to boot to recovery after successfully booting Miui, it works, but I get the stock Xiaomi recovery, which will not help me root my phone. I'm running out of ideas on how to get this thing into the custom recovery. Still a little suspicious it's an AVB related issue, or some form of anti-rollback protection kicking in. Anyone here got any better ideas?

My device has terrible adb support. Can I install a ROM without using adb?

(UPDATE: The accepted answer has since been patched. 12-16-2021) I have a Gabb Wireless which is an Android that is programmed to be "dumb". By "dumb", I mean it only has core apps such as Settings, Phone, Messaging, etc. I like it because it is not additive to where I can't focus on my school. It has some major drawbacks though. To keep kids from messing up the restrictions, they pretty much bricked the phone. I can't flash, ADB*, install apps**, or unlock the bootloader*** the way other sites say to do. All I want to do is host a web server and customize the OS a bit. I have contacted the distributor and of course, they would not reveal anything. Stars: 1. The original way to allow USB debugging/Developer mode is gone. 2. The store was removed and you can't install raw APKs. 3. When I boot into the Bootloader, the screen is blank with "=> FASTBOOT mode..." at the bottom. Overall, I am disappointed with the extremes which the company took. I have gotten them to admit that the device *is* hackable. Of course, any device is hackable so I did not get much from that. Any ideas?

I was experimenting (more specifically, trying to flash ROMs) with my Samsung Galaxy J1 Ace (rooted). It was all going well until I tried flashing the TWRP recovery mode. I followed all the steps mentioned on various XDA forums, but a red exclamation mark appears at the top left of the screen when I try to turn it on along with the Samsung logo, and the phone just hangs. When I go to the Download mode, it shows "MDM Download Block: 0". I tried flashing, using ODIN, other versions of the TWRP for my phone model, but the same error persists. Is my phone soft-bricked? How do I fix it? I am trying to restore the original stock Samsung firmware now.

I have a ZTE nubia Red Magic 7 on Android 13. I accidentally had to erase all checked in QFIL when trying to bring it back from soft bricked. That's irrelevant now though as erase all did just that. - 0 partitions. - 0 GPT headers. I have backups from before in QFIL. However, this is not working either as they are all snippets for QFIL to use. I have a full partition list from before d and a few readings from the partition manager as well, user and system I believe, maybe different, can't read it to tell. no help on XDA or the manufacturer or Qualcomm or online communities. How can I bring this phone back from death?

I've been trying to root my xperia ray device by following the instruction given in this post. It doesn't seem to work properly for me. Whenever I try to flash with 4.1.A.0.562 kernel it says that my device USB debugging is off even when I've ticked it. Also I've put it onto MSC mode. When I try to put it on flash mode both kernel.sin & loader.sin is grayed out. Below is the log what I get. 02/016/2014 02:16:42 - INFO - <- This level is successfully initialized 02/016/2014 02:16:42 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00 02/016/2014 02:16:48 - INFO - Device disconnected 02/016/2014 02:16:50 - INFO - Selected ST18 / 4.1.A.0.562 / Kernel 02/016/2014 02:16:50 - INFO - Preparing files for flashing 02/016/2014 02:16:50 - INFO - Please connect your device into flashmode. 02/017/2014 02:17:28 - INFO - Device connected with USB debugging off 02/017/2014 02:17:28 - INFO - For 2011 devices line, be sure you are not in MTP mode 02/017/2014 02:17:44 - INFO - Device disconnected 02/017/2014 02:17:47 - INFO - Device connected with USB debugging on 02/017/2014 02:17:47 - INFO - Connected device : SonyEricson Xperia Ray 02/017/2014 02:17:48 - INFO - Installed version of busybox : BusyBox v1.18.5 (2011-07-18 07:43:28 PDT) multi-call binary. 02/017/2014 02:17:48 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Build number : 4.1.B.0.587 02/018/2014 02:18:14 - INFO - Device disconnected 02/018/2014 02:18:31 - INFO - Device connected in flash mode 02/018/2014 02:18:31 - INFO - Opening device for R/W 02/018/2014 02:18:31 - INFO - Reading device information 02/018/2014 02:18:32 - INFO - Phone ready for flashmode operations. 02/018/2014 02:18:32 - INFO - Current device : ST18i - CB511VGBZ7 - 1252-6163_R1I - 1248-9545_4.1.A.0.562 - WORLD-i_4.1.B.0.587 02/018/2014 02:18:32 - INFO - Start Flashing 02/018/2014 02:18:32 - INFO - Processing loader.sin 02/018/2014 02:18:32 - INFO - Checking header 02/018/2014 02:18:32 - INFO - Flashing data 02/018/2014 02:18:37 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Boot version : R9A029 / Bootloader status : ROOTABLE 02/018/2014 02:18:37 - INFO - Disabling final data verification check 02/018/2014 02:18:37 - INFO - Processing kernel.sin 02/018/2014 02:18:37 - INFO - Checking header 02/018/2014 02:18:37 - INFO - Flashing data 02/018/2014 02:18:39 - INFO - Ending flash session 02/018/2014 02:18:39 - INFO - Flashing finished. 02/018/2014 02:18:39 - INFO - Please unplug and start your phone 02/018/2014 02:18:39 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings 02/018/2014 02:18:39 - INFO - Device connected in flash mode 02/018/2014 02:18:55 - INFO - Device disconnected And I've attached a sample screen of what I get. Please advise me what to do.. I'm totally lost... even the log says flashing finished, my current kernel build is in 4.1.A.0.587 but not 4.1.A.0.562. Model number: ST18! , Android Version: 4.0.4 , Build number: 4.1.B.0.587