Trying to get CWM and root on previously rooted Note 3 - General Questions and Answers

*** note i have figured out all issues on my own, trying to figure out how to delete this thread****
I have a TMOB Note 3 that I recently upgraded to OEM Lollipop. I had a couple of issues so decided to take the plunge and just upgrade further to an unsupported 5.1.1 ROM. I took nandroid and Titanium backups and stored them away on my PC.
Here's where I started getting into trouble. First I wiped everything, then realized I didn't have CWB installed.
So I tried to install CWB using Odin and n9005-cwm-recovery-6.0.4.7-kk(0125).tar. This worked but it didn't also provide me root. CWB prompted me if I wanted to root when it rebooted, but SuperSU says I am not rooted. Once I install CWB, I can no longer boot into recovery mode either with the key combo.
In this process I also lost my carrier unlock.
1. How do I obtain root after using Odin to install CWB? - solved
2. Why can't I boot into recovery mode with the three key combo after CWB has been installed - sort of solved, using ROM Toolbox
3. Can someone point me to a thread on how to carrier unlock the TMOB Note 3? There was a software unlock for it that I used 3 years ago but I can't find that thread (and not sure if it's OS specific at all, ie, if it will still work with Lollipop once I find it)
I'm continuing to work on these problems, but wanted to get this post out in case I'm still stumped by the time someone with an answer sees it. Thanks!

Related

[Q] Rooting Samsung Galaxy i5500

Hello all,
I have had my Galaxy i5500 for awhile now and have used odin to flash updates for the firmware etc.
I have recently rooted my phone using Superoneclick and this worked fine. Overclocked the phone, and ran a number of Apps using SuperUser Access to gain all the benefits from this.
I installed Titanium Backup and Installed it on my SD Card, this caused a number of problems and I had to pull the battery on my phone to reboot it. Anyway it then hung at the GT-I5500 screen and I ended up having to download a new firmware (not custom) and use Odin to update it.
I now have a working phone, however I now can't root it. I have tried Superoneclick, that no longer works. I have also tried Universal Androot..with that I get an error message of Root Failed - No Fu Guu (or something like that) and I have just tried using z4root... with that it says acquiring Root Shell and then it just kicks me out...have checked and it's not rooted.
I also can't seem to access the reboot menu on my phone (the one where you press a couple of buttons to enter the menu where you can factory set your phone.
Can anyone shed any light on this? Other than these problems mentioned, the phone works as it should
Solved....
It took awhile of trying different root software but.... after reflashing my phone with another stock rom, I found Super One Click still didn't work, nor did z4root or universal Androot (I'm guessing it would have worked without reflashing a different rom).
I did however find that Unlock Root 2.2 worked! My phone is now flashed, no error messages and I have Superuser Access!! Now time to install a custom bootloader and start with the custom roms!!

[Completed] Formatting Samsung S3 Problem

