Related
Just picked up my G3, rooted and unlocked bootloader as soon as i got home. Downloaded one of the jelly bean roms and cwm, did a backup then flashed the rom. Everything looked fine but the screen went dark after the boot animation then nothing. Wont power up or reset using the power home volume combo. What the heck do i do now, thanks for any help.
Might be a stupid question, but have you pulled the battery?
Be more specific.
VZW GALAXY S 3 4G LTE
Do YOUR homework first
How about reading all the threads about unbricking. It certainly seems you did not read all the threads about rooting the phone. Do that too.
Finally, and I know this is not that helpful. Don't screw with a new phone. Use it at least for a month to make sure there are no problems with it.
That being said, there is plenty of information about how to handle your problem here in xda. Read all that and try what has already been posted before asking people to solve your self inflicted problem.
BTW when you do ask for help specify exactly what you did, with what script. I.E. don't ask someone to solve your problem without you taking the time to be very specific about how you got there.
pull the battery and go into recovery or odin and fix it.
Dead battery?
Sent from my Transformer TF101 using xda premium
Skubacb - Don't be a douche buddy. If you do not have any thing to add then shut the **** up.
With that being said I have been rooting phones for years, never had an issue when I couldn't get the phone to at least go into recovery. The phone is dead. Battery was fully charged and I have done a battery pull. It is a Verizon G3. I have read the unbrick articles but none explain if the phone will not boot into recovery. If someone could could just point me in the correct direction I would greatly appreciate it.
How did you actually do the flash? Odin? Some other way? As noted, more details are needed.
I flashed the new rom using Rom manager, went in to revovery and flashed it
jmill75 said:
I flashed the new rom using Rom manager, went in to revovery and flashed it
Click to expand...
Click to collapse
I don't believe rom manager is supported for our phone yet. U need to flash straight from recovery. That said I'm sorry I'm not sure where u go from here.
Sent from my SCH-I535 using xda premium
If you can't get into either recovery , or download mode you maybe SOL. However I would take this to IRC and see if someone can help on there. #verizons3 channel.
If the phone is under warranty, one other alternate solution is to take it into a VZW store and say it won't start. Of course I'd only go that route if I couldn't get it going any other way. On the plus side, your could at least confirm that battery didn't die on you.
Looks like you forgot to flash the insecure bootloader, buddy.
Sent from my SCH-I535
Rom manager is supported I flashed clockwork there And the 3 cm nightlies
Sent from my SCH-I535 using Tapatalk 2
Keep this discussion to technical solutions only, please. Leave gray area ethics out of it.
JMink said:
I don't believe rom manager is supported for our phone yet. U need to flash straight from recovery. That said I'm sorry I'm not sure where u go from here.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Completely incorrect.
mikeew83 said:
Rom manager is supported I flashed clockwork there And the 3 cm nightlies
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Me too, been doing it since 6.0.1.2
abissel22 said:
Looks like you forgot to flash the insecure bootloader, buddy.
Sent from my SCH-I535
Click to expand...
Click to collapse
I'm gonna go with this one (possibly). Did you unlock the phone? Sorry, did you say it won't boot into anything? Download/Odin mode? Recovery? Anything at all when you do the vol up/down, home key, and power button?
Idk if this would help but I'd order a downloader jig off ebay for a couple dollars and use that to see if it'll boot to recovery
Sent from my GT-I9300 using xda app-developers app
Me too
I went to turn on my Verizon SGS3 on this morning and nothing happened. I have not even rooted it yet. It was charged when I turned it off 5 minutes before that and even did a battery swap. Phone is completely dead. Will not turn on. I have had it since it first came out, so I called Verizon and they are over-nighting me a "like-new" one. I hope I don't hear more of these stories.
jmill75 said:
Just picked up my G3, rooted and unlocked bootloader as soon as i got home. Downloaded one of the jelly bean roms and cwm, did a backup then flashed the rom. Everything looked fine but the screen went dark after the boot animation then nothing. Wont power up or reset using the power home volume combo. What the heck do i do now, thanks for any help.
Click to expand...
Click to collapse
I had a similar issue. If you do the volume/home/power combo (try both volume buttons separately, i forgot which one worked) and hold them through the initial Samsung logo it should put you into download mode, where you can Odin back to stock. I used PureMotive's Unbrick method in the Dev section (I think) and it took all of 20 min. Just make sure to follow the directions carefully.
Sent from my SCH-I535 using xda app-developers app
Is there a difference is button sequence between recovery and download mode? (I thought it was the same thing)
Sent from my SCH-I535 using XDA Premium App
Hello, I have had a Samsung Galaxy S II LTE from Rogers for three months now and it suddenly stopped working after trying to make a phone call.
The firmware was the Gingerbread 2.3.6 I believe (The most current firmware before ICS for the SGH-I727R)
There has been a history of attemping to install Cyanogenmod 10, but I had Clockwork Recovery installed and I was never able to install Cyanogenmod 10 because it gave me errors.
So I used Odin and an official release from Rogers to restore back to Gingerbread.
A month later, this is where I am at.
Status:
I can boot as far as the Carrier logo before going blank and vibrating every 2 - 3 seconds
I can go into download and recovery mode for 5 seconds before being met with a quick flash of a blue screen.
The phone randomly vibrates when a battery is inserted, when it is being charged, or a combination of the two
The battery needs to be taken out and placed back in before attempting a normal, download or recovery boot.
I also do not know if Samsung can tell, as there is no Clockwork Mod or any left over roms or Superuser permissions.
What should I do? Thanks!
If you do a battery pull and reinsert it, does the phone start to boot on it's own without any button pushs
Sent from my SGH-I727 using xda premium
xbladeinc said:
Hello, I have had a Samsung Galaxy S II LTE from Rogers for three months now and it suddenly stopped working after trying to make a phone call.
The firmware was the Gingerbread 2.3.6 I believe (The most current firmware before ICS for the SGH-I727R)
There has been a history of attemping to install Cyanogenmod 10, but I had Clockwork Recovery installed and I was never able to install Cyanogenmod 10 because it gave me errors.
So I used Odin and an official release from Rogers to restore back to Gingerbread.
A month later, this is where I am at.
Status:
I can boot as far as the Carrier logo before going blank and vibrating every 2 - 3 seconds
I can go into download and recovery mode for 5 seconds before being met with a quick flash of a blue screen.
The phone randomly vibrates when a battery is inserted, when it is being charged, or a combination of the two
The battery needs to be taken out and placed back in before attempting a normal, download or recovery boot.
I also do not know if Samsung can tell, as there is no Clockwork Mod or any left over roms or Superuser permissions.
What should I do? Thanks!
Click to expand...
Click to collapse
You should read the stickies that people invested much time into helping.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
stoopendis said:
If you do a battery pull and reinsert it, does the phone start to boot on it's own without any button pushs
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Yes, it boots on its own. If I plug it in, it shows the battery icon for a moment and then goes to black.
xbladeinc said:
Yes, it boots on its own. If I plug it in, it shows the battery icon for a moment and then goes to black.
Click to expand...
Click to collapse
Sounds like a stuck power button. I'd try pushing it on and off a ton and see if that clears it. Reinserting the battery shouldn't do anything until you push the power button. If all else fails.... Bring it back.
Sent from my SGH-I727 using xda premium
stoopendis said:
Sounds like a stuck power button. I'd try pushing it on and off a ton and see if that clears it. Reinserting the battery shouldn't do anything until you push the power button. If all else fails.... Bring it back.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
I will keep on trying that. Any more ideas? Should I send it in to Rogers or send it to mobiletechvideos.com for their J-TAG service?
xbladeinc said:
I will keep on trying that. Any more ideas? Should I send it in to Rogers or send it to mobiletechvideos.com for their J-TAG service?
Click to expand...
Click to collapse
It's not bricked. This phone we have is notorious for power button issues... Not your fault.. Let Rogers deal with it!
Is there a Rogers store near by where you can take your phone?
Sent from my SGH-I727 using xda premium
stoopendis said:
It's not bricked. This phone we have is notorious for power button issues... Not your fault.. Let Rogers deal with it!
Is there a Rogers store near by where you can take your phone?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Yeah, I am going to take it there tomorrow. Would they be able to tell if I have previously rooted my phone before in this case? I know that it is an official firmware on here now, but still. Thanks for the help!
xbladeinc said:
Yeah, I am going to take it there tomorrow. Would they be able to tell if I have previously rooted my phone before in this case? I know that it is an official firmware on here now, but still. Thanks for the help!
Click to expand...
Click to collapse
Just show them how it starts to boot on it's own. They should recognize the issue. If the phone never fully boots they can't see what's on there. And if you've never used Odin then the flash counter has never been incremented.
Sent from my SGH-I727 using xda premium
---------- Post added at 05:06 PM ---------- Previous post was at 05:05 PM ----------
Btw... Your welcome!
Sent from my SGH-I727 using xda premium
stoopendis said:
Just show them how it starts to boot on it's own. They should recognize the issue. If the phone never fully boots they can't see what's on there. And if you've never used Odin then the flash counter has never been incremented.
Sent from my SGH-I727 using xda premium
---------- Post added at 05:06 PM ---------- Previous post was at 05:05 PM ----------
Btw... Your welcome!
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
I have used Odin a few times, but I cleared all my caches, reformated and etc. using Clockwork Recovery with ICS, then I installed the Gingerbread Rom. This was a month ago, so idk.
If I can't even get into it, then it should be fine. Right?
xbladeinc said:
I have used Odin a few times, but I cleared all my caches, reformated and etc. using Clockwork Recovery with ICS, then I installed the Gingerbread Rom. This was a month ago, so idk.
If I can't even get into it, then it should be fine. Right?
Click to expand...
Click to collapse
Right. You gotta start somewhere. Just claim ignorance...... You got the official update and bam!
Sent from my SGH-I727 using xda premium
xbladeinc said:
I have used Odin a few times, but I cleared all my caches, reformated and etc. using Clockwork Recovery with ICS, then I installed the Gingerbread Rom. This was a month ago, so idk.
If I can't even get into it, then it should be fine. Right?
Click to expand...
Click to collapse
Once they unstick that button they'll see everything. They might not care, if they do you'll be paying for a new phone.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
Once they unstick that button they'll see everything. They might not care, if they do you'll be paying for a new phone.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
The thing is about this is that I don't have it Clockwork Recovery installed nor is it rooted, so I don't know if they would be able to tell.
xbladeinc said:
The thing is about this is that I don't have it Clockwork Recovery installed nor is it rooted, so I don't know if they would be able to tell.
Click to expand...
Click to collapse
if you restored to stock w/odin then you are fine, it wipes over previous roms/recoveries/rooting and "no one" would be able to see that you had previously installed custom roms or that the phone was rooted.
using odin does "not" increase the flash counter, using certain modified stock firmware like k0anes stock rom which you would use odin to install would increase your flash counter, but thats from an old thread and no one else has made a odin flashable stock rom since then, all the latest recovery flashable roms(zip files) would not increase the flash counter.
you are good to go for warranty repair, maybe wipe your internal sdcard if you can and take out your sdcard
My phone is currently experiencing same problem as the OP. :crying: Please don't tell me bringing it back to Rogers is the only option. My 1 year warranty might be expired already.
A quick update. I went to the store and they said that they would take it. They tried to fix the button with an exacto knife. I wasn't ready to send it in yet so I waited a few hours. I tried again and I was able to boot it properly. So, there is nothing wrong with the software. To those who might be having the same issues, check your power button first before sending it in.
Thanks for the help!
xbladeinc said:
A quick update. I went to the store and they said that they would take it. They tried to fix the button with an exacto knife. I wasn't ready to send it in yet so I waited a few hours. I tried again and I was able to boot it properly. So, there is nothing wrong with the software. To those who might be having the same issues, check your power button first before sending it in.
Thanks for the help!
Click to expand...
Click to collapse
They fixed it.?.... With a exacto knife?
Sent from my SGH-I727 using xda premium
To Juude90
Hi I had a similar issue. I'ts most likely the power button. If you're willing to open up the device and clean the power button area try that.
If you're still under warranty, try to send it in for a repair.
Here is some info on my situation:
http://forum.xda-developers.com/showthread.php?t=1993616
Here is info that was helpful to me.
vincom said:
its 99% the power button, hearing it click is no indication thats its working as its an internal problem, theres 3 links to the problem in the "info" section in the "1 stop" sticky in my sig . taking it apart to get to the internal contact is one way to fix it, maybe the only way to fix it. if phone starts as soon as you put the battery in w/out touching any buttons then its a sticky/failed power button. warranty repair is also another solution
its 1% for a battery and/or battery contact problem
here are the links:
[INFO] Skyrocket randomly restarts and vibrates at 2 second intervals ...... possible sticky power button and solution
[INFO] Another thread with a bootloop problem
[INFO] Video of Skyrocket randomly restarts and vibrates at 2 second intervals />
Click to expand...
Click to collapse
I hope it helps.
stoopendis said:
They fixed it.?.... With a exacto knife?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Yeah, that's what I was thinking. I was wondering what the hell they were doing. It worked I guess, but sometimes it still randomly reboots. I will send it in when I have the time, I'm not in a rush.
Yeah, Rogers acted in an unprofessional manner.
Take it in to Rogers,
I just had mine serviced and returned from Rogers, No problems and free of charge.
I dropped it off to Rogers with TWRP recovery/CM10 still installed, and the reason it was broken was I used a screwdriver to remove my sim card and tore out the sim card slot from the motherboard. Totally my fault. Also, my skyrocket is a used one from ebay, no less. Did not get it new from rogers myself.
Rogers fixed, no problems or cost to me. Rogers kindly restored it to a rogers Firmware, which I promptly removed immediately.
Heeter
Hello all,
I recently rooted my Galaxy S3 only to have my Mic fail on me 2 weeks later... Very dissatisfied with my Samsung about that - even though I am loving the phone. Anyways, back to the issue. Verizon has agreed to send me a replacement and I have to send them mine back. The problem is that I know that if I send them a rooted phone they will not honor the warranty, and I am having a very hard time flashing the Verizon Stock rom.
More specifically, and to see if I am doing anything wrong.. I used ODIN to flash a custom rooted rom onto my phone which worked perfectly, and now I am once again trying to use ODIN in order to flash the stock rom which I downloaded from goo.im - the file that I am using is HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5
Simple steps - reboot into downloading mode -> check auto-reboot and reset time on ODIN and choose the file above under PDA. All works fine, the phone reboots and I get a PASS, and yet my phone is stuck on the Verizon 4G loading intro. I think that's what they call a soft brick.
The first time this happened, I flashed a different rom and the phone loaded properly but it had the open lock symbol under Samsung which I think means that it was unlocked.. Either way, it was not the unrooted and official stock rom which is what I need on my phone in order to keep my warranty. The file that DOES work is COMBINATION_I535VRBLJ1_I535VZWBLJ1_381038_REV09_user_low_ship(NO_WIPE).tar.md5
I have followed the above steps over and over again and I always get the same result - stock doesn't work, the other one does.
Any ideas? What could the issue be?
http://forum.xda-developers.com/showthread.php?t=1762709
Personally I would try the files found in section 5 of this thread.
According to Droidstyles guide before his recent edits, if it freezes on the boot logo after a successful Odin factory flash then you're supposed to pull the battery, boot into recovery, and do a factory reset. Try that.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
According to Droidstyles guide before his recent edits, if it freezes on the boot logo after a successful Odin factory flash then you're supposed to pull the battery, boot into recovery, and do a factory reset. Try that.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yes this works, also had this happen to me, and to boot to recovery just hold home+volume up+power button. It should work.
Sent from my SCH-I535 using xda premium
You should probably factory reset after flashing, for you don't want to be running a buggy phone.
Sent from my Nexus 7 using xda app-developers app
Use a full wipe version and this would not happen...part of the reason why i removed nowipe versions such as f2. But yes as slimsnoop said, data wipe /factory reset will fix that.
So I bought the s3 Verizon it was rooted and switched to cricket pre paid before my friend sold it to me he tried to root back to Verizon but of course he failed, is there anyway to get the phone completelyback to stock even though he switched providers cuz the phone is stuck on the activating part I'm no noobe at rooting just don't know much bout this phone
Sent from my LT28at using xda app-developers app
FhtmChandley85 said:
is there anyway to get the phone completelyback to stock even though he switched providers cuz the phone is stuck on the activating part I'm no noobe at rooting just don't know much bout this phone
Sent from my LT28at using xda app-developers app
Click to expand...
Click to collapse
Follow section 5 of Droidstyle's (the guy above you) guide. Click the link in his signature. I'm not sure about how this handles modified network configuration though, that's not something I remotely know anything about.
I thought there was a way to bypass the activation screen? On older phones, you could tap the four corners of the screen or something like that? Anyone ever heard that before?
Sent from my SCH-I535 using xda app-developers app
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
ryan9316 said:
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
Click to expand...
Click to collapse
You could take your phone back and tell them it won't boot etc.
If you can't get it to boot neither can they, so no-one will know it's been unlocked/rooted.
Some people will say this is fraudulent, but hey, if you can live with yourself who cares what anyone else thinks?
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
exad said:
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I saw this and will give it a try, thank you for the advice!
ryan9316 said:
I saw this and will give it a try, thank you for the advice!
Click to expand...
Click to collapse
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
mkalbarc said:
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
Click to expand...
Click to collapse
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
If the emmc controller isn't responding, it's worth even less than that.
Sent from my One X using xda app-developers app
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
mkalbarc said:
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
Click to expand...
Click to collapse
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
pside15 said:
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
Click to expand...
Click to collapse
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. the rom that I had flashed was the latest cleanrom. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
mkalbarc said:
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
Click to expand...
Click to collapse
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
pside15 said:
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
Click to expand...
Click to collapse
Funny thing about the One... I was thinking about getting it but after this issue I will never look at another phone that doesn't have a removable sd card...
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
3 words: Dropbox Camera Upload.
exad said:
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Very well said... I always get a little nervous when screwing with a new $500+ device.
Sent from my HTC One X using xda app-developers app
iElvis said:
3 words: Dropbox Camera Upload.
Click to expand...
Click to collapse
Thank you for the advice! I will remember that with my next phone.
I just use g+ to instantly upload my photos. Unlimited space is hard to argue with
Sent from my One X using xda app-developers app
phone not able to boot
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
anuj.sherawat said:
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
Click to expand...
Click to collapse
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
31ken31 said:
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks first of all I was on CMW, formatted the drive as computer prompted, lost the data but was able to flash the ROM and fastboot the boot image to phone.
Now only one problem the phone restarts and then goes to boot loop everytime I have to fastboot the boot image file.
DO I need to change the recovery and is there any way to by pass the fastboot process? Sorry for noob question
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