Hi,
I've already read a number of threads both on this forum and others, but need someone to point me in the right direction.
I recently installed Chewitts Dark theme and all was well, at this stage I became over confident and tried to install final simple theme also from this forum and this is where my problems started.
Once the simple theme had completed my phone started to a boot loop and i was gutted. I then tried PC suite and nothing, then after some reading I tried SEUS and it does not recognise my phone.
I can now get PC suite to recognise the phone, however it asks me to mount the SD card, which I can't do as the phone screen show a battery symbol with a flash through it.
I've found the following threads,
http://forum.xda-developers.com/showthread.php?t=683793 (seems complicated)
http://forum.xda-developers.com/showthread.php?t=776278 (seems simple)
but need help, I need something like an idiots guide please.....
what can I try next?
sannan06 said:
Hi,
I've already read a number of threads both on this forum and others, but need someone to point me in the right direction.
I recently installed Chewitts Dark theme and all was well, at this stage I became over confident and tried to install final simple theme also from this forum and this is where my problems started.
Once the simple theme had completed my phone started to a boot loop and i was gutted. I then tried PC suite and nothing, then after some reading I tried SEUS and it does not recognise my phone.
I can now get PC suite to recognise the phone, however it asks me to mount the SD card, which I can't do as the phone screen show a battery symbol with a flash through it.
I've found the following threads,
http://forum.xda-developers.com/showthread.php?t=683793 (seems complicated)
http://forum.xda-developers.com/showthread.php?t=776278 (seems simple)
but need help, I need something like an idiots guide please.....
what can I try next?
Click to expand...
Click to collapse
Fingers crossed I've sorted the problem..
Took the Sim and SD card out and tried SEUS again, this time it worked and only gave me the option to update software. I've just finished and all seems well.
Now i need to root and try and install another theme....
Thanks to all who have contributed to a number of threads on here....only by reading most of the comments was I able to solve my problem....
sannan06 said:
Fingers crossed I've sorted the problem..
Took the Sim and SD card out and tried SEUS again, this time it worked and only gave me the option to update software. I've just finished and all seems well.
Now i need to root and try and install another theme....
Thanks to all who have contributed to a number of threads on here....only by reading most of the comments was I able to solve my problem....
Click to expand...
Click to collapse
If anyone bricks their phone this does work. I picked the wrong flash last night and it looped my phone and removed Xrecovery. Tried Seus with sdcard installed still looped. Removed sdcard and tried again. Works perfectly. Seus installed 2.1 generic.
Close call. Don't try to flash phone after working 14hr days. Lesson learned.
Related
So i have tried Jit enabler v2 and bricked my SE
it freezes at Sony Ericsson logo,
what i can do is boot via xrecovery and since there i dont know how to remove Jit enabler,
Any advice?
Depending on what version of firmware you have, you need to download : http://forum.xda-developers.com/showthread.php?t=902974
and install as update.zip "*10* 2.0.A.0.*** Disable JIT.zip". That should help. If not, clear dalvik cache and reboot.
thanks, but how to put it to SD card because since its bircked i cant properly connect the phone so PC would read its SD card?
newestuser said:
thanks, but how to put it to SD card because since its bircked i cant properly connect the phone so PC would read its SD card?
Click to expand...
Click to collapse
I suppose that You don't have any card reader :/
I don't really remember if ADB works in xRecovery mode, but You can try, to unpack the "disable jit" package, and push manually files to "/system/bin", and "system/lib". The build.prop should not be a problem tho. You can do that with http://forum.xda-developers.com/showthread.php?t=868423 but, as I said, I'm not sure about working ADB in xRecovery. I figure You don't have enough time to push files on "Sony Ericsson" logo, cuz it reboots ;/
Just try.
thanks for helping out!
unfortunetly i have a reader, and only remembered after i did via xrecovery full reset (wipe data). BUT it still didnt booted, froze uppon sony ericsson logo, so im now moving files you gave a link and praying xrecovery still works
You moved to fast with wipe
I don't really know what to say to You right now.
but seems there is xrecovery backup, so in case...i think maybe i can reinstall via update service, than restore backup i made before wiping data out and installing jit disabler. Well thats by my logic should work. But im not really expierienced with phones and dont have x10 for a long time...
Unfortunately that I think is the last thing it's left to do. Just repair the phone via SEUS. I don't want to be a ****, but it's a bitter lesson for You, that if You have xRecovery, and ADB enabled theres always a way to get passed "Sony Ericsson logo reboot". Wipe was just to fast thinking. Hope You don't get in a trouble like that ever.
Yea, i tried too long time ago JiT v2 and i also bricked my phone, i also installed by accident wrong firmware ver JiT v1 and ended up, again, with a brick.
I that case, only solution to it is to Reflash whole firmware again. Trust me, i tried all possible solutions and it didnt worked. Luckily i had my contacts backed up on my g account.
I also learned my lesion hard way, and, this is 100% true.. "If you have xRec be sure to always have a backup."
P.S. Dont worry, mini/pro dont die that easily.. Its just get hardly wounded, it will always recover, but sometimes with memory loss (since u didnt had a backup)
When i first time bricked my phone it was a day old, i freaked out, but manage to get a grip and searched forum a bit. Since i like experimenting with my software i manager to brick my phone 10+ times per day..
And.. guess what phone im using now? x10 mini
Well, yea often flashes are not a big problem, but i don't wish that to anybody, cuz as you said, and all know it's a pain in the ass to get back settings, and all the data.
"Bricking" is defiantly to strong word. Boot loops, or hanging on SE logo is far from bricking, we always have a chance to "repair" our devices by ourself, so no problem here. The real problem can be in the future, when boot loader get fully cracked, and for example we interrupt his flashing process - situation well known for other android phones users. Phone gets bricked, and theres **** we can do about it, cuz recovery is obviously not working.
I did learned something else back then (5 years ago) when flashing my phone with with a desktop PC and suddenly power failure.. bricked my phone which not even got any bootloader to start with. Since that moment I always use my laptop to flash my phone as it has battery to continue the flashing process in case power failure happen again.
farsight73 said:
Since that moment I always use my laptop to flash my phone as it has battery to continue the flashing process in case power failure happen again.
Click to expand...
Click to collapse
Amen to that.
was using zedomax's root method and got a bunch of errors "too many devices, more than 1 emulator" and now it won't finish booting. Gets just to the point where the unlock ring should come up and then nothing...
I can pull down the status bar and thats about it ...please help. I have the insurance, but will they be able to see that i started rooting it...
I would try to install the RUU to get it back.
It's probably not Bricked.
You can also check out the more full unlocking procedure http://forum.xda-developers.com/showthread.php?t=1690919
I believe one or both these procedures could be started while in the bootloader.
I'd try the RUU first though.
Look in the Sticky thread in Dev for the RUU (an EXE you run on the PC).
greek goddess said:
was using zedomax's root method and got a bunch of errors "too many devices, more than 1 emulator" and now it won't finish booting. Gets just to the point where the unlock ring should come up and then nothing...
I can pull down the status bar and thats about it ...please help. I have the insurance, but will they be able to see that i started rooting it...
Click to expand...
Click to collapse
This happened to me as well. Then i realized i have both my old Epic4g AND my new EVOLTE plugged into my computer. I unplugged my epic and voila. it worked just fine. If it still doesnt work, try restarting your PC and redo the process.
Thanks guys for your answers. problem is resolved, but I will what happened in case anyone else has this problem.
I couldn't get the drivers to install on my laptop so I went to the desktop and ran the root. The error messages I got were like this: after the second reboot (supposed to reboot 3 times) it would say "device offline" and it filled the whole screen with that line. Then it said "error too many emulators" and then it would say it was done and that is as far as it would go. It did not boot a third time. I could reboot it, but it would only get as far as the screen JUST before the unlok ring comes up, and that's it.
After posting this thread I read another thread where someone suggested holding the volume down and power to bring up stock recovery and doing a factory reset from there (rookie mistake, I have had the Epic Touch for a while and forgot about the Evo's stock recovery). That got me back. THANK GOD! But still no root.
I didn't want to give up trying to I went back to my laptop and still without necessarily "installing" the drivers, went ahead and tried running the root and VIOLA! It worked flawlessly!
So I don't understand what was going on with the desktop though with the "device offline" and "too many emulators" thing, so if anyone could shed some light on that, I would appreciate it.
glad to hear you got it fixed but if you would have had to filed a claim then you can always say you lost it or something like that.
Okay, So I am as NOOB as NOOB can be,
I got a used SGS2 (Bell/Virgin), I am on Telus so I figured, how hard can it be to unlock it instead of paying some dude to do it for me? (First mistake, and have been humbled every step of the way since!...)
Anyway I will try to keep this relatively short (it will be difficult)... ...I read a few things online and saw that I needed ODIN and a Rooting software, I originally used SuperOneClick, and to download the right insecure kernel to match my original one etc... ...problem is I obviously didn't read nearly enough when I started because I was almost done and then there was a hiccup when SuperOneClick said that I needed to enable SU in Kies. So I decided to go into Kies to try and do so but the instructions before I started Rooting said to put the phone in USB debugging mode. Apparently Kies doesn't see the phone if it is in that mode. Well by this time I can't get past the logo screen and this is where my downward spiral begins.
I then tried to unroot the phone to go back to stock but didn't really know what I was doing and then I read something about the cache needing to be wiped and then after that I read that maybe my OS was wiped. So at this point I did lots of reading (what I should have done in the first place) and most of anything useful I found was on XDA so that is why I am here. It seemed like yes, in fact my OS was wiped because of one of my not so S-M-R-T actions. So I fumbled through and found the right OS for my S2 and I had ODIN going strong and I had the OS loading, the green bar getting bigger in ODIN and the blue bar working it's way across the screen of my S2...I thought "finally!!, I rock!!"... ...then for some reason everything stopped! I had seen in a post that I had to uninstall Kies before doing anything, which I did...but I didn't see until after the fact that my anti-virus likely interfered (I didn't disable it for the process before I started).
At that point of course I was left with a phone that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So then I was afraid to try anything else because many say to steer clear of Kies and also I had read that I may need a USB jig to be able to get it back into download mode because all I was getting was the "firmware upgrade issue" screen. I did make a USB jig with a resistance of 300K Ohms and I *can* get the phone into download mode. (Though another concern is that when I plug the USB jig in and it brings the phone into download mode, the counter is not reset and I read that that was supposed to be reset by the jig.)
So last night I got brave and decided to try and run ODIN and to have another attempt at installation of OS. Now I can get ODIN to detect the phone, but I put the I9100MUGLD3_I9100MBMCLD3_I9100MXXLD3_HOME.tar.md5 file into the PDA section of ODIN and it starts and gets to the part where it says loading firmware or something and then bootload.bin and it stayed like that for like, an hour and then I gave up, fearing that I am just going to screw it up even more.
So now I decided that I am not even close to knowing what to do next but every time I found anything to move forward it was on this site so I figured I may as well join the site since I have been here so often. Now I am hoping for some kind of miracle...so, in advance, please please please and thank you thank you thank you all for your input. (Sorry for the length of this I just wanted to get all the info I could into this)
Its quite a long story and didnt bother reading it.
If you can still access your phone via odin at downloadmode. Flash a stock firmware for your device and it should fix if it is just a soft brick.
Sent from my GT-I9100 using Tapatalk
UnwiredDroid said:
Its quite a long story and didnt bother reading it.
If you can still access your phone via odin at downloadmode. Flash a stock firmware for your device and it should fix if it is just a soft brick.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Sorry for the length of the story, I thought there may be alot of useful info mixed in with the useless info... ...when you say use stock firmware do you mean the kernel or the actual OS? I tried loading ICS onto it (which I thought was stock but I may be wrong). Is it supposed to be gingerbread or something else? Also where would I find a good file for it.
Thank you again for any input, very much appreciated!
Hey ,
I also have a Virgin Samsung S2 i9100 and the first time I tried rooting it, it got stuck on the screen with the yellow triangle and wouldnt move at all. I believe it was bricked?
anyways, I m not sure I totally understand your situation, but I solved my problem using this thread
http://forum.xda-developers.com/showthread.php?p=21493413
look it under the i9100M section. hope this helps
schtiven said:
Hey ,
I also have a Virgin Samsung S2 i9100 and the first time I tried rooting it, it got stuck on the screen with the yellow triangle and wouldnt move at all. I believe it was bricked?
anyways, I m not sure I totally understand your situation, but I solved my problem using this thread
http://forum.xda-developers.com/showthread.php?p=21493413
look it under the i9100M section. hope this helps
Click to expand...
Click to collapse
Thank you all so much for your help, I could not get it to work after several tries, I even tried three or 4 different USB cables and ports on my PC and still no. I read on another thread that one person tried another PC and it worked so I tried my friend's laptop and it worked!...my SGS2 boots up and all that now! Very very happy thank you all.
Phone specs first
Samsung Galaxy S2 GT-i9100
Rooted
CWM
Hardcore speedmod
android 4.1.2 jb
PC is windows 8
I remember i had turned the usb debugging on in dev options
so last night i tried to install cyanogenmod on my device with the cyanogenmod installer for PC and Android.
I was having a bit of usb problems with noticing that my pc did detect the phone, but i couldn't see the phone in
"my computer" file. I thought it would soon fix by itself(i dont know why) and also noticing that detecting device in cm installer
took a lot of time. So when it finally detected the phone it started installing the CM. Although after coming to the
"installing operating system" point, it stopped and said "we couldn't talk to your phone" and having this blue CM guy standing in the screen
of my phone. I tried again several times with rebooting my pc and phone. To the phone appeared again this blue cm figure just standing there.
When i would go and try again on pc it said the "we couldn't talk to your phone" text again. So i gave up with the installer and thought that would be better to flash that CM with Odin. At this point i couldn't access my phone(except for download mode and recovery) of course because it had screwed up the system. I tried to search internet for some usb problem fixes and there were some solutions on changing something in your
device settings and dev options, i cant go there, so for now thats not an option. I started following a tutorial in youtube on how to install cm with odin and root your device. My first question here is that should i install everything and start from scratch (Gapps,CM and kernel) or just the CM ROM? And the problem here is that when i started following the tutorial and came up to the part of having to move the Rom,kernel and gapps to the phone's sd card, i realised that wouldn't work because i cant see the phone on my pc, for now that's the problem number 1. My pc says "unknown device" ( i think thats what it means, see im translating) when i try to plug my phone in. Got any solution for this so we could move on to step 2?
And btw this is in a bit of a hurry, as i really have to get this phone working today.I need it! :crying:
And yeah i did read the other threads about PC not recognizing the phone but those solutions there require the phone to be turned on and changing something there. So basically my phone is bricked and cant connect to pc with usb, i have tried another pc too with 2 usb cables but the phone wont show up under "my computer"
Get stock firmware from Samfirmware, try & flash with Odin. Problems with flash ? Find Hopper8's 'Odin troubleshooting' thread stickied in General; try as much of the stuff in that thread as you need to in order to get a successful flash of stock firmware & a clean slate (I.E a working phone, getting the phone back to this state should be your only thought at this point), then you can try reflashing a custom rom/whatever from there if you want to.
If you do have problems with the stock flash, make sure you actually do everything in the thread, or your phone will stay busted. These things are fixed with perseverance & doing everything possible, there is no easy fix.
Also, please don't post about the same issue twice, there was no need for you to make this thread & post to the other thread as well.
MistahBungle said:
Get stock firmware from Samfirmware, try & flash with Odin. Problems with flash ? Find Hopper8's 'Odin troubleshooting' thread stickied in General; try as much of the stuff in that thread as you need to in order to get a successful flash of stock firmware & a clean slate (I.E a working phone, getting the phone back to this state should be your only thought at this point), then you can try reflashing a custom rom/whatever from there if you want to.
If you do have problems with the stock flash, make sure you actually do everything in the thread, or your phone will stay busted. These things are fixed with perseverance & doing everything possible, there is no easy fix.
Also, please don't post about the same issue twice, there was no need for you to make this thread & post to the other thread as well.
Click to expand...
Click to collapse
So just flashing the stock rom? Does the firmware need to be specifically from that region you live in?
Got the Odin detecting my phone now so that's one step further. Huge thanks for helping me!
itsFreezy said:
So just flashing the stock rom? Does the firmware need to be specifically from that region you live in?
Got the Odin detecting my phone now so that's one step further. Huge thanks for helping me!
Click to expand...
Click to collapse
Yes, for me. I never tried to flash stock rom using other country. So, I don't know what will happen if I do so. Maybe you will get some problems with calls, messages, etc..?
So now i have tried to flash 3 different ROM's and everytime i get stuck for a while in the SetupConnection step and after about 2 minutes it just says all threads completed succeed 0/1 failed and cant open the serial (COM) port. I am on download mode on the phone.
Then you need to go back to Hopper's thread and try everything suggested in the thread, including multiple PC's if necessary.
I did say your phone will stay busted in my PP if you didn't do everything in that thread as many times as you need to (looks like the prophecy is being fulfilled). There is nothing else that isn't in that thread that can be suggested in these situations, that thread is the Bible.
Only you can fix your phone in this situation, we can't do it for you. I've given you the tools to get it done, it's up to you whether you do & how long your phone stays in its current state.
Huuuge thanks to you !
MistahBungle said:
Then you need to go back to Hopper's thread and try everything suggested in the thread, including multiple PC's if necessary.
I did say your phone will stay busted in my PP if you didn't do everything in that thread as many times as you need to (looks like the prophecy is being fulfilled). There is nothing else that isn't in that thread that can be suggested in these situations, that thread is the Bible.
Only you can fix your phone in this situation, we can't do it for you. I've given you the tools to get it done, it's up to you whether you do & how long your phone stays in its current state.
Click to expand...
Click to collapse
I already said this, but thank you for helping, i got it working! I flashed in a cwm kernel and stock rom.You really dont know how
grateful i am! It was kinda stupid to go and try install cyanogenmod without backing up, but that's not going to happen in the future.
Also i think i needed this to happen, i mean it still was a very good lesson to understand the basics of odin flashing and kernels,roms and rooting.
I really thought for a while that i had lost my phone. Hopper8's thread really helped!
Good man. And yes, you're right, having this sort of thing happen early on can be a really good learning experience & give you the knowledge/confidence to recover from just about anything (had a not dissimilar experience to yourself about a week after I got my S2 2+ yrs ago, I learned a helluva a lot in the two days my phone was borked) that happens in future.
Don't forget to thank Hopper's OP in his thread if you haven't already.
It's my beloved I9100P. Last night it strangely failed. I realised in the morning when the alarm didn't go off. The phone was switched off.
When I tried to switch on, it got stuck in boot loop. The carrier animation and samsung logo will keep repeating. So I thought I will go into recover mode and do a factory reset. Phone went into factory mode the first time. I thought let me do a restart from there, just to see what happens. At this point, I noticed a lot of red errors on recovery mode screen, most of which saying something like "unable to mount /cache". I restarted it, but unfortunately the phone again went into boot loop.
Now when I tried, it refused to go even to recovery mode. I tried several times, but every time it got stuck on Samsung Galaxy logo.
It went into download mode fine, so I thought I will flash Orange UK carrier ROM. I downloaded the ROM and tried flashing with ODIN. ODIN recognised the device, but the flashing failed with error "Complete (Write) operation failed".
I don't know what to do now, have exhausted all option that I knew.
Any help in reviving my phone please?
@kaushal101 Keep yourphone phone connected to your pc and keep it in download mode. Dont disconnect it it could turn into a hardbrick which you can't fix without jtag repair service.
What you could do is see or you have installled all drivers, kies is disabled, right odin version. Google the problem and you would probably find an answer fast. I hope this message isnt too late..
wulsic said:
@kaushal101 Keep yourphone phone connected to your pc and keep it in download mode. Dont disconnect it it could turn into a hardbrick which you can't fix without jtag repair service.
What you could do is see or you have installled all drivers, kies is disabled, right odin version. Google the problem and you would probably find an answer fast. I hope this message isnt too late..
Click to expand...
Click to collapse
Interesting. After trying several things, I did unplugged it from the machine. It shows the upgrade failed warning message whenever I try to switch it on now, which was expected.
I can still go to download mode and restart the ODIN flashing original Orange firmware process, but it fails with the same error. The only difference is, the first time it failed on CACHE step. Now it is failing one step earlier, at NAND writing stage.
Is there any hope? I had kies disabled etc., but will give it another shot. My phone was accessible with kies and I could also upload my development APKs from Android studio. So I think drivers shouldn't be a problem.
@kaushal101 I dont really have much knowledge about the s2 anymore, so the only good thing I can suggest is to google the problem and get more people to your thread here to help you and or find other threads about the same thing.
It is good that your phone can still go into downloadmode, I think there is still hope to fix your phone
wulsic said:
@kaushal101 I dont really have much knowledge about the s2 anymore, so the only good thing I can suggest is to google the problem and get more people to your thread here to help you and or find other threads about the same thing.
It is good that your phone can still go into downloadmode, I think there is still hope to fix your phone
Click to expand...
Click to collapse
Thanks for keeping the hope alive!
Have followed XDA's S2-ODIN troubleshoot guide, with no luck so far. Tried different versions of ODIN, reinstalled USB drivers, made sure KIES is removed from processes etc. None has helped so far. I'll keep looking!
kaushal101 said:
Thanks for keeping the hope alive!
Have followed XDA's S2-ODIN troubleshoot guide, with no luck so far. Tried different versions of ODIN, reinstalled USB drivers, made sure KIES is removed from processes etc. None has helped so far. I'll keep looking!
Click to expand...
Click to collapse
Did you tryed another stock rom version?
Try other usb cable.
Sounds weird but try to leave the battery out of your phone for like a couple minutes
Try other usb port.
Try other computer:silly:
These are the things I can think of atm.
Have tried other USB port. Have tried a different firmware.
Am going to try a different PC today, will also give different cable a shot. But the cable I'm using is Samsung official one which came with the phone. And I've been uploading APKs using this cable fine, so am quite sure the cable is fine. But still, will give it a shot. Thanks for replying