Related
I don't know who's going to read this and/or if there will be any comments to it. I just want to take this horrible frustration and downheartedness out of my chest. I hope this will be of some help for anybody out there trying the same.
Today, I've hit what I hope will be the lowest most bitter point for me as an Android aficionado. Ever since the G1 was announced and came out, I jumped on the wagon and pre-ordered from Tmo (I was a customer at that time). As soon as I had it in my hands, I began learning about its customization, user experience, etc. I came here and learned how to root it (although I registered a bit later). I've owned four G1s, two G2s, an HTC Sensation and two Tbolts. All of them motivated me to dare tweaking and customizing more and more. Always with more or less satisfying results at the end, after overcoming the always present unexpected troubles. This time, however... I feel like I've got a pretty ugly dose of failure.
<s>I'll try to make it short.</s> My in-laws came from China. They had very old phones and wanted to get iPhones. However, the screen ended up seeming pretty small for them compared to my Tbolt. They asked me if I could help them get a good phone. I came up with a couple of choices. The HTC One X and the Samsung Galaxy S2. After thinking about it, I went for the S2. Now, it was a matter of picking the right (GSM) one. Either the ATT or Tmo version. I did more research and picked the ATT (I777) version, since "that's closer" to the international version.
I purchased two of them, still sealed, from Craigslist. I just loved them! Immediately, I purchased the unlocking codes for both. I got home and inserted a Tmo SIM to test them. I couldn't wait to hand them over to them. Then, things started to go just wrong in every way...
I was shocked to see the S2 had no Chinese option in language. The only Asian language available was Korean. At some point later, I realized that the Chinese options in my other phones were probably due to HTC being a Taiwanese company. I kept searching for an answer and ended up trying a couple of apps from the market like Morelocale2, etc. But they only translated about %30 of the whole. Failure.
I kept reading and learned I could flash a ROM with the language included. After more and more reading and rooting it, I had two choices. I could flash the Hong Kong or Singapore version of the phone. Those two come with the language already installed. Even though I don't know Chinese, I managed to get some help from a dev acquaintance and found the HK (I9100) version that even had the ICS version. I followed the tut and flashed it using Odin. When it booted it looked all good. Looking at that Chinese all over the place even made me smile. I sighed and said "I'm done"... little did I know my failure was far from avoided.
First of all, I learned that only two of the four buttons work due to the kernel. Only Back and menu work. I tried to see the good side. It'd be easier for them to get used to using only two buttons. I started installing more goodies, like Chinese input (by strokes, not by keyboard), even a wonderful app I found called Buttonsavior to replace the physical buttons. I was "done" and handed over the phone; only one of them. I wanted to be sure of the procedure to go, before doing the other. Then, I realized something horrific...
As they were trying the phone, poking menus here and there to become familiar with the UI; suddenly, while testing making a phone call, I heard that phrase: "It has no sound!" I wanted to kick myself out of my own disbelief... I thought "OMG! It was so hard hard to get a hold of that ROM. Now what?" I sadly understood I'd have to restore and go back to trying to find a solution to the partially translated gingerbread version. Then, I restored and went cold when I realized what had happened.
During the restoring, I was quite glad I had backed up in case of a disaster. When I booted up and just out of curiosity of how good the sound of the call was supposed to sound, I made a call. Guess what? IT DIDN'T WORK EITHER! This is when I started panicking! I thought "OK, I restored, now what?" I quickly did a wipe, factory reset, even unrooting back to the stock ROM. Did it work? No!! No audio call! "OMG!! The phone I just bought on Craigslist it's defective!"
I didn't give up and let that make me feel down (completely). I said "OK, after all this struggle and time, at least I'm going to make the other one work." I took the other phone and made a call to finally hear the quality of the audio call. It was very good to say the least. It was very nice and clear. At this point I started to feel half of an epic failure. In less than 5 mins the phone was rooted and being updated to the HK ICS ROM. I went as quickly as I could through the initial setup. I hit the home screen and the first thing I touched was the phone call icon, dialed and waited to see what the phone was supposed to be like. Then, the half failure, became full failure. I don't remember feeling that down for something before. I threw in the towel...
The audio didn't work... that's when I realized I had just messed up two brand new S2s I bought out of a stranger's hands. I've thought about it, and I got the feeling something can be done, but at this point I'm not sure what. I feel like my brain has dried up. I struggled with this for about a week, having a massive headache at least three times. But the story didn't end there...
In a feeling of total defeat, I did the last thing I could think of... I called tech support and tell them about the lack of sound. After lot of talking and pushing for some solution (they wanted me to take it back to the 'store'), they said the warranty was good for another eleven months. They've got my info and emailed me a prepaid UPS label. You think think it's a happy ending? No. You want to know why? I can't even reset the binary counter. I even got a jig connector to do the job, but of course 'for some strange reason', it won't do it. If this isn't an example of a perfect failure, then what is it? Total lost: $900.
I'm not as good as most guys here, but I like to read and use common sense as much as I can. This time I thought to my self "I'm a dumbass, what else can I say?" Aren't I?
Thanks for reading,
Edit: Yes, I did flash a stock ROM.
Hi buddy,
I just read your story.. U will both phone work again, I am pretty sure! Try to get some experienced help! Fully restoring by flashing a stocks rom should be the help... Make sure I do it correct!
Good luck!!!
Sent from my GT-I9100 using xda premium
*you do it right..
Sent from my GT-I9100 using xda premium
I can tell you right off the bat that the reason the Home and Search buttons didn't work on your i777 (AT&T S2) is because you flashed an i9100 ROM. The i9100 has a physical home button and no search button. i9100 ROMs ARE compatible with the i777 since other than that they are identical phones, but you need to fix the key mappings. As for the audio, I'm not sure.
I don't know if I forgot to mention it, but I did flash a stock ROM.
I may not have the greatest knowledge of these things but are you sure it's not a radio issue? Have you tried flashing a different radio (one that's compatible with the ROM and region you want to install)? I know I mate who had an issue with calls after flashing a new ROM to his new S2 and the problem turned out to be the radio. Once he flashed a new one (it may have been the factory one he flashed back on to it) it all worked.
Sent from my HTC Desire using Tapatalk 2
Man that's a crazy story. Not sure if I over read it or not cuz I'm baked or not but maybe they were tinkered with before you got them? Like did audio work originally? I know I'm sure glad I found the sbf files for my old OG, since they've saved me numerous times being able to flash to out of the box status. Sounds like you might've jumped into it too quickly without ironing out all the details. Shoot I know it took me like 2 weeks thinking about just rooting my phone to finally do it a couple years ago.
Sent from my OG using XDA
Yes, that was my first thought after flashing that ICS regional ROM: the radio. And that was the reason why I decided to flash the unrooted stock ROM. But like I said, nothing! I'm sure there was nothing wrong with the phones. The second was working fine before I did it. I actually tested it over and over, kind of like to make me feel better that at least that one of them was going to work.
Hi, are you getting no sound at all or just no sound in call.
I would suggest flashing back using Odin. I've had some issue's when flashing using Odin for customers. Some have had non EU devices and wanted EU firmware flashed. After flashing i also experienced sound issues.
I found that flashing back to the earliest possible stock Samsung Rom helped in my case.
hope this help you out bro
gazlufc said:
Hi, are you getting no sound at all or just no sound in call.
I would suggest flashing back using Odin. I've had some issue's when flashing using Odin for customers. Some have had non EU devices and wanted EU firmware flashed. After flashing i also experienced sound issues.
I found that flashing back to the earliest possible stock Samsung Rom helped in my case.
hope this help you out bro
Click to expand...
Click to collapse
Like I said. The reason why I thought it was a radio issue (and flashed a stock ROM via Odin) was because they do have sound, but no during a call.
gazlufc said:
Hi, are you getting no sound at all or just no sound in call.
I would suggest flashing back using Odin. I've had some issue's when flashing using Odin for customers. Some have had non EU devices and wanted EU firmware flashed. After flashing i also experienced sound issues.
I found that flashing back to the earliest possible stock Samsung Rom helped in my case.
hope this help you out bro
Click to expand...
Click to collapse
I'd still suggest trying to flash a radio separately. When it happened to my mate he still had sound issues after flashing back to a stock ROM and it was only fixed by flashing a separate radio zip.
Sent from my HTC Desire using Tapatalk 2
GraphicGoose said:
I'd still suggest trying to flash a radio separately. When it happened to my mate he still had sound issues after flashing back to a stock ROM and it was only fixed by flashing a separate radio zip.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
I think trying that is the only thing that separates me from having spent $900 in, virtually, two paper weights. I got this strange feeling it might be a fate prank. If so, I'll probably take a break from this kind of endeavors.
The only time I've done a radio update was when updating my G1 to 1.6. The radio file was hard to find though...
The_Forastero said:
I think trying that is the only thing that separates me from having spent $900 in, virtually, two paper weights. I got this strange feeling it might be a fate prank. If so, I'll probably take a break from this kind of endeavors.
The only time I've done a radio update was when updating my G1 to 1.6. The radio file was hard to find though...
Click to expand...
Click to collapse
This could be a start:
http://www.veyka.co.uk/radios/
http://www.mofirouz.com/wordpress/2011/11/samsung-galaxy-s2-radios/
Sent from my HTC Desire using Tapatalk 2
GraphicGoose said:
This could be a start:
http://www.veyka.co.uk/radios/
http://www.mofirouz.com/wordpress/2011/11/samsung-galaxy-s2-radios/
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much mate! Really, I really appreciate it. The clock is ticking back. They're leaving tomorrow. I'll get into it and report back.
Thanks again,
While trying to find the right radio, it just hit me. Should I use a chinese (ZS, ZC) version? I feel like a total n00b asking this, but... does the baseband has to do with roaming or something like that?
Thanks,
The_Forastero said:
While trying to find the right radio, it just hit me. Should I use a chinese (ZS, ZC) version? I feel like a total n00b asking this, but... does the baseband has to do with roaming or something like that?
Thanks,
Click to expand...
Click to collapse
That one I'm not overly sure about sorry mate. Someone else might be able to chime in? But hey, considering they don't work in their current state it can't hurt to give it a try?
Sent from my HTC Desire using Tapatalk 2
The modem firmware has to match the hardware. You need to the one that came with the phone. The frequencies are physically programmed into the radio and flashing a radio with a different frequency will make it not work until you flash the correct one.
Sent from my SPH-D710 using xda premium
Product F(RED) said:
The modem firmware has to match the hardware. You need to the one that came with the phone. The frequencies are physically programmed into the radio and flashing a radio with a different frequency will make it not work until you flash the correct one.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Does that mean, that there are worldwide phones with different hardware chips? Isn't there any chance to reconfigure these chips?
KanocX said:
Does that mean, that there are worldwide phones with different hardware chips? Isn't there any chance to reconfigure these chips?
Click to expand...
Click to collapse
The phones are identical in terms of hardware specs (i9100s I mean) but each region may have one that picks up different frequencies. No you can't reconfigure it unless the radio supports it which is rare and not the case for the S2. Like I said flash the radio that came with the phone. You most likely flashed a ROM for an S2 that was a different region and came with a different radio. The software for the radio is trying to tell the radio to tune to a frequency it doesn't support. Get it?
Hopefully you made a nandroid backup before you did anything and can restore it. Also you can always play around with it in English and then change the language to Chinese when you are done if you are able to find a rom that has the language support.
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
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!
Ok, so please forgive me for this. I'm used to Samsung devices, and rooting/custom recovery is as simple as "Download this, flash through Odin, Easy as pie".
So I have my brother's P769. He had rooted it, but was unsure how to install CWM on it. Me, being completely ignorant of unlocking the bootloader, was able to get CWM on it and flash CM10.2. Which, of course, gave me the LG Security Error. Been stuck for many a day trying to get back to V20F_00. It doesn't help that there is ABSOLUTELY NO WAY to install the omap4 drivers in Windows 8.1, and reserving USB devices to Virtualbox is a pain in the (insert desired graphical descriptor here:_______).
So, I am just trying to clarify the steps to get my brother the CyanogenMod he so desires.
From Stock:
Root device
Unlock Bootloader
Install CWM
Flash CM from CWM
Is this a correct assumption?
jparnell8839 said:
Ok, so please forgive me for this. I'm used to Samsung devices, and rooting/custom recovery is as simple as "Download this, flash through Odin, Easy as pie".
So I have my brother's P769. He had rooted it, but was unsure how to install CWM on it. Me, being completely ignorant of unlocking the bootloader, was able to get CWM on it and flash CM10.2. Which, of course, gave me the LG Security Error. Been stuck for many a day trying to get back to V20F_00. It doesn't help that there is ABSOLUTELY NO WAY to install the omap4 drivers in Windows 8.1, and reserving USB devices to Virtualbox is a pain in the (insert desired graphical descriptor here:_______).
So, I am just trying to clarify the steps to get my brother the CyanogenMod he so desires.
From Stock:
Root device
Unlock Bootloader
Install CWM
Flash CM from CWM
Is this a correct assumption?
Click to expand...
Click to collapse
Welcome JP,getting a break from the Blaze. I've had this beast for a week and I'm ready to crush the phone. So far I've been able to root and remove T-Mobile bloatware.
I've tried to unlock the boot loader many times and no luck. I've read thru the guides and the result is the same.
I sitting patiently to see if the devs can solve the mystery of the bootloader. I can't wait for the day so I can leave the stock Rom. Hope all is well
Sent from my LG-P769 using xda app-developers app
I've had this phone almost a year. As far as the unlocking bootloader goes, it seems like some p769s just aren't unlockable, no matter what method used. Mine is one of those. It may never be able to be unlocked. Just throwing that out there.
THIS link will show you the most common way to unlock the bootloader. It has simple directions and even a video. The only problem is that it doesn't work on some devices, such as mine, so just be wary. And many people in the thread have managed to get results by modifying the instructions, but others have not had any luck.
Good luck! Hope yours works
Welcome to the dark pits of xda hell....LMAO! :sly:
Sent from my LG-P769 using XDA Premium 4 mobile app
LaDY Vengeance said:
Welcome to the dark pits of xda hell....LMAO! :sly:
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is as bad as when I had the Cliq XT , that was a beast as well. That was a replacement phone as well. Hopefully the devs can crack it
thehritzinator said:
I've had this phone almost a year. As far as the unlocking bootloader goes, it seems like some p769s just aren't unlockable, no matter what method used. Mine is one of those. It may never be able to be unlocked. Just throwing that out there.
THIS link will show you the most common way to unlock the bootloader. It has simple directions and even a video. The only problem is that it doesn't work on some devices, such as mine, so just be wary. And many people in the thread have managed to get results by modifying the instructions, but others have not had any luck.
Good luck! Hope yours works
Click to expand...
Click to collapse
That's the link I found, and thought "There's no way it's that complicated!"
HTC uses a dev key. I don't remember Moto's method, but it was simple. Samsung is ridiculously simple. Why is LG so complicated? This has only re-enforced my idea of "Never get an LG"
LaDY Vengeance said:
Welcome to the dark pits of xda hell....LMAO! :sly:
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol thanks! I'm starting to believe it
flyers00 said:
This is as bad as when I had the Cliq XT , that was a beast as well. That was a replacement phone as well. Hopefully the devs can crack it
Click to expand...
Click to collapse
This is the worst phone, as far as modding goes, I've ever seen. I haven't experienced many devices, but geez. Heck, hacking a SGS2 i777 with a faulty USB board was easier than this, and I couldn't even access recovery without ADB commands (because it thought a USB cable was plugged in even when it wasn't, was going to download mode) and couldn't enable ADB (because it thought a cable was plugged). I had to use SQLite hacks to force ADB to enable.
However, I've never let anything stop me before. I'm a world-champion Googler, and so I will crack this will probably take me a while, but meh.
jparnell8839 said:
That's the link I found, and thought "There's no way it's that complicated!"
HTC uses a dev key. I don't remember Moto's method, but it was simple. Samsung is ridiculously simple. Why is LG so complicated? This has only re-enforced my idea of "Never get an LG"
Lol thanks! I'm starting to believe it
This is the worst phone, as far as modding goes, I've ever seen. I haven't experienced many devices, but geez. Heck, hacking a SGS2 i777 with a faulty USB board was easier than this, and I couldn't even access recovery without ADB commands (because it thought a USB cable was plugged in even when it wasn't, was going to download mode) and couldn't enable ADB (because it thought a cable was plugged). I had to use SQLite hacks to force ADB to enable.
However, I've never let anything stop me before. I'm a world-champion Googler, and so I will crack this will probably take me a while, but meh.
Click to expand...
Click to collapse
Congrats on coming into teh darkside. I know you are world class Googler and if you find something or come up with something, I am in to help the cause. I was a guinea pig with the Blaze so why not here. Good luck with your Google skills
Hello everyone. When I started enjoying smartphones, my first love was with HTC. After some time of quality issues across many of their phones, I made the switch to Samsung. I must say, while I was always impressed with Samsung during the warranty period, it became clear to me that the phones don't hold up much longer than that... and in the case of my S5, made several visits to the repair shop during its warranty period.
My question is this. Should I even give the LG consideration? The G3 has been around a while now so there should be some good input at this point. Am I just trading one evil for another? Or is there much more to look forward to if I make the switch? Also, how difficult is it to root? And if I root, is it possible to undo that so there is no trace in case I need to send it in for warranty?
I would especially like the opinion of folks who have played with both the G3 and the Samsung line.
Thanks in advance.
I love the G3. Performance wise it's a beast. It was a pain to root. I even bricked it once in the process but was lucky enough to fix it. If you plan on unrooting it and rerooting it every time something goes wrong with the phone, then I highly recommend you stick with Samsung. Your life will be easier.
I've had both, g3, to me, is easier to root. Root with stump root app, but you must downgrade, using flashtool, to zv4 1st if your phone came with zv6. After that you just flash bumped version of TWRP using flashify app or ADB. I quit Samsung because of KNOX. One false move with downgrading boot loader accidentally, phone is toast. I have softbricked my g3 numerous times, used flashtool Every time to get out of trouble. As far as unrooting goes, use flashtool once again. Not sure if boot loader counts mods like Samsung tho.
sent from my LG G3