The Saga of my Razr Maxx HD - Android Q&A, Help & Troubleshooting

Greetings all,
I had a Razr Maxx HD for about two years. loved it. Then one day the date and time stopped syncing. I spent weeks trying to fix it, scouring the internet and tried every possible fix I could find; from fiddling with airplane mode, soft/hard resets, replaced the screen (found several people who claimed this fixed the problem) and I even went so far as to flash a Verizon ROM onto the phone I grabbed from the net. (VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml)
I've been using a backup phone for a while now but would really like my razr back. I have nothing to lose at this point so I'm willing to try anything. Assuming this is a software glitch and not a hardware problem, I would like to completely wipe out the phone. Like EVERYTHING. I don't need anyone to hold my hand but would appreciate it if someone could post some resources that I can read through/follow. Googling the topic brings up alot of info on unlocking and rooting. I feel like those are things I might want to do on a healthy phone that I just want more control over. I want to do the equivalent to my phone of what I'm familiar with on a PC. (format HDD/creating partitions/loading OS) Don't know if this is even possible with a cell phone.
Any help would be appreciated.
Edit: so my understanding of a Kernel is that it manages communications between the hardware and software. I have wondered if something went wonky with that and if I can flash a basic android kernel/OS onto my phone to see if it fixes the problem. Forgive me if I'm not using terminology right.

Related

[Q] Playing with my build.prop

If I play with my build.prop settings is there any chance of bricking my phone?
I fully intend on making a backup of the build.prop for when I inevitably mess it up, but I don't have a full system backup if I softbrick.
The reason I want to do this is that some of the Tegra 2 games won't work on my phone because they are "not available in my region". I think that is bs, and I think modding my build.porp will help. So I want to modify my settings to trick the game into letting me play.
On that note, could anyone tell me what settings to change? The 'region' setting is a no-brainer, but anything else? There are quite a few items that indicate KR or olleh (the provider).
DrNugu said:
If I play with my build.prop settings is there any chance of bricking my phone?
Click to expand...
Click to collapse
Worst case just flash a ROM
sent via tapatalk from my CM7 Atrix
btw - I'm stock gingerbread with root. I'm not really interested in ROMs (at the moment), I'd just like my phone to act like it's American <insert joke here >. Basically, I want it to tell the software that it is an AT&T phone in America, so that I don't get rejected because I'm in Korea. They have strange gaming rules and many hoops to jump through before a game can be released here. Hence my shenanigans.
If you have a knowledge of adb then you are fine. You can soft brick but not hard brick.
sent from my Atrix via XDA premium
N00B in N33D
Hey guys,
I've been searching and searching and I can't really find a way to fix this problem I've been having.
I have a Motorola Atrix from Bell running 2.3.6 and I had rooted it.
I got a little power hungry since this is my first android and therefore obviously my first root, and I started deleting stuff like crazy. Unfortunately one of those things was all of the yahoo system apps since I didn't look up if they were important or not, and they obviously were.
My problem is as an attempt to re-install all the yahoo files, I tweaked the build.prop file. I opened it as a text file and changed the ro.build.version.sdk=10 to ro.build.version.sdk=9, i think it was the 6th line of the build.prop text then I rebooted my phone.
I never made a backup or nandroid or anything like that, mainly because I didn't think anything that bad could happen from it. Then I ran multiple factory resets of my phone in hopes to fix this problem, but it still persists. All my phone does now is continously try to boot up, but it just keeps restarting itself halfway through, I can't get to the unlock screen or anything like that. I feel like I royally messed up my phone, if anyone could help me out with this it would be much appreciated.
I can run hard resets using the buttons and run things such as fastboot and RSD even though I dont really have much idea what they are. So I've been trying to educate myself a little with http://forum.xda-developers.com/showthread.php?t=1154600&highlight=soft-bricked+atrix and I'm finally starting to understand what I actually did to my phone.
Once again any help would be much appreciated, thanks, if you need any more information just let me know.

[Q] Got new phone, trouble rooting

