Hi Guys,
I have a Verizon SGS3 with stock JB 4.1.1 and I was following the steps posted here ([GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 3/5***).
I got a little distracted and flashed both TWRP(1st) and Clockwork(2nd) but I still managed to successfully get to step 5 and root my phone and unlock boot loader.
Then I used clockwork and tried to install the liquid smooth 4.2 ( wiped cache and memeory etc) and after the rom installed and I selected reboot, and my phone was hard bricked. ie not response to any key and black screen, so no way to reload or restore anything. of course it was at the point I realized my mistake of flashing both.
I am going to JTAG the phone today, but I have a few questions,
My questions -
-was it because I had both TWRP and clockwork that caused this?
-if yes, how do I get rid of TWRP?
-I only want touchwiz and non of the other Verizon bloat, can you recommend a good stable rom.
thanks
What you have failed to realize that you don't have both recoveries you overwritten one when you flash the other. Believe it or not most if not all of Touchwiz ROMs are stable. The mistake came from the flashing of a custom ROMs as you failed to mention whether or not you have flashed the right Gapps for the ROM.
jmxc23 said:
What you have failed to realize that you don't have both recoveries you overwritten one when you flash the other. Believe it or not most if not all of Touchwiz ROMs are stable. The mistake came from the flashing of a custom ROMs as you failed to mention whether or not you have flashed the right Gapps for the ROM.
Click to expand...
Click to collapse
Thanks for the quick reply.
I did not flash gaaps. I thought I could do it after I got the liquid smooth 4.2 on it. Are you saying that I needed to flash the gaaps first before the liquid smooth?
Not flashing the gapps wouldn't "hard brick" your phone. You just wouldn't have the Play Store, Google Music, etc. OP, are you sure you're hard bricked? Because it's really difficult to hard brick this phone. The only way I've currently seen people HB their phone is by flashing something for the international S3. You can't get into recovery or download mode? Buy either holding Volume Up, Power or Volume Down, Power?
RCOVA said:
Not flashing the gapps wouldn't "hard brick" your phone. You just wouldn't have the Play Store, Google Music, etc. OP, are you sure you're hard bricked? Because it's really difficult to hard brick this phone. The only way I've currently seen people HB their phone is by flashing something for the international S3. You can't get into recovery or download mode? Buy either holding Volume Up, Power or Volume Down, Power?
Click to expand...
Click to collapse
none of the button combination have any response. I tried removing battery and waiting 5 mins and reinserting but nothing. My battery was at 80% when I flashed the liquid smooth and bricked it. When I plug in to the PC, the USB drivers no longer load so I cannot use ODIN.
I am out of ideas. Anything anyone can help would be appreciated. thanks
What is the name of the file you flashed?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
What is the name of the file you flashed?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Liquid-JB-v2.2-OFFICIAL-t0lte
lloydteo said:
Liquid-JB-v2.2-OFFICIAL-t0lte
Click to expand...
Click to collapse
Well, that makes sense. You flashed the Galaxy Note 2 version. You need to flash d2vzw roms for our GSIII. Everything you did beforehand was presumably fine.
Sent from my SCH-I535 using xda app-developers app
lloydteo said:
Liquid-JB-v2.2-OFFICIAL-t0lte
Click to expand...
Click to collapse
And boom goes the dynamite.
RCOVA said:
And boom goes the dynamite.
Click to expand...
Click to collapse
Alright alright this is what you do. If the phone isn't hard bricked (which it may be since you flashed a GNII rom) you need to either try to boot into recovery (hold volume down and home at the same time, then hold power. When it vibrates, release the power and hold the other two until you get recovery) or ODIN (odin is the same, just hold volume up instead of down). Report back if you can boot into these and I will assist from there.
nrock2256 said:
Alright alright this is what you do. If the phone isn't hard bricked (which it may be since you flashed a GNII rom) you need to either try to boot into recovery (hold volume down and home at the same time, then hold power. When it vibrates, release the power and hold the other two until you get recovery) or ODIN (odin is the same, just hold volume up instead of down). Report back if you can boot into these and I will assist from there.
Click to expand...
Click to collapse
You have the button combinations reversed. Volume up puts your phone in recovery mode, volume down puts it in download (Odin) mode.
And he is hard bricked. He stated no response from any button combinations.
RCOVA said:
And he is hard bricked. He stated no response from any button combinations.
Click to expand...
Click to collapse
That is correct, there is not response from ANY buttons and my battery is confirmed charged. USB drivers unable to load when plug int o PC also.
Do you guys know of any good sites that lists the latest custom roms for verizon SGS3? I mean the correct and latest file names for the roms.
thanks
lloydteo said:
That is correct, there is not response from ANY buttons and my battery is confirmed charged. USB drivers unable to load when plug int o PC also.
Do you guys know of any good sites that lists the latest custom roms for verizon SGS3? I mean the correct and latest file names for the roms.
thanks
Click to expand...
Click to collapse
You can find them all here on xda. Just browse the Android Development and Original Android Development forums for the Verizon Galaxy s3 only. You'll find AOSP ROMs and all kernels in Original Android Development and Touchwiz ROMs and mods and other stuff in Android Development. Don't flash anything that isn't made for the Verizon Galaxy S3
Sent from my Verizon Samsung Galaxy SIII
lloydteo said:
That is correct, there is not response from ANY buttons and my battery is confirmed charged. USB drivers unable to load when plug int o PC also.
Do you guys know of any good sites that lists the latest custom roms for verizon SGS3? I mean the correct and latest file names for the roms.
thanks
Click to expand...
Click to collapse
Not that I know of besides xda and rootzwiki, just be more careful. When you download roms always look for the download links for "d2vzw" roms or that specifically state "Verizon GSIII" when the link isn't immediately on xda. Typically AOSP roms are the ones with multiple multi-carrier, multi-device download links so always check and re-check after downloading zips.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Not that I know of besides xda and rootzwiki, just be more careful. When you download roms always look for the download links for "d2vzw" roms or that specifically state "Verizon GSIII" when the link isn't immediately on xda. Typically AOSP roms are the ones with multiple multi-carrier, multi-device download links so always check and re-check after downloading zips.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks again for the pointers.
When I get my phone back today, I have decided to flash the Bean ROM. I read the instructions and have one question. What does STEP 1 mean when it says "pick the locked version?" Does he mean pick the locked ROM version? If someone can explain briefly it would be appreciated. thanks
Install Instructions:
Step 1-
Make sure u are unlocked or pick the locked version during flash
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom
Step 4-
Reboot and Enjoy! after first boot reboot if youre using a custom ui and not the stock one(fixed soon)
lloydteo said:
Thanks again for the pointers.
When I get my phone back today, I have decided to flash the Bean ROM. I read the instructions and have one question. What does STEP 1 mean when it says "pick the locked version?" Does he mean pick the locked ROM version? If someone can explain briefly it would be appreciated. thanks
Install Instructions:
Step 1-
Make sure u are unlocked or pick the locked version during flash
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom
Step 4-
Reboot and Enjoy! after first boot reboot if youre using a custom ui and not the stock one(fixed soon)
Click to expand...
Click to collapse
He's taking about your bootloader. If you chose to root and unlock your bootloader when you rooted your phone, you get the regular rom. If you chose to only root and not unlock then your bootloader is locked and you must flash the locked version.
Sent from my Verizon Samsung Galaxy SIII
lloydteo said:
Thanks again for the pointers.
When I get my phone back today, I have decided to flash the Bean ROM. I read the instructions and have one question. What does STEP 1 mean when it says "pick the locked version?" Does he mean pick the locked ROM version? If someone can explain briefly it would be appreciated. thanks
Install Instructions:
Step 1-
Make sure u are unlocked or pick the locked version during flash
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom
Step 4-
Reboot and Enjoy! after first boot reboot if youre using a custom ui and not the stock one(fixed soon)
Click to expand...
Click to collapse
Oh, long story short that's the ICS rom that he created in July. From July-August, we had a locked bootloader, which is what he's referring. Thi meant flashing roms required something with a Kexec boot sequence, but once the GSIII was unlocked in August his rom and every rom presently available requires you to have an unlocked bootloader.
That said, when you get your phone you will need to:
1) root
2) unlock the bootloader
3) then proceed from there, whether that's backing up your IMEI or flashing a rom, etc.
I thoroughly suggest his JB rom since there's active development on it. Beans JB rom was updated last week and has "Build 15 [04/21/13]" in the title.
joshua5683 said:
He's taking about your bootloader. If you chose to root and unlock your bootloader when you rooted your phone, you get the regular rom. If you chose to only root and not unlock then your bootloader is locked and you must flash the locked version.
Sent from my Verizon Samsung Galaxy SIII
Click to expand...
Click to collapse
Just got some bad news from the repair shop, they said that they cannot recover the phone. Any suggestions of a good shop that can recover the phone from a hard brick?
Also is this d2vzw_JellyBeans_B15 the locked or unlocked version? thans
lloydteo said:
Just got some bad news from the repair shop, they said that they cannot recover the phone. Any suggestions of a good shop that can recover the phone from a hard brick?
Also is this d2vzw_JellyBeans_B15 the locked or unlocked version? thans
Click to expand...
Click to collapse
Not sure about the shop thing but in the instructions for flashing that rom it says you must be unlocked. Which means you must have an unlocked bootloader. You do this by flashing SuperSU_Bootloader_FIXED.zip in recovery. That zip file is recommended for flashing when you're following the root guide and they have a download link for it.
Sent from my Verizon Samsung Galaxy SIII
Related
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "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."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Lembro said:
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "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."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Click to expand...
Click to collapse
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
RyanW114 said:
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
Click to expand...
Click to collapse
Agreed! Op, do more reading and less flashing before you end up with a 600.00 paperweight!
Like he says above you have not unlocked your bootloader . Restore nandroid or recover to stock. Then unlock your bootloader and try again
Sent from my SCH-I535 using xda premium
Get rid of the Verizon screen of death
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
MDMoore313 said:
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
Click to expand...
Click to collapse
Refer to my last post
droidstyle said:
Refer to my last post
Click to expand...
Click to collapse
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
refer to post #3 and read this link
http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13
Zalithian said:
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
Click to expand...
Click to collapse
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Zalithian said:
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Click to expand...
Click to collapse
That makes more sense, as the nightlys progress and more modifications are being made, overnight the "switch is flipped" so to speak, and if you're not running a custom rom,
MDMoore313 said:
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
Click to expand...
Click to collapse
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
The secure aboot.img only checks 3 of the 5 system images on boot. Since we can flash a custom recovery to the recovery partition, the secure aboot img lets it ride, but knows it there....hence why you see the custom lock screen, but device still boots. Kexec allowed the bootloader aka secure aboot.img to see the stock kernel(boot.img) and pass signature checks, then side loads the custom kernel. Thats why there was 3 reboots...now that the bootloader is unlocked, we ditch kexec because unsecure aboot is unlocked and not checking signatures.
However, if you flash a kernel thats non kexec and the bootloader is locked, you will get the verizon screen of death since the secure aboot.img is checking signatures. So never lock the bootloader unless your on stock rom/kernel or using kexec.
Deleted
Jesus. All of these people who don't read up on things before they flash something astounds me.
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
EvoSideHustlAZ said:
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ezrecovery to unlock? What?
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
No, that just means that it normally has detected some changed files. If you WERE unlocked you would never see that icon.
TAPPED in on my (now unlocked bootloader) Verizon S3
strung said:
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
Click to expand...
Click to collapse
Well, step 1 is going Odin back to stock, but if a cache wipe and factory reset aren't done (like in Droidstyle's guide), then it will never completely boot, at least that's what I experienced after my phone sat at that screen for 10+ minutes. It doesn't run the user setup again.
I'm thinking about romming an HTC One X for Rogers and I've tried looking up information about installing custom roms. I know I need to unlock the bootloader first and that TWRP is likely the easiest method in order to rom. But I've read some conflicting things. Does it matter which version of the software I have? There just seems to be multiple guides.
Would this guide work?
h t t p:// theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
I'm happy to do the research, but hopefully someone can point me in the right direction.
I'm thinking about romming an HTC One X for Rogers and I've tried looking up information about installing custom roms. I know I need to unlock the bootloader first and that TWRP is likely the easiest method in order to rom. But I've read some conflicting things. Does it matter which version of the software I have? There just seems to be multiple guides.
Would this guide work?
h t t p:// theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
I'm happy to do the research, but hopefully someone can point me in the right direction.
Click to expand...
Click to collapse
The version of software do matter. Currently 2.20 is un rootable if you did not unlock bootloader on earlier version
Here is the link which you need follow http://forum.xda-developers.com/showthread.php?p=26512322
Sent from my HTC One X using xda premium
Thabnk, I did read through part of that but I don't see anything there for version 1.94?
You can root and unlock 1.94 then flash recovery and rom fine.
Rogers HTC One X can be unlocked through the HTCdev site. Once the bootloader is unlocked you can install TWRP and flash any evita rom you want.
Sent from my HTC One XL using xda premium
Any variant of the HOX can be bootloader unlocked via HTCDev except for the AT&T version. Firmware numbers for you will not matter in the slightest.
Sent from my HTC One XL using xda app-developers app
Athrun88 said:
Any variant of the HOX can be bootloader unlocked via HTCDev except for the AT&T version. Firmware numbers for you will not matter in the slightest.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
So I was able to unlock the bootloader. To install TWRP I installed GooManager and Installed "OpenRecoveryScript".
When I try to reboot the phone into recovery, nothing happens.
Is there a guide how to use TWRP. Most of the guides seem pretty basic, but I don't even know if I have it installed properly. I'm trying to install ViperX
n3gkiwi said:
So I was able to unlock the bootloader. To install TWRP I installed GooManager and Installed "OpenRecoveryScript".
When I try to reboot the phone into recovery, nothing happens.
Is there a guide how to use TWRP. Most of the guides seem pretty basic, but I don't even know if I have it installed properly. I'm trying to install ViperX
Click to expand...
Click to collapse
Nevermind. I just installed using command prompt following http://forum.xda-developers.com/showthread.php?t=1814914 this guide. Thanks Athrun88!
Is there a specific directory I should be putting the roms in order to install them or does it not matter?
n3gkiwi said:
Nevermind. I just installed using command prompt following http://forum.xda-developers.com/showthread.php?t=1814914 this guide. Thanks Athrun88!
Is there a specific directory I should be putting the roms in order to install them or does it not matter?
Click to expand...
Click to collapse
hey! that's my guide! haha, glad to see my first real contribution be somewhat of a success.
As long as it's in the root directory (not in a folder) of the internal SDcard, you'll be fine. Also, make sure you make a backup of your stock ROM just in case you need to go back to it.
Another thing, copy down your APN settings (word by word) from your stock ROM. Not sure if Rogers is the same as Telus, but Telus needs two APNs to get LTE enabled. If you could PM those to me as well, I could add them to my guide as well. Thanks.
Ughhh. Tried to install ViperX 2.6.0 using TWRP however it didn't work. Says Checking Model ID then "assert failed: getprop("ro.product.device")==
Any ideas?
n3gkiwi said:
Ughhh. Tried to install ViperX 2.6.0 using TWRP however it didn't work. Says Checking Model ID then "assert failed: getprop("ro.product.device")==
Any ideas?
Click to expand...
Click to collapse
Might have answered my own question, but can I only install Roms in this dev section because I'm on Roger (so no international mods)?
n3gkiwi said:
Might have answered my own question, but can I only install Roms in this dev section because I'm on Roger (so no international mods)?
Click to expand...
Click to collapse
Don't domt ddon't don't domt don't please don't flash an international rom! Or your device will be most likely a close to hard brick
omario8484 said:
Don't domt ddon't don't domt don't please don't flash an international rom! Or your device will be most likely a close to hard brick
Click to expand...
Click to collapse
Yes after some research, I quickly figured that... Phew.
Is there any way to tell if the rom is stable or not for the AT&T/Rogers model?
n3gkiwi said:
Yes after some research, I quickly figured that... Phew.
Is there any way to tell if the rom is stable or not for the AT&T/Rogers model?
Click to expand...
Click to collapse
I recommend any of our ggreat roms I'm running viper 2.00 trust me try it and you'll love iit! Remember to full wipe! ( not SD if course)
omario8484 said:
I recommend any of our ggreat roms I'm running viper 2.00 trust me try it and you'll love iit! Remember to full wipe! ( not SD if course)
Click to expand...
Click to collapse
I think that will be the first one I will install. So I have backed up my original default Rogers/HTC backup using TWRP and will download titanium backup?
Anything else you can/would recommend before I proceed?
The help has been great and much appreciated.
n3gkiwi said:
I think that will be the first one I will install. So I have backed up my original default Rogers/HTC backup using TWRP and will download titanium backup?
Anything else you can/would recommend before I proceed?
The help has been great and much appreciated.
Click to expand...
Click to collapse
So if you would like toto back up your apps than yes u can use titanium but yes make a back up sounds like u already did of your stock rom ...download viper 2.00 put it on your SD where you'll remember. To find it ... Once in twrp hit wipe menu ...wipe system ..factory reset ...and wipe dalvic cache than go back to the home menu in twrp and click install and find viper and this is very important since you wiped system you'll see in viper menu flash stock kernel or install rom ...hit install rom and go from there if you don't you'll be stuck. At. HTC dev screen and have to get back into recovery
---------- Post added at 04:07 AM ---------- Previous post was at 04:03 AM ----------
n3gkiwi said:
I think that will be the first one I will install. So I have backed up my original default Rogers/HTC backup using TWRP and will download titanium backup?
Anything else you can/would recommend before I proceed?
The help has been great and much appreciated.
Click to expand...
Click to collapse
One last important thing in case u didn't know
If you're ever stuck in bootloop this will do the trick to get into bootloader and back to recovery
Turn on, hold power 10-15 seconds, until screen goes black, let off, press n hold volume down, press power just 2-3 seconds, let off power button but continue holding vol. Down
LoL wow, already done. Using the rom now. :laugh:
Wow, that was easy. Not sure if I should have checked some of the options (like one to enable exchange mail, and another for better sound). But it was so easy I guess I can always just redo it.
Was starting to think rooting maybe wasn't worth it (last root I did was on the original Nexus). Just going through all the features on ViperX, I'm glad I did.
n3gkiwi said:
LoL wow, already done. Using the rom now. :laugh:
Wow, that was easy. Not sure if I should have checked some of the options (like one to enable exchange mail, and another for better sound). But it was so easy I guess I can always just redo it.
Was starting to think rooting maybe wasn't worth it (last root I did was on the original Nexus). Just going through all the features on ViperX, I'm glad I did.
Click to expand...
Click to collapse
Roms are the best part . Here's the link to the sound mod thread http://forum.xda-developers.com/showthread.php?t=1819524 download the first one of course NOT the cm10 one DONT wipe anything before installing but after when it says done you LL see an option to wipe cache/dalvic cache choose that then reboot
Just rooted my new SGS3 using New Root Method Released for Verizon’s Galaxy S3, No Odin Required. i did the data & kelvic wipe then install Clean Rom 5.0. All progressed without a hitch. Even backed up with CWM prior to flash.
I rebooted into the new rom and got this: System software not authorized by Verizon Wireless... rebooted several time with same result.
What can I do now? Thanks for your help.
Just a wild guess, but me thinks your bootloader is still locked! But I'm not sure that will even apply because I rooted my device before unlocking the bootloader. But I rooted my device via ODIN first.
You can try EZ-Unlock via the Market. The GUI is still very buggy and will show the status as unknown but the internal workings of the app works good.
You got nothin to loose in trying. Go back to stock and give it another whirl after you've unlocked the bootloader.
Of that fails then I would suggest using the tried and true method..ODIN.
G'luck!
yup your bootloader is still locked
check the downloads thread and use version 1.2.
That means your boatloader is locked. You now must Odin back to stock and start over. Droid style has a guide stickied in the development thread. Follow section 6 of it.
Next time use ez unlock version 1.2 to unlock you boatloader.
Sent from my SGS3 running Eclipse 2.1
downloads list
http://forum.xda-developers.com/showthread.php?t=1850506
tekrhino said:
Just a wild guess, but me thinks your bootloader is still locked! But I'm not sure that will even apply because I rooted my device before unlocking the bootloader. But I rooted my device via ODIN first.
You can try EZ-Unlock via the Market. The GUI is still very buggy and will show the status as unknown but the internal workings of the app works good.
You got nothin to loose in trying. Go back to stock and give it another whirl after you've unlocked the bootloader.
Of that fails then I would suggest using the tried and true method..ODIN.
G'luck!
Click to expand...
Click to collapse
Thanks. I can't get past the warning dialogue screen. Pulled the battery, no good. PC can't see the phone with USB.
Prophotog said:
Thanks. I can't get past the warning dialogue screen. Pulled the battery, no good. PC can't see the phone with USB.
Click to expand...
Click to collapse
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
tekrhino said:
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Thanks to everyone!! Looks to be a long night. :>)
tekrhino said:
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
I lol'ed at your post. A little dramatic, don't you think? He's not even close to bricked. Just Odin from download mode back to stock, and redo the steps with bootloader unlock.
Here is a gift (working ez-unlock v1.2)
http://dl.dropbox.com/u/42057363/com.mmmeff.ez.unlock_3.apk
@Techsavvy
Yeah, perhaps a tad overdone on the theatricals.
Cut me some slack, I'm taking acting classes..lol
And... I know... I know..don't quit my day job!
Still having issues. I "think" I am in the download mode. Screen says Downloading.... It has Odin in red in top left corner. Device connects with Odin. BUT I am not getting a PASS message when flashing VRALEC bootchain. Last text line in Odin is: <OSM> Leave CS...
I have tried several attempts.
Suggestions?
Prophotog said:
Still having issues. I "think" I am in the download mode. Screen says Downloading.... It has Odin in red in top left corner. Device connects with Odin. BUT I am not getting a PASS message when flashing VRALEC bootchain. Last text line in Odin is: <OSM> Leave CS...
I have tried several attempts.
Suggestions?
Click to expand...
Click to collapse
No need to do the boot chains. Just follow section 5 of this guide and I recommend root 66 for the ROM you flash
http://forum.xda-developers.com/showthread.php?p=28530394
Sent from my SGS3 running Eclipse 2.1
tekrhino said:
@Techsavvy
Yeah, perhaps a tad overdone on the theatricals.
Cut me some slack, I'm taking acting classes..lol
And... I know... I know..don't quit my day job!
Click to expand...
Click to collapse
I appreciate the theatricals...however, I am having issues with Odin. Can't get the Pass message. I assume the "Downloading..." text means I'm in the download mode. Tried several attempts. I AM glad I'm not close to bricked too! Can't afford $600 or a divorce. Might have to sell a camera instead.
Prophotog said:
Just rooted my new SGS3 using New Root Method Released for Verizon’s Galaxy S3, No Odin Required. i did the data & kelvic wipe then install Clean Rom 5.0. All progressed without a hitch. Even backed up with CWM prior to flash.
I rebooted into the new rom and got this: System software not authorized by Verizon Wireless... rebooted several time with same result.
What can I do now? Thanks for your help.
Click to expand...
Click to collapse
And just for future reference, it's Dalvik, not Kelvic
Sent from my SCH-I535 using xda app-developers app
Prophotog said:
I appreciate the theatricals...however, I am having issues with Odin. Can't get the Pass message. I assume the "Downloading..." text means I'm in the download mode. Tried several attempts. I AM glad I'm not close to bricked too! Can't afford $600 or a divorce. Might have to sell a camera instead.
Click to expand...
Click to collapse
Just a heads up. You can get a real brick with Odin and easy. Follow the guide I linked earlier to a t and you'll be fine
Sent from my SGS3 running Eclipse 2.1
kintwofan said:
Just a heads up. You can get a real brick with Odin and easy. Follow the guide I linked earlier to a t and you'll be fine
Sent from my SGS3 running Eclipse 2.1
Click to expand...
Click to collapse
You are a scholar and a gentleman!! THANK YOU very much. You can have a portrait session on me any time. Name the time and place.
Prophotog said:
You are a scholar and a gentleman!! THANK YOU very much. You can have a portrait session on me any time. Name the time and place.
Click to expand...
Click to collapse
Cool, I take it you're up and running again. Just make sure you use ez unlock 1.2 next time. And the positive is you're an Odin pro now!
Sent from my SGS3 running Eclipse 2.1
Hi, I have a Verizon S3 flashed to Boost Mobile. I tried to gain root by flashing a stock rooted Rom and messed up the flash. I had to take it back to be flashed again  Now I'm more cautious before hand. I should have backed it up before attempting it, I know I know lol can anyone shed some light on how to update a flashed phone as well as how to root it. I could really use the help 
Also after I messed up the boost flash I paniced and flashed a sprint kernel hoping this would fix the problem. Since then anything that I've tried to view including taking camera shots and web browsing if done in landscape mode will be upside down, any remedy for this problem? I know now... root first, flash later. 
Sent from my SPH-L710 using XDA HD
Alex0826 said:
Hi, I have a Verizon S3 flashed to Boost Mobile. I tried to gain root by flashing a stock rooted Rom and messed up the flash. I had to take it back to be flashed again  Now I'm more cautious before hand. I should have backed it up before attempting it, I know I know lol can anyone shed some light on how to update a flashed phone as well as how to root it. I could really use the help 
Also after I messed up the boost flash I paniced and flashed a sprint kernel hoping this would fix the problem. Since then anything that I've tried to view including taking camera shots and web browsing if done in landscape mode will be upside down, any remedy for this problem? I know now... root first, flash later. 
Sent from my SPH-L710 using XDA HD
Click to expand...
Click to collapse
Sprint kernel is causing the inversion. Flash a vzw kernel. Read first flash later.
Sent from my SCH-I535 using xda app-developers app
Who ever did your flash might not done it right cause ya not supposed to lose a flash like that unless he didn't do things right. I can factory reset mine and I wont loose flash
Sent from my SPH-L900 using Tapatalk 2
how to unroot samsung galaxay tab 2 7.0 P3113 straight up without any guessing
but guess what i am not the one to be mad at or responsible if anything happens to your device
backup your data of anything
lol had to put that
making this because i was up for like almost 3 hours trying to figure out how to get this done.
first you need 3 files
the latest Jelly Bean stock
http://www.hotfile.com/dl/188869946/30f5c4d/P3113UECLK7_P3113XACCLK7_XAC.zip.html
the odin with root
http://download.chainfire.eu/256/CF...fi-espressowifiue-gtp3113.zip?retrieve_file=1
and
Triangle Away this is where i got the app from
http://forum.xda-developers.com/showthread.php?t=1494114
i put the files in order of size so you can download the files as you go
for extra guidance watch
http://www.youtube.com/watch?v=WzydHUG7XZE
its for s3 but the concept is the exact same
I started from a stock rooted rom i backed up thats what the Triangle Away fourm said to do
Ok while rooted go install Triangle Away once installed boot in to download mode. By turning off the device and holding (Power + Vol down button).
when in download mode press up to enter it this is so you can check your flash / binary count. Once you found out boot restart by (Power + Vol up button) when fully booted
go into Triangle Away before you click reset counter make sure its the same number you saw in the download mode once matched then click the button.
Next after the stock firmware is downloaded extract the file then go back into download mode and press Vol up button to enter it connect device to Odin dont touch or look at anything just click on the left where it says pda click on the md5 file that was extracted from download then click start. Dont touch or look at device until its done because you can possible brick it while in download mode
After flashing let it reboot then skip threw set up to see if superuser is still there. if so (like mine) install Triangle Away app again check the counter. (should be on zero) now go back to download mode and reflash the stock md5 again
and now should be fully stock with no root and no binary count. Take it back to store!! lol or just enjoy stock for new OTA.
#1 this is for the Canadian version of the tab 2. you need to state that.
#2 couldn't you have uploaded this to somewhere else other than hotfile?
First of all, thank you for posting this, wealthy23!
Second, I see fix-this! said this is Canadian version of stock ROM. Is this different from the US version? If so, what's the difference and where I can find the US stock ROM?
premudriy said:
First of all, thank you for posting this, wealthy23!
Second, I see fix-this! said this is Canadian version of stock ROM. Is this different from the US version? If so, what's the difference and where I can find the US stock ROM?
Click to expand...
Click to collapse
Thanks but
I am not sure what he is talking about but it worked on my tab 2 which is US version and
also hot file is used because I didn't upload it I got link from official Samsung site used it so you won't have to sign up for a Samsung account just to get the link and wanted the file to be as pure from source as possible especially when using Odin to flash
Sent from my HTC Glacier using xda premium
I didnt mean to be rude but the file you uploaded is for the canadian version. I double checked on google with the build number. Theres also a US version but with a slightly different extension. Im not at home or i would upload it.
fix-this! said:
I didnt mean to be rude but the file you uploaded is for the canadian version. I double checked on google with the build number. Theres also a US version but with a slightly different extension. Im not at home or i would upload it.
Click to expand...
Click to collapse
O ok wasn't sure how you meant it but that version worked on my tablet and I am in the US but if your file is US you can post it thank you for helping out
Sent from my HTC Glacier using xda premium
I think I found a way
The thread is a month old, so please forgive the necromancy. I haven't noted it elsewhere, so I post in hopes it will help somebody else out.
I found that this works if you flashed via CF-Auto-Root-espressowifi. In triangle away, I reset the counter. Rebooted and clicked "system modified workaround". Rebooted again. Immediately checked the status and after mauling that matter over a bit, it decided "Official" and let me update. (Or, rather, told me I was up to date) Note: probably a good idea to disable the system modified workaround before upgrading. As of yet, it still says "Offical" after disabling modified workaround & reboot, but from what I've read, it will eventually change it's mind. Hence, using this, I imagine you should be able to keep root and use Triangle Away to check for updates every so often. Not stock flashing required.
If you find these instuctions helpful, pay for the App - he deserves it.
Question if I boot into clockworkmod recovery and do a factory reset, wipe cache portions, & dalvik cache then boot into download mode and flash the stock rom will I still be rooted?
Homebound said:
Question if I boot into clockworkmod recovery and do a factory reset, wipe cache portions, & dalvik cache then boot into download mode and flash the stock rom will I still be rooted?
Click to expand...
Click to collapse
Most likely you didn't change back the recovery plus root still might show up after you flash stock rom did you flash with Odin or cwm?
Sent from my HTC Glacier using xda premium
wealthy23 said:
Most likely you didn't change back the recovery plus root still might show up after you flash stock rom did you flash with Odin or cwm?
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I flashed using Odin. I installed rom manager but it said it couldn't find root & when I boot into recovery I get the shock recovery.
Homebound said:
I flashed using Odin. I installed rom manager but it said it couldn't find root & when I boot into recovery I get the shock recovery.
Click to expand...
Click to collapse
Ok great just check your flash counter in download mode
Sent from my HTC Glacier using xda premium
I went to make a backup and ROM Manager said there was a new version of Recovery (ended in .8). I accepted and selected the Touch version. When I then tried to make a backup, 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. There is no way to restore a backup or use the phone in any way. I have been doing this since the days of the OG Droid, but I am lost now. Please help.
sounds like you didnt unlock your booloader
Yes it does, but it has been unlocked for a long time, and I don't think I lost the unlock with tthe 4.1.2 update. How can I unlock the bootloader without being able to start the phone?
melucci said:
Yes it does, but it has been unlocked for a long time, and I don't think I lost the unlock with tthe 4.1.2 update. How can I unlock the bootloader without being able to start the phone?
Click to expand...
Click to collapse
Prostrate yourself to Odin.
Sent from my SCH-I535 using Tapatalk 2
melucci said:
Yes it does, but it has been unlocked for a long time, and I don't think I lost the unlock with tthe 4.1.2 update.
Click to expand...
Click to collapse
OTA's ALWAYS re-lock the bootloader and remove root.
Sent from my SCH-I535 using xda app-developers app
melucci said:
Yes it does, but it has been unlocked for a long time, and I don't think I lost the unlock with tthe 4.1.2 update. How can I unlock the bootloader without being able to start the phone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1974114
See download #4 and step 1 on how to use odin.
melucci said:
Volume up/home/power just boots to this message every time. So does Volume down/home/power. There is no way to restore a backup or use the phone in any way. I have been doing this since the days of the OG Droid, but I am lost now. Please help.
Click to expand...
Click to collapse
Are you sure? Make sure you hold down Volume Down + Home for a few seconds before also hitting the Power button. I saw that same message yesterday when going back to stock and I was still able to boot into recovery/download mode. Also make sure your device is completely powered down (and not plugged in/charging)
deleted
THAT DID IT! I held volume down/home for a few seconds and then held power. The phone booted to a mode I had not seen before (recovery/download as you said?) and I said cancel and the phone booted!
I ran EZ-Unlock to unlock the boot loader. I tried several apps that require superuser permissions and they were granted it and run fine. So I assume I am still rooted, right?
Thanks so much for your help.
sounds like you should be good to go. one thing you should should consider doing is backing your IMEI if you havent already.
http://forum.xda-developers.com/showthread.php?t=1852255
bricked
melucci said:
THAT DID IT! I held volume down/home for a few seconds and then held power. The phone booted to a mode I had not seen before (recovery/download as you said?) and I said cancel and the phone booted!
I ran EZ-Unlock to unlock the boot loader. I tried several apps that require superuser permissions and they were granted it and run fine. So I assume I am still rooted, right?
Thanks so much for your help.
Click to expand...
Click to collapse
I done the same thing and it continues to go back to that same screen and will not restart.
PLEASE HELP!
kustom1955 said:
I done the same thing and it continues to go back to that same screen and will not restart.
PLEASE HELP!
Click to expand...
Click to collapse
Odin flash a stock image then re-root and unlock your bootloader if you so desire.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Odin flash a stock image then re-root and unlock your bootloader if you so desire.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
My computer will not recognize my phone has been plugged in. I have deleted all the drivers and then reinstalled them anf can get my phone in odin mode but the computer still will not recognize my device.
Thanks for your help
kustom1955 said:
My computer will not recognize my phone has been plugged in. I have deleted all the drivers and then reinstalled them anf can get my phone in odin mode but the computer still will not recognize my device.
Thanks for your help
Click to expand...
Click to collapse
First, some background info is needed.
1) What did you do to your phone?
2) You have no success booting into Download mode?
3) Did you flash something in recovery? If so, what is the file name of the file you flashed?
Edit: Disregard #2, apparently I can't read. Are you using the Samsung OEM cable? Have you tried using a different USB port? Different computer?
SlimSnoopOS said:
First, some background info is needed.
1) What did you do to your phone?
2) You have no success booting into Download mode?
3) Did you flash something in recovery? If so, what is the file name of the file you flashed?
Edit: Disregard #2, apparently I can't read. Are you using the Samsung OEM cable? Have you tried using a different USB port? Different computer?
Click to expand...
Click to collapse
I just noticed the person you helped before me had a galaxy s3 and mine is a note 2 I605.
I opened the ROM manager app and it said something about allowing other devices to text from your same #.
I really hope this helps to figure this out. I'm going to try a different computer now.
kustom1955 said:
I just noticed the person you helped before me had a galaxy s3 and mine is a note 2 I605.
I opened the ROM manager app and it said something about allowing other devices to text from your same #.
I really hope this helps to figure this out. I'm going to try a different computer now.
Click to expand...
Click to collapse
You...have a Note 2? Why are you commenting in the Verizon GSIII forum bud? You have to try either your respective Note 2 carrier forum (i605 = Verizon Note 2 right?) or the international Note 2 forums. No one here can help you. Create a new thread in the Q/A section of the proper phone forum you need and you will receive relevant help.
SlimSnoopOS said:
You...have a Note 2? Why are you commenting in the Verizon GSIII forum bud? You have to try either your respective Note 2 carrier forum (i605 = Verizon Note 2 right?) or the international Note 2 forums. No one here can help you. Create a new thread in the Q/A section of the proper phone forum you need and you will receive relevant help.
Click to expand...
Click to collapse
Sorry, I didn't realize I was in the wrong area.
Thanks for your help
Verizon Warning NO MATTER WHAT
SlimSnoopOS said:
Odin flash a stock image then re-root and unlock your bootloader if you so desire.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So far flashed HyperDrive, now AOKP, no matter what I do I get a yellow triangle and a warning.
I reflash stock
relfash VARLEC bootchain
reflash CWM
and try again.
No matter what options, settings, or ROM, I keep getting softbricked! ANY IDEAS?!>!
garvus said:
So far flashed HyperDrive, now AOKP, no matter what I do I get a yellow triangle and a warning.
I reflash stock
relfash VARLEC bootchain
reflash CWM
and try again.
No matter what options, settings, or ROM, I keep getting softbricked! ANY IDEAS?!>!
Click to expand...
Click to collapse
After flashing CWM, you need to unlock the bootloader. You should be flashing a vrale6 bootloader zip OR using EZ Unlock v1.2 to unlock.
Sent from my SCH-I535 using Tapatalk 4 Beta
boot loader
if during start up and i see the word SAMSUNG WITH A LOCK THAT APPEARS UNLOCKED does that mean i have an unlocked bootloader?
puchodog1977 said:
if during start up and i see the word SAMSUNG WITH A LOCK THAT APPEARS UNLOCKED does that mean i have an unlocked bootloader?
Click to expand...
Click to collapse
That means your Bootloader is not Unlocked. Make sure you use ez unlock 1.2 when unlocking. You can verify it's unlocked when you turn on the phone, and you see the word Samsung flash for a split second.
Sent from my SCH-I535 using Tapatalk 2