Related
Hey guys, first of all I'm a complete n00b to all of this stuff, so please bear with me and consider using layman type language with me. Some of you may think I shouldn't even be messing with this stuff with my limited knowledge, but I'm determined to get the best out of my Galaxy Nexus and generally learn quickly and follow directions well.
Here's the bullet-point run-down of what happened:
- Bought a Galaxy Nexus that was "yakjuux" and wasn't getting updates.
- Read through a thread on here on how to flash to "yakju". Did so successfully.
- I then wanted to root since my device was already wiped from unlocking bootloader or flashing some partition or something
- Followed this thread (http://forum.xda-developers.com/showthread.php?p=19583168#post19583168)
- Rebooted, saw the "Superuser" app and thought I nailed it.
- Saw an update for Jellybean, it requested a reboot before install
- Upon reboot I got a dreaded android on it's back with a red exclamation, nearly wet myself. Took battery out, put back in, phone booted normally. It didn't update to JB anymore and when I check for updates it doesn't show. I figured it'll come around again.
- Went to "superuser" app to update, it said it "Failed!" upon trying to gain root access. Upon reading around, downloaded SU Update Fixer from the store, failed gaining root access. Read some more, downloaded "Root Checker" app and it said my device was not rooted.
So where do I go from here? I'm tempted to just follow the 'flash to yakju' thread again and go back to a clean ROM and forget rooting, but maybe there's something simple I can do from here.
** One side note, in that rooting thread I mentioned above, I did not understand step #7 (7. Using CWM recovery, install su.zip that you downloaded in step 1) too clearly. I didn't understand how my phone could even get the su.zip file. So after reading some other rooting methods, I copy and pasted the .zip into the "Internal Storage" drive under My Computer > Samsung Phone > Internal Storage. Then using CWM Recovery on my phone just selected to install it from sdcard (since the Gnex doesn't have an sdcard) and it seemed to be a success. But I'm not sure if that was right. I assumed it was since I got the Superuser app.
Another thing that felt kind of wrong is that, when I flashed to yakju, it wiped my phone clean. I expected rooting to do the same thing, but it didn't (I think because my bootloader was already unlocked?). So I'm not sure if that has anything to do with it either.
Please help. And remember to please refer to things in dummy form. I only know things that involve the above, like using the cmd and typing fastboot and flashing files from a directory, etc.
Thank you in advance.
BryMerc said:
Hey guys, first of all I'm a complete n00b to all of this stuff, so please bare with me and consider using layman type language with me. Some of you may think I shouldn't even be messing with this stuff with my limited knowledge, but I'm determined to get the best out of my Galaxy Nexus and generally learn quickly and follow directions well.
Here's the bullet-point run-down of what happened:
- Bought a Galaxy Nexus that was "yakjuux" and wasn't getting updates.
- Read through a thread on here on how to flash to "yakju". Did so successfully.
- I then wanted to root since my device was already wiped from unlocking bootloaderor or replace some partition or something
- Followed this thread (http://forum.xda-developers.com/showthread.php?p=19583168#post19583168)
- Rebooted, saw the "Superuser" app and thought I nailed it.
- Saw an update for Jellybean, it requested a reboot before install
- Upon reboot I got a dreaded android on it's back with a red exclamation, nearly wet myself. Took battery out, put back in, phone booted normally. It didn't update to JB anymore and when I check for updates it doesn't show. I figured it'll come around again.
- Went to "superuser" app to update, it said it "Failed!" upon trying to gain root access. Upon reading downloaded SU Update fixed from the store, failed gaining root access. Read some more, downloaded "Root Checker" app and it said my device was not rooted.
So where do I go from here? I'm tempted to just follow the 'flash to yakju' thread again and go back to a clean ROM and forget rooting, but maybe there's something simple I can do from here.
One side note, in that rooting thread I mentioned above, I did not understand step #7 (7. Using CWM recovery, install su.zip that you downloaded in step 1) too clearly. I didn't understand how my phone could even get the su.zip file. So after reading some other rooting methods, I copy and pasted the .zip into the "Internal Storage" drive under My Computer > Samsung Phone > Internal Storage. Then using CWM Recovery just selected to install it from sdcard (since the Gnex doesn't have an sdcard) and it seemed to be a success. But I'm not sure if that was right. I assume it was if I got the Superuser app.
Please help. And remember to please refer to things in dummy form. I only know things that involve the above, like using the cmd and typing fastboot and flashing .img files from a directory, etc.
Thank you in advance.
Click to expand...
Click to collapse
Re-install superuser the same way you did the first time. The OTA failed because you have a custom recovery installed. If you want to update to Jelly Bean, look into installing one of the JB ROMs in the development forums, or if you must have the OTA you'll have to flash the stock recovery and make sure everything else is stock as well. OTAs do not care if you are rooted or have an unlocked bootloader.
you can also install the OTA manually, heres my method
1) grab the link for yakju IMM76i > 4.1.1 from here: http://forum.xda-developers.com/showthread.php?t=1764536 and place that iin your sdcard. ALSO download this version of Superuser (chainfires one): http://download.chainfire.eu/197/SuperSU/CWM-SuperSU-v0.93.zip and place that in your sdcard too.
2) install clockworkmod recovery again the same way you did before, using fastboot flash recovery recovery.img, press vol down twice in the bootloader and go straight into the recovery.
3) install the OTA zip you downloaded and placed in your sdcard
4) clear cache and fix permissions (might not be necessary but you can do it just incase)
5) reboot, you should now have stock jellybean. the ClockworkMod recovery would be removed at this point because stock android has a file in system which replaces the stock recovery after every reboot, unless you delete that file.
6) go back into the bootloader, flash recovery as before and again boot straight into the recovery. this time flash the superuser zip you downloaded.
7) reboot. should be all sorted now
JaiaV said:
Re-install superuser the same way you did the first time. The OTA failed because you have a custom recovery installed. If you want to update to Jelly Bean, look into installing one of the JB ROMs in the development forums, or if you must have the OTA you'll have to flash the stock recovery and make sure everything else is stock as well. OTAs do not care if you are rooted or have an unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the fast response.
So basically, I just copy and paste su.zip again into my Internal Storage on my computer. Put my phone into Recovery Mode, plug it in, find and install that su.zip again, and then reboot?
Also, this is something I didn't know: So if you are rooted, you cannot update "normally"? I will always have to flash over the latest ROM?
Thanks.
BryMerc said:
So basically, I just copy and paste su.zip again into my Internal Storage on my computer. Put my phone into Recovery Mode, plug it in, find and install that su.zip again, and then reboot
Click to expand...
Click to collapse
Yes.
BryMerc said:
Also, this is something I didn't know: So if you are rooted, you cannot update "normally"? I will always have to flash over the latest ROM?
Click to expand...
Click to collapse
JaiaV said:
OTAs do not care if you are rooted or have an unlocked bootloader.
Click to expand...
Click to collapse
They only care that the recovery and /system are stock, and even then (as I said) don't care if you're rooted. Rooting doesn't matter. Having a custom recovery does. They are not the same thing. Also, read through ||Nexus|| response.
IINexusII said:
you can also install the OTA manually, heres my method
1) grab the link for yakju IMM76i > 4.1.1 from here: http://forum.xda-developers.com/showthread.php?t=1764536 and place that iin your sdcard. ALSO download this version of Superuser (chainfires one): http://download.chainfire.eu/197/SuperSU/CWM-SuperSU-v0.93.zip and place that in your sdcard too.
2) install clockworkmod recovery again the same way you did before, using fastboot flash recovery recovery.img, but dont reboot this time, press vol down twice in the bootloader and go straight into the recovery.
3) install the OTA zip you downloaded and placed in your sdcard
4) clear cache and fix permissions (might not be necessary but you can do it just incase)
5) reboot, you should now have stock jellybean. the ClockworkMod recovery would be removed at this point because stock android has a file in system which replaces the stock recovery after every reboot, unless you delete that file.
6) go back into the bootloader, flash recovery as before and again boot straight into the recovery. this time flash the superuser zip you downloaded.
7) reboot. should be all sorted now
Click to expand...
Click to collapse
OK, thank you so much. I'm going to do exactly this. When I "fastboot flash" these over again, will they just replace the old ones? Or do I have to uninstall the ones already on my phone or something. I feel like it may get cluttered or something lol, sorry if that's stupid.
BryMerc said:
OK, thank you so much. I'm going to do exactly this. When I "fastboot flash" these over again, will they just replace the old ones? Or do I have to uninstall the ones already on my phone or something. I feel like it may get cluttered or something lol, sorry if that's stupid.
Click to expand...
Click to collapse
no, youre just reflashing the recovery which wont affect anything else. once you reboot it will revert back to the stock recovery anyway, so youll be able to get future OTA updates just fine.
edit: yes itll just be replacing the recovery, nothing else
IINexusII said:
no, youre just reflashing the recovery which wont affect anything else. once you reboot it will revert back to the stock recovery anyway, so youll be able to get future OTA updates just fine.
edit: yes itll just be replacing the recovery, nothing else
Click to expand...
Click to collapse
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
BryMerc said:
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
Click to expand...
Click to collapse
in clockwork mod recovery there should be a "Wipe Cache" option, and for fixing permissions go to "advanced" and "Fix Permissions"
BryMerc said:
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
Click to expand...
Click to collapse
Wait, actually I don't think the JB installed now that I'm staring at the screen properly.
It went Installing update...
assert failed: file .........blah blah
Installation aborted.
Also, the drivers I thought I had for my phone seem to be messing up and in device manager it says "Full" with an exclamation point. I'm not sure why.
Sorry for the late responses as a n00b I'm stuck with 5 minute intervals here.
which country are you from?
IINexusII said:
which country are you from?
Click to expand...
Click to collapse
Canada.
I just tried reinstalling the drivers and everything and for some reason it's not working. I flash Clockwork Recovery, I see the JB.zip, but when I click to install it it says "assert failed" and has the dead Android. Not sure if it's a driver issue, but I redid the Universal Naked one I had before that worked.
BryMerc said:
Canada.
I just tried reinstalling the drivers and everything and for some reason it's not working. I flash Clockwork Recovery, I see the JB.zip, but when I click to install it it says "assert failed" and has the dead Android. Not sure if it's a driver issue, but I redid the Universal Naked one I had before that worked.
Click to expand...
Click to collapse
After selecting "Install zip from sdcard" I see an option "apply /sdcard/update.zip". Is that anything maybe I need to do or something?
check your PM
The problem I encountered must be the worst problem ever! For some reason my nexus reboot randomly and its not just a regular reboot but it reboot as a DEEP FREEZE. So basically once it rebooted, it goes back to a same specific point of time. I can't even delete stuff from the phone, for example if I deleted 1GB of music off my phone, after few second the phone will reboot automatically OR if i reboot the phone myself the 1GB of music would be back in my phone. Like WTH? I am completely lost. I have no idea how it happened, but I know it happened after I installed Paranoid Android AOSP 2.99 beta5. I was fine when flashing Paranoid Android 1,3,4. ALSO I cannot do a factory reset or install a factory rom. It just go back to 4.2.1 AOSP 2.99 beta5...
please guys, if anyone can help me that would be great. If you guys need more explaining please email or PM me. I will be glad to write a whole essay on what you guys need to know to help me out. Thank you
Go back to stock and start fresh.
Sent from my i9250
bk201doesntexist said:
Go back to stock and start fresh.
Sent from my i9250
Click to expand...
Click to collapse
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..
Yellowfriedrice said:
Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here
ahmadallica said:
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here
Click to expand...
Click to collapse
You cant brick a nexus! Try making a jig with this link http://www.youtube.com/watch?v=jKRrTZayRxU Then get download odin and an img file of whatever rom you want and flash it through odin. Problem should be solved.
Yellowfriedrice said:
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out
khuzema9 said:
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out
Click to expand...
Click to collapse
Based on the language used in the OP I think he used a toolkit to root/unlock his Nexus and that's why he knows nothing about his device and how to fix it.
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again
altimax98 said:
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again
Click to expand...
Click to collapse
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck
still didn't work
ahmadallica said:
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck
Click to expand...
Click to collapse
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you
Yellowfriedrice said:
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you
Click to expand...
Click to collapse
I really have not done anything to my GNex via Windows becuse I am using Ubuntu Linux so I have not experienced installing these drivers on Windows. I also have neither returned my phone to stock before nor used the Nexus toolkit. I am doing everything manually.
I think you are referring to the drivers in this page. If you are using Windows 8 then there are some steps mentioned on how to get pass the driver signature enforcement.
If you are on Windows 7, then look here.
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?
ahmadallica said:
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?
Click to expand...
Click to collapse
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol
Yellowfriedrice said:
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol
Click to expand...
Click to collapse
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!
ahmadallica said:
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!
Click to expand...
Click to collapse
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.
Yellowfriedrice said:
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.
Click to expand...
Click to collapse
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
ahmadallica said:
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.
ahmadallica said:
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
Thank Goodness im not the only one who has this issue... Bugs the crap outta me lol..
To the OP:
Try this, 1: make sure your an admin on your PC. From the sounds of it you may not be if it said 'access denied'. 2: Plug your nexus in while in the 'device manager' section of windows. 3: Find the new device and delete it. Delete anything that says Android ADB or Android anything or galaxy Nexus or Galaxy phone. Just delete them. Windows will warn you but do it anyways... 4: reboot the pc. 5: Plug your nexus back in, it should either install the device or fail. At that point find and download the newest samsung naked drivers and use the option on windows to install driver from disk and navigate to your unzipped folder.
That is the sure fire way to get it working again. Sorry to say if you still have driver issues then your doing something wrong. Do alot of reading and the answer will show itself.
1. Can you boot your phone into fastboot mode?
2. If so, once in fastboot mode, what happens when you connect the phone to the computer?
It is very very difficult to brick a nexus, so don't worry... .
Yellowfriedrice said:
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.
Click to expand...
Click to collapse
Sorry for not being able to help you better. I'm sure that others who are familiar with Windows can help you overcome your earlier issues with drivers and so on thus be able to return to stock and start fresh
Good Luck
It is very very difficult to brick a nexus said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse
OKAY i tried everything.. nothing seem to work.. selling my nexus!
Yellowfriedrice said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse
Hey guys I followed this guide
http://forum.xda-developers.com/show....php?t=2235366
I used a file called "CF-Auto-Root-d2spr-d2spr-sphl710.tar"
Everything goes well and I get a green pass from oden3, the phone reboots. But superSU is not installed and when I check "Root checker" there is no root....
I have 4.1.2
Thoughts?
Just download superuser and simply place it on your phones SD card it's really easy
Sent from my SPH-L710 using xda app-developers app
ricanjoe said:
Hey guys I followed this guide
http://forum.xda-developers.com/show....php?t=2235366
I used a file called "CF-Auto-Root-d2spr-d2spr-sphl710.tar"
Everything goes well and I get a green pass from oden3, the phone reboots. But superSU is not installed and when I check "Root checker" there is no root....
I have 4.1.2
Thoughts?
Click to expand...
Click to collapse
Your phone is not finishing the process it seems. After Odin says pass do you get a big red Android on the screen? If not flash the cf auto root file but uncheck auto reboot in Odin first. Then when it finishes, pull the cable and remove the battery. Reinsert the battery and manually boot to recovery by holding volume up+home+power and it should finish installing root.
I don't know what the post above me is taking about. Installing superuser isn't going to magically give you root. js
billard412 said:
Your phone is not finishing the process it seems. After Odin says pass do you get a big red Android on the screen? If not flash the cf auto root file but uncheck auto reboot in Odin first. Then when it finishes, pull the cable and remove the battery. Reinsert the battery and manually boot to recovery by holding volume up+home+power and it should finish installing root.
I don't know what the post above me is taking about. Installing superuser isn't going to magically give you root. js
Click to expand...
Click to collapse
Yes its a screen with red letters and numbers saying the phone will reboot in 10 seconds.... So I re root in oden? then I pull the battery out before reboot? Could this brick my phone?
Thanks foe the help
ricanjoe said:
Yes its a screen with red letters and numbers saying the phone will reboot in 10 seconds.... So I re root in oden? then I pull the battery out before reboot? Could this brick my phone?
Thanks foe the help
Click to expand...
Click to collapse
It wouldnt brick the phone but if you are seeing the red android then i was mistaken about what your issue is so disregard. Is your phone new? I bet the issue is related to one others are having where recovery cant mount partitions. To confirm that try this. Download this and place on pc http://goo.im/devs/billard412/d2spr/AUTOBOOT_RECOVERY/SPH-L710_TWRP_AUTOBOOT.exe
Its a odin one click that will autoboot you to twrp recovery just open it and click start with your phone connected in download mode.
Download this and place on your sd card. (preferably external)
http://forum.xda-developers.com/attachment.php?attachmentid=1584076&d=1356201390
If you can successfully flash that zip, it will root the phone.
billard412 said:
It wouldnt brick the phone but if you are seeing the red android then i was mistaken about what your issue is so disregard. Is your phone new? I bet the issue is related to one others are having where recovery cant mount partitions. To confirm that try this. Download this and place on pc http://goo.im/devs/billard412/d2spr/AUTOBOOT_RECOVERY/SPH-L710_TWRP_AUTOBOOT.exe
Its a odin one click that will autoboot you to twrp recovery just open it and click start with your phone connected in download mode.
Download this and place on your sd card. (preferably external)
http://forum.xda-developers.com/attachment.php?attachmentid=1584076&d=1356201390
If you can successfully flash that zip, it will root the phone.
Click to expand...
Click to collapse
About to give it a shot. Placing the root file on my external SD and phone into download mode, about to launch the odin app on pc.
billard412 said:
It wouldnt brick the phone but if you are seeing the red android then i was mistaken about what your issue is so disregard. Is your phone new? I bet the issue is related to one others are having where recovery cant mount partitions. To confirm that try this. Download this and place on pc http://goo.im/devs/billard412/d2spr/AUTOBOOT_RECOVERY/SPH-L710_TWRP_AUTOBOOT.exe
Its a odin one click that will autoboot you to twrp recovery just open it and click start with your phone connected in download mode.
Download this and place on your sd card. (preferably external)
http://forum.xda-developers.com/attachment.php?attachmentid=1584076&d=1356201390
If you can successfully flash that zip, it will root the phone.
Click to expand...
Click to collapse
my man, so far im in a 'team win recovery project screen' its all blue and stuff
this is pretty exiting for me.
So what do I press now? what does this screen mean?
(some personal insight, I have rooted my old evo 3d back in the day but il still pretty noobish, the twrp thing rings a bell)
ricanjoe said:
my man, so far im in a 'team win recovery project screen' its all blue and stuff
this is pretty exiting for me.
So what do I press now? what does this screen mean?
(some personal insight, I have rooted my old evo 3d back in the day but il still pretty noobish, the twrp thing rings a bell)
Click to expand...
Click to collapse
You want to press install then hit "up a level" until youre in the root "/" directory. Then choose "external_sdcard" then tap "root.zip" and swipe to confirm at the bottom.
billard412 said:
You want to press install then hit "up a level" until youre in the root "/" directory. Then choose "external_sdcard" then tap "root.zip" and swipe to confirm at the bottom.
Click to expand...
Click to collapse
sweet man, Im in root checker and it says "congratulations this device has root access"
I wanted to ask you how does this method differ from the method I was trying to perform?
ricanjoe said:
sweet man, Im in root checker and it says "congratulations this device has root access"
I wanted to ask you how does this method differ from the method I was trying to perform?
Click to expand...
Click to collapse
It's basically the same thing. Cf auto root will install a special recovery made by chainfire and a cache.img with a root zip. It's supposed to flash that zip then restore stock recovery. I've never seen cf auto root fail to do the job so im not sure what went wrong.
But the way you did it was you installed your own custom recovery and manually flashed a root zip created by me instead. Only thing different here is that you still have that custom recovery instead of stock recovery now.
billard412 said:
It's basically the same thing. Cf auto root will install a special recovery made by chainfire and a cache.img with a root zip. It's supposed to flash that zip then restore stock recovery. I've never seen cf auto root fail to do the job so im not sure what went wrong.
But the way you did it was you installed your own custom recovery and manually flashed a root zip created by me instead. Only thing different here is that you still have that custom recovery instead of stock recovery now.
Click to expand...
Click to collapse
Got it man, is this custom recovery better than the stock or is it essentially the same? I plan to install a custom rom soon.
(I didn't find many threads like this on google nor the search tool so hopefully people with the same strange problem as me will now find it. Should be useful)
ricanjoe said:
Got it man, is this custom recovery better than the stock or is it essentially the same? I plan to install a custom rom soon.
(I didn't find many threads like this on google nor the search tool so hopefully people with the same strange problem as me will now find it. Should be useful)
Click to expand...
Click to collapse
The custom recovery is the same with the exception that it gives you additional privileges over stock recovery. Like installing custom roms, so if you're planning on a custom rom soon then you may as well just stick with the custom one. I do however recommend you download goo manager from the playstore and updating your recovery to the newest with it before trying to flash anything. The recovery I gave you may be a little outdated. And if for any reason you want stock recovery back I'll make a odin tar of it and place it in this post
STOCK RECOVERY TAR
billard412 said:
The custom recovery is the same with the exception that it gives you additional privileges over stock recovery. Like installing custom roms, so if you're planning on a custom rom soon then you may as well just stick with the custom one. I do however recommend you download goo manager from the playstore and updating your recovery to the newest with it before trying to flash anything. The recovery I gave you may be a little outdated. And if for any reason you want stock recovery back I'll make a odin tar of it and place it in this post
Click to expand...
Click to collapse
I got the goo manager, which recovery do I update to?
The app wants me to update to open recovery twerp 2/6/2/0/d2spr.img
ricanjoe said:
I got the goo manager, which recovery do I update to?
The app wants me to update to open recovery twerp 2/6/2/0/d2spr.img
Click to expand...
Click to collapse
Just open it. Hit Menu then tap "install openrecoveryscript" Then "Yes". Then "Yes" again. It'll download the latest TWRP and flash it automatically.
Edit:sorry had to reread that. Twrp 2620 is right
advocatebutdfh
billard412 said:
Just open it. Hit Menu then tap "install openrecoveryscript" Then "Yes". Then "Yes" again. It'll download the latest TWRP and flash it automatically.
Click to expand...
Click to collapse
Alright man I wont waste anymore of your time here, just want to say thanks for all the help, this gives me the courage to continue to learn more about rooting and custom roms. I was about to give up last night because of this frustrating issue I had. Thanks again!
ricanjoe said:
Alright man I wont waste anymore of your time here, just want to say thanks for all the help, this gives me the courage to continue to learn more about rooting and custom roms. I was about to give up last night because of this frustrating issue I had. Thanks again!
Click to expand...
Click to collapse
No problem glad to help. And just in case u need it, the stock recovery tar is attached below.
billard412 said:
Just open it. Hit Menu then tap "install openrecoveryscript" Then "Yes". Then "Yes" again. It'll download the latest TWRP and flash it automatically.
Edit:sorry had to reread that. Twrp 2620 is right
Click to expand...
Click to collapse
about to install moar rom. I saw a video saying you should wipe dalvic cache and do several other things before.
Is there anything you reccomend I do before I flash this custom rom (Moar)
ricanjoe said:
about to install moar rom. I saw a video saying you should wipe dalvic cache and do several other things before.
Is there anything you reccomend I do before I flash this custom rom (Moar)
Click to expand...
Click to collapse
Just a factory reset. It should automatically wipe the cache and other areas that need wiped. I've ran moar before it's am awesome rom
billard412 said:
Just a factory reset. It should automatically wipe the cache and other areas that need wiped. I've ran moar before it's am awesome rom
Click to expand...
Click to collapse
Awesome im working on it now, also do you backup efs? Or is that just for the paranoid crowd?
(I will give you a shout out on my next vid
ricanjoe said:
Awesome im working on it now, also do you backup efs? Or is that just for the paranoid crowd?
(I will give you a shout out on my next vid
Click to expand...
Click to collapse
Personally I think the chances of your efs going bad are slim and a backup is more for paranoid people. With that said it never hurts to back it up. I just wouldn't restore it unless you have to.
Hello, I have done a bit of research around the web and yet I have not come across any possible way to root my Galaxy note 2 from AT&T, Some people have said that it wont work or that It's not possible and really have run out of options, This is the only place where I think I could get some help. Any help is appreciated, Thank you in advanced.
gerardo891 said:
Hello, I have done a bit of research around the web and yet I have not come across any possible way to root my Galaxy note 2 from AT&T, Some people have said that it wont work or that It's not possible and really have run out of options, This is the only place where I think I could get some help. Any help is appreciated, Thank you in advanced.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1987541
Section 7: How To's/Guides
dicksteele said:
http://forum.xda-developers.com/showthread.php?t=1987541
Section 7: How To's/Guides
Click to expand...
Click to collapse
I have already tried this but i ran into the KNOX problem
gerardo891 said:
I have already tried this but i ran into the KNOX problem
Click to expand...
Click to collapse
Go to Google play and update, It will shut down Knox
dicksteele said:
Go to Google play and update, It will shut down Knox
Click to expand...
Click to collapse
Update what? Also now when ever I install any app from the Playstore the knox notification comes up
gerardo891 said:
Update what? Also now when ever I install any app from the Playstore the knox notification comes up
Click to expand...
Click to collapse
Update SuperSU app. After the update a window will pop up asking if you want to disable Knox. Answer yes
As you can see their is no update for superuser
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
gerardo891 said:
As you can see their is no update for superuser
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
And if you open it, what does it do?
When I open it closes it self and I get the KNOX error
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Flash this from custom recovery
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
dicksteele said:
Flash this from custom recovery
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Click to expand...
Click to collapse
I'm a bit of a nooby at this meaning I don't know how to flash that. also I am running on 4.3 don't know if that's relevant or not. I'm sorry but could u possibly tell me how to flash that?
gerardo891 said:
I'm a bit of a nooby at this meaning I don't know how to flash that. also I am running on 4.3 don't know if that's relevant or not. I'm sorry but could u possibly tell me how to flash that?
Click to expand...
Click to collapse
Here's some links to help.. Read all first.
http://forum.xda-developers.com/showthread.php?p=34039100#post34039100
http://www.addictivetips.com/android/what-is-twrp-how-to-install-use-it-on-android-devices-guide/
http://www.addictivetips.com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/
After reading above,
Follow the info in Post #1
http://forum.xda-developers.com/showthread.php?t=2618447
Replace this file that is called out in the guide, KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar.md5, with the file that you download below openrecovery-twrp-2.7.0.0-t0lteatt.img.tar
TWRP download link
http://goo.im/devs/OpenRecovery/t0lteatt/openrecovery-twrp-2.7.0.0-t0lteatt.img.tar
The follow instructions here.
http://www.addictivetips.com/android/what-is-twrp-how-to-install-use-it-on-android-devices-guide/
You will be doing this....
Install
As the name suggests, the Install option lets you install any recovery-flashable zip file to your device. This can be a ROM, a kernel, a mod, a theme, a system app – pretty much anything that’s available in the recovery-flashable zip file format.
The recovery-flashable zip will be the UPDATE 1.93 SU file
Make this best friend
http://forum.xda-developers.com/showthread.php?t=1987541
dicksteele said:
Here's some links to help.. Read all first.
http://forum.xda-developers.com/showthread.php?p=34039100#post34039100
http://www.addictivetips.com/android/what-is-twrp-how-to-install-use-it-on-android-devices-guide/
http://www.addictivetips.com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/
After reading above,
Follow the info in Post #1
http://forum.xda-developers.com/showthread.php?t=2618447
Replace this file that is called out in the guide, KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar.md5, with the file that you download below openrecovery-twrp-2.7.0.0-t0lteatt.img.tar
TWRP download link
http://goo.im/devs/OpenRecovery/t0lteatt/openrecovery-twrp-2.7.0.0-t0lteatt.img.tar
The follow instructions here.
http://www.addictivetips.com/android/what-is-twrp-how-to-install-use-it-on-android-devices-guide/
You will be doing this....
Install
As the name suggests, the Install option lets you install any recovery-flashable zip file to your device. This can be a ROM, a kernel, a mod, a theme, a system app – pretty much anything that’s available in the recovery-flashable zip file format.
The recovery-flashable zip will be the UPDATE 1.93 SU file
Make this best friend
http://forum.xda-developers.com/showthread.php?t=1987541
Click to expand...
Click to collapse
I want to try this But at the same time i don't want to brick my phone. Is there any way so that the KNOX error will stop coming up? I think i might just not do this I don't want to brick my phone because of something i don't know off and can't do. I don't know what to do. well thank you i suppose.
gerardo891 said:
I want to try this But at the same time i don't want to brick my phone. Is there any way so that the KNOX error will stop coming up? I think i might just not do this I don't want to brick my phone because of something i don't know off and can't do. I don't know what to do. well thank you i suppose.
Click to expand...
Click to collapse
Flashing the TWRP is the same way as you flashed Root.
Is this what you used ?
CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.zip
If so ODIN was in there.... You are using the same method to flash the custom recovery. If you didn't use that file above, that may be part of your problem.
The only way to get rid of the Knox messages is to disable it. Flashing the Update SU file will do that.
dicksteele said:
Flashing the TWRP is the same way as you flashed Root.
Is this what you used ?
CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.zip
If so ODIN was in there.... You are using the same method to flash the custom recovery. If you didn't use that file above, that may be part of your problem.
The only way to get rid of the Knox messages is to disable it. Flashing the Update SU file will do that.
Click to expand...
Click to collapse
The file I installed on my phone thru odin was called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar it was a .tar file idk if that makes a diffrence
gerardo891 said:
The file I installed on my phone thru odin was called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar it was a .tar file idk if that makes a diffrence
Click to expand...
Click to collapse
That is fine.... That file was in the zip file I posted....
You flash the recovery file the same way.. Then you follow the instructions to boot into recovery. After you copy the UPDATE-SuperSU-v1.93.zip to your external sdcard or sdcard.
Then follow the TWRP flashable zip install instructions. Takes less than 15 minutes for the whole process.
After it flashes, go to the supersu app, click it should pop and ask to disable Knox.
Or try and reflash the CF-auto-root file since you have done that already. Pay attention to the status screen makes sure it completes successfully.
dicksteele said:
That is fine.... That file was in the zip file I posted....
You flash the recovery file the same way.. Then you follow the instructions to boot into recovery. After you copy the UPDATE-SuperSU-v1.93.zip to your external sdcard or sdcard.
Then follow the TWRP flashable zip install instructions. Takes less than 15 minutes for the whole process.
After it flashes, go to the supersu app, click it should pop and ask to disable Knox.
Or try and reflash the CF-auto-root file since you have done that already. Pay attention to the status screen makes sure it completes successfully.
Click to expand...
Click to collapse
So I pretty much have Flash the recovery file to install CWM correct? And then I boot into recovery mode, So I could then flash the superuser update? I think thats how it goes.. Lol im sorry it's kinda confusing.
gerardo891 said:
So I pretty much have Flash the recovery file to install CWM correct? And then I boot into recovery mode, So I could then flash the superuser update? I think thats how it goes.. Lol im sorry it's kinda confusing.
Click to expand...
Click to collapse
Correct. The recovery file is the custom recovery.
There are two main types of custom recoveries.
- CWM, ClockWorkMod, which comes in a touch format or a format you need to use your power button, up/down volume keys to navigate.
- Or TWRP, Team Win Recovery Project To start with use TWRP, I think it is the easier of the two to use.
You have the steps correct.
1. Flash the TWRP custom recovery file in ODIN. (same method you attempted with the CF-AUTO-Root)
2. Reboot into recovery.
Power off phone.
Wait a minute and turn it back on. To boot into TWRP recovery (HOLD VOL UP+HOME+POWER) while it is powering on. Do this quickly after turning phone on, within seconds of powering on.
3. You'll see a screen that says Team Win Recovery Project at the top with about six grey buttons on a black background
Click install.
Upon hitting Install, you’re presented with the files and folders on your phone’s storage, from which you can select the file you want to flash. Find the UPDATE-SuperSU-v1.93.zip.
With the file selected, you can swipe the slider to confirm and start flashing the selected file.
4. Once the flashing process is complete, TWRP gives you some handy options for quick access to certain tasks that many users would need to perform after flashing, eliminating the extra steps required to pick them from their individual sections. These include wiping cache and dalvik cache, and rebooting the system, in addition to a Home shortcut.
Click reboot. Then go to SuperSU app and test it.
dicksteele said:
Correct. The recovery file is the custom recovery.
There are two main types of custom recoveries.
- CWM, ClockWorkMod, which comes in a touch format or a format you need to use your power button, up/down volume keys to navigate.
- Or TWRP, Team Win Recovery Project To start with use TWRP, I think it is the easier of the two to use.
You have the steps correct.
1. Flash the TWRP custom recovery file in ODIN. (same method you attempted with the CF-AUTO-Root)
2. Reboot into recovery.
Power off phone.
Wait a minute and turn it back on. To boot into TWRP recovery (HOLD VOL UP+HOME+POWER) while it is powering on. Do this quickly after turning phone on, within seconds of powering on.
3. You'll see a screen that says Team Win Recovery Project at the top with about six grey buttons on a black background
Click install.
Upon hitting Install, you’re presented with the files and folders on your phone’s storage, from which you can select the file you want to flash. Find the UPDATE-SuperSU-v1.93.zip.
With the file selected, you can swipe the slider to confirm and start flashing the selected file.
4. Once the flashing process is complete, TWRP gives you some handy options for quick access to certain tasks that many users would need to perform after flashing, eliminating the extra steps required to pick them from their individual sections. These include wiping cache and dalvik cache, and rebooting the system, in addition to a Home shortcut.
Click reboot. Then go to SuperSU app and test it.
Click to expand...
Click to collapse
So I pretty much just flash TWRP and then I understand from there. But what do I need to flash CWM for then?
gerardo891 said:
So I pretty much just flash TWRP and then I understand from there. But what do I need to flash CWM for then?
Click to expand...
Click to collapse
Close your eyes and erase CWM from your mind.... Think happy TWRP flashing thoughts.
They are technically both the same thing. They do the same thing.
So far ive tried superoneclick... froze on step 7
tried manually installing superuser... couldnt verify.
tried installing a root zip... couldnt verify.
the only thing that claims to have worked is clockworkmod... except that it will NOT allow me access to any of the actual rooted functions.
i was able to download superuser (which you cannot download from google play unless rooted- that worked.)
trying to keep the OS on it now while being able to delete bloatware, for a friend.
is it purely impossible to root a stock rom? why can i install programs that requre root but i cannot use them for their intended purpose (rom manager says it cant find superuser in either of 2 locations).
what the heck am i missing?? ive been googling and trying methods for hours to no avail. cant boot into cwm recovery at all, by rom manager or from powered off (it goes into stock recovery.).
what else can i do?
Pawprints1986 said:
So far ive tried superoneclick... froze on step 7
tried manually installing superuser... couldnt verify.
tried installing a root zip... couldnt verify.
the only thing that claims to have worked is clockworkmod... except that it will NOT allow me access to any of the actual rooted functions.
i was able to download superuser (which you cannot download from google play unless rooted- that worked.)
trying to keep the OS on it now while being able to delete bloatware, for a friend.
is it purely impossible to root a stock rom? why can i install programs that requre root but i cannot use them for their intended purpose (rom manager says it cant find superuser in either of 2 locations).
what the heck am i missing?? ive been googling and trying methods for hours to no avail. cant boot into cwm recovery at all, by rom manager or from powered off (it goes into stock recovery.).
what else can i do?
Click to expand...
Click to collapse
What device do you have? There a several variations of the Tab 3.
gr8nole said:
What device do you have? There a several variations of the Tab 3.
Click to expand...
Click to collapse
in the model number it says sm-t210R
running android 4.1.2
build number jzo54k.t210euwamk1
she needs it back by sunday night so any help would be greatly appreciated
Pawprints1986 said:
in the model number it says sm-t210R
running android 4.1.2
build number jzo54k.t210euwamk1
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2433853
gr8nole said:
http://forum.xda-developers.com/showthread.php?t=2433853
Click to expand...
Click to collapse
saw that but cant use it as i cant get my system to boot in to CWM recovery, to flash a root zip, although it is installed.
cant flash zips with odin.
so im basically stuck.
Pawprints1986 said:
saw that but cant use it as i cant get my system to boot in to CWM recovery, to flash a root zip, although it is installed.
cant flash zips with odin.
so im basically stuck.
Click to expand...
Click to collapse
Did you watch the video in the CWM thread?
Tell me your steps EXACTLY and we'll figure it out.
Finally got it to work. i guess the magic step is not letting odin auto reboot. I was afraid not to let it because its not even mine. But, i followed the video in that thread exactly and that let my root zip install correctly.
phew!
Pawprints1986 said:
Finally got it to work. i guess the magic step is not letting odin auto reboot. I was afraid not to let it because its not even mine. But, i followed the video in that thread exactly and that let my root zip install correctly.
phew!
Click to expand...
Click to collapse
Well actually the guide say rem8ve the check mark of reboot. You most do it by your own.
Send from my SM-T210R (Rocket Tab Rom) using XDA HD Premium