So yesterday I got this Samsung Galaxy S III that was I535 but had a I9300 4.1.2 Firmware in it. (I don't know how was it there) It had been rooted. I don't know about the bootloader if it was locked or unlocked.
I wanted to install the official firmware for i535 so I used Odin to flash I535's official 4.4.2 (downloaded from sammobile.com) and it worked fine. I then used towelroot v3 apk to root the phone and it got rooted again, then I used safestrap 3.71 to install custom recovery and that too went well.
I then flashed a zip to get Motolora Cricles widget, although that didn't install properly but my phone was still working fine until then. Then I used EZUnlock14 to unlock my bootloader and the app supposedly decraled that my bootloader was "now" unlocked, again I couldn't confirm because that's when the problem starts.
After closing that app I plugged in my phone through usb cable to my laptop and had been using it for facebook and texting. Then I turned off my phone and it never turned on back again.
When I connect it to the PC now, it is not recognized and Device manager shows QHSUSB_DLOAD device
I hope somebody can help me with that.
well, ya dun messed it up. But its fixable. For future reference, never try a bootloader unlock app, thats what messed yours up. Those apps only work on 4.2.2 bootloader phones and have caused many a headache for lots of folks. Lemme grabe you a link quick.
here ya go. this will get it fixed for ya
http://forum.xda-developers.com/showthread.php?p=68239621#post68239621
Related
So, I've done this before, and I've never bricked a device until now.
I tried installing a custom rom for my Galaxy S3 on Verizon, but when I restarted, it says this:
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 can't get into clockwork, or any bootloader. Any attempt to do anything brings this screen up.
Now, I can get into the Odin downloader. (Power, volume down and home). But, I can't figure out how to get a Rom to load. This is where I am stuck. I have downloaded a few roms, all stock, but none of them want to be recognized. I have no idea where to go. I've been downloading stuff for 5 hrs and nothing has worked, so now Im going to the forumns. Any help is appreciated.
I have the Verizon i-535 Galaxy SIII.
You did not brick your phone you failed to unlock your bootloader. There are 2 guides in the android dev section for rooting.
http://forum.xda-developers.com/showthread.php?t=1974114
Odin back to stock and next time after rooting make sure to use EZUnlock 1.2 to unlock the bootloader BEFORE loading a ROM
Hi,
Just used chainfires rooting program for my galaxy note 2. Did everything correctly , odin and the phone showed everything done right.But after re- booting, something in phones security blocked the rooting. What can I do?
describe clearly
was ur boot loader unlocked? and was the phone carrier specific like u bought the phone from at&t,tmobile,verizon or sprint?
root blocked
[email protected] said:
was ur boot loader unlocked? and was the phone carrier specific like u bought the at&t,tmobile,verizon or sprint?
Click to expand...
Click to collapse
My phone is the AT&T version of the note 2. The root that I used was for this version. As for the boot loader, I'm not sure what you mean. I ran not the files through odin, just as described in the video.odin showed that everything was good. As did the phone until it re booted. Samsung is doing automatic Security updates now. And after the phone booted up, a message popped up from Samsung saying "an attempt to access a Secure area of your phone without authorization has been blocked."
My next step will be to install a custom rom. But I don't know if they will be able to block me from accomplishing this as well. This whole thing is really getting frustrating. It all started when I ran the update to 4.3 couple of weeks ago, and lost my tethering ability. This all I want. Just to get the free tethering app to work again. I had jelly bean 4.1.2. And the tethering app worked perfectly every time. Now with 4.3, doesn't work anymore. Do I need to downgrade back to 4.1.2? Or is their an easier solution? I'm wondering if it will matter what jelly bean you're using anymore if they're going to do auto security up dates that block all these type of things like custom rooms and rooting. Please tell me I'm wrong!
Thanks.
skoobiesnack said:
My phone is the AT&T version of the note 2. The root that I used was for this version. As for the boot loader, I'm not sure what you mean. I ran not the files through odin, just as described in the video.odin showed that everything was good. As did the phone until it re booted. Samsung is doing automatic Security updates now. And after the phone booted up, a message popped up from Samsung saying "an attempt to access a Secure area of your phone without authorization has been blocked."
My next step will be to install a custom rom. But I don't know if they will be able to block me from accomplishing this as well. This whole thing is really getting frustrating. It all started when I ran the update to 4.3 couple of weeks ago, and lost my tethering ability. This all I want. Just to get the free tethering app to work again. I had jelly bean 4.1.2. And the tethering app worked perfectly every time. Now with 4.3, doesn't work anymore. Do I need to downgrade back to 4.1.2? Or is their an easier solution? I'm wondering if it will matter what jelly bean you're using anymore if they're going to do auto security up dates that block all these type of things like custom rooms and rooting. Please tell me I'm wrong!
Thanks.
Click to expand...
Click to collapse
as of my knowledge ur bootloader was locked and KNOX was installe on ur mob through security updates and u might have to flash stockrom of specific model number search for flashing stock rom search for ur model number and carrier specific roms ask for it in the q&a thread for ur specific mobile you can ask for it <a href=http://forum.xda-developers.com/galaxy-note-2-att><here>
I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help." Then thats where i couldn't do anyting with my phone but go to download/ODIN MODE and rebooting system thing where you can reboot system. IM very new and i don't know much about rooting and the meanings of a lot of words like unlock bootloader. If i go to ODIN MODE it says
ODINE MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: Yes (1 Counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER RP SWREV:1
i think this doesn't look good. WHat should i do to make my phone be working again and not showing that black screen.
I already wiped all data and tried to do that StockROm thing on my computer ODIN and still nothing.
Is my bootloader locked? if so do i need to unlock it to make my phone work again? Thanks so much for your time
Same with mine I think it's called a bricked phone and think there is nothing we can do about it, hopefully someone has a solution
Might Work?
Remeax said:
I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help." Then thats where i couldn't do anyting with my phone but go to download/ODIN MODE and rebooting system thing where you can reboot system. IM very new and i don't know much about rooting and the meanings of a lot of words like unlock bootloader. If i go to ODIN MODE it says
ODINE MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: Yes (1 Counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER RP SWREV:1
i think this doesn't look good. WHat should i do to make my phone be working again and not showing that black screen.
I already wiped all data and tried to do that StockROm thing on my computer ODIN and still nothing.
Is my bootloader locked? if so do i need to unlock it to make my phone work again? Thanks so much for your time
Click to expand...
Click to collapse
I dunno if this will work for you. But I had the same message and when I booted in Download mode I just hit Cancel then rebooted and it worked?
If you flashed cyanogenmod, that means you're bootloader is unlocked, which is a good thing.
Can you get into CWM or TWRP? I don't have a samsung so i don't know about ODIN (i presume it's like flashtools for Xperia).
For as long as your phone vibrates (or does pretty much anything when you boot it up) your phone is not hardbricked, which is also good .
Try getting into CWM, shut down your phone completely, wait 5 seconds, then do: Volume Down + Home + Power key . This will get you into bootloader state and try reflashing your old backup, a stock rom or cyanogenmod.
First time with these softbricks is always the most fun ^^. Been there done that, i thought i spend 250 euro's on a phone that was broken .
Btw. Always make a backup for these kind of situations.
Remeax said:
I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help."...
Click to expand...
Click to collapse
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Ok how do i get it?
afextwin said:
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Click to expand...
Click to collapse
Ok so is do i do the same thing as i was trying to flash or something like grab a kies file( the ones that take 2+ hours to download) and then flash or get to factory reset with the 4.3 file? if so do you know where i can grab a 4.3 update file to restore? please help me if you have skype or PM me? thanks
afextwin said:
You took the 4.3 update. You must now Odin to stock 4.3 to unbrick, do not Odin to any other (previous) version. There is a safe root method.
I do not think there is custom recovery and bootloader is now permalocked.
http://forum.xda-developers.com/showthread.php?t=2270191 has a link to the odin file and the root method in post 2 or 3 i believe.
Click to expand...
Click to collapse
I just recently ODIN flashed the latest 4.3 stock firmware for my TMO GS3 and then attempted to roll back to 4.1.2. It didn't brick my device, but it didn't work either. I would simply fail to install. I was able to reflash, through ODIN, the 4.3 stock firmware (actually used the root66 version). Then I was able to ODIN flash CWM recovery and install Dandroid 5.1, which is also a 4.3 based ROM. All is well now. I guess I simply can't go back to any previous 4.3 ROMs now, and I'm not sure about any AOSP ROMs. I may give a try at some point to see.
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
scottrf8 said:
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
Click to expand...
Click to collapse
I don't have a Note (I have the GS3 on TMO). Do you have any idea if the Note 2 has the same issue that the GS3 has, where with the 4.3 update you get a new locked bootloader that prevents you from going back to anything earlier than 4.3? That's the way it is on the GS3. I guess if you were able to actually boot up and make calls after you downgraded back to 4.1.1, then that must not be the case.
In any case, you're getting stuck on the boot logo when you power it on? Can you get into the recovery at all? Do you have the stock recovery or a custom recovery installed? Have you tried clearing cache/dalvik and fixing perms? That often fixes things for me when I'm stuck on the boot logo.
scottrf8 said:
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
Click to expand...
Click to collapse
I start to wonder if people research before doing anything.
To say again. You can't downgrade. You have Knox. You possibly tripped the Knox flag. Reflash the 4.3 stock ROM. If that fails, It's most probably eFuse, if It's 4.3.
(Basically, eFuse messes up your phone aka bricks You phone aka @#%& it up.)
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
---------- Post added 5th January 2014 at 12:05 AM ---------- Previous post was 4th January 2014 at 11:59 PM ----------
mcgrabowski said:
I don't have a Note (I have the GS3 on TMO). Do you have any idea if the Note 2 has the same issue that the GS3 has, where with the 4.3 update you get a new locked bootloader that prevents you from going back to anything earlier than 4.3? That's the way it is on the GS3. I guess if you were able to actually boot up and make calls after you downgraded back to 4.1.1, then that must not be the case.
In any case, you're getting stuck on the boot logo when you power it on? Can you get into the recovery at all? Do you have the stock recovery or a custom recovery installed? Have you tried clearing cache/dalvik and fixing perms? That often fixes things for me when I'm stuck on the boot logo.
Click to expand...
Click to collapse
You're right. The locked bootloader messed those who didn't research about it's life's real bad. 4.3 supposedly has eFuse in it, which FU*CKS your phone. I read it up on the Samsung Knox website, and it said that eFuse "rewrites a read-only part of the phone, resulting in a unusable phone." If u triggered that, it'll be a hard brick, (in my knowledge)
Knox itself is irritating. The Knox Warranty Void counter, which max at 1, is unresetable, (even with JTAG, will brick if h try) so your warranty is *poof*
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
I did a fair amount of research before downgrading. In fact I didn't want to downgrade, but I did want to unlock it. It is unlocked and it's running on 4.1.1. So when you say that you can't downgrade, you mean you shouldn't downgrade cause then you will be stuck with 4.1.1?
scottrf8 said:
I did a fair amount of research before downgrading. In fact I didn't want to downgrade, but I did want to unlock it. It is unlocked and it's running on 4.1.1. So when you say that you can't downgrade, you mean you shouldn't downgrade cause then you will be stuck with 4.1.1?
Click to expand...
Click to collapse
When you were on 4.3, was that an OTA update or an ODIN flash of a stock firmware? Or did you just have a 4.3 ROM from the forums that you loaded (AOSP or rooted stock based ROM with Knox, etc., removed) with TWRP or CWM? Supposedly from what I've been reading if you take the 4.3 OTA or ODIN flash the stock 4.3, the bootloader gets updated, as Irwenzhao mentions above and I've experienced, where you CAN'T downgrade again to 4.1.2 or earlier. I believe that just means you can't go back to a fully stock pre 4.3. I THINK it just means you can't ODIN back to a factory image earlier than 4.3, which is what I experienced. But with TWRP or CWM, I believe I can still load other ROMs at will regardless if they are pre 4.3 or not.
yeah, that sounds kinda like the same thing I have come across. 4.3 was OTA and downgraded to a stock 4.1.1 ROM. Guess this triggers KNOX cause now KNOX WARRANTY VOID is 1. which once that is triggered, you cannot go from a non KNOX version (4.1.1) to a version that has KNOX. My question now is does that apply to just the stock firmware? Would ANY of the ROM's created by the devs work?
There were some posts in the unlock thread that people were able to go from 4.1.1 (after downgrading) back up to 4.3. Just trying to figure out how that would be the case? Could the knox warranty flag not have been set for them?
scottrf8 said:
yeah, that sounds kinda like the same thing I have come across. 4.3 was OTA and downgraded to a stock 4.1.1 ROM. Guess this triggers KNOX cause now KNOX WARRANTY VOID is 1. which once that is triggered, you cannot go from a non KNOX version (4.1.1) to a version that has KNOX. My question now is does that apply to just the stock firmware? Would ANY of the ROM's created by the devs work?
There were some posts in the unlock thread that people were able to go from 4.1.1 (after downgrading) back up to 4.3. Just trying to figure out how that would be the case? Could the knox warranty flag not have been set for them?
Click to expand...
Click to collapse
Just to make it clear, Knox is a bootloader, which means u can flash anything that's not a bootloader, but your warranty would be history. Flashing anything trips the flag, even 4.1.1/2 stock ROMs.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
Truthfully, that doesn't clear it up. Do the stock firmware through Kies or ota include a bootloader and that's why it won't install? Thanks
Flashing the stock firmware through kies, ODIN, or the OTA update will update the boot loader as far as I know and will ruin any chance of returning to stock and void your warranty. As long as you don't want to do that, I don't think it's too big of a deal.
At this point, I couldn't care less about the warranty. I would think it's expired now anyhow. As long as I can flash ROMs and boy the phone up and use it. I'm happy.
Sent from my SGH-T999 using xda app-developers app
Well, this is my story. I tried to revive my old Verizon SIII because I really like that model. The problem is I never noticed the 4.4 bootloader lock. I rooted my device after a factory reset, I tried to install the cyanogenmod but at the start the custon recovery wont trigger despite installing the adequate app, first I believed KNOX was the issue so I proceeded to unistall it with TitanimBackup, that made the "custom" Samsung boot screen appear but then a "Unauthorized sofware blah blah blah" message from Verizon appeared so I used download mode to reboot sucessfully, then I remembered that the bootloader wasnt unlocked so I proceeded to unlocked with EZunlocker and the unlock was successful, when the TWRP manager app asked me to reboot to install the custom recovery it never did, just bricked. My questions are, my phone was already running a form of custom rom for region-free SIM card operation, as far I know the device was NOT on 4.4 since it wasn't even on the US anymore and Verizon update services don't operate here, as I remember my sytem version was 4.0.4 why did it bricked? if I buy another device what I must check to avoid another bricking? Is there any way to recover my device? it is a hard brick, noob here.