VRALL4 soft bricked my phone. "System software not authorized by Verizon Wireless" - Verizon Samsung Galaxy Note II

VRALL4 soft bricked my phone. "System software not authorized by Verizon Wireless"
This update bricked my phone and I don't know why. I was watching YouTube videos, went to go pee and came back to a "System software is not authorized by Verizon Wireless" message. This was minutes before I had to leave to work so I just popped my SIM in my galaxy nexus . Anybody know how to undo this? I got no warnings of update. I only found out about the update just now online. it sopped working around 10am pst ,the time of update (at least this was a constant time I found online for it). Im rooted but not unlocked cause I had no desire to change Roms. And thus I am not backed up at all.
Any way to fix without Odin stock flash? I wanted to give up on flashing with this phone. Ugh.
Thanks

Nope. Had the same thing and had to Odin.

It has a bootloader in it. If you guys are gonna mess with your devices, you need to steer clear of OTAs unless given the all clear by those who know.

adrynalyne said:
It has a bootloader in it. If you guys are gonna mess with your devices, you need to steer clear of OTAs unless given the all clear by those who know.
Click to expand...
Click to collapse
Exactly my point. I never wanted to mess with this phone. Never even wanted to unlock it. Didnt get an option to update. The screen just popped up.
If I had the option I would of said no since I didnt want to lose root. I need my RootDim app or all go crazy.
But thanks adrnalyne. I've always admired your work but now try and stay clear of all this ROM/kernel business.
If anybody would know what happen I thought you would. Spontaneous Verizon bricking...

lazynok said:
Exactly my point. I never wanted to mess with this phone. Never even wanted to unlock it. Didnt get an option to update. The screen just popped up.
If I had the option I would of said no since I didnt want to lose root. I need my RootDim app or all go crazy.
But thanks adrnalyne. I've always admired your work but now try and stay clear of all this ROM/kernel business.
If anybody would know what happen I thought you would. Spontaneous Verizon bricking...
Click to expand...
Click to collapse
I've a feeling its the bootloader, although it shouldn't have been possible if you had a custom recovery. Were you using the stock recovery?

If you did anything besides root your phone, the OTA should have failed at some point in the verification process.

adrynalyne said:
I've a feeling its the bootloader, although it shouldn't have been possible if you had a custom recovery. Were you using the stock recovery?
Click to expand...
Click to collapse
Yeah stock recovery. I've never even booted to recovery. Loved this phone just the way it was. Maybe I'll just Odin tonight after work and lose everything. Is this a Verizon problem or does this screen come up with other carriers? Will this phone work on ATT or T-Mobile? Last straw with vzw. I can't get a concrete answer online. Some say yes some say no

lazynok said:
Yeah stock recovery. I've never even booted to recovery. Loved ne just the way it was. Maybe I'll just Odin tonight after work and lose everything. Is this a Verizon problem or does this screen come up with other carriers? Will this phone work on ATT or T-Mobile? Last straw with vzw. I can't get a concrete answer online. Some say yes some say no
Click to expand...
Click to collapse
Changing carrier won't stop the annoyances you see with the device. You have to change the device too.
As I mentioned in another thread, all carriers suck. It wasn't all that long ago that ATT didn't allow sideloading.

Re: VRALL4 soft bricked my phone. "System software not authorized by Verizon Wireless
lazynok said:
Yeah stock recovery. I've never even booted to recovery. Loved this phone just the way it was. Maybe I'll just Odin tonight after work and lose everything. Is this a Verizon problem or does this screen come up with other carriers? Will this phone work on ATT or T-Mobile? Last straw with vzw. I can't get a concrete answer online. Some say yes some say no
Click to expand...
Click to collapse
That's what you'll have to do is ODIN back to stock and start over
Doin' big thangs from my Note Deuce

Yeah. You managed to softbrick it.....odin back to stock is easier than bricking your phone.

