i flashed a stick rom and now getting unathorized software message on boot and cant get in to the phone, but I do have access to odin, am i screwed or what : (
moocowgal said:
i flashed a stick rom and now getting unathorized software message on boot and cant get in to the phone, but I do have access to odin, am i screwed or what : (
Click to expand...
Click to collapse
Go to my guide and follow section 6....also try reading a couple threads before posting. This the whole reason why verizon locked the darn bootloader in the first place. Research then flash, dont flash then research!!!
Edited for incorrect advice.
voodoomanx said:
http://forum.xda-developers.com/showthread.php?t=1762204
Download and flash root66 with odin. What stock rom gave you the triangle?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This is incorrect...you must flash the stock kernel before flashing a stock rom in odin. Op go to my guide and follow section 6.
I suggest doing a factory reset in recovery, immediately after you flash root66. My phone would not finish booting after ODIN'ing root66 coming from BeansRom 9. It was sticking at the Verizon 4g boot image for 20 minutes.
droidstyle said:
This is incorrect...you must flash the stock kernel before flashing a stock rom in odin. Op go to my guide and follow section 6.
Click to expand...
Click to collapse
Depends on what rom he flashed. That's why I asked. If he flashed a stock rom with stock kernel flashing root 66 in odin would work.
Sent from my SCH-I535 using xda app-developers app
voodoomanx said:
Depends on what rom he flashed. That's why I asked. If he flashed a stock rom with stock kernel flashing root 66 in odin would work.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Read the op...she is getting the verizon triangle of death...that means one thing, either she flashed a custom recovery via odin or flashed a custom rom that was packaged with a custom kernel on a locked bootloader. The advice you gave is incorrect for this situation. Im not here to argue, im here to help pass along correct information to keep bricks at a minimum. Sometimes i may come off a bit brash, but im just trying to get the point across. Seems silly to take a 600.00 device and turn it into a paper weight all because lack of research don it?
droidstyle said:
Read the op...she is getting the verizon triangle of death...that means one thing, either she flashed a custom recovery via odin or flashed a custom rom that was packaged with a custom kernel on a locked bootloader. The advice you gave is incorrect for this situation. Im not here to argue, im here to help pass along correct information to keep bricks at a minimum. Sometimes i may come off a bit brash, but im just trying to get the point across. Seems silly to take a 600.00 device and turn it into a paper weight all because lack of research don it?
Click to expand...
Click to collapse
All I did was ask what rom they attempted to flash. I don't care either way. Your guides have gotten me out of a couple jams. I wish people would read them first.
I'm also getting sick of all the warranty fraud going on.
Now that I reread the OP you are correct. I will edit my reply so as not mislead anyone.
Sent from my SCH-I535 using xda app-developers app
voodoomanx said:
All I did was ask what rom they attempted to flash. I don't care either way. Your guides have gotten me out of a couple jams. I wish people would read them first.
I'm also getting sick of all the warranty fraud going on.
Now that I reread the OP you are correct. I will edit my reply so as not mislead anyone.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
We all misread a post from time to time no biggie. You corrected me on a post in the ez unlock thread. The end result is to make sure the right information is getting passed around. :highfive:
Just saying. Nice catch droidstyle on saying "she" . I thought that was cool. Lol
Sent from my SCH-I535 using xda premium
Hello there everyone...
I was helping my friend with his sgs iii and I successfully rooted and unlocked its bootloader and flashed TWRP recovery and such. Anyways, I decided to install Synergy rom on it, but when the phone booted, wifi didn't work. I figured it might be a kernel issue so I downloaded Scrosler's kernel and flashed that. Anyways, now instead of booting up, the phone just says "software unauthorized by Verizon has been installed on this device, please power off and take your device to the nearest Verizon store to get fixed". I can get into download mode but adb does not recognize the device and I am not sure how to get into recovery otherwise. Is there a shortcut to get into it from the powered off state? Or is my friend's sgs iii soft bricked and do I need to follow the guide in this thread here?
I apologize if this has been asked before but I searched and could not find anything specific on fixing this...
Thanks in advance
If you actually unlocked the BL, you shouldn't be seeing that message.
I'm keeping track of these separate "Bricked" threads. If you would have read the 13 other ones, you would know what to do.
Odin. That's your answer.
Sent from my SCH-I535 using Tapatalk 2
Yeah, you're soft bricked. This was the easiest way i find for a fix.
http://forum.xda-developers.com/showthread.php?t=1840030
Odin a stock kernel, then odin stock rom...section 6 of my guide for further information.
You didn't unlock the phone bootloader. Synergy has a failsafe built into the rom that prevents loading its kernel if you are not unlocked.
Follow the guide droidstyle posted and if you had searched no WiFi in the synergy thread you would have seen lots of advice to unlock bootloader before you soft brickedm
Sent from my SCH-I535 using xda app-developers app
fearjego said:
Yeah, you're soft bricked. This was the easiest way i find for a fix.
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
droidstyle said:
Odin a stock kernel, then odin stock rom...section 6 of my guide for further information.
Click to expand...
Click to collapse
voodoomanx said:
You didn't unlock the phone bootloader. Synergy has a failsafe built into the rom that prevents loading its kernel if you are not unlocked.
Follow the guide droidstyle posted and if you had searched no WiFi in the synergy thread you would have seen lots of advice to unlock bootloader before you soft brickedm
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks guys I was able to fix it. I am going to unlock the bootloader today.
Hello everyone, so I have a couple questions for you guys in regards to rooting my S3. Back in November when I got the phone, I had rooted it and unlocked it using Odin and the EZ-Unlock app off of the play store. Not long after that, i returned back to stock, and here we are 6/7 months later and I am wanting to re-root, but I have discovered that the way to go about this has since changed.
I have looked at this guide http://forum.xda-developers.com/showthread.php?t=2046439 and looked at these videos http://forum.xda-developers.com/showthread.php?t=2295146 but am still a little iffy about jumping right into this since the methods involved are different than the last time I did it. One thing I noticed on the guide that I linked is that they do not have the bootchain for the version on my phone (VRBMF1).
Basically so this thread does not turn into a short story, I am just going to ask if the steps I lay out is the correct way to go about this. I am strictly wanting to root and unlock so that I can flash to a custom ROM, mainly CM10.
1. install samsung drivers
2. download Odin
3. download the "both root and unlocked bootloader"
4. download VRALEC bootchain
5. download either CWM or TWRP
6. and for this step, should I just flash to either VRBMB1 or VRBMD3, or should I just skip this step since it is optional and go straight to flashing a custom ROM?
In addition to this, I have heard things mentioned about backing up the IMEI, and I see them saying you can do it in a Terminal Emulator (the su and reboot nvbackup commands) . Is this something that has to be done after root and unlock?
I would love to get back to rooted and running custom ROMS again, so any help you can provide would be greatly appreciated.
Bump.
Flash the VRBMD3 bootchain and backup your IMEI after rooting and unlocking the bootloader but before flashing a custom ROM.
Thanks for your reply. Is there any benefit to flashing the md3 bootchain if I am just going to be flashing to a custom ROM?
Sent from my SCH-I535 using Tapatalk 2
The boot chain makes a great stable platform before you go off on a custom. That way you can boot and make sure the root has taken
Sent from my SCH-I535
Lord_Tardis said:
The boot chain makes a great stable platform before you go off on a custom. That way you can boot and make sure the root has taken
Sent from my SCH-I535
Click to expand...
Click to collapse
Thanks for your reply. I am happy to report that I listened and flashed the VRBMD3 bootchain and am successfully unlocked and rooted and am running a custom ROM. I did not know that the bootchain would have an effect after I had flashed a custom ROM, so I am glad that I did that. Thanks for your replies everyone. One question though. Since my baseband version is VRBMF1, is there any downside to flashing the VRBMD3 bootchain or does it really matter?
Atwooooood said:
Thanks for your reply. I am happy to report that I listened and flashed the VRBMD3 bootchain and am successfully unlocked and rooted and am running a custom ROM. I did not know that the bootchain would have an effect after I had flashed a custom ROM, so I am glad that I did that. Thanks for your replies everyone. One question though. Since my baseband version is VRBMF1, is there any downside to flashing the VRBMD3 bootchain or does it really matter?
Click to expand...
Click to collapse
The mf1 is the most current radio data. I do not believe there is harm in flashing to an older one. The best bet is to find the one that gives you the best signal strength.
Sent from my SCH-I535
If I wanted to test a couple bootchains as far as signal strength goes , am I able to flash to a different one after I've already flashed a custom ROM or are there more steps involved?
Sent from my SCH-I535 using Tapatalk 2
Correct me if I'm wrong. But bootchains do not affect signal. Only modems/basebands. You can go download any which one as long as kids meant for your model/carrier.
Sent from my SCH-I535 using Tapatalk 4
Sandman-007 said:
Correct me if I'm wrong. But bootchains do not affect signal. Only modems/basebands. You can go download any which one as long as kids meant for your model/carrier.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
You, sir, are correct.
Sent from my SCH-I535 using xda app-developers app
Thanks for clarifying guys. Appreciate your alls help.
Sent from my SCH-I535 using Tapatalk 2
I have read through multiple posts but I am still slightly confused. So I have a Samsung Galaxy S3 running VRUCNC1. I have read that it is unrootable and that using ODIN to downgrade is the only option, but I have also read that downgrading will brick your phone. Could someone assist me with this?
Trevon75 said:
I have read through multiple posts but I am still slightly confused. So I have a Samsung Galaxy S3 running VRUCNC1. I have read that it is unrootable and that using ODIN to downgrade is the only option, but I have also read that downgrading will brick your phone. Could someone assist me with this?
Click to expand...
Click to collapse
Once your phone has taken either 4.3 OTA (VRUCML1 or VRUCNC1), downgrading to 4.1.2 will result in a hard brick. You can only switch between VRUMCL1 and VRUCNC1, the phone will essentially not boot on any other firmware. Downgrade to VRUCML1 then root via Saferoot. It is safe to do this.
Users with unlocked bootloaders (aka people who did not take either 4.3 OTA) can switch to ICS or JB 4.1.2 via Odin without fail or issue. We can do so, unless somehow we end up taking either 4.3 ota.
SlimSnoopOS said:
Once your phone has taken either 4.3 OTA (VRUCML1 or VRUCNC1), downgrading to 4.1.2 will result in a hard brick. You can only switch between VRUMCL1 and VRUCNC1, the phone will essentially not boot on any other firmware. Downgrade to VRUCML1 then root via Saferoot. It is safe to do this.
Users with unlocked bootloaders (aka people who did not take either 4.3 OTA) can switch to ICS or JB 4.1.2 via Odin without fail or issue. We can do so, unless somehow we end up taking either 4.3 ota.
Click to expand...
Click to collapse
Thank you! I apologize for the late response, but you explained this perfectly for me. I was able to downgrade and root, install safestrap, and even flash a ROM. However, I have only gotten one ROM to flash correctly. Is there another step I have missed? I have only gotten CleanROM 8.1 to flash correctly while everything else flashes but does not boot. I really appreciate the help!
Trevon75 said:
Thank you! I apologize for the late response, but you explained this perfectly for me. I was able to downgrade and root, install safestrap, and even flash a ROM. However, I have only gotten one ROM to flash correctly. Is there another step I have missed? I have only gotten CleanROM 8.1 to flash correctly while everything else flashes but does not boot. I really appreciate the help!
Click to expand...
Click to collapse
Unsure why it won't flash any other roms try this thread it's a good starting point
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
So I've been working on this all night last night and all day today.
The issue- phone will boot, get to the red Verizon boot screen, sit there for approximately 45-60 seconds, then go to the lock screen. Within a couple of seconds, Then a message pops up that says process com.android.phone has stopped, then the phone reboots.
What I've tried- flashing various Vralec boot strings through Odin 3.2 and 1.3. Also tried five different stock ROMs and a CF Auto Root, in the hopes unlocking the bootloader would allow me to get a ROM to flash. Each and every one of these things has had an AUTH fail in Odin. Can anyone help me please?
I've also googled stuck red verizon screen, verizon s3 boot loop, process com.android.phone has stopped. None of the solutions I've found have been helpful, and are usually what led to the actions tried above. I believe I've encountered this before, but I checked my post history and wasn't able to find a thread, so I assume I found the solution on my own the last time.
Any assistance would be greatly appreciated!
What software version are you running? What baseband?
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
What software version are you running? What baseband?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
This is a warranty replacement from Verizon. Since I can't get it to boot, is there an alternative method to find those versions?
I have another S3, replaced less than a month ago, so I would assume they are the same software version and basebands, and that one is running 4.4.2 and I535OYUDNE1
The soft bricked, boot loop, S3 belongs to my girlfriend.
Flashing other ROMs on the S3 4.3 and newer will brick it. The bootloader was never unlocked. I'll try to find the thread describing the issue and post it here.
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
I hope that helps.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
Flashing other ROMs on the S3 4.4 and newer will brick it. The bootloader was never unlocked. I'll try to find the thread describing the issue and post it here.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Flashing the ROMS through Odin failed every time, and none of that was done until AFTER the phone went in to a boot loop. It was already soft bricked, so I tried various different methods. Now I know, for future reference, that attempting to flash ROMs without unlocking the bootloader will brick it. Good to know.
If I can work around the Odin failed authorization, I believe I can flash a stock ROM to the phone and be all right, OR if someone can tell me how to unlock the bootloader, I should be able to flash a custom ROM, correct? It seems that the boot partition permissions were changed and have now affected the boot process, from what I've been reading.
Hybridnoob said:
Flashing other ROMs on the S3 4.3 and newer will brick it. The bootloader was never unlocked. I'll try to find the thread describing the issue and post it here.
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
I hope that helps.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Reading up on your link now, will let you know result. Thank you!
edit: ok, I looked at the download mode accessible link, and that is one I'd tried before. Flashed the ALL I535 .tar and ran in to the auth fail message on odin. Going to try the other method now.
No one has been able to unlock the bootloader since 4.3. I doubt anyone's really trying now because the phone is older. Sorry man.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
No one has been able to unlock the bootloader since 4.3. I doubt anyone's really trying now because the phone is older. Sorry man.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I got towelroot to work to get my S3 to be able to install SuperSU and then Titanium Backup, but haven't found a bootloader unlock either. So, the phone is pretty much bricked?
jester369 said:
I got towelroot to work to get my S3 to be able to install SuperSU and then Titanium Backup, but haven't found a bootloader unlock either. So, the phone is pretty much bricked?
Click to expand...
Click to collapse
Bricked no, if your able to install apps it's far from bricked. He is correct however once the bootloader is locked your pretty much stuck. Replacements directly from verizon are coming back with 4.4.2 installed.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Unless you can find a fully stock ROM to flash via Odin, you may be in trouble. Unlocking the bootloader isn't an option. Without seeing your phone, I won't say it's bricked though.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
Unless you can find a fully stock ROM to flash via Odin, you may be in trouble. Unlocking the bootloader isn't an option. Without seeing your phone, I won't say it's bricked though.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
As I just stated in the post above yours if you can install apps the phone isn't bricked. Bootloader unlocking on the S3 with 4.3 or 4.4 is merely a possibility but probably unlikely
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Hybridnoob said:
No one has been able to unlock the bootloader since 4.3. I doubt anyone's really trying now because the phone is older. Sorry man.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
All right, tried the recover from computer, it's to recover a bricked bootloader. My bootloader isn't bricked, it's the actual ROM that's non functional. So that didn't help. Just need a stock ROM to flash to the phone, can still get to download mode, which connects to Odin, no problem, can also get to stock recovery, Volume Up, Menu, power. Just need a stock ROM that works, or a way to get whatever authorization Odin or the phone wants in order to flash a boot chain and stock ROM. (I do know now not to flash a custom ROM, thank you for that!)
ShapesBlue said:
Bricked no, if your able to install apps it's far from bricked. He is correct however once the bootloader is locked your pretty much stuck. Replacements directly from verizon are coming back with 4.4.2 installed.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Sorry, some clarification. I have TWO S3s, MY S3 is fine, and can install apps. The girlfriend's S3 is soft bricked and in a boot loop. Bootloader is fine, download mode is fine. Just hangs on red Verizon boot screen, when it gets to lock screen says process com.android.phone has stopped and reboots.
Hybridnoob said:
Unless you can find a fully stock ROM to flash via Odin, you may be in trouble. Unlocking the bootloader isn't an option. Without seeing your phone, I won't say it's bricked though.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Been trying to find a fully stock ROM and been unsuccessful. Any I've found have failed in Odin and failed to flash in stock recovery mode, something about a certificate failure.
jester369 said:
Sorry, some clarification. I have TWO S3s, MY S3 is fine, and can install apps. The girlfriend's S3 is soft bricked and in a boot loop. Bootloader is fine, download mode is fine. Just hangs on red Verizon boot screen, when it gets to lock screen says process com.android.phone has stopped and reboots.
Click to expand...
Click to collapse
I definitely would not call that soft bricked. Can you get into recovery and try clearing cache and reboot? Worst case, factory reset from recovery and you should be good to go.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
I definitely would not call that soft bricked. Can you get into recovery and try clearing cache and reboot? Worst case, factory reset from recovery and you should be good to go.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I can get in to recovery, I've tried clearing cache, factory reset, no dice. Exact same thing.
have you tried using odin or kies to just flash the stock NE1 4.4.2? youll have to reroot with towelroot afterwards but atleast the phone will be functional. as for the bootloader, sounds like its locked anyways so it wont be no worse than the shape youre in already.
4.4 and 4.3 Sticky Roll-Up Thead
http://forum.xda-developers.com/showthread.php?t=2639337
TouchWiz 4.4 Download List
http://forum.xda-developers.com/gal...4-download-list-7-10-14-t2812189/post54062704
VRUDNE1 (Android 4.4.2 - Kit Kat) No-Wipe Factory Image
http://forum.xda-developers.com/showthread.php?t=2795659
-somebody- said:
have you tried using odin or kies to just flash the stock NE1 4.4.2? youll have to reroot with towelroot afterwards but atleast the phone will be functional. as for the bootloader, sounds like its locked anyways so it wont be no worse than the shape youre in already.
Click to expand...
Click to collapse
I have tried that, I believe I haven't been able to find a stock 4.4.2 ROM though. I'm fine with rebooting and re rooting, that's not my concern, even if I can't root, I don't care about that. Could you point me to a solid stock ROM image?
The images I've tried, numerous labeled stock ROMs, and, out of desperation last night, two custom ROMs. Through either recovery mode, or Odin, all failed, through recovery it was a certificate error, and through Odin it was an authorization error. AUTH FAIL, specifically.
jester369 said:
I have tried that, I believe I haven't been able to find a stock 4.4.2 ROM though. I'm fine with rebooting and re rooting, that's not my concern, even if I can't root, I don't care about that. Could you point me to a solid stock ROM image?
The images I've tried, numerous labeled stock ROMs, and, out of desperation last night, two custom ROMs. Through either recovery mode, or Odin, all failed, through recovery it was a certificate error, and through Odin it was an authorization error. AUTH FAIL, specifically.
Click to expand...
Click to collapse
that last link i believe is the actual tar file for NE1 if i remember correctly, i used kies when i updated mine and i didnt encounter any errors. did you delete the .md5 so it was just .tar (not .tar.md5) before trying it in odin? i know most people prefer odin over kies but if youre having this many problems kies is worth a shot.
worst case i can upload the one i have
-somebody- said:
that last link i believe is the actual tar file for NE1 if i remember correctly, i used kies when i updated mine and i didnt encounter any errors. did you delete the .md5 so it was just .tar (not .tar.md5) before trying it in odin? i know most people prefer odin over kies but if youre having this many problems kies is worth a shot.
worst case i can upload the one i have
Click to expand...
Click to collapse
I will try that and report back. Thank you!