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.
Related
Okay so in twrp i installed a custom rom for 4.4.2(cyan fox) and the setup wizard would crash immediately so I had the brilliant idea to wipe EVERYTHING in my phone, not realizing that also removed any roms and backups I had So now the phone doesnt go past the samsung logo, and I need to get a clean 4.3 on my phone and I can't use old firmwares in odin.
I've been trying to find a 4.3 firmware to use in odin and I can't seem to find anything. Or an alternative solution would be to help me find a way to transfer files to my phone in recovery mode(which is an issue since i cant get adb to recognize my device or get usb-otg to enable itself in twrp)
if anyone can help that's be swell
I take it that you are on the i747 (AT&T) and not one the i747M Canadian versions. If so, this thread, AT&T I747 UCUEMJB Stock Restore, may be of use to you. That is, it may be of use if you can load the zip file on your external SD card from your pc and then flash from recovery.
My sister has a Sprint GS3, SPH-L710 and recently installed the 4.4.2 OTA (L710VPUDND8) not realizing that her apps will no longer be allowed to write/backup to her External SD card after the OTA (thanks google ). Anyway, I told her I could probably fix that problem by rooting it and making a few tweaks to restore the ability to write to the external SD card. Does rooting this phone require unlocking the bootloader (can you even unlock the bootloader anymore?) or can I get root without unlocking the bootloader? If so, what is the best/simplest method to use? She doesn't plan to be installing any custom ROMs, won't need a custom recovery and I'd like to root it without wiping her phone if possible. Thanks
This phone doesn't have a locked bootloader, to root just odin the tar for Philz recovery, boot directly into the recovery (uncheck auto reboot in odin, pull battery then boot to recovery) then flash the su.zip in recovery... Then boot the phone and you're rooted... Easy as pie
flastnoles11 said:
This phone doesn't have a locked bootloader, to root just odin the tar for Philz recovery, boot directly into the recovery (uncheck auto reboot in odin, pull battery then boot to recovery) then flash the su.zip in recovery... Then boot the phone and you're rooted... Easy as pie
Click to expand...
Click to collapse
Thank you. Sry for my ignorance, obviously I'm not very familiar with the GS3. Can you direct me to step by step instructions? And will I be able to root her phone without wiping it? I want to keep this a simple as possible and not have to mess with restoring everything on her phone.
I found this on another thread: http://forum.xda-developers.com/showpost.php?p=52610162&postcount=2. Will this procedure work?
Thanks again
It's worked for some people.
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 3/20/2014 and TWRP v2.7.0.0.
I can verify that the method in post #3 above did work. However, after reboot, SuperSU sent a message that it had stopped working. I checked and it was installed. I went and updated SuperSU to the latest version (v1.94) via the market. I then went to SuperSU settings and installed it into the system. I now had root access and SuperSU was running properly. I then installed NextApp SDFix from the market and enabled writing to the external sd card. All is good now, her phone has root access and her apps can now write to the external SD Card. Thanks to all for your help.
I do not have access to any PC, whether its windows, Linux or mac. All I have is my chromebook. With that said, is there any way to install the stock recovery back to my nexus device without the use of a pc? I currently have TWRP installed, but just got prompted to update to 6.0, and would like to install it. Any suggestions?
timrock said:
I do not have access to any PC, whether its windows, Linux or mac. All I have is my chromebook. With that said, is there any way to install the stock recovery back to my nexus device without the use of a pc? I currently have TWRP installed, but just got prompted to update to 6.0, and would like to install it. Any suggestions?
Click to expand...
Click to collapse
You'll need a copy of the stock recovery image, which you should be able to pull from a factory image.
Once you have that, you should be able to flash it from within TWRP itself (be careful - if you do this, once you exit TWRP, you'll only have the stock recovery until TWRP is re-flashed), or you can use the flashify app if you are rooted.
There are some things to consider though - are you rooted and/or have made any modifications to the /system partitiion? If so, an OTA will likely fail even if the stock recovery is re-installed. If you're rooted, I'd say just wait patiently on a stock (or near-stock) rooted flashable ROM, and upgrade that way by just flashing in TWRP. I believe there are 1 or 2 options for this already in the forums here, and I'm sure more will be coming soon, along with updates to the many custom ROMS out there.
If you do successfully flash stock recovery and successfully accept/install the 6.0 OTA, you'll eventually need access to a PC with fastboot to get TWRP back and/or root the device again, so that's also a consideration for many users.
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?
I got a galaxy tab 3 (sm-t217s) given to me and had a wild hair to root it so i natually looked up some auto root methods after towelroot didnt work and was pointed to Kingroot. Never used it before and not sure if im regretting it yet or not. I obviously have root access because i can install and use root only apps but i tried downloading supersu (before realizing that kingroot also installs its own super user app) but it wouldnt successfully update the binaries. Also there seems to be no custom recovery options availablefor me to directly install from the device, all have tobe done via Odin. My big main question is would i be fine to use Flashify or Rashr to flash a custom rom or a custom recovery file i downloaded?
Yeah You can Use flashify Or Download TWRP Manager From Playstore and select Samsung Tab 3 lteltmo And Then install it ..it'll install successfully And you can use The custom ROMs to flash it via TWRP..
majorkid said:
Yeah You can Use flashify Or Download TWRP Manager From Playstore and select Samsung Tab 3 lteltmo And Then install it ..it'll install successfully And you can use The custom ROMs to flash it via TWRP..
Click to expand...
Click to collapse
Sweet I'll try it out. I kinda figured it would work but better safe than slaving on Odin later reflashing stock firmware
Please repot your sucess..
It works or at least did for me. With the kingo su thing that came with it I just installed titanium backup and uninstalled the kingosu and then installed supersu via store and/or flashing n custom recovery if I already flashed it using flashfire/twrp/flashify.