I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk
dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
Click to expand...
Click to collapse
Thanks! I'll give that a shot. But a question before I do something really dumb. Where does this recovery tar file go in odin? PDA?
Yep always PDA
Sent from my SM-P900 using Tapatalk
Worked! I now have rooted KOT49H.T900UEUAND4.
Good stuff
Sent from my SM-P900 using Tapatalk
OK. Here comes the "but". It turns out that I cannot connect over SSL. Wifi works, I have an IP, I can brows non-secure websites. But I cannlt connect to anything https, nor will apps like Google Play connect.
Do we think this is related, or should i start a new thread?
UPDATE: I wiped data and now all is fine. The really interesting thing that I've noticed is that the Device Status is showing as "Official".
JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?
gbr357 said:
JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?
Click to expand...
Click to collapse
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.
Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?
gbr357 said:
Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?
Click to expand...
Click to collapse
I think I would have done that if I had known there was a B5 recovery image available. The guidance that I was given was to flash the B3 image from the P900. And that *did* work fine. Before there was a root flash for the T900, people were using the P900 root with success. Don't know that there is much difference. In the end, either way, you will end up with a B5 recovery image, as that is what Chainfire included in the T900 root file.
Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.
gbr357 said:
Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.
Click to expand...
Click to collapse
Which file from Chainfire did you flash? Was it CF-Auto-Root-v2wifi-v2wifixx-smt900.zip? For me, flashing that after OTAing to ND4 left me unable to boot. Maybe that got fixed in the past couple of day?
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Well. technically I wasn't rooted either. I completely removed root with SuperSU.Is your recovery NB5?
JJMT said:
I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?
Click to expand...
Click to collapse
That's the problem I've been writing about for a week. The new OTA update (t900ueuand4) doesn't work with auto-root and crashes exactly where yours did.
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Can you give me the link for the new chainfire file that must have been re-written in the last 2 days
---------- Post added at 11:32 PM ---------- Previous post was at 11:28 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Just re-downloaded the chainfire file and it's identical to the file I got 10 days ago dated May 10th. If you had success flashing it with the firmware t900ueuand4 installed at the time of rooting, then I'll give it a shot too.
JJMT said:
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.
Click to expand...
Click to collapse
All I had to do, was stop after 3. Didn't require a factory reset. Everything is great
The same here. Used the Note 12 recovery mod to unbrick the tablet.
Flashed the CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5 and it works. :good:
Now oor Samsung tablet pro 12.2 is rooted.
dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I ran into a similar issue except my device came up to an error regarding firmware upgrade failed, use kies to recover. I could not get this to work with kies 3. Searching the threads, I found your post. Worked beautifully. The failed attempt did trip Knox. Not sure I care.
Thanks!
Related
I am new with rooting my phone. I have used Rooted phones before, I followed http://forum.xda-developers.com/showthread.php?t=2258633 Motochopper how to. I ran into a problem. I click the superuser app that was installed onto my phone, and it tells me that "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." I click install and it tells me there was an error. I would like to root my phone along with potentially installing CWM so that I can easily install Cyanogenmod when they release a stable verison for the S4. Also would love to install titanium backup along with some Adfree apps.
Any help would be very much appreciated.
OK, so it looks like you already have it rooted.
When super SU asks that question, dont install via CWM, tell it to just install normally.
Once you have SuperSU working, Download Rom Manager from the play store and install CWM Recovery right from within the ROM Manager app.
It will give you the option to pick between two types of CWM(ClockWorkMod). The Touch version, like its name gives you the ability to use the touch screen and not only the volume up/down + Power button.
Telling it to install normally causes it to just tell me there was an error, it also tells me it is out of date as well. Titanium Backup tells me that it cant get root access and I was never asked about it.
OK, so your phone is not rooted then.
Your going to have to try rooting it again or flashing an already rooted rom with Odin.
I just tried it again, this time it said failure after the install of the superuser.apk. I just read that one of the later updates by samsung can make it harder to root. I just got my phone and i was fully updated. What Roms, are already rooted for the S4. I am actually enjoying some of the default apps that came with the phone.
Wicked (and most ROMs that don't include the [STOCK] tag) are pre-rooted...but you'll need to ODIN a custom recovery first then flash the ROM.
If you want to stay on rooted stock, follow the steps in the "root May 7 MDL" thread to ODIN a rooted kernel, and you'll be good to go.
(You don't need root access to get a custom recovery flashed)
Basically, any of your options are pretty straightforward, but they're going to involve Odin-ing stuff.
So there isn't really a way to just root my phone without installing a custom rom?
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
movieaddict said:
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Spud37 said:
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Click to expand...
Click to collapse
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
lazaro17 said:
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
Click to expand...
Click to collapse
Root checker says no root. I believe it does have that over the air update installed. T Mobile updated it when they gave me the phone, because they thought I didn't really know anything about phones. I assume this means I have to follow another method to root my phone?
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
ronin4740 said:
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
Click to expand...
Click to collapse
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Spud37 said:
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Click to expand...
Click to collapse
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Atmazzz said:
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Click to expand...
Click to collapse
Thank you so much, I am about to go and do this. I will use the kernel you suggested since that looks like a better option, after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Spud37 said:
after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
Click to expand...
Click to collapse
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
Spud37 said:
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Click to expand...
Click to collapse
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Atmazzz said:
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Click to expand...
Click to collapse
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Spud37 said:
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Click to expand...
Click to collapse
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Atmazzz said:
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Click to expand...
Click to collapse
Thank You so much. However it now seems like I have both Super User and SuperSU installed.
How did you root? Did you install the ROOT_M919?UVUAMDL zip and install SuperSU?
For some reason its passing in Odin and saying it worked. Go into the phone and phone isn't rooted. Tried about 9 times running Odin and its not working. It says in download mode that I'm running custom binary but its not installing Su Binary when i run Super SU. The CF-Auto-Root isn't also installing with this package.
I reverted back to stock 4.1 from 4.2 because it was not letting me use the OTA update fuction before this mess started so I thought I had to remove my root to begin with. Then after having many errors/crashes in 4.1 I had to factory reset then it let my update to 4.3. Well now I'm following the first post in the root with CF-Auto-Root thread and its not letting me "root" and install the SU Binary.
http://forum.xda-developers.com/showthread.php?t=1963812
Check out the last few pages of THIS thread. A few people claim to have gotten it done. Just be sure to read, and be sure of what going on before proceeding forward.
GOT IT!!!!
Thanks for the post it helped get my phone rooted, I had to follow the post you linked to get it rooted smoothly then this post |Guide|How-To| Root & Install Custom Recovery for 4.3 Update |22 Nov 2013| to get SuperSU and KNOX remover to get root working.
Seems the root was not taking with CF-Auto-Root like everyone else but TeamEpic-Root-from-Recovery-v5.zip worked from TWRP. I just had pop ups in Android saying security policy update had blocked a app from accessing anything. Flashed the SuperSU app with the Knox remover from recovery then rebooted and TA DA! SuperSu worked and wanted to update my Binary.
Hope this post finds it way to other users stuck in the same boat I was in cause the last couple days I've been staying up HOURS trying to root my phone!
Zspy1985 said:
Cool thanks I'm going to give the first post a whirl.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
If you did the OTA update, then you should be aware that you now have the Knox bootloader on your phone. Do not, under any circumstances, try to Odin back to 4.1.2, which has a different bootloader, which will brick your phone. And if you flash cwm through Odin, it won't brick, but will void your warranty by tripping the Knox counter(triangle away won't erase this one). But to get root, simply flash PhilZ latest recovery for this phone through Odin, reboot to recovery, and flash SuperSu update, reboot, profit. Both links are on the rim op below. Make sure you have SuperSu downloaded before you reboot to recovery, and uncheck auto reboot and f. Reset Time in Odin. Good luck!
http://forum.xda-developers.com/showthread.php?t=2546505
Sent from my SPH-L710 using Tapatalk
prboy1969 said:
Check out the last few pages of THIS thread. A few people claim to have gotten it done. Just be sure to read, and be sure of what going on before proceeding forward.
Click to expand...
Click to collapse
Which last few pages because you posted this about 4 days ago. Could you tell me which page number to look at please?
Just do the first page on how to root
Sent from my SPH-L710 using Tapatalk
tbudke said:
Which last few pages because you posted this about 4 days ago. Could you tell me which page number to look at please?
Click to expand...
Click to collapse
If you are on 4.3 Stock OTA, people are getting it done using THIS method. If you are on 4.1.2 then use the method on the thread HERE.
I have flashed twrp recovery over odin. I can only get into stock recovery though. Usual fix would be to remove battery b4 rebooting, but I can not make out the battery on this device - seems integrated / hidden.
I am running 4.4.2 KitKat. Trying to root it to debloat.
Any ideas? Maybe remove some startup scripts or Idk...
EDIT: I got word that it seems to be either some hash verification in the new android 4.4.x kernel or even a locked bootloader on top. Is that correct? And, if so, what would be a good course of action now?
More info can be found imo when googling for
Android 4.4 KitKat: Google Making Root Without Unlocked Bootloader Difficult?
Click to expand...
Click to collapse
(sry can't link)
JoeRifle said:
I have flashed twrp recovery over odin. I can only get into stock recovery though. Usual fix would be to remove battery b4 rebooting, but I can not make out the battery on this device - seems integrated / hidden.
I am running 4.4.2 KitKat. Trying to root it to debloat.
Any ideas? Maybe remove some startup scripts or Idk...
EDIT: I got word that it seems to be either some hash verification in the new android 4.4.x kernel or even a locked bootloader on top. Is that correct? And, if so, what would be a good course of action now?
More info can be found imo when googling for (sry can't link)
Click to expand...
Click to collapse
I don't know of any tablet that has user removable battery. I'm sure you have to be rooted before you can install a custom recovery. Are you using the rooting method in the development topic?
The question would be why you didn't use the recommended way of using Flashify to flash twrp?
Eddie Hicks said:
I don't know of any tablet that has user removable battery. I'm sure you have to be rooted before you can install a custom recovery. Are you using the rooting method in the development topic?
Click to expand...
Click to collapse
Yes. Would have posted there too had it been allowed. It is the method described in the t800 thread, where it says you should flash twrp via odin and then install SuperUser zip in TWRP.
kenkiller said:
The question would be why you didn't use the recommended way of using Flashify to flash twrp?
Click to expand...
Click to collapse
I thought that this was the way to do it. I have not read anything in that thread about flashify.
If flashify works with Android 4.4.2 I will dig into that. Does it?
JoeRifle said:
Yes. Would have posted there too had it been allowed. It is the method described in the t800 thread, where it says you should flash twrp via odin and then install SuperUser zip in TWRP.
I thought that this was the way to do it. I have not read anything in that thread about flashify.
If flashify works with Android 4.4.2 I will dig into that. Does it?
Click to expand...
Click to collapse
You did not follow the instructions in the first post, but the latter ones posted by bodivas? Then you should consider trying those in the first post - they work for T805 as well.
The ones in the first post work. Flashify I found it in the CF-Root for T700 thread, it works fine on T805 as well, as long as you get the correct img file from the TWRP site.
kenkiller said:
You did not follow the instructions in the first post, but the latter ones posted by bodivas? Then you should consider trying those in the first post - they work for T805 as well.
The ones in the first post work. Flashify I found it in the CF-Root for T700 thread, it works fine on T805 as well, as long as you get the correct img file from the TWRP site.
Click to expand...
Click to collapse
yes bodivas is his name. it seemed to be the better method. but since it did not "accept" the image, although odin said success, I dug deeper and found out that there is supposed to be a hash check in 4.4.2 which keeps me from keeping the flashed image
Will flashify solve that problem and make TWRP "resident"? I would rather not flash the CF Auto since it is for a t800 not t805, but maybe i am overcautious:angel:
JoeRifle said:
yes bodivas is his name. it seemed to be the better method. but since it did not "accept" the image, although odin said success, I dug deeper and found out that there is supposed to be a hash check in 4.4.2 which keeps me from keeping the flashed image
Will flashify solve that problem and make TWRP "resident"? I would rather not flash the CF Auto since it is for a t800 not t805, but maybe i am overcautious:angel:
Click to expand...
Click to collapse
You don't get by in XDA by being cautious in everything. There's enough reports to tell otherwise.
Yes, using Flashify to flash TWRP replaces stock recovery. TOTALLY.
Requires root though right? So is not possible for me I fear Only way would then be CF Auto for t800...as we found out. TU anyhow.
JoeRifle said:
Requires root though right? So is not possible for me I fear Only way would then be CF Auto for t800...as we found out. TU anyhow.
Click to expand...
Click to collapse
Of course it requires root. Not possible because you don't dare to flash the T800 files? Hehe.....you're gonna have a hard time here.
kenkiller said:
Of course it requires root. Not possible because you don't dare to flash the T800 files? Hehe.....you're gonna have a hard time here.
Click to expand...
Click to collapse
I just need to get the hang of these appy lil spy thingy thing things...god knows what g**gle has in store for you. out of curiosity, so you are saying there is no hash check in the bootloader keeping me/us from doing our evil deeds? how about the article up there I quoted, and what the heck happened when i odined TWRP?
just asking...will flash the CF. so lets cross thumbs and make tha knox trip count
Hi Guys. As following the instructions to flash openrecovery-twrp-2.8.0.1-chagallwifi.tar using Odin3 v3.09, my T805 reboots into recovery, the TWRP boot screen is blurred, and after the Menu appears, my device locks up and there is no way to reboot it. Force reboot by holding down the Power button doesn't work. I've been trying for nearly an hour and nothing works. The Task Menu and Return buttons are lit, but the screen is blank. Any suggestions on how to get my T805 to reboot normally?
Thanks.
UPDATE:
I found that 2.8.0.1 appears out of alignment on the screen, and I had to poke around until I found where the Reboot button was located. By chance I got it to go into Bootloader and the system rebooted. Once online I installed Flashify and installed TWRP 2.7.1.1 and SUCCESS!! Now my T805 is working normally. WHEW!!
I got a Galaxy S3 SPH-L710 and it was all ready updated to the L710VPUDOH1 baseband version. After searching around a little bit I noticed that most of the Roms are for baseband L710VPUDND8 and that some of the ND8 roms would not flash correctly.
I guess maybe i found a workaround for this. When i first tried to flash the CM 12.1 Rom I got error and it did not load. Did not hurt anything either. Was a little tricky getting initial root but got it all working.
Figured id share how i accomplished this in case someone else with the L710VPUDOH1 baseband wants to run the other Roms.
First i tried to root with Odin and the supersu.zip but it didnt take correctly.
Odin showed successful and the supersu flashed to the /system but every time i tried to run supersu I get Unfortunately SuperSU stopped working.
So i ended up using ODIN to get Temp CWM recovery and installed the CF-Autoroot in the CWM recovery. This woorked to get Root.
I downloaded the TWRP manager from playstore andused it to install TWRP 2.8.1.0
The TWRP Manager gave me an error but when i booted into recovery I had TWRP.
After that i tried to flash CM 12.1 in TWRP but got error and it didnt work.
I read that wicked 2.2 would load,
its big all most a gig so i figured it was pretty complete. maybe based off of stock.
I loaded it successfully.
afterwards i booted back into twrp and did an advanced wipe of.
Dalvic Cache
/ system
/data
/internal storage
/cache
Then i loaded Cm 12.1 with no issues.
Tested Pac-Rom No issues.
Im thinking any of the newer roms will flash fine now.
BigCountry907 said:
After that i tried to flash CM 12.1 in TWRP but got error and it didnt work.
Click to expand...
Click to collapse
I'm hoping you left out some steps, because if you tried flashing CM 12.1 without doing a wipe on System/Data/Cache/Dalvik then you will not have a working phone.
BigCountry907 said:
I got a Galaxy S3 SPH-L710 and it was all ready updated to the L710VPUDOH1 baseband version. After searching around a little bit I noticed that most of the Roms are for baseband L710VPUDND8 and that some of the ND8 roms would not flash correctly.
I guess maybe i found a workaround for this. When i first tried to flash the CM 12.1 Rom I got error and it did not load. Did not hurt anything either. Was a little tricky getting initial root but got it all working.
Figured id share how i accomplished this in case someone else with the L710VPUDOH1 baseband wants to run the other Roms.
First i tried to root with Odin and the supersu.zip but it didnt take correctly.
Odin showed successful and the supersu flashed to the /system but every time i tried to run supersu I get Unfortunately SuperSU stopped working.
So i ended up using ODIN to get Temp CWM recovery and installed the CF-Autoroot in the CWM recovery. This woorked to get Root.
I downloaded the TWRP manager from playstore andused it to install TWRP 2.8.1.0
The TWRP Manager gave me an error but when i booted into recovery I had TWRP.
After that i tried to flash CM 12.1 in TWRP but got error and it didnt work.
I read that wicked 2.2 would load,
its big all most a gig so i figured it was pretty complete. maybe based off of stock.
I loaded it successfully.
afterwards i booted back into twrp and did an advanced wipe of.
Dalvic Cache
/ system
/data
/internal storage
/cache
Then i loaded Cm 12.1 with no issues.
Tested Pac-Rom No issues.
Im thinking any of the newer roms will flash fine now.
Click to expand...
Click to collapse
I don't think the roms care if your on ND8 or NJ2 or whatever the latest is . You should also update twrp to 2.8.7.0 . Version 2.8.4.0 and on allow you to flash a new twrp version image right from recovery . 2.8.1.0 is pretty old . Best of luck with your new hobby .
Ya i didnt have any troubles.
Im currently working on 5 devices and writing sort of a kitchen.
But it dose way more than most kitchens. Even creates a CWM style backup over adb like onandroid.
I found a way to patch a factory recovery.img to flash files signed with my own keys and that kinda started it all.
Anyway Merry Christmas
what's the root method for DOH1? ;; I can't seem to find a thread specifically walking through the root method for the latest baseband and i have an old S3 and was thinking of playing around with it for a while for fun turn it into a light weight media player to save battery on my LG G4 since we all know how inconsistent and crap the battery can be with the G4 lol
The root is pretty easy.
I used this.
http://forum.xda-developers.com/showthread.php?t=1963812
Then just get Clockworkmod or TWRP recovery for the d2spr sphl710 and flash it.
After that load any rom you want
silvernirvash said:
what's the root method for DOH1? ;; I can't seem to find a thread specifically walking through the root method for the latest baseband and i have an old S3 and was thinking of playing around with it for a while for fun turn it into a light weight media player to save battery on my LG G4 since we all know how inconsistent and crap the battery can be with the G4 lol
Click to expand...
Click to collapse
Same as always, use odin to flash a .tar of twrp. Then use twrp to flash a .zip of SuperSU. Done
Doh1
Is there any rom working at Doh1 version?
bael616 said:
Is there any rom working at Doh1 version?
Click to expand...
Click to collapse
All of them
madbat99 said:
All of them
Click to expand...
Click to collapse
Really? I have been told there was nothing for the l710vpudoh1 version. Would you mind to help me out with this topic of flashing a rom, please? P.D: Sorry about my english.
bael616 said:
Really? I have been told there was nothing for the l710vpudoh1 version. Would you mind to help me out with this topic of flashing a rom, please? P.D: Sorry about my english.
Click to expand...
Click to collapse
Oh1 is not a version of the phone. It's just a build number.
Do you have the triband model? What carrier?
madbat99 said:
Oh1 is not a version of the phone. It's just a build number.
Do you have the triband model? What carrier?
Click to expand...
Click to collapse
Got no idea. It is the sprint CDMA version.
bael616 said:
Got no idea. It is the sprint CDMA version.
Click to expand...
Click to collapse
Well that's what you need to know. Oh1 doesn't matter. There is oh1 for regular s3 and triband s3. Regular is sph-L710 and triband is sph-L710t. Does it have a t at the end of the model number?
madbat99 said:
Well that's what you need to know. Oh1 doesn't matter. There is oh1 for regular s3 and triband s3. Regular is sph-L710 and triband is sph-L710t. Does it have a t at the end of the model number?
Click to expand...
Click to collapse
It doesn't have any t. So I guess it Ies the regular one. I want to know how to root it and flash a rom.
bael616 said:
It doesn't have any t. So I guess it Ies the regular one. I want to know how to root it and flash a rom.
Click to expand...
Click to collapse
To root, you need odin on your PC. You can get it here.
Use odin to flash twrp recovery. You can get twrp from their site. twrp
Get the .tar of the newest build for d2spr (sprint s3). Put it on you PC somewhere you can find it (download folder is fine)
There are tutorials everywhere for using odin. It's the way to root almost all Samsung phones.
You also need the Samsung drivers on your PC. I don't have a link for that at this moment.
Then launch odin on your PC.
Put phone in download mode (from powered off, hold power+home+volume down)
Plug phone in to PC and odin should say "added"
Click AP button in odin then navigate to where you have the Twrp .tar downloaded and select it
Click start in odin.
When it finishes it should say pass.
Don't let the phone boot to system, unplug it and take out battery
Put batter back in and boot directly to twrp recovery by holding power+home+VOLUME UP
In twrp select reboot, then system. It should say you don't have root and ask if you want root. Swipe the arrow for yes. Once it boots, open SuperSU and update binaries if it asks. Choose normal method.
Done. Rooted.
You should really have looked up how to root before coming to a thread about flashing roms. There are tutorials everywhere for rooting this phone. Google is your friend dude.
Edit: you can get the Samsung USB drivers here
That thread has rooting instructions too. It's for the virgin Mobile s3, but its the same phone. Those instructions work fine. Only difference is I linked you to twrp recovery instead of philztouch (philz development is dead) and I linked you to a newer odin.
If you are that new that you aren't sure about rooting, maybe start over there in Android forums. I'm a guide there.
bael616 said:
Really? I have been told there was nothing for the l710vpudoh1 version. Would you mind to help me out with this topic of flashing a rom, please? P.D: Sorry about my english.
Click to expand...
Click to collapse
I was given a SPH-L710... Originally purchased from sprint.... Currently activated on boost. I got the phone Dec. 24 2015. It had stock unrooted DOH1 with untripped warranty bit. I have successfully booted and ran these roms for a minimum of 24 hrs each. As far as I could tell they were fully functional including: 4G LTE, MMS send and recieve, hotspot, wifi, bluetooth, camera (still and video). All main fuctions worked correctly for the limited time that I used each rom. :
-Wicked-X-Bare-Bones.zip
-Wicked-X-v8.2.zip
-cm-11-20150831_SNAPSHOT-XNG3CAO3FN-d2lte.zip
-cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
-cm-12.1-20160202-NIGHTLY-d2spr.zip
-cm-13.0-20160130-UNOFFICIAL-d2spr.zip
Im currently running CM13 unofficial as a daily driver. Cm12.1 SNAPSHOT was also very responsive and gave me no problems. I flashed them with twrp.2.8.7.2-d2spr.img. i flashed the recovery with odin after i made it into a .tar.md5 using linux mint 17.3 cinnamon. For the lte and mms i used "apn backup and restore" from google play with the root explorer method. Open gapps aroma for each android version i got from cyanogenmod website. i would recommend searching and using the dd command with adb shell in a linux terminal or cygwin to backup every partition on your doh1 first. (You will need root and busybox) There should be 24 partitions in mmcblk0. Make a backup of every one and you can recover one way or another ALMOST regardless of what may or may not go wrong. I used supersu 2.65 zip. Ive had alot of issues due to DOH1 but all the resources are in that easily used omnibox. Hope any of this info helps you.
madbat99 said:
To root, you need odin on your PC. You can get it here.
Use odin to flash twrp recovery. You can get twrp from their site. twrp
Get the .tar of the newest build for d2spr (sprint s3). Put it on you PC somewhere you can find it (download folder is fine)
There are tutorials everywhere for using odin. It's the way to root almost all Samsung phones.
You also need the Samsung drivers on your PC. I don't have a link for that at this moment.
Then launch odin on your PC.
Put phone in download mode (from powered off, hold power+home+volume down)
Plug phone in to PC and odin should say "added"
Click AP button in odin then navigate to where you have the Twrp .tar downloaded and select it
Click start in odin.
When it finishes it should say pass.
Don't let the phone boot to system, unplug it and take out battery
Put batter back in and boot directly to twrp recovery by holding power+home+VOLUME UP
In twrp select reboot, then system. It should say you don't have root and ask if you want root. Swipe the arrow for yes. Once it boots, open SuperSU and update binaries if it asks. Choose normal method.
Done. Rooted.
You should really have looked up how to root before coming to a thread about flashing roms. There are tutorials everywhere for rooting this phone. Google is your friend dude.
Edit: you can get the Samsung USB drivers here
That thread has rooting instructions too. It's for the virgin Mobile s3, but its the same phone. Those instructions work fine. Only difference is I linked you to twrp recovery instead of philztouch (philz development is dead) and I linked you to a newer odin.
If you are that new that you aren't sure about rooting, maybe start over there in Android forums. I'm a guide there.
Click to expand...
Click to collapse
Thanks a lot. I have already rooted the phone but now I want to know what Roms are made to this device.
---------- Post added at 05:28 AM ---------- Previous post was at 05:24 AM ----------
HouseHG said:
I was given a SPH-L710... Originally purchased from sprint.... Currently activated on boost. I got the phone Dec. 24 2015. It had stock unrooted DOH1 with untripped warranty bit. I have successfully booted and ran these roms for a minimum of 24 hrs each. As far as I could tell they were fully functional including: 4G LTE, MMS send and recieve, hotspot, wifi, bluetooth, camera (still and video). All main fuctions worked correctly for the limited time that I used each rom. :
-Wicked-X-Bare-Bones.zip
-Wicked-X-v8.2.zip
-cm-11-20150831_SNAPSHOT-XNG3CAO3FN-d2lte.zip
-cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
-cm-12.1-20160202-NIGHTLY-d2spr.zip
-cm-13.0-20160130-UNOFFICIAL-d2spr.zip
Im currently running CM13 unofficial as a daily driver. Cm12.1 SNAPSHOT was also very responsive and gave me no problems. I flashed them with twrp.2.8.7.2-d2spr.img. i flashed the recovery with odin after i made it into a .tar.md5 using linux mint 17.3 cinnamon. For the lte and mms i used "apn backup and restore" from google play with the root explorer method. Open gapps aroma for each android version i got from cyanogenmod website. i would recommend searching and using the dd command with adb shell in a linux terminal or cygwin to backup every partition on your doh1 first. (You will need root and busybox) There should be 24 partitions in mmcblk0. Make a backup of every one and you can recover one way or another ALMOST regardless of what may or may not go wrong. I used supersu 2.65 zip. Ive had alot of issues due to DOH1 but all the resources are in that easily used omnibox. Hope any of this info helps you.
Click to expand...
Click to collapse
Thanks man is there any link you can share with me? I really want to flash a rom but there is no one with this device in Facebook groups. So if you can share any Rom and the way it should be flashed I will be really thankful.
P. D: as I mentioned before I have no perfect English skills so I hope you understand what I mean.
bael616 said:
Thanks a lot. I have already rooted the phone but now I want to know what Roms are made to this device.
---------- Post added at 05:28 AM ---------- Previous post was at 05:24 AM ----------
Thanks man is there any link you can share with me? I really want to flash a rom but there is no one with this device in Facebook groups. So if you can share any Rom and the way it should be flashed I will be really thankful.
P. D: as I mentioned before I have no perfect English skills so I hope you understand what I mean.
Click to expand...
Click to collapse
I cant post links due to my total number of posts. PM me and I'll send them to you.
bael616 said:
Thanks a lot. I have already rooted the phone but now I want to know what Roms are made to this device.
---------- Post added at 05:28 AM ---------- Previous post was at 05:24 AM ----------
Thanks man is there any link you can share with me? I really want to flash a rom but there is no one with this device in Facebook groups. So if you can share any Rom and the way it should be flashed I will be really thankful.
P. D: as I mentioned before I have no perfect English skills so I hope you understand what I mean.
Click to expand...
Click to collapse
You have the sprint s3, but are you on sprint? If you are not on Sprint there are additional instructions. Any rom that says its for D2spr is fine. That's the sprint s3.
this is the one I'm using.
HouseHG said:
I cant post links due to my total number of posts. PM me and I'll send them to you.
Click to expand...
Click to collapse
Ok man thanks
---------- Post added at 01:39 AM ---------- Previous post was at 01:35 AM ----------
madbat99 said:
You have the sprint s3, but are you on sprint? If you are not on Sprint there are additional instructions. Any rom that says its for D2spr is fine. That's the sprint s3.
this is the one I'm using.
Click to expand...
Click to collapse
Actually, I don't use any company cause I don't live in the US so I use the phone only with WiFi.
**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.
balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
Fixed!
koop1955 said:
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.
Click to expand...
Click to collapse
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).
JoeFCaputo113 said:
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).
Click to expand...
Click to collapse
I wasn't sure if CM13 is already working on International phones.
I only know what I read....
From Chainfire's post:
Rooting procedure:
- flash/upgrade to Marshmellow
- flash modified boot.img
- flash/boot TWRP and sideload latest...
Joe, be careful if you try this. Looks like you need to Odin back to stock.
Does this still void knox?
1619415 said:
Does this still void knox?
Click to expand...
Click to collapse
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.
koop1955 said:
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.
Click to expand...
Click to collapse
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox
1619415 said:
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox
Click to expand...
Click to collapse
Well Merry Christmas!
JoeFCaputo113 said:
Well Merry Christmas!
Click to expand...
Click to collapse
You to
---------- Post added at 01:52 PM ---------- Previous post was at 01:01 PM ----------
Has anyone tried rooting with this method and trying samsumg pay?
Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.
todivefor said:
Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.
Click to expand...
Click to collapse
Try Number 15
1619415 said:
Try Number 15
Click to expand...
Click to collapse
Thanks. Been there done that.
Sent from my SM-T710 using Tapatalk
For those asking about whether this root method trips knox or not. Yes this will trip knox. Anytime you use odin to flash non official Samsung firmware/software then it forever trips knox. Therefore flashing any custom recovery will absolutely trip knox... forever.
Samsung and Android pay apps will not work on rooted devices. Period. The pay apps are intended for official factory software for obvious reasons. Security is the main focus with these types of apps that deal with your personal banking/credit card information. Hence a rooted device is not considered "secure".
using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.
yaibakt said:
using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.
Click to expand...
Click to collapse
Try installing/updating busybox and try removing titanium backups root access them regrant it
JoeFCaputo113 said:
**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.
Click to expand...
Click to collapse
Nice work will give this a go soon.
1619415 said:
Try installing/updating busybox and try removing titanium backups root access them regrant it
Click to expand...
Click to collapse
thank you. ill give it a try. :good:
This may be a weird question, but we don't have a stock kernel to flash. Would there be a way to make a zip of a stock kernel and then use this to get root? I'd like to have a custom ROM but with the stability of a stock Kernel. This is the first phone I can think of that I've owned that didn't have a stock kernel with root.