I followed the instructions from this youtube video that I found under this xda how to sticky .
There are only a couple points were my experience differed from what was expected in the video.
A) I used the V 3.0.0 of the Samsung Galaxy Note II Tool kit and the video used version V 2.0.0
B) In his video there was only one variant of the Sprint Note II within the toolkit. In my toolkit there were two variants. I couldn't figure out which one was mine, so I chose the same that he did (Build JRO03C ALJ1).
C) After the root was completed TWRP did not come up after rebooting with volume down,home,power button. Instead, a screen giving a warning about flashing ROMS came up. There was volume up to continue, or volume down to cancel. After hitting volume up, it showed the iconic green android with the text "Downloading... Do not turn off target !!" I've included pictures of both screens.
Can anyone explain why this happened? The root was successful. I've already used SuperSU multiple times.
Android Vs 4.1.2
Recovery is volume up, home and power. Volume down, home and power takes you to download/odin mode
I like to break stuff!
Related
Hi there, Guys.
I'm noticing that it's so difficult to load the Stock Recovery Mode! For example, when the device is off and I hold Volume Up + Home + Power, I can't load it if I hold them forever, just like I used to do on the first Note.
Basically, I need to stop holding them absolutely immediately after "Galaxy Note II - GT-7100" white letters disappears to have success loading it.
Is this normal or just with me?
If using CWM, this would be different? For example, My Galaxy Note has CWM and It loads so easily just holding the three buttons forever. I don't need to "respect this ultra fast time gap" after device white letters name appears to release buttons!
=====
Edit:
Just noticed that actually I need to release the three buttons WHILE the "Galaxy Note II" white letters are still on the screen.
I'm confused. Can't understand this "time out" rule that messed up the "easyness" to enter Recovery Mode.
You'r not alone, i have this too. Is your device rooted ? Mine is (with chainfire method), maybe it's a side effect of rooting.
Edit: Thank for the tips on how to enter recovery mode, very useful ))
I can enter recovery easily by holding the three buttons, then when the white note 2 logo appears, let go of the power button and keep holding only the volume and home button until you get into recovery. Works every time.
spidermoon said:
You'r not alone, i have this too. Is your device rooted ? Mine is (with chainfire method), maybe it's a side effect of rooting.
Edit: Thank for the tips on how to enter recovery mode, very useful ))
Click to expand...
Click to collapse
Yeah, I'm also rooted and using CF method!
And you're welcome!
MohJee said:
I can enter recovery easily by holding the three buttons, then when the white note 2 logo appears, let go of the power button and keep holding only the volume and home button until you get into recovery. Works every time.
Click to expand...
Click to collapse
That's right, after some time and fails I'm used to it. Actually I don't release just Power Button, but all three buttons when white logo appears and it works also!
Hey guys, first time poster 3-4 year lurker.
I have a question about my Odin flash that I did last night. I followed these steps http://forum.xda-developers.com/showthread.php?t=2391367
and everything flashed and tablet is working. The only problem I have is when I restart or cold boot the device the screen stays on but with a black screen for about 20 seconds then the screen dims for another 15 seconds after that the screen goes black for another ten seconds. I wait another 10 seconds with the screen black (off) and then I can press the home button and my home screen comes up. The device is rooted and everything seems to working fine.
Power > Samsung splash screen > bright 20s > dim 15s > screen off 15s > wait 10s > home screen comes up. (no sound during this process)
during this process my power, volume and home screen button does not do anything till after I wait 10s after the screen off
I have attempted to re-flash the rom using the same method and even downloaded "prerooted.tar.md5" and the "odin 3.07 from other sources and I still get the same results. I have also download drivers directly form Samsung page, uninstalled, rebooted, re-installed. I have also used different USB ports and I still get the same results. I read a suggetion to try odin 3.09 but I receive a "FAILED" when flashing.
I am using windows 7 pro X64 my tablet is Mo:SM-T210, current kernal 3.4.5-1256430-user, Build JZO54K. T210XXAMG2
unfortunately I have searched for this problem on Google and the forums but nothing I have found fits this description. I am not allowed to post in the dev section due to my lack of post. Hope to hear from you soon and thank you for the years of support you have given me. Hopefully I will be able to be of some use to someone in the future.
I've got a sprint GS3 that is rooted and has the clockwork recovery mod on it, but was otherwise running stock OS. It had been acting up, hanging, that kind of thing so I decided to go ahead and accept the download new software prompt I've had for the last year or so. When it went to the bootimage(?) menu it asked if I wanted to install this untrusted image. That gave me pause, so I selected no. The little android icon got a red X-ish thing on it's chest and it rebooted. And sat at the samsung galaxy s3 screen for about a half an hour. I pulled the power and it kept going between hanging at that screen, or hanging at random points (app 6, 8, 9, 11) of an "upgrading android" screen I have never seen before. I tried going into the recovery mode but when I follow the instructions (up vol, home and power, when it vibrates for power release the power button) but that doesn't work at all. It just sits there. I'm 100% certain it's not a button/physical issue. I decided to try the download option and can get to a screen that warns me about custom rom. I've tried both installing (let it go for over an hour, gave up) and hitting cancel, to no avail. Before I take this as a sign from the android gods that it's time to go get a GS5, does anyone have any ideas/advice? TIA.
Wrong section.. Report it yourself and adj a mod to move it to correct section..
Sent from my GT-I9300 using xda app-developers app
Have you tried to plug the phone in with the USB cable into the computer?
Hey guys I have a Samsung Galaxy Tab S and it's my first Samsung. It is brand new and I was just looking through apps then found this mysterious superuser app. I wanted to record and needed to use this app. After doing research I finally found how to root my device and did so. It didn't work the first time but retried it and it worked! It said I rooted my tablet on my computer but when I look down to my tablet it is on the "Samsung GALAXY Tab S" screen also known as the Bootup screen. It doesn't do anything once it goes on. Now I have been waiting for 30 - 45 mins and nothing happened. I have tried re - rooting it and using Kies 3 to fix it. But sadly nothing worked. Thanks for reading this and if you can please help me out.
P.S. - My Samsung is a Galaxy Tab S
SM - T800
moved to correct forum
MD
Try holding power, vol up and down, and home buttons at the same time and it should force reboot. Then quickly press power, home and vol down to get into download mode. Then flash stock firnware. What root did you use?
Received a Nexus 7 LTE (2013) today from Amazon Warehouse. After installing some apps, I upgraded from 4.3 to 4.4.2 from the system screen in Settings. It went through the bootloader process and I wasn't watching after that, but now at the end I've got Google's screen of death so it seems, i.e., white "Google" on a black screen and neither power or power + volume up/down responds. What's the best way out of this? Thanks,
UPDATE: Kept searching, and on the Google Nexus product forum found a thread, "Nexus 7 stuck on Google screen."
1. Turn off the device by holding the Power key for about 5 seconds.
2. Press and hold the Volume Down and Power keys at the same time for about 10 seconds.
3. An image of an Android lying on its back should appear.
4. Press the Volume Down key until "Start mode" appears on the screen.
5. Press the Power key to restart.
6. An image of 4 moving balls should appear.
7. After the balls disappear the tablet should start as normal.
8. [upgrade finished installing...]
So this will make the KitKat work?
3316556 said:
So this will make the KitKat work?
Click to expand...
Click to collapse
It did for me, although I didn't do extensive testing of apps. After that, I updated step by step to 5.1. So far, taps aside, everything I've come across is working.
Sorry to waist your time I replayed to the wrong post I got the same thing you do but instead of upgrading its downgrading that my problem,stupid 5.0.1
3316556 said:
Sorry to waist your time I replayed to the wrong post I got the same thing you do but instead of upgrading its downgrading that my problem,stupid 5.0.1
Click to expand...
Click to collapse
I have the same problem. I downgrade my nexus 7 (2013) from 5.1 to 4.x, it stuck on the google's logo. I also tried to build from aosp, but the result is same. My device only work on 5.0 or above. I don't know why? And if I enter the recovery, I got some error messages like "Failed to mount /cache (No such file or directory)".
I posted my problem at here http://forum.xda-developers.com/nex...ogles-logo-t3259757/post64063398#post64063398