[Q] Most common ways to brick a galaxy S4 - Verizon Samsung Galaxy S 4

Hey everyone,
So I'm pretty new to the weird and wonderful world of rooting and custom ROMs, and as part of my research I just wanted to learn about the most common ways to completely ruin your phone. So bring on the horror stories!

joethesupercow said:
Hey everyone,
So I'm pretty new to the weird and wonderful world of rooting and custom ROMs, and as part of my research I just wanted to learn about the most common ways to completely ruin your phone. So bring on the horror stories!
Click to expand...
Click to collapse
Don't drop it in the toilet when your texting in the washroom.

Check the pockets of the clothes you are washing.....I lost many gameboy games that way when i was a child
And dont update with low battery and dont turn off the phone during an update/flashing a rom

Be patient. Seriously. I remember the first time I was backing up in recovery I got frustrated and terrified that I messed something up after 2 minutes, and shut off the phone. Thankfully this was just during a backup, but I've heard plenty of brick stories of the "I don't think anything's happening after __ time, I'll just kill it it."
Also, READING IS FUNDAMENTAL. There are often silly nuances of your phone giving you some type of message and your left to pick a command. Often every other install sees the same message, and it isn't necessarily true that the right option looks like the right option.
Read and be patient.

Back everything up as you go. It's easy and quick and can save you loads of time and effort if something goes wrong. In my experience, when following instructions and proceeding carefully it's difficult to brick your device.
Sent from my SCH-I545 using xda app-developers app

I like to get drunk and flash stuff on the weekends though!
You know what I do when I buy a video game? If you guessed read the instructions then play the game, you're dead wrong! I jump right in and start killing stuff!
Anyways, my point is, sometimes I'll just miss a step, or not pay attention, and was wondering is it easy to get out of a jam like that? I've never worked Odin, but have some adb experience. Can I just Odin back to the stock image and restore a nandroid after I get a recovery back on it?
Sent from my Nexus 7 using Tapatalk 2

As someone may use this thread to commit warranty fraud it is being closed
Moral of the story is: Backup backup backup
Do not flash anything not specifically for your model and carrier unless VERY specific instructions are given by someone who succeeded
And on that same note READ READ READ

Related

[Q] So I'm finally about to root my phone, a few questions!

