Database Info

Unlocking Bootloader

Hey I have tried everything to unlock the boot loader but i keep getting a error " Waiting for device" I even downloaded everything for AVD and SDK manager and changed USB ports. I was wondering if anyone can help me through skype or aim.
Thanks

looks like you don't have the proper driver for the one S phone

Sorry to barge in like this.
But since you were saying something like this maybe you can help me.
I am using an a Acer TravelMate 3200 windows xp.
What is the driver that I need to preinstall in the computer for me to use for later exploits like flashing,rooting for my xperia arc.
Sent from my LT15i using xda app-developers app

Sandro8771 said:
Sorry to barge in like this.
But since you were saying something like this maybe you can help me.
I am using an a Acer TravelMate 3200 windows xp.
What is the driver that I need to preinstall in the computer for me to use for later exploits like flashing,rooting for my xperia arc.
Sent from my LT15i using xda app-developers app
Click to expand...
Click to collapse
Im on a Mac running Windows 7.

Doughh said:
Hey I have tried everything to unlock the boot loader but i keep getting a error " Waiting for device" I even downloaded everything for AVD and SDK manager and changed USB ports. I was wondering if anyone can help me through skype or aim.
Thanks
Click to expand...
Click to collapse
Tried putting your phone in fastboot?

you need to put the phone in fastboot and have these fastboot files downloaded on your computer
http://www.mediafire.com/?50baad8rykng2j0

Have you tried the AIO?
http://forum.xda-developers.com/showthread.php?t=1604677
[TOOL] HTC One S All-In-One Toolkit V1.1 [6-11-12] [PERM ROOT][Noob-Proof]
Sent from my HTC One S using Tapatalk 2

O0cynix0o said:
Have you tried the AIO?
http://forum.xda-developers.com/showthread.php?t=1604677
[TOOL] HTC One S All-In-One Toolkit V1.1 [6-11-12] [PERM ROOT][Noob-Proof]
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Just tried AIO. Finally unlocked the bootloader! Now im confused on what to do lol..

if you have root then all that's left is to boot up into recovery (volume down and power then select recovery from the bootloader) and flash a custom rom .zip file from your sd card. just be sure to follow all the installation steps for your selected rom (i recommened AOKP Jelly Bean, check my signature for the link if you like) and always ALWAYS wipe data/cache before installing a new rom. and happy flashing

Doughh said:
Just tried AIO. Finally unlocked the bootloader! Now im confused on what to do lol..
Click to expand...
Click to collapse
First things first you need to boot into recovery (I use Goo Manager for this; Im lazy like that. It will also install the TWRP recovery.) and make a backup of the stock ROM your running now and keep a copy on your PC. Some times the contents of the SD Card can be corrupted. If any thing goes wrong your going to need something to go back to.
Then depending on your needs (AOSP/Sence) location in the world (EU/US) and what kind of One S (S3/S4) you have; you want to pick a ROM that's suits your needs.
I would stay away from Viper for now at least till your more secure with flashing, there are some extra steps like flashing a different boot.img; which can soft brick your phone or worse.
Start with something like Axiom S, for all your Sence needs. Or CodefireX CM10 for AOSP. If you use TWRP for your recovery you won't have to fast boot flash the boot.IMG for the ROM you chose. But again this depends on the ROM you choose to use, some ROMs don't play well with TWRP.
But most of all read. And then read some more. And when you think you know what your doing read a little more. This device seems to be real finicky. What works on one might not work on a another.
Good luck, be safe and welcome to the One S Forums!
Sent from my HTC One S using Tapatalk 2

[Q] [SOLVED] Urgent! Status 7 when installing a ROM and wont install OTA

Hi,
i have a Xoom and it wont install any ROMS. It is a wingray model and it gets status 7 (symlink) when installing CM10 and errors when install Superuser.zip. It isnt recovery as GAPPS install. Its running CWM and i cant get the tablet to boot up. I also used HWI69.zip and restored the images and no its askes for a password? Wth? But I really want CM10 back on my tablet. I restored ALL the images. Can i get rid of this password screen?
Please help

It has a password screen. what does that even mean? is that encrpyted from the seller as I can ask the seller to put it in... What am i even meant to do?

