I'm trying to update an old Note 10.1 n8010 to a recent Android version so we can use modern apps.
I'm trying to follow instructions, but some of what I've followed appears to be out of date, missing files at linked URLs, etc.
My understanding is that I need to get TWRP installed, and then a ROM like the LineageOS 14.1 Nougat or the LineageOS 14.1 threads on the development forum here.
At this stage I have Kies installed on Windows PC, I have the Android SDK unzipped on the PC. I have got as far as getting into download mode on the tablet showing "ODIN MODE" in red at the top.
Now I'm not sure how to continue, as I thought I had TWRP installed on the tablet, but when I try to get to it, I see this.
Can anyone help me to get to the next step?
The answer, for anyone coming across this in future, was that TWRP is not Power+Vol Down, it's Power+Vol UP
Related
For Tab 2 P3100:
I'm a stranger to flashing Android ROMs, and it's hardly a surprise that after 2 hours of struggling with my rooting and then flashing, Cyanogenmod gets stuck on the blue-circles load screen.
Cause of the problem would likely be that I unknowingly flashed in the newest nightly release, which was unstable. All stock roms I've encountered either don't allow me to load it from Odin because it's not a .md5, or it takes hours to download (and the server likely cuts me off before I'm done).
I've been roaming these boards (and others) for a long while, but there's been no easy way to unscrew the Cyanogenmod up without those stock roms that have to be downloaded from failing servers with terrible download rates and cut me off. Any help on how to easily recover it with any working ROM in any way (even if it unroots the device) would be appreciated. (Got to lower my standards by now!)
Alternatively, are there any custom ROMs out there that flash straight from Odin instead of from ROM Manager (I don't know how to make Cyanogenmod flash from Odin)? With the OS stuck in boot I obviously can't open ROM Manager app to flash a new one...
Side note: Clockwork Recovery is definitely on my Tab, but using Vol.Up and Power buttons won't conjure it (although Vol.Down and Power does conjure my Odin). Therefore my plight.
icehawk_1995 said:
For Tab 2 P3100:
Side note: Clockwork Recovery is definitely on my Tab, but using Vol.Up and Power buttons won't conjure it (although Vol.Down and Power does conjure my Odin). Therefore my plight.[/I]
Click to expand...
Click to collapse
Make sure you hold the Power and vol + until you see the Samsung Tab2 and then keep holding the vol+ a little longer till Recovery starts to load.
Here is a good video on installing CM 10.2 with download links in the description area.
https://www.youtube.com/watch?v=uooLuG0Ydr8
Try wiping data from recovery.
You know, it's a sad day when your cellular service is faster than your home broadband.
Hi, thanks for your replies.
I've made some progress, because I could load my default ROM again via Odin, so I can sustainably retry different Cyanogenmod builds.
Sadly, I've tried the latest nightly build, release candidate and stable release, and ALL of them have gotten stuck during booting (at the cyanogenmod spinning circle).
I have since tried to reformat the device and clear the cache, but that apparently hasn't been working as well.
Regarding the YouTube tutorial video shared above, I tried following the steps exactly, but it appears that my Clockworkmod Recovery mode screen looks quite different from the one in the video, and mine doesn't have some of the options it has. (I did use ROM Manager to automatically download CWM Recovery, not sure what is wrong with that). In any case, I still can't conjure Recovery mode from Vol.Up + Power button--I can only access it by using the ROM Manager app and clicking restart into Recovery.
Is there a similar error to what I'm experiencing? Because so far I still haven't found a thread that has a resolved issue with my device's symptoms.
Thanks for any help again!
Thanks for your help, particularly the YouTube tutorial video link that concisely showed me how the successful install looks like.
Turns out the CWM Recovery that ROM Manager automatically downloaded and flashed for me the first couple of times was an outdated/screwed up one that didn't work properly (ie. couldn't follow every step in the video because some features required in the video's steps were unavailable).
For future reference, if anyone encounters the same problem I did, it's something wrong with the Clockworkmod Recovery version, no doubt. For some reason, one fine instance like any other, ROM Manager finally got it right and installed the right version of CWM Recovery and I can now access all the features, and pressing Vol.Up + Power does conjure the Recovery Mode now.
Thanks for helping me fix my tablet, guys. I kinda absolutely hate TouchWiz UI and Cyanogenmod is indeed miles ahead. Happily running the latest nightly build of 10.2, loving it.
Cyanegonmod stuck
I cant reboot system , I have tried everything but wipe data/system restore. everytime it goes back to same screen. Now I am getting error messages while back and restoring image of data. I my be just not familiar but it shows my recovery files dated back to 2000 and 2010. How could the date change.
Hello, I hope I'm posting to the right forum, because I haven't been able to root my phone (Samsung Galaxy A5 2016) no matter what I tried.
The classic procedure is that you go to cf-auto-root and download the version for your phone (mine is SM-A510F). I donwloaded that, which also includes Odin 3.10.6. files.
So then I turn off my phone, set it to the download mode by holding the volume down button, home button and power button at the same time.
Then I press the volume up button to continue to the download mode. Once I'm there, I plug the phone to the PC and open Odin. In Odin, I then see "Added" and I can also see the blue line indicating that I've got all the necessary Samsung drivers already installed (I even re-installed them a bunch of times, just to make sure that it's not the cause of the problem).
Then I click on AP in Odin and add the cf-auto-root file with the ".tar.md5" extension. Then I let everything load and initialize and I click on "Start".
That process takes a while and I can also see the loading bar working on the phone itself. Then the phone restarts and I can see "PASS" in the Odin. However, the phone itself never goes to the recovery mode to enable some of the superuser features, but it straight goes to the Samsung logo screen, where I can see on the top left corner: "Recovery is not seandroid enforcing." Also, I'm sure that I've got the latest firmware with Android Marshmallow 6.0.1. update and also have all the developer options enabled on the phone, like USB debugging and OEM Unlock.
I tried almost every possible tutorial on google and youtube, but I just can't seem to be able to root it properly, even though I'm taking the right steps.
I would really appreciate if you guys, who are experienced with rooting, could help me with this Thank you so much, and Happy New Year 2017!
XDA Visitor said:
Hello, I hope I'm posting to the right forum, because I haven't been able to root my phone (Samsung Galaxy A5 2016) no matter what I tried.
The classic procedure is that you go to cf-auto-root and download the version for your phone (mine is SM-A510F). I donwloaded that, which also includes Odin 3.10.6. files.
So then I turn off my phone, set it to the download mode by holding the volume down button, home button and power button at the same time.
Then I press the volume up button to continue to the download mode. Once I'm there, I plug the phone to the PC and open Odin. In Odin, I then see "Added" and I can also see the blue line indicating that I've got all the necessary Samsung drivers already installed (I even re-installed them a bunch of times, just to make sure that it's not the cause of the problem).
Then I click on AP in Odin and add the cf-auto-root file with the ".tar.md5" extension. Then I let everything load and initialize and I click on "Start".
That process takes a while and I can also see the loading bar working on the phone itself. Then the phone restarts and I can see "PASS" in the Odin. However, the phone itself never goes to the recovery mode to enable some of the superuser features, but it straight goes to the Samsung logo screen, where I can see on the top left corner: "Recovery is not seandroid enforcing." Also, I'm sure that I've got the latest firmware with Android Marshmallow 6.0.1. update and also have all the developer options enabled on the phone, like USB debugging and OEM Unlock.
I tried almost every possible tutorial on google and youtube, but I just can't seem to be able to root it properly, even though I'm taking the right steps.
I would really appreciate if you guys, who are experienced with rooting, could help me with this Thank you so much, and Happy New Year 2017!
Click to expand...
Click to collapse
Hello and welcome to Assist
According to this threadyou need to flash twrp recovery before rooting the A5 2016 series.
If you follow the instructions posted there, I'm sure you'll have success rooting your device
If you have further questions and want to post in the thread, please register an account first
Good luck and welcome to XDA
Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
J727P
Nupid Stoob said:
Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
Click to expand...
Click to collapse
ok you have an older phone the J700P you can start by downloading odin an twrp recovery an superSU zip you can get twrp from here !https://twrp.me/devices/samsunggalaxyj72015qcomsprint.html
an odin from here
https://mega.nz/#!nYVDXBAC!_cTWbW4_Ow8sZMWcZvO7bVwEEBFlD1DQsB5NeFhj1EY
An just google latest superSU zip to find that !
good luck !
step 1 enable oem in development settings !
step 2 put phone into download mod an flash twrp then boot into twrp recovery an flash superSU zip !
Thank you for the info. I'm presently confused. Here's what I've done:
I ran Odin and flashed with twrp-3.2.1-0-j7ltespr.img.tar. It went through successfully going off odin's message.
Vol. up + home + power. It'll eventually show a yellow triangle with the white trash can guy on it's side stating "No Command". Power + up gets the Android Recovery screen.
At this point, am I supposed to choose the Wipe Data/factory reset option? I see tuts that seem suggest I should already be in the twrp UI or something. I've tried watching vids and looking at a handful of tuts, but either they are the wrong phone, too old, the button combos show something else entirely, etc.
Thanks!
Anyone? Videos show the buttons vol. up + home + power as booting right into twrp recovery gui. For me, it's going into "Android Recovery" screen. Is there an extra step with Odin or something that I missed? Or am I supposed to wipe/boot in the Android Recovery screen and it'll boot the twrp recovery gui? If bricking something I'm not familiar with wasn't a concern, I'd be courageous with it.
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
J700P
Nupid Stoob said:
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
Click to expand...
Click to collapse
Ok when flashing twrp with Odin first uncheck auto reboot in options flash twrp pull battery replace battery an boot into twrp an flash superSU zip then reboot system !
Thank you so much Peter! That did the trick THANK YOU :good:
For posterity to anyone else w/limited root knowledge with a SM-J700P Virgin variant running 7.1.1 (and what was most recent factory updates until this point); Flashed the twrp-3.2.1-0-j7ltespr.img.tar again w/o auto reboot in options of Odin, pulled battery once safe (i.e. you get the "Pass" message from Odin confirming everything went as planned) to get out of the downloading screen, replaced battery, booted the recovery (vol up + power + home) and it finally booted into the twrp recovery gui. Selected the "Install" option, then went to where the supersu.zip was stored on the SD (I created a separate "supersu" folder via PC connection for easy locating; internal phone memory card looks to now be unlocked, so can most likely use that if you don't have a SD card). Checked the "reboot once installed option" in the gui box and swiped to install supersu,zip and verified it was rooted via app after phone fully booted back up.
BTW, If anyone gets a hang/crash in Odin immediately after trying to select a twrp tar image in the "AP" box, try downloading the twrp image via PC instead of the through the phone (the legit twrp site that has the repository of past/current .tar), and just put it somewhere like Odin folder on desktop. Somehow, mine were getting corrupted via phone download through the twrp app, and Odin would NOT recognize the file was bad/corrupt when trying to select it via the AP box and hangs instead of giving a warning message. I ran into this earlier on then noticed the file was too small for some reason after viewing it on my PC, hence the Odin hang that needed a task manager kill.
I hate to necro an old thread but I still do not want to create an entire new topic for a single question. If I was to follow this info will it wipe the phone or will it simply root it while keeping all data on the phone? I ask as it is my wife's old phone and she would be pissed if I wiped her apps and everything on accident since she wont be able to remember what she had.
Edit: also when I add the TWRP file to odin it immediately hang/crashes like OP mentions but I am already DLing via pc. any thoughts?
Hi folks, I’m not finding the CORRECT info on what I need to reset my phone. The following is what I have gleaned (& used) from the web sources etc.
Phone details: S6 SM-G920W8, was rooted and running Oreo quite happily (aside from telephony)
Was changing, using a TWRP BU to a Nougat TWRP BU ROM something went wrong!!!
Only have access to Odin: (Vol -/Home/Power buttons
Not able to use: Vol+/Home/Power buttons response
Used Odin to install the following file, G920W8VLS6DRC1_G920W8OYA6DRC1_G920W8VLS6DRC1_HOME.tar.md5. It installs giving off the following: Pass in Odin. Phone then Reboots after install to “System Update” then “Erasing”, then Samsung Logo then "Android is starting up". After this it just loops between Logo & Android Starting.
The other file, G920W8VLU5DQD4_G920W8OYA5DQD4_G920W8VLU5DQD4_HOME.tar.md5 (just checks the MD5,hit start then “Fails”
Using Odin 3.13.1 & Samsung Drivers are installed.
Anyone point me as to what I’m doing wrong please??
The 2 files used are:
G920W8VLU5DQD4_G920W8OYA5DQD4_G920W8VLU5DQD4_HOME.tar.md5
G920W8VLS6DRC1_G920W8OYA6DRC1_G920W8VLS6DRC1_HOME.tar.md5
C'mon guys! Someone must have some advice/help with all the expertise on this site. If the post doesn't make sense, please tell me & I'll try to re-phrase it. All I want to do is to get it up & running again in some shape or other. I have a pile of TWRP backups but no way to install them, so, I have to use Odin for something (as in the 2 .img files I referred to).
PLEASE help me!
gpreen said:
Hi folks, I’m not finding the CORRECT info on what I need to reset my phone. The following is what I have gleaned (& used) from the web sources etc.
Phone details: S6 SM-G920W8, was rooted and running Oreo quite happily (aside from telephony)
Was changing, using a TWRP BU to a Nougat TWRP BU ROM something went wrong!!!
Only have access to Odin: (Vol -/Home/Power buttons
Not able to use: Vol+/Home/Power buttons response
Used Odin to install the following file, G920W8VLS6DRC1_G920W8OYA6DRC1_G920W8VLS6DRC1_HOME.tar.md5. It installs giving off the following: Pass in Odin. Phone then Reboots after install to “System Update” then “Erasing”, then Samsung Logo then "Android is starting up". After this it just loops between Logo & Android Starting.
The other file, G920W8VLU5DQD4_G920W8OYA5DQD4_G920W8VLU5DQD4_HOME.tar.md5 (just checks the MD5,hit start then “Fails”
Using Odin 3.13.1 & Samsung Drivers are installed.
Anyone point me as to what I’m doing wrong please??
The 2 files used are:
G920W8VLU5DQD4_G920W8OYA5DQD4_G920W8VLU5DQD4_HOME.tar.md5
G920W8VLS6DRC1_G920W8OYA6DRC1_G920W8VLS6DRC1_HOME.tar.md5
Click to expand...
Click to collapse
The First File (G920W8VLS6DRC1) it flashes ok because the bootloader on your phone is "6" (Thats the fifth number in that file name) the second it fails because the Bootloader is version 6 so is only accepting version "6" and not "5" (G920W8VLU5DQD4).
To fix your problem turn off your phone pressing Vol- + Power. Keep pressing Vol+ + Home + Power (the three at the same time). its going to boot on recovery. its going to appear an Android with an X and under it "No Command (keep calm this is normal). let it there without touching anything until the recovery appears, then wipe Data+Cache and reboot it should be fixed by now.
Many, Many Thanks Razor001_. Worked like a charm once I let the Android "No Command" sit a few seconds. If only I had left it alone and been more patient with it! You truly saved me (Well my old phone anyway!).
Thanks again for your help and input.
As an aside, would I be correct that when it first went wrong and went into the Factory Reset mode, would it have installed the last version of my rooted ROM?? Please say "no" and don't make me cry with a "yes"!
Hi folks
following the tutorial I posted many years back, here is my updated instructions for Android upgrade. After much research, I decided to go for Android 6 (Marshmallow) - to be honest, Nougat and others just seem to slow on the device - and anything is better than ICS (the stock).
Note - in all tutorials I have seen, the key combination for the GT P5110 to get into download mode appears to be to press simultaneously, the Power button with the volume rocker closest to the power button (Volume Up). However, with my device (Australian device?) the Volume Up key is FURTHEST away from the power button. So if you are having issues, that could be why and you may need to try reversing which buttons you are pressing!
Here are the tools you need:
1) I did a stock reset for my GT-p5110. The p5110 stock rom I got from here, but any google search will help you - you don't have to take this step as you're going to wipe it anyway, but I wanted to know how to do it so I could revert any time I wanted.
2) To install any newer Android versions, you need TWRP on your p5110 espressowifi .
TWRP will allow you to add custom Android version in future steps and is an easier way to manage the device. I took Common TWRP version from Android Andi from here (I used 3.2.3.0 .tar.md5 - ensure to get the one that is right for your device.). Download it to your PC then flash to device using ODIN (I used ODIN version 3-13-1).
3) After flashing TWRP with ODIN, restart the device using power and volume up - it should boot into TWRP. Once you are in TWRP, do a basic wipe and then you can install lineage 13-0 from Android Andi here annoyingly this seems to overwrite TWRP with cyanmod and I had to reinstall TWRP again via ODIN
4) Reboot device and Lineage13 should now be installed..
5) If you want Google Apps such as playstore etc, you can install from reading the WIKI here - I did it after checking that LOS13 was loading fine. So if you do it that way, you then must launch back into TWRP, do a factory reset, then install GAPPS - I suggest you choose the smallest package (pico).
6) restart device and...... if all goes well, you should be up and running. In my experience Lineage13 is faster and pretty stable than the later versions, but the GAPPS really slows down the machine.
I am still evaluating this set up and will update this thread at some point.
*deleted*
clappertrap said:
Hi folks
following the tutorial I posted many years back, here is my updated instructions for Android upgrade. After much research, I decided to go for Android 6 (Marshmallow) - to be honest, Nougat and others just seem to slow on the device - and anything is better than ICS (the stock).
Note - in all tutorials I have seen, the key combination for the GT P5110 to get into download mode appears to be to press simultaneously, the Power button with the volume rocker closest to the power button (Volume Up). However, with my device (Australian device?) the Volume Up key is FURTHEST away from the power button. So if you are having issues, that could be why and you may need to try reversing which buttons you are pressing!
Here are the tools you need:
1) I did a stock reset for my GT-p5110. The p5110 stock rom I got from here, but any google search will help you - you don't have to take this step as you're going to wipe it anyway, but I wanted to know how to do it so I could revert any time I wanted.
2) To install any newer Android versions, you need TWRP on your p5110 espressowifi .
TWRP will allow you to add custom Android version in future steps and is an easier way to manage the device. I took Common TWRP version from Android Andi from here (I used 3.2.3.0 .tar.md5 - ensure to get the one that is right for your device.). Download it to your PC then flash to device using ODIN (I used ODIN version 3-13-1).
3) After flashing TWRP with ODIN, restart the device using power and volume up - it should boot into TWRP. Once you are in TWRP, do a basic wipe and then you can install lineage 13-0 from Android Andi here annoyingly this seems to overwrite TWRP with cyanmod and I had to reinstall TWRP again via ODIN
4) Reboot device and Lineage13 should now be installed..
5) If you want Google Apps such as playstore etc, you can install from reading the WIKI here - I did it after checking that LOS13 was loading fine. So if you do it that way, you then must launch back into TWRP, do a factory reset, then install GAPPS - I suggest you choose the smallest package (pico).
6) restart device and...... if all goes well, you should be up and running. In my experience Lineage13 is faster and pretty stable than the later versions, but the GAPPS really slows down the machine.
I am still evaluating this set up and will update this thread at some point.
Click to expand...
Click to collapse
thanks for this info, it's all working well. I was just wondering if it's possible to install newer versions of Lineage too please?
mc.dodd said:
thanks for this info, it's all working well. I was just wondering if it's possible to install newer versions of Lineage too please?
Click to expand...
Click to collapse
You were able to successfully get your GT-51xx above Android 4?
Granted, It's been years since I've installed any custom Android versions on a device...but I've spent several days trying to get my GT-5110 to anything Above Android 5, as most apps refuse to run on Android 4.x, and I'm hitting snags at every step basically. Just curious to know if you successfully did it, and its working before I keep wasting my time on this tablet.
So frustrating that I have so many expensive devices for their time, that are not useable because Samsung makes it so difficult to keep alive after they move on. The hardware is perfectly capable of doing everything I need...but Samsung wants it to go to the landfill.