Re: VRALL4 soft bricked my phone. "System software not authorized by Verizon Wireless
I have that issue now..im using wifeys phone. I can get to download mode. I flashed stockroot66 from galaxynote2.com it went 75% then failed. I tried the stock rom as well. No go on my end.
I think I have to unick bootloader and then flash the stock rom. Is that possible for me to unlock bootloader then flash?
I hope im making sense. Please correct me if im wrong.
Sent from my Portable SCH-I605

maybe this will help ... try at your own risk tho
try to find this in the forum under verizon galaxy note 2 ...original development its from droidstyle 1st December 2012, 11:43 AM (Last edited by droidstyle; Yesterday at 03:37 PM.) #1
Senior Member - OP
Thanks Meter 2283
Posts: 4,883
Join Date: May 2011
Location: Fort Wayne
MORE INFO >
[GUIDE][VZW Edition]How to Root/Recovery/Rom the VZW Galaxy Note II!
Here is a guide I have put together for the VZW Samsung SCH-I605 Galaxy Note II
it should help just take your time it worked for me and on you tube adam outler has a vid. that shows you how ..... i flashed a tmobile rom the other day and locked up mine and got the same message but luckily i had custome recovery and wiped it away and flashed my back up ...if it works youll have TWRP recovery ...MAKE A BACKUP right from jump in case it trys to update again ... hope ive helped you :victory:

click the note 2 link in my sig and don't use anything from galaxynote2.com...xda has everything you need right here and its guaranteed to be from original source.

Related

Accept T-Mobile Update?

