Okay, so while doing some unadvised actions, my Desire Z is in the state of not even being able to go into bootloader, recovery or signs of booting up. Not being able to get into bootloader I am unable to get into fasboot to reflash to needed files. It happened when I flashed the radio with Vision_TMOUS_RADIO_12.21.60.09b_26.02.01.15, the G2 one. The phone is s-off with 0005 hboot. I used the newer gfree method of doing this. If anyone can help me to get the phone to connect to the computer, then maybe I can flash whats needed. Or help me do what else to fix this brick, kinda shy of opening it up.
As far as I know, your phone is F.U.B.A.R. due to the fact that they have different radios, one specific to the tmobile G2 which has the different 3G bands as its "world" euro version aka the Desire Z. Sorry bro, vaya con dios. Someone correct me if Im wrong.
Sent from my HTC Vision using XDA App
kholk said:
Welcome to the HTC Vision (TMOUS G2 and Desire Z) Radio ROM & Official BLs Thread!
Well, my old HD2 Radio ROM Thread became a reference for all HD2 users, so.. I'm retrying this here now
Radio ROM Downloads:
Vision_RADIO_12.28e.60.140f_26.04.02.17: MegaUpload
Vision_RADIO_12.28b.60.140e_26.03.02.26: MegaUpload
Vision_RADIO_12.28b.60.140e_26.03.02.18: MegaUpload
Vision_RADIO_12.28a.60.140e_26.03.02.08: MegaUpload
Vision_RADIO_12.26.60.1301_26.02.00.24: MegaUpload
Vision_TMOUS_RADIO_12.21.60.09b_26.02.01.15 (G2): MegaUpload
Official hBoot Downloads:
Vision_HBOOT_0.85.0005: MegaUpload
Vision_HBOOT_0.85.0002: MegaUpload
Vision_TMOBILE_HBOOT_0.82.0000 (G2): MegaUpload
Installing:
1. Download the archive
2. Decompress it, you'll have a .img file (its name should be "radio.img")
3. Copy it into your fastboot folder
4. Boot your device into FastBoot mode and connect it to your PC via USB
5. Go into your Android SDK folder with CMD (Windows) or Linux terminal
6. Flash the Radio on your device: "fastboot flash radio radio.img"
7. Wait until the process finishes. You should read "COMPLETE" on your device's display.
8. Reboot
9. Enjoy!
Please note that you should flash a new radio only if you really know what you're doing!
NOTE: 26.04.02.17 is known to work on G2 and most probably all the radios are flashable on both G2 and D-Z.
Happy flashing!
-kholk
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
Hmmm, is there any way to force fastboot in cmd or anything of the sort? or what would it be like dealing with HTC?
Do you have adb? If so, you can flash another radio.
Also you might try putting stock rom on SD. Make sure its named update. Try booting into hboot. You may just not have an image. Hboot will pick up that update and do its thing. Good luck.
Sent from my G2 using xda app
The phone wont let me in hboot. I cant get adb or fastboot to recognize it without hboot right?
EDIT: Only sign of life i get outta the phone is the amber led showing that its charging
mdayjr said:
Do you have adb? If so, you can flash another radio.
Also you might try putting stock rom on SD. Make sure its named update. Try booting into hboot. You may just not have an image. Hboot will pick up that update and do its thing. Good luck.
Sent from my G2 using xda app
Click to expand...
Click to collapse
There is so much fail in that quote lol.
Well sure. Anything is worth a try. Trying to save the man $600. You have a better idea besides bashing my quote?
Sent from my G2 using xda app
wallyhonda said:
The phone wont let me in hboot. I cant get adb or fastboot to recognize it without hboot right?
EDIT: Only sign of life i get outta the phone is the amber led showing that its charging
Click to expand...
Click to collapse
Its bricked... send it back for a replacement. There is no way they can prove its been rooted, modded, or anything else.
mdayjr said:
Well sure. Anything is worth a try. Trying to save the man $600. You have a better idea besides bashing my quote?
Sent from my G2 using xda app
Click to expand...
Click to collapse
The thing is he already said he can't get into bootloader. Its a fail because you can't even read, lol
sino8r said:
The thing is he already said he can't get into bootloader. Its a fail because you can't even read, lol
Click to expand...
Click to collapse
Thing is I read fine. I ask him about adb and I mentioned putting stock rom on sd. Now. Do you have an idea?
And the biggest thing is this, we wouldn't be even trying to help this member if he could read. LOL
Sent from my G2 using xda app
Any advice on returning it to HTC for a replacement? cuz obviously i shouldnt of been doing what caused this to happen. Anyone have any experience getting phones replaced by HTC, specifically bricked phones?
wallyhonda said:
Any advice on returning it to HTC for a replacement? cuz obviously i shouldnt of been doing what caused this to happen. Anyone have any experience getting phones replaced by HTC, specifically bricked phones?
Click to expand...
Click to collapse
Enough is enough. Go through this forum and grab the ruu radio from football for desire z. I believe this is the only way you are going to break brick. Once you have the file, be on the page with ruu , pull your batt, hook up your phone to pc, hit ruu and wait for it to recognize your phone. If it doesn't, it should give you instructions on what to do. This is the only chance you have I believe.
Sent from my G2 using xda app
sino8r said:
Its bricked... send it back for a replacement. There is no way they can prove its been rooted, modded, or anything else.
Click to expand...
Click to collapse
He bricked it with the radio file. All the os info is still on the phone. Htc will know. These guys went to school for this stuff. Don't be so sure of yourself. There are techs that can pull info from a device that has been underwater so don't think they won't be able to tell. They will go through the phone to find out why it bricked or won't boot and then it will sit with the refurbs after they have put stock os back on that comes with radio file.
Sent from my G2 using xda app
Annnnd in the meantime before they figure all that out, will they send me a new one you think?
One of the first questions a tech will ask you is "did you root the phone?" And unless you purchased that phone directly from htc, you have to deal with your carrier and they wiill tell you that. Real thing is this, you have a nice $600 paper weight. Good luck.
Sent from my G2 using xda app
At that point do i just play dumb lol? As pathetic as it sounds, just until the point they send me a new unit or something. I mean they already told me to deal with the manufacturer. I just dont know what extent they"re going to take with it, ya know. Thanks alot for your time too.
mdayjr has no idea what he is talking about. I'm not meaning to sound insulting but you are simply wrong. He can not overcome this. You are bricked, very simple. The only way to overcome a TRUE brick is with JTAG which I'm sure is unknown how to do on a G2 as of now.
If you have insurance, call your carrier and tell them it just started acting up. If they ask about rooting at all just play dumb. They will not be able to ever know any different. Scouts honor. The only possible way to do this is very time-consuming, would be expensive if you had to pay for it, and is VERY risky. You think they can unbrick a phone? If they COULD unbrick a phone easily, they wouldn't replace it with a brand new one. They would make you send it in, fix it, and send it back. That's just better for business. Even if they could tell you rooted, you would already have your new phone before they knew and you would still be sitting there with a brand new phone.
Next time you flash a radio follow read to be sure other people with the same phone/SPL have flashed it and confirmed it working. Coming from a MT3G/G1 the most common reason for TRUE bricks is an improper radio or SPL flash.
If you are ever able to get into recovery or fastboot you are fine. Since you are unable to get into either recovery or fastboot your phone is bricked. If you would like to read about what's going on with your phone right now, you can read more here:
http://forum.xda-developers.com/showthread.php?t=655097
mdayjr said:
He bricked it with the radio file. All the os info is still on the phone. Htc will know. These guys went to school for this stuff. Don't be so sure of yourself. There are techs that can pull info from a device that has been underwater so don't think they won't be able to tell. They will go through the phone to find out why it bricked or won't boot and then it will sit with the refurbs after they have put stock os back on that comes with radio file.
Sent from my G2 using xda app
Click to expand...
Click to collapse
Lol! Are you a cell tech? No...
Am I?
Yes... well... was, for many years
No, you moron... they don't check or try and pull any info if it doesn't power on or have liquid or physical damage. They don't use the same recovery software that you use to recover criminal/goverment files on a damaged drive, lol! What a waste of time! They replace the board if it isn't flashable and obviously they can't see the previous build without a functional bootloader. Plus, a damaged radio is enough to brick. Reflashing a radio won't fix it for sure but its worth trying EXCEPT he can't get into bootloader or fastboot!!! Shut up and quit making this guy more confused, please!
wallyhonda said:
At that point do i just play dumb lol? As pathetic as it sounds, just until the point they send me a new unit or something. I mean they already told me to deal with the manufacturer. I just dont know what extent they"re going to take with it, ya know. Thanks alot for your time too.
Click to expand...
Click to collapse
If you can... get a replacement phone from your carrier. Tell them you charged it overnight and it won't power on. Simple as that! Don't listen to that other guy... he has no idea what he is talking about. He means well but is an idiot. He's what we call, in the IT profession, a user that has just enough experience to do some damage, lol! You will be fine... just play dumb. Same deal what I told you with HTC if you get referred there.
Related
SOooooooooooo, I was hoping to get Froyo installed on my DInc, and considered waiting for the OTA version, but wanted to do a full wipe and start from scratch. I got a hold of the RUU file and tried to install via the windows interface. When I couldnt get that to work I exctracted the Rom.zip file, renamed it PB31img.zip and ran it through the recovery screen. Everything seemed to work just fine. It verified the file several times, then asked me if I wanted to update. I hit volume up for yes and allowed it to do its thing. It showed several different screens with different progress bars, and seemed to reboot several times. One of the times though, it just went black. Now I cant get it to do anything.
So the question lies therein,,,, did I kill it? I researched a lot before, and have obviously been researching since, and feel like I followed everything correctly. If I did mess it up, is there any saving it?
Jimmydaux said:
SOooooooooooo, I was hoping to get Froyo installed on my DInc, and considered waiting for the OTA version, but wanted to do a full wipe and start from scratch. I got a hold of the RUU file and tried to install via the windows interface. When I couldnt get that to work I exctracted the Rom.zip file, renamed it PB31img.zip and ran it through the recovery screen. Everything seemed to work just fine. It verified the file several times, then asked me if I wanted to update. I hit volume up for yes and allowed it to do its thing. It showed several different screens with different progress bars, and seemed to reboot several times. One of the times though, it just went black. Now I cant get it to do anything.
So the question lies therein,,,, did I kill it? I researched a lot before, and have obviously been researching since, and feel like I followed everything correctly. If I did mess it up, is there any saving it?
Click to expand...
Click to collapse
Well let me ask you a few questions.
1) how much battery did you have
2) what radio and software were you on previously.
3)s-off, or s-on
4) does it give you the charging light on the phone when plugged in?
Do you remember if it got past the "flashing hboot" and "flashing radio" screens all the way? If it did, you can still probably recover. Does the light turn on when you plug it in?
I probably had 80-85% battery. It was stock other than an update to the 2.05 radio.
It went through a few screens but I wasnt paying much attention to what they were exactly. I think I was nervous enough that I had to work on something else while it was working *laundry*
Software was stock 2.1. I hadnt done anything with that. From the Ruu I think I remember it being 1.36 or something close to that. Deffinitely not the 3.xx that the RUU said it would flash it to.
And the one that I think is going to seal my fate,,, no, the battery light does not come on when plugged in.....
I think I sense the answer,,, hello expensive paper weight,,, door stop, potato gun ammunition...
Jimmydaux said:
I probably had 80-85% battery. It was stock other than an update to the 2.05 radio.
It went through a few screens but I wasnt paying much attention to what they were exactly. I think I was nervous enough that I had to work on something else while it was working *laundry*
Software was stock 2.1. I hadnt done anything with that. From the Ruu I think I remember it being 1.36 or something close to that. Deffinitely not the 3.xx that the RUU said it would flash it to.
And the one that I think is going to seal my fate,,, no, the battery light does not come on when plugged in.....
I think I sense the answer,,, hello expensive paper weight,,, door stop, potato gun ammunition...
Click to expand...
Click to collapse
The question though is: How did it happen?
It could be possible that the RUU download was corrupted. Specifically the bootloader. Do you have the insurance?
Also a battery pull / charge and pray couldnt hurt at this point. How long has it been this way?
Fretless said:
The question though is: How did it happen?
It could be possible that the RUU download was corrupted. Specifically the bootloader. Do you have the insurance?
Also a battery pull / charge and pray couldnt hurt at this point. How long has it been this way?
Click to expand...
Click to collapse
I totally agree, if on radio 2.05x it doesn't make much of any sense that a brick happened.
Agreed. In fact, I just performed this exact same procedure myself and it worked perfectly. The only difference was that I had s-off and the stock radio.
Were certainly missing a variable here.
Jimmydaux said:
It was stock other than an update to the 2.05 radio.
...
Click to expand...
Click to collapse
Bingo.
If I was to point to one thing, it would be the 2.x radio, as this ruu and the accompanying ota probably assume the use of the 1.x radio, since the 2.x ota was never publicly released. Unless the battery somehow died or fried in the middle of the flash. I feel for you man. I would cry if mine died...
I'd point my inexperienced unlearned finger squarely at the 2.05.x radio.
Dude, this is a very good chance for you to make verizon give you a new one. Think of it as a golden opportunity.
Fretless said:
Bingo.
If I was to point to one thing, it would be the 2.x radio, as this ruu and the accompanying ota probably assume the use of the 1.x radio, since the 2.x ota was never publicly released. Unless the battery somehow died or fried in the middle of the flash. I feel for you man. I would cry if mine died...
I'd point my inexperienced unlearned finger squarely at the 2.05.x radio.
Dude, this is a very good chance for you to make verizon give you a new one. Think of it as a golden opportunity.
Click to expand...
Click to collapse
Also called warranty fraud.
ACD168 said:
Also called warranty fraud.
Click to expand...
Click to collapse
Not so! Its called warranty use!
He did not root the phone, so its not fraud. All he was doing was installing what he thought was a legitimate RUU.
Not fraud.
Apologies if i missed something.
Fretless said:
Not so! Its called warranty use!
He did not root the phone, so its not fraud. All he was doing was installing what he thought was a legitimate RUU.
Not fraud.
Apologies if i missed something.
Click to expand...
Click to collapse
I agree, just being a smart ass lol. I'd make full use outta calling for a refurb.
ACD168 said:
I agree, just being a smart ass lol. I'd make full use outta calling for a refurb.
Click to expand...
Click to collapse
To be honest, I'd be a hot candidate for warranty fraud if mine messed up. Call me evil...
The 2.05 radio is not to blame. I had the that same radio and used the Rom.zip to update my phone with no problems. Only difference was I have s-off but that shouldn't make a difference here. Everything else was stock including the recovery.
Sent from my Droid Incredible
OP, did you perform a checksum on the RUU to verify it was a complete download?
I also don't think the 2.05 radio is to blame here either.
Hmm....
Technically, it is warranty fraud, since he's invoking the warranty right by damage caused by the user, which warranties don't cover unless they're accidental damage warranties.
The 2.05 radio shouldn't matter. The RUU contains a radio img not a patch like the 2.05 leak.
Well friends, I couldnt get anything to happen. I took it into the Verizon store and I told them that I was trying to install the update and something happened mid install and it died. I asked him if that would be something I would have to file an insurance claim on, but he said that it wasnt my fault if it died during the update........... his words.... so they gave me another phone to replace it. THey were all out of their 'replacement' phones, so I actually got a brand new phone because of this whole deal. I lucked out I know! And yes,,,, i may have shed a tear or two yesterday when it happend, but after walking into the V store, I had a crazy overwhelming relief that I wasnt going to be at a complete loss.
So, just in case anyone is following this,,, what other variables would need to be looked at in order to see why this happened.
I did not run a Checksum, but it seemed to run other than the driver issues. The Rom file that was installed was 168 mb, renamed properly and installed through the recovery screen from the sd card root. The phone was not touched during this time. Did I just have a misfortunate run in with what I thought was a legitimate way to get the update installed?
Jimmydaux said:
Well friends, I couldnt get anything to happen. I took it into the Verizon store and I told them that I was trying to install the update and something happened mid install and it died. I asked him if that would be something I would have to file an insurance claim on, but he said that it wasnt my fault if it died during the update........... his words.... so they gave me another phone to replace it. THey were all out of their 'replacement' phones, so I actually got a brand new phone because of this whole deal. I lucked out I know! And yes,,,, i may have shed a tear or two yesterday when it happend, but after walking into the V store, I had a crazy overwhelming relief that I wasnt going to be at a complete loss.
So, just in case anyone is following this,,, what other variables would need to be looked at in order to see why this happened.
I did not run a Checksum, but it seemed to run other than the driver issues. The Rom file that was installed was 168 mb, renamed properly and installed through the recovery screen from the sd card root. The phone was not touched during this time. Did I just have a misfortunate run in with what I thought was a legitimate way to get the update installed?
Click to expand...
Click to collapse
You brick your phone and they give you a brand new one. no way, how old was your other phone. and what state are you in. they took care of u.
You going to tell on him lol
Sent from my ADR6300 using XDA App
I know i will get trashed for this post. but i am just not sure and do not want to brick my phone
i recently had speaker problems with my evo and dirt under my screen. So i need to return my phone and get a new one.
how can i get rid of nandroid and flash the ota froyo rom and have it back to stock.
do i run this
PC36IMG.zip
http://forum.xda-developers.com/showthread.php?t=715915&highlight=froyo
you want to unroot? http://forum.xda-developers.com/showthread.php?t=743192
If your going through HTC directly just return your phone as is. They don't really care about the software if the replacement is due to a hardware issue. I'm not sure if sprint will be as finicky but my guess is they will be about the same.
What I've done is go to a sprint repair center. They tend to be fairly intelligent and generally swap right there.
Why would you get trashed for asking a question like that? The only reason I could see would be that it should be under the Q&A section, but if you think you'd get trashed because you asked a question about unrooting, I would like to know who's been giving this community a bad name. Not that I could do anything about it, but I like to think that we're pretty friendly here.
quietpopcorn said:
Why would you get trashed for asking a question like that? The only reason I could see would be that it should be under the Q&A section, but if you think you'd get trashed because you asked a question about unrooting, I would like to know who's been giving this community a bad name. Not that I could do anything about it, but I like to think that we're pretty friendly here.
Click to expand...
Click to collapse
Ageed. Theres nothing wrong with unrooting especially if you are trying to get a replacement.
Run the RUU ?? I think that should put you back to unrooted stock.
NO NO NO
martijua said:
Run the RUU ?? I think that should put you back to unrooted stock.
Click to expand...
Click to collapse
Dont run any RUU you wont get it up and running anymore.
Hi, I am unable to hookup to my laptop due to usb port loose/faulty connection. I will be taking phone back to BestBuy to either fix or replace. Well- would like to anyways. So how would I do this if I cannot run the ruu or HTC sync? Could I just put the step 2 pcimg. On my sdcard and flash that? I was unable to get my pri to update so I have flashed the zip file that just changes the numbers to be correct.
Thanks for any help.
J
Sent from my PC36100 using XDA App
Run the official RUU.
Sent from my PC36100 using XDA App
I'm asking on behalf of a friend of mine who doesnt actually have a computer so he cant post here himself to ask. I'm a vibrant/N1/G1 user myself, so i'm familiar with the aspects here: he has a slide, has the split-screen/ribbon problem on opening/closing the keyboard. He managed to get a warranty replacement from TMO, but he's super paranoid about having to pay the damages fee because he has CM loaded on it instead of the stock firmware.
Bottom line, he wants to brick it just to be sure before he sends it back (he already has the replacement phone). What is the simplest way (that I could explain to him over the phone) to hard brick the phone?
Quick and dirty is all I really need to help him get the job done, all help much appreciated!
If he can brick it, then he can flash the factory ROM that is available to bring it back to unrooted stated. Why not just do that?
-sigh- I guess he can just try to follow the S-OFF instructions to where it says not 2 power off, take out battery- disconnect phone... do the oppsite of what it says not to do? Just saying though... why not just do what Fermunky said?
fermunky said:
If he can brick it, then he can flash the factory ROM that is available to bring it back to unrooted stated. Why not just do that?
Click to expand...
Click to collapse
CaliBoyPhillip said:
Just saying though... why not just do what Fermunky said?
Click to expand...
Click to collapse
Problem is that he lives in virginia and I live in colorado. I rooted and customized his phone when I was out there visiting because he's completely inept at this kind of stuff, so I was just looking for a simpler solution than to try and walk him through a reflash over the phone. Plus, apparently what he told the TMO reps was that he got an OTA update and it bricked him, which is the only way (he said) that they'd do a warranty exchange.
Well, I guess your short answer is No, there is no "quick" way. Whether you try to brick it or not, either way will require some attempt at flashing "something", but to just do it in a completely wrong way. Maybe by connecting to a PC and using clever ADB/Shell commands could also do it, but not entirely sure.
Couldn't you flash the radio for say, a Droid X or any CDMA radio?
I know you can brick CDMA phones by flashing GSM radios.
And yay Colorado ;D
I'm going to have to close this as it's discussing warranty fraud.
Hello everyone, I just got a problem last night. I tried to permroot my G2 using Visionary+ and once it rebooted it got stuck on the HTC loadup screen. I have done a factory reset and have gone into recovery mode but when I do go into recovery mode, I get a droid phone with an exclamation mark in the middle and it just stays there.
I don't know many details about the phone other than what I can tell you from the HBOOT menu, I'd rather avoid sending it back in for a warranty repair unless I can just get to the normal screen where I can unroot it, I don't care who you are I just need help on what to do because I have no idea :\
Thanks guys, you're my last hope >:|
First off, this is why you DO NOT use visionary. Well documented to brick phones:http://forum.xda-developers.com/showthread.php?t=1025135
You can start off trying to recover your brick by looking at this thread: http://forum.xda-developers.com/showthread.php?t=842495
You might as well have written that in chinese, I have no idea what any of this means. it's S-ON and it won't go into recovery mode.
Walk me through what I need to do..? :\
So I had a thought, if I could use a friends Android which, Idk the model to, but could I just uninstall Visionary from there? Would that do anything at all?
xTyrant said:
You might as well have written that in chinese, I have no idea what any of this means. it's S-ON and it won't go into recovery mode.
Walk me through what I need to do..? :\
So I had a thought, if I could use a friends Android which, Idk the model to, but could I just uninstall Visionary from there? Would that do anything at all?
Click to expand...
Click to collapse
You cant really uninstall visionary if you cant even boot up your phone. Right now the rom is corrupted and you need to follow an unbricking guide like the one mentioned above
Sent from my HTC Vision using XDA App
xTyrant said:
So I had a thought, if I could use a friends Android which, Idk the model to, but could I just uninstall Visionary from there? Would that do anything at all?
Click to expand...
Click to collapse
What are you talking about? Connecting your phone to your friend's phone? It doesn't work that way.
Alright everyone, I called T-Mobile and I'm having a new phone by tomorrow, there's nothing I can do as, I have no idea how to fix my corrupted ROM,
I tried following the unbricking guide but I can't so much as get my phone detected by my computer to even do anything with it.
And another noob bites the dust
Sent from my SilverBullet 'HTCDesireZ running CM7'
xTyrant said:
Alright everyone, I called T-Mobile and I'm having a new phone by tomorrow, there's nothing I can do as, I have no idea how to fix my corrupted ROM,
I tried following the unbricking guide but I can't so much as get my phone detected by my computer to even do anything with it.
Click to expand...
Click to collapse
You really need to research before you try to root your phone. Like a lot of research.
and when you brick it, you need to research to try and un-brick it. This stuff is easy, but its tedious, and if you're not ready to deal with hours of trying to fix your phone, you shouldn't been rushing into rooting.
All of the info is in that thread. Dozens of people have followed it and recovered their semi-brick.
martonikaj said:
You really need to research before you try to root your phone. Like a lot of research.
and when you brick it, you need to research to try and un-brick it. This stuff is easy, but its tedious, and if you're not ready to deal with hours of trying to fix your phone, you shouldn't been rushing into rooting.
All of the info is in that thread. Dozens of people have followed it and recovered their semi-brick.
Click to expand...
Click to collapse
Agree with everything you said. One click roots can be dangerous and tempting, as they lure people to an easy method, without having to learn the basics . . . and that's how the trouble starts. Especially when the one click root method is known to result in possible semi bricks.
If anybody wonders why HTC tried going to locked bootloaders, or constantly trying to increase the security against rooting, situations like this is why. People not wanting to make an effort to root by proper methods, or fix their mistakes, and claiming a "warranty issue".
Hi guys, my brother sent me up his HTC Desire in the mail asking me to fix it. Now I'm pretty **** at fixing android phones so I don't really know what to do. He tells me he started to root it but the cable came out half way through. Don't ask me what he was using to root it because neither of us know.
When I boot holding VOLUME DOWN + POWER this screen shows up:
(imgur) /F9oojVv.jpg (sorry that is an imgur link, I'm not allowed to link things as I don't have 10 posts)
Factory Reset does nothing.
I think doing a recovery might be able to fix it but I have no idea what to download.
If anyone can help fix this for me I will appreciate it so much, I have been searching the internet for hours and can't find a solution...
P.S. The device won't show up in Odin or in Windows explorer if that helps at all.
He's S-Off. All he needs to do is fastboot flash a recovery.img, then flash a ROM from there and he's good.
bananagranola said:
He's S-Off. All he needs to do is fastboot flash a recovery.img, then flash a ROM from there and he's good.
Click to expand...
Click to collapse
So how do I do that? Remember I'm really new at this kind of thing.
Fazzy McGee said:
So how do I do that? Remember I'm really new at this kind of thing.
Click to expand...
Click to collapse
The link in my signature has everything you need to know.
Honestly, if my brother borked his phone, not known what he did, not figured out how to fix it himself, and wanted me to do it for him, I wouldn't do it. You're a better person than I am.
bananagranola said:
The link in my signature has everything you need to know.
Honestly, if my brother borked his phone, not known what he did, not figured out how to fix it himself, and wanted me to do it for him, I wouldn't do it. You're a better person than I am.
Click to expand...
Click to collapse
I joined that IRC but you never replied. I'll try and read this guide but I don't know how relevant a lot of it is actually going to be.
ok using the following command.
fastboot getvar all
this will help out some what. Does selecting anything in Hboot cause the phone to freeze if not then its just a matter of getting a recovery on. If you do get freezes then it could be borked.
s-off
I recommend going to s-off it.Then up another rom see if overcome