So today, While I was using it my phone suddently rebooted. Since then it could not boot back to android and is stuck at the google logo. I can still access CWM but even data wipe did'nt do any good.
Is there any way to save my phone ?
Kalak35 said:
So today, While I was using it my phone suddently rebooted. Since then it could not boot back to android and is stuck at the google logo. I can still access CWM but even data wipe did'nt do any good.
Is there any way to save my phone ?
Click to expand...
Click to collapse
Yes, definitely. If you're able to access download mode or the custom recovery, the device is easily recoverable. By easily, I mean most users are able to complete the steps although some users require more time and labor than others.
When the device hangs at the initial boot logo screen, in your case the Google logo, this generally indicates an issue with either the kernel or the ramdisk. The simpliest solution is generally to flash a known good kernel which is compatible with the currently loaded ROM.
If you have a nandroid on hand of a previously known good working state, that would be the easiest to restore. If not, you'll want to find a known good working kernel which is compatiable with the currently loaded ROM. If you're unable to find this combination, a ROM and compatible kernel will need to be loaded.
The odd part of the situation is how it seemed to "randomly" reboot and encounter this issue. Without knowning the details of the custom software loaded, difficult to accurately speculate the root cause.
Hope that helps point in the right direction!
Thank you.
Since I didn't know how to push files from my computer to my phone and had already done a full wipe I flashed google factory image and it worked!!
Now evrithing is good.
Thank you one more time, it realymade me freak out...
you wont't brick your phone unless you somehow brick the bootloader, even then you might be able to recover
So just to state the lead up to the unbootable phone.
Condensed version:
Flashed to Bio360 (ONLY working rom that was running for me thus far)
After a week of use, phone would boot for 5 seconds until screen turned pixelated
reflashed but did nothing
flashed to ICS using download mode again and worked but with limited function as when I first flashed ICS before Bio360
flashed using CWM6 back to Bio360 but still same problem
now will not boot into CWM6 and gets the pixelated screen either way
WILL go into download mode so I tried a few more ROMs to hopefully write over whatever issue there is with the software but nothing
reflashed using ODIN the CWM to 5 and 6 but same problem (will not load to CWM at all now
tried a few more times in the precise order as the first time I ever got the phone working with Bio360 (STILL a messaged up screen)
More detailed account of things:
I originally tried updating to the ICS upgrade a few weeks ago but got stuck on the boot screen and other issues. I finally flashed the CWM6 and updated the rom via that to the Bio360 rom. I finally had a working phone again after countless hours of trying to get it working. I locked my screen after timeout to a pin number but actually found it was a pain in the behind so tried to switch back. However I used the 'settings' feature which was present on the home screen after boot that comes with the Bio360. Then I deleted the icon an could no longer find the one that I was originally using, but found the other newer icon in the applications. So I took the lock feature off. Though it did nothing and the phone still required the pin. I tried changing it etc etc etc and nothing worked.
So, I flashed the Bio360 rom again and tried to start fresh, only to find that most of the settings that I originally were using before the re-flash were still present. This lead me to believe the settings are not completely wiped and flashing through CWM6 does not do a pristine clean update. Then I read that I should have to clear any and all settings by factory reset, clear cache, partition or whatever other clear functions I found within CWM6. So I did that and everything was back in good order again.
That is until I woke up 3 days ago and found my phone 'bricked'. Not literally as I am told it is almost impossible to brick one of these. Upon rebooting the phone I found that it was booting to the Samsung logo and after about 5 seconds, the screen becomes pixelated with red and green colours, sometimes lines all over. The longer I leave it, the more the screen becomes a wash out.
So I tried flashing the rom again using CWM6 hoping this would fix, but the same thing occured. So I tried to use CWM5 hoping that would fix it but still the same. I tried flashing back to gingerbread, then ICS, then Bio360 as I originally did to get the phone working with Bio360 but the only thing that I can do now is boot into download mode. Anything else causes the screen to become pixelated and wil not boot past the messed up screen no matter how long I leave it.
I searched for other threads but only found threads based on a single large pixel or a physically damaged screen. However, the screen is still functional as when I boot to download mode or just before the screen becomes pixelated, everything looks great. Plus there was one time when I flashed to ICS I got into the blank screen with limited functional capacity as when I first flashed ICS and the pixelated screen disappeared. So this leads me to believe this is a software issue.
I believe that there is an issue with files being left behind that are corrupted or something similar but I cannot even boot to CWM in order to clear everything possible.
ANY IDEAS? I have explored every option that my limited understanding of software could.
picture of what it looks like
This is a crappy picture from my old phone of something like what it looks like.
https://plus.google.com/photos/111944628817208100010/albums/5793637254528885841
This is a capture after it was turned off even and I plugged it into my computer, displaying the battery charging animation, though turned pixelated after a few seconds.
My gut says hardware damage, like something inside the Tegra itself is fried, ESPECIALLY since it's happening sometimes while still in the bootloader (charging animation).
Try Kies emergency recovery. If it flashes successfully but still won't boot, or glitches out like this during the flash, you'll have to start the RMA process.
I am unsure if it would be a hardware issue though since the screen is fine during the 'download mode' and did boot into the stock recovery after a flash a while back, then flipped back to not getting past the Samsung logo and pixelating again.
Would I be able to load the download mode portion of the phone if it was a hardware issue?
I ask because my gut says the opposite.
flashing CWM 6 causes my phone to be unbootable and pixelated screen
So, I have tried to update the phone into whatever other ROM that I can possibly get working only to find out that after flashing a ROM that flashes the original recovery program included with Android, voilà! The phone works again and boots into the black screen with pull down menu. Back to square one for me.
Why would CWM6 be causing such a thing?
EaglesIII said:
So, I have tried to update the phone into whatever other ROM that I can possibly get working only to find out that after flashing a ROM that flashes the original recovery program included with Android, voilà! The phone works again and boots into the black screen with pull down menu. Back to square one for me.
Why would CWM6 be causing such a thing?
Click to expand...
Click to collapse
I'm on CWMR6 since the begining without any issue. Did you flash the touch or the non touch version ? Also whcih odin version are you using, maybe that makes a difference. The 1.82 and 1.85 are tested to be working fine with both cwmr 5 and 6. Also by reading your thread is seems you've never been able to flash through ICS one click, if possible try doing that.
ninthsense said:
I'm on CWMR6 since the begining without any issue. Did you flash the touch or the non touch version ? Also whcih odin version are you using, maybe that makes a difference. The 1.82 and 1.85 are tested to be working fine with both cwmr 5 and 6. Also by reading your thread is seems you've never been able to flash through ICS one click, if possible try doing that.
Click to expand...
Click to collapse
I have been using the cwm5/6 touch and non touch. I have tried flashing them both. I have been using the most suggested version of ODIN 1.85 to flash. I do not think that it would make a difference as to which ODIN version I use, but then again I am quite ignorant on software.
The first thing that I did was tried the flashing using the one click method. I could only get to a black screen with the pull down menu containing the turn wifi on/off etc. I read that the problem may be permissions but I have tried that using the CWM when it worked and I was still stuck at the black screen with pull down menu. Without CWM I have no way of doing anything really since everything is in zip form and without CWM you cant use the zips.
EaglesIII said:
I have been using the cwm5/6 touch and non touch. I have tried flashing them both. I have been using the most suggested version of ODIN 1.85 to flash. I do not think that it would make a difference as to which ODIN version I use, but then again I am quite ignorant on software.
The first thing that I did was tried the flashing using the one click method. I could only get to a black screen with the pull down menu containing the turn wifi on/off etc. I read that the problem may be permissions but I have tried that using the CWM when it worked and I was still stuck at the black screen with pull down menu. Without CWM I have no way of doing anything really since everything is in zip form and without CWM you cant use the zips.
Click to expand...
Click to collapse
Well then probably a logcat output to a developer would help understand the problem you're facing. Find some knowledgeable developer who can help you read the logcat and find the issue. Or post it here and maybe somebody would give you a clue.
EaglesIII said:
So just to state the lead up to the unbootable phone.
Condensed version:
Flashed to Bio360 (ONLY working rom that was running for me thus far)
After a week of use, phone would boot for 5 seconds until screen turned pixelated
reflashed but did nothing
flashed to ICS using download mode again and worked but with limited function as when I first flashed ICS before Bio360
flashed using CWM6 back to Bio360 but still same problem
now will not boot into CWM6 and gets the pixelated screen either way
WILL go into download mode so I tried a few more ROMs to hopefully write over whatever issue there is with the software but nothing
reflashed using ODIN the CWM to 5 and 6 but same problem (will not load to CWM at all now
tried a few more times in the precise order as the first time I ever got the phone working with Bio360 (STILL a messaged up screen)
More detailed account of things:
I originally tried updating to the ICS upgrade a few weeks ago but got stuck on the boot screen and other issues. I finally flashed the CWM6 and updated the rom via that to the Bio360 rom. I finally had a working phone again after countless hours of trying to get it working. I locked my screen after timeout to a pin number but actually found it was a pain in the behind so tried to switch back. However I used the 'settings' feature which was present on the home screen after boot that comes with the Bio360. Then I deleted the icon an could no longer find the one that I was originally using, but found the other newer icon in the applications. So I took the lock feature off. Though it did nothing and the phone still required the pin. I tried changing it etc etc etc and nothing worked.
So, I flashed the Bio360 rom again and tried to start fresh, only to find that most of the settings that I originally were using before the re-flash were still present. This lead me to believe the settings are not completely wiped and flashing through CWM6 does not do a pristine clean update. Then I read that I should have to clear any and all settings by factory reset, clear cache, partition or whatever other clear functions I found within CWM6. So I did that and everything was back in good order again.
That is until I woke up 3 days ago and found my phone 'bricked'. Not literally as I am told it is almost impossible to brick one of these. Upon rebooting the phone I found that it was booting to the Samsung logo and after about 5 seconds, the screen becomes pixelated with red and green colours, sometimes lines all over. The longer I leave it, the more the screen becomes a wash out.
So I tried flashing the rom again using CWM6 hoping this would fix, but the same thing occured. So I tried to use CWM5 hoping that would fix it but still the same. I tried flashing back to gingerbread, then ICS, then Bio360 as I originally did to get the phone working with Bio360 but the only thing that I can do now is boot into download mode. Anything else causes the screen to become pixelated and wil not boot past the messed up screen no matter how long I leave it.
I searched for other threads but only found threads based on a single large pixel or a physically damaged screen. However, the screen is still functional as when I boot to download mode or just before the screen becomes pixelated, everything looks great. Plus there was one time when I flashed to ICS I got into the blank screen with limited functional capacity as when I first flashed ICS and the pixelated screen disappeared. So this leads me to believe this is a software issue.
I believe that there is an issue with files being left behind that are corrupted or something similar but I cannot even boot to CWM in order to clear everything possible.
ANY IDEAS? I have explored every option that my limited understanding of software could.
Click to expand...
Click to collapse
I have the same problem, i bought mine in ebay, (i live outside USA so i cant get money back) my problem start when i try to install a apk, then, i try to restore with wipe in cwm (sometimes works, sometimes no) and eventually, only download mode work. I dont know what i do, but in one of my trys, ICS 4.04 works everything, but i was network lock,i try to downgrade to Gingerbread and the problem come back, i dont know what to do, i feel like i waste te money.
PD: I have the roger version
EDIT: I just flashed ICS from ATT And works, but i w ould like to root and i cant, every time that i flash CWM, the problem come back
EDIT 2: I use the one click to install ICS from att and works, its seem the problem is when i use a custom rom or the CWM, dont know why, its seems that is not hardware because ICS works perfect, but Every custom rom or CWM, cause the problem
Maybe is there a way torecreate all the internal partition, i dont know, or something like that, to make a clean install, I am starting to regret for buying this phone, maybe the problem is because is from rogers (a security rule maybe?)
Sorry for my english
EaglesIII : your phone has hardware malfunction.
It is basically trash.
*sorry*
Sent from my SGH-I927 using xda app-developers app
ericpeacock79 said:
EaglesIII : your phone has hardware malfunction.
It is basically trash.
*sorry*
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
I dont Know, its happen similar to me, but if i use ICS from ATT, everything works right
---------- Post added at 03:05 AM ---------- Previous post was at 02:45 AM ----------
Ok, i learned something, when a flash the Gingerbread version, there is a error while booting (the first time that boot lik recovery) , the error is can't access to /system/csc/ATT/system/
When i use the ICS from ATT, that doesnt happen, maybe that is the problem? i dont know, maybe someone can tell us what are these files
There is a working solution, http://forum.xda-developers.com/showthread.php?t=1953672 thanks to Rawr0w0,its works when you flash in that order, my phone is rooted and full working in ICS, i hope that helps you
I was using my phone flashed with Mokee Nightly rom and everything was working great until the screen stopped working for no obvious reason. It happened yesterday, I tried to use the phone and the Home button didn't open the screen anymore. Then, I tried to reboot the phone but all I could see was the blue led flashing as if the phone was booting but there was nothing on the screen. When I got back home, I tried to repair the problem and I was able to enter download mode, so I used that opportunity to reinstall the factory firmware with Odin. I was able to get it working but I'm just wondering what was the cause of this? I know I'm a serial flasher so maybe something got ****ed up while flashing it and it caused it to bug later?
Nico3d3 said:
I was using my phone flashed with Mokee Nightly rom and everything was working great until the screen stopped working for no obvious reason. It happened yesterday, I tried to use the phone and the Home button didn't open the screen anymore. Then, I tried to reboot the phone but all I could see was the blue led flashing as if the phone was booting but there was nothing on the screen. When I got back home, I tried to repair the problem and I was able to enter download mode, so I used that opportunity to reinstall the factory firmware with Odin. I was able to get it working but I'm just wondering what was the cause of this? I know I'm a serial flasher so maybe something got ****ed up while flashing it and it caused it to bug later?
Click to expand...
Click to collapse
With custom ROMs, especially nightlies, errors like this are not to be unexpected. Recall it is still undergoing development and may not be bug-free. If you must stick with this ROM, I'd suggest you wait for the stable now that you know what may happen.
So I've had this problem, and I fought with it for one night until I got it working. I'm sharing my experience here in case others have this issue, and I invite people that have encountered this issue to criticize the way I fixed my problems so that we can get the minimum bricked to working procedure and identify issues in loading custom roms.
The problem is that the phone after flashing a custom rom will work, but you get 'no carrier' meaning that the radio on the device isn't connecting to your carrier. In my case, 'Sprint'. I don't know why this happens, but no matter what I did, I couldn't get it to connect.
What I had to do was go back to stock. The MD4 stock didn't work for me, it would display the samsung note 2 branding screen, then the screen would fuzz out like an old tv that lost the vsync signal, and then the red light would blink blink blink. I bricked my pho.ne
The good news is, I didn't completely brick it. What you have to do is ODIN the phone. The problem was, it would never go into odin mode, it would always crash before it got there. What I had to do was take the battery out and power it ONLY via USB. Then it would go into odin, and I was able to flash the LJC firmware. It seems that if you want to replace the radio, you have to flash an entire rom to do it. Those downloads are a gig!
So even after doing this, it wouldn't quite work right. If you still have issues, you may have to ODIN a new BOOT image. Once you do that, then when it boots you'll get the standard sprint logo and animation / sound, but it will still hang. What you have to do then is load a custom recovery (odin), boot into that recovery, and format system twice then cache twice. The recovery that worked best for me was ClockworkMod Recovery v6.0.4.3.
That seemed to reset the radio/carrier and then I could load the original LJC rom & radio. I verified that I could access everything. Then, I did CF Auto-Root, and loaded a new custom rom. All was working afer that!
Hi there!
I don't know if anyone will read these lines, since it's already quite an old phone, but I'll give it a try anyway.
Short story: my wife dropped her phone and the digitizer got smashed. I removed it and before I got the new digitizer on, our kid had had the time to break the LCD. So I bought a new LCD + digitizer module and installed it. Then I started the phone and got stuck at the Sony boot logo.
I've tried the repair function of the Xperia companion. It apparently detects the phone and goes throught the whole procedure, then tell me the phone's software's been repaired, but when I start it, I'm stuck at the logo again.
Just in case you wonder:
- bootloader is locked
- USB debugging was not enabled
So is there anything I can try, or should I just head to the phone store and buy her a new one? She was happy with it and sees no reason to change it, so if there's a chance we might save it...
EDIT: I have also tried this now:
- download a stock ROM in ftf format
- installed flashtool
- flashed the ROM (no USB debugging or unlocked bootloader required)
- flash successful
But I'm still stuck at the Sony logo, only that now, instead of having "Sony" in the center of the screen and "Xperia" on the bottom, I only have "Sony" in the center. I was hoping for more change than that
Thanks!
Fa
Alright, I haven't received a lot of answers, so I'm just going to post as I go. Maybe I'll get the damn thing boot again and this will help someone in the future.
Now I have downloaded a custom ROM, a recovery (actually I have dld both CWM and TWRP) and I'd like to flash it BUT: in order to do that, the bootloader must be unlocked.
I used flashtool (the "blu" button), and it worked. So that's out of the way. Now it seems I should have USB debugging on, but surely there is a way to flash a ROM without it? Or am I screwed?
How do I flash a recovery for the first time? The files I downloaded are img.
Thanks!
And here we go again
So I found from the list of Nougat ROMs that a very good one is LOS by Munjeni, so I decided to go with it (if I get the phone to work, I might as well go with a good ROM .
The instructions were clear, so first, what I did was:
- flash the openbootloader file to enable permanent recovery (flashed with Flashtool)
- flash recovery, I first went with TWRP provided on Munjeni's own page, but I could not use the touch interface, so I switched to CWM, since it offers physical button support (flashed with Flashtool)
- Then I copied the ROM (zip file) I downloaded from the same place to my microSD and inserted it into the phone.
- I wiped everything as required in the instructions
- I flashed the ROM from CWM
And voilà! I can now boot into the ROM!
The only problem is that my touch screen is unresponsive, although the whole LCD/digitizer assembly is brand new
It seems the touch interface just does not work, since it is unavailable in both recoveries and in the ROM.
Anyway, this is probably it for this thread, since the issue being stuck on Sony logo and not booting is solved (well, it boots into a ROM, not stock, but that's beside the point). Hope this will help someone else in the future!
Cheers!