I followed the instructions on the first post of this thread, but when I went to restart, my tablet wouldn't get past the "Galaxy Tab 2" splash screen. Whatever it told me to do with the kernel or whatever must've caused the problem. I didn't have CWM at the time. I then followed this thread to try to root it. So, I have CWM if that helps, and my tablet is very likely rooted. But I still can't get past the splash screen. Any help would be greatly appreciated, and since I can get to download and CWM, I don't think it's bricked (although, I'm not entirely sure what "bricked" means, software/hardware wise).
Thanks in advance
EDIT: I have a Samsung Galaxy Tab 2 7.0" GT-P3113 running Android 4.0.4
yoharnu said:
I followed the instructions on the first post of this thread, but when I went to restart, my tablet wouldn't get past the "Galaxy Tab 2" splash screen. Whatever it told me to do with the kernel or whatever must've caused the problem. I didn't have CWM at the time. I then followed this thread to try to root it. So, I have CWM if that helps, and my tablet is very likely rooted. But I still can't get past the splash screen. Any help would be greatly appreciated, and since I can get to download and CWM, I don't think it's bricked (although, I'm not entirely sure what "bricked" means, software/hardware wise).
Thanks in advance
EDIT: I have a Samsung Galaxy Tab 2 7.0" GT-P3113 running whatever version of Android that Kies gave me
Click to expand...
Click to collapse
If it were me, I'd load the adb drivers and see if I could get into an adb shell. This would do two things. First, it would let you get a logcat which might tell us what happened. Second, it would let you do things to fix whatever seemed to be the problem. If it is the kernel, this probably won't work, but if it is something else it should. You can get into a shell from CWM but that won't get you a logcat of the problem.
If you have CWM have you tried doing a complete wipe from the CWM menu?
yoharnu said:
I followed the instructions on the first post of this thread, but when I went to restart, my tablet wouldn't get past the "Galaxy Tab 2" splash screen. Whatever it told me to do with the kernel or whatever must've caused the problem. I didn't have CWM at the time. I then followed this thread to try to root it. So, I have CWM if that helps, and my tablet is very likely rooted. But I still can't get past the splash screen. Any help would be greatly appreciated, and since I can get to download and CWM, I don't think it's bricked (although, I'm not entirely sure what "bricked" means, software/hardware wise).
Thanks in advance
EDIT: I have a Samsung Galaxy Tab 2 7.0" GT-P3113 running whatever version of Android that Kies gave me
Click to expand...
Click to collapse
I had this happen to me today. I got a new P3113 because I had a dead pixel. Anyway, my new one came with 4.0.3 and immediately wanted to update to 4.0.4. After this, I used Odin to flash cwm, and was immediately stuck in a boot loop. I checked my source again and saw that there was a new file to flash, and sure enough that did it. I was so worried that I screwed up my new tab, but it works now. My counter now reads 2 flashes.
I used this guide and got the latest espressowifi image:
http://rootzwiki.com/topic/25228-how-to-rooting-gt-p3113-step-by-step-updated-07182012/
Sent from my GT-P3113 using Tapatalk 2
Dralanmage said:
I had this happen to me today. I got a new P3113 because I had a dead pixel. Anyway, my new one came with 4.0.3 and immediately wanted to update to 4.0.4. After this, I used Odin to flash cwm, and was immediately stuck in a boot loop. I checked my source again and saw that there was a new file to flash, and sure enough that did it. I was so worried that I screwed up my new tab, but it works now. My counter now reads 2 flashes.
I used this guide and got the latest espressowifi image:
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. But where can I get the latest version of espressowifi?
EDIT: I tried espressowifi-recovery-5-18.tar.md5, but that didn't work. I think the problem has something to do with the PIT file I flashed, but I'm not sure. Also, I have access to adb now, and logcat just spits out a big stream of stuff. Should I upload it?
EDIT2: Fixed it with ueblg5_espressowifi_recovery.tar.md5. Thanks to both of you!
yoharnu said:
Thanks. But where can I get the latest version of espressowifi?
EDIT: I tried espressowifi-recovery-5-18.tar.md5, but that didn't work. I think the problem has something to do with the PIT file I flashed, but I'm not sure. Also, I have access to adb now, and logcat just spits out a big stream of stuff. Should I upload it?
EDIT2: Fixed it with ueblg5_espressowifi_recovery.tar.md5. Thanks to both of you!
Click to expand...
Click to collapse
Awesome! That was what fixed it for me too. It really sucked to bootloop my device about 20 minutes after opening it and not see a way out! I'm glad you got yours working!
Sent from my GT-P3113 using Tapatalk 2
First, if you're stuck in a bootloop, try accessing the recovery mode then wipe data, if this doesn't work, try getting into download mode and flash a firmware file (from sammobile.com or anywhere else)
Related
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
aperture said:
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
Click to expand...
Click to collapse
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
riverboat2001 said:
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
Click to expand...
Click to collapse
As long as you are using cm, I don't think it will be a problem. I will never go back to official. The problem stems from an issue with the stock recovery from Samsung. So in short, the devs are aware of the issue, but Samsung doesn't seem to care. As long as you are running the current cwm, and the dev isn't an idiot, you shouldn't have a problem. (No offense aorth and locerra, I know you're aware)
Sent from my Galaxy Tab 7 Plus
riverboat2001 said:
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
Click to expand...
Click to collapse
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
wingie6200 said:
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
Click to expand...
Click to collapse
Wow, thanks so much for taking the time to offer your advice.
I only have myself to blame for getting into this pickle! After Flashing so many different ROM's on loads of devices i just got a bit blaiz'e
Last night i did a wipe and factory reset through CWM and it all went well, so my question is, giving that i know i'm at risk, i can see three options,which is the "safest"
1/ Put tab away and don't use it until Samsung release a fix we can use
2/ Keep using the tab, but have that worrying niggle in the back of my mind
3/ Follow the post above and carry out the suggested procedure outlined above? (is it 1000% safe?
Can i assume that if i go as far as recovery mode via the ICS version to see the "recovery 3e" but don't wipe/factory reset i'm safe?
And consequently if i DON'T see that i would be safe to go ahead?
I do feel as if I'm sitting on a time-bomb here
(years ago i would have spent weeks messing around with this sort of thing, but as a middle aged housewife thats always on the go, i don't have the time, I just like to get my stuff working fast and bloatware free and i'm happy!)
Once again thanks for your input.
lol cant guarantee the 1000% safe part (since the offending code is in part coming from samsung) but people are aware of it / working to fix it and all non stock stuff is most probably safe. the CWM 6.0.1.0 definitely is, just used it myself.
and these things are kinda random (if all posts are to be believed) so i would just use the tab normally and worry about it much.. reports also say that samsung does repair these bricked tabs under warranty in case the unthinkable does happen.
and its not a time bomb :laugh:! (although there would probably be an app for that somewhere..)
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
ringnutz said:
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Kuniokun said:
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Click to expand...
Click to collapse
Yeah, I did.. happened the first time
Sent from my myTouch 4g via Tapatalk
Brickbug is caused by ****ty flashing firmware on some of our devices.
No danger with cwm 6.0.1.0 from aorth. We r safe!
Sent from my GT-P6200 using xda app-developers app
I have had no luck searching for the stock firmware of the SCH i705 model and cannot get it to boot.
After following this http://forum.xda-developers.com/showthread.php?t=1885558 Root tutorial, i got to step 2, and after doing the bootloader part, my tab froze at the Odin screen..
tried to reboot into recovery mode, got it for a few tries, and it gave me errors like
"E: could not find.. . ... .system
E: failed to mount,,,.,..,cache/blah"
then the device went into a boot loop and now I powered it off.
EDIT: now when I try booting into recovery, it shows the blue loading text, then goes into odin mode with the message
"Could not do normal boot.
ODIN MODE
PRODUCT NAME: SCH-I705
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
System Status: Official
QUALCOMM SECUREBOOT: ENABLE"
Can I get a link for some firmware or something? I need to get this back to normal >_<
igotbricked said:
I have had no luck searching for the stock firmware of the SCH i705 model and cannot get it to boot.
After following this http://forum.xda-developers.com/showthread.php?t=1885558 Root tutorial, i got to step 2, and after doing the bootloader part, my tab froze at the Odin screen..
tried to reboot into recovery mode, got it for a few tries, and it gave me errors like
"E: could not find.. . ... .system
E: failed to mount,,,.,..,cache/blah"
then the device went into a boot loop and now I powered it off.
EDIT: now when I try booting into recovery, it shows the blue loading text, then goes into odin mode with the message
"Could not do normal boot.
ODIN MODE
PRODUCT NAME: SCH-I705
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
System Status: Official
QUALCOMM SECUREBOOT: ENABLE"
Can I get a link for some firmware or something? I need to get this back to normal >_<
Click to expand...
Click to collapse
At what state was your tab when you tried flashing aboot? This is supposed to be flashed when you have booted into android normally. Unfotunately, Verizon has not released stock firmware so this is all we have. You wouldn't even be able to flash a stock recovery or boot image that I've dumped because it's not signed by VZW.
Try going through Step 1b in the root thread again and flash the stock rooted ODIN system image.
Another question, when you're in ODIN mode, is the screen in portrait or landscape mode? Portrait = stock, locked bootloader; landscape = unlocked bootloader.
The thing you don't seem to understand is : you HAVE to reflash your tablet using ODIN. It's not that hard. Just follow the second method here (you don't need to download android SDK)
copy this in your navigator bar : rootzwiki . com/topic/37272-verizonsch-i705-root-for-all-current-firmware/ ( delete space around the dot)
Or here :http://forum.xda-developers.com/showthread.php?t=1885558
Plus, your tab will be rooted.
You're welcome.
P.S : This limitation of URL is annoying as hell.
P.S 2: Oh I see my friend up here has posted the same tutorial. Don't know which one is first. Will link to his thread.
Paulli1 said:
The thing you don't seem to understand is : you HAVE to reflash your tablet using ODIN. It's not that hard. Just follow the second method here (you don't need to download android SDK)
copy this in your navigator bar : rootzwiki . com/topic/37272-verizonsch-i705-root-for-all-current-firmware/ ( delete space around the dot)
Or here :http://forum.xda-developers.com/showthread.php?t=1885558
Plus, your tab will be rooted.
You're welcome.
P.S : This limitation of URL is annoying as hell.
P.S 2: Oh I see my friend up here has posted the same tutorial. Don't know which one is first. Will link to his thread.
Click to expand...
Click to collapse
The tutorial on rootzwiki is mine I never go over there so revosfts posted it there.
Gg. My tablet stopped powering on. Doesn't respond at all now.
Nice..
Chances are your battery is dead. Plug it into the wall for a few hours.
First off, i appreciate your help, but I am pretty sure my device is done-zo. lol
Its been plugged for at least 5 hours, still unresponsive.
Do you think I have a chance bringing in an absolutely dead (brand new) tablet to the Verizon store?
It was purchased last month so it is probably covered under warranty.. If not there is always the mfc. warranty
If it doesn't respond at all then I'd say it's safe to take it in.
igotbricked said:
First off, i appreciate your help, but I am pretty sure my device is done-zo. lol
Its been plugged for at least 5 hours, still unresponsive.
Do you think I have a chance bringing in an absolutely dead (brand new) tablet to the Verizon store?
It was purchased last month so it is probably covered under warranty.. If not there is always the mfc. warranty
Click to expand...
Click to collapse
Verizon won't be able to do a damn thing, I had the same issue and had to ship it to Samsung, I'm still waiting for them to reflash it and see if they charge me any money, because according to them it might be out of warranty
(obviously I didn't tell them that I was rooting and flashing a new rom)
melog69 said:
Verizon won't be able to do a damn thing, I had the same issue and had to ship it to Samsung, I'm still waiting for them to reflash it and see if they charge me any money, because according to them it might be out of warranty
(obviously I didn't tell them that I was rooting and flashing a new rom)
Click to expand...
Click to collapse
Yeah,I didn't think Vz. Would be any help..
I talked to Samsung already about shipping it in. It should be free without the cost of shipping. Let me know how it works out for u
J1 OTA Update
Hey guys, for the life of me, I can't find a good link to download the G3 to J1 ota update that was originally posted on another thread (which i can't post on since im the new guy. I rooted and unlocked using odin as described and wanted to get samsroms cleanrom1 but need to be on the J1 base. Can't seem to find it so any help would be appreciated. Thanks a ton.
Look on page 4 in the OTA for another link
Sent from my SCH-I535 using XDA Premium HD app
Yeah i had tried that last night and just saw a bunch of folders and files... none that matched the mp5 . Am i doing something wrong? It doesn't seem like the same process i had to do before.
So the original post says to copy Patch to device then flash it from recovery. Do i save the whole folder to the sdcard or just the patch file or what. Im still unsure this is the correct download. Has anyone confirmed it? Thanks
Sent from my SCH-i705 using xda app-developers app
You download the 'J1 OTA Update - Pre-Rooted.zip' to your SD Card and flash it in CWM... You don't do anything to any folder or file. Don't open the 'J1 OTA Update - Pre-Rooted.zip'. Just download it to your SD card and flash it.
Gotcha, thanks for the help. You guys are great. Keep up the good work and Merry Christmas!
Sent from my SCH-i705 using xda app-developers app
Did Samsung send it back...I had to send mine in a week ago and I'm still waiting
Sent from my Galaxy Nexus using xda premium
So I have an old Infuse that my kids use and it went crazy the other day. Not sure what happened. Long story short I keep getting a boot loop at the ATT screen. This phone is not rooted and I'm not sure if it was on Froyo or GB. I've flashed every return from brick I can find on XDA. I'm using Odin and I'm pretty familiar with flashing/rooting etc. Can't figure this one out. The only thing I can think is the boot loaders are not the correct ones? Not sure, I keep seeing GTG's ultimate unbrick but all the links I get to it don't work. this is the only thing I haven't tried. Any help would be appreciated.
Edit to add: After I flash in Odin it goes to reboot then does the open update, verifying update, installing update, successfully installed update package.
Copying media files it says failed to mount/sdcard, can't mount /sdcard your storage not prepared yet please use UI menu for format and reboot. ??? I think that's the problem. How do I fix??
Just search in the stickies for bootloaders. That will solve your problems
Sent from my SGH-I997 using xda app-developers app
COfatboy said:
So I have an old Infuse that my kids use and it went crazy the other day. Not sure what happened. Long story short I keep getting a boot loop at the ATT screen. This phone is not rooted and I'm not sure if it was on Froyo or GB. I've flashed every return from brick I can find on XDA. I'm using Odin and I'm pretty familiar with flashing/rooting etc. Can't figure this one out. The only thing I can think is the boot loaders are not the correct ones? Not sure, I keep seeing GTG's ultimate unbrick but all the links I get to it don't work. this is the only thing I haven't tried. Any help would be appreciated.
Edit to add: After I flash in Odin it goes to reboot then does the open update, verifying update, installing update, successfully installed update package.
Copying media files it says failed to mount/sdcard, can't mount /sdcard your storage not prepared yet please use UI menu for format and reboot. ??? I think that's the problem. How do I fix??
Click to expand...
Click to collapse
If you'd like to try GTG's Ultimate Unbrick, you can find a working download here:
http://forum.xda-developers.com/showpost.php?p=22404446&postcount=391
Tried everything and no go. Not sure where to go from here. Sure seems like a hardware issue.
COfatboy said:
Tried everything and no go. Not sure where to go from here. Sure seems like a hardware issue.
Click to expand...
Click to collapse
You mentioned it's boot-looping at the Samsung logo - perhaps there's an issue with the power button.
Here's a couple of threads that may be helpful:
http://forum.xda-developers.com/showthread.php?t=2107558
http://forum.xda-developers.com/showthread.php?t=1996709
prairied0gg said:
You mentioned it's boot-looping at the Samsung logo - perhaps there's an issue with the power button.
Here's a couple of threads that may be helpful:
http://forum.xda-developers.com/showthread.php?t=2107558
http://forum.xda-developers.com/showthread.php?t=1996709
Click to expand...
Click to collapse
It goes past the Samsung logo screen then to the ATT Rethink Possible screen then keeps looping on that screen over and over. It charges normally also.
COfatboy said:
It goes past the Samsung logo screen then to the ATT Rethink Possible screen then keeps looping on that screen over and over. It charges normally also.
Click to expand...
Click to collapse
I would try flashing just a kernel (not the whole unbrick package). I have been in a similar situation and after trying everything imaginable that's what ended up fixing it for me.
Sent from my SGH-I997 using Tapatalk 2
prairied0gg said:
I would try flashing just a kernel (not the whole unbrick package). I have been in a similar situation and after trying everything imaginable that's what ended up fixing it for me.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Tried that earlier I thought, tried again just to make sure. Still no go. I appreciate all your help! :good: I'm gonna give up for tonight anyways.
COfatboy said:
Tried that earlier I thought, tried again just to make sure. Still no go. I appreciate all your help! :good: I'm gonna give up for tonight anyways.
Click to expand...
Click to collapse
This happened to me earlier. What I did was-
1 Went to full stock using heimdal one click, After completetion, U may stuck in bootloop in at&t as you said
2 Flash efs.zip found in the link below using odin. put efs.zip in odin and untouch any other setting and flash, (Ur imei may be previously corrupted so u got bootloop). This doesnot do any harm. So flash with confidence. If ur device doesnot show up in odin after u flash with heimdal one click , reinstal drivers with kies mini
Link for download http://forum.xda-developers.com/showthread.php?t=1729838
3 Now u'll be out of AT&T bootloop if ur imei was previously corrupted.
I was in similar situation. And this solved my proble.
Hit me thanks if I helped you :good:
Thanks for all the advise. Still not working. Tried everything above and much more. Different things I do give different results but pretty much the same in end. Either sticks in recovery or boot loops one way or another. Really don't see how this could be related to software but you never know I guess.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Here's the story:
I got excited about the bootloader vulnerability (Loki) being released, and I saw that a few devs had updated their ROMs to work with Loki so I decided to give it a shot.
The easiest, fail-free way of installing a recovery was to install TWRP through goomanager. I had only ever used CWM, but I figured it couldn't be that difficult to learn/use. And it wasn't, I'm just dumb. I went to wipe my S4 and I misunderstood what I was supposed to do and ended up formatting the phone instead. On CWM, this is normal and basically just means factory restore, but on TWRP this wipes everything, including the OS. This might not have been as big of a problem if that wipe hadn't just erased the ROM I was intending to install.
Long story short, with no OS on the phone, I was stuck on the Samsung boot screen and I could not even get into recovery. I tried ODIN restoring the stock firmware twice, but despite the fact that ODIN said "SUCCESS", my phone was in the same state. After panicking for a couple of hours :crying: and trying different things (including just leaving the phone alone for a while in hopes that I would come back and it would be magically fixed) I downloaded Kies. I figured, Kies comes directly from Samsung. If there's a way to fix my phone, this has to be it.
I did the emergency firmware recovery, and it took forever and when it was done it looked like I was going to end up right where I started, when after about a minute of the Samsung boot screen, I saw the heavenly blue-purple swish of the boot animation. :victory:
tl;dr: I thought I bricked my phone. I brought it back to life with Kies.
That's my story. Hopefully it'll help someone who is panicking that they just borked their new phone and helps them restore it.
I'm sad to say that I also wiped a phone with TWRP. It wasn't an S4 and I didn't need Kies.
I had no idea that it would delete the OS - I don't think there was even a warning.
What ROM were you going to use that supported Loki?? I can't seem to find one anywhere...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
drucquerkellan said:
What ROM were you going to use that supported Loki?? I can't seem to find one anywhere...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
okzygen said:
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
Click to expand...
Click to collapse
OK thanks I'll try them in a little bit and report back here how it goes!
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
You can still mount to USB through recovery and transfer a ROM zip over and then flash it.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
okzygen said:
Here's the story:
I got excited about the bootloader vulnerability (Loki) being released, and I saw that a few devs had updated their ROMs to work with Loki so I decided to give it a shot.
The easiest, fail-free way of installing a recovery was to install TWRP through goomanager. I had only ever used CWM, but I figured it couldn't be that difficult to learn/use. And it wasn't, I'm just dumb. I went to wipe my S4 and I misunderstood what I was supposed to do and ended up formatting the phone instead. On CWM, this is normal and basically just means factory restore, but on TWRP this wipes everything, including the OS. This might not have been as big of a problem if that wipe hadn't just erased the ROM I was intending to install.
Long story short, with no OS on the phone, I was stuck on the Samsung boot screen and I could not even get into recovery. I tried ODIN restoring the stock firmware twice, but despite the fact that ODIN said "SUCCESS", my phone was in the same state. After panicking for a couple of hours :crying: and trying different things (including just leaving the phone alone for a while in hopes that I would come back and it would be magically fixed) I downloaded Kies. I figured, Kies comes directly from Samsung. If there's a way to fix my phone, this has to be it.
I did the emergency firmware recovery, and it took forever and when it was done it looked like I was going to end up right where I started, when after about a minute of the Samsung boot screen, I saw the heavenly blue-purple swish of the boot animation. :victory:
tl;dr: I thought I bricked my phone. I brought it back to life with Kies.
That's my story. Hopefully it'll help someone who is panicking that they just borked their new phone and helps them restore it.
Click to expand...
Click to collapse
all you have to do is boot to recovery, and push a rom through adb to your phone. I've done this dozens of times accidentally and the easiest way to avoid it is to keep a backup rom on your sd at all times
mcmb03 said:
all you have to do is boot to recovery, and push a rom through adb to your phone. I've done this dozens of times accidentally and the easiest way to avoid it is to keep a backup rom on your sd at all times
Click to expand...
Click to collapse
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
niceppl said:
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
yeah, either way kies was probably at the bottom of the list for solutions since you were trying to put a different rom on your phone anyways
niceppl said:
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
Or the easiest of the options that I already mentioned 4 posts up... Don't even need to bother with adb or taking off your back cover. Plug in, mount, click-and-drag file transfer, unmount, flash, done.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I'm just glad you got it taken care of OP. Hopefully this thread will help others who may have a mishap while flashing ROMs.
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
This is incredible. Incredible how badly you almost screwed yourself over with, and incredible that Kies was actually helpful.
I installed Kies to backup contacts, once. After that? Thing crashes on updates, takes 30 minutes to load, hated any music I threw at it, didnt like my wireless transfer setting....
idk I had a pretty bad experience with Kies, i'm glad to hear that program isnt all useless.
okzygen said:
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
Click to expand...
Click to collapse
Yea that part doesn't make sense though. Many times I've seen people try to boot out of recovery with no system and always be able to get right back into recovery. Not that I don't believe you, just saying it's weird. Which leads me to the guy above... he didn't really screw himself that bad, no danger of bricking at all, just needed a reflash.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Just FYI on Kies
Am not sure on windows pc, but on my imac adb does not work with Kies. Had to use the Kies uninstaller to get if off imac then use adb. Maybe this isn't an issue on all phones?
Just got s4, and coming from HTC One S. So, if this is old news, sorry--
okzygen said:
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
Click to expand...
Click to collapse
I'm pretty sure you have to wipe cache once you do odin in order to boot back in OS or else you'll just get stuck at logo
polish_pat said:
I'm pretty sure you have to wipe cache once you do odin in order to boot back in OS or else you'll just get stuck at logo
Click to expand...
Click to collapse
I'm curious, is there a way to do this in download mode (via Odin or otherwise)? As far as I know, I can only do that through recovery. Do I have to adb and wipe /cache?
Sent from my SGH-I337 using xda app-developers app
okzygen said:
I'm curious, is there a way to do this in download mode (via Odin or otherwise)? As far as I know, I can only do that through recovery. Do I have to adb and wipe /cache?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
i do it thru recovery, thats always how it worked for me. You cant do it thru adb since you need root to do that and odin wipes root
okzygen said:
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
Click to expand...
Click to collapse
OK I installed the AOKP one and it works like a charm. Only thing is NFC doesn't work so once that works it will be pretty Much perfect
Sent from my SGH-I337 using Tapatalk 2
jasbur17 said:
I'm sad to say that I also wiped a phone with TWRP. It wasn't an S4 and I didn't need Kies.
I had no idea that it would delete the OS - I don't think there was even a warning.
Click to expand...
Click to collapse
Yeah me too, was and still am not happy about it. Should gave stuck to CWM. TWRP is a cool recovery, as long as you realize what you hit.
Glad Kies worked! Now that I have an Att phone I can utilize it again. Wouldn't recognize my International SGS3, so Kies was useless.
Sent from GT-I9505 transformed SGH-I337
I have the samsung galaxy s3 through verizon, purchased a few weeks ago. I rooted a couple of weeks ago using CWM and was running CM10. No problems until I decided to fix the camera issue everyone seems to be having. I thought I was flashing back to stock but when my phone restarted, I now have the yellow triangle and a screen that says "Unauthorized software found on phone take to a verizon store" blah blah blah. I can't get back into recovery, but I can get into download mode. I've searched this forum and google and have tried everything, flashing VRALEC, CWM, etc etc and nothing is working. I've been at it all morning and really don't want toadmit defeat and go to Verizon.
Can anyone please help? I can't unlock the bootloader until I can get my phone started. I'm trying to flash stock rom but it doesn't seem to be working. the file I am using is "VRBMB1_bootchain.tar.md5" is this not correct???
Thank you so much in advance!
MissJessa13 said:
the file I am using is "VRBMB1_bootchain.tar.md5" is this not correct???
Thank you so much in advance!
Click to expand...
Click to collapse
If you have just recently bought your phone, it is most likely the I535VRBMF1 boot chain found here http://hotfile.com/dl/233901611/1c99bd9/SCH-I535_VZW-I535VRBMF1_Original.zip.html restore to stock using Odin and begin anew.
philosoweed said:
If you have just recently bought your phone, it is most likely the I535VRBMF1 boot chain found here http://hotfile.com/dl/233901611/1c99bd9/SCH-I535_VZW-I535VRBMF1_Original.zip.html restore to stock using Odin and begin anew.
Click to expand...
Click to collapse
Thank you! I followed the directions found here: http://forum.xda-developers.com/showthread.php?t=1984436 and was able to get everything working, thank heavens!
Thank you guys so much for your help, I really appreciate it!