Related
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?
deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.
I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.
deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.
same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...
nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David
I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.
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.
So basically I have my nexus 5 and it’s completely stocked. I don’t want to root or do anything that could prevent me from receiving OTA updates?
What are the steps to update my phone rom stock 4.4 to 4.4.1.
Thanks
I found this video very helpful.
http://www.youtube.com/watch?v=rfZ4f5Bdgfc&list=FLJJ5N1JCwlum5OdXVTemjHw&index=2
richport29 said:
I found this video very helpful.
http://www.youtube.com/watch?v=rfZ4f5Bdgfc&list=FLJJ5N1JCwlum5OdXVTemjHw&index=2
Click to expand...
Click to collapse
I have a nexus 5.
rayoubi said:
I have a nexus 5.
Click to expand...
Click to collapse
Exact same process.
---------- Post added at 06:05 PM ---------- Previous post was at 06:04 PM ----------
Obviously use the Nexus 5 4.1.1 ota
Be patient and receive the update directly from Google as an OTA within a week, or so. There might need to be a revision to this update, due to issues with the new radio seeming to not get good signal strength and so forth, which is why Goofle sends it out incrementally.
Sent from my Nexus 5 using Tapatalk
F n a I've never seen so many dopes in a row
http://forum.xda-developers.com/showthread.php?p=47369234
jd1639 said:
F n a I've never seen so many dopes in a row
http://forum.xda-developers.com/showthread.php?p=47369234
Click to expand...
Click to collapse
People need to search first, but that guide doesn't work for everyone.
My phone wouldn't reboot into actual recovery...it came up saying "No error" or some nonsense and wouldn't get into recovery. It makes the guide useless.
hotleadsingerguy said:
People need to search first, but that guide doesn't work for everyone.
My phone wouldn't reboot into actual recovery...it came up saying "No error" or some nonsense and wouldn't get into recovery. It makes the guide useless.
Click to expand...
Click to collapse
The guide is not useless. If you can't boot into recovery you're doing something wrong or your recovery is borked. If its borked you can fix it.
jd1639 said:
The guide is not useless. If you can't boot into recovery you're doing something wrong or your recovery is borked. If its borked you can fix it.
Click to expand...
Click to collapse
Oh, I didn't realize the guide explained how to fix it if something happened to your recovery. If so, I redact my statement.
(Obviously that's sarcasm and I don't redact my statement, since it doesn't do that)
My phone is completely bone-stock. I haven't rooted or unlocked. It doesn't boot into recovery using the method listed in the guide, and booting into the system menu and selecting Recovery just boots the phone normally for me.
hotleadsingerguy said:
Oh, I didn't realize the guide explained how to fix it if something happened to your recovery. If so, I redact my statement.
(Obviously that's sarcasm and I don't redact my statement, since it doesn't do that)
My phone is completely bone-stock. I haven't rooted or unlocked. It doesn't boot into recovery using the method listed in the guide, and booting into the system menu and selecting Recovery just boots the phone normally for me.
Click to expand...
Click to collapse
Then your recovery is broken. Look at the how to flash factory images sticky in General and fastboot flash a fixed recovery.
Nothing to do with the fact that this is another OTA thread when there is an OTA sticky. The guide is not useless, your phone is.
rootSU said:
Then your recovery is broken. Look at the how to flash factory images sticky in General and fastboot flash a fixed recovery.
Nothing to do with the fact that this is another OTA thread when there is an OTA sticky. The guide is not useless, your phone is.
Click to expand...
Click to collapse
And, as I mentioned, I haven't modified a thing on the phone. If my recovery is broken, it was broken from the factory.
And, again, the guide had nothing to do with that. If anyone else has the issue (which people are having, according to a few other topics I've seen), the guide makes no account for it -- for anyone with the issue, the guide is of no help.
hotleadsingerguy said:
And, as I mentioned, I haven't modified a thing on the phone. If my recovery is broken, it was broken from the factory.
Click to expand...
Click to collapse
I never said it was anything to do with what you had done or when it had broken.
hotleadsingerguy said:
And, again, the guide had nothing to do with that. If anyone else has the issue (which people are having, according to a few other topics I've seen), the guide makes no account for it -- for anyone with the issue, the guide is of no help.
Click to expand...
Click to collapse
And why would it? It also doesn't help people with a smashed screen or broken volume buttons. The guide is a guide to do what needs to be done on a fully working phone. It does NOT need to cover every fault that someone might have that prevents them doing the things in the guide. The fact your phone is broken bears no relevance to the usefulness of the guide. Besides, I already advised you what you could try to fix it.
Anyway, this thread is a duplicate and I have requested it be closed.
hotleadsingerguy said:
Oh, I didn't realize the guide explained how to fix it if something happened to your recovery. If so, I redact my statement.
(Obviously that's sarcasm and I don't redact my statement, since it doesn't do that)
My phone is completely bone-stock. I haven't rooted or unlocked. It doesn't boot into recovery using the method listed in the guide, and booting into the system menu and selecting Recovery just boots the phone normally for me.
Click to expand...
Click to collapse
hi
i am a noob. my phone is also compleely stock. not rooted and locked. i just activated with my carrier and downloaded speedtest. thats it. i have android sdk and platform tools and universal naked driver with adb support installed on my pc.
Code:
adb boot recovery
takes me to recovery. and i side loaded from there. :good:
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.
Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
akaplo said:
Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
Click to expand...
Click to collapse
I am in the same boat. Please let me know if you get an unbrick image..
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Chay555 said:
I am in the same boat. Please let me know if you get an unbrick image..
Click to expand...
Click to collapse
akaplo said:
Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
Click to expand...
Click to collapse
Good news! I was able to get the phone booted up again. Bad News: Its back on Lollipop firmware (BP1.) So what I did was I used the files from jrkuses working root method 3/4/16 and flashed them through Odin. First I flashed the PB1 unbrick image in his OK3 file, then I flashed the Nk2 kernel also included in the OK3 file, and last I flashed a file called VZW_BPB1_KERNEL_ONLY.tar.md5 also in the folder. Flashing those got me booted back on 5.0 safely.
---------- Post added at 08:57 PM ---------- Previous post was at 08:55 PM ----------
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
Thank You very much for the offered help. I just found a fix using jrkuses files in his root method and am now up and running again. Again Thank You.
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
It's definitely a hard brick. I can't boot into recovery, download mode, or anything! I've got a retail phone. You'd be a lifesaver if it works!
Chay555 said:
Thank You very much for the offered help. I just found a fix using jrkuses files in his root method and am now up and running again. Again Thank You.
Click to expand...
Click to collapse
Were you able to boot the phone during your ordeal? I can't get mine to do anything.
akaplo said:
Were you able to boot the phone during your ordeal? I can't get mine to do anything.
Click to expand...
Click to collapse
I was able to boot and I kept freezing at the Verizon splash screen. I did not realize that you couldn't even boot up. It was just a softbrick on my end. I hope you can get everything sorted out
---------- Post added at 09:55 PM ---------- Previous post was at 09:34 PM ----------
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
Question. Everytime I flash the PD1 firmware on my phone it always gets stuck on the Verizon splash screen. Am I doing something wrong?
Chay555 said:
I was able to boot and I kept freezing at the Verizon splash screen. I did not realize that you couldn't even boot up. It was just a softbrick on my end. I hope you can get everything sorted out
---------- Post added at 09:55 PM ---------- Previous post was at 09:34 PM ----------
Question. Everytime I flash the PD1 firmware on my phone it always gets stuck on the Verizon splash screen. Am I doing something wrong?
Click to expand...
Click to collapse
Just flash stock PD1 using Odin and factory reset in stock recovery afterwards. Once you get used to it, softbricks won't scare you anymore
Nandr0idC0nsumer said:
Just flash stock PD1 using Odin and factory reset in stock recovery afterwards. Once you get used to it, softbricks won't scare you anymore
Click to expand...
Click to collapse
When I flash stock PD1 using Odin and factory reset it still freezes at Verizon splash screen. Any other way I flash PD1 whether it be Kies or Odin outputs the same result.Freeze at Verizon splashscreen
Chay555 said:
When I flash stock PD1 using Odin and factory reset it still freezes at Verizon splash screen. Any other way I flash PD1 whether it be Kies or Odin outputs the same result.Freeze at Verizon splashscreen
Click to expand...
Click to collapse
Reset using stock recovery. it usually takes about 20min on the vzw screen
Only problem is that I have a developer model, keep scouting the community I'm pretty positive someone has retail pit file with partitions. I have hard bricked my phone before I repaired it using win32img creator using an sd card. I never messed with partitions ever again after that.
akaplo said:
It's definitely a hard brick. I can't boot into recovery, download mode, or anything! I've got a retail phone. You'd be a lifesaver if it works!
Click to expand...
Click to collapse
stellar0322 said:
Only problem is that I have a developer model, keep scouting the community I'm pretty positive someone has retail pit file with partitions.
Click to expand...
Click to collapse
Darn. Thanks though! @Nandr0idC0nsumer, is there any way you might be able to get this for me? I posted on your debrick thread but haven't heard from anyone, so I started this thread in hopes to catch someone's (ANYONE'S) eye
In order for someone to do this, they'd have to be on a rooted version on PD1, yes?
akaplo said:
Darn. Thanks though! @Nandr0idC0nsumer, is there any way you might be able to get this for me? I posted on your debrick thread but haven't heard from anyone, so I started this thread in hopes to catch someone's (ANYONE'S) eye
In order for someone to do this, they'd have to be on a rooted version on PD1, yes?
Click to expand...
Click to collapse
Alright. I'm confused
EDIT: looked through the thread now. That's a hardbrick. Nobody has created a debrick image for PD1, so just try the PB1 debrick.
Re-explain what's going on. Unless your device is 100% dead, my debrick thread will not be of any use.
Nandr0idC0nsumer said:
Nobody has created a debrick image for PD1, so just try the PB1 debrick.
Re-explain what's going on. Unless your device is 100% dead, my debrick thread will not be of any use.
Click to expand...
Click to collapse
From the beginning:
Yesterday, I was on rooted OE1, using muniz_ri's build from months ago. I decided to use his thread that had been updated the other day to update my phone to PD1 (Android 6.0). I updated the ROM and the bootloader.
It got stuck on the Samsung boot screen, and after about 40 minutes, I decided to flash the PB1 (Android 5.0) stock ROM. I downloaded the full tar from sammobile and flashed using odin. It went successfully, as far as I could tell. My phone froze on the Verizon boot screen as expected, and after about 10 minutes the screen went black and the notification LED started blinking red. I pulled the battery, put it back in, and tried to power the phone on. It has been completely unresponsive every since. Neither recovery mode nor download mode is accessible.
Obviously, I have a hard brick. I've tried using the PB1 debrick image you (@Nandr0idC0sumer) gave in your other thread with my 16GB external SD card. I followed the steps given there exactly. I've had no luck in getting my phone to respond. I thought that maybe my flash went bad and that my bootloader is still on PD1 while my ROM is PB1, and I would therefore need a PD1 debrick image. Thus, this thread was born.
akaplo said:
From the beginning:
Yesterday, I was on rooted OE1, using muniz_ri's build from months ago. I decided to use his thread that had been updated the other day to update my phone to PD1 (Android 6.0). I updated the ROM and the bootloader.
It got stuck on the Samsung boot screen, and after about 40 minutes, I decided to flash the PB1 (Android 5.0) stock ROM. I downloaded the full tar from sammobile and flashed using odin. It went successfully, as far as I could tell. My phone froze on the Verizon boot screen as expected, and after about 10 minutes the screen went black and the notification LED started blinking red. I pulled the battery, put it back in, and tried to power the phone on. It has been completely unresponsive every since. Neither recovery mode nor download mode is accessible.
Obviously, I have a hard brick. I've tried using the PB1 debrick image you (@Nandr0idC0sumer) gave in your other thread with my 16GB external SD card. I followed the steps given there exactly. I've had no luck in getting my phone to respond. I thought that maybe my flash went bad and that my bootloader is still on PD1 while my ROM is PB1, and I would therefore need a PD1 debrick image. Thus, this thread was born.
Click to expand...
Click to collapse
Unplug your device and open device manager on windows. now plug it in. does device manager refresh as if it detected a new device?
Because sdcard mode will only work if you can get the device into qhsusb_bulk mode.
Nandr0idC0nsumer said:
Reset using stock recovery. it usually takes about 20min on the vzw screen
Click to expand...
Click to collapse
Is good now. Thank You
Chay555 said:
Is good now. Thank You
Click to expand...
Click to collapse
Congrats! You get a cookie.
Nandr0idC0nsumer said:
Unplug your device and open device manager on windows. now plug it in. does device manager refresh as if it detected a new device?
Because sdcard mode will only work if you can get the device into qhsusb_bulk mode.
Click to expand...
Click to collapse
No, it does not. Is there some sort of button combo I should be pressing to get the device into that mode? I've tried long-holding the following combos:
1. Power
2. Power, volume down, and home
3. Power, volume up, and home
akaplo said:
No, it does not. Is there some sort of button combo I should be pressing to get the device into that mode? I've tried long-holding the following combos:
1. Power
2. Power, volume down, and home
3. Power, volume up, and home
Click to expand...
Click to collapse
I've read up on the Snapdragon 80x boot ROMs, and there appears there is only 1 way to get into qhsusb_bulk mode, which is to have the bootloader corrupted and it is automatically triggered.
If it's not in that mode, it's a brick, go to Verizon and tell them it randomly died
there is nothing that can be done from now. good luck dealing with verizon/samsung and I hope you're still in warranty.
PD1 unbrick image.
https://www.androidfilehost.com/?fid=24562946973631519