Related
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
muleman said:
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
Click to expand...
Click to collapse
Hmm I'd say if the USB jig didn't work, you're not soft bricked. That's a hard brick.
What kind of USB jig are you using?
Was it a ROM or a kernel you flashed? which one, version etc.?
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
donation rewards for anybody that can help! lol this is depressing, my old captivate isnt this sensitive and has been through hell and back, but this SGS4g.... im dissappointed in.
Uninstall all the drivers for the phone make sure you have the right ones also, and try plugging it into a usb 2.0 slot then run it again, this seemed to work for me. I ran into the same issue I plugged in my jig but it gave me a black screen, but odin recognized it and I flashedthe kd1 update and it was fixed. Hope this helps
muleman said:
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
Click to expand...
Click to collapse
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Along with what krylon said, maybe a bad download, try download file again
Sent from my SGH-T959V using XDA Premium App
will do thanks guys, ill try it tonight and let ya know how it goes for me.
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
krylon360 said:
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Click to expand...
Click to collapse
youre the man.... Thanks much
muleman said:
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
Click to expand...
Click to collapse
Heimdall works at that same warning screen too. I've done it on my SGS4G.
I am confused..
sgyee said:
Heimdall works at that same warning screen too. I've done it on my SGS4G.
Click to expand...
Click to collapse
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
amishraa said:
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
Click to expand...
Click to collapse
If its currently in the state which I'm assuming..
-won't turn on, no sign of life period...
-plugging it in the wall charger won't even show the green battery status...
-won't get recognized when plugged into pc (or odin)...
-all combinations of buttons and battery pulling+usb cable plugging does nothing...
Yea I think its safe to say it went to a land far far away just like my friend's phone and only Samsung can revive it now.. Because I remember reading all the stories how everyone brought theres back to life so easily with the button combos or the jig usage, but those phones all at least showed a sign of life with that cable screen. But if its pitch black like I'm assuming then...
Same here. The jig didn't seem to work - I still got the cell + comp but odin worked anyway and reflashed stock. It's probably better to run Odin off a desktop if you have one.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. In most cases I have been able recognize the phone using odin. A few of the key steps that I have used to get the phone recognizable in odin are:
1. If the computer says "usb not recognized" when initially plugging in the phone, uplug it and plug it back in. Most of the time when I do this the phone is recognized as samsung device.
1b: If odin now recognizes the phone after running through step 1 I will try to flash the files again. it will usually fail after trying to load the flash files on the first try. I have to mess around with this process a few times and I can usually get a successful flash.
2. I had an case when having to deal with this problem yesterday. I was running through steps 1,1b and not having success. Odin was hanging, (I forget which step). I let it sit for about 10 minutes and was still hanging. I unplugged the phone with odin still hanging pulled battery, powered on, plugged back in. Odin, which was still open and still trying to connect, continued its already started process after plugging it back in!!! This was an accident to still have the odin running and trying to connect, but after reconnecting the phone it successfully flashed!
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
These kind of observations are especially helpful! I can concur that I get the same <phone..!..pc> error, when odin tries to flash and gets a write fail, however, I do not have the "re-partition" option set. I then have to run through my previously mentioned steps to try to get a successful flash.
My question is what can i do to keep odin from failing to write when flashing?? I have only been using PDA packages, with the exception of using discrete packages (pit,csc,phone,pda) when loading the 2.3.4 rom leak.
It seems like the flashing write error in odin in causing the <phone..!..pc> error quite often with different flash processes. Does anyone have a solution to what might be causing this write error and what can be done to prevent this whole cycle? If so I sticky or new thread might be useful for other users. It has caused to have to warranty my first phone, urrrg!
Scariest feeling ever........ Not seeing your phone come up on Odin.
Sent from my SGH-T959V using XDA Premium App
Woops ahahahha. Was talkin to my friend. SOrry!
fvnktion said:
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. ..... [cut] ......
Click to expand...
Click to collapse
I had the same issue yesterday, when I tried to flash KD1 vanilla (stock) ROM
using ODIN, it failed the first 4 seconds, it boots into fuzzy looking screen and
that's it, every time I tried to boot it the fuzzy screen fades away to pitch black.
there is 2 possibilities that messed up the whole thing for me:
1) Bad ROM.. (i.e, can't be used with ODIN) although some members said it works
but don't know if there anything special to do before hand, if I want to downgrade.
2) Samsung Kies' fault, I installed just right before I used ODIN, and told me my
device is not registered.. hmm.
It could be both cases, but I suspect Kies the culprit, I had to uninstall it, and
uninstall the drivers came with it, installed the drivers found here in these forums,
and Odin recognized a COM port, although black screen on the phone, flashed
to KH1 and I am back to business. phew..
GB is awesome, but I can't stand the weak WIFI issue even with the latest KH1
I have to stand 3 feet away from my router to get a solid signal, with froyo
vanilla rom, I was able to connect like 50 feet away. but that's another problem
not for this thread.
Heh funny thing I read today in some thread, there is a conflict between Kies and
Odin after the incident happened. my fault for not reading a lot, jumping the gun
almost cost me the phone :/
I tried flashing the ics source port but forgot to flash cm7 first... It flashed fine and I followed the procedure to flash. The phone would turn on but always go straight to recovery. I figured this was because I didn't go to cm7 first, so I went to flash it but I kept getting errors. I went to flash stock, it started going so I walked away. When I came back my phone was just a white screen and odin was stuck at sbl.bin. So now I can't boot up the phone, there's no bootloaders, just a black screen whenever I try to do anything. The thing is, I can get into download mode just fine through button combos which leads me to think it's not bricked. However, odin/heimdall will not recognize it... Anyone know what to do?
Edit: resolved. After trying like a bazillion times it finally worked
mikel.canovas said:
I tried flashing the ics source port but forgot to flash cm7 first... It flashed fine and I followed the procedure to flash. The phone would turn on but always go straight to recovery. I figured this was because I didn't go to cm7 first, so I went to flash it but I kept getting errors. I went to flash stock, it started going so I walked away. When I came back my phone was just a white screen and odin was stuck at sbl.bin. So now I can't boot up the phone, there's no bootloaders, just a black screen whenever I try to do anything. The thing is, I can get into download mode just fine through button combos which leads me to think it's not bricked. However, odin/heimdall will not recognize it... Anyone know what to do?
Edit: resolved. After trying like a bazillion times it finally worked
Click to expand...
Click to collapse
Glad it worked, the day when a Cappy dies is a sad one...
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
hechoen said:
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
Click to expand...
Click to collapse
I didn't feel like i really hard bricked it until i saw the USB computer connection error "device pluged in malfunctioned" in more than one PC.
Then i really felt like its a hardware BIOS chipset level problem now but man...
That story cracked me up. That is exactly why I spend days reading before I even root my phone. I made the mistake one time on my old G1 and it could not be revived.
Congrats on getting it working. (especially without flooding the q&a with redundant questions that have been described in detail several places )
hani1400 said:
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Click to expand...
Click to collapse
Wheooooooooowwww,..you just UNBRICKED mine, I know of the Battery pull etc...but the post you referenced
is MAGIC
This was not my first Rom nor Root on this phone, it weirdly happened while doing the GB starter....via ODIN, which i also used before..no clue what went wrong, oh well...
Thank you, thank you "i did"....Yohoooo
Yup i agree i like to read, reread then read as i do. This way i got a pretty good understanding of what I'm doing. Btw i have just started using one click and it is sooooo simple. I love it.
Sent from my SGH-T959V using XDA App
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
diavel said:
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=881162
Im still carrying this phone, stupid baseband unlock for iphone won't come out now I am carrying 2 phones, one as an ipod touch and the galaxy s! Good story, hope it can help others, but I am prepared to jump off of this bandwagon anytime now!
I need help guys,
I used Odin to root the phone and did my first custom rom which is the clean rom...it went through the process and when it was about to reboot i got the system software not approved by verizon and take phone to store
I have been told to odin back to stock but it wont let me. The stock image on odin wont work it says fail
I tried the first method and used odin in download mode to flash the stock image
Failed:
This is what I get
added
Odin V3 engine
File Analysis
all threads completed (succeed 0 / Fail 1)
In the Odin Download mode on the phone the top left reads as follow
Odin Mode (Red Letters)
Product Name (SCH-I535)
Custom Binary Download : Yes (1 counts )
Current Binary Custom
System Status Custom
Qualcomm Secureboot: Enable
One thing I gotta mention is that when I got the phone last week it had an OTA update from Verizon which I did install and then a few days later I rooted the phone and when I tried to use Clean Rom it gave me the dreaded Verizon message
Sounds like you didn't unlock the bootloader.
Ya your bootloader is locked again ... unlock it and redo the steps everything should be fine after that
Guys I know that the bootloader is locked but i cannot get back to stock to unroot phone and then unlock the bootloader
Odin recognizes phone but the stock image goes into fail mode right away
I cannot get into recovery and the only thing I can do is go to download mode and Odin but nothing else
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=jtag
http://forum.xda-developers.com/showthread.php?t=1798850
http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/
http://www.android.gs/fix-bricked-verizon-galaxy-s3/
one of these may be able to help you ... i lost the original link i had but saved these for bootloader issues hope they help they should
Stranger_84 said:
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=jtag
http://forum.xda-developers.com/showthread.php?t=1798850
http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/
http://www.android.gs/fix-bricked-verizon-galaxy-s3/
one of these may be able to help you ... i lost the original link i had but saved these for bootloader issues hope they help they should
Click to expand...
Click to collapse
You are aware he can Odin flashed the latest OTA instead of that you have provided. Here it is :http://forum.xda-developers.com/showthread.php?t=2046439. This will also help fix his phone being that it is recent. Forgot this link to get him back on track: http://forum.xda-developers.com/showthread.php?t=1974114.
i thought thats what he already tried? but yes you can odin any ota file being that an unlocked bootloader isnt needed.
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
I'm not sure being ive never had that issues ... im sorry and good luck
try flashing odin stock ROM, not bootchain
NYGiants4Natic said:
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
Click to expand...
Click to collapse
Did you put the file in PDA in Odin they only work if you checked PDA.
NYGiants4Natic said:
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
Click to expand...
Click to collapse
I had a similar issue once. This helpful post by h3llsdr0id eventually got me up and running. Took a total of like 4 hours though lol.
http://forum.xda-developers.com/showpost.php?p=30569324&postcount=26
Make sure you have the correct files. This is for the original root66 so it's ICS. Once I booted up and activated I took the Verizon OTAs all the way to JB and then rooted/unlocked bootloader.
edit: I actually had to go back to ICS to reprovision my SIM so not sure you have to go through all of this. Try to odin stock JB ROM like mentioned above.
Thank YOU so much guys you have made my day.
After trying all last night and today I got it back to stock with the OTA file through ODIN. That is all I needed and it went right back to brand new stock phone using 4.1.1
WOW.
I thought I was going to have a dead phone.
Thank you all
Glad you got it up and working!!!!!
Yea I had the same problem but all it needed was a handy flash back to stock. The good thing with making these mistakes is that if it happens again you know what to do.
Sent from my SCH-I535 using xda app-developers app
I'm having the same problem and can't get into download mode
Gatanater said:
Yea I had the same problem but all it needed was a handy flash back to stock. The good thing with making these mistakes is that if it happens again you know what to do.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hi there,
Could someone please help me. I bricked my phone 3 days go and went through odin and root66 stock to unbrick it. I installed CWR and backed up everything, then i purchased triangle away to reset the flash counter. When I did that I got the software not authorized by verizon error screen. It won't let me get into download mode or recovery. Can I still try to use odin? What should I do? I'd really appreciate some help today is the 4th day I have been trying to fix my phone, only to make it worse.
Thank you in advance
You have to get into download mode to use Odin. It will go into download mode, if you will search, there are ways to pull battery along with button combo to get it there. After rooting, use EZ Unlock 1.2 and that will unlock your bootloader without then unauthorized message from Verizon. Make sure you use only that version, the others don't work.
Re: I'm having the same problem and can't get into download mode
mj76 said:
Hi there,
Could someone please help me. I bricked my phone 3 days go and went through odin and root66 stock to unbrick it. I installed CWR and backed up everything, then i purchased triangle away to reset the flash counter. When I did that I got the software not authorized by verizon error screen. It won't let me get into download mode or recovery. Can I still try to use odin? What should I do? I'd really appreciate some help today is the 4th day I have been trying to fix my phone, only to make it worse.
Thank you in advance
Click to expand...
Click to collapse
Pull battery, hold volume down+home+power keys while you put the battery back in. If that's too many buttons to fumble with at the same time you can try pulling battery, put it back, hold all three keys while plugging it into your computer. My old phone worked that way, idk about the s3. You SHOULD get the download triangle and it asking you if you want to continue. Hit volume up to continue then plug it in and odin should recognize it. Get the stock rom image to flash in the PDA slot of odin. Accept the OTA's until you're up to date then unlock bootloader, root, then flash custom roms/kernels AFTER you've done the appropriate reading. Theres a sticky in development takes you step by step on how to unbrick, then unlock and root. Those should help once you get into download. Hope this helps! :fingers-crossed:
flammablepez said:
Pull battery, hold volume down+home+power keys while you put the battery back in. If that's too many buttons to fumble with at the same time you can try pulling battery, put it back, hold all three keys while plugging it into your computer. My old phone worked that way, idk about the s3. You SHOULD get the download triangle and it asking you if you want to continue. Hit volume up to continue then plug it in and odin should recognize it. Get the stock rom image to flash in the PDA slot of odin. Accept the OTA's until you're up to date then unlock bootloader, root, then flash custom roms/kernels AFTER you've done the appropriate reading. Theres a sticky in development takes you step by step on how to unbrick, then unlock and root. Those should help once you get into download. Hope this helps! :fingers-crossed:
Click to expand...
Click to collapse
Thank you for your response. I tried pulling the battery out and holding volume down, home and power keys at the same time while putting battery in, even as i plugged it into my phone, but nothing but the unauthorized error screen comes up. I should note that my phone is note 2 not s3. I apologize for posting it here, but this thread seemed to be just like the problem i was having.
Hey guys,
I am totally freaking out because I was trying to flash my phone back to a somewhat stock position to erase it and just sort of get back to a stock place and then start flashing again. I tried keeping all the different instructions straight and I think I got turned around someplace.
This is where I am at for what is going on:
Flashed the VRALEC bootchain after I flashed the Stock rooted rom root66_VZW_I535VRBMB1.tar.md5.
The phone currently is accessible for the Odin download mode and when it boots I show the Samsung logo with the lock logo that is unlocked. I am totally not sure where to go from here and need some serious help with what to do next. The phone seems to be simply stock at booting on the 4Glte screen with the Verizon logo.
Any help would be very much appreciated as I am so mixed up as to what to do I don't know where to go and I don't want to make matters worse.
:crying:
NeCr0mStR said:
Hey guys,
I am totally freaking out because I was trying to flash my phone back to a somewhat stock position to erase it and just sort of get back to a stock place and then start flashing again. I tried keeping all the different instructions straight and I think I got turned around someplace.
This is where I am at for what is going on:
Flashed the VRALEC bootchain after I flashed the Stock rooted rom root66_VZW_I535VRBMB1.tar.md5.
The phone currently is accessible for the Odin download mode and when it boots I show the Samsung logo with the lock logo that is unlocked. I am totally not sure where to go from here and need some serious help with what to do next. The phone seems to be simply stock at booting on the 4Glte screen with the Verizon logo.
Any help would be very much appreciated as I am so mixed up as to what to do I don't know where to go and I don't want to make matters worse.
:crying:
Click to expand...
Click to collapse
Pull the battery, boot into recovery (hold volume Up, power, and home), then do a Factory reset.
SlimSnoopOS said:
Pull the battery, boot into recovery (hold volume Up, power, and home), then do a Factory reset.
Click to expand...
Click to collapse
Booting into recovery gives me some message about unauthorized software as I had tried that. I was trying this method but the VRALF bootchain was showing as invalid. I just found a copy of it on invisiblek's site and flashed that and was going to continue with that method trying to get this working. I will update once that has gone through as the stock.vzw_root66.tar image is flashing now. Wish me luck!
Ok, so this time when it finished flashing it rebooted, then it showed the android with the spinning hexagon type thing that you would see when doing a rom backup or something of the sort. I pulled the battery rebooted and did a factory reset along with wiping cache directory and now I am waiting at the 4Glte screen again... Keeping fingers crossed and hoping this works.
AND OMG AWESOME!!!!!
Man, now it is time to get back to flashing. Thank you so much SlimSnoopOS for that last thing I was missing, I really appreciate it.