So I rooted my Note 2 and installed rom manager to so I could install a zip File and the phone rebooted and I got this massage:
System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help
Volume up/home/power just boots to this message every time. So does Volume down/home/power.
It will not boot into Download mode or odin mode.
Please help.
Thank you.
Sounds like you tried to use ROM Manager to install CWM, an alternate recovery before unlocking your bootloader.
What version of software did you have - 4.1.2 or 4.3?
---------- Post added at 03:38 PM ---------- Previous post was at 03:35 PM ----------
By the by, your phone IS recoverable, but the surefire method (Verizon Software Update) will also force you to upgrade to 4.3 and you will be locked into the new, secure bootloader. No exploit to unlock this bootloader has been found, so no custom ROMs can be installed once you have 4.3.
If you already had the official 4.3 OTA, you're locked already and it won't change anything to use Verizon's software to restore your phone.... though you undoubtedly tripped the KNOX counter trying to flash a custom recovery in that case.
I was able to get in to odin mode but it gets allmost done and it fails its saying unsupported version
I am running ota 4.3
Sent from my SCH-I605 using xda app-developers app
As far as I know there is only one method top root that works on 4.3 right now but it doesn't unlock the boot loader
Sent from my SCH-I605 using xda app-developers app
I've accidentally done what OP did too, having been unaware of the changes to prevent custom recoveries.
I've tried using Odin to flash back to stock 4.1.1 but apparently that didn't work, and I guess the custom recovery is still triggering the error.
Is there a way to reset the recovery to stock now or at least bypass Verizon's system check?
I have had this happen as well. Is there any way to unlock this phone using any methods on here? Thanks.
Same issues, anyone have any luck on 4.4.3?
Trouble installing CWM/TWRP on rooted Note 2 SCH-i605 4.4.2
BrianAnim said:
Same issues, anyone have any luck on 4.4.3?
Click to expand...
Click to collapse
No luck on 4.4.2 -- Trouble Installing CWM/TWRP on Rooted Vz Note 2 SCH-i605 4.4.2
The title of this post summarizes my present challenge ... I have not been able to successfully install CWM or TWRP using any popular method. For example ODIN attempts fail each time, no matter what I try, e.g. swapping USB ports, reloading drivers, removing batteries, sim cards, SD card, changing cables, turning virus protection on/off, battery charge level (50 thru 100%) ... and various combinations of these approaches. ROM Mgr and other Flash apps don't get it done -- well, to be fair, they may be getting it done, but on reboot I receive an error message "System software not authorized by Verizon Wireless has been found...." blah, blah, blah. --SO, does anyone have any thoughts or approaches they might recommend? I'm really stumped. And to make it all the more vexing, I'm a novice or whatever is just before novice. I've enjoyed getting this far and have recovered from a few soft bricks along the way. The first time was worrisome, but now I don't worry so much. I've lucked out and found a lot of great guidance on forums, like this one and others. But so far, I haven't landed on the trick of getting past 'whatever roadblock(s)' are in place on this Note 2 SCH-i605 4.4.2 set-up. I'm stumped.
fibertowner said:
No luck on 4.4.2 -- Trouble Installing CWM/TWRP on Rooted Vz Note 2 SCH-i605 4.4.2
The title of this post summarizes my present challenge ... I have not been able to successfully install CWM or TWRP using any popular method. For example ODIN attempts fail each time, no matter what I try, e.g. swapping USB ports, reloading drivers, removing batteries, sim cards, SD card, changing cables, turning virus protection on/off, battery charge level (50 thru 100%) ... and various combinations of these approaches. ROM Mgr and other Flash apps don't get it done -- well, to be fair, they may be getting it done, but on reboot I receive an error message "System software not authorized by Verizon Wireless has been found...." blah, blah, blah. --SO, does anyone have any thoughts or approaches they might recommend? I'm really stumped. And to make it all the more vexing, I'm a novice or whatever is just before novice. I've enjoyed getting this far and have recovered from a few soft bricks along the way. The first time was worrisome, but now I don't worry so much. I've lucked out and found a lot of great guidance on forums, like this one and others. But so far, I haven't landed on the trick of getting past 'whatever roadblock(s)' are in place on this Note 2 SCH-i605 4.4.2 set-up. I'm stumped.
Click to expand...
Click to collapse
As far as I know if you do official OTA 4.3 and above update you bootloader is locked/secure and you cannot install a custom recovery therefore no custom roms. at least the old fashion way.
My phone does not have these issues so I haven't looked into whats out there. You may be able to still root the phone at least, and as for custom roms I would look into the safestrap options if there are any.
If one gets a note 2 like warranty replacement or for some other reason in the recent past or future check immediately when turning on if you are 4.1 or 4.3 and dont take any OTA. You may get lucky and have old software on it.
Edit: Looking around maybe this will help you. http://forum.xda-developers.com/note-2-verizon/help/finally-safestrap-recovery-v3-72-nd7-4-t2968273
I had updated to the official OTA 4.3 and the only way heard of was to send your phone into mobiletechvideos and they will downgrade your phone back to 4.1.2 I don't know the details on what they do, but it involves taking your phone apart. I sent my GN 2 in on a Wednesday and I had it back by the following Thursday. I re-rooted and I am back running cm12. I talked with Josh on the phone regarding replacing my rear housing at the same time. Nice guy, very helpful. I ordered the rear housing and sent it with the phone. They changed it out at no cost.
Sent from my SCH-I605 using Tapatalk
Related
My Verizon Samsung Galaxy S4 (Model # SCH-I545) is stuck at an error screen with a yellow triangle in the middle and a picture of a phone on the left and a picture of a computer on the right. It also reads: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I JUST purchased this phone and the latest update was installed. I attempted to root the phone but after researching I found there is no current solution. I searched more and found a thread (that i can't post because I am a noob): I followed the instructions hoping to remove the update and return to stock, however the process did not work and Odin failed. Even though Odin was through, my phone still showed a line like it was downloading. I tried everything to reboot my phone, but could not find a way to do it, so I pulled the battery. Now, I cannot get past this screen. Is there anything I can do to fix this awesome blunder?
P.S. I am prepared for the scoldings I plan on getting...
I literally just posted the same question. Any help would be appreciated if you can figure it out. Ill return the favor if i can get any information :good:
If you took the latest update I'm not sure what the answer is because I haven't been willing to take the update.
If you were in mdk before the yellow triangle then all you have to do is Odin the mdk kernel.
I'd imagine if you are on the latest then odining the latest would take care of it also but again, I won't take the latest so I can't say for sure
sent from my blu vzw gs4
Thanks Jakemkv, I will update you as I get more info. I will also be looking at your thread, you can bet.
Dubbsy, where can I find that new mdk Kernel?
richardawood said:
Thanks Jakemkv, I will update you as I get more info. I will also be looking at your thread, you can bet.
Dubbsy, where can I find that new mdk Kernel?
Click to expand...
Click to collapse
Im on a search for the updated kernel as well. At least there is someone in the same boat as i am.
richardawood said:
My Verizon Samsung Galaxy S4 (Model # SCH-I545) is stuck at an error screen with a yellow triangle in the middle and a picture of a phone on the left and a picture of a computer on the right. It also reads: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I JUST purchased this phone and the latest update was installed. I attempted to root the phone but after researching I found there is no current solution. I searched more and found a thread (that i can't post because I am a noob): I followed the instructions hoping to remove the update and return to stock, however the process did not work and Odin failed. Even though Odin was through, my phone still showed a line like it was downloading. I tried everything to reboot my phone, but could not find a way to do it, so I pulled the battery. Now, I cannot get past this screen. Is there anything I can do to fix this awesome blunder?
P.S. I am prepared for the scoldings I plan on getting...
Click to expand...
Click to collapse
If the phone was running ME7 then you can ONLY flash ME7 again (at least right now).
Grab the image from this thread...
http://forum.xda-developers.com/showthread.php?t=2357235
and flash it using Odin.
Thank You
That worked great! I am back up in running and waiting patiently w/ the rest of us that updated... THANK YOU!!!!!! :highfive:
Thanks
I can't thank you enough. The S4 is my first Android phone and after 3 weeks, the USB connection on the phone broke and I finally got my new one today. While I was setting up SuperSU/Titanium Backup/ROM Manager, I guess the phone downloaded the ME7 update in the background and I told it to install (stupid me). This will teach me from rushing to get my phone back to the state it was in. (Not that I can do that now because I need SuperSU before I can install ROM Manager). Hopefully once I can get ROM Manager back, I can restore my MDK backup with all my custom settings and apps. I think I will make a visit to the VZ store tomorrow and see if they can revert back to the MDK version. I will make up some lame excuse of why I don't want to be on this new release.
This leads to my question of, is there a way to disable or remove the apk file that controls the software updates?
Thanks again for saving my life!!!
Once you take me7 update theres no going back unless you get a different phone. When someone gets the me7 ota rooted you can rename/remove sdm.apk and itll keep your phone from downloading new updates. I would say freeze as well but some users reported their phones updating even with it froze. When the me7 bootloader/recovery situation gets resolved there wont be much reason to go back to mdk anyway since people will start creating roms with it as the base.
SCH-I545 using Tapatalk 2
Thanks
hexitnow said:
Once you take me7 update theres no going back unless you get a different phone. When someone gets the me7 ota rooted you can rename/remove sdm.apk and itll keep your phone from downloading new updates. I would say freeze as well but some users reported their phones updating even with it froze. When the me7 bootloader/recovery situation gets resolved there wont be much reason to go back to mdk anyway since people will start creating roms with it as the base.
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the information about the sdm.apk. When I debloated my phone I used the adb shell to remove most of the *.apk packages that I did not want. This was of course after I took a full Titanium Backup and ROM Backup.
Sounds good and I will not waste my time going to Verizon today.
You make a really good point about not going back to the mdk, but rather move forward with the technology and updates. This leads me to some more questions once I have root again:
1. Is my mdk rom backup totally useless at this point?
2. If yes to 1, since my mdk rom contained all my apps/customized settings, do I have to manually download everything and reconfigure?
3. If no to 2, how would I go about getting the app/customized settings back, Titanium Backup?
4. If yes to 2, if I go about downloading everything manually and configuring, will the new root remove all these settings?
I am sure I will have more questions so thanks in advanced
PS: I think I figured out what caused my USB port to stop working. I take my phone with me when I run so I think some sweat got in from my arm band and corroded the connections. I tried cleaning them with rubbing alcohol and compressed air, but still no dice. If connected to a computer or wall charger, it will charge, but a computer will not detected it. So my guess is there is damage to the board allowing whatever communication is needed to work with a computer.
So, I have the i545, it was updated to the newest firmware when I got it. Lucky!
I first tried all the old stuff like the noob I am. Bricked it a couple times, blah blah, fixed it.
I tried the newer stuff, and was successful in getting into the recovery, but all I can do is wipe personal data and cache, its not CWM. When I do, it gets locked into download odin section and says its broken essentially.
Any bootloader bricks it, and any attempt to do the newer stuff like Loki has bricked it. I have the original Rom saved, so I just have to push it through odin each time.
I want Hyperdrive rom, I am rooted, and I can't get the common "working" ways to work. What am I doing wrong? I just tried the loki method and it locked into odin download when it restarted.
I'm not frustrated at anyone here by any means, I know the big companies are jerks, and....I need help side stepping them...
Any suggestions?
Again, i545, 32gb, Verizon Galaxy s4. It is rooted. And I want Hyperdrive rom.
Thanks!
EDIT.
If there is a way through odin or something to push Hyperdrive, I dont need the CWM. Im just a simple custom rom user, nothing crazy. And if there is no way to go from the ME7 update, be it downgrade and then root and flash, be it odin, be in CWM or Loki method, etc., where do I go to add to the bounty?
Excessumcarcer said:
So, I have the i545, it was updated to the newest firmware when I got it. Lucky!
I first tried all the old stuff like the noob I am. Bricked it a couple times, blah blah, fixed it.
I tried the newer stuff, and was successful in getting into the recovery, but all I can do is wipe personal data and cache, its not CWM. When I do, it gets locked into download odin section and says its broken essentially.
Any bootloader bricks it, and any attempt to do the newer stuff like Loki has bricked it. I have the original Rom saved, so I just have to push it through odin each time.
I want Hyperdrive rom, I am rooted, and I can't get the common "working" ways to work. What am I doing wrong? I just tried the loki method and it locked into odin download when it restarted.
I'm not frustrated at anyone here by any means, I know the big companies are jerks, and....I need help side stepping them...
Any suggestions?
Again, i545, 32gb, Verizon Galaxy s4. It is rooted. And I want Hyperdrive rom.
Thanks!
Click to expand...
Click to collapse
Your stuck at the moment there is no custom recovery for me7. Theres been about 100 posts/threads about it. Hashcode a member here is working on a safestrap for me7 so custom roms can be flashed I advise checking it out. Its in the general section.
http://forum.xda-developers.com/showthread.php?p=45185924
Sent from my SCH-I545 using Tapatalk 2
---------- Post added 2nd September 2013 at 12:07 AM ---------- Previous post was 1st September 2013 at 11:53 PM ----------
No way to downgrade or flash rom through odin. Like I said your stuck for moment on stock me7. In the thread I linked there is a donation link for hashcode with the safestrap. There is also a bounty page for unlocking the bootloader in the general section as well.
Sent from my SCH-I545 using Tapatalk 2
Excessumcarcer said:
So, I have the i545, it was updated to the newest firmware when I got it. Lucky!
I first tried all the old stuff like the noob I am. Bricked it a couple times, blah blah, fixed it.
I tried the newer stuff, and was successful in getting into the recovery, but all I can do is wipe personal data and cache, its not CWM. When I do, it gets locked into download odin section and says its broken essentially.
Any bootloader bricks it, and any attempt to do the newer stuff like Loki has bricked it. I have the original Rom saved, so I just have to push it through odin each time.
I want Hyperdrive rom, I am rooted, and I can't get the common "working" ways to work. What am I doing wrong? I just tried the loki method and it locked into odin download when it restarted.
I'm not frustrated at anyone here by any means, I know the big companies are jerks, and....I need help side stepping them...
Any suggestions?
Again, i545, 32gb, Verizon Galaxy s4. It is rooted. And I want Hyperdrive rom.
Thanks!
EDIT.
If there is a way through odin or something to push Hyperdrive, I dont need the CWM. Im just a simple custom rom user, nothing crazy. And if there is no way to go from the ME7 update, be it downgrade and then root and flash, be it odin, be in CWM or Loki method, etc., where do I go to add to the bounty?
Click to expand...
Click to collapse
It would have helped you greatly to have research GS4 with ME7....it can ONLY be rooted at this time.
decaturbob said:
It would have helped you greatly to have research GS4 with ME7....it can ONLY be rooted at this time.
Click to expand...
Click to collapse
The first time it bricked itself I did some research. Found that the ME7 was a punk, found guides where people claimed to have gotten around it, which all failed. I presumed it had been cracked if there were ways posted, but after they failed I came here.
Excessumcarcer said:
The first time it bricked itself I did some research. Found that the ME7 was a punk, found guides where people claimed to have gotten around it, which all failed. I presumed it had been cracked if there were ways posted, but after they failed I came here.
Click to expand...
Click to collapse
It bricked "itself" pretty amazing. You should do a little research before you mess with your phone.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
It bricked "itself" pretty amazing. You should do a little research before you mess with your phone.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Ugh, I could explain everything in detail and not joke around, but then I'd just be a jerk. I've rooted, installed bootloaders, roms, etc., on many phones, not just mine. I know what I'm doing so generally I don't have to research how to do it. I upgraded from a galaxy S3 with MOAR (rom) installed, also did paranoid rom right before, jumped in and hoped that the S4 would play nice. It didn't. And you won't find a post from me asking how to unbrick it. The original Rom was backed up, so nothing to fear. I understand that bricking a phone is part of the risk, and unbricking it is part of the knowledge one needs to jump in comfortably. I did it 8 times yesterday. I tried 5 methods, one I tried a couple times because I could get into the bootloader but it would freeze on removing the cache. After each different combo, it killed it. Once I felt defeated for the day I came here. Believe me, Im not the person who turns on their phone and posts for help about what to do after its on. ^_^
Well, all I can say is you're learning the s4 the hard way
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
ME7 =no custom recovery =no custom ROMs.
Read the thread about SafeStrap being worked on by hashcode
Sent from my Nexus 7 using Tapatalk 2
jd1639 said:
Well, all I can say is you're learning the s4 the hard way
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Thats the only way I learn. : ) Following the 50 million different articles and blogs and tutorials is the only way I ever find anything. Rarely do I get a piece of equipment that just works the first time with the common used method for it. That's never my luck. There's always something stupid that stops it. This is the same with everything in truth, cars, computers, phones, etc. Nothing has ever just worked for me. So, now I just throw things at it until something goes through. People say there's no way, well...if that's the case then all the DEV's should stop trying. lol. There is a way, we just have to find it.
Well, every phone is different and just jumping in on a new phone without knowing the issues and pitfalls because you rooted other phones being naive imo. I've rooted maybe a half dozen phones and countless roms but when i got my S4 i still waited a few days and just read. The point is no matter how many times you do something whenever you get something new/updated, be a phone or anything else, you should always take the time to read and read.
Edit:
Also because of these locked down bootloaders (like the sammy knox) i would if i were you do A LOT of reading before buying new phones in the future to make sure you CAN root and slap a custom recovery on it. The root and custom recoveries may be a thing of the past pretty soon and we'll be purchasing Developers and Google Play editions if we want custom stuff.
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Anyone? Even a, "Yeah, that's weird man! Sounds like you did everything right!" Would make me feel better...
Yes I've tried it and it worked make sure u have the unofficial safestrap the one for your phone and do the busy box and terminal emulator thing and it works if you try to install safestrap without the other things you will brick I did it twice but it very easy to unbrick so download busybox terminal emulator and the correct safestrap for you device and also I'm on 4.4.2 also and there is only one rom i have found that works and its called superliter there ya go hope I help would provide download links but I'm not home
Also I forgot to mention your bootloader won't be unlocked it'll be bypassed and you will have a custom recovery
androidforums.com/threads/verizon-verizon-bootloader-unlock.856221/page-2[/url]
forum.xda-developers.com/showthread.php?t=2605648
device specific safestrap recovery and image
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
schmitey said:
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Click to expand...
Click to collapse
Verizon spends a pretty penny when it comes to making sure their devices................. stay theirs i guess you can say when it comes to the boot-loader! To my knowledge their isn't a way of getting around that with a permanent recovery flash that completely replaces Verizon's stock recovery. I can almost guaranteeing you that your problem is Verizon locked boot loader. Stock recoveries are solely only their for their technicians, so unless someone somehow has leaked a program that they use to get around that stuff without screwing it up, we the general public will never be able to flash anything permanent with any phones stock recovery unless we have their "secret" software! Every once in a while you do find a leaked one. I got lucky and found one for the T-mobile galaxy S6 Edge. As far as Odin I've noticed that the new versions seem to be very particular. Meaning if a dot or a space is misplaced anywhere in the zip or what not it will always fail. With my t-mobile S6 I spent two days figuring out I had to take a letter out of the name of the file i was trying to Odin. One letter that was it and once I did that it went flawlessly. Otherwise man i really don't know what to tell you, seems like ya followed the lines as described. Just remember its a Samsung Galaxy in my opinion Galaxies are unbrickable. Ive even pulled the cord in the middle of a Odin flash to see if i could brick it for good and was still able to go right into download mode and flash stock back onto it and everything working. So don't be afraid of bricking it. It will be way easier (sorry to say) for you to re-flash stock right now! Good luck bro wish you the best!
---------- Post added at 08:25 PM ---------- Previous post was at 08:18 PM ----------
schmitey said:
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
Click to expand...
Click to collapse
Are you able to disable Signature verification in the recovery?
Are you able to disable Signature verification in the recovery?
You can once I flash to say clockworkmod recovery. Stock I don't know of a way to...hence the Catch 22 there's no going forward and no going back...you're stuck with stock ROM/recovery but at least its rooted.
Well ****. Take my word for it you CAN brick a galaxy s3.
I used KIES to restore back to factory stock recovery etc etc.
I then used towelroot to root phone and install supersu. I then installed safestrap which totally worked! I was able to bypass the stock recovery and everything was running smoothly...I got overzealous and tried to install the cyanogenmod vrale6 bootloader zip through safestrap. I currently have a brick. It won't boot, no led's, no screen, no vibrate. I have another galaxy s3 charging batteries and swapped it out...removed sim and micro sd. I should have just installed the cyanogenmod app and done it that way...
So close and now I bricked it...
OK got my brick back by writing image to microSD card...pretty happy about that little trick. And that's utter nonsense about needing the same size card as your internal memory! I used a 32gig card on a 16gig phone...
Still trying but this locked 4.4.2 bootloader is BULL****. Going to try to downgrade but I'm not sure I'm going to end up with anything but a rooted stock rom...
So does anyone know of a way to downgrade or change recovery on Verizon 4.4.2?
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
slimcyril said:
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
Click to expand...
Click to collapse
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
schmitey said:
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
Click to expand...
Click to collapse
Well no zip has ever failed on my end using safestrap, does your device have init.d support?
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
schmitey said:
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
Click to expand...
Click to collapse
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
slimcyril said:
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
Click to expand...
Click to collapse
system partition is NOT checked within safestrap. Installed universal init.d but I'm out of my league on it... Init.d says stock kernel does not have support...
A couple days ago I got a g3. Immediately I let it to the Ota updates not thinking that perhaps thes latest might root able.
I found one thread with instructions to downgrade, root, and then flash 6.0. Didn't work. The lg flash tool and LG up never worked. It always said unknown device.
I found the king root app. It rooted my stock MM temporarily. So I used twrp manager to try and flash twrp. The end result was a black screen with the led blinking. I could not boot into any recovery.
So then I followed guides to uunbrick and return to stock but no success. The lg pc tool didn't recognize/connect to my phone. However I got adb working. At any I, I still download the LG drivers again, different versions of lg tool and downloaded firmware from different sources. Same result, didn't flash and left with blank recovery.
So then I thought twrp could be flashed with fast boot. Found a guide that had me delete download mode to allow access to fast boot.
I was able to get into fast boot fine but wasn't able to flash a recovery or any image. And now I can't figure out how to get download mode back. The download mode image is backed up on SD card but I can't flash it.
Otherwise the phone works fine. I can't do a factory reset or get into any recovery.
I believe I deleted the recovery partition at some point.
Now I doubt care about root but I do care if I have the ability to factory reset.
Any help? I've looked at many guides on unbrickibg, flashing and so forth. If you have advice please be specific.
Only other thing to mention is I am using a Windows 10 laptop when a computer is needed.
Thanks for the help.
Oh boy. I apologize that I probably don't have anything useful to suggest. Almost anything I would think of requires Download mode.
When you plug the phone into the PC, what does it show up as in Windows' Device Manager in the Port section? "LGE..." something or "QHSUSB_BULK 9008"? If the latter, you might be able to use special drivers and BoardDiag for Windows to recover - it'll use the 10B TOT so have that on hand if that's the case, plus Google "QHSUSB_BULK" to find the program, drivers and instructions.
If it's not in QHSUSB_BULK 9008 mode, you may be able to force it into that mode. I've never had to, but there's a thread in the General section for that. I think it's the one that mentions "hard brick" and/or "test point", and requires at least a very slight disassembly of the back of the phone, and shorting two specific electrical contacts.
Thanks for your input. I will look into the things you suggested and report my findings. Taking the phone apart and shorting out wires seems dangerous.
Sure man, good luck! I notice you have two threads going on, the other about a G3 you're going to get this week? Just confirming that either you're dealing with two separate G3s or your replacing this one with the other one.
I haven't activated my vs985k with the carrier yet, as I've been thinking that I should root it first to avoid another OTA messing things up even more than is the case with 57A.
I've been collecting the software tools to run on my laptop, but don't have it all lined up yet.
Anyway the idea has crossed my mind that when I activate a rooted phone that they might refuse to activate a rooted phone. So a catch 22 situation if that's the case.
Any thoughts or stories out there about this kind of situation?
Sent from my LG-D801 using Tapatalk
---------- Post added at 11:48 PM ---------- Previous post was at 11:23 PM ----------
SofaSpud said:
I haven't activated my vs985k with the carrier yet, as I've been thinking that I should root it first to avoid another OTA messing things up even more than is the case with 57A.
I've been collecting the software tools to run on my laptop, but don't have it all lined up yet.
Anyway the idea has crossed my mind that when I activate a rooted phone that they might refuse to activate a rooted phone. So a catch 22 situation if that's the case.
Any thoughts or stories out there about this kind of situation?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Edit: 47A, not 57A!
Sent from my LG-H810 using Tapatalk
SofaSpud said:
Any thoughts or stories out there about this kind of situation?
Click to expand...
Click to collapse
I haven't heard one way or the other. I doubt if you'd have trouble activating while rooted, but it's been almost two years since my wife and I activated our G3s and my VK810 4G LG G Pad 8.3, and they were all activated while 100% stock.
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!