i am on Xperianze Rom v3.0.3 and got an update of CM, and when i flashed an update my device does not getting start, when i press power button nothing happen.
even i tried to reset my phone from back button, but still nothing happened. even my cell does not going into charging mode.
anyone can tell me what is the problem?
What update did you flash? An update for CM on a different ROM...?
If so, no wonder your phone isn't booting.
You'll have to flash an FTF file using flashtool. All data will be lost though.
As Gamm86 says, you'll need to flash a suitable FTF file. But in the future, do not install CM updates directly unless your phone has original CM software!
Xperianze is BASED on CM, but is not CM.
Related
I wanted to flash CyanogenMod 7.1 on my Samsung Galaxy S.
I flashed before a Froyo Bootloader (because I had Firmware 2.3.3) on it, copied the CM7.1 Rom on internal storage and tried to flash through Recovery.
While updating it shows me the install process till:
Checking state of BML/MTD
then it interruptes the install process and restarts the phone. But then it just shows me the Samsung logo and nothing happens (=freeze).
No chance to start the phone, altough I restart it several times.
Then I can flash again with Odin to the starting state again. The files for that I found here (german):
http://www.giga.de/smartphones/samsung-galaxy-s-i9000/tipps/samsung-galaxy-s-cyanogenmod-7-flashen/
EZodin
EZbase-CSC-XXJV1.tar.md5
EZbase-PDA-XWJS3.tar.md5
EZbase-PHONE-XXJVE.tar.md5
Ezbase.pit
How can I flash CM7.1 now..?
Sometimes the cm7 rom will need flashed twice....you should be able to flash from any gingerbread rom also as cm7 was updated a while back to allow this. Try again, and if the phone starts bootlooping-pull the battery, replace and get into recovery-then reflash rom.
Unfortunately i cant enter recovery after unsuccessful flash. I have to use odin and flash back to old froyo... then i tried to reflash again to cm7.1 but it was always the same.
Thx anyway for ur answer...!
Hmmmmm ;(
Gesendet von meinem HTC Desire mit Tapatalk
no ideas? it is urgent.. ;(
it's really strange. it happened to me and I solved like this:
I removed the battery
volume up key + power button + home button
in recovery,I wipe everything and reflash of the rom
If recovery doesn't work, you need to reflash a stock rom, and a kernel with root and CWM
puuhh, at least another one who had this issue...
ok i understood that if i cant flash to cm7.1 then i have to chosse another rom, maybe just a stock rom.
but can anybody recommend a custom rom which will work? it is just a file system problem here, isnt it?
Done it!
Trying to flash the stable Rom didnt work.
Then i tried the nightly (181) and it took a while then it restarted. but when it was starting for the first time i got a loop while booting.
but this time i could enter the recovery (after stable installation it wasnt possible anymore) and i could reflash it (nightly again). and this time it worked!!! yeah finally after over 8 hours of work....
i hope i could help somebody who has got same issues
Glad you got it -and cm9 is now an easy upgrade from the latest nightly
Hello everybody!
I used to have a working stock firmware 2.67 Android 4.2.2, but I decided to unlock my bootloader.
I did the operation twice and then I encountered bootloop issue.
I downloaded a stock firmware and flashed it using Androxyde Flashtool.
Oh god! The firmware FTF file was corrupted.
I AM sure that it was corrupted.
Next up, I booted my device but it won't let me inside: Just the SONY screen and a black screen and afterwards and it goes off.
Then I flashed CWM Recovery as a boot.img file. After that I entered (luckily!) the CWM recovery, Cleaned Cache and performed Hard reset and installed the CyanogenMod 10.2 Yuga Nightly (or sth like that) as a zip. It said that it had been successful.
Despite that, when I rebooted device through CWM, I got the CyanogenMod boot screen( a blue orbit moving around) and it shows that forever!
What is wrong with my smartphone?
How can I fix this thing without a fresh installation of the stock firmware?
And if you flash cm again without wipe data?
Do you tryed to flash only an other kernel?
Tipp: always do Backups before flashing new CFWs.
Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
zerkylo said:
Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
Click to expand...
Click to collapse
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
kalpetros said:
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
Click to expand...
Click to collapse
Thank you for answering!
I fixed the issue. Tried different usb port along with a different version of CWM (5.5.0.4) which I installed with Odin v4.43. CWM 5.5.0.4 caused a bootloop, but i used it only to install CWM 6.0.4.9 from external_sd, so the bootloop problem was gone. Then flashed CyanogenMod 11 and now works like a charm !
I attached an archive with CWM 5.5.0.4, AriesVE.ops and Odin v4.43, so that anyone having my problem can solve it the way i did. But keep in mind that this version of CWM *may* cause a bootloop, so prior to installing it, you should have a working version of CWM on your external_sd. Use CWM 5.5.0.4 to install the better version of CWM from your external_sd. Also, whatever you do is at your own risk!
Hi, Dear xda members
Last week i soft bricked my Sony Xperia Z c6603
After flashing modified kernel, i lost everything
I couldn't reach recovery even couldn't flash one with fastboot(as my device was not recognized)
I tried flashing offcial firmware through flashtool. It succeeded flashing
But After reboot i had bootloob and the ROM didn't boot
Finally I had a solution to get my phone fixed. Here's what i did:
*Reboot to FlashMode
*In flashtool I flashed TWRP Recovery in FlashMode
Now all custom ROMs are working but when I flash an official and other ROM's based on official, I'm having bootloops
Tried to wait. NO result
Could you help me with it?
P.S the modified kernel was made by this tool http://forum.xda-developers.com/xpe...ot-automatic-repack-stock-kernel-dm-t3301605/
When i softbricked my phone I tried to fix it according to this guide http://forum.xda-developers.com/xpe...rick-sony-xperia-z-c6602-c6603-c6606-t3215134
after i flashed the cm rom, i got the same problem. after flash the stock ROM or official firmware, It keep bootloop. how you fixed It ?
315cqab said:
after i flashed the cm rom, i got the same problem. after flash the stock ROM or official firmware, It keep bootloop. how you fixed It ?
Click to expand...
Click to collapse
Do you still need the method i have gone through?
do you know how to flash the official ROM or firmware back? now i can only flash the custom ROM
315cqab said:
do you know how to flash the official ROM or firmware back? now i can only flash the custom ROM
Click to expand...
Click to collapse
Sorry even i need this. Currently i have the same problem. I cant flash official firmware or the one that is based on official. I need the solution
Same here, after install CM 14.1, i can't go back to official or rom based in Stock...
gussbravo said:
Same here, after install CM 14.1, i can't go back to official or rom based in Stock...
Click to expand...
Click to collapse
I have several problems too including not being able to run stock anymore. (endless black screen after experia logo). I tried flashtool (latest stock via xperifirm), Sony's flashtool. Companion didn't even want to flash (UEGetPhoneInfoMissingInfo), and left me wondering wether something is corrupt.
I've been running CM's for a while now and was wondering why NFC was not working. Not sure if it needs an updated firmware or what.
Other problem I've seen is that "fastboot flash recovery" always gives an error. "fastboot flash boot" works (this is how I install TWRP).
Can I try zeroing mmcblk0 or would that brick it? (does it really need to have a TA partition to accept boot connection? How does Sony init it anyways?)
I think I have a mmcblk0 backup from after unlocking (DRM lost though) but perhaps that will give me a somewhat clean situation again. Or perhaps I can compare it.
Edit: dd-ed my old mmc backup and now Xperia Companion didn't give an error anymore, did a factory reset, and after a long wait of the blue waving animation, I got it to work.
Even NFC firmware update started after rooting and deleting /data/ucf folder.
Now I want to go back to Nougat xD
Hi Friends,
I have played a lot with xperia z and never got into such situation.
So i have been using this resurrection remix 7.1.1 rom 12122016 build, and wanted to switch device so to give this device to my family member i flashed .222 5.1.1 as he is not techy like me and wont be able to fix problems on his own.
now the thing is i am stuck at black screen after sony logo
I know kernel is there there is just some system issue and to fix it i did below things still no success.
1. flashed ftf 6602 (Double checked and re downloaded FTF in case ftf was courrepted)
2. used emma tool and updated phone
3. flash twrp and flashed Xperia_Z_eXistenZ_Premium_v4.0.0
non of about gave me stock Rom and now i am stuck at non system in my phone just kernel mean as soon as i start my phone there is sony logo but after that there is no process.
Help would be great solace.
Thanks
chauhanjayc said:
Hi Friends,
I have played a lot with xperia z and never got into such situation.
So i have been using this resurrection remix 7.1.1 rom 12122016 build, and wanted to switch device so to give this device to my family member i flashed .222 5.1.1 as he is not techy like me and wont be able to fix problems on his own.
now the thing is i am stuck at black screen after sony logo
I know kernel is there there is just some system issue and to fix it i did below things still no success.
1. flashed ftf 6602 (Double checked and re downloaded FTF in case ftf was courrepted)
2. used emma tool and updated phone
3. flash twrp and flashed Xperia_Z_eXistenZ_Premium_v4.0.0
non of about gave me stock Rom and now i am stuck at non system in my phone just kernel mean as soon as i start my phone there is sony logo but after that there is no process.
Help would be great solace.
Thanks
Click to expand...
Click to collapse
First of all: read the forum rules. After 1400 posts you should know that the GENERAL section is not the right place to ask questions like this.
Second: Wich file system are you using? If it's any other but ext4 you should format the storage using twrp.
Did you flash with Androxyde's flashtool, or just with Emma?
Hey ! i too experienced the same issue earlier today.. Only the latest build isnt working when flashed ..I flashed the kitkat build via flashtool and it worked.. is there any solution.. ? ive been trying since morning.. And another thing is that recovery also cant be flashed . So im literally stuck at this phase. :crying:
just flash a stock rom from flashtool i always encounter that when i corrupt flashing thru recovery.. like i fully wipe and forgot to put rom in internal lol
Flashed with both Emma and flashetool
Even tried custom lp rom via twrp but the same situation
Have you fixed your issue? I have the same case. I flashed it to stock ROM but the black screen is still occurring after xperia logo.
1. make sure your partition is ext4
2. download proper official Kitkat 4.4.4 firmware (.tft), flash it with Androxyde's flashtool (make sure the .ftf is not corrupted, driver is installed, good usb cable and 75% of battery or above).
3. if you wanna check the device is in good shape, try to boot up (in my case, I'll flash LP 5.1.1 right after flashing KK firmware is done).
4. if the device is boot up correctly, turn off your device and begin to flash LP 5.1.1 firmware
NOTE: somewhere on this forum say about the right version of flashtool to flash the firmware to our device, older version of flashtool. But I'm using version 0.9.22.3 and everything is fine. However, I can see that the flashtool is not using the newest engine while flashing my device (C6603) but using the older engine instead.
Hi,
I have already been in such a situation.
1) Try to flash (with flashtool) official 4.2 Android firmware, boot, then flash latest one (5.1.1)
2) Try to flash official firmware (4.2) with xflasher (https://forum.xda-developers.com/showpost.php?p=74122327&postcount=212, https://forum.xda-developers.com/showpost.php?p=74122295&postcount=2)
Good luck!
still having same issue with my z3, flashing with emma and tft but stuck on sony logo
I also met this problem yesterday.
I use the latest Flashtool and flash the latest firmware but it said The bundle does not match the connected device.
Then I use a older version like 0.9.18 to flash the latest firmware. The problem you said occurred. It stuck in black screen after Sony logo.
Here is how I fix it:
1. Use an older version of Flashtool to flash an older firmware such as 4.4.4_10.5.1.A.0.283 like me.
2. After flashing the old firmware it should be normally powered on. Then power off and enter the flash mode again. And flash the latest firmware, problem fixed.
Hope that my experience can offer a bit help for you.