Related
Hello again
Sometimes we can brick our devices by a bad unlock, flashing process, or simply bad luck.
The phone doesn't turn on and there is a Red Led Of Death when pressing power button. Even with a GREEN led when we plug the phone with back key pressed the computer detect the phone as "unknown device" so there is no chance to get fixed by Flashtool or SEUS/PC Companion.
Well this problem normally means that the bootloader is broken or damaged. So, in order to fix it we need to write a new SEMCboot and after this we were able to flash a full and fresh firmware with flashtool and unbrick our Xperia.
This process like unlocking process requires SETool dongle/box and a paperclip to make a testpoint to put the phone in flash mode and be able to write the SEMCBoot.
I can help to anyone with a bricked Xperia Arc/Play/Neo/Pro just make send me a PM.
Like unlocking process you will need this 3 programs:
SETool software for unlocking
USB Over network client for remote dongle
Teamviewer client for remote support and guide
anyway if you want me to buy a Dr. Pepper just
Sometimes even after fix the bootloader the phone doesn't want to boot. In most cases this is by a damaged TRIM AREA (TA).
The trim area is a part of softwere stored in eeprom so it can be read and write with the proper software like SETool.
Read and Write trim area is very easy but you should know that some sectors of the TA are unique for you phone, lets call it Security Units.
The process for repair trim area is indeed very easy.
For sure we need Testpoint like in unlocking or bootloader repair process.
1. Backup Security Units with this script:
Code:
taread:00020851
taread:000207D3
taread:000207Da
2. Write a Working TA backup from another phone (same model)
3. Restore Security Units.
Thats all, now your phone should boot well but is 90% possible that you dont get Signal so for fix that we need to unlocking.
If this last thing is needed you can refer to this thread:
http://forum.xda-developers.com/showthread.php?t=1232033
huh u
huh u again . plz mention it is not a free tool so everybody can understand what is going on......????!!! you said it is free ?? free as 20 dollars or what i sent u a pm and you said pay . how could it be lol
taliani2 said:
huh u again . plz mention it is not a free tool so everybody can understand what is going on
Click to expand...
Click to collapse
need fix bug 0%batery .....
anikill3010 said:
need fix bug 0%batery .....
Click to expand...
Click to collapse
There is no fix as of yet for this problem. unfortunately, the devs are still trying to find a solution.
Trim area repair process is now tested and working for NEO PLAY and ARC
Alejandrissimo said:
Trim area repair process is now tested and working for NEO PLAY and ARC
Click to expand...
Click to collapse
Hi.
Is repairing the "Trim area" a solution for the 0 % Problem?
greets,
Marco
waiting....
gork1975 said:
Hi.
Is repairing the "Trim area" a solution for the 0 % Problem?
greets,
Marco
Click to expand...
Click to collapse
Nup is not
Then... how can it be fixed?
Nobody knows yet.
Thanks Alejandrissimo!!
Alejandrissimo is the best!!
Two weeks ago, I tried to flash cyanogenmod7, but I'm a n00b, so ofcourse it went wrong. My device(Arc) wouldn't boot anymore, I tried some things and suddenly it even wouldn't connect with fastboot..
So I saw this topic and some other ones from Alejandrissimo, Many comments praising him for his patience and help, that's why I contacted him, and that evening he helped me getting my phone working! He really Knowles where he is talking about!
Only problem I had left was NO SIGNAL, I asked Alejandrissimo if he could help me with that and yes he said he could. For almost a whole week, oh well. Much time difference, so it was hard to catch eachother we tried flashing it again and again in different ways. Yesterday he thought he had the answer, we tried it, and it worked!! I'm so happy he helped me getting my phone back! So so many thanks again Alejandrissimo!!
In order to unlock my trim area for my SIM I had to pay 24USD, cause Alejandrissimo had to buy credits at Sony Ericsson, but it was totally worth it!
Sent from my WORKING LT15i using xda premium
happened to me this morning but with a lot of luck i managed to get the phone in the flashboot mode (with a lot of tries connecting to PC) and install the stock FW (as i read FW is light on the boot loader)and tried to boot (with a lot of tries) i got it boot once but stops after Xperia screen i tried and tried until it booted normally i want to get back to the custom ROM but afraid that problem accrued again.
NOTE:last night tried to install True licensed market to get paid apps for free the phone heated and heated i uninstalled it and connected the phone to the laptop to charge overnight.
check your gtalk @Alejandrissimo. i've just send you invitation
i need your help for giving my mini pro back,now its on the dead of red led :crying:
Hi people. Because of work and children I have no much time to visit every thread on xda or check all PM, but you can always can contact me to gmail or hangouts.
Hi all...
I saw this thread already on other forums, but there was not enough detail to explain the trouble, so this topic.
I am affraid there is a trouble on some devices when you update to 2.3.4 (GENERIC GLOBAL) then downgrade to 2.3.2 (GENERIC GLOBAL) with the reason of ROOT them, battery looks dead, but is not.
I saw on the forum in two different devices already, and yesterday it happened to me as well.
So I tell you what I've done, and I really hope there will be a solution.
- my phone (MT15i) shown me a message, that there is a new software available. I wanted to try how is that, so I made a system backup, relocked the bootloader and then I updated via SEUS. Everything was fine, with it, except that little problem, that I wanted my baby to be rooted.
- downgraded to 2.3.2 (GENERIC GLOBAL) via SE Flashtool 2.9.1, to complete the GingerBreak treathment (I've done this due to the locked bootloader)
- GingerBreak has been successfuly completed, phone restarted, battery were on 0%, I knew this can be normal, so I switched off, removed the battery for 1 min and restarted.
- And the nightmare began: THE BATTERY STAYS ON 0% and the phone goes off. If I plug the device to the mains, stays on, looks like is charging, but it does not.
I've tryied other battery same issue. I tried my batteries in other NEO, the were perfectly fine.
Funy is, I unlocked the bootloader again, and I can do any operation with my phone like such a ClockWork Recovery or flashing it, but I can not start the ANDROID O/S a without mains.
Please guys help me, and those who have the same experience with Arc/Neo/X10.
Many many thanks.
Remove battery, and put it back after 10 minutes.
I have tried even for two hours. Nothing changed, same issue, but thank you anyway..
Also "battery calibration etc battery stats wipe?
Yes my friend. All of these things I tried. Even reflashed sytem and boot images with fastboot (I guess this has nothing to do with bootloader, but I gave a try)... No changes..
broken bootloader, search this forum...
Enough information is on these forums about rooting without needing to relock the bootloader, like RootXperia method.
That very day there was not solution yet for the latest S/W update about rooting it. But I already tried many solution I can find here, but there is no luck.
Your problem, but your spreading false information. Rooting method has been available before 2.3.3 and is same for all FWs
No matter which FW you have anyone can root if they have unlocked bootloader, just get RootXperia.zip and install via recoveryNeo.img
Search
Yeah, the thing is, I wanted to relock my bootloader, and doing the OTA update. From 2.3.2 to 2.3.4. Please read what I wrote again. And that time I did not found anything about rooting the 2.3.4.
Cheers
Raoa said:
No matter which FW you have anyone can root if they have unlocked bootloader, just get RootXperia.zip and install via recoveryNeo.img
Search
Click to expand...
Click to collapse
I's it true?
Sent from my MT15i using Tapatalk
battery 0%
taaviu said:
I's it true?
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
Yeah i've rooted all my FWs with RootXperia.zip
OTA is if you have locked bootloader, the whole method of going back to 2.3.2 is to not unlock bootloader and get root. To go through that with already unlocked bootloader is like going around when you could go straight.
The reports of, oh wait... this is not the first time OTA bricks phones. Wasn't it with 2.3.3 Arc update as well. So why do people fall to same trap?
Really there's enough relevant information on Arc forum, read up before doing something you don't need to do. It's a phone so thrashing around with flashing in any random way will end with bricked phones. It's your fault for not reading up and thinking well. SE might do something stupid with all these people bricking their phones in ways and for a reason they should not.... for customer protection. That would suck for us all.
Raoa said:
Yeah i've rooted all my FWs with RootXperia.zip
OTA is if you have locked bootloader, the whole method of going back to 2.3.2 is to not unlock bootloader and get root. To go through that with already unlocked bootloader is like going around when you could go straight.
The reports of, oh wait... this is not the first time OTA bricks phones. Wasn't it with 2.3.3 Arc update as well. So why do people fall to same trap?
Really there's enough relevant information on Arc forum, read up before doing something you don't need to do. It's a phone so thrashing around with flashing in any random way will end with bricked phones. It's your fault for not reading up and thinking well. SE might do something stupid with all these people bricking their phones in ways and for a reason they should not.... for customer protection. That would suck for us all.
Click to expand...
Click to collapse
What can we do?
I have a unlock bootlander.
Scroll down this forum and you'll see http://forum.xda-developers.com/showthread.php?t=1254409 Get a new battery or connect USB wires to - and + battery connectors and try it or send it to repairs.
Unless any dev finds yet another method to unbrick this new batch of phones then nothing else can be done.
Raoa said:
broken bootloader, search this forum...
Enough information is on these forums about rooting without needing to relock the bootloader, like RootXperia method.
Click to expand...
Click to collapse
I can confirm is not bootloader problem
Maybe is something with trim area.
This can be fixed but if you have warranty is better to send it to SE
Anyway if someone want to try this method to repair the trim area please contact me by PM.
Also anyone with working locked or unlocked NEO I need some trim area backups to acn repair others phones.
Please if you want to help send me a PM, the backup process is as easy as connect in flashtool by pressing back key
Raoa said:
Scroll down this forum and you'll see http://forum.xda-developers.com/showthread.php?t=1254409 Get a new battery or connect USB wires to - and + battery connectors and try it or send it to repairs.
Unless any dev finds yet another method to unbrick this new batch of phones then nothing else can be done.
Click to expand...
Click to collapse
Rember this was my same problem Raoa,, you told me to reflash with a difernt ftf file,,, problem was fixed there and then,,,
Sent from my MZ604 using xda premium
I am not so certain it is the exact same situation, Kormatoes. IF it's not a bootloader problem then I don't know what it is.
IF this would be fixed as easily as flashing a full working FW... well worth a try, nonetheless.
It is not a randomly flashing around and I DO WANTED my bootloader to be relocked and not open it again.. I used to flash my phone without any problem. I never had any problem repair anything. Since SonyEricsson and then Xperia exists, I know what to do with them if they are sick. I had enough experience, and I know you can find solutions on the forum, this is why you can see that from my posting history, that since I am member of XDA, never had stupid questions. I knew what to do when phone was bricked because of unlocked bootloader+over the air update. It is a simple accident that can happen to anyone. And here I asked for solution not for meaningless words, where some people try to show how brilliant and perfect they are. This is a development website, we are here to help for eachother or on those who needs help. So please stop to sue anyone, and help or please just do not reply for threads that you think is stupid, moderators/operators will deal with those. Just keep the rules of the website.
BTW, this MUST be a software problem, as I tested the battery, works perfectly in other devices, the phone is all okay about the 'elctrovise'
As I saw this on ARC's forum as well, this happened there in same way: Update to 2.3.4 then downgrade to any of the previous S/W versions, caused this. So I think this situation will incrase soon, this why I thing we need to find a solution as well. I normally working with Linux/ubuntu laptops. I had simular issue, but then was just the battery. Now... I dont know.
laceex said:
It is not a randomly flashing around and I DO WANTED my bootloader to be relocked and not open it again.. I used to flash my phone without any problem. I never had any problem repair anything. Since SonyEricsson and then Xperia exists, I know what to do with them if they are sick. I had enough experience, and I know you can find solutions on the forum, this is why you can see that from my posting history, that since I am member of XDA, never had stupid questions. I knew what to do when phone was bricked because of unlocked bootloader+over the air update. It is a simple accident that can happen to anyone. And here I asked for solution not for meaningless words, where some people try to show how brilliant and perfect they are. This is a development website, we are here to help for eachother or on those who needs help. So please stop to sue anyone, and help or please just do not reply for threads that you think is stupid, moderators/operators will deal with those. Just keep the rules of the website.
BTW, this MUST be a software problem, as I tested the battery, works perfectly in other devices, the phone is all okay about the 'elctrovise'
As I saw this on ARC's forum as well, this happened there in same way: Update to 2.3.4 then downgrade to any of the previous S/W versions, caused this. So I think this situation will incrase soon, this why I thing we need to find a solution as well. I normally working with Linux/ubuntu laptops. I had simular issue, but then was just the battery. Now... I dont know.
Click to expand...
Click to collapse
I have the ****ed same problem!!
batery 0%....
i tried flash to other versions and no get solution..
wipe batery stats none
.......
ANY IDEA?
anikill3010 said:
I have the ****ed same problem!!
batery 0%....
i tried flash to other versions and no get solution..
wipe batery stats none
.......
ANY IDEA?
Click to expand...
Click to collapse
I am affraid we still have to wait until more people will have the same problem. Right now there is no solution, only to leave on charger. Why not. A little retro. Just like a landline phone
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
sfrat said:
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
Click to expand...
Click to collapse
if you can get into download mode im guessing there is some hope for you.
go here: http://droidangel.blogspot.com/2011/05/samsung-galaxy-ace-s5830-original-stock.html
look for: S5830XXKP9
and make sure you have odin 4.38 and flash with that.
try to install cwm and install a customrom
Sent from my GT-S5830 using xda premium
sfrat said:
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
Click to expand...
Click to collapse
with the cellphone off, put out ur baterry for a minute, then maintain ur finger into the volume down button and the power button tell a friend or if u can alone insert the batery while quickly pressing volume down and power button to get into download mode, and flash.
Hehehe,bootloop is horrible,you just have to get in download mode & flash with 2.3.4 firmware with Odin,just that steps and you save your SGA.
I got bootloop many times and Odin saved me.
Sent from my SGA
robinandroid said:
try to install cwm and install a customrom
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
he cant go back in recovery mod............
If you can go to recovery mode than you can just wipe the data and cache. This saved me many times. Otherwise on what ever OS you may be , just create new user name after removing samsung android drivers. Login from new user name and than re install drivers again and now flash your phone from firmware which was installed on your phone before you bricked it. This helped me a few times.
dr_vishal said:
If you can go to recovery mode than you can just wipe the data and cache. This saved me many times. Otherwise on what ever OS you may be , just create new user name after removing samsung android drivers. Login from new user name and than re install drivers again and now flash your phone from firmware which was installed on your phone before you bricked it. This helped me a few times.
Click to expand...
Click to collapse
hey guys thanks for the answers, but unfortunately i am not able to reach the recovery mode, my phone just reach the download mode.....i will try with the xxkp9, even if i have already tried it...I guess i have tried at least 15 firmwares without any success
Helping to make your Christmas Merry
It seems that you've already received a lot of help for unbricking your device. So I'll try to help out in unlocking your phone after you finished unbricking it.
This is the method I personally used on my locked Ace:
http://forum.xda-developers.com/showthread.php?t=1335548
It's perfectly safe. 100%.
King Kaze said:
if you can get into download mode im guessing there is some hope for you.
look for: S5830XXKP9
and make sure you have odin 4.38 and flash with that.
Click to expand...
Click to collapse
I have tried the XXKP9 again, it is not working, as usual Odin ends to load the firmware and then it goes back in the endless loop mode....there is no chance to get it back?
franzks said:
It seems that you've already received a lot of help for unbricking your device. So I'll try to help out in unlocking your phone after you finished unbricking it.
This is the method I personally used on my locked Ace:
http://forum.xda-developers.com/showthread.php?t=1335548
It's perfectly safe. 100%.
Click to expand...
Click to collapse
thank you very much I will follow your advice...IF I will be able to get my phone back which seems impossible =(
@dr_vishal
Thank you first of all, I have tried to uninstall and reinstall the android device driver, but it doesn't seems to be the problem, Odin ends with a "PASS" at the end, I guess there still is comunication in the between the two devices...
Hopefully it will be a Merry Christmas =)
It's not impossible. I'm relatively new here but I have noticed quite a few "bricked" threads already. Most of them (if not all) have been able to fix their device. I haven't seen a single person permanently brick their device, so I would guess that your chances of fixing it are really high. Just be patient and keep describing your situation and more experienced help will certainly arrive. I'd really like to help out but I have no idea how to fix it as I have not experienced bricking my phone yet.
Anyway, if the method for unlocking I suggested works for you kindly press the Thanks Button. Merry Christmas!
franzks said:
It's not impossible. I'm relatively new here but I have noticed quite a few "bricked" threads already. Most of them (if not all) have been able to fix their device. I haven't seen a single person permanently brick their device, so I would guess that your chances of fixing it are really high. Just be patient and keep describing your situation and more experienced help will certainly arrive. I'd really like to help out but I have no idea how to fix it as I have not experienced bricking my phone yet.
Anyway, if the method for unlocking I suggested works for you kindly press the Thanks Button. Merry Christmas!
Click to expand...
Click to collapse
Thank you franzks!
I promise I will try your method and I am positive it will works, but I need to get my phone back...so I will add few new information I have found out talking to a friend of mine which has my same device and the same carrier as well.
The version built-in is:
GINGERBREAD.BVKQ9
S5830BVKQB
[email protected]#1
Any suggestion about the firmware I am suppose to flash in?
I am actually passing through all the version contained in the address droidangel you gave me...at the moment no one is working...I will keep trying...
sfrat said:
Thank you franzks!
I promise I will try your method and I am positive it will works, but I need to get my phone back...so I will add few new information I have found out talking to a friend of mine which has my same device and the same carrier as well.
The version built-in is:
GINGERBREAD.BVKQ9
S5830BVKQB
[email protected]#1
Any suggestion about the firmware I am suppose to flash in?
I am actually passing through all the version contained in the address droidangel you gave me...at the moment no one is working...I will keep trying...
Click to expand...
Click to collapse
Guys,
I am out of ideas, I have tried each single firmware I have seen around internet, no one is working, any tip or advice or suggestion?
I messed up with the efs, and I guess that's all, the phone is gone....now it needs a JTAG or whatever is its name....
maybe to get the warranty still valid I should broke totally the phone over charging it....??
sfrat said:
Guys,
I am out of ideas, I have tried each single firmware I have seen around internet, no one is working, any tip or advice or suggestion?
I messed up with the efs, and I guess that's all, the phone is gone....now it needs a JTAG or whatever is its name....
maybe to get the warranty still valid I should broke totally the phone over charging it....??
Click to expand...
Click to collapse
Did you try that?
http://forum.xda-developers.com/showthread.php?t=1153310
just a thought
a lot of people have talked about reflashing it and all but have you managed to get into the recovery mode at all once you have reinstalled the rom with odin? if you can get to that you just need to hit factory reset, wipe cache and wipe dalvik and normaly after that it will work fine... so far ive been stuck in soft brink 3 times and each time doing the wipes from the recovery mode has worked...
Pinting said:
Did you try that?
http://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
I've tried to use the oneclick, but it seems it doesn't recognize the phone, since, i guess, it's made for a galaxy s.
The others are not my case, since I am able to get download mode, and all these are made to can get it back.
Anyway I found out a post in which the people were talking about the s5500, which apparentely is similiar to my device, and the owners of that model experienced a similar problem doing the same process....anyway in that post the people needed to use a Jtag, which is the only way to get it back....so I though it could be the same solution for my problem...but I don't know anybody with Jtag, so the only way is contacting the service center.
thanks anyway, when I will be back at home after Christmas I will try to find the ticket and I will probably try to get it back in warranty, since is preatty new...
@torchwolfery
I am not able to reach recovery mode, there is no way to get it back, even flashing the phone with different firmwares, all I got is download mode, and apparently that is completely pointless...since the only change in the phone behavior is that if i install a certain firmwares it doesn't even have the back-light working when it is stuck in bootloop.
Warranty is your only hope (as it was mine once and it worked).
I didn't think it was possible to brick these phones. There I have tried so much to try and brick it but I have not been able to as it still always goes into 'download' mode. The only advice I can give you is double check that you are using the correct version of Odin which is v4.38 and that you use cooper v1.0 as your OPS. If dont mind me asking, but exactly what did you do or do you remember the steps you took to brick it? What buttons are you using for 'recovery' mode.
Also please clarify if Odin is going in a loop or does the phone come on and then keeps rebooting? If it is the phone that keeps rebooting, then wiping cache and data partition should do the trick. This can be done by going into recovery mode (which I am aware you cannot get into) or if you can manage to get into the dialler quick enough before the reboot, by dialling *7267*3855# and that should format the relevant partitions (data and cahce) and bring it back to factory settings. Without further info, I cannot really tell exactly what the situation is.
The fact that you are getting 'download' mode, I dont think that it is bricked because it will still allow you to write the relevant directory/files to the relevant blocks. Either way, would be interested to know.
So I had previously rooted my SGSII, and decided to try installing CM7 on it. I used CWM Recovery and ran it off the SD card, and everything appeared to work fine. I think I had a bad/not fully functioning CWM or something, as it didn't list an option to backup anything (I'm guessing because I flashed the stock kernel after rooting?) Anyway, it will no longer boot. I can access download mode, but Odin fails everytime I try to flash anything back on there. When I try to boot my phone, I just get a "Firmware upgrade encountered an issue" error.
EDIT: I just tried again as I was writing this, after rebooting, reinstalling my drivers and rebooting my computer. I was able to get the Firmware to flash properly in Odin. Now I have my phone booting and getting stuck on the "Samsung Galaxy SII GT-I9100 splash screen... Doesn't seem to go any further than that though, unfortunately.
Any ideas what I can do? Is it possible that I need re-flash a bootloader or something ??
Any help would be supremely appreciated!
So I was just trying to re-install the Kernel, using the CF unsecured kernel, and it failed, but when I try to go into recovery mode, it looks as though it managed to install CWM Recovery. I have no idea what to do from here, and am sort of afraid to do anything for fear or bricking the phone completely...
I'm hoping someone out there knows how to fix this, I feel like such a tool
As long as you can get into download-mode, your phone isn't bricked.
If you switch from or to a TouchWiz-based ROM, you have to do a full-wipe in the recovery.
Sent from my GT-I9100 using XDA App
Go back to stock first via download mode via odin
Nah you're good. Similar thing happened to me at my first flashing attempt. Get your stock firmware from Intratech's thread, put the phone into download mode & flash the firmware via Odin.
Then maybe have another go at rooting the phone with the matching CFRoot kernel.
Porkchops said:
So I was just trying to re-install the Kernel, using the CF unsecured kernel, and it failed, but when I try to go into recovery mode, it looks as though it managed to install CWM Recovery. I have no idea what to do from here, and am sort of afraid to do anything for fear or bricking the phone completely...
I'm hoping someone out there knows how to fix this, I feel like such a tool
Click to expand...
Click to collapse
yes, if you can still go in download mode it's no so difficult..this "small brick" it's on of "Android things to do" once in your SGS2 life
Hi guys. I'm in a worst situation. As my phone after a failed ODIN downgrade from Android 2.3.6 to one stock kernel is completelly dead - it doesn't boot anymore - not even managed to put it back into download mode or revert to fact defaults (no keys, no lights not even battery charging displayed when pluged in) - tryed the USB jig also. Nothing worked.
The question is: Will Samsung manage to repair and how much will it cost - an average ammount offcourse. Because I guess it's out of the question to be considered a warranty issue. I guess it will be visible somebody have done smth to the ROM by a software approach....
This is the short story because I would bore you to discuss all the things I have been through - it was only my faoult out of stupidity
HELP!
I don't see why Samsung wouldn't fix it ? As to how much they'll charge you, I think you'll find that will vary from country to country (labour costs being variable, etc). No, I don't think you'll be able to have it repaired under warranty.
You might want to look at having it JTAG repaired by someone other than Samsung. This will possibly be cheaper than having Samsung repair it. Do a search on here/Google.
alexdonc said:
The question is: Will Samsung manage to repair and how much will it cost - an average ammount offcourse. Because I guess it's out of the question to be considered a warranty issue. I guess it will be visible somebody have done smth to the ROM by a software approach....
HELP!
Click to expand...
Click to collapse
Thank you very much. I have searched alot to actually understand - unfortunatelly for me it will cost... I saw on youtube a JTAG in action right now (cannot post the link yet). I understand now it is the only way. I'll keep you posted guys. Tomorrow I'll go to service.
I'm sorry it's going to cost Alex. A difficult thing to happen, I know
Here's a link for a JTAG repairer in the US who is also a member here, tho I see you've already found one. I'm sure doing it this way will be cheaper/probably faster than having Samsung do the repair as well.
alexdonc said:
Thank you very much. I have searched alot to actually understand - unfortunatelly for me it will cost... I saw on youtube a JTAG in action right now (cannot post the link yet). I understand now it is the only way. I'll keep you posted guys. Tomorrow I'll go to service.
Click to expand...
Click to collapse
Thax. Funny thing is that this is exactly the thing I found - the same mobiletechvideos in US Now I allready have an ideea of how much should cost that. Hopefully I'll find a local GSM repair shop with the posibilitty to unbrick it cheep - or at least not much than 50USD - in local currency ofcource.
I'm still thinking if it is possible to use an ATMEL copy process - like in the old times for EEPROMS - I have done that in the past. In theory it might work but I will never do it - alredy scared about what happened to my beloved droid.
Thx again Mistah and have a gr8 day and a wonderfull new 2012!
Yeah I've seen a report or two on here from people who have used his service & have been happy. Must admit I found his page when thought I'd bricked my phone after my first flash attempt messed up. Yeah you might be able to get it done cheaper somewhere local, and that will mean less time without the phone for you without the phone in mail from you to the US & back again.
Let us know how you get on, your experience will be a good guide for people in future who have the same problems as you.
No probs man, happy to give you the little help I did. You too Alex Hope you have a great year & you get your phone back & working soon
alexdonc said:
Thax. Funny thing is that this is exactly the thing I found - the same mobiletechvideos in US Now I allready have an ideea of how much should cost that. Hopefully I'll find a local GSM repair shop with the posibilitty to unbrick it cheep - or at least not much than 50USD - in local currency ofcource.
I'm still thinking if it is possible to use an ATMEL copy process - like in the old times for EEPROMS - I have done that in the past. In theory it might work but I will never do it - alredy scared about what happened to my beloved droid.
Thx again Mistah and have a gr8 day and a wonderfull new 2012!
Click to expand...
Click to collapse
Hello again. Solved right now. The service didn't charged me at all - I was kind of lucky after all. Unfortunately there are still some issues I have from the start. I'll keep on digging - software related.
So this damned problem happened to me too!.. My phone hasn't been rooted or anything.. just today my Sim lost signals so I decided to turn on the flight mode on and off to reset the networking but the flight mode wont turn off..
I remember when this happened to me before once too I had taken the battery out once or twice also had restarted the phone and it started to work again but now it didn't respond to that treatment at all..
Got online read about the problem to know that I also have the 'Unknown IMEI/IMEI SV/Baseband' problem.. I have no idea what so ever what to do to fix it.. my phone has warranty till 30th November.. I don't know if the partner will honor the warranty but anyhow as of yet I can't go to the service center cause its already closed.. will tomorrow.. anyhow been reading around..
Saw these two threads..
http://forum.xda-developers.com/showthread.php?t=1261948
http://forum.xda-developers.com/showthread.php?t=1362285
Both are explaining replacing the corrupt EFS files with back up ones.. but what scares me what if I don't have them? as explained in thread 2..
anyhow is there any way to fix the problem without rooting? I'm not sure if those methods are for none rooted devices..
I'm just a noob I have never even tried rooting or even updating! just because I was happy with what I had...
Backup data and factory reset if that does not fix its a service centre .
Or you mess with other methods that may brick your phone or void warranty in any case .
Tell service it has happened before .
jje
-sighs- Alright.. its service center for me.. the only problem is.. sending phones to service center here is like inviting more problems to whatever you are trying to get fixed >.>..
I still can't believe why my phone lost/corrupted such critical files when I never even tried messing with it..
D: I should messed with it! lol..
M.. well anyhow wish me luck.. the phone served me a good 6 months..
redfeeniks said:
-sighs- Alright.. its service center for me.. the only problem is.. sending phones to service center here is like inviting more problems to whatever you are trying to get fixed >.>..
I still can't believe why my phone lost/corrupted such critical files when I never even tried messing with it..
D: I should messed with it! lol..
M.. well anyhow wish me luck.. the phone served me a good 6 months..
Click to expand...
Click to collapse
do u ave a bckup of efs
My phone wasn't rooted.. nor did I back up anything I don't think I can even see if I have those files or not without root privileges..
I just wanna hear the worst case scenario..
-edit-
unless there is way to check please let me know..
Alright.. Sad news for me, The retailer I bought the phone from told me the service center is an other city(whoa) and he then further pointed to that service center's outlet here that would take my phone and process it through..
The guy kept saying this error only happens when you are updating but I was never updating to begin with.. never have updated my phone!
Now I'm worried if going to this outlet and handing my phone over to them for I don't know how long! without any replacement phone is a good idea or not.. Nor do I think I'm willing go to take a trip to the other city.. but tomorrow I would definitely visit the outlet..
anyhow I'm deciding to try out the methods or restoring my Phone's Efs files here because honestly I don't think anyone here has a clue, I've been hovering on these forums and lurking around for almost an year and I was gonna root my phone anyway after the warranty period was over..
now my question is, Can I root without any issues having the 'Unknown Baseband/IMEI'? I have done a factory reset which has cured the flight mode problem but my phone isn't responding to Kies on PC cause it seems to be stuck on 'connecting'.. but I'm assuming that wont be a problem when rooting.. but again this is why I'm asking the advanced and experienced users..
I've read most of this guide:
http://forum.xda-developers.com/showthread.php?t=1103399
and have understood most of it however I'd definitely need some mature advices over this matter..
I'm just rooting to try the App GSII_Repair by Helroz.. anyhow still mature Advice needed..
Please Help me out guys
bump..
redfeeniks said:
Alright.. Sad news for me, The retailer I bought the phone from told me the service center is an other city(whoa) and he then further pointed to that service center's outlet here that would take my phone and process it through..
The guy kept saying this error only happens when you are updating but I was never updating to begin with.. never have updated my phone!
Tell them it was a Kies update .
anyhow I'm deciding to try out the methods or restoring my Phone's Efs files here because honestly I don't think anyone here has a clue
THATS NOT TRUE THEIR ARE A NUMBER OF METHODS THAT MAY WORK IN SOME CASES .
But you cannot restore something you never backed up in the first place .
now my question is, Can I root without any issues having the 'Unknown Baseband/IMEI'? I have done a factory reset which has cured the flight mode problem but my phone isn't responding to Kies on PC cause it seems to be stuck on 'connecting'.. but I'm assuming that wont be a problem when rooting.. but again this is why I'm asking the advanced and experienced users..
ROOT is via
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
Click to expand...
Click to collapse
JJEgan said:
redfeeniks said:
Alright.. Sad news for me, The retailer I bought the phone from told me the service center is an other city(whoa) and he then further pointed to that service center's outlet here that would take my phone and process it through..
The guy kept saying this error only happens when you are updating but I was never updating to begin with.. never have updated my phone!
Tell them it was a Kies update .
anyhow I'm deciding to try out the methods or restoring my Phone's Efs files here because honestly I don't think anyone here has a clue
THATS NOT TRUE THEIR ARE A NUMBER OF METHODS THAT MAY WORK IN SOME CASES .
But you cannot restore something you never backed up in the first place .
now my question is, Can I root without any issues having the 'Unknown Baseband/IMEI'? I have done a factory reset which has cured the flight mode problem but my phone isn't responding to Kies on PC cause it seems to be stuck on 'connecting'.. but I'm assuming that wont be a problem when rooting.. but again this is why I'm asking the advanced and experienced users..
ROOT is via
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
Click to expand...
Click to collapse
well so there is no point in doing all this because I haven't backed up my efs files(which I never could from the first place cause I never tweaked around)
many people out there have explained having not saved any efs files.. yet they have been able to get their back using different methods.. I mean I'm assuming it must have happened when I took the battery out? assuming a sudden loss of power supply corrupted the files?
Click to expand...
Click to collapse
anyone?