So here's my story, I am not entirely new to rooting as I have successfully rooted my Motorola Droid, My Droid X2, My Acer Iconia a500 (twice), My aunts Lg something, and my mothers Kindle Fire.
So a few days ago my Droid X2 started acting up, and would go hours on end sometimes without working.
I was very happy to find out that Verizon would replace it with no hassle as it was less than a year old. I got the replacement yesterday and it's working great... that is until I found out it came stock with 2.3.5 right out of the box.
Now I have always trusted XDA forums and have used them for a long time (although I finally just registered today to ask this)
The only root method I can find is to downgrade to 2.3.4 and then root, then install voodoo root protector, then upgrade.
Now I saw a few things about possibilities of bricking your phone when trying to read those tutorials (I have never had to downgrade before) and I was a bit concerned.
I was mainly wondering, I don't care about loosing data on the phone. I have a backup sd card I can use if I need to format that, and like I said, the phone is new and actually doesnt have a single app I have installed on it yet.
Is there any easy way to go back down to 2.3.4 for my situation? I just got the free phone and don't want to brick it a day later you know?
From what I gather, you can SBF back down to 2.3.4 with no problem. There may be a certain way you have to do it though. I have never been on stock 2.3.5 so I cant tell you from experience. But Everyone says it's possible.
That's my question in a nutshell
Yeah, I read a tutorial about how to do it using RSDlite, which I downloaded to my comp.
Now what I'm cautious about is white file to use. One of the tutorials had one, now while I know a tiny bit about rooting I know NOTHING about flashing it back, I wasn't sure if there was a way that this could screw up my phone, as it seems everything tested is with a phone that had already been rooted, or if there is anything phone specific in that file, or even if it actually is an OTA original (I'd rather not mess around with anything customized right now)
Whatever is the easiest method for getting be back down, I know how to take it from there as I've done it before.
Thanks for the response though!
Excolo said:
Yeah, I read a tutorial about how to do it using RSDlite, which I downloaded to my comp.
Now what I'm cautious about is white file to use. One of the tutorials had one, now while I know a tiny bit about rooting I know NOTHING about flashing it back, I wasn't sure if there was a way that this could screw up my phone, as it seems everything tested is with a phone that had already been rooted, or if there is anything phone specific in that file, or even if it actually is an OTA original (I'd rather not mess around with anything customized right now)
Whatever is the easiest method for getting be back down, I know how to take it from there as I've done it before.
Thanks for the response though!
Click to expand...
Click to collapse
So you have never used an SBF file? If you would have used it on your broken Droid X2 when it wasnt acting right, it might have fixed your phone. An SBF file simply wipes everything of your phone (excluding your SD card) and flashes brand new software on it. The SBF files are provided by Motorola so its not like you are using something made by a dev and can break your phone easily. You should be able to use RSD lite to flash the 2.3.4 SBF file and you should be fine. But then again, I have never SBF'd from 2.3.5 to 2.3.4 personally so I would feel bad saying go ahead with no worries and something bad happen. So wait for someone else to respond first.
Thanks!
Thanks for that info!
Also, I doubt that would have fixed my old phone, it seems pretty much like a hardware issue. The screen will display static for hours on end (think like an old tv if you didnt have cable plugged in) I think it's a loose connection somewhere or something. I didn't bother to really troubleshoot it myself though because I was like "lets see if Verizon will give me a new one" and they did, and because they didnt have any "replacements" i got a brand new one, with a brand new battery, so I wasn't going to argue the fact
Anyway, if the file is from Motorola where can I get it? I saw on a verizon forum that they were not allowed to post it there (or is it "from motorola" in the sense it was leaked?)
Thanks for all your help so far, you've been great!
Excolo said:
Thanks for that info!
Also, I doubt that would have fixed my old phone, it seems pretty much like a hardware issue. The screen will display static for hours on end (think like an old tv if you didnt have cable plugged in) I think it's a loose connection somewhere or something. I didn't bother to really troubleshoot it myself though because I was like "lets see if Verizon will give me a new one" and they did, and because they didnt have any "replacements" i got a brand new one, with a brand new battery, so I wasn't going to argue the fact
Anyway, if the file is from Motorola where can I get it? I saw on a verizon forum that they were not allowed to post it there (or is it "from motorola" in the sense it was leaked?)
Thanks for all your help so far, you've been great!
Click to expand...
Click to collapse
Yeah, it does sounds like it was a hardware problem. Actually, I never thought about if motorola had a list of sbf files somewhere or if they were just leaked or what. I always downloaded them from threads like these. I just know they are made by motorola. You got me curious now. hmmm...
Duh
forget about my question as to where to get them, just saw the sticky at the front of this forum.
Although, it would be interesting to know if they were officially given out by motorola or leaked
Excolo said:
forget about my question as to where to get them, just saw the sticky at the front of this forum.
Although, it would be interesting to know if they were officially given out by motorola or leaked
Click to expand...
Click to collapse
What's An SBF File?
• SBF Is A File Leaked By Motorola That Is The System Image Flashed By RSDLite.
Taken from the Motorola Droid X2 FAQ page here
Excolo said:
So here's my story, I am not entirely new to rooting as I have successfully rooted my Motorola Droid, My Droid X2, My Acer Iconia a500 (twice), My aunts Lg something, and my mothers Kindle Fire.
So a few days ago my Droid X2 started acting up, and would go hours on end sometimes without working.
I was very happy to find out that Verizon would replace it with no hassle as it was less than a year old. I got the replacement yesterday and it's working great... that is until I found out it came stock with 2.3.5 right out of the box.
Now I have always trusted XDA forums and have used them for a long time (although I finally just registered today to ask this)
The only root method I can find is to downgrade to 2.3.4 and then root, then install voodoo root protector, then upgrade.
Now I saw a few things about possibilities of bricking your phone when trying to read those tutorials (I have never had to downgrade before) and I was a bit concerned.
I was mainly wondering, I don't care about loosing data on the phone. I have a backup sd card I can use if I need to format that, and like I said, the phone is new and actually doesnt have a single app I have installed on it yet.
Is there any easy way to go back down to 2.3.4 for my situation? I just got the free phone and don't want to brick it a day later you know?
Click to expand...
Click to collapse
bro, you wont have any problems downgrading/sbfing back to 2.3.4, i did it without any problems
i used sbf_flash through linux though idk about RSDLite

If You Bought a Used Android You Could Be Being Tracked!

I believe this information should be out there for all Android users and i dont recall seeing it anywhere but i hang out here right now and thought i would share what i discovered on accident.
i reference a RAZR M here but INSERT any Android phone as far as i can tell.
***please Devs and such i am not one so ignore my possible misuse of how exactly it operates but i just wanted to share the point of this not how the Android OS operates
i had a RAZR M with ROOT and installed Avast Mobile Security (i believe many others would do this as well) and since i was root i installed it as a /System app. this as some of you may not know makes it kinda part of the OS now. this means that a Factory Reset does not remove it but instead installs it again. i will explain how i discovered this:
- had a RAZR M as mentioned and i installed Avast as /System
- you can rename the app itself to whatever you want like "fletch33" and so anyone who finds your phone wouldnt know it was a security app and try to uninstall it. this is a great feature so i renamed it.
- this will do the standard stuff like locate your device, wipe it, make it beep, etc....
- i decided to give the phone to someone else and they wouldnt want root items or anything so i did a factory reset forgetting i had installed Avast as /System so they would have a clean start with the M
- since Avast was /System it became part of the Factory Reset process and so a what i thought was a clean fresh phone actually still had Avast on it but now since it was fresh and clean there were no signs like an app to remind me i had installed it as root. i honestly forgot it was on there.
- i had selected to get notifications of where the phone is if it traveled a distance but could see it whenever i wanted with a browser login to website and although i had reset it that STILL WORKS! i am getting emails when it moves and can login and see it.
- there are no visible signs that this is on the M (insert any phone)
- in my knowledge the only way the tracking etc... would stop is if i were to ODIN or SBF or whatever the equivalent is on that particular device or i would have to re-install Avast and it would then allow me to put in my passcode and then i could uninstall it.
the moral of the story is that any used phone could have had this done and if not by accident like mine but on purpose for whatever reason.
fortunately i gave the M to a family member and i will fix it for him but it really made me think what it could be used for ....
if this has been mentioned or i am incorrect i apologize in advance but when i started getting emails about where the phone i gave away was located all the time from Avast after a Factory Reset i decided i should share this so that others might take precautions with their second hand Android device.
1. I always Odin my phone and procedure to rooting with in a few short hours of owning device.
And if not, I'm pretty sure unlocking the device will erase everything. (in a lot of my previous cases)
2. And I see nothing wrong with the previous owner being able to track me picking up his wife and taking her back to the white house to make her my First lady
Yep, first thing I would do is wipe the phone properly.
"Factory reset" is a really bad name for the process...it does nothing of the sort.
Um, makes complete sense that you can still track the device. I assumed that before you even posted it. Same way you can track devices through android device manager, moto software, etc etc.
You're forgetting a huge oversight here.......it doesn't really do much good if stealing someones phone, then wiping it, would get rid of all tracking options. Kinda defeats the purpose. Otherwise people would steal someone's phone, factory reset, then go about their merry way and you're SOL...
TechSavvy2 said:
Um, makes complete sense that you can still track the device. I assumed that before you even posted it. Same way you can track devices through android device manager, moto software, etc etc.
You're forgetting a huge oversight here.......it doesn't really do much good if stealing someones phone, then wiping it, would get rid of all tracking options. Kinda defeats the purpose. Otherwise people would steal someone's phone, factory reset, then go about their merry way and you're SOL...
Click to expand...
Click to collapse
sure but since most Android phones dont offer a iPhone like recovery and most users dont even know what root it then to me its those people that should have concern.
i always ODIN or SBF etc.. myself if i pick up a used phone but most people woudnt even know about that.
Manufacturers should release iPhone like recovery system so that an average person can clean their phone without tech knowledge and downloading a file somewhere.

[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.

[Q] XT912 rooting help requested

Hi guys,
I'm trying to completely migrate off my old XT912 Razr Maxx that I haven't used as a phone in over a year, but still have app data on it that require me to use it periodically and want to move over to another device, probably my Ellipsis 8 tablet. In the last several months, I've also had to twice replace the battery after it ballooned on me on both occasions and it is starting to do it again. I tried to root the Razr Maxx using the one-click script for Windows a while ago, but I must have been using a crappy USB cable or connection as the phone crashed in the middle of it and reattempts produce a number of errors on the PC screen. I'm curious if anyone is willing to assist me in debugging the problem(s) since, while I am a professional software developer, I don't know much about the inner workings of the Android OS and am unable to dedicate the time to learn at the moment. If anyone is willing to assist me, please what do you need from me to get started?
Try this
http://forum.xda-developers.com/showthread.php?t=2855364
Sent from my Razr XT910
Thanks welder. It works like a charm.
How safe is it to leave installed on the old phone? It only sits in my basement and probably will be disposed once I completely migrate off of it, but Android is complaining about it constantly and I can't read what looks like Indonesian text in the app itself. Given today's anxieties about malware, I wonder if I should migrate and unroot as fast as I can.

Categories

Resources