Hey, so basically I'm in a situation where I have no idea what to do.
I recently just got a new phone, and am going to give my Samsung Galaxy S3, SGH-T999V model - from Wind Mobile to my Dad. Basically, when I first got the phone - a couple months after, I decided to try Rooting it, and I did, successfully. Since I didn't really know what to do with my rooted phone, I decided to unroot it - then tried rooting it again some months later, but it didn't work successfully. Basically my phone wasn't rooted, but I had the "Team-Win" recovery on it.
I wanted to bring my phone back to it's original state - and have the stock recovery on it. After some Googling, my solution seemed to be to flash the stock rom for the SGH-T999V model onto my phone using Odin. And I did that - and it worked successfully. But I still couldn't check for OTA updates or anything, it said my phone had still been modified in an unauthorized way.
Now that I need to give the phone to my Dad, I have to format the device and erase everything. This is where my problem starts. When I try to format it (using the Stock recovery), I see a bunch of error messages, with the Android logo falling down in a kind of dead way. I reboot my device, and nothing changes.
It still has all my data, and everything on it.
Sorry if this is the wrong area to post this (I'm relatively new to the forum), and if my problem doesn't make much sense - I've tried being as detailed as possible. Could anyone help?
Hi, thank you for using XDA Assist. Flashing the stock firmware should show you to get ota's. This should have everything you need,http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125. Also, you can ask further questions here,http://forum.xda-developers.com/galaxy-s3/help/help-thread-galaxy-s3-question-t2690307
Thread closed

[Q] Verizon Galaxy S3- Me Messing up

As the title of this suggests, I messed up BIG TIME when attempting to get Cyanogenmod on my Verizon Galaxy S3.
Long story short, I tried putting CWM on my phone without looking up things about it, like whether or not the bootloader was locked for 4.4.2 Kitkat, which it was, and has been since 4.3 Jellybean, which I did not know at the time I tried screwing with my device (which was around a week ago), and I started trying to mess with the phone without knowing what the hell I was doing, since the last time I tried modding a GS3 was over two years ago.
Long story, well, long, I tried installing CWM via the ROM Manager app, and, upon installing it, I screwed up the recovery mode on the phone. It wasn't a big deal, until I decided I wanted to put the latest version of Cyanogenmod on it, instead of using the stock Touchwiz interface.
Well, a couple days ago, I stuck Safestrap on it, and was able to use that as a recovery mode, since the normal recovery mode was locked off, entirely.
I figured that, tonight, I would look up ways to stick Cyanogenmod on my GS3.
I found a couple ways to do so, downloaded the gapps file I needed, the SU binary update, as well as an unofficial version of Cyanogenmod to let me use 5.1 Lolipop.
Well, I wiped the cache on the phone, as well as the dalvik cache, and factory reset the thing, ad went to the folder I put the gapps, SU binary update, and CM files in, and tried installing them.
Well, the SU update went fine.
gapps won't install.
The CM file I'm using SAYS it's installed, but the phone doesn't have an OS, which is confusing me.
I don't know if the phone is bricked, I just know that I did something stupid, and I don't know how to put an operating system back on the phone, either through Kies or Odin (I can't install anything from the SD card in the phone, because now I can't access it, since when I boot it up, there's no OS, and I need one to access the files on the device).
Whenever I try using Odin to put either a stock firmware version on it, it fails.
My phone, in DL mode, says: "SECURE CHECK FAIL : RECOVERY"
I don't know what this means, but I think it means I'm pretty well screwed.
I need to get rid of CWM and Safestrap via my computer, THEN reinstall the stock recovery mode on my computer, too.
I NEED to know how to do this.
If there is ANYONE out there who can help me out, or direct me to some other thread, that would be amazing, and GREATLY appreciated.

Root on PD2 6.0.1 Sprint S6 Edge/TWRP 3.0.2-1.

Hi folks,
just posting this writeup thinking maybe it might be of help to some people.
Started with a clean S6 Edge straight from Samsung repair for broken screen. Factory wipe, KNOX reset. It had the PD2 update. Tried using Skipsoft's Toolkit and ponied up a donation to get the Pro version with the S6 Edge 6.0.1 update, but it didn't work: it got stuck at the "SEANDROID NOT ENFORCING" screen after flashing TWRP 3.0.2. I know there are issues with 3.0.2, but it's what's optioned in Toolkit now.
Flashing TWRP 2.8.7.0 results in normal boot, but I could not enter recovery mode for some reason. 3.0.0-0 didn't work, either.
What I ended up doing is forcing phone into download mode (Power+Volume Down+Home), ODINing TWRP 3.0.2-1. This resulted in a bootloop (somewhat expected). But I could get into recovery easily. From recovery, I flashed Renegade's PD2-Aroma V3.0 Full ROM via ADB sideload. After a very long first boot, everything works 100%! Root, SuperSU, etc., all taken care of. Hotspot works.
Notes and tips:
- While I didn't use Skipsoft's Toolkit in the end, it's still worth supporting. Might work smoothly using 3.0.2-1 instead of 3.0.2.0, but I'm comfortable with adb/fastboot/etc. so just ended up using that. If you don't already have Android SDK and tools/platform-tools, Skipsoft conveniently includes those commands in its directory under C:\Unified_Android_Toolkit (they're named adb-toolkit and fastboot-toolkit. You can copy and rename them as "adb" and "fastboot" for convenience).
- Make sure you get the right TWRP 3.0.2-1 device version. You want to use twrp-3.0.2-1-zeroltespr.tar.md5 for Sprint S6 Edge. Remove the .md5 part and set it to use the .tar extension (stupid Windows asks you to confirm file extension type change).
- In TWRP you can either push your custom ROM or sideload it. To push a file, move the custom ROM into the same directory you've got adb/fastboot for convenience. Open a terminal window in that directory, and either "adb push customromfilenamehere.zip /sdcard/" or in TWRP, click Advanced/ADB Sideload, and enter "adb sideload customromfilenamehere.zip".
- If you're sideloading it, it's gonna take a while, and will start flashing even while the transfer percentage is creeping up. Example: at around 9%, it started AROMA, around 14%, it went through some of the installation options. It was done flashing everything and ready for reboot even though the terminal window said only 76% was transferred. That's ok. Click "finish" in AROMA on phone, reboot. Unplug phone. Wait a long time for first boot (this took around 20 minutes for me). ENJOY.
Remember: all is not lost as long as you can get into download mode! Power-Volume Down-Home until you get to screen prompting to get to download mode. Volume up to select that mode. You can ODIN from here.
Additionally: if you find yourself for whatever reason stuck at the initial S6 Edge boot screen with "SEANDROID NOT ENFORCING," you might be in some kinda of boot limbo. I was able to issue some adb commands here, even with recovery was borked and the phone didn't boot all the way. Doing an "adb reboot-bootloader" would let me do a complete boot to ROM while I was trying to get the different TWRP versions working (until 3.0.2-1).
Hope this helps someone.
tl;dr: For PD2/6.0.1 Sprint S6 Edge, manual flash TWRP 3.0.2-1. Push custom ROM through Recovery. Reboot, wait a long time. Success!
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN latest TWRP 3.0.2.1 - HERE.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Alpine- said:
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN Ram's TWRP 3.0.2 - HERE I'm assuming the other guy's 3.0.2 works fine too, I am not sure why you hung and had to revert to a 2.x TWRP build.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Click to expand...
Click to collapse
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
baknblack said:
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
Click to expand...
Click to collapse
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Alpine- said:
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Click to expand...
Click to collapse
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
baknblack said:
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
Click to expand...
Click to collapse
Edge is better imo, certainly looks better. All you need is Renegade rom anyway. May be a few more roms in active dev for s6 but nothing better per se. Renegade rom dev is alive and well.
Would these root methods trip knox?
chen69chuck said:
Would these root methods trip knox?
Click to expand...
Click to collapse
Yes
Thanks.
Working for g920v 6.0.1?
freaking thank you been struggling with twrp on and off for two days trying to bring this phone back from the dead! YOU the man

I can't get wifi to work after installing TWRP

Hi all,
Before you jump at me telling me I haven't searched the forum, I DID and I couldn't solve my issue even with these solutions. To get you up to speed on what exactly I did.
Briefing (not very important):
I was doing my own business and I was free, I use my phone daily and it served me well. But I noticed that the last security patch I got was on 2020 and got me thinking. Why not just use custom ROMs to update my phone and get a year or two from my MIX3 (2018). I just recently flushed my brother's phone (Samsung) with a custom ROM and I liked it. I already installed TWRP 3 years ago on my brother's phone and I just had to install a zip file and boom new Android 12 on a 2014 phone.
The problem:
after reading here on the forums, it seemed that it is more complicated to do. I'm up to the challenge, I have done it before and the reward is worth it.
+Unlocking the Bootloader
this was a bit easy other than the connection issues but I got it unlocked eventually. (use the QR code to sign it. it is much easier)
I had an issue where after unlocking the bootloader the phone didn't allow me to install TWRP and do a backup, it immediately went into erasing the entire phone.
+Installing TWRP
I downloaded the files from TWRP website and everything was smooth other than the Mi Recovery popping every time I restart (install Magisk to plant TWRP then remove it if you don't need root)
+The downhill
after restarting, the phone worked fine I installed all the apps and restored everything. Afterward, I noticed that the camera does not work. It gives me an error. I reinstalled TWRP again since it was reverting to its Mi Recovery and I think here was the problem I flashed the recovery.img into the boot partition by mistake (I didn't notice at first) but after going back to the command I saw I made a mistake and reflashed the recovery with recovery.img and installed the Magisk and everything was ok. At the initial start, the SIM and the WIFI are not working.
after several attempts at reinstalling different flashable stock ROMs, I saw that the issue is consistent. I read online that you have five .img files that control the different parts of your phone. I got tired and decided to reflash the stock ROM via the Mi flasher and get it back to stock.
Even after flashing the stock ROM, I'm still having the same issue.
I reflashed the modem.img in the modem and still wifi and sim card are not working
I read that some phones have an A/B partition and my phone does NOT have it.
I'M AT A LOSS I CAN NOT FIX IT. IT'S BEEN 3 DAYS ON THIS AND I CAN NOT FIGURE IT OUT!!
Ok, If anyone was passing by I think I found what was the problem.
First, check if your problem matches mine. Go to Settings and check your IMEI. Or just dial *#06# ,if your phone did not return with a number then you lost your IMEI number.
follow this guide and I hope it helps. this is only for some phones so don't try it, it might break your phone
[GUIDE] Backup, edit and restore QCN. Fixing lost IMEI.
Introduction This is a guide to backup and restore the QCN, and to edit other's QCN in case you lost your IMEI and you don't have a backup of your QCN. There are other ways to do some steps (the most popular is via Fastboot) but I'm gonna...
forum.xda-developers.com

Categories

Resources