weeo said:
Hi,
i have a Xoom and it wont install any ROMS. It is a wingray model and it gets status 7 (symlink) when installing CM10 and errors when install Superuser.zip. It isnt recovery as GAPPS install. Its running CWM and i cant get the tablet to boot up. I also used HWI69.zip and restored the images and no its askes for a password? Wth? But I really want CM10 back on my tablet. I restored ALL the images. Can i get rid of this password screen?
Please help
Click to expand...
Click to collapse
Boot into fastboot, then unlock it
Code:
fastboot oem unlock

Mjamocha said:
Boot into fastboot, then unlock it
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Hi,
Thank you for reply but I got it working. It's on 3.01 now but how do I root this properly and get it on CM10?

weeo said:
Hi,
Thank you for reply but I got it working. It's on 3.01 now but how do I root this properly and get it on CM10?
Click to expand...
Click to collapse
Universal Root
or
7Heavens Projekt

Mjamocha said:
Universal Root
or
7Heavens Projekt
Click to expand...
Click to collapse
It'll have to be 7heavens as the other one hasn't got a download link. File has been deleted
Thanks

weeo said:
It'll have to be 7heavens as the other one hasn't got a download link. File has been deleted
Thanks
Click to expand...
Click to collapse
The universal root - has the links witin the instructions. I just tried the links and they are valid.

Mjamocha said:
The universal root - has the links witin the instructions. I just tried the links and they are valid.
Click to expand...
Click to collapse
Have you got a rooted Xoom? Could you take me through the process as it never works for me
Sent from my Xoom using xda app-developers app

weeo said:
Have you got a rooted Xoom? Could you take me through the process as it never works for me
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
How far have you got? Have you unlocked the bootloader through fastboot?
Once that's done it's fairly easy. Just fastboot flash a custom recovery. I recommend Team Rogues recovery: http://forum.xda-developers.com/showthread.php?t=1235170
then reboot the device, but go into recovery before the device boots or the recovery is overwritten. To get into recovery: power on, 2 seconds later press the down button, then press the up button once you see 'Android Recovery'
Then flash the zip I have attached to root the device. Choose the JB one if you're on jelly bean, anything else, so honeycomb or ICS use the other one.
From there it's the same as any other device. Backup apps etc, make a nandroid, wipe data/factory reset, install CM10

matt4321 said:
How far have you got? Have you unlocked the bootloader through fastboot?
Once that's done it's fairly easy. Just fastboot flash a custom recovery. I recommend Team Rogues recovery: http://forum.xda-developers.com/showthread.php?t=1235170
then reboot the device, but go into recovery before the device boots or the recovery is overwritten. To get into recovery: power on, 2 seconds later press the down button, then press the up button once you see 'Android Recovery'
Then flash the zip I have attached to root the device. Choose the JB one if you're on jelly bean, anything else, so honeycomb or ICS use the other one.
From there it's the same as any other device. Backup apps etc, make a nandroid, wipe data/factory reset, install CM10
Click to expand...
Click to collapse
Oh ok. I'll flash that as I'm on honeycomb. Will report back if I get a status 7 again.

weeo said:
Oh ok. I'll flash that as I'm on honeycomb. Will report back if I get a status 7 again.
Click to expand...
Click to collapse
That's something to do with CM reads the device as XOOM but on stock a wingray is MZ604 so if I remember rightly that's what causes the status 7, to get around it, once rooted use a build prop editor to change your model to XOOM not MZ604. I think that's the way to get around it if my memory serves me well

matt4321 said:
That's something to do with CM reads the device as XOOM but on stock a wingray is MZ604 so if I remember rightly that's what causes the status 7, to get around it, once rooted use a build prop editor to change your model to XOOM not MZ604. I think that's the way to get around it if my memory serves me well
Click to expand...
Click to collapse
Thank you. So that's what a sym link error is?

weeo said:
Thank you. So that's what a sym link error is?
Click to expand...
Click to collapse
Don't me hold to it, but I seem to remember others getting status 7 errors and it was just to do with how the CM zip reads your device. You can also turn off script verification in android recovery. I think that was also another solution

matt4321 said:
Don't me hold to it, but I seem to remember others getting status 7 errors and it was just to do with how the CM zip reads your device. You can also turn off script verification in android recovery. I think that was also another solution
Click to expand...
Click to collapse
Thanks. Doing it now. Just install SU. Good luck with Gigatechworld... formerly known as Orion... BTW i know this as im your website owners friend.

