EDIT: I managed to flash stockrom via flashtool, I didn't do anything different so I can't really help others with the same problems, I just kept trying.
But I can tell you the root of all the mess I did: Neowave ROM requires unlocked bootloader, which I didn't had. I'm still curious why it messes up everything and not only /boot
and /system, but I'm glad that everything works again.
So I managed to (hopefully soft)brick my phone again when flashing new rom. (from Omega to Neowave)
What I did:
-flashed new recovery (Philz Touch recovery)
-wiped /system
-flashed new rom, gapps minimal, aosp calendar sync addon and supersu update (all without rebooting)
-then I rebooted the phone, screen was black, no LED, only a vibrate at the beginning.
-PC detects it as SEMC flash drive, the phone automatically disconnects and then reconnects again after ~1min
-Repair with Sony Companion didn't work, it just said that there is no software for my phone
-adb devices said there are no devices
-I can't enter recovery or fastboot, only fastboot worked twice but I disconnected the phone because the Sony Companion said so
Additional info:
-rooted
-locked bootloader
What should I do now?
I wanted a new clean rom because the old one was so damn laggy and had many problems and high battery drain, and I'm going on a vacation
in 2 day so I'm in a hurry. I don't have a 2nd phone because this is already my 2nd (lost my LG G2 2 weeks ago..)
I hope u understand my struggle and take your time to help me, thanks in advance)
NO surrender
Tazmaniiac said:
EDIT: I managed to flash stockrom via flashtool, I didn't do anything different so I can't really help others with the same problems, I just kept trying.
But I can tell you the root of all the mess I did: Neowave ROM requires unlocked bootloader, which I didn't had. I'm still curious why it messes up everything and not only /boot
and /system, but I'm glad that everything works again.
So I managed to (hopefully soft)brick my phone again when flashing new rom. (from Omega to Neowave)
What I did:
-flashed new recovery (Philz Touch recovery)
-wiped /system
-flashed new rom, gapps minimal, aosp calendar sync addon and supersu update (all without rebooting)
-then I rebooted the phone, screen was black, no LED, only a vibrate at the beginning.
-PC detects it as SEMC flash drive, the phone automatically disconnects and then reconnects again after ~1min
-Repair with Sony Companion didn't work, it just said that there is no software for my phone
-adb devices said there are no devices
-I can't enter recovery or fastboot, only fastboot worked twice but I disconnected the phone because the Sony Companion said so
Additional info:
-rooted
-locked bootloader
What should I do now?
I wanted a new clean rom because the old one was so damn laggy and had many problems and high battery drain, and I'm going on a vacation
in 2 day so I'm in a hurry. I don't have a 2nd phone because this is already my 2nd (lost my LG G2 2 weeks ago..)
I hope u understand my struggle and take your time to help me, thanks in advance)
Click to expand...
Click to collapse
When a mistake is always better to return to the " factory " ROM before trying again . I recommend using flashtool . through fastboot , put his boot.img and then a flash the stock rom
I have a TX, roms and testing step that you like . but if the PC recognizes there is hope.
I'm using the google translator . : P
Tazmaniiac said:
EDIT: I managed to flash stockrom via flashtool, I didn't do anything different so I can't really help others with the same problems, I just kept trying.
But I can tell you the root of all the mess I did: Neowave ROM requires unlocked bootloader, which I didn't had. I'm still curious why it messes up everything and not only /boot
and /system, but I'm glad that everything works again.
Click to expand...
Click to collapse
You need to flash a stock ftf.
Keep us updated on how far.
sublinker said:
You need to flash a stock ftf.
Keep us updated on how far.
Click to expand...
Click to collapse
With flashing stockrom I meant flashing stock ftf, sorry for that.
Related
Phone Details:
- Xperia Z (T-Mobile) C6606
- Firmware or Build 10.1.1.B.0.166
I was able unbrick my phone and hope the method I used is helpful to others.
****Here's what happened.....******
Got the phone from T-Mobile had a lot of useless apps. Tried to root the phone all kinds of ways. Connected the phone to PC and opened up Flashtool. Flashtool did not detect the phone. I had to go into USB debugging and uncheck it off and check it back on, phone was detected and it says Root Access Allowed.
Installed Dual Recovery.. and installed the rom from zip. Rom instructions as follow:
Requirements: (Click on link below to get them)
1. Root - You probably don't really need this since this ROM itself also include stable and proper root package but most locked bootloader phones require root access to install recovery.
2. CWM/TWRP Recovery support - This is the real requirements. If you can access Recovery to flash this ROM, the rest should be working fine like root/busybox. Sadly you'll need either root or get custom kernel with recovery so you can forget root and be done with.
Instructions did not say install a different firmware, so I am thinking I can use my original firmware since the rom was based on a stock rom.
After installation of custom zip, cleared dalvik cache and reboot the phone. The phone bricked on me. All it did was cycle through the sony xperia boot screen and restart over and over again. I couldn't even get back to recovery(pressing vol. down on reboot) to restore my back up of my previous rom.
*****How I unbricked my phone*****
Remembered back in the day when I was flashing roms for on my previous xperia... I use Sony Companion Suite to restore my phone back to factory. Luckily it worked for my Xperia Z and now I am back with the stock rom.
Link for xperia Z tmobile repair.
sonymobile.com/us/software/phones/xperia-z-tmobile
Link for other phones.
sonymobile.com/us/software/phones/
Hope others find this post helpful.
i recently flashed the eXistenZ Ultra 2, and im sure i did everything fine, after flashing the rom in recovery and flashing suprsu and wifi fix, i powered off the phone, and powered on but sony logo has apeared until now , and welcoming`s sounding 999..times. i cant turn it off, or i should say i cant do anything.
please help,
After flashing ROM and the fixes you should flash the 12.1.A.0.266 Firmware with FlashTool!
If problem still persists:
http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Take a look at this site A recovery would be quite useful, but I think the kernel of eXistenZ ROM has one. If not, you'll find one in the development section. Otherwise, use the ADB as solution.
Good luck
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
eefathi said:
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
Click to expand...
Click to collapse
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Schokonuss said:
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Click to expand...
Click to collapse
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
eefathi said:
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
Click to expand...
Click to collapse
You're welcome
1. Do you have SuperSU installed? On AOKP ROM I'm running it asked for superuser permission for ROM Control (the control center implemented in the settings of the ROM). Maybe it'll ask you if SuperSU is installed. Otherwise, because it is after the first boot it needs to rebuild cache and so on.. If problem persists after reboot, just use an other clock speed controler (No-frills CPU, SetCPU..)
2. If you did that at the same time, maybe Go Backup didn't really backup your data. Try again, if it doesn't work and if you have a nandroid backup (backup from recovery) you can go into recovery, then to advanced restore and restore data. Otherwise your data is unfortunately gone I think :/
PS: I prefer Titanium Backup
Hi all,
I have received a brand new Xperia SP just a few days ago and I'm getting ready to install CyanogenMod 11. I actually chose this model specifically because there is a version of CM 11 with a lot of users.
Before getting my hands dirty, I am gathering all the documentation and info I can about it, and I'd like a confirmation I'm not forgetting anything or about to do anything wrong... This seems more complicated than what I did a year ago on my Galaxy Ace LOL!
For the record I'll be using an OpenSUSE Linux desktop. No windows here. So I guess this can also be used as a roadmap for other Linux users.
So my steps would be...
1. Get my IMEI number by typing #06# on the phone's keyboard then use it to get the unlocking code from http://unlockbootloader.sonyericsson.com/instructions
2. Download the latest ROM for "Huashan" from http://fxpblog.co/cyanogenmod/cyanogenmod-11/ - or should I take the one from http://download.cyanogenmod.org/?device=huashan ?
3. Extract boot.img from it, put it on the external SD card. Also put the whole zip there.
4. Place the phone in USB debugging mode by turning it off, then holding the up volume button then plugging in the mini-usb cable. It should flash blue (already tested).
5. Root the device using http://forum.xda-developers.com/showthread.php?t=2327472 - my version (12.1.A.0.266) is more recent than the one this was tested with (12.0.A.1.284) I hope this still works... As I understand rooting would be required only to backup the TA partition, correct?
6. Backup the TA partition using Flashtool (http://forum.xda-developers.com/showthread.php?p=46114879&highlight=linux#post46114879) which I got from http://www.flashtool.net/download.php - note to anyone attempting this: you will need Java 1.8 (I originally had Java 1.7 and Flashtool wouldn't start). Also, a specific Udev rule is required, see the "installation" page on Flashtool's website.
7. Install the Android SDK in order to have the "fastboot" tool.
8. Unlock the bootloader by running in a console: fastboot -i 0x0fce oem unlock 0xKEY (where KEY is the key obtained at #1).
9. In a console run fastboot -i 0xfce flash boot boot.img and then fastboot -i 0xfce reboot
10. While rebooting, press the volume buttons a few times to start in recovery mode
11. Once in CWM, do wipe data / factory reset and then install zip from card
12. Reboot
From there I should only have to install the Gapps from http://forum.xda-developers.com/showthread.php?t=2397942 and I should be good to go...
Did I forget anything?
Thanks.
Seb.
The method I quoted above for rooting isn't going to work on my device... I found that information at the end of the thread I referenced.
This should work theunlockr.com/2014/03/04/root-sony-xperia-sp-12-1-0-266/ but requires an unlocked bootloader which means losing the TA partition as I understand... Correct?
This would mean there is no way to backup the TA partition on that device...
Edit: I think I got it... From http://forum.xda-developers.com/showpost.php?p=50356952&postcount=8 - basically install an older version first using Flashtool - this shouldn't require rooting or unlocking the bootloader so the TA partition should be preserved. Root it with Doomlord's method. Backup TA with Flashtool.
Am I correct?
I am in the same situation as you. But I am in the latest firmware (.205) and so I used Towelroot for obtaining root and now I am going to use flashtool to backup my ta (I think that option it's integrated in the flash tool?). Then unlock bl and flash the cm nightly for huashan. But the question I have is, what baseband should I have for the cm nighties? Also, are they compatible with the C5303 model?
Hope we can both find our answers!
Sent from my C5303 using XDA Free mobile app
Edit: So far I backed up my TA partition, unlocked bootloader (which did a factory reset, so be aware when you do it! i backed up everything and so should you), now I'm updating and installing some apps to make sure I can create a CWM Backup that is pretty decent, soon I will flash the Kernel from the Cyanogenmod nightlies. So far I did pretty much like you are saying here, except that I rooted with much less hassle by using Towelroot. Btw if you want to install Cyanogenmod, dont install the Nightly from 16/07, that one is bugged and causing systemui FC, the bug is already detected and fixed for the next nightly, install the previous one and then install the one from 17/07
Edit: I am installing busybox now so I can make an Online Nandroid backup, this way I will have the stock rom fully backed up, including the correct kernel, so I can later revert back to a fully functional rom just from CWM Recovery. Then I will flash the CM kernel, boot it and flash the CM rom! Progress is going smootly so far
Edit: So far so good, installed the CM kernel, it doesn't show up the Online Nandroid backup I did tho, and I even moved it to the place it should be... I have to figure that out after, I backed up that nandroid to my pc too just in case, and I am creating a nandroid backup inside CWM, even tho it doesn't have the stock kernel in this backup, just in case there is a problem with the backup I did with Online Nandroid, at least I have the full system backed up and just need to pick a .ftf and install the .1.205 kernel only.. I am almost done with this nandroid will install the rom just after!
Edit: Process went very smooth, already booted on CM, everything is fine, I just forgot to install Gapps but it's okay I install later.
Edit: CM 11 is so much more smoother than Stock 4.3... You wont even believe how faster it is. The only drawback I got was the sound quality from the rear speaker, is not as good, still is decent (still better than my Xperia U, LOL)
Edit: Not sure about this tho but I think the Wifi is much more stable, I sometimes got randomly disconnected from my Wifi and so far it didnt disconnected on CM11!
Dude, just go on with it, root the phone, backup Trim Area (TA), unlock and flash CM11! You will like! Also, I saw FXP is working on Firefox OS for our device, seems like we will get another thing to play arround
Hello,
I flashed CM11 yesterday and everything went alright. This morning I noticed I had an update for it and proceed to do it.
After the instalation and optimizing all apps it asked me for my simcard PIN and after I unlocked the phone it just went back to the cyanogenmod logo over and over.
I tried to reboot phone but it didn't help.
I've tried to search for similar threads but since i'm a newbie (first time I ever flashed anything) to this I decided to create this thread.
What should I do?
Thank you!
try to use flashtool. google it on how to use flashtool or check other threads.
So I guess i have to flash a stock ROM with flashtool and do it all over again right?
And btw, any reason you guys might think It got stuck in bootloop after I updated CM11? I came from a fresh stock rom. I'm kinda scared it might happen again after the reinstall.
Can't you enter recovery to flash a nandroid backup? (If you have one)
If not, you have two options to choose from.
Fastboot or flash a kernel with CWM or TWRP.
ADB push a zip file of a ROM and flash that.
Flash an FTF file using flashtool and start all over again.
There are many reasons why you're stuck in bootloop at the moment.
With the info you provided, there's no way of telling what caused it for you.
Well, i flashed stock ROM with flashtool, installed CM11 and I had no problems.
Went to settings and OTA update was available. Downloaded it and installed it, stuck in loopboot again. I just can't figure out what's wrong. My phone has bootload unlocked.
Might just do it all over and not update, is that a problem?
Don't use OTA, just download and flash updates manually using recovery.
In the future, for your ease, if this happens again just wipe the phone very clean (cache, /system, /data etc except /boot) and then re-flash the CM zip that you have.
It is a good practise if you make a nandroid backup before flashing a newer version of zip, in case of breaks. Or, you can have Titanium Backup to backup your apps automatically (pro version) everyday, so that you can be ready if there will be something bad happen.
Hi everyone,
I really need help, I have tried everything I could think of and nothing works. So if someone more knowledgeable could help me, that would be great.
I followed the instructions in this thread https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
and everything went ok until I flashed a new ROM.
Current situation : Bootloop when I power up. Can still access TWRP recovery. Phone is recognized by flashtool/xperia companion/emma.
Tried to flash a new ROM with flashtool->error (can't read byte value), I tried de/re-installing flashtool and the drivers and different ROMs, always the same result
Tried to repair with xperia companion->error, can't complete
Tried emma->phone is locked
Tried sideloading ROM to flash through TWRP-> error
I don't understand how, even if I flashed a corrupted ROM, it could prevent me from flashing a new one over it?
Any ideas?
Thank you.
You can try xflasher tool as well.
https://forum.xda-developers.com/crossdevice-dev/sony/dev-xflasher-command-line-flasher-t2986634
But be warned - this is for more experienced users. I never tried it but it sounds like to be very powerfull.
For questions ask in xflasher thread... I never used it up to now...
But sometimes it helps to wipe cache/dalvik AND data from TWRP. Yes - all your data is away then!
Not nice to loose data but a bootable phone is even better...
Or flash again full ftf via flashtool. Wipe APPS_LOG/USERDATA (check boxes) but do not flash simlock.ta (if its there) !!!
This will wipe all your data as well..... While flashing, say NO to "fcs-script" popup.
. .
Thanks for the replies.
I tried different USB cable/port, no change.
I always selected to wipe everything in flashtool. I just got the phone so there was none of my data to save.
I will look at xflasher although, as you said, it looks intimidating...
. .