Hi,
Just used chainfires rooting program for my galaxy note 2. Did everything correctly , odin and the phone showed everything done right.But after re- booting, something in phones security blocked the rooting. What can I do?
describe clearly
was ur boot loader unlocked? and was the phone carrier specific like u bought the phone from at&t,tmobile,verizon or sprint?
root blocked
[email protected] said:
was ur boot loader unlocked? and was the phone carrier specific like u bought the at&t,tmobile,verizon or sprint?
Click to expand...
Click to collapse
My phone is the AT&T version of the note 2. The root that I used was for this version. As for the boot loader, I'm not sure what you mean. I ran not the files through odin, just as described in the video.odin showed that everything was good. As did the phone until it re booted. Samsung is doing automatic Security updates now. And after the phone booted up, a message popped up from Samsung saying "an attempt to access a Secure area of your phone without authorization has been blocked."
My next step will be to install a custom rom. But I don't know if they will be able to block me from accomplishing this as well. This whole thing is really getting frustrating. It all started when I ran the update to 4.3 couple of weeks ago, and lost my tethering ability. This all I want. Just to get the free tethering app to work again. I had jelly bean 4.1.2. And the tethering app worked perfectly every time. Now with 4.3, doesn't work anymore. Do I need to downgrade back to 4.1.2? Or is their an easier solution? I'm wondering if it will matter what jelly bean you're using anymore if they're going to do auto security up dates that block all these type of things like custom rooms and rooting. Please tell me I'm wrong!
Thanks.
skoobiesnack said:
My phone is the AT&T version of the note 2. The root that I used was for this version. As for the boot loader, I'm not sure what you mean. I ran not the files through odin, just as described in the video.odin showed that everything was good. As did the phone until it re booted. Samsung is doing automatic Security updates now. And after the phone booted up, a message popped up from Samsung saying "an attempt to access a Secure area of your phone without authorization has been blocked."
My next step will be to install a custom rom. But I don't know if they will be able to block me from accomplishing this as well. This whole thing is really getting frustrating. It all started when I ran the update to 4.3 couple of weeks ago, and lost my tethering ability. This all I want. Just to get the free tethering app to work again. I had jelly bean 4.1.2. And the tethering app worked perfectly every time. Now with 4.3, doesn't work anymore. Do I need to downgrade back to 4.1.2? Or is their an easier solution? I'm wondering if it will matter what jelly bean you're using anymore if they're going to do auto security up dates that block all these type of things like custom rooms and rooting. Please tell me I'm wrong!
Thanks.
Click to expand...
Click to collapse
as of my knowledge ur bootloader was locked and KNOX was installe on ur mob through security updates and u might have to flash stockrom of specific model number search for flashing stock rom search for ur model number and carrier specific roms ask for it in the q&a thread for ur specific mobile you can ask for it <a href=http://forum.xda-developers.com/galaxy-note-2-att><here>
Related
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
scottrf8 said:
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
Click to expand...
Click to collapse
I don't have a Note (I have the GS3 on TMO). Do you have any idea if the Note 2 has the same issue that the GS3 has, where with the 4.3 update you get a new locked bootloader that prevents you from going back to anything earlier than 4.3? That's the way it is on the GS3. I guess if you were able to actually boot up and make calls after you downgraded back to 4.1.1, then that must not be the case.
In any case, you're getting stuck on the boot logo when you power it on? Can you get into the recovery at all? Do you have the stock recovery or a custom recovery installed? Have you tried clearing cache/dalvik and fixing perms? That often fixes things for me when I'm stuck on the boot logo.
scottrf8 said:
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
Click to expand...
Click to collapse
I start to wonder if people research before doing anything.
To say again. You can't downgrade. You have Knox. You possibly tripped the Knox flag. Reflash the 4.3 stock ROM. If that fails, It's most probably eFuse, if It's 4.3.
(Basically, eFuse messes up your phone aka bricks You phone aka @#%& it up.)
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
---------- Post added 5th January 2014 at 12:05 AM ---------- Previous post was 4th January 2014 at 11:59 PM ----------
mcgrabowski said:
I don't have a Note (I have the GS3 on TMO). Do you have any idea if the Note 2 has the same issue that the GS3 has, where with the 4.3 update you get a new locked bootloader that prevents you from going back to anything earlier than 4.3? That's the way it is on the GS3. I guess if you were able to actually boot up and make calls after you downgraded back to 4.1.1, then that must not be the case.
In any case, you're getting stuck on the boot logo when you power it on? Can you get into the recovery at all? Do you have the stock recovery or a custom recovery installed? Have you tried clearing cache/dalvik and fixing perms? That often fixes things for me when I'm stuck on the boot logo.
Click to expand...
Click to collapse
You're right. The locked bootloader messed those who didn't research about it's life's real bad. 4.3 supposedly has eFuse in it, which FU*CKS your phone. I read it up on the Samsung Knox website, and it said that eFuse "rewrites a read-only part of the phone, resulting in a unusable phone." If u triggered that, it'll be a hard brick, (in my knowledge)
Knox itself is irritating. The Knox Warranty Void counter, which max at 1, is unresetable, (even with JTAG, will brick if h try) so your warranty is *poof*
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
I did a fair amount of research before downgrading. In fact I didn't want to downgrade, but I did want to unlock it. It is unlocked and it's running on 4.1.1. So when you say that you can't downgrade, you mean you shouldn't downgrade cause then you will be stuck with 4.1.1?
scottrf8 said:
I did a fair amount of research before downgrading. In fact I didn't want to downgrade, but I did want to unlock it. It is unlocked and it's running on 4.1.1. So when you say that you can't downgrade, you mean you shouldn't downgrade cause then you will be stuck with 4.1.1?
Click to expand...
Click to collapse
When you were on 4.3, was that an OTA update or an ODIN flash of a stock firmware? Or did you just have a 4.3 ROM from the forums that you loaded (AOSP or rooted stock based ROM with Knox, etc., removed) with TWRP or CWM? Supposedly from what I've been reading if you take the 4.3 OTA or ODIN flash the stock 4.3, the bootloader gets updated, as Irwenzhao mentions above and I've experienced, where you CAN'T downgrade again to 4.1.2 or earlier. I believe that just means you can't go back to a fully stock pre 4.3. I THINK it just means you can't ODIN back to a factory image earlier than 4.3, which is what I experienced. But with TWRP or CWM, I believe I can still load other ROMs at will regardless if they are pre 4.3 or not.
yeah, that sounds kinda like the same thing I have come across. 4.3 was OTA and downgraded to a stock 4.1.1 ROM. Guess this triggers KNOX cause now KNOX WARRANTY VOID is 1. which once that is triggered, you cannot go from a non KNOX version (4.1.1) to a version that has KNOX. My question now is does that apply to just the stock firmware? Would ANY of the ROM's created by the devs work?
There were some posts in the unlock thread that people were able to go from 4.1.1 (after downgrading) back up to 4.3. Just trying to figure out how that would be the case? Could the knox warranty flag not have been set for them?
scottrf8 said:
yeah, that sounds kinda like the same thing I have come across. 4.3 was OTA and downgraded to a stock 4.1.1 ROM. Guess this triggers KNOX cause now KNOX WARRANTY VOID is 1. which once that is triggered, you cannot go from a non KNOX version (4.1.1) to a version that has KNOX. My question now is does that apply to just the stock firmware? Would ANY of the ROM's created by the devs work?
There were some posts in the unlock thread that people were able to go from 4.1.1 (after downgrading) back up to 4.3. Just trying to figure out how that would be the case? Could the knox warranty flag not have been set for them?
Click to expand...
Click to collapse
Just to make it clear, Knox is a bootloader, which means u can flash anything that's not a bootloader, but your warranty would be history. Flashing anything trips the flag, even 4.1.1/2 stock ROMs.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
Truthfully, that doesn't clear it up. Do the stock firmware through Kies or ota include a bootloader and that's why it won't install? Thanks
Flashing the stock firmware through kies, ODIN, or the OTA update will update the boot loader as far as I know and will ruin any chance of returning to stock and void your warranty. As long as you don't want to do that, I don't think it's too big of a deal.
At this point, I couldn't care less about the warranty. I would think it's expired now anyhow. As long as I can flash ROMs and boy the phone up and use it. I'm happy.
Sent from my SGH-T999 using xda app-developers app
I have read threads all day and tried to use a few ways to root my phone but i keep getting failures or some error warnings (not real errors)
I cant seem to access towelroot to try it - is there something i am doing wrong or is it no longer available? i tried searching the forum and i didnt find any answers
I am on Verizon S3 - 535, v4.4.2, NE1 (last kernel update may 20th) Build VRUDNE1
I tried ONIN and it failed - could not even get boatloader to go through....
Can someone help please? i really dont know what to do next. I am already international and now have access to text and phone but no data unless i am on Wifi (which i need to find my way around)
Thanks!
KipKip! said:
I have read threads all day and tried to use a few ways to root my phone but i keep getting failures or some error warnings (not real errors)
I cant seem to access towelroot to try it - is there something i am doing wrong or is it no longer available? i tried searching the forum and i didnt find any answers
I am on Verizon S3 - 535, v4.4.2, NE1 (last kernel update may 20th) Build VRUDNE1
I tried ONIN and it failed - could not even get boatloader to go through....
Can someone help please? i really dont know what to do next. I am already international and now have access to text and phone but no data unless i am on Wifi (which i need to find my way around)
Thanks!
Click to expand...
Click to collapse
I have versions 1 & 3 of towelroot. The first version may work better. Do you have an international sim card or are you still attempting to use the vzw one?
From my Wicked S3 running MIUI
ShapesBlue said:
I have versions 1 & 3 of towelroot. The first version may work better. Do you have an international sim card or are you still attempting to use the vzw one?
From my Wicked S3 running MIUI
Click to expand...
Click to collapse
I was able to actually root it with Kingo Root
The only other issue is still getting the message SIM not recorgnized even though the phone, data and text are working on the local network. I have configured the APN to point to the carrier but the message still pops up when i reboot or if my phone is in idle mode
Good afternoon all if anyone could please help I'd greatly appreciate it!
So I just bought a Sprint Galaxy S5 from ebay with the assumption that with some customizing I'd be able to get the phone domestically unlocked. I got the phone and it was already updated to 5.0 Lollipop so I followed this tutorial to get the SSU.apk to actually work
http://forum.xda-developers.com/spr...locking-sprint-galaxy-s5-g900p-t3085624/page2
After a lot of time I was successful at rooting the phone and was able to downgrade to 4.4.4 but the tutorial calls for 4.4.2 but it seems that 4.4.4 was the only fw that would successfully install.
But now here's the problem I was able to obtain the domestic unlock code through Sprint but now the activation/update app doesn't work and doesn't open automatically the way that the reps said it would,. I've tried to reset stock through Kies but Kies doesn't recognize the phone. I've also tried to use Odin through out this process not only to reset back to stock but also downgrade the fw and the modem. The really annoying part is that small PDA/AP updates and installs work fine but when I try to Odin the original tars it always fails 100% getting a "sw rev check fail aboot fused 2 binary 1 " error on my phone.
I really don't know what to do at this point, and it seems the error is associated with a soft brick but the device still powers on and boots.
I thought this would be a pretty straight forward process but I've hit the wall and am losing my mind, I need help!
P.s. I flashed 4.4.4 fw with CWM and the device is still rooted
Thanks
So basically I never wanted to update my phone but I accidentally pressed Install Now when I was trying to open the messaging app. Now I can't root it anymore or downgrade it. Worst mistake ever for my phone :crying:
So my phone found a new update, but I don't want to update it because I want to look for a updated ROOTED rom that is later than OG7. If anyone has a odin flashable / zip flashable, PLEASE message me. I have a friend that works with android roms, he said that its something to do with the bootloader and it has to be rewritten by hand to make it rootable because of verizons bootloader, and to unlock the bootloader. PingPongRoot doesn't work anymore after the 5.1.1 update. I really hate this update. it slowed my phone down a lot. **** you verizon :crying::crying::crying:
Anyways I need a rooted rom to flash on my phone to make my phone think its signed by Samsung or Verizon and it's a new update. Please help me root my phone. I really got nothing to root it now ;-;
AndroidFan16 said:
So basically I never wanted to update my phone but I accidentally pressed Install Now when I was trying to open the messaging app. Now I can't root it anymore or downgrade it. Worst mistake ever for my phone :crying:
So my phone found a new update, but I don't want to update it because I want to look for a updated ROOTED rom that is later than OG7. If anyone has a odin flashable / zip flashable, PLEASE message me. I have a friend that works with android roms, he said that its something to do with the bootloader and it has to be rewritten by hand to make it rootable because of verizons bootloader, and to unlock the bootloader. PingPongRoot doesn't work anymore after the 5.1.1 update. I really hate this update. it slowed my phone down a lot. **** you verizon :crying::crying::crying:
Anyways I need a rooted rom to flash on my phone to make my phone think its signed by Samsung or Verizon and it's a new update. Please help me root my phone. I really got nothing to root it now ;-;
Click to expand...
Click to collapse
Sorry, it doesn't exist for the Verizon Galaxy S6. The last rooted ROM was OE2.
Mike
AndroidFan16 said:
So basically I never wanted to update my phone but I accidentally pressed Install Now when I was trying to open the messaging app. Now I can't root it anymore or downgrade it. Worst mistake ever for my phone :crying:
So my phone found a new update, but I don't want to update it because I want to look for a updated ROOTED rom that is later than OG7. If anyone has a odin flashable / zip flashable, PLEASE message me. I have a friend that works with android roms, he said that its something to do with the bootloader and it has to be rewritten by hand to make it rootable because of verizons bootloader, and to unlock the bootloader. PingPongRoot doesn't work anymore after the 5.1.1 update. I really hate this update. it slowed my phone down a lot. **** you verizon :crying::crying::crying:
Anyways I need a rooted rom to flash on my phone to make my phone think its signed by Samsung or Verizon and it's a new update. Please help me root my phone. I really got nothing to root it now ;-;
Click to expand...
Click to collapse
Have you tried updating to Marshmallow? I'm on CleanROM 1.5 android 5.0.2 OE2, and have been curious of the new android version, but at the same time do not want to lose root. Let me know if Marshmallow is worth losing root. Only advantage I see to root at this point is not having all that damn bloatware I really hate and cannot remove without root. Thanks.
isruco said:
Have you tried updating to Marshmallow? I'm on CleanROM 1.5 android 5.0.2 OE2, and have been curious of the new android version, but at the same time do not want to lose root. Let me know if Marshmallow is worth losing root. Only advantage I see to root at this point is not having all that damn bloatware I really hate and cannot remove without root. Thanks.
Click to expand...
Click to collapse
I rather not update it unless
1: A root method is available
2: A rooted rom for Marshmallow is available
Just saying. upgrading to 5.1.1 unintentially (mainly because i was directly going to the messaging app but accidentally pressed install now) made me loose my root access. That's why I'm seeing if there is a rooted rom for that rom or a root method for that room.
AndroidFan16 said:
I rather not update it unless
1: A root method is available
2: A rooted rom for Marshmallow is available
Just saying. upgrading to 5.1.1 unintentially (mainly because i was directly going to the messaging app but accidentally pressed install now) made me loose my root access. That's why I'm seeing if there is a rooted rom for that rom or a root method for that room.
Click to expand...
Click to collapse
From what I understand, it seems verizon is never going to allow it. Just look at Note 4 from verizon, it came out in 2014 and still no sign there will ever be root available for that one either. I'm even considering moving to tmo since there is root on their devices. Good luck.
isruco said:
From what I understand, it seems verizon is never going to allow it. Just look at Note 4 from verizon, it came out in 2014 and still no sign there will ever be root available for that one either. I'm even considering moving to tmo since there is root on their devices. Good luck.
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913
sent from your mom's phone.
Droid_JD said:
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913
sent from your mom's phone.
Click to expand...
Click to collapse
Wow, I'll have to check this out. Maybe verizon SGS6 5.1.1 and later will come some day as well.
Thanks for the info :victory:
isruco said:
Wow, I'll have to check this out. Maybe verizon SGS6 5.1.1 and later will come some day as well.
Thanks for the info :victory:
Click to expand...
Click to collapse
Still sticking in 5.1.1
maybe it might work in the future exploits
So yesterday I got this Samsung Galaxy S III that was I535 but had a I9300 4.1.2 Firmware in it. (I don't know how was it there) It had been rooted. I don't know about the bootloader if it was locked or unlocked.
I wanted to install the official firmware for i535 so I used Odin to flash I535's official 4.4.2 (downloaded from sammobile.com) and it worked fine. I then used towelroot v3 apk to root the phone and it got rooted again, then I used safestrap 3.71 to install custom recovery and that too went well.
I then flashed a zip to get Motolora Cricles widget, although that didn't install properly but my phone was still working fine until then. Then I used EZUnlock14 to unlock my bootloader and the app supposedly decraled that my bootloader was "now" unlocked, again I couldn't confirm because that's when the problem starts.
After closing that app I plugged in my phone through usb cable to my laptop and had been using it for facebook and texting. Then I turned off my phone and it never turned on back again.
When I connect it to the PC now, it is not recognized and Device manager shows QHSUSB_DLOAD device
I hope somebody can help me with that.
well, ya dun messed it up. But its fixable. For future reference, never try a bootloader unlock app, thats what messed yours up. Those apps only work on 4.2.2 bootloader phones and have caused many a headache for lots of folks. Lemme grabe you a link quick.
here ya go. this will get it fixed for ya
http://forum.xda-developers.com/showthread.php?p=68239621#post68239621