weeo said:
Thanks. Doing it now. Just install SU. Good luck with Gigatechworld... formerly known as Orion... BTW i know this as im your website owners friend.
Click to expand...
Click to collapse
Glad you got everything working alright. Cheers. sweet! you know friends through xda or you actually know know him? if you know what I mean

matt4321 said:
Glad you got everything working alright. Cheers. sweet! you know friends through xda or you actually know know him? if you know what I mean
Click to expand...
Click to collapse
XDA. We've been friends for 2 years. I use to make ROMS for the ZTE blade. I think he started talking to me when I made HTC Sense with a few others on the blade. I have him the idea for Orion

weeo said:
XDA. We've been friends for 2 years. I use to make ROMS for the ZTE blade. I think he started talking to me when I made HTC Sense with a few others on the blade. I have him the idea for Orion
Click to expand...
Click to collapse
that's pretty awesome! I remember you over at modaco, used to be fairly active there as the zte blade has a big community there but the xoom has a bigger one here. how come you didn't come aboard with us on the blog?

matt4321 said:
that's pretty awesome! I remember you over at modaco, used to be fairly active there as the zte blade has a big community there but the xoom has a bigger one here. how come you didn't come aboard with us on the blog?
Click to expand...
Click to collapse
I was active a lot here too. Till I shut my account down. I already have my own website. That's where the idea was set off from.
Success, CM10 is booting on my Xoom .

weeo said:
I was active a lot here too. Till I shut my account down. I already have my own website. That's where the idea was set off from.
Success, CM10 is booting on my Xoom .
Click to expand...
Click to collapse
That's awesome!
Nice to hear you have CM10 running too, so much better than stock

matt4321 said:
That's awesome!
Nice to hear you have CM10 running too, so much better than stock
Click to expand...
Click to collapse
Thanks to you
Sent from my Xoom using XDA Premium HD app

[Q] TWRP + Clockwork ...now hard bricked?

