alright..
i've read possibly 5 or 6 threads from start to end, post by post last week..
some people faced similiar problems but none of them faced exactly the same..
only one guy did, but i don't know if he could solve it or not..
i'm trying to install Wolf's gingerbread ROM but i have a problem on flashing..
i've downloaded all the files in this topic and followed all the directions there correctly..
i have installed SEMC Flash Drivers..
tried different USB ports..
but i keep receiving this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
anyone faced the same problem before or can help about solving it?
*
edit:
here is a similiar thread but i get the error sooner..
**
edit:
this either didn't work..
the green led never turn on, until i put the battery back in..
***
edit:
can this be the problem:
in the tutorial's pictures "Firmware Content" frame shows the included .sin file
****
edit:
I solved the problem with a very wierd way.
Hope it helps when you try.
After you've extracted and installed Flashtool;
go to your computer's Control Panel.
Open "Clock, Language and Region".
Click "Region and Language".
Choose format as English (United Kingdom); and location as United States.
Click ok and close control panel.
Now you shold be able to see loader.sin and kernel.sin files inside "Firmware Content" frame when you open Flashtool.
Same error to me...I try everything, every tool that I found for X10 but nothing help it...I also try wotan server with several different firmwares but always same error...ERROR: file header write failed!
I think that is imposible to repair without some dongle like setool...
i try to help...
1.first root ur stock rom n install xrecovery....
2.backup stock rom using xrecovery..
3.wipe data, wipe cache, n wipe dalvik cache using xrecovery...
4. install wolfbreak rom using "XRECOVERY".. When finish, put out the battery
5.lastly install the 2.3.3 n .71 baseband using flashtool....
phobias1903 said:
edit:
can this be the problem:
in the tutorial's pictures "Firmware Content" frame shows the included .sin file
Click to expand...
Click to collapse
wtf dude, you are missing some files there!??! "loader.sin & kernel.sin" ... try re-downloading the flashtool from that thread (http://forum.xda-developers.com/showthread.php?t=1196808)
cikgu senaman said:
1.first root ur stock rom n install xrecovery....
Click to expand...
Click to collapse
man, thats the point where we have problem..
slikk76 said:
wtf dude, you are missing some files there!??! "loader.sin & kernel.sin" ... try re-downloading the flashtool from that thread (http://forum.xda-developers.com/showthread.php?t=1196808)
Click to expand...
Click to collapse
i have downloaded them but i'll try again..
Hey I've had the same exact problem for about 3 months now I've tried everything i can think of.
i even made a battery charger from a usb cord to make sure it wasn't the battery being dead...
D:
any news?
I was having the EXACT same issue that led me to this thread. I had a custom kernal loaded so not sure if that was why I was getting "error flash aborted". Anyhow as someone mentioned here, I held down the back button until the entire flash was completed. That finally worked. Thanks!
One2many said:
I was having the EXACT same issue that led me to this thread. I had a custom kernal loaded so not sure if that was why I was getting "error flash aborted". Anyhow as someone mentioned here, I held down the back button until the entire flash was completed. That finally worked. Thanks!
Click to expand...
Click to collapse
I've had this issue for about a month, I'll try your method when i get home
I had come to the conclusion it was some kind of NAND deterioration
AusX10 said:
I've had this issue for about a month, I'll try your method when i get home
I had come to the conclusion it was some kind of NAND deterioration
Click to expand...
Click to collapse
hi! have you somehow restored your x10 back to life?
if it is NAND problem, have someone found a way to repair/replace it?
necrohades said:
hi! have you somehow restored your x10 back to life?
if it is NAND problem, have someone found a way to repair/replace it?
Click to expand...
Click to collapse
Nope sorry mate I have two devices, that's why i assume its hardware failure because they were both flashed the same way and my primary one is fine (running FXP45)
The bricked X10 is actually from a much newer batch which is odd, you would think the first one to die would be the one i have been flashing roms on since i debranded my 1.6 rom!
The phone is beyond my help now i think because its not even getting into flash mode and neither SEUS or flashtool can see it. It slowly got worse and worse until it wouldn't do anything at all.
I have been using Wolf's tweaked GB ROM for ten days.
I solved the problem with a very wierd way.
Hope it helps when you try.
After you've extracted and installed Flashtool;
go to your computer's Control Panel.
Open "Clock, Language and Region".
Click "Region and Language".
Choose format as English (United Kingdom); and location as United States.
Click ok and close control panel.
Now you shold be able to see loader.sin and kernel.sin files inside "Firmware Content" frame when you open Flashtool.
X10 failure in flashing ROM
I experienced a very hard situation after an unsuccessful ROM flashing onto my x10. Flashing procession was nearly finished but error message was happened and then aborted! Since that my device was permanently unbootable at all, when press the switch button to turn it on, there was no vibration nor SE boot up logo, just a red light brinked up for a few seconds. It seemed to be permanently dead. I tried many ways to reflash ROM onto the device via SE PC Companion, SESU, FlashTool but the program couldn't detect the device nor wiring on flash mode.
The device could not be accessed at all. Is there any experts who can solve this problems, please show me and the other owners how to fix X10 in this matter upon the software; programs, and the obvious procession. That would be greatly appreciated.
tommyboy_bkk said:
I experienced a very hard situation after an unsuccessful ROM flashing onto my x10. Flashing procession was nearly finished but error message was happened and then aborted! Since that my device was permanently unbootable at all, when press the switch button to turn it on, there was no vibration nor SE boot up logo, just a red light brinked up for a few seconds. It seemed to be permanently dead. I tried many ways to reflash ROM onto the device via SE PC Companion, SESU, FlashTool but the program couldn't detect the device nor wiring on flash mode.
The device could not be accessed at all. Is there any experts who can solve this problems, please show me and the other owners how to fix X10 in this matter upon the software; programs, and the obvious procession. That would be greatly appreciated.
Click to expand...
Click to collapse
blinking red you say?
try to charge your battery first, probably using a desktop charger, or another fully charged battery, and re-do flashing through either SEUS or repair thru PCCompanion.
blinking red led indicates battery power too low to boot.
if that fails, i'm afraid you have to try and see a tech
phobias1903 said:
After you've extracted and installed Flashtool;
go to your computer's Control Panel.
Open "Clock, Language and Region".
Click "Region and Language".
Choose format as English (United Kingdom); and location as United States.
Click ok and close control panel.
Click to expand...
Click to collapse
I was able to flash back to stock generic firmware 2.0.A.0.504 using this, not sure if this was the fix or coincidental. Using X10 Flash tool 0.5.3.0.
From there I have flashed the correct BB, Doom kernel for unlocked and recovery yadda yadda. The phone lives (for now...)
Related
This Thread is for those Unlucky Users of X10 mini who were hang in Boot-Loop and Can't able to Switch-Off their precious phone.
I am talking about An Hardwre Trick to Switch-Off your phone and make it to the SEUS easly... Thats works 101%.
To Switch-Off your Phone you need to perform these Steps....
1. Remove the back cover.
2. You will see a rubber cog Just left side of the Camera...
3. Remove the Rubber Cog by any way (just be gental with it)....with the help of Pin or Sumthing that you can lift it up.
4. After removing that Cog.....you will see a White small Plug that connects the wire to internal battery!!!
5. Remove that Pulg(Very gentally.......with the same method you done with Cog).....After this you will see that your phone got Switched-Off.
6. Replug the White Pulg.And the Job is Done.
7. Launch the SEUS application in your computer and follow the steps....
8. And WOW you got your Phone back Completely working!!!
Here's The Screen Shots For The Respective Steps-:
(Sorry For The Blurry Images)
1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2,3.
4.
5.
6.
This Isn't Risky....I Personally Done This Method Several Times!!!!
(So No Need To Be Afraid)
Don't Forget To Click On THANKS Button If It Helped You!!!
Disclaimer-: I AM NOT RESPONSIBLE for any damage to your precious device......But i'll help to solve any Query regarding this method!!!
I think flash tool method is safer. No need to power off just holding home+power button make phone restart.
Sent from my X10mini using XDA Premium App
I've put the link for your thread on my blog. I hope you don't mind.
http://xperiaminicyanogen.wordpress.com/help/bricked/
yeah, this kinda feels too risky, better the simple connect phone, open flashtools,select a rom to flash, press home+back+on and then release everything but back, works every time
LOL nice share..but by pressed power+home key i can restart my mini...
But without really turning off your phone, you can't use SEUS or flashtool.
Divr said:
But without really turning off your phone, you can't use SEUS or flashtool.
Click to expand...
Click to collapse
Not really.
Check this post.
Done it hundreds of times, always worked even when the phone was on a bootloop.
Regards, D_d
Divr said:
I've put the link for your thread on my blog. I hope you don't mind.
http://xperiaminicyanogen.wordpress.com/help/bricked/
Click to expand...
Click to collapse
Yeahhh i really don't mind.....its a kind of help!!!!
Clarification Of Thread !!!
People please try to understand this is for those people who can't able to handle the Loop problem with only (Power+Home) buttons.......or miss there clicks during several restarts to flash there ROM.....This method enables them to easy flash there ROM.....without doing this in hurry....So did you people got that!!!!
Any more query!!!
DaRk_dOg said:
Not really.
Check this post.
Done it hundreds of times, always worked even when the phone was on a bootloop.
Regards, D_d
Click to expand...
Click to collapse
That's right, on a bootloop there's no way to make flashtool work!
Anyway during bootloop xrecovery works fine and if i know what i did wrong i can fix it
zippov3 said:
That's right, on a bootloop there's no way to make flashtool work!
Anyway during bootloop xrecovery works fine and if i know what i did wrong i can fix it
Click to expand...
Click to collapse
Of course you can.
If you had your /system formatted (by accident or smth), you would not be able to access xrecovery menu.
However, you can stop the bootloop sequence with the instructions i posted earlier (and it is not something secret, most of the advanced users know this procedure). Flashtool and SEUS can recognise the device and they work.
seems u just wanna have an arguement. i myself tried ur method first and i went crazy without any luck. then i got a toolkit and actually opened my phone apart and took out the battery terminal and reinserted it. i wish that i got pratyush idea before. it would have saved me lot of time
DaRk_dOg said:
Of course you can.
If you had your /system formatted (by accident or smth), you would not be able to access xrecovery menu.
However, you can stop the bootloop sequence with the instructions i posted earlier (and it is not something secret, most of the advanced users know this procedure). Flashtool and SEUS can recognise the device and they work.
Click to expand...
Click to collapse
Agree with you. I have done it a few time by those instructions uou posted earlier and I know other users who have done it by the same way also.
abdullah1982 said:
seems u just wanna have an arguement. i myself tried ur method first and i went crazy without any luck. then i got a toolkit and actually opened my phone apart and took out the battery terminal and reinserted it. i wish that i got pratyush idea before. it would have saved me lot of time
Click to expand...
Click to collapse
abdullah1982,
i don't need to argue with anyone and it is very sad that i have to defend myself right now. I have fixed, or help in fixing, many bricked mini/mini pro devices and many users in here, know my contribution.
I insist on the button reset method because its less dangerous than just pulling the battery connector plug.
It is not my fault if you were incapable of doing a soft reset, but that does not mean i am obliged to accept malicious criticism from you or anyone.
I understand that pratyush_gamer's pure intention, was to help people and i am not try to offend him IN ANY WAY.
BTW take a look at this thread. You will see that "unplug connector" method was well known before.
Regards, D_d
Guyz its ok.....this will be a hardware method its a little bit unique......And if anybody got software Technique its better.....but its really Safe as well as Reliable.
So if any of you wanna try it.....its ok ......nothing to worries about.....
I AM ALWAYS HERE TO HELP!!!
@D_d i know you just wanna help....but dude...if they find this method more easy or secure or reliable.....thats really no matter.This thread is mean for that purpose only......I heard many times about the Phone Got Bricked....so i just tried to help.....Thats why i created or suggested this method.........if you really didn't seems this thread to be secure....Then its OK.....But pls don't let others to Dis believe others.....
THANKS Bro.
@gopichand2810 down is your file dude!!!! replace is with ur 's
Click Thanks Button if it helps you!!!!
what now, help!
ok i managed to shut off the phone, plug in to seus, reply..ur software up todate, no repair option? this problem was during installing a new rom. after installing, rebooting to se logo..loop..se logo...loop...when i plug in the power charge there is no light.
Dude if you aren't able to update via SEUS...then pls try thses steps as in order -:
1. Start SEUS(updated version).
2. Choose your phone model.
3. Turn -Off your phone and then press next at SEUS.
4. Plug the USB cod with pressed back button(jsut before you plug the USB to phone click & hold button).
5. After checking the software it says that you got the latest version of fermware....if prob. then Repair.
6.Click repair and it will start.
sorry i m not clear on step 4. can explain again? tq. i tried again as much your step but no repair
cwkhong said:
sorry i m not clear on step 4. can explain again? tq. i tried again as much your step but no repair
Click to expand...
Click to collapse
4. i mean that first click and hold Back button on phone,keep holding button and plug USB cod in ur phone!!!!
There is people out there that can't figure out how to use PC Companion to fix their phones, this tutorial is going to show you how to reinstall the stock Android 2.3 SE firmware and Kernel wich is usefull if you are stuck at the SE Logo, experiencing battery drain issues or if you just want to make a fresh install of a custom ROM
I am not responsible if you break your phone (more than it is already ) so do it at your own risk.
This is a really easy process so keep calm if you follow all the steps i bet your phone will be fixed
Before doing this you have to consider a couple of things:
You are going to lose all your data.
If your phone is Rooted, Root will be gone (you are going to lose superuser and xrecovery aswell).
Phone it's going to be like if it was brand new (it will include all the Service Provider useless apps and default settings).
Be sure to have at least 50% of battery life because PC Companion is going to download the stock ROM from server when your X10 is already connected in flash mode and this could take a while. If you need to charge the battery and you are stuck at SE logo: take the battery out, connect phone to charger then put the battery in.
External Memory will be formatted so your photos, music and everything in SD will be wiped.
Ok, Let's do it!!
- Don't Connect your phone to USB yet and Open PC Companion. (if Support Zone doesn't show up restart your PC and try again)
Then just follow the instructions:
1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.
3.
4.
[/IMG]
5.
6.
Sometimes after this step it says something about Server Connection Error or something, this means your PC can't connect to SE servers so you should check your internet connection or your firewall settings, sometimes SE servers are down (happened to me, if this is the case just try again later).
7.
8. Now this is the tricky part BE SURE TO HAVE AT LEAST 50% BATTERY LEFT BEFORE DOING THIS STEP and turn your phone off:
If in this step your phone turns on to the SE logo instead of the GREEN LED just unplug your phone, take the battery out and try to put the battery in first but inmediately after press and hold the back button and plug X10 to USB, then green led will appear and release back button
After 15 minutes or something (it depends on your PC's internet connection speed) your phone will be flashed and it will restart by itself and it will be fixed
Sorry if my english sucks it isn't my native language xD
Hope this helps all the noobies out there! and don't worry your PC Companion won't be in spanish like mine, peace
Very Good
Great post there my friend! easy simple to follow (even though pc companion is in Spanish ). My question is what if the phone does not want to boot at all? So no S.E. logo appears or anything, can the pc companion still repair the x10 and get it to work again? not that mine is just curious...
now this message..
Agera said:
Great post there my friend! easy simple to follow (even though pc companion is in Spanish ). My question is what if the phone does not want to boot at all? So no S.E. logo appears or anything, can the pc companion still repair the x10 and get it to work again? not that mine is just curious...
Click to expand...
Click to collapse
If you are able to set X10 into Flash Mode it still can be flashed, the only problem would be how to charge the battery.
Sent from my X10i using XDA App
romasalah said:
now this message..
Click to expand...
Click to collapse
Try running PC Companing like an admin, if the problem continues try uninstalling/reinstalling PC Companion, by the way sometimes the SE server is down so you may get an error about it, when that happens just try again later.
CescVicious said:
If you are able to set X10 into Flash Mode it still can be flashed, the only problem would be how to charge the battery.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Its my friends phone, he cant fix it nor can be bothered so he went and got himself another phone and is willing to sell the phone to me for $100, but his telling me it wont boot at all.. so if use my battery instead of his there might be a possibility i can get it going into flash mode?
Agera said:
Its my friends phone, he cant fix it nor can be bothered so he went and got himself another phone and is willing to sell the phone to me for $100, but his telling me it wont boot at all.. so if use my battery instead of his there might be a possibility i can get it going into flash mode?
Click to expand...
Click to collapse
Maybe, but the only way to be sure is doing it
i do all the steps but when its trying to connect to the phone it says to me to tab mount while i'm stuck at SE logo
Is there any way to go from 2.1 back to 1.6. My wife has this phone and hates the new update.
Sent from my Inspire 4G using XDA Premium App
So if i follow that it will return my phone to stock firmware? So xrecovery gone as well?
Andybrit said:
So if i follow that it will return my phone to stock firmware? So xrecovery gone as well?
Click to expand...
Click to collapse
Yes xrecovery will be gone.
Sent from my X10i using XDA Premium App
Ok thanks. I haven't rooted my phone yet (only got it a few days ago), but i could root my phone, installed xrecovery and enable JIT. Then once gingerbread comes out i do this and restore it back to normal and upgrade using sony's updater?
Yes I am pretty sure.
Sent from my X10i using XDA Premium App
Is there any way I can put on any kind of rom when all of my partitions are empty (hence stuck on Sony Ericsson Logo), and the usb port is broken?
Thanks CescVicious. it works finanly.
Do you need a video how to repair your phone ? +.+
pc companion does not repair
hiii i tried to repair my x10i but pc companion says software not available...
any other solutionnnn????
I'm having the same problem as Mr. Hello. I'm not exactly experienced at this, but I've flashed my phone about 7 times since the first 2.1 appeared before the official release. I'm currently running 2.3 cyanogenmod 7. I've given it about 2 months worth of testing and regardless of what people have said, it's the worst of the three 2.3 roms I've tried. The only feature I truly enjoy that most mods don't have is the auto screen orientation for all apps including the app menu. I found a nice stock 2.3 and I'd like to try it out and wanted a fresh stock base to go from. I thought this would be less work than finding the appropriate firmware/baseband/rom but its turning into more. Any help would be appreciated.
Right now i am on xperia s rom android version 2.3.4 unlocked bootloader can i use this guide and will i be able to get the stock rom back
Goder101 said:
I'm having the same problem as Mr. Hello. I'm not exactly experienced at this, but I've flashed my phone about 7 times since the first 2.1 appeared before the official release. I'm currently running 2.3 cyanogenmod 7. I've given it about 2 months worth of testing and regardless of what people have said, it's the worst of the three 2.3 roms I've tried. The only feature I truly enjoy that most mods don't have is the auto screen orientation for all apps including the app menu. I found a nice stock 2.3 and I'd like to try it out and wanted a fresh stock base to go from. I thought this would be less work than finding the appropriate firmware/baseband/rom but its turning into more. Any help would be appreciated.
Click to expand...
Click to collapse
Have you tried it yet? What happened?
sudersanmurthy said:
Right now i am on xperia s rom android version 2.3.4 unlocked bootloader can i use this guide and will i be able to get the stock rom back
Click to expand...
Click to collapse
Yes works on all Xperias to go back to 100% stock. Pretty sure this relocks bootloader and everything.
~Jaramie
from my LT28at rooted & eating an Ice Cream Sandwich
I upgraded my Neo to 2.3.4 from pccompanion for test it, then downgraded to 2.3.2 to enable root and my battery shows 0% charge. It refuses to charge showing always a red light on led. Reflashing to 2.3.4 doesn't resolve problem. Reflashing 2.3.2 and rooting to delete batterystats.bin doesn't resolve the problem.
I tried everything, remove battery, cleaning it, charging via pc usb, via wall socket all night...
I see in Arc forums more people with this problem.
First rule of safety. Don't trust some ftf(or any software for that matter) files put up from china. There are more expert hackers there than you can imagine. Anything might have some little "bonus" code along the normal stuff(doing nothing in your interest), which may break some normal functioning as well. Blind faith and trust will get your stuff broken sooner or later. IF the ftf is in any way tampered it will not work well with your locked bootloader, things can and will break. Use Wotanserver, it's safer but even then... you're not 100% safe.
You tried relocking bootloader and repairing via SEUS?
Get 2.3.3 via Wotanserver before if necessary.
remove the battery from phone and reconnect.
My bootloader is locked. I always used wotanserver to downgrade, so no chinese ftf used. And tried upgrading, downgrading and repairing via SEUS and problem persists.
I removed battery and reconnected dozens of times.
Seems that in Arc forum are more people with same problem.
Ok do you know that you can start phone without battery? I can't immediately find the thread here in XDA. One method was in Motorola Defy forums, using spare USB cable to connect it to phone - and + battery connectors. For other you need some battery juice to get to second bootimage.
Had my defy go into similar state after USB connection failed during upgrade to official froyo... It was deader than dead. Sent it back to shop for repairs.
If you can get another battery you could try if your phone is discovered in SETool and if not then on this thread you can find help to fix bootloader http://forum.xda-developers.com/showthread.php?t=1254409.
To use it you still need a charged battery, so get yours charged or get new.
Did you watch btw how much battery you had left before flashing? Flashing may fail in mid process if it goes below 40%.
Hi Elessar, I suggest you to send your phone to SE if you still have your warranty. I had the same problem and SE replaced a new motherboard for my NEO. I saw this issue on a couple of forums and there is no solution yet.
And Raoa, I do understand your concerns, but I think you have worried too much. Most ftf files that I can find on Chinese forums are mirrored from XDA as well as flashing tools, etc. If the Chinese really want your phone hacked, it has already been hacked anyways, because your phone is probably made in China or part of some part of your phone is made in China.
flash any stock FTF
DO NOT power on device
now directly connect to charger (usb or wall charger) for a few hours [make sure that the offline-charging "animation" is seen on screen]
the battery stats will get refreshed
DooMLoRD said:
flash any stock FTF
DO NOT power on device
now directly connect to charger (usb or wall charger) for a few hours [make sure that the offline-charging "animation" is seen on screen]
the battery stats will get refreshed
Click to expand...
Click to collapse
flashed the stock ROM
did not power on the device.
directly connected to the wall charger....
but the device powered on automatically and the battery still at 0%..
PLEASE HELP!!!!!! I DONT EVEN HAVE THE WARRANTY NOW....
Your logic is incomplete yunle. It's the other way around, a very eager ftf providing comes from China, and these files get mirrored on US/EU servers not the opposite way. Official phone making is not the same as "enthusiastic" providing of unofficial flashing files. 3rdly, trust or not, but always check what is what. Worry and think whatever, thinking can always be wrong. I rather trust an European who puts the source of SE files up along with user made ftf file. Saying anything else is suggesting to "flash away and don't think, all will be fine, nothing bad will happen".
Anyone with this battery problem have you tried relocking bootloader and fixing via SEUS? Try it, if you haven't. It worked for someone in a simliar situation.
My bootloader is locked by Vodafone and tried to refix with SEUS 3 times, no luck.
DooMLoRD said:
flash any stock FTF
DO NOT power on device
now directly connect to charger (usb or wall charger) for a few hours [make sure that the offline-charging "animation" is seen on screen]
the battery stats will get refreshed
Click to expand...
Click to collapse
Can anybody confirm that this works, I tried it but as soon as I connect to wall charger the phone auto start!!
Please DooMLoRD Help...
No, phone autostarts for me too.
My arc got this problem too.can anyone tell me which way to get it back normal???
I tried，doesn't work。 Plug in the charger and phone starts
Can someone try this modification of DooMLoRD's advice:
1. flash any stock FTF
2. DO NOT power on device
3. now press back button without release it and directly connect to charger (usb or wall charger) for a few hours [make sure that the offline-charging "animation" is seen on screen] and test if led is green or orange. If it's red, it doesn't work.
4. If it's not red, you can release back button and wait a few hours charging and reboot your phone.
regards
my arc show green
heidality said:
my arc show green
Click to expand...
Click to collapse
Really?
My Neo don't show green LED....
Same issue happened with me also
Hey man,,
I do have same problem after flashing 2.3.2 kernel from wotanserver for rooting my Xperia Neo mobile.
I tried everything all night charging... and reflashing latest update from SE PC suite.
Same issue persists..
Tomorrow I am going to contact SE service people.
Regards,
Bhanu Chaitanya
Hyderabad,
India
Hello, sorry for my english.
Can you guys try this method:
There is a simple reset button at the back of the phone.
Firstly remove the hull, then see that images:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
remove the plastic mask
Then press the button.
I hope that could help you
NeoJeo said:
Hello, sorry for my english.
Can you guys try this method:
There is a simple reset button at the back of the phone.
Firstly remove the hull, then see that images:
remove the plastic mask
Then press the button.
I hope that could help you
Click to expand...
Click to collapse
Are you sure it is BUTTON, not plug for ANTENNA....?
Hello, my phone is stuck ath the sony logo, when I restart it it just stays there. What should I do to make my phone work again?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is the last working picture of my phone
mrdjibrilo said:
Hello, my phone is stuck ath the sony logo, when I restart it it just stays there. What should I do to make my phone work again?
Click to expand...
Click to collapse
Stock, no root or recovery?
Have you used flashtool before?
EDIT: First of all turn it off: hold power | volume up untill you feel 3 vibrations. and charge.
ChikeD said:
Stock, no root or recovery?
Have you used flashtool before?
EDIT: First of all turn it off: hold power | volume up untill you feel 3 vibrations. and charge.
Click to expand...
Click to collapse
thanks I did that, the power/volume combo, and it turned off, and then I used this http://talk.sonymobile.com/t5/Xperi...ctions-using-Pc-Companion-Windows/td-p/249946, if anyone has the same problem this will solve it!
mrdjibrilo said:
thanks I did that, the power/volume combo, and it turned off, and then I used this http://talk.sonymobile.com/t5/Xperi...ctions-using-Pc-Companion-Windows/td-p/249946, if anyone has the same problem this will solve it!
Click to expand...
Click to collapse
Now I would recommend building your flashtool flashable firmware file from PCC/SUS files.
flashtool: http://www.flashtool.net/
Guides:
http://mytechencounters.wordpress.c...eate-an-ftf-file-of-your-xperia-ics-firmware/
http://forum.xda-developers.com/showthread.php?t=2188129
ChikeD said:
Now I would recommend building your flashtool flashable firmware file from PCC/SUS files.
flashtool: http://www.flashtool.net/
Guides:
http://mytechencounters.wordpress.c...eate-an-ftf-file-of-your-xperia-ics-firmware/
http://forum.xda-developers.com/showthread.php?t=2188129
Click to expand...
Click to collapse
i was trying to put cyanogenmod's kitkat4, but it failed, and started showing only the sony logo, while trying to fix it(before i saw this thread), i flashed the c-mod's kernel onto my phone, that didnt help, and now i'm not able to update my phone using the sony site link which is given above, it says, "unkown software is present in the phone, so cant install". Somebody please help!! :crying::crying:
dont panic bro
lalithesh said:
i was trying to put cyanogenmod's kitkat4, but it failed, and started showing only the sony logo, while trying to fix it(before i saw this thread), i flashed the c-mod's kernel onto my phone, that didnt help, and now i'm not able to update my phone using the sony site link which is given above, it says, "unkown software is present in the phone, so cant install". Somebody please help!! :crying::crying:
Click to expand...
Click to collapse
stay calm i know how u feel.flashing kernel wont help u cus u missing some system file that why your phone won't boot.Just do as i say
1.download flashtool here the link http://www.flashtool.net/download.php
2.download xperia p stock firmware jb or ics or gb(i recommend jb this link http://forum.xda-developers.com/showthread.php?t=2322163 )
3.learn how to use flashtool (i think already know how to use it but if u dont try to search google)
4.flash it done
work or not please tell me maybe i can help u more
flashtool is ur last option, 1st u need to repair using SUS. since u can open ur phone so its not going to be any problem in repair it using SUS. just open sus, close ur phone and press power and up down button and plug the usb to enter flashmode.
1st of ll power off your phone bu presiing power & Vol+button ubtill you feel 3 vibrations,then Charge your phone for atleast 1 hr.Then flash the stock JB/ICS/GB firmware (ftf(including kernel)),whichever you want.Thats it!
dara007_168 said:
stay calm i know how u feel.flashing kernel wont help u cus u missing some system file that why your phone won't boot.Just do as i say
1.download flashtool here the link http://www.flashtool.net/download.php
2.download xperia p stock firmware jb or ics or gb(i recommend jb this link http://forum.xda-developers.com/showthread.php?t=2322163 )
3.learn how to use flashtool (i think already know how to use it but if u dont try to search google)
4.flash it done
work or not please tell me maybe i can help u more
Click to expand...
Click to collapse
Thanks a lot dara, really appreciate your help.., I did what u told me to, and my phone is up and running now...! I had the flashtool, I flashed the stock .100 firmare on to my phone, and then moved on to the honami ROM.. Sorry for the late reply....
lalithesh said:
Thanks a lot dara, really appreciate your help.., I did what u told me to, and my phone is up and running now...! I had the flashtool, I flashed the stock .100 firmare on to my phone, and then moved on to the honami ROM.. Sorry for the late reply....
Click to expand...
Click to collapse
good to hear that bro
Sent from my Xperia U using xda app-developers app
Same problem on my XU with Honami
I have been facing the same problem with Honami on my Xperia U. I used the experimental v12 kernal. DO not reboot your phone (eihter in cwm or normal reboot). I was switching my sim and I forgot that the phone would reboot. It got stuck and I had to use flashtool, reroot and go thru the pain. This has happened thrice to me now. Dont let your phone reboot, restart. If you want to restart, then power off and then power on.
I am kinda scared that if this happens when I am away, I wont be able to repair the phone without a computer, flashtool, stock kernal, firmware. Even cwm is not accessible when this happens and its very scary.
The Rom otherwise is the smoothest JB you'll find, everything works well. I have already put in all the usual apps like whatsapp, gmail, hangout, stock fm radio from xperia, maps etc. No facebook - it is process and memory hogger.
I want to build a flashable ftf of my current setup of honami so I can flash it using flashtool. How do I do that. I dont want to flash the stock firmware and then restore the honami everytime. Is it possible to build an ftf and a boot.img kernal of your custom rom and kernal to flash with flashtool?
lalithesh said:
Thanks a lot dara, really appreciate your help.., I did what u told me to, and my phone is up and running now...! I had the flashtool, I flashed the stock .100 firmare on to my phone, and then moved on to the honami ROM.. Sorry for the late reply....
Click to expand...
Click to collapse
hi,
when you downloaded the rom from the link,
was is in *.tar format?
how did you manage to use it in flashtool?
thanks in advance.
Edits...
google-ed & got the full rom in *.tff format from the following link:
h t t p:// android.sc/install-official-jelly-bean-4-1-2-6-2-a-1-100-firmware-on-sony-xperia-p/
booting into 6.2.A.0.400
Stuck at Sony Logo
Heres the entire story which i posted as question but havent recieved a reply yet. Hope someone checks this and helps
OK i ve been trying to flash a new custom rom on my Xperia P, i looked at a number of guidelines and doing things step by step.
Since im very new to this i downloaded a few Roms. I was following the guide "http://droidors.com/2014/07/08/update-xperia-p-lt22i-to-android-4-4-4-kitkat-with-slimkat-custom-rom/2/" and everything was going fine. I reached the step to "fastboot flash boot boot.img", i did that and then went on the next step to boot in CWM Recovery and install the zip rom and the Gapps. During the Zip Rom install i got status 7 error.
Now, i noticed that i might have flashed the wrong Rom so rechecked the guide and installed the correct Rom which is mentioned in "http://forum.xda-developers.com/xperia-u/p-development/rom-slimkat-4-4-2-release-candidate-t2657795" and installed it through Fastboot. But now THE PROBLEM IS, AFTER I FLASHED THE INCORRECT IMG, MY PC IS NOT RECOGNISING THE XPERIA P SAYING IT DOESNOT RECOGNISE THE DRIVERS, therefore im not able to copy the ROM Zip on the SDcard, to then run it from CWM.
Please help.
After sometime i tried the below
After I flashed the SlimKat Rom, and things went out of hand ( till this point i could see Slimkat logo at boot and could also go in CWM Recovery ), I tried to restore through Nandroid Backup i had done. As soon i selected the restore option and then the backup file, within 2-3 seconds the phone went off, and then on boot all i can do is see "SONY" on screen. Nothing else happens.
Ok, now i tried to flash the stock Rom through this link "http://forum.xda-developers.com/xperia-u/p-development/ftf-firmware-xperia-p-generic-world-t2322163", through flashtool to bring my phone back to life. I installed the drivers as per instructions from drivers folder, but for some reason the pc is just not accepting. I did install through this exact method yesterday night and it worked perfectly.
Please suggest. I hope im asking at the right place.
Urgent help please
Kindly advise, im stuck with no spare phone.
OK, the flashing tool from Sony, EMMA enabled me to flash the jb firmware (it recognised my xperia p ) . once I got that working I managed to flash Cm11 on my device, with assistance from another user..
Thanks.. Hope it helps someone
General info on how to come out of soft brick, or bootloop, or status 7 error.
What you did is the right thing.
For someone who might experience the same thing ( flashed the kernel, got some error, and is stuck at bootloop), or has got the status 7 error, follow the below steps:
1) Download the LT22i_6.2.A.1.100.ftf file from the net, google a bit and u will find a download link.
1) Press and hold the power button + Vol Up. The phone vibrates once, and then after about 2 seconds, vibrates thrice, only then leave the keys. IT IS IMPORTANT TO WAIT FOR 3 VIBRATES. The phone is powered off now.
2) Hold the vol Up key and connect to the pc, it will connect in the fastboot mode, indicated by a violet notification light. If u dont get the violet light, you have not connected in the fast boot mode. remove the connection and repeat the above steps if necessary.
3) In flashtool, select the ftf file and carry on with the next instructions.
4) When it asks you to disconnect the phone and connect by holding menu key, disconnect the phone, hold the vol down key and connect it back. The flashing process will continue.
5) Disconnect once its done. Start the phone, wait till it loads up, Restart again, let it settle for about 5 min, you are good to go.
For status 7 error:
It is usually caused because of the kernel and rom not being compatible, or if the kernel is not compatible with the phone.., Follow the above steps to come out of it, find the right kernel and proceed as usual.. Hope this will help someone, Press thanks if it did.., Cheers.
I have a sony v3+ when i start it,it has stucked on the sony logo. what do i do
Hi All,
I have an Xperia Z2 D6503 South Africa (Vodacom) .402
I would like to de-brand it and possibly root it (will think on this).
Currently I am downloading D6503_17.1.2.A.0.314_Generic CA.ftf. Is this the right thing to do?
I am looking at XperiFirm but I am not sure how to find generic firmware there. I do get an option for 1281-8114/South Africa/Customized ZA (ver 314). What is this Customized operator? Is it essentially generic?
Currently I really hate Vodacom's customization. had them on my S3, S4 and now Z2 and they just break all the time. Plus I can barely use my dialer/contacts/call log so just want to reload but preferably sans operator crap.
I know there are plenty of threads out there that may possibly answer this question for me but I have not been able to find much regarding South African firmware and I am loath to just wing it without a little info from someone in the know.
Any help would be much appreciated!
Many Thanks
Tarn
tarnalcock said:
Hi All,
I have an Xperia Z2 D6503 South Africa (Vodacom) .402
I would like to de-brand it and possibly root it (will think on this).
Currently I am downloading D6503_17.1.2.A.0.314_Generic CA.ftf. Is this the right thing to do?
I am looking at XperiFirm but I am not sure how to find generic firmware there. I do get an option for 1281-8114/South Africa/Customized ZA (ver 314). What is this Customized operator? Is it essentially generic?
Currently I really hate Vodacom's customization. had them on my S3, S4 and now Z2 and they just break all the time. Plus I can barely use my dialer/contacts/call log so just want to reload but preferably sans operator crap.
I know there are plenty of threads out there that may possibly answer this question for me but I have not been able to find much regarding South African firmware and I am loath to just wing it without a little info from someone in the know.
Any help would be much appreciated!
Many Thanks
Tarn
Click to expand...
Click to collapse
Yes, "Customized" firmwares are those debranded ones.
You'll be fine with the Customized ZA.
Jackos said:
Yes, "Customized" firmwares are those debranded ones.
You'll be fine with the Customized ZA.
Click to expand...
Click to collapse
Thank you Jackos! Wasn't expecting such a fast response! I really appreciate it! :good:
BRICKED!
So I managed to brick my Z2 using the latest version of FlashTool/Xperifirm.
I upgraded it to 4.4.4, using a Generic UK variant as it is not yet available in my country, and my battery started draining tons faster and half of my apps would just close randomly (no errors) almost as if the back button was being pushed so much so that I could not type any messages or anything.
I tried to re-flash the previous 4.4.2 version (RSA Generic) and that just resulted in a boot loop. So I am back up and running using 4.4.4 but it is not going too well. Could anyone please give me some advice on the best step forward?
tarnalcock said:
So I managed to brick my Z2 using the latest version of FlashTool/Xperifirm.
I upgraded it to 4.4.4, using a Generic UK variant as it is not yet available in my country, and my battery started draining tons faster and half of my apps would just close randomly (no errors) almost as if the back button was being pushed so much so that I could not type any messages or anything.
I tried to re-flash the previous 4.4.2 version (RSA Generic) and that just resulted in a boot loop. So I am back up and running using 4.4.4 but it is not going too well. Could anyone please give me some advice on the best step forward?
Click to expand...
Click to collapse
Let me get a few screen shots ready then I'll help... I bricked mine last week - no issues...
---------- Post added at 03:13 PM ---------- Previous post was at 02:54 PM ----------
Here is what you should do:
01] Install the following drivers (assuming that flashtool is already installed) C:\Flashtool\drivers\Flashtool-drivers.exe and select the first two boxes as shown and the Z2 boxes at the bottom:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
01] Load Flashtool
02] Turn off the phone
03] Hold down the Vol-down button (and keep it down) and plug in the USB (hold the buttol will you see some output in Flashtool). You should see Windows install the Flashmode drivers in your taskbar if it has not done so yet. Flashtool should also show that the device is in flashmode. It is crusial that these flashmode drivers are installed before flashing. Just to make sure that the flashmode drivers are installed, remove the USB and repeat the pressing of Vol-Down whilst plugging the USB.
If all seems fine with flashmode in flashtool, remove device and go on to selecting the shown FTF, double click it after it is queried from the server and build the FTF ON YOUR OWN PC. Do not download an FTF from a site. They could be damaged. When selecting the files to build the FTF, select all files EXCEPT the *.ta ones. They should NOT be selected.
Then flash with the following boxes ticked and unticked:
Puffin617 said:
Let me get a few screen shots ready then I'll help... I bricked mine last week - no issues...
---------- Post added at 03:13 PM ---------- Previous post was at 02:54 PM ----------
Here is what you should do:
01] Install the following drivers (assuming that flashtool is already installed) C:\Flashtool\drivers\Flashtool-drivers.exe and select the first two boxes as shown and the Z2 boxes at the bottom:
01] Load Flashtool
02] Turn off the phone
03] Hold down the Vol-down button (and keep it down) and plug in the USB (hold the buttol will you see some output in Flashtool). You should see Windows install the Flashmode drivers in your taskbar if it has not done so yet. Flashtool should also show that the device is in flashmode. It is crusial that these flashmode drivers are installed before flashing. Just to make sure that the flashmode drivers are installed, remove the USB and repeat the pressing of Vol-Down whilst plugging the USB.
If all seems fine with flashmode in flashtool, remove device and go on to selecting the shown FTF, double click it after it is queried from the server and build the FTF ON YOUR OWN PC. Do not download an FTF from a site. They could be damaged. When selecting the files to build the FTF, select all files EXCEPT the *.ta ones. They should NOT be selected.
Then flash with the following boxes ticked and unticked:
Click to expand...
Click to collapse
Wow! Thank you for the informative post there Puffin. This is the same process I used to unbrick it but I had to stick with the newer ftf (4.4.4). Supposedly something to do with partitioning. Will ticking the boxes as you have done allow me to switch back to 4.4.2?
tarnalcock said:
Wow! Thank you for the informative post there Puffin. This is the same process I used to unbrick it but I had to stick with the newer ftf (4.4.4). Supposedly something to do with partitioning. Will ticking the boxes as you have done allow me to switch back to 4.4.2?
Click to expand...
Click to collapse
I did. I was on 4.4.4. I bricked my device by trying to install the TWRP recovery 2.8. I flashed the 314 (4.4.2) build to get my phone unbricked and started over...
PS: This does a full wipe of internal sdcard
Puffin617 said:
I did. I was on 4.4.4. I bricked my device by trying to install the TWRP recovery 2.8. I flashed the 314 (4.4.2) build to get my phone unbricked and started over...
PS: This does a full wipe of internal sdcard
Click to expand...
Click to collapse
I will try that. Thank you. Initially 4.4.4 seemed to be behaving but it has started doing random things again. Which is sad. I like the new look. And there are some nice little features I could get used to. Really don't know how they could release it so buggy. Then again I am way ahead of my country's release cycle. By the time we get 4.4.4, Lollipop will be old news already hahaha.
del.
Thanks Puffin617!
Thank you Puffin617. I was able to restore my phone as described.
I think the trick was ultimately ticking the 'Data' box which then overwrote the partition as I had previously left this un-ticked to preserve my data.
tarnalcock said:
Thank you Puffin617. I was able to restore my phone as described.
I think the trick was ultimately ticking the 'Data' box which then overwrote the partition as I had previously left this un-ticked to preserve my data.
Click to expand...
Click to collapse
Yip. Appart from the /data partition, that /sdcard/Android/data folder on the internal sd card is a poison when updating/changing between ROMs. I delete that folder EVERY time I flash a ROM.
Puffin617 said:
Yip. Appart from the /data partition, that /sdcard/Android/data folder on the internal sd card is a poison when updating/changing between ROMs. I delete that folder EVERY time I flash a ROM.
Click to expand...
Click to collapse
Good to know! Do you think that is what may have caused all of my problems with 23.0.1.A.0.32 in the first place? Was such weird behavior!
Volume button never worked
keyboards kept collapsing as if the back button was pushed (stock android/minuum/swiftkey all did the same)
apps would close randomly
Google Play Music would pause every time the screen orientation changed or if I turned a page too fast in Play Books.
Battery drain was significantly faster (10% passive drain in about 1.5 hours)
4k recording would not open, nor would the camera stay open for more than a few seconds (this was very intermittent)
In fact I eventually became convinced that there was a physical fault with the phone, but this is not the case (thank God!).
tarnalcock said:
Good to know! Do you think that is what may have caused all of my problems with 23.0.1.A.0.32 in the first place? Was such weird behavior!
Volume button never worked
keyboards kept collapsing as if the back button was pushed (stock android/minuum/swiftkey all did the same)
apps would close randomly
Google Play Music would pause every time the screen orientation changed or if I turned a page too fast in Play Books.
Battery drain was significantly faster (10% passive drain in about 1.5 hours)
4k recording would not open, nor would the camera stay open for more than a few seconds (this was very intermittent)
In fact I eventually became convinced that there was a physical fault with the phone, but this is not the case (thank God!).
Click to expand...
Click to collapse
23.0.1.A.0.32 was a test build - not an official release. You should've flashed 23.x.x.x.167
Puffin617 said:
23.0.1.A.0.32 was a test build - not an official release. You should've flashed 23.x.x.x.167
Click to expand...
Click to collapse
Ah. My bad I just Googled the version number quickly while posting to be accurate (fail!). haha! I did do 23***167_R2B (Generic UK)