I'm finally rooting my phone after months of messing about waiting for an unlock
My phone is international model i9300 and I've been reading this guide: http://forum.xda-developers.com/showthread.php?t=1695238
Looks really good, well detailed should be very easy with the help of chainfire!
But I've still got a few questions
1) I think I can't back up my phone until it's rooted to get access to the system files, am I right in thinking when I'm rooted I can use CWM to make a full back up of the phone?
2) Once it's rooted what is a thing that you must not do? The phone was expensive and as these threads may be annoying to all of you I just need to know before I do anything silly so apologies for all the topics
3) I'm going to wait until JB is released for official ROMs, when it comes to flashing a new ROM do I need to unroot the device?
4) Can I remove bloatware with just the standard root? The amount is ridiculous, it fills up 2 whole pages of apps and 95% of them I haven't used and don't plan on using, ever. I'm sure if I ever needed to there will be an app for it
5) any other advice on keeping my phone safe would be great, I am just really really cautious with this kind of stuff lol. Technology is really fussy I don't want to brick my phone
Thanks to everybody who posts, you guys have helped me so much since I joined and I really appreciate it
UrbanDesigns said:
I'm finally rooting my phone after months of messing about waiting for an unlock
My phone is international model i9300 and I've been reading this guide: http://forum.xda-developers.com/showthread.php?t=1695238
Looks really good, well detailed should be very easy with the help of chainfire!
But I've still got a few questions
1) I think I can't back up my phone until it's rooted to get access to the system files, am I right in thinking when I'm rooted I can use CWM to make a full back up of the phone?
2) Once it's rooted what is a thing that you must not do? The phone was expensive and as these threads may be annoying to all of you I just need to know before I do anything silly so apologies for all the topics
3) I'm going to wait until JB is released for official ROMs, when it comes to flashing a new ROM do I need to unroot the device?
4) any other advice on keeping my phone safe would be great, I am just really really cautious with this kind of stuff lol. Technology is really fussy I don't want to brick my phone
Thanks to everybody who posts, you guys have helped me so much since I joined and I really appreciate it
Click to expand...
Click to collapse
Answer 1: Check the link in my description (Win 8 -help) and download the adb executables. Then (Using Windows 7/8) Press and hold shift + Right mouse button in the folder and open cmd.
Once in cmd type:
Code:
adb start-server
adb devices (To check if your phone is connected properly)
adb backup -f %Userprofile%\Desktop\ADBackup\backup.ab -apk -nosystem -noshared -all
That will backup your user apps, incase you do do something wrong
Answer 2: Yes, there are a few things you shouldn't do;
Flash a ROM without making a backup
Deleting partitons in the phones' root.
Deleting system apps (APKs), when you don't know what they do, or even what they are.
Flashing a ROM/kernel, that wasn't made for your phone.
Overclocking/undervolting your phone too much.
And there are a couple more, but I don't want to waist your time ^^
Answer 3: JB is already released. No, you don't have to unroot your phone, before flashing. In fact, you probably can't, because you need the recovery program, to flash the ROM.
Answer 4: Don't flash bad stuff, don't install apps, that are reported (i.e. viruses) don't flash ROMs and kernels, that aren't for your device. And last but not least: Only use Odin, if you really have to!
Hope I could help!
UrbanDesigns said:
I'm finally rooting my phone after months of messing about waiting for an unlock
My phone is international model i9300 and I've been reading this guide: http://forum.xda-developers.com/showthread.php?t=1695238
Looks really good, well detailed should be very easy with the help of chainfire!
But I've still got a few questions
1) I think I can't back up my phone until it's rooted to get access to the system files, am I right in thinking when I'm rooted I can use CWM to make a full back up of the phone?
2) Once it's rooted what is a thing that you must not do? The phone was expensive and as these threads may be annoying to all of you I just need to know before I do anything silly so apologies for all the topics
3) I'm going to wait until JB is released for official ROMs, when it comes to flashing a new ROM do I need to unroot the device?
4) any other advice on keeping my phone safe would be great, I am just really really cautious with this kind of stuff lol. Technology is really fussy I don't want to brick my phone
Thanks to everybody who posts, you guys have helped me so much since I joined and I really appreciate it
Click to expand...
Click to collapse
1) You are right
2) Do not unroot
3) Official JB is already available. Flashing using odin doesn't required unroot. Update via OTA or kies required unroot.
4) Read, read and read is the best way to prevent bricking your device.
Sent from my GT-I9300 using xda app-developers app
Thank you guys!
I did not know JB was released, I saw it come out for Poland but I received no notification on my S3.
Now I'm not quite sure in which order I should do things, shall I update to JB and then root?
Can anyone link me to a guide to update for the official JB, al my search results come up with old results with leaked firmware
so I use odin for the first flash and then use CWM from there on out
UrbanDesigns said:
Thank you guys!
I did not know JB was released, I saw it come out for Poland but I received no notification on my S3.
Its only the Poland release so far .
All the rest are the old leaks .
jje
Click to expand...
Click to collapse
UrbanDesigns said:
Thank you guys!
I did not know JB was released, I saw it come out for Poland but I received no notification on my S3.
Now I'm not quite sure in which order I should do things, shall I update to JB and then root?
Can anyone link me to a guide to update for the official JB, al my search results come up with old results with leaked firmware
so I use odin for the first flash and then use CWM from there on out
Click to expand...
Click to collapse
If you want a Jellybean rom with bloat removed, then download Checkrom http://forum.xda-developers.com/showthread.php?t=1738527 . It's a stock samsung rom, bloat taken out, rooted, and is ready for if you wanted themeing etc..
In his kitchen app (that comes with the rom) you can find a package with ALL the removed bloat for you to download and install (ota) but he's also separated them so you can download just the ones you want. Also in the kitchen you will find tweaks for changing the notification drawer toggles, changing the theme, different modems, kernels etc... And check in the kitchen now and again for any updates to the rom (as and when samsung release them)
It's all there and very noob friendly. It's the smoothest most stable stock rom I've tried.
So root your phone using odin (easiest method by far), pay for titanium backup and back up your apps, boot into recovery and make a nandroid, move them onto you exSd or computer, wipe your phone, install checkrom, download titanium again and restore your apps from it.
That's a good start for you, EVERYTHING you need to know has been asked and answered before, so just google or search XDA, it's all still relevant, and you won't go wrong.
I'm going to root it now, seems pretty straight-forward but I'll let you know!
Now I will be shortly rooted what's the best anti-theft to use?
edit: wow... that was possible the easiest thing I have ever done lol, i was expecting it to be hard but it's literally selecting a file and pressing start. it's so much easier then jailbreaking (easy as hell but this tops it for sure)
Just done a CWM back up I didnt expect it to take so long haha
In my opinion, Cerberus is the best anti-theft app out there. You can use for a week as a free trial, I'll bet you're gonna buy it after 15 minutes.
Note that no anti-theft protection will prevent a thief from actually using your phone. Within like 2 minutes of Googling, the thief knows that he can use Download mode to overwrite the firmware (including the "anti theft" app) and 5 minutes later he has done it.
I use one such app (Watchdroid) to find my phone when I have misplaced it and for family members to be able to locate my position through an sms in case of personal distress.
Sent from my GT-I9300 using xda premium
d4fseeker said:
Note that no anti-theft protection will prevent a thief from actually using your phone. Within like 2 minutes of Googling, the thief knows that he can use Download mode to overwrite the firmware (including the "anti theft" app) and 5 minutes later he has done it.
I use one such app (Watchdroid) to find my phone when I have misplaced it and for family members to be able to locate my position through an sms in case of personal distress.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I guess it just depends on who finds it, there should be a password for download mode that can't be overwritten
I'm going to have it on either way, it can't hurt
d4fseeker said:
Note that no anti-theft protection will prevent a thief from actually using your phone. Within like 2 minutes of Googling, the thief knows that he can use Download mode to overwrite the firmware (including the "anti theft" app) and 5 minutes later he has done it.
I use one such app (Watchdroid) to find my phone when I have misplaced it and for family members to be able to locate my position through an sms in case of personal distress.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Only a thief, who knows what he's doing will use Google. Idiots are more likely to throw the phone away, or give it back..
And Avast! Anti Virus has a lockdown feature, which forces GPS, WiFi/Data and number forwarding (Root), so my phone is pretty safe
I've just installed avast - cheers!
What happens if the SIM is replaced?
and how do I track the phone if it gets lost/stolen?
also in my notification bar it says "avast mobile security is protecting you" i renamed the app for obvious reasons like it suggested. it's pretty stupid if the app renames its self if only reported lost/stolen
UrbanDesigns said:
I've just installed avast - cheers!
What happens if the SIM is replaced?
and how do I track the phone if it gets lost/stolen?
also in my notification bar it says "avast mobile security is protecting you" i renamed the app for obvious reasons like it suggested. it's pretty stupid if the app renames its self if only reported lost/stolen
Click to expand...
Click to collapse
Check the anti-theft settings in the app. It lets you set up trusted numbers, so you can control your phone remotely, and you can set things up, like force GPS and Data on, that way the phone can tell you it's position..
familyguy59 said:
Check the anti-theft settings in the app. It lets you set up trusted numbers, so you can control your phone remotely, and you can set things up, like force GPS and Data on, that way the phone can tell you it's position..
Click to expand...
Click to collapse
I've done all that, I've enabled anti-theft stealth mode where it states it will remain hidden after my next reboot.
I rebooted the phone but to no avail. It keeps showing in the notification bar and anti-theft seems useless, I've set up a pin but anybody who saw my phone would see the app straight away and would just use google on "how to remove avast samsung galaxy s3"
i don't think a thief could do it themselves but any idiot can search keywords into google to find a solid result
UrbanDesigns said:
I've done all that, I've enabled anti-theft stealth mode where it states it will remain hidden after my next reboot.
I rebooted the phone but to no avail. It keeps showing in the notification bar and anti-theft seems useless, I've set up a pin but anybody who saw my phone would see the app straight away and would just use google on "how to remove avast samsung galaxy s3"
i don't think a thief could do it themselves but any idiot can search keywords into google to find a solid result
Click to expand...
Click to collapse
Yes, but not everyone knows what the avast! symbol look like, do they? I doubt you're going to find an XDA-Member would have stolen your phone, it will probably be an Asi, or someone really retarded.
And anyways, they'll get frightened enough, when the phone rights junk to the SD, locks itself up and sounds the siren, with a personal "greeting"..
Give it a go, if your phone gets stolen, there's always the police, they'll (hopefully) help you But that's worst-case-scenario..
familyguy59 said:
Yes, but not everyone knows what the avast! symbol look like, do they? I doubt you're going to find an XDA-Member would have stolen your phone, it will probably be an Asi, or someone really retarded.
And anyways, they'll get frightened enough, when the phone rights junk to the SD, locks itself up and sounds the siren, with a personal "greeting"..
Give it a go, if your phone gets stolen, there's always the police, they'll (hopefully) help you But that's worst-case-scenario..
Click to expand...
Click to collapse
No but I'd still like it hidden
Anyone with google and the least bit of experience or interest will just reflash the stock Samsungrom anyway, rendering all and any (including Samsung's own) anti-theft utterly useless.
(In many cases thiefs steal to buy drugs, the dealer will certainly know someone to "freshen" up the phone.
It's very useful for finding the phone though if you have misplaced it =)
Sent from my GT-I9300 using xda premium
UrbanDesigns said:
No but I'd still like it hidden
Click to expand...
Click to collapse
You could remove the icon by going into avast > Settings > Notification Icon > None
Hope this helps
Sent from my GT-I9300 using Tapatalk 2
d4fseeker said:
Anyone with google and the least bit of experience or interest will just reflash the stock Samsungrom anyway, rendering all and any (including Samsung's own) anti-theft utterly useless.
(In many cases thiefs steal to buy drugs, the dealer will certainly know someone to "freshen" up the phone.
It's very useful for finding the phone though if you have misplaced it =)
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
So you're saying if I left my phone on the bus or something and somebody picked it up and decided to be a thief they automatically are casual drug users who know dodgy people, all because they found my phone?
I don't see how it could be useful for finding a "misplaced" phone, what would you class as misplaced? If I left the phone under my bed or something and "misplaced" it surely avast! isn't going to show a picture of inside my house?

[Q] Help! I bricked my Verizon Note 2! (SCH-I605)

Great. I, like a dumbass, decided to try and root my new phone without a backup plan. I have had no luck using the XDA video, and now I'm stuck with the "Please select recovery mode in Kies" screen. Kies doesn't recognize it, and I have no way to restore the stock ROM. Is my only option to wait until a stock firmware ROM is released, like it was for sprint?
Based on the information we're currently provided with, I think it'd be safe to say you're screwed for now. Why you would even try to root a device that doesn't currently have any rooting methods is beyond me. You should definitely read up before you try anything you're not sure of.
The only other option you'd have at this point is taking the phone into Verizon, showing them the screen and telling them that this is how it has looked since it came out of the box. Although it's a lie, and you bricked it out of your own neglect, the reps can't really turn you away.
Can you return it?
Sent from my SCH-I605 using xda premium
I did some research, and nobody had any negative things to say about the rooting process, especially with all the videos and forums on it. I searched for how to root the Samsung note 2, versus the model number, which is different for different carriers.
MedicMillan said:
I did some research, and nobody had any negative things to say about the rooting process, especially with all the videos and forums on it. I searched for how to root the Samsung note 2, versus the model number, which is different for different carriers.
Click to expand...
Click to collapse
Every carrier is different. You must be new here.
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
MedicMillan said:
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
Click to expand...
Click to collapse
You will need to wait until the boot loader is unlocked to flash a rom, only way I can think of.
MedicMillan said:
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
Click to expand...
Click to collapse
At this point in time, you can't flash anything, you can't root, and there are no recovery images to return to stock with. You either have to wait it out, or try to exchange it at Verizon.
You can exchange, they will not know the difference
Sent from my SCH-I605 using Tapatalk 2
Just take it to Verizon play dumb and get it replaced. It's within the 14 days so it will be swapped on the spot. They wont/don't care what's wrong with it.
The suggestion of just return it to the store, they won't notice, is a really **** move and I'm not saying that in defense of Verizon. I'm saying it that it is things like that that in the end cause more harm to the end user than good. They up costs and add charges, create obscene policies, etc. It may not negatively impact you immediately, but when multiple people do this all over the country it adds up.
DaRkL3AD3R said:
The suggestion of just return it to the store, they won't notice, is a really **** move and I'm not saying that in defense of Verizon. I'm saying it that it is things like that that in the end cause more harm to the end user than good. They up costs and add charges, create obscene policies, etc. It may not negatively impact you immediately, but when multiple people do this all over the country it adds up.
Click to expand...
Click to collapse
I have to say I agree 100%. If people just used common sense, or read up a bit, situations like these could be entirely avoided.
MedicMillan said:
Great. I, like a dumbass, decided to try and root my new phone without a backup plan. I have had no luck using the XDA video, and now I'm stuck with the "Please select recovery mode in Kies" screen. Kies doesn't recognize it, and I have no way to restore the stock ROM. Is my only option to wait until a stock firmware ROM is released, like it was for sprint?
Click to expand...
Click to collapse
Check the development section. There is a leaked ODIN .tar file that you can flash. It is a prerelease, but at least you will have a functioning phone until a proper root/unlock solution is found.
bork.it.consulting said:
Check the development section. There is a leaked ODIN .tar file that you can flash. It is a prerelease, but at least you will have a functioning phone until a proper root/unlock solution is found.
Click to expand...
Click to collapse
This Odin file fails. It will not flash. Someone was trying to flash it last night with the same screen you are on.
just odin the stock image in the dev section and you will be back up and running...do not I repeat do not anybody try any root methods for the other gn2 variants!
http://samsung-updates.com/device/?id=SCH-I605
if it fails then your screwed until the latest odin image is release, which im sure wont be too long.
Nit3mare said:
I have to say I agree 100%. If people just used common sense, or read up a bit, situations like these could be entirely avoided.
Click to expand...
Click to collapse
I'm not saying that everyone should go flash happy, attempt to root without knowing what they are doing destroy their phones and take them back to Verizon then rinse and repeat the process. But there have to be a few that are a tempting to get root for everyone else there is bound to be some hard bricks. Should they be out 700, and that's kinda harsh.
Check out this link for a fixed brick....
http://forum.xda-developers.com/showthread.php?p=34862234#post34862234
mrlaigle said:
I'm not saying that everyone should go flash happy, attempt to root without knowing what they are doing destroy their phones and take them back to Verizon then rinse and repeat the process. But there have to be a few that are a tempting to get root for everyone else there is bound to be some hard bricks. Should they be out 700, and that's kinda harsh.
Click to expand...
Click to collapse
But with a little reading in the correct forum, people could avoid owning a $700 paperweight. It's really not that difficult, and any issues that arise from lack of research are due to their own ignorance. I can't feel sympathy for anyone who flashes blindly.
Nit3mare said:
But with a little reading in the correct forum, people could avoid owning a $700 paperweight. It's really not that difficult, and any issues that arise from lack of research are due to their own ignorance. I can't feel sympathy for anyone who flashes blindly.
Click to expand...
Click to collapse
I'm not disagreeing with you. If you do not know what you are doing or if this is your first time you shouldn't be attempting to root an un rooted device. But there will always be those guinea pigs...
Sent from my SCH-I605 using Tapatalk 2
This is exactly the reason why everyone else who follows commense is punished with locked bootloader.

How should I prevent bricks?

I have taken a recent interest in making roms, specifically ports for the note 2. Currently I only have one note 2 so what should I do in order to test my roms without bricking my phone?
Ps: If anyone knows of a good beginners guide for building roms that would be great but it is not my concern.
Thanks in advance.
Sent from my Galaxy Note 2
Leave it stock.
Best way? Read the OP/Intructions carefully. That's all. You will never brick your phone if you read the instructions. Also, if you feel uncomfortable doing something with your phone that may result in a brick, don't perform it. But there's always a way to unbrick a phone and you have a community that has your back so you're set for any bricking
Provided you're only flashing test roms and not kernels, it's pretty much impossible to brick. Just make sure you have a backup!
Sent from my SCH-I605 using Tapatalk 2
BennyJr said:
Leave it stock.
Click to expand...
Click to collapse
That's what I was thinking also.
I used to play around with building ROMs back in my Windows phone days (I don't have time to do that anymore) but I always kept a spare phone around for "bricking" purposes.
I don't think I would want to use my only phone as a test dummy for new ROMs (especially if you aren't REALLY experienced at it)
I think I'm going to try with my old samsung fascinate, It would be less of a hassle if I broke that phone.
Thanks guys.
Sent from my Galaxy Note 2
Don't be stupid. The only way to really brick a phone anymore is if you're being dumb and doing stuff beyond your knowledge. Knowing what you're flashing and making sure it is compatible with your phone will help. Also, don't flash anything in Odin unless you're restoring to stock (or unlocking).

[Q] Well. My curiousity led to a hard-bricked phone

Well. My curiousty led to a hard-bricked phone
It's definetly official. I am not going to install any more custom roms after this. To make my story breif. I aquired a motorola atrix 2 phone, and had read it could accomdate a custom rom, so I used a one click root method program and the program said it had done its job. I booted into the recovery and installed the rom, which ended in an infinite reboot. Great, so I read more on how to revert back to firmware using rsd lite. I did this, but the battery was dead. so I went out and purchased anther battery, attempted the restore, phone restart, then BOOM. it stayed black and now it wont come on. wtf.
Can any please recommend the proper cable I have to order to get the phone back working>?
Sunaj1 said:
Well. My curiousty led to a hard-bricked phone
It's definetly official. I am not going to install any more custom roms after this. To make my story breif. I aquired a motorola atrix 2 phone, and had read it could accomdate a custom rom, so I used a one click root method program and the program said it had done its job. I booted into the recovery and installed the rom, which ended in an infinite reboot. Great, so I read more on how to revert back to firmware using rsd lite. I did this, but the battery was dead. so I went out and purchased anther battery, attempted the restore, phone restart, then BOOM. it stayed black and now it wont come on. wtf.
Can any please recommend the proper cable I have to order to get the phone back working>?
Click to expand...
Click to collapse
Did you flashed rom with stock recovery?
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
Did you flashed rom with stock recovery?
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried to. Unless i acidentally downloaded the wrong file.
Sunaj1 said:
Yes, I tried to. Unless i acidentally downloaded the wrong file.
Click to expand...
Click to collapse
You should flash roms with custom recoveries that built for your device like clockworkmod or twrp recovery.
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
You should flash roms with custom recoveries that built for your device like clockworkmod or twrp recovery.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Yes, I am aware of that. The problem is now my phone is hard bricked and it wont turn on at all, not even to display an error message.
How can I fix this? whats that special cable That i need?
I would love to help you but I don't have the device and I think you should ask to your device's q/a forum. It will more helpful for you.
Sent from my Sony Tablet S using xda app-developers app
Sunaj1 said:
Well. My curiousty led to a hard-bricked phone
It's definetly official. I am not going to install any more custom roms after this. To make my story breif. I aquired a motorola atrix 2 phone, and had read it could accomdate a custom rom, so I used a one click root method program and the program said it had done its job. I booted into the recovery and installed the rom, which ended in an infinite reboot. Great, so I read more on how to revert back to firmware using rsd lite. I did this, but the battery was dead. so I went out and purchased anther battery, attempted the restore, phone restart, then BOOM. it stayed black and now it wont come on. wtf.
Can any please recommend the proper cable I have to order to get the phone back working>?
Click to expand...
Click to collapse
Hi, I guess you can use THIS LINK to try and fix your problem. Thank you for consulting the forums, and have a nice day.
ATkeneiville said:
Hi, I guess you can use THIS LINK to try and fix your problem. Thank you for consulting the forums, and have a nice day.
Click to expand...
Click to collapse
Thank you. But an experienced repair guy said my phone wasn't responding to neither the USB jtag or the fast boot. So my phone is dead forever? Should I start digging its grave?
Sure sounds this way, and you shouldn't be doing JTAG through the USB port anyway unless your phone is something special I've never heard of
But in truth rooting your phone won't damage it, it just gives someone the opportunity to do so. I'm a firm believer in rooting all androids so long as they read and understand what they are doing, its very hard to brick a phone if you know what you're doing
So although this phone may be dead forever (unless you find someone who for sure knows the proper way to JTAG it) then still consider rooting your next one, just be sure to completely understand what's going on, and try to stay away from one click roots, its hard to learn anything from this
Best of luck on your next phone
*side note, if you still have warranty and your phone is completely unresponsive chances are you will get your warranty exchange, just play dumb and say "I was playing angry birds and it just froze, now it won't turn on"
Sent from my Nexus 4 using Tapatalk 2
I wish I had warranty on this thing. I got it second hand from craigslist. However i've managed to acquire an HTC inspire 4G, what an upgrade from a motorola cliq xt! I would love to install jelly bean on this thing but after messing up the Atrix 2 i'm scared I will F*ck this one up too. I can never find clear and concise instructions on the internet. Every web page I visit, it seems to be someones personal way of doing it. Steps not mentioned, or instructions written for intermediate users. For example, Every video or piece of instruction i've watched on youtube regarding booting into the fast boot on the atrix 2, said something about holding volume up and power button upon booting and I would see something on the top of the screen. However that did not work, First I had to use the volume down and power button, then I would get to this fastboot screen where those recovery options werent available, from there I had to hold both volume buttons down and press the power button twice which would bring me to the recovery options screen. thats just one example, and even then for some reasons I didn't have all the recovery options the instructions spoke of... for example. Very annoying and frustrating. On a side note, is there anyone on this site who lives in the US that can unbrick my atrix 2? The guy who repair phones I took it to said theres a device for 250.00 bucks he's waiting to get that can unbrick any device. However he doesnt have the funds and had gotten laid off work. I am just having a hard time believing a simple soft user error could permanently damage my device forever and that as sophiscated as our technology has gotten there's absolutely no way to revive it.
demkantor said:
Sure sounds this way, and you shouldn't be doing JTAG through the USB port anyway unless your phone is something special I've never heard of
But in truth rooting your phone won't damage it, it just gives someone the opportunity to do so. I'm a firm believer in rooting all androids so long as they read and understand what they are doing, its very hard to brick a phone if you know what you're doing
So although this phone may be dead forever (unless you find someone who for sure knows the proper way to JTAG it) then still consider rooting your next one, just be sure to completely understand what's going on, and try to stay away from one click roots, its hard to learn anything from this
Best of luck on your next phone
*side note, if you still have warranty and your phone is completely unresponsive chances are you will get your warranty exchange, just play dumb and say "I was playing angry birds and it just froze, now it won't turn on"
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I can't attest to the videos you saw, but for most androids this is the best site with the most info, I only suggest being sure how to root before you do it, and to understand how the method works as well. When your not understanding this is when bricks happen.
I know it can be lots of reading and lots of questions but in the long run its worth the time
As for the JTAG equipment there are many who have it and you can easily spend less than 250 on getting the proper stuff.
Every logicboard is different so maybe this machine he speaks of has a wide variety of cables that come with it, but he's still paying too much
Anyway, most people seem to charge 50$ or so to JTAG it back, if that's more than the phone is worth to you just sell it on eBay for parts
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
I can't attest to the videos you saw, but for most androids this is the best site with the most info, I only suggest being sure how to root before you do it, and to understand how the method works as well. When your not understanding this is when bricks happen.
I know it can be lots of reading and lots of questions but in the long run its worth the time
As for the JTAG equipment there are many who have it and you can easily spend less than 250 on getting the proper stuff.
Every logicboard is different so maybe this machine he speaks of has a wide variety of cables that come with it, but he's still paying too much
Anyway, most people seem to charge 50$ or so to JTAG it back, if that's more than the phone is worth to you just sell it on eBay for parts
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Can you link me to clear and concise instructions on how to upgrade my 2.3.7 ( i think) to jellybean on an htc inspire 4g? and is there anyone here who can fix my phone that you know of?
HERE IS YOUR PHONES FORUM
you will find links to all the guides you need here, always read the stickies in each section, this tends to have the important info you need
then anything your not sure about should be asked in the proper place within this forum for the best answers
example, question on how to root should be asked in the how to root thread for best chance of a good answer, question on how to flash a new radio should be asked in a thread pertaining to this
im sorry but i dont know enough about your phone specificly to help further but hopefully the members in your device specific forum will
best of luck!

[Q] I call upon the dark powers of the XDA to help me fix my Kindle Fire HDX

Here's my problem XDA Gods:
I've recently made a huge mistake, I was %&$#ing around with roms for the HDX and with Hashcode's Safestrap and had my phone fully rooted with the ADB drivers installed on my pc. I was using the default rom slot to operate(Yes it's stupid, but I have problems working with under 8gb of space and it was working fine.). Through an accidental factory reset I managed to delete my safestrap backup and screw up the current Rom. So I went into safestrap and tried to flash a new rom which suddenly wouldn't flash correctly. So I did advanced wipe and cleared everything and rebooted the device whilst still set to bootup from the default rom slot. My Proceeded to then bootloop the grey kindle logo. In a panic trying to fix it, I did the factory reset by holding the volume and power buttons (Another stupid move in my game of life.). Now when I plug it into a PC it reads the device as MTP USB Device and proceeds to fail installing Drivers that I've already installed. Adb wont recognize the device and I'm currently attempting to reinstall all my drivers.
To Sum It Up:
* My Device Can't Boot Into Safestrap
* My Device Can't Boot Past The Kindle Gray Logo
* My Computers wont recognize the kindle and calls it an MTP USB Device and fails driver installation.
*ADB also rejects my love.
Dear XDA Gods, I pray to thee for divine help and request the speedy help of thy talents. Many goats I will sacrifice for any that will help. I have scoured the Internet looking for a holy answer and have stumbled only upon ADB fixes to which I cannot. Please look upon my request and help me fly through this terrible storm.
From what I understand...
...this is a brick situation. Not to be a debby downer but I found myself in the same situation. I spent countless hours in the XDA forums and beyond, read every Android Cowboy post (who knows his way around this issue), tried a fastboot cable (didn't work), and even looked for a way to JTAG the internal memory - all to no avail. My advice - if you can't get ADB to wreckonize, accept your fate and flaunt your expensive taste in paperweights because, indeed, the stakes of being a tinkerer are high.
zomblitous said:
Here's my problem XDA Gods:
I've recently made a huge mistake, I was %&$#ing around with roms for the HDX and with Hashcode's Safestrap and had my phone fully rooted with the ADB drivers installed on my pc. I was using the default rom slot to operate(Yes it's stupid, but I have problems working with under 8gb of space and it was working fine.). Through an accidental factory reset I managed to delete my safestrap backup and screw up the current Rom. So I went into safestrap and tried to flash a new rom which suddenly wouldn't flash correctly. So I did advanced wipe and cleared everything and rebooted the device whilst still set to bootup from the default rom slot. My Proceeded to then bootloop the grey kindle logo. In a panic trying to fix it, I did the factory reset by holding the volume and power buttons (Another stupid move in my game of life.). Now when I plug it into a PC it reads the device as MTP USB Device and proceeds to fail installing Drivers that I've already installed. Adb wont recognize the device and I'm currently attempting to reinstall all my drivers.
To Sum It Up:
* My Device Can't Boot Into Safestrap
* My Device Can't Boot Past The Kindle Gray Logo
* My Computers wont recognize the kindle and calls it an MTP USB Device and fails driver installation.
*ADB also rejects my love.
Dear XDA Gods, I pray to thee for divine help and request the speedy help of thy talents. Many goats I will sacrifice for any that will help. I have scoured the Internet looking for a holy answer and have stumbled only upon ADB fixes to which I cannot. Please look upon my request and help me fly through this terrible storm.
Click to expand...
Click to collapse
---------- Post added at 12:18 PM ---------- Previous post was at 12:04 PM ----------
Google "Setting Up Your Kindle Fire Tablet for Testing" there is an article that might help to get ADB up.
This may be helpful to try to get ADB working. Also, a fastboot cable might be worth a try, though I don't think it will work if you don't get ADB working. Did you modify build.prop? Delete any system files?
I am sure that there is a way to restore through QPST:
http://forum.xda-developers.com/showthread.php?p=49862146
but I lack the skills to complete this process
Thanks
Thanks for the speedey responses guys, I'll try the QTSP method when I have time, but still thanks. Any other help is good to.
Same happened to me also , and i contacted with Amazon Customer Service. I explained whole situation ( that i tried the install gapps and bricked it like you - same way - ) they offered me a replacement. Then they sent me a new Kindle.
If you cant do anything just contact with them and explain everything. They will help im sure about that.
They are the most amazing Customer Service i've ever seen in my life. Just 2 days , i got my new Kindle and sent bricked one back.
Also they sent me a email for return shipping expenses. I used it at UPS and did not paid any money for return shipping.
Aren't they amazing?
Really!?!?
squee9 said:
Same happened to me also , and i contacted with Amazon Customer Service. I explained whole situation ( that i tried the install gapps and bricked it like you - same way - ) they offered me a replacement. Then they sent me a new Kindle.
If you cant do anything just contact with them and explain everything. They will help im sure about that.
They are the most amazing Customer Service i've ever seen in my life. Just 2 days , i got my new Kindle and sent bricked one back.
Also they sent me a email for return shipping expenses. I used it at UPS and did not paid any money for return shipping.
Aren't they amazing?
Click to expand...
Click to collapse
So even after ""breaking the system"" I'll get my money back. I dont have a warranty by the way, and I got it in December. Will that effect anything.
zomblitous said:
So even after ""breaking the system"" I'll get my money back. I dont have a warranty by the way, and I got it in December. Will that effect anything.
Click to expand...
Click to collapse
I have to admit I went through something very similar to you with my first HDX. I wiped the system without fully understanding it and afterwards it was bricked with my computer being unable to recognize it.
I also spent quite a bit of time looking for a solution but ultimately it was far easier talking to Amazon about this and having them send a replacement. Now with my second HDX I didn't make the same mistake twice.
I didn't tell the truth though. I just said that after I powered it on one day it would get stuck on the boot screen and after a troubleshoot run through Amazon offered a replacement.
Good luck.
Fastboot & the system
lawnnewm said:
...this is a brick situation. Not to be a debby downer but I found myself in the same situation. I spent countless hours in the XDA forums and beyond, read every Android Cowboy post (who knows his way around this issue), tried a fastboot cable (didn't work), and even looked for a way to JTAG the internal memory - all to no avail. My advice - if you can't get ADB to wreckonize, accept your fate and flaunt your expensive taste in paperweights because, indeed, the stakes of being a tinkerer are high.
---------- Post added at 12:18 PM ---------- Previous post was at 12:04 PM ----------
Google "Setting Up Your Kindle Fire Tablet for Testing" there is an article that might help to get ADB up.
This may be helpful to try to get ADB working. Also, a fastboot cable might be worth a try, though I don't think it will work if you don't get ADB working. Did you modify build.prop? Delete any system files?
Click to expand...
Click to collapse
Well I did the advanced system wipe, I think I may have just wiped off all traces of a rom by formatting the system, I havent touched the build.prop or any file like that, only format. Also I'll grab a fastboot cable off ebay and give tinkering a try,
Thanks
zXiC said:
I have to admit I went through something very similar to you with my first HDX. I wiped the system without fully understanding it and afterwards it was bricked with my computer being unable to recognize it.
I also spent quite a bit of time looking for a solution but ultimately it was far easier talking to Amazon about this and having them send a replacement. Now with my second HDX I didn't make the same mistake twice.
I didn't tell the truth though. I just said that after I powered it on one day it would get stuck on the boot screen and after a troubleshoot run through Amazon offered a replacement.
Good luck.
Click to expand...
Click to collapse
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
zomblitous said:
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
Click to expand...
Click to collapse
Rubbish. A bad kindle is a temporary thing. Bad karma lasts a lifetime & even if you can work it off, it's on a sliding scale approximately 1000:1.
The worst thing you can do is panic. 99.999% of devices can be recovered. However, you greatly increase your chances of being in that screwed .001% statistically by panicking & doing things like factory resetting or rebooting.
Personally, after sitting down to think about it, I can say I have actually borked my device 23 times. Nearly every three times, it was a different issue, since I was recreating issues to find solutions for others. To this day, I still have my FIRST HDX. I even got the update, the one that nobody can reverse. Guess what? I'm rooted, have SafeStrap & GAPPS still, because I didn't panic.
When you screw something up, you have to walk away. 3 out of 4 times, if you react to an issue without planning & reasoning, you will only make things worse, particularly if you really have no idea what you are doing & how Linux, Android Bootloaders & firmware in general work together. You don't need to know every detail, but a basic understanding at the very least. Listen, I am by no means a developer. I am a butcher hack of a coder, but I am a mechanical engineer & so I approach everything methodically, especially when dealing with something I do not know. Knowing your limits can be the most important thing to know at times & when you have stepped outside of your knowledge base, reacting with a guess rarely goes good. Just ask all the folks leaving Las Vegas casinos without their money. The bottom line is that bad things happen when you panic & let fear take hold. Bad things happen when you think you know more than you do.
What also helps me, is that this is my NEWEST username (you used to be able to have multiple, for different devices, etc), which is from 2006. I am pretty sure my first login was from 2002, maybe early 2003. When I joined I didn't do anything other than lurk, read, ask questions & follow things that interested me in IRC for a year & a half. I never even posted for the first 9 months I was around. I used PM & IRC, then it was only to ask questions to things I could find answers too reading through the earlier posts. Again, there are brand new members that understand & have abilities in technology that far outstrip anything I'll ever comprehend. Just like there were over a decade ago. Find those people & become friends. Follow one of the tutorials on building a basic app or building a rom like CM or AOSP or any of the other open roms from scratch. You'll learn something new, I garuntee it & it will come in handy some day, even if it's just a hobby. Of course things are different at XDA these days. It used to be that EVERY member was here to learn how to do these things for themselves & to share the experience & what was learned. Now, you still have some of those types, but predominantly, you have members that are here just because they want someone else to make a theme, or mod, or fix for them & they have no desire to contribute.
At any rate, I don't have the time to keep up with all the bootloops & bricks these days. Right now, work is crazy busy & that is what pays the bills, so it takes precedence over everything else. I'll start answering PM's & taking a look at borked devices again when things slow down again, however, I think I could probably recover 8 out of 10 if I had it in my hands & so could you. For those of you unwilling to give up, I suggest you read around other forums, check out some of the qualcomm developer forums & find some of the very talented developers that participate in those communities too. Most of them WILL take the time, not necessarily to fix your problem, but to answer questions & even to teach you a thing or two, if you are sincere about wanting to learn & not just looking for the first sucker to fix whatever problem you have.
GSLEON3 said:
Rubbish. A bad kindle is a temporary thing. Bad karma lasts a lifetime & even if you can work it off, it's on a sliding scale approximately 1000:1.
The worst thing you can do is panic. 99.999% of devices can be recovered. However, you greatly increase your chances of being in that screwed .001% statistically by panicking & doing things like factory resetting or rebooting.
Personally, after sitting down to think about it, I can say I have actually borked my device 23 times. Nearly every three times, it was a different issue, since I was recreating issues to find solutions for others. To this day, I still have my FIRST HDX. I even got the update, the one that nobody can reverse. Guess what? I'm rooted, have SafeStrap & GAPPS still, because I didn't panic.
When you screw something up, you have to walk away. 3 out of 4 times, if you react to an issue without planning & reasoning, you will only make things worse, particularly if you really have no idea what you are doing & how Linux, Android Bootloaders & firmware in general work together. You don't need to know every detail, but a basic understanding at the very least. Listen, I am by no means a developer. I am a butcher hack of a coder, but I am a mechanical engineer & so I approach everything methodically, especially when dealing with something I do not know. Knowing your limits can be the most important thing to know at times & when you have stepped outside of your knowledge base, reacting with a guess rarely goes good. Just ask all the folks leaving Las Vegas casinos without their money. The bottom line is that bad things happen when you panic & let fear take hold. Bad things happen when you think you know more than you do.
What also helps me, is that this is my NEWEST username (you used to be able to have multiple, for different devices, etc), which is from 2006. I am pretty sure my first login was from 2002, maybe early 2003. When I joined I didn't do anything other than lurk, read, ask questions & follow things that interested me in IRC for a year & a half. I never even posted for the first 9 months I was around. I used PM & IRC, then it was only to ask questions to things I could find answers too reading through the earlier posts. Again, there are brand new members that understand & have abilities in technology that far outstrip anything I'll ever comprehend. Just like there were over a decade ago. Find those people & become friends. Follow one of the tutorials on building a basic app or building a rom like CM or AOSP or any of the other open roms from scratch. You'll learn something new, I garuntee it & it will come in handy some day, even if it's just a hobby. Of course things are different at XDA these days. It used to be that EVERY member was here to learn how to do these things for themselves & to share the experience & what was learned. Now, you still have some of those types, but predominantly, you have members that are here just because they want someone else to make a theme, or mod, or fix for them & they have no desire to contribute.
At any rate, I don't have the time to keep up with all the bootloops & bricks these days. Right now, work is crazy busy & that is what pays the bills, so it takes precedence over everything else. I'll start answering PM's & taking a look at borked devices again when things slow down again, however, I think I could probably recover 8 out of 10 if I had it in my hands & so could you. For those of you unwilling to give up, I suggest you read around other forums, check out some of the qualcomm developer forums & find some of the very talented developers that participate in those communities too. Most of them WILL take the time, not necessarily to fix your problem, but to answer questions & even to teach you a thing or two, if you are sincere about wanting to learn & not just looking for the first sucker to fix whatever problem you have.
Click to expand...
Click to collapse
Thanks for the pep-talk, I haven't even thought about giving up, and I don't really want to just get out the easy lying way. But sadly my problem is one of few and will take time even with the help of power techies. I really only have one option at the moment and that is to continue troubleshooting and ignore everyone who just says that i have acquired a taste in paperweights. And Thanks anyway, means alot when a member takes time just to cheer ya on.
zomblitous said:
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
Click to expand...
Click to collapse
Replacement was expediated by Amazon so in two days.
You have a limited warranty for a year. You just have to convince Amazon that your problem falls under that.
Edit: It's admirable to try and fix it yourself but in my opinion it's far too time consuming.
1 year then...
zXiC said:
Replacement was expediated by Amazon so in two days.
You have a limited warranty for a year. You just have to convince Amazon that your problem falls under that.
Edit: It's admirable to try and fix it yourself but in my opinion it's far too time consuming.
Click to expand...
Click to collapse
Well I have about a year then.

Categories

Resources