Related
I am preparing to root my Verizon GS3. The process looks pretty simple, but I still have a few questions I would like to have cleared up first just to make sure everything goes to plan.
I have downloaded the following files as instructed to in one of the threads on how to ROOT the GS3:
- USB Drivers
- Odin (unzipped with Winzip)
- Stock rooted system image (mirror link)
- CWM
My first question is whether or not I am supposed to unzip the stock rooted system image. The post says I should have a file named "rooted.system.img.tar" to select in the PDA section of ODIN, but the name of the file I have is just "rooted.system.img."
The second question I have is which custom recovery should I choose? I downloaded both, but don't know if one is better than the other or if it just comes down to personal preference. Also, do I need to unzip either one of those files? And if I choose not to push a recovery now, can I push it later if needed to flash a new ROM that I like. I ask this because the only real reason I want to root right now is to disable the ridiculous wifi notification in the notification bar and the pop up that you get when opening a "high data usage application."
Another concern I have is returning to stock. On my DROID X2, all I had to do was use RSD Lite and flash back to stock. I have downloaded the stock kernel and stock ROM off of one of the threads on here (I can't find it for some reason), but was just wondering how I would go about using that to get back to the way it was out of the box.
Thanks for the help!
Edit: As far as the first question goes, I selected the rooted.system.img in ODIN and it shows it as rooted.system.image.tar at the end, so I'm guessing no unzipping for that file is necessary, correct?
Don't unzip that tar you are good with that system image. Install the usb drivers and put your phone into download mode. Start Odin then set that to pda plug in your phone and wait for the drivers to install correctly. Remember you should have a full battery before flashing. Browse to your image then flash the system image, it might take a while to flash so be patient and don't move the computer or phone.
Just pick the recovery you like they are really up to personal preference. I like cwm because I used it in my og droid and dinc. You can always change recoveries in the future if you find a different one you like more.
You don't need to install cwm in the old way, just download it from the play store after you are rooted. When you install the recovery from the app choose Verizon galaxy s3 from the list. It will ask for root before trying to install cwm recovery. When you install cwn it will make your phone say custom when you boot up so if you don't want that skip the recovery for now.
I have never returned a phone to stock but I think to return to stock flash the stock Verizon image with Odin.
Down with Verizon for locking my bootloader
manchild83 said:
Don't unzip that tar you are good with that system image. Install the usb drivers and put your phone into download mode. Start Odin then set that to pda plug in your phone and wait for the drivers to install correctly. Remember you should have a full battery before flashing. Browse to your image then flash the system image, it might take a while to flash so be patient and don't move the computer or phone.
Just pick the recovery you like they are really up to personal preference. I like cwm because I used it in my og droid and dinc. You can always change recoveries in the future if you find a different one you like more.
You don't need to install cwm in the old way, just download it from the play store after you are rooted. When you install the recovery from the app choose Verizon galaxy s3 from the list. It will ask for root before trying to install cwm recovery. When you install cwn it will make your phone say custom when you boot up so if you don't want that skip the recovery for now.
I have never returned a phone to stock but I think to return to stock flash the stock Verizon image with Odin.
Down with Verizon for locking my bootloader
Click to expand...
Click to collapse
Sorry for the late reply. I went out to eat with the fam.
Thanks for clearing that stuff up for me! Can't wait to root my GS3 in 7 days after my return policy is used up!
Thanks again!
You're welcome good luck with the phone.
Down with Verizon for locking my bootloader
So I am officially getting ready to ROOT my GS3. Is there anything I need to do to prepare for the process? I have seen people say you need to enable any of the bloat you have disabled and I have also seen wiping the cache thrown around a few times, so I would just like to know if there is anything along those lines that I need to do before I start.
DROIDLOVERX2 said:
So I am officially getting ready to ROOT my GS3. Is there anything I need to do to prepare for the process? I have seen people say you need to enable any of the bloat you have disabled and I have also seen wiping the cache thrown around a few times, so I would just like to know if there is anything along those lines that I need to do before I start.
Click to expand...
Click to collapse
I'd follow this to root. Don't need to do anything else but what it says there.
Hi all, I'm newly registered here, however, I have been coming here to XDA for over two years now as unregistered to browse and become more knowledgeable regarding rooting, unlocking and ROMing my phones. I would like to use the Casual Root/Unlock/Recovery AIO Toolkit and finally have more freedom over my locked down Verizon Galaxy S3. I am currently running MF1 and I'm completely 100 percent stock. I've downloaded Casual, have all the Samsung drivers installed and am anxious to pull the trigger. I just want to confirm I'm on the right page and do diligence first. After I run Casual and Root, unlock the bootloader and install TWRP, would it be wise to immediately boot into recovery and then backup the rooted MF1 firmware and then back up my imei by copying the efs folder to the SD card and my PC? Is this method correct for backing up the imei or is there a specific program for it? I have searched through many custom ROM's and I am planning on flashing Beanstown106's Jelly 'Beans' Build 19 ROM, as I love the fact it's AOSP themed but has a lot of features from Touchwiz. Does this ROM happen to back up the imei automatically by chance? I've already backed up my contacts and important information, so are there many things I'm missing or am I on the right track? Before flashing Jelly 'Beans', would I need to wipe the cache / davlik at all? Or is that only when coming from a different ROM? Any help wouwould be greatly appreciated and many thanks in advance for your time!
K20Z1 said:
Hi all, I'm newly registered here, however, I have been coming here to XDA for over two years now as unregistered to browse and become more knowledgeable regarding rooting, unlocking and ROMing my phones. I would like to use the Casual Root/Unlock/Recovery AIO Toolkit and finally have more freedom over my locked down Verizon Galaxy S3. I am currently running MF1 and I'm completely 100 percent stock. I've downloaded Casual, have all the Samsung drivers installed and am anxious to pull the trigger. I just want to confirm I'm on the right page and do diligence first. After I run Casual and Root, unlock the bootloader and install TWRP, would it be wise to immediately boot into recovery and then backup the rooted MF1 firmware and then back up my imei by copying the efs folder to the SD card and my PC? Is this method correct for backing up the imei or is there a specific program for it? I have searched through many custom ROM's and I am planning on flashing Beanstown106's Jelly 'Beans' Build 19 ROM, as I love the fact it's AOSP themed but has a lot of features from Touchwiz. Does this ROM happen to back up the imei automatically by chance? I've already backed up my contacts and important information, so are there many things I'm missing or am I on the right track? Before flashing Jelly 'Beans', would I need to wipe the cache / davlik at all? Or is that only when coming from a different ROM? Any help wouwould be greatly appreciated and many thanks in advance for your time!
Click to expand...
Click to collapse
To backup your imei/eri check the synergy rom thread. They have a zip to back them up. It's in the attachments. It only takes a few seconds but will save you a world of headache. If you want my opinion that's the first thing you should do once you root, unlock and have your custom recovery. Store that zip on your SD card, PC and cloud(Dropbox, Copy, Box, Mediafire, etc).
Sent from my SCH-I535 using Tapatalk 4
TheAfroSamurai said:
To backup your imei/eri check the synergy rom thread. They have a zip to back them up. It's in the attachments. It only takes a few seconds but will save you a world of headache. If you want my opinion that's the first thing you should do once you root, unlock and have your custom recovery. Store that zip on your SD card, PC and cloud(Dropbox, Copy, Box, Mediafire, etc).
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I greatly appreciate your insight and input TheAfroSamurai. I will check that thread out and get that zip to backup the imei / eri.
K20Z1 said:
I greatly appreciate your insight and input TheAfroSamurai. I will check that thread out and get that zip to backup the imei / eri.
Click to expand...
Click to collapse
Here you go : http://forum.xda-developers.com/attachment.php?attachmentid=1281376&d=1345868740
Once you get root and unlock the bootloader, backing up your EMEI is recommended (I did not until I flashed my first ROM). There is a great
thread that the previous poster may have pointed you too (if so, sorry for the repost): http://forum.xda-developers.com/showthread.php?t=1852255
Previously you were pointed to the Synergy method (B). But A is very easy too, requiring you to have a terminal emulation app on your phone (I have Rom Toolbox Pro, which has a terminal emulator). Type in the two commands as instructed and it reboots. I then did B and hopefully I am doubly covered.
After that, flash your preferred ROM (lots of really good ones, I use BoneStock 3.4) and you are ready to go.
TheAfroSamurai said:
Here you go : http://forum.xda-developers.com/attachment.php?attachmentid=1281376&d=1345868740
Click to expand...
Click to collapse
Ahh, thanks very much for the link, even easier to find.
Nomad1600 said:
Once you get root and unlock the bootloader, backing up your EMEI is recommended (I did not until I flashed my first ROM). There is a great
thread that the previous poster may have pointed you too (if so, sorry for the repost): http://forum.xda-developers.com/showthread.php?t=1852255
Previously you were pointed to the Synergy method (B). But A is very easy too, requiring you to have a terminal emulation app on your phone (I have Rom Toolbox Pro, which has a terminal emulator). Type in the two commands as instructed and it reboots. I then did B and hopefully I am doubly covered.
After that, flash your preferred ROM (lots of really good ones, I use BoneStock 3.4) and you are ready to go.
Click to expand...
Click to collapse
I greatly appreciate your help and advice as well, it's nice to know of other possible options backing up the imei. Something else I just thought of, once I root, unlock and get recovery using Casual, should I expect to see a message from Verizon stating that the software running is not official and to visit one of their stores? I have seen others mentioning this, but I'm not sure if and why that pops up. If it does, does it continue to pop up or stay on the screen at all? Or is it something that you can dismiss and you don't see it again?
Do you guys know if terminal emulator comes already installed on the Jelly beans rom by chance? Because that seems the easiest way to do it just by typing in those two commands. However, I would still download that .zip tool from Synergy as backup. Or would that not be needed at all if I was to use terminal emulator?
TheAfroSamurai said:
To backup your imei/eri check the synergy rom thread. They have a zip to back them up. It's in the attachments. It only takes a few seconds but will save you a world of headache. If you want my opinion that's the first thing you should do once you root, unlock and have your custom recovery. Store that zip on your SD card, PC and cloud(Dropbox, Copy, Box, Mediafire, etc).
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
After using casual, do I just place that zip on my sdcard pc and cloud and then run it if and only when the imei is lost? Or run it prior to placing it on the SD card and such? Sorry for all the newb questions.
K20Z1 said:
After using casual, do I just place that zip on my sdcard pc and cloud and then run it if and only when the imei is lost? Or run it prior to placing it on the SD card and such? Sorry for all the newb questions.
Click to expand...
Click to collapse
After you finish casual place the zip on your external sd card. If you haven't flashed a custom rom with boot to recovery menu you'll have to get to your recovery the hard way. Power down phone, hold vol up and home button at the same time you press power. Keep holding home and vol up key and let power button go. Phone should boot to your custom recovery, either CWM or TRWP depending on what you choose to use. Next go to install and navigate to the Synergy zip and choose install just like flashing a rom, kernel,etc. It will place a Synergy folder on your external sd. That folder will contain the backup zip you'll need in case you lose your IMEI/ERI. Make at least a couple backups of that.
Awesome! I really appreciate the help and quick responses. So once I've done that, if my imei should become lost, I would open that synergy folder and use the backup to restore the imei?
K20Z1 said:
Awesome! I really appreciate the help and quick responses. So once I've done that, if my imei should become lost, I would open that synergy folder and use the backup to restore the imei?
Click to expand...
Click to collapse
If you should ever need to just flash the zip in the Synergy folder, hopefully you won't ever need to. Once I got mine restored I haven't had to yet...fingers crossed.
Ok, perfect. That really sums it all up for me. Yea, hopefully you won't ever need it.
K20Z1 said:
Hi all, I'm newly registered here, however, I have been coming here to XDA for over two years now as unregistered to browse and become more knowledgeable regarding rooting, unlocking and ROMing my phones. I would like to use the Casual Root/Unlock/Recovery AIO Toolkit and finally have more freedom over my locked down Verizon Galaxy S3. I am currently running MF1 and I'm completely 100 percent stock. I've downloaded Casual, have all the Samsung drivers installed and am anxious to pull the trigger. I just want to confirm I'm on the right page and do diligence first. After I run Casual and Root, unlock the bootloader and install TWRP, would it be wise to immediately boot into recovery and then backup the rooted MF1 firmware and then back up my imei by copying the efs folder to the SD card and my PC? Is this method correct for backing up the imei or is there a specific program for it? I have searched through many custom ROM's and I am planning on flashing Beanstown106's Jelly 'Beans' Build 19 ROM, as I love the fact it's AOSP themed but has a lot of features from Touchwiz. Does this ROM happen to back up the imei automatically by chance? I've already backed up my contacts and important information, so are there many things I'm missing or am I on the right track? Before flashing Jelly 'Beans', would I need to wipe the cache / davlik at all? Or is that only when coming from a different ROM? Any help wouwould be greatly appreciated and many thanks in advance for your time!
Click to expand...
Click to collapse
Man i was right there with you. Not quite two years, but maybe two months of reading, researching, watching vids, etc. I downloaded the casual too because i am not great with adb commands, etc. I will tell you from personal experience exactly what my opinion is of what you should do. Someone else more experience may have a better way but now that i have become a serial flashaholic hindsight is always 20/20.
1. Find the stock firmware for the Verizon Samsung Galaxy S3 any version whether is be VRBMF1 or older and download Odin. That way if anything happens short of a hard brick you can ALWAYS Odin back to stock if you are completely out of options.
2. Run CASUAL to (a) Root (b) Unlock the Bootloader and (c) download TWRP ; I have used Clockword Mod and TWRP and I personally found TWRP much easier to use
3. First thing I would do is download the Synergy HWkeys backup zip and flash it while you are still stock rooted to backup the imei. Thank God i haven't lost the imei before i backed mine up but that way you have plan b and plan c, etc.
4. Make a TWRP Nandroid backup of your stock rom that way you can always restore back up stock.
After you do that you are good to flash away my brotha. And a note too, remember that for most roms you need to flash gapps separately. I freaked my first flash and thought i broke my phone because i had no google apps but that was noob stuff on my end.
I hope this helps but all these roms and everything are really cool. the reason i came to android in the first place. and i dont donate as much as i should but you gotta give it up to these developers. anyways. later man
happy flashing
Synergy backup works. I recently lost mine and had to restore it. It was super easy to do, but I wasn't sure at first if it was going to work. Couldn't tell you what caused it because I am super careful to download all the correct files to flash Roms. Also all AOSP Roms require you to download the GAPPS for whatever version of android it is running. All TW based Roms already have the GAPPS included in the ROM zip file. Just be careful when switching back and forth between AOSP and TW Roms. A good practice is to wipe everything 3 times to make sure you got everything. Sometimes also there are residual files and/or folders left over from AOSP Roms when switching back to TW so I have a practice of wiping internal storage before I switch back to TW. Just move whatever files you want to save to your external SD card. I switch Roms often so I usually don't have to move very much. I also don't restore apps or data from titanium backup. This most likely can cause problems if you're restoring data from a different ROM.
Sent from my SCH-I535 using Tapatalk 4
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!
3. Using your USB 2.0 cable and ports Install the Custom Rom "P900XXUANB3-RecoveryImg.tar" FIRST and flash it via ODIN 3.07 under the PDA checkbox that is "fixed" (so you noobs don’t make any soft bricks if this is your first attempt at rooting), and only use the ODIN 3.07 THAT COMES W/ CHAINFIRES AUTO ROOT .zip file and then unzip the folder to open ODIN 3.07 ONLY! This is only because I have read that there have been issues installing the SU via Chain Fires Auto Root Process... the file is called (currently as of 25 JUNE 2014) "P900XXUANB3-RecoveryImg.tar" PDA select it and then start when in DOWNLOAD MODE on your device. Manually select DOWNLOAD MODE if you have to BEFORE PRESSING START! Otherwise, one is just going to sit there and not accomplish anything.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
http://forum.xda-developers.com/attachment.php?attachmentid=2591159&d=1392930654
http://forum.xda-developers.com/attachment.php?attachmentid=2775098&d=1401644348
4 Reboot back into DOWNLOAD MODE. Flash in ODIN 3.07 with the PDA section and select this file next to install: "openrecovery-twrp-2.7.1.0-v1awifi.img.tar"
5. In DOWNLOAD MODE and flash the file under the PDA box TWRP (OR CURRENT RECOVERY OF YOUR CHOICE THAT IS AVAILABLE)
6. AGAIN... Restart your device into DOWNLOAD MODE via ODIN 3.07 and select PDA and then finally root this: "CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5" Then you can backup, restore, flash anything, and be happy! YOU SHOULD FINALLY HAVE A SUCCESSFUL ROOT! Turn off and REBOOT into RECOVERY to see if TWRP stuck and then reboot to see if the SU stuck. IF everything stuck reboot back into TWRP to flash whatever rom is available MAKE SURE TO BACK UP EVERY FILE BEFORE YOU FLASH ANY NON-STOCK ROMS. If not successful rinse wash and repeat until it does!
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
7. That’s it you should have root and a custom rom and recovery if you followed these instructions for flashing via ODIN 3.07 and Chainfires AutoRoot files. If you still have an issue repeat until root/recovery/Rom sticks. If you have to update the Binary for the SU just go to the Google Play Store and install the app and then try it again till it works. GOOD LUCK it worked for me this way!
**IMPORTANT**
BACK UP BACK UP BACK UP BACK UP after every flash that is possible to back up. If you can, back up the NON-SU stock ROM BEFORE installing SU, after installing the recovery and/or back up.
***IF I HELPED YOU OUT THANK ME***
DISCLAIMER - all research was observed via comments on the thread according to issues people have been having during ROOTING the device I simply have compiled the data and made a check list!
Need a link to the files you mentioned.
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
sstea said:
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
Click to expand...
Click to collapse
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Spere said:
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Click to expand...
Click to collapse
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
sstea said:
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
Click to expand...
Click to collapse
You can always flash stock firmware via odin
I was just wondering if everyone was having a much easier time with achieving root now? Kies caused me to "Hang" a lot during the Root and custom rom to stick w root... as of right now i can not get the only ONE custom ROM that looks promising, i have found by GWatts (correct me if i am wrong and i apologize if i have typed the wrong screen name handle) i believe his handle is... at this point im not sure what i am doing wrong as of yet but im sure i am missing a step or i just need to start back at unroot back to stock firmware and try and try again lol. not saying anything is wrong with his work at all by any means because people other than me with the same device have gotten it to stick and im just wishing i could as well because its sweet looking ROM! NOT TO MENTION THE ONLY ONE THAT IS OUT (that is which i know about. i haven't been on in a few months idk), SO KUDOS TO WATTS i just haven't been successful at installing his custom rom just yet... Im hoping that its just going to need to be erased again and then reformatted after a factory reset and what not, i pray it sticks because his incorporation of the aroma installer was a nice touch and his ROM really looks good... Now if i can just get it not to stick at samsung boot logo and freeze id be good lol!
sanvara said:
Need a link to the files you mentioned.
Click to expand...
Click to collapse
ok
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
pnuker said:
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
Click to expand...
Click to collapse
**Edit**
I went back and reflashed the twrp file and it got me out of the error screen. I installed supersu, and then re-flashed the cf-auto-root file, and it worked like a charm. I'm not sure if it was the installation of supersu, or just repeating the process that fixed it, but I'm happy either way...
Thank you! I succesfully rooted my SM-P900 after all mentioned problems ( hanging in the cache.img and after a while a disturbed screen etc.) with your guide. I am a very happy rooter now.
Thanks,
Thanks to the poster. I tried rooting with the instructions from a few other sites and thought I bricked it,
Followed your instructions, and presto.. Rooted! :good:
Rooted!
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
your welcome!
frankiecxyz said:
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
Click to expand...
Click to collapse
your very welcome! it took me a bit to get it down but i eventually figured it out and at the time information on rooting the device was hard to find with this specific model. then i discovered what the issues where and felt the need to post it! im glad i could help!:laugh:
Flash SU with TWRP not ODIN
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
soft bricked
Hello!
First of all let me say that I'm a complete newbie, this is my first android device. I tried to root my SM-P900 (P900XXUANI1) using an online guide (image with URL attached, as I am not allowed to paste URLs)
Unfortunately at Step 10 (flashing with Odin) the operation failed and now I ended up with a soft bricked device (I assume this is the correct definition). It will only show the message asking me to connect it to KIES to recover it.
I know i can try to use KIES 3 and restore it, but before that i would like to ask if there is any alternative which will allow me to unbrick the device without losing all my data... (yeah i know...).
If i follow this guide will this help? I'm not sure if I can even put the device in download mode again as it shows the error message about connecting it to KIES...
At this point I don't care about rooting, I just want to unbrick the device.... I understand the guide up to (and including) step 3. But for the rest of the steps I'm lost Could anyone please explain them in a bit more detail? I don't want to install any custom firmware, just to unbrick it...
Any help would be very appreciated!
Thank you
Yemble said:
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
Click to expand...
Click to collapse
Have you got a link to the odin rwrp 2.7 you used and the su 2.7 flash for twrp please?
VenomousViper said:
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!.......
Click to expand...
Click to collapse
When i trying root, my SGN freeze in "cache". Odin show error and tablet goes to Emergency Firmware Recovery. Аnd it does not matter what program I use and how I do it.
Mine Reboots Constantly
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
sunnykhs said:
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
Click to expand...
Click to collapse
Have you cleared dalvic cache and cache in TWRP recovery? Be forewarned the process takes a while for cache wipe.
Sent from my SM-P900 using Tapatalk
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
luan96 said:
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
That's what I love about Samsung, as long as you have your ducks in a row, the files and tools are extremely easy to use, a 4 year old could do it.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Thank you, ill be sure to check them out. Although, i would like to do the entire process from the beginning (root it again myself since i have no idea what the previous owner has done) and then try to install custom roms and other cool features rooting offers. I read that the KNOX security on samsung phones can pose some problems, any thoughts on that ?
Thank you again for your response.
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
I've got no experience with Linux, sorry. SuperSU disables knox so there's nothing to worry about.
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Droidriven said:
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Click to expand...
Click to collapse
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
luan96 said:
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
Click to expand...
Click to collapse
First, just to make sure that you are not walking blindly into some potential traps.
1) download the root checker app from Playstore, use it to verify whether the device is actually rooted.
2) power the device off, wait 5 seconds, hold volume up+home+power, when it boots past the logo, let go. It should boot to recovery, tell me what you see. Does it say TWRP with grey buttons on a black screen? Or does it have an android lying on his back and have options listed?
3) verify whether or not the bootloader is unlocked or not on your specific device model number with your specific build number/android version, if it's locked it will create problems if you try to flash custom recovery. Though you can flash CF autoroot with locked bootloader.
Then I'll help find what you need to do what you are looking to do. It may be simpler than you think.
If he in fact used Odin and the device is rooted, he did one of three things.
1) flashed custom recovery(TWRP) via Odin then flashed SuperSU.zip to root, not possible with locked bootloader.
2) flashed CF auto root via Odin, potentially leaving stock recovery if your bootloader is locked.
3) flashed a pre-rooted stock firmware via Odin, not likely though.
The first 2 being more likely than the last one, the second one being the most likely if your bootloader is locked.
Edit: @luan96, edited for more information.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
-Hope- said:
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
Click to expand...
Click to collapse
I'm going to use Odin for this. Since I'm quite new to the rooting community I dont want to mess things up on the first try. I'd rather get comfortable with some standard stuff before I proceed to try different variations. Thank you for your input. Though I would still like to know if I should use cm auto root or do a manual root. The difference is not quite clear to me yet. Again, thank you for your input, it is appreciated.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
Flashing CF autoroot will simplify rooting, again, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as your bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Flashing CF autoroot will simplify rooting, afain, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as you're bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
luan96 said:
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
Click to expand...
Click to collapse
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
luan96 said:
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
Click to expand...
Click to collapse
Did you get this restored with Kies?
Droidriven said:
Did you get this restored with Kies?
Click to expand...
Click to collapse
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
luan96 said:
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
Click to expand...
Click to collapse
If you have issues with Xposed causing a bootloop, you can flash the Xposed uninstaller zip in TWRP to remove it, then troubleshoot why it bootlooped and try again.
Are you using the Touch wiz marshmallow Xposed framework?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hello Forum,
I am in desperate need of rooting my old Galaxy Express Prime 2 (SM-J327a), because I accidentally deleted all of my images. I cannot find a .tar file to recover the device. I checked TWRP's site, and they don't have a file to support this device yet. Does anyone know another way to root this device, or where I can find a .tar file to use with Odin? I have tried virtually all root apps and programs.
Thank you,
Mosaic Owl
I would like to second this request (though I am not near as desperate). Has anyone tried using the Samsung one click root method for this phone?
Link to modded Odin to skip SHA256
Hydran said:
I would like to second this request (though I am not near as desperate). Has anyone tried using the Samsung one click root method for this phone?
Click to expand...
Click to collapse
I tried loading up One Click Root on my laptop and it said it couldn't find its servers. I also tried flashing twrp for a similar Boost phone, (SM-J327p) knowing there was a risk of bricking it. My J327a was free and I plan to stick with my Moto, so I could afford to risk it, plus I've always been able to un brick anything from graphics cards to phones and game systems.
Anyway, Odin 3.12 gets a few steps into the twrp install, but before it actually begins to install, an error pops up that says "SHA256 is invalid". I searched for a couple of hours, and all I can come up with is that AT&T put an extra check in there to see where the files were coming from, and attempting to install custom recovery will cause this error. A modified Odin was released to skip this check on an older phone, but I could not find a working link to it.
That's what I came here for: a link to the modified Odin that will allow me to install TWRP without that check. If it's posted, DO NOT try flashing the wrong twrp recovery if you can't afford having it bricked for a while like I can.
I guess you would need to start with an eng bootloader that will let your phone boot then work on a tethered root... I'm still looking for binary 2 with rev 2 combination file without luck, all I need is to extract the boot and see if I can reset lock pattern. I tried google account but it does not have the option to lock-relock screen anymore. It's my nephew's phone and my daughter messed it up. I can login the google account and make it ring and locate it but can't disable the pattern. He has no backup of this phone...
Have any one make it done?