Hi Guys,
I have a Verizon SGS3 with stock JB 4.1.1 and I was following the steps posted here ([GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 3/5***).
I got a little distracted and flashed both TWRP(1st) and Clockwork(2nd) but I still managed to successfully get to step 5 and root my phone and unlock boot loader.
Then I used clockwork and tried to install the liquid smooth 4.2 ( wiped cache and memeory etc) and after the rom installed and I selected reboot, and my phone was hard bricked. ie not response to any key and black screen, so no way to reload or restore anything. of course it was at the point I realized my mistake of flashing both.
I am going to JTAG the phone today, but I have a few questions,
My questions -
-was it because I had both TWRP and clockwork that caused this?
-if yes, how do I get rid of TWRP?
-I only want touchwiz and non of the other Verizon bloat, can you recommend a good stable rom.
thanks

What you have failed to realize that you don't have both recoveries you overwritten one when you flash the other. Believe it or not most if not all of Touchwiz ROMs are stable. The mistake came from the flashing of a custom ROMs as you failed to mention whether or not you have flashed the right Gapps for the ROM.

jmxc23 said:
What you have failed to realize that you don't have both recoveries you overwritten one when you flash the other. Believe it or not most if not all of Touchwiz ROMs are stable. The mistake came from the flashing of a custom ROMs as you failed to mention whether or not you have flashed the right Gapps for the ROM.
Click to expand...
Click to collapse
Thanks for the quick reply.
I did not flash gaaps. I thought I could do it after I got the liquid smooth 4.2 on it. Are you saying that I needed to flash the gaaps first before the liquid smooth?

Not flashing the gapps wouldn't "hard brick" your phone. You just wouldn't have the Play Store, Google Music, etc. OP, are you sure you're hard bricked? Because it's really difficult to hard brick this phone. The only way I've currently seen people HB their phone is by flashing something for the international S3. You can't get into recovery or download mode? Buy either holding Volume Up, Power or Volume Down, Power?

RCOVA said:
Not flashing the gapps wouldn't "hard brick" your phone. You just wouldn't have the Play Store, Google Music, etc. OP, are you sure you're hard bricked? Because it's really difficult to hard brick this phone. The only way I've currently seen people HB their phone is by flashing something for the international S3. You can't get into recovery or download mode? Buy either holding Volume Up, Power or Volume Down, Power?
Click to expand...
Click to collapse
none of the button combination have any response. I tried removing battery and waiting 5 mins and reinserting but nothing. My battery was at 80% when I flashed the liquid smooth and bricked it. When I plug in to the PC, the USB drivers no longer load so I cannot use ODIN.
I am out of ideas. Anything anyone can help would be appreciated. thanks

What is the name of the file you flashed?
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
What is the name of the file you flashed?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Liquid-JB-v2.2-OFFICIAL-t0lte

lloydteo said:
Liquid-JB-v2.2-OFFICIAL-t0lte
Click to expand...
Click to collapse
Well, that makes sense. You flashed the Galaxy Note 2 version. You need to flash d2vzw roms for our GSIII. Everything you did beforehand was presumably fine.
Sent from my SCH-I535 using xda app-developers app

lloydteo said:
Liquid-JB-v2.2-OFFICIAL-t0lte
Click to expand...
Click to collapse
And boom goes the dynamite.

RCOVA said:
And boom goes the dynamite.
Click to expand...
Click to collapse
Alright alright this is what you do. If the phone isn't hard bricked (which it may be since you flashed a GNII rom) you need to either try to boot into recovery (hold volume down and home at the same time, then hold power. When it vibrates, release the power and hold the other two until you get recovery) or ODIN (odin is the same, just hold volume up instead of down). Report back if you can boot into these and I will assist from there.

nrock2256 said:
Alright alright this is what you do. If the phone isn't hard bricked (which it may be since you flashed a GNII rom) you need to either try to boot into recovery (hold volume down and home at the same time, then hold power. When it vibrates, release the power and hold the other two until you get recovery) or ODIN (odin is the same, just hold volume up instead of down). Report back if you can boot into these and I will assist from there.
Click to expand...
Click to collapse
You have the button combinations reversed. Volume up puts your phone in recovery mode, volume down puts it in download (Odin) mode.

And he is hard bricked. He stated no response from any button combinations.

RCOVA said:
And he is hard bricked. He stated no response from any button combinations.
Click to expand...
Click to collapse
That is correct, there is not response from ANY buttons and my battery is confirmed charged. USB drivers unable to load when plug int o PC also.
Do you guys know of any good sites that lists the latest custom roms for verizon SGS3? I mean the correct and latest file names for the roms.
thanks

lloydteo said:
That is correct, there is not response from ANY buttons and my battery is confirmed charged. USB drivers unable to load when plug int o PC also.
Do you guys know of any good sites that lists the latest custom roms for verizon SGS3? I mean the correct and latest file names for the roms.
thanks
Click to expand...
Click to collapse
You can find them all here on xda. Just browse the Android Development and Original Android Development forums for the Verizon Galaxy s3 only. You'll find AOSP ROMs and all kernels in Original Android Development and Touchwiz ROMs and mods and other stuff in Android Development. Don't flash anything that isn't made for the Verizon Galaxy S3
Sent from my Verizon Samsung Galaxy SIII

lloydteo said:
That is correct, there is not response from ANY buttons and my battery is confirmed charged. USB drivers unable to load when plug int o PC also.
Do you guys know of any good sites that lists the latest custom roms for verizon SGS3? I mean the correct and latest file names for the roms.
thanks
Click to expand...
Click to collapse
Not that I know of besides xda and rootzwiki, just be more careful. When you download roms always look for the download links for "d2vzw" roms or that specifically state "Verizon GSIII" when the link isn't immediately on xda. Typically AOSP roms are the ones with multiple multi-carrier, multi-device download links so always check and re-check after downloading zips.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Not that I know of besides xda and rootzwiki, just be more careful. When you download roms always look for the download links for "d2vzw" roms or that specifically state "Verizon GSIII" when the link isn't immediately on xda. Typically AOSP roms are the ones with multiple multi-carrier, multi-device download links so always check and re-check after downloading zips.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks again for the pointers.
When I get my phone back today, I have decided to flash the Bean ROM. I read the instructions and have one question. What does STEP 1 mean when it says "pick the locked version?" Does he mean pick the locked ROM version? If someone can explain briefly it would be appreciated. thanks
Install Instructions:
Step 1-
Make sure u are unlocked or pick the locked version during flash
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom
Step 4-
Reboot and Enjoy! after first boot reboot if youre using a custom ui and not the stock one(fixed soon)

lloydteo said:
Thanks again for the pointers.
When I get my phone back today, I have decided to flash the Bean ROM. I read the instructions and have one question. What does STEP 1 mean when it says "pick the locked version?" Does he mean pick the locked ROM version? If someone can explain briefly it would be appreciated. thanks
Install Instructions:
Step 1-
Make sure u are unlocked or pick the locked version during flash
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom
Step 4-
Reboot and Enjoy! after first boot reboot if youre using a custom ui and not the stock one(fixed soon)
Click to expand...
Click to collapse
He's taking about your bootloader. If you chose to root and unlock your bootloader when you rooted your phone, you get the regular rom. If you chose to only root and not unlock then your bootloader is locked and you must flash the locked version.
Sent from my Verizon Samsung Galaxy SIII

lloydteo said:
Thanks again for the pointers.
When I get my phone back today, I have decided to flash the Bean ROM. I read the instructions and have one question. What does STEP 1 mean when it says "pick the locked version?" Does he mean pick the locked ROM version? If someone can explain briefly it would be appreciated. thanks
Install Instructions:
Step 1-
Make sure u are unlocked or pick the locked version during flash
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom
Step 4-
Reboot and Enjoy! after first boot reboot if youre using a custom ui and not the stock one(fixed soon)
Click to expand...
Click to collapse
Oh, long story short that's the ICS rom that he created in July. From July-August, we had a locked bootloader, which is what he's referring. Thi meant flashing roms required something with a Kexec boot sequence, but once the GSIII was unlocked in August his rom and every rom presently available requires you to have an unlocked bootloader.
That said, when you get your phone you will need to:
1) root
2) unlock the bootloader
3) then proceed from there, whether that's backing up your IMEI or flashing a rom, etc.
I thoroughly suggest his JB rom since there's active development on it. Beans JB rom was updated last week and has "Build 15 [04/21/13]" in the title.

