Hi all!
My device is the Samsung Galaxy Tab S 8.4 (LTE) running Android 5.0.2
I've rooted it successfully using Odin 3.10.6 and CF-Auto-Root-klimtlte-klimtltexx-smt705.tar. SuperSU was installed and Root Checker verified the root.
Then, I downloaded FlashFire and the CyanogenMod for my device from their website.
The CyanogenMod OS was stored on device memory (not an external SD card)
On FlashFire, i selected the option to wipe and then loaded the CyanogenMod file and flashed it.
Everything seemed OK however once Android rebooted I got a message "No Command" which flashed for a second and then I went into "Android System Recovery <3e>."
I don't know what I did wrong!
Any help would be much appreciated.
Many thanks, and Android is fascinating
Related
LG G3 D855, 16Gb UK Model with quickcase
I have earlier put on TWRP, and Cyanogenmod 12.1, and super su, quickcase view etc.
supersu had to be installed via twrp, as the app from playstore would not update the binary
then downloaded xposed 3.1 apk and installed that
now it asked to install xposed so
then downloaded xposed-v74-sdk22-arm-by-romracer-20150911.zip and saved into downloads
booted into twrp recovery, installed it, and rebooted
now it no longer boots, gets stuck at the blue face logo.
I have tried to go back into recovermode,
advanced , terminal and created /data/data/de.robv.android.xposed.installer/conf/disabled
but it is still getting stuck on reboot.
no idea what to do now.
I could consider complete wipe/reflash, but would like to recover this.
any help appreciated.
thanks.
Update:
copied xposed-v75-sdk22-arm.zip to sdcard, and used twrp to install that.
Seems to have fixed the bootloop problem. Now need to get xposed correctly installed.
Not sure why I had downloaded the romracer version.
Hi Guys,
This is my first time working with a custom ROM. I have an old S3 which sucks due to Samsung bloatware. So, I wanted to play and install Cyanogenmod on it.
I have a Rogers Samsung Galaxy S3 (Canada) and the model is SGH-I747M. I was following https://wiki.cyanogenmod.org/w/Install_CM_for_d2att to install the recovery image & Release build (https://download.cyanogenmod.org/?device=d2att&type=snapshot). I am using a Mac.
Steps I followed:
Installed Heimdall Suite on the Mac
Downloaded CM12 build & Google App and transferred it over to my phone's internal storage
Restared in download mode
Transferred recovery image
Restarted in recovery mode
Wiped/Factory settings
Apply Update -> cmbuild.zip file
It tried to install and then gave me a "Install Failed" error. I was then able to re-boot normally and get into the phone.
Any ideas, suggestions on what did I miss and what can I do? Is it ok to install the CM12 release build for my S3? Or do I need to go with CM11 or lower?
Thanks.
Flash twrp via heimdall to the s3. After flashing, boot into twrp and flash cm12.1 and gapps.
audit13 said:
Flash twrp via heimdall to the s3. After flashing, boot into twrp and flash cm12.1 and gapps.
Click to expand...
Click to collapse
Ok, so I tried what you suggested. I am still getting Install failed error.
The error says:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/d2att.zip'
UPDATE:
Fixed the problem by Formatting through TWRP and flashing CM12 & GApps again. Worked . Thanks for the help.
Glad you succeeded!
I have an older Galaxy S3 that I would like to flash Cyangenmod 13 on. It has the new Kernel, so Towelroot doesn't work. I'm planning to use Kingroot, on device (not ideal), as I hope to do this whole process without a pc (not a necessity, but just preference). Assuming this root works, I'm am going to install TWRP via TWRP manager, and then download the Cyangenmod 13 nightly (will I have to install a certain file manager to place the .img file in the root of the phones root or is it simply putting it in the same place as SD Card and Internal storage Work?). After this, I will boot into recovery, create a Nanadroid backup, then flash Cyangenmod. Will this plan work and are there any major flaws? Thank you!!!!
From my experience with the i747m, if you have access to a pc, search and download cf autoroot for your android version and flash with odin to get root. Its been a few months, but kingroot wouldn't work for my canadian sgs3.
Hi people.
I'm in the process of flashing my friend's Samsung Galaxy S4 Mini LTE.
Here's some details:
TWRP version: 2.6.3.0 (The one some dude here made himself)
ROM: cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx
SuperSU installed
Rooted using CM AUTO ROOT
Used Odin 3.09 to install TWRP
Everything is working fine but i'm having an issue flashing GAPPS.
9195 has a Krait 300 - which is an ARM processor so i downloaded the ARM 6.0 Micro package from OpenGapps.
Wiped all partitions, queued up the ROM and GAPPS in TWRP and flashed.
The process goes by fast and smooth, but the phone doesn't boot up after that.
The first time it took 25 or so minutes to boot up and ALL the GAPPS crashed after that.
What should i do?
I tried the following alternatives as well:
Bliss-v6.3-serranoltexx-UNOFFICIAL-20160521-1003
Slim_mini_gapps.BETA.6.0.build.0.x-20160516-2250
benzo-gapps-M-20151011-signed-chroma-r3
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
noppy22 said:
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
Click to expand...
Click to collapse
This worked!
I thought the old TWRP version was the only version compatible with the SGS4Mini.
I'm a Newb sure, but fairly sure this isn't my fault....
Hello, I have spent the past 2 days working on this flash you've stated as well and I can't understand for the life of me what I am doing wrong. You mentioned that TWRP may not have supported the mini but it seems that it does - odin just isn't installing it right? I am hoping people on here have already hashed this out on both ODIN and TWRP for this device and after spending 24 hours figuring this out i'm wondering if it's just some stupid thing i'm doing wrong. I've put the full stuff below which you may largely be able to ignore but what i need to figure out is how to install TWRP 3.0 or higher on my device, and how to keep ODIN from crashing. Can you help?
1. where I started and my goal:
My homestay mother in New Zealand who works for the tech firm Datacom provided me with a Galaxy S4 mini (GT-I9195 spark edition) that she had left over because she got a new phone for her work. I had a galaxy note 2 running default controls due to its setup on KNOXED up verizon, so i thought this was a good opportunity to switch to cyanogen since i've used the service before (someone else went through all this trouble for me and I am eternally grateful). So I am trying to install Cyanogen mod 13 with GAPPS package nano on to it.
2. The file repretoires and guides I used:
TWRP 2.8.1 (originally) and it's accompanied manager
Trying to upgrade to TWRP 3.0.2.0 or 3.1.0
GAPPS arm 6.0 mini/nano/pico (I've tried all three)
Odin 3.12.3 with requisite drivers (shows blue on status bar)
Default Bootloader for Android devices
CMD ADB systems with requisite drivers
CyanogenMod 13 (cm-13.0-20160820-ZNH5YAO0J7) (currently installed and working san-GAPPs)
3. What I've done Start to current:
starting with the phone locked, unrooted, and factory resets not working (company KNOX settings)
Installed Kingroot, superSU, RootChecker, TWRP manager and official ap, P-uninstall = Obtained Root
Attained root on the phone, deleted all KNOX and KGNT protection. = obtained unlocked sim/recovery loader
Installed TWRP 2.8.6 (any more recent installs failed as I will explain below in problems) Attempted to flash it = read success
Failed to boot into TWRP recovery - provided default recovery instead.
downloaded and installed ODIN. Used default boot loader and attempted to install TWRP directly through ODIN = Works
placed CM13 zip file and GAPPS 6.0 - ARMS Nano on SD card.
Created recovery on SD card
Wiped cash, devalk cache, and internal storage = clean partition
Installed BOTH CM13 and GAPPs 6.0 as zip files using TWRP 2.8.6 = worked
rebooted system into new OS
OS got stuck in boot cycle due to GAPPs package. after some googling i found out that Gapps requires TWRP 3.02 or higher (but i couldn't get those to download onto my phone at all. [here enlies the ROOT of my problem - you're allowed to kill me now]
Returned to TWRP and installed JUST CM13 on the device = works great! just no GAPPs! and no ability to download apps
Used Odin, TWRP manager, the official TWRP app, and CMD ADB sideloader to attempt to install all 3.0 and higher TWRP files = all of them failed
now I cannot access a bootloader at all, but can access my OS just fine. It refuses to accept any TWRP bootloaders but without them i cannot install GAPPS
4. Where I am Currently & Problems I'm running in to:
Right now CM13 is on and stable for my device. My Recovery loader is refusing to come up AT ALL. Attempting to install both .img and .tar files of TWRP read as succeeding in the apps but don't come up.
ODIN can't load anything on the device. Either it keeps freezing and crashing any time I touch it or when it does go through the device still can't bring up TWRP. Even when flashing 2.8.6 which originally worked as a recovery file it fails as well. I can't get back to TWRP working at all.
ADB sideloading just results in <waiting for device>. I am clearly using "fastboot" instead of ADB during the point in which i am flashing the recovery file on to it.
5. What I need Help with:
I need to know why TWRP is freezing any time i attempt to install it regardless of version and how to get it properly installed
if someone could point me to a reason odin freezes regardless of what options I tick on or off, file I upload, or whatever i'd love to know
I see 2 ways out of my predicament and i'm not sure which one I should spend more time on: 1) get TWRP 2.8.6 to work again and then find an older GAPP partition to load on to it. or 2) Get TWRP 3.0 or greater to work on it, and then use current GAPP packages. which would be best?
Hi all,
While I have successfully installed Lineage 14.1 and the GApps 7.1 on my Tab Pro 12.2, I can't get it to install Lineage 17.1. I had issues getting 14.1 onto it until I loaded a new bootloader file through Odin (BL_T900XARBOJ1), but I can't seem to find a bootloader that will let me install Lineage 17.1. Does anyone have any suggestions?
Similar problem
-- sorry, wrong device, please disregard. I can't seem to find a delete button. Newby passing through.--
I have not previously installed custom ROMs on my devices. Now I am also trying to install Lineage 17.1 on my Galaxy Tab Pro 12.2 and thus far have been unable. Maybe your experience is similar to mine:
I used ODIN to flash the latest TWRP to the boot loader and booted to recovery (so Samsung system boot would not replace TWRP with stock recovery) and TWRP recovery is stable. In TWRP, I installed SuperSU from a zip file on the extSD. After booting into the stock system, I was prompted to finish rooting, which I did using TWRP. Once I was able to reliably boot into recovery or normally (stock system), I booted to recovery and made a backup of my stock image. I have reliably flashed Samsung stock image, which boots to the initial setup process, and restored by backed up image, which boots to the previously configured state.
At this point I downloaded the Lineage 17.1 image zip file onto the extSD card and tried flashing it from recovery. While unzipping the image, the recovery screen shows a couple of error messages, along the lines of image is 'for device v1awifi but this device is .' and flashing fails. I believe at this point rebooting hangs with the Samsung logo animation, but I have been able to boot recovery and restore my previous rooted Samsung stock state. Custom ROM Manager confirms my device Codename is v1awifi.
Is this what you experienced? If not, how is your experience different? Can you describe your approach, what steps you've taken, and where the process does not go as expected?
ScrooLoose said:
Hi all,
While I have successfully installed Lineage 14.1 and the GApps 7.1 on my Tab Pro 12.2, I can't get it to install Lineage 17.1. I had issues getting 14.1 onto it until I loaded a new bootloader file through Odin (BL_T900XARBOJ1), but I can't seem to find a bootloader that will let me install Lineage 17.1. Does anyone have any suggestions?
Click to expand...
Click to collapse
where did you find 17.1 for tab pro 12.2?
ScrooLoose said:
Hi all,
While I have successfully installed Lineage 14.1 and the GApps 7.1 on my Tab Pro 12.2, I can't get it to install Lineage 17.1. I had issues getting 14.1 onto it until I loaded a new bootloader file through Odin (BL_T900XARBOJ1), but I can't seem to find a bootloader that will let me install Lineage 17.1. Does anyone have any suggestions?
Click to expand...
Click to collapse
So you are on TWRP 3.4.0-0?
Although I own a P900 I had problems flashing 17.1 before updating to 3.4.0-0.
And for 17.1 I used BiTGapps instead of opengapps for the last didn't like it.
Does anyone know how to modify this note 12.2 LOS 17 zip so it can be flashed on tab 12.2? https://forum.xda-developers.com/t/...l-lineage-17-1-android-10-q-20201221.4152395/
I was able to get it installed on my Tab pro 12.2 T900. It gets stuck on the bootup lineage logo screen. I guess android 10 on this device is too good to be true.
Dusterrr said:
I was able to get it installed on my Tab pro 12.2 T900. It gets stuck on the bootup lineage logo screen. I guess android 10 on this device is too good to be true.
Click to expand...
Click to collapse
I had the same issue. You need to flash 17.1 over 14.1.
rojorojorojo said:
I had the same issue. You need to flash 17.1 over 14.1.
Click to expand...
Click to collapse
I tried this and it isn't working. Any suggestions? Can you help me out? Nevermind, its working this time! I tried many times, but the final time I didn't clear cache and it worked .
NVM not working again...
I clean flashed lollipop with odin, then twrp, then lineageos14.1, configure it, and dirty flashed 17.1, and at the moment it's working. No root installed.