Related
I am trying to put my Optimus S into emergency mode by following these instructions here: http://cheapcellunlockedphones.com/how-to-fix-a-bricked-lg-optimus-s/
I can not get it into e-mode for nothing. All I get is a black screen. Is there something I am missing?
Nevermind, I got it.
hm. well heres a try
it appears i cannot post to where this is most related...bricked p500h's optimus ones. phone number 3. koodo shall hate me but i will lie again and just say no turn on if noone has a solution. everytime its the update-openoptimus as the culprit, the flash after as per instructions with baseband(force close always occurs and thats the next step) fails and phone goes dead. no life. bricked. whats rather saddening is all the hundreds of posts i read here about people calling their phones bricked when they are in fastboot or emergency mode. hell life would be nice...little note to people. fastboot or emergency mode is NOT a bricked phone. phone going dead during a kdz flash and fail with NO SIGN OF LIFE afterwards is a bricked phone. im going to cry if i see someone else say. i haz yellow screen. ARRGH I BRICKED MY PHONE!!~! HAAALP OH YE WIZARDS OF XDA!!!
now..is there some trick to give this guy power aside from a charged battery and plug via ac or usb...some hidden little nub in this phone to hella reset the freakin thing? im not confident koodo gonna send another. although i will say i dont want a lg ill pay for an upgrade above n beyond. i just would prefer to make this work and say to hell with ciaoux (think thats how the young fella spells it) pretty rom...it worked the first time and thats why i want it its nice i liked it then phone bricked somehow. gone through two more tryin to get there. there has to be a way to give these phones some power tho...has to be! pls xda gurus: this is my first post and ive waited awhile for it. how to save p500h no boot no post.
cheers,.
proud champion of actual phone bricking.
sinner99 said:
now..is there some trick to give this guy power aside from a charged battery and plug via ac or usb...some hidden little nub in this phone to hella reset the freakin thing? im not confident koodo gonna send another. although i will say i dont want a lg ill pay for an upgrade above n beyond.
Click to expand...
Click to collapse
No. Just JTAG. Forget it, it costs more than a PCB change or even more than a brand new phone.
lol ill try my luck, 3rd replacement(if i was honest with them none of em woulda been outright replaced, but hey i was stupid enough to brick it 3 times, not gonna be so stupid to tell the truth what i did!) tomorrow am i call and say ***k lg! gimme a nexus s! 16gb internal. really ive fought gettin the one rom with 4gb sd-ext for internal memory, non issue if i persuade them with my charm. this is what i shall do. next up...lookup what jtagging is. ive meant to. guess now i will. thinkin without a thought its jtag=tagged for garbage. yanno when they take them in and theres no power. they have no real proof, not the provider i doubt. only on amce lg gets it they know whats was done..if that. fill me in if im wrong. im quite good at gettin **** for free from telus/shaw/any of them like outfits.
JTAG is a device that will flash the dead phone with a working firmware. You need to dismantle the phone and connect the JTAG to a connector on PCB. Yeah, Google it, but as said, expensive and totally not worth it unless you are doing the stuff for living.
totally not worth it..as in how much can these devices be. and how much or where would they maybe be found. i get **** cheaper then most ppl in most cases if the right places are sought out....imma server guy to be honest but lately ive had a pile of this phone stuff start piling up. ppl dont wanna pay much but somethin can be made for sure so maybe, thanks very much for the info i be keepin my ears to the ground! my buddy is tryin to figure the formulas used for imei > puk and imei > unlock. thatd be some handy info to have too. i got this one real nice arc.....nice. boneheads tried random net unlock codes like 200 times before i seen it. shoulda asked about that before i shelled out $5 for a code i had in 2 hrs. lol guess this isnt the place for this discussion tho....
koodos sendin another. easy enough. now. wtf does this rom upgrade to ciaoux's update-openoptimus keep pooching my phones for though. 3 tries.. 3 bricks, never on the actual rom upgrade...but afterwards always force close so i run fix permissions in recovery, followed by the v20g_00 baseband upgrade........this is where it fails everytime. i should note, in the past the lge virtual modem has been present but disabled as required, but not lately. its now always lge android usb modem....i dont think i disabled that guy.....maybe the problem? really leary about running any kdz or lpdm updater now for sure. to call in a 4th time in two weeks with a dead phone my provider is gonna sorta maybe start askin questions......im pretty sure. lol goddam i needa large capacity phone, i haz a 20tb server but only a 512mb capaacity droid phone. messed. ****.
honestly, i just wrote a giant essay on what happened and it all got deleted when i tried to submit it so im not very happy right now and dont feel like retyping it so ill just keep it short
i (tried) to format my sd card with the clockwork mod app (not recovery) but it failed and when i rebooted my phone was soopah doopah ultra mega bricked³, i believe is the technical term
it "boots" to a black screen when the battery is inserted and none of the buttons, capactive or physical, work and the only way to power it off is to pull the battery
my computer only picks up some qualcomm-usb-whatever drivers (been a while since i plugged it) which according to the internet has to do with some sort of qualcomm download mode
i was hoping to jtag it, because according to the internet, its the ultimate recovery tool, but i have no clue how to use it and cant find a good guide on the internet specifically for an evo or something related
i have a board coming, so now i need your guys help using it and getting the software i need to reload my evo
i just wanna do a 100% total restore of the entire system, since id venture to guess thats the easiest and probably only option at this point
I AM SOOPAH DOOPAH ULTRA MEGA GRATEFUL FOR ANY HELP YOU GUYS CAN PROVIDE!!!
note: i would have probably gone to sprint to get a new one a day later, but right now im deployed to afghanistan so even if there was a sprint store here i dont wanna have to set up an entire convoy and send ied clearance and all that good stuff
edit: drivers are called "QHSUSB_DLOAD" although i was pretty close to guessing the name, atleast i think so
Its not possible without usbjtag.
However, there was also another port that was being experiemented with on this phone, but I don't think anything every resolved.
It is possible. You can be our guinea pig. Search for a thread already about this. It's probably at the beginning, I remember we were going to use this to nand write, before we had root.
But it's just easier to buy insurance.
sure anything to fix this thing
i posted on it that im willing to be a test subject (http://forum.xda-developers.com/showthread.php?t=1188510)
i did have insurance... but i bricked it over here lolz
you mean usbjtag as in a usb jtag board or a subjtag nt from usbjtag.com?
if possible or you run outa luck you could try just sending it to HTC...
Seems others had this issue too.
http://forum.xda-developers.com/showthread.php?t=1041153
Guys phone was rooted and had this same issue and got a new one from HTC within 3days...
though if you get the thing to work right yourself more power to ya, and im sure the whole community will love to see it happen!
Keep us updated. Read up on that thread in here you posted in, in the Dev section that TrevE was workin on Download mode. Think he was gettin with RevSkills to use that stuff somehow. my memory is foggy though on all that since it was so long ago...
i would, but im deployed to afghanistan, so it would take FOR FREAKIN EVER to get it there and back
im gonna email htc and just say i randomly booted it and its giving me this problem and see what they say. im not expecting much but you never know
daktah said:
i would, but im deployed to afghanistan, so it would take FOR FREAKIN EVER to get it there and back
im gonna email htc and just say i randomly booted it and its giving me this problem and see what they say. im not expecting much but you never know
Click to expand...
Click to collapse
yeah. just was thinking b/c itd be with HTC that they'd have to have more options for places to ship it to for fixing than the USA for ya.
i dont even have the ability to send out mail where im stationed at and plus i think the community is close to finding a jtag restore solution (hopefully)
so i think ill just stick it out and not abandon my 1 and only 3d baby just because its in a coma right now (if you guys cant tell i freakin love this phone )
iwhenever i bootup my phone turns into colors then turns white and my computer wont recognize it. i am running blackstar x and am rooted. if anyone can help me i'd appreciate it. oh and i cant go into recovery but can access odin.
So just flash a rom with odin.
rangercaptain said:
So just flash a rom with odin.
Click to expand...
Click to collapse
Agreed....
and once the new image is pushed over to the device, you will need to boot once, then reboot into recovery and wipe all caches and data.
Otherwise, you will have dirty flashed, and you will have stability issues....g
I've never used odin I am reading up on it now as far as I can tell you can't flash zip files so do you know any good roms I can use for my galaxy note?
izdabombest1 said:
I've never used odin I am reading up on it now as far as I can tell you can't flash zip files so do you know any good roms I can use for my galaxy note?
Click to expand...
Click to collapse
Odin is used to push stock image files...
And they can be found in the super thread, at the top of the general section.
concentrate on getting a stock build running properly first, then we can worry about custom builds later.
Edit:
This is the thread, and inside will be the file you need:
Read carefully, and take your time on this...g
http://forum.xda-developers.com/showthread.php?t=1506330
gregsarg said:
Odin is used to push stock image files...
And they can be found in the super thread, at the top of the general section.
concentrate on getting a stock build running properly first, then we can worry about custom builds later.
Edit:
This is the thread, and inside will be the file you need:
Read carefully, and take your time on this...g
http://forum.xda-developers.com/showthread.php?t=1506330
Click to expand...
Click to collapse
well I ran loading and it came up with firmware upgrade in encounter in issue please select recovery mode in kies and try again so I will do the next I guess. but I can never get kies and the phone to connect.
can't get kies and phone to connect and i followed all the steps. what gives?
update: after 16 hours with kies decided to give odin one more shot on a different computer. she's back up and running! now to decide with what rom to go with. LOL. thanx guys for the help.
Kies is a fickle pig. Sometimes you're using the wrong cable or usb port.
rangercaptain said:
Kies is a fickle pig. Sometimes you're using the wrong cable or usb port.
Click to expand...
Click to collapse
wow this is unbelievable when it went to reboot and never came back on and it makes the Microsoft Windows keep asking you need to format a disk in drive D before you can use it so itslight turning itself on in 3 seconds in 3 to 4 second intervals. then the computer started loading drivers for a Qualcomm CDMA technologies MSM now where would that come from?
evidently from what i have gathered through many hours of reading and studying, i have hard-bricked my device. like i reported in previous post my computer will recognize it in short intervals. it continues to attempt to download drivers for Qualcomm CDMA.....but disconnects before finishing installing. one time ofter unplugging it left an icon that read.....oh i forget but i immediately looked it up and all reports from xda says that means a hard brick. called service provider and they are sending out new one but what happens when they recieve it and see that it has been rooted? i would really like to keep trying to save the phone i have. any suggestions?
If you are using files from our section, you must have the SGH-I717 device.
You mentioned CDMA. And although present in the chipset, this version of the note is a GSM device, and runs on the following networks respectively.
AT&T, BELL, ROGERS, TELUS, STRAIGHTALK, and carriers in far eastern countries....
Please link us the information on the Odin file you used to repair the device.
It appears you may have inadvertently pushed the wrong image. Perhaps for the N7000 ???
If that's the case, then the device will be hard bricked, and can be repaired using a JTAG repair service.
After you post the rom information, we will know for sure.
A general search for JTAG information will link you to several threads that talk about the service.
I'm sorry you are in this predicament, but for $50 U.S. dollars the device can be repaired.
I do not condone sending the device back under warranty, as it technically is not a defect, and is not the fault of Samsung or the carrier.
Good luck to you Sir.....g
gregsarg said:
If you are using files from our section, you must have the SGH-I717 device.
You mentioned CDMA. And although present in the chipset, this version of the note is a GSM device, and runs on the following networks respectively.
AT&T, BELL, ROGERS, TELUS, STRAIGHTALK, and carriers in far eastern countries....
Please link us the information on the Odin file you used to repair the device.
It appears you may have inadvertently pushed the wrong image. Perhaps for the N7000 ???
If that's the case, then the device will be hard bricked, and can be repaired using a JTAG repair service.
After you post the rom information, we will know for sure.
A general search for JTAG information will link you to several threads that talk about the service.
I'm sorry you are in this predicament, but for $50 U.S. dollars the device can be repaired.
I do not condone sending the device back under warranty, as it technically is not a defect, and is not the fault of Samsung or the carrier.
Good luck to you Sir.....g
Click to expand...
Click to collapse
first off I would like to say thank you for all of your guys help.how do I send a link from the Odeon file that I used?and I am pretty positive that it is hard brick.I do not want to be dishonest in I want to resolve this on my own.oops I mean with your help of course.
Simply copy/paste the link into your next reply.
then we can see the source for the file.....g
okay i took your advice and sent the replacement back. your right if i can't spend $50 to save my $600 phone i shouldn't start on this road. however as thorough as i usually am i am not very organized. i started installing upgrades and little modifications for my friends and family as a little hobby. then other people started asking me for this and that, so i would help them. so, i have downloaded a LOT of things to my computer (ROM's, MOD's,, etc.) for different android phones and from different forums (now i only use software from xda) and i rarely delete or uninstall anything. needless to say my computer started to look like a teenagers bedroom. i have now started to organize things so i can get a better grip on what i'm doing so i can take this more serious. with that being said i can't remember exactly what file i used to flash with Odin. is there some kind of log that is automatically kept by Odin?.....i have decided to try to use a phone jig to get my phone to at least turn on. is that a wise move? i am studying all there is available on the ins and outs of phone jigs. if that fails i will send off to be JTAG'd. if there is any advise or info that you feel i could use please send my way. thank you.
oh one more thing i do not own any windows phone software or cdma software, but i was connected to my friends nokia lumia 822 hot spot when i flashed my phone. and that's when it went dead and popped up as a cdma devise. could that have anything to do with it? sounds farfetched but so does alot of things that we are capable of doing nowadays.
The jig doesn't work for the note 1, so it's off to the JTAG guy.
ouch! can u plz send me a link i cant seem to find any. thank you.
www.mobiletechvideos.com
izdabombest1 said:
okay i took your advice and sent the replacement back. your right if i can't spend $50 to save my $600 phone i shouldn't start on this road. however as thorough as i usually am i am not very organized. i started installing upgrades and little modifications for my friends and family as a little hobby. then other people started asking me for this and that, so i would help them. so, i have downloaded a LOT of things to my computer (ROM's, MOD's,, etc.) for different android phones and from different forums (now i only use software from xda) and i rarely delete or uninstall anything. needless to say my computer started to look like a teenagers bedroom. i have now started to organize things so i can get a better grip on what i'm doing so i can take this more serious. with that being said i can't remember exactly what file i used to flash with Odin. is there some kind of log that is automatically kept by Odin?.....i have decided to try to use a phone jig to get my phone to at least turn on. is that a wise move? i am studying all there is available on the ins and outs of phone jigs. if that fails i will send off to be JTAG'd. if there is any advise or info that you feel i could use please send my way. thank you.
oh one more thing i do not own any windows phone software or cdma software, but i was connected to my friends nokia lumia 822 hot spot when i flashed my phone. and that's when it went dead and popped up as a cdma devise. could that have anything to do with it? sounds farfetched but so does alot of things that we are capable of doing nowadays.
Click to expand...
Click to collapse
A clean and reliable PC environment is at least as important as the proper files.
Maintenance is king on any file structure...
And while I feel badly that your device was damaged, I applaud your choice in sending back the replacement device.
People forget that when these phone manufacturers take back damaged product under warranty, they increase the price of new devices to maintain the same profit margin.
We pay at the register for others mistakes.
Again, thank you for your honesty, and integrity in this matter.
And don't worry, the device will return quickly, and will run like new.
We are always willing to assist users here through the lessons we have learned, and it becomes much more gratifying when we know the caliber of the user we help.
You have earned high marks for your choices today, and stand with the most reputable Members of XDA ....IMHO
Should you need anything upon the return of your device, consider it done ...g
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app
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
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.