Can someone point me in the right direction?
I updated the S3 Bootloader Unlocker and for some stupid reason i decided that i wanted to relock and unlock the bootloader.
I relocked it to find out that it didnt give me the option to unlock again.
Then i proceeded to reboot the phone and low and behold, The verizon screen of death popped up.
The screen im talking about is the one that says:
"System software not autorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
Is there a way to reflash the bootloader? Odin perhaps?
I just need a little guidance on getting me in the right path. Thanks all!
If you can boot to download mode still, you can Odin back. That's the great thing about Odin, doesn't matter what state your phone is in as long as you can get to download mode, it'll take care of the rest.
Vol Down + home key + power - do this while booting.
I assume you did what several of us did and used the ez-unlock tool? The update for that app actually is broken temporarily, mmeff said he's gonna fix it later tonight. Here is an old v1.2 I managed to find that works flawlessly.
http://dl.dropbox.com/u/42057363/com.mmmeff.ez.unlock_3.apk
I did a few more searches. I found the soft brick fix page. I just reflashed everything.. But everything is lost......
Im gonna shoot myself.. Had tons of pictures from my daughters first birthday on there.. ALL GONE!!
Didnt think it would flash the internal storage.. FML
Actually it sounds like what he did was re lock his bootloader with a custom kernel on the phone. Because the update broke the unlocking part of the app his bootloader stayed locked and with a custom kernel on the device the subsequent reboot caused it to fail Verizon's signature check.
OP: Use the stock root66 Odin file in the stickies to restore stock.
iSpyder said:
I did a few more searches. I found the soft brick fix page. I just reflashed everything.. But everything is lost......
Im gonna shoot myself.. Had tons of pictures from my daughters first birthday on there.. ALL GONE!!
Didnt think it would flash the internal storage.. FML
Click to expand...
Click to collapse
I'm pretty sure that step 8 in that guide is what erased your internal sd card. That's where it says "Nand Erase All." That's tough that you lost all your pics.
JBO1018 said:
Actually it sounds like what he did was re lock his bootloader with a custom kernel on the phone. Because the update broke the unlocking part of the app his bootloader stayed locked and with a custom kernel on the device the subsequent reboot caused it to fail Verizon's signature check.
OP: Use the stock root66 Odin file in the stickies to restore stock.
Click to expand...
Click to collapse
This is what i did. I have lost all data that was on there. I even lost the CWM backups that were saved the the internal storage. So i couldnt flash back to any of those. Starting from square one.. and it sucks.
Edit:I found an old back up on my desktop. Flashed it and it was going really slow. I downloaded a rom, and flashed that. Then it took me right back to the VERIZON screen saying there was unauthorized software again.. What am i doing wrong? The bootloader app says the boot loader is unlocked.. maybe ill try the APK file from this thread instead of the market.
iSpyder said:
This is what i did. I have lost all data that was on there. I even lost the CWM backups that were saved the the internal storage. So i couldnt flash back to any of those. Starting from square one.. and it sucks.
Edit:I found an old back up on my desktop. Flashed it and it was going really slow. I downloaded a rom, and flashed that. Then it took me right back to the VERIZON screen saying there was unauthorized software again.. What am i doing wrong? The bootloader app says the boot loader is unlocked.. maybe ill try the APK file from this thread instead of the market.
Click to expand...
Click to collapse
Yea, unless EZ Unlock was updated again today you need to use EZ Unlock 1.2 to properly unlock.
SlimSnoopOS said:
Yea, unless EZ Unlock was updated again today you need to use EZ Unlock 1.2 to properly unlock.
Click to expand...
Click to collapse
I think that was the problem. The app updated and is thinking that the boot loader was still unlocked so i couldnt unlock it again even after odin.
I just reflashed stock rooted with odin. downloaded unlock apk and rom manager. making back up of stock rooted. looks like it booted back to home screen! TIME TO ROM IT UP AGAIN!
EDIT:
TechSavvy2 said:
If you can boot to download mode still, you can Odin back. That's the great thing about Odin, doesn't matter what state your phone is in as long as you can get to download mode, it'll take care of the rest.
Vol Down + home key + power - do this while booting.
I assume you did what several of us did and used the ez-unlock tool? The update for that app actually is broken temporarily, mmeff said he's gonna fix it later tonight. Here is an old v1.2 I managed to find that works flawlessly.
http://dl.dropbox.com/u/42057363/com.mmmeff.ez.unlock_3.apk
Click to expand...
Click to collapse
I LOVE YOU FOR PROVIDING THAT APK!!
Thank you
TechSavvy2 said:
If you can boot to download mode still, you can Odin back. That's the great thing about Odin, doesn't matter what state your phone is in as long as you can get to download mode, it'll take care of the rest.
Vol Down + home key + power - do this while booting.
I assume you did what several of us did and used the ez-unlock tool? The update for that app actually is broken temporarily, mmeff said he's gonna fix it later tonight. Here is an old v1.2 I managed to find that works flawlessly.
apk
Click to expand...
Click to collapse
Thank you so much for that apk.
Its been updated to 1.4. I dont know if i want to do even that one until the bugs are taken care of.
Thanks again to everyone that helped me get my phone back up and running.
I got my rom flashed. Apps installed. All is good in this world again. minus the losing pictures and stuff.
I upgraded to 1.4 before seeing this. Do I just uninstall EZunlocker completely and then flash 1.2?
this time back up your pics to the cloud!
im late to this thread but there is a guide in the development section that would of saved you alot of hassle as all your issues are explained there...hmmm I wonder who wrote that?
This was a really useful thread. Learned a lot, prompted me to check my backups and moments after reading the thread, I got an EZ-Lock update pushed to my phone (v. 1.4). Is this the one that addresses the bug?
iSpyder said:
I did a few more searches. I found the soft brick fix page. I just reflashed everything.. But everything is lost......
Im gonna shoot myself.. Had tons of pictures from my daughters first birthday on there.. ALL GONE!!
Didnt think it would flash the internal storage.. FML
Click to expand...
Click to collapse
I suggest you to download dropbox and activate the auto upload of pictures and video ( it should be active by default...) you can pick between upload only over WiFi to save your data plan or both WiFi and mobile.
It saved me and my pics many times..
Sent from my SCH-I535 using xda premium
iSpyder said:
Its been updated to 1.4. I dont know if i want to do even that one until the bugs are taken care of.
Thanks again to everyone that helped me get my phone back up and running.
I got my rom flashed. Apps installed. All is good in this world again. minus the losing pictures and stuff.
Click to expand...
Click to collapse
What the heck is he even updating in the ez unlock app? All it does is copy aboot.
piiman said:
What the heck is he even updating in the ez unlock app? All it does is copy aboot.
Click to expand...
Click to collapse
He has a changelog...
v1.4
hotfix for last issue. Bootloader checking is disabled for the time being, so all you will see is UNKNOWN for the status. Fret not, as unlocking and relocking are still working. Sorry about all this, will rectify ASAP. I recommend using 1.2 from the Rootzwiki linked thread in the description.
v1.3
Use SHA-1 to check bootloader status (much more reliable)
removed sound
Bad hash value....???? Help pls?
Hey guys,
Im new, but I am stuck. I am a victim of this as well. I am trying to use the instructions in the [HOW-TO] Unbrick your soft bricked Galaxy S III thread but Odin says that the VRALF bootchain file has a bad MD5 Hash value. The original link is bad, the file does not download. I was able to download from the mirror and the MD5 for that file does match the download, but for some reason Odin doesnt like it....
Im stuck. Can someone send me a file they have used? I just got this phone today....
Any help would be VERY appreciated.
Firstsage said:
Hey guys,
Im new, but I am stuck. I am a victim of this as well. I am trying to use the instructions in the [HOW-TO] Unbrick your soft bricked Galaxy S III thread but Odin says that the VRALF bootchain file has a bad MD5 Hash value. The original link is bad, the file does not download. I was able to download from the mirror and the MD5 for that file does match the download, but for some reason Odin doesnt like it....
Im stuck. Can someone send me a file they have used? I just got this phone today....
Any help would be VERY appreciated.
Click to expand...
Click to collapse
Whats the error that Odin is giving you?
apacseven said:
Whats the error that Odin is giving you?
Click to expand...
Click to collapse
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2- (2).md5 is invalid.
<OSM> End...
Related
So, this happened recently, and I fixed it. Link: http://forum.xda-developers.com/showthread.php?t=1735119
Well, outta no where, same basic issue, but with a twist.
This afternoon while I was asleep my GTab rebooted. It came back to the "Samsung Galaxy Tab 7.0 Plus" splash screen and is stuck. I *can* get into download mode, and I can almost get into recovery. When I try to go into recovery, it loads what looks like it will be recovery, then says:
# Manual Mode #
-- Updating Application
Then a minute or so later it reboots right back to the GT7+ splash screen and stays there...
Twist:
So, knowing what I did last time, I installed Odin and the Samsung drivers on my POS computer at home, booted into Download Mode, and did the "PDA" option with the correct FW (same as I used last time for the T869 from SamMobile, I saved all the files). It runs through just fine, gets to the end and the Tab reboots. It then goes into recovery and and does a few things (I believe it said it was deleting the cache and a few other processes). Then, lastly, it again says:
"# Manual Mode #
-- Updating Application
... followed by a reboot, and back to hanging on the boot logo.
Any ideas?!? Ironically, I put it on CL today to see if I can sell it for enough to cover a Nexus7. I woke up to an offer, and a bricked Tab. Figures.
Any thoughts/help are greatly appreciated. The sooner the better. lol
Is it possible that I need to flash a good recovery in Odin? If so, what's the procedure. and can someone link me to the one I would need for the US TMobile 4G version of the GT7+?
Also, since flashing the stock FW isn't fixing anything, and it seems like a possible Recovery issue, a friend at work is suggesting I choose the option in Odin to delete the partitions.
Thoughts??? (quickly)
Damn dude, again?
I think there is 3 or 4 threads about this on this forum and same amount on 7.7 forum. None come to a cause our solution, seems like people repeats some procedures and out of nothing it works again.
When it happened to me a let its battery drain fully to the point it won't turn on anymore let it this way for some time. Then fully charged, this is a little harmful to your bat, for the record. Then try to turn on, it will take some time but eventually it could enter on the system.
I think the data partition got corrupted.
Sent from my GT-P6210 using Tapatalk 2
Yup.
So, I tried the option in Odin to re0make the partition, and every time I try it fails with an error of "Can't Open Package" (or something along those lines).
I have reinstalled the FW through Odin no less than 10 times, nogo. The first time I open recovery after flashing, It says it is installing a package, clearing cache, etc, and the last line always says "-- Updating Application". After 10-15 seconds, that goes away and it reboots only to hang on the GT7Plus splash screen again. Then, any time I go into recovery after that first post-Odin instance, if says:
"# Manual Mode #
-- Updating Application
Should I be trying to reinstall Recovery? If so, what do I use (link)? Also, how do I do that in Odin...
I believe that for use remake partition you have to provide the pit file if your stock does not have it.
Anyway I did that also about 3 times, providing the pit and the md5, they flashed ok, but the problem was the same. Did you tried the battery thing? Some guy give a tip to start with the usb plugged.
Sent from my MB525 using Tapatalk 2
leodfs said:
I believe that for use remake partition you have to provide the pit file if your stock does not have it.
Anyway I did that also about 3 times, providing the pit and the md5, they flashed ok, but the problem was the same. Did you tried the battery thing? Some guy give a tip to start with the usb plugged.
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
Where was that tip? Link?
Also, any one have that .pit file I can try with?
http://forum.xda-developers.com/showthread.php?p=28574760
Sent from my MB525 using Tapatalk 2
Hey buddy..
Which fw u using? T869 came shipped with 2 different, search for both of them and try each one...don't use repartition without the correct pit file...
Maybe not here but I google sgh-t869 factory and found a website with both tar
Sent from my Galaxy Nexus using xda app-developers app
statuzz said:
Hey buddy..
Which fw u using? T869 came shipped with 2 different, search for both of them and try each one...don't use repartition without the correct pit file...
Maybe not here but I google sgh-t869 factory and found a website with both tar
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm not sure which file it is that I'm using, I'll have to look at home in a couple of hours. This happened to me a few weeks ago (link in original post), and I flashed this FW with Odin and it recovered, and has been fine since (till now), so I know it's at least a usable FW. I'll try to find the other one today.
I just tried finding the stock pit file for the TMo SGH-T869, but I can't find it. Anyone have a link to it by chance? Also, once I get it, what do I do (options to choose) in Odin to flash it?... and do I do it at the same time as the FW?
Thanks for any help! I was really hoping to sell it in the next day or two to fund the Nexus7, so now I'm really frustrated.
ETA: Also, I let it completely die, to the point it wouldn't boot. Then charged it for a bit and booted. Same issue.
I think that if u find the pit file they should be flash at the same time...fw in pda and pit in phone...(this need to be check to confirm) after flashing.. reboot into factory recovery wipe everything and try to boot
Hopefully u fix that today
Sent from my Galaxy Nexus
When it happened to me, i flashed the pit first and at the same with stock with re partition checked, didnt help. I did everything that I could find and I feel like it only worked again by itself
You can look every single thread of this exact problem, the ones that got it back working can't really say how, they flash everything many times and it suddenly works.
The good things are that flash the stock ones don't increase you flash count, and as long as you can enter download mode you are not really s#%
Sent from my MB525 using Tapatalk 2
Thanks for the help...
Anyone have a link to the .pit for this model (T869)?
Also, I had a thought. When I go into Recovery, I get the following and then it reboots again:
# Manual Mode #
-- Updating Application
1. Is it possible that recovery is hosed, and overwriting it with a fresh version will allow me to wipe the device, set to factory and then boot? Maybe this is the issue?
2. Is it even possible to just flash a fresh copy of the recovery over whatever is there (or replace it)?
2.a. If it is possible, what file should I use, and do I do it though Odin? Anyone have a link to what I should use?
Thanks :good:
VisualOddity said:
Thanks for the help...
Anyone have a link to the .pit for this model (T869)?
Also, I had a thought. When I go into Recovery, I get the following and then it reboots again:
# Manual Mode #
-- Updating Application
1. Is it possible that recovery is hosed, and overwriting it with a fresh version will allow me to wipe the device, set to factory and then boot? Maybe this is the issue?
2. Is it even possible to just flash a fresh copy of the recovery over whatever is there (or replace it)?
2.a. If it is possible, what file should I use, and do I do it though Odin? Anyone have a link to what I should use?
Thanks :good:
Click to expand...
Click to collapse
The problem is that there's is not development for t869 so there's not much to look for...just factory images and root method
Sent from my Galaxy Nexus
Can anyone link me to the proper pit file? Also, in the linked thread a few posts back, there are a couple of files, will those work for this?
Can someone post the proper pit file for me so I can repartition? I'm doing this on my wife's phone because my internet at home is down till tomorrow...
Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad?
VisualOddity said:
Can anyone link me to the proper pit file? Also, in the linked thread a few posts back, there are a couple of files, will those work for this?
Can someone post the proper pit file for me so I can repartition? I'm doing this on my wife's phone because my internet at home is down till tomorrow...
Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad?
Click to expand...
Click to collapse
i think u should forget about the pit file, couz the firmware have the pit repackage with the tar, im gussing u will only need the pit file in case u want to change the phone partitions, try to get those 2 fw and try them :good:
That's why I'd like the pit file, so I can check the option in Odin to re-partition.
So, I have internet at home now. I have now tried again letting it completely die, then completely charge, same issue. I have also tried 2 different versions of the SGH-T869 firmware.
Any thoughts?
Also, given what I have done so far, I posted this yesterday, any thoughts?
"Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad? "
Yes. Unplug is bad. Possibly fatal. you should be able to.find a stock recovery.img in a stock Odin.tar, flash it with heimdall. Recommend factory reset beforeand after doing so.
I dont know about tmobile tabs but international ones look to apply CSC files after displaying that manual mode message. Perhaps something has gone awry with a CSC,etc.
chrisrotolo said:
Yes. Unplug is bad. Possibly fatal. you should be able to.find a stock recovery.img in a stock Odin.tar, flash it with heimdall. Recommend factory reset beforeand after doing so.
I dont know about tmobile tabs but international ones look to apply CSC files after displaying that manual mode message. Perhaps something has gone awry with a CSC,etc.
Click to expand...
Click to collapse
Thank You. A few questions:
Would that stock recovery.img have to be model specific. i.e. for the SGH-T869, or could it be from any GT 7 Plus (or is it generic on all devices with HoneyComb)? I *think* from experience it has to be T869 specific, but it's worth asking.
Also, about Heimdall, where do I get that, and how do I use it to flash? I've heard of it, but never used it.
Lastly, about the CSC files. That makes sense seeing as what it's doing, so that *could* be the whole issue. How can I overcome that? Can I download and flash those files somehow? Do you have a link to them?
Thanks for the help everyone. I'm hoping that in doing all this, maybe whatever ends up fixing this will be a guide for everyone else having the issue...
OK, I saw a couple of you guys mention the 7.7 people having this issue, so I went there to research. If I am reading right, it *sounds* like this could be a solid mix of a data system being corrupted, and the stock recovery (Samsung e3?) being bad.
Someone mentioned that you can pull the stock recovery.img from a the firmware, make a .tar with only that, then flash that. Once that's done you can do a full wipe in recovery, flash the full FW, and hopefully be back in business.
I want to try this, and if it works, maybe we will have a proven solution for the people getting this issue. However, not only have I never created a .tar, I have especially never created a flashable .tar, so...
What do I do? Other than pulling the recovery.img from the FW, how do I do this?
So long story short, my tab was running stock ICS (rooted, with temp CWM/cwm.zip). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Do I have the Brick Bug?
rumpypumpy said:
So long story short, my tab was running stock ICS (rooted, with temp CWM). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Click to expand...
Click to collapse
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers
gmaster1 said:
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers
Click to expand...
Click to collapse
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...
rumpypumpy said:
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...
Click to expand...
Click to collapse
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers
gmaster1 said:
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers
Click to expand...
Click to collapse
I forgot about download mode. I'll have a go then I'll report back.
Thanks
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866
rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
If cwm works then we both know theres hope
Sent from the phone of Gamers
lsherif said:
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866
Click to expand...
Click to collapse
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually
rumpypumpy said:
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually
Click to expand...
Click to collapse
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers
gmaster1 said:
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers
Click to expand...
Click to collapse
:crying:
I was reading the following articles:
http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
http://forum.xda-developers.com/showthread.php?t=1810954
Could this Brick Bug be the source of my problems?
I was running a leaked version of ICS AND I have been using the cwm.zip so there is the possibility
Being unable to flash through either Odin or CWM surely sounds a lot like the brickbug.
If I were you, I'd reboot to download mode, and install a full ROM with repartition + PIT file. If it works, install locerra's CWM (it's one of the few recoveries for our tablet that's confirmed to be brickbug-free), and work as usual. But remember to wipe everything before installing anything through CWM...
If Odin doesn't work, you probably have been hit by the brickbug. However, all is not lost: this guy seems to have found a "fix" for many devices. It involves giving up on all your data and making your onboard storage a couple of GB smaller than it used to be, but it can make your device work again. Read the thread, try to understand it, and (if you can't find another way out) use the PIT file for the GT-6800 provided. If your tab isn't the international WiFi+3G GT-P6800, you may have to ask the guy (hg42) for a PIT tailored to your device.
The other option, in the case of a eMMC-related brick, is to remove all traces of CWM, go to a Samsung store and repair it under warranty, saying "its broke down when I were running that backie upppe thing in kies".
The other option is the better one, as i bricked my note. When i am able to revive it, i am left with 8GB space and it seems real laggy. Change a new motherboard would be better if still cover undr warrantly.
Sent from my GT-P6800 using xda premium
Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks
rumpypumpy said:
Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks
Click to expand...
Click to collapse
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.
Steve_max said:
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.
Click to expand...
Click to collapse
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Thats...a...problem...if it takes longer then 15 mins its bricked...i have been a gt user and devs on other sites told me it was bricked. Maybe there is a solution but...i havnt found one. It should never take too long on one thing in odin.
Sent from the phone of Gamers
rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.
Steve_max said:
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.
Click to expand...
Click to collapse
The warrenty is not void unless they find proof of tampering with system files. So basicly yeah...everything that guy said. Get it as close to stock as possible and send.
Sent from the phone of Gamers
Right OK, I definately don't want my warrenty void!
So would it be ok if I flashed 'P6800OXALQ1_P6800XXLQ1_HOME.tar.md5' (minus the factoryfs.img) to my tab?
Thanks
Hi all , just joined xda-developers but i spend straight 14 hours trying to fix this DAMM photon q yesterday
all i got in the end is a normal boot after following this http://forum.xda-developers.com/showthread.php?t=2001108
BUT at the startup , the screen comes like for a millisecond and then this " starting services" logo doesn't go at all...it just continues forever
any help would be appreciate .
Can you explain what your setup is, and exactly what you've done to get where you are?
For example, you were bootloader official unlocked, on CWM and asa-10, etc.
Thanks.
arrrghhh said:
Can you explain what your setup is, and exactly what you've done to get where you are?
For example, you were bootloader official unlocked, on CWM and asa-10, etc.
Thanks.
Click to expand...
Click to collapse
bootloader is not qaulified for official unlock... and its my friends phone so he gave to me since he was unable to use it.. i thought i could give it life again.. so...i don't what esle info you want but i did EXACTLY what that thread told me to do... and still the that thing does not go ..
tune345 said:
bootloader is not qaulified for official unlock... and its my friends phone so he gave to me since he was unable to use it.. i thought i could give it life again.. so...i don't what esle info you want but i did EXACTLY what that thread told me to do... and still the that thing does not go ..
Click to expand...
Click to collapse
Still doesn't tell me what you've done, what state the phone is actually in, etc.
I thought my question was pretty straightforward. Unless you provide more detail, I don't know how anyone will be able to help you.
Is this a stolen device? Why is it not qualified for the official unlock? Either way, how does that play into what's wrong with the device?
Did you have custom recovery on it? Give some details!!!
arrrghhh said:
Still doesn't tell me what you've done, what state the phone is actually in, etc.
I thought my question was pretty straightforward. Unless you provide more detail, I don't know how anyone will be able to help you.
Is this a stolen device? Why is it not qualified for the official unlock? Either way, how does that play into what's wrong with the device?
Did you have custom recovery on it? Give some details!!!
Click to expand...
Click to collapse
i think i am a noob at explaining things but let me try again...i don't know the exact history of this phone , my friend gave it to me yesterday and its not stolen ... he paid his insurance every month but then who know what he did... i have no idea why its not qaulified for the official unlock probably because he bought a new phone on the same line so the company deactivated this phone..
ok so when i got the phone yesterday , the bootlocker logo appeared and i was unable to do anything ...then i installed CWMrecovery and it was successfull and then i installed every possible rom available online as far as i know but same thing happened with all of them ..... successfully installed , it reboots and little square thing saying " starting services..." and then it does not go away at all ... but at the same time i am able to bring the top menu ..and go to the settings and everything from there but i can't go to home screen since ...it is black and is occupied by "starting services.."
so finally i came accross this thread for master reboot and i followed it ....i installed TWRrecovery and made backup and then restored a backup providers by that guy ... i flashed new stock recovery after that... so following his thread , he told that if all went successful ... it will return to original stock
and now i am at the same screen as previous... " starting serivces..." my friend told me he tired to root it and he messed up really bad ..so i believe there is still some old files in the internal storage from previous rom versions.... but i deleted everything......wiped, data facotry reset and then
installed a clean backup provided by the thread starter...... and everyone else had success except me ...
i hope i answered your questions if not .. i would aprreciate if you tell me what exactly you want to know ..... thanks
i also tired every US ROMS from here http://sbf.droid-developers.org/asanti_c/list.php
and all of them showed " starting services.." after i installed them from sdcard using CWMrecovery.
we have full RSD lite backups now to restore a phone can be found in this thread
http://forum.xda-developers.com/showthread.php?t=2095536 i think some xml editing is required tho but it explained it in the thread. that will erase everything on the phone and restore it to complete stock minus unlocked bootloader
Rangerbry said:
we have full RSD lite backups now to restore a phone can be found in this thread
http://forum.xda-developers.com/showthread.php?t=2095536 i think some xml editing is required tho but it explained it in the thread. that will erase everything on the phone and restore it to complete stock minus unlocked bootloader
Click to expand...
Click to collapse
i tried that but m getting confused which commands to delete and how to delete them........because its in the zip
tune345 said:
i tried that but m getting confused which commands to delete and how to delete them........because its in the zip
Click to expand...
Click to collapse
You have to extract the files and edit the xml file. And you use rsdlite on your pc phone connected thru usb to write it to the phone
Sent from my GT-N8013 using Tapatalk HD
Rangerbry said:
You have to extract the files and edit the xml file. And you use rsdlite on your pc phone connected thru usb to write it to the phone
Sent from my GT-N8013 using Tapatalk HD
Click to expand...
Click to collapse
ok i will do it right now...give me 1 minute
Woooooooooooooooooooooooooooooooo ..... DUDE YOU SAVED ME FROM GOING INSANE lol ....thanks
its working now ... i did that yesterday but my dumbass was choosing the whole zip file without extraction haha...
but the questing is which is the lastest update for it ??
If you installed the asa-14 then it should be. Make sure you flash the right one dont flash the us cellular unless thats what you have
Sent from my GT-N8013 using Tapatalk HD
Rangerbry said:
If you installed the asa-14 then it should be. Make sure you flash the right one dont flash the us cellular unless thats what you have
Sent from my GT-N8013 using Tapatalk HD
Click to expand...
Click to collapse
asanti_c-user-4.0.4-7.7.1Q-6_SPR-125_ASA-10-11-release-keys-Sprint-US.xml
i installed that one... can i make over the air update on it ... and is this like stock rom ... everything will work ..hdmi ..wifi ??
tune345 said:
asanti_c-user-4.0.4-7.7.1Q-6_SPR-125_ASA-10-11-release-keys-Sprint-US.xml
i installed that one... can i make over the air update on it ... and is this like stock rom ... everything will work ..hdmi ..wifi ??
Click to expand...
Click to collapse
You should be able to and everything should function its a complete stock just as sprint flashed it
Sent from my GT-N8013 using Tapatalk HD
is there any other way around for bootlocker ...without official ??
Thank you so much Rangerbry.........
If you Flashed CWM and TWRP your bootloader is already unlocked
Rangerbry said:
If you Flashed CWM and TWRP your bootloader is already unlocked
Click to expand...
Click to collapse
This.
Glad you got it workin with RSD lite.
Alright thank you .....all of you guys..
I meant to say remove the boot locker screen at startup ....
Another question is can i reactivate in sprint ?
tune345 said:
Alright thank you .....all of you guys..
I meant to say remove the boot locker screen at startup ....
Another question is can i reactivate in sprint ?
Click to expand...
Click to collapse
For bootlogos: http://forum.xda-developers.com/showthread.php?t=1873834
Reactivate in Sprint? What do you mean? Only Sprint can tell you whether the phone can be activated or not. Call them. Not sure why you would even worry about that if it's not stolen.....
Ok I think I will go in store and see what happens...
Ok I have this anither problem now....batteryy life is very short..I charged in the morning and after straight 3 hours.of use its out ..from 96 ,%
M looking into market ...can someone throw some light on battery calibration ...mine phone is not rooted
Sent from my XT897 using xda app-developers app
I was attempting to root and unlock my S3 tonight, I flashed the VRALEC.bootchain.tar.md5 and odin said it was done and had the reset! pop up. I shut down odin and waited for my phone to restart. It did not. Now i sit here with my S3 that will not turn on, the screen does not light, the led does not glow and i cant get it to enter odin/download mode or recovery. All i did was the first step and it broke. I've had this phone for 2 days please help me fix this...
TechieMonkey said:
I was attempting to root and unlock my S3 tonight, I flashed the VRALEC.bootchain.tar.md5 and odin said it was done and had the reset! pop up. I shut down odin and waited for my phone to restart. It did not. Now i sit here with my S3 that will not turn on, the screen does not light, the led does not glow and i cant get it to enter odin/download mode or recovery. All i did was the first step and it broke. I've had this phone for 2 days please help me fix this...
Click to expand...
Click to collapse
When you flashed in odin, did you use pda? If not there's your fisrt mistake.
Please read forum rules
Questions and help issues go in Q&A
Thread moved!
Sorry i panicked and wrote this in the first forum i could find lol
but yes i used pda, i had Auto Reboot and F. Reset Time checked as well
It doesnt turn on, no led, and it will not vibrate as i hold the power button (or any combo with the power button) to say its turning on and i just cant see anything either. Im literally getting no response from the phone.
TechieMonkey said:
Sorry i panicked and wrote this in the first forum i could find lol
but yes i used pda, i had Auto Reboot and F. Reset Time checked as well
It doesnt turn on, no led, and it will not vibrate as i hold the power button (or any combo with the power button) to say its turning on and i just cant see anything either. Im literally getting no response from the phone.
Click to expand...
Click to collapse
This is a Verizon GS3? Hard bricks are fairly rare but the usual cause of hard bricks is wrong firmware (international gs3 vs. US) or an interrupted process. From what you typed, it seems like you did everything right. Shouldn't be a corrupt file either if the md5 checked out
yeah its a verizon s3, i followed the instructions to a T and im freaking out that i cant get it to even vibrate or hit recovery mode. i'd love to just reset it and try again with the root... i dont really care about anything on it, its practically new and there isnt really much on it anyways. so deleting stuff isnt an issue
Have you tried pulling the battery? I just ran though the whole process without a hitch.
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
TechieMonkey said:
I was attempting to root and unlock my S3 tonight, I flashed the VRALEC.bootchain.tar.md5 and odin said it was done and had the reset! pop up. I shut down odin and waited for my phone to restart. It did not. Now i sit here with my S3 that will not turn on, the screen does not light, the led does not glow and i cant get it to enter odin/download mode or recovery. All i did was the first step and it broke. I've had this phone for 2 days please help me fix this...
Click to expand...
Click to collapse
The file should be VRALEC.bootchain.tar.tar you didn't extract it did you? See in the quote in red.
the guide that i used gave me that kind of file, all i did was download and install it the way that they told me... this is the link that i used...
http://droidviews.com/2013/root-and...erizon-galaxy-s3-sch-i535-android-4-1-14-1-2/
idk if im allowed to post a link to a different site, if not im sorry for that >.<
Try this..... http://forum.xda-developers.com/showthread.php?t=1840030
so i've been doing more digging... i think im hard bricked... is there an easy way to fix this (and cheap?) i cant afford to do the mobiletech site as im in college and havent been getting more than 5 hours a week for a long time... I'm really panicking, my dad was giving me crap about not rooting/unlocking bootloaders so i didnt accidentally do just this and now i messed it up :/
TechieMonkey said:
the guide that i used gave me that kind of file, all i did was download and install it the way that they told me... this is the link that i used...
http://droidviews.com/2013/root-and...erizon-galaxy-s3-sch-i535-android-4-1-14-1-2/
idk if im allowed to post a link to a different site, if not im sorry for that >.<
Click to expand...
Click to collapse
Didn't read your link but then try this once you get it booting. Download the file from the links here and you will be good to go..... http://forum.xda-developers.com/showthread.php?t=2046439
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-download-mode-jig/
question
I did this same thing. Since I bricked it flashing the vrelac boot chain and didn't actually flash a recovery or ROM does that trip the flash counter at all?????
roothead said:
I did this same thing. Since I bricked it flashing the vrelac boot chain and didn't actually flash a recovery or ROM does that trip the flash counter at all?????
Click to expand...
Click to collapse
Anyone ?
roothead said:
I did this same thing. Since I bricked it flashing the vrelac boot chain and didn't actually flash a recovery or ROM does that trip the flash counter at all?????
Click to expand...
Click to collapse
You can get the phone into download mode? If so, follow the thread I linked in post #9, download the files from that thread and follow the directions exactly. It will not brick you phone. I had just got done rooting and unlocking, using that guide, the other night when you posted this thread.
mefloump said:
You can get the phone into download mode? If so, follow the thread I linked in post #9, download the files from that thread and follow the directions exactly. It will not brick you phone. I had just got done rooting and unlocking, using that guide, the other night when you posted this thread.
Click to expand...
Click to collapse
The phone is bricked, no download mode, no recovery, nothing.MOD EDIT: DELETED FOR FRAUD DISCUSSION
Did you check the MD5checksum?
andybones said:
Did you check the MD5checksum?
Click to expand...
Click to collapse
No I didn't but should have obviously. It doesn't matter why I bricked the phone, it went back already. I was just wondering if they will be Able to tell I tried to flash something
roothead said:
No I didn't but should have obviously. It doesn't matter why I bricked the phone, it went back already. I was just wondering if they will be Able to tell I tried to flash something
Click to expand...
Click to collapse
well that's 99.9% the problem right there.
when flashing things that could brick your phone, radios, recovery, ESP bootchain!
double check that MD5, but hey I've done the same, and now I ALWAYS check it on everything even little things, lesson learned the hard way for me.
glad you'll be getting new phone..
and for about flashing prob not, I have sent back 2 SG3's rooted with TWRP recovery, but that's me..
I even brought one to VZW and she was going to do a factory reset reading from the screen and it brought her to TWRP recovery LMAO! her and the manager looked at each other like WTF, and STILL gave me a brand new phone uotta the box.
Rather than start a new thread, I'm just going to bump this one. I had this same problem. I followed the instructions from the XDA article, along with the ones provided in DroidModd3rX's YouTube video exactly on my VZW GS3, build JZO54K. I hard bricked my phone. It only showed up in the Device Manager on Windows 8 as QHSUSB_DLOAD. It was stuck like that as soon as I flashed the VRALEC Bootchain. Is there something I've done wrong that I could have done differently to prevent it from happening? I had just purchased it the day before, so I was able to get a replacement, but I'm highly interested in rooting my device and want to ensure this doesn't happen again. Is it a problem with Windows 8, is it the build my phone is running on, or is it perhaps because I had USB Debugging checked on? I just find it odd that I had the same problem, and went through it the same day as the person who started this thread. And yes, I did check the MD5, it was fine.
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I've tried that a few times already. No luck thus far
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
What baseband are you on ?
jlyle said:
What baseband are you on ?
Click to expand...
Click to collapse
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
ImBarone said:
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
Click to expand...
Click to collapse
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
jlyle said:
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
Click to expand...
Click to collapse
1000% sure that it was 4.1.2 and MF1 because it was trying to push an OTA update that i kept canceling. should i attempt reflashing through odin again? and if so could you link me to something specifically i should flash and possibly some instructions because ive been without a phone for 2 weeks and wouldnt like to wait til october for another one....
thanks
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
prdog1 said:
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
Click to expand...
Click to collapse
im completely sure it was NOT 4.3 though. it flashed fine when i ran this http://forum.xda-developers.com/showthread.php?t=2046439 i just forgot to flash the bootloader unlock through recovery so then i tried reflashing stock and now im here. and where could you point me in the direction of a stock tar and some instructions because ive been using the ones on the original thread i linked with no luck
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/?fid=23134718111254196
http://forum.xda-developers.com/showthread.php?t=2332825
prdog1 said:
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/user/settings-dev-files.php?action=show-files&flid=7111#
http://forum.xda-developers.com/showthread.php?t=2332825
Click to expand...
Click to collapse
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
ImBarone said:
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Click to expand...
Click to collapse
Try again with this link.
http://www.androidfilehost.com/?fid=23134718111254196
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
im currently flashing the root66.tar through odin hopefully my problem will be solved afterwards
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
ImBarone said:
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
Click to expand...
Click to collapse
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Your in download mode right ? HA / just checking
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
Boot into download mode and on the screen where the option to continue or restart phone, choose to restart your phone. This worked for me just this morning, for some reason it bypasses the check.
Sent from my SCH-I535 using XDA Premium 4 mobile app
jlyle said:
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Click to expand...
Click to collapse
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Odin will reboot your phone.. are you getting Pass in Odin ??
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Yes. It is common for it to reboot but bootloop. Pull battery and then boot into stock recovery and factory reset. Then it should boot.