Hello.
I have a galaxy note 2 international version running 4.4.2. I have never rooted before, so I tried to find as much resources and tutorials as I could about it. Honestly, I'm not very tech savvy, so it may just be me. Hopefully, someone can help me out or point me in the right direction.
The video I followed the first time was this: youtube.com/watch?v=GBP1Ql7wck4
I made sure to follow it step by step, downloading what he did in the video(Drivers/ODIN/TWRC/SUPERSU), and ODIN gave me a pass, so I thought everything worked. When I tried pressing volume up+home+power though, I got the dead android and "no command" error. Some options came out as well (reboot your phone, wipe cache, etc)
I started panicking and thought maybe it was because the things I downloaded were out of date. So I went and downloaded the latest supersu and TWRC files. ODIN was a pass again, but still, "no command".
At this point, I was full out panicking, so I went to galaxynote2root.com/[/url] and downloaded their files and flashed it again (this is CWM now). ODIN once again gave me a pass but I got worried because when my phone started rebooting, the galaxy note 2 logo was flickering and being weird. The phone booted up normally after, then I went to the playstore and updated supersu. When I tried opening it though, it said I wasn't rooted and that I needed binaries or something.
I really hope someone can help, as I am so confused.
Anon007 said:
Hello.
I have a galaxy note 2 international version running 4.4.2. I have never rooted before, so I tried to find as much resources and tutorials as I could about it. Honestly, I'm not very tech savvy, so it may just be me. Hopefully, someone can help me out or point me in the right direction.
The video I followed the first time was this: youtube.com/watch?v=GBP1Ql7wck4
I made sure to follow it step by step, downloading what he did in the video(Drivers/ODIN/TWRC/SUPERSU), and ODIN gave me a pass, so I thought everything worked. When I tried pressing volume up+home+power though, I got the dead android and "no command" error. Some options came out as well (reboot your phone, wipe cache, etc)
I started panicking and thought maybe it was because the things I downloaded were out of date. So I went and downloaded the latest supersu and TWRC files. ODIN was a pass again, but still, "no command".
At this point, I was full out panicking, so I went to galaxynote2root.com/[/url] and downloaded their files and flashed it again (this is CWM now). ODIN once again gave me a pass but I got worried because when my phone started rebooting, the galaxy note 2 logo was flickering and being weird. The phone booted up normally after, then I went to the playstore and updated supersu. When I tried opening it though, it said I wasn't rooted and that I needed binaries or something.
I really hope someone can help, as I am so confused.
Click to expand...
Click to collapse
This is the exact procedure to follow: http://www.ibtimes.co.uk/root-galax...d-4-4-2-kitkat-install-philz-recovery-1447891
Read this carefully and you should be superfine.
[emoji12] Hit thanks button above if someone helps[emoji12]
I have checked with root checker and now have root. Thank you so very much.
Related
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
cvall91 said:
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
Click to expand...
Click to collapse
I thought rooted phones weren't allowed to update via Kies or OTA.
allenjthomsen said:
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I guess I'll try to download it again and see if that works. Do you know if that's through Kies or through manually downloading it then using Odin?
Techngro said:
I thought rooted phones weren't allowed to update via Kies or OTA.
Click to expand...
Click to collapse
Well it seemed to update for me. At least the verification process went through. I used Wanam Xposed and had the fake system status thing checked. Either way something went wrong and didn't finish the updating process and got stuck at boot logo with no recovery options.
The OTA update did not work though. I was able to get the update downloading after Wanam, but once the download finished, the update failed before trying to install. Did not try OTA again though I just went to Kies, then Odin. But all 3 methods failed.
Hey Folks, I am using a SM-T210
I downloaded a tool called 'Kingo Root' when reading an Article Here from CNET
I run the tool and followed the instructions and at the end it said 'Device Rooted Successfully' Then restarted my Device.
However It then Got stuck into a boot loader loop. So I followed instructions to put TWRP onto the device
I then thought well why not put a decent firmware on it so I used the (StockKitkatRom_T210(R) V1.7) and Side loaded it the messages appeared and said the flash and kernel were written so I pressed restart.
However my Android is stuck loading into TWRP.
I thought maybe I was just being an idiot so I clicked the 'Advanced' setting and selected 'Factory Reset' and then rebooted and still I got thrown to TWRP.
So I decided fair enough obviously Flashing isnt for me so tried to put Stock Firmware back on and used Odin except it failed at the very end which indicates a NAND RW Error?
So bottom line I'm stuck in TWRP anyone know how to remove it.
Again I am using an SM-T210
Dean_186 said:
Hey Folks, I am using a SM-T210
I downloaded a tool called 'Kingo Root' when reading an Article Here from CNET
I run the tool and followed the instructions and at the end it said 'Device Rooted Successfully' Then restarted my Device.
However It then Got stuck into a boot loader loop. So I followed instructions to put TWRP onto the device
I then thought well why not put a decent firmware on it so I used the (StockKitkatRom_T210(R) V1.7) and Side loaded it the messages appeared and said the flash and kernel were written so I pressed restart.
However my Android is stuck loading into TWRP.
I thought maybe I was just being an idiot so I clicked the 'Advanced' setting and selected 'Factory Reset' and then rebooted and still I got thrown to TWRP.
So I decided fair enough obviously Flashing isnt for me so tried to put Stock Firmware back on and used Odin except it failed at the very end which indicates a NAND RW Error?
So bottom line I'm stuck in TWRP anyone know how to remove it.
Again I am using an SM-T210
Click to expand...
Click to collapse
It seems you need to flash a Stock firmware using ODIN to start freshly.
Please avoid using those Chinese Programs with Original Tablets !
Chinese Programs are designed for Chinese Tablets/Phones
Hope problem is solved by now?
Hey guys I'm new to android. I researched about rooting and I thought I'd give it a go. I followed a step by step instructions for my specific model and I originally used Odin3 1.85. I flashed it and it passed but when I booted up the phone again using power up/home/power buttons it began a system update but then it errored and gave me options to:
Reboot now
Apply update from ADB
wipe data/factory reset
Wipe cache partition
So I researched more and was told that my specific phone (Canadian Telus note 4) worked when flashed with Odin 3.07. So I downloaded that version and when I tried to flash, it got stuck at "setup processing". And now every time I try to go into download mode, it goes to recovery booting which then gives me the same options that I listed above. I don't know how to go back to the regular download mode. I tried removing the battery from a minute and putting it back in and still no luck. When I went to check if my software is up to date it gives me an error because I attempted to root my phone. So I guess since I've already gone that far I might as well root it properly. I assume I've voided my warranty already. Anyway sorry for the long explanation but like I said I'm very new to android operating systems and I'm trying to understand the termology and the whole rooting process. In short I'm not sure what to do from the recovery screen
hi,
so i just got my s6 edge for sprint shipped to me (it wasn't activated to any service when i got it). here is the order of events i took:
1) tried to activate my service, but there was a delay in porting the #
2) while waiting for them to port it, i rooted it, installed twrp and a rom (this was when it was on 5.0.2)
3) they called and said they were ready to port, but the new rom didn't have the activation software in it. so i stalled them and said i would call back. i then reverted back to stock using odin.
4) got the number ported and was fine using the phone at that point.
5) this is where the day turned bad...... i didn't realize that coincidentally today, a new firmware was released to 5.1.1 and the phone auto-updated to it while i wasn't looking
6) i went to go re-root it using the same 5.02 root and now my phone is stuck. it's sitting on the "Samsung Galaxy S6 Edge, Powered by Android" screen and in the top left in red it says "RECOVERY IS NOT SEANDROID ENFORCING"
7) i tried to restore it back to the stock using odin, but it errored in the download mode (i don't remember the error off hand)
i can get into download mode, and that's about it. i had to let the phone's battery die on it's own to turn it off (this phone gets super hot, btw)
so i guess what i need to know is how to restore back to factory default again, now that it thinks it's on 5.1.1. is there any hope?
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
bbacon said:
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
Click to expand...
Click to collapse
check this post, download the tar and flash it in odin. it worked for my phone!
http://forum.xda-developers.com/showpost.php?p=61650724&postcount=142
it got me into a recovery image that worked and i was able to factory reset in there. my phone is booting properly now. (after it reboots when done, it took a bit on the first title screen to do anything, just be patient)
Thanks man, that worked great. Although I found out in the process of trying to fix it the past few days, I must have flashed a non-compatible kernel because once it boots the touch screen is unresponsive. I guess I'll have to wait until the firmware download is available after all. Thanks again for the help though
So I used this guide:
https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
When I got to step 8, the phone would freeze. Super Sume wasn't doing anything. Then the whole phone would freeze. I looked into what it was supposed to do, and I read that this step was just uninstalling the app due to spyware. I figured "I'll worry about that once I get root. Then I can install a whole new rom, and it won't be there regardless." So I moved onto the next step. I got all the way down to step 10, and the adb wouldn't connect. So, I went to reboot the phone, and it says "root is not available, would you like twrp to root?" or something like that. I said yes. Now the phone is in a boot loop. I don't know if I have root or not. I tried doing a factory reset, by wiping. That didn't work. Still boot looping. I know my device isn't lost, but I don't know what the next steps are to getting it back.
I'm also currently downloading http://www.sammobile.com/firmwares/download/65392/N910VVRU2BPA1_N910VVZW2BPA1_VZW/
this, in case I need to start all over with my phone.
Can anyone help me at least get past the bootloop sequence? It goes samsung galaxy screen, samsung animaltion, verizon red screen, then bootloop.
Did you format you're SD card?
Sent from my SM-N920F using Tapatalk
Lost My Mind said:
So I used this guide:
https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
When I got to step 8, the phone would freeze. Super Sume wasn't doing anything. Then the whole phone would freeze. I looked into what it was supposed to do, and I read that this step was just uninstalling the app due to spyware. I figured "I'll worry about that once I get root. Then I can install a whole new rom, and it won't be there regardless." So I moved onto the next step. I got all the way down to step 10, and the adb wouldn't connect. So, I went to reboot the phone, and it says "root is not available, would you like twrp to root?" or something like that. I said yes. Now the phone is in a boot loop. I don't know if I have root or not. I tried doing a factory reset, by wiping. That didn't work. Still boot looping. I know my device isn't lost, but I don't know what the next steps are to getting it back.
I'm also currently downloading http://www.sammobile.com/firmwares/download/65392/N910VVRU2BPA1_N910VVZW2BPA1_VZW/
this, in case I need to start all over with my phone.
Can anyone help me at least get past the bootloop sequence? It goes samsung galaxy screen, samsung animaltion, verizon red screen, then bootloop.
Click to expand...
Click to collapse
Did you get it working??
Sent from my SM-N920F using Tapatalk
I did. I followed that guide about 4 times, and each time I had to reflash to stock with odin. As all this was happening, on a second computer I was researching why it was bootlooping. Well, as it turns out, the guide is bad. The reason I was bootlooping is because 5.1.1 has a special security detection that if it detects root, it will bootloop. You need a different kernal, but his guide said to turn the phone back on after root but before flashing the new kernal.
So, eventually I just tried my own way. I got the bootloader unlocked, and then went into twrp, to flash the new kernal and supersu from zip. It worked.
As I type this, I'm backing up my real SD card (I used a smaller temporary one for the root process), because I'm going to format this, and only put my pictures/old apks/music on it. That should clear up 90% of the space. After I have it backed up, formatted, and files moved to the SD card I will be flashing my first rom.
I have chosen http://forum.xda-developers.com/not...rom-dr-ketan-rom-dr-ketan-rom-l16-n5-t3370495
this to be my new Rom
Lost My Mind said:
I did. I followed that guide about 4 times, and each time I had to reflash to stock with odin. As all this was happening, on a second computer I was researching why it was bootlooping. Well, as it turns out, the guide is bad. The reason I was bootlooping is because 5.1.1 has a special security detection that if it detects root, it will bootloop. You need a different kernal, but his guide said to turn the phone back on after root but before flashing the new kernal.
So, eventually I just tried my own way. I got the bootloader unlocked, and then went into twrp, to flash the new kernal and supersu from zip. It worked.
As I type this, I'm backing up my real SD card (I used a smaller temporary one for the root process), because I'm going to format this, and only put my pictures/old apks/music on it. That should clear up 90% of the space. After I have it backed up, formatted, and files moved to the SD card I will be flashing my first rom.
I have chosen http://forum.xda-developers.com/not...rom-dr-ketan-rom-dr-ketan-rom-l16-n5-t3370495
this to be my new Rom
Click to expand...
Click to collapse
Please help! what was your own way and what did you do to get the bootloader unlocked?