Related
http://support.setool.net/showthread.php?3-UPDATES-AND-NEWS&p=74240#post74240
read down to Oct 27 news update.
This should kinda serve as a general warning to those who want to unlock their bootloader, though it is not fully confirmed as of yet
Please check production date of your model before any attempt
oh thats so scary. My phone is E16i and has a date of 11W34.
I was able to unlock and relock bootloader for so many times... does it mean that my phone will not get a bad luck on that?
whats resurruction cable method?
Sent from my E15i using xda premium
vientito said:
read down to Oct 27 news update.
This should kinda serve as a general warning to those who want to unlock their bootloader, though it is not fully confirmed as of yet
Please check production date of your model before any attempt
Click to expand...
Click to collapse
To spare everyone the trouble, here's the text of the post in question:
seems most of lately produced msm7227-based phones have chipset with FIXED security hole, which used to altbypass unlock.
(that is not 100% confirmed, we only have few reports, however better be warned)
such phones will DIE after successful unlock procedure.
such dead phones CAN NOT be recovered. ( perhaps, jtag can fix that, perhaps, qualcomm fixed jtag security hole too )
there is NO WAY to determine if phone has fixed chipset or chipset with security hole.
the ONLY safe way is to use unlock by resurrection cables.
if phone can be connected and booted by resurrection cables, phone is safe to unlock.
if phone can not be booted by resurrection cables, phone has fixed chipset and could not be unlocked.
you have been warned.
get and use resurrection cables.
update:
e16 phone with manufacture date 11w38 affected, i think we should care about phones which produced after 11w26
maliceomalice said:
whats resurruction cable method?
Click to expand...
Click to collapse
Seems to be a special designed interface to access the UART recovery mode on a hard bricked device (very low-level stuff, comes right after JTAG'ing). See this YouTube link.
If anyone of you ever followed the awesome Samsung unbrick posts by Adam Outler you should have an idea what UART access means and therefore should have a clue about what the "recovery cable" device is able to do.
The only thing that doesn't add up ... the recovery cable video doesn't show any interface for the W8/E16.
so does it mean newer phones cant unlock bootloader? so my w8 i bought from last week got brick during unlocking bootloader might be a victim of this new security hole? o ya...why must SE do this? to prevent us from bootloading?
....... I got my x8 12 months ago and I successfuly unlocked my bootloader. But what your basically saying is that newer phones can't be unlocked.. like the unlock tool to new phones is a deathtrap? Woooo. Watch out new buyers
sent from my x8 running gingerdx
Simply put, SE has a lot of stakes to protect.
wilbso said:
But what your basically saying is that newer phones can't be unlocked.. like the unlock tool to new phones is a deathtrap?
Click to expand...
Click to collapse
That's the point in case. If the phone is within the specified date of manufacturing you can successfully unlock the bootloader, but after you did the stunt and reboot the device it's basically hard bricked beyond "do it yourself at home" repair possibilities.
The best shot you then have left is to find a repair shop having a RIFF Box (JTAG) or the aforementioned Resurrection Cable (UART Recover) to breathe new life into the device.
However, it's at least good to know that this pithole is there (though I find it fascinating that they kept on fixing up the hardware flaws - or hardware based security holes - in the chipset). EDIT: Might also explain why some people experience weird problems with custom ROMs the majority isn't able to reproduce.
Mine's a 11W28 unlocked my bootloader and it's not bricked.......
B.Jay said:
That's the point in case. If the phone is within the specified date of manufacturing you can successfully unlock the bootloader, but after you did the stunt and reboot the device it's basically hard bricked beyond "do it yourself at home" repair possibilities.
The best shot you then have left is to find a repair shop having a RIFF Box (JTAG) or the aforementioned Resurrection Cable (UART Recover) to breathe new life into the device.
However, it's at least good to know that this pithole is there (though I find it fascinating that they kept on fixing up the hardware flaws - or hardware based security holes - in the chipset). EDIT: Might also explain why some people experience weird problems with custom ROMs the majority isn't able to reproduce.
Click to expand...
Click to collapse
Mine must have been within the specified date cuz like I said before
I unlocked it successfuly, its works perfect. But yeah, thanks for the explanation
sent from my x8 running gingerdx
wilbso said:
....... I got my x8 12 months ago and I successfuly unlocked my bootloader.
Click to expand...
Click to collapse
wilbso said:
Mine must have been within the specified date cuz like I said before I unlocked it successfuly, its works perfect.
Click to expand...
Click to collapse
If you got yours 12 MONTHS ago ... No, yours is NOT in the specified date!
11w26 (and onwards) seem to be problematic
11w38 (and onwards) seem to be sure hard brick
2011, wilbso - NOT 2010 (hint: we're still in 2011 for a few more days)
B.Jay said:
If you got yours 12 MONTHS ago ... No, yours is NOT in the specified date!
11w26 (and onwards) seem to be problematic
11w38 (and onwards) seem to be sure hard brick
2011, wilbso - NOT 2010 (hint: we're still in 2011 for a few more days)
Click to expand...
Click to collapse
Just cuz I got it 12 months ago dosnt mean the model was created then.... on he back of my x8 it says 10w47, that specific anough for ya?
sent from my x8 running gingerdx
Plus my phone is an e15 not an e16 as mentioned in earlier post that's its e16 not e15 phones that willl have the problem
sent from my x8 running gingerdx
amnher said:
oh thats so scary. My phone is E16i and has a date of 11W34.
I was able to unlock and relock bootloader for so many times... does it mean that my phone will not get a bad luck on that?
Click to expand...
Click to collapse
Mine with 11w33,, not bricked..., and always change with many custom kernel....
can explain me with it...?
@wilbso:
U mad, bro?
donny_mey said:
Mine with 11w33,, not bricked..., and always change with many custom kernel....
can explain me with it...?
Click to expand...
Click to collapse
Well, as we can only speculate on the Engrish post TheLaser made on the site from where the info comes from ...
W8/E16 phones within the range of 11W26 through 11W37 seem to be problematic. I interpret this as "there's some hardware fix though it can be worked around in software". If this now refers to flashtool or the replacement bootloader binary is up for anyone's guess.
11W38 and onwards seems to be a candidate for a sure kill after unlocking the bootloader. I interpret this as "the new bootloader binary that gets installed doesn't manage to start up because various 'security holes' have been fixed in the hardware therefore rendering the code defunct". That would at least explain why such hard bricks show no sign of life anymore at all (no LED, no screen, no nothing).
If you find a better theory or a better detailed description written in non-Engrish type ahead ...
B.Jay said:
@wilbso:
U mad, bro?
Well, as we can only speculate on the Engrish post TheLaser made on the site from where the info comes from ...
W8/E16 phones within the range of 11W26 through 11W37 seem to be problematic. I interpret this as "there's some hardware fix though it can be worked around in software". If this now refers to flashtool or the replacement bootloader binary is up for anyone's guess.
11W38 and onwards seems to be a candidate for a sure kill after unlocking the bootloader. I interpret this as "the new bootloader binary that gets installed doesn't manage to start up because various 'security holes' have been fixed in the hardware therefore rendering the code defunct". That would at least explain why such hard bricks show no sign of life anymore at all (no LED, no screen, no nothing).
If you find a better theory or a better detailed description written in non-Engrish type ahead ...
Click to expand...
Click to collapse
i realy sure about that but in 11w38 maybe killed with this act....
but i'm not sure for this,,,, or this a promotion tools from SE tool, and we must buy if we want to unlock that...
it's right...???
donny_mey said:
but i'm not sure for this,,,, or this a promotion tools from SE tool, and we must buy if we want to unlock that...
Click to expand...
Click to collapse
This is not a promotion from SE or any other company. The fact behind this is...
...that if you have a hard bricked W8 you need the "resurrection cable" thingy to _maybe_ restore the firmware on the phone (as there's no intel on how the "resurrection" is possible on the aforementioned models it's yet another guessing based on what has been written all over the place (read: "oberservation"), therefore the "maybe").
...that the safest way to attempt a bootloader unlock on said phones is to do it through the "resurrection cable" as only there you can tell IF it will work or not.
The only "promotion" in all of it is the heads-up on that piece of hardware a do-it-yourself-at-home technician (or privateer wanting to specialize in unbricking dead phones) may need - and that's all.
B.Jay said:
@wilbso:
U mad, bro? Is the 10w47 within the specified date. Because I unlocked bootloader without trouble
Well, as we can only speculate on the Engrish post TheLaser made on the site from where the info comes from ...
W8/E16 phones within the range of 11W26 through 11W37 seem to be problematic. I interpret this as "there's some hardware fix though it can be worked around in software". If this now refers to flashtool or the replacement bootloader binary is up for anyone's guess.
11W38 and onwards seems to be a candidate for a sure kill after unlocking the bootloader. I interpret this as "the new bootloader binary that gets installed doesn't manage to start up because various 'security holes' have been fixed in the hardware therefore rendering the code defunct". That would at least explain why such hard bricks show no sign of life anymore at all (no LED, no screen, no nothing).
If you find a better theory or a better detailed description written in non-Engrish type ahead ...
Click to expand...
Click to collapse
Sorry.... is 10w47 in the specific date? Cuz I managed to unlock bootloader and flash custom kernel. In about to flash another soon just need your oponion
sent from my x8 running gingerdx
wilbso said:
is 10w47 in the specific date? Cuz I managed to unlock bootloader and flash custom kernel. In about to flash another soon just need your oponion
Click to expand...
Click to collapse
10W## through 11W25 should be considered safe
(where 10W## means "from start of production all through 2010")
11W26 through 11W37 could turn out to be problematic
(though I'm not sure what Laser means by that exactly)
11W38 and newer are supposed to hard brick
("no sign of life" .. no LED, no vibrate, no screen, no flash-mode connection)
Note that this seems to apply to the W8 E16 AND X8 E15 as well ... in one of tohno's threads we have a hard bricked X8 (11W43) mentioned.
I'm still trying to make head and tails out of the random info, but I think it's safe to say that one should better have a look at the manufacturing code before trying to unlock the bootload to avoid a bad awakening.
Edit: On a second thought ... while we're still lacking in-depth details I think someone should prod one of the mods to post a sticky tagged as "[WARNING] Read BEFORE attempting bootloader unlock".
I can confirm a hard brick on my Xperia x8 (11w40) when trying to unlock my bootloader.
So, i've tried to unlock bootloader using this guide: http://forum.xda-developers.com/showthread.php?t=1254225
The first part (up to step 5c) ha gone really smoothly, without any complications.
However when i tried to connect phone to Flashtool all i got was "Device connected with USB debugging off". So then i decided to do the dumbest thing (now i know that) i could do: reboot my phone. Now it's not powering on, so I'm assuming it's bricked.
So my questions:
1. Is it bricked beyond all repair, and i cannot do anything about it, or perhaps there is still some hope left for me?
2. If it's bricked, will service be able to help me? And if yes then how much approximetly would they charge me for that (I'm assuming that my warranty is void because of my attempts)?
kw4ss said:
So, i've tried to unlock bootloader using this guide: http://forum.xda-developers.com/showthread.php?t=1254225
The first part (up to step 5c) ha gone really smoothly, without any complications.
However when i tried to connect phone to Flashtool all i got was "Device connected with USB debugging off". So then i decided to do the dumbest thing (now i know that) i could do: reboot my phone. Now it's not powering on, so I'm assuming it's bricked.
So my questions:
1. Is it bricked beyond all repair, and i cannot do anything about it, or perhaps there is still some hope left for me?
2. If it's bricked, will service be able to help me? And if yes then how much approximetly would they charge me for that (I'm assuming that my warranty is void because of my attempts)?
Click to expand...
Click to collapse
try flashtool
for unlocking bootloader easier way
http://forum.xda-developers.com/showthread.php?t=1267273
flashtool http://forum.xda-developers.com/showthread.php?t=986697
for more info : http://forum.xda-developers.com/showthread.php?t=1399381
kw4ss said:
So, i've tried to unlock bootloader using this guide: http://forum.xda-developers.com/showthread.php?t=1254225
The first part (up to step 5c) ha gone really smoothly, without any complications.
However when i tried to connect phone to Flashtool all i got was "Device connected with USB debugging off". So then i decided to do the dumbest thing (now i know that) i could do: reboot my phone. Now it's not powering on, so I'm assuming it's bricked.
So my questions:
1. Is it bricked beyond all repair, and i cannot do anything about it, or perhaps there is still some hope left for me?
2. If it's bricked, will service be able to help me? And if yes then how much approximetly would they charge me for that (I'm assuming that my warranty is void because of my attempts)?
Click to expand...
Click to collapse
Answers:
1. A cellphone technician with a JTAG/RIFF BOX tool can fix your phone, or the alternative is by replacing the motherboard of your device, you cannot fix at home, that is for sure not unless you have this devices and know how to use it.
2. As for the warranty, just play dumb and say that you dont know what happen to your device. Your warranty is safe as long as they didnt find out that you have mess up the bootlader, IDK much about this, but for me this work.
It happens that, x8 that has been manufactured in 11w26 to 11w37 is problematic and 11w38 beyond is surely bricked if tried to unlock the bootlader. The issue is, they have fixed the security loophole in the bootloader in the later releases. I have 11w44 x8 black that has been hard bricked a few days ago, and I just play dumb in the service center, and they didnt asked anything, it has been covered in the warranty, so free service.
kirmada said:
try flashtool
for unlocking bootloader easier way
http://forum.xda-developers.com/showthread.php?t=1267273
flashtool http://forum.xda-developers.com/showthread.php?t=986697
for more info : http://forum.xda-developers.com/showthread.php?t=1399381
Click to expand...
Click to collapse
Yeah, when i try
Step 1: (Downloads)
A) Download Flash Tool : From http://forum.xda-developers.com/showthread.php?t=920746 or http://www.multiupload.com/GYL7A7XQBT
B) Download S1tool : From http://forum.xda-developers.com/show...0&postcount=26
C) Download Unlocker : From http://forum.xda-developers.com/show...77&postcount=3
Step 2: (Prepare)
A) Unzip all downloaded files
B) Shut Down Phone
C) Open S1tool, Click on DO JOB, Press Back on phone, Connect it to PC.
D) Look For Line "XXXX SIMLOCK CERTIFICATE"
Step 3: (Unlock)
A) Turn the phone on, Connect it with PC in Debugging mode.
B) if XXXX is "NOT RECOGNIZED" then sorry, it can't be unlocked.
C) if XXXX is SEMC then run "msm7227_semc.cmd"
D) if "XXXX SIMLOCK CERTIFICATE" was not found then run "msm7227_Setool2.cmd"
E) Wait...
F) if "Press any key to continue . . ." is found, press any key.
Step 4: (Verify)
A) Shut Down Phone
Click to expand...
Click to collapse
This is basically what I did. However when i try to power on phone it does not respond. Also when I try the second part:
B) Open S1tool, Click on DO JOB, Press Back on phone, Connect it to PC.
C) Look For Line RUNNING S1_EROM VER "x8A029"
D) if x is "r" then it is done, Congrats...
E) if x is "R" then Sorry, Do everything again. or Search in the Frorum for Help
Click to expand...
Click to collapse
nothing happens when I connect phone to PC.
I still have the same message: "PLEASE ATTACH TURNED OFF PHONE NOW"
kirmada said:
try flashtool
for unlocking bootloader easier way
http://forum.xda-developers.com/showthread.php?t=1267273
flashtool http://forum.xda-developers.com/showthread.php?t=986697
for more info : http://forum.xda-developers.com/showthread.php?t=1399381
Click to expand...
Click to collapse
OP is in a state that it cannot be recovered through home remedies, it is a hard bricked phone. I know it because, been there done that.
Symptoms:
doesnt turn on, no LED(RED), cant enter FLASH MODE, no vibrate, nothing at all, almost same as a brick literally.
Cause:
Damaged bootlader
hixvolnutt said:
OP is in a state that it cannot be recovered through home remedies, it is a hard bricked phone. I know it because, been there done that.
Symptoms:
doesnt turn on, no LED(RED), cant enter FLASH MODE, no vibrate, nothing at all, almost same as a brick literally.
Cause:
Damaged bootlader
Click to expand...
Click to collapse
yes, its a hardbrick too i guessed,but everything is worth a try
so its for service center now
hixvolnutt said:
Answers:
1. A cellphone technician with a JTAG/RIFF BOX tool can fix your phone, or the alternative is by replacing the motherboard of your device, you cannot fix at home, that is for sure not unless you have this devices and know how to use it.
2. As for the warranty, just play dumb and say that you dont know what happen to your device. Your warranty is safe as long as they didnt find out that you have mess up the bootlader, IDK much about this, but for me this work.
It happens that, x8 that has been manufactured in 11w26 to 11w37 is problematic and 11w38 beyond is surely bricked if tried to unlock the bootlader. The issue is, they have fixed the security loophole in the bootloader in the later releases. I have 11w44 x8 black that has been hard bricked a few days ago, and I just play dumb in the service center, and they didnt asked anything, it has been covered in the warranty, so free service.
Click to expand...
Click to collapse
So there is still some hope for me! yay!
hixvolnutt said:
OP is in a state that it cannot be recovered through home remedies, it is a hard bricked phone. I know it because, been there done that.
Symptoms:
doesnt turn on, no LED(RED), cant enter FLASH MODE, no vibrate, nothing at all, almost same as a brick literally.
Cause:
Damaged bootlader
Click to expand...
Click to collapse
Yup, not even a light indicating battery charging when i connect it to charger.
kw4ss said:
Yeah, when i try
This is basically what I did. However when i try to power on phone it does not respond. Also when I try the second part:
nothing happens when I connect phone to PC.
I still have the same message: "PLEASE ATTACH TURNED OFF PHONE NOW"
Click to expand...
Click to collapse
There is nothing wrong with the procedures that has been provided by the guide, its just that there is something wrong with your phone, most probably youre x8's mfc is 11w38 or up, "remove your battery, then look for the e.g. 11w38 something like that in the back of your phone, 11 is year 38 is week that it has been manufactured."
hixvolnutt said:
There is nothing wrong with the procedures that has been provided by the guide, its just that there is something wrong with your phone, most probably youre x8's mfc is 11w38 or up, "remove your battery, then look for the e.g. 11w38 something like that in the back of your phone, 11 is year 38 is week that it has been manufactured."
Click to expand...
Click to collapse
11w43...
damn...
someone really should add warning about this somewhere where it would be visible
Any experiences with 11w34???
kw4ss said:
11w43...
damn...
someone really should add warning about this somewhere where it would be visible
Click to expand...
Click to collapse
there is,u did not lookout iguess
http://forum.xda-developers.com/showthread.php?t=1399381
kw4ss said:
11w43...
damn...
someone really should add warning about this somewhere where it would be visible
Click to expand...
Click to collapse
There already one, the thread "warning ahead of unlocking bootloader"...its in this section
Sent from my E15i using xda premium
kirmada said:
there is,u did not lookout iguess
http://forum.xda-developers.com/showthread.php?t=1399381
Click to expand...
Click to collapse
i meant to that thread with guide. because honestly, i only checked things that guide said i have to check, didnt look any further to find out if i can or cannot unlock.
Anyway, looks like it's a trip to service center for me.
hixvolnutt said:
Answers:
1. A cellphone technician with a JTAG/RIFF BOX tool can fix your phone, or the alternative is by replacing the motherboard of your device, you cannot fix at home, that is for sure not unless you have this devices and know how to use it.
2. As for the warranty, just play dumb and say that you dont know what happen to your device. Your warranty is safe as long as they didnt find out that you have mess up the bootlader, IDK much about this, but for me this work.
It happens that, x8 that has been manufactured in 11w26 to 11w37 is problematic and 11w38 beyond is surely bricked if tried to unlock the bootlader. The issue is, they have fixed the security loophole in the bootloader in the later releases. I have 11w44 x8 black that has been hard bricked a few days ago, and I just play dumb in the service center, and they didnt asked anything, it has been covered in the warranty, so free service.
Click to expand...
Click to collapse
How long did you receive your phone after you get sent it to the service center?
I had 11w34 and unlocked bootloader just fine but am afraid of doin it to a new one just bought 11w48, any ways i tried this morning but nothing happen just got a message on cmd adb not a valid command and to press any key to exit
Sent from my E15i using XDA
Hardbircked
I just hardbricked my friend's phone, it was a 11w41, so he is going to claim his warranty tomorrow, do you know if there is some way to unlock bootloader to a 11w41+???
hi,
I bought a X8 by mail delivery from the internet and got a bricked phone (so it seems)!
Symptom is phone doesn't connect to GSM network, and although i can scan for networks i can't connect to them. Tried several networks, same result. Everything else seems to work fine.
I'm completely newbie to Android phones, and only bought this one to try to avoid to stay behind, but this was a lousy way to start. I've been browsing through the forum, but there's too much info which only makes it more confusing to me.
I tried connecting the phone to S1tool and msm7227setool but i can't find the SEMC flash drivers, and although i browsed through the forum stickies for them i didn't find them.
So, my questions are:
1- Can someone provide a link to the drivers?
2- Is the following link the best way to solve my problem?
http://forum.xda-developers.com/showthread.php?t=1304258&highlight=no+network
3- I also want to debrand the phone, from the 360 apps i assume the phone is from vodafone. Can you recommend a fast ROM with full features support? And a good noob proof flash tutorial..
4- Will any of the above operations remove my SP unlock?
Sorry if most (or all) of this questions are a repetition of past threads, but starting with a phone this way, i honestly feel like a donkey looking at a palace! (Portuguese proverb, not sure you'll understand)
Thanks, Regards!
madz78 said:
hi,
I bought a X8 by mail delivery from the internet and got a bricked phone (so it seems)!
Symptom is phone doesn't connect to GSM network, and although i can scan for networks i can't connect to them. Tried several networks, same result. Everything else seems to work fine.
I'm completely newbie to Android phones, and only bought this one to try to avoid to stay behind, but this was a lousy way to start. I've been browsing through the forum, but there's too much info which only makes it more confusing to me.
I tried connecting the phone to S1tool and msm7227setool but i can't find the SEMC flash drivers, and although i browsed through the forum stickies for them i didn't find them.
So, my questions are:
1- Can someone provide a link to the drivers?
2- Is the following link the best way to solve my problem?
http://forum.xda-developers.com/showthread.php?t=1304258&highlight=no+network
3- I also want to debrand the phone, from the 360 apps i assume the phone is from vodafone. Can you recommend a fast ROM with full features support? And a good noob proof flash tutorial..
4- Will any of the above operations remove my SP unlock?
Sorry if most (or all) of this questions are a repetition of past threads, but starting with a phone this way, i honestly feel like a donkey looking at a palace! (Portuguese proverb, not sure you'll understand)
Thanks, Regards!
Click to expand...
Click to collapse
I have a X8 on Vodafone, and when I repairded my X8 in PCC it removed the vodafone apps and icon from Settings :-D
Sent from my tablet running Honeycomb
IrishStuff09 said:
I have a X8 on Vodafone, and when I repairded my X8 in PCC it removed the vodafone apps and icon from Settings :-D
Sent from my tablet running Honeycomb
Click to expand...
Click to collapse
Just 4 curiosity how to make the vodafone icons appear again??just4fun
Sorry for off-topic thing
As irishstuff said u should try to update your phone with pc companion(google it) and try to update the software.After that if u want to root your phone and install recovery search in xda for x8toolbox , is the most noob-friendly thing u will find
X8invisible13 said:
Just 4 curiosity how to make the vodafone icons appear again??just4fun
Sorry for off-topic thing
As irishstuff said u should try to update your phone with pc companion(google it) and try to update the software.After that if u want to root your phone and install recovery search in xda for x8toolbox , is the most noob-friendly thing u will find
Click to expand...
Click to collapse
Thanx for clarifying that.
But, if i update the phone via PCC, won't i lose the sp unlock? I'm saying this cuz i read that the no network problem is due to sim lock protection.
madz78 said:
Thanx for clarifying that.
But, if i update the phone via PCC, won't i lose the sp unlock? I'm saying this cuz i read that the no network problem is due to sim lock protection.
Click to expand...
Click to collapse
sp unlock? You mean "SIM unlocked"?
No, you won't lose the unlocked SIM by simply flashing back to Stock through PC Companion (in case PCC tells you that there's no update available you need to resort to the Flashtool method).
As for the drivers ... best method would be to install PC Companion. However, if you don't want that crapware on your system I can upload you the drivers (out of PCC) in a ZIP - then you have to point Windows manually to the directory so it can find the appropriate driver (EDIT: shouldn't be much of a trouble if you're familiar with installing drivers by pointing Windows to the directory or the INF file).
The only situation where you might lose your SIM unlock is at unlocking the boot loader to enable installation of custom kernels, but before you head into that you better check the manufacturing date of your phone (sticker below the battery) and then look through this forum to work out if it's a candidate for hard bricking or not.
B.Jay said:
sp unlock? You mean "SIM unlocked"?
No, you won't lose the unlocked SIM by simply flashing back to Stock through PC Companion (in case PCC tells you that there's no update available you need to resort to the Flashtool method).
As for the drivers ... best method would be to install PC Companion. However, if you don't want that crapware on your system I can upload you the drivers (out of PCC) in a ZIP - then you have to point Windows manually to the directory so it can find the appropriate driver (EDIT: shouldn't be much of a trouble if you're familiar with installing drivers by pointing Windows to the directory or the INF file).
The only situation where you might lose your SIM unlock is at unlocking the boot loader to enable installation of custom kernels, but before you head into that you better check the manufacturing date of your phone (sticker below the battery) and then look through this forum to work out if it's a candidate for hard bricking or not.
Click to expand...
Click to collapse
Yup, it says up to date, just clicked repair to see if it works. crapware.. lol, yeah i'd appreciate that zip file, thanks.
I think the issue is exactly that, a bad boot loader unlock, at least all symptoms point to that.. all i see in no network threads seems to be pointing there.
Thanx!
P.S.- SP (service provider) Unlocked.
madz78 said:
yeah i'd appreciate that zip file, thanks.
Click to expand...
Click to collapse
Download here
The Sony Ericsson X8 (and possibly other SE phones) Android drivers (ADB / Smartphone / USB Flash Device) for Windows (incl. x64 Editions) out of the latest and greatest PC Companion crapware.
madz78 said:
I think the issue is exactly that, a bad boot loader unlock, at least all symptoms point to that.. all i see in no network threads seems to be pointing there.
Click to expand...
Click to collapse
Errr... no. A "unsuccessful" boot loader unlock would turn your device into a hard brick (no lights, no vibration, no screen). As you're able to boot up into Android the bootloader and kernel seems to be intact.
IF the previous owner (in case you bought it used) tinkered around with boot loader unlocking ...
Use the s1tool to verify if the boot loader is locked or not. If it's unlocked simply follow the tutorial in the Development section to relock the boot loader or try the trick deedii posted about first (she had the same problem that GSM radio went dead after unlocking the boot loader).
---------- Post added at 12:40 AM ---------- Previous post was at 12:36 AM ----------
*ping* driver ZIP download link inserted
Holy crap!
Thanx for the zip btw..
I hit Repair in PCC and it re-flashed the phone. Now, instead of no network, the phone doesn't recognize ANY SIM card!!
I checked boot loader with S1tool, and the phone is locked (i see R).
I'm starting to think maybe it's a hardware problem and not from ROM.
Any ideas? Thanks.
madz78 said:
Thanx for the zip btw..
Click to expand...
Click to collapse
No problem, you're welcome.
madz78 said:
I hit Repair in PCC and it re-flashed the phone. Now, instead of no network, the phone doesn't recognize ANY SIM card!!
I checked boot loader with S1tool, and the phone is locked (i see R).
I'm starting to think maybe it's a hardware problem and not from ROM.
Any ideas? Thanks.
Click to expand...
Click to collapse
Yes, the "R" means the boot loader is locked.
As for the mSD card ... here's where we enter "trouble reloaded":
- What card? Class? Size? Brand?
- Does the card hold any important data? If not try to reformat the card (FAT32!!!). If Android refuses to format the mSD simply use a card reader and re-format the mSD in Windows.
EDIT: Also, just to make sure everything's vanilla: could you please take a look into Settings -> About phone to confirm you're running the genuine SE baseband/kernel and not some custom kernel?
EDIT 2: Errrrrrrrr.... never mind ... I somehow misread "SIM card" as "SD card". My fault!
X8invisible13 said:
Just 4 curiosity how to make the vodafone icons appear again??just4fun
Sorry for off-topic thing
As irishstuff said u should try to update your phone with pc companion(google it) and try to update the software.After that if u want to root your phone and install recovery search in xda for x8toolbox , is the most noob-friendly thing u will find
Click to expand...
Click to collapse
I actually don't have a clue, but I was glad when thety went
I dont like operators branding the phone with the software
The only apps i had by the operator (vodafone IE) were
Gold Rush, Vodafone Music Store, SIM Settings and SIM Toolkit <- I have GDX and i still have toolkit. XD
I had the 'vodafone 360' option in Settings
Sent from my tablet running Honeycomb
B.B.- M76XX-TSNCJOLYM-53404015
kernel- 2.6.29 [email protected] #1
Thanks again.
madz78 said:
B.B.- M76XX-TSNCJOLYM-53404015
kernel- 2.6.29 [email protected] #1
Click to expand...
Click to collapse
Yes, that's definitely the genuine baseband and kernel.
However, no matter how hard I think it through I don't see a good reason why it won't accept ANY SIM card, as a SIM unlock (or carrier/operator unlock if you want to put it that way) is as good as permanent unless you play around with unlocking the bootloader and either do something wrong or face the problem that it suddenly reverts back to the original SIM lock (in case it got unlocked and didn't ship unlocked by default).
The only problem I know about is ... if you live in a region where you would actually need a E15a baseband but happen to have the E15i baseband (you know, has to do with the frequencies that get used to transmit between your phone and the tower) flashed - or the other way around - you won't be able to connect to the GSM/3G network - but even then the phone won't reject the SIM card but simply fail to find any network.
In that case the problem resolve would be as easy as swapping out the baseband through flashing by Flashtool.
Good morning,
This keeps getting more and more confusing... thank god you've been such a valuable help BJ!
Dunno if it's "don't accept SIM" as much as don't recognize them.. I usually remove PIN codes from all my SIM's but today i've popped a new one to see if anything different happened.. The phone asked me for pin and validated it, but after this it doesn't recognize it anymore, i get a SIM with a red "!" on top of it in the upper right corner of the screen (same icon you get without SIM in phone).
As for all the other cards, it doesn't appear such icon, the phone starts normally and then asks for language and after asks to "insert SIM and restart phone"..
I don't think baseband is the problem, i think it's definitely related to SIM card reading.
NOTE: Before seemed irrelevant but now seems important to say, before, when i scanned for networks and tried to connect to one (same from SIM), phone gave me a message saying something like "your SIM card doesn't allow connecting to this network".
The problem seems to be definitely SIM card reader, the big doubt is if it's HW or SW.
My best guess is SW, because he can read PIN's but then just locks.. Where is the SIM card reader "driver"? baseband, kernel, ROM? should i try to update all those?
Thanks again!
hello again,
i found this in SETool forum which seems to be exactly my problem.
E15i - (x8) it doesn't read sim card and hangs during unlocking
I've had a problem with XPERIA X8 (E15i) for a long time now and I can't fix it.
I was trying to unlock it. I updated Android to v. 2.1. I have credits, I turn on debugg mode, I installed drivers. I push 1,2,5 and press Unlock/Repair.
Unfortunately it didn't finish, the program froze and switched off (on Vista). It took 5 credits. After turning it back on it wouldn't log to the network, even though it saw the network. But it shows that the phone is unlocked. By Setool I installed the version form after the update. After that it stopped detecting the sim card.
In hosting I read that I should repeat the unlock. I reinstalled the drivers, downloaded setool's previous version (v1.1106), but the program hangs every time in the same place and it doesn't go to the end (see screen below). With v1.1107 there's the same problem. I tried on Vista and XP – no difference. I installed setool on my other computer, where there are no boxes, drivers or antiviruses and still I couldn't succeed.
Does anyone have some expirience with the x8?
Thx in advance for help.
---------------
Reply
1.
reflash phone with generic 2.1 firmware, repeat unlock procedure.
2.
to restore phone to original state, write as script most earlier secunits backup from backup\%imei% folder
Click to expand...
Click to collapse
Could this be a bad unlock problem?
Thanx.
IrishStuff09 said:
I actually don't have a clue, but I was glad when thety went
I dont like operators branding the phone with the software
The only apps i had by the operator (vodafone IE) were
Gold Rush, Vodafone Music Store, SIM Settings and SIM Toolkit <- I have GDX and i still have toolkit. XD
I had the 'vodafone 360' option in Settings
Sent from my tablet running Honeycomb
Click to expand...
Click to collapse
Sim toolkit is on every phone,not only on vodafone
Been reading more and more, and this seem to be a very common issue in SETool SIM unlocking. can anyone suggest a solution?
Thanks.
Hello again,
I've been trying to run msm7227 setool2 and semc, but seem to be getting nowhere.. enters debugging mode and nothing else. What am i doing wrong?
Also, i've read in the following thread that sometimes boot is unlocked and S1tool says it's locked, but i can't find SEUS to download anywhere in the forum..
http://forum.xda-developers.com/showthread.php?t=1404148&highlight=sim+card
HEEELLP!!!
Thanks.
Hi, madz ...
To pull it together:
- The "SIM reader" is a software that comes as a part of Android in the form of a system app (inside /system/app). You can't exchange the related parts as they are specific to the Android version, in case your thoughts are running into this direction.
- The problem with "SEtool" is more like this ...
Let us assume the phone was originally SIM locked (bound to only allow SIMs of a specific operator/carrier) and then got SIM unlocked. The original SIM lock will jump back into place once the the boot loader got unlocked.
My observation is that this problem should actually go away once the boot loader got re-locked again. That being said I also read various threads where the SIM lock didn't vanish and the phone had to be unlocked anew.
On another note, it also depends on how the phone got unlocked ... there's a difference if it got SIM unlocked through SEtool or through Omious (<-- I hope it's spelled right)
The one fact that remains: simply querying the boot loader status ("R" vs "r") does not make the SIM lock to fire.
- SEUS ... well ...
I found Update Service (SEUS) 2.11.10.7 in the depths of my hard drive. Going to slap it on MultiUpload for you in a minute - though I can't guarantee that it still works; all I know is that SEUS got discontinued (or something along that line). Wait for the edit of the download!
EDIT: MultiUpload swallowed the file --> Download link
---------- Post added at 01:07 AM ---------- Previous post was at 12:59 AM ----------
Missed this one ...
madz78 said:
I've been trying to run msm7227 setool2 and semc, but seem to be getting nowhere.. enters debugging mode and nothing else. What am i doing wrong?
Click to expand...
Click to collapse
Shouldn't you connect the phone in flash mode instead of USB-Debugging mode?
Flash Mode means:
- Pull the USB cable out of your computer but leave it attached to the phone
- Turn the phone OFF
- Start the software
- Press the Back button and connect the USB cable to the computer
KEEP THE BACK BUTTON PRESSED UNTIL THE PHONE IS RECOGNIZED!
(Note: Windows may want to install the "SEMC Flash Device" driver)
Hi BJ,
The phone is not locked! it accepts pin from all networks, but after this, simply doesn't read the cards anymore. I only talked about this because the thread i found in SETOOL forum explains in detail what's happening to me.
I dunno if what happens to people who have no network or sim locked due to bad boot loader unlock is the same or not. It would be nice to know, but in my thread no one except you steps up.
If unlocked, i believe it's SETool and not Omnius because i only see threads with this issue in SETool support (dozens of complains) and found nothing in Omnius.
I still believe that maybe there's a solution other than unlocking it again, but due to inexperience i fail to see it.
about msm7227: i'm sorry, i meant flash mode, and it detects the phone, sometimes.. but always hangs in 2nd line (can't remember what said, but i'll try it again in a while and post here).
Where exactly is the phone unlocked? ROM, kernel, baseband? Do you think re-flashing it could solve the problem?
Thanks again friend!
Regards.
madz78 said:
The phone is not locked! it accepts pin from all networks, but after this, simply doesn't read the cards anymore. [...]
I dunno if what happens to people who have no network or sim locked due to bad boot loader unlock is the same or not. It would be nice to know, but in my thread no one except you steps up.
Click to expand...
Click to collapse
My X8 came SIM unlocked by default. Since it's old enough, and therefore safe for boot loader unlocking, I gave it a try (even been as daring as to unlock while having GDX v021 flashed).
Connected and checked with s1tool that it's suited for unlocking: Pass
Unlocked the boot loader: Pass
Booted up (SIM does not have PIN1 set)...
Connecting to the GSM Network: Pass
Connecting to the APN for 3G Internet access: Pass
Reboot (to make sure it didn't brick): Pass
Re-locked boot loader: Pass
Checked with s1tool that boot loader is locked: Pass
Device still able to connect to GSM/3G: Pass
I didn't try to flash a custom kernel but just stayed with the stock kernel. During the whole testing scenario - from unlocking to re-locking - I didn't have any problems with GSM/3G network connectivity or troubles reading the SIM.
Like I wrote above the PIN1 check was disabled because sometimes GingerDX shows the "Network unlock" screen after inputting the PIN ... that's more-or-less a bug workaround.
madz78 said:
If unlocked, i believe it's SETool and not Omnius
Click to expand...
Click to collapse
Thank you for correcting the spelling of "Omnius" ... I was typing it from the top of my head and failed to recall how it's spelled.
madz78 said:
Where exactly is the phone unlocked? ROM, kernel, baseband? Do you think re-flashing it could solve the problem?
Click to expand...
Click to collapse
If you refer to "how is the SIM lock lifted" then I think the best persons to answer this question are the guys who cracked the boot loader. I don't know enough about how the low-level init of the phone really works ... the boot loader guys aren't very chatty about telling us how the low-level boot of the X8 works.
Since, in my case, the SIM unlock prevails when flashing a custom ROM on top of the stock kernel (keep in mind I never flashed a custom kernel, so I never altered the "baseband" partition) the unlock can't reside in the ROM partitions.
But ... as the problem only arises when tinkering around with the boot loader but didn't affect my phone during boot loader unlock / re-lock ... and this is now purely guessing ...
The boot loader unlock only replaces the boot loader binary with a altered one. So if the thing that tells the phone that it's SIM unlocked resides in the part of the NAND where the boot loader / kernel / baseband is located it can only be a digital certificate or some sort of a binary that gets loaded through "Stage 1" init (during which the boot loader and kernel gets loaded and all the security checking stuff happens). It can't be in the higher init routines where the initialized kernel is boot strapping the ROM as that would disable the SIM unlock when flashing a custom ROM.
If blagus or the kernel devs have some ideas it would be great to read a few lines from a source knowing about the low-level init routines (to actually understand how the X8 comes to life once the power button is pressed).
On another thought ... the msm7227 CPU also must have some kind of firmware (think of it similar to a BIOS like a PC has) to init itself and the hardware ... maybe the SIM unlock is somewhere in there?
EDIT: On a third thought ... it would seem almost logical that the SIM unlock stuff is stored somewhere in the "security" related part of the NAND (somewhere deep down at the low-level init). If the phone came locked and got unlocked at some point the original SIM lock will most likely spring back into place at boot loader unlocking - so the SIM locked/unlocked thingy has to be somewhere in the low-level boot init; otherwise it wouldn't disable a "soft unlock" once the boot loader got unlocked and replaced past the cracked one which bypasses a whole lot of the security checks so unsigned boot binaries (kernel) can be loaded and executed.
I got through msm7227_semc the boot loader unlock the phone but then no longer clear.
I'm doing?
My phone is not clear
sorry for my english
omidsys said:
I got through msm7227_semc the boot loader unlock the phone but then no longer clear.
I'm doing?
Click to expand...
Click to collapse
By "no longer clear" you mean what?
You unlocked the boot loader and now the phone does NOT show any light, vibration or things on the screen anymore?
Simply try to describe the problem in a few words so we can get the idea.
got the same issue unlocking bootloader, wait till process is dne completely!
then verify using s1 tool if unlocked!
ur fone shud boot up! hope ur on stock rom
Sent from my E15i using XDA App
B.Jay said:
You unlocked the boot loader and now the phone does NOT show any light, vibration or things on the screen anymore?
.
Click to expand...
Click to collapse
Yes! I have exactly the same
The phone does not react.
The phone does not power.
In this case I'm very sorry to break it over to you, but this is a hard brick - especially if the manufacturing date of your phone is 11W29 or newer (11W30, 11W31, 11W32, ...) - take out the battery and look at the sticker below.
There's no way left by which you can "repair" the phone yourself. You need to either take the phone to a repair shop (if such a thing even exists in Iran) or send it in for repair.
From the hard bricks we observed around here the repair measure will be that the motherboard needs to be replaced past a working one.
Simply take a look in the X8 Q&A section and have a look at the "Warning ahead of unlocking bootloader" thread.
B.Jay said:
In this case I'm very sorry to break it over to you, but this is a hard brick - especially if the manufacturing date of your phone is 11W29 or newer (11W30, 11W31, 11W32, ...) - take out the battery and look at the sticker below.
There's no way left by which you can "repair" the phone yourself. You need to either take the phone to a repair shop (if such a thing even exists in Iran) or send it in for repair.
From the hard bricks we observed around here the repair measure will be that the motherboard needs to be replaced past a working one.
Simply take a look in the X8 Q&A section and have a look at the "Warning ahead of unlocking bootloader" thread.
Click to expand...
Click to collapse
yes.Date of manufacture 11w40
Whether the box is setool?
omidsys said:
yes.Date of manufacture 11w40
Click to expand...
Click to collapse
Yap, that phone is dead.
omidsys said:
Whether the box is setool?
Click to expand...
Click to collapse
I honestly don't get what you mean, but the hard brick you now have in your hands was caused by two facts ...
1. The phone being manufactured 11W40 (way past 11W29 where the trouble starts) means that the chips used in your phone are of a newer revision which have the security hole the boot loader unlock tool uses closed. At the moment you unlock the boot loader you kill the phone.
2. You didn't do your homework in gathering info about the boot loader unlock procedure. While the guys maintaining the "How to unlock the boot loader" are ignorant to inserting the hard brick warning, a simple in-depth reading of the X8 related boards and posts would have spared you this fate.
The only way to get the phone back to work now is to, as written above, take it to a repair shop or to send it to Sony Ericsson.
Try charging the bettery ,full, then begin the whol process again
Sent from my E15i using XDA App
B.Jay said:
Yap, that phone is dead.
I honestly don't get what you mean, but the hard brick you now have in your hands was caused by two facts ...
1. The phone being manufactured 11W40 (way past 11W29 where the trouble starts) means that the chips used in your phone are of a newer revision which have the security hole the boot loader unlock tool uses closed. At the moment you unlock the boot loader you kill the phone.
2. You didn't do your homework in gathering info about the boot loader unlock procedure. While the guys maintaining the "How to unlock the boot loader" are ignorant to inserting the hard brick warning, a simple in-depth reading of the X8 related boards and posts would have spared you this fate.
The only way to get the phone back to work now is to, as written above, take it to a repair shop or to send it to Sony Ericsson.
Click to expand...
Click to collapse
I've pm'ed the op to put the bootloader warning long ago.
To this thread op.. ur phone is dead.. take it to sony center for repair..
Sent from my Android using Tapatalk
joe200 said:
I've pm'ed the op to put the bootloader warning long ago.
Click to expand...
Click to collapse
That was a good idea on your behalf (will give a thanks to you), though it seems the warning didn't stick or wasn't understood in full.
Well, seems to be a somewhat common issue that English seems to be too hard to learn.
why r my phone get hard bricked after succesfully unlock bootloader ..the script is like these ..
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
1743 KB/s (585731 bytes in 0.328s)
error: protocol fault (no status)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
192 KB/s (3087 bytes in 0.015s)
success
Waiting ...
Getting ROOT rights.
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
504 KB/s (8064 bytes in 0.015s)
Second, we need to write semcboot
1130 KB/s (596916 bytes in 0.515s)
successfully wrote 0003ff00
Press any key to continue . . .
after that my phone won't boot nor any green light ..please help ..
it's my friends phone and his brother bought it for his mother and i was giving him a stupid idea that unlock bl will make phone more faster ..
Edit : ..i have unlock bl before using my own x8 and it went well ..no problem at all ..but my friends phone ..well ..
try removing the battery and putting it back and try again to start the phone.
i unlocked bootloader a few days ago got the same log and everything worked well
before putting your battery back..post here the 11wXX number behind the battery.
well ..its my friends phone but i'll ask em when he comes ..but ..i did tried remove the battery for couple of minutes ..the battery status is about 32% before i unlock the bl ..when use s1tool to identify, ..it can't even detect the phone anymore ..like i said ..not even a green light ..
they said if there were a green light, then i will have a little hope left ..
EDIT : ..the battery is 11w29
i think after 11w28 if you successfully unlock the bootloader,your phone is DEAD......saw it in the bootloader unlocking thread....
hope it helps
ohh my
great ..looks like i'm going to replace my friends phone ..uhh ..i don't have that much kind of money ..thanks though~
caer_ayu said:
11w29
Click to expand...
Click to collapse
That's exactly the start of the manufacturing date range where the "hard brick upon boot loader unlock starts.
In short - if it does not show any signs of life (no LED, no vibrate, no screen) you can safely assume it's dead now.
humm... read this thread
http://forum.xda-developers.com/showthread.php?t=1399381
I think you are unlucky!
Sorry for my bad english!
pesky_89 said:
try removing the battery and putting it back and try again to start the phone.
i unlocked bootloader a few days ago got the same log and everything worked well
before putting your battery back..post here the 11wXX number behind the battery.
Click to expand...
Click to collapse
what about my 11W14 and my friends 10W33 ??is it safe to unlock bootloader??
wanazrimuahaha said:
what about my 11W14 and my friends 10W33 ??is it safe to unlock bootloader??
Click to expand...
Click to collapse
11w28 bellow = safe
11w29 above = risky
can it be fix by jtag ? ..who live's in malaysia and stay around ipoh ..does ipoh have jtag ? ..i've search at google but it only came out jtag xbox360 ..wtf
EDIT : even though if i send it back to se cause the phone was bought only 1 week, will they notice that the warranty has been sealed because i root first before unlock the bl ..even though tried to unlock the bl ..will they notice ?
caer_ayu said:
can it be fix by jtag ? ..who live's in malaysia and stay around ipoh ..does ipoh have jtag ? ..i've search at google but it only came out jtag xbox360 ..wtf
EDIT : even though if i send it back to se cause the phone was bought only 1 week, will they notice that the warranty has been sealed because i root first before unlock the bl ..even though tried to unlock the bl ..will they notice ?
Click to expand...
Click to collapse
tohno, who happens to live in Malaysia as well, also hard bricked his W8 and had it repaired (motherboard got replaced).
Various other posts also suggest that SE won't recognize the cause - they will either swap out the motherboard or send you a new phone altogether.
@B.jay I don't thing so..
because my 2nd bricked I got E15i stock rom running on my W8
and on the rom I has super User and rooted..
when repaired done..I got the same firmware and with the superuser..
I thing maybe they just push bootloader ro something like that..
(just my 2cent IMO)
@caer_ayu
for me I got 4 times hard bricked
and they repaired my phone without lot of questions
I mean just show them my phone died and:-
(for1st bricked)i said IDK when I leave it for charging and when I cameback it died..
(2nd bricked)(just less than 1hour i got my phone) I ask my friend to sent it
(3rd bricked) I sent to vendor (not like b4 sent dirrect to warranty provider)
(4th bricked) Just like 2nd brick (with same person)
Hahaha...and now I confirm my phone can't go far enought...
and that why i just catch a X8 which can go far enought..11w23 and cypress digitizer...and very happy when i have to waiting for my W8 comeback...
sorry for long explaination..
nelikp ..where did you live ? ..my friend buy this phone at the shopping mall, at there, they know about rooting and unlck bootloaders to android phones. i was just affraid they might notice. will they send it to se or they do it themself ..
I live in KL..
for me I brought at shopping mall
and this is "AP" set (I mean warranty provided by 'COMSAT')
and the original set (warranty provided by 'SE')
'AP' set cheper than 'ORI' set
and if "COMSAT" can't fix the phone they will send to "SE" to handle
in my case "COMSAT" only 10 miniutes drive from my home
so I'm lucky stay here..
In your case..ask them about your "phone set (ORI or AP)
and ask them which company provide warranty for your phone
and go direct to the warranty (incase wanrannty provider isn't SE)
i think it was an ORI set ..because it has a Midland warranty seal ..i bought my x8 originally from the se center few months ago and it has Midland warranty seal also ..so it's definitely ORI set ..i hope they didn't charge for repair fees ..
nelikp said:
@B.jay I don't thing so..
because my 2nd bricked I got E15i stock rom running on my W8
and on the rom I has super User and rooted..
when repaired done..I got the same firmware and with the superuser..
I thing maybe they just push bootloader ro something like that..
(just my 2cent IMO)
Click to expand...
Click to collapse
I don't see why it should be impossible to "revive" a hard bricked phone when the repair shop, or SE themselves, have the required hardware and knowledge about how to do it ... that would explain why the phone you got back still had the ROM you had flashed prior to the hard brick.
I never ruled this possibility out, I only questioned the service centers having the means to get it done.
caer_ayu said:
i think it was an ORI set ..because it has a Midland warranty seal ..i bought my x8 originally from the se center few months ago and it has Midland warranty seal also ..so it's definitely ORI set ..i hope they didn't charge for repair fees ..
Click to expand...
Click to collapse
good luck honey..
B.Jay said:
I don't see why it should be impossible to "revive" a hard bricked phone when the repair shop, or SE themselves, have the required hardware and knowledge about how to do it ... that would explain why the phone you got back still had the ROM you had flashed prior to the hard brick.
I never ruled this possibility out, I only questioned the service centers having the means to get it done.
Click to expand...
Click to collapse
wow ..now i'm more nervous and affraid to send it back to the vendor ..i'm affraid of they charging repair fees ..cause i don't have any money ..i'm just a student at some college ..
this my advise...
just play dummy to them..
just said u really don't know what really happened
and play seriously!
IF U WON"T REPAIR MY PHONE I'LL REPORT TO KHDNDHEP
(KementerianDalamNegeriDanHalEhwalPengguna)
i wish your luck..
---------- Post added at 01:08 PM ---------- Previous post was at 01:05 PM ----------
B.Jay said:
I don't see why it should be impossible to "revive" a hard bricked phone when the repair shop, or SE themselves, have the required hardware and knowledge about how to do it ... that would explain why the phone you got back still had the ROM you had flashed prior to the hard brick.
I never ruled this possibility out, I only questioned the service centers having the means to get it done.
Click to expand...
Click to collapse
Yeah and I tot maybe they got a rifbox or Jtag cable..
and maybe they found the tutorial about how to do it on youtube..
nelikp said:
this my advise...
just play dummy to them..
just said u really don't know what really happened
and play seriously!
IF U WON"T REPAIR MY PHONE I'LL REPORT TO KHDNDHEP
(KementerianDalamNegeriDanHalEhwalPengguna)
i wish your luck..
Click to expand...
Click to collapse
HAHA ..my cousin works at LHDN ...i was just affraid after it has successfuly revive the device ..they would find the superuser app just like ur case ..