I've mistakenly upload HardSPL from Mega-Touch2 ...
Phone is not react on nothing
i've try soft and hard reset, phone is dead ...
is there any solution ?
JFH said:
I've mistakenly upload HardSPL from Mega-Touch2 ...
Phone is not react on nothing
i've try soft and hard reset, phone is dead ...
is there any solution ?
Click to expand...
Click to collapse
Use it as a paperweight?
Seriously, though, the only way to recover from that, if it won't do anything, is a JTAG recovery. See if any of your local electronics dealers can do it for you. Otherwise, it might be better for you to get a new one...
i've try to do something with mtty usb
but "ub port can not open".
i disabled usb connection in w7pro
JFH said:
i've try to do something with mtty usb
but "ub port can not open".
i disabled usb connection in w7pro
Click to expand...
Click to collapse
It isn't going to work. You have the wrong SPL flashed to it. The SPL is what loads up EVERYTHING in the device and makes it all play nicely together. You won't be able to recover via USB. JTAG is the only option, but it isn't something you will be able to do, I would imagine.
service said,procesor is fake
they said, "we try few times with 3 different recovery tools, in 75% phone go down"
is this possible, procesor is death ?
JFH said:
service said,procesor is fake
they said, "we try few times with 3 different recovery tools, in 75% phone go down"
is this possible, procesor is death ?
Click to expand...
Click to collapse
I've already said that your problem is that you flashed the wrong SPL. The device is dead. Get a new one.
Think of this as an opportunity to get a new phone and a lesson learned.
I gave my old broken Nokia to my nephew and he plays with it all the time. Silly kid thinks he can make calls from it.
JFH said:
service said,procesor is fake
they said, "we try few times with 3 different recovery tools, in 75% phone go down"
is this possible, procesor is death ?
Click to expand...
Click to collapse
This is the ugly truth that you have to face with it. I'm sorry to hear that.
Try a new phone right now, use the old dead one as a paperweight like others have said.
Replace the mainboard, you bricked the device.
Okay, i can not understand this guy.
Can someone translate to proper english if you understand?
What has he done?
ryannathans said:
Okay, i can not understand this guy.
Can someone translate to proper english if you understand?
What has he done?
Click to expand...
Click to collapse
He flashed the Hard SPL from the HTC Mega (Touch 2) to his HTC Rhodium (Touch Pro2). Doing this bricked his device. The only solution is to either J-TAG it to recover directly, replace the mainboard, or replace the whole device. Since the OP flashed the wrong SPL, I am assuming that he is probably not qualified or capable of J-TAG or mainboard replacement (I mean no offense to the OP). This is why I simply stated that he just get a new one.
The moral of the story is to read carefully before doing any of this stuff for this very reason. He now has a $300 paper weight.
cajunflavoredbob said:
He flashed the Hard SPL from the HTC Mega (Touch 2) to his HTC Rhodium (Touch Pro2). Doing this bricked his device. The only solution is to either J-TAG it to recover directly, replace the mainboard, or replace the whole device. Since the OP flashed the wrong SPL, I am assuming that he is probably not qualified or capable of J-TAG or mainboard replacement (I mean no offense to the OP). This is why I simply stated that he just get a new one.
The moral of the story is to read carefully before doing any of this stuff for this very reason. He now has a $300 paper weight.
Click to expand...
Click to collapse
Ahh, makes sense now.
As long as you sit in the right forum you should be fine OP
Didnt realise there was no way to recover it once it is bricked. I tend to be really careful but I still worry when flashing my phone. Makes me scared to do it on my next phone now knowing its game over if I do something wrong.
fade2black101 said:
Didnt realise there was no way to recover it once it is bricked. I tend to be really careful but I still worry when flashing my phone. Makes me scared to do it on my next phone now knowing its game over if I do something wrong.
Click to expand...
Click to collapse
You'll be just fine if you read carefully before flashing. The OP's problem was that he flashed a SPL from a completely different device. If he had done something wrong with the Rhodium software, then we could have helped him recover. As long as you stick to stuff to your device, you should be fine.
fade2black101 said:
Didnt realise there was no way to recover it once it is bricked.
Click to expand...
Click to collapse
That's what a brick is, a paperweight. Useless and unrecoverable, that's the main point in calling it a "brick". Some have defined a brick as unrecoverable w/o opening up the phone. And some use terms like "semi-brick". But the "semi-brick" distinction in particular seems silly. If you can recover from it fairly easily, than its not a brick. You just hit a roadbump,and then you figured it out.
The OP is screwed because he messed with the SPL, and as cajun said, the SPL is what loads EVERYTHING else. If you are just flashing ROMs and whatnot, even a bad flash is easy to recover from. As long as you can get into bootloader, you're fine. Just flash a known good ROM.
redpoint73 said:
That's what a brick is, a paperweight. Useless and unrecoverable, that's the main point in calling it a "brick". Some have defined a brick as unrecoverable w/o opening up the phone. And some use terms like "semi-brick". But the "semi-brick" distinction in particular seems silly. If you can recover from it fairly easily, than its not a brick. You just hit a roadbump,and then you figured it out.
The OP is screwed because he messed with the SPL, and as cajun said, the SPL is what loads EVERYTHING else. If you are just flashing ROMs and whatnot, even a bad flash is easy to recover from. As long as you can get into bootloader, you're fine. Just flash a known good ROM.
Click to expand...
Click to collapse
Is this covered in the warranty? lol
I can recover hard bricked phones including the TP2 and many other devices using JTAG. PM me with any questions about a bricked Tp2.
Related
Ok my screen broke today. Took it out of my pocket and it had cracked
Is there any app I can install on my phone to see the IPL and SPL versions? Or is there any other way I can fine out what I have?
yes there is an app called wiki search and i heard it works perfectly
anyhow press and hold left ok key + da power button and then use ur stylus to press down the soft reset key that should take you to da bootloader screen
Going into the bootloader to see this info is pointless. Screen is cracked and I cant see anything.
Go to the bootloader screen. Uncheck "allow USB" in Active Sync. Connect your unit with USB cable. (Download and) run MTTY program, choosing your unit, (not a comm port) for connection. Hit ENTER, to get a cmd prompt. Type "info 7" without the quotes. It will show you the bootloader info.
Examples:
USB>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.50a
Device Name: H, Bootloader Version : 1.04
Built at: May 26 2006 20:17:35
Copyright (c) 1998-2006 High Tech Computer Corporation
Click to expand...
Click to collapse
Have you tried "My Mobiler"? I got it from pocketpcfreewares - I'm sure it can be found elsewhere too. It includes the ability to view your phone screen right on your desktop PC, and should help you get through your current dilemma.
HTC Integrated Re-Flash Utility, Common Base Version : 1.50a
Device Name: H, Bootloader Version : 1.04
Built at: May 26 2006 20:17:35
Copyright (c) 1998-2006 High Tech Computer Corporation
Click to expand...
Click to collapse
That is what I get. I downgraded from oli pro to SPL 1.04 so I am guessing this is correct?
is it safe to downgrade? Can I get my warranty if I downgrade to the original SPL?
Good luck having a cracked screen covered by warranty...
Yeah I know. Maybe I wont tell them the screen is cracked and just say it wont come one anymore that there is no light. I disabled the back light so it wont turn on except only on a reset. If it wont come on then how will I know its cracked?? Worth a shot I guess.
Phantisy said:
Yeah I know. Maybe I wont tell them the screen is cracked and just say it wont come one anymore that there is no light. I disabled the back light so it wont turn on except only on a reset. If it wont come on then how will I know its cracked?? Worth a shot I guess.
Click to expand...
Click to collapse
It is a good bet that a reset will be part of their diagnostic procedure.
If you are feeling really daring, just brick it before sending it back. One way to ensure that they cannot boot it is to overwrite the IPL/SPL with a bad file. I would certainly not ADVOCATE such things, but it would probably be highly effective to ensure they do not get the thing booted. Of course, you never will either.
Zuckron said:
is it safe to downgrade? Can I get my warranty if I downgrade to the original SPL?
Click to expand...
Click to collapse
Well, we would need some more info, like what your Hermes' problem is, but read the MrVanx downgrade guide and it is pretty safe. It is definitely best to downgrade back before sending it in, if you have a warranty replacement issue.
todd_jg said:
It is a good bet that a reset will be part of their diagnostic procedure.
If you are feeling really daring, just brick it before sending it back. One way to ensure that they cannot boot it is to overwrite the IPL/SPL with a bad file. I would certainly not ADVOCATE such things, but it would probably be highly effective to ensure they do not get the thing booted. Of course, you never will either.
Click to expand...
Click to collapse
Well I was hoping that they would just send me a replacement and not ask many questions since "I can't see anything" on the screen. I have no idea how the warranty works on these things.
todd_jg said:
It is a good bet that a reset will be part of their diagnostic procedure.
If you are feeling really daring, just brick it before sending it back. One way to ensure that they cannot boot it is to overwrite the IPL/SPL with a bad file. I would certainly not ADVOCATE such things, but it would probably be highly effective to ensure they do not get the thing booted. Of course, you never will either.
Click to expand...
Click to collapse
You wouldn't happen to have a "bad" file anywhere that I could download. I am daring enough to try this. I got the phone from wirefly (don't bash me please) and they are sending me a replacement. I don't know what kinda techs they have. They said all they check for when they receive the phone is all the contents in the box and nothing else but I don't trust that. Bricking it would be a good way to ensure they don't see the screen.
Phantisy said:
You wouldn't happen to have a "bad" file anywhere that I could download. I am daring enough to try this. I got the phone from wirefly (don't bash me please) and they are sending me a replacement. I don't know what kinda techs they have. They said all they check for when they receive the phone is all the contents in the box and nothing else but I don't trust that. Bricking it would be a good way to ensure they don't see the screen.
Click to expand...
Click to collapse
Well, the easiest way is to make sure that HardSPL is not on there and then build your own file using Dutty's god NBH tool. Just create an NBH for a IPL.SPL flash and reverse the files. In other words, instead of putting the SPL.nb in where the IPL should be and vice versa. I assure you, they would not be able to boot the phone. I know this because I did this *on accident* one time and completely bricked the phone. Completely unrecoverable! To the point that the LED did not even come on to indicate that the phone was plugged in. It was well and truly dead. Again, I would not really advocate doing this type of thing, only pointing out that it will most certainly render your phone completely and irretrievably dead.
Alright. I am thinking hard about this because if they can see the screen is cracked (Can be done in the right light at the right angle) then they might send it back and I don't want to be stuck with the bricked phone. Would be cheaper to void the warranty and replace the screen on my own. Thanks for the info though.
I have to push my qwerty keyboard bottons REAL hard to make them working. This is a problem that came resently. Please, can someone give me a link to the spl downgrade guide? I can't find it. And to be honest, i do not understand how i should use the wiki correct yet.
Zuckron said:
I have to push my qwerty keyboard bottons REAL hard to make them working. This is a problem that came resently. Please, can someone give me a link to the spl downgrade guide? I can't find it. And to be honest, i do not understand how i should use the wiki correct yet.
Click to expand...
Click to collapse
Follow this guide EXACTLY and you will be able to downgrade.
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=59&Itemid=27
but my original spl was 1.11 . . What should I do? Downgrade to 1.06 and then upgrade? And where do I find the files I need?
Zuckron said:
but my original spl was 1.11 . . What should I do? Downgrade to 1.06 and then upgrade? And where do I find the files I need?
Click to expand...
Click to collapse
Your IPL was not 1.11 - i was prolly 1.01.
There are links to necessary files in the guide.
The original IPL and SPL on my AT&T 8525 was:
IPL-1.03
SPL-1.11
These were the original on 2 8525's I have had.
Do As I Did
I had a qtek 9100 with a smashed screen that i could not recur to the warranties because of the ROM plus other things, the only way was to change the screen was on my own, using the service manual (and it was easier than i thought) now i have a tytn but my old 9100 still works at 100% ps: GOOD LUCK
Hello,
just got a HTC diamond Touch,locked so was trying to unlock it followed the Sticky on How To Unlock step by step,but when i clicked Yes to run "EnterBootloader.exe on my phone the screen went black the connection to the phone was lost! & now it wont turn on at all
Tryed to take out the battery,hard reset,nothing worked...
I hope that some1 in this forum will be able to help me
Try hard reset... hold volume down/enter key and do a "soft reset"
mouragio said:
Try hard reset... hold volume down/enter key and do a "soft reset"
Click to expand...
Click to collapse
thx m8 already tryed it....no luck
There are only two ways if you cannot get Bootloader (SPL) to run :
1. Send to RMA (gsm only : if it wasn't security unlocked)
2. Use Jtag (we only know pinouts for normal diamond yet)
Cya,
Viper BJK
thx every1 who tryed to help got the phone fixed had to send it in to htc uk only had to pay for posting it to them the rest was covered by the warranty diagnosis was main board failure? anyway back up and working 100% the only thing that it`s still locked on *range uk....has any1 ever unlocked their simlock?
OffTopic ... for unlocking read threads about that OR ask Olipro or cmonex or tupisdin
On the same topic, i have a bricked touch diamond that does not have a working bootloader. Totally dead, computer does not recognize it etc. And to make thigns worse i dont have a receit for it. Bricking happened during installing a new cooked rom over a previous cooked rom without doing a hard reset between them.
What are my options to possibly make this HTC working again? For example, can i get it JTAG'ed somewhere, or can i get it repaired somewhere (manufacturer?) even without warrenty?
Iikoo said:
On the same topic, i have a bricked touch diamond that does not have a working bootloader. Totally dead, computer does not recognize it etc. And to make thigns worse i dont have a receit for it. Bricking happened during installing a new cooked rom over a previous cooked rom without doing a hard reset between them.
What are my options to possibly make this HTC working again? For example, can i get it JTAG'ed somewhere, or can i get it repaired somewhere (manufacturer?) even without warrenty?
Click to expand...
Click to collapse
Flashing a new cooked ROM over a previously cooked ROM (obviously you have hardspl and all that) wont brick. Thats weirddddd!
Im sure you tried hardreset and all that stuff right?
Can you enter bootloader at least? or tottaly dead?
Tried hard reset > no luck. Left the phone sitting without a battery for a few days > nothing. Allso can't acces the bootloader, so basically totally dead
Any ideas?
is battery charging?
As far as i can tell, no. I'll check that again later, don't habe the phone here at the moment.
To Sergio PC: i read from somewhere that you should not install a new rom without a hard reset before that. None the less, that is propably what has happened here. You think that something else has gone wrong here?
Well it seems that you indeed killed your spl.
I'm trying to jtag my diamond soon and will reply to this thread.
Cya,
Viper BJK
This is so weird. Maybe somebody flashed cdma hspl on gsm diamond. This brick phone 101%, but gsm hspl on gsm phone - this is almous impossible, unless your battery is too low (but flashing with low battery even won't start). I'm litle scarry about flashing any htc device these days. And can somebody post here DIAM100 JTAG pinout ?
viperbjk said:
Well it seems that you indeed killed your spl.
I'm trying to jtag my diamond soon and will reply to this thread.
Cya,
Viper BJK
Click to expand...
Click to collapse
You mean dead as in throw it to the dogs or dead as in keep trying there is a way to unbrick it?
With JTAG, yes
Exactly. RMA or JTAG.
For the latter one I need to code an app and verify that my jtag pinouts work.
The first option is however the best if you aren't quite good in soldering cables to small pads.
Cya,
Viper BJK
You need to send to warrenty... Your Diamond is death!!!!
I have same problem and send to repair and change all mainboard, new IMEI.
You kill the phone!!!!
hellonasty said:
You need to send to warrenty... Your Diamond is death!!!!
I have same problem and send to repair and change all mainboard, new IMEI.
You kill the phone!!!!
Click to expand...
Click to collapse
Damn, that sounds quite bad. So do you happen to know why would this totally kill the phone rather than just mess up the nand flash that could be saved with JTAG. What i've been reading about the way that nand flash memory is written, when you scren up the write and you dont have hardcoded bootloader, then there is nothing to "channel" the new data (new rom) throught the usb/motherboard/other circuitry. So here comes JTAG to the rescue as it can reprogram the flash using only four wires connected directly to the chip and some clever sounding techniques that happens inside the chip...
Then again, i might be totally wrong here because my knowledge about inner workings of a modern ic chip is slim to none. But never the less, i still keep on hoping that there would be a way to save my touch, maybe even by sending it to someone with better knowledge and equipment to JTAG it (and pay a hefty compensation for it offcourse).
Any idea how much does the service cost to change the whole mainboard?
Ps. my english is not that great, especially on the techincal vocabulary. So i hope you all can still at least partially understant what i am trying to say...
You are absolutely right. Only SPL is bricked, thus you only need to write spl to nand. You can do so using jtag.
Cya,
Viper BJK
About the charging, even that is'nt working...
How about the JTAG'n, does anyone or any place do it for money, besides actual service. Anyone here willing to help me?
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.
Hi everyone! Here is the thing that is bothering me. I bought my phone month and a half ago. I recently unlocked bootloader, installed CWM, rooted it, changed kernel to Titanium KISS and overclocked it, while running stock rom. I have worries because many users reported that their phones suddenly died in 2 months period from purchase. What to do if that happens? I guess that my cell operator wont accept warranty if I give them unlocked and rooted phone back. What is your suggestion?
empyting ur pockets if system partition isnt burned up
I'm thinking to put it all back to stock and wait for another month to see how the phone will behave. :/
BGmaster said:
I'm thinking to put it all back to stock and wait for another month to see how the phone will behave. :/
Click to expand...
Click to collapse
If the phone is rooted (BL unlocked) the warranty is void as is.
If you get the QHUSB (dead) mode, and cannot resurrect the phone via the tool, it is quite possible, that you can claim warranty, given that even the manufacturer cannot read back anything from the phone.
Ken-Shi_Kun said:
If you get the QHUSB (dead) mode, and cannot resurrect the phone via the tool, it is quite possible, that you can claim warranty, given that even the manufacturer cannot read back anything from the phone.
Click to expand...
Click to collapse
You mean like if it's completely dead and I can't access to fastboot or anything they can't see what I did with the phone? So do you suggest that I go back to stock and wait for a little while or leave it like this?
paarthdesai said:
empyting ur pockets if system partition isnt burned up
Click to expand...
Click to collapse
How do they charge you dude??
5000 :'( whole mobo needs to be replaced
If your phone ends up going completely dead (QHSUSB_DLOAD mode, unable to get out of it), chances are your operator might not be able to tell you've done anything to it.
For example, I either ended up bricking my first One V due to overclocking way too high, or it had a faulty memory chip, and got the QHSUSB_DLOAD mode. I sent it back to my operator, and they said they were "unable to fix it" and sent me a replacement, so I'm assuming they couldn't tell I had rooted/unlocked/installed a kernel.
Some QHSUSB_DLOADs are recoverable though, so be careful.
BGmaster said:
You mean like if it's completely dead and I can't access to fastboot or anything they can't see what I did with the phone? So do you suggest that I go back to stock and wait for a little while or leave it like this?
Click to expand...
Click to collapse
If you get that dead mode, then it isn't matters that you are on custom or stock.
Guess i'll then then stick with the customization. If anything goes down that badly I'm gonna act dumb all the way :silly:
Why Worry?
Don't worry. buddy.
First of all, my and my friend's One V didn't die.
Second, if it dies, as you see the previous posts, HTC won't be able to tell that it's rooted if it's hard bricked.
First you could try to repair it using some methods available on the internet or at last you could send it to HTC.
When you're going to win in either way, they why worry?
SWIM wants to know if there is a way to brick an unrooted AT&T HOX that is on 2.20 firmware purposely. And if so, how? Thanks in advance fellow xda members...
i think yes but you would need an s-off(doesn't break warranty) phone or unlocked bootloader(breaks warranty) in s-on, how ?
im not sure, but pulling usb out while flashing an ruu will most likely do it.
The real and interesting question would be why ?
Vcek said:
i think yes but you would need an s-off(doesn't break warranty) phone or unlocked bootloader(breaks warranty) in s-on, how ?
im not sure, but pulling usb out while flashing an ruu will most likely do it.
The real and interesting question would be why ?
Click to expand...
Click to collapse
S-OFF is still a WIP so that's a no and it doesn't have an unlocked bootloader either. It's stock, brand new out of the box from AT&T and the HOX the rep gave us had 2.20 already on it...
Me n my pal are working on a little experiment, if it works, we'll tell you guys all about it. Also, been reading thru the thinktank trying to brainstorm some ideas for root also...
the lack of a removable battery makes bricking it a less of a possibility.. =/
pulling the usb mid disk transfer of a file wouldn't do anything but make the file corrupt and unusable, right?
doubledrake20 said:
S-OFF is still a WIP so that's a no and it doesn't have an unlocked bootloader either. It's stock, brand new out of the box from AT&T and the HOX the rep gave us had 2.20 already on it...
Me n my pal are working on a little experiment, if it works, we'll tell you guys all about it. Also, been reading thru the thinktank trying to brainstorm some ideas for root also...
the lack of a removable battery makes bricking it a less of a possibility.. =/
pulling the usb mid disk transfer of a file wouldn't do anything but make the file corrupt and unusable, right?
Click to expand...
Click to collapse
What level of "bricked" are you looking for ? 1- can't be fixed by just a personal computer or 2-as useful as a piece of rock ?
Type 1: Removing the usb while flashing a radio/kernel update(using ruu.exe flasher from htc) will cause a corrupt bootloader/kernel and the phone might not be able to start the hardware (and hence bricked i guess)
to brick it you would have to make the bootloader(hardware) unable to recover itself,
Type 2:
if you really want it hard-bricked you can just connect all connectors on the motherboard randomly with a metal foil/wool.(tryed it on my laptop and worked)
EDIT: the bios chip was already soft-bricked due to a non-compatible feature that didn't allow my RAM to start, although motherboard WAS powering on)
You know its almost impossible to brick a phone as long as the hardware is ok, whether rooted or not. As manufacturers can flash stuff directly onto the chip.
Vcek said:
What level of "bricked" are you looking for ? 1- can't be fixed by just a personal computer or 2-as useful as a piece of rock ?
Type 1: Removing the usb while flashing a radio/kernel update(using ruu.exe flasher from htc) will cause a corrupt bootloader/kernel and the phone might not be able to start the hardware (and hence bricked i guess)
to brick it you would have to make the bootloader(hardware) unable to recover itself,
Type 2:
if you really want it hard-bricked you can just connect all connectors on the motherboard randomly with a metal foil/wool.(tryed it on my laptop and worked)
EDIT: the bios chip was already soft-bricked due to a non-compatible feature that didn't allow my RAM to start, although motherboard WAS powering on)
You know its almost impossible to brick a phone as long as the hardware is ok, whether rooted or not. As manufacturers can flash stuff directly onto the chip.
Click to expand...
Click to collapse
hmm.. good info, the case is fairly easy to remove without doing any physical damage to it. So just some foil to the connectors touching each other should short circuit it... that might work.
I can't flash a kernel or anything because it isn't rooted and can't root it either cause there isn't an exploit yet.
I'll try the foil out n see how that works.
Thanks dude.
doubledrake20 said:
hmm.. good info, the case is fairly easy to remove without doing any physical damage to it. So just some foil to the connectors touching each other should short circuit it... that might work.
I can't flash a kernel or anything because it isn't rooted and can't root it either cause there isn't an exploit yet.
I'll try the foil out n see how that works.
Thanks dude.
Click to expand...
Click to collapse
I think you can flash an RUU without rooting (you CAN'T flash an ruu with the bootloader UNLOCKED, not sure will work with "locked" but definitely will work with "relocked")
And for trying out the foil, i recommend you to be very careful as the warranty can be void by just opening the case(says so in manual)