hi all im hoping u can help me i have an xperia play which i tryed to root using cynogen mod 12 but it fails on install it will then reboot and show the blue cynogen logo but sit thier untill battery pull. i can access cyonogen recovery but thats all. ive tried installing other roms such as 9, 10 and 11 but all do the same thing (although 11 does seam to install/unpack).
i unlocked the bootloader and rooted the phone successfully. i also used flashtool to flash the boot.img.
i have heard i could fix the problem by sideloading another better recovery tool but i dont know how to do that. as off now im stuck in cynogen recovery.
any advice you could give would be greatfully appreciated, at this point im completely out of ideas and if you need anymore info i would be happy to provide it
thanks in advance
Hi,
It would be nice if you linked the exact ROM you tried to flash on you phone. It sounds like the boot.img is incorrect.
You can try flashing this kernel forum.xda-developers.com/showthread.php?t=1804003 . This one is for ICs roms(4.0.x).
Or this one - for Jelly Bean versions(4.1-4.2) - forum.xda-developers.com/showthread.php?t=1861970 .
All you have to do, is boot into fasboot mode and flash the given .img file as boot.img. (The difference between 480p and 720p kernels, are that 480 can't capture 720p videos, but sometimes 720p kernel doesn't work with all roms).
hi tnx for the help the rom i tried to install was cm-12-20150314-UNOFFICIAL-LegacyXperia-zeus
i think your idea would work but im unable to boot into fastboot mode as i used flashtool before and it doesnt recognise my phone anymore ( i dont know if i can use ADB as that option is available on my boot loader)
if you could provide me with a link to how to flash a new .img/rom using another way other than flash tools that would be really helpful. im sry to be such a noob, i have rooted every phone i had and never encountered this problem before and am completely stuck.
tnx again for your help
ok ignore my last msg i managed to flash the .img in fastboot no problem but now it wont let me into recovery mode so i think im stuck in some infinate boot loop no matter how many times i click volume down it just reboots after about 2 mins, anything i can do about that or am i now really bricked?
tnx again for your help
rob17zero1 said:
ok ignore my last msg i managed to flash the .img in fastboot no problem but now it wont let me into recovery mode so i think im stuck in some infinate boot loop no matter how many times i click volume down it just reboots after about 2 mins, anything i can do about that or am i now really bricked?
tnx again for your help
Click to expand...
Click to collapse
Well you could try to return to point zero by flashing your phone to stock rom and try to begin from there.
You can do that by using flashtool and downloading stock ROM from these forums.
BTW, you can enter flash mode by inserting usb cable and holding search button(i think, you can try other buttons). Your LED has to turn green, blue is fast boot.
Also if your flashtool give you errors, download earlier version (see some other threads about flashtool, there are links to older version). Maybe it doesn't recognize your phone, because of the new version, i've had problems with it too, but i had to download old version and everything started to work as expected.
Related
sorry folks. i can't figure this one out. i f ed up and stuck xperia play att in clockwork loop during boot. tried a billion things including re flashing doomsimg . i tried installing r800a current bulid but still can't get out of clock work. if someone fixes this i'm in their debt
i still can fastboot. I just want to get back to stock
alright got r800a fw onto phone everything is working good except no root. did i loose unlock during flashtool fw update? how can i check? I can get to clockwork.
if i am unlocked how can i get doom to boot? everytime i flash tool boot boot the phone gets stuck on the cool android logo.
stuff about my phone
android 2.3.3
kernel version 2.6.32.9-perf (help putting dooms kernel on this would be nice I think thats the way to go but i dont know how to install it no .ftf or .sin as far as i can find)
build: 4.0.A.2.368
THANKS!! THANKS!!!
Just because i feel stupid i figured i'd post my solution
1. unlock by finding imei in aboutphone-status-imei
2. follow the unlock guide phone in fastboot spits out already unlocked (yea!)
3. flash boot boot
4. keep connected to computer when finished after screen flashes on then turns off disconnect (here is where i got stuck in a loop wouldn't boot past animation until finally turning off while conected to computer)- 5days of searching because i wasn't patient enough to wait a minute before disconecting phone from computer. *Banging my head loudly*
5. reboot
6. enjoy and buy a beer
manwhosoldtheworld said:
sorry folks. i can't figure this one out. i f ed up and stuck xperia play att in clockwork loop during boot. tried a billion things including re flashing doomsimg . i tried installing r800a current bulid but still can't get out of clock work. if someone fixes this i'm in their debt
i still can fastboot. I just want to get back to stock
Click to expand...
Click to collapse
Did you flash clockwork instead of just booting from it?
Sent from my R800x using XDA App
clockwork problem
Thanks for the reply. That was the problem initially I flash system instead of booting did a flashtool.back to stock thanks to.some wonderful posts by doom xxxxsonic plus others. I love xda
Anyway now I can't get root again after using flashtool to get to r800a 4.0 baseband used doom kernel for appropriate baseband I get stuck on boot v2 and three fastboot flash boot I only get the cool logo never boots
I'm going to scour the forums again something about fastboot clear cache then retry doom fix v2 plus zoom
I dunno after hours and hours I'm back to having a working phone no root but no shifty bloatware either
Anything on how to root this I can still get into clockworkI would be thankful
Hi,
I've just rooted the device (c6503), backed up TA-keys, and finally unlocked the bootloader using the official way through sony website. The phone booted fine and my next step was flashing a custom rom... That's when **** happend. I downloaded P.A.C True All in 1 ROM[Nightlies] and followed the instructions how to flash. Flashed the boot.img and then you need to reboot the device in recovery but the 3 sec violet led never happend...
Now I have downloaded stock ftf (C6503_10.1.A.1.434_Customized_DE.ftf) and want to flash it with flashtool but I'm unable to boot the device in flashmode (green led). I can however boot in flashboot mode (blue led) but as I understand, that doesn't help because i can't boot into recovery.
I never flashed a recovery, is that a problem?
What can i do now? Is the phone bricked?
Thanks in advance!
Now I have downloaded stock ftf (C6503_10.1.A.1.434_Customized_DE.ftf) and want to flash it with flashtool but I'm unable to boot the device in flashmode (green led). I can however boot in flashboot mode (blue led) but as I understand, that doesn't help because i can't boot into recovery.
-----------------------------------
It happened to me also.
Start Flashtool, choose your xxxx.ftf and wait till it totally loads (do not connect your phone yet). Now, when your Flashtool is totally ready and the small window opens with the instruction how to connect the phone, open the small backcover of your phone and press-hold the small yellow button till it rings x3 times (it takes ~10-13 seconds to hold the button). Now, do not waist time, press-hold volume down and insert the usb cable, the flashing should start.
I had similar problem and I guess my phone root is corrupted, I cannot download updates directly from Sony but I can flash updates without problems.
If anyone knows how (if its possible) totally reflash everything, you help will be appreciated.
Good luck.
Alright, it seems like I'm having some problems with the usb drivers for flashtool... Are there different drivers for flashmode and fastboot? Because the fastboot drivers seems to be working correct but not flashmode drivers. Running windows xp, maybe that is a problem too Can someone please point me to the right direction of where i can download those usb drivers?
I have the modified android_winusb.inf for the Xperia Z but that doesn't seems to be enough.
I managed to flash FXP cm10.1 and got it running which also gave me a working recovery. But I would like to try out the P.A.C True All in 1 ROM[Nightlies] but when I flash the boot.img of that one I lose the recovery.... Weird, my old HTC desire Z always had the same recovery without any problems while flashing all kinds of ROM:s. This is indeed confusing.
Should i flash the boot.img of the ROM and then a recovery? If so which recovery? As i understand all the recoveries are for stock kernel but the kernel for these custom ROM:s could not be stock right? I'm a bit confused here really
Excuse my bad spelling and such, english is not my main language.
Thank ChimPilot for the quick reply!
Go to Google Play Store and download: Superuser, X-parts and ROM manager. Those are must haves if you are playing with ROMs.
You are in better shape if you can access the bootloader because I cannot, so I am considering to reflash everything and that would be my weekend project.
The problem I have is corrupt path to root and so Sony's PC companion spit me out, Sony's SUS does not go through and my last try would be Emma but it requires unlocked bootloader which is corrupt in my case. If anyone would give me a hint which directon to follow, it would be much appreciated. Thanks.
Hello there, all xda members.
I got Ace 2 to fix from my friend. He doesnt know exactly why did the phone becoming stuck on bootlogo. Maybe messing up with flashing GB or JB. or maybe wrong terminal command.
Ace 2 Condition :
- Its unable to pass boot logo samsung galaxy ace 2
- Its unable to enter recovery mode
- Its able to enter download mode, and its custom binary download : No, Current binary : Samsung official
Here all the thing that i have tried to fix the phone :
1. Flashing the phone with Russian Gingerbread with 3 files, Pit, CSC, and PDA. But it still stuck on bootlogo and unable to enter stock recovery. it shows succeed though on Odin, but it can't boot.
2. Flashing the phone with Latest Jelly bean, with Jelly bean pit file. Odin displaying succeed, but it doesnt boot either.
Can someone help me how to solve this problem?
Is there a condition where phone completely unable to recover from hardbrick such as stuck on bootlogo, but still able to enter download mode?
I'm going to download jelly bean mb2 or mb4 which include pit and csc from jelly bean and try to reflash it. Hope it gonna work.
Thanks for any help.
Anyone here to help me?
@ChronoMonochrome , maybe you've experienced something like this and able to resolve the problem.
The phone can't boot at all. and im a little frustrated here. I've already tried a 3 parted firmware MB4, and it doesnt work either. Tried to flash chrono 4.3 cwm through odin and it doesnt work either.
And if it really doesnt have a solution, maybe i'll just give it up. And doesnt continue researching to fix this phone. Thanks
maybe another devs that able to fix this. @ace2nutzer @fluffi444 or anyone??
It got the same case. Successfull flashing, but still doesnt boot, it just like flashing is fail. or it just like it reverted the way it was before flashing. Your help is very appreciated.
riyosakura said:
maybe another devs that able to fix this. @ace2nutzer @fluffi444 or anyone??
Click to expand...
Click to collapse
Very strange. And more strange is that several people have this "only boot to logo / only downloadmode issue"
Up to now I have no Idea - I asume that ADB is not working, because of missing recovery mode? With ADB there are plenty of possibilities.
An complete Factory reset could be helpfull - But how to do it out of downloadmode ?! Don't know.
Up to now I didn't had a Phone with this behaviour for repair at home. If it would be reproducible how this all happens, I would bring my phone to this state to find out how to repair it (riff box here - so dead ACE 2 is not a problem) - But even this is unclear - Every report regarding this said only "suddenly" "without any reason" "flashed this or that" - But no exact infomation what happend acctually.
I'm out of Ideas. Sorry!
Thanks for answering.
I dont know if i have to give up already or not. But i'll try to flash it with another pc and data cable. Maybe it gonna work.
riyosakura said:
Thanks for answering.
I dont know if i have to give up already or not. But i'll try to flash it with another pc and data cable. Maybe it gonna work.
Click to expand...
Click to collapse
Another try:
Flash with ODIN Ace2Nutzers Stock Kernel (search on FTP)
Do not let the Phone boot
After Flashing pull usb und press drictly the 3 keys to get into Rec. Mode
riyosakura said:
Anyone here to help me?
@ChronoMonochrome , maybe you've experienced something like this and able to resolve the problem.
The phone can't boot at all. and im a little frustrated here. I've already tried a 3 parted firmware MB4, and it doesnt work either. Tried to flash chrono 4.3 cwm through odin and it doesnt work either.
Click to expand...
Click to collapse
No, I haven't had the phone in such condition as described above. But I have heard that any odin-flashable file that's wrongly flashed via "Phone" entry can lead brick which is similar to this. I remember only one case - one user from 4pda has flashed some file via odin, wrongly putting file to the "phone", and wasn't able to restore it anyhow - but he also had some brick on GPIO side - vol.up worked like vol.down, and the real vol.down didn't work at all. I don't know however, what memory partitions / any devices capable of storing data would be messed after this operation, and whether it's reparable at all. I mentioned devices, that can also store data, I know only that touchscreen has small memory for its firmware(that what I had broke one day in the past after accidental firmware change in the kernel) - but maybe some other devices also has it?!
There are also some chances that it's dead flash memory - chances are pretty small, but should also be taken into account.
Hello everyone here, im a noob around these parts but hope that this beautiful community might help me.
So heres the deal, my gf got an xperia m, that outta the blue started acting out, what i mean for this is, rebooting, outta nowhere and eventually a couple of days later it died.
Making my investigations to get to the problem and therefore the solution, she stated that putting it on the SUS or SONY Pc Companion didn't help at all, plus keep getting error 0x0000067 or 0x000007d5 on PC Companion.
After seeing this, she says tried to unlock the bootloader to install a CWM 6.0 for the 15.4.A.1.9 software, wich it had running, didnt got through since the moment she enter the command through fastboot to check the bootloader status throgh the command fastboot flashing get_unlock_ability but no response just stuck on three dots.
Also tried to flash through FLASHTOOL installing the drivers and everything as ive done with other decives checking everything is okay, which they are, since ive succefully recovered an brick C1904 using CWM with a previous Backup, but the tool gets stuck on flashing loader and wont give a percentage.
Tried Flashing remotely the CWM.img to the boot, but it wont flash, always failed, as for specifics about the code, If really needed ill post them on the next reply.
Hope Someone can Help me,
Regards Jmaquilon
Which error are you getting while flashing the recovery? is it something like remote command not allowed ? If it is then try to flash the recovery in the boot partition (I have done the same many time cuz there are some problem s with my current kernel)and what happens is instead of system the recovery boots up ..
If this doesnt works then try xperiafirm it may bring your phone back to life!
Hope it helps!
Just flash stock rom using flashtool software. Download the Stock Sony Xperia M Rom here http://forum.xda-developers.com/showthread.php?t=2699085 and flash it using flash mode in flashtool. Good Luck
HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler
Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom
Tsuragi said:
Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom
Click to expand...
Click to collapse
Thanks Tsuragi,
Forgot about that - it was me who posted that solution some time ago duh!
Pootler
pootler said:
HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler
Click to expand...
Click to collapse
Hey bro same experience, thats why im stock in android 10 with unlock bootloader. but i successfully flashed lineage with unofficial twrp but the problem is i cant flashed gapps thats why i cant install pre apps and cant use the default message and call. please help me