My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
JJMT said:
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
Click to expand...
Click to collapse
Shouldn't break anything. Most are still waiting for the update. Personally I was impatient and flashed it through ODIN last night.
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
JJMT said:
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
Click to expand...
Click to collapse
Go to the Development section that are a few threads about this. I looks like anyone with a lag fix, or GPS fix (from JI2) where having this issue, plus I have seen stock people having it too.
Or you can go read my blog post here. the post tells the steps I took to get back the JFD, but you could flash JI6 instead.
you will need to flash JI6 with ODIN to restore, you can not just do a nandroid restore, it is an issue with the kernel and nandroid does not restore/backup the kernel.
*facepalm*@Samsung
http://forum.xda-developers.com/showthread.php?t=803492
Anderdroid said:
*facepalm*@Samsung
Click to expand...
Click to collapse
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
dan0zone said:
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
Click to expand...
Click to collapse
So now instead, they get flooded with returns because the phone isn't what people expected.
zephiK said:
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
Click to expand...
Click to collapse
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
camalot said:
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
Click to expand...
Click to collapse
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
zephiK said:
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
Click to expand...
Click to collapse
Well, I know the 2 people that updated stock and got stuck at the vibrant screen were 100% stock because they both called me on what they need to do. one came over and I fixed it with ODIN back to stock (JI6) and the other just said he'd call TMO and get a replacement. they dont even know what rooting is, or that there is a site like that that they can get files to do "one click root"
OK. I'm the OP and I'm back. I was traveling today (with a phone flashed back to stock - that's as far as I got before getting kicked out of the hotel). I've now got the ROM restored and I'm where I was before trying to install the update.
My question is this (probably simple): my phone still wants to do the update. How do I make it go away? I can't install it, and I don't want to have to postpone it every day. Is there a cache I can clear or something?
You could just update it through Odin. I'm on stock with root and JAC's oc/uv kernel and the OTA failed but Odin worked perfectly.
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
JJMT said:
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
Click to expand...
Click to collapse
It will only stop once you are on JI6
camalot said:
It will only stop once you are on JI6
Click to expand...
Click to collapse
OK. I guess I will have to try to push the update through odin. Can someone point me to a link to the files?
I'm kind of irritated by this whole thing. I'm pleased with tmo for pushing the update out, but I mean, really, even Windows allows you to decline to install an update.
http://forum.xda-developers.com/showthread.php?t=798125
chad658eku said:
http://forum.xda-developers.com/showthread.php?t=798125
Click to expand...
Click to collapse
Thanks for the link. It really looks to me that I'm going to need to flash to a stock ROM before flashing JI6. That, as they say, is a bummer.
As I am actually quite content at the moment with Vibrant9, it really seems to me that it would be easier to somehow remove whatever it is on my phone that is requesting that I update. Presumably there is an update.zip file sitting somewhere, that will be copied into sdcard before the updater involves reboot recovery. Any ideas where to look?
I would really rather not do any further flashing until is an official Froyo to flash to.
JWhipple said:
So now instead, they get flooded with returns because the phone isn't what people expected.
Click to expand...
Click to collapse
Flooded with returns by morons who think they are smart.

[Q] Trouble unlocking i777 after root.

I have root, the first time it froze and didn't sent a test correctly. So I tried it again using Super one. Now I have superuser. Tried both apps on the market and neither one seem to have worked thus yet.
When I try Herolz Galaxy s unlock It is unable to copy EFS, All it says is Done, Error, Not saved. And yes there is an SD card present.
The GS2 unlocker also available on the market will fart around for over 5 minutes and say unlock code not found.
What gives am I doing something wrong? I have tried it with the sim in and with it out. Using Family mobile from Walmart, so I am guessing Tmobile sim card.
Please give me some other root around this.
android 2.3.4
I777UCKH7
kernel version 2.6.35.7
Just go to stock and reroot
Sent from my SGH-I777 using XDA
I didn't know ti wasn't stock. LOL . I just bought it used from a shop here yesterday as am upgrade from gs1. Could you possibly direct me in the right direction as I am unsure what part you are talking about mot being stock.
Than ks in advance
you know you'll only get Edge on Tmo bands.
KH7 is stock, but you stated you have root. Did you do it? if not then check the android Development forums on how to get back to stock. and start the root proccess again.
I got the root through superoneclick. It seemed it did ok as the secong time I went through it said it was already rooted. as for the crappy internet it won't really matter here as we don't even have 3g here in this town for t-mobile anyhow.
if I un-root and re flash back to stock just using the button press combo work? Any why does it only get edge on tmobile?
-Steve
stevewasthere said:
if I un-root and re flash back to stock just using the button press combo work? Any why does it only get edge on tmobile?
-Steve
Click to expand...
Click to collapse
Unroot and back to stock would require Odin/Heimdall.
Only gets Edge on Tmo because its an at&t phone. different bands for 3g.
I have used Super One Click in the past, but its just easier to flash a rooted kernal in Odin/Heimdall, then flash a custom ROM via CWM.
Back to stock is mainly because SuperOneClick is an old tool. and then starting fresh with the latest.
But I had no need to unlock my phone, but from what I've heard its very simple, and most dont have any issues. using the app from the market
I am not afraid of ODIN. I have done that in the past but I did have a huge problem with the GS1 installing an older kernel. I just about bricked the phone. I had to use the HEimdall or what ever it was to get back in it.
On these phone with a custom kernal and rom will it automatically unlock the phone? I am just afraid of using the wrong one and in this particualr section I am sure as to where to go. It doesn't give a whole lot of detail and with the cryogen mod thing it is getting places where I am not sure if I want to really try that. I would but the information is spaced out so much I am afraid of missing something and buggering everything up. What should I have to worry about when doing this?
Also it is the software unlocking I am having problems with.
stevewasthere said:
I am not afraid of ODIN. I have done that in the past but I did have a huge problem with the GS1 installing an older kernel. I just about bricked the phone. I had to use the HEimdall or what ever it was to get back in it.
On these phone with a custom kernal and rom will it automatically unlock the phone? I am just afraid of using the wrong one and in this particualr section I am sure as to where to go. It doesn't give a whole lot of detail and with the cryogen mod thing it is getting places where I am not sure if I want to really try that. I would but the information is spaced out so much I am afraid of missing something and buggering everything up. What should I have to worry about when doing this?
Also it is the software unlocking I am having problems with.
Click to expand...
Click to collapse
Custom kernal will not unlock the phone to be used on a network other than at&t.
Software unlock? assuming you mean using s/w to unlock the device, yes thats the way i understood this thread. I cant really tell ya much about that, but i have heard that its easy and works fine, which is why you should go back to stock first, to get rid of anything messy leftover from using an old rooting method.
stevewasthere said:
I have root, the first time it froze and didn't sent a test correctly. So I tried it again using Super one. Now I have superuser. Tried both apps on the market and neither one seem to have worked thus yet.
When I try Herolz Galaxy s unlock It is unable to copy EFS, All it says is Done, Error, Not saved. And yes there is an SD card present.
The GS2 unlocker also available on the market will fart around for over 5 minutes and say unlock code not found.
What gives am I doing something wrong? I have tried it with the sim in and with it out. Using Family mobile from Walmart, so I am guessing Tmobile sim card.
Please give me some other root around this.
android 2.3.4
I777UCKH7
kernel version 2.6.35.7
Click to expand...
Click to collapse
You get this error when you dont reboot the phone after installing busybox and Herolz Galaxy s phone. Just reboot and try. Same happened for me
stevewasthere said:
I got the root through superoneclick. It seemed it did ok as the secong time I went through it said it was already rooted.
Click to expand...
Click to collapse
You're probably fine as is. Look in Settings | About Phone. If you are stock UCKH7 it should read something like -
Android version 3.2.4
Baseband version UCKH7
Kernel version 2.6.35.7
And why does it only get edge on tmobile?
Click to expand...
Click to collapse
AT&T hardware handles different frequencies than T-Mobile hardware. It's a limitation of the phone's capability to receive the signal.
Try this thread for unlocking the phone.
FIXED!!
Stupid busy box was causing errors. re-downloaded it from the market and installed. Whoalla, unlocked. WTF.... Stupid phone. HAHAHA Thanks...
Trouble Unlocking After Odin Root of
I rooted my phone using Odin and the Siyah-v3.4.2-nomswap-I777.tar file in the PDA. The phone passed, and it reloads with the triangle on the start up as expected. However, it then says "enter network lock control key". It has nothing to do with the sim, as the sim works in another phone. I have done the process several times, running odin back to the original factory settings with I777UCLE5_I777ATTLE5_I777UCLE5_HOME.tar.md5
Could someone please tell me how to get the phone unlocked?
I have done this process before with another i777 phone, and it worked fine.
KEITH000000 said:
I rooted my phone using Odin and the Siyah-v3.4.2-nomswap-I777.tar file in the PDA. The phone passed, and it reloads with the triangle on the start up as expected. However, it then says "enter network lock control key". It has nothing to do with the sim, as the sim works in another phone. I have done the process several times, running odin back to the original factory settings with I777UCLE5_I777ATTLE5_I777UCLE5_HOME.tar.md5
Could someone please tell me how to get the phone unlocked?
I have done this process before with another i777 phone, and it worked fine.
Click to expand...
Click to collapse
Just go back to stock 2.3.4 and go from there.
Sent from Team Pirate Headquarters. AKA yer moms basement.
Also, why expect the triangle? Only time I've seen a triangle is in other people's screenshots...
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
aviseqdas said:
You get this error when you dont reboot the phone after installing busybox and Herolz Galaxy s phone. Just reboot and try. Same happened for me
Click to expand...
Click to collapse
I have tried re-installing both software and then reboot. still no luck.:crying:

Unable to unlock 2.3.4

Hello guys!
I have troubles unlocking my Atrix for a while........
I am rooted with 2.3.4/4.5.91 AT&T stock version.
When I try to unlock my device I get OEM Unlock is not implemented....
Now I know that this is due to the fact that the bootloader is not unlockable. That's why I try to flash the sbf file with the one that is unlockable but this is where i actually fail...............
When I try to Flash the phone with RSD Lite (I have tried with both 4547-fix-try2.sbf and with the big one 1.4GB) it goes to 100% when the phone is suppose to reboot. The phone actually reboots but get stuck at the MOTO LOGO while the RSD Lite gives me the ERROR Unable to Re-enumerate something.... Even if i w8 an hour is still dosnt boot until i pull off the battery. Then my phone starts normaly.........
I have tried to go into fastboot after the freez and try the fastboot oem unlock but still I get the OEM Unlock is not implemented.....
I guess that the whole reason for not unlocking the phone is that I am unable to flash the sbf file.
I want to point out that I have all drivers installed and working correctly.
Also I am unable to Install 2.3.6 OTA Update. It downloads it from the servers and when the phone reboots it gets the triangle mark and unable to update then loads normally .....
So everything points out to not being possible to update sbf...
I am asking for any solution or sugestions since I have tried everything on the forums... I love the phone it's been surving me good for 1 and a half year already. I am not afraid of breaking it since it had its times. Only newer version would save it from replacement (tried of that laggy blur interface....)
PS: Thats wierld phone i cant even hardbreak....
I would be realy happy if someone can help ... ;(
Noone ;(
you've got yourself a blocked bootloader. No one has been able to get passed it. Unfortunately you can't unlock it.
Sorry bro... You got unlucky and got an atrix with an impossible boot lock. There is one method i know of.. It hard bricks so many phones it wasnt worth the devs time to finish.
Dohhh
Well may u link the thread so I can see it
Would be interesting to me..
pre4speed said:
you've got yourself a blocked bootloader. No one has been able to get passed it. Unfortunately you can't unlock it.
Click to expand...
Click to collapse
I am not sure if this is true. I have a permalocked boot loader and only know this to be a problem on 4.5.141. I may be wrong but I would keep at it.
But you do seam to get the same error on phone. It is strange that you cannot OTA. I was locked on 4.5.141 and just took the soak test OTA to I think it was 4.5.145 or something like that
affiatic said:
I am not sure if this is true. I have a permalocked boot loader and only know this to be a problem on 4.5.141. I may be wrong but I would keep at it.
But you do seam to get the same error on phone. It is strange that you cannot OTA. I was locked on 4.5.141 and just took the soak test OTA to I think it was 4.5.145 or something like that
Click to expand...
Click to collapse
Have you tried to unlock again after the OTA? Would be interesting to know if its unlockable now.
pre4speed said:
Have you tried to unlock again after the OTA? Would be interesting to know if its unlockable now.
Click to expand...
Click to collapse
Yes tried and failed. Same error message as 4.5.141.
affiatic said:
Yes tried and failed. Same error message as 4.5.141.
Click to expand...
Click to collapse
Damn Motorola. Wont give ice, wont give you the options to make your phone better. Makes me double glad I went to Samsung.
pre4speed said:
Damn Motorola. Wont give ice, wont give you the options to make your phone better. Makes me double glad I went to Samsung.
Click to expand...
Click to collapse
On the galaxy note here. Selling atrix Friday. Held off to try the soak. Nothing great in it so selling.
My wife is keeping her atrix on cm10 for now.
affiatic said:
On the galaxy note here. Selling atrix Friday. Held off to try the soak. Nothing great in it so selling.
My wife is keeping her atrix on cm10 for now.
Click to expand...
Click to collapse
Im not selling mine. Gonna keep as a backup. I've actually got 2 atrixes, one is my bf and I keep the other for the backup to his and in case my Sammy (skyrocket) dies. Its not a bad phone just the manufacturer has burned too many bridges over wide rivers.
pre4speed said:
Im not selling mine. Gonna keep as a backup. I've actually got 2 atrixes, one is my bf and I keep the other for the backup to his and in case my Sammy (skyrocket) dies. Its not a bad phone just the manufacturer has burned too many bridges over wide rivers.
Click to expand...
Click to collapse
Just put cm10.1 jelly beer on note today. Very smooth and fully functional. I recommend. Sorry to OP for off topic
affiatic said:
Just put cm10.1 jelly beer on note today. Very smooth and fully functional. I recommend. Sorry to OP for off topic
Click to expand...
Click to collapse
I agree, we got a little off topic.

[Q] NOTE 3 FAILED ROOT. How to fix?

Ok guys, been using these forums to root phones for a while now. First phone i did was my att s3. hit a few bumps but overall it was a piece of cake. have done several different s3s and a tmobile note 3 with ease. Tried to root my sisters note 3 sprint (SM-N900P) today, and of course, i am having some issues.
I started out by trying to use the cf auto root for the phone in question, and then i get could not do normal boot. so i restart and it just boots into the same screen. I have tried reflashing stock firmware, but it fails everytime fused 2 binary 1. So then i flashed the pit file, which succeeded in letting me turn the phone back on lol, but i still cant use stock recovery anymore. also, if i try to reflash custom firmware now, i get firmware update encountered an issues screen, so i have to take the battery out for a few seconds and put it back in to get the phone to be able to restart.
SO.... I guess my questions are, what exactly went wrong? how do i fix stock recovery if nothing else? and is there a way to unlock this phone without rooting if i cant root after all? because my sister doesnt really care about custom roms, she just needs to be able to use a different carrier.
COMMENTS AND SUGGESTIONS BELOW PLEASE
any help is greatly appreciated.
soony45 said:
Ok guys, been using these forums to root phones for a while now. First phone i did was my att s3. hit a few bumps but overall it was a piece of cake. have done several different s3s and a tmobile note 3 with ease. Tried to root my sisters note 3 sprint (SM-N900P) today, and of course, i am having some issues.
I started out by trying to use the cf auto root for the phone in question, and then i get could not do normal boot. so i restart and it just boots into the same screen. I have tried reflashing stock firmware, but it fails everytime fused 2 binary 1. So then i flashed the pit file, which succeeded in letting me turn the phone back on lol, but i still cant use stock recovery anymore. also, if i try to reflash custom firmware now, i get firmware update encountered an issues screen, so i have to take the battery out for a few seconds and put it back in to get the phone to be able to restart.
SO.... I guess my questions are, what exactly went wrong? how do i fix stock recovery if nothing else? and is there a way to unlock this phone without rooting if i cant root after all? because my sister doesnt really care about custom roms, she just needs to be able to use a different carrier.
COMMENTS AND SUGGESTIONS BELOW PLEASE
any help is greatly appreciated.
Click to expand...
Click to collapse
And you haven't said anything to us but you don't know how to read .... You haven't said what you flashed and with what Odin etc ... you have given nothing to help fix your problem and there is no unlock besides sprint doing it or you would have READ that too
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
And you haven't said anything to us but you don't know how to read .... You haven't said what you flashed and with what Odin etc ... you have given nothing to help fix your problem and there is no unlock besides sprint doing it or you would have READ that too
Click to expand...
Click to collapse
Well, I fixed it anyway so it doesn't matter. Now trying to install custom recovery, but had issues with that. Guess cwm is not working for this phone correctly. So only way to unlock is pay sprint? And thanks soooo much for your helpful attitude
soony45 said:
Well, I fixed it anyway so it doesn't matter. Now trying to install custom recovery, but had issues with that. Guess cwm is not working for this phone correctly. So only way to unlock is pay sprint? And thanks soooo much for your helpful attitude
Click to expand...
Click to collapse
It amazes me that some people cannot just read a post and move on if they have nothing helpful to say but instead take the time out of their busy lives to slam someone.
You should feel honored.

PLEASE help rooting Verizon Note 2 SCH-i605 4.4.2

I have internetted to the best of my ability and tried many, many different things, but I cannot get my Note 2 to root. Odin keeps failing on NAND or on restore.img or any other step. I have tried every usb port and every cable in my house. I tried this once before (maybe a year or two ago) and managed to get a verizon "unauthroized software" message. From this, I was able to get it back to stock, and I have left it alone since.
Now this is no longer my main phone, and I WILL root it, but I need some help.
It is deactivated (my service phone is now an old Fascinate).
It is SCH-I605, on 4.4.2, baseband is I605VRUFND7, kernel is 3.0.31, build is KOT49H.I605VRUFND7.
The phone is in developer mode, USB debugging is enabled, verify apps is disabled, and I don't have an option to "unlock OEM". I (currently) have Odin 3.10 and 3.12 on my desktop. I've got a thing called "CF-Auto-Root-t0ltevzw-t0ltevzw-schi605" which I believe it some kind of "patch" for the kernel that will grant root access.
I can boot the phone to recovery/download mode. I can start Odin, I can connect the phone, I can see it in Odin (usually on COM5). In NONE of the versions of Odin I have seen, do I ever see this "PDA" button, but I do have a AP button. Depending on the version of Odin, usually AP is the only button that is enabled. One of the tutorials talks about PDA button but the screenshot shows the AP button, so I have been trying this exclusively.
I can click start, and things will work pretty good for a little while, but then I will get some error. Usually it is on recovery.img, sometimes it is on NAND rewrite (I think ... I can't get back there). Always just "FAIL!". I cannot find a log to tell me why, and the message is completely useless. Sometimes it will just hang on SetupConnection, and once it hung on recovery.img for over 10 minutes.
The last time I did this (and recovered) I was on Win 7, now I'm on Win 10.
Can somebody please offer some advice? I can provide screenshots, chat on Skype, whatever is needed. Thanks!!
Emery
I also want to mention that I tried ghetto root but I am getting errors in it as well. The main error is that there is an unexpected newline (but I do not know which file), and then I am told that root fails, and Super SU does not appear on the phone.
i used Saferoot and it seems to work each time...
Forum
http://forum.xda-developers.com/showthread.php?t=2565758
SafeRoot Link:
http://forum.xda-developers.com/attachment.php?attachmentid=2760984&d=1400951117
Jaws4God said:
i used Saferoot and it seems to work each time...
Forum
http://forum.xda-developers.com/showthread.php?t=2565758
SafeRoot Link:
http://forum.xda-developers.com/attachment.php?attachmentid=2760984&d=1400951117
Click to expand...
Click to collapse
Thanks! I will try it right now!
Ok. So saferoot failed with "Your kernel is patched! This device is not supported."
I think it also said something about a locked bootloader, so I went looking for more information and found
http://forum.xda-developers.com/showthread.php?t=2118348
I tried "no you verizon" version first, which said that it failed (I took a copy of the log).
Then I tried the earlier "Back Atcha Verizon", and now I am back to "system software not authorized by verizon ..... blah blah go to the nearest verizon store for help".
Lol, now I have to remember how to undo this ... I think I had to restore the stock image with Odin or something.
In any case, what the heck is possibly going on? How is this the most locked-down phone on the planet? This is incredible and ridiculous and I don't even know!
emeryalan said:
Ok. So saferoot failed with "Your kernel is patched! This device is not supported."
I think it also said something about a locked bootloader, so I went looking for more information and found
http://forum.xda-developers.com/showthread.php?t=2118348
I tried "no you verizon" version first, which said that it failed (I took a copy of the log).
Then I tried the earlier "Back Atcha Verizon", and now I am back to "system software not authorized by verizon ..... blah blah go to the nearest verizon store for help".
Lol, now I have to remember how to undo this ... I think I had to restore the stock image with Odin or something.
In any case, what the heck is possibly going on? How is this the most locked-down phone on the planet? This is incredible and ridiculous and I don't even know!
Click to expand...
Click to collapse
weird.. yeah i used saferoot on my device a few times and haven't had an issue.. it shouldn't matter if your bootloader is locked.. that would only keep you from flashing a customer recovery...
I know mine is running 4.1.2 (MC3) so I should be able to unlock my bootloader but can't got get CASUAL to work... just fails at different points or loops trying to install CAD or something... so not sure what i need to do.
I did try to use Flashify to put a custom recovery on.. i got the "system software not authorized... " blah blah.. knew I did have to use ODIN to restore the factory firmware.. but it wasn't reading my phone.. finally after switching USB ports, it worked and I was able to put it back to stock and get it to boot and root again..
so if anyone has any ideas on how to get CASUAL to work, please let me know.
Galaxy Note 2 lessons from Verizon
There is still no root or bootloader unlock for Verizon Galaxy Note2 (Model SCH-I605). Ours quit working, by shutting down/locking up often. From what I've found out, this behavior is caused by Verizon's own software, not the hardware, forcing us to get a new phone. I STRONGLY recommend anyone on Verizon to drop the service immediately, before this becomes the standard. What we will see is, having to purchase a new phone product every two years, requiring us to turn in the old phone, then being sold a repackaged refurbished model at new phone prices.
Verizon is pushing the boundaries, and they are preventing a piece of equipment that you own from functioning in order to force you to buy another of their products. If allowed, this business model WILL spread to all their competitors. It will stunt the growth of future technologies since innovation will not be the motivation to buy a new product, the only motivation being the continual failure of a sabatoged product.
So again, please drop Verizon if you have them, and if you don't have them don't get them.
update.. i was able to get CASUAL to work.. had to download another program to reset the CAD Driver.. then it worked like a charm.. so have an unlocked bootloader and rooted. Right now i'm trying out Alliance ROM..
emeryalan said:
Ok. So saferoot failed with "Your kernel is patched! This device is not supported."
Click to expand...
Click to collapse
yep, i got this error too after I had tried Alliance 4.4 ROM... so I guess that saferoot only works for 4.3 and older..
LordBaronMarshall said:
There is still no root or bootloader unlock for Verizon Galaxy Note2 (Model SCH-I605). Ours quit working, by shutting down/locking up often. From what I've found out, this behavior is caused by Verizon's own software, not the hardware, forcing us to get a new phone. I STRONGLY recommend anyone on Verizon to drop the service immediately, before this becomes the standard. What we will see is, having to purchase a new phone product every two years, requiring us to turn in the old phone, then being sold a repackaged refurbished model at new phone prices.
Verizon is pushing the boundaries, and they are preventing a piece of equipment that you own from functioning in order to force you to buy another of their products. If allowed, this business model WILL spread to all their competitors. It will stunt the growth of future technologies since innovation will not be the motivation to buy a new product, the only motivation being the continual failure of a sabatoged product.
So again, please drop Verizon if you have them, and if you don't have them don't get them.
Click to expand...
Click to collapse
Even though my device is bootloader unlocked for testing CM releases I always go back to stock ND7 for stability minus bootloader then Ghettoroot and it's been working solid for years. And, unlimited data for $60 is hard to beat. Absolutely nothing wrong with the phone and software and not yet with the service as long as I can avoid the $20 unlimited data increase when contract expires in 2017.
mi7chy said:
I always go back to stock ND7 for stability minus bootloader then Ghettoroot and it's been working solid for years. .
Click to expand...
Click to collapse
what version is ND7 ? thank you.
Jaws4God said:
what version is ND7 ? thank you.
Click to expand...
Click to collapse
ND7 is Kit Kat 4.4.2.
mi7chy said:
ND7 is Kit Kat 4.4.2.
Click to expand...
Click to collapse
oh got ya. i haven't read much about that version.. wonder if it has possibility of unlocked bootloader or root.
Jaws4God said:
oh got ya. i haven't read much about that version.. wonder if it has possibility of unlocked bootloader or root.
Click to expand...
Click to collapse
It's the last official release. If you're already bootloader unlocked you can use Mobile Odin Pro to flash it minus the bootloader then use Ghettoroot. Only thing is Mobile Odin Pro only works with Lollipop such as CM12.1 or older. So, if you try CM13 and decide to go back to stock ND7 you have to first flash CM12.1 then use Mobile Odin Pro to flash stock ND7.
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
mi7chy said:
It's the last official release. If you're already bootloader unlocked you can use Mobile Odin Pro to flash it minus the bootloader then use Ghettoroot. Only thing is Mobile Odin Pro only works with Lollipop such as CM12.1 or older. So, if you try CM13 and decide to go back to stock ND7 you have to first flash CM12.1 then use Mobile Odin Pro to flash stock ND7.
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
Click to expand...
Click to collapse
oh interesting.. so right now i'm on a ND7 port.. should I bother flashing the ND7 without bootloader or is not really needed?
Thanks!

Categories

Resources