Hello ppl. So, I was playing with my old phone, Sprint Samsung Galaxy Note II, (it's always a good idea to torture old phones instead of the new ones, right?) and I've done a lot of stuff with it, but for a long time, nothing was happening. So, this is the list of what I did with the phone:
0. I had my original OS rooted, then unrooted it, and I was said to use twrp, if I'm not wrong (can look up, but it will take time).
1. Rooted it. Knox disabled root. (I had the latest, NC2, update)
2. Tried to flash the older OS. It wouldn't. I guess because of Knox.
3. As I was trying to flash older OS, I kind of lost the OS, and had no OS at all. No problem, I thought. I'd just download and flash several other versions of OS, and eventually I'll find one that'll be working
4. It appeared to be the latest, NC2.
5. Back to root. Until restart.
6. Whenever I root, I try to install cwm with ROM Manager. Upon restart, the recovery is <3e>. Not <2e> or cwm. Not even twrp that I had.
7. So now I'm here, and I just don't know what to do. I remember that I somehow disabled the knox, and I'm sure just by updating the SuperSU (or its binaries? But I can't find any in the market), but this CF-AutoRoot installs latest SuperSU, and so there is nothing to update.
Then I finally figured out what to do. I should warn you, it took me 3 days to figure out what to do to install CWM, so if you have any kind of a problem with installing it, just use this tutorial, I guess. Even though it covers just the basics.
1. In SuperSU, choose "Uninstall to install other Superuser application" or similar.
2. It was necessary for my phone to actually update binaries
3. As the Knox was disabled by updating the binaries, I could now use ROM Manager to install Clockworkmod Recovery (Yay!!!)
4. Download the Cyanogenmod ROM, either through ROM Manager or the web site (choose most stable and recent. Otherwise, who knows what problems it might have) and install it:
4.1 In Clockworkmod (CWM, cwm) (if you still haven't copied the Cyanogenmod (CM, cm) and Google Apps to your external SD, please do that. Just restart the phone and copy it from your computer. Download from the web site) (Vol Up, Home, Power from the phone turned off) just choose the right update and press to install. Then do the same for Google Apps.
4.2 In ROM Manager, just choose the CM and don't forget to install Google Apps.
5. When my phone actually installed Cyanogenmod, it loaded forever. As I was sleepy, I don't actually remember what I did, but I reinstalled the ROM several times, and finally, it worked.
6. Now I'm enjoying my old phone that uses Cyanogenmod.
Related
OK, I know this has been asked and asked again, but I have been reading and digging and googling for several days now, and cannot find a solution.
I've got a JB S3 At&t, and wanted to root it, so after reading for a few weeks, I got the "Samsung_Galaxy_S3_ToolKit_v7.0", donated, and got 7.2 (newest version). I flashed with the toolkit to get an unsecured boot image, with SuperSU 1.04, busybox, and TWRP .
Root happened fine. The phone booted, and when I went to open SuperSU (the icon was in my apps), it asked to update the binaries. I said yes, it failed, and the app opened anyway to allow me to access the options. Triangle away worked fine.
The update binaries thing was bugging me, so I updated to SuperSU 1.10 via google store, and the same thing happened, but now I could not access the program after the binary update failed. It still works (triangle away asks and gets permission) but I could not access the program any longer. It just closes after it informs me that updating the binaries failed.
I have tried installing the program as an app, pushing an APK, and installing a zip from recovery. No matter what I do, it ends up the same.
I have also re-flashed the boot several times, and tried a different method using Odin directly and CF-Root. (seems to be the only way to uninstall it) I have tried numerous combinations, but to no avail. I feel like I have done everything I know how to do short of an unroot to stock and try again.
Any helpful suggestions are welcome.
I'd like to be able to use the program, but this is turning into an OCD nightmare. I'd post this in a development forum, but do not have enough posts yet.
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
illmatic24 said:
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
Click to expand...
Click to collapse
Thanks. I ended up doing it the hard way. (I swear I had auto email notification enabled here, or I would have seen your post and tried it)
Anyway, I cleared caches/userdata/wipe cache partition first, then flashed a stock unrooted 4.1.1 rom from here,
Then I used CF-autoroot, and low and behold, SU was showing up as an app. (it was not previously when I used CF-AR)
I let it update itself and bam, it works! Installed adbd insecure, and it works too. (it was not showing up as an app when I did it before either)
Next I added TWRP 2.4.3.0. and everything still works!
Either the stock AT&T rom on this unit had something interfereing with root, or the root image I used in the toolkit has an issue. I'm leaning towards a toolkit issue since when I used it and it installed TWRP 2.4.1.0, I could not get into recovery, just a black screen.
I lieu of this, I'm limiting my use of the toolkit.
Curiously, the toolkit also allows a sideload via TWRP/CWM, but does not provide a driver. Windows 7 cannot recognize the phone in recovery mode with a custom recovery installed, although it does when a stock recovery is. I have yet to find a driver.
Hello everyone, please be patient with me as I am relatively new to modifying phones. However, I have spent a good portion of the past 1-2 weeks looking into this problem on XDA + google, and I am at the end of my rope.
Here is my problem (I'm sure you already know):
I have no current solution to installing a custom recovery on my phone. I really just want custom recovery to restore FULL backups via Nandroid or equivalent.
Here are my questions:
1) In download mode, Odin has no problem flashing an official image/firmware (tar.md5) to the phone. Is it possible to create my own image of my phone into one file and flash it via Odin to my phone when I would like to restore? I have a feeling that something in the phone checks the hash of the image (I'm sure that I'm not saying it right), and that, considering my image would be twice the size of the official, there would be no way to make my image pass using collisions or what not. However, this would probably be my first choice after safestrap (assuming that won't work), so let me know.
2) I have read that certain people with phones similar to mine (not my variant though) have successfully "swapped" the external and internal SD cards. If I remember correctly they just change a couple lines in void.fstab. If this could actually be done, I could easily restore a backup to the now external internal SD, then change the settings to reswap on reboot. I feel like this is too good to be true though, as I have not seen this as a solution to my specific problem online. Is this actually a suitable option?
3) Currently my phone model is not an officially recognized device which Safestrap will work on. However, I have read that it is possible to do on my model using the Safestrap version which corresponds to a close variant of my phone. Can this be done? Please let me know if you have any information on this.
4) I guess this would be the last resort. I'm pretty good at taking things apart, but even better I can put those things back together Is the internal "SD" really just an SD card deep inside the phone? Would it be possible to replace that card for the purpose of backing up?
Here are my phone specs:
-Samsung Galaxy S4 Mini (SCH-I435)
-The carrier is Verizon Wireless
-Android Version 4.4.2 (kitkat)
-Baseband Version I435VRUBOC1
-Kernel Version 3.4.0 [email protected] #1 Fri May 23 2014
-Build Number KOT49H.I435VRUBOC1
-Hardware Version I435.05
-Configuration version B13.SAM.SCHI435.0
-Needless to say, phone is rooted and has busybox + etc correctly installed.
Any help will be greatly, GREATLY appreciated -- even if that help is telling me that it isn't possible. I can't seem to give up on this.
Thanks,
Kurt
Help
Does anyone have any advice on this? I would REALLY appreciate it. Thanks again.
-Kurt
I'm also interested on this. Thanks for your efforts
Nope no recovery because the Verizon minis bootloader is locked. It can be rooted with kingroot i think its called and then switched to SuperSU by replacing it.(I used super sume pro to get rid of kr) ****!!After root install a application like "disable application [root]" and disabe all Knox applications and any unused apps.(look for a list of recommended apps to disable)
Kannz2 said:
Nope no recovery because the Verizon minis bootloader is locked. It can be rooted with kingroot i think its called and then switched to SuperSU by replacing it.(I used super sume pro to get rid of kr) ****!!After root install a application like "disable application [root]" and disabe all Knox applications and any unused apps.(look for a list of recommended apps to disable)
Click to expand...
Click to collapse
How did you switch it over to SuperSU? I tried, but when it tried updating the root binaries it couldn't continue because of KNOX, so I was stuck with Kingoroot's.
I used this method to replace KINGROOT NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243 with supersu. most other versions i tried didnt want to cooperate and would make me lose root after one reboot. also i bought the pro version of supersume pro its 4$ off google play.
Kannz2 said:
I used this method to replace KINGROOT NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243 with supersu. most other versions i tried didnt want to cooperate and would make me lose root after one reboot. also i bought the pro version of supersume pro its 4$ off google play.
Click to expand...
Click to collapse
I tried it with the free version they linked to and it de-rooted it, so maybe I'll try later when I have enough Opinion Rewards credit to get the pro version. That or it doesn't work on this phone with Kingoroot. (The Google Play description says it should do Kingoroot though.)
Did you download the correct version? The one off the kingroot site doesn't work for me. It just deroots. I still have root on both of my s4mini Verizon phones. Try this link to get a working one.HERE scroll down a bit and the different versions are there. Try each one starting with 4.5. Also remember to restart after you root with kingroot and install super sume after the restart.
I just had to re-image my phone, so I did it according to your directions. (Though with the free version still of super sume) and it worked, although it won't update to the newest root binaries. It fails when I try. Did you have this issue? Other than that, SuperSU works.
I updated using "normal" and it worked fine for me. Glad su works at least. also for one phone I did a full unroot factory reset and then I reflashed a tar with Odin. Did the normal root with kingroot 4.5. Restarted tried a few root things like no frills cpu thing then installed super sume pro. Did stage 1. An 2 then supersu started up automatically it asks to update (I think net connection is needed) *do update "normal" because there isnt any recovery. Uninstalled kingroot like supersume says. Did a few root things then restarted. (Checked for superuser after reboot and it stayed)
The most recent guide regarding Android Pay is dated and written for OOS 3.2.2 and Magisk v6. I got to thinking tonight that I might as well actually try Android Pay since I'm absolutely hating the damn chip readers. Plus the added security and whatnot. I've tried getting it to work by disabling SuperSU, but it still flagged my device and said no. I remember reading somewhere that it's also checking for unlocked bootloaders but that a custom kernel could circumvent the check entirely.
Am I missing anything else? I'm beyond willing to back my phone up and return to stock, as long as I'm able to still use root and my custom kernel.
You can use Android Pay with the latest Magisk. I think Xposed breaks Android Pay although.
The process to get Android Pay working with root is:
1. Flash the stock ROM again (or any custom ROM that doesn't come with root by default eg: LineageOS)
2. Flash your favorite kernel if you want to. (Any kernel, or none if you don't want to)
3. Delete /data/magisk.img and /data/su.img if you have them. (Just to give it a fresh start)
3. Flash Magisk. It will automatically install MagiskSU, which is the default (and recommended) root for Magisk.
4. Reboot.
5. Install Magisk Manager from the play store.
6. Go into the settings in Magisk Manager and enable Magisk Hide.
7. Reboot.
8. Android Pay should work.
Hello everyone
I am new to flashing/rooting a android phone. I have a Sony Xperia Z1 Compact with Android 5.1.1 Lollipop, Kernel 3.4 (I think), Version 14.6.A.1.236. I want to customize it to get a better battery life and most importent to rid of bloatware and as many google services as possible but Google Play Store.
I first unlocked the bootloader by following Sony's own guide using commandline in a "mini adb/fastboot installation" on a W7 pc. Check...
Then I flashed a TWRP v2.8.70 again by commands in the same "mini adb/fastboot installation" Check...
Then I got black screen but the phone was up and running. Then I flashed a image found here on this site: [UB ONLY] [kernel] Root, init.d support, Recovery & Busybox for 14.6.A.0.368 and I was up and running again with Android 5.1.1 Lollipop, Kernel 3.4 (I think), Version 14.6.A.1.236. (dont know why though)
Then I got the phone rooted by entering TWRP and installing SuperSU. Check...
Now it runs normal and I can also boot into TWRP by pressing volume up when Sony logo pops up on the screen. So I think i am good?
Now my goal is get my phone to run smooth with no bloatware, minimal google services and better battery time and all this in that order.
Now I know that I problably can get this by uninstalling most of the bloatware and google services with for an example Titanium and then disable running services not needed with for example Servicely.
But I really want to learn to flash custom roms, but as a newbie I am afraid to to something wrong with all the talk about kernels and so on.
So my questions is as follows.
1. Is there a custom Lollipop rom (I guess a ROM is both kernel and OS(android version)), I can flash using TWRP, that is without bloatware and minimal Google services? would appreciate links directly the the ROM's you have in mind please
2. If there is such a ROM, I guess it should be put on a SD card that I can put in the phone and access when in TWRP?
3. Such a ROM I guess should be the same kernel and android version which is the same as the stock version that the phone has now?
4. The order is what?
1. Make a factory reset
2. Enter TWRP
3. Make a backup of kernel image, System and data to a SD card
4. Then wipe 1. Dalvik Cache, 2. System, 3. Cache, 4. Data
5. Then Flash Custom ROM image from SD card
6. Reboot
5. What are the potential dangers here?
I know there problably is a lot of former threads with the same subject, but in my search I quickly got lost in the abbreviations you guys use, so my hope is that you will bear with me. Also this is not my native language, so please excuse any misspelling. Any help are appreciated and thanks in advance
Hr.Skjold said:
Hello everyone
I am new to flashing/rooting a android phone. I have a Sony Xperia Z1 Compact with Android 5.1.1 Lollipop, Kernel 3.4 (I think), Version 14.6.A.1.236. I want to customize it to get a better battery life and most importent to rid of bloatware and as many google services as possible but Google Play Store.
I first unlocked the bootloader by following Sony's own guide using commandline in a "mini adb/fastboot installation" on a W7 pc. Check...
Then I flashed a TWRP v2.8.70 again by commands in the same "mini adb/fastboot installation" Check...
Then I got black screen but the phone was up and running. Then I flashed a image found here on this site: [UB ONLY] [kernel] Root, init.d support, Recovery & Busybox for 14.6.A.0.368 and I was up and running again with Android 5.1.1 Lollipop, Kernel 3.4 (I think), Version 14.6.A.1.236. (dont know why though)
Then I got the phone rooted by entering TWRP and installing SuperSU. Check...
Now it runs normal and I can also boot into TWRP by pressing volume up when Sony logo pops up on the screen. So I think i am good?
Now my goal is get my phone to run smooth with no bloatware, minimal google services and better battery time and all this in that order.
Now I know that I problably can get this by uninstalling most of the bloatware and google services with for an example Titanium and then disable running services not needed with for example Servicely.
But I really want to learn to flash custom roms, but as a newbie I am afraid to to something wrong with all the talk about kernels and so on.
So my questions is as follows.
1. Is there a custom Lollipop rom (I guess a ROM is both kernel and OS(android version)), I can flash using TWRP, that is without bloatware and minimal Google services? would appreciate links directly the the ROM's you have in mind please
2. If there is such a ROM, I guess it should be put on a SD card that I can put in the phone and access when in TWRP?
3. Such a ROM I guess should be the same kernel and android version which is the same as the stock version that the phone has now?
4. The order is what?
1. Make a factory reset
2. Enter TWRP
3. Make a backup of kernel image, System and data to a SD card
4. Then wipe 1. Dalvik Cache, 2. System, 3. Cache, 4. Data
5. Then Flash Custom ROM image from SD card
6. Reboot
5. What are the potential dangers here?
I know there problably is a lot of former threads with the same subject, but in my search I quickly got lost in the abbreviations you guys use, so my hope is that you will bear with me. Also this is not my native language, so please excuse any misspelling. Any help are appreciated and thanks in advance
Click to expand...
Click to collapse
to debloat your rom,just use this https://forum.xda-developers.com/crossdevice-dev/sony/wip-debloat-lp-690-correct-functioning-t3076161
and you re pretty much done.
as for google services,my opinion is let them untouched.
Hey Good Morning folks.. I bought a new phone J6+ and I didn't care for warranty and I decided to void it and root my device. I updated my phone to the latest software from Samsung through Odin and everything went well. I downloaded Magisk Manager after that then pulled the boot image from the stock room I have using 7-zip and patched it then flashed it to my phone through Odin. As in such case it was supposed to work as it worked with all other Samsung devices I rooted.
After that I downloaded Solid Explorer and I tried to remove some apps from my /system/apps as a simple test to see if my root works. it was Youtube it wasn't a dangerous critical app. But then my phone hanged and restarted then I found Youtube is back.
I went to Magisk again and downloaded BusyBox from there and installed an app called "Uninstall System Apps" and I used it to remove Youtube also as a test it removed it and the restarted the phone flawlessly then I went to remove "Facebook" then restarted my phone then Gosh Youtube is back and also Facebook.
I found out if I try to modify anything in /system the phone will restart then undo what I've done.
what is the reason? is it Defex? is it RMM? is it Knox? is it DM-VERITY? I just wanna know what is wrong with it to see how I can fix it.
Edit:
Phone: SM-J610F/DS
Software Build: M1AJQ.J610FXXU1ASA3
Magisk version: 18.1
I keep reading other threads and posts. I can see there is a way using Ashyx Method https://forum.xda-developers.com/ga...ecovery-twrp-3-2-3-1-galaxy-j6-j610f-t3875150
I just wanna know why it fails if I install Magisk with "Patched Boot method" only.