joshua5683 said:
He's taking about your bootloader. If you chose to root and unlock your bootloader when you rooted your phone, you get the regular rom. If you chose to only root and not unlock then your bootloader is locked and you must flash the locked version.
Sent from my Verizon Samsung Galaxy SIII
Click to expand...
Click to collapse
Just got some bad news from the repair shop, they said that they cannot recover the phone. Any suggestions of a good shop that can recover the phone from a hard brick?
Also is this d2vzw_JellyBeans_B15 the locked or unlocked version? thans

lloydteo said:
Just got some bad news from the repair shop, they said that they cannot recover the phone. Any suggestions of a good shop that can recover the phone from a hard brick?
Also is this d2vzw_JellyBeans_B15 the locked or unlocked version? thans
Click to expand...
Click to collapse
Not sure about the shop thing but in the instructions for flashing that rom it says you must be unlocked. Which means you must have an unlocked bootloader. You do this by flashing SuperSU_Bootloader_FIXED.zip in recovery. That zip file is recommended for flashing when you're following the root guide and they have a download link for it.
Sent from my Verizon Samsung Galaxy SIII

Kies just saved my phone

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

Installing CyanogenMod onto TF300T

I've been trying to flash CyanogenMod using the instructions on their website for a good week or so in collaboration with a general search of the internet. So far all I've managed to do is soft brick my tablet multiple times.
Here are the problems I've seen so far
ClockworkMod Recovery doesn't work on this tablet anymore
TWRP should be able to install cyanogenMod but for whatever reason just wipes the whole of the system folder
I can't seem to find directions on how to manually install cyanogenMod anywhere on the internet (the stock asus rom can be flashed fairly simply using fastboot)
Sorry about not being able to post a link!
Has anyone been able to install CM10 on their TF300T and if so can they link me to the directions they followed?
Thanks!

Have a look in the Development forum
http://forum.xda-developers.com/showthread.php?p=44823836
Sent from my NookColor using Tapatalk 4

Thanks!
kozmo2k4 said:
Have a look in the Development forum
http://forum.xda-developers.com/showthread.php?p=44823836
Sent from my NookColor using Tapatalk 4
Click to expand...
Click to collapse
Worked like a charm in the way that it installed and I got the cyanogenMod boot screen to show up. Now I am thinking it is stuck on the boot screen and looping. Any ideas for a fix?

harend said:
Worked like a charm in the way that it installed and I got the cyanogenMod boot screen to show up. Now I am thinking it is stuck on the boot screen and looping. Any ideas for a fix?
Click to expand...
Click to collapse
Wipe Data, Dalvik, and Cache before flashing CM. Usually bootloops for me if not.

That did the trick!! Thank you so much! Now running android 4.3.1 on my TF300T!!!