Related
Help please. I'm basically in a boot loop with no recovery. Idk what I should do or if its possible to make a warranty claim.
Hey guys I'm in a boot loop of some kind. I'm not an advanced user of this stuff but idk what to do at this point. So this is the situation. I have a X10a from at&t and its rooted with busybox and freex10 recovery or whatever. I had a default 2.1 ROM and flashed the offline recharging thing. My phone seemed to work fine but then my battery died out. For a while I've had recharging problems with my phone either my cable is messed up or the usb port. So anyways after it died out I tried to recharge but I was in the 3x red flashing light problem and accidentally broke my charger cord, but continuing I borrowed my friends cord and still had problems so knowing my usb port is kinda broken i just left it there. After about 2 hours my phone majestically starts up lol. So I decided I wanted to put on xrecovery just incase and My computer wont read my phone. I try everything from takeing out my sd card to restarting my computer to reinstalling pc companion like 20 times. So I tried a factory reset through the phone settings and ended up where i currently am in a boot loop. It turns on and does the sony ericsson thing then does the boot animation then my phone vibrates and the screen darkens and my buttons are lit up. It has been like this for about 30 mins so far. I tried restarting my phone by taking out the battery and taking out the sd card/sim card.
Sorry for this being long but this is my situation. Could you please help me out? I Don't know if I can do a warranty claim or anything I'm desperate so please any help would be greatly appreciated. Thanks in advance. Also if there is anymore information you need please just ask.
use flashtool and flash a rooted generic 2.1 rom
install xrecovery
restore a back up
My computer can't read my phone. How can I fix that? It can go into flash mode but nothing shows up not even in the /:c/ area
if your phone is in flash mode, it's fine. start flashtool, click "flash", select the rom you want to flash, put phone in flash mode (turn off, hold back button while plugging phone in, wait for green light), click ok, let it do it's thing.
Even when i go into flash mode it doesn't work. It goes in flash mode while it searches then after a while the x10 leaves flash mode. Tbh I think its my cable though. Any idea where to get an official one that will ship to hawaii?
You may be missing the drivers.
Install SEUS "Sony Erricson Update Service" from the sony erricson website.
And let it detect your phone at least once.
You can also use it to restore your phone.
Good luck.
I got all the drivers. I'm just gonna buy a Xperia Play and see if i can fix my x10 and sell it or somthing. But thanks for all the help guys
Go to flashtool, press on flash select firmware. Then after it asks put your x10 connected without your battery. Put your battery in and it should flash.
cloud911208 said:
Even when i go into flash mode it doesn't work. It goes in flash mode while it searches then after a while the x10 leaves flash mode. Tbh I think its my cable though. Any idea where to get an official one that will ship to hawaii?
Click to expand...
Click to collapse
any mini usb cable should work. i use the cable from my bt device for my phone.
If the x10 goes out of flashmode, try to hold in the back button under the whole flashing progress.
cloud911208 said:
Even when i go into flash mode it doesn't work. It goes in flash mode while it searches then after a while the x10 leaves flash mode. Tbh I think its my cable though. Any idea where to get an official one that will ship to hawaii?
Click to expand...
Click to collapse
Any electronics store has the cables ranging from $5-$30 depending on what your looking for in quality.
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
Well thanks for the help. I'm gonna try use it on a different computer and see if it still works. Wish me luck.
Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much
One day my defy (which used MIUI Pikachu) didn't boot up properly. It showed me a MIUI splash screen. What I did was to go to bootloader mode and installed the CEE Nordic fixed SBF I found on the net. After flashing, the phone only gave me a motorola logo. I patiently waited for 15 minutes or so but nothing happened.
I took a research on the net and found out that I had to put my phone into stock recovery mode. But when I turned off my phone (Had to do it by a battery pull), pushed the volume down button and pushed the power button afterwards, the screen was still black.
So, what mistakes did I made, are there any ways to fix my phone without bringing it to service center. I think the problem lies in the sbf files, it's only 37mb while a "normal" sbf from droid-developers is about 200mb.
By the way, if my phone is a korean one, can I use a nordic version ?
yes you can fix it. take the battery out then put it back in after a while to make sure its off.
hold down volume up and push the power on. This will get you into bootloader, It may not show anything on the screen but if you hook up the USB cable and open RSD lite it should say its connected.
Now from here you just have to find the right SBF file to flash. This may take 1 go or 10 goes (took me about 10) till I found one that works and it booted straight away.
I must warn you, Your phone WONT! charge in this state so take the battery out when your downloading the files or not flashing it or using it as it will run the battery out fast.
If the battery runs out then you will have to search and do the macqyver method
idecaf said:
One day my defy (which used MIUI Pikachu) didn't boot up properly. It showed me a MIUI splash screen. What I did was to go to bootloader mode and installed the CEE Nordic fixed SBF I found on the net. After flashing, the phone only gave me a motorola logo. I patiently waited for 15 minutes or so but nothing happened.
I took a research on the net and found out that I had to put my phone into stock recovery mode. But when I turned off my phone (Had to do it by a battery pull), pushed the volume down button and pushed the power button afterwards, the screen was still black.
So, what mistakes did I made, are there any ways to fix my phone without bringing it to service center. I think the problem lies in the sbf files, it's only 37mb while a "normal" sbf from droid-developers is about 200mb.
By the way, if my phone is a korean one, can I use a nordic version ?
Click to expand...
Click to collapse
after flashing stock rom you have to get into stock recovery & do factory reset ^^ ph should boot up after that...
if your battery is flat/dead you need to become McGyver -=or=- get extra charged battery & repeat process
After flashing CEE nordic, T-Mobile US and UK roms, I couldn't even go to bootloader mode nor recovery mode. so this is impossible to clear date.
bootloader will not show but RSD lite will say its connected, Unless the battery is flat as it wont charge in this state.
If you hook up the macqyver method and turn the phone on holding the up button and connect the USB cable. RSD lite should say that its connected if you have done it right. It took me 3 goes to get it working but once I did it worked.
It took me 10 roms before I found one that worked. So dont give up
kelbygreen said:
bootloader will not show but RSD lite will say its connected, Unless the battery is flat as it wont charge in this state.
If you hook up the macqyver method and turn the phone on holding the up button and connect the USB cable. RSD lite should say that its connected if you have done it right. It took me 3 goes to get it working but once I did it worked.
It took me 10 roms before I found one that worked. So dont give up
Click to expand...
Click to collapse
same here. macgyver worked on about the 3rd attempt (not sure why, the wires looked connected each time), and my 3rd SBF worked... then i couldn't root, flashed another sbf, and the 5th method worked...z4root, superoneclick, doroot, droid2root, and DOOMLORD worked
but now my sdcard wont load, so i got more problems... sigh... if you have warranty just get a new phone!!!
I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it before by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
I don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?
Niko. said:
I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it before by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
I don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?
Click to expand...
Click to collapse
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.
htto said:
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.
Click to expand...
Click to collapse
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing
Niko. said:
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing
Click to expand...
Click to collapse
Too bad Anyway, did you try 8. from here, that is
"
If you get " Please manually power up this phone " in RSD Lite pull battery out > put your battery back > reboot into stock recovery by holding Power button and Vol- button > Choose Wipe data/cache > Choose Reboot system now
"? Also holding Power and Vol-Down while inserting battery is said to work.
I wonder if there is an SBF that also flashes cache and userdata partitions...
Nope, it just stays black-screened.... It only works if i do VOL-UP for bootloader mode, but that doesnt help
Umm, as a shot into the blue: Did you try to reinstall the Defy drivers from Motorola? It seems that missing those hinder RSD lite from detecting the Phone as MB52x and instead just show the Processor identification, i.e. "S Flash OMAP3630"
Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Sent from my MB526 using Tapatalk
thekguy said:
Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Click to expand...
Click to collapse
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.
htto said:
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.
Click to expand...
Click to collapse
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...
Niko. said:
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...
Click to expand...
Click to collapse
Umm, according to this thread it is supposed to be this one.
The GR vs CN maybe doesn't make a difference, but maybe the P022_A022 vs. P015_A030?
Doesn't a working phone portal allow for somehow to get logs/adb etc?
My Xperia M5 which was on Android 6 was on charging when this happened. When I removed the phone from the charger and tried to power on (as I remember the phone had around 60% of battery remaining and it had been switched on when I plug it to the charger; however the device had been powered off when I unplugged it from the charger), it showed me the Sony logo and after that some startup screen. Then it was all black. Phone was switched off automatically. I tried switching it on again and couldn't.
After a while I tried switching it on again and the same thing happened. Then I kept the device aside for couple of days and tried switching it on again. Nothing happened this time. Then I plugged that into the charger and it showed me the icon of charging. It started from 0% and went on to 100%. After that, I tried to switched it on again. The same thing happened, but this time, couple of iterations. But it was not a boot loop. I had manually switch the phone.
However, non of the attempts switched on the phone for me. I plugged the phone back to the charger and this time it did not show me the charging icon. But the red LED was switched on and it kept the color red all along. If the device was charging properly, the LED should gradually go to color green. But it did not. I cannot even power on to see the previously seen startup screen. But if I keep the phone away for couple of days to completely drain the battery out, i will be able to see the charging icon with a successful charging process again.
What I need to know is, what has happened to my device. Is it soft bricked or hard bricked?
To be honest, I can give it to the shop for the repair since I am still on warranty period. But I need to recover my data and completely wipe them out from the internal memory. I tried connecting it to the computer. but computer cant recognize it. But I hear the sound of new usb connection. It is like a loop. I hear it, then a silence for a while, and again I hear it. But nothing on screen of the phone or the computer.
One thing to mention is that, the device was once recognized by Yodot tool for android recovery when the device was charging successfully(As I mentioned previously). I scanned the device and the tool went through all the steps until the last step of recovery. In fact I did not have license for the tool.
What Can I do to recover my data?
And also I need to wipe off the internal memory too.
vigamage said:
My Xperia M5 which was on Android 6 was on charging when this happened. When I removed the phone from the charger and tried to power on (as I remember the phone had around 60% of battery remaining and it had been switched on when I plug it to the charger; however the device had been powered off when I unplugged it from the charger), it showed me the Sony logo and after that some startup screen. Then it was all black. Phone was switched off automatically. I tried switching it on again and couldn't.
After a while I tried switching it on again and the same thing happened. Then I kept the device aside for couple of days and tried switching it on again. Nothing happened this time. Then I plugged that into the charger and it showed me the icon of charging. It started from 0% and went on to 100%. After that, I tried to switched it on again. The same thing happened, but this time, couple of iterations. But it was not a boot loop. I had manually switch the phone.
However, non of the attempts switched on the phone for me. I plugged the phone back to the charger and this time it did not show me the charging icon. But the red LED was switched on and it kept the color red all along. If the device was charging properly, the LED should gradually go to color green. But it did not. I cannot even power on to see the previously seen startup screen. But if I keep the phone away for couple of days to completely drain the battery out, i will be able to see the charging icon with a successful charging process again.
What I need to know is, what has happened to my device. Is it soft bricked or hard bricked?
To be honest, I can give it to the shop for the repair since I am still on warranty period. But I need to recover my data and completely wipe them out from the internal memory. I tried connecting it to the computer. but computer cant recognize it. But I hear the sound of new usb connection. It is like a loop. I hear it, then a silence for a while, and again I hear it. But nothing on screen of the phone or the computer.
One thing to mention is that, the device was once recognized by Yodot tool for android recovery when the device was charging successfully(As I mentioned previously). I scanned the device and the tool went through all the steps until the last step of recovery. In fact I did not have license for the tool.
What Can I do to recover my data?
And also I need to wipe off the internal memory too.
Click to expand...
Click to collapse
M5 forum help and troubleshooting...
levone1 said:
M5 forum help and troubleshooting...
Click to expand...
Click to collapse
Yeah, I realized that I have posted in the wrong thread and sent an email to delete it for me
Thanks
The phone is faulty. Send to service Center.
ataraxist said:
The phone is faulty. Send to service Center.
Click to expand...
Click to collapse
I need to recover the data before sending it to the service center
vigamage said:
I need to recover the data before sending it to the service center
Click to expand...
Click to collapse
Did u do a hard reboot? Plug in charger while hard rebooting.
Another method is use Flashtool and flash the ROM again without wiping data.
ataraxist said:
Did u do a hard reboot? Plug in charger while hard rebooting.
Another method is use Flashtool and flash the ROM again without wiping data.
Click to expand...
Click to collapse
Flashing a ROM will avoid my warranty. Isn't it? I tried a tool called Yodot android recovery for data recovery. I think it found the data in the memory, but it does not allow me to retrieve data with out license. Is there any other tool which can help me in this case.? I have a concern about the warranty too.
vigamage said:
Flashing a ROM will avoid my warranty. Isn't it? I tried a tool called Yodot android recovery for data recovery. I think it found the data in the memory, but it does not allow me to retrieve data with out license. Is there any other tool which can help me in this case.? I have a concern about the warranty too.
Click to expand...
Click to collapse
U must be a noob. The first that says flashing a stock rom void warranty. It doesn't and if u do not know how to, it's better to send to the service centre.
ataraxist said:
U must be a noob. The first that says flashing a stock rom void warranty. It doesn't and if u do not know how to, it's better to send to the service centre.
Click to expand...
Click to collapse
I thought that flashing a rom is going to void the warranty. I know how to flash a rom, but never have flashed a one to a xperia device. Is the Flashtool the official one for xperia devices?
Have you tried to hard power off, "vol+ & power button"? I've had to do that this morning after switching my phone off yesterday to charge it, gone to switch it on this morning and nothing happened when I pressed the power button, I tried vol+ & power button and it vibrated a few times, tried the power button again and it switched back on. Try that or repairing your phone with official tools - http://support.sonymobile.com/gb/tools/xperia-companion/ - http://developer.sonymobile.com/open-devices/flash-tool/
vigamage said:
I thought that flashing a rom is going to void the warranty. I know how to flash a rom, but never have flashed a one to a xperia device. Is the Flashtool the official one for xperia devices?
Click to expand...
Click to collapse
If u are with Android 6, press power vol_up vol_down altogether and wait for vibration...10'sec...it might reboot.
---------- Post added at 01:00 PM ---------- Previous post was at 12:58 PM ----------
XperienceD said:
Have you tried to hard power off, "vol+ & power button"? I've had to do that this morning after switching my phone off yesterday to charge it, gone to switch it on this morning and nothing happened when I pressed the power button, I tried vol+ & power button and it vibrated a few times, tried the power button again and it switched back on. Try that or repairing your phone with official tools - http://support.sonymobile.com/gb/tools/xperia-companion/ - http://developer.sonymobile.com/open-devices/flash-tool/
Click to expand...
Click to collapse
Only this flashtool host m5 rom
http://forum.xda-developers.com/showthread.php?t=2489955
ataraxist said:
If u are with Android 6, press power vol_up vol_down altogether and wait for vibration...10'sec...it might reboot.
---------- Post added at 01:00 PM ---------- Previous post was at 12:58 PM ----------
Only this flashtool host m5 rom
http://forum.xda-developers.com/showthread.php?t=2489955
Click to expand...
Click to collapse
According to this article, we can use the latest flashtool for flashing the rom
ataraxist said:
Did u do a hard reboot? Plug in charger while hard rebooting.
Another method is use Flashtool and flash the ROM again without wiping data.
Click to expand...
Click to collapse
Now I am going to Flash the rom. But the concern is if I do not have enough battery, it will hard brick my device while flashing. I cannot check my battery percentage sine I don't have any way of checking that.
How can I check for my battery pls?